The MPLS WG Archive

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



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

PHP

  • From: "Vach Kompella" <vkompella@timetra.com>
  • Date: Thu, 18 Apr 2002 15:26:02 -0700
  • Cc: "David Charlap" <David.Charlap@marconi.com>, <mpls@UU.NET>
  • Importance: Normal
  • X-OriginalArrivalTime: 18 Apr 2002 22:24:02.0964 (UTC) FILETIME=[BE8B8540:01C1E727]

I like that idea.  Since, from a need-to-know point of view, the outer LSP
doesn't care, why make it visible?

-Vach

> -----Original Message-----
> From: Kireeti Kompella [mailto:kireeti@juniper.net]
> Sent: Thursday, April 18, 2002 3:08 PM
> To: Markus Jork
> Cc: Vach Kompella; David Charlap; mpls@UU.NET
> Subject: Re: PHP
>
>
>
> On Thu, 18 Apr 2002, Markus Jork wrote:
>
> > It looks to me as if the L3PID signaling seemed like a good idea at the
> > time but turned out to be not particularly useful.
>
> It's not that bad, but it is less than optimal.  One could use IP
> LSPs for IP, IP VPNs, etc., where the payload is IP; and establish a
> parallel set of LSPs for non-IP traffic.
>
> > Maybe it should be redefined to only
> > apply to packets with a label stack of 1 while all other packets on
> > the LSP with label stack > 1 are simply of unknown protocol type.
>
> That was my suggestion when this topic came up 2+ years ago, got
> little traction.  I still like it, though :-)
>
> Kireeti.
>


  • References:
    • PHP
      • From: Kireeti Kompella <kireeti@juniper.net>