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