rfc2074.txt

<VC++网络游戏建摸与实现>源代码

Bierman & Iddon             Standards Track                    [Page 26]

RFC 2074               RMON Protocol Identifiers            January 1997


5.2.5.1.  IANA Assigned Protocol Identifiers

   The following protocol-variant-identifier macro declarations are used
   to identify the RMONMIB IANA assigned protocols in a proprietary way,
   by simple enumeration. Note that an additional four-octet layer
   identifier may be used for some enumerations (as with the 'vsnap'
   base-layer identifier). Refer to the 'CHILDREN' clause in the
   protocol-identifier macro for a particular protocol to determine the
   number of octets in the 'ianaAssigned' layer-identifier.

ipxOverRaw8023 PROTOCOL-IDENTIFIER
    VARIANT-OF  "ipx"
    PARAMETERS  { }
    ATTRIBUTES  { }
    DESCRIPTION
       "This pseudo-protocol describes an encapsulation of IPX over
       802.3, without a type field.

       Refer to the macro for IPX for additional information about this
       protocol."
    DECODING
       "Whenever the 802.3 header indicates LLC a set of protocol
       specific tests needs to be applied to determine whether this is a
       'raw8023' packet or a true 802.2 packet.  The nature of these
       tests depends on the active child protocols for 'raw8023' and is
       beyond the scope of this document."
    ::= { ianaAssigned 1 }

5.3.  L3: Children of Base Protocol Identifiers

   Network layer protocol identifier macros contain additional
   information about the network layer, and is found immediately
   following a base layer-identifier in a protocol identifier.

   The ProtocolDirParameters supported at the network layer are
   'countsFragments(0)', and 'tracksSessions(1). An agent may choose to
   implement a subset of these parameters.

   The protocol-name should be used for the ProtocolDirDescr field.  The
   ProtocolDirType ATTRIBUTES used at the network layer are
   'hasChildren(0)' and 'addressRecognitionCapable(1)'. Agents may
   choose to implement a subset of these attributes for each protocol,
   and therefore limit which tables the indicated protocol can be
   present (e.g.  protocol distribution, host, and matrix tables)..

   The following protocol-identifier macro declarations are given for
   example purposes only. They are not intended to constitute an
   exhaustive list or an authoritative source for any of the protocol



Bierman & Iddon             Standards Track                    [Page 27]

RFC 2074               RMON Protocol Identifiers            January 1997


   information given.  However, any protocol that can encapsulate other
   protocols must be documented here in order to encode the children
   identifiers into protocolDirID strings. Leaf protocols should be
   documented as well, but an implementation can identify a leaf
   protocol even if it isn't listed here (as long as the parent is
   documented).

5.3.1.  IP

ip PROTOCOL-IDENTIFIER
    PARAMETERS {
          countsFragments(0)  -- This parameter applies to all child
                              -- protocols.
    }
    ATTRIBUTES {
        hasChildren(0),
        addressRecognitionCapable(1)
    }
    DESCRIPTION
       "The protocol identifiers for the Internet Protocol (IP). Note
       that IP may be encapsulated within itself, so more than one of
       the following identifiers may be present in a particular
       protocolDirID string."
    CHILDREN
       "Children of 'ip' are selected by the value in the Protocol field
       (one octet), as defined in the PROTOCOL NUMBERS table within the
       Assigned Numbers Document.

       The value of the Protocol field is encoded in an octet string as
       [ 0.0.0.a ], where 'a' is the protocol field .

       Children of 'ip' are encoded as [ 0.0.0.a ], and named as 'ip a'
       where 'a' is the protocol field value. For example, a
       protocolDirID-fragment value of:
          0.0.0.1.0.0.8.0.0.0.0.1

       defines an encapsulation of ICMP (ether2.ip.icmp)"
    ADDRESS-FORMAT
       "4 octets of the IP address, in network byte order.  Each ip
       packet contains two addresses, the source address and the
       destination address."
    DECODING
       "Note: ether2/ip/ipip4/udp is a different protocolDirID than
       ether2/ip/udp, as identified in the protocolDirTable. As such,
       two different local protocol index values will be assigned by the
       agent. E.g. (full INDEX values shown):
        ether2/ip/ipip4/udp 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.4.0.0.0.0
        ether2/ip/udp       12.0.0.0.1.0.0.8.0.0.0.0.17.3.0.0.0 "



Bierman & Iddon             Standards Track                    [Page 28]

RFC 2074               RMON Protocol Identifiers            January 1997


    REFERENCE
       "RFC 791 [RFC791] defines the Internet Protocol; The following
       URL defines the authoritative repository for the PROTOCOL NUMBERS
       Table:

          ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers"
    ::= {
          ether2 0x0800,
          llc 0x06,
          snap 0x0800,
          ip 4,
          ip 94
    }

5.3.2.  IPX

ipx PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
         hasChildren(0),
         addressRecognitionCapable(1)
    }
    DESCRIPTION
       "Novell IPX"
    CHILDREN
       "Children of IPX are defined by the 16 bit value of the
       Destination Socket field.  The value is encoded into an octet
       string as [ 0.0.a.b ], where 'a' and 'b' are the network byte
       order encodings of the MSB and LSB of the destination socket
       field."
    ADDRESS-FORMAT
       "4 bytes of Network number followed by the 6 bytes Host address
       each in network byte order".
    REFERENCE
       "The IPX protocol is defined by the Novell Corporation
















Bierman & Iddon             Standards Track                    [Page 29]

RFC 2074               RMON Protocol Identifiers            January 1997


       A complete description of IPX may be secured at the following
       address:
              Novell, Inc.
              122 East 1700 South
              P. O. Box 5900
              Provo, Utah 84601 USA
              800 526 5463
              Novell Part # 883-000780-001"
    ::= {
        ether2     0x8137,           -- 0.0.129.55
        llc        0xe0e003,         -- 0.224.224.3
        snap       0x8137,           -- 0.0.129.55
        ianaAssigned 0x1               -- 0.0.0.1   (ipxOverRaw8023)
    }

5.3.3.  ARP

arp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "An Address Resolution Protocol message (request or response).
       This protocol does not include Reverse ARP (RARP) packets, which
       are counted separately."
    REFERENCE
       "RFC 826 [RFC826] defines the Address Resolution Protocol."
    ::= {
        ether2 0x806,   -- [ 0.0.8.6 ]
        snap 0x806
    }

5.3.4.  IDP

idp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
         hasChildren(0),
         addressRecognitionCapable(1)
    }
    DESCRIPTION
       "Xerox IDP"
    CHILDREN
       "Children of IDP are defined by the 8 bit value of the Packet
       type field.  The value is encoded into an octet string as [
       0.0.0.a ], where 'a' is the value of the packet type field in
       network byte order."





Bierman & Iddon             Standards Track                    [Page 30]

RFC 2074               RMON Protocol Identifiers            January 1997


    ADDRESS-FORMAT
       "4 bytes of Network number followed by the 6 bytes Host address
       each in network byte order".
    REFERENCE
       "Xerox Corporation, Document XNSS 028112, 1981"
    ::=  {
       ether2  0x600,     -- [ 0.0.6.0 ]
       snap    0x600
    }

5.3.5.  AppleTalk ARP

atalkarp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "AppleTalk Address Resolution Protocol."
    REFERENCE
       "AppleTalk Phase 2 Protocol Specification, document ADPA
       #C0144LL/A."
    ::=   {
      ether2 0x80f3,  --  [ 0.0.128.243 ]
      vsnap(0x080007) 0x80f3
    }

5.3.6.  AppleTalk

atalk PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
        hasChildren(0),
        addressRecognitionCapable(1)
    }
    DESCRIPTION
       "AppleTalk Protocol."
    CHILDREN
       "Children of ATALK are defined by the 8 bit value of the DDP type
       field.  The value is encoded into an octet string as [ 0.0.0.a ],
       where 'a' is the value of the DDP type field in network byte
       order."
    ADDRESS-FORMAT
       "2 bytes of Network number followed by 1 byte of node id each in
       network byte order".








Bierman & Iddon             Standards Track                    [Page 31]

RFC 2074               RMON Protocol Identifiers            January 1997


    REFERENCE
       "AppleTalk Phase 2 Protocol Specification, document ADPA
       #C0144LL/A."
    ::=   {
      ether2  0x809b,   -- [ 0.0.128.155 ]
      vsnap(0x080007) 0x809b
    }

5.4.  L4: Children of L3 Protocols

5.4.1.  ICMP

icmp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Internet Message Control Protocol."
    REFERENCE
       "RFC 792 [RFC792] defines the Internet Control Message Protocol."
    ::= { ip 1 }

5.4.2.  TCP

tcp  PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
         hasChildren(0)
    }
    DESCRIPTION
       "Transmission Control Protocol."
    CHILDREN
       "Children of TCP are identified by the 16 bit Destination Port
       value as specified in RFC 793. They are encoded as [ 0.0.a.b],
       where 'a' is the MSB and 'b' is the LSB of the Destination Port
       value. Both bytes are encoded in network byte order.  For
       example, a protocolDirId-fragment of:
           0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23

       identifies an encapsulation of the telnet protocol
       (ether2.ip.tcp.telnet)"
    REFERENCE
       "RFC 793 [RFC793] defines the Transmission Control Protocol.

       The following URL defines the authoritative repository for
       reserved and registered TCP port values:

         ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers"
    ::=  { ip 6 }



Bierman & Iddon             Standards Track                    [Page 32]

RFC 2074               RMON Protocol Identifiers            January 1997


5.4.3.  UDP

udp  PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
         hasChildren(0)
    }
    DESCRIPTION
       "User Datagram Protocol."
    CHILDREN
       "Children of UDP are identified by the 16 bit Destination Port
       value as specified in RFC 768. They are encoded as [ 0.0.a.b ],
       where 'a' is the MSB and 'b' is the LSB of the Destination Port
       value. Both bytes are encoded in network byte order.  For
       example, a protocolDirId-fragment of:
           0.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161

       identifies an encapsulation of SNMP (ether2.ip.udp.snmp)"
    REFERENCE
       "RFC 768 [RFC768] defines the User Datagram Protocol.

       The following URL defines the au