The MPLS WG Archive

["Busschbach, Peter B (Peter)" <busschbach@lucent.com>]

Loa,

Two questions about the end of the document:

TTL Management: What exactly is the concern? Is it that the operator would set a TTL value assuming that the uniform model is used, while in fact the T-MPLS core uses the pipe model and does not decrease the TTL value in the way the operator expected? If so, is it realistic to assume that the operator would not be aware of this?

Interoperability over interface between MPLS and T-MPLS networks: are we merely pointing out that the T-MPLS spec should address these issues, or is there a really concern that this will not work? E.g. PWs use per-platform labels because of potential PHP. However, I don't see how not using PHP would invalidate the existing PW specs. Same comment for VPNs. Am I missing something?

Peter

> -----Original Message-----
> From: Loa Andersson [mailto:loa@pi.se]
> Sent: Tuesday, April 18, 2006 6:31 PM
> To: mpls@ietf.org
> Subject: [mpls] list of concerns on T-MPLS
> 
> 
> All,
> 
> this is the very preliminary information we sent to Q12/15 on
> T-MPLS. The intention is to consolidate it further during this
> week.
> 
> Comments appreciated.
> 
> Loa and George
> 
> -- 
> Loa Andersson
> 
> Principal Networking Architect
> Acreo AB                           phone:  +46 8 632 77 14
> Isafjordsgatan 22                  mobile: +46 739 81 21 64
> Kista, Sweden                      email:  loa.andersson@acreo.se
>                                             loa@pi.se
> 

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls