>The requirement for router("r" in below ase) between 2
>targeted session peer is capable of mpls forwarding.
>
>Question: in the case where R2 as the egress for FEC x
>and R2 assigns label 0 as label binding for fec x on
>its session with R1 ; now If transit LSR 'r'
>forward the mpls frame(w/ label 0) to R1, does it
>violate the RFC since RFC says LSR has to pop mpls
>frame w/ label 0 ?
First of all R1 needs to forward the frame to 'r'.
I think this is what u meant [not the other way around]
---
Thanks for the correction.
At R1, there needs be a 2 level label stack for the LSP
corresponding to FEC x outgoing towards r
The bottom most is the one corresponding R2's label [value = 0]
The top most is the one corresponding to r's label [value = 'a']
---
Targeted session with 2 label stack (rsvp over ldp) is more to vendor implementation,
as per-RFC there's no requirement for targeted session that should be in two label stack format.
To be more precise, in targeted session w/ one label stack environment, is it acceptable
for transit LSR to forward mpls frame with exp-null label ?
Carlos