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