TTL Processing expansion for 1-hop LSP
draft-satoru-mpls-1hop-lsp-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Shigeki Matsushima | ||
| Last updated | 2001-07-23 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The structure that LSP was handled as 1-hop became necessary. It came from the requirement of LSP topology management in the MPLS network. As for VPN services using LSP, VPN customers may be confused by receiving ICMP packet, e.g., traceroute includes the routers in the MPLS backbone un-belonging to the user's VPN topology view, from non VPN topology.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)