RSVP-TE IPv6
draft-manral-mpls-rsvpte-ipv6-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Vishwas Manral | ||
| Last updated | 2012-10-01 (Latest revision 2012-03-30) | ||
| 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
RSVP defined in [RFC2205] defines a resource reservation setup protocol, designed for an integrated service internet. RSVP-TE defined in [RFC2205] extends RSVP to establish LSP's in MPLS. For RSVP-TE hops that cannot allocate Labels cannot exist in the PATH of the LSP's. It is therefore specified that for IPv6 RSVP-TE LSP's Path, PathTear and ResvConf Messages should address the messages directly to an adjacent node control plane IPv6 address. This document also specfies some other changes required for RSVP-TE to work over IPv6 transport.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)