idnits 2.17.1 draft-li-mpls-ldp-mt-mib-00.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (March 6, 2011) is 4800 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 174, but not defined == Missing Reference: 'RFC2579' is mentioned on line 180, but not defined == Missing Reference: 'RFC2580' is mentioned on line 178, but not defined == Missing Reference: 'RFC3289' is mentioned on line 186, but not defined == Missing Reference: 'RFC3811' is mentioned on line 190, but not defined == Unused Reference: 'RFC3814' is defined on line 633, but no explicit reference was found in the text == Unused Reference: 'RFC5036' is defined on line 638, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 Summary: 1 error (**), 0 flaws (~~), 8 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 China Mobile 5 Expires: September 7, 2011 Emily. Chen 6 Quintin. Zhao 7 Huawei Technologies 8 March 6, 2011 10 Management Information Base for MPLS LDP Multi Topology 11 draft-li-mpls-ldp-mt-mib-00 13 Abstract 15 This memo defines an portion of the Management Information Base (MIB) 16 for use with network management protocols in the Internet community. 17 In particular, it describes a MIB module for Multi-Topology Networks 18 over Multi-protocol Label Switching(MPLS) Label Switching 19 Routers(LSRs). 21 Status of this Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at http://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on September 7, 2011. 38 Copyright Notice 40 Copyright (c) 2011 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (http://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. The Internet-Standard Management Framework . . . . . . . . . . 3 57 3. Overview of MT-MPLS-STD-MIB objects . . . . . . . . . . . . . 3 58 4. MPLS-LDP-MT-STD-MIB Module Definitions . . . . . . . . . . . . 5 59 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 60 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 61 7. Normative References . . . . . . . . . . . . . . . . . . . . . 14 62 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15 64 1. Introduction 66 There are increasing requirements to support multi-topology in MPLS 67 network. For example, service providers want to assign different 68 level of service(s) to different topologies so that the service 69 separation can be achieved. It is also possible to have an in-band 70 management network on top of the original MPLS topology, or maintain 71 separate routing and MPLS domains for isolated multicast or IPv6 72 islands within the backbone, or force a subset of an address space to 73 follow a different MPLS topology for the purpose of security, QoS or 74 simplified management and/or operations. 76 For a detailed overview of the multi topology, please refer to 77 draft-zhao-mpls-ldp-multi-topology-01. 79 2. The Internet-Standard Management Framework 81 For a detailed overview of the documents that describe the current 82 Internet-Standard Management Framework, please refer to section 7 of 83 RFC 3410[RFC3410] . Managed objects are accessed via a virtual 84 information store, termed the Management Information Base or MIB. 85 MIB objects are generally accessed through the Simple Network 86 Management Protocol (SNMP). Objects in the MIB are defined using the 87 mechanisms defined in the Structure of Management Information (SMI). 88 This memo specifies a MIB module that is compliant to the SMIv2, 89 which is described in STD 58, RFC 2578[RFC2578], STD 58, RFC 90 2579[RFC2579] and STD 58, RFC 2580[RFC2580] 92 3. Overview of MT-MPLS-STD-MIB objects 94 The following subsections describe the purpose of each of the objects 95 contained in the MT-MPLS-STD-MIB. 97 3.1. MPLS LDP MT Entity Table 99 The mplsLdpEntityTable specificed in [RFC3815] is used to configure 100 information which is used by the LDP protocol to setup potential LDP 101 Sessions. The mplsLdpMtEntityTable can be considered as an extention 102 to mplsLdpEntityTable to setup potential LDP MT Sessions. 104 Each entry/row in this table represents a single LDP MT Entity. 105 There is no maximum number of LDP MT Entities specified. However, 106 there is an mplsLdpMtEntityIndexNext object which should be retrieved 107 by the command generator prior to creating an LDP MT Entity. If the 108 mplsLdpMtEntityIndexNext object is zero, this indicates that the LSR/ 109 LER is not able to create another LDP MT Entity at that time. 111 3.2. MPLS LDP MT Session Table 113 Since all the MT related label messages can be advertised by LDP 114 Sessions in default topology, there is no need to create extra tcp 115 connection for Multi Topology. 117 The mplsLdpMtSessionTable is a read-only table. Each entry in this 118 table represents an MT Session which is related to one or more LDP MT 119 Entities and only one LDP Session in default topology. 121 3.3. MPLS LDP MT LSP Table 123 The Label Information Base (LIB) contains information about labels 124 learned by the LSR. The LIB for LDP and MPLS-RSVP (i.e., all 125 currently defined MPLS protocols) is represented in the LSR MIB 126 [RFC3813]. The LIB is represented by the LSR MIB's mplsXCTable (mpls 127 Cross Connect Table), mplsInSegmentTable (mpls In Segment Table) and 128 the mplsOutSegmentTable (mpls Out Segment Table). The mplsXCTable 129 models the cross-connection of the incoming label with a specific 130 outgoing label. 132 In Multi Topology network, the MT-ID TLV can be inserted into the 133 following LDP messages as an optional parameter during LDP 134 advertisement, including the following message: 136 Label Mapping "Label Mapping Message" 138 Label Request "Label Request Message" 140 Label Abort Request "Label Abort Request Message" 142 Label Withdraw "Label Withdraw Message" 144 Label Release "Label Release Message" 146 The message with inserted MT-ID TLV associates a FEC in same message 147 to the topology identified by MT-ID. 149 3.4. MT statistics Table 151 MTStatisticsTable is a read-only table which contains statistical 152 information related to packet passing through the LSP under the 153 topology. The statistical information includes packets total counts, 154 delay, jitter and so on. 156 3.5 MPLS LDP MT Notifications 158 The mplsLdpMtSessionUp and mplsLdpMtSessionDown notifications are 159 generated when there is an appropriate change in the 160 mplsLdpMtSessionState object, e.g., when sessions change state (Up to 161 Down for the mplsLdpMtSessionDown notification, or Down to Up for the 162 mplsLdpMtSessionUp notification). 164 4. MPLS-LDP-MT-STD-MIB Module Definitions 166 MPLS-LDP-MT-STD-MIB DEFINITIONS ::= BEGIN 168 IMPORTS 170 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 172 Counter32, Unsigned32 174 FROM SNMPv2-SMI -- [RFC2578] 176 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 178 FROM SNMPv2-CONF -- [RFC2580] 180 RowStatus, TimeStamp, StorageType FROM SNMPv2-TC -- [RFC2579] 182 IndexInteger, 184 IndexIntegerNextFree 186 FROM DIFFSERV-MIB -- [RFC3289] 188 MplsLdpIdentifier, 190 FROM MPLS-TC-STD-MIB -- [RFC3811] 192 mplsLdpStdMIB MODULE-IDENTITY 194 LAST-UPDATED "20110304" -- March 4, 2011 196 CONTACT-INFO 198 "To be added 200 Emily Chen (chenying220@huawei.com) Huawei Technologies Co., Ltd." 202 DESCRIPTION 204 "This MIB contains managed object definitions for the 'Multiprotocol 205 Label Switching, Label Distribution Protocol, Multi Topology' 206 document." 208 ::= { mplsLdpMtStdMIB 1 } 210 -- MPLS LDP MT Entity Table 212 mplsLdpMtEntityTable OBJECT-TYPE 214 SYNTAX SEQUENCE OF mplsLdpMtEntityEntry 216 MAX-ACCESS not-accessible 218 STATUS current 220 DESCRIPTION 222 "This table contains information about the MPLS Label Distribution 223 Protocol Entities which exist on this Label Switching Router (LSR) or 224 Label Edge Router (LER)." 226 ::= { mplsLdpMtEntityObjects 3 } 228 mplsLdpMtEntityEntry OBJECT-TYPE 230 SYNTAX mplsLdpMtEntityEntry 232 MAX-ACCESS not-accessible 234 STATUS current 236 DESCRIPTION 238 "An entry in this table represents an LDP MT entity. An entry can be 239 created by a network administrator or by an SNMP agent as instructed 240 by LDP." 242 INDEX { mplsLdpMtEntityLdpId, mplsLdpMtEntityIndex } 244 ::= { mplsLdpMtEntityTable 1 } 246 mplsLdpMtEntityEntry ::= SEQUENCE { 248 mplsLdpMtEntityLdpId MplsLdpIdentifier, 250 mplsLdpMtEntityIndex IndexInteger, 252 mplsLdpMtEntityAdminStatus INTEGER, 253 mplsLdpMtEntityStorageType StorageType, 255 mplsLdpMtEntityRowStatus RowStatus 257 } 259 mplsLdpMtEntityLdpId OBJECT-TYPE 261 SYNTAX MplsLdpIdentifier 263 MAX-ACCESS not-accessible 265 STATUS current 267 DESCRIPTION 269 "The LDP identifier." 271 REFERENCE 273 "RFC3036, LDP Specification, Section on LDP Identifiers." 275 ::= { mplsLdpMtEntityEntry 1 } 277 mplsLdpMtEntityMtId OBJECT-TYPE 279 SYNTAX Unsigned32 281 MAX-ACCESS read-create 283 STATUS current 285 DESCRIPTION 287 "The Multi Topology identifier of this LDP MT Entity." 289 DEFVAL { 0 } 291 ::= { mplsLdpMtEntityEntry 2 } 293 mplsLdpMtEntityIndex OBJECT-TYPE 295 SYNTAX IndexInteger 297 MAX-ACCESS not-accessible 299 STATUS current 300 DESCRIPTION 302 "This index is used as a secondary index to uniquely identify this 303 row. Before creating a row in this table, the 304 'mplsLdpMtEntityIndexNext' object should be retrieved. That value 305 should be used for the value of this index when creating a row in 306 this table. NOTE: if a value of zero (0) is retrieved, that 307 indicates that no rows can be created in this table at this time." 309 ::= { mplsLdpEntityEntry 3 } 311 mplsLdpMtEntityAdminStatus OBJECT-TYPE 313 SYNTAX INTEGER { 315 enable(1), 317 disable(2) 319 } 321 MAX-ACCESS read-create 323 STATUS current 325 DESCRIPTION 327 "The administrative status of this LDP MT Entity. If this object is 328 changed from 'enable' to 'disable' and this entity has already 329 attempted to establish contact with a MT Session, then all contact 330 with that MT Session is lost and all information from that MT Session 331 needs to be removed from the MIB. (This implies that the network 332 management subsystem should clean up any related entry in the 333 mplsLdpMtSessionTable.). At this point the operator is able to 334 change values which are related to this entity. When the admin 335 status is set back to 'enable', then this MT Entity will attempt to 336 establish a new MT Session." 338 DEFVAL { enable } 340 ::= { mplsLdpMtEntityEntry 4 } 342 mplsLdpMtEntityStorageType OBJECT-TYPE 344 SYNTAX StorageType 346 MAX-ACCESS read-create 347 STATUS current 349 DESCRIPTION 351 "The storage type for this conceptual row. Conceptual rows having 352 the value 'permanent(4)' need not allow write-access to any columnar 353 objects in the row." 355 DEFVAL{ nonVolatile } 357 ::= { mplsLdpMtEntityEntry 5 } 359 mplsLdpMtEntityRowStatus OBJECT-TYPE 361 SYNTAX RowStatus 363 MAX-ACCESS read-create 365 STATUS current 367 DESCRIPTION 369 "The status of this conceptual row. All writable objects in this row 370 may be modified at any time, however, as described in detail in the 371 section entitled, 'Changing Values After Session Establishment', and 372 again described in the DESCRIPTION clause of the 373 mplsLdpMtEntityAdminStatus object, if a session has been initiated 374 with a Peer, changing objects in this table will wreak havoc with the 375 session and interrupt traffic. To repeat again: the recommended 376 procedure is to set the mplsLdpMtEntityAdminStatus to down, thereby 377 explicitly causing a session to be torn down. Then, change objects 378 in this entry, then set the mplsLdpMtEntityAdminStatus to enable, 379 which enables a new session to be initiated." 381 ::= { mplsLdpMtEntityEntry 6 } 383 -- MPLS LDP MT Session Table 385 mplsLdpSessionTable OBJECT-TYPE 387 SYNTAX SEQUENCE OF MplsLdpSessionEntry 389 MAX-ACCESS not-accessible 391 STATUS current 393 DESCRIPTION 394 "A table of MT Sessions between the LDP MT Entities. Each row in 395 this table represents a single MT session." 397 ::= { mplsLdpMtSessionObjects 3 } 399 mplsLdpMtSessionEntry OBJECT-TYPE 401 SYNTAX mplsLdpMtSessionEntry 403 MAX-ACCESS not-accessible 405 STATUS current 407 DESCRIPTION 409 "An entry in this table represents information on a single MT 410 session. The information contained in a row is read-only." 412 ::= { mplsLdpSessionTable 1 } 414 mplsLdpMtSessionEntry ::= SEQUENCE { 416 mplsLdpSessionState INTEGER, 418 mplsLdpMtSessionStateLastChange TimeStamp, 420 mplsLdpMtSessionMtId Unsigned32, 422 } 424 mplsLdpSessionState OBJECT-TYPE 426 SYNTAX INTEGER { 428 initialized(1), 430 operational(2) 432 } 434 MAX-ACCESS read-only 436 STATUS current 438 DESCRIPTION 440 "The current state of the MT Session. When the tcp connection in 441 default topology is established, and both ends have the capability of 442 the given MT-ID, the state can change from initialized to 443 operational." 445 ::= { mplsLdpMtSessionEntry 1 } 447 mplsLdpMtSessionStateLastChange OBJECT-TYPE 449 SYNTAX TimeStamp 451 MAX-ACCESS read-only 453 STATUS current 455 DESCRIPTION 457 "The value of sysUpTime at the time this MT Session was created." 459 ::= { mplsLdpMtSessionEntry 2 } 461 mplsLdpMtSessionMtId OBJECT-TYPE 463 SYNTAX Unsigned32 465 MAX-ACCESS read-create 467 STATUS current 469 DESCRIPTION 471 "The Multi Topology identifier of this LDP MT Session." 473 DEFVAL { 0 } 475 ::= { mplsLdpMtSessionEntry 3 } 477 -- MT LDP LSP Table 479 MTLdpLspTable OBJECT-TYPE 481 SYNTAX SEQUENCE OF MTLdpLspTableEntry 483 MAX-ACCESS not-accessible 485 STATUS current 487 DESCRIPTION 489 "This table specifies MT LIB label switching information. Entries in 490 this table define LIB label switching entries associated with the 491 specified topology." 493 ::= { mplsLdpMtStdMIB 1 } 495 MTLdpLspEntry OBJECT-TYPE 497 SYNTAX MTLdpLspEntry 499 MAX-ACCESS not-accessible 501 STATUS current 503 DESCRIPTION 505 "An entry in this table is created by an LSR for every label within 506 the context of a specific topology capable of supporting MT LDP LSP. 507 The indexing provides an ordering of topologies per interface." 509 INDEX { MTLdpLspMtId, 511 MTLdpLspInLabel, 513 MTLdpLspOutLabel, 515 MTLdpLspNHopType, 517 MTLdpLspNHop, 519 } 521 ::= { MTLdpLspTable 1 } 523 MTLdpLspEntry ::= SEQUENCE { 525 MTLdpLspInLabel MplsLabel, 527 MTLdpLspOutLabel MplsLabel, 529 MTLdpLspNHop InterfaceIndexorZero, 531 } 533 MTLdpLspInLabel OBJECT-TYPE 535 SYNTAX MplsLabel 537 MAX-ACCESS not-accessible 538 STATUS current 540 DESCRIPTION 542 "The incoming label of the packet, The label should include the MT-ID 543 TLV of the previous LSR" 545 ::= { MTLdpLspLabelEntry 1 } 547 DESCRIPTION 549 "The out label point to next P router, which will replace the 550 incoming label. the label should carry the MT-ID TLV of the current 551 LSR. The value of the MT-ID TLV should set non-zero if current LSR 552 supports Multi topology." 554 ::= { MTLdpLspLabelEntry 2 } 556 MTLdpLspNHop OBJECT-TYPE 558 SYNTAX InterfaceIndexOrZero 560 MAX-ACCESS read-create 562 STATUS current 564 DESCRIPTION 566 "The ifIndex value that identifies the local interface through which 567 the next hop of the packet should be forwarded. A value of 0 is 568 valid and represents the scenario where no interface is specified." 570 ::= { MTLdpLspLabelEntry 3 } 572 -- Notifications 574 mplsLdpMtSessionUp NOTIFICATION-TYPE 576 OBJECTS { 578 mplsLdpMtSessionState, 580 mplsLdpMtSessionMtId, 582 mplsLdpMtSessionDiscontinuityTime 584 } 585 STATUS current 587 DESCRIPTION 589 "If this notification is sent when the value of 590 'mplsLdpMtSessionState' enters the 'operational(2)' state." 592 ::= { mplsLdpMtNotifications 1 } 594 mplsLdpMtSessionDown NOTIFICATION-TYPE 596 OBJECTS { 598 mplsLdpMtSessionState, 600 mplsLdpMtSessionMtId, 602 mplsLdpMtSessionDiscontinuityTime 604 } 606 STATUS current 608 DESCRIPTION 610 "This notification is sent when the value of 'mplsLdpMtSessionState' 611 leaves the 'operational(2)' state." 613 ::= { mplsLdpNotifications 2 } 615 5. Security Considerations 617 It needs to be further identified. 619 6. IANA Considerations 621 It is no necessary to request new IANA code in the draft. 623 7. Normative References 625 [RFC3813] C. Srinivasan, Bloomberg L.P., A. Viswanathan,T. Nadeau, 626 "MPLS/BGP Layer 3 Virtual Private Network (VPN) Management 627 Information Base", RFC 3813, June 2004. 629 [RFC3815] J. Cucchiara and H. Sjostrand ,"Definitions of Managed 630 Objects for the Multiprotocol Label Switching (MPLS),Label 631 Distribution Protocol (LDP)",RFC 3815,June 2004. 633 [RFC3814] C. Srinivasan, Bloomberg L.P., A. 634 Viswanathan,"Multiprotocol Label Switching (MPLS) Forwarding 635 Equivalence Class To Next Hop Label Forwarding Entry (FEC-To-NHLFE) 636 Management Information Base (MIB)", RFC 3814, June 2004. 638 [RFC5036] L. Andersson,I. Minei,B. Thomas,"LDP Specification",October 639 2007 641 [RFC3410] J. Case,R. Mundy,D. Partain,B. Stewart,"Introduction and 642 Applicability Statements for Internet Standard Management 643 Framework",December 2002 645 Authors' Addresses 647 Chen Li 648 China Mobile 649 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 650 Beijing 100053 651 P.R. China 653 Email: lichenyj@chinamobile.com 655 Lianyuan Li 656 China Mobile 657 Unit2, Dacheng Plaza, No. 28 Xuanwumenxi Ave, Xuanwu District 658 Beijing 100053 659 P.R. China 661 Email: lilianyuan@chinamobile.com 663 Emily Chen 664 Huawei Technologies 665 No. 5 Street, Shangdi Information, Haidian 666 Beijing 100053 667 P.R. China 669 Email: chenying220@huawei.com 670 Quintin Zhao 671 Huawei Technologies 672 125 Nagog Technology Park 673 Acton, MA 01719 674 US 676 Email: qzhao@huawei.com