idnits 2.17.1 draft-ietf-ptopomib-pdp-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** 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 Abstract 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 5 instances of too long lines in the document, the longest one being 9 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1002 has weird spacing: '...', then this ...' == Line 1107 has weird spacing: '...', then this ...' -- 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 (17 September 1997) is 9718 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: 'TBD' is mentioned on line 581, but not defined == Outdated reference: A later version (-01) exists of draft-bierman-entmib-compid-00 -- Possible downref: Normative reference to a draft: ref. 'ENTITY-EXT' == Outdated reference: A later version (-05) exists of draft-ietf-ptopomib-mib-00 ** Downref: Normative reference to an Informational draft: draft-ietf-ptopomib-mib (ref. 'PTOPO') ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Obsolete normative reference: RFC 1573 (Obsoleted by RFC 2233) ** Obsolete normative reference: RFC 1902 (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2037 (Obsoleted by RFC 2737) Summary: 19 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Draft PTOPO Discovery Protocol and MIB September 1997 4 5 Physical Topology Discovery Protocol and MIB 7 17 September 1997 9 Andy Bierman 10 Cisco Systems Inc. 11 abierman@cisco.com 13 Keith McCloghrie 14 Cisco Systems Inc. 15 kzm@cisco.com 17 Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, and 21 its working groups. Note that other groups may also distribute working 22 documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet- Drafts as reference material 27 or to cite them other than as ``work in progress.'' 29 To learn the current status of any Internet-Draft, please check the 30 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 31 Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), 32 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 34 1. Introduction 36 This memo defines an experimental protocol, and an experimental portion 37 of the Management Information Base (MIB) for use with network management 38 protocols in the Internet community. In particular, it describes a 39 physical topology discovery protocol and managed objects used for 40 Draft PTOPO Discovery Protocol and MIB September 1997 42 managing the protocol. 44 2. The SNMP Network Management Framework 46 The SNMP Network Management Framework presently consists of three major 47 components. They are: 49 o the SMI, described in RFC 1902 [RFC1902], - the mechanisms used for 50 describing and naming objects for the purpose of management. 52 o the MIB-II, STD 17, RFC 1213 [RFC1213], - the core set of managed 53 objects for the Internet suite of protocols. 55 o the protocol, RFC 1157 [RFC1157] and/or RFC 1905 [RFC1905], - the 56 protocol for accessing managed information. 58 Textual conventions are defined in RFC 1903 [RFC1903], and conformance 59 statements are defined in RFC 1904 [RFC1904]. 61 The Framework permits new objects to be defined for the purpose of 62 experimentation and evaluation. 64 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. A 65 semantically identical MIB conforming to the SNMPv1 SMI can be produced 66 through the appropriate translation. 68 2.1. Object Definitions 70 Managed objects are accessed via a virtual information store, termed the 71 Management Information Base or MIB. Objects in the MIB are defined 72 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 73 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 74 an administratively assigned name. The object type together with an 75 object instance serves to uniquely identify a specific instantiation of 76 the object. For human convenience, we often use a textual string, 77 termed the descriptor, to refer to the object type. 79 3. Overview 81 There is a need for a standardized way of representing the physical 82 network connections pertaining to a given management domain. A 83 standardized discovery mechanism is also required to increase the 84 Draft PTOPO Discovery Protocol and MIB September 1997 86 likelihood of multi-vendor interoperability of such physical topology 87 management information. 89 This document specifies a discovery protocol, suitable for use with the 90 Physical Topology MIB [PTOPO]. 92 3.1. Terms 94 Some terms are used throughout this document: 96 SNMP Agent 97 This term refers to an SNMP agent co-located with a particular PDP 98 Agent. Specifically, it refers to the SNMP Agent providing PDP MIB, 99 Entity MIB, Interfaces MIB, and possibly PTOPO MIB support for a 100 particular chassis. 102 PDP Agent 103 This term refers to a software entity which implements the PTOPO 104 Discovery Protocol for a particular chassis. 106 3.2. Persistent Identifiers 108 The PTOPO MIB utilizes non-volatile identifiers to distinguish 109 individual chassis and port components. These identifiers are 110 associated with external objects in order to relate topology information 111 to the existing managed objects. 113 In particular, an object from the Entity MIB or Interfaces MIB can be 114 used as the 'reference-point' for a connection component identifier. 116 3.3. Relationship to the Physical Topology MIB 118 The Physical Topology MIB [PTOPO] allows a PDP Agent to expose learned 119 physical topology information, using a standard MIB. PDP is intended to 120 fully support the PTOPO MIB. 122 3.4. Relationship to Entity MIB 124 The Entity MIB [RFC2037] allows the physical component inventory and 125 hierarchy to be identified. The chassis identifier strings passed in 126 PDP messages identify entPhysicalTable entries, and implementation of 127 Draft PTOPO Discovery Protocol and MIB September 1997 129 the entPhysicalTable and entPhysicalXTable (found in 'Entity MIB 130 Extensions for Persistent Component Identification' [ENTITY-EXT]) are 131 required for SNMP agents which also implement the PDP MIB. 133 3.5. Relationship to Interfaces MIB 135 The Interfaces MIB provides a standard mechanism for managing network 136 interfaces. The port identifier strings passed in PDP messages identify 137 ifTable (or entPhysicalTable) entries, and implementation of the ifTable 138 and ifXTable [RFC1573] are required for SNMP agents which also implement 139 the PDP MIB, for the ports which are represented in the Interfaces MIB. 141 4. PTOPO Discovery Protocol 143 This section defines a discovery protocol, suitable for supporting the 144 data requirements of the PTOPO MIB. 146 The PTOPO Discovery Protocol (PDP) is a media independent protocol 147 intended to be run on routers, bridges, access servers, switches, 148 repeaters, etc., allowing a PDP agent to learn SNMP reachability and 149 connection endpoint information from adjacent devices. 151 PDP runs on various media that support Subnetwork Access Protocol 152 (SNAP), and runs over the data-link layer only, allowing two systems 153 running different network layer protocols can learn about each other. 155 Each device configured with an active PDP Agent sends periodic messages 156 to a multicast MAC address on all physical interfaces enabled for PDP 157 transmission, and listens for PDP messages on the same set on 158 interfaces. Each PDP message contains information identifying the source 159 port as a PTOPO connection endpoint identifier. It also contains at 160 least one network address which can be used by an NMS to reach an SNMP 161 agent on the device (via the indicated source port). Each PDP message 162 contains a configurable time-to-live value, which tells the recipient 163 PDP agent when to discard each element of learned topology information. 165 4.1. Frame Encapsulation 167 The following open issues are under consideration by the working group: 169 An EtherType value must be selected to identify PDP messages 170 transmitted over DIX Ethernet, and IEEE 802.3,802.5 media types 172 Draft PTOPO Discovery Protocol and MIB September 1997 174 (using LLC/SNAP encapsulation). 176 A multicast MAC address must be selected for the destination 177 address (DA) field in PDP messages transmitted over DIX Ethernet, 178 IEEE 802.3, and IEEE 802.5 media types. 180 4.2. PDP Forwarding 182 If at all possible, PDP agents are not supposed to forward PDP messages 183 received on any port. However, some devices, such as repeaters, cannot 184 examine each frame received on an interface or port. Such a device will 185 allow PDP messages to be retransmitted on one or more local ports, and 186 will transmit its own PDP messages on those ports as well. These agents 187 are termed 'forwarding' PDP agents. 189 PDP agents located on devices which examine each frame before 190 retransmitting it (e.g., routers and bridges), are expected to process 191 received PDP messages and not retransmit them on any local port. These 192 agents are termed 'non-forwarding' PDP agents. 194 An NMS may find physical topology information about the same physical 195 port, represented by several PTOPO agents. This may occur for one of 196 several reasons, including a mixture of forwarding and non-forwarding 197 PDP agents within a network. 199 4.3. PDP Message Format 201 The basic PDP packet consists of a header, followed by a variable number 202 of variable bindings in an ASN.1/BER encoded 'VarBindList', as indicated 203 in Figure 1. 205 +------------+--------------------------------------+ 206 | header | (ASN.1/BER) VarBindList | 207 +------------+--------------------------------------+ 209 [ Figure 1 -- Basic PDP Message Format ] 211 4.3.1. PDP Header Format 213 The PDP header is a 6 byte header, in network byte order, 214 containing 4 fields, as shown in figure 2: 216 Draft PTOPO Discovery Protocol and MIB September 1997 218 0 1 2 3 219 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 220 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 221 | Version | Flags | Time To Live | 222 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 224 0 1 225 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 226 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 227 | Checksum | 228 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 230 [ figure 2 -- PDP Message Format ] 232 The PDP header contains the following fields: 234 - Version 235 The PDP protocol version number, set to 0x01 for this version of 236 the protocol. 238 - Flags 239 The PDP flags field provide for future header extensions and keep 240 the header word-aligned for easier processing. No flag definition 241 bits are defined at this time. This field must be set to zero in 242 all version 1 PDP messages. 244 - Time to live 245 The number of seconds the information in this PDP message should be 246 regarded as valid by the recipient. Agents of the PTOPO MIB must 247 not return MIB information based on expired PDP messages. The 248 valid range is 0 to 65535 for this field. 250 - Checksum 251 An optional one's complement of the one's complement checksum of 252 the entire PDP message. An entity generating PDP messages shall set 253 this field to zero if the checksum is omitted. An entity receiving 254 PDP messages must skip the checksum validation if this field is 255 zero, otherwise the checksum is calculated and compared to the 256 value of this field. Messages containing incorrect checksums must 257 be ignored. (See section 4.5.2.3 for a detailed description of 258 checksum processing.) 260 Draft PTOPO Discovery Protocol and MIB September 1997 262 4.3.2. PDP PDU Encoding 264 Following the PDP header is an SNMP varbind list encoded in ASN.1/BER 265 [ref. TBD], also referred to as the PDP protocol data unit (PDP-PDU). 266 The invidual MIB instances contained in a PDP PDU are referred to as PDP 267 data elements. 269 The standard PDP data elements, defined in the PDP Data MIB, are encoded 270 as a VarBindList in each PDP message. This data enables a PDP agent to 271 implement the PTOPO MIB for connections terminating on the local 272 chassis. 274 This section defines the ASN.1 syntax specific to the PDP message. 275 Refer to the Protocol Operations specification [RFC1905] for a complete 276 definition of the 'VarBindList' construct. 278 Note that PDP places no constraints on which MIB instances may be 279 included in a particular VarBindList. 281 PDP-PDU DEFINITIONS ::= BEGIN 283 IMPORTS 284 MODULE-IDENTITY 285 FROM SNMPv2-SMI 286 VarBindList 287 FROM SNMPv2-PDU; 289 PDPv1-PDU MODULE-IDENTITY 290 LAST-UPDATED "9709150000Z" 291 ORGANIZATION "IETF PTOPOMIB Working Group" 292 CONTACT-INFO 293 "PTOPOMIB WG Discussion: 294 ptopo@3com.com 295 Subscription: 296 majordomo@3com.com 297 msg body: [un]subscribe ptopomib 299 Andy Bierman 300 Cisco Systems Inc. 301 170 West Tasman Drive 302 San Jose, CA 95134 303 408-527-3711 304 abierman@cisco.com 306 Keith McCloghrie 308 Draft PTOPO Discovery Protocol and MIB September 1997 310 Cisco Systems Inc. 311 170 West Tasman Drive 312 San Jose, CA 95134 313 408-526-5260 314 kzm@cisco.com" 315 DESCRIPTION 316 "The definition module for version 1 of the PTOPO Discovery 317 Protocol PDU syntax." 318 ::= { experimental xx } 320 PDP-PDU ::= 321 SEQUENCE { 322 pdp-variable-bindings 323 VarBindList 324 } 326 END 328 4.4. PDP Data MIB 330 This section defines the standard data elements which may be contained 331 in PDP messages. These elements are defined as MIB objects, but are 332 only intended to be encoded into PDP PDUs, and not intended to be 333 instrumented by an SNMP agent. 335 The MIB defines six standard data elements: 337 - Chassis ID 338 - Chassis ID Type 339 - Port ID 340 - Port ID Type 341 - Management Address Type 342 - Management Address 344 4.4.1. Definitions 346 PDP-DATA-MIB DEFINITIONS ::= BEGIN 348 IMPORTS 349 MODULE-IDENTITY, OBJECT-TYPE, Integer32 350 FROM SNMPv2-SMI 351 MODULE-COMPLIANCE, OBJECT-GROUP 352 FROM SNMPv2-CONF 354 Draft PTOPO Discovery Protocol and MIB September 1997 356 IANAAddrFamily, PtopoGenAddr, PtopoChassisIdType, 357 PtopoChassisId, PtopoPortIdType, PtopoPortId 358 FROM PTOPO-MIB; 360 pdpDataMIB MODULE-IDENTITY 361 LAST-UPDATED "9709150000Z" 362 ORGANIZATION "IETF PTOPOMIB Working Group" 363 CONTACT-INFO 364 "PTOPOMIB WG Discussion: 365 ptopo@3com.com 366 Subscription: 367 majordomo@3com.com 368 msg body: [un]subscribe ptopomib 370 Andy Bierman 371 Cisco Systems Inc. 372 170 West Tasman Drive 373 San Jose, CA 95134 374 408-527-3711 375 abierman@cisco.com 377 Keith McCloghrie 378 Cisco Systems Inc. 379 170 West Tasman Drive 380 San Jose, CA 95134 381 408-526-5260 382 kzm@cisco.com" 383 DESCRIPTION 384 "The MIB module for describing PDP data elements." 385 ::= { experimental xx } 387 pdpDataMIBObjects OBJECT IDENTIFIER ::= { pdpDataMIB 1 } 389 -- MIB groups 390 pdpDataElements OBJECT IDENTIFIER ::= { pdpDataMIBObjects 1 } 392 -- 393 -- *********************************************************** 394 -- 395 -- P D P D A T A E L E M E N T S 396 -- 397 -- *********************************************************** 398 -- 399 Draft PTOPO Discovery Protocol and MIB September 1997 401 pdpChassisIdType OBJECT-TYPE 402 SYNTAX PtopoChassisIdType 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "This object identifies the type of chassis component 407 identifier contained in the pdpChassisId object, within a 408 given PDP message." 409 ::= { pdpDataElements 1 } 411 pdpChassisId OBJECT-TYPE 412 SYNTAX PtopoChassisId 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "This object identifies the chassis component of the 417 particular connection endpoint identifier containing the PDP 418 agent transmitting PDP messages. 420 If the chassis ID is unknown for the entry, then this object 421 will contain an empty string." 422 ::= { pdpDataElements 2 } 424 pdpPortIdType OBJECT-TYPE 425 SYNTAX PtopoPortIdType 426 MAX-ACCESS read-only 427 STATUS current 428 DESCRIPTION 429 "This object identifies the type of port component 430 identifier contained in the pdpPortId object, within a given 431 PDP message." 432 ::= { pdpDataElements 3 } 434 pdpPortId OBJECT-TYPE 435 SYNTAX PtopoPortId 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "This object identifies the port component of a particular 440 connection endpoint identifier, associated with the port 441 chosen for transmission of a given PDP message. 443 For PDP agents contained within repeaters or concentrators, 444 this object may identify the backplane component chosen for 445 transmission of a given PDP message, instead of a specific 447 Draft PTOPO Discovery Protocol and MIB September 1997 449 port component (attached to the identified backplane). 451 If the port ID is unknown for the entry, then this object 452 will contain an empty string." 453 ::= { pdpDataElements 4 } 455 pdpMgmtAddrType OBJECT-TYPE 456 SYNTAX IANAAddrFamily 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "This object identifies the type of network address 461 contained in the pdpMgmtAddr object, within a given PDP 462 message." 463 ::= { pdpDataElements 5 } 465 pdpMgmtAddr OBJECT-TYPE 466 SYNTAX PtopoGenAddr 467 MAX-ACCESS read-only 468 STATUS current 469 DESCRIPTION 470 "This object identifies a particular network address, 471 associated with an SNMP agent which contains additional 472 information pertaining to the connection endpoint identified 473 in a given PDP message. 475 If a management address is unknown for the endpoint 476 described in a given PDP message, then this object will 477 contain an empty string." 478 ::= { pdpDataElements 6 } 480 -- conformance information 481 pdpDataConformance OBJECT IDENTIFIER ::= { pdpDataMIB 2 } 483 pdpDataCompliances OBJECT IDENTIFIER ::= { pdpDataConformance 1 } 484 pdpDataGroups OBJECT IDENTIFIER ::= { pdpDataConformance 2 } 486 -- compliance statements 488 pdpDataCompliance MODULE-COMPLIANCE 489 STATUS current 490 DESCRIPTION 491 "The compliance statement for entities which implement the 493 Draft PTOPO Discovery Protocol and MIB September 1997 495 PTOPO Discovery Protocol." 496 MODULE -- this module 497 MANDATORY-GROUPS { pdpPtopoDataGroup } 499 ::= { pdpDataCompliances 1 } 501 -- MIB groupings 503 pdpPtopoDataGroup OBJECT-GROUP 504 OBJECTS { 505 pdpChassisIdType, 506 pdpChassisId, 507 pdpPortIdType, 508 pdpPortId, 509 pdpMgmtAddrType, 510 pdpMgmtAddr 511 } 512 STATUS current 513 DESCRIPTION 514 "The collection of objects which identify connection 515 endpoint data elements, as used in the PTOPO Discovery 516 Protocol, and represented in the PTOPO MIB. 518 This group is mandatory for agents which implement the PTOPO 519 Discovery Protocol." 520 ::= { pdpDataGroups 1 } 522 END 524 4.5. Protocol Operation 526 An active PDP Agent must perform the following tasks: 528 - transmit PDP messages 529 - process received PDP messages 530 - maintain an instance of the PDP MIB 531 - maintain an instance of the PTOPO MIB 532 - maintain appropriate ifEntry and/or entPhysicalEntry instances 533 - implement ifAlias and/or entPhysicalAlias MIB objects 535 Draft PTOPO Discovery Protocol and MIB September 1997 537 4.5.1. Protocol Initialization 539 Upon system reinitialization, the following tasks are performed by the 540 PDP agent: 542 Non-volatile configuration for the PDP MIB is retrieved if 543 applicable, otherwise appropriate default values are assigned to 544 all PDP configuration variables. 546 If pdpAdminStatus is equal to 'disabled(2)', then PDP 547 initialization is terminated (until such time that the 548 pdpAdminStatus object is set to 'enabled(1)'), otherwise continue. 550 Internal (implementation-specific) data structures are initialized. 551 such that appropriate local physical topology information and PDP 552 transmission parameters are set. 554 4.5.2. Message Encoding 556 This section does not assume a particular buffering strategy, and such 557 details are omitted. 559 4.5.2.1. Header Fields 561 The version field is set to one (0x01). 563 The flags field is set to zero (0x00). 565 The time-to-live field is set to the value obtained by the following 566 formula: 568 TTL = min(65535, (pdpMessageTxInterval * pdpMessageTxHoldMultiplier)) 570 The checksum is set to zero (0x0000). If checksums are implemented by 571 the PDP agent, then this field will be set again later. 573 4.5.2.2. VarBindList 575 Each message must contain one instance of each of the six mandatory 576 PDP-PDU data elements, defined in the PDP Data MIB. Additional data 577 elements may be added as maximum frame size permits. 579 Draft PTOPO Discovery Protocol and MIB September 1997 581 ASN.1/BER encoding is defined in [TBD], and is outside the scope of this 582 document. 584 4.5.2.3. Checksum 586 If checksums are implemented by the PDP agent, then a simple UDP-style 587 checksum is calculated for the PDP message (i.e., concatenated header 588 and ASN.1/BER encoded VarBindList). 590 If the PDP message length is odd, then a zero-valued octet is appended 591 to the PDP message. This padding is done only for PDP checksum 592 calculation, and the additional octet is not transmitted with the PDP 593 message. 595 A 16-bit unsigned integer temporary variable is initialized to zero. 597 Each unsigned 16-bit word of the PDP message is added to the temporary 598 variable, and any overflows are ignored. 600 The ones-complement (i.e., all bits reversed) of the temporary variable 601 is written to the checksum field, in network byte order. 603 4.5.3. Message Transmission 605 An active PDP agent must transmit a PDP message out each appropriate 606 port, once each message interval, as determined by the 607 pdpMessageTxInterval MIB object. Messages transmitted on repeater 608 devices may be sent for each repeater backplane, once per message 609 interval. Actual transmission intervals should be jittered to prevent 610 synchronization effects. 612 Regarding the transmission of a single PDP message, for the indicated 613 physical interface contained in the local system: 615 The PDP agent checks for the existence of a pdpSuppressEntry for 616 the port. If an entry exists then this port is skipped, otherwise 617 continue. 619 The PDP message is encapsulated as appropriate for the port. 621 The MAC header is filled in with appropriate SA and DA and 622 EtherType fields. (Ignoring LLC/SNAP details). 624 Draft PTOPO Discovery Protocol and MIB September 1997 626 The frame is transmitted or passed to a lower layer for 627 transmission. 629 The pdpStatsOutPkts counter is incremented for the indicated local 630 port. 632 4.5.4. Received Message Processing 634 An active PDP agent must process PDP messages received on each 635 appropriate port, as such messages arrive. 637 The following sections refer to the reception of a single PDP message, 638 for the indicated physical interface contained in the local system: 640 4.5.4.1. Header Fields 642 The PDP message and the chassis/port indices associated with the 643 receiving port are retrieved. 645 The PDP version and flags field are checked. The version should equal 646 one (0x01) and the flags should equal zero (0x00). If not, the 647 pdpStatsInErrors counter for the receiving port is incremented and 648 processing is terminated; otherwise continue. 650 4.5.4.2. Checksum 652 If the checksum field is zero then continue, otherwise verify the 653 checksum with the following procedure: 655 The value of checksum is saved in a temporary variable. 657 The checksum field is set to zero. 659 If the PDP message length is odd, then a zero-valued octet is 660 conceptually appended to the PDP message. This padding is done only 661 for PDP checksum calculation. 663 A 16-bit unsigned integer temporary variable is initialized to 664 zero. 666 Each unsigned 16-bit word of the PDP message is added to temporary 667 variable, and any overflows are ignored. 669 Draft PTOPO Discovery Protocol and MIB September 1997 671 The ones-complement (i.e., all bits reversed) of this temporary 672 variable is compared to the saved checksum field. If they are 673 different, then the pdpStatsInErrors counter for the receiving port 674 is incremented, and processing is terminated. Otherwise, the 675 checksum is valid, so continue. 677 4.5.4.3. VarBindList 679 The ASN.1/BER portion of the message is decoded. (Such parsing 680 techniques are beyond the scope of this document.) If this portion of 681 the PDP message is not properly encoded, as defined in the PDP Data MIB, 682 then the pdpStatsInErrors counter for the receiving port is incremented, 683 and processing is terminated; otherwise continue. 685 The list of data elements is examined. The agent must skip and ignore 686 PDU data elements unknown to the agent. If any of the mandatory data 687 elements are missing, then the pdpStatsInErrors counter for the 688 receiving port is incremented, and processing is terminated; otherwise 689 continue. 691 The pdpStatsInPkts counter is incremented for the receiving port. 693 4.5.4.4. PTOPO MIB Update 695 If the time-to-live field in the PDP message header is zero then execute 696 this interface shutdown procedure, described below. Processing of the 697 PDP message is now complete. 699 If the time-to-live field is non-zero, then the appropriate 700 ptopoConnEntry is found or created, based on the data elements included 701 in the PDP message. If the indicated entry is dynamic (i.e., 702 ptopoConnIsStatic is true), then the current sysUpTime value is stored 703 in the ptopoConnLastVerifyTime field for the entry. 705 If a ptopoConnEntry was added then the ptopoConnTabInserts counter is 706 incremented. 708 If a ptopoConnEntry of one type was replaced with an entry of a 709 different type, then the ptopoConnTabReplaces counter is incremented. 711 If any ptopoConnEntry was added or deleted, or if information other than 712 the ptopoConnLastVerifyTime changed for any entry due to the processing 713 of this PDP message, then the ptopoLastChangeTime object is set with the 714 Draft PTOPO Discovery Protocol and MIB September 1997 716 current sysUpTime, and a ptopoConfigChange trap event is generated. (See 717 the PTOPO MIB for information on ptopoConfigChange trap generation.) 719 4.5.5. Interface Shutdown Procedure 721 A special procedure exists for the case in which a PDP agent knows a 722 particular port is about to become non-operational. 724 4.5.5.1. PDP Shutdown Transmission 726 In the event an interface, currently configured with PDP message 727 transmission enabled, either becomes disabled for PDP activity, or the 728 interface is administratively disabled, a final PDP message is 729 transmitted with a time to live value of zero (before the interface is 730 disabled). This message is only sent if pdpOperStatus is enabled and no 731 pdpSuppressEntry exists for the indicated local interface. 733 In the event the pdpOperStatus is transitioning to the disabled state, 734 then this shutdown procedure should be executed for all local 735 interfaces. 737 4.5.5.2. PDP Shutdown Reception 739 After reception of a valid PDP message with a time-to-live value equal 740 to zero, the PDP Agent must remove all information in the PTOPO MIB 741 learned from the particular PDP agent, which is associated with the 742 indicated remote connection endpoint. 744 If any entries are found, the ptopoConnTabDeletes counter is incremented 745 for each deleted entry. 747 This procedure is only followed if pdpOperStatus is in the enabled state 748 and no pdpSuppressEntry exists for the local interface on which the PDP 749 message was received. 751 5. PTOPO Discovery Protocol MIB 753 This section defines the MIB used to configure PDP agent behavior. 755 Draft PTOPO Discovery Protocol and MIB September 1997 757 5.1. Definitions 759 PDP-MIB DEFINITIONS ::= BEGIN 761 IMPORTS 762 MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32 763 FROM SNMPv2-SMI 764 RowStatus 765 FROM SNMPv2-TC 766 MODULE-COMPLIANCE, OBJECT-GROUP 767 FROM SNMPv2-CONF 768 PhysicalIndex 769 FROM ENTITY-MIB; 771 pdpMIB MODULE-IDENTITY 772 LAST-UPDATED "9707300000Z" 773 ORGANIZATION "IETF PTOPOMIB Working Group" 774 CONTACT-INFO 775 "PTOPOMIB WG Discussion: 776 ptopo@3com.com 777 Subscription: 778 majordomo@3com.com 779 msg body: [un]subscribe ptopomib 781 Andy Bierman 782 Cisco Systems Inc. 783 170 West Tasman Drive 784 San Jose, CA 95134 785 408-527-3711 786 abierman@cisco.com 788 Keith McCloghrie 789 Cisco Systems Inc. 790 170 West Tasman Drive 791 San Jose, CA 95134 792 408-526-5260 793 kzm@cisco.com" 794 DESCRIPTION 795 "The MIB module for managing the Physical Topology Discovery 796 Protocol." 797 ::= { experimental xx } 799 pdpMIBObjects OBJECT IDENTIFIER ::= { pdpMIB 1 } 801 -- MIB groups 802 Draft PTOPO Discovery Protocol and MIB September 1997 804 pdpConfig OBJECT IDENTIFIER ::= { pdpMIBObjects 1 } 805 pdpStats OBJECT IDENTIFIER ::= { pdpMIBObjects 2 } 807 PdpPortIdType ::= TEXTUAL-CONVENTION 808 STATUS current 809 DESCRIPTION 810 "The type of index value used to represent a port component. 812 If an object of this type has a value of 'ifIndexType(1)', 813 then the associated 'port ID' value represents an ifEntry, 814 with the same ifIndex value. 816 If an object of this type has a value of 817 'entPhysicalIndexType(2)', then the associated 'port ID' 818 value represents an entPhysicalEntry, with the same 819 entPhysicalIndex value." 820 SYNTAX INTEGER { 821 ifIndexType(1), 822 entPhysicalIndexType(2) 823 } 825 -- 826 -- *********************************************************** 827 -- 828 -- P D P C O N F I G 829 -- 830 -- *********************************************************** 831 -- 832 -- The Physical Topology Discovery Protocol Configuration Group 834 pdpAdminStatus OBJECT-TYPE 835 SYNTAX INTEGER { 836 enabled(1), 837 disabled(2) 838 } 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION 842 "The administratively desired status of the the local PDP 843 agent. 845 If the agent is capable of storing non-volatile 846 configuration, then the value of this object must be 847 restored after a re-initialization of the management 849 Draft PTOPO Discovery Protocol and MIB September 1997 851 system." 852 ::= { pdpConfig 1 } 854 pdpOperStatus OBJECT-TYPE 855 SYNTAX INTEGER { 856 enabled(1), 857 disabled(2) 858 } 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The current operational status of the local PDP agent." 863 ::= { pdpConfig 2 } 865 pdpMessageTxInterval OBJECT-TYPE 866 SYNTAX Integer32 (5..32768) 867 UNITS "seconds" 868 MAX-ACCESS read-write 869 STATUS current 870 DESCRIPTION 871 "The interval at which PDP messages are transmitted on 872 behalf of this PDP agent. 874 If the agent is capable of storing non-volatile 875 configuration, then the value of this object must be 876 restored after a re-initialization of the management 877 system." 878 DEFVAL { 60 } 879 ::= { pdpConfig 3 } 881 pdpMessageTxHoldMultiplier OBJECT-TYPE 882 SYNTAX Integer32 (2..10) 883 MAX-ACCESS read-write 884 STATUS current 885 DESCRIPTION 886 "The time-to-live value expressed as a multiple of the 887 pdpMessageTxInterval object. The actual time-to-live value 888 used in PDP messages, transmitted on behalf of this PDP 889 agent, can be expressed by the following formula: 891 TTL = min(65535, (pdpMessageTxInterval * pdpMessageTxHoldMultiplier)) 893 For example, if the value of pdpMessageTxInterval is '60', 894 and the value of pdpMessageTxHoldMultiplier is '3', then the 895 value '180' is encoded in the TTL field in the PDP header. 897 Draft PTOPO Discovery Protocol and MIB September 1997 899 If the agent is capable of storing non-volatile 900 configuration, then the value of this object must be 901 restored after a re-initialization of the management 902 system." 903 DEFVAL { 3 } 904 ::= { pdpConfig 4 } 906 pdpTxWithChecksum OBJECT-TYPE 907 SYNTAX TruthValue 908 MAX-ACCESS read-only 909 STATUS current 910 DESCRIPTION 911 "This object indicates whether the optional checksum field 912 is generated for the PDP messages transmitted by this PDP 913 agent. 915 If this object has the value 'true(1)', then this PDP agent 916 generates a (non-zero) valid PDP checksum for each 917 transmitted PDP message. If this object has the value 918 'false(2)', then this PDP agent sets the PDP checksum to 919 zero in each transmitted PDP message." 920 ::= { pdpConfig 5 } 922 -- 923 -- PdpSuppressTable: 924 -- Disable PDP activity on individual local ports 926 pdpSuppressTable OBJECT-TYPE 927 SYNTAX SEQUENCE OF PdpSuppressEntry 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "A table controlling PDP message transmission on individual 932 interfaces, ports, or backplanes." 933 ::= { pdpConfig 6 } 935 pdpSuppressEntry OBJECT-TYPE 936 SYNTAX PdpSuppressEntry 937 MAX-ACCESS not-accessible 938 STATUS current 939 DESCRIPTION 940 "PDP message configuration information for a particular 941 port. The port must be contained in the same chassis as the 942 PDP agent. PDP messages will not be transmitted or received 943 on the indicated port, even if the port is enabled. 945 Draft PTOPO Discovery Protocol and MIB September 1997 947 If the agent is capable of storing non-volatile 948 configuration, then each active pdpSuppressEntry must be 949 re-created after a re-initialization of the management 950 system. An agent should store enough information about the 951 associated entPhysicalEntry (e.g., entPhysicalAlias) or 952 ifEntry (e.g. ifAlias), to properly re-create the entry, 953 even if the pdpSuppressChassisId and/or pdpSuppressPortId 954 values change across a system re-initialization." 955 INDEX { 956 pdpSuppressChassisId, 957 pdpSuppressPortIdType, 958 pdpSuppressPortId 959 } 960 ::= { pdpSuppressTable 1 } 962 PdpSuppressEntry ::= SEQUENCE { 963 pdpSuppressChassisId PhysicalIndex, 964 pdpSuppressPortIdType PdpPortIdType, 965 pdpSuppressPortId Integer32, 966 pdpSuppressRowStatus RowStatus 967 } 969 pdpSuppressChassisId OBJECT-TYPE 970 SYNTAX PhysicalIndex 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "The entPhysicalIndex value used to identify the chassis 975 component associated with this entry. The associated 976 entPhysicalEntry must be active, and the associated 977 entPhysicalClass object must be equal to 'chassis(3)'." 978 ::= { pdpSuppressEntry 1 } 980 pdpSuppressPortIdType OBJECT-TYPE 981 SYNTAX PdpPortIdType 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "The type of index value contained in the associated 986 pdpSuppressPortId object." 987 ::= { pdpSuppressEntry 2 } 989 pdpSuppressPortId OBJECT-TYPE 990 SYNTAX Integer32 (1..2147483647) 991 MAX-ACCESS not-accessible 993 Draft PTOPO Discovery Protocol and MIB September 1997 995 STATUS current 996 DESCRIPTION 997 "The index value used to identify the port component of this 998 entry. The type of index value depends on the 999 pdpSuppressPortIdType value for this entry. 1001 If the associated pdpSuppressPortIdType is equal to 1002 'ifIndexType(1)', then this pdpSuppressPortId represents an 1003 ifEntry with the same ifIndex value. The associated ifEntry 1004 must be active, and represent a physical interface on the 1005 local chassis. 1007 If the associated pdpSuppressPortIdType is equal to 1008 'entPhysicalIndexType(2)', then this pdpSuppressPortId 1009 represents an entPhysicalEntry with the same 1010 entPhysicalIndex value. The associated entPhysicalEntry 1011 must be active, and the associated entPhysicalClass object 1012 must be equal to 'port(10)' or 'backplane(4)'." 1013 ::= { pdpSuppressEntry 3 } 1015 pdpSuppressRowStatus OBJECT-TYPE 1016 SYNTAX RowStatus 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "The status of this entry." 1021 ::= { pdpSuppressEntry 4 } 1023 -- 1024 -- *********************************************************** 1025 -- 1026 -- P D P S T A T S 1027 -- 1028 -- *********************************************************** 1029 -- 1030 -- PDP Stats Group 1032 pdpStatsTable OBJECT-TYPE 1033 SYNTAX SEQUENCE OF PdpStatsEntry 1034 MAX-ACCESS not-accessible 1035 STATUS current 1036 DESCRIPTION 1037 "A table containing PDP statistics for individual ports. 1039 Entries are not required to exist in this table while the 1041 Draft PTOPO Discovery Protocol and MIB September 1997 1043 pdpAdminStatus or pdpOperStatus objects are equal to 1044 'disabled(2)'. 1046 Entries are not required to exist in this table if a 1047 corresponding entry (with identical index values) exists in 1048 the pdpSuppressTable." 1049 ::= { pdpStats 1 } 1051 pdpStatsEntry OBJECT-TYPE 1052 SYNTAX PdpStatsEntry 1053 MAX-ACCESS not-accessible 1054 STATUS current 1055 DESCRIPTION 1056 "PDP message statistics for a particular port. The port 1057 must be contained in the same chassis as the PDP agent." 1058 INDEX { 1059 pdpStatsChassisId, 1060 pdpStatsPortIdType, 1061 pdpStatsPortId 1062 } 1063 ::= { pdpStatsTable 1 } 1065 PdpStatsEntry ::= SEQUENCE { 1066 pdpStatsChassisId PhysicalIndex, 1067 pdpStatsPortIdType PdpPortIdType, 1068 pdpStatsPortId Integer32, 1069 pdpStatsInPkts Counter32, 1070 pdpStatsInErrors Counter32, 1071 pdpStatsOutPkts Counter32 1072 } 1074 pdpStatsChassisId OBJECT-TYPE 1075 SYNTAX PhysicalIndex 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "The entPhysicalIndex value used to identify the chassis 1080 component associated with this entry. The associated 1081 entPhysicalEntry must be active, and the associated 1082 entPhysicalClass object must be equal to 'chassis(3)'." 1083 ::= { pdpStatsEntry 1 } 1085 pdpStatsPortIdType OBJECT-TYPE 1086 SYNTAX PdpPortIdType 1087 MAX-ACCESS not-accessible 1089 Draft PTOPO Discovery Protocol and MIB September 1997 1091 STATUS current 1092 DESCRIPTION 1093 "The type of index value contained in the associated 1094 pdpStatsPortId object." 1095 ::= { pdpStatsEntry 2 } 1097 pdpStatsPortId OBJECT-TYPE 1098 SYNTAX Integer32 (1..2147483647) 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The index value used to identify the port component of this 1103 entry. The type of index value depends on the 1104 pdpStatsPortType value for this entry. 1106 If the associated pdpStatsPortIdType is equal to 1107 'ifIndexType(1)', then this pdpStatsPortId represents an 1108 ifEntry with the same ifIndex value. The associated ifEntry 1109 must be active, and represent a physical interface on the 1110 local chassis. 1112 If the associated pdpStatsPortIdType is equal to 1113 'entPhysicalIndexType(2)', then this pdpStatsPortId 1114 represents an entPhysicalEntry with the same 1115 entPhysicalIndex value. The associated entPhysicalEntry 1116 must be active, and the associated entPhysicalClass object 1117 must be equal to 'port(10)' or 'backplane(4)'." 1118 ::= { pdpStatsEntry 3 } 1120 pdpStatsInPkts OBJECT-TYPE 1121 SYNTAX Counter32 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "The number of valid PDP messages received by this PDP agent 1126 on the indicated port, while this PDP agent is enabled." 1127 ::= { pdpStatsEntry 4 } 1129 pdpStatsInErrors OBJECT-TYPE 1130 SYNTAX Counter32 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "The number of invalid PDP messages received by this PDP 1135 agent on the indicated port, while this PDP agent is 1137 Draft PTOPO Discovery Protocol and MIB September 1997 1139 enabled. A PDP message may be invalid for several reasons, 1140 including: 1141 - invalid MAC header; length or DA fields 1142 - invalid PDP header; version or flags fields 1143 - invalid PDP VarBindList ASN.1/BER encoding 1144 - invalid or missing PDP VarBindList data elements" 1145 ::= { pdpStatsEntry 5 } 1147 pdpStatsOutPkts OBJECT-TYPE 1148 SYNTAX Counter32 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "The number of PDP messages transmitted by this PDP agent on 1153 the indicated port." 1154 ::= { pdpStatsEntry 6 } 1156 -- conformance information 1157 pdpConformance OBJECT IDENTIFIER ::= { pdpMIB 2 } 1159 pdpCompliances OBJECT IDENTIFIER ::= { pdpConformance 1 } 1160 pdpGroups OBJECT IDENTIFIER ::= { pdpConformance 2 } 1162 -- compliance statements 1164 pdpCompliance MODULE-COMPLIANCE 1165 STATUS current 1166 DESCRIPTION 1167 "The compliance statement for SNMP entities which implement 1168 the PDP MIB." 1169 MODULE -- this module 1170 MANDATORY-GROUPS { pdpConfigGroup, pdpStatsGroup } 1172 ::= { pdpCompliances 1 } 1174 -- MIB groupings 1176 pdpConfigGroup OBJECT-GROUP 1177 OBJECTS { 1178 pdpAdminStatus, 1179 pdpOperStatus, 1180 pdpMessageTxInterval, 1181 pdpMessageTxHoldMultiplier, 1182 pdpTxWithChecksum, 1184 Draft PTOPO Discovery Protocol and MIB September 1997 1186 pdpSuppressRowStatus 1187 } 1188 STATUS current 1189 DESCRIPTION 1190 "The collection of objects which are used to configure the 1191 PTOPO Discovery Protocol implementation behavior. 1193 This group is mandatory for agents which implement the PTOPO 1194 Discovery Protocol." 1195 ::= { pdpGroups 1 } 1197 pdpStatsGroup OBJECT-GROUP 1198 OBJECTS { 1199 pdpStatsInPkts, 1200 pdpStatsInErrors, 1201 pdpStatsOutPkts 1202 } 1203 STATUS current 1204 DESCRIPTION 1205 "The collection of objects which are used to represent PTOPO 1206 Discovery Protocol statistics. 1208 This group is mandatory for agents which implement the PTOPO 1209 Discovery Protocol." 1210 ::= { pdpGroups 2 } 1212 END 1214 6. Acknowledgements 1216 The PTOPO Discovery Protocol is a product of the IETF PTOPOMIB Working 1217 Group. 1219 Draft PTOPO Discovery Protocol and MIB September 1997 1221 7. References 1223 [ENTITY-EXT] 1224 Bierman, A., McCloghrie, K., "Entity MIB Extensions for Persistent 1225 Component Identification", draft-bierman-entmib-compid-00.txt, 1226 Cisco Systems, July 1997. 1228 [PTOPO] 1229 Bierman, A., Kones, K., "Physical Topology MIB", draft-ietf- 1230 ptopomib-mib-00.txt, Cisco Systems, Bay Networks, July 1997. 1232 [RFC1157] 1233 Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1234 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1235 International, MIT Laboratory for Computer Science, May 1990. 1237 [RFC1213] 1238 McCloghrie, K., and M. Rose, Editors, "Management Information Base 1239 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1240 RFC 1213, Hughes LAN Systems, Performance Systems International, 1241 March 1991. 1243 [RFC1573] 1244 McCloghrie, K., and Kastenholtz, F., "Interfaces Group Evolution", 1245 RFC 1573, Hughes LAN Systems, FTP Software, January 1994. 1247 [RFC1902] 1248 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1249 S. Waldbusser, "Structure of Management Information for version 2 1250 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1251 January 1996. 1253 [RFC1903] 1254 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1255 S. Waldbusser, "Textual Conventions for version 2 of the Simple 1256 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1258 [RFC1904] 1259 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1260 S. Waldbusser, "Conformance Statements for version 2 of the Simple 1261 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1263 [RFC1905] 1264 SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1265 S. Waldbusser, "Protocol Operations for version 2 of the Simple 1267 Draft PTOPO Discovery Protocol and MIB September 1997 1269 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1271 [RFC2037] 1272 McCloghrie, K., Bierman, A., "Entity MIB using SMIv2", RFC 2037, 1273 Cisco Systems, October 1996. 1275 Draft PTOPO Discovery Protocol and MIB September 1997 1277 8. Security Considerations 1279 This protocol and associated MIB can expose the existence of physical 1280 components, MAC layer addresses, and network layer addresses, pertaining 1281 to devices within a given network. A network administrator may wish to 1282 restrict access to this management information, using SNMP access 1283 control mechanisms, and restrict PDP message processing to a particular 1284 set of ports, by configuring entries in the pdpSuppressTable. 1286 9. Authors' Addresses 1288 Andy Bierman 1289 Cisco Systems, Inc. 1290 170 West Tasman Drive 1291 San Jose, CA 95134 1292 Phone: 408-527-3711 1293 Email: abierman@cisco.com 1295 Keith McCloghrie 1296 Cisco Systems, Inc. 1297 170 West Tasman Drive 1298 San Jose, CA 95134 1299 Phone: 408-526-5260 1300 Email: kzm@cisco.com 1302 Draft PTOPO Discovery Protocol and MIB September 1997 1304 Table of Contents 1306 1 Introduction .................................................... 1 1307 2 The SNMP Network Management Framework ........................... 2 1308 2.1 Object Definitions ............................................ 2 1309 3 Overview ........................................................ 2 1310 3.1 Terms ......................................................... 3 1311 3.2 Persistent Identifiers ........................................ 3 1312 3.3 Relationship to the Physical Topology MIB ..................... 3 1313 3.4 Relationship to Entity MIB .................................... 3 1314 3.5 Relationship to Interfaces MIB ................................ 4 1315 4 PTOPO Discovery Protocol ........................................ 4 1316 4.1 Frame Encapsulation ........................................... 4 1317 4.2 PDP Forwarding ................................................ 5 1318 4.3 PDP Message Format ............................................ 5 1319 4.3.1 PDP Header Format ........................................... 5 1320 4.3.2 PDP PDU Encoding ............................................ 7 1321 4.4 PDP Data MIB .................................................. 8 1322 4.4.1 Definitions ................................................. 8 1323 4.5 Protocol Operation ............................................ 12 1324 4.5.1 Protocol Initialization ..................................... 13 1325 4.5.2 Message Encoding ............................................ 13 1326 4.5.2.1 Header Fields ............................................. 13 1327 4.5.2.2 VarBindList ............................................... 13 1328 4.5.2.3 Checksum .................................................. 14 1329 4.5.3 Message Transmission ........................................ 14 1330 4.5.4 Received Message Processing ................................. 15 1331 4.5.4.1 Header Fields ............................................. 15 1332 4.5.4.2 Checksum .................................................. 15 1333 4.5.4.3 VarBindList ............................................... 16 1334 4.5.4.4 PTOPO MIB Update .......................................... 16 1335 4.5.5 Interface Shutdown Procedure ................................ 17 1336 4.5.5.1 PDP Shutdown Transmission ................................. 17 1337 4.5.5.2 PDP Shutdown Reception .................................... 17 1338 5 PTOPO Discovery Protocol MIB .................................... 17 1339 5.1 Definitions ................................................... 18 1340 6 Acknowledgements ................................................ 27 1341 7 References ...................................................... 28 1342 8 Security Considerations ......................................... 30 1343 9 Authors' Addresses .............................................. 30