<?xml version='1.0'?>

<reference anchor='RFC2210'>

<front>
<title abbrev='RSVP with INTSERV'>The Use of RSVP with IETF Integrated Services</title>
<author initials='J.' surname='Wroclawski' fullname='John Wroclawski'>
<organization>MIT Laboratory for Computer Science</organization>
<address>
<postal>
<street>545 Technology Sq.</street>
<street>Cambridge</street>
<street>MA  02139</street></postal>
<phone>617-253-7885</phone>
<facsimile>617-253-2673 (FAX)</facsimile>
<email>jtw@lcs.mit.edu</email></address></author>
<date month='September' year='1997' />
<area>Transport</area>
<keyword>Internet Engineering Task Force</keyword>
<keyword>integrated services</keyword>
<keyword>resource reservation protocol</keyword>
<abstract>
<t>
   This note describes the use of the RSVP resource reservation protocol
   with the Controlled-Load and Guaranteed QoS control services.  The
   RSVP protocol defines several data objects which carry resource
   reservation information but are opaque to RSVP itself.  The usage and
   data format of those objects is given here.
</t></abstract></front>

<seriesInfo name='RFC' value='2210' />
<format type='HTML' octets='92807' target='http://xml.resource.org/public/rfc/html/rfc2210.html' />
<format type='XML' octets='78400' target='http://xml.resource.org/public/rfc/xml/rfc2210.xml' />
</reference>
