[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00

Internet Draft                                                 R. Braden
Expiration: October 1999                                             ISI
File: draft-ietf-rsvp-iana-00.txt                               L. Zhang
                                                                    UCLA

                 IANA Considerations for RSVP Version 1

                             April 20, 1999

Status of Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026. Internet-Drafts are Working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   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."

      The list of current Internet-Drafts can be accessed at
      http://www.ietf.org/ietf/1id-abstracts.txt

      The list of Internet-Draft Shadow Directories can be accessed at
      linebreak http://www.ietf.org/shadow.html.

Abstract

   This document provides an IANA Considerations section that will be
   included in a future revision of the RSVP (Resource Reservation
   Protocol) specification, RFC 2205 [RSVP97].  Meanwhile, this document
   should be used to perform protocol parameter assignment for the RSVP
   protocol.

Braden & Zhang          Expiration: October 1999                [Page 1]


Internet Draft          RSVP IANA Considerations              April 1999

1. Introduction

   The responsible Internet authority (presently called the IANA) should
   assign values to RSVP protocol parameters using rules presented in
   this document, which uses the terminology of BCP 26 [Guide98].

   The contents of this document will become the IANA Considerations
   section in a future revision of the RSVP (Resource Reservation
   Protocol) specification, RFC 2205 [RSVP97].

2. IANA Considerations

   2.1 Message Type (or Msg Type)

      Message Type is an 8-bit number that identifies the function of
      the RSVP message.  Its values fall into the following ranges:

         0          Illegal value
         1-127      Assigned by IANA with IETF Consensus.
         128-191    Assigned by IANA using First-Come-First-Served
         192-255    Private usage.

   2.2 Class Number (or Class Num)

      Class Number is an 8-bit number that identifies a class of data
      objects to be carried in an RSVP message.  Within each such class,
      an 8-bit Class Type number (below) further specifies the
      particular object type.

      The two high-order bits of the Class Number are used to encode the
      desired behavior when an RSVP implementation receives a message
      containing an object whose Class Number it does not understand
      [RFC2205].  In the following table: bits "x" are to be assigned by
      the IANA.  The bit "r" is currently required to have the value 1.

         Class
         Number      Behavior     Meaning
         Range
         ________    ________     _____________________________________
         0xxxxxxx    REJECT       RSVP rejects the RSVP message and
                                      sends an RSVP error message.

         10rxxxxx    IGNORE       RSVP silently ignores the object and
                                      does not forward it.

         11xxxxxx    FORWARD      RSVP silently ignores the object but
                                      forwards it.

Braden & Zhang          Expiration: October 1999                [Page 2]


Internet Draft          RSVP IANA Considerations              April 1999

      The following table shows the behavior and IANA assignment rule
      for each sub-range of the Class Number value:

         0-80        REJECT; assigned by IANA with IETF Consensus.
         81-127      REJECT; assigned by IANA using First-Come-First-Served
         128-159     (Reserved)
         160-191     IGNORE; assigned by IANA with IETF Consensus.
         192-223     FORWARD; assigned by IANA with IETF Consensus.
         224-255     FORWARD; assigned by IANA using First-Come-First-Served

   2.3 Class Type

      Class Type is an 8-bit number that is assigned distinctly for each
      Class Number.

         0           Illegal value
         1-127       Assigned by IANA with IETF Consensus.
         128-191     Assigned by IANA using First-Come-First-Served
         192-255     Private usage.

   2.4 Virtual Destination Port (vDstPort)

      Virtual Destination Port is a 16-bit value number is used in
      objects with the SESSION Class Number and the IPv4/GPI or IPv6/GPI
      Class Type.  Values of this quantity are assigned using the
      following rules:

         0            Illegal Value
         1-10         Reserved.  Contact authors of RFC 2207.
         11-8191      Assigned by IANA using First-Come-First-Served.
         8192-65535   Reserved for dynamic allocation.

      For values assigned by IANA, the rules are those for UDP port
      assignment: the requestor must provide (a) a Point of Contact, (b)
      a brief description of the intended use, and (c) a short name to
      be associated with the assignment.

   2.5 Error Code

      This 8-bit number indicates the basic type of error.  New values
      should be assigned using Expert Review.  A document must be
      submitted that defines the precise meaning of the error code and
      the accompanying Error Value field.

   2.6 Globally-Defined Error Value Sub-Code

      These sub-codes form the low-order 12 bits of a 16-bit Error Value
      of the form:

Braden & Zhang          Expiration: October 1999                [Page 3]


Internet Draft          RSVP IANA Considerations              April 1999

         0000xxxxxxxxxxxx

      New sub-code values of this form should be assigned using Expert
      Review [Guide98], and a document must be submitted that defines
      their precise meaning.  Currently assigned Error Code values
      include the following for which additional globally defined error
      value sub-codes may be defined:

      o    Error Code = 01: Admission control failure.

      o    Error Code = 12: Service preemption.

      o    Error Code = 21: Traffic control error.

      In addition, new error codes may be defined in the future that
      expand this list; they must be fully and explicitly documented.

   3. References

[Guide98]  Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
    Considerations Section in an RFC", October 1998.

[RSVP97] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
    Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional
    Specification", RFC 2205, September 1997.

Security Considerations

   The security considerations for RSVP are specified in [RSVP97].

Authors' Addresses

   Bob Braden
   USC Information Sciences Institute
   4676 Admiralty Way
   Marina del Rey, CA 90292

   Phone: (310) 822-1511
   EMail: Braden@ISI.EDU

Braden & Zhang          Expiration: October 1999                [Page 4]


Internet Draft          RSVP IANA Considerations              April 1999

   Lixia Zhang
   Xerox Palo Alto Research Center
   3333 Coyote Hill Road
   Palo Alto, CA 94304

   Phone: (415) 812-4415
   EMail: Lixia@PARC.XEROX.COM

Braden & Zhang          Expiration: October 1999                [Page 5]


Html markup produced by rfcmarkup 1.129b, available from https://tools.ietf.org/tools/rfcmarkup/