idnits 2.17.1 draft-li-mpls-ldp-mt-mib-02.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 7 instances of too long lines in the document, the longest one being 1 character in excess of 72. ** There are 189 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 11, 2012) is 4419 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: 'I-D.ietf-mpls-ldp-multi-topology' is mentioned on line 78, but not defined == Missing Reference: 'RFC2578' is mentioned on line 157, but not defined == Missing Reference: 'RFC2579' is mentioned on line 163, but not defined == Missing Reference: 'RFC2580' is mentioned on line 160, but not defined == Missing Reference: 'RFC4001' is mentioned on line 167, but not defined == Missing Reference: 'RFC3289' is mentioned on line 171, but not defined == Missing Reference: 'RFC3811' is mentioned on line 174, but not defined == Unused Reference: 'RFC3814' is defined on line 625, but no explicit reference was found in the text == Unused Reference: 'RFC5036' is defined on line 630, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 3 errors (**), 0 flaws (~~), 10 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: September 12, 2012 China Mobile 6 Emily Chen 7 Quintin Zhao 8 Huawei Technologies 9 March 11, 2012 11 Management Information Base for MPLS LDP Multi Topology 12 draft-li-mpls-ldp-mt-mib-02 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 September 12, 2012. 39 Copyright Notice 41 Copyright (c) 2011 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 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 57 2. The Internet-Standard Management Framework . . . . . . . . . . 3 58 3. Overview of MT-MPLS-STD-MIB objects . . . . . . . . . . . . . 3 59 4. MPLS-LDP-MT-STD-MIB Module Definitions . . . . . . . . . . . . 5 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 62 7. Normative References . . . . . . . . . . . . . . . . . . . . . 16 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 65 1. Introduction 67 There are increasing requirements to support multi-topology in MPLS 68 network. For example, service providers want to assign different 69 level of service(s) to different topologies so that the service 70 separation can be achieved. It is also possible to have an in-band 71 management network on top of the original MPLS topology, or maintain 72 separate routing and MPLS domains for isolated multicast or IPv6 73 islands within the backbone, or force a subset of an address space to 74 follow a different MPLS topology for the purpose of security, QoS or 75 simplified management and/or operations. 77 For a detailed overview of the multi topology, please refer to 78 [I-D.ietf-mpls-ldp-multi-topology]. 80 2. The Internet-Standard Management Framework 82 For a detailed overview of the documents that describe the current 83 Internet-Standard Management Framework, please refer to section 7 of 84 RFC 3410[RFC3410] . Managed objects are accessed via a virtual 85 information store, termed the Management Information Base or MIB. 86 MIB objects are generally accessed through the Simple Network 87 Management Protocol (SNMP). Objects in the MIB are defined using the 88 mechanisms defined in the Structure of Management Information (SMI). 89 This memo specifies a MIB module that is compliant to the SMIv2, 90 which is described in STD 58, RFC 2578[RFC2578], STD 58, RFC 91 2579[RFC2579] and STD 58, RFC 2580[RFC2580]. 93 3. Overview of MT-MPLS-STD-MIB objects 95 The following subsections describe the purpose of each of the objects 96 contained in the MT-MPLS-STD-MIB. 98 3.1. MPLS LDP MT Entity Table 100 The mplsLdpEntityTable specificed in [RFC3815] is used to configure 101 information which is used by the LDP protocol to setup potential LDP 102 Sessions. The mplsLdpMtEntityTable can be considered as an extention 103 to mplsLdpEntityTable to setup potential LDP MT Sessions. 105 Each entry/row in this table represents a single LDP MT Entity. 106 There is no maximum number of LDP MT Entities specified. However, 107 there is an mplsLdpMtEntityIndexNext object which should be retrieved 108 by the command generator prior to creating an LDP MT Entity. If the 109 mplsLdpMtEntityIndexNext object is zero, this indicates that the LSR/ 110 LER is not able to create another LDP MT Entity at that time. 112 3.2. MPLS LDP MT Session Table 114 Since all the MT related label messages can be advertised by LDP 115 Sessions in default topology, there is no need to create extra tcp 116 connection for Multi Topology. 118 The mplsLdpMtSessionTable is a read-only table. Each entry in this 119 table represents an MT Session which is related to one or more LDP MT 120 Entities and only one LDP Session in default topology. 122 3.3. MPLS LDP MT LSP Table 124 The Label Information Base (LIB) contains information about labels 125 learned by the LSR. The LIB for LDP and MPLS-RSVP (i.e., all 126 currently defined MPLS protocols) is represented in the LSR MIB 127 [RFC3813]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 128 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 129 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 130 models the cross-connection of the incoming label with a specific 131 outgoing label. 133 In Multi Topology network, the MT-ID is used during LDP advertisement 134 to identify an LSP in specified topology. 136 3.4. MT statistics Table 138 MTStatisticsTable is a read-only table which contains statistical 139 information related to packet passing through the LSP under the 140 topology. The statistical information includes packets total counts, 141 delay, jitter and so on. 143 3.5 MPLS LDP MT Notifications 145 The mplsLdpMtSessionUp and mplsLdpMtSessionDown notifications are 146 generated when there is an appropriate change in the 147 mplsLdpMtSessionState object, e.g., when sessions change state (Up to 148 Down for the mplsLdpMtSessionDown notification, or Down to Up for the 149 mplsLdpMtSessionUp notification). 151 4. MPLS-LDP-MT-STD-MIB Module Definitions 152 MPLS-LDP-MT-STD-MIB DEFINITIONS ::= BEGIN 154 IMPORTS 155 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 156 Counter32, Unsigned32 157 FROM SNMPv2-SMI -- [RFC2578] 159 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 160 FROM SNMPv2-CONF -- [RFC2580] 162 RowStatus, TimeStamp, StorageType 163 FROM SNMPv2-TC -- [RFC2579] 165 InetAddressPrefixLength, 166 InetAddress 167 FROM INET-ADDRESS-MIB -- [RFC4001] 169 IndexInteger, 170 IndexIntegerNextFree 171 FROM DIFFSERV-MIB -- [RFC3289] 173 MplsLdpIdentifier, 174 FROM MPLS-TC-STD-MIB -- [RFC3811] 176 MplsLdpMtStdMIB MODULE-IDENTITY 177 LAST-UPDATED "20120228" -- Feb 28, 2012 178 CONTACT-INFO 179 "To be added" 180 DESCRIPTION 181 "This MIB contains managed object definitions for the 'Multiprotocol 182 Label Switching, Label Distribution Protocol, Multi Topology' 183 document." 184 ::= { mplsStdMIB 9 } 186 --**************************************************************** 188 mplsLdpMtNotifications OBJECT IDENTIFIER ::= { MplsLdpMtStdMIB 0 } 189 mplsLdpMtObjects OBJECT IDENTIFIER ::= { MplsLdpMtStdMIB 1 } 190 --**************************************************************** 191 -- MPLS LDP Objects 192 --**************************************************************** 194 mplsLdpMtEntityObjects OBJECT IDENTIFIER ::= { mplsLdpMtObjects 1 } 196 mplsLdpMtSessionObjects OBJECT IDENTIFIER ::= { mplsLdpMtObjects 2 } 197 mplsLdpMtLspObjects OBJECT IDENTIFIER ::= { mplsLdpMtObjects 3 } 199 -- 200 -- The MPLS Label Distribution Protocol Multi Topology Entity Objects 201 -- 203 mplsLdpMtEntityLastChange OBJECT-TYPE 204 SYNTAX TimeStamp 205 MAX-ACCESS read-only 206 STATUS current 207 DESCRIPTION 208 "The value of sysUpTime at the time of the most 209 recent addition or deletion of an entry 210 to/from the mplsLdpMtEntityTable, or 211 the most recent change in value of any objects in the 212 mplsLdpMtEntityTable. 214 If no such changes have occurred since the last 215 re-initialization of the local management subsystem, 216 then this object contains a zero value." 217 ::= { mplsLdpMtEntityObjects 1 } 219 mplsLdpMtEntityIndexNext OBJECT-TYPE 220 SYNTAX IndexIntegerNextFree 221 MAX-ACCESS read-only 222 STATUS current 223 DESCRIPTION 224 "This object contains an appropriate value to 225 be used for mplsLdpEntityIndex when creating 226 entries in the mplsLdpEntityTable. The value 227 0 indicates that no unassigned entries are 228 available." 229 ::= { mplsLdpMtEntityObjects 2 } 231 mplsLdpMtEntityTable OBJECT-TYPE 232 SYNTAX SEQUENCE OF mplsLdpMtEntityEntry 233 MAX-ACCESS not-accessible 234 STATUS current 235 DESCRIPTION 236 "This table contains information about the 237 MPLS Label Distribution Protocol Multi Topology 238 Entities which exist on this Label Switching 239 Router (LSR) or Label Edge Router (LER)." 240 ::= { mplsLdpMtEntityObjects 3 } 242 -- MPLS LDP MT Entity Table 244 mplsLdpMtEntityEntry OBJECT-TYPE 245 SYNTAX mplsLdpMtEntityEntry 246 MAX-ACCESS not-accessible 247 STATUS current 248 DESCRIPTION 249 "An entry in this table represents an LDP MT entity. An entry can be 250 created by a network administrator or by an SNMP agent as instructed 251 by LDP." 252 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityIndex } 253 ::= { mplsLdpMtEntityTable 1 } 255 mplsLdpMtEntityEntry ::= SEQUENCE { 256 mplsLdpMtEntityLdpId MplsLdpIdentifier, 257 mplsLdpMtEntityMtId Unsigned32, 258 mplsLdpMtEntityIndex IndexInteger, 259 mplsLdpMtEntityAdminStatus INTEGER, 260 mplsLdpMtEntityStorageType StorageType, 261 mplsLdpMtEntityRowStatus RowStatus 262 } 264 mplsLdpMtEntityLdpId OBJECT-TYPE 265 SYNTAX MplsLdpIdentifier 266 MAX-ACCESS not-accessible 267 STATUS current 268 DESCRIPTION 269 "The LDP identifier." 270 REFERENCE 271 "RFC5036, LDP Specification, Section on LDP Identifiers." 272 ::= { mplsLdpMtEntityEntry 1 } 274 mplsLdpMtEntityMtId OBJECT-TYPE 275 SYNTAX Unsigned32 276 MAX-ACCESS read-create 277 STATUS current 278 DESCRIPTION 279 "The Multi Topology identifier of this LDP MT Entity." 280 DEFVAL { 0 } 281 ::= { mplsLdpMtEntityEntry 2 } 283 mplsLdpMtEntityIndex OBJECT-TYPE 284 SYNTAX IndexInteger 285 MAX-ACCESS not-accessible 286 STATUS current 287 DESCRIPTION 288 "This index is used as a secondary index to uniquely identify this 289 row. Before creating a row in this table, the 290 'mplsLdpMtEntityIndexNext' object should be retrieved. That value 291 should be used for the value of this index when creating a row in 292 this table. NOTE: if a value of zero (0) is retrieved, that 293 indicates that no rows can be created in this table at this time." 294 ::= { mplsLdpMtEntityEntry 3 } 296 mplsLdpMtEntityAdminStatus OBJECT-TYPE 297 SYNTAX INTEGER { 298 enable(1), 299 disable(2) 300 } 301 MAX-ACCESS read-create 302 STATUS current 303 DESCRIPTION 304 "The administrative status of this LDP MT Entity. If this object is 305 changed from 'enable' to 'disable' and this entity has already 306 attempted to establish contact with a MT Session, then all contact 307 with that MT Session is lost and all information from that MT Session 308 needs to be removed from the MIB. (This implies that the network 309 management subsystem should clean up any related entry in the 310 mplsLdpMtSessionTable.). At this point the operator is able to 311 change values which are related to this entity. When the admin 312 status is set back to 'enable', then this MT Entity will attempt to 313 establish a new MT Session." 314 DEFVAL { enable } 315 ::= { mplsLdpMtEntityEntry 4 } 317 mplsLdpMtEntityStorageType OBJECT-TYPE 318 SYNTAX StorageType 319 MAX-ACCESS read-create 320 STATUS current 321 DESCRIPTION 322 "The storage type for this conceptual row. Conceptual rows having 323 the value 'permanent(4)' need not allow write-access to any columnar 324 objects in the row." 325 DEFVAL{ nonVolatile } 326 ::= { mplsLdpMtEntityEntry 5 } 328 mplsLdpMtEntityRowStatus OBJECT-TYPE 329 SYNTAX RowStatus 330 MAX-ACCESS read-create 331 STATUS current 332 DESCRIPTION 334 "The status of this conceptual row. All writable objects in this row 335 may be modified at any time, however, as described in detail in the 336 section entitled, 'Changing Values After Session Establishment', and 337 again described in the DESCRIPTION clause of the 338 mplsLdpMtEntityAdminStatus object, if a session has been initiated 339 with a Peer, changing objects in this table will wreak havoc with the 340 session and interrupt traffic. To repeat again: the recommended 341 procedure is to set the mplsLdpMtEntityAdminStatus to down, thereby 342 explicitly causing a session to be torn down. Then, change objects 343 in this entry, then set the mplsLdpMtEntityAdminStatus to enable, 344 which enables a new session to be initiated." 345 ::= { mplsLdpMtEntityEntry 6 } 347 -- MPLS LDP MT Session Table 349 mplsLdpMtSessionLastChange OBJECT-TYPE 350 SYNTAX TimeStamp 351 MAX-ACCESS read-only 352 STATUS current 353 DESCRIPTION 354 "The value of sysUpTime at the time of the most 355 recent addition or deletion to/from the 356 mplsLdpMtSessionTable." 357 ::= { mplsLdpMtSessionObjects 1 } 359 mplsLdpMtSessionTable OBJECT-TYPE 360 SYNTAX SEQUENCE OF mplsLdpMtSessionEntry 361 MAX-ACCESS not-accessible 362 STATUS current 363 DESCRIPTION 364 "A table of MT Sessions between the LDP MT Entities. Each row in 365 this table represents a single MT session." 366 ::= { mplsLdpMtSessionObjects 2 } 368 mplsLdpMtSessionEntry OBJECT-TYPE 369 SYNTAX mplsLdpMtSessionEntry 370 MAX-ACCESS not-accessible 371 STATUS current 372 DESCRIPTION 373 "An entry in this table represents information on a single MT 374 session. The information contained in a row is read-only." 375 ::= { mplsLdpMtSessionTable 1 } 377 mplsLdpMtSessionEntry ::= SEQUENCE { 378 mplsLdpSessionState INTEGER, 379 mplsLdpMtSessionStateLastChange TimeStamp, 380 mplsLdpMtSessionMtId Unsigned32 381 } 382 mplsLdpMtSessionState OBJECT-TYPE 383 SYNTAX INTEGER { 384 initialized(1), 385 operational(2) 386 } 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "The current state of the MT Session. When the tcp connection in 391 default topology is established, and both ends have the capability of 392 the given MT-ID, the state can change from initialized to 393 operational." 394 ::= { mplsLdpMtSessionEntry 1 } 396 mplsLdpMtSessionStateLastChange OBJECT-TYPE 397 SYNTAX TimeStamp 398 MAX-ACCESS read-only 399 STATUS current 400 DESCRIPTION 401 "The value of sysUpTime at the time this MT Session was created." 402 ::= { mplsLdpMtSessionEntry 2 } 404 mplsLdpMtSessionMtId OBJECT-TYPE 405 SYNTAX Unsigned32 406 MAX-ACCESS read-create 407 STATUS current 408 DESCRIPTION 409 "The Multi Topology identifier of this LDP MT Session." 410 DEFVAL { 0 } 411 ::= { mplsLdpMtSessionEntry 3 } 413 -- MT LDP LSP Table 415 mplsLdpMtLspLastChange OBJECT-TYPE 416 SYNTAX TimeStamp 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "The value of sysUpTime at the time of the most 421 recent addition/deletion of an entry 422 to/from the mplsLdpMtLspTable or 423 the most recent change in values to any objects 424 in the mplsLdpMtLspTable. 426 If no such changes have occurred since the last 427 re-initialization of the local management subsystem, 428 then this object contains a zero value." 430 ::= { mplsLdpMtLspObjects 1 } 432 mplsLdpMtLspNext OBJECT-TYPE 433 SYNTAX IndexIntegerNextFree 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "This object contains an appropriate value to 438 be used for mplsLdpMtLspIndex when creating 439 entries in the mplsLdpMtLspTable. The value 440 0 indicates that no unassigned entries are 441 available." 442 ::= { mplsLdpMtLspObjects 2 } 444 mplsLdpMtLspTable OBJECT-TYPE 445 SYNTAX SEQUENCE OF mplsLdpMtLspEntry 446 MAX-ACCESS not-accessible 447 STATUS current 448 DESCRIPTION 449 "This table specifies MT LIB label switching information. Entries in 450 this table define LIB label switching entries associated with the 451 specified topology." 452 ::= { mplsLdpMtLspObjects 3 } 454 mplsLdpMtLspEntry OBJECT-TYPE 455 SYNTAX mplsLdpMtLspEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "An entry in this table is created by an LSR for every label within 460 the context of a specific topology capable of supporting MT LDP LSP. 461 The indexing provides an ordering of topologies per interface." 462 INDEX { mplsLdpMtLspIndex } 463 ::= { mplsLdpMtLspTable 1 } 465 mplsLdpMtLspEntry ::= SEQUENCE { 466 mplsLdpMtLspIndex IndexInteger, 467 mplsLdpMtLspMtId Unsigned32, 468 mplsLdpMtLspFecAddr InetAddress, 469 mplsLdpMtLspFecAddrLength InetAddressPrefixLength, 470 mplsLdpMtLspStorageType StorageType, 471 mplsLdpMtLspRowStatus RowStatus 472 } 474 mplsLdpMtLspIndex OBJECT-TYPE 475 SYNTAX IndexInteger 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "The index which uniquely identifies this entry." 480 ::= { mplsLdpMtLspEntry 1 } 482 mplsLdpMtLspMtId OBJECT-TYPE 483 SYNTAX Unsigned32 484 MAX-ACCESS read-create 485 STATUS current 486 DESCRIPTION 487 "The Multi Topology identifier of this LDP MT LSP." 488 DEFVAL { 0 } 489 ::= { mplsLdpMtLspEntry 2 } 491 mplsLdpMtLspFecAddr OBJECT-TYPE 492 SYNTAX InetAddress 493 MAX-ACCESS read-create 494 STATUS current 495 DESCRIPTION 496 "The FEC address of this LDP MT LSP. Note that the 497 value of this object is interpreted as prefix address." 498 REFERENCE 499 "RFC5036, Section 3.4.1 FEC TLV." 500 ::= { mplsLdpMtLspEntry 3 } 502 mplsLdpMtLspFecAddrLength OBJECT-TYPE 503 SYNTAX InetAddressPrefixLength 504 MAX-ACCESS read-create 505 STATUS current 506 DESCRIPTION 507 "The FEC prefix length of this LDP MT LSP." 508 REFERENCE 509 "RFC5036, Section 3.4.1. FEC TLV." 510 DEFVAL { 0 } 511 ::= { mplsLdpMtLspEntry 4 } 513 mplsLdpMtLspStorageType OBJECT-TYPE 514 SYNTAX StorageType 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "The storage type for this conceptual row. 519 Conceptual rows having the value 'permanent(4)' 520 need not allow write-access to any columnar 521 objects in the row." 522 DEFVAL { nonVolatile } 523 ::= { mplsLdpMtLspEntry 5 } 525 mplsLdpMtLspRowStatus OBJECT-TYPE 526 SYNTAX RowStatus 527 MAX-ACCESS read-create 528 STATUS current 529 DESCRIPTION 530 "The status of this conceptual row. If the value of this 531 object is 'active(1)', then none of the writable objects 532 of this entry can be modified, except to set this object 533 to 'destroy(6)'. 535 NOTE: if this row is being referenced by any entry in 536 the mplsLdpLspFecTable, then a request to destroy 537 this row, will result in an inconsistentValue error." 538 ::= { mplsLdpMtLspEntry 7 } 540 -- MT LDP LSP Statistics Table 542 mplsLdpMtLspStatTable OBJECT-TYPE 543 SYNTAX SEQUENCE OF mplsLdpMtLspStatEntry 544 MAX-ACCESS not-accessible 545 STATUS current 546 DESCRIPTION 547 "This table contains statistical information related to packet 548 passing through the LSP under the topology." 549 ::= { mplsLdpMtLspObjects 4 } 551 mplsLdpMtLspStatEntry OBJECT-TYPE 552 SYNTAX MTLdpLspStatTableEntry 553 MAX-ACCESS not-accessible 554 STATUS current 555 DESCRIPTION 556 "Each entry in the table contains information of a specific MT LDP 557 LSP. The indexing provides an ordering of LSPes per interface." 558 INDEX { mplsLdpMtLspIndex } 559 ::= { mplsLdpMtLspStatTable 1 } 561 mplsLdpMtLspStatEntry ::= SEQUENCE { 562 mplsLdpMtLspStatStartTime TimeStamp, 563 mplsLdpMtLspStatPackets Counter32 564 } 566 mplsLdpMtLspStatStartTime OBJECT-TYPE 567 SYNTAX TimeStamp 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The value of sysUpTime at the time statistics began." 572 ::= { mplsLdpMtLspStatEntry 1 } 573 mplsLdpMtLspStatPackets Counter32 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "The number of packets which have passed through a specific 578 MT LDP LSP." 579 ::= { mplsLdpMtLspStatEntry 2 } 581 -- Notifications 583 mplsLdpMtSessionUp NOTIFICATION-TYPE 584 OBJECTS { 585 mplsLdpMtSessionState, 586 mplsLdpMtSessionMtId 587 } 588 STATUS current 589 DESCRIPTION 590 "If this notification is sent when the value of 591 'mplsLdpMtSessionState' enters the 'operational(2)' state." 592 ::= { mplsLdpMtNotifications 1 } 594 mplsLdpMtSessionDown NOTIFICATION-TYPE 595 OBJECTS { 596 mplsLdpMtSessionState, 597 mplsLdpMtSessionMtId 598 } 599 STATUS current 600 DESCRIPTION 601 "This notification is sent when the value of 'mplsLdpMtSessionState' 602 leaves the 'operational(2)' state." 603 ::= { mplsLdpNotifications 2 } 605 END 607 5. Security Considerations 609 It needs to be further identified. 611 6. IANA Considerations 613 It is no necessary to request new IANA code in the draft. 615 7. Normative References 617 [RFC3813] C. Srinivasan, Bloomberg L.P., A. Viswanathan,T. Nadeau, 618 "MPLS/BGP Layer 3 Virtual Private Network (VPN) Management 619 Information Base", RFC 3813, June 2004. 621 [RFC3815] J. Cucchiara and H. Sjostrand ,"Definitions of Managed 622 Objects for the Multiprotocol Label Switching (MPLS),Label 623 Distribution Protocol (LDP)",RFC 3815,June 2004. 625 [RFC3814] C. Srinivasan, Bloomberg L.P., A. 626 Viswanathan,"Multiprotocol Label Switching (MPLS) Forwarding 627 Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) 628 Management Information Base (MIB)", RFC 3814, June 2004. 630 [RFC5036] L. Andersson,I. Minei,B. Thomas,"LDP Specification",October 631 2007 633 [RFC3410] J. Case,R. Mundy,D. Partain,B. Stewart,"Introduction and 634 Applicability Statements for Internet Standard Management 635 Framework",December 2002 637 Authors' Addresses 639 Chen Li 640 China Mobile 641 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 642 Beijing 100053 643 P.R. China 645 Email: lichenyj@chinamobile.com 647 Lianyuan Li 648 China Mobile 649 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 650 Beijing 100053 651 P.R. China 653 Email: lilianyuan@chinamobile.com 655 Lu Huang 656 China Mobile 657 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 658 Xunwu District, Beijing 100053 659 China 661 Email: huanglu@chinamobile.com 663 Emily Chen 664 Huawei Technologies 665 2330 Central Expressway 666 Santa Clara, CA 95050 667 US 669 Email: emily.chenying@huawei.com 671 Quintin Zhao 672 Huawei Technologies 673 125 Nagog Technology Park 674 Acton, MA 01719 675 US 677 Email: qzhao@huawei.com