idnits 2.17.1 draft-farrel-mpls-p2mp-te-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 21. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1951. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1924. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1931. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1937. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 34) being 64 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (August 2006) is 6465 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) ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) ** Downref: Normative reference to an Informational RFC: RFC 4461 -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) Summary: 6 errors (**), 0 flaws (~~), 4 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Adrian Farrel (Editor) 3 Updates: RFC3812 Old Dog Consulting 4 Category: Standards Track Seisho Yasukawa 5 Expires: January 2007 NTT 6 Thomas D. Nadeau 7 Cisco Systems, Inc. 9 August 2006 11 Point-to-Multipoint Multiprotocol Label Switching (MPLS) 12 Traffic Engineering (TE) Management Information Base (MIB) module 14 draft-farrel-mpls-p2mp-te-mib-01.txt 16 Status of this Memo 18 By submitting this Internet-Draft, each author represents that any 19 applicable patent or other IPR claims of which he or she is aware 20 have been or will be disclosed, and any of which he or she becomes 21 aware will be disclosed, in accordance with Section 6 of BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that other 25 groups may also distribute working documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be 36 accessed at http://www.ietf.org/shadow.html. 38 Abstract 40 This memo defines a portion of the Management Information Base 41 for use with network management protocols in the Internet community. 42 In particular, it describes managed objects for point-to-multipoint 43 Multiprotocol Label Switching-based traffic engineering. 45 Table of Contents 47 1. Introduction .................................................. 3 48 2. The Internet-Standard Management Framework .................... 4 49 3. Feature List .................................................. 4 50 4. Outline ....................................................... 5 51 4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module .. 5 52 4.2. Use of MPLS-TE-STD-MIB ................................... 6 53 4.3. mplsTeP2mpTunnelTable .................................... 8 54 4.4. mplsTeP2mpTunnelDestTable ................................ 8 55 4.5. mplsTeP2mpTunnelBranchPerfTable .......................... 9 56 5. Using the P2MP MPLS-TE MIB Module ............................. 9 57 5.1. Example Use of the P2MP MPLS-TE MIB Module ............... 9 58 5.2. Remerge Cases in the P2MP MPLS-TE MIB Module ............. 9 59 6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module ......... 9 60 6.1. Example Use of the LSR MIB Module ....................... 11 61 6.2. Remerge Cases in the LSR MIB Module ..................... 12 62 7. MPLS Traffic Engineering P2MP MIB Definitions ................ 13 63 8. Security Considerations ...................................... 37 64 9. Acknowledgments .............................................. 39 65 10. IANA Considerations .......................................... 39 66 10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB ............ 39 67 11. References ................................................... 39 68 11.1. Normative References .................................... 39 69 11.2. Informative References .................................... 40 70 12. Authors' Addresses ........................................... 41 71 13. Intellectual Property ........................................ 41 72 14. Full Copyright Statement ..................................... 42 74 0. Changes Since Previous Revision 76 [This section to be removed before publication as an RFC.] 78 Rename mplsMp2pGroups to mplsP2mpGroups. 80 Rename everything mplsP2mp* to mplsTeP2mp*, and everything MplsP2mp* 81 to MplsTeP2mp* 83 Rename members of mplsTeP2mpDestEntry to be consistently named. 85 mplsTeP2mpTunnelSubGroupIDNext SYNTAX changed to reflect same range 86 as mplsTeP2mpTunnelSubGroupID. 88 mplsTeP2mpTunnelDestination and mplsTeP2mpTunnelSubGroupOrigin given 89 SIZE clauses in their SYNTAX. 91 Change special value of mplsTeP2mpTunnelBranchOutSegment to be a 92 single octet with value 0x00. 94 Change reference to sysUpTIme (from SysUpTime) in 95 mplsTeP2mpTunnelDestCreationTime. 97 Added mplsTeP2mpTunnelDestDiscontinuityTime. 99 Added mplsTeP2mpTunnelBranchDiscontinuityTime. 101 Add clarification of mplsTeP2mpTunnelDestOperStatus with regard to 102 mplsTunnelOperStatus. 104 Add mplsTeP2mpTunnelBranch as an index to 105 mplsTeP2mpTunnelBranchPerftable. 107 Add mplsTeP2mpTunnelSubGroupOriginType, 108 mplsTeP2mpTunnelSubGroupOrigin, and mplsTeP2mpTunnelSubGroupID to 109 record the Sub-Group Fields received on an incoming Path message. 111 Minor typos throughout. 113 Supply missing text in section 4.5. 115 Add a placeholder for text to describe the remerge cases (sections 116 5.2 and 6.2). 118 Acknowledgments updated. 120 1. Introduction 122 This memo defines a portion of the Management Information Base (MIB) 123 for use with network management protocols in the Internet community. 124 In particular, it describes managed objects for modeling 125 point-to-multipoint (P2MP) Multiprotocol Label Switching (MPLS) 126 traffic engineering (TE). 128 MPLS is defined in [RFC3031] and a signaling protocol for 129 point-to-point (P2P) MPLS-TE (TE extensions to the Resource 130 Reservation Protocol - RSVP-TE) is defined in [RFC3209]. RSVP-TE is 131 extended for use in a P2MP environment by [P2MP-TE] following the 132 requirements set out in [RFC4461]. 134 [RFC3812] provides a MIB module for modeling and controlling P2P 135 MPLS-TE in conjunction with Textual Conventions defined in [RFC3811]. 136 In addition, [RFC3813] defines a MIB module for modeling and 137 controlling an MPLS label switching router (LSR) that may support 138 MPLS-TE. An overview of MPLS MIB modules can be found in [RFC4221]. 140 This document defines a MIB module for managing and controlling P2MP 141 MPLS-TE. It builds on the objects and tables defined in [RFC3812] so 142 that P2MP MPLS-TE management is an extension of P2P MPLS-TE 143 management. 145 In addition, this document provides a description of how to use the 146 LSR MIB module [RFC3813] to model and control an LSR that supports 147 P2MP MPLS-TE. 149 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 150 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 151 document are to be interpreted as described in BCP 14, RFC 2119 152 [RFC2119]. 154 2. The Internet-Standard Management Framework 156 For a detailed overview of the documents that describe the current 157 Internet-Standard Management Framework, please refer to section 7 of 158 RFC 3410 [RFC3410]. 160 Managed objects are accessed via a virtual information store, termed 161 the Management Information Base or MIB. MIB objects are generally 162 accessed through the Simple Network Management Protocol (SNMP). 163 Objects in the MIB are defined using the mechanisms defined in the 164 Structure of Management Information (SMI). This memo specifies a MIB 165 module that is compliant to the SMIv2, which is described in STD 58, 166 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 167 [RFC2580]. 169 3. Feature List 171 The feature list for this MIB module is built on the feature list for 172 the P2P MPLS-TE MIB module [RFC3812]. The features in the list below 173 are marked with a star (*) if they are new features for this MIB 174 module and with a circle (o) if they are features satisfied by 175 [RFC3812]. 177 * The MIB module supports configuration of point-to-multipoint 178 unidirectional tunnels. 180 o MPLS tunnels need not be interfaces, but it is possible to 181 configure a tunnel as an interface. 183 o The MIB module supports tunnel establishment via an MPLS 184 signaling protocol wherein the tunnel parameters are specified 185 using this MIB module at the head end of the LSP, and end-to-end 186 tunnel LSP establishment is accomplished via signaling. The MIB 187 module also supports manually configured tunnels, i.e., those for 188 which label associations at each hop of the tunnel LSP are 189 provisioned by the administrator via the LSR MIB [RFC3813]. 191 o The MIB module supports persistent, as well as non-persistent 192 tunnels. 194 4. Outline 196 P2MP MPLS-TE requires that MPLS tunnels are established from a single 197 source point (the root) to one or more destination points (the 198 leaves). 200 Associated with the MPLS tunnel is a set of configured parameters 201 that describe the forwarding behavior of each LSR along the path of 202 the label switched paths (LSPs) that support the tunnel. It should 203 be noted that, according to [RFC4461] these configuration parameters 204 are invariant across the branches of a P2MP LSP towards different 205 leaves. 207 One of the configuration parameters associated with an MPLS tunnel is 208 the path (or route) that supporting LSPs are required to follow. This 209 can be specified as a series of loose or strict hops. In P2MP TE, 210 this specification of the LSP route includes implicit or explicit 211 identification of the branch points in the P2MP LSPs. 213 The setup of P2MP tunnels can be achieved as: 214 - management actions only, by using [RFC3813] 215 - control plane actions under the direction of management by using 216 [RFC3812] and the MIB module defined in this document 217 - control plane actions under the direction of some other management 218 process, monitored using [RFC3812] and the MIB module defined in 219 this document. 221 Note that [GMPLS-TE-MIB] defines a MIB module that can be used to 222 manage and model Generalized MPLS (GMPL) LSPs - it is a series of MIB 223 objects and tables some of which extend tables in MPLS-TE-STD-MIB 224 [RFC3812]. [RFC4461] and [P2MP-TE] are clear that they apply to 225 MPLS-TE [RFC3031] and GMPLS [RFC3945]. This document describes a MIB 226 module that can be used for both MPLS-TE and GMPLS P2MP LSPs. 228 The following section describes the components of the P2MP MPLS-TE 229 MIB module. The subsequent section provides an explanation and 230 example of how the P2MP MPLS-TE MIB module can be used for the 231 processes listed above in combination with the MPLS-TE MIB module 232 defined in [RFC3812]. A further section describes how P2MP tunnels 233 can be managed solely through the LSR MIB module defined in 234 [RFC3813], and gives an example. 236 4.1. Summary of the P2MP MPLS Traffic Engineering MIB Module 238 The MIB module consists of the following objects and tables: 240 - P2MP Tunnel table (mplsTeP2mpTunnelTable) that sparse augments the 241 MPLS-TE Tunnel table (mplsTunnelTable) and is used to set up and 242 monitor P2MP MPLS-TE tunnels. 244 - P2MP Tunnel Destination table (mplsTeP2mpTunnelDestTable) that 245 lists the destinations (leaves) of each P2MP MPLS-TE tunnel, 246 provides the status of the tunnel to each destination, and 247 supplies pointers into the configured hop table, actual route hop 248 table, and computed hop table (mplsTunnelHopTable, 249 mplsTunnelARHopTable, and mplsTunnelCHopTable) for the routes to 250 each of the destinations. 252 These tables are described in the following sections after a 253 description of how the MPLS-TE-STD-MIB module [RFC3812] is used as a 254 basis for MIB management and modeling of P2MP MPLS-TE. 256 4.2. Use of MPLS-TE-STD-MIB 258 The MIB module defined in this document builds on the objects and 259 tables of MPLS-TE-STD-MIB defined in [RFC3812]. That is, most of the 260 basic properties of the MPLS tunnel are modeled and managed by 261 objects in MPLS-TE-STD-MIB, and new objects are only defined within 262 this document where additional features or different behavior is 263 required. 265 When an MPLS-TE tunnel is a P2MP tunnel, certain objects in the 266 mplsTunnelTable have new meanings just as the signaling objects in 267 RSVP-TE [RFC3209] have different meanings when the signaling messages 268 are used to establish P2MP LSPs [P2MP-TE]. 270 As indicated in the next section, the presence of the 271 mplsTeP2mpTunnelTable of the MIB module defined in this document with 272 the object mplsTeP2mpTunnel containing the value True (1) shows that 273 a tunnel defined in the mplsTunnelTable of MPLS-TE-STD-MIB is a P2MP 274 tunnel. Under those circumstances the following objects from 275 MPLS-TE-STD-MIB MUST be interpreted as follows. The text below is 276 supplementary for the Description clauses in [RFC3812]. 278 mplsTunnelMaxHops 280 This object continues to refer to the maximum number of hops that 281 can be configured to a single destination for a tunnel on this 282 device. Thus, for a P2MP tunnel, this refers to the maximum number 283 of hops that can be configured on this device to any individual 284 destination of the tunnel. 286 A new object, mplsTeP2mpTunnelTotalMaxHops, is defined in this MIB 287 module to supply the total number of hops across all destinations 288 of a P2MP tunnel. 290 mplsTunnelEgressLSRId 292 This object continues to map to the field in the RSVP-TE Session 293 Object that occupies the space used by the IPv4 Tunnel Endpoint 294 Address [RFC3209], but for a P2MP tunnel, this object does not 295 identify an address of the egress of the tunnel. Instead it 296 contains the P2MP ID value that identifies the identifier of the 297 set of destinations for the P2MP tunnel and is carried in the P2MP 298 Session Object [P2MP-TE]. The Description clause for this object 299 can be read as follows. 301 "Identity of the egress LSR associated with this 302 tunnel instance. 304 When an entry in the mplsTeP2mpTunnelTable is present 305 corresponding to this entry in the mplsTunnelTable and when 306 the mplsTeP2mpTunnel object in that table entry is present 307 with the value True(1), this object contains the P2MP ID that 308 identifies the set of destinations of this tunnel and that is 309 signaled in the P2MP ID field of the P2MP Session Object if 310 the MPLS signaling protocol for this tunnel indicated by 311 mplsTunnelSignallingProto in MPLS-TE-STD-MIB is rsvp (2)." 313 The destinations of the P2MP tunnel are found in the new 314 mplsTeP2mpTunnelDestTable. 316 mplsTunnelHopTableIndex 318 If the tunnel is a P2MP tunnel as indicated by the presence of an 319 entry in the mplsTeP2mpTunnelTable corresponding to this tunnel 320 and when the mplsTeP2mpTunnel object in that table entry is 321 present with the value True (1), this object is not used. This is 322 because the destinations and paths to those destinations are found 323 in the mplsTeP2mpTunnelDestTable. 325 If this object is present for a P2MP tunnel, it should contain the 326 value 0. 328 mplsTunnelPathInUse 330 If the tunnel is a P2MP tunnel as indicated by the presence of an 331 entry in the mplsTeP2mpTunnelTable corresponding to this tunnel 332 and when the mplsTeP2mpTunnel object in that table entry is 333 present with the value True(1), this object is not used. This is 334 because the destinations and paths to those destinations are found 335 in the mplsTeP2mpTunnelDestTable. 337 If this object is present for a P2MP tunnel, it should contain the 338 value 0. 340 mplsTunnelARHopTableIndex 342 If the tunnel is a P2MP tunnel as indicated by the presence of an 343 entry in the mplsTeP2mpTunnelTable corresponding to this tunnel 344 and when the mplsTeP2mpTunnel object in that table entry is 345 present with the value True(1), this object is not used. This is 346 because the destinations and paths to those destinations are found 347 in the mplsTeP2mpTunnelDestTable. 349 If this object is present for a P2MP tunnel, it should contain the 350 value 0. 352 mplsTunnelCHopTableIndex 354 If the tunnel is a P2MP tunnel as indicated by the presence of an 355 entry in the mplsTeP2mpTunnelTable corresponding to this tunnel 356 and when the mplsTeP2mpTunnel object in that table entry is 357 present with the value True(1), this object is not used. This is 358 because the destinations and paths to those destinations are found 359 in the mplsTeP2mpTunnelDestTable. 361 If this object is present for a P2MP tunnel, it should contain the 362 value 0. 364 4.3. mplsTeP2mpTunnelTable 366 The mplsTeP2mpTunnelTable extends (through a sparse augmentation) the 367 MPLS Tunnel table (mplsTunnelTable) from MPLS-TE-STD-MIB [RFC3812] to 368 allow P2MP MPLS-TE tunnels to be created, controlled and monitored at 369 any LSR in the network. 371 A P2MP MPLS-TE tunnel may be represented in the MIB, by defining it 372 in the mplsTunnelTable and providing objects in this table to 373 indicate that it is a P2MP tunnel and to define P2MP-specific 374 properties of this tunnel. 376 4.4. mplsTeP2mpTunnelDestTable 378 P2MP LSPs have multiple destinations and, although the LSP parameters 379 (such as bandwidth) for each destination are the same, the explicit 380 route requested, computed, and signaled is different for each 381 destination. The mplsTeP2mpTunnelDestTable encodes each destination 382 and the information specific to the LSP to that destination. 384 4.5. mplsTeP2mpTunnelBranchPerfTable 386 Per-tunnel statistics are counted in mplsTunnelPerfTable in 387 MPLS-TE-STD-MIB [RFC3812], but these objects are only partially 388 useful for a P2MP tunnel. The five objects in that table 389 (mplsTunnelPerfPackets, mplsTunnelPerfHCPackets, 390 mplsTunnelPerfErrors, mplsTunnelPerfBytes, mplsTunnelPerfHCBytes) 391 continue to be used for tunnels that forward packets, and reflect 392 the counts of data received on the incoming interface and forwarded 393 to the downstream interfaces. 395 However, in a P2MP tunnel, the downstream interfaces (out-segments) 396 may behave differently and so it is appropriate to record the 397 performance on each out-going branch. This is achieved through the 398 mplsTeP2mpTunnelBranchPerfTable which is indexed by the tunnel 399 identifiers and by the same identifier of the branch as is used in 400 mplsTeP2mpTunnelDestTable. 402 5. Using the P2MP MPLS-TE MIB Module 404 TBD 406 5.1. Example Use of the P2MP MPLS-TE MIB Module 408 TBD 410 5.2. Remerge Cases in the P2MP MPLS-TE MIB Module 412 TBD 414 6. Managing P2MP MPLS-TE LSPs Through the LSR MIB Module 416 The nature of P2MP tunnels is such that an LSR that is crossed by a 417 tunnel may either be the ingress of that tunnel or have precisely one 418 upstream LSP segment (also known as in-segment [RFC3812]) for that 419 LSP. On the other hand, any LSR that is crossed by a tunnel may be an 420 egress for that tunnel, have one or more downstream segments (also 421 known as out-segments [RFC3812]) for that tunnel, or be both an 422 egress and have one or more out-segments. Thus, for an LSP at an LSR 423 there may be zero or one in-segments, and zero, one, or more than one 424 out-segments. 426 In-segments, out-segments and their relationship through 427 cross-connections are modeled and managed in the MPLS-LSR-STD-MIB 428 module [RFC3813]. The mplsInSegmentTable contains in-segments, and 429 the mplsOutSegmentTable contains out-segments. The mplsXCTable 430 maintains the relationships between in- and out-segments such that 431 any many-to-many relationship is allowed. Each segment points into 432 the mplsXCTable using mplsInSegmentXCIndex and mplsOutSegmentXCIndex. 434 The mplsXCTable contains a series of entries indexed by the primary 435 mplsXCIndex object and subsidiary indexes mplsXCInSegmentIndex and 436 mplsXCOutSegmentIndex. 438 A single P2MP cross-connect has zero or one in-segment. At the 439 ingress LSR, there is no in-segment and mplsXCInSegmentIndex is set 440 to the single octet 0x00. At transit LSRs, there is exactly one 441 in-segment and mplsXCInSegmentIndex is set to the value of 442 mplsInSegmentIndex for the in-segment as it appears in the 443 mplsInSegmentTable. 445 A single P2MP cross-connect has zero, one or many out-segments. If 446 there is no out-segment (the cross-connect is on an egress LSR), 447 there is one entry in the mplsXCTable indexed by mplsXCIndex set to 448 mplsInSegmentXCIndex from the in-segment's entry in 449 mplsInSegmentTable, mplsXCInSegmentIndex set to the value of 450 mplsInSegmentIndex that identifies the in-segment in 451 mplsInSegmentTable, and mplsXCOutSegmentIndex set to the single octet 452 0x00. This behavior is exactly as described in [RFC3813]. 454 If there is exactly one out-segment (the cross-connect is on a 455 transit LSR) then the behavior is also exactly as described in 456 [RFC3813], and as well as the in-segment objects described in the 458 previous paragraph, mplsXCOutSegmentIndex is set to the value of 459 mplsOutSegmentIndex that identifies the out-segment in 460 mplsOutSegmentTable. Note that mplsInSegmentXCIndex and 461 mplsOutSegmentXCIndex from the relevant table entries will have the 462 same value which will provide the value of mplsXCIndex for the 463 cross-connect. 465 If there is more than one out-segment then there is one entry in 466 mplsXCTable table for each out-segment. The value of mplsXCIndex is 467 consistent across all of these table entries, and the in-segment 468 index (mplsXCInSegmentIndex) is also consistent identifying the 469 single in-segment or (on the ingress LSR) containing the single octet 470 0x00. Each of these mplsXCTable entries contains a different 471 mplsXCOutSegmentIndex value so that the table can easily be walked to 472 find all of the out-segments for the same cross-connect. 474 Finally, if an LSR is an egress as well as a transit or branch for 475 the P2MP LSP (we call this a bud LSR), mplsXCTable contains the 476 entries described above in combination. That is, one entry will have 477 mplsXCOutSegmentIndex set to the single octet 0x00, and other entries 478 with the same value of mplsXCIndex and mplsXCInSegmentIndex will 479 exist for each out-segment. 481 6.1. Example Use of the LSR MIB Module 483 This section demonstrates how the objects in MPLS-LSR-STD-MIB would 484 be set for an example P2MP LSP cross-connect. The information here 485 does not show how and in what order these objects should be set to 486 create the cross-connect, but shows what information would be read if 487 the tables were examined. 489 The figure shows the LSP at the LSR that is being examined. There are 490 three interfaces to LSR X: 10, 21 and 22. The LSP enters through 491 interface 10 using label 7, and exits through interfaces 21 and 22 492 using labels 8 and 9 respectively. Let us assume that LSR X is also 493 an egress for the LSP. 495 ------- 496 | |21 Label 8 497 Label 7 | +-------------> 498 --->----------+ LSR X | 499 10| +-------------> 500 | |22 Label 9 501 ------- 503 In mplsInSegmentTable there is a single entry 504 { 505 mplsInSegmentIndex = 0x00000015, 506 mplsInSegmentLabel = 7, -- incoming label 507 mplsInSegmentNPop = 1, 508 mplsInSegmentInterface = 10, -- incoming interface 509 mplsInSegmentXCIndex = 0x37 -- index into XC table 510 } 512 In mplsOutSegmentTable there are two entries. 513 { 514 mplsOutSegmentIndex = 0x00000432, 515 mplsOutSegmentPushTopLabel = true(1), 516 mplsOutSegmentTopLabel = 8, -- outgoing label 517 mplsOutSegmentInterface = 21, -- outgoing interface 518 mplsOutSegmentXCIndex = 0x37 -- index into XC table 519 } 520 { 521 mplsOutSegmentIndex = 0x00000017, 522 mplsOutSegmentPushTopLabel = true(1), 523 mplsOutSegmentTopLabel = 9, -- outgoing label 524 mplsOutSegmentInterface = 22, -- outgoing interface 525 mplsOutSegmentXCIndex = 0x37 -- index into XC table 526 } 527 In mplsXCTable there are three entries. The first two are for the 528 cross-connections to the out-segments, and the third is for the local 529 egress. 530 { 531 mplsXCIndex = 0x37, -- common index 532 mplsXCInSegmentIndex = 0x00000015,-- the in-segment 533 mplsXCOutSegmentIndex = 0x00000432,-- first out-segment 534 mplsXCLspId = 0x0102 -- unique LSP ID 535 mplsXCLabelStackIndex = 0x00, -- only one outgoing label 536 } 537 { 538 mplsXCIndex = 0x37, -- common index 539 mplsXCInSegmentIndex = 0x00000015,-- the in-segment 540 mplsXCOutSegmentIndex = 0x00000017,-- second out-segment 541 mplsXCLspId = 0x0102 -- unique LSP ID 542 mplsXCLabelStackIndex = 0x00, -- only one outgoing label 543 } 544 { 545 mplsXCIndex = 0x37, -- common index 546 mplsXCInSegmentIndex = 0x00000015,-- the in-segment 547 mplsXCOutSegmentIndex = 0x00, -- no out-segment 548 mplsXCLspId = 0x0102 -- unique LSP ID 549 mplsXCLabelStackIndex = 0x00, -- no other outgoing label 550 } 552 6.2. Remerge Cases in the LSR MIB Module 554 TBD 555 7. MPLS Traffic Engineering P2MP MIB Definitions 557 This MIB module uses imports from [RFC2578], [RFC2580], [RFC2579], 558 [RFC3811], [RFC3812], [RFC3813], [RFC3289], and [RFC3291]. 560 MPLS-TE-P2MP-STD-MIB DEFINITIONS ::= BEGIN 562 IMPORTS 563 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 564 Unsigned32, Counter32, Counter64, TimeTicks 565 FROM SNMPv2-SMI -- RFC2578 566 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 567 FROM SNMPv2-CONF -- RFC2580 568 TruthValue, RowStatus, StorageType, TimeStamp 569 FROM SNMPv2-TC -- RFC2579 570 mplsStdMIB, MplsPathIndexOrZero 571 FROM MPLS-TC-STD-MIB -- RFC3811 572 MplsIndexType 573 FROM MPLS-LSR-STD-MIB -- RFC3813 574 mplsTunnelIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, 575 mplsTunnelEgressLSRId 576 FROM MPLS-TE-STD-MIB -- RFC3812 577 IndexIntegerNextFree 578 FROM DIFFSERV-MIB -- RFC3289 579 InetAddress, InetAddressType 580 FROM INET-ADDRESS-MIB -- RFC3291 581 ; 583 mplsTeP2mpStdMIB MODULE-IDENTITY 584 LAST-UPDATED "200605240000Z" -- May 24, 2006 585 ORGANIZATION 586 "Multiprotocol Label Switching (MPLS) Working Group" 587 CONTACT-INFO 588 " Adrian Farrel 589 Old Dog Consulting 590 Email: adrian@olddog.co.uk 592 Seisho Yasukawa 593 NTT Corporation 594 Email: s.yasukawa@hco.ntt.co.jp 596 Thomas D. Nadeau 597 Cisco Systems, Inc. 598 Email: tnadeau@cisco.com 600 Comments about this document should be emailed 601 directly to the MPLS working group mailing list at 602 mpls@lists.ietf.org" 604 DESCRIPTION 605 "Copyright (C) The Internet Society (2006). The 606 initial version of this MIB module was published 607 in RFC XXXX. For full legal notices see the RFC 608 itself or see: http://www.ietf.org/copyrights/ianamib.html 609 -- RFC Editor. Please replace XXXX with the RFC number for this 610 -- document and remove this note. 612 This MIB module contains managed object definitions 613 for Point-to-Multipoint (P2MP) MPLS Traffic Engineering (TE) 614 defined in: 615 1. Signaling Requirements for Point-to-Multipoint 616 Traffic-Engineered MPLS Label Switched Paths (LSPs), 617 S. Yasukawa, RFC 4461, April 2006. 618 2. Extensions to RSVP-TE for Point to Multipoint TE LSPs, 619 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 620 progress." 622 -- Revision history. 624 REVISION 625 "200605240000Z" -- May 24, 2006 626 DESCRIPTION 627 "Initial version issued as part of RFC XXXX." 628 -- RFC Editor. Please replace XXXX with the RFC number for this 629 -- document and remove this note. 631 ::= { mplsStdMIB YYY } 633 -- RFC Editor. Please replace YYY with the codepoint issued by IANA 634 -- and remove this note. 636 -- Top level components of this MIB module. 638 -- notifications 639 mplsTeP2mpNotifications OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 0 } 640 -- tables, scalars 641 mplsTeP2mpScalars OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 1 } 642 mplsTeP2mpObjects OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 2 } 643 -- conformance 644 mplsTeP2mpConformance OBJECT IDENTIFIER ::= { mplsTeP2mpStdMIB 3 } 645 -- MPLS P2MP Tunnel scalars. 647 mplsTeP2mpTunnelConfigured OBJECT-TYPE 648 SYNTAX Unsigned32 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "The number of P2MP tunnels configured on this device. A 653 tunnel is considered configured if the mplsTunnelRowStatus 654 in MPLS-TE-STD-MIB is active(1)." 655 REFERENCE 656 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 657 Engineering (TE) Management Information Base (MIB), 658 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 659 ::= { mplsTeP2mpScalars 1 } 661 mplsTeP2mpTunnelActive OBJECT-TYPE 662 SYNTAX Unsigned32 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "The number of P2MP tunnels active on this device. A 667 tunnel is considered active if the mplsTunnelOperStatus 668 in MPLS-TE-STD-MIB is up(1)." 669 REFERENCE 670 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 671 Engineering (TE) Management Information Base (MIB), 672 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 673 ::= { mplsTeP2mpScalars 2 } 675 mplsTeP2mpTunnelTotalMaxHops OBJECT-TYPE 676 SYNTAX Unsigned32 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "The maximum number of hops that can be specified for 681 an entire P2MP tunnel on this device. 682 This object should be used in conjunction with 683 mplsTunnelMaxHops in MPLS-TE-STD-MIB that is used in the 684 context of P2MP tunnels to express the maximum number of 685 hops to any individual destination of a P2MP tunnel that 686 can be configured on this device." 687 REFERENCE 688 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 689 Engineering (TE) Management Information Base (MIB), 690 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 691 ::= { mplsTeP2mpScalars 3 } 693 -- End of MPLS Tunnel scalars. 695 -- MPLS P2MP tunnel table. 697 mplsTeP2mpTunnelTable OBJECT-TYPE 698 SYNTAX SEQUENCE OF MplsTeP2mpTunnelEntry 699 MAX-ACCESS not-accessible 700 STATUS current 701 DESCRIPTION 702 "The mplsTeP2mpTunnelTable allows new P2MP MPLS tunnels to be 703 created between an LSR and one or more remote end-points, 704 and existing P2MP tunnels to be reconfigured or removed. 706 This table sparse augments mplsTunnelTable in 707 MPLS-TE-STD-MIB such that entries in that table can be 708 flagged as point-to-multipoint, and can be configured and 709 monitored appropriately." 710 REFERENCE 711 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 712 Engineering (TE) Management Information Base (MIB), 713 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 714 ::= { mplsTeP2mpObjects 1 } 716 mplsTeP2mpTunnelEntry OBJECT-TYPE 717 SYNTAX MplsTeP2mpTunnelEntry 718 MAX-ACCESS not-accessible 719 STATUS current 720 DESCRIPTION 721 "An entry in this table represents a P2MP MPLS tunnel. 722 An entry can be created by a network administrator or by an 723 SNMP agent as instructed by an MPLS signaling protocol. 725 An entry in this table MUST correspond to an entry in the 726 mplsTunnelTable in MPLS-TE-STD-MIB. This table shares index 727 objects with that table and sparse augments that table. 729 Thus, an entry in this table can only be created at the same 730 time as or after a corresponding entry in mplsTunnelTable, 731 and an entry in mplsTunnelTable cannot be deleted while a 732 corresponding entry exists in this table. 734 This table entry includes a row status object, but 735 administrative and operational statuses should be taken from 736 mplsTunnelAdminStatus and mplsTunnelOperStatus in the 737 corresponding entry in mplsTunnelTable." 738 REFERENCE 739 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 740 Engineering (TE) Management Information Base (MIB), 741 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 743 INDEX { mplsTunnelIndex, 744 mplsTunnelInstance, 745 mplsTunnelIngressLSRId, 746 mplsTunnelEgressLSRId 747 } 748 ::= { mplsTeP2mpTunnelTable 1 } 750 MplsTeP2mpTunnelEntry ::= SEQUENCE { 751 mplsTeP2mpTunnelIsP2MP TruthValue, 752 mplsTeP2mpTunnelP2mpIntegrity TruthValue, 753 mplsTeP2mpTunnelBranchRole INTEGER, 754 mplsTeP2mpTunnelSubGroupOriginType InetAddressType, 755 mplsTeP2mpTunnelSubGroupOrigin InetAddress, 756 mplsTeP2mpTunnelSubGroupID Unsigned32, 757 mplsTeP2mpTunnelRowStatus RowStatus, 758 mplsTeP2mpTunnelStorageType StorageType 759 } 761 mplsTeP2mpTunnelIsP2MP OBJECT-TYPE 762 SYNTAX TruthValue 763 MAX-ACCESS read-create 764 STATUS current 765 DESCRIPTION 766 "Denotes whether or not this tunnel is a point-to-multipoint 767 tunnel. 768 If this object is not present or is present and set to 769 false(2), this tunnel is not a point-to-multipoint tunnel 770 and all other objects in this table entry are not valid." 771 DEFVAL { true } 772 ::= { mplsTeP2mpTunnelEntry 1 } 774 mplsTeP2mpTunnelP2mpIntegrity OBJECT-TYPE 775 SYNTAX TruthValue 776 MAX-ACCESS read-create 777 STATUS current 778 DESCRIPTION 779 "Denotes whether or not P2MP Integrity is required for this 780 tunnel. 781 If P2MP integrity is operational on a P2MP tunnel then the 782 failure of the path to any of the tunnel destinations should 783 cause the teardown of the entire P2MP tunnel." 784 REFERENCE 785 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 786 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 787 progress." 788 DEFVAL { false } 789 ::= { mplsTeP2mpTunnelEntry 2 } 791 mplsTeP2mpTunnelBranchRole OBJECT-TYPE 792 SYNTAX INTEGER { notBranch(1), 793 branch(2), 794 bud(3) } 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "This value supplements the value in the object 799 mplsTunnelRole in MPLS-TE-STD-MIB that indicates the role 800 of this LSR in the tunnel represented by this entry in 801 mplsTeP2mpTunnelTable. 803 mplsTunnelRole may take any of the values: 804 head(1), 805 transit(2), 806 tail(3), 807 headTail(4) 809 If this LSR is an ingress and there is exactly one 810 out-segment, mplsTunnelRole should contain the value 811 head(1), and mplsTeP2mpTunnelBranchRole should have the 812 value notBranch(1). 814 If this LSR is an ingress with more than one out segment, 815 mplsTunnelRole should contain the value head(1), and 816 mplsTeP2mpTunnelBranchRole should have the value branch(2). 818 If this LSR is an ingress, an egress, and there is one or 819 more out-segments, mplsTunnelRole should contain the value 820 headTail(4), and mplsTeP2mpTunnelBranchRole should have the 821 value bud(3). 823 If this LSR is a transit with exactly one out-segment, 824 mplsTunnelRole should contain the value transit(2), and 825 mplsTeP2mpTunnelBranchRole should have the value 826 notBranch(1). 828 If this LSR is a transit with more than one out-segment, 829 mplsTunnelRole should contain the value transit(2), and 830 mplsTeP2mpTunnelBranchRole should have the value branch(2). 832 If this LSR is a transit with one or more out-segments and 833 is also an egress, mplsTunnelRole should contain the value 834 transit(2), and mplsTeP2mpTunnelBranchRole should have the 835 value bud(3). 837 If this LSR is an egress with no out-segment and is not the 838 ingress, mplsTunnelRole should contain the value tail(3), 839 and mplsTeP2mpTunnelBranchRole should have the value 840 notBranch(1). 842 If this LSR is an egress and has one or more out-segments, 843 mplsTunnelRole should contain the value transit(1), and 844 mplsTeP2mpTunnelBranchRole should have the value bud(3)." 845 REFERENCE 846 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 847 Engineering (TE) Management Information Base (MIB), 848 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 849 DEFVAL { notBranch } 850 ::= { mplsTeP2mpTunnelEntry 3 } 852 mplsTeP2mpTunnelSubGroupOriginType OBJECT-TYPE 853 SYNTAX InetAddressType 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "This object identifies the type of address carried in 858 mplsTeP2mpTunnelSubGroupOrigin. 860 Since the object mplsTeP2mpTunnelSubGroupOrigin must conform 861 to the protocol specification, this object must return 862 either ipv4(1) or ipv6(2) at a transit or egress LSR. 864 At an ingress LSR, mplsTeP2mpTunnelSubGroupOrigin should not 865 be used, and this object should return the value 866 unknown(0)." 867 ::= { mplsTeP2mpTunnelEntry 4 } 869 mplsTeP2mpTunnelSubGroupOrigin OBJECT-TYPE 870 SYNTAX InetAddress (SIZE (1..16)) 871 MAX-ACCESS read-only 872 STATUS current 873 DESCRIPTION 874 "The TE Router ID (reachable and stable IP address) of the 875 originator of the P2MP sub-group as received on a Path 876 message by a transit or egress LSR. 878 This object is interpreted in the context of 879 mplsTeP2mpTunnelSubGroupOriginType. 881 The value of the sub-group originator used on outgoing Path 882 messages is found in mplsTeP2mpTunnelDestSubGroupOrigin and 883 is copied from this object unless this LSR is responsible 884 for changing the sub-group ID. 886 At an ingress LSR this object is not used because there is 887 no received Path message. mplsTeP2mpTunnelSubGroupOriginType 888 should return unknown(0), and this object should return the 889 value 0x00, or should be absent." 891 REFERENCE 892 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 893 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 894 progress." 895 ::= { mplsTeP2mpTunnelEntry 5 } 897 mplsTeP2mpTunnelSubGroupID OBJECT-TYPE 898 SYNTAX Unsigned32 (1..4294967295) 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The unique identifier assigned by the sub-group originator 903 for this sub-group of this P2MP tunnel as received on a Path 904 message by a transit or egress LSR. 906 The value of the sub-group identifier used on outgoing Path 907 messages is found in mplsTeP2mpTunnelDestSubGroupID and is 908 copied from this object unless this LSR is responsible for 909 changing the sub-group ID. 911 At an ingress LSR this object is not used because there is 912 no received Path message, and the object should be absent or 913 should return zero." 914 REFERENCE 915 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 916 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 917 progress." 918 ::= { mplsTeP2mpTunnelEntry 6 } 920 mplsTeP2mpTunnelRowStatus OBJECT-TYPE 921 SYNTAX RowStatus 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "This variable is used to create, modify, and/or delete a row 926 in this table. When a row in this table is in active(1) 927 state, no objects in that row can be modified by the agent 928 except mplsTeP2mpTunnelRowStatus and 929 mplsTeP2mpTunnelStorageType. 931 This object and mplsTunnelRowStatus in the corresponding 932 entry in mplsTunnelTable in MPLS-TE-STD-MIB should be 933 managed together. No objects in a row in this table can be 934 modified when the mplsTunnelRowStatus object in the 935 corresponding row in mplsTunnelTable has value active(1). 937 Note that no admin or oper status objects are provided in 938 this table. The administrative and operational status of 939 P2MP tunnels is taken from the values of 940 mplsTunnelAdminStatus and mplsTunnelOperStatus in the 941 corresponding row mplsTunneltable." 942 REFERENCE 943 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 944 Engineering (TE) Management Information Base (MIB), 945 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 946 ::= { mplsTeP2mpTunnelEntry 7 } 948 mplsTeP2mpTunnelStorageType OBJECT-TYPE 949 SYNTAX StorageType 950 MAX-ACCESS read-create 951 STATUS current 952 DESCRIPTION 953 "The storage type for this tunnel entry. 954 Conceptual rows having the value 'permanent' need not allow 955 write-access to any columnar objects in the row." 956 DEFVAL { volatile } 957 ::= { mplsTeP2mpTunnelEntry 8 } 959 -- End of mplsTeP2mpTunnelTable 961 -- MPLS P2MP tunnel destination table. 963 mplsTeP2mpTunnelSubGroupIDNext OBJECT-TYPE 964 SYNTAX IndexIntegerNextFree (0..4294967295) 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "This object contains an unused value for 969 mplsTeP2mpTunnelDestSubGroupID, or a zero to indicate that 970 none exists. Negative values are not allowed, as they do not 971 correspond to valid values of 972 mplsTeP2mpTunnelDestSubGroupID. 974 Note that this object offers an unused value for an 975 mplsTeP2mpTunnelDestSubGroupID value at the local LSR when 976 it is a sub-group originator. In other cases, the value of 977 mplsTeP2mpTunnelDestSubGroupID SHOULD be taken from the 978 received value signaled by the signaling protocol and 979 corresponds to the value in mplsTeP2mpTunnelSubGroupID." 980 ::= { mplsTeP2mpObjects 2 } 982 mplsTeP2mpTunnelDestTable OBJECT-TYPE 983 SYNTAX SEQUENCE OF MplsTeP2mpTunnelDestEntry 984 MAX-ACCESS not-accessible 985 STATUS current 986 DESCRIPTION 987 "The mplsTeP2mpTunnelDestTable allows new destinations of 988 P2MP MPLS tunnels to be added to and removed from P2MP 989 tunnels. 991 Entries in this table share some index fields with the 992 mplsTeP2mpTunnelTable and the mplsTunnelTable in 993 MPLS-TE-STD-MIB. Entries in this table have no meaning 994 unless there is a corresponding entry in 995 mplsTeP2mpTunnelTable (which, itself, depends on a 996 corresponding entry in mplsTunnelTable) and that entry has 997 mpl2P2mpTunnelIsP2mp set to true(1)." 998 REFERENCE 999 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 1000 Engineering (TE) Management Information Base (MIB), 1001 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 1002 ::= { mplsTeP2mpObjects 3 } 1004 mplsTeP2mpTunnelDestEntry OBJECT-TYPE 1005 SYNTAX MplsTeP2mpTunnelDestEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "An entry in this table represents a destination of a P2MP 1010 MPLS tunnel. An entry can be created by a network 1011 administrator or by an SNMP agent as instructed by an MPLS 1012 signaling protocol. 1014 Entries in this table share some index fields with the 1015 mplsTeP2mpTunnelTable and the mplsTunnelTable in 1016 MPLS-TE-STD-MIB. Entries in this table have no meaning 1017 unless there is a corresponding entry in 1018 mplsTeP2mpTunnelTable (which, itself, depends on a 1019 corresponding entry in mplsTunnelTable) and that entry has 1020 mpl2P2mpTunnelIsP2mp set to true(1). 1022 Note that the same destination may be present more than once 1023 if it is in more than one sub-group as reflected by the 1024 mplsTeP2mpTunnelDestSubGroupOriginType, 1025 mplsTeP2mpTunnelDestSubGroupOrigin, and 1026 mplsTeP2mpTunnelDestSubGroupID, index objects. 1028 Entries in this table may be created at any time. If created 1029 before an entry in the mplsTeP2mpTunnelTable the entries 1030 have no meaning, but may be kept ready for the creation of 1031 the P2MP tunnel. If created after the entry in 1032 mplsTeP2mpTunnelTable, entries in table may reflect the 1033 addition of destinations to active P2MP tunnels. For this 1034 reason, entries in this table are equipped with row, admin, 1035 and oper status objects. " 1036 REFERENCE 1037 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 1038 Engineering (TE) Management Information Base (MIB), 1039 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 1040 INDEX { mplsTunnelIndex, 1041 mplsTunnelInstance, 1042 mplsTunnelIngressLSRId, 1043 mplsTunnelEgressLSRId, 1044 mplsTeP2mpTunnelDestSubGroupOriginType, 1045 mplsTeP2mpTunnelDestSubGroupOrigin, 1046 mplsTeP2mpTunnelDestSubGroupID, 1047 mplsTeP2mpTunnelDestDestinationType, 1048 mplsTeP2mpTunnelDestDestination 1049 } 1050 ::= { mplsTeP2mpTunnelDestTable 1 } 1052 MplsTeP2mpTunnelDestEntry ::= SEQUENCE { 1053 mplsTeP2mpTunnelDestSubGroupOriginType InetAddressType, 1054 mplsTeP2mpTunnelDestSubGroupOrigin InetAddress, 1055 mplsTeP2mpTunnelDestSubGroupID Unsigned32, 1056 mplsTeP2mpTunnelDestDestinationType InetAddressType, 1057 mplsTeP2mpTunnelDestDestination InetAddress, 1058 mplsTeP2mpTunnelDestBranchOutSegment MplsIndexType, 1059 mplsTeP2mpTunnelDestHopTableIndex MplsPathIndexOrZero, 1060 mplsTeP2mpTunnelDestPathInUse MplsPathIndexOrZero, 1061 mplsTeP2mpTunnelDestCHopTableIndex MplsPathIndexOrZero, 1062 mplsTeP2mpTunnelDestARHopTableIndex MplsPathIndexOrZero, 1063 mplsTeP2mpTunnelDestTotalUpTime TimeTicks, 1064 mplsTeP2mpTunnelDestInstanceUpTime TimeTicks, 1065 mplsTeP2mpTunnelDestPathChanges Counter32, 1066 mplsTeP2mpTunnelDestLastPathChange TimeTicks, 1067 mplsTeP2mpTunnelDestCreationTime TimeStamp, 1068 mplsTeP2mpTunnelDestStateTransitions Counter32, 1069 mplsTeP2mpTunnelDestDiscontinuityTime TimeStamp, 1070 mplsTeP2mpTunnelDestAdminStatus INTEGER, 1071 mplsTeP2mpTunnelDestOperStatus INTEGER, 1072 mplsTeP2mpTunnelDestRowStatus RowStatus, 1073 mplsTeP2mpTunnelDestStorageType StorageType 1074 } 1075 mplsTeP2mpTunnelDestSubGroupOriginType OBJECT-TYPE 1076 SYNTAX InetAddressType 1077 MAX-ACCESS not-accessible 1078 STATUS current 1079 DESCRIPTION 1080 "This object identifies the type of address carried in 1081 mplsTeP2mpTunnelDestSubGroupOrigin. 1083 This object forms part of the index of this table and can, 1084 therefore, not return the value unknown(0). Similarly, since 1085 the object mplsTeP2mpTunnelDestSubGroupOrigin must conform 1086 to the protocol specification, this object must return 1087 either ipv4(1) or ipv6(2)." 1088 ::= { mplsTeP2mpTunnelDestEntry 1 } 1090 mplsTeP2mpTunnelDestSubGroupOrigin OBJECT-TYPE 1091 SYNTAX InetAddress (SIZE (1..16)) 1092 MAX-ACCESS not-accessible 1093 STATUS current 1094 DESCRIPTION 1095 "The TE Router ID (reachable and stable IP address) of the 1096 originator of the P2MP sub-group. In many cases, this will 1097 be the ingress LSR of the P2MP tunnel and will be the 1098 received signaled value as available in 1099 mplsTeP2mpTunnelSubGroupOrigin. 1101 When a signaling protocol is used, this object corresponds 1102 to the Sub-Group Originator field in the SENDER_TEMPLATE 1103 object. 1105 This object is interpreted in the context of 1106 mplsTeP2mpTunnelDestSubGroupOriginType." 1107 REFERENCE 1108 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 1109 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 1110 progress." 1111 ::= { mplsTeP2mpTunnelDestEntry 2 } 1113 mplsTeP2mpTunnelDestSubGroupID OBJECT-TYPE 1114 SYNTAX Unsigned32 (1..4294967295) 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "The unique identifier assigned by the sub-group originator 1119 for this sub-group of this P2MP tunnel. 1121 An appropriate value for this object during row creation 1122 when the sub-group origin in 1123 mplsTeP2mpTunnelDestSubGroupOrigin is the local LSR can 1124 be obtained by reading mplsTeP2mpTunnelSubGroupIDNext." 1126 REFERENCE 1127 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 1128 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 1129 progress." 1130 ::= { mplsTeP2mpTunnelDestEntry 3 } 1132 mplsTeP2mpTunnelDestDestinationType OBJECT-TYPE 1133 SYNTAX InetAddressType 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "This object identifies the type of address carried in 1138 mplsTeP2mpTunnelDestDestination. 1140 This object forms part of the index of this table and can, 1141 therefore, not return the value unknown(0). Similarly, since 1142 the object mplsTeP2mpTunnelDestDestination must conform to 1143 the protocol specification, this object must return either 1144 ipv4(1) or ipv6(2)." 1145 ::= { mplsTeP2mpTunnelDestEntry 4 } 1147 mplsTeP2mpTunnelDestDestination OBJECT-TYPE 1148 SYNTAX InetAddress (SIZE (1..16)) 1149 MAX-ACCESS not-accessible 1150 STATUS current 1151 DESCRIPTION 1152 "A single destination of this P2MP tunnel. That is, a 1153 routable TE address of a leaf. This will often be the TE 1154 Router ID of the leaf, but can be any interface address. 1156 When a signaling protocol is used, this object corresponds 1157 to the S2L Sub-LSP destination address field in the 1158 S2L_SUB_LSP object. 1160 This object is interpreted in the context of 1161 mplsTeP2mpTunnelDestDestinationType." 1162 REFERENCE 1163 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 1164 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 1165 progress." 1166 ::= { mplsTeP2mpTunnelDestEntry 5 } 1168 mplsTeP2mpTunnelDestBranchOutSegment OBJECT-TYPE 1169 SYNTAX MplsIndexType 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "This object identifies the outgoing branch from this LSR 1174 towards the destination represented by this table entry. It 1175 must be a unique identifier within the scope of this tunnel. 1177 If MPLS-LSR-STD-MIB is implemented, this object should 1178 contain an index into mplsOutSegmentTable. 1180 If MPLS-LSR-STD-MIB is not implemented, the LSR should 1181 assign a unique value to each branch of the tunnel. 1183 The value of this object is also used as an index into 1184 mplsTeP2mpTunnelBranchPerfTable." 1185 ::= { mplsTeP2mpTunnelDestEntry 6 } 1187 mplsTeP2mpTunnelDestHopTableIndex OBJECT-TYPE 1188 SYNTAX MplsPathIndexOrZero 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "Index into the mplsTunnelHopTable entry that specifies the 1193 explicit route hops for this destination of the P2MP tunnel. 1195 This object represents the configured route for the branch 1196 of the P2MP tree to this destination and is meaningful only 1197 at the head-end (ingress or root) of the P2MP tunnel. Note 1198 that many such paths may be configured within the 1199 mplsTunnelHopTable for each destination, and that the object 1200 mplsTeP2mpTunnelDestPathInUse identifies which path has been 1201 selected for use." 1202 DEFVAL { 0 } 1203 ::= { mplsTeP2mpTunnelDestEntry 7 } 1205 mplsTeP2mpTunnelDestPathInUse OBJECT-TYPE 1206 SYNTAX MplsPathIndexOrZero 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "This value denotes the configured path that was chosen as 1211 the explicit path to this destination of this P2MP tunnel. 1212 This value reflects the secondary index into 1213 mplsTunnelHopTable where the primary index comes from 1214 mplsTeP2mpTunnelDestHopTableIndex. 1216 The path indicated by this object might not exactly match 1217 the one signaled and recorded in mplsTunnelCHopTable as 1218 specific details of the path might be computed locally. 1220 Similarly, the path might not match the actual path in use 1221 as recorded in mplsTunnelARHopTable due to the fact that 1222 some details of the path may have been resolved within the 1223 network. 1225 A value of zero denotes that no path is currently in use or 1226 available." 1227 DEFVAL { 0 } 1228 ::= { mplsTeP2mpTunnelDestEntry 8 } 1230 mplsTeP2mpTunnelDestCHopTableIndex OBJECT-TYPE 1231 SYNTAX MplsPathIndexOrZero 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "Index into the mplsTunnelCHopTable that identifies the 1236 explicit path for this destination of the P2MP tunnel. 1238 This path is based on the chosen configured path identified 1239 by mplsTeP2mpTunnelDestHopTableIndex and 1240 mplsTeP2mpTunnelDestPathInUse, but may have been modified 1241 and automatically updated by the agent when computed hops 1242 become available or when computed hops get modified. 1244 If this destination is the destination of the 'first S2L 1245 sub-LSP' then this path will be signaled in the Explicit 1246 Route Object. If this destination is the destination of a 1247 'subsequent S2L sub-LSP' then this path will be signaled in 1248 a Secondary Explicit Route Object." 1249 REFERENCE 1250 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 1251 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 1252 progress." 1253 ::= { mplsTeP2mpTunnelDestEntry 9 } 1255 mplsTeP2mpTunnelDestARHopTableIndex OBJECT-TYPE 1256 SYNTAX MplsPathIndexOrZero 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "Index into the mplsTunnelARHopTable that identifies the 1261 actual hops traversed to this destination of the P2MP 1262 tunnel. This is automatically updated by the agent when the 1263 actual hops becomes available. 1265 If this destination is the destination of the 'first S2L 1266 sub-LSP' then this path will be signaled in the Recorded 1267 Route Object. If this destination is the destination of a 1268 'subsequent S2L sub-LSP' then this path will be signaled in 1269 a Secondary Recorded Route Object." 1271 REFERENCE 1272 "Extensions to RSVP-TE for Point to Multipoint TE LSPs, 1273 R. Aggarwal, S. Yasukawa, and D. Papadimitriou, work in 1274 progress." 1275 ::= { mplsTeP2mpTunnelDestEntry 10 } 1277 mplsTeP2mpTunnelDestTotalUpTime OBJECT-TYPE 1278 SYNTAX TimeTicks 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "This value represents the aggregate up time for all 1283 instances of this tunnel to this destination, if this 1284 information is available. 1286 If this information is not available, this object MUST 1287 return a value of 0." 1288 ::= { mplsTeP2mpTunnelDestEntry 11 } 1290 mplsTeP2mpTunnelDestInstanceUpTime OBJECT-TYPE 1291 SYNTAX TimeTicks 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "This value identifies the total time that the currently 1296 active tunnel instance to this destination has had its 1297 operational status (mplsTeP2mpTunnelDestOperStatus) set to 1298 up(1) since it was last previously not up(1)." 1299 ::= { mplsTeP2mpTunnelDestEntry 12 } 1301 mplsTeP2mpTunnelDestPathChanges OBJECT-TYPE 1302 SYNTAX Counter32 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "This object counts the number of times the actual path for 1307 this destination of this P2MP tunnel instance has changed. 1308 This object should be read in conjunction with 1309 mplsTeP2mpTunnelDestDiscontinuityTime." 1310 ::= { mplsTeP2mpTunnelDestEntry 13 } 1312 mplsTeP2mpTunnelDestLastPathChange OBJECT-TYPE 1313 SYNTAX TimeTicks 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "Specifies the time since the last change to the actual path 1318 for this destination of this P2MP tunnel instance." 1319 ::= { mplsTeP2mpTunnelDestEntry 14 } 1321 mplsTeP2mpTunnelDestCreationTime OBJECT-TYPE 1322 SYNTAX TimeStamp 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "Specifies the value of sysUpTime when the first instance of 1327 this tunnel came into existence for this destination. That 1328 is, when the value of mplsTeP2mpTunnelDestOperStatus was 1329 first set to up(1)." 1330 ::= { mplsTeP2mpTunnelDestEntry 15 } 1332 mplsTeP2mpTunnelDestStateTransitions OBJECT-TYPE 1333 SYNTAX Counter32 1334 MAX-ACCESS read-only 1335 STATUS current 1336 DESCRIPTION 1337 "This object counts the number of times the status 1338 (mplsTeP2mpTunnelDestOperStatus) of this tunnel instance to 1339 this destination has changed. 1341 This object should be read in conjunction with 1342 mplsTeP2mpTunnelDestDiscontinuityTime." 1343 ::= { mplsTeP2mpTunnelDestEntry 16 } 1345 mplsTeP2mpTunnelDestDiscontinuityTime OBJECT-TYPE 1346 SYNTAX TimeStamp 1347 MAX-ACCESS read-only 1348 STATUS current 1349 DESCRIPTION 1350 "The value of sysUpTime on the most recent occasion at which 1351 any one or more of this row's Counter32 objects expeirenced 1352 a discontinuity. If no such discontinuity has occurred since 1353 the last re-initialization of the local management 1354 subsystem, then this object contains a zero value." 1355 ::= { mplsTeP2mpTunnelDestEntry 17 } 1357 mplsTeP2mpTunnelDestAdminStatus OBJECT-TYPE 1358 SYNTAX INTEGER { 1359 up(1), -- ready to pass data 1360 down(2), -- out of service 1361 testing(3) -- in some test mode 1362 } 1363 MAX-ACCESS read-create 1364 STATUS current 1365 DESCRIPTION 1366 "Indicates the desired operational status of this 1367 destination of this P2MP tunnel." 1368 DEFVAL { up } 1369 ::= { mplsTeP2mpTunnelDestEntry 18 } 1371 mplsTeP2mpTunnelDestOperStatus OBJECT-TYPE 1372 SYNTAX INTEGER { 1373 up(1), -- ready to pass data 1374 down(2), -- out of service 1375 testing(3), -- in some test mode 1376 unknown(4), -- status cannot be determined 1377 lowerLayerDown(7) -- down due to the state of 1378 -- lower layer interfaces 1379 } 1380 MAX-ACCESS read-only 1381 STATUS current 1382 DESCRIPTION 1383 "Indicates the actual operational status of this destination 1384 of this P2MP tunnel. 1385 This object may be compared to mplsTunnelOperStatus that 1386 includes two other values: 1387 dormant(5) -- some component is missing 1388 notPresent(6) -- down due to the state of 1389 -- lower layer interfaces. 1390 These states do not aply to an individual destinaton of a 1391 P2MP MPLS-TE LSP and so are not included in this object." 1392 REFERENCE 1393 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 1394 Engineering (TE) Management Information Base (MIB), 1395 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 1396 ::= { mplsTeP2mpTunnelDestEntry 19 } 1398 mplsTeP2mpTunnelDestRowStatus OBJECT-TYPE 1399 SYNTAX RowStatus 1400 MAX-ACCESS read-create 1401 STATUS current 1402 DESCRIPTION 1403 "This object is used to create, modify, and/or delete a row 1404 in this table. When a row in this table is in active(1) 1405 state, no objects in that row can be modified by SET 1406 operations except mplsTeP2mpTunnelDestAdminStatus and 1407 mplsTeP2mpTunnelDestStorageType." 1408 ::= { mplsTeP2mpTunnelDestEntry 20 } 1410 mplsTeP2mpTunnelDestStorageType OBJECT-TYPE 1411 SYNTAX StorageType 1412 MAX-ACCESS read-create 1413 STATUS current 1414 DESCRIPTION "The storage type for this table entry. 1416 Conceptual rows having the value 'permanent' need 1417 not allow write-access to any columnar objects in 1418 the row." 1419 DEFVAL { volatile } 1420 ::= { mplsTeP2mpTunnelDestEntry 21 } 1422 -- End of mplsTeP2mpTunnelDestTable 1424 -- MPLS Tunnel Branch Performance Table. 1426 mplsTeP2mpTunnelBranchPerfTable OBJECT-TYPE 1427 SYNTAX SEQUENCE OF MplsTeP2mpTunnelBranchPerfEntry 1428 MAX-ACCESS not-accessible 1429 STATUS current 1430 DESCRIPTION 1431 "This table provides per-tunnel branch MPLS performance 1432 information. 1434 This table is not valid for switching types other than 1435 packet." 1436 ::= { mplsTeP2mpObjects 4 } 1438 mplsTeP2mpTunnelBranchPerfEntry OBJECT-TYPE 1439 SYNTAX MplsTeP2mpTunnelBranchPerfEntry 1440 MAX-ACCESS not-accessible 1441 STATUS current 1442 DESCRIPTION 1443 "An entry in this table is created by the LSR for each 1444 downstream branch (out-segment) from this LSR for this P2MP 1445 tunnel. 1447 More than one destination as represented by an entry in the 1448 mplsTeP2mpTunnelDestTable may be reached through a single 1449 out-segment. More than one out-segment may belong to a 1450 single P2MP tunnel represented by an entry in 1451 mplsTeP2mpTunnelTable. 1453 Each entry in the table is indexed by the four identifiers 1454 of the P2MP tunnel, and the out-segment that identifies the 1455 outgoing branch." 1456 INDEX { mplsTunnelIndex, 1457 mplsTunnelInstance, 1458 mplsTunnelIngressLSRId, 1459 mplsTunnelEgressLSRId, 1460 mplsTeP2mpTunnelBranchPerfBranch 1461 } 1462 ::= { mplsTeP2mpTunnelBranchPerfTable 1 } 1464 mplsTeP2mpTunnelBranchPerfEntry ::= SEQUENCE { 1465 mplsTeP2mpTunnelBranchPerfBranch MplsIndexType, 1466 mplsTeP2mpTunnelBranchPerfPackets Counter32, 1467 mplsTeP2mpTunnelBranchPerfHCPackets Counter64, 1468 mplsTeP2mpTunnelBranchPerfErrors Counter32, 1469 mplsTeP2mpTunnelBranchPerfBytes Counter32, 1470 mplsTeP2mpTunnelBranchPerfHCBytes Counter64, 1471 mplsTeP2mpTunnelBranchDiscontinuityTime TimeStamp 1472 } 1474 mplsTeP2mpTunnelBranchPerfBranch OBJECT-TYPE 1475 SYNTAX MplsIndexType 1476 MAX-ACCESS not-accessible 1477 STATUS current 1478 DESCRIPTION 1479 "This object identifies the outgoing branch from this LSR 1480 for this tunnel. Its value is unique within the context of 1481 the tunnel. If MPLS-LSR-STD-MIB is implemented, this object 1482 should contain a row pointer to the out-segment for this 1483 branch. Under all circumstances, this object should contain 1484 the same value as mplsTeP2mpTunnelDestBranchOutSegment for 1485 destinations reached on this branch." 1486 ::= { mplsTeP2mpTunnelBranchPerfEntry 1 } 1488 mplsTeP2mpTunnelBranchPerfPackets OBJECT-TYPE 1489 SYNTAX Counter32 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "Number of packets forwarded by the tunnel onto this branch. 1494 This object should represents the 32-bit value of the least 1495 significant part of the 64-bit value if both 1496 mplsTeP2mpTunnelBranchPerfHCPackets is returned. 1497 This object should be read in conjunction with 1498 mplsTeP2mpTunnelBranchDiscontinuityTime." 1499 ::= { mplsTeP2mpTunnelBranchPerfEntry 2 } 1501 mplsTeP2mpTunnelBranchPerfHCPackets OBJECT-TYPE 1502 SYNTAX Counter64 1503 MAX-ACCESS read-only 1504 STATUS current 1505 DESCRIPTION 1506 "High capacity counter for number of packets forwarded by the 1507 tunnel onto this branch. 1508 This object should be read in conjunction with 1509 mplsTeP2mpTunnelBranchDiscontinuityTime." 1510 ::= { mplsTeP2mpTunnelBranchPerfEntry 3 } 1512 mplsTeP2mpTunnelBranchPerfErrors OBJECT-TYPE 1513 SYNTAX Counter32 1514 MAX-ACCESS read-only 1515 STATUS current 1516 DESCRIPTION 1517 "Number of packets dropped because of errors or for other 1518 reasons, that were supposed to be forwarded onto this 1519 branch for this tunnel. 1520 This object should be read in conjunction with 1521 mplsTeP2mpTunnelBranchDiscontinuityTime." 1522 ::= { mplsTeP2mpTunnelBranchPerfEntry 4 } 1524 mplsTeP2mpTunnelBranchPerfBytes OBJECT-TYPE 1525 SYNTAX Counter32 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "Number of bytes forwarded by the tunnel onto this branch. 1530 This object should represents the 32-bit value of the least 1531 significant part of the 64-bit value if both 1532 mplsTeP2mpTunnelBranchPerfHCBytes is returned. 1533 This object should be read in conjunction with 1534 mplsTeP2mpTunnelBranchDiscontinuityTime." 1535 ::= { mplsTeP2mpTunnelBranchPerfEntry 5 } 1537 mplsTeP2mpTunnelBranchPerfHCBytes OBJECT-TYPE 1538 SYNTAX Counter64 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "High capacity counter for number of bytes forwarded 1543 by the tunnel onto this branch. 1544 This object should be read in conjunction with 1545 mplsTeP2mpTunnelBranchDiscontinuityTime." 1546 ::= { mplsTeP2mpTunnelBranchPerfEntry 6 } 1548 mplsTeP2mpTunnelBranchDiscontinuityTime OBJECT-TYPE 1549 SYNTAX TimeStamp 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "The value of sysUpTime on the most recent occasion at which 1554 any one or more of this row's Counter32 or COunter64 objects 1555 expeirenced a discontinuity. If no such discontinuity has 1556 occurred since the last re-initialization of the local 1557 management subsystem, then this object contains a zero 1558 value." 1559 ::= { mplsTeP2mpTunnelBranchPerfEntry 7 } 1561 -- End of mplsTeP2mpTunnelBranchPerfTable 1563 -- Notifications. 1565 mplsTeP2mpTunnelNotificationEnable OBJECT-TYPE 1566 SYNTAX TruthValue 1567 MAX-ACCESS read-write 1568 STATUS current 1569 DESCRIPTION 1570 "If this object is true(1), then it enables the generation of 1571 mplsTeP2mpTunnelDestUp and mplsTeP2mpTunnelDestDown 1572 notifications. Otherwise these notifications are not 1573 emitted." 1574 DEFVAL { false } 1575 ::= { mplsTeP2mpObjects 5 } 1577 mplsTeP2mpTunnelDestUp NOTIFICATION-TYPE 1578 OBJECTS { 1579 mplsTeP2mpTunnelDestAdminStatus, 1580 mplsTeP2mpTunnelDestOperStatus 1581 } 1582 STATUS current 1583 DESCRIPTION 1584 "This notification is generated when a 1585 mplsTeP2mpTunnelDestOperStatus object for one of the 1586 destinations of one of the configured tunnels is about to 1587 leave the down(2) state and transition into some other 1588 state. This other state is indicated by the included value 1589 of mplsTeP2mpTunneldestOperStatus. 1590 This reporting of state transitions mirrors mplsTunnelUp." 1591 REFERENCE 1592 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 1593 Engineering (TE) Management Information Base (MIB), 1594 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 1595 ::= { mplsTeP2mpNotifications 1 } 1597 mplsTeP2mpTunnelDestDown NOTIFICATION-TYPE 1598 OBJECTS { 1599 mplsTeP2mpTunnelDestAdminStatus, 1600 mplsTeP2mpTunnelDestOperStatus 1601 } 1602 STATUS current 1603 DESCRIPTION 1604 "This notification is generated when a 1605 mplsTeP2mpTunnelDestOperStatus object for one of the 1606 destinations of one of the configured tunnels is about to 1607 enter the down(2) state from some other state. This other 1608 state is indicated by the included value of 1609 mplsTeP2mpTunnelDestOperStatus. 1610 This reporting of state transitions mirrors mplsTunnelDown." 1611 REFERENCE 1612 "RFC 3812 - Multiprotocol Label Switching (MPLS) Traffic 1613 Engineering (TE) Management Information Base (MIB), 1614 Srinivasan, C., Viswanathan, A., and T. Nadeau, June 2004." 1615 ::= { mplsTeP2mpNotifications 2 } 1617 -- End of notifications. 1619 -- Module compliance. 1621 mplsTeP2mpGroups 1622 OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 1 } 1624 mplsTeP2mpCompliances 1625 OBJECT IDENTIFIER ::= { mplsTeP2mpConformance 2 } 1627 -- Compliance requirement for fully compliant implementations. 1629 mplsTeP2mpModuleFullCompliance MODULE-COMPLIANCE 1630 STATUS current 1631 DESCRIPTION 1632 "Compliance statement for agents that provide full support 1633 for MPLS-TE-P2MP-STD-MIB. Such devices can be monitored and 1634 also be configured using this MIB module." 1636 MODULE -- This module. 1638 MANDATORY-GROUPS { 1639 mplsTeP2mpGroup, 1640 mplsTeP2mpNotifGroup 1641 } 1642 ::= { mplsTeP2mpCompliances 1 } 1644 -- Units of conformance. 1646 mplsTeP2mpGroup OBJECT-GROUP 1647 OBJECTS { 1648 mplsTeP2mpTunnelConfigured, 1649 mplsTeP2mpTunnelActive, 1650 mplsTeP2mpTunnelTotalMaxHops, 1651 mplsTeP2mpTunnelIsP2MP, 1652 mplsTeP2mpTunnelP2mpIntegrity, 1653 mplsTeP2mpTunnelBranchRole, 1654 mplsTeP2mpTunnelRowStatus, 1655 mplsTeP2mpTunnelStorageType, 1656 mplsTeP2mpTunnelSubGroupIDNext, 1657 mplsTeP2mpTunnelDestBranchOutSegment, 1658 mplsTeP2mpTunnelDestHopTableIndex, 1659 mplsTeP2mpTunnelDestPathInUse, 1660 mplsTeP2mpTunnelDestCHopTableIndex, 1661 mplsTeP2mpTunnelDestARHopTableIndex, 1662 mplsTeP2mpTunnelDestTotalUpTime, 1663 mplsTeP2mpTunnelDestInstanceUpTime, 1664 mplsTeP2mpTunnelDestPathChanges, 1665 mplsTeP2mpTunnelDestLastPathChange, 1666 mplsTeP2mpTunnelDestCreationTime, 1667 mplsTeP2mpTunnelDestStateTransitions, 1668 mplsTeP2mpTunnelDestDiscontinuityTime, 1669 mplsTeP2mpTunnelDestAdminStatus, 1670 mplsTeP2mpTunnelDestOperStatus, 1671 mplsTeP2mpTunnelDestRowStatus, 1672 mplsTeP2mpTunnelDestStorageType, 1673 mplsTeP2mpTunnelBranchPerfPackets, 1674 mplsTeP2mpTunnelBranchPerfHCPackets, 1675 mplsTeP2mpTunnelBranchPerfErrors, 1676 mplsTeP2mpTunnelBranchPerfBytes, 1677 mplsTeP2mpTunnelBranchPerfHCBytes, 1678 mplsTeP2mpTunnelBranchDiscontinuityTime, 1679 mplsTeP2mpTunnelNotificationEnable 1680 } 1681 STATUS current 1682 DESCRIPTION 1683 "Collection of objects needed for MPLS P2MP." 1684 ::= { mplsTeP2mpGroups 1 } 1685 mplsTeP2mpNotifGroup NOTIFICATION-GROUP 1686 NOTIFICATIONS { 1687 mplsTeP2mpTunnelDestUp, 1688 mplsTeP2mpTunnelDestDown 1689 } 1690 STATUS current 1691 DESCRIPTION 1692 "Notifications implemented in this module." 1693 ::= { mplsTeP2mpGroups 2 } 1694 END 1696 8. Security Considerations 1698 It is clear that this MIB module is potentially useful for the 1699 monitoring of P2MP MPLS TE tunnels. This MIB module can also be used 1700 for the configuration of certain objects, and anything that can be 1701 configured can be incorrectly configured, with potentially disastrous 1702 results. 1704 There are a number of management objects defined in this MIB module 1705 with a MAX-ACCESS clause of read-write and/or read-create. Such 1706 objects may be considered sensitive or vulnerable in some network 1707 environments. The support for SET operations in a non-secure 1708 environment without proper protection can have a negative effect on 1709 network operations. These are the tables and objects and their 1710 sensitivity/vulnerability: 1712 - The mplsTeP2mpTunnelTable and mplsTeP2mpTunnelDestTable contain 1713 objects that can be used to provision P2MP MPLS tunnels, the 1714 destinations of those tunnels, and the hops that those tunnels take 1715 through the network. Unauthorized access to objects in these tables 1716 could result in disruption of traffic in the network. This is 1717 especially true if a tunnel has already been established. 1719 The use of stronger mechanisms, such as SNMPv3 security, should be 1720 considered where possible. Specifically, SNMPv3 VACM and USM MUST 1721 be used with any v3 agent which implements this MIB module. 1722 Administrators SHOULD also consider whether read access to these 1723 objects is allowed, since read access may be undesirable under 1724 certain circumstances as described below. 1726 - The use of this MIB module depends on the use of certain objects 1727 within MPLS-TE-STD-MIB defined in [RFC3812]. Note that those 1728 objects are also subject to the same security considerations, and 1729 any vulnerability to those objects could compromise the P2MP MPLS 1730 tunnels and/or data in the network. The security section of 1731 [RFC3812] MUST be applied in conjunction with this security 1732 section. 1734 - This MIB module does not depend on MPLS-LSR-STD-MIB, but may be 1735 used in conjunction with that MIB module. If MPLS-LSR-STD-MIB is 1736 implemented on an LSR, then access to its objects can compromise 1737 any P2MP MPLS tunnels that start or end on, or transit the LSR. 1738 MPLS-LSR-STD-MIB is defined in [RFC3813] which has its own security 1739 section that MUST be applied in conjunction with this security 1740 section if both MIB modules are supported. 1742 Some of the readable objects in this MIB module (i.e., objects with a 1743 MAX-ACCESS other than not-accessible) may be considered sensitive or 1744 vulnerable in some network environments. It is thus important to 1745 control even GET and/or NOTIFY access to these objects, and possibly 1746 even to encrypt the values of these objects when sending them over 1747 the network via SNMP. These are the tables and objects and their 1748 sensitivity/vulnerability: 1750 - The mplsTeP2mpTunnelTable, mplsTeP2mpTunnelDestTable, and 1751 mplsTeP2mpTunnelBranchPerfTable collectively show information about 1752 the P2MP MPLS tunnel, its route through the network, and its 1753 performance characteristics. Knowledge of this information could be 1754 used to compromise the network, or simply to breach 1755 confidentiality. If an Administrator does not want to reveal this 1756 information, these tables should be considered 1757 sensitive/vulnerable. 1759 - The objects in MPLS-TE-STD-MIB also provide information about the 1760 P2MP MPLS tunnels defined in this MIB module. If an Administrator 1761 does not want to reveal this information, the security section of 1762 [RFC3812] should be applied. 1764 - The objects in MPLS-LSR-STD-MIB, if implemented, may also provide 1765 information about the P2MP MPLS tunnels present at an LSR, 1766 especially the label swapping and cross-connect operations. If an 1767 Administrator does not want to reveal this information, the 1768 security section of [RFC3813] should be applied. 1770 SNMP versions prior to SNMPv3 did not include adequate security. 1771 Even if the network itself is secure (for example by using IPSec), 1772 even then, there is no control as to who on the secure network is 1773 allowed to access and GET/SET (read/change/create/delete) the objects 1774 in this MIB module. 1776 It is RECOMMENDED that implementers consider the security features as 1777 provided by the SNMPv3 framework (see [RFC3410], section 8), 1778 including full support for the SNMPv3 cryptographic mechanisms (for 1779 authentication and privacy). 1781 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1782 RECOMMENDED. Instead, it is RECOMMENDED that SNMPv3 be deployed and 1783 cryptographic security enabled. It is then a customer/operator 1784 responsibility to ensure that the SNMP entity giving access to an 1785 instance of this MIB module is properly configured to give access to 1786 only those principals (users) that have legitimate rights to those 1787 objects. 1789 9. Acknowledgments 1791 The authors wish to thank Tom Petch and Ben Niven-Jenkins for their 1792 input to this work. 1794 Comments should be made directly to the MPLS mailing list at 1795 mpls@lists.ietf.org 1797 10. IANA Considerations 1799 As requested in MPLS-TC-STD-MIB [RFC3811], MPLS-related standards 1800 track MIB modules should be rooted under the mplsStdMIB subtree. 1802 There is one new MPLS MIB module contained in this document, and the 1803 following "IANA Considerations" subsection requests IANA for a new 1804 assignment under the mplsStdMIB subtree. 1806 New assignments can only be made via a Standards Action as specified 1807 in [RFC2434]. 1809 10.1. IANA Considerations for MPLS-TE-P2MP-STD-MIB 1811 IANA is requested to assign an oid under the mplsStdMIB subtree to 1812 the MPLS-TE-P2MP-STD-MIB module specified in this document. 1814 -- RFC Editor. Please see the marker YYY in this document and replace it 1815 -- with the value assigned by IANA. 1816 -- Please remove this note. 1818 11. References 1820 11.1. Normative References 1822 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate 1823 Requirement Levels", BCP 14, RFC 2119, March 1997. 1825 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1826 "Structure of Management Information Version 2 (SMIv2)", 1827 STD 58, RFC 2578, April 1999. 1829 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1830 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1831 1999. 1833 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1834 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1835 April 1999. 1837 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1838 Label Switching Architecture", RFC 3031, January 2001. 1840 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., 1841 and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP 1842 Tunnels", RFC 3209, December 2001. 1844 [RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information 1845 Base for the Differentiated Services Architecture", RFC 1846 3289, May 2002. 1848 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and J. 1849 Schoenwaelder, "TextualConventions for Internet Network 1850 Addresses", RFC 3291, May 2002. 1852 [RFC3811] Nadeau, T. and J. Cucchiara, "Definition of Textual 1853 Conventions and for Multiprotocol Label Switching (MPLS) 1854 Management", RFC 3811, June 2004. 1856 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1857 "Multiprotocol Label Switching (MPLS) Traffic 1858 Engineering (TE) Management Information Base (MIB)", 1859 RFC 3812, June 2004. 1861 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1862 "Multiprotocol Label Switching (MPLS) Label Switching 1863 (LSR) Router Management Information Base (MIB)", RFC 3813, 1864 June 2004. 1866 [RFC3945] Mannie, E., Ed., "Generalized Multiprotocol Label 1867 Switching (GMPLS) Architecture", RFC 3945, October 2004. 1869 [RFC4461] S. Yasukawa, Editor "Signaling Requirements for 1870 Point-to-Multipoint Traffic Engineered MPLS LSPs", 1871 RFC4461, April 2006. 1873 [P2MP-TE] Aggarwal, R., Papadimitriou, D., and Yasukawa, S., 1874 "Extensions to RSVP-TE for Point to Multipoint TE 1875 LSPs", draft-ietf-mpls-rsvp-te-p2mp, work in progress. 1877 11.2. Informative References 1879 [RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol 1880 Label Switching (MPLS) Management Overview", RFC 4221, 1881 November 2005. 1883 [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an 1884 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 1885 October 1998. 1887 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1888 "Introduction and Applicability Statement for Internet 1889 Standard Management Framework", RFC 3410, December 2002. 1891 [GMPLS-TE-MIB] Nadeau, T. and A. Farrel, "Generalized Multiprotocol 1892 Label Switching (GMPLS) Traffic Engineering Management 1893 Information Base", draft-ietf-ccamp-gmpls-te-mib, work 1894 in progress. 1896 12. Authors' Addresses 1898 Adrian Farrel 1899 Old Dog Consulting 1900 Email: adrian@olddog.co.uk 1902 Seisho Yasukawa 1903 NTT Corporation 1904 9-11, Midori-Cho 3-Chome 1905 Musashino-Shi, Tokyo 180-8585 Japan 1906 Phone: +81 422 59 4769 1907 EMail: s.yasukawa@hco.ntt.co.jp 1909 Thomas D. Nadeau 1910 Cisco Systems, Inc. 1911 1414 Massachusetts Ave. 1912 Boxborough, MA 01719 1913 Email: tnadeau@cisco.com 1915 13. Intellectual Property 1917 The IETF takes no position regarding the validity or scope of any 1918 Intellectual Property Rights or other rights that might be claimed to 1919 pertain to the implementation or use of the technology described in 1920 this document or the extent to which any license under such rights 1921 might or might not be available; nor does it represent that it has 1922 made any independent effort to identify any such rights. Information 1923 on the procedures with respect to rights in RFC documents can be 1924 found in BCP 78 and BCP 79. 1926 Copies of IPR disclosures made to the IETF Secretariat and any 1927 assurances of licenses to be made available, or the result of an 1928 attempt made to obtain a general license or permission for the use of 1929 such proprietary rights by implementers or users of this 1930 specification can be obtained from the IETF on-line IPR repository at 1931 http://www.ietf.org/ipr. 1933 The IETF invites any interested party to bring to its attention any 1934 copyrights, patents or patent applications, or other proprietary 1935 rights that may cover technology that may be required to implement 1936 this standard. Please address the information to the IETF at ietf- 1937 ipr@ietf.org. 1939 14. Full Copyright Statement 1941 Copyright (C) The Internet Society (2006). This document is subject 1942 to the rights, licenses and restrictions contained in BCP 78, and 1943 except as set forth therein, the authors retain all their rights. 1945 This document and the information contained herein are provided on an 1946 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 1947 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1948 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1949 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1950 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1951 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.