Integrated Services (IntServ) Extension to Allow Signaling of Multiple Traffic Specifications and Multiple Flow Specifications in RSVPv1
draft-ietf-tsvwg-intserv-multiple-tspec-01
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
---|---|---|---|
Authors | James Polk , Subha Dhesikan | ||
Last updated | 2012-09-13 (Latest revision 2012-03-12) | ||
Replaces | draft-polk-tsvwg-intserv-multiple-tspec | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Martin Stiemerling | ||
Send notices to | tsvwg-chairs@tools.ietf.org, draft-ietf-tsvwg-intserv-multiple-tspec@tools.ietf.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines extensions to Integrated Services (IntServ) allowing multiple traffic specifications and multiple flow specifications to be conveyed in the same Resource Reservation Protocol (RSVPv1) reservation message exchange. This ability helps optimize an agreeable bandwidth through a network between endpoints in a single round trip.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)