idnits 2.17.1 draft-sun-ccamp-gmpls-perf-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 : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The abstract seems to contain references ([I-D.ietf-ccamp-dpm], [RFC5814]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 252 has weird spacing: '...tion is initi...' == The document seems to contain a disclaimer for pre-RFC5378 work, but was first submitted on or after 10 November 2008. The disclaimer is usually necessary only for documents that revise or obsolete older RFCs, and that take significant amounts of text from those RFCs. If you can contact all authors of the source material and they are willing to grant the BCP78 rights to the IETF Trust, you can and should remove the disclaimer. Otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (July 2, 2011) is 4675 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) ** Downref: Normative reference to an Informational RFC: RFC 3410 == Outdated reference: A later version (-08) exists of draft-ietf-ccamp-dpm-03 Summary: 4 errors (**), 0 flaws (~~), 4 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group W. Sun 3 Internet-Draft SJTU 4 Intended status: Standards Track T. Nadeau 5 Expires: January 3, 2012 Lucidvision 6 M. Morrow 7 Cisco Systems 8 G. Zhang 9 CATR 10 W. Hu 11 SJTU 12 July 2, 2011 14 Label Switched Path (LSP) Provisioning Performance Management 15 Information Base for Generalized MPLS (GMPLS) / MPLS-TE networks 16 draft-sun-ccamp-gmpls-perf-mib-00.txt 18 Abstract 20 This memo defines Management Information Bases (MIBs) for 21 performances of provisioning Label Switched Paths (LSPs) in 22 Generalized MPLS or MPLS-TE networks. 24 When Generalized MPLS/MPLS-TE is used to provision LSPs, it is useful 25 to record the performance of the provisioning process, such as the 26 delay in creating and deleting the LSPs. The managed information may 27 be retrieved by the Management System and visualized on the GUI, so 28 that the performance of dynamic provisioning may be monitored in a 29 timely manner. 31 This work is a continuation of the work in [RFC5814] and 32 [I-D.ietf-ccamp-dpm], where the provisioning performance values are 33 obtained through active measurements. 35 Status of this Memo 37 This Internet-Draft is submitted in full conformance with the 38 provisions of BCP 78 and BCP 79. 40 Internet-Drafts are working documents of the Internet Engineering 41 Task Force (IETF). Note that other groups may also distribute 42 working documents as Internet-Drafts. The list of current Internet- 43 Drafts is at http://datatracker.ietf.org/drafts/current/. 45 Internet-Drafts are draft documents valid for a maximum of six months 46 and may be updated, replaced, or obsoleted by other documents at any 47 time. It is inappropriate to use Internet-Drafts as reference 48 material or to cite them other than as "work in progress." 49 This Internet-Draft will expire on January 3, 2012. 51 Copyright Notice 53 Copyright (c) 2011 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 This document may contain material from IETF Documents or IETF 67 Contributions published or made publicly available before November 68 10, 2008. The person(s) controlling the copyright in some of this 69 material may not have granted the IETF Trust the right to allow 70 modifications of such material outside the IETF Standards Process. 71 Without obtaining an adequate license from the person(s) controlling 72 the copyright in such materials, this document may not be modified 73 outside the IETF Standards Process, and derivative works of it may 74 not be created outside the IETF Standards Process, except to format 75 it for publication as an RFC or to translate it into languages other 76 than English. 78 Table of Contents 80 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 82 2. Conventions Used in This Document . . . . . . . . . . . . . . 5 84 3. The Internet-Standard Management Framework . . . . . . . . . . 6 86 4. Brief Description of LSP performance MIB Objects . . . . . . . 7 87 4.1. gmplsPerfMaxEntries . . . . . . . . . . . . . . . . . . . 7 88 4.2. gmplsPerfTunnelConfigured . . . . . . . . . . . . . . . . 7 89 4.3. gmplsPerfTable . . . . . . . . . . . . . . . . . . . . . . 7 91 5. GMPLS Performance MIB Module . . . . . . . . . . . . . . . . . 8 93 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 94 6.1. Normative References . . . . . . . . . . . . . . . . . . . 15 95 6.2. Informative References . . . . . . . . . . . . . . . . . . 15 97 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 99 1. Introduction 101 When Label Switched Paths (LSPs) are provisioned dynamically within 102 an operational network, it is helpful to monitor and record the 103 related performance information, such as the experienced provisioning 104 delay and error events. Such information may help operators to 105 ensure correct operation of dynamic LSP provisioning in their 106 network, or possibly identify performance degradation in the control 107 plane. 109 This memo defines a set of objects that can reveal the performance of 110 an operational network in terms of dynamic LSP provisioning. It is 111 intended to complement the performance objects, such as the number of 112 packets received and sent, per LSP tunnel, in [RFC3812] and 113 [RFC4802]. 115 Unlike the work in [RFC5814] and [I-D.ietf-ccamp-dpm], where the 116 performance values are obtained through active measurements, this 117 document focuses on the performance values in operational 118 environments. The actual value of the performance in this document 119 is recorded only when an LSP is provisioned, and is thus collected 120 passively. Hence such information reflects only the performance at 121 specific and discrete times. However, when properly used, they can 122 be helpful in identifying performance degradation, or even 123 malfunctioning, in the network control plane. 125 2. Conventions Used in This Document 127 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 128 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 129 document are to be interpreted as described in [RFC2119]. 131 3. The Internet-Standard Management Framework 133 For a detailed overview of the documents that describe the current 134 Internet-Standard Management Framework, please refer to section 7 of 135 [RFC3410]. 137 Managed objects are accessed via a virtual information store, termed 138 the Management Information Base or MIB. MIB objects are generally 139 accessed through the Simple Network Management Protocol (SNMP). 140 Objects in the MIB are defined using the mechanisms defined in the 141 Structure of Management Information (SMI). This memo specifies a MIB 142 module that is compliant to the SMIv2, which is described in STD 58, 143 RFC 2578[RFC2578], STD 58, RFC 2579[RFC2579] and STD 58, RFC 144 2580[RFC2580]. 146 4. Brief Description of LSP performance MIB Objects 148 4.1. gmplsPerfMaxEntries 150 Defines the maximum number of rows stored in the gmplsPerfTable. An 151 implementation MUST start assigning gmplsPerfEntryIndex values at 1 152 and wrap after exceeding the maximum possible value, as defined by 153 the limit of this object. 155 4.2. gmplsPerfTunnelConfigured 157 Defines the The total number of tunnels configured. 159 4.3. gmplsPerfTable 161 The performance of past LSP provisioning process is stored in this 162 table. To handle possible provisioning failures, start and complete 163 timestamp of a provisioning operation is recorded. For example, for 164 LSP creation process, the timestamps of creation initiation and 165 completion are recorded seperatly. It is up to the users to 166 determine the actual performance value, or identify a possible 167 creation/deletion failure. The maximum number of entries stored in 168 this table is determined by the value of gmplsPerfMaxEntries. 170 5. GMPLS Performance MIB Module 172 GMPLS-PROV-PERF-STD-MIB DEFINITIONS ::= BEGIN 174 IMPORTS 175 gmplsTeStdMIB 176 FROM GMPLS-TE-STD-MIB 177 mplsStdMIB, 178 MplsTunnelIndex, 179 MplsExtendedTunnelId 180 FROM MPLS-TC-STD-MIB -- RFC 3811 181 TimeStamp 182 FROM SNMPv2-TC 183 MODULE-IDENTITY, OBJECT-TYPE, 184 Gauge32, Unsigned32 185 FROM SNMPv2-SMI 186 OBJECT-GROUP 187 FROM SNMPv2-CONF; 189 gmplsPerfMIB MODULE-IDENTITY 190 LAST-UPDATED "201104180654Z" -- Apr 18, 2011 6:54:00 AM 191 ORGANIZATION "IETF Common Control and Measurement Plane Working 192 Group" 193 CONTACT-INFO 194 "Weiqiang Sun 195 Shanghai Jiao Tong University (SJTU) 196 Email: sunwq@mit.edu 198 Thomas D. Nadeau 199 Email: thomas.nadeau@huawei.com" 200 DESCRIPTION 201 "Copyright (C) The Internet Society (2011). This version of 202 this MIB module is part of RFC XXX; see the RFC itself for 203 full legal notices. 205 This MIB module defines managed object definitions 206 for dynamic LSP provisioning." 207 REVISION "201104180654Z" -- Apr 18, 2011 6:54:00 AM 208 DESCRIPTION 209 "Initial version." 210 -- 1.3.6.1.2.1.10.166.13.1 211 ::= { gmplsTeStdMIB 1 } 213 gmplsPerfTunnelConfigured OBJECT-TYPE 214 SYNTAX Unsigned32 215 MAX-ACCESS read-only 216 STATUS current 217 DESCRIPTION 218 "The total number of tunnels configured." 219 -- 1.3.6.1.2.1.10.166.13.1.3 220 ::= { gmplsPerfMIB 3 } 222 gmplsPerfMaxEntries OBJECT-TYPE 223 SYNTAX Gauge32 224 MAX-ACCESS read-only 225 STATUS current 226 DESCRIPTION 227 "An implementation MUST start assigning gmplsPerfEntryIndex 228 values at 1 and wrap after exceeding the maximum possible 229 value, as defined by the limit of this object. 231 A value of 0 for this object disables creation of 232 gmplsPerfEntry." 233 -- 1.3.6.1.2.1.10.166.13.1.2 234 ::= { gmplsPerfMIB 2 } 236 --Performance Table 238 gmplsPerfTable OBJECT-TYPE 239 SYNTAX SEQUENCE OF GmplsPerfEntry 240 MAX-ACCESS not-accessible 241 STATUS current 242 DESCRIPTION 243 "Defines a table for storing the results of LSP 244 provisioning operations. It allows the provisioning 245 performance be retrieved later for monitoring or 246 diagnostic purposes. The recorded performance information 247 is intended to complement the existing performance 248 statistics in the MPLS-TE-STD-MIB and GMPLS-TE-STD-MIB. 250 Note that the creation and tear-down operation performances 251 are stored in one table, ie., gmplsPerfTable. When an LSP 252 tunnel creation operation is initiated, an entry MUST be 253 added in this table and Tunnel ID as well as the time of 254 initiation MUST be recorded. Upon completion of the creation 255 process, ie., a positive signaling feedback is received by 256 the ingress LSR, this complete time object in this entry 257 MUST be updated. 259 When an LSP tunnel deletion process is initiated, the 260 corresponding entry with the same tunnel ID MUST be located 261 and updated with time of the deletion initiation time. When 262 the deletion operation is complete, the entry MUST again 263 be updated with the completion time. 265 Under circumstances that the creation or deletion operation 266 may fail, an entry may be partially updated. Eg., when a 267 creation operation timeouts without a positive signaling 268 feedback, the creation completion time may never be updated. 269 When a tear-down operation is caused by nodes other than the 270 Ingress LSR, the tear-down start time may not be known to 271 the ingress LSR. In such cases, the user of the MIB MUST be 272 aware of such events and treat the performance information 273 accordingly. 275 The number of entries in this table is limited by the value 276 of the corresponding gmplsPerfMaxEntries object. An 277 implementation MUST start assigning gmplsPerfEntryIndex at 278 1 and wrap after exceeding the maximum possible value, as 279 defined by the limit of gmplsPerfMaxEntries. An 280 implementation of this MIB will remove the oldest entry 281 in the gmplsPerfTable to allow the addition of a new entry 282 once the number of rows in the gmplsPerfTable reaches the 283 value specified by gmplsPerfMaxEntries." 284 -- 1.3.6.1.2.1.10.166.13.1.1 285 ::= { gmplsPerfMIB 1 } 287 gmplsPerfEntry OBJECT-TYPE 288 SYNTAX GmplsPerfEntry 289 MAX-ACCESS not-accessible 290 STATUS current 291 DESCRIPTION 292 "Defines an entry in the gmplsPerfTable. An entry can be 293 created when an LSP tunnel is signaled. An implementation 294 of this MIB MAY choose to disable the creation of 295 performance entry, when an LSP is provisioned through 296 SNMP." 297 INDEX { 298 gmplsPerfEntryIndex, 299 gmplsPerfTunnelID } 300 -- 1.3.6.1.2.1.10.166.13.1.1.1 301 ::= { gmplsPerfTable 1 } 303 GmplsPerfEntry ::= SEQUENCE { 305 gmplsPerfEntryIndex Gauge32, 306 gmplsPerfTunnelID MplsTunnelIndex, 307 gmplsPerfCurrentStatus INTEGER, 308 gmplsPerfSrcID MplsExtendedTunnelId, 309 gmplsPerfDstID MplsExtendedTunnelId, 310 gmplsPerfCreateStartTime TimeStamp, 311 gmplsPerfCreateCompleteTime TimeStamp, 312 gmplsPerfDeleteStartTime TimeStamp, 313 gmplsPerfDeleteCompleteTime TimeStamp } 315 gmplsPerfEntryIndex OBJECT-TYPE 316 SYNTAX Gauge32 317 MAX-ACCESS not-accessible 318 STATUS current 319 DESCRIPTION 320 "The index of the performance entry. The number of entries 321 in this table is limited by the value of the corresponding 322 gmplsPerfMaxEntries object. An implementation MUST start 323 assigning gmplsPerfEntryIndex at 1 and wrap after exceeding 324 the maximum possible value, as defined by the limit of 325 gmplsPerfMaxEntries. An implementation of this MIB will 326 remove the oldest entry in the gmplsPerfTable to allow the 327 addition of an new entry once the number of rows in the 328 gmplsPerfTable reaches the value specified by 329 gmplsPerfMaxEntries." 330 -- 1.3.6.1.2.1.10.166.13.1.1.1.1 331 ::= { gmplsPerfEntry 1 } 333 gmplsPerfTunnelID OBJECT-TYPE 334 SYNTAX MplsTunnelIndex 335 MAX-ACCESS read-create 336 STATUS current 337 DESCRIPTION 338 "The ID of the tunnel being provisioned." 339 REFERENCE 340 "RFC 3812" 341 -- 1.3.6.1.2.1.10.166.13.1.1.1.2 342 ::= { gmplsPerfEntry 2 } 344 gmplsPerfCurrentStatus OBJECT-TYPE 345 SYNTAX INTEGER { 346 CreationInProgress(0), 347 Up(1), 348 DeletionInProgress(2), 349 Deleted(3) } 350 MAX-ACCESS read-create 351 STATUS current 352 DESCRIPTION 353 "This object defines the current status of the LSP tunnel. 355 CreationInProgress 356 The corresponding LSP tunnel is being created, but 357 the creation operation has not finished yet. 359 Up 360 The corresponding LSP tunnel has been created 361 successfully. 363 DeletionInProgress 364 The corresponding LSP tunnel is being deleted, but 365 the deletion process has not finished yet. 367 Deleted 368 The corresponding LSP tunnel has been deleted." 369 -- 1.3.6.1.2.1.10.166.13.1.1.1.3 370 ::= { gmplsPerfEntry 3 } 372 gmplsPerfSrcID OBJECT-TYPE 373 SYNTAX MplsExtendedTunnelId 374 MAX-ACCESS read-create 375 STATUS current 376 DESCRIPTION 377 "The address of the ingress LSR ID." 378 -- 1.3.6.1.2.1.10.166.13.1.1.1.5 379 ::= { gmplsPerfEntry 5 } 381 gmplsPerfDstID OBJECT-TYPE 382 SYNTAX MplsExtendedTunnelId 383 MAX-ACCESS read-create 384 STATUS current 385 DESCRIPTION 386 "The address of the egress LSR ID." 387 -- 1.3.6.1.2.1.10.166.13.1.1.1.6 388 ::= { gmplsPerfEntry 6 } 390 gmplsPerfCreateStartTime OBJECT-TYPE 391 SYNTAX TimeStamp 392 MAX-ACCESS read-create 393 STATUS current 394 DESCRIPTION 395 "The time when the tunnel setup operation is 396 initiated." 397 -- 1.3.6.1.2.1.10.166.13.1.1.1.7 398 ::= { gmplsPerfEntry 7 } 400 gmplsPerfCreateCompleteTime OBJECT-TYPE 401 SYNTAX TimeStamp 402 MAX-ACCESS read-create 403 STATUS current 404 DESCRIPTION 405 "The time when the LSP tunnel create operation 406 is complete." 407 -- 1.3.6.1.2.1.10.166.13.1.1.1.8 408 ::= { gmplsPerfEntry 8 } 410 gmplsPerfDeleteStartTime OBJECT-TYPE 411 SYNTAX TimeStamp 412 MAX-ACCESS read-create 413 STATUS current 414 DESCRIPTION 415 "The time when the LSP Tunnel tear-down operation 416 is initiated." 417 -- 1.3.6.1.2.1.10.166.13.1.1.1.9 418 ::= { gmplsPerfEntry 9 } 420 gmplsPerfDeleteCompleteTime OBJECT-TYPE 421 SYNTAX TimeStamp 422 MAX-ACCESS read-create 423 STATUS current 424 DESCRIPTION 425 "The time when an LSP tear-down operation 426 is complete." 427 -- 1.3.6.1.2.1.10.166.13.1.1.1.10 428 ::= { gmplsPerfEntry 10 } 430 gmplsPerfGroups OBJECT IDENTIFIER 431 -- 1.3.6.1.2.1.10.166.13.1.4 432 ::= { gmplsPerfMIB 4 } 434 gmplsDeletionGroup OBJECT-GROUP 435 OBJECTS { 436 gmplsPerfTunnelID, 437 gmplsPerfCurrentStatus, 438 gmplsPerfSrcID, 439 gmplsPerfDstID, 440 gmplsPerfDeleteStartTime, 441 gmplsPerfDeleteCompleteTime } 442 STATUS current 443 DESCRIPTION 444 "The group of object that constitute the LSP tunnel 445 deletion performance." 446 -- 1.3.6.1.2.1.10.166.13.1.4.1 447 ::= { gmplsPerfGroups 1 } 449 gmplsCreationGroup OBJECT-GROUP 450 OBJECTS { 451 gmplsPerfTunnelID, 452 gmplsPerfCurrentStatus, 453 gmplsPerfSrcID, 454 gmplsPerfDstID, 455 gmplsPerfCreateStartTime, 456 gmplsPerfCreateCompleteTime } 457 STATUS current 458 DESCRIPTION 459 "The group of object that constitute the LSP tunnel 460 creation performance." 461 -- 1.3.6.1.2.1.10.166.13.1.4.2 462 ::= { gmplsPerfGroups 2 } 464 gmplsPerfBasicGroup OBJECT-GROUP 465 OBJECTS { 466 gmplsPerfEntryIndex, 467 gmplsPerfTunnelID, 468 gmplsPerfMaxEntries, 469 gmplsPerfCurrentStatus, 470 gmplsPerfCreateStartTime, 471 gmplsPerfCreateCompleteTime, 472 gmplsPerfDeleteStartTime, 473 gmplsPerfDeleteCompleteTime, 474 gmplsPerfDstID, 475 gmplsPerfSrcID, 476 gmplsPerfTunnelConfigured, 477 gmplsPerfErrThreshold } 478 STATUS current 479 DESCRIPTION 480 "Basic objects." 481 -- 1.3.6.1.2.1.10.166.13.1.4.3 482 ::= { gmplsPerfGroups 3 } 484 END 486 6. References 488 6.1. Normative References 490 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 491 Requirement Levels", BCP 14, RFC 2119, March 1997. 493 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 494 Schoenwaelder, Ed., "Structure of Management Information 495 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 497 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 498 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 499 STD 58, RFC 2579, April 1999. 501 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 502 "Conformance Statements for SMIv2", STD 58, RFC 2580, 503 April 1999. 505 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 506 "Introduction and Applicability Statements for Internet- 507 Standard Management Framework", RFC 3410, December 2002. 509 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 510 "Multiprotocol Label Switching (MPLS) Traffic Engineering 511 (TE) Management Information Base (MIB)", RFC 3812, 512 June 2004. 514 [RFC4802] Nadeau, T. and A. Farrel, "Generalized Multiprotocol Label 515 Switching (GMPLS) Traffic Engineering Management 516 Information Base", RFC 4802, February 2007. 518 6.2. Informative References 520 [I-D.ietf-ccamp-dpm] 521 Sun, W. and G. Zhang, "Label Switched Path (LSP) Data Path 522 Delay Metrics in Generalized MPLS/ MPLS-TE Networks", 523 draft-ietf-ccamp-dpm-03 (work in progress), May 2011. 525 [RFC5814] Sun, W. and G. Zhang, "Label Switched Path (LSP) Dynamic 526 Provisioning Performance Metrics in Generalized MPLS 527 Networks", RFC 5814, March 2010. 529 Authors' Addresses 531 Weiqiang Sun 532 Shanghai Jiao Tong University 533 800 Dongchuan Road 534 Shanghai 200240 535 China 537 Phone: +86 21 3420 5359 538 Email: sunwq@mit.edu 540 Thomas D. Nadeau 541 Lucidvision 543 Email: tnadeau@lucidvision.com 545 Monique Morrow 546 Cisco Systems 547 Richistrasse 7 548 CH-8304 Zurich-Wallisellen 549 Switzerland 551 Phone: +41 44 878 9412 552 Email: mmorrow@cisco.com 554 Guoying Zhang 555 China Academy of Telecommunication Research,MII. 556 No.52 Hua Yuan Bei Lu,Haidian District 557 Beijing 100083 558 China 560 Phone: +86-1062300106 561 Email: zhangguoying@mail.ritt.com.cn 563 Weisheng Hu 564 Shanghai Jiao Tong University 565 800 Dongchuan Road 566 Shanghai 200240 567 China 569 Phone: +86 21 3420 5419 570 Email: wshu@sjtu.edu.cn