Signalling Unnumbered Links in Resource ReSerVation Protocol - Traffic Engineering (RSVP-TE) in an IPv6 Network
draft-davey-mpls-rsvp-ipv6-unnum-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Alan Davey , Nic Neate | ||
| Last updated | 2005-02-10 | ||
| 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
Currently, RSVP-TE signalling over unnumbered links identifies routers using 32-bit Router IDs [RFC3477]. Traffic engineering extensions to IGP protocols for use in IPv6 networks use 128-bit IPv6 addresses to identify routers [OSPFv3-TE], [ISIS-TE]. This document specifies extensions for RSVP-TE signalling over unnumbered links to use 128-bit Router IDs in an IPv6 network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)