RFC 3936:Procedures for Modifying the Resource reS...
RFC-Ref

RSVP


Click on the red underlined text to get to the source

... This memo specifies procedures for modifying the Resource reSerVation Protocol (RSVP) [RSVP], including (but not limited to) adding, updating, extending or obsoleting: messages, message formats ...
... and procedures for sending, receiving, and addressing RSVP messages. IANA ...
... IANA recognizes the following RSVP name spaces: Message Types, Class Names, Class Numbers ...
... Virtual Destination Ports, and Error Codes and (Subcode) Values (all of these will collectively be referred to as RSVP entities in this document). This memo specifies ranges for each name space ...
... name space and assignment policies for each range. New RSVP name spaces must be defined in a Standards Track RFC which include guidelines for IANA assignments ...
... this document. The intent of these assignment policies is to ensure that extensions to RSVP receive adequate review before code-points are assigned, without being overly rigid. Thus, if an extension is widely accepted and its ramifications are well understood, it may ...
... A standards body other than the IETF that wishes to obtain an assignment for an RSVP entity must decide from which type of name/number space ...


... Assignment Policies for RSVP Entities ...
... For each of the RSVP name spaces identified by IANA, the space is divided into assignment ranges ...
... thereafter is for the private use of the registered enterprise. (For each RSVP entity that has a Vendor Private range ...
... Message Type is an 8-bit number that identifies the function of the RSVP message. Values from 0 through 239 are to be assigned by Standards Action. Values from 240 through 255 are to be assigned by Expert Review. ...
... Each class of data objects in an RSVP message is identified by an all upper-case Class Name and an 8-bit ...


... Modifying RSVP Procedures ...
... RSVP entities have associated procedures describing when and how they are to be sent, received, processed, and responded to. A change to a procedure that affects the processing of an RSVP ...
... RSVP entities have associated procedures describing when and how they are to be sent, received, processed, and responded to. A change to a procedure that affects the processing of an RSVP entity that belongs to a range ...
... range designated "Standards Action" MUST be documented in a Standards Track RFC. A change to a procedure that affects the processing of an RSVP entity that belongs to a range designated ...


... It is hoped that the procedures outlined in this memo will ensure that changes made to RSVP will be better reviewed and thus more architecturally sound, thereby enhancing the security ...


... Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification", RFC 2205prop ...
... Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209prop ...
... Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209prop, December 2001. ...
... Berger, L. and T. O'Malley, "RSVP Extensions for IPSEC Data Flows", RFC 2207prop ...



Google
Web
RFC-Ref