2.7.10 Resource Reservation Setup Protocol (rsvp) *

This Working Group Did Not Meet

NOTE: This charter is a snapshot of the 40th IETF Meeting in Washington, DC. It may now be out-of-date. Last Modified: 13-May-97

Chair(s):

Lixia Zhang <lixia@cs.ucla.edu>
Bob Braden <braden@isi.edu>

Transport Area Director(s):

Scott Bradner <sob@harvard.edu>
Allyn Romanow <allyn.romanow@eng.sun.com>

Transport Area Advisor:

Scott Bradner <sob@harvard.edu>

Mailing Lists:

General Discussion:rsvp@isi.edu
To Subscribe: rsvp-request@isi.edu
Archive: ftp://ftp.isi.edu/rsvp/rsvp.mail

Description of Working Group:

RSVP is a resource reservation setup protocol for the Internet. Its major features include: (1) the use of ``soft state'' in the routers, (2) receiver-controlled reservation requests, (3) flexible control over sharing of reservations and forwarding of subflows, and (4) the use of IP multicast for data distribution.

The primary purpose of this working group is to evolve the RSVP specification and to introduce it into the Internet standards track. The working group will also serve as a meeting place and forum for those developing and experimenting with RSVP implementations.

The task of the RSVP Working Group, creating a robust specification for real-world implementations of RSVP, will require liaison with two other efforts: (1) continuing research and development work on RSVP in the DARTnet research community, and (2) the parallel IETF working group that is considering the service model for integrated service. Although RSVP is largely independent of the service model, its design does depend upon the overall integrated service architecture and the requirements of real-time applications. As an additional task, RSVP will maintain coordination with the IPng-related working groups.

Goals and Milestones:

Done

  

Hold BOF on RSVP at Houston IETF meeting.

Done

  

Prepare new draft of RSVP Protocol in time for Seattle IETF meeting, following e-mail review and possible MBONE meetings.

Nov 94

  

Submit the RSVP specification to the IESG for consideration as a Prototype RFC. Begin revision based on experience.

Mar 95

  

Release revised specification.

Jul 95

  

Submit RSVP specification to IESG for Proposed Standard status.

Internet-Drafts:

Request For Comments:

RFC

Status

Title

 

RFC2205

PS

Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification

RFC2206

PS

RSVP Management Information Base using SMIv2

RFC2207

PS

RSVP Extensions for IPSEC Data Flows

RFC2208

 

Resource ReSerVation Protocol (RSVP) Version 1 Applicability Statement Some Guidelines on Deployment

RFC2209

PS

Resource ReSerVation Protocol (RSVP) -- Version 1 Message Processing Rules

Previous PageNext Page