One document matched: draft-ietf-rsvp-procrules-00.txt

A new Request for Comments is now available in online RFC libraries.


        RFC 2209

        Title:      Resource ReSerVation Protocol (RSVP) --
                    Version 1 Message Processing Rules
	Author:     R. Braden, L. Zhang
        Status:     Proposed Standard
	Date:       September 1997
        Mailbox:    braden@isi.edu, lixia@cs.ucla.edu
        Pages:      25
        Characters: 51873
        Updates/Obsoletes:  None

        URL:        ftp://ds.internic.net/rfc/rfc2209.txt


This memo contains an algorithmic description of the rules used by an
RSVP implementation for processing messages.  It is intended to
clarify the version 1 RSVP protocol specification.
 
This memo provides a generic description of the rules for the
operation of Version 1 of RSVP [RFC 2205].  It is intended to outline
a set of algorithms that will accomplish the needed function, omitting
many details.

This document is a product of the Resource Reservation Setup Protocol
Working Group of the IETF.
 
This is now a Proposed Standard Protocol.
 
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute