idnits 2.17.1 draft-ietf-idpr-mib-03.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 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. ** 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 == The page length should not exceed 58 lines per page, but there was 47 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 176 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([10,11]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2136 has weird spacing: '... active sourc...' -- 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 (January 1994) is 11059 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) == Unused Reference: '6' is defined on line 2439, but no explicit reference was found in the text ** Downref: Normative reference to an Unknown state RFC: RFC 1052 (ref. '1') ** Downref: Normative reference to an Unknown state RFC: RFC 1109 (ref. '2') ** Downref: Normative reference to an Historic RFC: RFC 1156 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '5') ** Obsolete normative reference: RFC 1158 (ref. '6') (Obsoleted by RFC 1213) -- Possible downref: Non-RFC (?) normative reference: ref. '7' -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '10' -- Possible downref: Non-RFC (?) normative reference: ref. '11' -- Possible downref: Non-RFC (?) normative reference: ref. '12' Summary: 15 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Policy Routing Working Group R. A. Woodburn, Editor 3 Internet Draft Sparta 4 October 1993 Expires January 1994 5 7 IDPR MIB 9 Definitions of Managed Objects for the 10 Inter-Domain Policy Routing Protocol (Version 1) 12 Contents 14 1 Historical Perspective 2 16 2 Objects 3 18 2.1 Format of Definitions :: :: :: :: :: :: :: :: :: :: :: :: :: 4 20 3 Overview 4 22 3.1 Domain Structure :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: 4 24 3.2 IDPR Functions : :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: 5 26 3.3 IDPR MIB : :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: 7 28 4 Object Definitions 7 30 5 Trap Messages 43 32 6 Security Considerations 46 34 7 Acknowledgements 46 36 8 References 46 38 9 Editor's Address 47 39 Status of this Memo 41 This document is an Internet Draft. Internet Drafts are working 42 documents of the Internet Engineering Task Force (IETF), its areas, and 43 its working groups. Note that other groups may also distribute working 44 documents as Internet Drafts. 46 This Internet Draft will be submitted to the RFC editor as an 47 experimental extension to the SNMP MIB. Distribution of this Internet 48 Draft is unlimited. Please send comments to IDPR working group 49 (idpr-wg@bbn.com). 51 Internet Drafts are draft documents valid for a maximum of six months. 52 Internet Drafts may be updated, replaced, or obsoleted by other documents 53 at any time. It is not appropriate to use Internet Drafts as reference 54 material or to cite them other than as a ``working draft'' or ``work in 55 progress''. 57 Please check the 1id-abstracts.txt listing contained in the 58 internet-drafts shadow directories on nic.ddn.mil, nnsc.nsf.net, 59 nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au to learn the current 60 status of any Internet Draft. 62 Abstract 64 This memo defines a portion of the Management Information Base (MIB) for 65 use with network management protocols in TCP/IP-based internets. In 66 particular, it defines objects for managing the Inter-Domain Policy 67 Routing Protocol [10,11]. 69 This memo does not specify a standard for the Internet community. 70 However, after experimentation, if sufficient consensus is reached in the 71 Internet community, then a subsequent revision of this document may be 72 incorporated into the Internet-standard MIB. 74 1 Historical Perspective 76 As reported in RFC 1052, ``IAB Recommendations for the Development of 77 Internet Network Management Standards'' [1], a two-prong strategy for 78 network management of TCP/IP-based internets was undertaken. In the 79 short-term, the Simple Network Management Protocol (SNMP), defined in RFC 80 1067, was to be used to manage nodes in the Internet community. In the 81 long-term, the use of the OSI network management framework was to be 82 examined. Two documents were produced to define the management 83 information: RFC 1065, which defined the Structure of Management 84 Information (SMI), and RFC 1066, which defined the Management Information 85 Base (MIB). Both of these documents were designed so as to be compatible 86 with both the SNMP and the OSI network management framework. 88 This strategy was quite successful in the short-term: Internet-based 89 network management technology was fielded, by both the research and 90 commercial communities, within a few months. As a result of this, 91 portions of the Internet community became network manageable in a timely 92 fashion. 94 As reported in RFC 1109, Report of the Second Ad Hoc Network Management 95 Review Group [2], the requirements of the SNMP and the OSI network 96 management frameworks were more different than anticipated. As such, the 97 requirement for compatibility between the SMI/MIB and both frameworks was 98 suspended. This action permitted the operational network management 99 framework, based on the SNMP, to respond to new operational needs in the 100 Internet community by producing MIB-II. 102 In May of 1990, the core documents were elevated to "Standard Protocols" 103 with "Recommended" status. As such, the Internet-standard network 104 management framework consists of: Structure and Identification of 105 Management Information for TCP/IP-based internets, RFC 1155 [3], which 106 describes how managed objects contained in the MIB are defined; 107 Management Information Base for Network Management of TCP/IP-based 108 internets, which describes the managed objects contained in the MIB, RFC 109 1156 [4]; and, the Simple Network Management Protocol, RFC 1157 [5], 110 which defines the protocol used to manage these objects. Consistent with 111 the IAB directive to produce simple, workable systems in the short-term, 112 the list of managed objects defined in the Internet-standard MIB was 113 derived by taking only those elements which are considered essential. 114 However, the SMI defined three extensibility mechanisms: one, the 115 addition of new standard objects through the definitions of new versions 116 of the MIB; two, the addition of widely-available but non-standard 117 objects through the experimental subtree; and three, the addition of 118 private objects through the enterprises subtree. Such additional objects 119 can not only be used for vendor-specific elements, but also for 120 experimentation as required to further the knowledge of which other 121 objects are essential. 123 This memo defines extensions to the MIB using the second method. It 124 contains definitions of managed objects used for experimentation. After 125 experimentation, if sufficient consensus is reached in the Internet 126 community, then a subsequent revision of this memo may be placed in the 127 Internet-standard MIB. 129 2 Objects 131 Managed objects are accessed via a virtual information store, termed the 132 Management Information Base or MIB. Objects in the MIB are defined using 133 the subset of Abstract Syntax Notation One (ASN.1) [7] defined in the 134 SMI. In particular, each object has a name, a syntax, and an encoding. 135 The name is an object identifier, an administratively assigned name, 136 which specifies an object type. The object type together with an object 137 instance serves to uniquely identify a specific instantiation of the 138 object. For human convenience, we often use a textual string, termed the 139 OBJECT DESCRIPTOR, to also refer to the object type. 141 The syntax of an object type defines the abstract data structure 142 corresponding to that object type. The ASN.1 language is used for this 143 purpose. However, the SMI [3] purposely restricts the ASN.1 constructs 144 which may be used. These restrictions are explicitly made for 145 simplicity. 147 The encoding of an object type is simply how that object type is 148 represented using the object type's syntax. Implicitly tied to the 149 notion of an object type's syntax and encoding is how the object type is 150 represented when being transmitted on the network. 152 The SMI specifies the use of the basic encoding rules of ASN.1 [8], 153 subject to the additional requirements imposed by the SNMP. 155 2.1 Format of Definitions 157 Section 6 contains the specification of all object types contained in 158 this MIB module. The object types are defined using the conventions 159 defined in the SMI, as amended by the extensions specified in [9]. 161 3 Overview 163 The Inter-Domain Policy Routing Protocol (IDPR) is a routing protocol for 164 use between Administrative Domains. The objective of IDPR is to 165 construct routes between source and destination administrative domains 166 that provide user traffic with the service requested within the 167 constraints stipulated by the domains transited. 169 With IDPR, we introduce a new network-layer Internet protocol based on 170 source-specified routing between administrative domains and a new 171 Internet addressing structure based on an administrative domain 172 hierarchy. However, for IDPR version 1, we recommend implementing a 173 proper subset of the complete architecture proposed in [11]. The 174 recommended subset provides the majority of the features of IDPR and 175 comprises the virtual gateway protocol, the domain status distribution 176 protocol, the route synthesis procedure, the path setup protocol, and the 177 message forwarding procedure. 179 3.1 Domain Structure 181 The IDPR architecture has been designed to accommodate an Internet with 182 tens of thousands of administrative domains collectively containing 183 hundreds of thousands of local networks. Inter-domain policy routes are 184 constructed using information about the policy attributes of, and the 185 connectivity between, administrative domains. The intra-domain details, 186 gateways and networks traversed, of an inter-domain policy route are the 187 responsibility of intra-domain routing and are thus outside the scope of 188 inter-domain routing. 190 An Administrative Domain (AD) is a collection of contiguous networks 191 managed by a single administrative authority that places policy 192 restrictions on transit traffic, defines policy requirements for 193 locally-generated traffic, and selects the intra-domain addressing 194 schemes and routing procedures. Each administrative domain has a unique 195 identity within the Internet. 197 Virtual Gateways (VGs) are the only IDPR-recognized connecting points 198 between adjacent administrative domains. Each virtual gateway is a 199 collection of directly-connected policy gateways in two adjacent domains, 200 whose existence has been sanctioned by the authorities in both domains. 201 The domain authorities may agree to establish more than one virtual 202 gateway between the two domains. For each such virtual gateway, the two 203 authorities together assign a virtual gateway identifier, unique within 204 the set of virtual gateways connecting the two domains. To produce a 205 virtual gateway identifier unique within its domain, the domain authority 206 concatenates the mutually assigned identifier together with the adjacent 207 domain's identifier. 209 Policy Gateways (PGs) are the physical gateways within a virtual gateway. 210 Each policy gateway enforces policy restrictions on transit traffic as 211 stipulated by the domain's administrative authority. A single policy 212 gateway may belong to multiple virtual gateways. Within a domain, two 213 policy gateways are neighbors if they are in different virtual gateways. 214 Within a virtual gateway, two policy gateways are peers if they are in 215 the same domain and are adjacent if they are in different domains. 216 Adjacent policy gateways are directly connected if they are the only 217 Internet-addressable entities attached to the connecting medium. Note 218 that this definition implies that not only point-to-point links but also 219 networks may serve as direct connections between adjacent policy 220 gateways. The authority for a given domain assigns to each of its policy 221 gateways an identifier, unique within that domain. 223 3.2 IDPR Functions 225 Inter-domain policy routing comprises the following functions: 227 1. Collecting and distributing connectivity and policy information 228 pertaining to transit domains. 230 2. Synthesizing and selecting policy routes based on the connectivity 231 and policy information associated with the transit domains and on 232 the service requirements associated with the source. 234 3. Setting up paths across the Internet, using the policy routes 235 synthesized. 237 4. Forwarding messages across and between administrative domains along 238 the established paths. 240 5. Maintaining databases of transit domain connectivity and policy, 241 inter-domain policy routes, configured global information such as 242 network-address/domain-identifier mappings, and configured local 243 information such as the policy gateways within an administrative 244 domain. 246 As described in [11], a source domain controls synthesis and selection of 247 policy routes to destination domains, while intermediate domains on a 248 specific source-selected policy route determine whether or not the route 249 is consistent with their transit policies. The route synthesis procedure 250 uses domain status information in the form of advertised transit policies 251 and adjacencies, to generate policy routes between source and destination 252 domains. The source then selects policy routes from those provided by 253 route synthesis, according to its own service requirements. Policy 254 routes require a path setup procedure during which policy gateways in 255 intermediate domains verify whether or not they will carry traffic 256 traveling along the path, and contingent upon route acceptance, form an 257 association between the path identifier and the previous and next policy 258 gateways on the path. Following path setup, intermediate policy gateways 259 use the path identifier carried in data messages to forward data traffic 260 along the path. 262 Several different entities are responsible for performing the IDPR 263 functions. Policy gateways collect and distribute status information 264 about their administrative domains, participate in path setup, and 265 forward data messages along established paths. Path agents act on behalf 266 of hosts to select policy routes and to set up and manage paths. 267 Special-purpose servers maintain the routing databases which are 268 distributed with partial redundancy throughout the Internet. Each 269 special-purpose server within an administrative domain has a unique 270 identifier, assigned by the domain authority. Route servers are 271 responsible for both the domain status (connectivity and policy) database 272 and the route database. Also, route servers synthesize policy routes 273 using domain status information and source traffic requirements. Name 274 servers are responsible for the 275 domain-name/network-address/domain-identifier database. Configuration 276 servers are responsible for databases of configured information that 277 apply to policy gateways, path agents, and route servers in the given 278 administrative domain and inform these entities of configuration changes. 280 Both route servers and name servers are organized hierarchically, where a 281 server's position in the hierarchy determines the extent of its database. 282 At the top are global servers that maintain information about all 283 Internet domains; at the bottom are local servers that maintain 284 information about a particular domain, its neighbors, and other 285 frequently visited domains, this last type of information usually 286 obtained from higher-level servers. Hierarchical database organization 287 releases hosts and gateways from the burden of maintaining information 288 about large portions of the Internet, most of which they will never use. 290 In IDPR version 1, each policy gateway performs all IDPR functions, 291 including those of the path agent and the special-purpose servers. 292 Aggregating all routing functions into policy gateways simplifies 293 implementation; one need only install IDPR protocols in policy gateways. 294 Moreover, it simplifies communication between routing functions, as all 295 functions reside within each policy gateway. We also note that IDPR 296 version 1 supports only a flat route server hierarchy; each policy 297 gateway contains a global route server. We are presently investigating 298 approaches to making efficient use of hierarchically-organized routing 299 information. 301 Given the size of the current Internet (on the order of 100 302 administrative domains) and the type of policies supported in IDPR 303 version 1 (access restrictions only), we believe that policy gateways 304 have adequate processing and memory resources to synthesize policy routes 305 and set up paths as well as to forward messages and participate in 306 intra-domain routing. Meanwhile, we are developing autonomous route 307 servers and configuration servers, separate from policy gateways, so that 308 IDPR can accommodate larger numbers of administrative domains and 309 policies in the future. 311 3.3 IDPR MIB 313 These objects are used to control and manage an IDPR [11] implementation. 315 This MIB is broken into 10 sections. The first section describes system 316 variables. The remaining sections describe tables and individual IDPR 317 sub-protocols. 319 4 Object Definitions 321 RFCxxxx-MIB DEFINITIONS ::= BEGIN 323 IMPORTS 324 experimental, IpAddress, Counter, TimeTicks 325 FROM RFC-1155 326 OBJECT-TYPE 327 FROM RFC-1212 328 DisplayString 329 FROM RFC-1213; 331 -- This MIB module uses the extended OBJECT-TYPE macro as 332 -- defined in [9]. The local BitField type is included 333 -- to improve readability. 335 -- The BitField type is an OCTET STRING of four octets. 336 -- The first octet contains bit positions 0-7. The second 337 -- octet contains bit positions 8-15. The third octet 338 -- contains bit positions 16-23. The fourth octet contains 339 -- bit positions 24-31. 341 BitField ::= OCTET STRING (Size 4) 343 idpr OBJECT IDENTIFIER ::= { experimental 28 } 345 -- 5.1 IDPR System Object Definitions 347 idprsys OBJECT IDENTIFIER ::= { idpr 1 } 349 idprAD OBJECT-TYPE 350 SYNTAX INTEGER 351 ACCESS read-only 352 STATUS mandatory 353 DESCRIPTION 354 "The AD identifier of the entity being queried." 355 ::= { idprsys 1 } 357 idprId OBJECT-TYPE 358 SYNTAX INTEGER 359 ACCESS read-only 360 STATUS mandatory 361 DESCRIPTION 362 "The entity identifier of the entity being queried." 363 ::= { idprsys 2 } 365 idprType OBJECT-TYPE 366 SYNTAX BitField 367 ACCESS read-only 368 STATUS mandatory 369 DESCRIPTION 370 "The functions supported by the local entity as 371 defined by the bitfields below. 372 Bit position 0 PG flag 373 Bit position 1 RS flag." 374 ::= { idprsys 3 } 376 idprADRep OBJECT-TYPE 377 SYNTAX INTEGER 378 ACCESS read-only 379 STATUS mandatory 380 DESCRIPTION 381 "The entity identifier of the AD representative 382 as perceived by the local entity." 383 ::= { idprsys 4 } 385 idprUpTime OBJECT-TYPE 386 SYNTAX TimeTicks 387 ACCESS read-only 388 STATUS mandatory 389 DESCRIPTION 390 "The amount of time since IDPR was last 391 initialized. The value is expressed in 392 TimeTicks (10 millisecond) units." 393 ::= { idprsys 5 } 395 idprPolicyState OBJECT-TYPE 396 SYNTAX INTEGER(0..255) 397 ACCESS read-write 398 STATUS optional 399 DESCRIPTION 400 "Reading this object returns the current policy 401 state for the entity. A domain administrator 402 may choose to associate source and transit 403 policies with one or more policy states. A 404 transit or source policy thus associated becomes 405 active only when one of its policy state values 406 matches the current policy state. Otherwise, 407 the policy is dormant and is not distributed 408 in RID messages or used in route computation. 409 Writing a new value to this object sets the 410 new policy state, which may cause a different 411 set of policies to take effect." 412 ::= { idprsys 6 } 414 idprDomainName OBJECT-TYPE 415 SYNTAX DisplayString (Size 64) 416 ACCESS read-only 417 STATUS mandatory 418 DESCRIPTION 419 "The name of the domain as represented by a 420 printable string." 421 ::= { idprsys 7 } 423 -- 5.2 IDPR CMTP Object Definitions 425 idprcmtp OBJECT IDENTIFIER ::= { idpr 2 } 427 idprcmtpVer OBJECT-TYPE 428 SYNTAX BitField 429 ACCESS read-only 430 STATUS mandatory 431 DESCRIPTION 432 "The CMTP versions supported by this PG. 433 Bit Position 0 == Version 1 434 Bit Position 1 == Version 2 435 ...and so on... 436 Bit Position n == Version n+1 437 where n <= 31." 438 ::= { idprcmtp 1 } 440 idprcmtpIns OBJECT-TYPE 441 SYNTAX Counter 442 ACCESS read-only 443 STATUS mandatory 444 DESCRIPTION 445 "The number of CMTP messages received by the 446 local entity." 447 ::= { idprcmtp 2 } 449 idprcmtpOuts OBJECT-TYPE 450 SYNTAX Counter 451 ACCESS read-only 452 STATUS mandatory 453 DESCRIPTION 454 "The number of CMTP messages issued by the 455 local entity." 456 ::= { idprcmtp 3 } 458 idprcmtpRetries OBJECT-TYPE 459 SYNTAX Counter 460 ACCESS read-only 461 STATUS mandatory 462 DESCRIPTION 463 "The number of retransmissions of CMTP messages 464 by the local entity." 465 ::= { idprcmtp 4 } 467 idprcmtpAckIns OBJECT-TYPE 468 SYNTAX Counter 469 ACCESS read-only 470 STATUS mandatory 471 DESCRIPTION 472 "The number of CMTP ACKs received by the local 473 entity." 474 ::= { idprcmtp 5 } 476 idprcmtpAckOuts OBJECT-TYPE 477 SYNTAX Counter 478 ACCESS read-only 479 STATUS mandatory 480 DESCRIPTION 481 "The number of CMTP ACKs issued by the local 482 entity." 483 ::= { idprcmtp 6 } 485 idprcmtpNakIns OBJECT-TYPE 486 SYNTAX Counter 487 ACCESS read-only 488 STATUS mandatory 489 DESCRIPTION 490 "The total number of CMTP NAKs received by the 491 local entity." 492 ::= { idprcmtp 7 } 494 idprcmtpNakOuts OBJECT-TYPE 495 SYNTAX Counter 496 ACCESS read-only 497 STATUS mandatory 498 DESCRIPTION 499 "The number of CMTP NAKs issued by the local 500 entity." 501 ::= { idprcmtp 8 } 503 idprcmtpTimeouts OBJECT-TYPE 504 SYNTAX Counter 505 ACCESS read-only 506 STATUS mandatory 507 DESCRIPTION 508 "The number of CMTP messages that failed to 509 be acknowledged in a timely manneer, causing 510 delivery of the message to timeout." 511 ::= { idprcmtp 9 } 513 idprcmtpUnkAuths OBJECT-TYPE 514 SYNTAX Counter 515 ACCESS read-only 516 STATUS mandatory 517 DESCRIPTION 518 "The number of CMTP protocol messages received 519 with an unrecognized authentication type." 520 ::= { idprcmtp 10 } 522 idprcmtpUnkProtos OBJECT-TYPE 523 SYNTAX Counter 524 ACCESS read-only 525 STATUS mandatory 526 DESCRIPTION 527 "The number of CMTP protocol messages received 528 with an invalid IDPR sub-protocol number." 529 ::= { idprcmtp 11 } 531 idprcmtpBadAuths OBJECT-TYPE 532 SYNTAX Counter 533 ACCESS read-only 534 STATUS mandatory 535 DESCRIPTION 536 "The number of CMTP protocol messages that 537 failed message authentication tests." 538 ::= { idprcmtp 12 } 540 idprcmtpBadLengths OBJECT-TYPE 541 SYNTAX Counter 542 ACCESS read-only 543 STATUS mandatory 544 DESCRIPTION 545 "The number of CMTP protocol messages received 546 with an invalid length field." 547 ::= { idprcmtp 13 } 549 idprcmtpBadTimes OBJECT-TYPE 550 SYNTAX Counter 551 ACCESS read-only 552 STATUS mandatory 553 DESCRIPTION 554 "The number of CMTP protocol messages received 555 with a bad timestamp." 556 ::= { idprcmtp 14 } 558 -- 5.3 IDPR VGP Object Definitions 560 idprvgp OBJECT IDENTIFIER ::= { idpr 3 } 562 idprvgpPer OBJECT-TYPE 563 SYNTAX INTEGER 564 ACCESS read-only 565 STATUS mandatory 566 DESCRIPTION 567 "The default update interval for the up/down 568 protocol in milliseconds. This object 569 corresponds to the vgp_per_sec configuration 570 parameter described in [12], but normalized 571 to millisecond units." 572 ::= { idprvgp 1 } 574 idprvgpPGInt OBJECT-TYPE 575 SYNTAX INTEGER 576 ACCESS read-only 577 STATUS mandatory 578 DESCRIPTION 579 "The retransmission interval for acknowledged 580 VGP message types in millisecond units. This 581 object corresponds to the vgp_int_usec system 582 configuration parameter [12] divided by 1000, 583 and rounded to the nearest millisecond." 584 ::= { idprvgp 2 } 586 idprvgpPGRet OBJECT-TYPE 587 SYNTAX INTEGER 588 ACCESS read-only 589 STATUS mandatory 590 DESCRIPTION 591 "The number of retransmissions to be sent 592 before a message is classified as undeliverable. 593 This object corresponds to the vgp_ret system 594 configuration parameter specified in [12]." 595 ::= { idprvgp 3 } 597 idprvgpSTSInt OBJECT-TYPE 598 SYNTAX INTEGER 599 ACCESS read-only 600 STATUS mandatory 601 DESCRIPTION 602 "The delay (hold time) in seconds from the time a 603 VG representative receives a PG connect message 604 until it issues a PG status message for that VG. 605 For systems which do not support more than 2 PGs 606 per VG, this object is not applicable and should 607 return the value 0." 608 ::= { idprvgp 4 } 610 idprvgpUpDownIns OBJECT-TYPE 611 SYNTAX Counter 612 ACCESS read-only 613 STATUS mandatory 614 DESCRIPTION 615 "The number of up/down messages received." 616 ::= { idprvgp 5 } 618 idprvgpUpDownInErrs OBJECT-TYPE 619 SYNTAX Counter 620 ACCESS read-only 621 STATUS mandatory 622 DESCRIPTION 623 "The number of invalid up/down messages received. 624 Up/down messages improperly addressed are 625 tabulated by this object, along with other 626 generic errors." 627 ::= { idprvgp 6 } 629 idprvgpUpDownOuts OBJECT-TYPE 630 SYNTAX Counter 631 ACCESS read-only 632 STATUS mandatory 633 DESCRIPTION 634 "The number of up/down messages sent." 635 ::= { idprvgp 7 } 637 idprvgpPGConIns OBJECT-TYPE 638 SYNTAX Counter 639 ACCESS read-only 640 STATUS optional 641 DESCRIPTION 642 "The number of PG connect messages received." 643 ::= { idprvgp 8 } 645 idprvgpPGConOuts OBJECT-TYPE 646 SYNTAX Counter 647 ACCESS read-only 648 STATUS optional 649 DESCRIPTION 650 "The number of PG connect messages sent. This 651 object should return the value 0 if PG connect 652 messages are not supported." 653 ::= { idprvgp 9 } 655 idprvgpPGPlcyIns OBJECT-TYPE 656 SYNTAX Counter 657 ACCESS read-only 658 STATUS optional 659 DESCRIPTION 660 "The number of PG policy messages received." 661 ::= { idprvgp 10 } 663 idprvgpPGPlcyOuts OBJECT-TYPE 664 SYNTAX Counter 665 ACCESS read-only 666 STATUS optional 667 DESCRIPTION 668 "The number of PG policy messages sent. This 669 object should return the value 0 if PG policy 670 messages are not supported." 671 ::= { idprvgp 11 } 673 idprvgpVGConIns OBJECT-TYPE 674 SYNTAX Counter 675 ACCESS read-only 676 STATUS mandatory 677 DESCRIPTION 678 "The number of VG connect messages received." 679 ::= { idprvgp 12 } 681 idprvgpVGConOuts OBJECT-TYPE 682 SYNTAX Counter 683 ACCESS read-only 684 STATUS mandatory 685 DESCRIPTION 686 "The number of VG connect messages sent." 687 ::= { idprvgp 13 } 689 idprvgpVGPlcyIns OBJECT-TYPE 690 SYNTAX Counter 691 ACCESS read-only 692 STATUS optional 693 DESCRIPTION 694 "The number of VG policy messages received." 695 ::= { idprvgp 14 } 697 idprvgpVGPlcyOuts OBJECT-TYPE 698 SYNTAX Counter 699 ACCESS read-only 700 STATUS optional 701 DESCRIPTION 702 "The number of VG policy messages sent. This 703 object should return the value 0 if VG policy 704 messages are not supported." 705 ::= { idprvgp 15 } 707 idprvgpPGTab OBJECT-TYPE 708 SYNTAX SEQUENCE OF IdprPGEntry 709 ACCESS not-accessible 710 STATUS mandatory 711 DESCRIPTION 712 "The table listing other policy gateways known 713 by this entity. The table contains PGs in 714 local and adjacent domains." 715 ::= { idprvgp 16 } 717 idprPGEntry OBJECT-TYPE 718 SYNTAX IdprPGEntry 719 ACCESS not-accessible 720 STATUS mandatory 721 DESCRIPTION 722 "Table entry information about a an adjacent, peer, 723 or neighbor PG." 724 INDEX { idprPGAD, idprPGId } 725 ::= { idprvgpPGTab 1 } 727 IdprPGEntry ::= SEQUENCE { 728 idprPGAD 729 INTEGER, 730 idprPGId 731 INTEGER, 732 idprPGStatus 733 INTEGER, 734 idprPGType 735 INTEGER, 736 idprPGTrans 737 Counter, 738 idprPGUpDownPer 739 INTEGER 740 } 742 idprPGAD OBJECT-TYPE 743 SYNTAX INTEGER 744 ACCESS read-only 745 STATUS mandatory 746 DESCRIPTION 747 "The AD identifier for the PG." 748 ::= { idprPGEntry 1 } 750 idprPGId OBJECT-TYPE 751 SYNTAX INTEGER 752 ACCESS read-only 753 STATUS mandatory 754 DESCRIPTION 755 "The entity identifier for the PG." 756 ::= { idprPGEntry 2 } 758 idprPGStatus OBJECT-TYPE 759 SYNTAX INTEGER { 760 up(1), 761 down(2) 762 } 763 ACCESS read-only 764 STATUS mandatory 765 DESCRIPTION 766 "Operational status of PG. Reading this object 767 returns the operational state of a PG." 768 ::= { idprPGEntry 3 } 770 idprPGType OBJECT-TYPE 771 SYNTAX INTEGER { 772 adjacent(1), 773 neighbor(2), 774 peer(3) 775 } 776 ACCESS read-only 777 STATUS mandatory 778 DESCRIPTION 779 "The type of PG entity" 780 ::= { idprPGEntry 4 } 782 idprPGTrans OBJECT-TYPE 783 SYNTAX Counter 784 ACCESS read-only 785 STATUS mandatory 786 DESCRIPTION 787 "The number of times a PG has transitioned state." 788 ::= { idprPGEntry 5 } 790 idprPGUpDownPer OBJECT-TYPE 791 SYNTAX INTEGER 792 ACCESS read-only 793 STATUS mandatory 794 DESCRIPTION 795 "This object returns the negotiated (or default) 796 interval for exchanging up/down messages." 797 ::= { idprPGEntry 6 } 799 idprvgpVGTab OBJECT-TYPE 800 SYNTAX SEQUENCE OF IdprVGEntry 801 ACCESS not-accessible 802 STATUS mandatory 803 DESCRIPTION 804 "The table of known VGs" 805 ::= { idprvgp 17 } 807 idprVGEntry OBJECT-TYPE 808 SYNTAX IdprVGEntry 809 ACCESS not-accessible 810 STATUS mandatory 811 DESCRIPTION 812 "Information regarding a single VG." 813 INDEX { idprVGAdj, idprVGId } 814 ::= { idprvgpVGTab 1 } 816 IdprVGEntry ::= SEQUENCE { 817 idprVGAdj 818 INTEGER, 819 idprVGId 820 INTEGER, 821 idprVGStatus 822 Counter, 823 idprVGVGRep 824 INTEGER 825 } 827 idprVGAdj OBJECT-TYPE 828 SYNTAX INTEGER 829 ACCESS read-only 830 STATUS mandatory 831 DESCRIPTION 832 "The adjacent AD that the VG connects to." 833 ::= { idprVGEntry 1 } 835 idprVGId OBJECT-TYPE 836 SYNTAX INTEGER 837 ACCESS read-only 838 STATUS mandatory 839 DESCRIPTION 840 "The entity identifier of the VG." 841 ::= { idprVGEntry 2 } 843 idprVGStatus OBJECT-TYPE 844 SYNTAX INTEGER { 845 up(1), 846 down(2) 847 } 848 ACCESS read-only 849 STATUS mandatory 850 DESCRIPTION 851 "The operational status of the entity." 852 ::= { idprVGEntry 3 } 854 idprVGVGRep OBJECT-TYPE 855 SYNTAX INTEGER 856 ACCESS read-only 857 STATUS mandatory 858 DESCRIPTION 859 "The PG acting as the VG representative for the 860 VG as seen by this PG." 861 ::= { idprVGEntry 4 } 863 idprvgpPGMap OBJECT-TYPE 864 SYNTAX SEQUENCE OF IdprPGMapEntry 865 ACCESS not-accessible 866 STATUS mandatory 867 DESCRIPTION 868 "A table that returns the association (or mapping) 869 between PG and VG entities. This table is used 870 to determine the VGs that PGs belongs to." 871 ::= { idprvgp 18 } 873 idprPGMapEntry OBJECT-TYPE 874 SYNTAX IdprPGMapEntry 875 ACCESS not-accessible 876 STATUS mandatory 877 DESCRIPTION 878 "Information for a single VG." 879 INDEX { idprPGMapAD, idprPGMapId, 880 idprPGMapAdj, idprPGMapVG } 881 ::= { idprvgpPGMap 1 } 883 IdprPGMapEntry ::= SEQUENCE { 884 idprPGMapAD 885 INTEGER, 886 idprPGMapId 887 INTEGER, 888 idprPGMapAdj 889 INTEGER, 890 idprPGMapVG 891 INTEGER 892 } 894 idprPGMapAD OBJECT-TYPE 895 SYNTAX INTEGER 896 ACCESS read-only 897 STATUS mandatory 898 DESCRIPTION 899 "The AD identifier of the PG." 900 ::= { idprPGMapEntry 1 } 902 idprPGMapId OBJECT-TYPE 903 SYNTAX INTEGER 904 ACCESS read-only 905 STATUS mandatory 906 DESCRIPTION 907 "The entity identifier of the PG." 908 ::= { idprPGMapEntry 2 } 910 idprPGMapAdj OBJECT-TYPE 911 SYNTAX INTEGER 912 ACCESS read-only 913 STATUS mandatory 914 DESCRIPTION 915 "The adjacent AD of the VG." 916 ::= { idprPGMapEntry 3 } 918 idprPGMapVG OBJECT-TYPE 919 SYNTAX INTEGER 920 ACCESS read-only 921 STATUS mandatory 922 DESCRIPTION 923 "A VG to which this PG belongs." 924 ::= { idprPGMapEntry 4 } 926 -- 5.4 IDPR RID Object Definitions 928 idprrid OBJECT IDENTIFIER ::= { idpr 4 } 930 idprridConfigPer OBJECT-TYPE 931 SYNTAX INTEGER 932 ACCESS read-only 933 STATUS mandatory 934 DESCRIPTION 935 "The interval in seconds between the periodic 936 issuance of configuration updates." 937 ::= { idprrid 1 } 939 idprridDynamicPer OBJECT-TYPE 940 SYNTAX INTEGER 941 ACCESS read-only 942 STATUS mandatory 943 DESCRIPTION 944 "The interval in seconds between the periodic 945 issuance of dynamic message updates." 946 ::= { idprrid 2 } 948 idprridInt OBJECT-TYPE 949 SYNTAX INTEGER 950 ACCESS read-only 951 STATUS mandatory 952 DESCRIPTION 953 "The retransmission interval of configuration and 954 dynamic updates on a millisecond timescale." 955 ::= { idprrid 3 } 957 idprridRet OBJECT-TYPE 958 SYNTAX INTEGER 959 ACCESS read-only 960 STATUS mandatory 961 DESCRIPTION 962 "The maximum number of retransmission attempts 963 of configuration or dynamic updates by the 964 CMTP module. An update that cannot be delivered 965 in idprridRet tries is declared undeliverable." 966 ::= { idprrid 4 } 968 idprridTimNew OBJECT-TYPE 969 SYNTAX INTEGER 970 ACCESS read-only 971 STATUS mandatory 972 DESCRIPTION 973 "The maximum wait time in seconds before 974 generating a 'correcting' update as a result 975 of receiving an old update." 976 ::= { idprrid 5 } 978 idprridConfigLif OBJECT-TYPE 979 SYNTAX INTEGER 980 ACCESS read-only 981 STATUS mandatory 982 DESCRIPTION 983 "The lifetime of configuration message updates 984 measured in seconds. Previously received 985 configuration messages are invalidated when 986 the lifetime of the configuration message expires." 987 ::= { idprrid 6 } 989 idprridDynamicLif OBJECT-TYPE 990 SYNTAX INTEGER 991 ACCESS read-only 992 STATUS mandatory 993 DESCRIPTION 994 "The lifetime of received dynamic message updates 995 in seconds. Previously received dynamic messages 996 are invalidated when the lifetime of the dynamic 997 message expires." 998 ::= { idprrid 7 } 1000 idprridConfigIns OBJECT-TYPE 1001 SYNTAX Counter 1002 ACCESS read-only 1003 STATUS mandatory 1004 DESCRIPTION 1005 "The number of configuration message updates 1006 received by the local entity." 1007 ::= { idprrid 8 } 1009 idprridConfigOuts OBJECT-TYPE 1010 SYNTAX Counter 1011 ACCESS read-only 1012 STATUS mandatory 1013 DESCRIPTION 1014 "The number of configuration message updates 1015 issued by the local entity. Note that an request 1016 to flood a config message update by the local 1017 entity is recorded as a single message issuance 1018 event. Furthermore, transit forwarding of config 1019 message updates which are issued by other entities 1020 are not included in this counter." 1021 ::= { idprrid 9 } 1023 idprridDynamicIns OBJECT-TYPE 1024 SYNTAX Counter 1025 ACCESS read-only 1026 STATUS mandatory 1027 DESCRIPTION 1028 "The number of dynamic updates received by the 1029 local Entity." 1030 ::= { idprrid 10 } 1032 idprridDynamicOuts OBJECT-TYPE 1033 SYNTAX Counter 1034 ACCESS read-only 1035 STATUS mandatory 1036 DESCRIPTION 1037 "The number of dynamic updates issued by the local 1038 entity. Note that an attempt to flood a Dynamic 1039 update by the local entity is recorded as a single 1040 out message event. Furthermore, transit forwarding 1041 of Dynamic updates which are issued by other entities 1042 are not recorded by this counter." 1043 ::= { idprrid 11 } 1045 -- 5.5 IDPR RSQP Object Definitions 1046 idprrsqp OBJECT IDENTIFIER ::= { idpr 5 } 1048 idprrsqpReqIns OBJECT-TYPE 1049 SYNTAX Counter 1050 ACCESS read-only 1051 STATUS mandatory 1052 DESCRIPTION 1053 "The number of route request messages received. 1054 This object contains a valid counter only if 1055 full route server functionality is supported." 1056 ::= { idprrsqp 1 } 1058 idprrsqpResps OBJECT-TYPE 1059 SYNTAX Counter 1060 ACCESS read-only 1061 STATUS mandatory 1062 DESCRIPTION 1063 "The number of responses returned by the route 1064 server. This object contains valid data only 1065 if full route server functionality is supported." 1066 ::= { idprrsqp 2 } 1068 idprrsqpNegResps OBJECT-TYPE 1069 SYNTAX Counter 1070 ACCESS read-only 1071 STATUS mandatory 1072 DESCRIPTION 1073 "The number of negative route responses returned 1074 by the route server. Negative responses are 1075 returned if no route could be found. This 1076 object contains valid data only if full route 1077 server functionality is supported." 1078 ::= { idprrsqp 3 } 1080 idprrsqpReqInt OBJECT-TYPE 1081 SYNTAX INTEGER 1082 ACCESS read-only 1083 STATUS mandatory 1084 DESCRIPTION 1085 "The retransmission interval for route server 1086 requests measured in seconds" 1087 ::= { idprrsqp 4 } 1089 idprrsqpReqRet OBJECT-TYPE 1090 SYNTAX INTEGER 1091 ACCESS read-only 1092 STATUS mandatory 1093 DESCRIPTION 1094 "The number of retransmissions for route server 1095 requests before timing out the request" 1096 ::= { idprrsqp 5 } 1098 idprrsqpRidReqIns OBJECT-TYPE 1099 SYNTAX Counter 1100 ACCESS read-only 1101 STATUS mandatory 1102 DESCRIPTION 1103 "The number of requests received by a route server 1104 for RID configuration or dynamic information." 1105 ::= { idprrsqp 6 } 1107 idprrsqpRidReqOuts OBJECT-TYPE 1108 SYNTAX Counter 1109 ACCESS read-only 1110 STATUS mandatory 1111 DESCRIPTION 1112 "The number of responses issued by a route server 1113 for RID configuration or dynamic information." 1114 ::= { idprrsqp 7 } 1116 idprrsqpRSTab OBJECT-TYPE 1117 SYNTAX SEQUENCE OF IdprRSEntry 1118 ACCESS not-accessible 1119 STATUS mandatory 1120 DESCRIPTION 1121 "The table of other known route servers." 1122 ::= { idprrsqp 8 } 1124 idprRSEntry OBJECT-TYPE 1125 SYNTAX IdprRSEntry 1126 ACCESS not-accessible 1127 STATUS mandatory 1128 DESCRIPTION 1129 "Information for a single RS." 1130 INDEX { idprRSAD, idprRSId } 1131 ::= { idprrsqpRSTab 1 } 1133 IdprRSEntry ::= SEQUENCE { 1134 idprRSAD 1135 INTEGER, 1136 idprRSId 1137 INTEGER, 1138 idprRSSend 1139 INTEGER, 1140 idprRSAdvert 1141 INTEGER, 1142 idprRSLastSend 1143 TimeTicks, 1144 idprRSLastRecv 1145 TimeTicks 1146 } 1148 idprRSAD OBJECT-TYPE 1149 SYNTAX INTEGER 1150 ACCESS read-only 1151 STATUS mandatory 1152 DESCRIPTION 1153 "The AD identifier for the RS." 1155 ::= { idprRSEntry 1 } 1157 idprRSId OBJECT-TYPE 1158 SYNTAX INTEGER 1159 ACCESS read-only 1160 STATUS mandatory 1161 DESCRIPTION 1162 "The entity identifier of the RS." 1163 ::= { idprRSEntry 2 } 1165 idprRSSend OBJECT-TYPE 1166 SYNTAX INTEGER { 1167 ignore(0), 1168 send(1) 1169 } 1170 ACCESS read-only 1171 STATUS mandatory 1172 DESCRIPTION 1173 "The value of this field indicates whether or not 1174 the RS should be included in the list of RSs to 1175 which updates are sent." 1176 ::= { idprRSEntry 3 } 1178 idprRSAdvert OBJECT-TYPE 1179 SYNTAX INTEGER { 1180 ignore(0), 1181 advert(1) 1182 } 1183 ACCESS read-only 1184 STATUS mandatory 1185 DESCRIPTION 1186 "The value of this field indicates whether or not 1187 the RS should be included in the list of RSs 1188 which are advertized from this AD." 1189 ::= { idprRSEntry 4 } 1191 idprRSLastSend OBJECT-TYPE 1192 SYNTAX TimeTicks 1193 ACCESS read-only 1194 STATUS mandatory 1195 DESCRIPTION 1196 "The last time an update was sent to this RS." 1197 ::= { idprRSEntry 5 } 1199 idprRSLastRecv OBJECT-TYPE 1200 SYNTAX TimeTicks 1201 ACCESS read-only 1202 STATUS mandatory 1203 DESCRIPTION 1204 "The last time an update was received from this RS." 1205 ::= { idprRSEntry 6 } 1207 -- 5.6 IDPR PSP Object Definitions 1209 idprpsp OBJECT IDENTIFIER ::= { idpr 6 } 1211 idprpspInt OBJECT-TYPE 1212 SYNTAX INTEGER 1213 ACCESS read-only 1214 STATUS mandatory 1215 DESCRIPTION 1216 "The retransmission interval for path setup 1217 messages, in units of seconds." 1218 ::= { idprpsp 1 } 1220 idprpspRet OBJECT-TYPE 1221 SYNTAX INTEGER 1222 ACCESS read-only 1223 STATUS mandatory 1224 DESCRIPTION 1225 "The number of retransmissions of a path setup 1226 message before the message is declared 1227 undeliverable." 1228 ::= { idprpsp 2 } 1230 idprpspSetupIns OBJECT-TYPE 1231 SYNTAX Counter 1232 ACCESS read-only 1233 STATUS mandatory 1234 DESCRIPTION 1235 "The number of path setup messages received 1236 by a PG." 1237 ::= { idprpsp 3 } 1239 idprpspSetupOuts OBJECT-TYPE 1240 SYNTAX Counter 1241 ACCESS read-only 1242 STATUS mandatory 1243 DESCRIPTION 1244 "The number of path setup messages issued 1245 by a PG." 1246 ::= { idprpsp 4 } 1248 idprpspTeardownIns OBJECT-TYPE 1249 SYNTAX Counter 1250 ACCESS read-only 1251 STATUS mandatory 1252 DESCRIPTION 1253 "The number of path teardown messages received 1254 by a PG." 1255 ::= { idprpsp 5 } 1257 idprpspTeardownOuts OBJECT-TYPE 1258 SYNTAX Counter 1259 ACCESS read-only 1260 STATUS mandatory 1261 DESCRIPTION 1262 "The number of path teardown messages issued 1263 by a PG." 1264 ::= { idprpsp 6 } 1266 idprpspRefuseIns OBJECT-TYPE 1267 SYNTAX Counter 1268 ACCESS read-only 1269 STATUS mandatory 1270 DESCRIPTION 1271 "The number of path refuse messages received 1272 by a PG." 1273 ::= { idprpsp 7 } 1275 idprpspRefuseOuts OBJECT-TYPE 1276 SYNTAX Counter 1277 ACCESS read-only 1278 STATUS mandatory 1279 DESCRIPTION 1280 "The number of path refuse messages issued 1281 by a PG." 1282 ::= { idprpsp 8 } 1284 idprpspAcceptIns OBJECT-TYPE 1285 SYNTAX Counter 1286 ACCESS read-only 1287 STATUS mandatory 1288 DESCRIPTION 1289 "The number of path accept messages received 1290 by a PG." 1291 ::= { idprpsp 9 } 1293 idprpspAcceptOuts OBJECT-TYPE 1294 SYNTAX Counter 1295 ACCESS read-only 1296 STATUS mandatory 1297 DESCRIPTION 1298 "The number of path accept messages issued 1299 by a PG." 1300 ::= { idprpsp 10 } 1302 idprpspRepairIns OBJECT-TYPE 1303 SYNTAX Counter 1304 ACCESS read-only 1305 STATUS mandatory 1306 DESCRIPTION 1307 "The number of path repair messages received 1308 by a PG." 1309 ::= { idprpsp 11 } 1311 idprpspRepairOuts OBJECT-TYPE 1312 SYNTAX Counter 1313 ACCESS read-only 1314 STATUS mandatory 1315 DESCRIPTION 1316 "The number of path repair messages issued 1317 by a PG." 1318 ::= { idprpsp 12 } 1320 idprpspErrorIns OBJECT-TYPE 1321 SYNTAX Counter 1322 ACCESS read-only 1323 STATUS mandatory 1324 DESCRIPTION 1325 "The number of path error messages received 1326 by a PG." 1327 ::= { idprpsp 13 } 1329 idprpspErrorOuts OBJECT-TYPE 1330 SYNTAX Counter 1331 ACCESS read-only 1332 STATUS mandatory 1333 DESCRIPTION 1334 "The number of path error messages issued 1335 by a PG." 1336 ::= { idprpsp 14 } 1338 -- 1339 -- PCP Path Table 1340 -- 1341 idprpspPathTab OBJECT-TYPE 1342 SYNTAX SEQUENCE OF IdprPathEntry 1343 ACCESS not-accessible 1344 STATUS mandatory 1345 DESCRIPTION 1346 "The table IDPR paths." 1347 ::= { idprpsp 15 } 1349 idprPathEntry OBJECT-TYPE 1350 SYNTAX IdprPathEntry 1351 ACCESS not-accessible 1352 STATUS mandatory 1353 DESCRIPTION 1354 "Information for a single IDPR path." 1355 INDEX { idprPathAD, idprPathEnt, idprPathId } 1356 ::= { idprpspPathTab 1 } 1358 IdprPathEntry ::= SEQUENCE { 1359 idprPathAD 1360 INTEGER, 1361 idprPathEnt 1362 INTEGER, 1363 idprPathId 1364 INTEGER, 1365 idprPathDst 1366 INTEGER, 1367 idprPathPrevPGAD 1368 INTEGER, 1370 idprPathPrevPGId 1371 INTEGER, 1372 idprPathPrevVGAD 1373 INTEGER, 1374 idprPathPrevVGId 1375 INTEGER, 1376 idprPathNextPGAD 1377 INTEGER, 1378 idprPathNextPGId 1379 INTEGER, 1380 idprPathNextVGAD 1381 INTEGER, 1382 idprPathNextVGId 1383 INTEGER, 1384 idprPathRefCnt 1385 INTEGER, 1386 idprPathState 1387 INTEGER, 1388 idprPathMsgs 1389 Counter, 1390 idprPathMsgsMax 1391 INTEGER, 1392 idprPathBytes 1393 Counter, 1394 idprPathBytesMax 1395 INTEGER, 1396 idprPathExpire 1397 INTEGER, 1398 idprPathAuth 1399 INTEGER, 1400 idprPathVer 1401 BitField, 1402 idprPathTos 1403 INTEGER, 1404 idprPathUCI 1405 INTEGER, 1406 idprPathTrType 1407 INTEGER 1408 } 1410 idprPathAD OBJECT-TYPE 1411 SYNTAX INTEGER 1412 ACCESS read-only 1413 STATUS mandatory 1414 DESCRIPTION 1415 "The administrative domain of the PG that 1416 originated the path." 1417 ::= { idprPathEntry 1 } 1419 idprPathEnt OBJECT-TYPE 1420 SYNTAX INTEGER 1421 ACCESS read-only 1422 STATUS mandatory 1423 DESCRIPTION 1424 "The entity identifier of the PG that 1425 originated the path." 1426 ::= { idprPathEntry 2 } 1428 idprPathId OBJECT-TYPE 1429 SYNTAX INTEGER 1430 ACCESS read-only 1431 STATUS mandatory 1432 DESCRIPTION 1433 "The unique identifier assigned to a path 1434 by the originating PG." 1435 ::= { idprPathEntry 3 } 1437 idprPathDst OBJECT-TYPE 1438 SYNTAX INTEGER 1439 ACCESS read-only 1440 STATUS mandatory 1441 DESCRIPTION 1442 "The destination or terminating AD for the path." 1443 ::= { idprPathEntry 4 } 1445 idprPathPrevPGAD OBJECT-TYPE 1446 SYNTAX INTEGER 1447 ACCESS read-only 1448 STATUS mandatory 1449 DESCRIPTION 1450 "The AD of the previous hop PG. If a path entered 1451 through another PG in the same domain, the value 1452 returned by this object will be the same as the AD 1453 for the PG being queried." 1454 ::= { idprPathEntry 5 } 1456 idprPathPrevPGId OBJECT-TYPE 1457 SYNTAX INTEGER 1458 ACCESS read-only 1459 STATUS mandatory 1460 DESCRIPTION 1461 "The entity identifier of the previous hop PG." 1462 ::= { idprPathEntry 6 } 1464 idprPathPrevVGAD OBJECT-TYPE 1465 SYNTAX INTEGER 1466 ACCESS read-only 1467 STATUS mandatory 1468 DESCRIPTION 1469 "The AD of the previous hop VG. This object 1470 refers to the AD of entry VG, which corresponds 1471 to the AD immediately before the current AD 1472 along a path." 1473 ::= { idprPathEntry 7 } 1475 idprPathPrevVGId OBJECT-TYPE 1476 SYNTAX INTEGER 1477 ACCESS read-only 1478 STATUS mandatory 1479 DESCRIPTION 1480 "The identifier of the previous hop VG." 1481 ::= { idprPathEntry 8 } 1483 idprPathNextPGAD OBJECT-TYPE 1484 SYNTAX INTEGER 1485 ACCESS read-only 1486 STATUS mandatory 1487 DESCRIPTION 1488 "The AD of the next hop PG. If a path is exiting 1489 through another PG in the same domain, the value 1490 returned by this object will be the same as the AD 1491 for the PG being queried." 1492 ::= { idprPathEntry 9 } 1494 idprPathNextPGId OBJECT-TYPE 1495 SYNTAX INTEGER 1496 ACCESS read-only 1497 STATUS mandatory 1498 DESCRIPTION 1499 "The entity identifier of the next hop PG." 1500 ::= { idprPathEntry 10 } 1502 idprPathNextVGAD OBJECT-TYPE 1503 SYNTAX INTEGER 1504 ACCESS read-only 1505 STATUS mandatory 1506 DESCRIPTION 1507 "The AD of the next hop VG. This object refers 1508 to the AD of the exit VG, which corresponds to 1509 the AD after the current AD along a path." 1510 ::= { idprPathEntry 11 } 1512 idprPathNextVGId OBJECT-TYPE 1513 SYNTAX INTEGER 1514 ACCESS read-only 1515 STATUS mandatory 1516 DESCRIPTION 1517 "The identifier of the next hop VG." 1518 ::= { idprPathEntry 12 } 1520 idprPathRefCnt OBJECT-TYPE 1521 SYNTAX INTEGER 1522 ACCESS read-only 1523 STATUS mandatory 1524 DESCRIPTION 1525 "The number of address map entries referencing 1526 a path." 1527 ::= { idprPathEntry 13 } 1529 idprPathState OBJECT-TYPE 1530 SYNTAX INTEGER { 1531 idle (1), -- the path is no longer being used 1532 start (2), -- a setup request has been received 1533 setup (3), -- a setup has been sent 1534 acceptwait (4), -- an ACK has been received 1535 active (5), -- the accept has been received 1536 dying (6) -- teardown has been received/sent 1537 } 1538 ACCESS read-only 1539 STATUS mandatory 1540 DESCRIPTION 1541 "The current state of the path as enumerated above." 1542 ::= { idprPathEntry 14 } 1544 idprPathMsgs OBJECT-TYPE 1545 SYNTAX Counter 1546 ACCESS read-only 1547 STATUS mandatory 1548 DESCRIPTION 1549 "The number of messages (i.e., packets) that has 1550 been forwarded on this path." 1551 ::= { idprPathEntry 15 } 1553 idprPathMsgsMax OBJECT-TYPE 1554 SYNTAX INTEGER 1555 ACCESS read-only 1556 STATUS mandatory 1557 DESCRIPTION 1558 "The maximum number of data messages 1559 (i.e., packets) that can be forwarded before 1560 a path expires." 1561 ::= { idprPathEntry 16 } 1563 idprPathBytes OBJECT-TYPE 1564 SYNTAX Counter 1565 ACCESS read-only 1566 STATUS mandatory 1567 DESCRIPTION 1568 "The number of bytes of data forwarded through 1569 a path thus far." 1570 ::= { idprPathEntry 17 } 1572 idprPathBytesMax OBJECT-TYPE 1573 SYNTAX INTEGER 1574 ACCESS read-only 1575 STATUS mandatory 1576 DESCRIPTION 1577 "The total allowable number of bytes of data 1578 that can be forwarded on a path before the 1579 path expires." 1580 ::= { idprPathEntry 18 } 1582 idprPathExpire OBJECT-TYPE 1583 SYNTAX INTEGER 1584 ACCESS read-only 1585 STATUS mandatory 1586 DESCRIPTION 1587 "The amount of time remaining (in seconds) before 1588 a path expires." 1589 ::= { idprPathEntry 19 } 1591 idprPathAuth OBJECT-TYPE 1592 SYNTAX INTEGER 1593 ACCESS read-only 1594 STATUS mandatory 1595 DESCRIPTION 1596 "The authentication protocol used for a path." 1597 ::= { idprPathEntry 20 } 1599 idprPathVer OBJECT-TYPE 1600 SYNTAX BitField 1601 ACCESS read-only 1602 STATUS mandatory 1603 DESCRIPTION 1604 "The version of the IDPR data encapsulation protocol 1605 supported by a path. 1606 Bit Position 0 == Version 1 1607 Bit Position 1 == Version 2 1608 ...and so on... 1609 Bit Position n == Version n+1 1610 where n <= 31." 1611 ::= { idprPathEntry 21 } 1613 -- The idprPathTos and idprPathUCI objects were originally 1614 -- specified with a syntax of OCTET STRING (Size 8). The 1615 -- syntax has been changed to INTEGER (0..255), because we 1616 -- assume that a path is uniquely associated with only one 1617 -- TOS or UCI value. However, the value 0 is special and 1618 -- denotes that a path supports traffic regardless of TOS 1619 -- or UCI specifications. 1621 idprPathTos OBJECT-TYPE 1622 SYNTAX INTEGER (0..255) 1623 ACCESS read-only 1624 STATUS mandatory 1625 DESCRIPTION 1626 "The type of service (TOS) associated with a path. 1627 Only packets with a matching the TOS are 1628 forwarded through the path, with one exception. 1629 A TOS value of 0 indicate that a path supports 1630 all types of service, regardless of specification. 1632 If a path is used to transport IP packets, this 1633 object refers to the 8-bit binary-encoded TOS 1634 field near the beginning of the IP header." 1635 ::= { idprPathEntry 22 } 1637 idprPathUCI OBJECT-TYPE 1638 SYNTAX INTEGER (0..255) 1639 ACCESS read-only 1640 STATUS mandatory 1641 DESCRIPTION 1642 "The user class identifier (UCI) associated with 1643 the path. Only packets matching the UCI returned 1644 by this object are transported over the path. A 1645 value of 0 indicates that a path supports all user 1646 classes, regardless of specification. A non-zero 1647 value indicates that only packets matching the 1648 UCI are capable of using the path." 1649 ::= { idprPathEntry 23 } 1651 idprPathTrType OBJECT-TYPE 1652 SYNTAX INTEGER (0..255) 1653 ACCESS read-only 1654 STATUS optional 1655 DESCRIPTION 1656 "The traffic type associated with the path. 1657 Only packets with a matching traffic type are 1658 transported over the path, with one exception. 1659 A value of 0 indicates that a path supports all 1660 traffic types, regardless of specification. 1661 A non-zero value indicates that only packets 1662 matching the traffic type are capable of using 1663 the path. 1665 If a path is used to transport IP packets, this 1666 object refers to the traffic type encoded as 1667 specified in IP option 144 (decimal)." 1668 ::= { idprPathEntry 24 } 1670 -- 1671 -- PCP Path Route Table. This table returns the routes 1672 -- taken by active IDPR paths. The route for each path 1673 -- is specified as the set of VGs through which the path 1674 -- traverses. The table index field is used to select 1675 -- information about each hop of path route. 1676 -- 1677 -- In the present specification, routes are provided 1678 -- only for paths that originate from the local domain. 1679 -- Transit or terminating paths are not included in the 1680 -- path route table. 1681 -- 1682 idprpspPathRouteTab OBJECT-TYPE 1683 SYNTAX SEQUENCE OF IdprPathRouteEntry 1684 ACCESS not-accessible 1685 STATUS mandatory 1686 DESCRIPTION 1687 "IDPR path route table. This table returns 1688 the routes taken by active IDPR paths. Each 1689 route is returned as the next hop AD and entry 1690 VG number, which can be thought of equivalently 1691 as the set of VGs through which the path 1692 traverses." 1693 ::= { idprpsp 16 } 1695 idprPathRouteEntry OBJECT-TYPE 1696 SYNTAX IdprPathRouteEntry 1697 ACCESS not-accessible 1698 STATUS mandatory 1699 DESCRIPTION 1700 "IDPR path route table entry. Each table entry 1701 corresponds a hop along the routing path. The 1702 index for this table corresponds to the path 1703 identifier plus a table index that denotes a 1704 path hop count from the source." 1705 INDEX { idprPathRouteAD, idprPathRouteEnt, 1706 idprPathRouteId, idprPathRouteIndex } 1707 ::= { idprpspPathRouteTab 1 } 1709 IdprPathRouteEntry ::= SEQUENCE { 1710 idprPathRouteAD 1711 INTEGER, 1712 idprPathRouteEnt 1713 INTEGER, 1714 idprPathRouteId 1715 INTEGER, 1716 idprPathRouteIndex 1717 INTEGER, 1718 idprPathRouteVGAD 1719 INTEGER, 1720 idprPathRouteVGId 1721 INTEGER, 1722 idprPathRouteADCmp 1723 INTEGER, 1724 idprPathRouteTrnPlcy 1725 INTEGER 1726 } 1728 -- 1729 -- Note that the first four objects in the table 1730 -- are used as a table index. The index consists 1731 -- of the path identifier along with an index which 1732 -- serves as a hop count field. 1733 -- 1734 idprPathRouteAD OBJECT-TYPE 1735 SYNTAX INTEGER 1736 ACCESS read-only 1737 STATUS mandatory 1738 DESCRIPTION 1739 "This object returns the AD identifier part of 1740 the path identifier. The object gives the AD 1741 that initiated path setup." 1742 ::= { idprPathRouteEntry 1 } 1744 idprPathRouteEnt OBJECT-TYPE 1745 SYNTAX INTEGER 1746 ACCESS read-only 1747 STATUS mandatory 1748 DESCRIPTION 1749 "This object returns the entity identifier part 1750 of the path identifier." 1751 ::= { idprPathRouteEntry 2 } 1753 idprPathRouteId OBJECT-TYPE 1754 SYNTAX INTEGER 1755 ACCESS read-only 1756 STATUS mandatory 1757 DESCRIPTION 1758 "This object returns the local identifier part 1759 of the path identifier." 1760 ::= { idprPathRouteEntry 3 } 1762 idprPathRouteIndex OBJECT-TYPE 1763 SYNTAX INTEGER 1764 ACCESS read-only 1765 STATUS mandatory 1766 DESCRIPTION 1767 "This object returns the path route table hop 1768 index. The first hop of the routing path is 1769 assigned the index value 1. The 'n'th hop is 1770 given the value n." 1771 ::= { idprPathRouteEntry 4 } 1773 idprPathRouteVGAD OBJECT-TYPE 1774 SYNTAX INTEGER 1775 ACCESS read-only 1776 STATUS mandatory 1777 DESCRIPTION 1778 "This object returns the administrative domain 1779 for the hop being referenced." 1780 ::= { idprPathRouteEntry 5 } 1782 idprPathRouteVGId OBJECT-TYPE 1783 SYNTAX INTEGER 1784 ACCESS read-only 1785 STATUS mandatory 1786 DESCRIPTION 1787 "This object returns the entry VG sub-identifier 1788 for the hop. The pair that is given by 1789 idprPathRouteAD and idprPathRouteVGId identify 1790 the VG through which a path traverses." 1791 ::= { idprPathRouteEntry 6 } 1793 idprPathRouteADCmp OBJECT-TYPE 1794 SYNTAX INTEGER 1795 ACCESS read-only 1796 STATUS mandatory 1797 DESCRIPTION 1798 "This object returns the domain component that 1799 advertised the RID information which led to 1800 the selection of the VG as part of the path. 1801 The value returned corresponds to the ``CMP'' 1802 field provided with path setup messages." 1803 ::= { idprPathRouteEntry 7 } 1805 idprPathRouteTrnPlcy OBJECT-TYPE 1806 SYNTAX INTEGER 1807 ACCESS read-only 1808 STATUS mandatory 1809 DESCRIPTION 1810 "This object returns the transit policy used to 1811 satisfy the path request. The value returned 1812 corresponds to the ``TP'' field provided with 1813 path setup messages." 1814 ::= { idprPathRouteEntry 8 } 1816 -- 5.7 IDPR Data Object Definitions 1818 idprdata OBJECT IDENTIFIER ::= { idpr 7 } 1820 idprdataVer OBJECT-TYPE 1821 SYNTAX BitField 1822 ACCESS read-only 1823 STATUS mandatory 1824 DESCRIPTION 1825 "The versions of the data encapsulation protocol 1826 supported by the PG being queried. One or more 1827 data protocol versions may be supported concurrently. 1828 Bit Position 0 == Version 1 1829 Bit Position 1 == Version 2 1830 ...and so on... 1831 Bit Position n == Version n+1 1832 where n <= 31." 1833 ::= { idprdata 1 } 1835 idprdataErrs OBJECT-TYPE 1836 SYNTAX Counter 1837 ACCESS read-only 1838 STATUS mandatory 1839 DESCRIPTION 1840 "The number of messages received which could 1841 not be processed." 1842 ::= { idprdata 2 } 1844 idprdataUnkPaths OBJECT-TYPE 1845 SYNTAX Counter 1846 ACCESS read-only 1847 STATUS mandatory 1848 DESCRIPTION 1849 "The number of data messages received by this 1850 entity referencing an unknown path." 1851 ::= { idprdata 3 } 1853 idprdataUnkProtos OBJECT-TYPE 1854 SYNTAX Counter 1855 ACCESS read-only 1856 STATUS mandatory 1857 DESCRIPTION 1858 "The number of data packets received that had an 1859 invalid protocol field. Each IDPR data message 1860 has an eight bit field which specifies the network 1861 layer protocol carried in the data message; e.g., 1862 IP is one of several possible network layer 1863 protocol types." 1864 ::= { idprdata 4 } 1866 idprdataBadLengths OBJECT-TYPE 1867 SYNTAX Counter 1868 ACCESS read-only 1869 STATUS mandatory 1870 DESCRIPTION 1871 "The number of data packets received with an 1872 invalid length field." 1873 ::= { idprdata 5 } 1875 idprdataBadAuths OBJECT-TYPE 1876 SYNTAX Counter 1877 ACCESS read-only 1878 STATUS mandatory 1879 DESCRIPTION 1880 "The number of data packets received that failed 1881 authentication checks. This object contains 1882 a valid counter only if authentication is used 1883 by the data protocol." 1884 ::= { idprdata 6 } 1886 -- 5.8 IDPR Address Mapping Table Object Definitions 1888 idpraddr OBJECT IDENTIFIER ::= { idpr 8 } 1890 idpraddrTab OBJECT-TYPE 1891 SYNTAX SEQUENCE OF IdprAddrEntry 1892 ACCESS not-accessible 1893 STATUS mandatory 1894 DESCRIPTION 1895 "The address mapping table that translates 1896 source and destination addresses into IDPR 1897 paths." 1898 ::= { idpraddr 1 } 1900 idpraddrEntry OBJECT-TYPE 1901 SYNTAX IdprAddrEntry 1902 ACCESS not-accessible 1903 STATUS mandatory 1904 DESCRIPTION 1905 "Information for a single IDPR Address Map entry." 1907 INDEX { idpraddrSrc, idpraddrDst, idpraddrTos, 1908 idpraddrProto, idpraddrSrcPort, 1909 idpraddrDstPort, idpraddrTrType } 1910 ::= { idpraddrTab 1 } 1912 IdprAddrEntry ::= SEQUENCE { 1913 idpraddrSrc 1914 IpAddress, 1915 idpraddrDst 1916 IpAddress, 1917 idpraddrSrcMask 1918 IpAddress, 1919 idpraddrDstMask 1920 IpAddress, 1921 idpraddrTos 1922 INTEGER, 1923 idpraddrProto 1924 INTEGER, 1925 idpraddrSrcPort 1926 INTEGER, 1927 idpraddrDstPort 1928 INTEGER, 1929 idpraddrUCI 1930 INTEGER, 1931 idpraddrTrType 1932 INTEGER, 1933 idpraddrPathAD 1934 INTEGER, 1935 idpraddrPathEnt 1936 INTEGER, 1937 idpraddrPathId 1938 INTEGER, 1939 idpraddrState 1940 INTEGER, 1941 idpraddrPriority 1942 INTEGER 1943 } 1945 idpraddrSrc OBJECT-TYPE 1946 SYNTAX IpAddress 1947 ACCESS read-only 1948 STATUS mandatory 1949 DESCRIPTION 1950 "The source address for the address map entry." 1951 ::= { idpraddrEntry 1 } 1953 idpraddrDst OBJECT-TYPE 1954 SYNTAX IpAddress 1955 ACCESS read-only 1956 STATUS mandatory 1957 DESCRIPTION 1958 "The destination address for the address map entry" 1959 ::= { idpraddrEntry 2 } 1961 idpraddrSrcMask OBJECT-TYPE 1962 SYNTAX IpAddress 1963 ACCESS read-only 1964 STATUS mandatory 1965 DESCRIPTION 1966 "The source address mask for the address map entry." 1967 ::= { idpraddrEntry 3} 1969 idpraddrDstMask OBJECT-TYPE 1970 SYNTAX IpAddress 1971 ACCESS read-only 1972 STATUS mandatory 1973 DESCRIPTION 1974 "The destination address mask for the address 1975 map entry." 1976 ::= { idpraddrEntry 4 } 1978 idpraddrTos OBJECT-TYPE 1979 SYNTAX INTEGER (0..255) 1980 ACCESS read-only 1981 STATUS mandatory 1982 DESCRIPTION 1983 "The TOS for the address map entry." 1984 ::= { idpraddrEntry 5} 1986 idpraddrProto OBJECT-TYPE 1987 SYNTAX INTEGER 1988 ACCESS read-only 1989 STATUS mandatory 1990 DESCRIPTION 1991 "The IP protocol for the address map entry." 1992 ::= { idpraddrEntry 6 } 1994 idpraddrSrcPort OBJECT-TYPE 1995 SYNTAX INTEGER 1996 ACCESS read-only 1997 STATUS mandatory 1998 DESCRIPTION 1999 "The higher layer (transport) protocol source port 2000 for the address map entry." 2001 ::= { idpraddrEntry 7 } 2003 idpraddrDstPort OBJECT-TYPE 2004 SYNTAX INTEGER 2005 ACCESS read-only 2006 STATUS mandatory 2007 DESCRIPTION 2008 "The higher layer (transport) protocol destination 2009 port for the address map entry." 2010 ::= { idpraddrEntry 8 } 2012 idpraddrUCI OBJECT-TYPE 2013 SYNTAX INTEGER (0..255) 2014 ACCESS read-only 2015 STATUS mandatory 2016 DESCRIPTION 2017 "The user class identifier associated with the 2018 address map entry." 2019 ::= { idpraddrEntry 9 } 2021 idpraddrTrType OBJECT-TYPE 2022 SYNTAX INTEGER (0..255) 2023 ACCESS read-only 2024 STATUS optional 2025 DESCRIPTION 2026 "The traffic type IP option associated with the 2027 address map. The traffic type specification is 2028 an abstract integer tag which is used to associate 2029 user data packets of a given type with a path." 2030 ::= { idpraddrEntry 10 } 2032 idpraddrPathAD OBJECT-TYPE 2033 SYNTAX INTEGER 2034 ACCESS read-only 2035 STATUS mandatory 2036 DESCRIPTION 2037 "The path AD identifier for the address map entry." 2038 ::= { idpraddrEntry 11 } 2040 idpraddrPathEnt OBJECT-TYPE 2041 SYNTAX INTEGER 2042 ACCESS read-only 2043 STATUS mandatory 2044 DESCRIPTION 2045 "The path entity identifier for the address 2046 map entry." 2047 ::= { idpraddrEntry 12 } 2049 idpraddrPathId OBJECT-TYPE 2050 SYNTAX INTEGER 2051 ACCESS read-only 2052 STATUS mandatory 2053 DESCRIPTION 2054 "The local path identifier for the address map 2055 entry." 2056 ::= { idpraddrEntry 13 } 2058 idpraddrState OBJECT-TYPE 2059 SYNTAX INTEGER { 2060 idle (1), -- no request pending, no path assigned 2061 waiting (2), -- request pending, no path assigned 2062 active (3) -- path assigned 2063 } 2064 ACCESS read-only 2065 STATUS mandatory 2066 DESCRIPTION 2067 "The state of the address map entry. An address 2068 map entry is in effect only when it is in the 2069 active(3) state." 2070 ::= { idpraddrEntry 14 } 2072 idpraddrPriority OBJECT-TYPE 2073 SYNTAX INTEGER (0..255) 2074 ACCESS read-only 2075 STATUS optional 2076 DESCRIPTION 2077 "The packet priority level associated with 2078 the address map entry." 2079 ::= { idprPathEntry 15 } 2081 -- 5.9 Source Policy Table 2083 idprsrcplcy OBJECT IDENTIFIER ::= { idpr 9 } 2085 idprsrcplcyTab OBJECT-TYPE 2086 SYNTAX SEQUENCE OF IdprSrcPlcyEntry 2087 ACCESS not-accessible 2088 STATUS mandatory 2089 DESCRIPTION 2090 "Table of source policies defined for this AD." 2091 ::= { idprsrcplcy 1 } 2093 idprSrcPlcyEntry OBJECT-TYPE 2094 SYNTAX IdprSrcPlcyEntry 2095 ACCESS not-accessible 2096 STATUS mandatory 2097 DESCRIPTION 2098 "Table entry for source policies for this AD." 2099 INDEX { idprSrcPlcyId } 2100 ::= { idprsrcplcyTab 1 } 2102 IdprSrcPlcyEntry ::= SEQUENCE { 2103 idprSrcPlcyId 2104 INTEGER, 2105 idprSrcPlcyStatus 2106 INTEGER, 2107 idprSrcPlcyInfoSyntax 2108 INTEGER, 2109 idprSrcPlcyInfo 2110 OCTET STRING 2111 } 2113 idprSrcPlcyId OBJECT-TYPE 2114 SYNTAX INTEGER 2115 ACCESS read-write 2116 STATUS mandatory 2117 DESCRIPTION 2118 "The identifier of the source policy." 2119 ::= { idprSrcPlcyEntry 1 } 2121 idprSrcPlcyStatus OBJECT-TYPE 2122 SYNTAX INTEGER { 2123 active(1), 2124 inactive(2) 2125 } 2126 ACCESS read-write 2127 STATUS optional 2128 DESCRIPTION 2129 "Status of the source policy. A source policy 2130 may be defined but may not be active. An 2131 inactive source policy is ignored during path 2132 computation. 2134 For implementations that support table write 2135 operations, writing the value inactive(2) 2136 for an active source policy causes the policy 2137 to become inactive. Changing the state of the 2138 source policy to active(1) re-enables the 2139 source policy." 2140 ::= { idprSrcPlcyEntry 2 } 2142 idprSrcPlcyInfoSyntax OBJECT-TYPE 2143 SYNTAX INTEGER { 2144 displaystring(1), 2145 opaque(2), 2146 other(3) 2147 } 2148 ACCESS read-write 2149 STATUS mandatory 2150 DESCRIPTION 2151 "This object gives the syntax of the 2152 idprSrcPlcyInfo object when it is read. If 2153 the syntax is displaystring(1), the source 2154 policy is returned as a DisplayString following 2155 the syntax recommended by the IDPR configuration 2156 guide. The value opaque(2) indicates that an 2157 ASN.1 syntax is wrapped inside the Opaque data 2158 type. The value other(3) is used for all 2159 other syntaxes." 2160 ::= { idprSrcPlcyEntry 3 } 2162 idprSrcPlcyInfo OBJECT-TYPE 2163 SYNTAX OCTET STRING 2164 ACCESS read-write 2165 STATUS mandatory 2166 DESCRIPTION 2167 "Source policy specification. A new source 2168 policy is supported by writing the new policy 2169 specification to this object." 2170 ::= { idprSrcPlcyEntry 4 } 2172 -- 5.10 Transit Policy Table 2174 idprtrnplcy OBJECT IDENTIFIER ::= { idpr 10 } 2176 idprtrnplcyTab OBJECT-TYPE 2177 SYNTAX SEQUENCE OF IdprTrnPlcyEntry 2178 ACCESS not-accessible 2179 STATUS mandatory 2180 DESCRIPTION 2181 "Table of transit policies known to this AD. This 2182 table contains both transit policies defined 2183 locally, as well as those received from other 2184 domains via configuration messages." 2185 ::= { idprtrnplcy 1 } 2187 idprTrnPlcyEntry OBJECT-TYPE 2188 SYNTAX IdprTrnPlcyEntry 2189 ACCESS not-accessible 2190 STATUS mandatory 2191 DESCRIPTION 2192 "Table entry for transit policies for this AD." 2193 INDEX { idprTrnPlcyAD, idprTrnPlcyId } 2194 ::= { idprtrnplcyTab 1 } 2196 IdprTrnPlcyEntry ::= SEQUENCE { 2197 idprTrnPlcyAD 2198 INTEGER, 2199 idprTrnPlcyEnt 2200 INTEGER, 2201 idprTrnPlcyId 2202 INTEGER, 2203 idprTrnPlcyStatus 2204 INTEGER, 2205 idprTrnPlcyInfoSyntax 2206 INTEGER, 2207 idprTrnPlcyInfo 2208 OCTET STRING 2209 } 2211 idprTrnPlcyAD OBJECT-TYPE 2212 SYNTAX INTEGER 2213 ACCESS read-write 2214 STATUS mandatory 2215 DESCRIPTION 2216 "The AD that advertised the transit policy." 2217 ::= { idprTrnPlcyEntry 1 } 2219 idprTrnPlcyEnt OBJECT-TYPE 2220 SYNTAX INTEGER 2221 ACCESS read-write 2222 STATUS mandatory 2223 DESCRIPTION 2224 "The entity that advertised the transit policy." 2225 ::= { idprTrnPlcyEntry 2 } 2227 idprTrnPlcyId OBJECT-TYPE 2228 SYNTAX INTEGER 2229 ACCESS read-write 2230 STATUS mandatory 2231 DESCRIPTION 2232 "The identifier of the transit policy." 2233 ::= { idprTrnPlcyEntry 3 } 2235 idprTrnPlcyStatus OBJECT-TYPE 2236 SYNTAX INTEGER { 2237 active(1), 2238 inactive(2) 2239 } 2240 ACCESS read-write 2241 STATUS optional 2242 DESCRIPTION 2243 "Status of the transit policy. Transit policies 2244 that are advertised and used for route computation 2245 are marked as active. Transit policies received 2246 from remote domains are always marked as being in 2247 the active state. 2249 Note that a local domain's transit policies may 2250 be in the active or inactive state. Inactive 2251 transit policies are not including in RID 2252 configuration updates and are not used by route 2253 computation. 2255 For implementations that support table write 2256 operations, writing the value inactive(2) to a 2257 defined transit policy puts the policy into a 2258 state where it is no longer advertised. 2260 Depending on implementation, changing the status 2261 to inactive(2) may not necessarily remove the 2262 entry from the transit policy table. Changing 2263 the state to active(1) may re-enable the transit 2264 policy." 2265 ::= { idprTrnPlcyEntry 4 } 2267 idprTrnPlcyInfoSyntax OBJECT-TYPE 2268 SYNTAX INTEGER { 2269 displaystring(1), 2270 opaque(2), 2271 other(3) 2272 } 2273 ACCESS read-write 2274 STATUS mandatory 2275 DESCRIPTION 2276 "This object specifies the syntax of the 2277 idprTrnPlcyInfo object. If the syntax is 2278 displaystring(1), the transit policy 2279 specification is returned as a DisplayString 2280 following the syntax recommended by the IDPR 2281 configuration guide. The value opaque(2) 2282 indicates that an ASN.1 syntax is wrapped 2283 inside the Opaque data type. The value other(3) 2284 is used for all other syntaxes." 2285 ::= { idprTrnPlcyEntry 5 } 2287 idprTrnPlcyInfo OBJECT-TYPE 2288 SYNTAX OCTET STRING 2289 ACCESS read-write 2290 STATUS mandatory 2291 DESCRIPTION 2292 "Transit policy specification. A new transit 2293 policy is supported by writing the new policy 2294 specification to this object. Reading from 2295 this object will return the current transit 2296 policy specification." 2297 ::= { idprTrnPlcyEntry 6 } 2299 END 2301 5 Trap Messages 2303 This section describes the trap messages that are issued by the network 2304 management system. 2306 RFCxxxx-TRAP DEFINITIONS ::= BEGIN 2308 IMPORTS 2309 experimental, IpAddress, Counter, TimeTicks 2310 FROM RFC-1155 2311 OBJECT-TYPE 2312 FROM RFC-1212 2313 TRAP-TYPE 2314 FROM RFC-1215; 2316 idprADRepChange TRAP-TYPE 2317 ENTERPRISE idpr 2318 VARIABLES { 2319 idprAD, -- AD and id of entity 2320 idprId, -- issuing trap message. 2321 idprADRep -- New AD representative. 2322 } 2323 DESCRIPTION 2324 "This trap is issued when the AD representative 2325 for a domain has changed. It is issued in 2326 response to the local domain becoming partitioned." 2327 ::= 1 2329 idprPGStateChange TRAP-TYPE 2330 ENTERPRISE idpr 2331 VARIABLES { 2332 idprPGAD, -- AD and id of remote entity 2333 idprPGId, -- affected by state change. 2334 idprPGStatus, -- New PG reachability state. 2335 idprPGType -- PG type. 2336 idprPGTrans, -- Number of transitions. 2337 } 2338 DESCRIPTION 2339 "This trap is issued when the VGP Pair-PG protocol 2340 has declared a peer entity as having transitioned 2341 between reachable and unreachable states. The 2342 peer entities may be in the same domain (i.e., IDPR 2343 neighbor or peer entities) or in an adjoining 2344 domain (i.e., adjacent entities). The variable 2345 binding list identifies the remote entity for which 2346 the state has changed." 2347 ::= 2 2349 idprVGRepChange TRAP-TYPE 2350 ENTERPRISE idpr 2351 VARIABLES { 2352 idprVGAdj, -- VG identifier for which 2353 idprVGId, -- there is a new AD rep. 2354 idprVGVGRep -- New VG representative. 2355 } 2356 DESCRIPTION 2357 "This trap is issued when the VG representative, 2358 has changed, and is issued only if the IDPR 2359 implementation supports multiple peer PGs in a VG." 2360 ::= 3 2362 idprpspError TRAP-TYPE 2363 ENTERPRISE idpr 2364 VARIABLES { 2365 idprPathAD, -- Path identifier 2366 idprPathEnt, -- which experienced 2367 idprPathId -- the path error. 2368 } 2369 DESCRIPTION 2370 "This trap message is issued when a path 2371 encounters an abnormal, un-recoverable error 2372 resulting in tear down of the path. The 2373 typical cause of such errors include one or 2374 more PGs along a path becoming unreachable. 2376 Tear down of paths due to path lifetime or 2377 usage expirations are considered to be normal 2378 events and do not result in trap messages 2379 being issued." 2380 ::= 4 2382 idprtrnPlcyExpired TRAP-TYPE 2383 ENTERPRISE idpr 2384 VARIABLES { 2385 idprTrnPlcyAD, -- Domain and entity that 2386 idprTrnPlcyEnt, -- issued the transit policy. 2387 idprTrnPlcyId -- Transit policy number. 2388 } 2389 DESCRIPTION 2390 "A RID configuration message has expired. 2391 Failure to receive periodic RID configuration 2392 messages imply that a domain may no longer 2393 be reachable or that the transit policies 2394 associated with it are no longer valid." 2395 ::= 5 2397 END 2399 6 Security Considerations 2401 Security issues are not discussed in this memo. 2403 7 Acknowledgements 2405 We would like to acknowledge the assistance of all the members of the 2406 IDPR Working Group and particularly the following individuals: 2408 Ken Carlberg, SAIC 2409 Dan Lee, SRI 2410 Mark Sleeper, Sparta 2411 Martha Steenstrup, BBN 2413 8 References 2415 [1] V. Cerf, IAB Recommendations for the Development of Internet Network 2416 Management Standards, Internet Working Group Request for Comments 1052. 2417 Network Information Center, SRI International, Menlo Park, California, 2418 April 1988. 2420 [2] V. Cerf, Report of the Second Ad Hoc Network Management Review Group, 2421 Internet Working Group Request for Comments 1109. Network Information 2422 Center, SRI International, Menlo Park, California, August 1989. 2424 [3] M.T. Rose and K. McCloghrie, Structure and Identification of 2425 Management Information for TCP/IP-based internets, Internet Working Group 2426 Request for Comments 1155. Network Information Center, SRI 2427 International, Menlo Park, California, May 1990. 2429 [4] K. McCloghrie and M.T. Rose, Management Information Base for Network 2430 Management of TCP/IP-based internets, Internet Working Group Request for 2431 Comments 1156. Network Information Center, SRI International, Menlo 2432 Park, California, May 1990. 2434 [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, Simple 2435 Network Management Protocol, Internet Working Group Request for Comments 2436 1157. Network Information Center, SRI International, Menlo Park, 2437 California, May 1990. 2439 [6] M.T. Rose (editor), Management Information Base for Network 2440 Management of TCP/IP-based internets, Internet Working Group Request for 2441 Comments 1158, Network Information Center, SRI International, Menlo Park, 2442 California, May 1990. 2444 [7] Information processing systems - Open Systems Interconnection - 2445 Specification of Abstract Syntax Notation One (ASN.1), International 2446 Organization for Standardization. International Standard 8824, December 2447 1987. 2449 [8] Information processing systems - Open Systems Interconnection - 2450 Specification of Basic Encoding Rules for Abstract Notation One (ASN.1), 2451 International Organization for Standardization. International Standard 2452 8825, December 1987. 2454 [9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB Definitions, 2455 Internet Working Group Request for Comments 1212, Network Information 2456 Center, SRI International, Menlo Park, California, September 1990. 2458 [10] M. Lepp and M. Steenstrup, An Architecture for Inter-Domain Policy 2459 Routing, Internet Draft, July 1990. 2461 [11] ORWG, Inter-Domain Policy Routing Protocol Specification and Usage, 2462 Internet Draft, July 1991. 2464 [12] H. Bowns and M. Steenstrup, Inter-Domain Policy Routing 2465 Configuration and Usage, Internet Draft, July 1991. 2467 9 Editor's Address 2469 IDPR Working Group 2470 c/o Robert A. Woodburn 2471 Sparta, Inc. 2472 7926 Jones Branch Drive 2473 Suite 900 2474 McLean, VA 22102-3303 2475 (703) 448-0210 2477 EMAIL: idpr-wg@bbn.com or woody@sparta.com