RFC relevance of reference

As per Relevance of the word reference, we have this rfc below:

Network Working Group A.
Requests for Comment: 2896 C.
Category: Informational Cisco Systems, Inc
R.
3Com, Inc
August 2000

Remote Network Monitoring MIB Protocol Identifier

Status of this

This memo provides information for the Internet community. It
not specify an Internet standard of any kind. Distribution of
memo is unlimited

Copyright

Copyright (C) The Internet Society (2000). All Rights Reserved

This memo contains various protocol identifier examples, which can
used to produce valid protocolDirTable INDEX encodings, as defined
the Remote Network Monitoring MIB (Management Information Base
Version 2 [RFC2021] and the RMON Protocol Identifier
[RFC2895].

This document contains protocol identifier macros for well-
protocols. A conformant implementation of the RMON-2 MIB [RFC2021]
can be accomplished without the use of these protocol identifiers
and accordingly, this document does not specify any IETF standard
It is published to encourage better interoperability between RMON-2
agent implementations, by providing a great deal of RMON
protocol information in one document

The first version of the RMON Protocol Identifiers Document [RFC2074]
has been split into a standards-track Reference portion [RFC2895],
and an "RMON Protocol Identifier Macros", document (this document
which contains the non-normative portion of that specification

Table of

1 The SNMP Network Management Framework ......................... 2
2 Overview ...................................................... 3
2.1 Terms ....................................................... 3
2.2 Relationship to the Remote Network Monitoring MIB ........... 4
2.3 Relationship to the RMON Protocol Identifier Reference ...... 4

Bierman, et al. Informational [Page 1]

RFC 2896 RMON PI Macros August 2000

2.4 Relationship to Other MIBs .................................. 4
3 Protocol Identifier Macros .................................... 4
3.1 Protocol Stacks And Single-Vendor Applications .............. 5
3.1.1 The TCP/IP protocol stack ................................. 5
3.1.2 Novell IPX Stack .......................................... 44
3.1.3 The XEROX Protocol Stack .................................. 49
3.1.4 AppleTalk Protocol Stack .................................. 51
3.1.5 Banyon Vines Protocol Stack ............................... 56
3.1.6 The DECNet Protocol Stack ................................. 61
3.1.7 The IBM SNA Protocol Stack. .............................. 65
3.1.8 The NetBEUI/NetBIOS Family ................................ 66
3.2 Multi-stack protocols ....................................... 70
4 Intellectual Property ......................................... 72
5 Acknowledgements .............................................. 72
6 References .................................................... 73
7 Security Considerations ....................................... 82
8 Authors' Addresses ............................................ 83
9 Full Copyright Statement ...................................... 84

1. The SNMP Network Management

The SNMP Management Framework presently consists of five
components

o An overall architecture, described in RFC 2571 [RFC2571].

o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and
1215 [RFC1215]. The second version, called SMIv2, is
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579]
STD 58, RFC 2580 [RFC2580].

o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [RFC1157]. A second version of
SNMP message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
and RFC 1906 [RFC1906]. The third version of the
protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
RFC 2572 [RFC2572] and RFC 2574 [RFC2574].

o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [RFC1157]. A second set
protocol operations and associated PDU formats is described
RFC 1905 [RFC1905].

Bierman, et al. Informational [Page 2]

RFC 2896 RMON PI Macros August 2000

o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism
in RFC 2575 [RFC2575].

A more detailed introduction to the current SNMP Management
can be found in RFC 2570 [RFC2570].

Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI

This memo does not specify a MIB module

2.

The RMON-2 MIB [RFC2021] uses hierarchically formatted OCTET
to globally identify individual protocol encapsulations in
protocolDirTable

This guide contains examples of protocol identifier encapsulations
which can be used to describe valid protocolDirTable entries.
syntax of the protocol identifier descriptor is defined in the
Protocol Identifier Reference [RFC2895].

This document is not intended to be an authoritative reference on
protocols described herein. Refer to the Official Internet
document [RFC2600], the Assigned Numbers document [RFC1700], or
appropriate RFCs, IEEE documents, etc. for complete and
protocol information

This is the the second revision of this document, and is intended
replace Section 5 of the first RMON-2 Protocol Identifiers
[RFC2074].

The RMONMIB working group has decided to discontinue maintenance
this Protocol Identifier Macro repository document, due to a lack
contributions from the RMON vendor community. This document
published as an aid in implementation of the protocolDirTable

2.1.

Refer to the RMON Protocol Identifier Reference [RFC2895]
definitions of terms used to describe the Protocol Identifier
and aspects of protocolDirTable INDEX encoding

Bierman, et al. Informational [Page 3]

RFC 2896 RMON PI Macros August 2000

2.2. Relationship to the Remote Network Monitoring

This document is intended to describe some protocol
macros, which can be converted to valid protocolDirTable
values, using the mapping rules defined in the RMON
Identifier Reference [RFC2895].

This document is not intended to limit the protocols that may
identified for counting in the RMON-2 MIB. Many
encapsulations, not explicitly identified in this document, may
present in an actual implementation of the protocolDirTable. Also
implementations of the protocolDirTable may not include all
protocols identified in the example section below

2.3. Relationship to the RMON Protocol Identifier

This document is intentionally separated from the normative
document defining protocolDirTable INDEX encoding rules and
protocol identifier macro syntax [RFC2895]. This allows
updates to this document without any republication of MIB objects
protocolDirTable INDEX encoding rules. Note that the base layer
IANA assigned protocol identifier macros are located in
document, since these encoding values are defined by the RMONMIB WG

Protocol Identifier macros submitted from the RMON working group
community at large (to the RMONMIB WG mailing list at '
rmonmib@cisco.com') will be collected and added to this document

Macros submissions will be collected in the IANA's MIB files
the directory "ftp://ftp.isi.edu/mib/rmonmib/rmon2_pi_macros/" and
the RMONMIB working group mailing list message archive
"ftp://ftpeng.cisco.com/ftp/rmonmib/rmonmib".

2.4. Relationship to Other

The RMON Protocol Identifier Macros document is intended for use
the RMON Protocol Identifier Reference [RFC2895] and the RMON-2
protocolDirTable [RFC2021]. It is not relevant to any other MIB,
intended for use with any other MIB

3. Protocol Identifier

This section contains protocol identifier macros for some well-
protocols, although some of them may no longer be in use.
macros reference the base layer identifiers found in section 4 of
RMON Protocol Identifier Reference [RFC2895]. These identifiers
listed below

Bierman, et al. Informational [Page 4]

RFC 2896 RMON PI Macros August 2000

ether

802-1

Refer to the RMON Protocol Identifier Reference [RFC2895] for
protocol identifier macro definitions for these protocols

3.1. Protocol Stacks And Single-Vendor

Network layer protocol identifier macros contain
information about the network layer, and is found
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
implement a subset of these parameters

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

The following protocol-identifier macro declarations are given
example purposes only. They are not intended to constitute
exhaustive list or an authoritative source for any of the
information given. However, any protocol that can encapsulate
protocols must be documented here in order to encode the
identifiers into protocolDirID strings. Leaf protocols should
documented as well, but an implementation can identify a
protocol even if it isn't listed here (as long as the parent
documented).

3.1.1. The TCP/IP protocol

arp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"An Address Resolution Protocol message (request or response).
This protocol does not include Reverse ARP (RARP) packets,
are counted separately."

"RFC 826 [RFC826] defines the Address Resolution Protocol."

Bierman, et al. Informational [Page 5]

RFC 2896 RMON PI Macros August 2000

::= {
ether2 0x806, -- [ 0.0.8.6 ]
snap 0x806,
802-1Q 0x806 -- [ 0.0.8.6 ]
}

ip PROTOCOL-
PARAMETERS {
countsFragments(0) -- This parameter applies to all
-- protocols
}
ATTRIBUTES {
hasChildren(0),
addressRecognitionCapable(1)
}

"The protocol identifiers for the Internet Protocol (IP).
that IP may be encapsulated within itself, so more than one
the following identifiers may be present in a
protocolDirID string."

"Children of 'ip' are selected by the value in the Protocol
(one octet), as defined in the PROTOCOL NUMBERS table within
Assigned Numbers Document

The value of the Protocol field is encoded in an octet string
[ 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,
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-
"4 octets of the IP address, in network byte order. Each
packet contains two addresses, the source address and
destination address."

"Note: ether2.ip.ipip4.udp is a different protocolDirID
ether2.ip.udp, as identified in the protocolDirTable. As such
two different local protocol index values will be assigned by
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, et al. Informational [Page 6]

RFC 2896 RMON PI Macros August 2000

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

ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers
::= {
ether2 0x0800,
llc 0x06,
snap 0x0800,
-- ip 4, ** represented by the ipip4
-- ip 94, ** represented by the ipip
802-1Q 0x0800, -- [0.0.8.0]
802-1Q 0x02000006 -- 1Q-LLC [2.0.0.6]
}

-- ****************************************************************
--
-- Children of
--
-- ****************************************************************

icmp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Internet Message Control Protocol

"RFC 792 [RFC792] defines the Internet Control Message Protocol."
::= {
ip 1,
ipip4 1,
ipip 1
}

igmp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Internet Group Management Protocol; IGMP is used by IP hosts
report their host group memberships to any immediately
neighboring multicast routers."

"Appendix A of Host Extensions for IP Multicasting [RFC1112]
defines the Internet Group Management Protocol."
::= {
ip 2,
ipip4 2,
ipip 2

Bierman, et al. Informational [Page 7]

RFC 2896 RMON PI Macros August 2000

}

ggp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Gateway-to-Gateway Protocol; DARPA Internet
(historical)"

"RFC 823 [RFC823] defines the Gateway-to-Gateway Protocol."
::= {
ip 3,
ipip4 3,
ipip 3
}

ipip4 PROTOCOL-
PARAMETERS { }
ATTRIBUTES {
hasChildren(0),
addressRecognitionCapable(1)
}

"IP in IP Tunneling

"Children of 'ipip4' are selected and encoded in the same
as children of IP."
ADDRESS-
"The 'ipip4' address format is the same as the IP
format."

"Note: ether2.ip.ipip4.udp is a different protocolDirID
ether2.ip.udp, as identified in the protocolDirTable. As such
two different local protocol index values will be assigned by
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 "

"RFC 1853 [RFC1853] defines IP in IP over Protocol 4."
::= {
ip 4,
ipip4 4,
ipip 4
}

st PROTOCOL-

Bierman, et al. Informational [Page 8]

RFC 2896 RMON PI Macros August 2000

PARAMETERS { }
ATTRIBUTES { }

"Internet Stream Protocol Version 2 (ST2); (historical) ST2 is
experimental resource reservation protocol intended to
end-to-end real-time guarantees over an internet."

"RFC 1819 [RFC1819] defines version 2 of the Internet
Protocol."
::= {
ip 5,
ipip4 5,
ipip 5
}

tcp PROTOCOL-
PARAMETERS { }
ATTRIBUTES {
hasChildren(0)
}

"Transmission Control Protocol

"Children of TCP are identified by the 16 bit Source
Destination Port value as specified in RFC 793. They are
as [ 0.0.a.b], where 'a' is the MSB and 'b' is the LSB of
port value. Both bytes are encoded in network byte order.
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
(ether2.ip.tcp.telnet)"

"RFC 793 [RFC793] defines the Transmission Control Protocol

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

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

egp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

Bierman, et al. Informational [Page 9]

RFC 2896 RMON PI Macros August 2000

"Exterior Gateway Protocol (historical)"

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

igp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Any private interior gateway."

"[RFC1700]"
::= {
ip 9,
ipip4 9,
ipip 9
}

nvp2 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"NVP-II; Network Voice Protocol

"RFC 741 [RFC741] defines the Network Voice Protocol
::= {
ip 11,
ipip4 11,
ipip 11
}

pup PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"PUP Protocol

"Xerox
::= {
ip 12,
ipip4 12,
ipip 12
}

Bierman, et al. Informational [Page 10]

RFC 2896 RMON PI Macros August 2000

xnet PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Cross Net Debugger (historical)"

"[IEN158]"
::= {
ip 15,
ipip4 15,
ipip 15
}

chaos PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"CHAOS Protocol; historical

"J. Noel Chiappa "
::= {
ip 16,
ipip4 16,
ipip 16
}

udp PROTOCOL-
PARAMETERS { }
ATTRIBUTES {
hasChildren(0)
}

"User Datagram Protocol

"Children of UDP are identified by the 16 bit Source
Destination Port value as specified in RFC 768. They are
as [ 0.0.a.b ], where 'a' is the MSB and 'b' is the LSB of
port value. Both bytes are encoded in network byte order.
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)"

"RFC 768 [RFC768] defines the User Datagram Protocol

The following URL defines the authoritative repository
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-
PARAMETERS { }
ATTRIBUTES { }

"Multiplexing Protocol (historical)"

"IEN-90 [IEN-90] defines the Multiplexing Protocol
::= {
ip 18,
ipip4 18,
ipip 18
}

hmp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Host Monitoring Protocol; historical

"RFC 869 [RFC869] defines the Host Monitoring Protocol
::= {
ip 20,
ipip4 20,
ipip 20
}

xns-idp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"XEROX NS IDP

"Xerox Corporation
::= {
ip 22,
ipip4 22,
ipip 22
}

rdp PROTOCOL-
PARAMETERS { }

Bierman, et al. Informational [Page 12]

RFC 2896 RMON PI Macros August 2000

ATTRIBUTES { }

"Reliable Data Protocol

"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-
PARAMETERS { }
ATTRIBUTES { }

"Internet Reliable Transaction Protocol

"RFC 938 [RFC938] defines the Internet Reliable
Protocol functional and interface specification."
::= {
ip 28,
ipip4 28,
ipip 28
}

iso-tp4 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"ISO Transport Protocol Specification

"RFC 905 [RFC905] defines the ISO Transport
Specification; ISO DP 8073"
::= {
ip 29,
ipip4 29,
ipip 29
}

netblt PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Bulk Data Transfer Protocol; historical

"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-
PARAMETERS { }
ATTRIBUTES { }

"MFE Network Services Protocol; historical

"Shuttleworth, B., 'A Documentary of MFENet, a National
Network', UCRL-52317, Lawrence Livermore Labs, Livermore
California, June 1977."
::= {
ip 31,
ipip4 31,
ipip 31
}

idpr PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Inter-Domain Policy Routing Protocol

"RFC 1479 [RFC1479] defines Version 1 of the Inter-Domain
Routing Protocol."
::= {
ip 35,
ipip4 35,
ipip 35
}

idpr-cmtp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"IDPR Control Message Transport Protocol

"RFC 1479 [RFC1479] defines Version 1 of the Inter-Domain
Routing Protocol."
::= {
ip 38,
ipip4 38,
ipip 38
}

Bierman, et al. Informational [Page 14]

RFC 2896 RMON PI Macros August 2000

sdrp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Source Demand Routing Protocol

"RFC 1940 [RFC1940] defines version 1 of the Source
Routing: Packet Format and Forwarding Specification
::= {
ip 42,
ipip4 42,
ipip 42
}

idrp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Inter-Domain Routing Protocol

"RFC 1745 [RFC1745] defines BGP4/IDRP for IP."
::= {
ip 45,
ipip4 45,
ipip 45
}

rsvp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Resource Reservation Setup Protocol

"Resource ReSerVation Protocol (RSVP); Version 1
Specification [RFC2205]."
::= {
ip 46,
ipip4 46,
ipip 46
}

gre PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"General Routing Encapsulation

"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
IPv4 networks
::= {
ip 47,
ipip4 47,
ipip 47
}

nhrp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"NBMA Next Hop Resolution Protocol (NHRP)"

"RFC 2332 [RFC2332] defines the Next Hop Resolution Protocol."
::= {
ip 54,
ipip4 54,
ipip 54
}

priv-host PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any internal host protocol."

"[RFC1700]"
::= {
ip 61,
ipip4 61,
ipip 61
}

priv-net PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any local network protocol."

"[RFC1700]"
::= {
ip 63,
ipip4 63,
ipip 63
}

priv-distfile PROTOCOL-

Bierman, et al. Informational [Page 16]

RFC 2896 RMON PI Macros August 2000

PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any distributed file system."

"[RFC1700]"
::= {
ip 68,
ipip4 68,
ipip 68
}

dgp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Dissimilar Gateway Protocol

"M/A-COM Government Systems, 'Dissimilar Gateway
Specification, Draft Version', Contract no. CS901145,
16, 1987."
::= {
ip 86,
ipip4 86,
ipip 86
}

igrp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"IGRP; Cisco routing protocol

"Cisco Systems, Inc."
::= {
ip 88,
ipip4 88,
ipip 88
}

ospf PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Open Shortest Path First Interior GW Protocol (OSPFIGP)."

"RFC 1583 [RFC1583] defines version 2 of the OSPF protocol."
::= {

Bierman, et al. Informational [Page 17]

RFC 2896 RMON PI Macros August 2000

ip 89,
ipip4 89,
ipip 89
}

mtp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Multicast Transport Protocol

"RFC 1301 [RFC1301] defines the Multicast Transport Protocol."
::= {
ip 92,
ipip4 92,
ipip 92
}

ax-25 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"AX.25 Frame Encapsulation

"RFC 1226 [RFC1226] defines Internet Protocol Encapsulation
AX.25 Frames."
::= {
ip 93,
ipip4 93,
ipip 93
}

ipip PROTOCOL-
PARAMETERS { }
ATTRIBUTES {
hasChildren(0),
addressRecognitionCapable(1)
}

"IP-within-IP Encapsulation Protocol

"Children of 'ipip' are selected and encoded in the same
as children of IP."
ADDRESS-
"The 'ipip' address format is the same as the IP address format."

"Note: ether2.ip.ipip.udp is a different protocolDirID
ether2.ip.udp, as identified in the protocolDirTable. As such

Bierman, et al. Informational [Page 18]

RFC 2896 RMON PI Macros August 2000

two different local protocol index values will be assigned by
agent. E.g. (full INDEX values shown):
ether2.ip.ipip.udp =
16.0.0.0.1.0.0.8.0.0.0.0.94.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 "

"RFC 2003 [RFC2003] defines IP Encapsulation within IP."
::= {
ip 94,
ipip4 94,
ipip 94
}

encap PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Encapsulation Header; A Scheme for an Internet
Protocol: Version 1"

"RFC 1241 [RFC1241] defines version 1 of the ENCAP Protocol."
::= {
ip 98,
ipip4 98,
ipip 98
}

priv-encript PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private encryption scheme."

"[RFC1700]"
::= {
ip 99,
ipip4 99,
ipip 99
}

-- ****************************************************************
--
-- Children of UDP and
--
-- ****************************************************************

tcpmux PROTOCOL-

Bierman, et al. Informational [Page 19]

RFC 2896 RMON PI Macros August 2000

PARAMETERS { }
ATTRIBUTES { }

"TCP Port Service Multiplexer Port."

"RFC 1078 [RFC1078] defines the TCP Port Service
Protocol."
::= { tcp 1 }

rje PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Job Entry Protocol; RJE Logger Port; (historical)."

"RFC 407 [RFC407] defines the Remote Job Entry Protocol."
::= { tcp 5 }

echo PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Echo Protocol for debugging TCP and UDP transports."

"RFC 862 [RFC862] defines the Echo Protocol."
::= {
tcp 7,
udp 7 }

discard PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Discard Protocol for debugging TCP and UDP transports."

"RFC 863 [RFC863] defines the Discard Protocol."
::= {
tcp 9,
udp 9 }

systat PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Retrieve the Active Users list; a debugging tool for TCP and
transports."

"RFC 866 [RFC866] defines the Active Users Protocol."

Bierman, et al. Informational [Page 20]

RFC 2896 RMON PI Macros August 2000

::= {
tcp 11,
udp 11 }

daytime PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Retrieve the current time of day; a debugging tool for TCP
UDP transports."

"RFC 867 [RFC867] defines the Daytime Protocol."
::= {
tcp 13,
udp 13 }

qotd PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Quote of the Day Protocol; retrieve a short message (up to 512
bytes); a debugging tool for TCP and UDP transports."

"RFC 865 [RFC865] defines the Quote of the Day Protocol."
::= {
tcp 17,
udp 17 }

msp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Message Send Protocol

"RFC 1312 [RFC1312] defines the Message Send Protocol."

::= {
tcp 18,
udp 18 }

chargen PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Character Generator Protocol; a debugging tool for TCP and
transports."

"RFC 864 [RFC864] defines the Character Generator Protocol."

Bierman, et al. Informational [Page 21]

RFC 2896 RMON PI Macros August 2000

::= {
tcp 19,
udp 19 }

ftp-data PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"The File Transfer Protocol Data Port; the FTP Server
default data-connection port. "

"RFC 959 [RFC959] defines the File Transfer Protocol. Refer
section 3.2 of [RFC959] for details on FTP data connections."
::= { tcp 20 }

ftp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"The File Transfer Protocol Control Port; An FTP client
an FTP control connection by sending FTP commands from user
(U) to this port."

"RFC 959 [RFC959] defines the File Transfer Protocol."
::= { tcp 21 }

telnet PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"The Telnet Protocol; The purpose of the TELNET Protocol is
provide a fairly general, bi-directional, eight-bit byte
communications facility. Its primary goal is to allow a
method of interfacing terminal devices and terminal-
processes to each other. "

"RFC 854 [RFC854] defines the basic Telnet Protocol."
::= { tcp 23 }

priv-mail PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private mail system."

"[RFC1700]"
::= { tcp 24,
udp 24 }

Bierman, et al. Informational [Page 22]

RFC 2896 RMON PI Macros August 2000

smtp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"The Simple Mail Transfer Protocol; SMTP control and
messages are sent on this port."

"RFC 821 [RFC821] defines the basic Simple Mail
Protocol."
::= { tcp 25 }

priv-print PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private printer server."

"[RFC1700]"
::= { tcp 35,
udp 35 }

time PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Time Protocol

"RFC 868 [RFC868] defines the Time Protocol."
::= { tcp 37,
udp 37 }

rap PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Route Access Protocol

"RFC 1476 [RFC1476] defines the Internet Route Access Protocol."
::= { tcp 38 }

rlp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Resource Location Protocol

"RFC 887 [RFC887] defines the Resource Location Protocol."
::= { udp 39 }

Bierman, et al. Informational [Page 23]

RFC 2896 RMON PI Macros August 2000

graphics PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Graphics Protocol

"RFC 493 [RFC493] defines the Graphics Protocol."
::= { tcp 41,
udp 41 }

nameserver PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Host Name Server Protocol

"IEN 116 [IEN116] defines the Internet Name Server."
::= { udp 42 }

nicname PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"NICNAME/WHOIS Protocol

"RFC 954 [RFC954] defines the NICNAME/Who Is Protocol."
::= { tcp 43 }

mpm-flags PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"MPM FLAGS Protocol; (historical)."

"RFC 759 [RFC759] defines the Message Processing Module."
::= { tcp 44 }

mpm PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Message Processing Module -- Receiver; (historical)."

"RFC 759 [RFC759] defines the Message Processing Module."
::= { tcp 45 }

mpm-snd PROTOCOL-
PARAMETERS { }

Bierman, et al. Informational [Page 24]

RFC 2896 RMON PI Macros August 2000

ATTRIBUTES { }

"Message Processing Module -- Default Send; (historical)."

"RFC 759 [RFC759] defines the Message Processing Module."
::= { tcp 46 }

tacacs PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Login Host Protocol (TACACS)"

"An Access Control Protocol, Sometimes Called TACACS [RFC1492]."
::= { tcp 49 }

re-mail-ck PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Mail Checking Protocol

"RFC 1339 [RFC1339] defines the Remote Mail Checking Protocol."
::= { udp 50 }

xns-time PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"XNS Time Protocol

"Xerox Corporation
::= { tcp 52,
udp 52 }

domain PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Domain Name Service Protocol; DNS may be transported by
UDP [RFC768] or TCP [RFC793]. If the transport is UDP,
requests restricted to 512 bytes in length may be sent to
port."

"RFC 1035 [RFC1035] defines the Bootstrap Protocol."
::= { udp 53,
tcp 53 }

Bierman, et al. Informational [Page 25]

RFC 2896 RMON PI Macros August 2000

xns-ch PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"XNS Clearinghouse

"Xerox Corporation
::= { tcp 54,
udp 54 }

xns-auth PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"XNS Authentication Protocol

"Xerox Corporation
::= { tcp 56,
udp 56 }

priv-term PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private terminal
protocol."

"[RFC1700]"
::= { tcp 57,
udp 57 }

xns-mail PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"XNS Mil Protocol

"Xerox Corporation
::= { tcp 58,
udp 58 }

priv-file PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private file service."

"[RFC1700]"

Bierman, et al. Informational [Page 26]

RFC 2896 RMON PI Macros August 2000

::= { tcp 59,
udp 59 }

tacacs-ds PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Default Server Port; TACACS Access Control Protocol
Service."

"RFC 1492 [RFC1492] defines the TACACS Protocol."
::= { tcp 65 }

sqlnet PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Oracle SQL*NET

"Oracle Corporation
::= { tcp 66 }

bootps PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Bootstrap Protocol Server Protocol; BOOTP Clients send
(usually broadcast) to the bootps port."

"RFC 951 [RFC951] defines the Bootstrap Protocol."
::= { udp 67 }

bootpc PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Bootstrap Protocol Client Protocol; BOOTP Server replies
sent to the BOOTP Client using this destination port."

"RFC 951 [RFC951] defines the Bootstrap Protocol."
::= { udp 68 }

tftp PROTOCOL-
PARAMETERS {
tracksSessions(1)
}
ATTRIBUTES { }

Bierman, et al. Informational [Page 27]

RFC 2896 RMON PI Macros August 2000

"Trivial File Transfer Protocol; Only the first packet of
TFTP transaction will be sent to port 69. If the
attribute is set, then packets for each TFTP transaction will
attributed to tftp, instead of the unregistered port numbers
will be encoded in subsequent packets."

"RFC 1350 [RFC1350] defines the TFTP Protocol (revision 2);
RFC 1782 [RFC1782] defines TFTP Option Extensions
RFC 1783 [RFC1783] defines the TFTP Blocksize Option
RFC 1784 [RFC1784] defines TFTP Timeout Interval and
Size Options."
::= { udp 69 }

gopher PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Internet Gopher Protocol

"RFC 1436 [RFC1436] defines the Gopher Protocol."
::= { tcp 70 }

netrjs-1 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Job Service Protocol; (historical)."

"RFC 740 [RFC740] defines the NETRJS Protocol."
::= { tcp 71 }

netrjs-2 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Job Service Protocol; (historical)."

"RFC 740 [RFC740] defines the NETRJS Protocol."
::= { tcp 72 }

netrjs-3 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Job Service Protocol; (historical)."

"RFC 740 [RFC740] defines the NETRJS Protocol."
::= { tcp 73 }

Bierman, et al. Informational [Page 28]

RFC 2896 RMON PI Macros August 2000

netrjs-4 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Job Service Protocol; (historical)."

"RFC 740 [RFC740] defines the NETRJS Protocol."
::= { tcp 74 }

priv-dialout PROTOCOL-

PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private dial out service."

"[RFC1700]"
::= { tcp 75,
udp 75 }

priv-rje PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private remote job
service."

"[RFC1700]"
::= { tcp 77,
udp 77 }

finger PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Finger User Information Protocol

"RFC 1288 [RFC1288] defines the finger protocol."
::= { tcp 79 }

www-http PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Hypertext Transfer Protocol

"RFC 1945 [RFC1945] defines the Hypertext Transfer
(HTTP/1.0).

Bierman, et al. Informational [Page 29]

RFC 2896 RMON PI Macros August 2000

RFC 2068 [RFC2068] defines the Hypertext Transfer
(HTTP/1.1).
RFC 2069 [RFC2069] defines an Extension to HTTP: Digest
Authentication
RFC 2109 [RFC2109] defines the HTTP State Management Mechanism
RFC 2145 [RFC2145] defines the use and interpretation of
version numbers."
::= { tcp 80 }

priv-termlink PROTOCOL-

PARAMETERS { }
ATTRIBUTES { }

"Pseudo-protocol reserved for any private terminal
protocol."

"[RFC1700]"
::= { tcp 87,
udp 87 }

kerberos PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"The Kerberos Network Authentication Service (V5)"

"RFC 1510 [RFC1510] defines the Kerberos protocol."
::= { udp 88 }

supdup PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"SUPDUP Display; (historical)"

"RFC 734 [RFC734] defines the SUPDUP Protocol."
::= { tcp 95 }

dixie PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"DIXIE Directory Service

"RFC 1249 [RFC1249] defines the DIXIE Protocol."
::= { tcp 96,
udp 96 }

Bierman, et al. Informational [Page 30]

RFC 2896 RMON PI Macros August 2000

hostname PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"NIC Internet Hostname Server Protocol; (historical)"

"RFC 953 [RFC953] defines the Hostname Server Protocol."
::= { tcp 101 }

3com-tsmux PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"3COM-TSMUX

"3Com, Inc."
::= { tcp 106,
udp 106 }

rtelnet PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote User Telnet Protocol; (historical)."

"RFC 818 [RFC818] defines the Remote User Telnet Service."
::= { tcp 107 }

pop2 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Post Office Protocol -- Version 2. Clients establish
with POP2 servers by using this destination port number
Historical."

"RFC 937 [RFC937] defines Version 2 of the Post Office Protocol."
::= { tcp 109 }

pop3 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Post Office Protocol -- Version 3. Clients establish
with POP3 servers by using this destination port number."

"RFC 1725 [RFC1725] defines Version 3 of the Post
Protocol."

Bierman, et al. Informational [Page 31]

RFC 2896 RMON PI Macros August 2000

::= { tcp 110,
udp 110 } -- RFC defines tcp

sunrpc PROTOCOL-

PARAMETERS {
tracksSessions(1) -- learn port mapping of
}
ATTRIBUTES {
hasChildren(0) -- port mapper function
}

"SUN Remote Procedure Call Protocol. Port mapper
requests are sent to this destination port."

"Specific RPC functions are represented as children of the
protocol. Each 'RPC function protocol' is identified by
function number assignment. RPC function number assignments
defined by different naming authorities, depending on
function identifier value
From [RFC1831]:

Program numbers are given out in groups of hexadecimal 20000000
(decimal 536870912) according to the following chart

0 - 1fffffff defined by rpc@sun.
20000000 - 3fffffff defined by
40000000 - 5fffffff
60000000 - 7fffffff
80000000 - 9fffffff
a0000000 - bfffffff
c0000000 - dfffffff
e0000000 - ffffffff

Children of 'sunrpc' are encoded as [ 0.0.0.111], the
identifier component for 'sunrpc', followed by [ a.b.c.d ],
a.b.c.d is the 32 bit binary RPC program number encoded
network byte order. For example, a protocolDirID-fragment
of
0.0.0.111.0.1.134.163

defines the NFS function (and protocol).

Children are named as 'sunrpc' followed by the RPC
number in base 10 format. For example, NFS would be named
'sunrpc 100003'."

"The first packet of many SUNRPC transactions is sent to

Bierman, et al. Informational [Page 32]

RFC 2896 RMON PI Macros August 2000

port- mapper program, and therefore decoded statically
monitoring RFC portmap requests [RFC1831]. Any subsequent
must be decoded and correctly identified by 'remembering'
port assignments used in each RPC function call (as
according to the procedures in the RPC Specification Version 2
[RFC1831]).

In some cases the port mapping for a particular protocol is
known and hard coded into the requesting client. In these
the client will not send portmap requests; instead it will
the SUNRPC request directly to the well known port. These
are rare and are being eliminated over time. NFS is the
significant SUNRPC program of this class. Such programs
still be declared as children of SUNRPC as described
CHILDREN above. How an implementation detects this behaviour
handles it is beyond the scope of this document

The 'tracksSessions(1)' PARAMETER bit is used to indicate
the probe can (and should) monitor portmapper activity
correctly track SUNRPC connections."

"RFC 1831 [RFC1831] defines the Remote Procedure Call
Version 2. The authoritative list of RPC Functions is
by the URL
ftp://ftp.isi.edu/in-notes/iana/assignments/sun-rpc-numbers
::= { tcp 111,
udp 111 }

auth PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Authentication Service; Identification Protocol."

"RFC 1413 [RFC1413] defines the Identification Protocol."
::= { tcp 113 }

sftp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Simple File Transfer Protocol; (historical)."

"RFC 913 [RFC913] defines the Simple File Transfer Protocol."
::= { tcp 115 }

uucp-path PROTOCOL-

Bierman, et al. Informational [Page 33]

RFC 2896 RMON PI Macros August 2000

PARAMETERS { }
ATTRIBUTES { }

"UUCP Path Service

"RFC 915 [RFC915] defines the Network Mail Path Service."
::= { tcp 117 }

nntp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Network News Transfer Protocol

"RFC 977 [RFC977] defines the Network News Transfer Protocol."
::= { tcp 119 }

cfdptkt PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"CFDPTKT; Coherent File Distribution Protocol

"RFC 1235 [RFC1235] defines the Coherent File
Protocol."
::= { udp 120 }

ntp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Network Time Protocol

"RFC 1305 [RFC1305] defines version 3 of the Network
Protocol."
::= { udp 123 }

pwdgen PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Password Generator Protocol

"RFC 972 [RFC972] defines the Password Generator Protocol."
::= { tcp 129,
udp 129 }

cisco-fna PROTOCOL-

Bierman, et al. Informational [Page 34]

RFC 2896 RMON PI Macros August 2000

PARAMETERS { }
ATTRIBUTES { }

"cisco FNATIVE

"Cisco Systems, Inc."
::= { tcp 130,
udp 130 }

cisco-tna PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"cisco TNATIVE

"Cisco Systems, Inc."
::= { tcp 131,
udp 131 }

cisco-sys PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"cisco SYSMAINT

"Cisco Systems, Inc."
::= { tcp 132,
udp 132 }

statsrv PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Statistics Server; (historical)."

"RFC 996 [RFC996] defines the Statistics Server Protocol."
::= { tcp 133,
udp 133 }

-- defined as nbt-name in IPX
-- netbios-ns 137/tcp NETBIOS Name
-- netbios-ns 137/udp NETBIOS Name
-- defined as nbt-data in IPX
-- netbios-dgm 138/tcp NETBIOS Datagram
-- netbios-dgm 138/udp NETBIOS Datagram

-- defined as nbt-session in IPX
-- netbios-ssn 139/tcp NETBIOS Session

Bierman, et al. Informational [Page 35]

RFC 2896 RMON PI Macros August 2000

-- netbios-ssn 139/udp NETBIOS Session

imap2 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Interactive Mail Access Protocol v2;
Internet Message Access Protocol v4 (IMAP4) also uses
server port."

"RFC 1064 [RFC1064] defines Version 2 of the Interactive

Protocol
RFC 1730 [RFC1730] defines Version 4 of the Internet

Protocol."
::= { tcp 143 }

iso-tp0 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"ISO-IP0; ISO-TP0 bridge between TCP and X.25"

"RFC 1086 [RFC1086] defines the ISO-TP0 protocol."
::= { tcp 146,
udp 146 }

iso-ip PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"ISO-IP; Use of the Internet as a Subnetwork for
with the OSI Network Layer

"RFC 1070 [RFC1070] defines the ISO-IP Protocol."
::= { tcp 147,
udp 147 }

hems PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"HEMS; High Level Entity Management System; (historical)."

"RFC 1021 [RFC1021] defines HEMS."
::= { tcp 151 }

Bierman, et al. Informational [Page 36]

RFC 2896 RMON PI Macros August 2000

bftp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Background File Transfer Program

"RFC 1068 [RFC1068] defines the Background File
Program."
::= { tcp 152 }

sgmp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Simple Gateway Monitoring Protocol; (historical)."

"RFC 1028 [RFC1028] defines the Simple Gateway
Protocol."
::= { udp 153 }

pcmail-srv PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"PCMail Server; Distributed Mail System Protocol (DMSP)"

"RFC 1056 [RFC1056] defines the PCMAIL Protocol."
::= { tcp 158 }

sgmp-traps PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Simple Gateway Monitoring Protocol Traps; (historical)."

"RFC 1028 [RFC1028] defines the Simple Gateway

Protocol."
::= { udp 160 }

-- snmp and snmptrap found in the Protocol-Independent
-- snmp 161/udp
-- snmptrap 162/udp

cmip-man PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

Bierman, et al. Informational [Page 37]

RFC 2896 RMON PI Macros August 2000

"CMIP/TCP (CMOT) Manager; (historical)."

"RFC 1095 [RFC1095] defines the Common Management
Services and Protocol over TCP/IP."
::= { tcp 163,
udp 163 }

cmip-agent PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"CMIP/TCP (CMOT) Agent; (historical)."

"RFC 1095 [RFC1095] defines the Common Management
Services and Protocol over TCP/IP."
::= { tcp 164,
udp 164 }

xdmcp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"X Display Manager Control Protocol

"X11 Consortium
::= { udp 177 }

bgp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Border Gateway Protocol

"RFC 1267 [RFC1267] defines version 3 of the Border

Protocol."
::= { tcp 179 }

remote-kis PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote-Knowbot Information Service (KIS)"

"RFC 1739 [RFC1739] describes the KNOWBOT Protocol."
::= { tcp 185,
udp 185 }

Bierman, et al. Informational [Page 38]

RFC 2896 RMON PI Macros August 2000

kis PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Knowbot Information Service (KIS)"

"RFC 1739 [RFC1739] describes the KNOWBOT Protocol."
::= { tcp 186,
udp 186 }

irc PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Internet Relay Chat Protocol

"RFC 1459 [RFC1459] defines the Internet Relay Chat Protocol."
::= { tcp 194,
udp 194 }

smux PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"SMUX; SNMP MUX Protocol and MIB; (historical)."

"RFC 1227 [RFC1227] defines the SMUX Protocol."
::= { tcp 199 }

--
-- AppleTalk applications are defined in the AppleTalk Stack
--
-- at-rtmp 201/tcp AppleTalk Routing
-- at-rtmp 201/udp AppleTalk Routing
-- at-nbp 202/tcp AppleTalk Name
-- at-nbp 202/udp AppleTalk Name
-- at-3 203/tcp AppleTalk
-- at-3 203/udp AppleTalk
-- at-echo 204/tcp AppleTalk
-- at-echo 204/udp AppleTalk
-- at-5 205/tcp AppleTalk
-- at-5 205/udp AppleTalk
-- at-zis 206/tcp AppleTalk Zone
-- at-zis 206/udp AppleTalk Zone
-- at-7 207/tcp AppleTalk
-- at-7 207/udp AppleTalk
-- at-8 208/tcp AppleTalk
-- at-8 208/udp AppleTalk

Bierman, et al. Informational [Page 39]

RFC 2896 RMON PI Macros August 2000

z39-50 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"ANSI Z39.50"

"RFC 1729 [RFC1729] describes the Z39.50 Protocol."
::= { tcp 210 }

ipx-tunnel PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Tunneling IPX Traffic through IP Networks

"RFC 1234 [RFC1234] defines the IPX Tunnel Protocol."
::= { udp 213 }

mpp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Netix Message Posting Protocol

"RFC 1204 [RFC1204] defines the Message Posting Protocol."
::= { tcp 218 }

imap3 PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Interactive Mail Access Protocol v3; (historical)."

"RFC 1203 [RFC1203] defines version 3 of the Interactive
Access Protocol."
::= { tcp 220 }

ldap PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Lightweight Directory Access Protocol

"RFC 1777 [RFC1777] defines Lightweight Directory
Protocol; RFC 1798 [RFC1798] defines Connection-less
X.500 Directory Access Protocol
::= { tcp 389, -- RFC 1777
udp 389 } -- RFC 1798

Bierman, et al. Informational [Page 40]

RFC 2896 RMON PI Macros August 2000

mobileip-agent PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"IP Mobility Support

"RFC 2002 [RFC2002] defines the IP Mobility Support protocol."
::= { udp 434 }

https PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Secure HTTP; HTTP over TLS/SSL

"Netscape; http://home.netscape.com/eng/ssl3/"
::= { tcp 443 }

smtps PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"SMTP protocol over TLS/SSL

"Netscape; http://home.netscape.com/eng/ssl3/"
::= { tcp 465 }

isakmp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Internet Security Association and Key Management
(ISAKMP)"

"RFC 2408 [RFC2408]"
::= { udp 500 }

login PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"BSD Rlogin; remote login a la telnet

"RFC 1282 [RFC1282] defines the BSD Rlogin Protocol."
::= { tcp 513 }

syslog PROTOCOL-
PARAMETERS { }

Bierman, et al. Informational [Page 41]

RFC 2896 RMON PI Macros August 2000

ATTRIBUTES { }

"syslog

"[RFC1700]"
::= { udp 514 }

uucp PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Unix-to-Unix copy protocol

"[RFC1700]"
::= { tcp 540 }

doom PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"DOOM Game;"

" Id Software
::= { tcp 666 }

radius PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Remote Authentication Dial In User Service (RADIUS)"

"RFC 2138 [RFC2138] defines the Radius protocol."
::= { udp 1812 }

radiusacct PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"RADIUS Accounting Protocol

"RFC 2139 [RFC2139] defines the Radius Accounting protocol."
::= { udp 1813 }

--
-- Portmapper Functions; Children of
--

portmapper PROTOCOL-

Bierman, et al. Informational [Page 42]

RFC 2896 RMON PI Macros August 2000

PARAMETERS { }
ATTRIBUTES { }

"SUNRPC PORTMAPPER program. This is the SUNRPC program which
used to locate the UDP/TCP ports on which other SUNRPC
can be found."

"Appendix A of RFC 1057 [RFC1057] describes the
operation."
::= { sunrpc 100000 }

nfs PROTOCOL-
PARAMETERS { }
ATTRIBUTES { }

"Sun Network File System (NFS);"

"NFS is a SUNRPC program which may or may not use the port
SUNRPC program to connect clients and servers. In many cases
NFS server program runs over UDP/TCP port 2049, but
implementation is encouraged to perform further analysis
assuming that a packet to/from this port is a SUNRPC/NFS packet
Likewise an implementation is encouraged to track port