idnits 2.17.1 draft-li-mpls-ldp-mt-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 164 instances of too long lines in the document, the longest one being 12 characters in excess of 72. ** There are 2 instances of lines with control characters in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 241: '...pMtLspOperStatus MUST both be set equa...' RFC 2119 keyword, line 248: '...time, the device SHOULD issue a single...' RFC 2119 keyword, line 253: '...erStatus objects MUST be the identical...' RFC 2119 keyword, line 266: '...pMtLspOperStatus MUST both be set equa...' RFC 2119 keyword, line 273: '... the device SHOULD issue a single...' (7 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 1116 has weird spacing: '...Service class...' == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: mplsLdpMtInSegmentIndex OBJECT-TYPE SYNTAX MplsIndexType MAX-ACCESS read-only STATUS current DESCRIPTION "The index for this MT in-segment. The string containing the single octet 0x00 MUST not be used as an index." ::= { mplsLdpMtInSegmentEntry 1 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: mplsLdpMtOutSegmentIndex OBJECT-TYPE SYNTAX MplsIndexType MAX-ACCESS read-only STATUS current DESCRIPTION "The index for this MT out-segment. The string containing the single octet 0x00 MUST not be used as an index." ::= { mplsLdpMtOutSegmentEntry 1 } == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 19, 2013) is 3841 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2578' is mentioned on line 112, but not defined == Missing Reference: 'RFC2579' is mentioned on line 113, but not defined == Missing Reference: 'RFC2580' is mentioned on line 113, but not defined == Unused Reference: 'RFC3813' is defined on line 1211, but no explicit reference was found in the text == Unused Reference: 'RFC3814' is defined on line 1216, but no explicit reference was found in the text == Unused Reference: 'RFC5036' is defined on line 1227, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-mpls-ldp-multi-topology' is defined on line 1234, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-12) exists of draft-ietf-mpls-ldp-multi-topology-08 Summary: 4 errors (**), 0 flaws (~~), 13 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MPLS Working Group Chen. Li 3 Internet-Draft Lianyuan. Li 4 Intended status: Standards Track Lu. Huang 5 Expires: January 09, 2014 Vic Liu 6 China Mobile 7 Tao. Chou 8 Quintin. Zhao 9 Huawei Technology 10 Emily. Chen 12 October 19, 2013 14 Management Information Base for MPLS LDP Multi Topology 15 draft-li-mpls-ldp-mt-mib-05.txt 17 Abstract 19 This memo defines an portion of the Management Information Base (MIB) 20 for use with network management protocols in the Internet community. 21 In particular, it describes a MIB module for Multi-Topology Networks 22 over Multi-protocol Label Switching(MPLS) Label Switching 23 Routers(LSRs). 25 Status of This Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on January 09, 2014. 42 Copyright Notice 44 Copyright (c) 2013 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 This document may contain material from IETF Documents or IETF 58 Contributions published or made publicly available before November 59 10, 2008. The person(s) controlling the copyright in some of this 60 material may not have granted the IETF Trust the right to allow 61 modifications of such material outside the IETF Standards Process. 62 Without obtaining an adequate license from the person(s) controlling 63 the copyright in such materials, this document may not be modified 64 outside the IETF Standards Process, and derivative works of it may 65 not be created outside the IETF Standards Process, except to format 66 it for publication as an RFC or to translate it into languages other 67 than English. 69 Table of Contents 71 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 72 2. The Internet-Standard Management Framework . . . . . . . . . 3 73 3. Overview of MPLS-LDP-MT-STD-MIB objects . . . . . . . . . . . 3 74 3.1. MPLS LDP MT Entity Table . . . . . . . . . . . . . . . . 3 75 3.2. MPLS LDP MT Entity Statistics Table . . . . . . . . . . . 3 76 3.3. MPLS LDP MT Session Table . . . . . . . . . . . . . . . . 3 77 3.4. MPLS LDP MT In-segment Tables . . . . . . . . . . . . . . 4 78 3.5. MPLS LDP MT Out-segment Tables . . . . . . . . . . . . . 4 79 3.6. MPLS LDP MT LSP Table . . . . . . . . . . . . . . . . . . 4 80 3.7. MPLS LDP MT Notifications . . . . . . . . . . . . . . . . 4 81 4. MPLS-LDP-MT-STD-MIB Module Definitions . . . . . . . . . . . 4 82 5. Security Considerations . . . . . . . . . . . . . . . . . . . 27 83 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 84 7. Normative References . . . . . . . . . . . . . . . . . . . . 27 85 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 28 87 1. Introduction 89 There are increasing requirements to support multi-topology in MPLS 90 network. For example, service providers want to assign different 91 level of service(s) to different topologies so that the service 92 separation can be achieved. It is also possible to have an in-band 93 management network on top of the original MPLS topology, or maintain 94 separate routing and MPLS domains for isolated multicast or IPv6 95 islands within the backbone, or force a subset of an address space to 96 follow a different MPLS topology for the purpose of security, QoS or 97 simplified management and/or operations. 99 For a detailed overview of the multi topology, please refer to I-D 100 .ietf-mpls-ldp-multi-topology. 102 2. The Internet-Standard Management Framework 104 For a detailed overview of the documents that describe the current 105 Internet-Standard Management Framework, please refer to section 7 of 106 RFC 3410[RFC3410] . Managed objects are accessed via a virtual 107 information store, termed the Management Information Base or MIB. 108 MIB objects are generally accessed through the Simple Network 109 Management Protocol (SNMP). Objects in the MIB are defined using the 110 mechanisms defined in the Structure of Management Information (SMI). 111 This memo specifies a MIB module that is compliant to the SMIv2, 112 which is described in STD 58, RFC 2578[RFC2578], STD 58, RFC 113 2579[RFC2579] and STD 58, RFC 2580[RFC2580]. 115 3. Overview of MPLS-LDP-MT-STD-MIB objects 117 The following subsections describe the purpose of each of the objects 118 contained in the MPLS-LDP-MT-STD-MIB. 120 3.1. MPLS LDP MT Entity Table 122 The mplsLdpEntityTable specified in [RFC3815] is used to configure 123 information which is used by the LDP protocol to setup potential LDP 124 Sessions. The mplsLdpMtEntityTable can be considered as an extension 125 to mplsLdpEntityTable to setup potential LDP MT Sessions. 127 Each entry/row in this table represents a single LDP MT Entity. 128 There is no maximum number of LDP MT Entities specified. However, 129 there is an mplsLdpMtEntityIndexNext object which should be retrieved 130 by the command generator prior to creating an LDP MT Entity. If the 131 mplsLdpMtEntityIndexNext object is zero, this indicates that the LSR/ 132 LER is not able to create another LDP MT Entity at that time. 134 3.2. MPLS LDP MT Entity Statistics Table 136 This table provides MPLS Multi Topology performance information on a 137 per-interface basis. 139 3.3. MPLS LDP MT Session Table 141 Since all the MT related label messages can be advertised by LDP 142 Sessions in default topology, there is no need to create extra tcp 143 connection for Multi Topology. 145 The mplsLdpMtSessionTable is a read-only table. Each entry in this 146 table represents an MT Session which is related to one or more LDP MT 147 Entities and only one LDP Session in default topology. 149 3.4. MPLS LDP MT In-segment Tables 151 The mplsLdpMtInSegmentTable contains information about the MPLS Label 152 Distribution Protocol Multi Topology In-Segments which exist on this 153 Label Switching Router (LSR) or Label Edge Router (LER). 155 The mplsLdpMtInSegmentStatsTable contains statistical information for 156 LDP MT in-segments. 158 3.5. MPLS LDP MT Out-segment Tables 160 This table contains information about the MPLS Label Distribution 161 Protocol Multi Topology Out-Segments which exist on this Label 162 Switching Router (LSR) or Label Edge Router (LER). 164 The mplsLdpMtInSegmentStatsTable contains statistical information for 165 LDP MT out-segments. 167 3.6. MPLS LDP MT LSP Table 169 This table specifies MT LIB label switching information. Entries in 170 this table define LIB label switching entries associated with the 171 specified FEC of the specified topology. 173 3.7. MPLS LDP MT Notifications 175 The mplsLdpMtLspUp and mplsLdpMtLspDown notifications are generated 176 when there is an appropriate change in the mplsLdpMtLspOperStatus 177 object, e.g., when the LSP changes state (Up to Down for the 178 mplsLdpMtLspDown notification, or Down to Up for the mplsLdpMtLspUp 179 notification). 181 4. MPLS-LDP-MT-STD-MIB Module Definitions 183 MPLS-LDP-MT-STD-MIB DEFINITIONS ::= BEGIN 185 IMPORTS 186 IndexIntegerNextFree, IndexInteger 187 FROM DIFFSERV-MIB 188 InetAddress, InetAddressPrefixLength 189 FROM INET-ADDRESS-MIB 190 MplsIndexType 191 FROM MPLS-LSR-STD-MIB 192 MplsLdpLabelType, MplsLspType, MplsLdpIdentifier 193 FROM MPLS-TC-STD-MIB 194 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 195 FROM SNMPv2-CONF 196 transmission, TimeTicks, Integer32, Unsigned32, Counter32, 197 Counter64, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE 198 FROM SNMPv2-SMI 199 QosService FROM INTEGRATED-SERVICES-MIB 200 TimeStamp, StorageType, RowStatus 201 FROM SNMPv2-TC; 203 mplsLdpMtStdMIB MODULE-IDENTITY 204 LAST-UPDATED "201206131436Z" -- June 13, 2012 at 14:36 GMT 205 ORGANIZATION 206 "Multiprotocol Label Switching (mpls) Working Group" 207 CONTACT-INFO 208 "Chen Li (lichenyj@chinamobile.com) 209 Lianyuan Li (lilianyuan@chinamobile.com) 210 Lu Huang (huanglu@chinamobile.com) 211 China Mobile 213 Emily Chen (emily.chenying@huawei.com) 214 Quintin Zhao (qzhao@huawei.com) 215 Huawei Technologies" 216 DESCRIPTION 217 "This MIB contains managed object definitions for the 218 'Multiprotocol Label Switching, Label Distribution Protocol, 219 Multi Topology'document." 220 ::= { mplsStdMIB 1 } 222 -- 223 -- Node definitions 224 -- 226 -- 1.3.6.1.2.1.10.1.1 227 mplsStdMIB OBJECT IDENTIFIER ::= { transmission 166 } 229 mplsLdpMtNotifications OBJECT IDENTIFIER ::= { mplsLdpMtStdMIB 0 } 231 mplsLdpMtLspUp NOTIFICATION-TYPE 232 OBJECTS { mplsLdpMtLspOperStatus, -- start of range 233 mplsLdpMtLspOperStatus -- end of range 234 } 235 STATUS current 236 DESCRIPTION 237 "This notification is generated when the 238 mplsLdpMtLspOperStatus object for one or more contiguous 239 entries in mplsLdpMtLspTable are about to enter the up(1) 240 state from some other state. The included values of 241 mplsLdpMtLspOperStatus MUST both be set equal to this new 242 state (i.e: up(1)). The two instances of 243 mplsLdpMtLspOperStatus in this notification indicate the range 244 of indexes that are affected. Note that all the indexes of 245 the two ends of the range can be derived from the instance 246 identifiers of these two objects. For cases where a contiguous 247 range of cross-connects have transitioned into the up(1) state 248 at roughly the same time, the device SHOULD issue a single 249 notification for each range of contiguous indexes in an effort 250 to minimize the emission of a large number of notifications. 251 If a notification has to be issued for just a single 252 cross-connect entry, then the instance identifier (and values) 253 of the two mplsLdpMtLspOperStatus objects MUST be the identical." 254 ::= { mplsLdpMtNotifications 1 } 256 mplsLdpMtLspDown NOTIFICATION-TYPE 257 OBJECTS { mplsLdpMtLspOperStatus, -- start of range 258 mplsLdpMtLspOperStatus -- end of range 259 } 260 STATUS current 261 DESCRIPTION 262 "This notification is generated when the 263 mplsLdpMtLspOperStatus object for one or more contiguous 264 entries in mplsLdpMtLspTable are about to enter the down(2) 265 state from some other state. The included values of 266 mplsLdpMtLspOperStatus MUST both be set equal to this down(2) 267 state. The two instances of mplsLdpMtLspOperStatus in this 268 notification indicate the range of indexes that are affected. 269 Note that all the indexes of the two ends of the range can be 270 derived from the instance identifiers of these two objects. 271 For cases where a contiguous range of cross-connects have 272 transitioned into the down(2) state at roughly the same time, 273 the device SHOULD issue a single notification for each range 274 of contiguous indexes in an effort to minimize the emission of 275 a large number of notifications. If a notification has to be 276 issued for just a single cross-connect entry, then the 277 instance identifier (and values) of the two 278 mplsLdpMtLspOperStatus objects MUST be identical." 279 ::= { mplsLdpMtNotifications 2 } 281 mplsLdpMtObjects OBJECT IDENTIFIER ::= { mplsLdpMtStdMIB 1 } 283 mplsLdpMtEntityObjects OBJECT IDENTIFIER ::= { mplsLdpMtObjects 1 } 285 mplsLpMtEntityLastChange OBJECT-TYPE 286 SYNTAX TimeStamp 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The value of sysUpTime at the time of the most 291 recent addition or deletion of an entry 292 to/from the mplsLdpMtEntityTable, or 293 the most recent change in value of any objects in the 294 mplsLdpMtEntityTable. 296 If no such changes have occurred since the last 297 re-initialization of the local management subsystem, 298 then this object contains a zero value." 299 ::= { mplsLdpMtEntityObjects 1 } 301 mplsLdpMtEntityIndexNext OBJECT-TYPE 302 SYNTAX IndexIntegerNextFree 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "This object contains an appropriate value to 307 be used for mplsLdpEntityIndex when creating 308 entries in the mplsLdpEntityTable. The value 309 0 indicates that no unassigned entries are 310 available." 311 ::= { mplsLdpMtEntityObjects 2 } 313 -- mplsLdpMtEntityTable 314 mplsLdpMtEntityTable OBJECT-TYPE 315 SYNTAX SEQUENCE OF MplsLdpMtEntityEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "This table contains information about the 320 MPLS Label Distribution Protocol Multi Topology 321 Entities which exist on this Label Switching 322 Router (LSR) or Label Edge Router (LER)." 323 ::= { mplsLdpMtEntityObjects 3 } 325 mplsLdpMtEntityEntry OBJECT-TYPE 326 SYNTAX MplsLdpMtEntityEntry 327 MAX-ACCESS not-accessible 328 STATUS current 329 DESCRIPTION 330 "An entry in this table represents an LDP MT entity. 331 An entry can be created by a network administrator 332 or by an SNMP agent as instructed by LDP." 333 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 334 mplsLdpMtEntityIndex } 335 ::= { mplsLdpMtEntityTable 1 } 337 MplsLdpMtEntityEntry ::= 338 SEQUENCE { 339 mplsLdpMtEntityLdpId 340 MplsLdpIdentifier, 341 mplsLdpMtEntityMtId 342 Unsigned32, 343 mplsLdpMtEntityIndex 344 IndexInteger, 345 mplsLdpMtEntityAdminStatus 346 INTEGER, 347 mplsLdpMtEntityStorageType 348 StorageType, 349 mplsLdpMtEntityRowStatus 350 RowStatus 351 } 353 mplsLdpMtEntityLdpId OBJECT-TYPE 354 SYNTAX MplsLdpIdentifier 355 MAX-ACCESS not-accessible 356 STATUS current 357 DESCRIPTION 358 "The LDP identifier." 359 REFERENCE 360 "RFC 5036, LDP Specification, Section on LDP Identifiers." 361 ::= { mplsLdpMtEntityEntry 1 } 363 mplsLdpMtEntityMtId OBJECT-TYPE 364 SYNTAX Unsigned32 (0..65535) 365 MAX-ACCESS read-create 366 STATUS current 367 DESCRIPTION 368 "The Multi Topology identifier of this LDP MT Entity." 369 REFERENCE 370 "draft-ietf-mpls-ldp-multi-topology, LDP Extensions for Multi 371 Topology Routing, Section on Multi-Topology ID." 372 ::= { mplsLdpMtEntityEntry 2 } 374 mplsLdpMtEntityIndex OBJECT-TYPE 375 SYNTAX IndexInteger 376 MAX-ACCESS not-accessible 377 STATUS current 378 DESCRIPTION 379 "This index is used as a secondary index to uniquely identify 380 this row. Before creating a row in this table, the 381 'mplsLdpMtEntityIndexNext' object should be retrieved. That 382 value should be used for the value of this index when creating 383 a row in this table. NOTE: if a value of zero (0) is 384 retrieved, that indicates that no rows can be created in this 385 table at this time." 386 ::= { mplsLdpMtEntityEntry 3 } 388 mplsLdpMtEntityAdminStatus OBJECT-TYPE 389 SYNTAX INTEGER 390 { 391 enable(1), 392 disable(2) 393 } 394 MAX-ACCESS read-create 395 STATUS current 396 DESCRIPTION 397 "The administrative status of this LDP MT Entity. If this 398 object is changed from 'enable' to 'disable' and this entity 399 has already attempted to establish contact with a MT Session, 400 then all contact with that MT Session is lost and all 401 information from that MT Session needs to be removed from the 402 MIB. (This implies that the network management subsystem 403 should clean up any related entry in the 404 mplsLdpMtSessionTable.). At this point the operator is able 405 to change values which are related to this entity. When the 406 admin status is set back to 'enable', then this MT Entity will 407 attempt to establish a new MT Session." 408 DEFVAL { enable } 409 ::= { mplsLdpMtEntityEntry 4 } 411 mplsLdpMtEntityStorageType OBJECT-TYPE 412 SYNTAX StorageType 413 MAX-ACCESS read-create 414 STATUS current 415 DESCRIPTION 416 "The storage type for this conceptual row. Conceptual rows 417 having the value 'permanent(4)' need not allow write-access 418 to any columnar objects in the row." 419 ::= { mplsLdpMtEntityEntry 5 } 421 mplsLdpMtEntityRowStatus OBJECT-TYPE 422 SYNTAX RowStatus 423 MAX-ACCESS read-create 424 STATUS current 425 DESCRIPTION 426 "The status of this conceptual row. All writable objects in 427 this row may be modified at any time, however, as described 428 in detail in the section entitled, 'Changing Values After 429 Session Establishment', and again described in the DESCRIPTION 430 clause of the mplsLdpMtEntityAdminStatus object, if a session 431 has been initiated with a Peer, changing objects in this table 432 will wreak havoc with the session and interrupt traffic. To 433 repeat again: the recommended procedure is to set the 434 mplsLdpMtEntityAdminStatus to down, thereby explicitly causing 435 a session to be torn down. Then, change objects in this entry, 436 then set the mplsLdpMtEntityAdminStatus to enable, which enables 437 a new session to be initiated." 438 ::= { mplsLdpMtEntityEntry 6 } 440 -- mplsLdpMtEntityStatsTable 441 mplsLdpMtEntityStatsTable OBJECT-TYPE 442 SYNTAX SEQUENCE OF MplsLdpMtEntityStatsEntry 443 MAX-ACCESS not-accessible 444 STATUS current 445 DESCRIPTION 446 "This table contains statistical information for 447 LDP MT entities to an LSR." 448 ::= { mplsLdpMtEntityObjects 4 } 450 mplsLdpMtEntityStatsEntry OBJECT-TYPE 451 SYNTAX MplsLdpMtEntityStatsEntry 452 MAX-ACCESS not-accessible 453 STATUS current 454 DESCRIPTION 455 "An entry in this table is created by the LSR for every 456 interface capable of supporting MPLS LDP Multi Topology. 457 It is an extension to the mplsLdpMtEntityEntry table. 458 Note that the discontinuity behavior of entries in this table 459 MUST be based on the corresponding 460 ifEntry's ifDiscontinuityTime." 462 AUGMENTS { mplsLdpMtEntityEntry } 463 ::= { mplsLdpMtEntityStatsTable 1 } 465 MplsLdpMtEntityStatsEntry ::= 466 SEQUENCE { 467 mplsLdpMtEntityStatsOctets 468 Counter32, 469 mplsLdpMtEntityStatsPackets 470 Counter32, 471 mplsLdpMtEntityStatsErrors 472 Counter32, 473 mplsLdpMtEntityStatsDiscards 474 Counter32, 475 mplsLdpMtEntityStatsHCOctets 476 Counter64, 477 mplsLdpMtEntityStatsDiscontinuityTime 478 TimeTicks 479 } 481 mplsLdpMtEntityStatsOctets OBJECT-TYPE 482 SYNTAX Counter32 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "This value represents the total number of octets received 487 by this MT interface. It MUST be equal to the least 488 significant 32 bits of mplsLdpMtEntityStatsHCOctets if 489 mplsLdpMtEntityStatsHCOctets is supported according to 490 the rules spelled out in RFC2863." 491 ::= { mplsLdpMtEntityStatsEntry 1 } 493 mplsLdpMtEntityStatsPackets OBJECT-TYPE 494 SYNTAX Counter32 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "Total number of packets received by this MT interface." 499 ::= { mplsLdpMtEntityStatsEntry 2 } 501 mplsLdpMtEntityStatsErrors OBJECT-TYPE 502 SYNTAX Counter32 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION 506 "The number of error packets received on this MT interface." 508 ::= { mplsLdpMtEntityStatsEntry 3 } 510 mplsLdpMtEntityStatsDiscards OBJECT-TYPE 511 SYNTAX Counter32 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "The number of labeled packets received on this MT interface, 516 which were chosen to be discarded even though no errors had 517 been detected to prevent their being transmitted. 518 One possible reason for discarding such a labeled packet 519 could be to free up buffer space." 520 ::= { mplsLdpMtEntityStatsEntry 4 } 522 mplsLdpMtEntityStatsHCOctets OBJECT-TYPE 523 SYNTAX Counter64 524 MAX-ACCESS read-only 525 STATUS current 526 DESCRIPTION 527 "The total number of octets received. This is the 64 bit 528 version of mplsLdpMtEntityStatsOctets, if 529 mplsLdpMtEntityStatsHCOctets is supported according to the 530 rules spelled out in RFC2863." 531 ::= { mplsLdpMtEntityStatsEntry 5 } 533 mplsLdpMtEntityStatsDiscontinuityTime OBJECT-TYPE 534 SYNTAX TimeTicks 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION 538 "The value of sysUpTime on the most recent occasion at which 539 any one or more of this MT interface's Counter32 or Counter64 540 suffered a discontinuity. If no such discontinuities have 541 occurred since the last re-initialization of the local 542 management subsystem, then this object contains a zero value." 543 ::= { mplsLdpMtEntityStatsEntry 6 } 545 mplsLdpMtSessionObjects OBJECT IDENTIFIER 546 ::= { mplsLdpMtObjects 2 } 548 mplsLdpMtSessionLastChange OBJECT-TYPE 549 SYNTAX TimeStamp 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The value of sysUpTime at the time of the most 554 recent addition or deletion to/from the 555 mplsLdpMtSessionTable." 556 ::= { mplsLdpMtSessionObjects 1 } 558 -- mplsLdpMtSessionTable 559 mplsLdpMtSessionTable OBJECT-TYPE 560 SYNTAX SEQUENCE OF MplsLdpMtSessionEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "A table of MT Sessions between the LDP MT Entities. Each row 565 in this table represents a single MT session." 566 ::= { mplsLdpMtSessionObjects 2 } 568 mplsLdpMtSessionEntry OBJECT-TYPE 569 SYNTAX MplsLdpMtSessionEntry 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION 573 "An entry in this table represents information on a single MT 574 session. The information contained in a row is read-only." 575 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 576 mplsLdpMtEntityIndex, mplsLdpMtSessionPeerId } 577 ::= { mplsLdpMtSessionTable 1 } 579 MplsLdpMtSessionEntry ::= 580 SEQUENCE { 581 mplsLdpMtSessionPeerId 582 MplsLdpIdentifier, 583 mplsLdpMtSessionState 584 INTEGER, 585 mplsLdpMtSessionStateLastChange 586 TimeStamp 587 } 589 mplsLdpMtSessionPeerId OBJECT-TYPE 590 SYNTAX MplsLdpIdentifier 591 MAX-ACCESS not-accessible 592 STATUS current 593 DESCRIPTION 594 "The LDP identifier of this LDP MT Peer." 595 ::= { mplsLdpMtSessionEntry 1 } 597 mplsLdpMtSessionState OBJECT-TYPE 598 SYNTAX INTEGER 599 { 600 initialized(1), 601 operational(2) 602 } 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "The current state of the MT Session. When the tcp connection 607 in default topology is established, and both ends have the 608 capability of the given MT-ID, the state can change from 609 initialized to operational." 610 ::= { mplsLdpMtSessionEntry 2 } 612 mplsLdpMtSessionStateLastChange OBJECT-TYPE 613 SYNTAX TimeStamp 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "The value of sysUpTime at the time this MT Session was 618 created." 619 ::= { mplsLdpMtSessionEntry 3 } 621 mplsLdpMtLspObjects OBJECT IDENTIFIER ::= { mplsLdpMtObjects 3 } 623 -- mplsLdpMtInSegmentTable 624 mplsLdpMtInSegmentTable OBJECT-TYPE 625 SYNTAX SEQUENCE OF MplsLdpMtInSegmentEntry 626 MAX-ACCESS not-accessible 627 STATUS current 628 DESCRIPTION 629 "This table contains information about the MPLS Label 630 Distribution Protocol Multi Topology 631 In-Segments which exist on this Label Switching Router (LSR) 632 or Label Edge Router (LER)." 633 ::= { mplsLdpMtLspObjects 1 } 635 mplsLdpMtInSegmentEntry OBJECT-TYPE 636 SYNTAX MplsLdpMtInSegmentEntry 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "An entry in this table represents information on a single 641 LDP MT LSP which is represented by a MT session's index 642 combination (mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 643 mplsLdpMtEntityIndex, mplsLdpMtSessionPeerId). 645 The information contained in a row is read-only." 646 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 647 mplsLdpMtEntityIndex, mplsLdpMtSessionPeerId } 648 ::= { mplsLdpMtInSegmentTable 1 } 650 MplsLdpMtInSegmentEntry ::= 651 SEQUENCE { 652 mplsLdpMtInSegmentIndex 653 MplsIndexType, 654 mplsLdpMtInSegmentLabelType 655 MplsLdpLabelType, 656 mplsLdpMtInSegmentLspType 657 MplsLspType 658 } 660 mplsLdpMtInSegmentIndex OBJECT-TYPE 661 SYNTAX MplsIndexType 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The index for this MT in-segment. The string containing 666 the single octet 0x00 MUST not be used as an index." 667 ::= { mplsLdpMtInSegmentEntry 1 } 669 mplsLdpMtInSegmentLabelType OBJECT-TYPE 670 SYNTAX MplsLdpLabelType 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The Layer 2 Label Type." 675 ::= { mplsLdpMtInSegmentEntry 2 } 677 mplsLdpMtInSegmentLspType OBJECT-TYPE 678 SYNTAX MplsLspType 679 MAX-ACCESS read-only 680 STATUS current 681 DESCRIPTION 682 "The type of LSP connection." 683 ::= { mplsLdpMtInSegmentEntry 3 } 685 -- mplsLdpMtInSegmentStatsTable 686 mplsLdpMtInSegmentStatsTable OBJECT-TYPE 687 SYNTAX SEQUENCE OF MplsLdpMtInSegmentStatsEntry 688 MAX-ACCESS not-accessible 689 STATUS current 690 DESCRIPTION 691 "This table contains statistical information for LDP MT 692 in-segments to an LSR." 693 ::= { mplsLdpMtLspObjects 2 } 695 mplsLdpMtInSegmentStatsEntry OBJECT-TYPE 696 SYNTAX MplsLdpMtInSegmentStatsEntry 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "An entry in this table contains statistical information about 701 one incoming MT segment which is configured in the 702 mplsLdpMtInSegmentTable. The counters in this entry should 703 behave in a manner similar to that of the MT interface. 704 mplsLdpMtInSegmentStatsDiscontinuityTime indicates the time 705 of the last discontinuity in all of these objects." 706 AUGMENTS { mplsLdpMtInSegmentEntry } 707 ::= { mplsLdpMtInSegmentStatsTable 1 } 709 MplsLdpMtInSegmentStatsEntry ::= 710 SEQUENCE { 711 mplsLdpMtInSegmentStatsOctets 712 Counter32, 713 mplsLdpMtInSegmentStatsPackets 714 Counter32, 715 mplsLdpMtInSegmentStatsErrors 716 Counter32, 717 mplsLdpMtInSegmentStatsDiscards 718 Counter32, 719 mplsLdpMtInSegmentStatsHCOctets 720 Counter64, 721 mplsLdpMtInSegmentStatsDiscontinuityTime 722 TimeTicks 723 } 725 mplsLdpMtInSegmentStatsOctets OBJECT-TYPE 726 SYNTAX Counter32 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "This value represents the total number of octets received 731 by this MT segment. It MUST be equal to the least significant 732 32 bits of mplsLdpMtInSegmentStatsHCOctets if 733 mplsLdpMtInSegmentStatsHCOctets is supported according to 734 the rules spelled out in RFC2863." 735 ::= { mplsLdpMtInSegmentStatsEntry 1 } 737 mplsLdpMtInSegmentStatsPackets OBJECT-TYPE 738 SYNTAX Counter32 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "Total number of packets received by this MT segment." 743 ::= { mplsLdpMtInSegmentStatsEntry 2 } 745 mplsLdpMtInSegmentStatsErrors OBJECT-TYPE 746 SYNTAX Counter32 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The number of error packets received on this MT segment." 751 ::= { mplsLdpMtInSegmentStatsEntry 3 } 753 mplsLdpMtInSegmentStatsDiscards OBJECT-TYPE 754 SYNTAX Counter32 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "The number of labeled packets received on this MT in-segment, 759 which were chosen to be discarded even though no errors had 760 been detected to prevent their being transmitted. 761 One possible reason for discarding such a labeled packet 762 could be to free up buffer space." 763 ::= { mplsLdpMtInSegmentStatsEntry 4 } 765 mplsLdpMtInSegmentStatsHCOctets OBJECT-TYPE 766 SYNTAX Counter64 767 MAX-ACCESS read-only 768 STATUS current 769 DESCRIPTION 770 "The total number of octets received. This is the 64 bit 771 version of mplsLdpMtInSegmentStatsOctets, if 772 mplsLdpMtInSegmentStatsHCOctets is supported according to the 773 rules spelled out in RFC2863." 774 ::= { mplsLdpMtInSegmentStatsEntry 5 } 776 mplsLdpMtInSegmentStatsDiscontinuityTime OBJECT-TYPE 777 SYNTAX TimeTicks 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "The value of sysUpTime on the most recent occasion at which 782 any one or more of this MT segment's Counter32 or Counter64 783 suffered a discontinuity. If no such discontinuities have 784 occurred since the last re-initialization of the local 785 management subsystem, then this object contains a zero value." 786 ::= { mplsLdpMtInSegmentStatsEntry 6 } 788 -- mplsLdpMtOutSegmentTable 789 mplsLdpMtOutSegmentTable OBJECT-TYPE 790 SYNTAX SEQUENCE OF MplsLdpMtOutSegmentEntry 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "This table contains information about the MPLS Label 795 Distribution Protocol Multi Topology Out-Segments which 796 exist on this Label Switching Router (LSR) or Label 797 Edge Router (LER)." 798 ::= { mplsLdpMtLspObjects 3 } 800 mplsLdpMtOutSegmentEntry OBJECT-TYPE 801 SYNTAX MplsLdpMtOutSegmentEntry 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "An entry in this table represents information on a single 806 LDP MT LSP which is represented by a MT session's index 807 combination (mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 808 mplsLdpMtEntityIndex, mplsLdpMtSessionPeerId). 810 The information contained in a row is read-only." 811 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 812 mplsLdpMtEntityIndex, mplsLdpMtSessionPeerId } 813 ::= { mplsLdpMtOutSegmentTable 1 } 815 MplsLdpMtOutSegmentEntry ::= 816 SEQUENCE { 817 mplsLdpMtOutSegmentIndex 818 MplsIndexType, 819 mplsLdpMtOutSegmentLabelType 820 MplsLdpLabelType, 822 mplsLdpMtOutSegmentLspType 823 MplsLspType 824 } 826 mplsLdpMtOutSegmentIndex OBJECT-TYPE 827 SYNTAX MplsIndexType 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The index for this MT out-segment. The string containing 832 the single octet 0x00 MUST not be used as an index." 833 ::= { mplsLdpMtOutSegmentEntry 1 } 835 mplsLdpMtOutSegmentLabelType OBJECT-TYPE 836 SYNTAX MplsLdpLabelType 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The Layer 2 Label Type." 841 ::= { mplsLdpMtOutSegmentEntry 2 } 843 mplsLdpMtOutSegmentLspType OBJECT-TYPE 844 SYNTAX MplsLspType 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "The type of LSP connection." 849 ::= { mplsLdpMtOutSegmentEntry 3 } 851 -- mplsLdpMtOutSegmentStatsTable 852 mplsLdpMtOutSegmentStatsTable OBJECT-TYPE 853 SYNTAX SEQUENCE OF MplsLdpMtOutSegmentStatsEntry 854 MAX-ACCESS not-accessible 855 STATUS current 856 DESCRIPTION 857 "This table contains statistical information for LDP MT 858 out-segments to an LSR." 859 ::= { mplsLdpMtLspObjects 4 } 861 mplsLdpMtOutSegmentStatsEntry OBJECT-TYPE 862 SYNTAX MplsLdpMtOutSegmentStatsEntry 863 MAX-ACCESS not-accessible 864 STATUS current 865 DESCRIPTION 866 "An entry in this table contains statistical information 867 about one incoming MT segment which is configured in the 868 mplsLdpMtOutSegmentTable. The counters in this entry should 869 behave in a manner similar to that of the MT interface. 870 mplsLdpMtOutSegmentStatsDiscontinuityTime indicates the time 871 of the last discontinuity in all of these objects." 872 AUGMENTS { mplsLdpMtOutSegmentEntry } 873 ::= { mplsLdpMtOutSegmentStatsTable 1 } 875 MplsLdpMtOutSegmentStatsEntry ::= 876 SEQUENCE { 877 mplsLdpMtOutSegmentStatsOctets 878 Counter32, 879 mplsLdpMtOutSegmentStatsPackets 880 Counter32, 881 mplsLdpMtOutSegmentStatsErrors 882 Counter32, 883 mplsLdpMtOutSegmentStatsDiscards 884 Counter32, 885 mplsLdpMtOutSegmentStatsHCOctets 886 Counter64, 887 mplsLdpMtOutSegmentStatsDiscontinuityTime 888 TimeTicks 889 } 891 mplsLdpMtOutSegmentStatsOctets OBJECT-TYPE 892 SYNTAX Counter32 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "This value represents the total number of octets received 897 by this MT segment. It MUST be equal to the least significant 898 32 bits of mplsLdpMtOutSegmentStatsHCOctets if 899 mplsLdpMtOutSegmentStatsHCOctets is supported according to 900 the rules spelled out in RFC2863." 901 ::= { mplsLdpMtOutSegmentStatsEntry 1 } 903 mplsLdpMtOutSegmentStatsPackets OBJECT-TYPE 904 SYNTAX Counter32 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "Total number of packets received by this MT segment." 909 ::= { mplsLdpMtOutSegmentStatsEntry 2 } 911 mplsLdpMtOutSegmentStatsErrors OBJECT-TYPE 912 SYNTAX Counter32 913 MAX-ACCESS read-only 914 STATUS current 915 DESCRIPTION 916 "The number of error packets received on this MT segment." 917 ::= { mplsLdpMtOutSegmentStatsEntry 3 } 919 mplsLdpMtOutSegmentStatsDiscards OBJECT-TYPE 920 SYNTAX Counter32 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The number of labeled packets received on this MT out-segment, 925 which were chosen to be discarded even though no errors had 926 been detected to prevent their being transmitted. 927 One possible reason for discarding such a labeled packet 928 could be to free up buffer space." 929 ::= { mplsLdpMtOutSegmentStatsEntry 4 } 931 mplsLdpMtOutSegmentStatsHCOctets OBJECT-TYPE 932 SYNTAX Counter64 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "The total number of octets received. This is the 64 bit 937 version of mplsLdpMtOutSegmentStatsOctets, if 938 mplsLdpMtOutSegmentStatsHCOctets is supported according to 939 the rules spelled out in RFC2863." 940 ::= { mplsLdpMtOutSegmentStatsEntry 5 } 942 mplsLdpMtOutSegmentStatsDiscontinuityTime OBJECT-TYPE 943 SYNTAX TimeTicks 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "The value of sysUpTime on the most recent occasion at which 948 any one or more of this MT segment's Counter32 or Counter64 949 suffered a discontinuity. If no such discontinuities have 950 occurred since the last re-initialization of the local 951 management subsystem, then this object contains a zero value." 952 ::= { mplsLdpMtOutSegmentStatsEntry 6 } 954 mplsLdpMtLspLastChange OBJECT-TYPE 955 SYNTAX TimeStamp 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "The value of sysUpTime at the time of the most recent addition 960 or deletion of an entry to/from the mplsLdpMtLspTable, or the 961 most recent change in value of any objects in the 962 mplsLdpMtLspTable. 964 If no such changes have occurred since the last 965 re-initialization of the local management subsystem, 966 then this object contains a zero value." 967 ::= { mplsLdpMtLspObjects 5 } 969 mplsLdpMtLspIndexNext OBJECT-TYPE 970 SYNTAX IndexIntegerNextFree 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "This object contains an appropriate value to be used for 975 mplsLdpMtLspIndex when creating entries in the 976 mplsLdpMtLspTable. The value 0 indicates that no unassigned 977 entries are available." 978 ::= { mplsLdpMtLspObjects 6 } 980 -- mplsLdpMtLspTable 981 mplsLdpMtLspTable OBJECT-TYPE 982 SYNTAX SEQUENCE OF MplsLdpMtLspEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "This table specifies MT LIB label switching information. 987 Entries in this table define LIB label switching entries 988 associated with the specified topology." 989 ::= { mplsLdpMtLspObjects 7 } 991 mplsLdpMtLspEntry OBJECT-TYPE 992 SYNTAX MplsLdpMtLspEntry 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "An entry in this table is created by an LSR for every label 997 within the context of a specific topology capable of 998 supporting MT LDP LSP.The indexing provides an ordering 999 of topologies per interface." 1001 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityMtId, 1002 mplsLdpMtEntityIndex, mplsLdpMtLspInSegmentIndex, 1003 mplsLdpMtLspOutSegmentIndex, mplsLdpMtLspIndex } 1004 ::= { mplsLdpMtLspTable 1 } 1006 MplsLdpMtLspEntry ::= 1007 SEQUENCE { 1008 mplsLdpMtLspIndex 1009 IndexInteger, 1010 mplsLdpMtLspFecAddr 1011 InetAddress, 1012 mplsLdpMtLspFecAddrLength 1013 InetAddressPrefixLength, 1014 mplsLdpMtLspInSegmentIndex 1015 MplsIndexType, 1016 mplsLdpMtLspOutSegmentIndex 1017 MplsIndexType, 1018 mplsLdpMtLspRowStatus 1019 Integer32, 1020 mplsLdpMtLspStorageType 1021 StorageType, 1022 mplsLdpMtLspOperStatus 1023 RowStatus, 1024 mplsLdpMtLspService 1025 QosService 1026 } 1028 mplsLdpMtLspIndex OBJECT-TYPE 1029 SYNTAX IndexInteger 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "The index which uniquely identifies this entry." 1034 ::= { mplsLdpMtLspEntry 1 } 1036 mplsLdpMtLspFecAddr OBJECT-TYPE 1037 SYNTAX InetAddress 1038 MAX-ACCESS read-only 1039 STATUS current 1040 DESCRIPTION 1041 "The FEC address of this LDP MT LSP. Note that the 1042 value of this object is interpreted as prefix address." 1043 REFERENCE 1044 "RFC 5036, Section 3.4.1 FEC TLV." 1045 ::= { mplsLdpMtLspEntry 2 } 1047 mplsLdpMtLspFecAddrLength OBJECT-TYPE 1048 SYNTAX InetAddressPrefixLength 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "The FEC prefix length of this LDP MT LSP." 1053 REFERENCE 1054 "RFC5036, Section 3.4.1. FEC TLV" 1055 ::= { mplsLdpMtLspEntry 3 } 1057 mplsLdpMtLspInSegmentIndex OBJECT-TYPE 1058 SYNTAX MplsIndexType 1059 MAX-ACCESS not-accessible 1060 STATUS current 1061 DESCRIPTION 1062 "Index of in-segment for this LDP MT LSP." 1063 ::= { mplsLdpMtLspEntry 4 } 1065 mplsLdpMtLspOutSegmentIndex OBJECT-TYPE 1066 SYNTAX MplsIndexType 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION 1070 "Index of out-segment for this LDP MT LSP." 1071 ::= { mplsLdpMtLspEntry 5 } 1073 mplsLdpMtLspRowStatus OBJECT-TYPE 1074 SYNTAX Integer32 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "For creating, modifying, and deleting this row. 1079 When a row in this table has a row in the active(1) 1080 state, no objects in this row except this object 1081 and the mplsLdpMtLspStorageType can be modified." 1082 ::= { mplsLdpMtLspEntry 6 } 1084 mplsLdpMtLspStorageType OBJECT-TYPE 1085 SYNTAX StorageType 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "The storage type for this conceptual row. 1090 Conceptual rows having the value 'permanent(4)' 1091 need not allow write-access to any columnar 1092 objects in the row." 1093 DEFVAL { nonVolatile } 1094 ::= { mplsLdpMtLspEntry 7 } 1096 mplsLdpMtLspOperStatus OBJECT-TYPE 1097 SYNTAX RowStatus 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The status of this conceptual row. If the value of this 1102 object is 'active(1)', then none of the writable objects 1103 of this entry can be modified, except to set this object 1104 to 'destroy(6)'. 1106 NOTE: if this row is being referenced by any entry in 1107 the mplsLdpLspFecTable, then a request to destroy 1108 this row, will result in an inconsistentValue error." 1109 ::= { mplsLdpMtLspEntry 8 } 1111 mplsLdpMtLspService OBJECT-TYPE 1112 SYNTAX QosService 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "The QoS Service classification index for multiple 1117 topology LSP." 1118 ::= { mplsLdpMtLspEntry 9 } 1120 mplsLdpMtConformance OBJECT IDENTIFIER ::= { mplsLdpMtStdMIB 2 } 1122 mplsLdpMtGroups OBJECT IDENTIFIER ::= { mplsLdpMtConformance 1 } 1124 mplsLdpMtEntityGroup OBJECT-GROUP 1125 OBJECTS { mplsLpMtEntityLastChange, mplsLdpMtEntityIndexNext, 1126 mplsLdpMtEntityMtId, mplsLdpMtEntityAdminStatus, 1127 mplsLdpMtEntityStorageType, mplsLdpMtEntityRowStatus, 1128 mplsLdpMtEntityStatsDiscontinuityTime, 1129 mplsLdpMtEntityStatsHCOctets, mplsLdpMtEntityStatsDiscards, 1130 mplsLdpMtEntityStatsErrors, mplsLdpMtEntityStatsPackets, 1131 mplsLdpMtEntityStatsOctets } 1132 STATUS current 1133 DESCRIPTION 1134 "Objects that apply to all MPLS LDP MT Entity implementations." 1135 ::= { mplsLdpMtGroups 2 } 1137 mplsLdpMtSessionGroup OBJECT-GROUP 1138 OBJECTS { mplsLdpMtSessionLastChange, mplsLdpMtSessionState, 1139 mplsLdpMtSessionStateLastChange } 1140 STATUS current 1141 DESCRIPTION 1142 "Objects that apply to all MPLS LDP MT Session implementations." 1143 ::= { mplsLdpMtGroups 3 } 1145 mplsLdpMtLspGroup OBJECT-GROUP 1146 OBJECTS { mplsLdpMtLspLastChange, mplsLdpMtLspIndexNext, 1147 mplsLdpMtLspFecAddr, mplsLdpMtLspFecAddrLength, 1148 mplsLdpMtLspRowStatus, mplsLdpMtLspStorageType, 1149 mplsLdpMtLspOperStatus, mplsLdpMtInSegmentIndex, 1150 mplsLdpMtInSegmentLabelType, mplsLdpMtInSegmentLspType, 1151 mplsLdpMtInSegmentStatsOctets, mplsLdpMtInSegmentStatsPackets, 1152 mplsLdpMtInSegmentStatsErrors, mplsLdpMtInSegmentStatsDiscards, 1153 mplsLdpMtInSegmentStatsHCOctets, 1154 mplsLdpMtInSegmentStatsDiscontinuityTime, 1155 mplsLdpMtOutSegmentIndex, mplsLdpMtOutSegmentLabelType, 1156 mplsLdpMtOutSegmentLspType, mplsLdpMtOutSegmentStatsOctets, 1157 mplsLdpMtOutSegmentStatsPackets, mplsLdpMtOutSegmentStatsErrors, 1158 mplsLdpMtOutSegmentStatsDiscards, 1159 mplsLdpMtOutSegmentStatsHCOctets, 1160 mplsLdpMtOutSegmentStatsDiscontinuityTime 1161 } 1162 STATUS current 1163 DESCRIPTION 1164 "Objects that apply to all MPLS LDP MT LSP implementations." 1165 ::= { mplsLdpMtGroups 4 } 1167 mplsLdpMtNotificationGroup NOTIFICATION-GROUP 1168 NOTIFICATIONS { mplsLdpMtLspUp, mplsLdpMtLspDown } 1169 STATUS current 1170 DESCRIPTION 1171 "The notifications for an MPLS LDP MT implementation." 1172 ::= { mplsLdpMtGroups 5 } 1174 mplsLdpMtCompliances OBJECT IDENTIFIER ::= { mplsLdpMtConformance 2 } 1176 mplsLdpMtModuleFullCompliance MODULE-COMPLIANCE 1177 STATUS current 1178 DESCRIPTION 1179 "The Module is implemented with support 1180 for read-create and read-write. In other 1181 words, both monitoring and configuration 1182 are available when using this MODULE-COMPLIANCE." 1183 MODULE -- this module 1184 MANDATORY-GROUPS { mplsLdpMtEntityGroup, mplsLdpMtSessionGroup, 1185 mplsLdpMtLspGroup, mplsLdpMtNotificationGroup } 1186 ::= { mplsLdpMtCompliances 1 } 1188 mplsLdpMtModuleReadOnlyCompliance MODULE-COMPLIANCE 1189 STATUS current 1190 DESCRIPTION 1191 "The Module is implemented with support 1192 for read-only. In other words, only monitoring 1193 is available by implementing this MODULE-COMPLIANCE" 1194 MODULE -- this module 1195 MANDATORY-GROUPS { mplsLdpMtEntityGroup, mplsLdpMtSessionGroup, 1196 mplsLdpMtLspGroup, mplsLdpMtNotificationGroup } 1197 ::= { mplsLdpMtCompliances 2 } 1199 END 1201 5. Security Considerations 1203 It needs to be further identified. 1205 6. IANA Considerations 1207 There is no necessary to request new IANA code in the draft. 1209 7. Normative References 1211 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1212 "Multiprotocol Label Switching (MPLS) Label Switching 1213 Router (LSR) Management Information Base (MIB)", RFC 3813, 1214 June 2004. 1216 [RFC3814] Nadeau, T., Srinivasan, C., and A. Viswanathan, 1217 "Multiprotocol Label Switching (MPLS) Forwarding 1218 Equivalence Class To Next Hop Label Forwarding Entry (FEC- 1219 To-NHLFE) Management Information Base (MIB)", RFC 3814, 1220 June 2004. 1222 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1223 of Managed Objects for the Multiprotocol Label Switching 1224 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, June 1225 2004. 1227 [RFC5036] Andersson, L., Minei, I., and B. Thomas, "LDP 1228 Specification", RFC 5036, October 2007. 1230 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1231 "Introduction and Applicability Statements for Internet- 1232 Standard Management Framework", RFC 3410, December 2002. 1234 [I-D.ietf-mpls-ldp-multi-topology] 1235 Zhao, Q., Fang, L., Zhou, C., Li, L., and K. Raza, "LDP 1236 Extensions for Multi Topology Routing", draft-ietf-mpls- 1237 ldp-multi-topology-08 (work in progress), May 2013. 1239 Authors' Addresses 1241 Chen Li 1242 China Mobile 1243 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 1244 Beijing 100053 1245 P.R. China 1247 Email: lichenyj@chinamobile.com 1249 Lianyuan Li 1250 China Mobile 1251 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 1252 Beijing 100053 1253 P.R. China 1255 Email: lilianyuan@chinamobile.com 1256 Lu Huang 1257 China Mobile 1258 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 1259 Xunwu District, Beijing 100053 1260 China 1262 Email: huanglu@chinamobile.com 1264 Vic Liu 1265 China Mobile 1266 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 1267 Xunwu District, Beijing 100053 1268 China 1270 Email: liuzhiheng@chinamobile.com 1272 Tao Chou 1273 Huawei Technology 1274 156 Beiqing Rd 1275 Haidian District, Beijing 100095 1276 China 1278 Email: tao.chou@huawei.com 1280 Quintin Zhao 1281 Huawei Technology 1282 125 Nagog Technology Park 1283 Acton, MA 01719 1284 US 1286 Email: quintin.zhao@huawei.com 1288 Emily Chen 1289 2717 Seville Blvd, Apt 1205 1290 Clearwater, FL 33764 1291 US 1293 Email: emily.chen220@gmail.com