rfc2896.txt

RFC 的详细文档！

tcp  PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
      hasChildren(0)
    }
    DESCRIPTION
       "Transmission Control Protocol"
    CHILDREN
       "Children of TCP are identified by the 16 bit Source or
       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
       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,
     ipip4 6,
     ipip 6
    }

egp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }



Bierman, et al.              Informational                      [Page 9]

RFC 2896                     RMON PI Macros                  August 2000


    DESCRIPTION
       "Exterior Gateway Protocol (historical)"
    REFERENCE
       "RFC 904 [RFC904] defines the Exterior Gateway Protocol."
    ::= {
     ip  8,
     ipip4  8,
     ipip  8
    }

igp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Any private interior gateway."
    REFERENCE
       "[RFC1700]"
    ::= {
     ip  9,
     ipip4  9,
     ipip  9
    }

nvp2 PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "NVP-II; Network Voice Protocol"
    REFERENCE
       "RFC 741 [RFC741] defines the Network Voice Protocol"
    ::= {
     ip 11,
     ipip4 11,
     ipip 11
    }

pup PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "PUP Protocol"
    REFERENCE
       "Xerox"
    ::= {
     ip 12,
     ipip4 12,
     ipip 12
    }



Bierman, et al.              Informational                     [Page 10]

RFC 2896                     RMON PI Macros                  August 2000


xnet PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Cross Net Debugger (historical)"
    REFERENCE
       "[IEN158]"
    ::= {
     ip  15,
     ipip4  15,
     ipip  15
    }

chaos PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "CHAOS Protocol; historical"
    REFERENCE
       "J. Noel Chiappa  <[e-mail]>"
    ::= {
     ip 16,
     ipip4 16,
     ipip 16
    }

udp  PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES {
      hasChildren(0)
    }
    DESCRIPTION
       "User Datagram Protocol"
    CHILDREN
       "Children of UDP are identified by the 16 bit Source or
       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
       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 authoritative repository for
       reserved and registered UDP port values:




Bierman, et al.              Informational                     [Page 11]

RFC 2896                     RMON PI Macros                  August 2000


         ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers"
   ::= {
     ip 17,
     ipip4 17,
     ipip 17
    }

mux PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Multiplexing Protocol (historical)"
    REFERENCE
       "IEN-90 [IEN-90] defines the Multiplexing Protocol"
    ::= {
     ip 18,
     ipip4 18,
     ipip 18
    }

hmp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Host Monitoring Protocol; historical"
    REFERENCE
       "RFC 869 [RFC869] defines the Host Monitoring Protocol"
    ::= {
     ip  20,
     ipip4  20,
     ipip  20
    }

xns-idp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "XEROX NS IDP"
    REFERENCE
       "Xerox Corporation"
    ::= {
     ip  22,
     ipip4  22,
     ipip  22
    }

rdp PROTOCOL-IDENTIFIER
    PARAMETERS { }



Bierman, et al.              Informational                     [Page 12]

RFC 2896                     RMON PI Macros                  August 2000


    ATTRIBUTES { }
    DESCRIPTION
       "Reliable Data Protocol"
    REFERENCE
       "RFC 908 [RFC908] defines the original protocol; RFC 1151
       [RFC1151] defines version 2 of the Reliable Data Protocol."
    ::= {
     ip 27,
     ipip4 27,
     ipip 27
    }

irtp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Internet Reliable Transaction Protocol"
    REFERENCE
       "RFC 938 [RFC938] defines the Internet Reliable Transaction
       Protocol functional and  interface specification."
    ::= {
     ip 28,
     ipip4 28,
     ipip 28
    }

iso-tp4  PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "ISO Transport Protocol Specification"
    REFERENCE
       "RFC 905 [RFC905] defines the ISO Transport Protocol
       Specification; ISO DP 8073"
    ::= {
     ip  29,
     ipip4  29,
     ipip  29
    }

netblt PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Bulk Data Transfer Protocol; historical"
    REFERENCE
       "RFC 998 [RFC998] defines NETBLT: A Bulk Data Transfer Protocol."
    ::= {



Bierman, et al.              Informational                     [Page 13]

RFC 2896                     RMON PI Macros                  August 2000


     ip 30,
     ipip4 30,
     ipip 30
    }

mfe-nsp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "MFE Network Services Protocol; historical"
    REFERENCE
       "Shuttleworth, B., 'A Documentary of MFENet, a National Computer
       Network', UCRL-52317, Lawrence Livermore Labs, Livermore,
       California, June 1977."
    ::= {
     ip 31,
     ipip4 31,
     ipip 31
    }

idpr PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Inter-Domain Policy Routing Protocol"
    REFERENCE
       "RFC 1479 [RFC1479] defines Version 1 of the Inter-Domain Policy
       Routing Protocol."
    ::= {
     ip 35,
     ipip4 35,
     ipip 35
    }

idpr-cmtp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "IDPR Control Message Transport Protocol"
    REFERENCE
       "RFC 1479 [RFC1479] defines Version 1 of the Inter-Domain Policy
       Routing Protocol."
    ::= {
     ip 38,
     ipip4 38,
     ipip 38
    }




Bierman, et al.              Informational                     [Page 14]

RFC 2896                     RMON PI Macros                  August 2000


sdrp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Source Demand Routing Protocol"
    REFERENCE
       "RFC 1940 [RFC1940] defines version 1 of the Source Demand
       Routing: Packet Format and Forwarding Specification"
    ::= {
     ip 42,
     ipip4 42,
     ipip 42
    }

idrp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Inter-Domain Routing Protocol"
    REFERENCE
       "RFC 1745 [RFC1745] defines BGP4/IDRP for IP."
    ::= {
     ip 45,
     ipip4 45,
     ipip 45
    }

rsvp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Resource Reservation Setup Protocol"
    REFERENCE
       "Resource ReSerVation Protocol (RSVP); Version 1 Functional
        Specification [RFC2205]."
    ::= {
     ip 46,
     ipip4 46,
     ipip 46
    }

gre PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "General Routing Encapsulation"
    REFERENCE
        "RFC 1701 [RFC1701] defines Generic Routing Encapsulation (GRE);



Bierman, et al.              Informational                     [Page 15]

RFC 2896                     RMON PI Macros                  August 2000


       RFC 1702 [RFC1702] defines Generic Routing Encapsulation over
       IPv4 networks"
    ::= {
     ip 47,
     ipip4 47,
     ipip 47
    }

nhrp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "NBMA Next Hop Resolution Protocol (NHRP)"
    REFERENCE
       "RFC 2332 [RFC2332] defines the Next Hop Resolution Protocol."
    ::= {
     ip 54,
     ipip4 54,
     ipip 54
    }

priv-host PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Pseudo-protocol reserved for any internal host protocol."
    REFERENCE
       "[RFC1700]"
    ::= {
     ip 61,
     ipip4 61,
     ipip 61
    }

priv-net PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Pseudo-protocol reserved for any local network protocol."
    REFERENCE
       "[RFC1700]"
    ::= {
     ip 63,
     ipip4 63,
     ipip 63
    }

priv-distfile PROTOCOL-IDENTIFIER



Bierman, et al.              Informational                     [Page 16]

RFC 2896                     RMON PI Macros                  August 2000


    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Pseudo-protocol reserved for any distributed file system."
    REFERENCE
       "[RFC1700]"
    ::= {
     ip 68,
     ipip4 68,
     ipip 68
    }

dgp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "Dissimilar Gateway Protocol"
    REFERENCE
       "M/A-COM Government Systems, 'Dissimilar Gateway Protocol
       Specification, Draft Version', Contract no. CS901145, November
       16, 1987."
    ::= {
     ip 86,
     ipip4 86,
     ipip 86
    }

igrp PROTOCOL-IDENTIFIER
    PARAMETERS { }
    ATTRIBUTES { }
    DESCRIPTION
       "IGRP; Cisco routing protocol"
    REFERENCE
       "Cisco Systems, Inc."