RSVP and Integrated Services with IPv6 Flow Labels
draft-berson-rsvp-ipv6-fl-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Steven Berson | ||
| Last updated | 1999-06-25 | ||
| 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, there is a brief definition about how RSVP works with IPv6[2]. However, there are a number of recent issues that need to be elaborated. These include issues with changes in the IPv6 Flow Label definition, routing RSVP messages, and security.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)