mpls6a----Page:4
1 2 3 4 5 6
|
Proposed Solution Heavy re-use of LSP Ping Need to identify the LSP LSP Ping has RSVP Session sub-TLV We need to identify a P2MP LSP Introduce RSVP P2MP Session sub-TLV Ingress can control ping/trace of whole tree or individual recipients Necessary to protect the ingress from being swamped Introduce P2MP Egress Identifier sub-TLV (of FEC Stack TLV) P2MP LSP Ping Echo request cannot be filtered based on identified recipient Echo response only from targeted recipient P2MP LSP traceroute Echo request cannot be filtered based on identified recipient Only LSRs on the path to identified recipients respond |