Removing a Restriction on the use of MPLS Explicit NULL
draft-rosen-mpls-explicit-null-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Eric C. Rosen | ||
| Last updated | 2003-12-19 | ||
| 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
RFC 3032 defines a reserved label value known as 'IPv4 Explicit NULL' and a reserved label value known as 'IPv6 Explicit NULL'. It states that these label values are only legal at the bottom of the MPLS label stack. This restriction is now removed, so that those label values are legal anywhere in the stack.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)