The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2005-Oct> msg00014



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

[mpls] TTL exception processing on P2MP LSPs

  • From: Harish Sitaraman <hsitaraman@avici.com>
  • Date: Tue, 11 Oct 2005 16:00:03 -0400
  • X-Avici-MailScanner-Information: Please contact the ISP for more information


Hi,

How does TTL expiration on the MPLS header work for P2MP LSPs ? If the 
payload is IP, then the ICMP error message (such as time exceeded) is 
tagged and sent along the LSP towards the egress, which would then 
hopefully route the packet towards the source. For P2MP LSPs, wouldn't this 
packet be replicated across all the branches ? If so, the set of egress PEs 
that receive this packet might route this packet towards the source. Is 
this an understood behavior for P2MP ? This probably doesn't cause any 
issues at the ingress when it receives multiple similar ICMP error messages.

I'm aware of the draft proposing P2MP extensions for LSP ping. If tools 
such as mtrace are used in IP multicast networks, will these work with P2MP 
LSPs ?

Thanks

Harish


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