The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2002-Apr> msg00152



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

PHP

  • From: Eric Rosen <erosen@cisco.com>
  • Date: Thu, 18 Apr 2002 12:18:49 -0400
  • cc: mpls@UU.NET
  • User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3(Unebigoryōmae) APEL/10.3 Emacs/21.2(sparc-sun-solaris2.6) MULE/5.0 (SAKAKI)


David> I would argue that it should not shunt incompatible traffic into that
David> LSP.  Don't allow a non-IP LSP to tunnel through an IP-LSP. 

What would be the point of this? 

I  admit I've  never  quite understood  the  role of  the  L3PID in  RSVP-TE
signaling. 

In practice, the only situations in which PHP causes a packet's bottom label
to be  popped off are  situations in which  the payload is an  "ordinary" IP
packet.  If the  payload is a layer 2  frame encapsulated via draft-martini,
or a VPN packet encapsulated according to one of the L3VPN schemes, then PHP
will never result in the bottom label being popped off.

So in practice, PHP always results in either an IP packet or an MPLS packet,
and the  appropriate ethertype (IP or  MPLS) can then be  applied before the
packet is transmitted to its next hop.


  • Follow-Ups:
    • PHP
      • From: Kireeti Kompella <kireeti@juniper.net>
    • PHP
      • From: David Charlap <David.Charlap@marconi.com>
  • References:
    • PHP
      • From: David Charlap <David.Charlap@marconi.com>