The MPLS WG Archive

[Curtis Villamizar <curtis@fictitious.org>]

In message <F15716MF6StXOplCSyT00033fce@hotmail.com>, "Sandeep B" writes:
> There are few other things - e.g. L3PID. GMPLS explicitly defines that for 
> Lsps that carry a certain type of traffic it needs to signal that using GPID 
> e.g IP lsp should set certain GPID and L2VPN-MPLS lsps a certain other GPID. 
> But there is no such defination in classic RSVP-TE. Such a case what should 
> be the criteria. Do we follow GMPLS RSVP-TE or classic??
> 
> Particular to this question - Do we have finally decided what should L2VPN 
> lsps signal as their L3PID????
> 
> http://cell.onecall.net/mhonarc/mpls/2002-Apr/msg00163.html
> 
> 
> 
> GMPLS def ==>>
> 
>    The G-PID parameter is normally only examined at the egress.  If the
>    indicated G-PID cannot be supported then the egress MUST generate a
>    PathErr message, with a "Routing problem/Unsupported L3PID"
>    indication.  In the case of PSC and when penultimate hop popping
>    (PHP) is requested, the penultimate hop also examines the (stored) G-
>    PID during the processing of the Resv message.  In this case if the
>    G-PID is not supported, then the penultimate hop MUST generate a
>    ResvErr message with a "Routing problem/Unacceptable label value"
>    indication.  The generated ResvErr message MAY include an Acceptable
>    Label Set, see Section 4.1.


Look at L3PID in rfc3209.txt

      L3PID

         an identifier of the layer 3 protocol using this path.
         Standard Ethertype values are used.

Curtis