The MPLS-OPS Archive

[Kumar S <ps2kumar@yahoo.com>]

Hi Daipayan,

Unlike L2 VPN TTL need to be propagated through MPLS core incase of L3 VPN. TTL value of the IP field has to be copied to the MPLS label during label imposition at the ingress router as is the case of normal MPLS path.

 

The reason why RFC specifically says 2 is added in TTL field to the VC label in case of L2 VPN is L2 VPN is a pseudo wire service between customer edge devices and is emulating some layer 2 service. But this is not the case with L3 VPNs where L3 routing in the core is always assumed by Customer.

 

Regards

Shailender

 

Daipayan Kar Choudhuri <daipayan@deccanetworld.com> wrote:

Hi all ,

           I have a query regarding the VPN Label value for L3VPN . What should be the TTL value for the VPN label at the ingress PE ?  As I understand from the martini draft for L2 Transport  the TTL value of the VC label is set to 2 at the ingress but RFC 2547 does not discuss about the TTL value of the VPN Label at the ingress . Please throw some light on this.

 

Regards,

Daipayan

 

********************************DISCLAIMER**********************************

This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege of Deccanet Designs Ltd.
If you have received this message in error, please notify the originator
immediately. If you are not the intended recipient, you are notified that
you are strictly prohibited from retaining, using, copying, altering or
disclosing the contents of this message.

****************************************************************************

---

Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online