rfc2206.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

Network Working Group                                       F. Baker
Request for Comments: 2206                             Cisco Systems
Category: Standards Track                                J. Krawczyk
                                           ArrowPoint Communications
                                                           A. Sastry
                                                       Cisco Systems
                                                      September 1997


              RSVP Management Information Base using SMIv2


Status of this Memo

   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.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing the Resource
   Reservation Protocol (RSVP) within the interface attributes defined
   in the Integrated Services Model.  Thus, the Integrated Services MIB
   is directly relevant to and cross-referenced by this MIB.  Comments
   should be made to the RSVP Working Group, [e-mail].

Table of Contents

   1 The SNMPv2 Network Management Framework ...............    2
   1.1 Object Definitions ..................................    2
   2 Overview ..............................................    3
   2.1 Textual Conventions .................................    3
   2.2 Structure of MIB ....................................    3
   2.3 Semantics of  Writing  the  Path  and  Reservation
        State Databases ....................................    3
   2.4 Intended use of Flow Notifications ..................    4
   2.4.1 The lostFlow Notification .........................    4
   2.4.2 The newFlow Notification ..........................    4
   3 Definitions ...........................................    4
   3.1 RSVP Session Statistics Database ....................    6
   3.2 RSVP Session Sender Database ........................    9
   3.3 RSVP Reservations Requested Database ................   25
   3.4 RSVP Reservation Requests Database ..................   35
   3.5 RSVP Interface Attributes Database ..................   44



Baker, et. al.              Standards Track                     [Page 1]

RFC 2206                  RSVP MIB using SMIv2            September 1997


   3.6 RSVP Neighbor Database ..............................   48
   3.7 Notifications .......................................   49
   4 Security Considerations................................   63
   5 Authors' Addresses ....................................   63
   6 Acknowledgements ......................................   63
   7 References ............................................   64

1.  The SNMPv2 Network Management Framework


   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

   o    RFC 1441 which defines the SMI, the mechanisms used for
        describing and naming objects for the purpose of
        management.

   o    STD 17, RFC 1213 defines MIB-II, the core set of managed
        objects for the Internet suite of protocols.

   o    RFC 1445 which defines the administrative and other
        architectural aspects of the framework.

   o    RFC 1448 which defines the protocol used for network
        access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

1.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
   specific instantiation of the object.  For human convenience, we
   often use a textual string, termed the descriptor, to refer to the
   object type.











Baker, et. al.              Standards Track                     [Page 2]

RFC 2206                  RSVP MIB using SMIv2            September 1997


2.  Overview

2.1.  Textual Conventions

   Several new data types are introduced as a textual convention in this
   MIB document.  These textual conventions enhance the readability of
   the specification and can ease comparison with other specifications
   if appropriate.  It should be noted that the introduction of the
   these textual conventions has no effect on either the syntax nor the
   semantics of any managed objects.  The use of these is merely an
   artifact of the explanatory method used.  Objects defined in terms of
   one of these methods are always encoded by means of the rules that
   define the primitive type.  Hence, no changes to the SMI or the SNMP
   are necessary to accommodate these textual conventions which are
   adopted merely for the convenience of readers and writers in pursuit
   of the elusive goal of clear, concise, and unambiguous MIB documents.

2.2.  Structure of MIB

   The MIB is composed of the following sections:

        General Objects
        Session Statistics Table
        Session Sender Table
        Reservation Requests Received Table
        Reservation Requests Forwarded Table
        RSVP Interface Attributes Table
        RSVP Neighbor Table

   As a general rule, it is difficult in SNMP to describe arbitrarily
   long of complex messages; this MIB therefore seeks to describe the
   Path State Database and the Reservation State Database as though each
   flow and filter description received in an aggregate message had been
   received in a separate reservation message.

   Thus, if a RESV message is received for session 224.1.2.3+UDP+4455
   with two filter/flow spec groups describing a sender 1.2.3.4 and
   another sender 1.2.7.8, these two will show in the MIB as two
   separate rows: one for 224.1.2.3+UDP+4455 from 1.2.3.4 and the other
   for 224.1.2.3+UDP+4455 from 1.2.7.8.

2.3.  Semantics of Writing the Path and Reservation State Databases

   The path and reservation state tables are writeable. Writing into the
   Path and Reservation State databases allows one to perform RSVP
   reservations without authenticating through RSVP mechanisms, but





Baker, et. al.              Standards Track                     [Page 3]

RFC 2206                  RSVP MIB using SMIv2            September 1997


   rather through SNMP mechanisms. State created in this way by SNMP
   does not time out and cannot be deleted by receiving an RSVP teardown
   message; it can only be deleted by SNMP.  Deletion is accomplished by
   writing 'destroy' to the associated Row Status object, and this will
   initiate a teardown message as if the state had timed out.

2.4.  Intended use of Flow Notifications

2.4.1.  The lostFlow Notification

   The Lost Flow notification is an asychronous event that signifies
   that a flow is no longer being observed.

2.4.2.  The newFlow Notification

   The newFlow Notification defined in this MIB can be used to advise a
   network management system of the state of a flow.

3.  Definitions

RSVP-MIB DEFINITIONS ::= BEGIN

        IMPORTS
                MODULE-IDENTITY, OBJECT-TYPE, Gauge32,
                NOTIFICATION-TYPE, Integer32, mib-2
                                                    FROM SNMPv2-SMI
                TEXTUAL-CONVENTION, TruthValue, RowStatus,
                TimeStamp, TestAndIncr, TimeInterval
                                                    FROM SNMPv2-TC
                MODULE-COMPLIANCE, OBJECT-GROUP,
                NOTIFICATION-GROUP                  FROM SNMPv2-CONF
                Port, SessionNumber, SessionType,
                Protocol, QosService, intSrvFlowStatus,
                MessageSize, BitRate, BurstSize
                                            FROM INTEGRATED-SERVICES-MIB
                ifIndex, InterfaceIndex             FROM IF-MIB;


    rsvp MODULE-IDENTITY
            LAST-UPDATED "9511030500Z" -- Thu Aug 28 09:03:53 PDT 1997
            ORGANIZATION "IETF RSVP Working Group"
            CONTACT-INFO
           "       Fred Baker
           Postal: Cisco Systems
                   519 Lado Drive
                   Santa Barbara, California 93111
           Tel:    [phone]
           E-Mail: [e-mail]



Baker, et. al.              Standards Track                     [Page 4]

RFC 2206                  RSVP MIB using SMIv2            September 1997


                   John Krawczyk
           Postal: ArrowPoint Communications
                   235 Littleton Road
                   Westford, Massachusetts 01886
           Tel:    [phone]
           E-Mail: [e-mail]

                   Arun Sastry
           Postal: Cisco Systems
                   210 W. Tasman Drive
                   San Jose, California 95134
           Tel:    [phone]
           E-Mail: [e-mail]"
       DESCRIPTION
          "The MIB module to describe the RSVP Protocol"
      ::= { mib-2 51 }

  rsvpObjects               OBJECT IDENTIFIER
                            ::= { rsvp 1 } -- tables
  rsvpGenObjects            OBJECT IDENTIFIER
                            ::= { rsvp 2 } -- global objects
  rsvpNotificationsPrefix   OBJECT IDENTIFIER
                            ::= { rsvp 3 } -- traps
  rsvpConformance           OBJECT IDENTIFIER
                            ::= { rsvp 4 } -- conformance


    RsvpEncapsulation ::= TEXTUAL-CONVENTION
         STATUS   current
         DESCRIPTION
           "This indicates the encapsulation that an  RSVP
           Neighbor is perceived to be using."
        SYNTAX   INTEGER {
                   ip (1),   -- IP Protocol 46
                   udp (2),  -- UDP Encapsulation
                   both (3)  -- neighbor is using both encapsulations
                 }


    RefreshInterval ::= TEXTUAL-CONVENTION
         DISPLAY-HINT "d"
         STATUS   current
         DESCRIPTION
           "The number of milliseconds that  are  expected
           to elapse between refreshes of path or reserva-
           tion state.  Unrefreshed  Path  or  reservation
           state is removed after a small multiple of this
           period."



Baker, et. al.              Standards Track                     [Page 5]

RFC 2206                  RSVP MIB using SMIv2            September 1997


        SYNTAX   INTEGER (0..'7FFFFFFF'h)


--      The RSVP Session Statistics Database displays statistics
--      relating to the number of senders and receivers in each
--      session.


    rsvpSessionTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF RsvpSessionEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
           "A table of all sessions seen by a  given  sys-
           tem."
       ::= { rsvpObjects 1 }


    rsvpSessionEntry OBJECT-TYPE
        SYNTAX      RsvpSessionEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
           "A single session seen by a given system."
       INDEX { rsvpSessionNumber }
       ::= { rsvpSessionTable 1 }


    RsvpSessionEntry ::=
        SEQUENCE {
        rsvpSessionNumber           SessionNumber,
        rsvpSessionType             SessionType,
        rsvpSessionDestAddr         OCTET STRING,
        rsvpSessionDestAddrLength   INTEGER,
        rsvpSessionProtocol         Protocol,
        rsvpSessionPort             Port,
        rsvpSessionSenders          Gauge32,
        rsvpSessionReceivers        Gauge32,
        rsvpSessionRequests         Gauge32
        }


    rsvpSessionNumber OBJECT-TYPE
        SYNTAX      SessionNumber
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
           "The number of this session.  This is for  SNMP



Baker, et. al.              Standards Track                     [Page 6]

RFC 2206                  RSVP MIB using SMIv2            September 1997


           Indexing  purposes  only and has no relation to
           any protocol value."
       ::= { rsvpSessionEntry 1 }


    rsvpSessionType OBJECT-TYPE
        SYNTAX      SessionType
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
           "The type of session (IP4, IP6, IP6  with  flow
           information, etc)."
       ::= { rsvpSessionEntry 2 }


    rsvpSessionDestAddr OBJECT-TYPE
        SYNTAX      OCTET STRING (SIZE(4..16))
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
           "The destination address used by all senders in
           this  session.   This object may not be changed
           when the value of the RowStatus object is  'ac-
           tive'."
       ::= { rsvpSessionEntry 3 }


    rsvpSessionDestAddrLength OBJECT-TYPE
        SYNTAX      INTEGER(0..128)
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
           "The CIDR prefix length of the session address,
           which  is  32  for  IP4  host and multicast ad-
           dresses, and 128 for IP6 addresses.   This  ob-
           ject  may  not be changed when the value of the
           RowStatus object is 'active'."
       ::= { rsvpSessionEntry 4 }


    rsvpSessionProtocol OBJECT-TYPE
        SYNTAX      Protocol
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
           "The IP Protocol used by  this  session.   This
           object may not be changed when the value of the
           RowStatus object is 'active'."



Baker, et. al.              Standards Track                     [Page 7]