Resource Reservation Setup Protocol (rsvp) Charter
NOTE: This charter is accurate as of the 32nd IETF Meeting in Danvers. It
may now be out-of-date. (Consider this a "snapshot" of the working
group from that meeting.) Up-to-date charters for all active working
groups can be found elsewhere in this Web server.
- Robert Braden <email@example.com>
- Lixia Zhang <firstname.lastname@example.org>
Transport Area Director(s):
- Allison Mankin <email@example.com>
Mailing List Information
- General Discussion:firstname.lastname@example.org
- To Subscribe: email@example.com
- 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
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
- Hold BOF on RSVP at Houston IETF meeting.
- 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.
No Request for Comments