Browse Prior Art Database

Procedures for Modifying the Resource reSerVation Protocol (RSVP) (RFC3936)

IP.com Disclosure Number: IPCOM000032066D
Original Publication Date: 2004-Oct-01
Included in the Prior Art Database: 2004-Oct-22
Document File: 8 page(s) / 15K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Kompella: AUTHOR [+2]

Abstract

This memo specifies procedures for modifying the Resource reSerVation Protocol (RSVP). This memo also lays out new assignment guidelines for number spaces for RSVP messages, object classes, class-types, and sub-objects.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 18% of the total text.

Network Working Group                                        K. Kompella

Request for Comments: 3936                              Juniper Networks

Updates: 3209, 2205                                              J. Lang

BCP: 96                                                  Rincon Networks

Category: Best Current Practice                             October 2004

   Procedures for Modifying the Resource reSerVation Protocol (RSVP)

Status of this Memo

   This document specifies an Internet Best Current Practices for the

   Internet Community, and requests discussion and suggestions for

   improvements.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   This memo specifies procedures for modifying the Resource reSerVation

   Protocol (RSVP).  This memo also lays out new assignment guidelines

   for number spaces for RSVP messages, object classes, class-types, and

   sub-objects.

1.  Introduction

   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, object classes and class types, object formats and

   procedures; header formats, error codes and subcodes and semantics,

   and procedures for sending, receiving, and addressing RSVP messages.

   IANA recognizes the following RSVP name spaces: Message Types, Class

   Names, Class Numbers, Class Types and Sub-objects, 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 and assignment

   policies for each range.  New RSVP name spaces must be defined in a

   Standards Track RFC which include guidelines for IANA assignments

   within the new name spaces.

   The assignment policies used in this document are: Standards Action

   (as defined in [IANA]), Expert Review, and Organization/Vendor

   Private (more simply, "Vendor Private"); the last two are defined in

   this document.  The intent of these assignment policies is to ensure

Kompella & Lang          Best Current Practice                  [Page 1]

RFC 3936             Procedures for Modifying RSVP          October 2004

   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

   receive an assignment from the Standards Action space; however, if an

   extension is experimental in nature, it receives an assignment from

   t...