Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). Abstract This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet. RSVP provides receiver-initiated setup of resource reservations for multicast or unicast data flows, with good scaling and robustness properties. What's Changed Since Seattle IETF o Redesign generic RSVP API (section 3.6.2) o Change encoding of style in RESV messages (section 3.1.2) o Clarify filterspec functions (section 2.1) o Simplify definition of DF style (sections 2.2, 2.4). o Revise discussion of flowspec merging (section 2.3.3). o Change format of variable-length filterspecs and flowspecs (section 3.1 and 3.6.1). o Add a user authentication field in all RSVP messages (Section 3). o Add short discussion of local repair (Section 3.3.3). o Editorial nits.
[1]
Scott Shenker,et al.
Supporting real-time applications in an Integrated Services Packet Network: architecture and mechanism
,
1992,
SIGCOMM '92.
[2]
Craig Partridge,et al.
A Proposed Flow Specification
,
1992,
RFC.
[3]
Scott Shenker,et al.
A Service Model for an Integrated Services Internet Status of Memo
,
1993
.
[4]
D. Estrin,et al.
RSVP: a new resource reservation protocol
,
1993,
IEEE Communications Magazine.
[5]
Scott Shenker,et al.
Integrated Services in the Internet Architecture : an Overview Status of this Memo
,
1994
.