RSVP Extensions for IPv6 Flow Label Support
draft-schmid-rsvp-fl-01

Document Type Expired Internet-Draft (individual)
Authors Stefan Schmid  , Martin Dunmore  , Nicholas Race 
Last updated 1998-09-01
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-schmid-rsvp-fl-01.txt

Abstract

This document is an addendum to Version 1 of RSVP (Resource ReSerVation Protocol) as defined in the proposed standard [RFC2205]. The flow label, one of the new header fields of the IPv6 protocol, allows improvements to resource reservation protocols on IPv6 capable networks. Utilization of the flow label simplifies packet classification and optimizes packet processing in routers along the transport path. The main objectives of this document are to specify the proper usage of the IPv6 flow label and to promote its support within RSVP. This memo defines extensions required to the Version 1 specification and additional processing rules needed to ensure correct operation. Rather than simply presenting the specification with no justification, we have tried to present the benefits of adopting the flow label within RSVP for IPv6. This addendum does not have any effect on the implementation or usage of RSVP for IPv4.

Authors

Stefan Schmid (sschmid@comp.lancs.ac.uk)
Martin Dunmore (dunmore@comp.lancs.ac.uk)
Nicholas Race (race@comp.lancs.ac.uk)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)