idnits 2.17.1 draft-ietf-rmonmib-rmonprot-mac-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 88 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 96 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' scope of this document."' ) ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 10 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([RFC2074], [RFC2021]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 616 has weird spacing: '...nal and inter...' == Line 1536 has weird spacing: '...fffffff defi...' == Line 1537 has weird spacing: '...fffffff defi...' == Line 1538 has weird spacing: '...fffffff tran...' == Line 1539 has weird spacing: '...fffffff rese...' == (6 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (27 August 1999) is 9010 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC2026' on line 17 looks like a reference -- Missing reference section? 'RFC2021' on line 4005 looks like a reference -- Missing reference section? 'RFC2074' on line 4025 looks like a reference -- Missing reference section? 'RFC2571' on line 4103 looks like a reference -- Missing reference section? 'RFC1155' on line 3729 looks like a reference -- Missing reference section? 'RFC1212' on line 3748 looks like a reference -- Missing reference section? 'RFC1215' on line 3758 looks like a reference -- Missing reference section? 'RFC2578' on line 4131 looks like a reference -- Missing reference section? 'RFC2579' on line 4138 looks like a reference -- Missing reference section? 'RFC2580' on line 4144 looks like a reference -- Missing reference section? 'RFC1157' on line 3734 looks like a reference -- Missing reference section? 'RFC1901' on line 3948 looks like a reference -- Missing reference section? 'RFC1906' on line 3982 looks like a reference -- Missing reference section? 'RFC2572' on line 4109 looks like a reference -- Missing reference section? 'RFC2574' on line 4120 looks like a reference -- Missing reference section? 'RFC1905' on line 3975 looks like a reference -- Missing reference section? 'RFC2573' on line 4115 looks like a reference -- Missing reference section? 'RFC2575' on line 4125 looks like a reference -- Missing reference section? 'RFC2570' on line 4097 looks like a reference -- Missing reference section? 'RFC1800' on line 3927 looks like a reference -- Missing reference section? 'RFC1700' on line 3865 looks like a reference -- Missing reference section? 'RFC826' on line 3561 looks like a reference -- Missing reference section? 'RFC791' on line 3534 looks like a reference -- Missing reference section? 'RFC792' on line 3539 looks like a reference -- Missing reference section? 'RFC1112' on line 3725 looks like a reference -- Missing reference section? 'RFC823' on line 3557 looks like a reference -- Missing reference section? 'RFC1853' on line 3944 looks like a reference -- Missing reference section? 'RFC1819' on line 3936 looks like a reference -- Missing reference section? 'RFC793' on line 3544 looks like a reference -- Missing reference section? 'RFC904' on line 3601 looks like a reference -- Missing reference section? 'RFC741' on line 3522 looks like a reference -- Missing reference section? 'RFC768' on line 3530 looks like a reference -- Missing reference section? 'IEN-90' on line 562 looks like a reference -- Missing reference section? 'RFC869' on line 3593 looks like a reference -- Missing reference section? 'RFC908' on line 3609 looks like a reference -- Missing reference section? 'RFC1151' on line 602 looks like a reference -- Missing reference section? 'RFC938' on line 3625 looks like a reference -- Missing reference section? 'RFC905' on line 3605 looks like a reference -- Missing reference section? 'RFC998' on line 3658 looks like a reference -- Missing reference section? 'RFC1479' on line 3845 looks like a reference -- Missing reference section? 'RFC1940' on line 3989 looks like a reference -- Missing reference section? 'RFC1745' on line 3896 looks like a reference -- Missing reference section? 'RFC2205' on line 4048 looks like a reference -- Missing reference section? 'RFC1701' on line 3869 looks like a reference -- Missing reference section? 'RFC1702' on line 3874 looks like a reference -- Missing reference section? 'RFC2332' on line 4086 looks like a reference -- Missing reference section? 'RFC1583' on line 3862 looks like a reference -- Missing reference section? 'RFC1301' on line 3801 looks like a reference -- Missing reference section? 'RFC1226' on line 3762 looks like a reference -- Missing reference section? 'RFC2003' on line 4001 looks like a reference -- Missing reference section? 'RFC1241' on line 3778 looks like a reference -- Missing reference section? 'RFC1078' on line 3712 looks like a reference -- Missing reference section? 'RFC407' on line 3508 looks like a reference -- Missing reference section? 'RFC862' on line 3571 looks like a reference -- Missing reference section? 'RFC863' on line 3574 looks like a reference -- Missing reference section? 'RFC866' on line 3584 looks like a reference -- Missing reference section? 'RFC867' on line 3587 looks like a reference -- Missing reference section? 'RFC865' on line 3581 looks like a reference -- Missing reference section? 'RFC1312' on line 3809 looks like a reference -- Missing reference section? 'RFC864' on line 3577 looks like a reference -- Missing reference section? 'RFC959' on line 3641 looks like a reference -- Missing reference section? 'RFC854' on line 3567 looks like a reference -- Missing reference section? 'RFC821' on line 3553 looks like a reference -- Missing reference section? 'RFC868' on line 3590 looks like a reference -- Missing reference section? 'RFC1476' on line 3841 looks like a reference -- Missing reference section? 'RFC887' on line 3597 looks like a reference -- Missing reference section? 'RFC493' on line 3512 looks like a reference -- Missing reference section? 'IEN116' on line 1143 looks like a reference -- Missing reference section? 'RFC954' on line 3637 looks like a reference -- Missing reference section? 'RFC759' on line 3526 looks like a reference -- Missing reference section? 'RFC1492' on line 3853 looks like a reference -- Missing reference section? 'RFC1339' on line 3813 looks like a reference -- Missing reference section? 'RFC1035' on line 3684 looks like a reference -- Missing reference section? 'RFC951' on line 3629 looks like a reference -- Missing reference section? 'RFC1350' on line 3817 looks like a reference -- Missing reference section? 'RFC1782' on line 3910 looks like a reference -- Missing reference section? 'RFC1783' on line 3914 looks like a reference -- Missing reference section? 'RFC1784' on line 3918 looks like a reference -- Missing reference section? 'RFC1436' on line 3831 looks like a reference -- Missing reference section? 'RFC740' on line 3519 looks like a reference -- Missing reference section? 'RFC1288' on line 3796 looks like a reference -- Missing reference section? 'RFC1945' on line 3994 looks like a reference -- Missing reference section? 'RFC2068' on line 4013 looks like a reference -- Missing reference section? 'RFC2069' on line 4018 looks like a reference -- Missing reference section? 'RFC2109' on line 4030 looks like a reference -- Missing reference section? 'RFC2145' on line 4043 looks like a reference -- Missing reference section? 'RFC1510' on line 3857 looks like a reference -- Missing reference section? 'RFC734' on line 3516 looks like a reference -- Missing reference section? 'RFC1249' on line 3783 looks like a reference -- Missing reference section? 'RFC953' on line 3633 looks like a reference -- Missing reference section? 'RFC818' on line 3549 looks like a reference -- Missing reference section? 'RFC937' on line 3621 looks like a reference -- Missing reference section? 'RFC1725' on line 3879 looks like a reference -- Missing reference section? 'RFC1831' on line 3940 looks like a reference -- Missing reference section? 'RFC1413' on line 3820 looks like a reference -- Missing reference section? 'RFC913' on line 3613 looks like a reference -- Missing reference section? 'RFC915' on line 3617 looks like a reference -- Missing reference section? 'RFC977' on line 3649 looks like a reference -- Missing reference section? 'RFC1235' on line 3774 looks like a reference -- Missing reference section? 'RFC1305' on line 3805 looks like a reference -- Missing reference section? 'RFC972' on line 3645 looks like a reference -- Missing reference section? 'RFC996' on line 3654 looks like a reference -- Missing reference section? 'RFC1064' on line 3698 looks like a reference -- Missing reference section? 'RFC1730' on line 3888 looks like a reference -- Missing reference section? 'RFC1086' on line 3716 looks like a reference -- Missing reference section? 'RFC1070' on line 3706 looks like a reference -- Missing reference section? 'RFC1021' on line 3674 looks like a reference -- Missing reference section? 'RFC1068' on line 3702 looks like a reference -- Missing reference section? 'RFC1028' on line 3678 looks like a reference -- Missing reference section? 'RFC1056' on line 3689 looks like a reference -- Missing reference section? 'RFC1095' on line 3720 looks like a reference -- Missing reference section? 'RFC1267' on line 3787 looks like a reference -- Missing reference section? 'RFC1739' on line 3892 looks like a reference -- Missing reference section? 'RFC1459' on line 3837 looks like a reference -- Missing reference section? 'RFC1227' on line 3766 looks like a reference -- Missing reference section? 'RFC1729' on line 3883 looks like a reference -- Missing reference section? 'RFC1234' on line 3770 looks like a reference -- Missing reference section? 'RFC1204' on line 3744 looks like a reference -- Missing reference section? 'RFC1203' on line 3740 looks like a reference -- Missing reference section? 'RFC1777' on line 3905 looks like a reference -- Missing reference section? 'RFC1798' on line 3923 looks like a reference -- Missing reference section? 'RFC2002' on line 3998 looks like a reference -- Missing reference section? 'RFC1282' on line 3792 looks like a reference -- Missing reference section? 'RFC2138' on line 4035 looks like a reference -- Missing reference section? 'RFC2139' on line 4040 looks like a reference -- Missing reference section? 'RFC1057' on line 3693 looks like a reference -- Missing reference section? 'RFC1813' on line 3931 looks like a reference -- Missing reference section? 'RFC1001' on line 3662 looks like a reference -- Missing reference section? 'RFC1002' on line 3668 looks like a reference -- Missing reference section? 'RFC1902' on line 3954 looks like a reference -- Missing reference section? 'RFC1420' on line 3828 looks like a reference -- Missing reference section? 'RFC1419' on line 3824 looks like a reference -- Missing reference section? 'IEN158' on line 3504 looks like a reference -- Missing reference section? 'RFC1213' on line 3752 looks like a reference -- Missing reference section? 'RFC1483' on line 3849 looks like a reference -- Missing reference section? 'RFC1757' on line 3901 looks like a reference -- Missing reference section? 'RFC1903' on line 3961 looks like a reference -- Missing reference section? 'RFC1904' on line 3968 looks like a reference -- Missing reference section? 'RFC2037' on line 4009 looks like a reference -- Missing reference section? 'RFC2233' on line 4054 looks like a reference -- Missing reference section? 'RFC2271' on line 4058 looks like a reference -- Missing reference section? 'RFC2272' on line 4064 looks like a reference -- Missing reference section? 'RFC2273' on line 4070 looks like a reference -- Missing reference section? 'RFC2274' on line 4075 looks like a reference -- Missing reference section? 'RFC2275' on line 4080 looks like a reference -- Missing reference section? 'RFC2408' on line 4092 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 10 warnings (==), 149 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 RMONMIB Working Group Andy Bierman 2 Internet Draft Cisco Systems, Inc. 3 Chris Bucci 4 Cisco Systems, Inc. 5 Robin Iddon 6 3Com, Inc. 7 27 August 1999 9 Remote Network Monitoring MIB Protocol Identifier Macros 11 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with all 16 provisions of Section 10 of RFC2026 [RFC2026]. 18 Internet-Drafts are working documents of the Internet Engineering Task 19 Force (IETF), its areas, and its working groups. Note that other groups 20 may also distribute working documents as Internet-Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet- Drafts as reference material 25 or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Distribution of this document is unlimited. Please send comments to the 34 RMONMIB Working Group, . 36 1. Copyright Notice 38 Copyright (C) The Internet Society (1999). All Rights Reserved. 40 2. Abstract 42 This memo contains various protocol identifier examples, which can be 43 used to produce valid protocolDirTable INDEX encodings, as defined by 44 the Remote Network Monitoring MIB Version 2 [RFC2021] and the RMON 45 Protocol Identifier Reference [RMONPROT_REF]. 47 This document contains protocol identifier macros for well-known 48 protocols. A conformant implementation of the RMON-2 MIB [RFC2021] can 49 be accomplished without the use of these protocol identifiers, and 50 accordingly, this document does not specify any IETF standard. It is 51 published to encourage better interoperability between RMON-2 agent 52 implementations, by providing a great deal of RMON related protocol 53 information in one document. 55 The first version of the RMON Protocol Identifiers Document [RFC2074] 56 has been split into a standards-track Reference portion [RMONPROT_REF], 57 and an 'RMON Protocol Identifier Macros' document (this document) which 58 contains the non-normative portion of that specification. 60 3. Table of Contents 62 1 Copyright Notice ................................................ 1 63 2 Abstract ........................................................ 2 64 3 Table of Contents ............................................... 2 65 4 The SNMP Network Management Framework ........................... 3 66 5 Overview ........................................................ 4 67 5.1 Terms ......................................................... 4 68 5.2 Relationship to the Remote Network Monitoring MIB ............. 4 69 5.3 Relationship to the RMON Protocol Identifier Reference ........ 5 70 5.4 Relationship to Other MIBs .................................... 5 71 6 Protocol Identifier Macros ...................................... 5 72 6.1 Protocol Stacks And Single-Vendor Applications ................ 6 73 6.1.1 The TCP/IP protocol stack ................................... 6 74 6.1.2 Novell IPX Stack ............................................ 48 75 6.1.3 The XEROX Protocol Stack .................................... 54 76 6.1.4 AppleTalk Protocol Stack .................................... 56 77 6.1.5 Banyon Vines Protocol Stack ................................. 61 78 6.1.6 The DECNet Protocol Stack ................................... 67 79 6.1.7 The IBM SNA Protocol Stack. ................................ 72 80 6.1.8 The NetBEUI/NetBIOS Family .................................. 73 81 6.2 Multi-stack protocols ......................................... 77 82 7 Intellectual Property ........................................... 79 83 8 Acknowledgements ................................................ 79 84 9 References ...................................................... 80 85 10 Security Considerations ........................................ 94 86 11 Authors' Addresses ............................................. 94 87 12 Full Copyright Statement ....................................... 96 89 4. The SNMP Network Management Framework 91 The SNMP Management Framework presently consists of five major 92 components: 94 o An overall architecture, described in RFC 2571 [RFC2571]. 96 o Mechanisms for describing and naming objects and events for the 97 purpose of management. The first version of this Structure of 98 Management Information (SMI) is called SMIv1 and described in 99 RFC 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. 100 The second version, called SMIv2, is described in RFC 2578 101 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580]. 103 o Message protocols for transferring management information. The 104 first version of the SNMP message protocol is called SNMPv1 and 105 described in RFC 1157 [RFC1157]. A second version of the SNMP 106 message protocol, which is not an Internet standards track 107 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] 108 and RFC 1906 [RFC1906]. The third version of the message 109 protocol is called SNMPv3 and described in RFC 1906 [RFC1906], 110 RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 112 o Protocol operations for accessing management information. The 113 first set of protocol operations and associated PDU formats is 114 described in RFC 1157 [RFC1157]. A second set of protocol 115 operations and associated PDU formats is described in RFC 1905 116 [RFC1905]. 118 o A set of fundamental applications described in RFC 2573 119 [RFC2573] and the view-based access control mechanism described 120 in RFC 2575 [RFC2575]. 122 A more detailed introduction to the current SNMP Management Framework 123 can be found in RFC 2570 [RFC2570]. 125 Managed objects are accessed via a virtual information store, termed 126 the Management Information Base or MIB. Objects in the MIB are 127 defined using the mechanisms defined in the SMI. 129 This memo does not specify a MIB module. 131 5. Overview 133 The RMON-2 MIB [RFC2021] uses hierarchically formatted OCTET STRINGs to 134 globally identify individual protocol encapsulations in the 135 protocolDirTable. 137 This guide contains examples of protocol identifier encapsulations, 138 which can be used to describe valid protocolDirTable entries. The 139 syntax of the protocol identifier descriptor is defined in the RMON 140 Protocol Identifier Reference [RMONPROT_REF]. 142 This document is not intended to be an authoritative reference on the 143 protocols described herein. Refer to the Official Internet Standards 144 document [RFC1800], the Assigned Numbers document [RFC1700], or other 145 appropriate RFCs, IEEE documents, etc. for complete and authoritative 146 protocol information. 148 This is the the second revision of this document, and is intended to 149 replace Section 5 of the first RMON-2 Protocol Identifiers document 150 [RFC2074]. 152 The RMONMIB working group has decided to discontinue maintenance of this 153 Protocol Identifier Macro repository document, due to a lack of 154 contributions from the RMON vendor community. This document is published 155 as an aid in implementation of the protocolDirTable. 157 5.1. Terms 159 Refer to the RMON Protocol Identifier Reference [RMONPROT_REF] for 160 definitions of terms used to describe the Protocol Identifier Macro and 161 aspects of protocolDirTable INDEX encoding. 163 5.2. Relationship to the Remote Network Monitoring MIB 165 This document is intended to describe some protocol identifier macros, 166 which can be converted to valid protocolDirTable INDEX values, using the 167 mapping rules defined in the RMON Protocol Identifier Reference 168 [RMONPROT_REF]. 170 This document is not intended to limit the protocols that may be 171 identified for counting in the RMON-2 MIB. Many protocol encapsulations, 172 not explicitly identified in this document, may be present in an actual 173 implementation of the protocolDirTable. Also, implementations of the 174 protocolDirTable may not include all the protocols identified in the 175 example section below. 177 5.3. Relationship to the RMON Protocol Identifier Reference 179 This document is intentionally separated from the normative reference 180 document defining protocolDirTable INDEX encoding rules and the protocol 181 identifier macro syntax [RMONPROT_REF]. This allows frequent updates to 182 this document without any republication of MIB objects or 183 protocolDirTable INDEX encoding rules. Note that the base layer and 184 IANA assigned protocol identifier macros are located in Reference 185 document, since these encoding values are defined by the RMONMIB WG. 187 Protocol Identifier macros submitted from the RMON working group and 188 community at large (to the RMONMIB WG mailing list at 189 'rmonmib@cisco.com') will be collected and added to this document. 191 Macros submissions will be collected in the IANA's MIB files under the 192 directory "ftp://ftp.isi.edu/mib/rmonmib/rmon2_pi_macros/" and in the 193 RMONMIB working group mailing list message archive file 194 "ftp://ftpeng.cisco.com/ftp/rmonmib/rmonmib". 196 5.4. Relationship to Other MIBs 198 The RMON Protocol Identifier Macros document is intended for use with 199 the RMON Protocol Identifier Reference [RMONPROT_REF] and the RMON-2 MIB 200 protocolDirTable [RFC2021]. It is not relevant to any other MIB, or 201 intended for use with any other MIB. 203 6. Protocol Identifier Macros 205 This section contains protocol identifier macros for some well-known 206 protocols, although some of them may no longer be in use. These macros 207 reference the base layer identifiers found in section 7 of the RMON 208 Protocol Identifier Reference [RMONPROT_REF]. These identifiers are 209 listed below: 211 ether2 212 llc 213 snap 214 vsnap 215 ianaAssigned 216 802-1Q 218 Refer to the RMON Protocol Identifier Reference [RMONPROT_REF] for the 219 protocol identifier macro definitions for these protocols. 221 6.1. Protocol Stacks And Single-Vendor Applications 223 Network layer protocol identifier macros contain additional information 224 about the network layer, and is found immediately following a base 225 layer-identifier in a protocol identifier. 227 The ProtocolDirParameters supported at the network layer are 228 'countsFragments(0)', and 'tracksSessions(1). An agent may choose to 229 implement a subset of these parameters. 231 The protocol-name should be used for the ProtocolDirDescr field. The 232 ProtocolDirType ATTRIBUTES used at the network layer are 233 'hasChildren(0)' and 'addressRecognitionCapable(1)'. Agents may choose 234 to implement a subset of these attributes for each protocol, and 235 therefore limit which tables the indicated protocol can be present (e.g. 236 protocol distribution, host, and matrix tables).. 238 The following protocol-identifier macro declarations are given for 239 example purposes only. They are not intended to constitute an exhaustive 240 list or an authoritative source for any of the protocol information 241 given. However, any protocol that can encapsulate other protocols must 242 be documented here in order to encode the children identifiers into 243 protocolDirID strings. Leaf protocols should be documented as well, but 244 an implementation can identify a leaf protocol even if it isn't listed 245 here (as long as the parent is documented). 247 6.1.1. The TCP/IP protocol stack 249 arp PROTOCOL-IDENTIFIER 250 PARAMETERS { } 251 ATTRIBUTES { } 252 DESCRIPTION 253 "An Address Resolution Protocol message (request or response). 254 This protocol does not include Reverse ARP (RARP) packets, which 255 are counted separately." 256 REFERENCE 257 "RFC 826 [RFC826] defines the Address Resolution Protocol." 258 ::= { 259 ether2 0x806, -- [ 0.0.8.6 ] 260 snap 0x806, 261 802-1Q 0x806 -- [ 0.0.8.6 ] 263 } 265 ip PROTOCOL-IDENTIFIER 266 PARAMETERS { 267 countsFragments(0) -- This parameter applies to all child 268 -- protocols. 269 } 270 ATTRIBUTES { 271 hasChildren(0), 272 addressRecognitionCapable(1) 273 } 274 DESCRIPTION 275 "The protocol identifiers for the Internet Protocol (IP). Note 276 that IP may be encapsulated within itself, so more than one of 277 the following identifiers may be present in a particular 278 protocolDirID string." 279 CHILDREN 280 "Children of 'ip' are selected by the value in the Protocol field 281 (one octet), as defined in the PROTOCOL NUMBERS table within the 282 Assigned Numbers Document. 284 The value of the Protocol field is encoded in an octet string as 285 [ 0.0.0.a ], where 'a' is the protocol field . 287 Children of 'ip' are encoded as [ 0.0.0.a ], and named as 'ip a' 288 where 'a' is the protocol field value. For example, a 289 protocolDirID-fragment value of: 290 0.0.0.1.0.0.8.0.0.0.0.1 292 defines an encapsulation of ICMP (ether2.ip.icmp)" 293 ADDRESS-FORMAT 294 "4 octets of the IP address, in network byte order. Each ip 295 packet contains two addresses, the source address and the 296 destination address." 297 DECODING 298 "Note: ether2.ip.ipip4.udp is a different protocolDirID than 299 ether2.ip.udp, as identified in the protocolDirTable. As such, 300 two different local protocol index values will be assigned by the 301 agent. E.g. (full INDEX values shown): 302 ether2.ip.ipip4.udp = 303 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.4.0.0.0.0 304 ether2.ip.udp = 305 12.0.0.0.1.0.0.8.0.0.0.0.17.3.0.0.0 " 306 REFERENCE 307 "RFC 791 [RFC791] defines the Internet Protocol; The following 308 URL defines the authoritative repository for the PROTOCOL NUMBERS 309 Table: 311 ftp://ftp.isi.edu/in-notes/iana/assignments/protocol-numbers" 312 ::= { 313 ether2 0x0800, 314 llc 0x06, 315 snap 0x0800, 316 -- ip 4, ** represented by the ipip4 macro 317 -- ip 94, ** represented by the ipip macro 318 802-1Q 0x0800, -- [0.0.8.0] 319 802-1Q 0x02000006 -- 1Q-LLC [2.0.0.6] 320 } 322 -- **************************************************************** 323 -- 324 -- Children of IP 325 -- 326 -- **************************************************************** 328 icmp PROTOCOL-IDENTIFIER 329 PARAMETERS { } 330 ATTRIBUTES { } 331 DESCRIPTION 332 "Internet Message Control Protocol" 333 REFERENCE 334 "RFC 792 [RFC792] defines the Internet Control Message Protocol." 335 ::= { 336 ip 1, 337 ipip4 1, 338 ipip 1 339 } 341 igmp PROTOCOL-IDENTIFIER 342 PARAMETERS { } 343 ATTRIBUTES { } 344 DESCRIPTION 345 "Internet Group Management Protocol; IGMP is used by IP hosts to 346 report their host group memberships to any immediately- 347 neighboring multicast routers." 348 REFERENCE 349 "Appendix A of Host Extensions for IP Multicasting [RFC1112] 350 defines the Internet Group Management Protocol." 351 ::= { 352 ip 2, 353 ipip4 2, 354 ipip 2 355 } 357 ggp PROTOCOL-IDENTIFIER 358 PARAMETERS { } 359 ATTRIBUTES { } 360 DESCRIPTION 361 "Gateway-to-Gateway Protocol; DARPA Internet Gateway 362 (historical)" 363 REFERENCE 364 "RFC 823 [RFC823] defines the Gateway-to-Gateway Protocol." 365 ::= { 366 ip 3, 367 ipip4 3, 368 ipip 3 369 } 371 ipip4 PROTOCOL-IDENTIFIER 372 PARAMETERS { } 373 ATTRIBUTES { 374 hasChildren(0), 375 addressRecognitionCapable(1) 376 } 377 DESCRIPTION 378 "IP in IP Tunneling" 379 CHILDREN 380 "Children of 'ipip4' are selected and encoded in the same manner 381 as children of IP." 382 ADDRESS-FORMAT 383 "The 'ipip4' address format is the same as the IP address 384 format." 385 DECODING 386 "Note: ether2.ip.ipip4.udp is a different protocolDirID than 387 ether2.ip.udp, as identified in the protocolDirTable. As such, 388 two different local protocol index values will be assigned by the 389 agent. E.g. (full INDEX values shown): 390 ether2.ip.ipip4.udp = 391 16.0.0.0.1.0.0.8.0.0.0.0.4.0.0.0.17.4.0.0.0.0 392 ether2.ip.udp = 393 12.0.0.0.1.0.0.8.0.0.0.0.17.3.0.0.0 " 394 REFERENCE 395 "RFC 1853 [RFC1853] defines IP in IP over Protocol 4." 396 ::= { 397 ip 4, 398 ipip4 4, 399 ipip 4 400 } 402 st PROTOCOL-IDENTIFIER 403 PARAMETERS { } 404 ATTRIBUTES { } 405 DESCRIPTION 406 "Internet Stream Protocol Version 2 (ST2); (historical) ST2 is an 407 experimental resource reservation protocol intended to provide 408 end-to-end real-time guarantees over an internet." 409 REFERENCE 410 "RFC 1819 [RFC1819] defines version 2 of the Internet Stream 411 Protocol." 413 ::= { 414 ip 5, 415 ipip4 5, 416 ipip 5 417 } 419 tcp PROTOCOL-IDENTIFIER 420 PARAMETERS { } 421 ATTRIBUTES { 422 hasChildren(0) 423 } 424 DESCRIPTION 425 "Transmission Control Protocol" 426 CHILDREN 427 "Children of TCP are identified by the 16 bit Source or 428 Destination Port value as specified in RFC 793. They are encoded 429 as [ 0.0.a.b], where 'a' is the MSB and 'b' is the LSB of the 430 port value. Both bytes are encoded in network byte order. For 431 example, a protocolDirId-fragment of: 432 0.0.0.1.0.0.8.0.0.0.0.6.0.0.0.23 434 identifies an encapsulation of the telnet protocol 435 (ether2.ip.tcp.telnet)" 436 REFERENCE 437 "RFC 793 [RFC793] defines the Transmission Control Protocol. 439 The following URL defines the authoritative repository for 440 reserved and registered TCP port values: 442 ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers" 443 ::= { 444 ip 6, 445 ipip4 6, 446 ipip 6 447 } 449 egp PROTOCOL-IDENTIFIER 450 PARAMETERS { } 451 ATTRIBUTES { } 452 DESCRIPTION 453 "Exterior Gateway Protocol (historical)" 454 REFERENCE 455 "RFC 904 [RFC904] defines the Exterior Gateway Protocol." 456 ::= { 457 ip 8, 458 ipip4 8, 459 ipip 8 460 } 462 igp PROTOCOL-IDENTIFIER 463 PARAMETERS { } 464 ATTRIBUTES { } 465 DESCRIPTION 466 "Any private interior gateway." 467 REFERENCE 468 "[RFC1700]" 469 ::= { 470 ip 9, 471 ipip4 9, 472 ipip 9 473 } 475 nvp2 PROTOCOL-IDENTIFIER 476 PARAMETERS { } 477 ATTRIBUTES { } 478 DESCRIPTION 479 "NVP-II; Network Voice Protocol" 480 REFERENCE 481 "RFC 741 [RFC741] defines the Network Voice Protocol" 482 ::= { 483 ip 11, 484 ipip4 11, 485 ipip 11 486 } 488 pup PROTOCOL-IDENTIFIER 489 PARAMETERS { } 490 ATTRIBUTES { } 491 DESCRIPTION 492 "PUP Protocol" 493 REFERENCE 494 "Xerox" 495 ::= { 496 ip 12, 497 ipip4 12, 498 ipip 12 499 } 501 xnet PROTOCOL-IDENTIFIER 502 PARAMETERS { } 503 ATTRIBUTES { } 504 DESCRIPTION 505 "Cross Net Debugger (historical)" 506 REFERENCE 507 "[IEN158]" 508 ::= { 509 ip 15, 510 ipip4 15, 511 ipip 15 512 } 514 chaos PROTOCOL-IDENTIFIER 515 PARAMETERS { } 516 ATTRIBUTES { } 517 DESCRIPTION 518 "CHAOS Protocol; historical" 519 REFERENCE 520 "J. Noel Chiappa " 521 ::= { 522 ip 16, 523 ipip4 16, 524 ipip 16 525 } 527 udp PROTOCOL-IDENTIFIER 528 PARAMETERS { } 529 ATTRIBUTES { 530 hasChildren(0) 531 } 532 DESCRIPTION 533 "User Datagram Protocol" 534 CHILDREN 535 "Children of UDP are identified by the 16 bit Source or 536 Destination Port value as specified in RFC 768. They are encoded 537 as [ 0.0.a.b ], where 'a' is the MSB and 'b' is the LSB of the 538 port value. Both bytes are encoded in network byte order. For 539 example, a protocolDirId-fragment of: 540 0.0.0.1.0.0.8.0.0.0.0.17.0.0.0.161 542 identifies an encapsulation of SNMP (ether2.ip.udp.snmp)" 543 REFERENCE 544 "RFC 768 [RFC768] defines the User Datagram Protocol. 546 The following URL defines the authoritative repository for 547 reserved and registered UDP port values: 549 ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers" 550 ::= { 551 ip 17, 552 ipip4 17, 553 ipip 17 554 } 556 mux PROTOCOL-IDENTIFIER 557 PARAMETERS { } 558 ATTRIBUTES { } 559 DESCRIPTION 560 "Multiplexing Protocol (historical)" 561 REFERENCE 562 "IEN-90 [IEN-90] defines the Multiplexing Protocol" 563 ::= { 564 ip 18, 565 ipip4 18, 566 ipip 18 567 } 569 hmp PROTOCOL-IDENTIFIER 570 PARAMETERS { } 571 ATTRIBUTES { } 572 DESCRIPTION 573 "Host Monitoring Protocol; historical" 574 REFERENCE 575 "RFC 869 [RFC869] defines the Host Monitoring Protocol" 576 ::= { 577 ip 20, 578 ipip4 20, 579 ipip 20 580 } 582 xns-idp PROTOCOL-IDENTIFIER 583 PARAMETERS { } 584 ATTRIBUTES { } 585 DESCRIPTION 586 "XEROX NS IDP" 587 REFERENCE 588 "Xerox Corporation" 589 ::= { 590 ip 22, 591 ipip4 22, 592 ipip 22 593 } 595 rdp PROTOCOL-IDENTIFIER 596 PARAMETERS { } 597 ATTRIBUTES { } 598 DESCRIPTION 599 "Reliable Data Protocol" 600 REFERENCE 601 "RFC 908 [RFC908] defines the original protocol; RFC 1151 602 [RFC1151] defines version 2 of the Reliable Data Protocol." 603 ::= { 604 ip 27, 605 ipip4 27, 606 ipip 27 607 } 609 irtp PROTOCOL-IDENTIFIER 610 PARAMETERS { } 611 ATTRIBUTES { } 612 DESCRIPTION 613 "Internet Reliable Transaction Protocol" 614 REFERENCE 615 "RFC 938 [RFC938] defines the Internet Reliable Transaction 616 Protocol functional and interface specification." 617 ::= { 618 ip 28, 619 ipip4 28, 620 ipip 28 621 } 623 iso-tp4 PROTOCOL-IDENTIFIER 624 PARAMETERS { } 625 ATTRIBUTES { } 626 DESCRIPTION 627 "ISO Transport Protocol Specification" 628 REFERENCE 629 "RFC 905 [RFC905] defines the ISO Transport Protocol 630 Specification; ISO DP 8073" 631 ::= { 632 ip 29, 633 ipip4 29, 634 ipip 29 635 } 637 netblt PROTOCOL-IDENTIFIER 638 PARAMETERS { } 639 ATTRIBUTES { } 640 DESCRIPTION 641 "Bulk Data Transfer Protocol; historical" 642 REFERENCE 643 "RFC 998 [RFC998] defines NETBLT: A Bulk Data Transfer Protocol." 644 ::= { 645 ip 30, 646 ipip4 30, 647 ipip 30 648 } 650 mfe-nsp PROTOCOL-IDENTIFIER 651 PARAMETERS { } 652 ATTRIBUTES { } 653 DESCRIPTION 654 "MFE Network Services Protocol; historical" 655 REFERENCE 656 "Shuttleworth, B., 'A Documentary of MFENet, a National Computer 657 Network', UCRL-52317, Lawrence Livermore Labs, Livermore, 658 California, June 1977." 659 ::= { 660 ip 31, 661 ipip4 31, 662 ipip 31 663 } 665 idpr PROTOCOL-IDENTIFIER 666 PARAMETERS { } 667 ATTRIBUTES { } 668 DESCRIPTION 669 "Inter-Domain Policy Routing Protocol" 670 REFERENCE 671 "RFC 1479 [RFC1479] defines Version 1 of the Inter-Domain Policy 672 Routing Protocol." 673 ::= { 674 ip 35, 675 ipip4 35, 676 ipip 35 677 } 679 idpr-cmtp PROTOCOL-IDENTIFIER 680 PARAMETERS { } 681 ATTRIBUTES { } 682 DESCRIPTION 683 "IDPR Control Message Transport Protocol" 684 REFERENCE 685 "RFC 1479 [RFC1479] defines Version 1 of the Inter-Domain Policy 686 Routing Protocol." 687 ::= { 688 ip 38, 689 ipip4 38, 690 ipip 38 691 } 693 sdrp PROTOCOL-IDENTIFIER 694 PARAMETERS { } 695 ATTRIBUTES { } 696 DESCRIPTION 697 "Source Demand Routing Protocol" 698 REFERENCE 699 "RFC 1940 [RFC1940] defines version 1 of the Source Demand 700 Routing: Packet Format and Forwarding Specification" 701 ::= { 702 ip 42, 703 ipip4 42, 704 ipip 42 705 } 707 idrp PROTOCOL-IDENTIFIER 708 PARAMETERS { } 709 ATTRIBUTES { } 710 DESCRIPTION 711 "Inter-Domain Routing Protocol" 712 REFERENCE 713 "RFC 1745 [RFC1745] defines BGP4/IDRP for IP." 714 ::= { 715 ip 45, 716 ipip4 45, 717 ipip 45 718 } 720 rsvp PROTOCOL-IDENTIFIER 721 PARAMETERS { } 722 ATTRIBUTES { } 723 DESCRIPTION 724 "Resource Reservation Setup Protocol" 725 REFERENCE 726 "Resource ReSerVation Protocol (RSVP); Version 1 Functional 727 Specification [RFC2205]." 728 ::= { 729 ip 46, 730 ipip4 46, 731 ipip 46 732 } 734 gre PROTOCOL-IDENTIFIER 735 PARAMETERS { } 736 ATTRIBUTES { } 737 DESCRIPTION 738 "General Routing Encapsulation" 739 REFERENCE 740 "RFC 1701 [RFC1701] defines Generic Routing Encapsulation (GRE); 741 RFC 1702 [RFC1702] defines Generic Routing Encapsulation over 742 IPv4 networks" 743 ::= { 744 ip 47, 745 ipip4 47, 746 ipip 47 747 } 749 nhrp PROTOCOL-IDENTIFIER 750 PARAMETERS { } 751 ATTRIBUTES { } 752 DESCRIPTION 753 "NBMA Next Hop Resolution Protocol (NHRP)" 754 REFERENCE 755 "RFC 2332 [RFC2332] defines the Next Hop Resolution Protocol." 756 ::= { 757 ip 54, 758 ipip4 54, 759 ipip 54 760 } 762 priv-host PROTOCOL-IDENTIFIER 763 PARAMETERS { } 764 ATTRIBUTES { } 765 DESCRIPTION 766 "Pseudo-protocol reserved for any internal host protocol." 767 REFERENCE 768 "[RFC1700]" 769 ::= { 770 ip 61, 771 ipip4 61, 772 ipip 61 773 } 775 priv-net PROTOCOL-IDENTIFIER 776 PARAMETERS { } 777 ATTRIBUTES { } 778 DESCRIPTION 779 "Pseudo-protocol reserved for any local network protocol." 780 REFERENCE 781 "[RFC1700]" 782 ::= { 783 ip 63, 784 ipip4 63, 785 ipip 63 786 } 788 priv-distfile PROTOCOL-IDENTIFIER 789 PARAMETERS { } 790 ATTRIBUTES { } 791 DESCRIPTION 792 "Pseudo-protocol reserved for any distributed file system." 793 REFERENCE 794 "[RFC1700]" 795 ::= { 796 ip 68, 797 ipip4 68, 798 ipip 68 799 } 801 dgp PROTOCOL-IDENTIFIER 802 PARAMETERS { } 803 ATTRIBUTES { } 804 DESCRIPTION 805 "Dissimilar Gateway Protocol" 806 REFERENCE 807 "M/A-COM Government Systems, 'Dissimilar Gateway Protocol 808 Specification, Draft Version', Contract no. CS901145, November 809 16, 1987." 810 ::= { 811 ip 86, 812 ipip4 86, 813 ipip 86 814 } 816 igrp PROTOCOL-IDENTIFIER 817 PARAMETERS { } 818 ATTRIBUTES { } 819 DESCRIPTION 820 "IGRP; Cisco routing protocol" 821 REFERENCE 822 "Cisco Systems, Inc." 823 ::= { 824 ip 88, 825 ipip4 88, 826 ipip 88 827 } 829 ospf PROTOCOL-IDENTIFIER 830 PARAMETERS { } 831 ATTRIBUTES { } 832 DESCRIPTION 833 "Open Shortest Path First Interior GW Protocol (OSPFIGP)." 834 REFERENCE 835 "RFC 1583 [RFC1583] defines version 2 of the OSPF protocol." 836 ::= { 837 ip 89, 838 ipip4 89, 839 ipip 89 840 } 842 mtp PROTOCOL-IDENTIFIER 843 PARAMETERS { } 844 ATTRIBUTES { } 845 DESCRIPTION 846 "Multicast Transport Protocol" 847 REFERENCE 848 "RFC 1301 [RFC1301] defines the Multicast Transport Protocol." 849 ::= { 850 ip 92, 851 ipip4 92, 852 ipip 92 853 } 855 ax-25 PROTOCOL-IDENTIFIER 856 PARAMETERS { } 857 ATTRIBUTES { } 858 DESCRIPTION 859 "AX.25 Frame Encapsulation" 860 REFERENCE 861 "RFC 1226 [RFC1226] defines Internet Protocol Encapsulation of 862 AX.25 Frames." 863 ::= { 864 ip 93, 865 ipip4 93, 866 ipip 93 867 } 869 ipip PROTOCOL-IDENTIFIER 870 PARAMETERS { } 871 ATTRIBUTES { 872 hasChildren(0), 873 addressRecognitionCapable(1) 874 } 875 DESCRIPTION 876 "IP-within-IP Encapsulation Protocol" 877 CHILDREN 878 "Children of 'ipip' are selected and encoded in the same manner 879 as children of IP." 880 ADDRESS-FORMAT 881 "The 'ipip' address format is the same as the IP address format." 882 DECODING 883 "Note: ether2.ip.ipip.udp is a different protocolDirID than 884 ether2.ip.udp, as identified in the protocolDirTable. As such, 885 two different local protocol index values will be assigned by the 886 agent. E.g. (full INDEX values shown): 887 ether2.ip.ipip.udp = 888 16.0.0.0.1.0.0.8.0.0.0.0.94.0.0.0.17.4.0.0.0.0 889 ether2.ip.udp = 890 12.0.0.0.1.0.0.8.0.0.0.0.17.3.0.0.0 " 891 REFERENCE 892 "RFC 2003 [RFC2003] defines IP Encapsulation within IP." 893 ::= { 894 ip 94, 895 ipip4 94, 896 ipip 94 897 } 899 encap PROTOCOL-IDENTIFIER 900 PARAMETERS { } 901 ATTRIBUTES { } 902 DESCRIPTION 903 "Encapsulation Header; A Scheme for an Internet Encapsulation 904 Protocol: Version 1" 905 REFERENCE 906 "RFC 1241 [RFC1241] defines version 1 of the ENCAP Protocol." 907 ::= { 908 ip 98, 909 ipip4 98, 910 ipip 98 911 } 913 priv-encript PROTOCOL-IDENTIFIER 914 PARAMETERS { } 915 ATTRIBUTES { } 916 DESCRIPTION 917 "Pseudo-protocol reserved for any private encryption scheme." 918 REFERENCE 919 "[RFC1700]" 920 ::= { 921 ip 99, 922 ipip4 99, 923 ipip 99 924 } 926 -- **************************************************************** 927 -- 928 -- Children of UDP and TCP 929 -- 930 -- **************************************************************** 932 tcpmux PROTOCOL-IDENTIFIER 933 PARAMETERS { } 934 ATTRIBUTES { } 935 DESCRIPTION 936 "TCP Port Service Multiplexer Port." 937 REFERENCE 938 "RFC 1078 [RFC1078] defines the TCP Port Service Multiplexer 939 Protocol." 940 ::= { tcp 1 } 942 rje PROTOCOL-IDENTIFIER 943 PARAMETERS { } 944 ATTRIBUTES { } 945 DESCRIPTION 946 "Remote Job Entry Protocol; RJE Logger Port; (historical)." 947 REFERENCE 948 "RFC 407 [RFC407] defines the Remote Job Entry Protocol." 949 ::= { tcp 5 } 951 echo PROTOCOL-IDENTIFIER 952 PARAMETERS { } 953 ATTRIBUTES { } 954 DESCRIPTION 955 "Echo Protocol for debugging TCP and UDP transports." 956 REFERENCE 957 "RFC 862 [RFC862] defines the Echo Protocol." 958 ::= { 959 tcp 7, 960 udp 7 } 962 discard PROTOCOL-IDENTIFIER 963 PARAMETERS { } 964 ATTRIBUTES { } 965 DESCRIPTION 966 "Discard Protocol for debugging TCP and UDP transports." 967 REFERENCE 968 "RFC 863 [RFC863] defines the Discard Protocol." 969 ::= { 970 tcp 9, 971 udp 9 } 973 systat PROTOCOL-IDENTIFIER 974 PARAMETERS { } 975 ATTRIBUTES { } 976 DESCRIPTION 977 "Retrieve the Active Users list; a debugging tool for TCP and UDP 978 transports." 979 REFERENCE 980 "RFC 866 [RFC866] defines the Active Users Protocol." 981 ::= { 982 tcp 11, 983 udp 11 } 985 daytime PROTOCOL-IDENTIFIER 986 PARAMETERS { } 987 ATTRIBUTES { } 988 DESCRIPTION 989 "Retrieve the current time of day; a debugging tool for TCP and 990 UDP transports." 991 REFERENCE 992 "RFC 867 [RFC867] defines the Daytime Protocol." 993 ::= { 994 tcp 13, 995 udp 13 } 997 qotd PROTOCOL-IDENTIFIER 998 PARAMETERS { } 999 ATTRIBUTES { } 1000 DESCRIPTION 1001 "Quote of the Day Protocol; retrieve a short message (up to 512 1002 bytes); a debugging tool for TCP and UDP transports." 1003 REFERENCE 1004 "RFC 865 [RFC865] defines the Quote of the Day Protocol." 1005 ::= { 1006 tcp 17, 1007 udp 17 } 1009 msp PROTOCOL-IDENTIFIER 1010 PARAMETERS { } 1011 ATTRIBUTES { } 1012 DESCRIPTION 1013 "Message Send Protocol" 1014 REFERENCE 1015 "RFC 1312 [RFC1312] defines the Message Send Protocol." 1017 ::= { 1018 tcp 18, 1019 udp 18 } 1021 chargen PROTOCOL-IDENTIFIER 1022 PARAMETERS { } 1023 ATTRIBUTES { } 1024 DESCRIPTION 1025 "Character Generator Protocol; a debugging tool for TCP and UDP 1026 transports." 1027 REFERENCE 1028 "RFC 864 [RFC864] defines the Character Generator Protocol." 1029 ::= { 1030 tcp 19, 1031 udp 19 } 1033 ftp-data PROTOCOL-IDENTIFIER 1034 PARAMETERS { } 1035 ATTRIBUTES { } 1036 DESCRIPTION 1037 "The File Transfer Protocol Data Port; the FTP Server process 1038 default data-connection port. " 1039 REFERENCE 1040 "RFC 959 [RFC959] defines the File Transfer Protocol. Refer to 1041 section 3.2 of [RFC959] for details on FTP data connections." 1042 ::= { tcp 20 } 1044 ftp PROTOCOL-IDENTIFIER 1045 PARAMETERS { } 1046 ATTRIBUTES { } 1047 DESCRIPTION 1048 "The File Transfer Protocol Control Port; An FTP client initiates 1049 an FTP control connection by sending FTP commands from user port 1050 (U) to this port." 1051 REFERENCE 1052 "RFC 959 [RFC959] defines the File Transfer Protocol." 1053 ::= { tcp 21 } 1055 telnet PROTOCOL-IDENTIFIER 1056 PARAMETERS { } 1057 ATTRIBUTES { } 1058 DESCRIPTION 1059 "The Telnet Protocol; The purpose of the TELNET Protocol is to 1060 provide a fairly general, bi-directional, eight-bit byte oriented 1061 communications facility. Its primary goal is to allow a standard 1062 method of interfacing terminal devices and terminal-oriented 1063 processes to each other. " 1064 REFERENCE 1065 "RFC 854 [RFC854] defines the basic Telnet Protocol." 1066 ::= { tcp 23 } 1068 priv-mail PROTOCOL-IDENTIFIER 1069 PARAMETERS { } 1070 ATTRIBUTES { } 1071 DESCRIPTION 1072 "Pseudo-protocol reserved for any private mail system." 1073 REFERENCE 1074 "[RFC1700]" 1075 ::= { tcp 24, 1076 udp 24 } 1078 smtp PROTOCOL-IDENTIFIER 1079 PARAMETERS { } 1080 ATTRIBUTES { } 1081 DESCRIPTION 1082 "The Simple Mail Transfer Protocol; SMTP control and data 1083 messages are sent on this port." 1084 REFERENCE 1085 "RFC 821 [RFC821] defines the basic Simple Mail Transfer 1086 Protocol." 1087 ::= { tcp 25 } 1089 priv-print PROTOCOL-IDENTIFIER 1090 PARAMETERS { } 1091 ATTRIBUTES { } 1092 DESCRIPTION 1093 "Pseudo-protocol reserved for any private printer server." 1094 REFERENCE 1095 "[RFC1700]" 1096 ::= { tcp 35, 1097 udp 35 } 1099 time PROTOCOL-IDENTIFIER 1100 PARAMETERS { } 1101 ATTRIBUTES { } 1102 DESCRIPTION 1103 "Time Protocol" 1104 REFERENCE 1105 "RFC 868 [RFC868] defines the Time Protocol." 1106 ::= { tcp 37, 1107 udp 37 } 1109 rap PROTOCOL-IDENTIFIER 1110 PARAMETERS { } 1111 ATTRIBUTES { } 1112 DESCRIPTION 1113 "Route Access Protocol" 1114 REFERENCE 1115 "RFC 1476 [RFC1476] defines the Internet Route Access Protocol." 1116 ::= { tcp 38 } 1118 rlp PROTOCOL-IDENTIFIER 1119 PARAMETERS { } 1120 ATTRIBUTES { } 1121 DESCRIPTION 1122 "Resource Location Protocol" 1123 REFERENCE 1124 "RFC 887 [RFC887] defines the Resource Location Protocol." 1125 ::= { udp 39 } 1127 graphics PROTOCOL-IDENTIFIER 1128 PARAMETERS { } 1129 ATTRIBUTES { } 1130 DESCRIPTION 1131 "Graphics Protocol" 1132 REFERENCE 1133 "RFC 493 [RFC493] defines the Graphics Protocol." 1134 ::= { tcp 41, 1135 udp 41 } 1137 nameserver PROTOCOL-IDENTIFIER 1138 PARAMETERS { } 1139 ATTRIBUTES { } 1140 DESCRIPTION 1141 "Host Name Server Protocol" 1142 REFERENCE 1143 "IEN 116 [IEN116] defines the Internet Name Server." 1144 ::= { udp 42 } 1146 nicname PROTOCOL-IDENTIFIER 1147 PARAMETERS { } 1148 ATTRIBUTES { } 1149 DESCRIPTION 1150 "NICNAME/WHOIS Protocol" 1151 REFERENCE 1152 "RFC 954 [RFC954] defines the NICNAME/Who Is Protocol." 1153 ::= { tcp 43 } 1155 mpm-flags PROTOCOL-IDENTIFIER 1156 PARAMETERS { } 1157 ATTRIBUTES { } 1158 DESCRIPTION 1159 "MPM FLAGS Protocol; (historical)." 1160 REFERENCE 1161 "RFC 759 [RFC759] defines the Message Processing Module." 1162 ::= { tcp 44 } 1164 mpm PROTOCOL-IDENTIFIER 1165 PARAMETERS { } 1166 ATTRIBUTES { } 1167 DESCRIPTION 1168 "Message Processing Module -- Receiver; (historical)." 1169 REFERENCE 1170 "RFC 759 [RFC759] defines the Message Processing Module." 1171 ::= { tcp 45 } 1173 mpm-snd PROTOCOL-IDENTIFIER 1174 PARAMETERS { } 1175 ATTRIBUTES { } 1176 DESCRIPTION 1177 "Message Processing Module -- Default Send; (historical)." 1178 REFERENCE 1179 "RFC 759 [RFC759] defines the Message Processing Module." 1180 ::= { tcp 46 } 1182 tacacs PROTOCOL-IDENTIFIER 1183 PARAMETERS { } 1184 ATTRIBUTES { } 1185 DESCRIPTION 1186 "Login Host Protocol (TACACS)" 1187 REFERENCE 1188 "An Access Control Protocol, Sometimes Called TACACS [RFC1492]." 1189 ::= { tcp 49 } 1191 re-mail-ck PROTOCOL-IDENTIFIER 1192 PARAMETERS { } 1193 ATTRIBUTES { } 1194 DESCRIPTION 1195 "Remote Mail Checking Protocol" 1196 REFERENCE 1197 "RFC 1339 [RFC1339] defines the Remote Mail Checking Protocol." 1198 ::= { udp 50 } 1200 xns-time PROTOCOL-IDENTIFIER 1201 PARAMETERS { } 1202 ATTRIBUTES { } 1203 DESCRIPTION 1204 "XNS Time Protocol" 1205 REFERENCE 1206 "Xerox Corporation" 1207 ::= { tcp 52, 1208 udp 52 } 1210 domain PROTOCOL-IDENTIFIER 1211 PARAMETERS { } 1212 ATTRIBUTES { } 1213 DESCRIPTION 1214 "Domain Name Service Protocol; DNS may be transported by either 1215 UDP [RFC768] or TCP [RFC793]. If the transport is UDP, DNS 1216 requests restricted to 512 bytes in length may be sent to this 1217 port." 1218 REFERENCE 1219 "RFC 1035 [RFC1035] defines the Bootstrap Protocol." 1220 ::= { udp 53, 1221 tcp 53 } 1223 xns-ch PROTOCOL-IDENTIFIER 1224 PARAMETERS { } 1225 ATTRIBUTES { } 1226 DESCRIPTION 1227 "XNS Clearinghouse" 1228 REFERENCE 1229 "Xerox Corporation" 1230 ::= { tcp 54, 1231 udp 54 } 1233 xns-auth PROTOCOL-IDENTIFIER 1234 PARAMETERS { } 1235 ATTRIBUTES { } 1236 DESCRIPTION 1237 "XNS Authentication Protocol" 1238 REFERENCE 1239 "Xerox Corporation" 1240 ::= { tcp 56, 1241 udp 56 } 1243 priv-term PROTOCOL-IDENTIFIER 1244 PARAMETERS { } 1245 ATTRIBUTES { } 1246 DESCRIPTION 1247 "Pseudo-protocol reserved for any private terminal access 1248 protocol." 1249 REFERENCE 1250 "[RFC1700]" 1251 ::= { tcp 57, 1252 udp 57 } 1254 xns-mail PROTOCOL-IDENTIFIER 1255 PARAMETERS { } 1256 ATTRIBUTES { } 1257 DESCRIPTION 1258 "XNS Mil Protocol" 1259 REFERENCE 1260 "Xerox Corporation" 1261 ::= { tcp 58, 1262 udp 58 } 1264 priv-file PROTOCOL-IDENTIFIER 1265 PARAMETERS { } 1266 ATTRIBUTES { } 1267 DESCRIPTION 1268 "Pseudo-protocol reserved for any private file service." 1269 REFERENCE 1270 "[RFC1700]" 1271 ::= { tcp 59, 1272 udp 59 } 1274 tacacs-ds PROTOCOL-IDENTIFIER 1275 PARAMETERS { } 1276 ATTRIBUTES { } 1277 DESCRIPTION 1278 "Default Server Port; TACACS Access Control Protocol Database 1279 Service." 1280 REFERENCE 1281 "RFC 1492 [RFC1492] defines the TACACS Protocol." 1282 ::= { tcp 65 } 1284 sql*net PROTOCOL-IDENTIFIER 1285 PARAMETERS { } 1286 ATTRIBUTES { } 1287 DESCRIPTION 1288 "Oracle SQL*NET" 1289 REFERENCE 1290 "Oracle Corporation" 1291 ::= { tcp 66 } 1293 bootps PROTOCOL-IDENTIFIER 1294 PARAMETERS { } 1295 ATTRIBUTES { } 1296 DESCRIPTION 1297 "Bootstrap Protocol Server Protocol; BOOTP Clients send requests 1298 (usually broadcast) to the bootps port." 1299 REFERENCE 1300 "RFC 951 [RFC951] defines the Bootstrap Protocol." 1301 ::= { udp 67 } 1303 bootpc PROTOCOL-IDENTIFIER 1304 PARAMETERS { } 1305 ATTRIBUTES { } 1306 DESCRIPTION 1307 "Bootstrap Protocol Client Protocol; BOOTP Server replies are 1308 sent to the BOOTP Client using this destination port." 1309 REFERENCE 1310 "RFC 951 [RFC951] defines the Bootstrap Protocol." 1311 ::= { udp 68 } 1313 tftp PROTOCOL-IDENTIFIER 1314 PARAMETERS { 1315 tracksSessions(1) 1316 } 1317 ATTRIBUTES { } 1318 DESCRIPTION 1319 "Trivial File Transfer Protocol; Only the first packet of each 1320 TFTP transaction will be sent to port 69. If the tracksSessions 1321 attribute is set, then packets for each TFTP transaction will be 1322 attributed to tftp, instead of the unregistered port numbers that 1323 will be encoded in subsequent packets." 1324 REFERENCE 1325 "RFC 1350 [RFC1350] defines the TFTP Protocol (revision 2); 1326 RFC 1782 [RFC1782] defines TFTP Option Extensions; 1327 RFC 1783 [RFC1783] defines the TFTP Blocksize Option; 1328 RFC 1784 [RFC1784] defines TFTP Timeout Interval and Transfer Size 1329 Options." 1330 ::= { udp 69 } 1332 gopher PROTOCOL-IDENTIFIER 1333 PARAMETERS { } 1334 ATTRIBUTES { } 1335 DESCRIPTION 1336 "Internet Gopher Protocol" 1337 REFERENCE 1338 "RFC 1436 [RFC1436] defines the Gopher Protocol." 1339 ::= { tcp 70 } 1341 netrjs-1 PROTOCOL-IDENTIFIER 1342 PARAMETERS { } 1343 ATTRIBUTES { } 1344 DESCRIPTION 1345 "Remote Job Service Protocol; (historical)." 1346 REFERENCE 1347 "RFC 740 [RFC740] defines the NETRJS Protocol." 1348 ::= { tcp 71 } 1350 netrjs-2 PROTOCOL-IDENTIFIER 1351 PARAMETERS { } 1352 ATTRIBUTES { } 1353 DESCRIPTION 1354 "Remote Job Service Protocol; (historical)." 1355 REFERENCE 1356 "RFC 740 [RFC740] defines the NETRJS Protocol." 1357 ::= { tcp 72 } 1359 netrjs-3 PROTOCOL-IDENTIFIER 1360 PARAMETERS { } 1361 ATTRIBUTES { } 1362 DESCRIPTION 1363 "Remote Job Service Protocol; (historical)." 1364 REFERENCE 1365 "RFC 740 [RFC740] defines the NETRJS Protocol." 1366 ::= { tcp 73 } 1368 netrjs-4 PROTOCOL-IDENTIFIER 1369 PARAMETERS { } 1370 ATTRIBUTES { } 1371 DESCRIPTION 1372 "Remote Job Service Protocol; (historical)." 1373 REFERENCE 1374 "RFC 740 [RFC740] defines the NETRJS Protocol." 1375 ::= { tcp 74 } 1377 priv-dialout PROTOCOL-IDENTIFIER 1378 PARAMETERS { } 1379 ATTRIBUTES { } 1380 DESCRIPTION 1381 "Pseudo-protocol reserved for any private dial out service." 1382 REFERENCE 1383 "[RFC1700]" 1384 ::= { tcp 75, 1385 udp 75 } 1387 priv-rje PROTOCOL-IDENTIFIER 1388 PARAMETERS { } 1389 ATTRIBUTES { } 1390 DESCRIPTION 1391 "Pseudo-protocol reserved for any private remote job entry 1392 service." 1393 REFERENCE 1394 "[RFC1700]" 1395 ::= { tcp 77, 1396 udp 77 } 1398 finger PROTOCOL-IDENTIFIER 1399 PARAMETERS { } 1400 ATTRIBUTES { } 1401 DESCRIPTION 1402 "Finger User Information Protocol" 1403 REFERENCE 1404 "RFC 1288 [RFC1288] defines the finger protocol." 1405 ::= { tcp 79 } 1407 www-http PROTOCOL-IDENTIFIER 1408 PARAMETERS { } 1409 ATTRIBUTES { } 1410 DESCRIPTION 1411 "Hypertext Transfer Protocol" 1412 REFERENCE 1413 "RFC 1945 [RFC1945] defines the Hypertext Transfer Protocol 1414 (HTTP/1.0). 1415 RFC 2068 [RFC2068] defines the Hypertext Transfer Protocol 1416 (HTTP/1.1). 1417 RFC 2069 [RFC2069] defines an Extension to HTTP: Digest Access 1418 Authentication. 1419 RFC 2109 [RFC2109] defines the HTTP State Management Mechanism. 1420 RFC 2145 [RFC2145] defines the use and interpretation of HTTP 1421 version numbers." 1422 ::= { tcp 80 } 1424 priv-termlink PROTOCOL-IDENTIFIER 1425 PARAMETERS { } 1426 ATTRIBUTES { } 1427 DESCRIPTION 1428 "Pseudo-protocol reserved for any private terminal link 1429 protocol." 1430 REFERENCE 1431 "[RFC1700]" 1432 ::= { tcp 87, 1433 udp 87 } 1435 kerberos PROTOCOL-IDENTIFIER 1436 PARAMETERS { } 1437 ATTRIBUTES { } 1438 DESCRIPTION 1439 "The Kerberos Network Authentication Service (V5)" 1440 REFERENCE 1441 "RFC 1510 [RFC1510] defines the Kerberos protocol." 1442 ::= { udp 88 } 1444 supdup PROTOCOL-IDENTIFIER 1445 PARAMETERS { } 1446 ATTRIBUTES { } 1447 DESCRIPTION 1448 "SUPDUP Display; (historical)" 1449 REFERENCE 1450 "RFC 734 [RFC734] defines the SUPDUP Protocol." 1451 ::= { tcp 95 } 1453 dixie PROTOCOL-IDENTIFIER 1454 PARAMETERS { } 1455 ATTRIBUTES { } 1456 DESCRIPTION 1457 "DIXIE Directory Service" 1458 REFERENCE 1459 "RFC 1249 [RFC1249] defines the DIXIE Protocol." 1460 ::= { tcp 96, 1461 udp 96 } 1463 hostname PROTOCOL-IDENTIFIER 1464 PARAMETERS { } 1465 ATTRIBUTES { } 1466 DESCRIPTION 1467 "NIC Internet Hostname Server Protocol; (historical)" 1468 REFERENCE 1469 "RFC 953 [RFC953] defines the Hostname Server Protocol." 1471 ::= { tcp 101 } 1473 3com-tsmux PROTOCOL-IDENTIFIER 1474 PARAMETERS { } 1475 ATTRIBUTES { } 1476 DESCRIPTION 1477 "3COM-TSMUX" 1478 REFERENCE 1479 "3Com, Inc." 1480 ::= { tcp 106, 1481 udp 106 } 1483 rtelnet PROTOCOL-IDENTIFIER 1484 PARAMETERS { } 1485 ATTRIBUTES { } 1486 DESCRIPTION 1487 "Remote User Telnet Protocol; (historical)." 1488 REFERENCE 1489 "RFC 818 [RFC818] defines the Remote User Telnet Service." 1490 ::= { tcp 107 } 1492 pop2 PROTOCOL-IDENTIFIER 1493 PARAMETERS { } 1494 ATTRIBUTES { } 1495 DESCRIPTION 1496 "Post Office Protocol -- Version 2. Clients establish connections 1497 with POP2 servers by using this destination port number. 1498 Historical." 1499 REFERENCE 1500 "RFC 937 [RFC937] defines Version 2 of the Post Office Protocol." 1501 ::= { tcp 109 } 1503 pop3 PROTOCOL-IDENTIFIER 1504 PARAMETERS { } 1505 ATTRIBUTES { } 1506 DESCRIPTION 1507 "Post Office Protocol -- Version 3. Clients establish connections 1508 with POP3 servers by using this destination port number." 1509 REFERENCE 1510 "RFC 1725 [RFC1725] defines Version 3 of the Post Office 1511 Protocol." 1512 ::= { tcp 110, 1513 udp 110 } -- RFC defines tcp use 1515 sunrpc PROTOCOL-IDENTIFIER 1516 PARAMETERS { 1517 tracksSessions(1) -- learn port mapping of programs 1518 } 1519 ATTRIBUTES { 1520 hasChildren(0) -- port mapper function numbers 1521 } 1522 DESCRIPTION 1523 "SUN Remote Procedure Call Protocol. Port mapper function 1524 requests are sent to this destination port." 1525 CHILDREN 1526 "Specific RPC functions are represented as children of the sunrpc 1527 protocol. Each 'RPC function protocol' is identified by its 1528 function number assignment. RPC function number assignments are 1529 defined by different naming authorities, depending on the 1530 function identifier value. 1531 From [RFC1831]: 1533 Program numbers are given out in groups of hexadecimal 20000000 1534 (decimal 536870912) according to the following chart: 1536 0 - 1fffffff defined by rpc@sun.com 1537 20000000 - 3fffffff defined by user 1538 40000000 - 5fffffff transient 1539 60000000 - 7fffffff reserved 1540 80000000 - 9fffffff reserved 1541 a0000000 - bfffffff reserved 1542 c0000000 - dfffffff reserved 1543 e0000000 - ffffffff reserved 1545 Children of 'sunrpc' are encoded as [ 0.0.0.111], the protocol 1546 identifier component for 'sunrpc', followed by [ a.b.c.d ], where 1547 a.b.c.d is the 32 bit binary RPC program number encoded in 1548 network byte order. For example, a protocolDirID-fragment value 1549 of: 1550 0.0.0.111.0.1.134.163 1552 defines the NFS function (and protocol). 1554 Children are named as 'sunrpc' followed by the RPC function 1555 number in base 10 format. For example, NFS would be named: 1556 'sunrpc 100003'." 1557 DECODING 1558 "The first packet of many SUNRPC transactions is sent to the 1559 port- mapper program, and therefore decoded statically by 1560 monitoring RFC portmap requests [RFC1831]. Any subsequent packets 1561 must be decoded and correctly identified by 'remembering' the 1562 port assignments used in each RPC function call (as identified 1563 according to the procedures in the RPC Specification Version 2 1564 [RFC1831]). 1566 In some cases the port mapping for a particular protocol is well 1567 known and hard coded into the requesting client. In these cases 1568 the client will not send portmap requests; instead it will send 1569 the SUNRPC request directly to the well known port. These cases 1570 are rare and are being eliminated over time. NFS is the most 1571 significant SUNRPC program of this class. Such programs should 1572 still be declared as children of SUNRPC as described under 1573 CHILDREN above. How an implementation detects this behaviour and 1574 handles it is beyond the scope of this document. 1576 The 'tracksSessions(1)' PARAMETER bit is used to indicate whether 1577 the probe can (and should) monitor portmapper activity to 1578 correctly track SUNRPC connections." 1579 REFERENCE 1580 "RFC 1831 [RFC1831] defines the Remote Procedure Call Protocol 1581 Version 2. The authoritative list of RPC Functions is identified 1582 by the URL: 1583 ftp://ftp.isi.edu/in-notes/iana/assignments/sun-rpc-numbers" 1584 ::= { tcp 111, 1585 udp 111 } 1587 auth PROTOCOL-IDENTIFIER 1588 PARAMETERS { } 1589 ATTRIBUTES { } 1590 DESCRIPTION 1591 "Authentication Service; Identification Protocol." 1592 REFERENCE 1593 "RFC 1413 [RFC1413] defines the Identification Protocol." 1594 ::= { tcp 113 } 1596 sftp PROTOCOL-IDENTIFIER 1597 PARAMETERS { } 1598 ATTRIBUTES { } 1599 DESCRIPTION 1600 "Simple File Transfer Protocol; (historical)." 1601 REFERENCE 1602 "RFC 913 [RFC913] defines the Simple File Transfer Protocol." 1603 ::= { tcp 115 } 1605 uucp-path PROTOCOL-IDENTIFIER 1606 PARAMETERS { } 1607 ATTRIBUTES { } 1608 DESCRIPTION 1609 "UUCP Path Service" 1610 REFERENCE 1611 "RFC 915 [RFC915] defines the Network Mail Path Service." 1612 ::= { tcp 117 } 1614 nntp PROTOCOL-IDENTIFIER 1615 PARAMETERS { } 1616 ATTRIBUTES { } 1617 DESCRIPTION 1618 "Network News Transfer Protocol" 1619 REFERENCE 1620 "RFC 977 [RFC977] defines the Network News Transfer Protocol." 1621 ::= { tcp 119 } 1623 cfdptkt PROTOCOL-IDENTIFIER 1624 PARAMETERS { } 1625 ATTRIBUTES { } 1626 DESCRIPTION 1627 "CFDPTKT; Coherent File Distribution Protocol" 1628 REFERENCE 1629 "RFC 1235 [RFC1235] defines the Coherent File Distribution 1630 Protocol." 1631 ::= { udp 120 } 1633 ntp PROTOCOL-IDENTIFIER 1634 PARAMETERS { } 1635 ATTRIBUTES { } 1636 DESCRIPTION 1637 "Network Time Protocol" 1638 REFERENCE 1639 "RFC 1305 [RFC1305] defines version 3 of the Network Time 1640 Protocol." 1641 ::= { udp 123 } 1643 pwdgen PROTOCOL-IDENTIFIER 1644 PARAMETERS { } 1645 ATTRIBUTES { } 1646 DESCRIPTION 1647 "Password Generator Protocol" 1648 REFERENCE 1649 "RFC 972 [RFC972] defines the Password Generator Protocol." 1650 ::= { tcp 129, 1651 udp 129 } 1653 cisco-fna PROTOCOL-IDENTIFIER 1654 PARAMETERS { } 1655 ATTRIBUTES { } 1656 DESCRIPTION 1657 "cisco FNATIVE" 1658 REFERENCE 1659 "Cisco Systems, Inc." 1660 ::= { tcp 130, 1661 udp 130 } 1663 cisco-tna PROTOCOL-IDENTIFIER 1664 PARAMETERS { } 1665 ATTRIBUTES { } 1666 DESCRIPTION 1667 "cisco TNATIVE" 1668 REFERENCE 1669 "Cisco Systems, Inc." 1670 ::= { tcp 131, 1671 udp 131 } 1673 cisco-sys PROTOCOL-IDENTIFIER 1674 PARAMETERS { } 1675 ATTRIBUTES { } 1676 DESCRIPTION 1677 "cisco SYSMAINT" 1678 REFERENCE 1679 "Cisco Systems, Inc." 1680 ::= { tcp 132, 1681 udp 132 } 1683 statsrv PROTOCOL-IDENTIFIER 1684 PARAMETERS { } 1685 ATTRIBUTES { } 1686 DESCRIPTION 1687 "Statistics Server; (historical)." 1688 REFERENCE 1689 "RFC 996 [RFC996] defines the Statistics Server Protocol." 1690 ::= { tcp 133, 1691 udp 133 } 1693 -- defined as nbt-name in IPX section 1694 -- netbios-ns 137/tcp NETBIOS Name Service 1695 -- netbios-ns 137/udp NETBIOS Name Service 1696 -- defined as nbt-data in IPX section 1697 -- netbios-dgm 138/tcp NETBIOS Datagram Service 1698 -- netbios-dgm 138/udp NETBIOS Datagram Service 1700 -- defined as nbt-session in IPX section 1701 -- netbios-ssn 139/tcp NETBIOS Session Service 1702 -- netbios-ssn 139/udp NETBIOS Session Service 1704 imap2 PROTOCOL-IDENTIFIER 1705 PARAMETERS { } 1706 ATTRIBUTES { } 1707 DESCRIPTION 1708 "Interactive Mail Access Protocol v2; 1709 Internet Message Access Protocol v4 (IMAP4) also uses this 1710 server port." 1711 REFERENCE 1712 "RFC 1064 [RFC1064] defines Version 2 of the Interactive Mail 1713 Access 1714 Protocol. 1715 RFC 1730 [RFC1730] defines Version 4 of the Internet Message 1716 Access 1717 Protocol." 1718 ::= { tcp 143 } 1720 iso-tp0 PROTOCOL-IDENTIFIER 1721 PARAMETERS { } 1722 ATTRIBUTES { } 1723 DESCRIPTION 1724 "ISO-IP0; ISO-TP0 bridge between TCP and X.25" 1725 REFERENCE 1726 "RFC 1086 [RFC1086] defines the ISO-TP0 protocol." 1727 ::= { tcp 146, 1728 udp 146 } 1730 iso-ip PROTOCOL-IDENTIFIER 1731 PARAMETERS { } 1732 ATTRIBUTES { } 1733 DESCRIPTION 1734 "ISO-IP; Use of the Internet as a Subnetwork for Experimentation 1735 with the OSI Network Layer" 1736 REFERENCE 1737 "RFC 1070 [RFC1070] defines the ISO-IP Protocol." 1738 ::= { tcp 147, 1739 udp 147 } 1741 hems PROTOCOL-IDENTIFIER 1742 PARAMETERS { } 1743 ATTRIBUTES { } 1744 DESCRIPTION 1745 "HEMS; High Level Entity Management System; (historical)." 1746 REFERENCE 1747 "RFC 1021 [RFC1021] defines HEMS." 1748 ::= { tcp 151 } 1750 bftp PROTOCOL-IDENTIFIER 1751 PARAMETERS { } 1752 ATTRIBUTES { } 1753 DESCRIPTION 1754 "Background File Transfer Program" 1755 REFERENCE 1756 "RFC 1068 [RFC1068] defines the Background File Transfer 1757 Program." 1758 ::= { tcp 152 } 1760 sgmp PROTOCOL-IDENTIFIER 1761 PARAMETERS { } 1762 ATTRIBUTES { } 1763 DESCRIPTION 1764 "Simple Gateway Monitoring Protocol; (historical)." 1765 REFERENCE 1766 "RFC 1028 [RFC1028] defines the Simple Gateway Monitoring 1767 Protocol." 1768 ::= { udp 153 } 1770 pcmail-srv PROTOCOL-IDENTIFIER 1771 PARAMETERS { } 1772 ATTRIBUTES { } 1773 DESCRIPTION 1774 "PCMail Server; Distributed Mail System Protocol (DMSP)" 1775 REFERENCE 1776 "RFC 1056 [RFC1056] defines the PCMAIL Protocol." 1777 ::= { tcp 158 } 1779 sgmp-traps PROTOCOL-IDENTIFIER 1780 PARAMETERS { } 1781 ATTRIBUTES { } 1782 DESCRIPTION 1783 "Simple Gateway Monitoring Protocol Traps; (historical)." 1784 REFERENCE 1785 "RFC 1028 [RFC1028] defines the Simple Gateway Monitoring 1786 Protocol." 1787 ::= { udp 160 } 1789 -- snmp and snmptrap found in the Protocol-Independent section 1790 -- snmp 161/udp SNMP 1791 -- snmptrap 162/udp SNMPTRAP 1793 cmip-man PROTOCOL-IDENTIFIER 1794 PARAMETERS { } 1795 ATTRIBUTES { } 1796 DESCRIPTION 1797 "CMIP/TCP (CMOT) Manager; (historical)." 1798 REFERENCE 1799 "RFC 1095 [RFC1095] defines the Common Management Information 1800 Services and Protocol over TCP/IP." 1801 ::= { tcp 163, 1802 udp 163 } 1804 cmip-agent PROTOCOL-IDENTIFIER 1805 PARAMETERS { } 1806 ATTRIBUTES { } 1807 DESCRIPTION 1808 "CMIP/TCP (CMOT) Agent; (historical)." 1809 REFERENCE 1810 "RFC 1095 [RFC1095] defines the Common Management Information 1811 Services and Protocol over TCP/IP." 1812 ::= { tcp 164, 1813 udp 164 } 1815 xdmcp PROTOCOL-IDENTIFIER 1816 PARAMETERS { } 1817 ATTRIBUTES { } 1818 DESCRIPTION 1819 "X Display Manager Control Protocol" 1820 REFERENCE 1821 "X11 Consortium" 1822 ::= { udp 177 } 1824 bgp PROTOCOL-IDENTIFIER 1825 PARAMETERS { } 1826 ATTRIBUTES { } 1827 DESCRIPTION 1828 "Border Gateway Protocol" 1829 REFERENCE 1830 "RFC 1267 [RFC1267] defines version 3 of the Border Gateway 1831 Protocol." 1832 ::= { tcp 179 } 1834 remote-kis PROTOCOL-IDENTIFIER 1835 PARAMETERS { } 1836 ATTRIBUTES { } 1837 DESCRIPTION 1838 "Remote-Knowbot Information Service (KIS)" 1839 REFERENCE 1840 "RFC 1739 [RFC1739] describes the KNOWBOT Protocol." 1841 ::= { tcp 185, 1842 udp 185 } 1844 kis PROTOCOL-IDENTIFIER 1845 PARAMETERS { } 1846 ATTRIBUTES { } 1847 DESCRIPTION 1848 "Knowbot Information Service (KIS)" 1849 REFERENCE 1850 "RFC 1739 [RFC1739] describes the KNOWBOT Protocol." 1851 ::= { tcp 186, 1852 udp 186 } 1854 irc PROTOCOL-IDENTIFIER 1855 PARAMETERS { } 1856 ATTRIBUTES { } 1857 DESCRIPTION 1858 "Internet Relay Chat Protocol" 1859 REFERENCE 1860 "RFC 1459 [RFC1459] defines the Internet Relay Chat Protocol." 1861 ::= { tcp 194, 1862 udp 194 } 1864 smux PROTOCOL-IDENTIFIER 1865 PARAMETERS { } 1866 ATTRIBUTES { } 1867 DESCRIPTION 1868 "SMUX; SNMP MUX Protocol and MIB; (historical)." 1869 REFERENCE 1870 "RFC 1227 [RFC1227] defines the SMUX Protocol." 1871 ::= { tcp 199 } 1873 -- 1874 -- AppleTalk applications are defined in the AppleTalk Stack section 1875 -- 1876 -- at-rtmp 201/tcp AppleTalk Routing Maintenance 1877 -- at-rtmp 201/udp AppleTalk Routing Maintenance 1878 -- at-nbp 202/tcp AppleTalk Name Binding 1879 -- at-nbp 202/udp AppleTalk Name Binding 1880 -- at-3 203/tcp AppleTalk Unused 1881 -- at-3 203/udp AppleTalk Unused 1882 -- at-echo 204/tcp AppleTalk Echo 1883 -- at-echo 204/udp AppleTalk Echo 1884 -- at-5 205/tcp AppleTalk Unused 1885 -- at-5 205/udp AppleTalk Unused 1886 -- at-zis 206/tcp AppleTalk Zone Information 1887 -- at-zis 206/udp AppleTalk Zone Information 1888 -- at-7 207/tcp AppleTalk Unused 1889 -- at-7 207/udp AppleTalk Unused 1890 -- at-8 208/tcp AppleTalk Unused 1891 -- at-8 208/udp AppleTalk Unused 1893 z39-50 PROTOCOL-IDENTIFIER 1894 PARAMETERS { } 1895 ATTRIBUTES { } 1896 DESCRIPTION 1897 "ANSI Z39.50" 1898 REFERENCE 1899 "RFC 1729 [RFC1729] describes the Z39.50 Protocol." 1900 ::= { tcp 210 } 1902 ipx-tunnel PROTOCOL-IDENTIFIER 1903 PARAMETERS { } 1904 ATTRIBUTES { } 1905 DESCRIPTION 1906 "Tunneling IPX Traffic through IP Networks" 1907 REFERENCE 1908 "RFC 1234 [RFC1234] defines the IPX Tunnel Protocol." 1909 ::= { udp 213 } 1911 mpp PROTOCOL-IDENTIFIER 1912 PARAMETERS { } 1913 ATTRIBUTES { } 1914 DESCRIPTION 1915 "Netix Message Posting Protocol" 1916 REFERENCE 1917 "RFC 1204 [RFC1204] defines the Message Posting Protocol." 1918 ::= { tcp 218 } 1920 imap3 PROTOCOL-IDENTIFIER 1921 PARAMETERS { } 1922 ATTRIBUTES { } 1923 DESCRIPTION 1924 "Interactive Mail Access Protocol v3; (historical)." 1925 REFERENCE 1926 "RFC 1203 [RFC1203] defines version 3 of the Interactive Mail 1927 Access Protocol." 1928 ::= { tcp 220 } 1930 ldap PROTOCOL-IDENTIFIER 1931 PARAMETERS { } 1932 ATTRIBUTES { } 1933 DESCRIPTION 1934 "Lightweight Directory Access Protocol" 1935 REFERENCE 1936 "RFC 1777 [RFC1777] defines Lightweight Directory Access 1937 Protocol; RFC 1798 [RFC1798] defines Connection-less Lightweight 1938 X.500 Directory Access Protocol" 1939 ::= { tcp 389, -- RFC 1777 1940 udp 389 } -- RFC 1798 1942 mobileip-agent PROTOCOL-IDENTIFIER 1943 PARAMETERS { } 1944 ATTRIBUTES { } 1945 DESCRIPTION 1946 "IP Mobility Support" 1947 REFERENCE 1948 "RFC 2002 [RFC2002] defines the IP Mobility Support protocol." 1949 ::= { udp 434 } 1951 https PROTOCOL-IDENTIFIER 1952 PARAMETERS { } 1953 ATTRIBUTES { } 1954 DESCRIPTION 1955 "Secure HTTP; HTTP over TLS/SSL" 1956 REFERENCE 1957 "Netscape; http://home.netscape.com/eng/ssl3/" 1958 ::= { tcp 443 } 1960 smtps PROTOCOL-IDENTIFIER 1961 PARAMETERS { } 1962 ATTRIBUTES { } 1963 DESCRIPTION 1964 "SMTP protocol over TLS/SSL" 1965 REFERENCE 1966 "Netscape; http://home.netscape.com/eng/ssl3/" 1967 ::= { tcp 465 } 1969 isakmp PROTOCOL-IDENTIFIER 1970 PARAMETERS { } 1971 ATTRIBUTES { } 1972 DESCRIPTION 1973 "Internet Security Association and Key Management Protocol 1974 (ISAKMP)" 1975 REFERENCE 1976 "RFC 2408 [RFC2408]" 1977 ::= { udp 500 } 1979 login PROTOCOL-IDENTIFIER 1980 PARAMETERS { } 1981 ATTRIBUTES { } 1982 DESCRIPTION 1983 "BSD Rlogin; remote login a la telnet" 1984 REFERENCE 1985 "RFC 1282 [RFC1282] defines the BSD Rlogin Protocol." 1986 ::= { tcp 513 } 1988 syslog PROTOCOL-IDENTIFIER 1989 PARAMETERS { } 1990 ATTRIBUTES { } 1991 DESCRIPTION 1992 "syslog" 1993 REFERENCE 1994 "[RFC1700]" 1995 ::= { udp 514 } 1997 uucp PROTOCOL-IDENTIFIER 1998 PARAMETERS { } 1999 ATTRIBUTES { } 2000 DESCRIPTION 2001 "Unix-to-Unix copy protocol" 2002 REFERENCE 2003 "[RFC1700]" 2004 ::= { tcp 540 } 2006 doom PROTOCOL-IDENTIFIER 2007 PARAMETERS { } 2008 ATTRIBUTES { } 2009 DESCRIPTION 2010 "DOOM Game;" 2012 REFERENCE 2013 " Id Software" 2014 ::= { tcp 666 } 2016 radius PROTOCOL-IDENTIFIER 2017 PARAMETERS { } 2018 ATTRIBUTES { } 2019 DESCRIPTION 2020 "Remote Authentication Dial In User Service (RADIUS)" 2021 REFERENCE 2022 "RFC 2138 [RFC2138] defines the Radius protocol." 2023 ::= { udp 1812 } 2025 radiusacct PROTOCOL-IDENTIFIER 2026 PARAMETERS { } 2027 ATTRIBUTES { } 2028 DESCRIPTION 2029 "RADIUS Accounting Protocol" 2030 REFERENCE 2031 "RFC 2139 [RFC2139] defines the Radius Accounting protocol." 2032 ::= { udp 1813 } 2034 -- 2035 -- Portmapper Functions; Children of sunrpc 2036 -- 2038 portmapper PROTOCOL-IDENTIFIER 2039 PARAMETERS { } 2040 ATTRIBUTES { } 2041 DESCRIPTION 2042 "SUNRPC PORTMAPPER program. This is the SUNRPC program which is 2043 used to locate the UDP/TCP ports on which other SUNRPC programs 2044 can be found." 2045 REFERENCE 2046 "Appendix A of RFC 1057 [RFC1057] describes the portmapper 2047 operation." 2048 ::= { sunrpc 100000 } 2050 nfs PROTOCOL-IDENTIFIER 2051 PARAMETERS { } 2052 ATTRIBUTES { } 2053 DESCRIPTION 2054 "Sun Network File System (NFS);" 2055 DECODING 2056 "NFS is a SUNRPC program which may or may not use the port mapper 2057 SUNRPC program to connect clients and servers. In many cases the 2058 NFS server program runs over UDP/TCP port 2049, but an 2059 implementation is encouraged to perform further analysis before 2060 assuming that a packet to/from this port is a SUNRPC/NFS packet. 2061 Likewise an implementation is encouraged to track port mapper 2062 activity to spot cases where it is used to locate the SUNRPC/NFS 2063 program as this is more robust." 2064 REFERENCE 2065 "The NFS Version 3 Protocol Specification is defined in RFC 1813 2066 [RFC1813]." 2067 ::= { 2068 sunrpc 100003 -- [0.1.134.163] 2069 } 2071 xwin PROTOCOL-IDENTIFIER 2072 PARAMETERS { 2073 tracksSessions(1) 2074 } 2075 ATTRIBUTES { } 2076 DESCRIPTION 2077 "X Windows Protocol" 2078 DECODING 2079 "The X Windows Protocol when run over UDP/TCP normally runs over 2080 the well known port 6000. It can run over any port in the range 2081 6000 to 6063, however. If the tracksSessions(1) parameter bit is 2082 set the agent can and should detect such X Window sessions and 2083 report them as the X protocol." 2084 REFERENCE 2085 "The X Windows Protocol is defined by TBD" 2086 ::= { 2087 tcp 6000, 2088 udp 6000 2089 -- lat ? 2090 } 2092 6.1.2. Novell IPX Stack 2094 ipx PROTOCOL-IDENTIFIER 2095 PARAMETERS { } 2096 ATTRIBUTES { 2097 hasChildren(0), 2098 addressRecognitionCapable(1) 2099 } 2100 DESCRIPTION 2101 "Novell IPX" 2102 CHILDREN 2103 "Children of IPX are defined by the 8 bit packet type field. The 2104 value is encoded into an octet string as [ 0.0.0.a ], where 'a' 2105 is the single octet of the packet type field. 2107 Notice that in many implementations of IPX usage of the packet 2108 type field is inconsistent with the specification and 2109 implementations are encouraged to use other techniques to map 2110 inconsistent values to the correct value (which in these cases is 2111 typically the Packet Exchange Protocol). It is beyond the scope 2112 of this document to describe these techniques in more detail. 2114 Children of IPX are encoded as [ 0.0.0.a ], and named as 'ipx a' 2115 where a is the packet type value. The novell echo protocol is 2116 referred to as 'ipx nov-echo' OR 'ipx 2'." 2117 ADDRESS-FORMAT 2118 "4 bytes of Network number followed by the 6 bytes Host address 2119 each in network byte order." 2120 REFERENCE 2121 "The IPX protocol is defined by the Novell Corporation 2123 A complete description of IPX may be secured at the following 2124 address: 2125 Novell, Inc. 2126 122 East 1700 South 2127 P. O. Box 5900 2128 Provo, Utah 84601 USA 2129 800 526 5463 2130 Novell Part # 883-000780-001" 2131 ::= { 2132 ether2 0x8137, -- [0.0.129.55] 2133 snap 0x8137, -- [0.0.129.55] 2134 ianaAssigned 1, -- [0.0.0.1] (ipxOverRaw8023) 2135 llc 224, -- [0.0.0.224] 2136 802-1Q 0x8137, -- [0.0.129.55] 2137 802-1Q 0x020000e0, -- 1Q-LLC [2.0.0.224] 2138 802-1Q 0x05000001 -- 1Q-IANA [5.0.0.1] (ipxOverRaw8023) 2139 } 2141 nov-rip PROTOCOL-IDENTIFIER 2142 PARAMETERS { } 2143 ATTRIBUTES { } 2144 DESCRIPTION 2145 "Novell Routing Information Protocol" 2146 REFERENCE 2147 "Novell Corporation" 2148 ::= { 2149 ipx 0x01, -- when reached by IPX packet type 2150 nov-pep 0x0453 -- when reached by IPX socket number 2151 } 2153 nov-echo PROTOCOL-IDENTIFIER 2154 PARAMETERS { } 2155 ATTRIBUTES { } 2156 DESCRIPTION 2157 "Novell Echo Protocol" 2158 REFERENCE 2159 "Novell Corporation" 2160 ::= { ipx 0x02 } 2162 nov-error PROTOCOL-IDENTIFIER 2163 PARAMETERS { } 2164 ATTRIBUTES { } 2165 DESCRIPTION 2166 "Novell Error-handler Protocol" 2167 REFERENCE 2168 "Novell Corporation" 2169 ::= { ipx 0x03 } 2171 nov-pep PROTOCOL-IDENTIFIER 2172 PARAMETERS { } 2173 ATTRIBUTES { 2174 hasChildren(0) 2175 } 2176 DESCRIPTION 2177 "Novell Packet Exchange Protocol. This is really a null protocol 2178 layer as all IPX packets contain the relevant fields for this 2179 protocol. This protocol is defined so that socket-based decoding 2180 has a point of attachment in the decode tree while still allowing 2181 packet type based decoding also." 2182 CHILDREN 2183 "Children of PEP are defined by the 16 bit socket values. The 2184 value is encoded into an octet string as [ 0.0.a.b ], where 'a' 2185 and 'b' are the network byte order encodings of the MSB and LSB 2186 of the socket value. 2188 Each IPX/PEP packet contains two sockets, source and destination. 2189 How these are mapped onto the single well-known socket value used 2190 to identify its children is beyond the scope of this document." 2191 REFERENCE 2192 "Novell Corporation" 2193 ::= { 2194 -- ipx 0x00 ** Many third party IPX's use this value always 2195 ipx 0x04 -- Xerox assigned for PEP 2196 -- ipx 0x11 ** Novell use this for PEP packets, often 2197 } 2199 nov-spx PROTOCOL-IDENTIFIER 2200 PARAMETERS { } 2201 ATTRIBUTES { 2202 hasChildren(0) 2203 } 2204 DESCRIPTION 2205 "Novell Sequenced Packet Exchange Protocol. This protocol is an 2206 extension of IPX/PEP as it shares a common header." 2207 CHILDREN 2208 "Children of SPX are defined by the 16 bit socket values. The 2209 value is encoded into an octet string as [ 0.0.a.b ], where 'a' 2210 and 'b' are the network byte order encodings of the MSB and LSB 2211 of the socket value. 2213 Each IPX/SPX packet contains two sockets, source and destination. 2214 How these are mapped onto the single well-known socket value used 2215 to identify its children is beyond the scope of this document." 2216 REFERENCE 2217 "Novell Corporation" 2218 ::= { 2219 ipx 0x05 -- Xerox assigned for SPX 2220 } 2222 nov-sap PROTOCOL-IDENTIFIER 2223 PARAMETERS { 2224 tracksSessions(1) 2225 } 2226 ATTRIBUTES { 2227 hasChildren(0) 2228 } 2229 DESCRIPTION 2230 "Novell Service Advertising Protocol. This protocol binds 2231 applications on a particular host to an IPX/PEP or IPX/SPX socket 2232 number. Although it never truly acts as a transport protocol 2233 itself it is used to establish sessions between clients and 2234 servers and barring well-known sockets is the only reliable way 2235 to determine the protocol running over a given socket on a given 2236 machine." 2237 CHILDREN 2238 "Children of SAP are identified by a 16 bit service type. They 2239 are encoded as [ 0.0.a.b ], where 'a' is the MSB and 'b' is the 2240 LSB of the service type. 2242 Children of SAP are named as 'nov-sap a' where 'a' is the service 2243 type in hexadecimal notation. The novell NCP protocol is 2244 referred to as 'nov-sap ncp' OR 'nov-sap 0x0004'." 2245 DECODING 2246 "The first packet of any session for a SAP based application 2247 (almost all IPX/PEP and IPX/SPX based applications utilize SAP) 2248 is sent to the SAP server(s) to map the service type into a port 2249 number for the host(s) on which the SAP server(s) is(are) 2250 running. These initial packets are SAP packets and not 2251 application packets and must be decoded accordingly. 2253 Having established the mapping, clients will then send 2254 application packets to the newly discovered socket number. These 2255 must be decoded by 'remembering' the socket assignments 2256 transmitted in the SAP packets. 2258 In some cases the port mapping for a particular protocol is well 2259 known and SAP will always return the same socket number for that 2260 application. 2262 Such programs should still be declared as children of nov-sap as 2263 described under CHILDREN above. How an implementation detects a 2264 client which is bypassing the SAP server to contact a well-known 2265 application is beyond the scope of this document. 2267 The 'tracksSessions(1)' PARAMETER bit is used to indicate whether 2268 the probe can (and should) monitor nov-sap activity to correctly 2269 track SAP-based connections." 2270 REFERENCE 2271 "A list of SAP service types can be found at 2272 ftp://ftp.isi.edu/in-notes/iana/assignments/novell-sap- 2273 numbers" 2274 ::= { nov-pep 0x0452 } 2276 ncp PROTOCOL-IDENTIFIER 2277 PARAMETERS { 2278 tracksSessions(1) 2279 } 2280 ATTRIBUTES { 2281 hasChildren(0) 2282 } 2283 DESCRIPTION 2284 "Netware Core Protocol" 2285 CHILDREN 2286 "Children of NCP are identified by the 8 bit command type field. 2287 They are encoded as [ 0.0.0.a ] where 'a' is the command type 2288 value. 2290 Children of NCP are named as 'ncp a' where 'a' is the command 2291 type in decimal notation. The NDS sub-protocol is referred to as 2292 'ncp nds' OR 'ncp 104'." 2293 DECODING 2294 "Only the NCP request frames carry the command type field. How 2295 the implementation infers the command type of a response frame is 2296 an implementation specific matter and beyond the scope of this 2297 document. 2299 The tracksSessions(1) PARAMETERS bit indicates whether the probe 2300 can (and should) perform command type inference." 2301 REFERENCE 2302 "Novell Corporation" 2303 ::= { nov-sap 0x0004, 2304 nov-pep 0x0451 } 2306 nds PROTOCOL-IDENTIFIER 2307 PARAMETERS { } 2308 ATTRIBUTES { } 2309 DESCRIPTION 2310 "The Netware Directory Services sub-protocol." 2311 REFERENCE 2312 "Novell Corporation" 2313 ::= { ncp 104 } 2315 nov-diag PROTOCOL-IDENTIFIER 2316 PARAMETERS { } 2317 ATTRIBUTES { } 2318 DESCRIPTION 2319 "Novell's diagnostic Protocol" 2320 REFERENCE 2321 "Novell Corporation" 2322 ::= { 2323 nov-sap 0x0017, -- [ed., this is the right one] 2324 nov-pep 0x0456 2326 } 2328 nov-sec PROTOCOL-IDENTIFIER 2329 PARAMETERS { } 2330 ATTRIBUTES { } 2331 DESCRIPTION 2332 "Novell security - serialization - copy protection protocol." 2333 REFERENCE 2334 "Novell Corporation" 2335 ::= { nov-pep 0x0457 } 2337 nov-watchdog PROTOCOL-IDENTIFIER 2338 PARAMETERS { } 2339 ATTRIBUTES { } 2340 DESCRIPTION 2341 "Novell watchdog protocol." 2342 REFERENCE 2343 "Novell Corporation" 2344 ::= { nov-pep 0x4004 } 2346 nov-bcast PROTOCOL-IDENTIFIER 2347 PARAMETERS { } 2348 ATTRIBUTES { } 2349 DESCRIPTION 2350 "Novell broadcast protocol." 2351 REFERENCE 2352 "Novell Corporation" 2353 ::= { nov-pep 0x4005 } 2355 6.1.3. The XEROX Protocol Stack 2357 idp PROTOCOL-IDENTIFIER 2358 PARAMETERS { } 2359 ATTRIBUTES { 2360 hasChildren(0), 2361 addressRecognitionCapable(1) 2362 } 2363 DESCRIPTION 2364 "Xerox IDP" 2365 CHILDREN 2366 "Children of IDP are defined by the 8 bit value of the Packet 2367 type field. The value is encoded into an octet string as [ 2368 0.0.0.a ], where 'a' is the value of the packet type field in 2369 network byte order. 2371 Children of IDP are encoded as [ 0.0.0.a ], and named as 'idp a' 2372 where a is the packet type value. The XNS SPP protocol is 2373 referred to as 'idp xns-spp' OR 'idp 2'." 2374 ADDRESS-FORMAT 2375 "4 bytes of Network number followed by the 6 bytes Host address 2376 each in network byte order." 2377 REFERENCE 2378 "Xerox Corporation, Document XNSS 028112, 1981" 2379 ::= { 2380 ether2 0x600, -- [ 0.0.6.0 ] 2381 snap 0x600, 2382 802-1Q 0x600 -- [ 0.0.6.0 ] 2383 } 2385 xns-rip PROTOCOL-IDENTIFIER 2386 PARAMETERS { } 2387 ATTRIBUTES { } 2388 DESCRIPTION 2389 "Routing Information Protocol." 2390 REFERENCE 2391 "Xerox Corporation" 2392 ::= { idp 1 } 2394 xns-echo PROTOCOL-IDENTIFIER 2395 PARAMETERS { } 2396 ATTRIBUTES { } 2397 DESCRIPTION 2398 "XNS echo protocol." 2399 REFERENCE 2400 "Xerox Corporation" 2401 ::= { idp 2 } 2403 xns-error PROTOCOL-IDENTIFIER 2404 PARAMETERS { } 2405 ATTRIBUTES { } 2406 DESCRIPTION 2407 "XNS error-handler protocol." 2408 REFERENCE 2409 "Xerox Corporation" 2410 ::= { idp 3 } 2412 xns-pep PROTOCOL-IDENTIFIER 2413 PARAMETERS { } 2414 ATTRIBUTES { 2415 hasChildren(0) 2417 } 2418 DESCRIPTION 2419 "XNS Packet Exchange Protocol." 2420 CHILDREN 2421 "Children of PEP are defined by the 16 bit socket values. The 2422 value is encoded into an octet string as [ 0.0.a.b ], where 'a' 2423 and 'b' are the network byte order encodings of the MSB and LSB 2424 of the socket value. 2426 Each XNS/PEP packet contains two sockets, source and destination. 2427 How these are mapped onto the single well-known socket value used 2428 to identify its children is beyond the scope of this document." 2429 REFERENCE 2430 "Xerox Corporation" 2431 ::= { idp 4 } 2433 xns-spp PROTOCOL-IDENTIFIER 2434 PARAMETERS { } 2435 ATTRIBUTES { 2436 hasChildren(0) 2437 } 2438 DESCRIPTION 2439 "Sequenced Packet Protocol." 2440 CHILDREN 2441 "Children of SPP are defined by the 16 bit socket values. The 2442 value is encoded into an octet string as [ 0.0.a.b ], where 'a' 2443 and 'b' are the network byte order encodings of the MSB and LSB 2444 of the socket value. 2446 Each XNS/SPP packet contains two sockets, source and destination. 2447 How these are mapped onto the single well-known socket value used 2448 to identify its children is beyond the scope of this document." 2449 REFERENCE 2450 "Xerox Corporation" 2451 ::= { idp 5 } 2453 6.1.4. AppleTalk Protocol Stack 2455 apple-oui PROTOCOL-IDENTIFIER 2456 PARAMETERS { } 2457 ATTRIBUTES { } 2458 DESCRIPTION 2459 "Pseudo-protocol which binds Apple's protocols to vsnap." 2460 CHILDREN 2461 "Children of apple-oui are identified by the ether2 type field 2462 value that the child uses when encapsulated in ether2. The value 2463 is encoded into an octet string as [ 0.0.a.b ], where 'a' and 'b' 2464 are the MSB and LSB of the 16-bit ether type value in network 2465 byte order." 2466 REFERENCE 2467 "AppleTalk Phase 2 Protocol Specification, document ADPA 2468 #C0144LL/A." 2469 ::= { 2470 vsnap 0x080007, -- [ 0.8.0.7 ] 2471 802-1Q 0x04080007 -- 1Q-VSNAP [ 4.8.0.7 ] 2472 } 2474 aarp PROTOCOL-IDENTIFIER 2475 PARAMETERS { } 2476 ATTRIBUTES { } 2477 DESCRIPTION 2478 "AppleTalk Address Resolution Protocol." 2479 REFERENCE 2480 "AppleTalk Phase 2 Protocol Specification, document ADPA 2481 #C0144LL/A." 2482 ::= { 2483 ether2 0x80f3, -- [ 0.0.128.243 ] 2484 snap 0x80f3, 2485 apple-oui 0x80f3, 2486 802-1Q 0x80f3 -- [ 0.0.128.243 ] 2487 } 2489 -- Should we call this alap (as in ELAP and TLAP?) 2490 -- Or perhaps DDP? 2492 atalk PROTOCOL-IDENTIFIER 2493 PARAMETERS { } 2494 ATTRIBUTES { 2495 hasChildren(0), 2496 addressRecognitionCapable(1) 2497 } 2498 DESCRIPTION 2499 "AppleTalk Protocol." 2500 CHILDREN 2501 "Children of ATALK are defined by the 8 bit value of the DDP type 2502 field. The value is encoded into an octet string as [ 0.0.0.a ], 2503 where 'a' is the value of the DDP type field in network byte 2504 order." 2505 ADDRESS-FORMAT 2506 "2 bytes of Network number followed by 1 byte of node id each in 2507 network byte order." 2508 REFERENCE 2509 "AppleTalk Phase 2 Protocol Specification, document ADPA 2510 #C0144LL/A." 2511 ::= { 2512 ether2 0x809b, -- [ 0.0.128.155 ] 2513 apple-oui 0x809b, 2514 802-1Q 0x809b -- [ 0.0.128.155 ] 2515 } 2517 rtmp PROTOCOL-IDENTIFIER 2518 PARAMETERS { } 2519 ATTRIBUTES { } 2520 DESCRIPTION 2521 "AppleTalk Routing Table Maintenance Protocol." 2522 REFERENCE 2523 "Apple Computer" 2524 ::= { 2525 atalk 0x01, -- responses 2526 atalk 0x05 -- requests 2527 } 2529 aep PROTOCOL-IDENTIFIER 2530 PARAMETERS { } 2531 ATTRIBUTES { } 2532 DESCRIPTION 2533 "AppleTalk Echo Protocol." 2534 REFERENCE 2535 "Apple Computer" 2536 ::= { atalk 0x04 } 2538 nbp PROTOCOL-IDENTIFIER 2539 PARAMETERS { } 2540 ATTRIBUTES { } 2541 DESCRIPTION 2542 "AppleTalk Name Binding Protocol." 2543 DECODING 2544 "In order to correctly identify the application protocol running 2545 over atp NBP packets must be analyzed. The mechanism by which 2546 this is achieved is beyond the scope of this document." 2547 REFERENCE 2548 "Apple Computer" 2549 ::= { atalk 0x02 } 2551 zip PROTOCOL-IDENTIFIER 2552 PARAMETERS { } 2553 ATTRIBUTES { } 2554 DESCRIPTION 2555 "AppleTalk Zone Information Protocol." 2556 REFERENCE 2557 "Apple Computer" 2558 ::= { 2559 atalk 0x06, 2560 atp 3 2561 } 2563 atp PROTOCOL-IDENTIFIER 2564 PARAMETERS { 2565 tracksSessions(1) 2566 } 2567 ATTRIBUTES { 2568 hasChildren(0) 2569 } 2570 DESCRIPTION 2571 "AppleTalk Transaction Protocol." 2572 CHILDREN 2573 "Children of atp are identified by the following (32 bit) 2574 enumeration: 2575 1 asp (AppleTalk Session Protocol) 2576 2 pap (Printer Access Protocol) 2577 3 zip (Zone Information Protocol) 2578 Children of atp are encoded as [ a.b.c.d ] where 'a', 'b', 'c' 2579 and 'd' are the four octets of the enumerated value in network 2580 order (i.e. 'a' is the MSB and 'd' is the LSB). 2582 The ZIP protocol is referred to as 'atp zip' OR 'atp 3'." 2583 DECODING 2584 "An implementation is encouraged to examine both the socket 2585 fields in the associated DDP header as well as the contents of 2586 prior NBP packets in order to determine which (if any) child is 2587 present. A full description of this algorithm is beyond the 2588 scope of this document. The tracksSessions(1) PARAMETER 2589 indicates whether the probe can (and should) perform this 2590 analysis." 2591 REFERENCE 2592 "Apple Computer" 2593 ::= { atalk 0x03 } 2595 adsp PROTOCOL-IDENTIFIER 2596 PARAMETERS { 2597 tracksSessions(1) 2598 } 2599 ATTRIBUTES { 2600 hasChildren(0) 2601 } 2602 DESCRIPTION 2603 "AppleTalk Data Stream Protocol." 2604 CHILDREN 2605 "Children of adsp are identified by enumeration. At this time 2606 none are known." 2607 DECODING 2608 "An implementation is encouraged to examine the socket numbers in 2609 the associated DDP header as well as the contents of prior NBP 2610 packets in order to determine which (if any) child of ADSP is 2611 present. 2613 The mechanism by which this is achieved is beyond the scope of 2614 this document. 2616 The tracksSessions(1) PARAMETER indicates whether the probe can 2617 (and should) perform this analysis." 2618 REFERENCE 2619 "Apple Computer" 2620 ::= { atalk 0x07 } 2622 asp PROTOCOL-IDENTIFIER 2623 PARAMETERS { } 2624 ATTRIBUTES { 2625 hasChildren(0) 2626 } 2627 DESCRIPTION 2628 "AppleTalk Session Protocol." 2629 CHILDREN 2630 "Children of asp are identified by the following (32 bit) 2631 enumeration: 2632 1 afp (AppleTalk Filing Protocol) 2633 Children of asp are encoded as [ a.b.c.d ] where 'a', 'b', 'c' 2634 and 'd' are the four octets of the enumerated value in network 2635 order (i.e. 'a' is the MSB and 'd' is the LSB). 2637 The AFP protocol is referred to as 'asp afp' OR 'asp 1'." 2638 DECODING 2639 "ASP is a helper layer to assist in building client/server 2640 protocols. It cooperates with ATP to achieve this; the 2641 mechanisms used when decoding ATP apply equally here (i.e. 2642 checking DDP socket numbers and tracking NBP packets). 2644 Hence the tracksSessions(1) PARAMETER of atp applies to this 2645 protocol also." 2646 REFERENCE 2647 "Apple Computer" 2648 ::= { atp 1 } 2650 afp PROTOCOL-IDENTIFIER 2651 PARAMETERS { } 2652 ATTRIBUTES { } 2653 DESCRIPTION 2654 "AppleTalk Filing Protocol." 2655 REFERENCE 2656 "Apple Computer" 2657 ::= { asp 1 } 2659 pap PROTOCOL-IDENTIFIER 2660 PARAMETERS { } 2661 ATTRIBUTES { } 2662 DESCRIPTION 2663 "AppleTalk Printer Access Protocol." 2664 REFERENCE 2665 "Apple Computer" 2666 ::= { atp 2 } 2668 6.1.5. Banyon Vines Protocol Stack 2670 vtr PROTOCOL-IDENTIFIER 2671 PARAMETERS { } 2672 ATTRIBUTES { 2673 hasChildren(0) 2674 } 2675 DESCRIPTION 2676 "Banyan Vines Token Ring Protocol Header." 2677 CHILDREN 2678 "Children of vines-tr are identified by the 8 bit packet type 2679 field. Children are encoded as [ 0.0.0.a ] where 'a' is the 2680 packet type value. 2682 The vines-ip protocol is referred to as 'vines-tr vip' OR 'vines- 2683 tr 0xba'." 2684 REFERENCE 2685 "See vip." 2686 ::= { 2687 llc 0xBC, -- declared as any LLC, but really TR only. 2688 802-1Q 0x020000BC -- 1Q-LLC [2.0.0.188] 2689 } 2691 vecho PROTOCOL-IDENTIFIER 2692 PARAMETERS { } 2693 ATTRIBUTES { } 2694 DESCRIPTION 2695 "Banyan Vines data link level echo protocol." 2696 REFERENCE 2697 "See vip." 2698 ::= { 2699 ether2 0x0BAF, -- [0.0.11.175] 2700 snap 0x0BAF, 2701 -- vfrp 0x0BAF, 2702 vtr 0xBB, -- [ed. yuck!] 2703 802-1Q 0x0BAF -- [0.0.11.175] 2704 } 2706 vip PROTOCOL-IDENTIFIER 2707 PARAMETERS { } 2708 ATTRIBUTES { 2709 hasChildren(0), 2710 addressRecognitionCapable(1) 2711 } 2712 DESCRIPTION 2713 "Banyan Vines Internet Protocol." 2714 CHILDREN 2715 "Children of vip are selected by the one-byte 'protocol type' 2716 field located at offset 5 in the vip header. The value is 2717 encoded as [ 0.0.0.a ], where a is the 'protocol type.' For 2718 example, a protocolDirId fragment of: 2720 0.0.0.1.0.0.11.173.0.0.0.1 2722 identifies an encapsulation of vipc (ether2.vip.vipc)." 2723 ADDRESS-FORMAT 2724 "vip packets have 6-byte source and destination addresses. The 2725 destination address is located at offset 6 in the vip header, and 2726 the source address at offset 12. These are encoded in network 2727 byte order." 2728 REFERENCE 2729 "Vines Protocol Definition - part# 092093-001, order# 003673 2730 BANYAN, 2731 120 Flanders Road, 2732 Westboro, MA 01581 USA" 2733 ::= { 2734 ether2 0x0BAD, 2735 snap 0x0BAD, 2736 -- vfrp 0x0BAD, 2737 vtr 0xBA, -- [ed. yuck!] 2738 802-1Q 0x0BAD -- [0.0.11.173] 2739 } 2741 varp PROTOCOL-IDENTIFIER 2742 PARAMETERS { } 2743 ATTRIBUTES { } 2744 DESCRIPTION 2745 "Banyan Vines Address Resolution Protocol." 2746 REFERENCE 2747 "BANYAN" 2748 ::= { vip 0x04 } 2750 vipc PROTOCOL-IDENTIFIER 2751 PARAMETERS { } 2752 ATTRIBUTES { 2753 hasChildren(0) 2754 } 2755 DESCRIPTION 2756 "Banyan Vines Interprocess Communications Protocol." 2757 CHILDREN 2758 "Children of Vines IPC are identified by the packet type field at 2759 offset 4 in the vipc header. 2761 These are encoded as [ 0.0.0.a ] where 'a' is the packet type 2762 value. Children of vipc are defined as 'vipc a' where 'a' is the 2763 packet type value in hexadecimal notation. 2765 The Vines Reliable Data Transport protocol is referred to as 2766 'vipc vipc-rdp' OR 'vipc 0x01'." 2767 DECODING 2768 "Children of vipc are deemed to start at the first byte after the 2769 packet type field (i.e. at offset 5 in the vipc header)." 2770 REFERENCE 2771 "BANYAN" 2772 ::= { vip 0x01 } 2774 -- Banyan treats vipc, vipc-dgp and vipc-rdp as one protocol, IPC. 2776 -- Vines IPC really comes in two flavours. The first is used to 2777 -- send unreliable datagrams (vipc packet type 0x00). The second is used 2778 -- to send reliable datagrams (vipc packet type 0x01), 2779 -- consisting of up to four actual packets. 2780 -- In order to distinguish between these we need two 'virtual' protocols 2781 -- to identify which is which. 2783 vipc-dgp PROTOCOL-IDENTIFIER 2784 PARAMETERS { } 2785 ATTRIBUTES { 2786 hasChildren(0) 2787 } 2788 DESCRIPTION 2789 "Vines Unreliable Datagram Protocol." 2790 CHILDREN 2791 "Children of vipc-dgp are identified by the 16 bit port numbers 2792 contained in the vipc (this protocol's parent protocol) header. 2794 These are encoded as [ 0.0.a.b ] where 'a' is the MSB and 'b' is 2795 the MSB of the port number in network byte order. 2797 Children of vipc-dgp are defined as 'vipc-dgp a' where 'a' is the 2798 port number in hexadecimal notation. 2800 The StreetTalk protocol running over vipc-dgp would be referred 2801 to as 'vipc-dgp streettalk' OR 'vipc-dgp 0x000F'. 2803 The mechanism by which an implementation selects which of the 2804 source and destination ports to use in determining which child 2805 protocol is present is implementation specific and beyond the 2806 scope of this document." 2807 DECODING 2808 "Children of vipc-dgp are deemed to start after the single 2809 padding byte found in the vipc header. In the case of vipc-dgp 2810 the vipc header is a so called 'short' header, total length 6 2811 bytes (including the final padding byte)." 2812 REFERENCE 2813 "BANYAN" 2814 ::= { vipc 0x00 } 2816 vipc-rdp PROTOCOL-IDENTIFIER 2817 PARAMETERS { 2818 countsFragments(0) 2819 } 2820 ATTRIBUTES { 2821 hasChildren(0) 2822 } 2823 DESCRIPTION 2824 "Vines Reliable Datagram Protocol." 2825 CHILDREN 2826 "Children of vipc-rdp are identified by the 16 bit port numbers 2827 contained in the vipc (this protocol's parent protocol) header. 2829 These are encoded as [ 0.0.a.b ] where 'a' is the MSB and 'b' is 2830 the MSB of the port number in network byte order. 2832 Children of vipc-dgp are defined as 'vipc-rdp a' where 'a' is the 2833 port number in hexadecimal notation. 2835 The StreetTalk protocol running over vipc-rdp would be referred 2836 to as 'vipc-rdp streettalk' OR 'vipc-rdp 0x000F'. 2838 The mechanism by which an implementation selects which of the 2839 source and destination ports to use in determining which child 2840 protocol is present is implementation specific and beyond the 2841 scope of this document." 2842 DECODING 2843 "Children of vipc-rdp are deemed to start after the error/length 2844 field at the end of the vipc header. For vipc-rdp the vipc 2845 header is a so called 'long' header, total 16 bytes (including 2846 the final error/length field). 2848 vipc-rdp includes a high level fragmentation scheme which allows 2849 up to four vipc packets to be sent as a single atomic PDU. The 2850 countsFragments(0) PARAMETERS bit indicates whether the probe can 2851 (and should) identify the child protocol in all fragments or only 2852 the leading one." 2853 REFERENCE 2854 "BANYAN" 2855 ::= { vipc 0x01 } 2857 vspp PROTOCOL-IDENTIFIER 2858 PARAMETERS { } 2859 ATTRIBUTES { 2860 hasChildren(0) 2861 } 2862 DESCRIPTION 2863 "Banyan Vines Sequenced Packet Protocol." 2864 CHILDREN 2865 "Children of vspp are identified by the 16 bit port numbers 2866 contained in the vspp header. 2868 These are encoded as [ 0.0.a.b ] where 'a' is the MSB and 'b' is 2869 the MSB of the port number in network byte order. 2871 Children of vspp are defined as 'vspp a' where 'a' is the port 2872 number in hexadecimal notation. 2874 The StreetTalk protocol running over vspp would be referred to as 2875 'vspp streettalk' OR 'vspp 0x000F'. 2877 The mechanism by which an implementation selects which of the 2878 source and destination ports to use in determining which child 2879 protocol is present is implementation specific and beyond the 2880 scope of this document." 2881 DECODING 2882 "The implementation must ensure only those vspp packets which 2883 contain application data are decoded and passed on to children. 2884 Although it is suggested that the packet type and control fields 2885 should be used to determine this fact it is beyond the scope of 2886 this document to fully define the algorithm used." 2887 REFERENCE 2888 "BANYAN" 2889 ::= { vip 0x02 } 2891 vrtp PROTOCOL-IDENTIFIER 2892 PARAMETERS { } 2893 ATTRIBUTES { } 2894 DESCRIPTION 2895 "Banyan Vines Routing Update Protocol." 2896 REFERENCE 2897 "BANYAN" 2898 ::= { vip 0x05 } 2900 vicp PROTOCOL-IDENTIFIER 2901 PARAMETERS { } 2902 ATTRIBUTES { } 2903 DESCRIPTION 2904 "Banyan Vines Internet Control Protocol." 2905 REFERENCE 2906 "BANYAN" 2907 ::= { vip 0x06 } 2909 -- [ed. - We have two choices how we do vines apps. 2911 -- (1) The SUNRPC portmapper model. 2912 -- This has to be the preferred way to define all NetRPC based programs, 2913 -- i.e. by NetRPC program number. 2914 -- (2) Really ignore NetRPC as there is no 2915 -- good way to include it. Instead define NetRPC protocols as children 2916 -- of vipc-rdp by port number. Works for well-known ones but dynamic 2917 -- port numbers are used and NetRPC has a way of propagating these 2918 -- (StreetTalk??). 2920 -- So, if there is a portmapper-like program with a well known port number 2921 -- we should define it as a child of vipc-rdp (and vipc-dgp I suspect) and 2922 -- then declare all NetRPC based applications as children of this node by 2923 -- program number. Use tracksSessions on the port mapper node to show 2924 -- that you need to do this in order to follow the RPC sessions.] 2926 6.1.6. The DECNet Protocol Stack 2928 dec PROTOCOL-IDENTIFIER 2929 PARAMETERS { } 2930 ATTRIBUTES { } 2931 DESCRIPTION 2932 "DEC" 2933 REFERENCE 2934 "Digital Corporation" 2935 ::= { 2936 ether2 0x6000, 2937 802-1Q 0x6000 -- [0.0.96.0] 2938 } 2940 lat PROTOCOL-IDENTIFIER 2941 PARAMETERS { } 2942 ATTRIBUTES { } -- Should have children but I don't know how. 2943 DESCRIPTION 2944 "DEC Local Area Transport Protocol." 2945 REFERENCE 2946 "Digital Corporation" 2947 ::= { 2948 ether2 0x6004, 2949 802-1Q 0x6004 -- [0.0.96.4] 2950 } 2952 mop PROTOCOL-IDENTIFIER 2953 PARAMETERS { } 2954 ATTRIBUTES { } 2955 DESCRIPTION 2956 "DEC Maintenance Operations Protocol." 2957 REFERENCE 2958 "Digital Corporation" 2959 ::= { 2960 ether2 0x6001, -- mop dump/load 2961 ether2 0x6002, -- mop remote console 2962 802-1Q 0x6001, -- [0.0.96.1] VLAN + mop dump/load 2963 802-1Q 0x6002 -- [0.0.96.2] VLAN + mop remote console 2964 } 2966 dec-diag PROTOCOL-IDENTIFIER 2967 PARAMETERS { } 2968 ATTRIBUTES { } 2969 DESCRIPTION 2970 "DEC Diagnostic Protocol." 2971 REFERENCE 2972 "Digital Corporation" 2973 ::= { 2974 ether2 0x6005, 2975 802-1Q 0x6005 -- [0.0.96.5] 2976 } 2978 lavc PROTOCOL-IDENTIFIER 2979 PARAMETERS { } 2980 ATTRIBUTES { } 2981 DESCRIPTION 2982 "DEC Local Area VAX Cluster Protocol." 2983 REFERENCE 2984 "Digital Corporation" 2985 ::= { 2986 ether2 0x6007, 2987 802-1Q 0x6007 -- [0.0.96.7] 2988 } 2990 drp PROTOCOL-IDENTIFIER 2991 PARAMETERS { 2992 countsFragments(1) 2993 } 2994 ATTRIBUTES { 2995 hasChildren(0), 2996 addressRecognitionCapable(1) 2997 } 2998 DESCRIPTION 2999 "DEC Routing Protocol." 3001 CHILDREN 3002 "There is only one child of DRP, NSP. This is encoded as [ 3003 0.0.0.1 ]." 3004 ADDRESS-FORMAT 3005 "There are three address formats used in DRP packets, 2-byte 3006 (short data packet and all control except ethernet endnode & 3007 router hello messages), 6-byte (ethernet router & endnode hello 3008 messages) and 8-byte (long data packet). All of these contain 3009 the 2-byte format address in the last 2 bytes with the remaining 3010 bytes being unimportant for the purposes of system 3011 identification. It is beyond the scope of this document to 3012 define the algorithms used to identify packet types and hence 3013 address formats. 3015 The 2-byte address format is the concatenation of a 6-bit area 3016 and a 10-bit node number. In all cases this is placed in little 3017 endian format (i.e. LSB, MSB). The probe, however, will return 3018 them in network order (MSB, LSB). Regardless of the address 3019 format in the packet, the probe will always use the 2-byte 3020 format. 3022 For example area=13 (001101) and node=311 (0100110111) gives: 3023 0011 0101 0011 0111 = 0x3537 in network order (the order the 3024 probe should return the address in). 3026 In packets this same value would appear as (hex): 3028 2-byte 37 35 3029 6-byte AA 00 04 00 37 35 3030 8-byte 00 00 AA 00 04 00 37 35 3032 Notice that the AA 00 04 00 prefix is defined in the 3033 specification but is unimportant and should not be parsed. 3035 Notice that control messages only have a source address in the 3036 header and so they can never be added into the conversation based 3037 tables." 3038 DECODING 3039 "NSP runs over DRP data packets; all other packet types are DRP 3040 control packets of one sort or another and do not carry any 3041 higher layer protocol. 3043 NSP packets are deemed to start at the beginning of the DRP data 3044 area. 3046 Data packets may be fragmented over multiple DRP data packets. 3047 The countsFragments(1) parameter indicates whether a probe can 3048 (and should) attribute non-leading fragments to the child 3049 protocol (above NSP in this case) or not. 3051 Recognition of DRP data packets and fragments is beyond the scope 3052 of this document." 3053 REFERENCE 3054 "DECnet Digital Network Architecture 3055 Phase IV 3056 Routing Layer Functional Specification 3057 Order# AA-X435A-TK 3058 Digital Equipment Corporation, Maynard, Massachusetts, USA" 3059 ::= { 3060 ether2 0x6003, 3061 snap 0x6003, 3062 802-1Q 0x6003 -- [0.0.96.3] 3063 } 3065 nsp PROTOCOL-IDENTIFIER 3066 PARAMETERS { 3067 tracksSessions(1) 3068 } 3069 ATTRIBUTES { 3070 hasChildren(0) 3071 } 3072 DESCRIPTION 3073 "DEC Network Services Protocol." 3074 CHILDREN 3075 "Children of NSP are identified by the SCP 8-bit object type. 3076 Notice that the object type is included only in the session 3077 establishment messages (connect initiate, retransmitted connect 3078 initiate). 3080 Children of NSP are encoded [ 0.0.0.a ] where 'a' is the SCP 3081 object type. Children of NSP are named as 'nsp' followed by the 3082 SCP object type in decimal. CTERM is referred to as 'nsp cterm' 3083 OR 'nsp 42'." 3084 DECODING 3085 "An implementation is encouraged to examine SCP headers included 3086 in NSP control messages in order to determine which child 3087 protocol is present over a given session. It is beyond the scope 3088 of this document to define the algorithm used to do this. 3090 The tracksSessions(1) flag indicates whether the probe can (and 3091 should) perform this analysis." 3092 REFERENCE 3093 "DECnet Digital Network Architecture 3094 Phase IV 3095 NSP Functional Specification 3096 Order# AA-X439A-TK 3097 Digital Equipment Corporation, Maynard, Massachusetts, USA" 3098 ::= { drp 1 } 3100 dap-v1 PROTOCOL-IDENTIFIER 3101 PARAMETERS { } 3102 ATTRIBUTES { } 3103 DESCRIPTION 3104 "DEC Data Access Protocol version 1." 3105 REFERENCE 3106 "Digital Corporation" 3107 ::= { nsp 1 } 3109 dap-v4 PROTOCOL-IDENTIFIER 3110 PARAMETERS { } 3111 ATTRIBUTES { } 3112 DESCRIPTION 3113 "DEC Data Access Protocol versions 4 and above." 3114 REFERENCE 3115 "Digital Corporation" 3116 ::= { nsp 17 } 3118 nice PROTOCOL-IDENTIFIER 3119 PARAMETERS { } 3120 ATTRIBUTES { } 3121 DESCRIPTION 3122 "DEC Network Information and Control Exchange protocol." 3123 REFERENCE 3124 "Digital Corporation" 3125 ::= { nsp 19 } 3127 dec-loop PROTOCOL-IDENTIFIER 3128 PARAMETERS { } 3129 ATTRIBUTES { } 3130 DESCRIPTION 3131 "DEC Loopback Protocol." 3132 REFERENCE 3133 "Digital Corporation" 3134 ::= { nsp 25 } 3136 dec-event PROTOCOL-IDENTIFIER 3137 PARAMETERS { } 3138 ATTRIBUTES { } 3139 DESCRIPTION 3140 "DEC Event Protocol." 3141 REFERENCE 3142 "Digital Corporation" 3143 ::= { nsp 26 } 3145 cterm PROTOCOL-IDENTIFIER 3146 PARAMETERS { } 3147 ATTRIBUTES { } 3148 DESCRIPTION 3149 "DEC CTERM Protocol." 3150 REFERENCE 3151 "Digital Corporation" 3152 ::= { nsp 42 } 3154 6.1.7. The IBM SNA Protocol Stack. 3156 sna-th PROTOCOL-IDENTIFIER 3157 PARAMETERS { } 3158 ATTRIBUTES { } 3159 -- [ed. - clearly this really does have children, but I have 3160 -- no idea what applications are at the top, so is it 3161 -- worth expanding the hierarchy?] 3162 DESCRIPTION 3163 "IBM's SNA TH protocol." 3164 REFERENCE 3165 "IBM Systems Network Architecture 3166 Format and Protocol 3167 Reference Manual: Architectural Logic 3169 SC30-3112-2 3171 IBM System Communications Division, 3172 Publications Development, 3173 Department E02, 3174 PO Box 12195, 3175 Research Triangle Park, 3176 North Carolina 27709." 3177 ::= { 3178 llc 0x04, -- [0.0.0.4] 3179 llc 0x08, -- [0.0.0.8] 3180 llc 0x0c, -- [0.0.0.12] 3181 ether2 0x80d5, -- [0.0.128.213] 3182 802-1Q 0x02000004, -- 1Q-LLC [2.0.0.4] 3183 802-1Q 0x02000008, -- 1Q-LLC [2.0.0.8] 3184 802-1Q 0x0200000c, -- 1Q-LLC [2.0.0.12] 3185 802-1Q 0x80d5 -- [0.0.128.213] 3186 } 3188 6.1.8. The NetBEUI/NetBIOS Family 3190 -- CHILDREN OF NETBIOS 3191 -- The NetBIOS/NetBEUI functions are implemented over a wide variety of 3192 -- transports. Despite varying implementations they all share two 3193 -- features. First, all sessions are established by connecting to 3194 -- locally named services. Second, all sessions transport application 3195 -- between the client and the named service. In all cases the 3196 -- identification of the application protocol carried within the data 3197 -- packets is beyond the scope of this document.] 3198 -- 3199 -- Children of NetBIOS/NetBEUI are identified by the following (32 bit) 3200 -- enumeration 3201 -- 3202 -- 1 smb (Microsoft's Server Message Block Protocol) 3203 -- 2 notes (Lotus' Notes Protocol) 3204 -- 3 cc-mail (Lotus' CC Mail Protocol) 3205 -- 3206 -- Children of NetBIOS/NetBEUI are encoded as [ a.b.c.d ] where 'a', 'b', 3207 -- 'c' and 'd' are the four octets of the enumerated value in network 3208 -- order (i.e. 'a' is the MSB and 'd' is the LSB). 3209 -- 3210 -- For example notes over NetBEUI is declared as 3211 -- 'notes ::= { netbeui 2 }' 3212 -- but is referred to as 3213 -- 'netbeui notes' OR 'netbeui 2'. 3215 netbeui PROTOCOL-IDENTIFIER 3216 PARAMETERS { 3217 tracksSessions(1) 3218 } 3219 ATTRIBUTES { 3220 hasChildren(0) 3221 } 3222 DESCRIPTION 3223 "Lan Manager NetBEUI protocol." 3225 CHILDREN 3226 "See `CHILDREN OF NETBIOS`" 3227 DECODING 3228 "NETBEUI provides a named service lookup function. This function 3229 allows clients to locate a service by (locally assigned) name. 3230 An implementation is encouraged to follow lookups and session 3231 establishments and having determined the child protocol, track 3232 them. 3234 How the child protocol is determined and how the sessions are 3235 tracked is an implementation specific matter and is beyond the 3236 scope of this document." 3237 REFERENCE 3238 "IBM" 3239 ::= { 3240 llc 0xF0, -- [0.0.0.240] 3241 802-1Q 0x020000F0 -- 1Q-LLC [2.0.0.240] 3242 } 3244 nbt-name PROTOCOL-IDENTIFIER 3245 PARAMETERS { } 3246 ATTRIBUTES { } 3247 DESCRIPTION 3248 "NetBIOS-over-TCP name protocol." 3249 REFERENCE 3250 "RFC 1001 [RFC1001] defines the 'PROTOCOL STANDARD FOR A NetBIOS 3251 SERVICE ON A TCP/UDP TRANSPORT: CONCEPTS AND METHODS.' RFC 1002 3252 [RFC1002] defines the 'PROTOCOL STANDARD FOR A NetBIOS SERVICE ON 3253 A TCP/UDP TRANSPORT: DETAILED SPECIFICATIONS'." 3254 ::= { 3255 udp 137, 3256 tcp 137 3257 } 3259 nbt-session PROTOCOL-IDENTIFIER 3260 PARAMETERS { } 3261 ATTRIBUTES { } 3262 DESCRIPTION 3263 "NetBIOS-over-TCP session protocol." 3264 REFERENCE 3265 "RFC 1001 [RFC1001] defines the 'PROTOCOL STANDARD FOR A NetBIOS 3266 SERVICE ON A TCP/UDP TRANSPORT: CONCEPTS AND METHODS.' RFC 1002 3267 [RFC1002] defines the 'PROTOCOL STANDARD FOR A NetBIOS SERVICE ON 3268 A TCP/UDP TRANSPORT: DETAILED SPECIFICATIONS'." 3269 ::= { 3270 udp 139, 3271 tcp 139 3272 } 3274 nbt-data PROTOCOL-IDENTIFIER 3275 PARAMETERS { } 3276 ATTRIBUTES { 3277 hasChildren(0) 3278 } 3279 DESCRIPTION 3280 "NetBIOS-over-TCP datagram protocol." 3281 CHILDREN 3282 "See `CHILDREN OF NETBIOS`" 3283 REFERENCE 3284 "RFC 1001 [RFC1001] defines the 'PROTOCOL STANDARD FOR A NetBIOS 3285 SERVICE ON A TCP/UDP TRANSPORT: CONCEPTS AND METHODS.' RFC 1002 3286 [RFC1002] defines the 'PROTOCOL STANDARD FOR A NetBIOS SERVICE ON 3287 A TCP/UDP TRANSPORT: DETAILED SPECIFICATIONS'." 3288 ::= { 3289 udp 138, 3290 tcp 138 3291 } 3293 netbios-3com PROTOCOL-IDENTIFIER 3294 PARAMETERS { } 3295 ATTRIBUTES { 3296 hasChildren(0) 3297 } 3298 DESCRIPTION 3299 "3COM NetBIOS protocol." 3300 CHILDREN 3301 "See `CHILDREN OF NETBIOS`" 3302 REFERENCE 3303 "3Com Corporation" 3304 ::= { 3305 ether2 0x3C00, 3306 ether2 0x3C01, 3307 ether2 0x3C02, 3308 ether2 0x3C03, 3309 ether2 0x3C04, 3310 ether2 0x3C05, 3311 ether2 0x3C06, 3312 ether2 0x3C07, 3313 ether2 0x3C08, 3314 ether2 0x3C09, 3315 ether2 0x3C0A, 3316 ether2 0x3C0B, 3317 ether2 0x3C0C, 3318 ether2 0x3C0D, 3319 802-1Q 0x3C00, 3320 802-1Q 0x3C01, 3321 802-1Q 0x3C02, 3322 802-1Q 0x3C03, 3323 802-1Q 0x3C04, 3324 802-1Q 0x3C05, 3325 802-1Q 0x3C06, 3326 802-1Q 0x3C07, 3327 802-1Q 0x3C08, 3328 802-1Q 0x3C09, 3329 802-1Q 0x3C0A, 3330 802-1Q 0x3C0B, 3331 802-1Q 0x3C0C, 3332 802-1Q 0x3C0D 3333 } 3335 nov-netbios PROTOCOL-IDENTIFIER 3336 PARAMETERS { } 3337 ATTRIBUTES { 3338 hasChildren(0) 3339 } 3340 DESCRIPTION 3341 "Novell's version of the NetBIOS protocol." 3342 CHILDREN 3343 "See `CHILDREN OF NETBIOS`" 3344 REFERENCE 3345 "Novell Corporation" 3346 ::= { 3347 nov-sap 0x0020, -- this is the right one to use 3348 -- these are typically also true, but derivable from the one 3349 -- above at run-time 3350 -- ipx 0x14; when reached by IPX packet type 3351 nov-pep 0x0455 -- when reached by socket number 3352 } 3354 burst PROTOCOL-IDENTIFIER 3355 PARAMETERS { } 3356 ATTRIBUTES { } 3357 DESCRIPTION 3358 "BURST [TBD]" 3359 REFERENCE 3360 "Novell Corporation" 3361 ::= { nov-pep 0x0d05 } 3363 6.2. Multi-stack protocols 3365 smb PROTOCOL-IDENTIFIER 3366 PARAMETERS { } 3367 ATTRIBUTES { } 3368 DESCRIPTION 3369 "Microsoft Server Message Block Protocol." 3370 REFERENCE 3371 "Microsoft Corporation" 3372 ::= { 3373 netbeui 1, 3374 netbios-3com 1, 3375 nov-netbios 1, 3376 nbt-data 1, 3377 nbt-session 1, 3378 nov-pep 0x550, 3379 nov-pep 0x552 3380 -- vspp ??? 3381 -- xns-spp ??? 3382 } 3384 notes PROTOCOL-IDENTIFIER 3385 PARAMETERS { } 3386 ATTRIBUTES { } 3387 DESCRIPTION 3388 "Lotus Notes Protocol." 3389 REFERENCE 3390 "Lotus Development" 3391 ::= { 3392 netbeui 2, 3393 netbios-3com 2, 3394 nov-netbios 2, 3395 nbt-data 2, 3396 tcp 1352, 3397 udp 1352, 3398 nov-sap 0x039b 3399 } 3401 ccmail PROTOCOL-IDENTIFIER 3402 PARAMETERS { } 3403 ATTRIBUTES { } 3404 DESCRIPTION 3405 "Lotus CC-mail Protocol." 3406 REFERENCE 3407 "Lotus Development" 3408 ::= { 3409 netbeui 3, 3410 netbios-3com 3, 3411 nov-netbios 3, 3412 nbt-data 3, 3413 tcp 3264, 3414 udp 3264 3415 } 3417 snmp PROTOCOL-IDENTIFIER 3418 PARAMETERS { } 3419 ATTRIBUTES { } 3420 DESCRIPTION 3421 "Simple Network Management Protocol. Includes SNMPv1 and SNMPv2 3422 protocol versions. Does not include SNMP trap packets." 3423 REFERENCE 3424 "The SNMP SMI is defined in RFC 1902 [RFC1902]. Version 1 of the 3425 SNMP protocol is defined in RFC 1905 [RFC1905]. Transport 3426 mappings are defined in RFC 1906 [RFC1906]; RFC 1420 (SNMP over 3427 IPX) [RFC1420]; RFC 1419 (SNMP over AppleTalk) [RFC1419]." 3428 ::= { 3429 udp 161, 3430 nov-pep 0x900f, -- [ 0.0.144.15 ] 3431 atalk 8, 3432 tcp 161 3433 } 3435 snmptrap PROTOCOL-IDENTIFIER 3436 PARAMETERS { } 3437 ATTRIBUTES { } 3438 DESCRIPTION 3439 "Simple Network Management Protocol Trap Port." 3440 REFERENCE 3441 "The SNMP SMI is defined in RFC 1902 [RFC1902]. The SNMP 3442 protocol is defined in RFC 1905 [RFC1905]. Transport mappings 3443 are defined in RFC 1906 [RFC1906]; RFC 1420 (SNMP over IPX) 3444 [RFC1420]; RFC 1419 (SNMP over AppleTalk) [RFC1419]." 3445 ::= { 3446 udp 162, 3447 nov-pep 0x9010, 3448 atalk 9, 3449 tcp 162 3450 } 3452 -- END 3454 7. Intellectual Property 3456 The IETF takes no position regarding the validity or scope of any 3457 intellectual property or other rights that might be claimed to pertain 3458 to the implementation or use of the technology described in this 3459 document or the extent to which any license under such rights might or 3460 might not be available; neither does it represent that it has made any 3461 effort to identify any such rights. Information on the IETF's 3462 procedures with respect to rights in standards-track and standards- 3463 related documentation can be found in BCP-11. Copies of claims of 3464 rights made available for publication and any assurances of licenses to 3465 be made available, or the result of an attempt made to obtain a general 3466 license or permission for the use of such proprietary rights by 3467 implementors or users of this specification can be obtained from the 3468 IETF Secretariat." 3470 The IETF invites any interested party to bring to its attention any 3471 copyrights, patents or patent applications, or other proprietary rights 3472 which may cover technology that may be required to practice this 3473 standard. Please address the information to the IETF Executive 3474 Director. 3476 8. Acknowledgements 3478 This document was produced by the IETF RMONMIB Working Group. 3480 The authors wish to thank the following people for their contributions 3481 to this document: 3483 Anil Singhal 3484 Frontier Software Development, Inc. 3486 Jeanne Haney 3487 Bay Networks 3489 Dan Hansen 3490 Network General Corp. 3492 Special thanks are in order to the following people for writing RMON PI 3493 macro compilers, and improving the specification of the PI macro 3494 language: 3496 David Perkins 3497 DeskTalk Systems, Inc. 3499 Skip Koppenhaver 3500 Technically Elite, Inc. 3502 9. References 3504 [IEN158] 3505 J. Haverty, "XNET Formats for Internet Protocol Version 4", IEN 3506 158, October 1980. 3508 [RFC407] 3509 Bressler, R., Guida. R., and A. McKenzie, "Remote Job Entry 3510 Protocol", RFC 407, MIT-DMCG, BBN-NET, October 1972. 3512 [RFC493] 3513 Michener, J., Cotton, I., Kelley, K., Liddle, D., and E. Meyer, 3514 "E.W., Jr Graphics Protocol", RFC 493, April 1973. 3516 [RFC734] 3517 M. Crispin, "SUPDUP Protocol", RFC 734, SU-AI, October 1977. 3519 [RFC740] 3520 R. Braden, "NETRJS Protocol", RFC 740, UCLA-CCN, November 1977. 3522 [RFC741] 3523 D. Cohen, "Specifications for the Network Voice Protocol", RFC 741, 3524 ISI/RR 7539, USC/Information Sciences Institute, March 1976. 3526 [RFC759] 3527 J. Postel, "Internet Message Protocol", RFC 759, USC/Information 3528 Sciences Institute, August 1980. 3530 [RFC768] 3531 J. Postel, "User Datagram Protocol", STD 6, RFC 768, 3532 USC/Information Sciences Institute, August 1980. 3534 [RFC791] 3535 J. Postel, "Internet Protocol - DARPA Internet Program Protocol 3536 Specification", STD 5, RFC 791, USC/Information Sciences Institute, 3537 September 1981. 3539 [RFC792] 3540 J. Postel, "Internet Control Message Protocol - DARPA Internet 3541 Program Protocol Specification", STD 5, RFC 792, USC/Information 3542 Sciences Institute, September 1981. 3544 [RFC793] 3545 J. Postel, "Transmission Control Protocol - DARPA Internet Program 3546 Protocol Specification", STD 5, RFC 793, USC/Information Sciences 3547 Institute, September 1981. 3549 [RFC818] 3550 J. Postel, "Remote User Telnet service", RFC 818, ISI, November 3551 1982. 3553 [RFC821] 3554 J. Postel, "Simple Mail Transfer Protocol", RFC 821, 3555 USC/Information Sciences Institute, August 1982. 3557 [RFC823] 3558 Hinden, R., and A. Sheltzer, "The DARPA Internet Gateway", RFC 823, 3559 BBN, September 1982. 3561 [RFC826] 3562 D. Plummer, "An Ethernet Address Resolution Protocol or Converting 3563 Network Protocol Addresses to 48-bit Ethernet Addresses for 3564 Transmission on Ethernet Hardware", STD 37, RFC 826, MIT-LCS, 3565 November 1982. 3567 [RFC854] 3568 Postel, J., and J. Reynolds, "Telnet Protocol Specification", STD 3569 8, RFC 854, ISI, May 1983. 3571 [RFC862] 3572 J. Postel, "Echo Protocol", STD 20, RFC 862, ISI, May 1983. 3574 [RFC863] 3575 J. Postel, "Discard Protocol", STD 21, RFC 863, ISI, May 1983. 3577 [RFC864] 3578 J. Postel, "Character Generator Protocol", STD 22, RFC 864, ISI, 3579 May 1983. 3581 [RFC865] 3582 J. Postel, "Quote of the Day Protocol", RFC 865, ISI, May 1983. 3584 [RFC866] 3585 J. Postel, "Active Users", STD 26, RFC 866, ISI, May 1983. 3587 [RFC867] 3588 J. Postel, "Daytime Protocol", STD 25, RFC 867, ISI, May 1983. 3590 [RFC868] 3591 J. Postel, "Time Protocol", STD 26, RFC 868, ISI, May 1983. 3593 [RFC869] 3594 R. Hinden, "A Host Monitoring Protocol", RFC 869, Bolt Beranek and 3595 Newman, December 1983. 3597 [RFC887] 3598 M. Accetta, "Resource Location Protocol", RFC 887, CMU, December 3599 1983. 3601 [RFC904] 3602 International Telegraph and Telephone Co., D. Mills, "Exterior 3603 Gateway Protocol Formal Specification", RFC 904, April 1984. 3605 [RFC905] 3606 International Standards Organization, A. McKenzie, "ISO Transport 3607 Protocol Specification - ISO DP 8073", RFC 905, April 1984. 3609 [RFC908] 3610 Velten, D., Hinden, R., and J. Sax, "Reliable Data Protocol", RFC 3611 908, BBN Communications Corporation, July 1984. 3613 [RFC913] 3614 M. Lottor, "Simple File Transfer Protocol", RFC 913, MIT, September 3615 1984. 3617 [RFC915] 3618 Elvy, M., and R. Nedved, "Network mail path service", RFC 915, 3619 Harvard University, Carnegie-Mellon University, December 1984. 3621 [RFC937] 3622 Butler, M., Chase, D., Goldberger, J., Postel, J., and J. Reynolds, 3623 "Post Office Protocol - version 2", RFC 937, ISI, February 1985. 3625 [RFC938] 3626 T. Miller, "Internet Reliable Transaction Protocol", RFC 938, ACC, 3627 February 1985. 3629 [RFC951] 3630 Croft, W., and J. Gilmore, "BOOTSTRAP Protocol (BOOTP)", RFC 951, 3631 Stanford and SUN Microsytems, September 1985. 3633 [RFC953] 3634 Feinler, E., Harrenstien, K., and M. Stahl, "Hostname Server", RFC 3635 953, SRI, October 1985. 3637 [RFC954] 3638 Feinler, E., Harrenstien, K., and M. Stahl, "NICNAME/WHOIS", RFC 3639 954, SRI, October 1985. 3641 [RFC959] 3642 Postel, J., and J. Reynolds, "File Transfer Protocol", RFC 959, 3643 USC/Information Sciences Institute, October 1985. 3645 [RFC972] 3646 F. Wancho, "Password Generator Protocol", RFC 972, WSMR, January 3647 1986. 3649 [RFC977] 3650 Kantor, B., and P. Lapsley, "Network News Transfer Protocol: A 3651 Proposed Standard for the Stream-Based Transmission of News", RFC 3652 977, U.C. San Diego, U.C. Berkeley, February 1986. 3654 [RFC996] 3655 D. Mills, "Statistics server", RFC 996, University of Delaware, 3656 February 1987. 3658 [RFC998] 3659 Clark, D., Lambert, M., and L. Zhang, "NETBLT: A Bulk Data Transfer 3660 Protocol", RFC 998, MIT, March 1987. 3662 [RFC1001], 3663 NetBIOS Working Group in the Defense Advanced Research Projects 3664 Agency, Internet Activities Board, End-to-End Services Task Force. 3665 "Protocol standard for a NetBIOS service on a TCP/UDP transport: 3666 Concepts and methods", RFC 1001, March 1987. 3668 [RFC1002], 3669 NetBIOS Working Group in the Defense Advanced Research Projects 3670 Agency, Internet Activities Board, End-to-End Services Task Force. 3671 "Protocol standard for a NetBIOS service on a TCP/UDP transport: 3672 Detailed specifications.", RFC 1002, March 1987. 3674 [RFC1021] 3675 Partridge, C., and G. Trewitt, "High-level Entity Management System 3676 HEMS", RFC 1021, BBN/NNSC, Stanford, October 1987. 3678 [RFC1028] 3679 Case, J., Davin, J., Fedor, M., and M. Schoffstall, "Simple Gateway 3680 Monitoring Protocol", RFC 1028, University of Tennessee at 3681 Knoxville, Proteon, Inc., Cornell University, Rensselaer 3682 Polytechnic Institute, November 1987. 3684 [RFC1035] 3685 P. Mockapetris, "Domain Names - Implementation and Specification", 3686 STD 13, RFC 1035, USC/Information Sciences Institute, November 3687 1987. 3689 [RFC1056] 3690 M. Lambert, "PCMAIL: A distributed mail system for personal 3691 computers", RFC 1056, MIT, June 1988. 3693 [RFC1057] 3694 Sun Microsystems, Inc, "RPC: Remote Procedure Call Protocol 3695 Specification version 2", RFC 1057, Sun Microsystems, Inc., June 3696 1988. 3698 [RFC1064] 3699 M. Crispin, "Interactive Mail Access Protocol: Version 2", RFC 3700 1064, SUMEX-AIM, July 1988. 3702 [RFC1068] 3703 A. DeSchon, and R. Braden, "Background File Transfer Program 3704 BFTP", RFC 1068, ISI, August 1988. 3706 [RFC1070] 3707 Hagens, R., Hall, N., and M. Rose, "Use of the Internet as a 3708 subnetwork for experimentation with the OSI network layer", RFC 3709 1070, U of Wiscsonsin - Madison, The Wollongong Group, February 3710 1989. 3712 [RFC1078] 3713 M. Lottor, "TCP port service Multiplexer TCPMUX", RFC 1078, SRI- 3714 NIC, November, 1988. 3716 [RFC1086] 3717 Onions, J., and M. Rose, "ISO-TP0 bridge between TCP and X.25", RFC 3718 1086, Nottingham, TWG, December 1988. 3720 [RFC1095] 3721 Warrier, U., and L. Besaw, "Common Management Information Services 3722 and Protocol over TCP/IP (CMOT)", RFC 1095, Unisys Corporation, 3723 Hewlett-Packard, April 1989. 3725 [RFC1112] 3726 S. Deering, "Host Extensions for IP Multicasting", RFC 1112, 3727 Stanford University, August 1989. 3729 [RFC1155] 3730 Rose, M., and K. McCloghrie, "Structure and Identification of 3731 Management Information for TCP/IP-based Internets", RFC 1155, 3732 Performance Systems International, Hughes LAN Systems, May 1990. 3734 [RFC1157] 3735 Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 3736 Management Protocol", RFC 1157, SNMP Research, Performance Systems 3737 International, Performance Systems International, MIT Laboratory 3738 for Computer Science, May 1990. 3740 [RFC1203] 3741 J. Rice, "Interactive Mail Access Protocol - Version 3", RFC 1203, 3742 Stanford, February 1991. 3744 [RFC1204] 3745 Lee, D., and S. Yeh, "Message Posting Protocol (MPP)", RFC 1204, 3746 Netix Communications, Inc., February 1991. 3748 [RFC1212] 3749 Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 3750 Performance Systems International, Hughes LAN Systems, March 1991. 3752 [RFC1213] 3753 McCloghrie, K., and M. Rose, "Management Information Base for 3754 Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 3755 1213, Hughes LAN Systems, Performance Systems International, March 3756 1991. 3758 [RFC1215] 3759 M. Rose, "A Convention for Defining Traps for use with the SNMP", 3760 RFC 1215, Performance Systems International, March 1991. 3762 [RFC1226] 3763 B. Kantor, "Internet Protocol Encapsulation of AX.25 Frames", RFC 3764 1226, UCSD, May 1991. 3766 [RFC1227] 3767 M. Rose, "SNMP MUX Protocol and MIB", RFC 1227, Performance Systems 3768 International, Inc., May 1991. 3770 [RFC1234] 3771 D. Provan, "Tunneling IPX Traffic through IP Networks", RFC 1234, 3772 Novell, Inc., June 1991. 3774 [RFC1235] 3775 Ioannidis, J., and G. Maguire, Jr., "The Coherent File Distribution 3776 Protocol", RFC 1235, Columbia University, June 1991. 3778 [RFC1241] 3779 Mills, D., and R. Woodburn, "A Scheme for an Internet Encapsulation 3780 Protocol: Version 1", RFC 1241, SAIC, University of Delaware, July 3781 1991. 3783 [RFC1249] 3784 Howes, T., Smith, M., and B. Beecher, "DIXIE Protocol 3785 Specification", RFC 1249, University of Michigan, August 1991. 3787 [RFC1267] 3788 Lougheed, K., and Y. Rekhter, "A Border Gateway Protocol 3 3789 (BGP-3)", RFC 1267, Cisco Systems, T.J. Watson Research Center, IBM 3790 Corp., October 1991. 3792 [RFC1282] 3793 B. Kantor, "BSD Rlogin", RFC 1282, Univ. of Calif San Diego, 3794 December 1991. 3796 [RFC1288] 3797 D. Zimmerman, "The Finger User Information Protocol", RFC 1288, 3798 Center for Discrete Mathematics and Theoretical Computer Science, 3799 December 1991. 3801 [RFC1301] 3802 Armstrong, S., Freier, A., and K. Marzullo, "Multicast Transport 3803 Protocol", RFC 1301, Xerox, Apple, Cornell, February 1992. 3805 [RFC1305] 3806 D. Mills, "Network Time Protocol (v3)", RFC 1305, University of 3807 Delaware, April 1992. 3809 [RFC1312] 3810 Nelson, R., and G. Arnold, "Message Send Protocol", RFC 1312, 3811 Crynwr Software, Sun Microsystems, Inc., April 1992. 3813 [RFC1339] 3814 Dorner, S., and P. Resnick, "Remote Mail Checking Protocol", RFC 3815 1339, U. of Illinois at Urbana-Champaign, June 1992. 3817 [RFC1350] 3818 K. Sollins, "TFTP Protocol (revision 2)", RFC 1350, MIT, July 1992. 3820 [RFC1413] 3821 M. St. Johns, "Identification Protocol", RFC 1413, US Department of 3822 Defense, February 1993. 3824 [RFC1419] 3825 Minshall, G., and M. Ritter, "SNMP over AppleTalk", RFC 1419, 3826 Novell, Inc., Apple Computer, Inc., March 1993. 3828 [RFC1420] 3829 S. Bostock, "SNMP over IPX", RFC 1420, Novell, Inc., March 1993. 3831 [RFC1436] 3832 Anklesaria, F., McCahill, M., Lindner, P., Johnson, D., John, D., 3833 Torrey, D., and B. Alberti, "The Internet Gopher Protocol (a 3834 distributed document search and retrieval protocol)", RFC 1436, 3835 University of Minnesota, March 1993. 3837 [RFC1459] 3838 Oikarinen, J., and D. Reed, "Internet Relay Chat Protocol", RFC 3839 1459, May 1993. 3841 [RFC1476] 3842 R. Ullmann, "RAP: Internet Route Access Protocol", RFC 1476, 3843 Process Software Corporation, June 1993. 3845 [RFC1479] 3846 M. Steenstrup, "Inter-Domain Policy Routing Protocol Specification: 3847 Version 1", RFC 1479, BBN Systems and Technologies, July 1993. 3849 [RFC1483] 3850 J. Heinanen, "Multiprotocol Encapsulation over ATM Adaptation Layer 3851 5", RFC 1483, Telecom Finland, July 1993. 3853 [RFC1492] 3854 C. Finseth, "An Access Control Protocol, Sometimes Called TACACS", 3855 RFC 1492, University of Minnesota, July 1993. 3857 [RFC1510] 3858 Kohl, J., and B. Neuman, "The Kerberos Network Authentication 3859 Service (V5)", RFC 1510, Digital Equipment Corporation, ISI, 3860 September 1993. 3862 [RFC1583] 3863 J. Moy, "OSPF Version 2", RFC 1583, Proteon, Inc., March 1994. 3865 [RFC1700] 3866 Reynolds, J., and J. Postel, "Assigned Numbers", STD 2, RFC 1700, 3867 USC/Information Sciences Institute, October 1994. 3869 [RFC1701] 3870 Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic Routing 3871 Encapsulation (GRE)", RFC 1701, Netsmiths, Ltd., Cisco Systems, 3872 October 1994. 3874 [RFC1702] 3875 Hanks, S., Li, T., Farinacci, D., and P. Traina, "Generic Routing 3876 Encapsulation over IPv4 networks", RFC 1702, Netsmiths, Ltd., Cisco 3877 Systems, October 1994. 3879 [RFC1725] 3880 Myers, J., and M. Rose, "Post Office Protocol - Version 3", RFC 3881 1725, Carnegie Mellon, Dover Beach Consulting, November 1994. 3883 [RFC1729] 3884 C. Lynch, "Using the Z39.50 Information Retrieval Protocol in the 3885 Internet Environment", RFC 1729, University of California, December 3886 1994. 3888 [RFC1730] 3889 M. Crispin, "Internet Message Access Protocol - Version 4", RFC 3890 1730, University of Washington, December 1994. 3892 [RFC1739] 3893 Kessler, G., and S. Shepard, "A Primer On Internet and TCP/IP 3894 Tools", RFC 1739, Hill Associates, Inc., December 1994. 3896 [RFC1745] 3897 Varadhan, K., Hares, S., and Y. Rekhter, "BGP4/IDRP for IP---OSPF 3898 Interaction", RFC 1745, OARnet & ISI, NSFnet/Merit, IBM, December 3899 1994. 3901 [RFC1757] 3902 S. Waldbusser, "Remote Network Monitoring MIB", RFC 1757, Carnegie 3903 Mellon University, February 1995. 3905 [RFC1777] 3906 Yeong, W., Howes, T., and S. Kille, "Lightweight Directory Access 3907 Protocol", Performance Systems International, University of 3908 Michigan, ISODE Consortium, March 1995. 3910 [RFC1782] 3911 Malkin, G., and A. Harkin, "TFTP Option Extension", RFC 1782, 3912 Xylogics, Inc., Hewlett Packard Co., March 1995. 3914 [RFC1783] 3915 Malkin, G., and A. Harkin, "TFTP BlockOption Option", RFC 1783, 3916 Xylogics, Inc., Hewlett Packard Co., March 1995. 3918 [RFC1784] 3919 Malkin, G., and A. Harkin, "TFTP Timeout Interval and Transfer Size 3920 Options", RFC 1784, Xylogics, Inc., Hewlett Packard Co., March 3921 1995. 3923 [RFC1798] 3924 A. Young, "Connection-less Lightweight Directory Access Protocol", 3925 RFC 1798, ISODE Consortium, June 1995. 3927 [RFC1800] 3928 J. Postel, "Internet Official Protocol Standards", STD 1, RFC 1800, 3929 IAB, July 1995. 3931 [RFC1813] 3932 Callaghan, B., Pawlowski, B., and P. Staubach, "NFS Version 3 3933 Protocol Specification", RFC 1813, Sun Microsystems, Inc., June 3934 1995. 3936 [RFC1819] 3937 Delgrossi, L., and L. Berger, "Internet Stream Protocol Version 2 3938 (ST2)", RFC 1819, ST2 Working Group, August 1995. 3940 [RFC1831] 3941 R. Srinivasan, "Remote Procedure Call Protocol Version 2", RFC 3942 1831, Sun Microsystems, Inc., August 1995. 3944 [RFC1853] 3945 W. Simpson, "IP in IP Tunneling", RFC 1853, Daydreamer, October 3946 1995. 3948 [RFC1901] 3949 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 3950 Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 3951 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 3952 Inc., International Network Services, January 1996. 3954 [RFC1902] 3955 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 3956 Waldbusser, "Structure of Management Information for version 2 of 3957 the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP 3958 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 3959 International Network Services, January 1996. 3961 [RFC1903] 3962 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 3963 Waldbusser, "Textual Conventions for version 2 of the Simple 3964 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 3965 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 3966 International Network Services, January 1996. 3968 [RFC1904] 3969 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 3970 Waldbusser, "Conformance Statements for version 2 of the Simple 3971 Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research, 3972 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 3973 International Network Services, January 1996. 3975 [RFC1905] 3976 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 3977 Waldbusser, "Protocol Operations for Version 2 of the Simple 3978 Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 3979 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 3980 International Network Services, January 1996. 3982 [RFC1906] 3983 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 3984 Waldbusser, "Transport Mappings for Version 2 of the Simple Network 3985 Management Protocol (SNMPv2)"", RFC 1906, SNMP Research, Inc., 3986 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 3987 Network Services, January 1996. 3989 [RFC1940] 3990 Estrin, D., Li, T., Rekhter, Y., Varadhan, K., and D. Zappala, 3991 "Source Demand Routing: Packet Format and Forwarding Specification 3992 (Version 1).", RFC 1940, USC, Cisco Systems, May 1996. 3994 [RFC1945] 3995 Berners-Lee, T., and R. Fielding, "Hypertext Transfer Protocol -- 3996 HTTP/1.0", RFC 1945, MIT/LCS, UC-Irvine, November 1995. 3998 [RFC2002] 3999 C. Perkins, IP Mobility Support", RFC 2002, IBM, October 1996. 4001 [RFC2003] 4002 C. Perkins, "IP Encapsulation within IP", RFC 2003, IBM, October 4003 1996. 4005 [RFC2021] 4006 S. Waldbusser, "Remote Network Monitoring MIB (RMON-2)", RFC 2021, 4007 International Network Services, January 1997. 4009 [RFC2037] 4010 McCloghrie, K., and A. Bierman, "Entity MIB using SMIv2", RFC 2037, 4011 Cisco Systems, October 1996. 4013 [RFC2068] 4014 Fielding, R., Gettys, J., Mogul, J., Frystyk, H., and T. Berners- 4015 Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2068, DEC, 4016 MIT/LCS, January 1997. 4018 [RFC2069] 4019 Franks, J., Hallam-Baker, P., Hostetler, J., Luotonen, P. A., and 4020 E. L. Stewart, "An Extension to HTTP: Digest Access 4021 Authentication", RFC 2069, CERN, Spyglass, Inc., Microsoft 4022 Corporation, Netscape Communications Corporation, Open Market, 4023 Inc., January 1997. 4025 [RFC2074] 4026 Bierman, A., and R. Iddon, "Remote Network Monitoring MIB Protocol 4027 Identifiers", RFC 2074, Cisco Systems, AXON Networks Inc., January 4028 1997. 4030 [RFC2109] 4031 Kristol, D., and L. Montulli, "HTTP State Management Mechanism", 4032 RFC 2109, Bell Laboratories/Lucent Technologies, Netscape 4033 Communications, February 1997. 4035 [RFC2138] 4036 Rigney, C., Rubens, A., Simpson, W., and W. Willens, "Remote 4037 Authentication Dial In User Service (RADIUS)", RFC 2138, 4038 Livingston, Merit, Daydreamer, Livingston, April 1997. 4040 [RFC2139] 4041 C. Rigney, "RADIUS Accounting", RFC 2139, Livingston, April 1997. 4043 [RFC2145] 4044 Mogul, J., Fielding, R., Gettys, J., and H. Frystyk, "Use and 4045 interpretation of HTTP version numbers", RFC 2145, DEC, MIT/LCS, 4046 May 1997. 4048 [RFC2205] 4049 Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S. Jamin, 4050 "Resource ReSerVation Protocol (RSVP) -- Version 1 Functional 4051 Specification", RFC 2205, ISI, UCLA, IBM Research, University of 4052 Michigan, September, 1997. 4054 [RFC2233] 4055 McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB Using 4056 SMIv2", RFC 2233, Cisco Systems, FTP Software, November, 1997. 4058 [RFC2271] 4059 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 4060 Describing SNMP Management Frameworks", RFC 2271, Cabletron 4061 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 4062 January 1998. 4064 [RFC2272] 4065 Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 4066 Processing and Dispatching for the Simple Network Management 4067 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 4068 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 4070 [RFC2273] 4071 Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 4072 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 4073 Systems, January 1998. 4075 [RFC2274] 4076 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 4077 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 4078 2274, IBM T. J. Watson Research, January 1998. 4080 [RFC2275] 4081 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 4082 Control Model (VACM) for the Simple Network Management Protocol 4083 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 4084 Cisco Systems, Inc., January 1998. 4086 [RFC2332] 4087 Luciani, J., Katz, D., Piscitello, D., Cole, B., and N. Doraswamy, 4088 "NBMA Next Hop Resolution Protocol (NHRP)", RFC 2332, Bay Networks, 4089 cisco Systems, Core Competence, Inc., Juniper Networks, Bay 4090 Networks, April 1998. 4092 [RFC2408] 4093 Maughan, D., Schertler, M., Schneider, M., and J. Turner, RFC 2408, 4094 National Security Agency, Securify, Inc. National Security Agency, 4095 RABA Technologies, Inc., November 1998. 4097 [RFC2570] 4098 Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 4099 Version 3 of the Internet-standard Network Management Framework", 4100 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, 4101 Inc., Ericsson, Cisco Systems, April 1999 4103 [RFC2571] 4104 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 4105 Describing SNMP Management Frameworks", RFC 2571, Cabletron 4106 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, April 4107 1999 4109 [RFC2572] 4110 Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 4111 Processing and Dispatching for the Simple Network Management 4112 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron Systems, 4113 Inc., BMC Software, Inc., IBM T. J. Watson Research, April 1999 4115 [RFC2573] 4116 Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 4117 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 4118 Systems, April 1999 4120 [RFC2574] 4121 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 4122 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 4123 2574, IBM T. J. Watson Research, April 1999 4125 [RFC2575] 4126 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 4127 Control Model (VACM) for the Simple Network Management Protocol 4128 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 4129 Cisco Systems, Inc., April 1999 4131 [RFC2578] 4132 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4133 and S. Waldbusser, "Structure of Management Information Version 2 4134 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 4135 Braunschweig, SNMP Research, First Virtual Holdings, International 4136 Network Services, April 1999 4138 [RFC2579] 4139 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4140 and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, STD 4141 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, First 4142 Virtual Holdings, International Network Services, April 1999 4144 [RFC2580] 4145 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4146 and S. Waldbusser, "Conformance Statements for SMIv2", RFC 2580, 4147 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 4148 First Virtual Holdings, International Network Services, April 1999 4150 [RMONPROT_REF] 4151 Bierman, A., Bucci, C., and R. Iddon, "RMON Protocol Identifier 4152 Reference", draft-ietf-rmonmib-rmonprot-ref-00.txt, Cisco Systems, 4153 Inc., 3Com, Inc., November, 1998. 4155 10. Security Considerations 4157 This document contains textual descriptions of well-known networking 4158 protocols, not the definition of any networking behavior. As such, no 4159 security considerations are raised by its publication. 4161 11. Authors' Addresses 4163 Andy Bierman 4164 Cisco Systems, Inc. 4165 170 West Tasman Drive 4166 San Jose, CA USA 95134 4167 Phone: +1 408-527-3711 4168 Email: abierman@cisco.com 4169 Chris Bucci 4170 Cisco Systems, Inc. 4171 170 West Tasman Drive 4172 San Jose, CA USA 95134 4173 Phone: +1 408-527-5337 4174 Email: cbucci@cisco.com 4176 Robin Iddon 4177 c/o 3Com Inc. 4178 Blackfriars House 4179 40/50 Blackfrias Street 4180 Edinburgh, EH1 1NE, UK 4181 Phone: +44 131.558.3888 4182 Email: None 4184 12. Full Copyright Statement 4186 Copyright (C) The Internet Society (1999). All Rights Reserved. 4188 This document and translations of it may be copied and furnished to 4189 others, and derivative works that comment on or otherwise explain it or 4190 assist in its implementation may be prepared, copied, published and 4191 distributed, in whole or in part, without restriction of any kind, 4192 provided that the above copyright notice and this paragraph are included 4193 on all such copies and derivative works. However, this document itself 4194 may not be modified in any way, such as by removing the copyright notice 4195 or references to the Internet Society or other Internet organizations, 4196 except as needed for the purpose of developing Internet standards in 4197 which case the procedures for copyrights defined in the Internet 4198 Standards process must be followed, or as required to translate it into 4199 languages other than English. 4201 The limited permissions granted above are perpetual and will not be 4202 revoked by the Internet Society or its successors or assigns. 4204 This document and the information contained herein is provided on an "AS 4205 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 4206 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 4207 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 4208 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 4209 FITNESS FOR A PARTICULAR PURPOSE."