idnits 2.17.1 draft-ietf-ptopomib-pdp-03.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 Internet-Drafts being working documents. ** 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? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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 5 instances of too long lines in the document, the longest one being 9 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 939 has weird spacing: '...', then this ...' == Line 1044 has weird spacing: '...', then this ...' == Line 1147 has weird spacing: '...imed to perta...' -- 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 (16 November 1998) is 9286 days in the past. Is this intentional? 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? 'RFC2271' on line 1253 looks like a reference -- Missing reference section? 'RFC1155' on line 1185 looks like a reference -- Missing reference section? 'RFC1212' on line 1196 looks like a reference -- Missing reference section? 'RFC1215' on line 1200 looks like a reference -- Missing reference section? 'RFC1902' on line 1210 looks like a reference -- Missing reference section? 'RFC1903' on line 1217 looks like a reference -- Missing reference section? 'RFC1904' on line 1224 looks like a reference -- Missing reference section? 'RFC1157' on line 1190 looks like a reference -- Missing reference section? 'RFC1901' on line 1204 looks like a reference -- Missing reference section? 'RFC1906' on line 1238 looks like a reference -- Missing reference section? 'RFC2272' on line 1259 looks like a reference -- Missing reference section? 'RFC2274' on line 1270 looks like a reference -- Missing reference section? 'RFC1905' on line 1231 looks like a reference -- Missing reference section? 'RFC2273' on line 1265 looks like a reference -- Missing reference section? 'RFC2275' on line 1275 looks like a reference -- Missing reference section? 'PTOPO' on line 1181 looks like a reference -- Missing reference section? 'RFC2037' on line 1245 looks like a reference -- Missing reference section? 'ENTITY-MIB' on line 1177 looks like a reference -- Missing reference section? 'RFC2233' on line 1249 looks like a reference Summary: 10 errors (**), 0 flaws (~~), 5 warnings (==), 21 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 PTOPOMIB Working Group Andy Bierman 3 Internet Draft Cisco Systems, Inc. 4 Keith McCloghrie 5 Cisco Systems, Inc. 6 16 November 1998 8 Physical Topology Discovery Protocol and MIB 10 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, and 16 its working groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference material 22 or to cite them other than as ``work in progress.'' 24 To learn the current status of any Internet-Draft, please check the 25 1id-abstracts.txt listing contained in the Internet- Drafts Shadow 26 Directories on ftp.ietf.org, nic.nordu.net, venera.isi.edu, or 27 munnari.oz.au. 29 Distribution of this document is unlimited. Please send comments to the 30 PTOPOMIB Working Group, . 32 1. Copyright Notice 34 Copyright (C) The Internet Society (1998). All Rights Reserved. 36 2. Abstract 38 This memo defines an experimental protocol, and an experimental portion 39 of the Management Information Base (MIB) for use with network management 40 protocols in the Internet community. In particular, it describes a 41 physical topology discovery protocol and managed objects used for 42 managing the protocol. 44 3. Table of Contents 46 1 Copyright Notice ................................................ 1 47 2 Abstract ........................................................ 1 48 3 Table of Contents ............................................... 2 49 4 The SNMP Network Management Framework ........................... 3 50 5 Overview ........................................................ 4 51 5.1 Terms ......................................................... 4 52 5.2 Persistent Identifiers ........................................ 4 53 5.3 Relationship to the Physical Topology MIB ..................... 4 54 5.4 Relationship to Entity MIB .................................... 5 55 5.5 Relationship to Interfaces MIB ................................ 5 56 6 PTOPO Discovery Protocol ........................................ 5 57 6.1 Frame Encapsulation ........................................... 6 58 6.2 PDP Forwarding ................................................ 6 59 6.3 PDP Message Format ............................................ 7 60 6.3.1 PDP Header Format ........................................... 7 61 6.3.2 PDP PDU Encoding ............................................ 8 62 6.4 PDP Data MIB .................................................. 9 63 6.4.1 Definitions ................................................. 9 64 6.5 Protocol Operation ............................................ 13 65 6.5.1 Protocol Initialization ..................................... 14 66 6.5.2 Message Encoding ............................................ 14 67 6.5.2.1 Header Fields ............................................. 14 68 6.5.2.2 VarBindList ............................................... 14 69 6.5.3 Message Transmission ........................................ 15 70 6.5.4 Received Message Processing ................................. 15 71 6.5.4.1 Header Fields ............................................. 16 72 6.5.4.2 VarBindList ............................................... 16 73 6.5.4.3 PTOPO MIB Update .......................................... 16 74 6.5.5 Interface Shutdown Procedure ................................ 17 75 6.5.5.1 PDP Shutdown Transmission ................................. 17 76 6.5.5.2 PDP Shutdown Reception .................................... 17 77 7 PTOPO Discovery Protocol MIB .................................... 18 78 7.1 Definitions ................................................... 18 79 8 Intellectual Property ........................................... 27 80 9 Acknowledgements ................................................ 28 81 10 References ..................................................... 28 82 11 Security Considerations ........................................ 30 83 12 Authors' Addresses ............................................. 30 84 13 Full Copyright Statement ....................................... 32 85 4. The SNMP Network Management Framework 87 The SNMP Management Framework presently consists of five major 88 components: 90 o An overall architecture, described in RFC 2271 [RFC2271]. 92 o Mechanisms for describing and naming objects and events for the 93 purpose of management. The first version of this Structure of 94 Management Information (SMI) is called SMIv1 and described in RFC 95 1155 [RFC1155], RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The 96 second version, called SMIv2, is described in RFC 1902 [RFC1902], 97 RFC 1903 [RFC1903] and RFC 1904 [RFC1904]. 99 o Message protocols for transferring management information. The 100 first version of the SNMP message protocol is called SNMPv1 and 101 described in RFC 1157 [RFC1157]. A second version of the SNMP 102 message protocol, which is not an Internet standards track 103 protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and 104 RFC 1906 [RFC1906]. The third version of the message protocol is 105 called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2272 106 [RFC2272] and RFC 2274 [RFC2274]. 108 o Protocol operations for accessing management information. The first 109 set of protocol operations and associated PDU formats is described 110 in RFC 1157 [RFC1157]. A second set of protocol operations and 111 associated PDU formats is described in RFC 1905 [RFC1905]. 113 o A set of fundamental applications described in RFC 2273 [RFC2273] 114 and the view-based access control mechanism described in RFC 2275 115 [RFC2275]. 117 Managed objects are accessed via a virtual information store, termed the 118 Management Information Base or MIB. Objects in the MIB are defined 119 using the mechanisms defined in the SMI. 121 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 122 conforming to the SMIv1 can be produced through the appropriate 123 translations. The resulting translated MIB must be semantically 124 equivalent, except where objects or events are omitted because no 125 information in SMIv2 will be converted into textual descriptions in 126 SMIv1 during the translation process. However, this loss of machine 127 readable information is not considered to change the semantics of the 128 MIB. 130 5. Overview 132 There is a need for a standardized way of representing the physical 133 network connections pertaining to a given management domain. A 134 standardized discovery mechanism is also required to increase the 135 likelihood of multi-vendor interoperability of such physical topology 136 management information. 138 This document specifies a discovery protocol, suitable for use with the 139 Physical Topology MIB [PTOPO]. 141 5.1. Terms 143 Some terms are used throughout this document: 145 SNMP Agent 146 This term refers to an SNMP agent co-located with a particular PDP 147 Agent. Specifically, it refers to the SNMP Agent providing PDP MIB, 148 Entity MIB, Interfaces MIB, and possibly PTOPO MIB support for a 149 particular chassis. 151 PDP Agent 152 This term refers to a software entity which implements the PTOPO 153 Discovery Protocol for a particular chassis. 155 5.2. Persistent Identifiers 157 The PTOPO MIB utilizes non-volatile identifiers to distinguish 158 individual chassis and port components. These identifiers are 159 associated with external objects in order to relate topology information 160 to the existing managed objects. 162 In particular, an object from the Entity MIB or Interfaces MIB can be 163 used as the 'reference-point' for a connection component identifier. 165 5.3. Relationship to the Physical Topology MIB 167 The Physical Topology MIB [PTOPO] allows a PDP Agent to expose learned 168 physical topology information, using a standard MIB. PDP is intended to 169 fully support the PTOPO MIB. 171 5.4. Relationship to Entity MIB 173 The Entity MIB [RFC2037] allows the physical component inventory and 174 hierarchy to be identified. The chassis identifier strings passed in 175 PDP messages identify entPhysicalTable entries, and implementation of 176 the entPhysicalTable as specified in the Version 1 of the Entity MIB 177 [RFC2037], and implementation of the entPhysicalAlias object from 178 Version 2 of the Entity MIB [ENTITY-MIB], are required for SNMP agents 179 which also implement the PDP MIB. 181 5.5. Relationship to Interfaces MIB 183 The Interfaces MIB provides a standard mechanism for managing network 184 interfaces. The port identifier strings passed in PDP messages identify 185 ifTable (or entPhysicalTable) entries, and implementation of the ifTable 186 and ifXTable [RFC2233] are required for SNMP agents which also implement 187 the PDP MIB, for the ports which are represented in the Interfaces MIB. 189 6. PTOPO Discovery Protocol 191 This section defines a discovery protocol, suitable for supporting the 192 data requirements of the PTOPO MIB. 194 The PTOPO Discovery Protocol (PDP) is a media independent protocol 195 intended to be run on routers, bridges, access servers, switches, 196 repeaters, etc., allowing a PDP agent to learn SNMP reachability and 197 connection endpoint information from adjacent devices. 199 PDP runs on various media that support Subnetwork Access Protocol 200 (SNAP), and runs over the data-link layer only, allowing two systems 201 running different network layer protocols can learn about each other. 203 Each device configured with an active PDP Agent sends periodic messages 204 to a multicast MAC address on all physical interfaces enabled for PDP 205 transmission, and listens for PDP messages on the same set on 206 interfaces. Each PDP message contains information identifying the source 207 port as a PTOPO connection endpoint identifier. It also contains at 208 least one network address which can be used by an NMS to reach an SNMP 209 agent on the device (via the indicated source port). Each PDP message 210 contains a configurable time-to-live value, which tells the recipient 211 PDP agent when to discard each element of learned topology information. 213 6.1. Frame Encapsulation 215 The following open issues are under consideration by the working group: 217 An EtherType value must be selected to identify PDP messages 218 transmitted over DIX Ethernet, and IEEE 802.3,802.5 media types 219 (using LLC/SNAP encapsulation). 221 A multicast MAC address must be selected for the destination 222 address (DA) field in PDP messages transmitted over DIX Ethernet, 223 IEEE 802.3, and IEEE 802.5 media types. 225 6.2. PDP Forwarding 227 If at all possible, PDP agents are not supposed to forward PDP messages 228 received on any port. However, some devices, such as repeaters, cannot 229 examine each frame received on an interface or port. Such a device will 230 allow PDP messages to be retransmitted on one or more local ports, and 231 will transmit its own PDP messages on those ports as well. These agents 232 are termed 'forwarding' PDP agents. 234 PDP agents located on devices which examine each frame before 235 retransmitting it (e.g., routers and bridges), are expected to process 236 received PDP messages and not retransmit them on any local port. These 237 agents are termed 'non-forwarding' PDP agents. 239 An NMS may find physical topology information about the same physical 240 port, represented by several PTOPO agents. This may occur for one of 241 several reasons, including a mixture of forwarding and non-forwarding 242 PDP agents within a network. 244 6.3. PDP Message Format 246 The basic PDP packet consists of a header, followed by a variable number 247 of variable bindings in an ASN.1/BER encoded 'VarBindList', as indicated 248 in Figure 1. 250 +------------+--------------------------------------+ 251 | header | (ASN.1/BER) VarBindList | 252 +------------+--------------------------------------+ 254 [ Figure 1 -- Basic PDP Message Format ] 256 6.3.1. PDP Header Format 258 The PDP header is a 4 byte header, in network byte order, 259 containing 3 fields, as shown in figure 2: 261 0 1 2 3 262 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 263 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 264 | Version | Flags | Time To Live | 265 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 267 [ figure 2 -- PDP Message Format ] 269 The PDP header contains the following fields: 271 - Version 272 The PDP protocol version number, set to 0x01 for this version of 273 the protocol. 275 - Flags 276 The PDP flags field provide for future header extensions and keep 277 the header word-aligned for easier processing. No flag definition 278 bits are defined at this time. This field must be set to zero in 279 all version 1 PDP messages. 281 - Time to live 282 The number of seconds the information in this PDP message should be 283 regarded as valid by the recipient. Agents of the PTOPO MIB must 284 not return MIB information based on expired PDP messages. The 285 valid range is 0 to 65535 for this field. 287 6.3.2. PDP PDU Encoding 289 Following the PDP header is an SNMP varbind list encoded in ASN.1/BER, 290 (as defined in the SMIv2 document [RFC1902]), also referred to as the 291 PDP protocol data unit (PDP-PDU). The individual MIB instances contained 292 in a PDP PDU are referred to as PDP data elements. 294 The standard PDP data elements, defined in the PDP Data MIB, are encoded 295 as a VarBindList in each PDP message. This data enables a PDP agent to 296 implement the PTOPO MIB for connections terminating on the local 297 chassis. 299 This section defines the ASN.1 syntax specific to the PDP message. 300 Refer to the Protocol Operations specification [RFC1905] for a complete 301 definition of the 'VarBindList' construct. 303 Note that PDP places no constraints on which MIB instances may be 304 included in a particular VarBindList. 306 PDP-PDU DEFINITIONS ::= BEGIN 308 IMPORTS 309 MODULE-IDENTITY 310 FROM SNMPv2-SMI 311 VarBindList 312 FROM SNMPv2-PDU; 314 PDPv1-PDU MODULE-IDENTITY 315 LAST-UPDATED "9709150000Z" 316 ORGANIZATION "IETF PTOPOMIB Working Group" 317 CONTACT-INFO 318 "PTOPOMIB WG Discussion: 319 ptopo@3com.com 320 Subscription: 321 majordomo@3com.com 322 msg body: [un]subscribe ptopomib 324 Andy Bierman 325 Cisco Systems Inc. 326 170 West Tasman Drive 327 San Jose, CA 95134 328 408-527-3711 329 abierman@cisco.com 331 Keith McCloghrie 332 Cisco Systems Inc. 333 170 West Tasman Drive 334 San Jose, CA 95134 335 408-526-5260 336 kzm@cisco.com" 337 DESCRIPTION 338 "The definition module for version 1 of the PTOPO Discovery 339 Protocol PDU syntax." 340 ::= { experimental xx } 342 PDP-PDU ::= 343 SEQUENCE { 344 pdp-variable-bindings 345 VarBindList 346 } 348 END 350 6.4. PDP Data MIB 352 This section defines the standard data elements which may be contained 353 in PDP messages. These elements are defined as MIB objects, but are 354 only intended to be encoded into PDP PDUs, and not intended to be 355 instrumented by an SNMP agent. 357 The MIB defines six standard data elements: 359 - Chassis ID 360 - Chassis ID Type 361 - Port ID 362 - Port ID Type 363 - Management Address Type 364 - Management Address 366 6.4.1. Definitions 368 PDP-DATA-MIB DEFINITIONS ::= BEGIN 370 IMPORTS 371 MODULE-IDENTITY, OBJECT-TYPE, Integer32 372 FROM SNMPv2-SMI 373 MODULE-COMPLIANCE, OBJECT-GROUP 374 FROM SNMPv2-CONF 376 IANAAddrFamily, PtopoGenAddr, PtopoChassisIdType, 377 PtopoChassisId, PtopoPortIdType, PtopoPortId 378 FROM PTOPO-MIB; 380 pdpDataMIB MODULE-IDENTITY 381 LAST-UPDATED "9709150000Z" 382 ORGANIZATION "IETF PTOPOMIB Working Group" 383 CONTACT-INFO 384 "PTOPOMIB WG Discussion: 385 ptopo@3com.com 386 Subscription: 387 majordomo@3com.com 388 msg body: [un]subscribe ptopomib 390 Andy Bierman 391 Cisco Systems Inc. 392 170 West Tasman Drive 393 San Jose, CA 95134 394 408-527-3711 395 abierman@cisco.com 397 Keith McCloghrie 398 Cisco Systems Inc. 399 170 West Tasman Drive 400 San Jose, CA 95134 401 408-526-5260 402 kzm@cisco.com" 403 DESCRIPTION 404 "The MIB module for describing PDP data elements." 405 ::= { experimental xx } 407 pdpDataMIBObjects OBJECT IDENTIFIER ::= { pdpDataMIB 1 } 409 -- MIB groups 410 pdpDataElements OBJECT IDENTIFIER ::= { pdpDataMIBObjects 1 } 412 -- 413 -- *********************************************************** 414 -- 415 -- P D P D A T A E L E M E N T S 416 -- 417 -- *********************************************************** 418 -- 419 pdpChassisIdType OBJECT-TYPE 420 SYNTAX PtopoChassisIdType 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "This object identifies the type of chassis component 425 identifier contained in the pdpChassisId object, within a 426 given PDP message." 427 ::= { pdpDataElements 1 } 429 pdpChassisId OBJECT-TYPE 430 SYNTAX PtopoChassisId 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "This object identifies the chassis component of the 435 particular connection endpoint identifier containing the PDP 436 agent transmitting PDP messages. 438 If the chassis ID is unknown for the entry, then this object 439 will contain an empty string." 440 ::= { pdpDataElements 2 } 442 pdpPortIdType OBJECT-TYPE 443 SYNTAX PtopoPortIdType 444 MAX-ACCESS read-only 445 STATUS current 446 DESCRIPTION 447 "This object identifies the type of port component 448 identifier contained in the pdpPortId object, within a given 449 PDP message." 450 ::= { pdpDataElements 3 } 452 pdpPortId OBJECT-TYPE 453 SYNTAX PtopoPortId 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "This object identifies the port component of a particular 458 connection endpoint identifier, associated with the port 459 chosen for transmission of a given PDP message. 461 For PDP agents contained within repeaters or concentrators, 462 this object may identify the backplane component chosen for 463 transmission of a given PDP message, instead of a specific 464 port component (attached to the identified backplane). 466 If the port ID is unknown for the entry, then this object 467 will contain an empty string." 468 ::= { pdpDataElements 4 } 470 pdpMgmtAddrType OBJECT-TYPE 471 SYNTAX IANAAddrFamily 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "This object identifies the type of network address 476 contained in the pdpMgmtAddr object, within a given PDP 477 message." 478 ::= { pdpDataElements 5 } 480 pdpMgmtAddr OBJECT-TYPE 481 SYNTAX PtopoGenAddr 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "This object identifies a particular network address, 486 associated with an SNMP agent which contains additional 487 information pertaining to the connection endpoint identified 488 in a given PDP message. 490 If a management address is unknown for the endpoint 491 described in a given PDP message, then this object will 492 contain an empty string." 493 ::= { pdpDataElements 6 } 495 -- conformance information 496 pdpDataConformance OBJECT IDENTIFIER ::= { pdpDataMIB 2 } 498 pdpDataCompliances OBJECT IDENTIFIER ::= { pdpDataConformance 1 } 499 pdpDataGroups OBJECT IDENTIFIER ::= { pdpDataConformance 2 } 501 -- compliance statements 503 pdpDataCompliance MODULE-COMPLIANCE 504 STATUS current 505 DESCRIPTION 506 "The compliance statement for entities which implement the 507 PTOPO Discovery Protocol." 508 MODULE -- this module 509 MANDATORY-GROUPS { pdpPtopoDataGroup } 511 ::= { pdpDataCompliances 1 } 513 -- MIB groupings 515 pdpPtopoDataGroup OBJECT-GROUP 516 OBJECTS { 517 pdpChassisIdType, 518 pdpChassisId, 519 pdpPortIdType, 520 pdpPortId, 521 pdpMgmtAddrType, 522 pdpMgmtAddr 523 } 524 STATUS current 525 DESCRIPTION 526 "The collection of objects which identify connection 527 endpoint data elements, as used in the PTOPO Discovery 528 Protocol, and represented in the PTOPO MIB. 530 This group is mandatory for agents which implement the PTOPO 531 Discovery Protocol." 532 ::= { pdpDataGroups 1 } 534 END 536 6.5. Protocol Operation 538 An active PDP Agent must perform the following tasks: 540 - transmit PDP messages 541 - process received PDP messages 542 - maintain an instance of the PDP MIB 543 - maintain an instance of the PTOPO MIB 544 - maintain appropriate ifEntry and/or entPhysicalEntry instances 545 - implement ifAlias and/or entPhysicalAlias MIB objects 547 6.5.1. Protocol Initialization 549 Upon system reinitialization, the following tasks are performed by the 550 PDP agent: 552 Non-volatile configuration for the PDP MIB is retrieved if 553 applicable, otherwise appropriate default values are assigned to 554 all PDP configuration variables. 556 If pdpAdminStatus is equal to 'disabled(2)', then PDP 557 initialization is terminated (until such time that the 558 pdpAdminStatus object is set to 'enabled(1)'), otherwise continue. 560 Internal (implementation-specific) data structures are initialized. 561 such that appropriate local physical topology information and PDP 562 transmission parameters are set. 564 6.5.2. Message Encoding 566 This section does not assume a particular buffering strategy, and such 567 details are omitted. 569 6.5.2.1. Header Fields 571 The version field is set to one (0x01). 573 The flags field is set to zero (0x00). 575 The time-to-live field is set to the value obtained by the following 576 formula: 578 TTL = min(65535, (pdpMessageTxInterval * pdpMessageTxHoldMultiplier)) 580 6.5.2.2. VarBindList 582 Each message must contain one instance of each of the six mandatory 583 PDP-PDU data elements, defined in the PDP Data MIB. Additional data 584 elements may be added as maximum frame size permits. 586 ASN.1/BER encoding is defined in Version 2 of the Structure of 587 Management Information (SMIv2) [RFC1902], and is outside the scope of 588 this document. 590 6.5.3. Message Transmission 592 An active PDP agent must transmit a PDP message out each appropriate 593 port, once each message interval, as determined by the 594 pdpMessageTxInterval MIB object. Messages transmitted on repeater 595 devices may be sent for each repeater backplane, once per message 596 interval. Actual transmission intervals should be jittered to prevent 597 synchronization effects. 599 Note that the agent must suppress the transmission of multiple PDP 600 messages during a single message interval, in the event message 601 transmission cannot be restricted to a single port, but rather a group 602 of ports (e.g., a repeater device). 604 In this case, a single port in the port group should be selected (in an 605 implementation-specific manner) to represent the port group. Note that 606 an agent is encouraged to represent port groups as 'backplanes', in the 607 entPhysicalTable of the Entity MIB, rather than individual ports in 608 either the Entity MIB or Interfaces MIB. 610 Regarding the transmission of a single PDP message, for the indicated 611 physical interface contained in the local system: 613 The PDP agent checks for the existence of a pdpSuppressEntry for 614 the port. If an entry exists then this port is skipped, otherwise 615 continue. 617 The PDP message is encapsulated as appropriate for the port. 619 The MAC header is filled in with appropriate SA and DA and 620 EtherType fields. (Ignoring LLC/SNAP details). 622 The frame is transmitted or passed to a lower layer for 623 transmission. 625 The pdpStatsOutPkts counter is incremented for the indicated local 626 port. 628 6.5.4. Received Message Processing 630 An active PDP agent must process PDP messages received on each 631 appropriate port, as such messages arrive. 633 The following sections refer to the reception of a single PDP message, 634 for the indicated physical interface contained in the local system: 636 6.5.4.1. Header Fields 638 The PDP message and the chassis/port indices associated with the 639 receiving port are retrieved. 641 The PDP version and flags field are checked. The version should equal 642 one (0x01) and the flags should equal zero (0x00). If not, the 643 pdpStatsInErrors counter for the receiving port is incremented and 644 processing is terminated; otherwise continue. 646 6.5.4.2. VarBindList 648 The ASN.1/BER portion of the message is decoded. (Such parsing 649 techniques are beyond the scope of this document.) If this portion of 650 the PDP message is not properly encoded, as defined in the PDP Data MIB, 651 then the pdpStatsInErrors counter for the receiving port is incremented, 652 and processing is terminated; otherwise continue. 654 The list of data elements is examined. The agent must skip and ignore 655 PDU data elements unknown to the agent. If any of the mandatory data 656 elements are missing, then the pdpStatsInErrors counter for the 657 receiving port is incremented, and processing is terminated; otherwise 658 continue. 660 The pdpStatsInGoodPkts counter is incremented for the receiving port. 662 6.5.4.3. PTOPO MIB Update 664 If the time-to-live field in the PDP message header is zero then execute 665 this interface shutdown procedure, described below. Processing of the 666 PDP message is now complete. 668 If the time-to-live field is non-zero, then the appropriate 669 ptopoConnEntry is found or created, based on the data elements included 670 in the PDP message. If the indicated entry is dynamic (i.e., 671 ptopoConnIsStatic is true), then the current sysUpTime value is stored 672 in the ptopoConnLastVerifyTime field for the entry. 674 If a ptopoConnEntry was added then the ptopoConnTabInserts counter is 675 incremented. 677 If a ptopoConnEntry of one type was replaced with an entry of a 678 different type, then the ptopoConnTabReplaces counter is incremented. 680 If any ptopoConnEntry was added or deleted, or if information other than 681 the ptopoConnLastVerifyTime changed for any entry due to the processing 682 of this PDP message, then the ptopoLastChangeTime object is set with the 683 current sysUpTime, and a ptopoConfigChange trap event is generated. (See 684 the PTOPO MIB for information on ptopoConfigChange trap generation.) 686 6.5.5. Interface Shutdown Procedure 688 A special procedure exists for the case in which a PDP agent knows a 689 particular port is about to become non-operational. 691 Note that the pdpSuppressTable has precedence over these procedures, and 692 they are only executed if the indicated interface is not specified in 693 the pdpSuppressTable. 695 If any entries are deleted as a result of these procedures, the 696 ptopoConnTabDeletes counter is incremented for each deleted entry. 698 6.5.5.1. PDP Shutdown Transmission 700 In the event an interface, currently configured with PDP message 701 transmission enabled, either becomes disabled for PDP activity, or the 702 interface is administratively disabled, a final PDP message is 703 transmitted with a time to live value of zero (before the interface is 704 disabled). 706 In the event the pdpOperStatus is transitioning to the disabled state, 707 then this shutdown procedure should be executed for all local 708 interfaces. 710 6.5.5.2. PDP Shutdown Reception 712 After reception of a valid PDP message with a time-to-live value equal 713 to zero, the PDP Agent must remove all information in the PTOPO MIB 714 learned from the particular PDP agent, which is associated with the 715 indicated remote connection endpoint. 717 7. PTOPO Discovery Protocol MIB 719 This section defines the MIB used to configure PDP agent behavior. 721 7.1. Definitions 723 PDP-MIB DEFINITIONS ::= BEGIN 725 IMPORTS 726 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32 727 FROM SNMPv2-SMI 728 RowStatus 729 FROM SNMPv2-TC 730 MODULE-COMPLIANCE, OBJECT-GROUP 731 FROM SNMPv2-CONF 732 PhysicalIndex 733 FROM ENTITY-MIB; 735 pdpMIB MODULE-IDENTITY 736 LAST-UPDATED "9707300000Z" 737 ORGANIZATION "IETF PTOPOMIB Working Group" 738 CONTACT-INFO 739 "PTOPOMIB WG Discussion: 740 ptopo@3com.com 741 Subscription: 742 majordomo@3com.com 743 msg body: [un]subscribe ptopomib 745 Andy Bierman 746 Cisco Systems Inc. 747 170 West Tasman Drive 748 San Jose, CA 95134 749 408-527-3711 750 abierman@cisco.com 752 Keith McCloghrie 753 Cisco Systems Inc. 754 170 West Tasman Drive 755 San Jose, CA 95134 756 408-526-5260 757 kzm@cisco.com" 758 DESCRIPTION 759 "The MIB module for managing the Physical Topology Discovery 760 Protocol." 762 ::= { experimental xx } 764 pdpMIBObjects OBJECT IDENTIFIER ::= { pdpMIB 1 } 766 -- MIB groups 767 pdpConfig OBJECT IDENTIFIER ::= { pdpMIBObjects 1 } 768 pdpStats OBJECT IDENTIFIER ::= { pdpMIBObjects 2 } 770 PdpPortIdType ::= TEXTUAL-CONVENTION 771 STATUS current 772 DESCRIPTION 773 "The type of index value used to represent a port component. 775 If an object of this type has a value of 'ifIndexType(1)', 776 then the associated 'port ID' value represents an ifEntry, 777 with the same ifIndex value. 779 If an object of this type has a value of 780 'entPhysicalIndexType(2)', then the associated 'port ID' 781 value represents an entPhysicalEntry, with the same 782 entPhysicalIndex value." 783 SYNTAX INTEGER { 784 ifIndexType(1), 785 entPhysicalIndexType(2) 786 } 788 -- 789 -- *********************************************************** 790 -- 791 -- P D P C O N F I G 792 -- 793 -- *********************************************************** 794 -- 795 -- The Physical Topology Discovery Protocol Configuration Group 797 pdpAdminStatus OBJECT-TYPE 798 SYNTAX INTEGER { 799 enabled(1), 800 disabled(2) 801 } 802 MAX-ACCESS read-write 803 STATUS current 804 DESCRIPTION 805 "The administratively desired status of the the local PDP 806 agent. 808 If the agent is capable of storing non-volatile 809 configuration, then the value of this object must be 810 restored after a re-initialization of the management 811 system." 812 ::= { pdpConfig 1 } 814 pdpOperStatus OBJECT-TYPE 815 SYNTAX INTEGER { 816 enabled(1), 817 disabled(2) 818 } 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "The current operational status of the local PDP agent." 823 ::= { pdpConfig 2 } 825 pdpMessageTxInterval OBJECT-TYPE 826 SYNTAX Integer32 (5..32768) 827 UNITS "seconds" 828 MAX-ACCESS read-write 829 STATUS current 830 DESCRIPTION 831 "The interval at which PDP messages are transmitted on 832 behalf of this PDP agent. 834 If the agent is capable of storing non-volatile 835 configuration, then the value of this object must be 836 restored after a re-initialization of the management 837 system." 838 DEFVAL { 60 } 839 ::= { pdpConfig 3 } 841 pdpMessageTxHoldMultiplier OBJECT-TYPE 842 SYNTAX Integer32 (2..10) 843 MAX-ACCESS read-write 844 STATUS current 845 DESCRIPTION 846 "The time-to-live value expressed as a multiple of the 847 pdpMessageTxInterval object. The actual time-to-live value 848 used in PDP messages, transmitted on behalf of this PDP 849 agent, can be expressed by the following formula: 851 TTL = min(65535, (pdpMessageTxInterval * pdpMessageTxHoldMultiplier)) 853 For example, if the value of pdpMessageTxInterval is '60', 854 and the value of pdpMessageTxHoldMultiplier is '3', then the 855 value '180' is encoded in the TTL field in the PDP header. 857 If the agent is capable of storing non-volatile 858 configuration, then the value of this object must be 859 restored after a re-initialization of the management 860 system." 861 DEFVAL { 3 } 862 ::= { pdpConfig 4 } 864 -- 865 -- PdpSuppressTable: 866 -- Disable PDP activity on individual local ports 868 pdpSuppressTable OBJECT-TYPE 869 SYNTAX SEQUENCE OF PdpSuppressEntry 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "A table controlling PDP message transmission on individual 874 interfaces, ports, or backplanes." 875 ::= { pdpConfig 6 } 877 pdpSuppressEntry OBJECT-TYPE 878 SYNTAX PdpSuppressEntry 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "PDP message configuration information for a particular 883 port. The port must be contained in the same chassis as the 884 PDP agent. PDP messages will not be transmitted or received 885 on the indicated port, even if the port is enabled. 887 If the agent is capable of storing non-volatile 888 configuration, then each active pdpSuppressEntry must be 889 re-created after a re-initialization of the management 890 system. An agent should store enough information about the 891 associated entPhysicalEntry (e.g., entPhysicalAlias) or 892 ifEntry (e.g. ifAlias), to properly re-create the entry, 893 even if the pdpSuppressChassisId and/or pdpSuppressPortId 894 values change across a system re-initialization." 895 INDEX { 896 pdpSuppressChassisId, 897 pdpSuppressPortIdType, 898 pdpSuppressPortId 899 } 900 ::= { pdpSuppressTable 1 } 902 PdpSuppressEntry ::= SEQUENCE { 903 pdpSuppressChassisId PhysicalIndex, 904 pdpSuppressPortIdType PdpPortIdType, 905 pdpSuppressPortId Integer32, 906 pdpSuppressRowStatus RowStatus 907 } 909 pdpSuppressChassisId OBJECT-TYPE 910 SYNTAX PhysicalIndex 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "The entPhysicalIndex value used to identify the chassis 915 component associated with this entry. The associated 916 entPhysicalEntry must be active, and the associated 917 entPhysicalClass object must be equal to 'chassis(3)'." 918 ::= { pdpSuppressEntry 1 } 920 pdpSuppressPortIdType OBJECT-TYPE 921 SYNTAX PdpPortIdType 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "The type of index value contained in the associated 926 pdpSuppressPortId object." 927 ::= { pdpSuppressEntry 2 } 929 pdpSuppressPortId OBJECT-TYPE 930 SYNTAX Integer32 (1..2147483647) 931 MAX-ACCESS not-accessible 932 STATUS current 933 DESCRIPTION 934 "The index value used to identify the port component of this 935 entry. The type of index value depends on the 936 pdpSuppressPortIdType value for this entry. 938 If the associated pdpSuppressPortIdType is equal to 939 'ifIndexType(1)', then this pdpSuppressPortId represents an 940 ifEntry with the same ifIndex value. The associated ifEntry 941 must be active, and represent a physical interface on the 942 local chassis. 944 If the associated pdpSuppressPortIdType is equal to 945 'entPhysicalIndexType(2)', then this pdpSuppressPortId 946 represents an entPhysicalEntry with the same 947 entPhysicalIndex value. The associated entPhysicalEntry 948 must be active, and the associated entPhysicalClass object 949 must be equal to 'port(10)' or 'backplane(4)'. 951 Note that some devices, such as repeaters, cannot restrict 952 frame transmission to a single port, but rather to a group 953 of ports. In such an event, an agent will disable PDP 954 activity on all ports in the port group, if any of the 955 individual ports in the group are specified in this table." 956 ::= { pdpSuppressEntry 3 } 958 pdpSuppressRowStatus OBJECT-TYPE 959 SYNTAX RowStatus 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "The status of this entry." 964 ::= { pdpSuppressEntry 4 } 966 -- 967 -- *********************************************************** 968 -- 969 -- P D P S T A T S 970 -- 971 -- *********************************************************** 972 -- 973 -- PDP Stats Group 975 pdpStatsTable OBJECT-TYPE 976 SYNTAX SEQUENCE OF PdpStatsEntry 977 MAX-ACCESS not-accessible 978 STATUS current 979 DESCRIPTION 980 "A table containing PDP statistics for individual ports. 982 Entries are not required to exist in this table while the 983 pdpAdminStatus or pdpOperStatus objects are equal to 984 'disabled(2)'. 986 Entries are not required to exist in this table if a 987 corresponding entry (with identical index values) exists in 988 the pdpSuppressTable." 989 ::= { pdpStats 1 } 991 pdpStatsEntry OBJECT-TYPE 992 SYNTAX PdpStatsEntry 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "PDP message statistics for a particular port. The port 997 must be contained in the same chassis as the PDP agent." 998 INDEX { 999 pdpStatsChassisId, 1000 pdpStatsPortIdType, 1001 pdpStatsPortId 1002 } 1003 ::= { pdpStatsTable 1 } 1005 PdpStatsEntry ::= SEQUENCE { 1006 pdpStatsChassisId PhysicalIndex, 1007 pdpStatsPortIdType PdpPortIdType, 1008 pdpStatsPortId Integer32, 1009 pdpStatsInGoodPkts Counter32, 1010 pdpStatsInErrors Counter32, 1011 pdpStatsOutPkts Counter32 1012 } 1014 pdpStatsChassisId OBJECT-TYPE 1015 SYNTAX PhysicalIndex 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION 1019 "The entPhysicalIndex value used to identify the chassis 1020 component associated with this entry. The associated 1021 entPhysicalEntry must be active, and the associated 1022 entPhysicalClass object must be equal to 'chassis(3)'." 1023 ::= { pdpStatsEntry 1 } 1025 pdpStatsPortIdType OBJECT-TYPE 1026 SYNTAX PdpPortIdType 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "The type of index value contained in the associated 1031 pdpStatsPortId object." 1032 ::= { pdpStatsEntry 2 } 1034 pdpStatsPortId OBJECT-TYPE 1035 SYNTAX Integer32 (1..2147483647) 1036 MAX-ACCESS not-accessible 1037 STATUS current 1038 DESCRIPTION 1039 "The index value used to identify the port component of this 1040 entry. The type of index value depends on the 1041 pdpStatsPortType value for this entry. 1043 If the associated pdpStatsPortIdType is equal to 1044 'ifIndexType(1)', then this pdpStatsPortId represents an 1045 ifEntry with the same ifIndex value. The associated ifEntry 1046 must be active, and represent a physical interface on the 1047 local chassis. 1049 If the associated pdpStatsPortIdType is equal to 1050 'entPhysicalIndexType(2)', then this pdpStatsPortId 1051 represents an entPhysicalEntry with the same 1052 entPhysicalIndex value. The associated entPhysicalEntry 1053 must be active, and the associated entPhysicalClass object 1054 must be equal to 'port(10)' or 'backplane(4)'." 1055 ::= { pdpStatsEntry 3 } 1057 pdpStatsInGoodPkts OBJECT-TYPE 1058 SYNTAX Counter32 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The number of valid PDP messages received by this PDP agent 1063 on the indicated port, while this PDP agent is enabled." 1064 ::= { pdpStatsEntry 4 } 1066 pdpStatsInErrors OBJECT-TYPE 1067 SYNTAX Counter32 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The number of invalid PDP messages received by this PDP 1072 agent on the indicated port, while this PDP agent is 1073 enabled. A PDP message may be invalid for several reasons, 1074 including: 1075 - invalid MAC header; length or DA fields 1076 - invalid PDP header; version or flags fields 1077 - invalid PDP VarBindList ASN.1/BER encoding 1078 - invalid or missing PDP VarBindList data elements" 1079 ::= { pdpStatsEntry 5 } 1081 pdpStatsOutPkts OBJECT-TYPE 1082 SYNTAX Counter32 1083 MAX-ACCESS read-only 1084 STATUS current 1085 DESCRIPTION 1086 "The number of PDP messages transmitted by this PDP agent on 1087 the indicated port." 1088 ::= { pdpStatsEntry 6 } 1090 -- conformance information 1091 pdpConformance OBJECT IDENTIFIER ::= { pdpMIB 2 } 1093 pdpCompliances OBJECT IDENTIFIER ::= { pdpConformance 1 } 1094 pdpGroups OBJECT IDENTIFIER ::= { pdpConformance 2 } 1096 -- compliance statements 1098 pdpCompliance MODULE-COMPLIANCE 1099 STATUS current 1100 DESCRIPTION 1101 "The compliance statement for SNMP entities which implement 1102 the PDP MIB." 1103 MODULE -- this module 1104 MANDATORY-GROUPS { pdpConfigGroup, pdpStatsGroup } 1106 ::= { pdpCompliances 1 } 1108 -- MIB groupings 1110 pdpConfigGroup OBJECT-GROUP 1111 OBJECTS { 1112 pdpAdminStatus, 1113 pdpOperStatus, 1114 pdpMessageTxInterval, 1115 pdpMessageTxHoldMultiplier, 1116 pdpSuppressRowStatus 1117 } 1118 STATUS current 1119 DESCRIPTION 1120 "The collection of objects which are used to configure the 1121 PTOPO Discovery Protocol implementation behavior. 1123 This group is mandatory for agents which implement the PTOPO 1124 Discovery Protocol." 1125 ::= { pdpGroups 1 } 1127 pdpStatsGroup OBJECT-GROUP 1128 OBJECTS { 1129 pdpStatsInGoodPkts, 1130 pdpStatsInErrors, 1131 pdpStatsOutPkts 1132 } 1133 STATUS current 1134 DESCRIPTION 1135 "The collection of objects which are used to represent PTOPO 1136 Discovery Protocol statistics. 1138 This group is mandatory for agents which implement the PTOPO 1139 Discovery Protocol." 1140 ::= { pdpGroups 2 } 1142 END 1144 8. Intellectual Property 1146 The IETF takes no position regarding the validity or scope of any 1147 intellectual property or other rights that might be claimed to pertain 1148 to the implementation or use of the technology described in this 1149 document or the extent to which any license under such rights might or 1150 might not be available; neither does it represent that it has made any 1151 effort to identify any such rights. Information on the IETF's 1152 procedures with respect to rights in standards-track and standards- 1153 related documentation can be found in BCP-11. Copies of claims of 1154 rights made available for publication and any assurances of licenses to 1155 be made available, or the result of an attempt made to obtain a general 1156 license or permission for the use of such proprietary rights by 1157 implementors or users of this specification can be obtained from the 1158 IETF Secretariat." 1160 The IETF invites any interested party to bring to its attention any 1161 copyrights, patents or patent applications, or other proprietary rights 1162 which may cover technology that may be required to practice this 1163 standard. Please address the information to the IETF Executive 1164 Director. 1166 The IETF has been notified of intellectual property rights claimed in 1167 regard to some or all of the specification contained in this document. 1168 For more information consult the online list of claimed rights. 1170 9. Acknowledgements 1172 The PTOPO Discovery Protocol is a product of the IETF PTOPOMIB Working 1173 Group. 1175 10. References 1177 [ENTITY-MIB] 1178 McCloghrie, K., and A. Bierman, "Entity MIB using SMIv2 (Version 1179 2)", draft-ietf-entmib-v2-01.txt, Cisco Systems, November 1998. 1181 [PTOPO] 1182 Bierman, A., and K. Jones, "Physical Topology MIB", draft-ietf- 1183 ptopomib-mib-01.txt, Cisco Systems, Bay Networks, November 1998. 1185 [RFC1155] 1186 Rose, M., and K. McCloghrie, "Structure and Identification of 1187 Management Information for TCP/IP-based Internets", RFC 1155, 1188 Performance Systems International, Hughes LAN Systems, May 1990. 1190 [RFC1157] 1191 Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1192 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1193 International, Performance Systems International, MIT Laboratory 1194 for Computer Science, May 1990. 1196 [RFC1212] 1197 Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1198 Performance Systems International, Hughes LAN Systems, March 1991. 1200 [RFC1215] 1201 M. Rose, "A Convention for Defining Traps for use with the SNMP", 1202 RFC 1215, Performance Systems International, March 1991. 1204 [RFC1901] 1205 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1206 Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 1207 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1208 Inc., International Network Services, January 1996. 1210 [RFC1902] 1211 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1212 Waldbusser, "Structure of Management Information for version 2 of 1213 the Simple Network Management Protocol (SNMPv2)", RFC 1902, SNMP 1214 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1215 International Network Services, January 1996. 1217 [RFC1903] 1218 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1219 Waldbusser, "Textual Conventions for version 2 of the Simple 1220 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 1221 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1222 International Network Services, January 1996. 1224 [RFC1904] 1225 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1226 Waldbusser, "Conformance Statements for version 2 of the Simple 1227 Network Management Protocol (SNMPv2)", RFC 1904, SNMP Research, 1228 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1229 International Network Services, January 1996. 1231 [RFC1905] 1232 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1233 Waldbusser, "Protocol Operations for Version 2 of the Simple 1234 Network Management Protocol (SNMPv2)", RFC 1905, SNMP Research, 1235 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1236 International Network Services, January 1996. 1238 [RFC1906] 1239 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1240 Waldbusser, "Transport Mappings for Version 2 of the Simple Network 1241 Management Protocol (SNMPv2)"", RFC 1906, SNMP Research, Inc., 1242 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1243 Network Services, January 1996. 1245 [RFC2037] 1246 McCloghrie, K., and A. Bierman, "Entity MIB using SMIv2", RFC 2037, 1247 Cisco Systems, October 1996. 1249 [RFC2233] 1250 McCloghrie, K., and F. Kastenholtz, "The Interfaces Group MIB using 1251 SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997. 1253 [RFC2271] 1254 Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1255 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1256 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1257 January 1998. 1259 [RFC2272] 1260 Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1261 Processing and Dispatching for the Simple Network Management 1262 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1263 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1265 [RFC2273] 1266 Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1267 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1268 Systems, January 1998. 1270 [RFC2274] 1271 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1272 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1273 2274, IBM T. J. Watson Research, January 1998. 1275 [RFC2275] 1276 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1277 Control Model (VACM) for the Simple Network Management Protocol 1278 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1279 Cisco Systems, Inc., January 1998. 1281 11. Security Considerations 1283 This protocol and associated MIB can expose the existence of physical 1284 components, MAC layer addresses, and network layer addresses, pertaining 1285 to devices within a given network. A network administrator may wish to 1286 restrict access to this management information, using SNMP access 1287 control mechanisms, and restrict PDP message processing to a particular 1288 set of ports, by configuring entries in the pdpSuppressTable. 1290 12. Authors' Addresses 1292 Andy Bierman 1293 Cisco Systems, Inc. 1294 170 West Tasman Drive 1295 San Jose, CA USA 95134 1296 Phone: +1 408-527-3711 1297 Email: abierman@cisco.com 1299 Keith McCloghrie 1300 Cisco Systems, Inc. 1301 170 West Tasman Drive 1302 San Jose, CA USA 95134 1303 Phone: +1 408-526-5260 1304 Email: kzm@cisco.com 1306 13. Full Copyright Statement 1308 Copyright (C) The Internet Society (1998). All Rights Reserved. 1310 This document and translations of it may be copied and furnished to 1311 others, and derivative works that comment on or otherwise explain it or 1312 assist in its implementation may be prepared, copied, published and 1313 distributed, in whole or in part, without restriction of any kind, 1314 provided that the above copyright notice and this paragraph are included 1315 on all such copies and derivative works. However, this document itself 1316 may not be modified in any way, such as by removing the copyright notice 1317 or references to the Internet Society or other Internet organizations, 1318 except as needed for the purpose of developing Internet standards in 1319 which case the procedures for copyrights defined in the Internet 1320 Standards process must be followed, or as required to translate it into 1321 languages other than English. 1323 The limited permissions granted above are perpetual and will not be 1324 revoked by the Internet Society or its successors or assigns. 1326 This document and the information contained herein is provided on an "AS 1327 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1328 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1329 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1330 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1331 FITNESS FOR A PARTICULAR PURPOSE."