idnits 2.17.00 (12 Aug 2021) /tmp/idnits17135/draft-mcast-vpls-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 : ---------------------------------------------------------------------------- ** There are 29 instances of too long lines in the document, the longest one being 35 characters in excess of 72. ** The abstract seems to contain references ([I-D.ietf-l2vpn-vpls-mcast]), 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 == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (March 26, 2012) is 3707 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'VPLS-MCAST' is mentioned on line 136, but not defined == Missing Reference: 'SNMP-CONTEXT-MAP-MIB' is mentioned on line 150, but not defined == Missing Reference: 'L2VPN' is mentioned on line 298, but not defined == Missing Reference: 'TODO' is mentioned on line 1064, but not defined == Unused Reference: 'RFC2629' is defined on line 1070, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 1073, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 1077, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 1082, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-l2vpn-vpls-mib' is defined on line 1110, but no explicit reference was found in the text == Unused Reference: 'RFC4761' is defined on line 1124, but no explicit reference was found in the text == Unused Reference: 'RFC4762' is defined on line 1129, but no explicit reference was found in the text == Unused Reference: 'RFC3468' is defined on line 1134, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2629 (Obsoleted by RFC 7749) == Outdated reference: draft-ietf-l2vpn-vpls-mcast has been published as RFC 7117 == Outdated reference: draft-ietf-l2vpn-vpls-mib has been published as RFC 7257 Summary: 3 errors (**), 0 flaws (~~), 16 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 L2 VPN Working Group P. Jain 3 Internet-Draft K. Singh 4 Intended status: BCP R. Boovaraghavan 5 Expires: September 27, 2012 Alcatel-Lucent, Inc. 6 March 26, 2012 8 VPLS with Point-To-Multipoint LSPs Management Information Base 9 draft-mcast-vpls-mib-00 11 Abstract 13 This memo defines an experimental portion of the Management 14 Information Base for use with network management protocols in the 15 Internet community. 17 In particular, it describes managed objects to configure and/or 18 monitor multicast in VPLS using Point-to-Multipoint LSPs or VPLS- 19 MCAST [I-D.ietf-l2vpn-vpls-mcast]. 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 27, 2012. 38 Copyright Notice 40 Copyright (c) 2012 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. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 60 5.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 61 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 62 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 63 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 64 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 65 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 24 66 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 67 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 68 12.1. Normative References . . . . . . . . . . . . . . . . . . . 24 69 12.2. Informative References . . . . . . . . . . . . . . . . . . 25 71 1. Introduction 73 VPLS using Point-to-Multipoint LSPs or [VPLS-MCAST] describes 74 procedures for VPLS multicast that utilize multicast trees in the 75 sevice provider (SP) network. The multicase tree is typically formed 76 using point-to-multipoint LSPs and is used to flood broadcast, 77 multicast, and unknown unicast traffic across a VPLS core network to 78 all the PE routers. 80 This memo describes managed objects to configure and/or monitor 81 multicast in VPLS using Point-to-Multipoint LSPs or VPLS-MCAST 82 [I-D.ietf-l2vpn-vpls-mcast]. 84 In the current version of this memo does not address MIB Objects for 85 Inter-AS VPLS Multicast. Objects related to this would be adressed 86 in subscequent updates of this proposal. 88 2. The Internet-Standard Management Framework 90 For a detailed overview of the documents that describe the current 91 Internet-Standard Management Framework, please refer to section 7 of 92 RFC 3410 [RFC3410]. 94 Managed objects are accessed via a virtual information store, termed 95 the Management Information Base or MIB. MIB objects are generally 96 accessed through the Simple Network Management Protocol (SNMP). 97 Objects in the MIB are defined using the mechanisms defined in the 98 Structure of Management Information (SMI). This memo specifies a MIB 99 module that is compliant to the SMIv2, which is described in STD 58, 100 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 101 [RFC2580]. 103 3. Conventions 105 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 106 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 107 document are to be interpreted as described in RFC 2119 [RFC2119]. 109 4. Terminology 111 Terminology used in this document: 113 VPLS : Virtual Provider LAN Service. 115 P2MP : Point-to-Multipoint. 117 MLDP : Multicast Label Distribution Protocol. 119 SNMP : Simple Network Management Protocol. 121 MIB : Management Information Base. 123 PE Router: Provider Edge Router. 125 P Router : Provider Core Router. 127 I-PMSI : Inclusive-Provider Multicast Service Interface. 129 S-PMSI : Selective-Provider Multicast Service Interface. 131 MVPN : Multicast Virtual Private Networks. 133 5. Structure of the MIB Module 135 The MIB Structure for defining VPLS using Point-to-Multipoint LSPs or 136 [VPLS-MCAST] would be based off the existing VPLS-MIB [I-D.ietf- 137 l2vpn-vpls-mib] defination. 139 Following is the relation of the VPLS-MCAST MIB with existing VPLS- 140 MIB 142 +--------+ +-----------------+ 143 PW Mapping | | | | 144 -----> | PW-MIB |-->|PW-ENET/MPLS-MIB | 145 __________ / | | | | 146 | | / +--------+ +-----------------+ 147 | VPLS MIB | / +------------+ 148 | |----------------------> | | 149 +----------- MAC addr. mapping using | BRIDGE-MIB | 150 | [SNMP-CONTEXT-MAP-MIB] | | 151 | +------------+ 152 | 153 +-----------+ 154 | | 155 | VPLS-MCAST| 156 | MIB | 157 +-----------+ 159 5.1. Summary of MIB Module 161 The configuration and states specific to an VPLS-MCAST include the 162 following: 164 - C-multicast routing exchange protocol BGP 166 - I-PMSI, S-PMSI and corresponding provider tunnels 168 - Mapping of c-multicast states to PMSI/tunnels 170 To represent them, the following tables defined. 172 VplsMcastGeneral ----> VplsPmsiConfig <----- VplsSpmsiConfig 174 VplsIpmsi ----> VplsPmsiTunnelAttribute <----- VplsSpmsi 175 | 176 +-VplsIpmsiBgpADAttribute 177 +-VplsIpmsiBgpVplsAttribute 179 - vplsMcastGeneralTable 181 An entry in this table contains general informaion about VPLS-PMSI 182 created on the device. 184 - vplsPmsiConfigTable 186 An entry in this table is created for each PMSI configured on this 187 router. It can be referred to by base VPLS configuration (in 188 vplsConfigEntry) or S-PMSI configuration (in vplsSpmsiConfigEntry). 190 - vplsIpmsiBgpADTable 192 This table specifies all advertised and received I-PMSI 193 advertisements. An entry is created in this table for each IPMSI 194 attribute advertised/ received in BGP-AD 196 - vplsIpmsiBgpVplsTable 198 An entry is created in this table for each IPMSI attribute 199 advertised/ received in BGP-VPLS 201 - vplsPmsiTunnelAttributeTable 203 This table is specified for advertised/received PMSI attributes to be 204 referred to by I-PMSI or S-PMSI table entries. 206 - vplsSpmsiConfigTable 207 This table specifies S-PMSI configuration for each VPLS entry 209 - vplsSpmsiTable 211 This table contains information about the VPLS S-PMSIs advertised/ 212 received for a given VPLS instance 214 6. Relationship to Other MIB Modules 216 This section provides an overview of the relationship between the 217 VPLS-MCAST MIB module and other VPLS MIB modules. 219 The arrows in the following diagram show a 'depends on' relationship. 220 A relationship "MIB module A depends on MIB module B" means that MIB 221 module A uses an object, object identifier, or textual convention 222 defined in MIB module B, or that MIB module A contains a pointer 223 (index or RowPointer) to an object in MIB module B. 225 VPLS-GENERIC-DRAFT-01-MIB VPLS-BGP-DRAFT-01-MIB 226 | | 227 +--------------------------+ 228 | 229 V 230 VPLS-MCAST-MIB 232 7. Definitions 234 VPLS-MCAST-MIB DEFINITIONS ::= BEGIN 236 IMPORTS 237 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 238 experimental, Unsigned32 239 FROM SNMPv2-SMI 241 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 242 FROM SNMPv2-CONF 244 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 245 FROM SNMPv2-TC 247 SnmpAdminString 248 FROM SNMP-FRAMEWORK-MIB 250 InetAddress, InetAddressType 251 FROM INET-ADDRESS-MIB 253 MplsLabel 254 FROM MPLS-TC-STD-MIB 256 vplsConfigIndex, 257 vplsBgpADConfigRouteDistinguisher, 258 vplsBgpADConfigPrefix, 259 vplsBgpADConfigVplsId 260 FROM VPLS-GENERIC-DRAFT-01-MIB 262 vplsBgpVEName 263 FROM VPLS-BGP-DRAFT-01-MIB; 265 vplsMcastMIB MODULE-IDENTITY 266 LAST-UPDATED "201203141200Z" -- 14 March 2012 12:00:00 GMT 267 ORGANIZATION "IETF Layer-2 Virtual Private 268 Networks Working Group." 269 CONTACT-INFO 271 " 273 Pradeep Jain 274 Alcatel-Lucent, Inc. 275 701 E Middlefield Rd 276 Mountain View, CA 94040 277 USA 278 Email: pradeep.jain@alcatel-lucent.com 280 Kanwar Singh 281 Alcatel-Lucent, Inc. 282 701 E Middlefield Rd 283 Mountain View, CA 94040 284 USA 285 Email: kanwar.singh@alcatel-lucent.com 287 Ranganathan Boovaraghavan 288 Alcatel-Lucent, Inc. 289 701 E Middlefield Rd 290 Mountain View, CA 94040 291 USA 292 Email: ranganathan.boovaraghavan@alcatel-lucent.com 294 " 296 DESCRIPTION 297 "This MIB contains managed object definitions for 298 multicast in Layer 2 VPLS defined by [L2VPN]. 299 Copyright (C) The Internet Society (2012)." 301 -- Revision history. 302 REVISION "201203141200Z" -- 14 March 2012 12:00:00 GMT 303 DESCRIPTION 304 "Initial version of the draft." 305 ::= { experimental 99 } -- number to be assigned 307 -- Top level components of this MIB. 308 -- Traps 309 vplsMcastNotifications OBJECT IDENTIFIER ::= { vplsMcastMIB 0 } 311 -- tables, scalars 312 vplsMcastObjects OBJECT IDENTIFIER ::= { vplsMcastMIB 1 } 314 -- conformance 315 vplsMcastConformance OBJECT IDENTIFIER ::= { vplsMcastMIB 2 } 317 vplsMcastScalars OBJECT IDENTIFIER ::= { vplsMcastObjects 1 } 318 vplsMcastGeneral OBJECT IDENTIFIER ::= { vplsMcastObjects 2 } 319 vplsMcastConfig OBJECT IDENTIFIER ::= { vplsMcastObjects 3 } 320 vplsMcastStates OBJECT IDENTIFIER ::= { vplsMcastObjects 4 } 322 -- Scalar Objects 324 vplsMcastNotificationEnable OBJECT-TYPE 325 SYNTAX TruthValue 326 MAX-ACCESS read-write 327 STATUS current 328 DESCRIPTION 329 "If this object is TRUE, then the generation of all 330 notifications defined in this MIB is enabled." 331 DEFVAL { false } 332 ::= { vplsMcastScalars 1 } 334 vplsMcastGeneralTable OBJECT-TYPE 335 SYNTAX SEQUENCE OF VplsMcastGeneralEntry 336 MAX-ACCESS not-accessible 337 STATUS current 338 DESCRIPTION 339 "This table specifies the general information about the VPLS-PMSI 340 present in this device." 341 ::= { vplsMcastGeneral 1 } 343 vplsMcastGeneralEntry OBJECT-TYPE 344 SYNTAX VplsMcastGeneralEntry 345 MAX-ACCESS not-accessible 346 STATUS current 347 DESCRIPTION 348 "An entry in this table is created for every MVRF in the 349 device." 350 INDEX { vplsConfigIndex } 351 ::= { vplsMcastGeneralTable 1 } 353 VplsMcastGeneralEntry ::= SEQUENCE { 354 vplsMcastGenOperStatusChange INTEGER, 355 vplsMcastGenOperChangeTime TimeStamp, 356 vplsMcastGenIpmsiConfig RowPointer, 357 vplsMcastGenInterasPmsiConfig RowPointer, 358 vplsMcastGenRowStatus RowStatus 359 } 361 vplsMcastGenOperStatusChange OBJECT-TYPE 362 SYNTAX INTEGER { createdVplsPmsi(1), 363 deletedVplsPmsi(2), 364 modifiedVplsIpmsiConfig(3), 365 modifiedVplsSpmsiConfig(4) 366 } 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "This object describes the last operational change that 371 happened for the given VPLS-PMSI. 373 createdVplsPmsi - indicates that VPLS PMSI was created in the 374 device. 376 deletedVplsPmsi - indicates that the VPLS PMSI was deleted from the 377 device. A row in this table will never have 378 vplsMcastGenOperStatusChange equal to deletedVplsPmsi(2), 379 because in that case the row itself will be deleted from the 380 table. This value for vplsMcastGenOperStatusChange is defined 381 mainly for use in vplsMcastPmsiChange notification. 383 modifiedVplsIpmsiConfig - indicates that the I-PMSI 384 for the VPLS was configured, deleted or changed. 386 modifiedVplsSpmsiConfig - indicates that the S-PMSI 387 for the VPLS was configured, deleted or changed." 388 DEFVAL { createdVplsPmsi } 389 ::= { vplsMcastGeneralEntry 1 } 391 vplsMcastGenOperChangeTime OBJECT-TYPE 392 SYNTAX TimeStamp 393 MAX-ACCESS read-only 394 STATUS current 395 DESCRIPTION 396 "The time at which the last operational change for the VPLS-PMSI in 397 question took place. The last operational change is specified 398 by vplsMcastGenOperStatusChange." 399 ::= { vplsMcastGeneralEntry 2 } 401 vplsMcastGenIpmsiConfig OBJECT-TYPE 402 SYNTAX RowPointer 403 MAX-ACCESS read-create 404 STATUS current 405 DESCRIPTION 406 "This points to a row in vplsMcastPmsiConfigTable, 407 for I-PMSI configuration." 408 ::= { vplsMcastGeneralEntry 3 } 410 vplsMcastGenInterasPmsiConfig OBJECT-TYPE 411 SYNTAX RowPointer 412 MAX-ACCESS read-create 413 STATUS current 414 DESCRIPTION 415 "This points to a row in vplsMcastPmsiConfigTable, 416 for inter-as I-PMSI configuration in case of segmented 417 inter-as provider tunnels." 418 ::= { vplsMcastGeneralEntry 4 } 420 vplsMcastGenRowStatus OBJECT-TYPE 421 SYNTAX RowStatus 422 MAX-ACCESS read-create 423 STATUS current 424 DESCRIPTION 425 "This is used to create or delete a row in this table." 426 ::= { vplsMcastGeneralEntry 5 } 428 -- VPLS PMSI Configuration Table 430 vplsPmsiConfigTable OBJECT-TYPE 431 SYNTAX SEQUENCE OF VplsPmsiConfigEntry 432 MAX-ACCESS not-accessible 433 STATUS current 434 DESCRIPTION 435 "An entry in this table is created for each PMSI configured 436 on this router. It can be referred to by base VPLS 437 configuration (in vplsConfigEntry) or S-PMSI configuration 438 (in vplsSpmsiConfigEntry)" 440 ::= { vplsMcastConfig 1 } 442 vplsPmsiConfigEntry OBJECT-TYPE 443 SYNTAX VplsPmsiConfigEntry 444 MAX-ACCESS not-accessible 445 STATUS current 446 DESCRIPTION 447 "An entry in this table is created for each PMSI configured 448 on this router under VPLS Service" 449 INDEX { vplsConfigIndex } 450 ::= { vplsPmsiConfigTable 1 } 452 VplsPmsiConfigEntry ::= SEQUENCE { 453 vplsPmsiCfgTunnelType INTEGER, 454 vplsPmsiCfgTunnelAuxInfo Unsigned32, 455 vplsPmsiCfgTunnelOrTemplateName SnmpAdminString, 456 vplsPmsiCfgEncapsType INTEGER, 457 vplsPmsiCfgSiteType INTEGER, 458 vplsPmsiCfgExcludeUnknownUnicast TruthValue, 459 vplsPmsiCfgRowStatus RowStatus 460 } 462 vplsPmsiCfgTunnelType OBJECT-TYPE 463 SYNTAX INTEGER { rsvpP2mp (1), 464 ldpP2mp (2), 465 ingressReplication (3) 466 } 467 MAX-ACCESS read-write 468 STATUS current 469 DESCRIPTION 470 "Type of tunnel used to instantiate the PMSI." 471 ::= { vplsPmsiConfigEntry 1 } 473 vplsPmsiCfgTunnelAuxInfo OBJECT-TYPE 474 SYNTAX Unsigned32 475 MAX-ACCESS read-write 476 STATUS current 477 DESCRIPTION 478 "Additional tunnel information depending on the type. 479 rsvp-p2mp: 1 for statically specified rsvp-p2mp tunnel 480 2 for dynamically created rsvp-p2mp tunnel 481 ingress-replication: 482 1 for using any existing p2p/mp2p lsp 483 2 for dynamically creating new p2p lsp" 484 ::= { vplsPmsiConfigEntry 2 } 486 vplsPmsiCfgTunnelOrTemplateName OBJECT-TYPE 487 SYNTAX SnmpAdminString 488 MAX-ACCESS read-write 489 STATUS current 490 DESCRIPTION 491 "The tunnel name or template name used to create tunnels. 492 Depending on vplsPmsiCfgTunnelType and 493 vplsPmsiCfgTunnelAuxInfo: 495 dynamically created rsvp-p2mp tunnel: template name 496 statically specified rsvp-p2mp tunnel: tunnel name 497 ingress-replication using 498 dynamically created lsps: template name 499 other: null" 500 ::= { vplsPmsiConfigEntry 3 } 502 vplsPmsiCfgEncapsType OBJECT-TYPE 503 SYNTAX INTEGER { greIp (1), 504 ipIp (2), 505 mpls (3) 506 } 507 MAX-ACCESS read-create 508 STATUS current 509 DESCRIPTION 510 "The encapsulation type to be used, in case of 511 ingress-replication." 512 ::= { vplsPmsiConfigEntry 4 } 514 vplsPmsiCfgSiteType OBJECT-TYPE 515 SYNTAX INTEGER { 516 senderReceiver (1), 517 receiverOnly (2), 518 senderOnly (3) 519 } 520 MAX-ACCESS read-write 521 STATUS current 522 DESCRIPTION 523 "Whether this site is a receiver-only site or not. 524 sender-receiver (1): both sender and receiver site. 525 receiver-only (2): receiver-only site. 526 sender-only (3): sender only site." 527 ::= { vplsPmsiConfigEntry 5 } 529 vplsPmsiCfgExcludeUnknownUnicast OBJECT-TYPE 530 SYNTAX TruthValue 531 MAX-ACCESS read-write 532 STATUS current 533 DESCRIPTION 534 "If this object is TRUE, then Unknown Unicast will not 535 be mapped to the provider tunnel. 536 If this object is FALSE, then Uknown Unicast will be 537 mapped to the provider tunnel." 538 DEFVAL { false } 539 ::= { vplsPmsiConfigEntry 6 } 541 vplsPmsiCfgRowStatus OBJECT-TYPE 542 SYNTAX RowStatus 543 MAX-ACCESS read-create 544 STATUS current 545 DESCRIPTION 546 "Used to create/modify/delete a row in this table." 547 ::= { vplsPmsiConfigEntry 7 } 549 -- Table of IPMSI BGP-AD Advertised/Received. 551 vplsIpmsiBgpADTable OBJECT-TYPE 552 SYNTAX SEQUENCE OF VplsIpmsiBgpADEntry 553 MAX-ACCESS not-accessible 554 STATUS current 555 DESCRIPTION 556 "This table specifies all advertised and received IPmsi advertisements." 557 ::= { vplsMcastStates 1 } 559 vplsIpmsiBgpADEntry OBJECT-TYPE 560 SYNTAX VplsIpmsiBgpADEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "An entry is created in this table for each IPMSI attribute advertised/received in BGP-AD" 565 INDEX { vplsConfigIndex, 566 vplsBgpADConfigRouteDistinguisher, 567 vplsBgpADConfigPrefix, 568 vplsBgpADConfigVplsId } 569 ::= { vplsIpmsiBgpADTable 1 } 571 VplsIpmsiBgpADEntry ::= SEQUENCE { 572 vplsIpmsiBgpADAttribute RowPointer 573 } 575 vplsIpmsiBgpADAttribute OBJECT-TYPE 576 SYNTAX RowPointer 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "Points to a row in the vplsIpmsiTunnelAttributeTable." 581 ::= { vplsIpmsiBgpADEntry 1 } 583 -- Table of IPMSI BGP-VPLS Advertised/Received. 585 vplsIpmsiBgpVplsTable OBJECT-TYPE 586 SYNTAX SEQUENCE OF VplsIpmsiBgpVplsEntry 587 MAX-ACCESS not-accessible 588 STATUS current 589 DESCRIPTION 590 "This table specifies the all advertised and received IPmsi advertisements." 591 ::= { vplsMcastStates 2 } 593 vplsIpmsiBgpVplsEntry OBJECT-TYPE 594 SYNTAX VplsIpmsiBgpVplsEntry 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "An entry is created in this table for each IPMSI attribute advertised/received in BGP-VPLS" 599 INDEX { vplsConfigIndex, 600 vplsBgpVEName} 601 ::= { vplsIpmsiBgpVplsTable 1 } 603 VplsIpmsiBgpVplsEntry ::= SEQUENCE { 604 vplsIpmsiBgpVplsAttribute RowPointer 605 } 607 vplsIpmsiBgpVplsAttribute OBJECT-TYPE 608 SYNTAX RowPointer 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "Points to a row in the vplsIpmsiTunnelAttributeTable." 613 ::= { vplsIpmsiBgpVplsEntry 1 } 615 -- Table of VPLS PMSI attributes 617 vplsPmsiTunnelAttributeTable OBJECT-TYPE 618 SYNTAX SEQUENCE OF VplsPmsiTunnelAttributeEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "This table is for advertised/received PMSI attributes, 623 to be referred to by I-PMSI or S-PMSI table entries" 624 ::= { vplsMcastStates 3 } 626 vplsPmsiTunnelAttributeEntry OBJECT-TYPE 627 SYNTAX VplsPmsiTunnelAttributeEntry 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "An entry in this table corresponds to an PMSI attribute 632 that is advertised/received on this router. 633 For BGP-based signaling (for I-PMSI via auto-discovery 634 procedure, or for S-PMSI via S-PMSI A-D routes), 635 they are just as signaled by BGP." 636 INDEX { 637 vplsPmsiTunnelAttributeType, 638 vplsPmsiTunnelAttributeLabel, 639 vplsPmsiTunnelAttributeFlags, 640 vplsPmsiTunnelAttributeId 641 } 642 ::= { vplsPmsiTunnelAttributeTable 1 } 644 VplsPmsiTunnelAttributeEntry ::= SEQUENCE { 645 vplsPmsiTunnelAttributeType Unsigned32, 646 vplsPmsiTunnelAttributeLabel MplsLabel, 647 vplsPmsiTunnelAttributeFlags OCTET STRING, 648 vplsPmsiTunnelAttributeId OCTET STRING, 649 vplsPmsiTunnelPointer RowPointer, 650 vplsPmsiTunnelIf RowPointer 651 } 653 vplsPmsiTunnelAttributeType OBJECT-TYPE 654 SYNTAX Unsigned32 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "The tunnel type identifies the type of tunneling technology 659 used to establish the PMSI tunnel. This document discusses the 660 following tunnel types: 661 0 - No tunnel information present 662 1 - RSVP-TE P2MP LSP 663 2 - mLDP P2MP LSP 664 " 665 ::= { vplsPmsiTunnelAttributeEntry 1 } 667 vplsPmsiTunnelAttributeLabel OBJECT-TYPE 668 SYNTAX MplsLabel 669 MAX-ACCESS not-accessible 670 STATUS current 671 DESCRIPTION 672 "If the MPLS Label field is non-zero, then it contains an MPLS 673 label encoded as 3 octets, where the high-order 20 bits contain the label 674 value. Absence of MPLS Label is indicated by setting the MPLS Label 675 field to zero." 676 ::= { vplsPmsiTunnelAttributeEntry 2 } 678 vplsPmsiTunnelAttributeFlags OBJECT-TYPE 679 SYNTAX OCTET STRING (SIZE (1)) 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "The Flags field has the following format: 684 0 1 2 3 4 5 6 7 685 +-+-+-+-+-+-+-+-+ 686 | reserved |L| 687 +-+-+-+-+-+-+-+-+ 688 This document defines the following flags: 689 + Leaf Information Required (L)" 690 ::= { vplsPmsiTunnelAttributeEntry 3 } 692 vplsPmsiTunnelAttributeId OBJECT-TYPE 693 SYNTAX OCTET STRING ( SIZE (4|8|12) ) 694 MAX-ACCESS not-accessible 695 STATUS current 696 DESCRIPTION 697 "When the type is set to 'No tunnel information present', the PMSI 698 Tunnel attribute carries no tunnel information (no Tunnel 699 Identifier). This type is to be used only in the following case: to 700 enable explicit tracking for a particular customer multicast flow (by 701 setting the Leaf Information Required flag to 1), but without binding 702 this flow to a particular provider tunnel (by omitting any tunnel 703 information). 705 When the type is set to RSVP-TE P2MP LSP, the Tunnel Identifier is 706 (Extended Tunnel ID, Reserved, Tunnel ID, P2MP ID) as carried in the 707 RSVP-TE P2MP LSP SESSION Object [RFC4875]. 709 When the type is set to mLDP P2MP LSP, the Tunnel Identifier is a 710 P2MP FEC Element [mLDP]." 711 ::= { vplsPmsiTunnelAttributeEntry 4 } 713 vplsPmsiTunnelPointer OBJECT-TYPE 714 SYNTAX RowPointer 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "If the tunnel exists in some MIB table, this is the row pointer 719 to it." 720 ::= { vplsPmsiTunnelAttributeEntry 5 } 722 vplsPmsiTunnelIf OBJECT-TYPE 723 SYNTAX RowPointer 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "If the tunnel has a corresponding interface, this is the 728 row pointer to the ifName table." 729 ::= { vplsPmsiTunnelAttributeEntry 6 } 731 -- S-PMSI configuration table 733 vplsSpmsiConfigTable OBJECT-TYPE 734 SYNTAX SEQUENCE OF VplsSpmsiConfigEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "This table specifies S-PMSI configuration." 739 ::= { vplsMcastConfig 2 } 741 vplsSpmsiConfigEntry OBJECT-TYPE 742 SYNTAX VplsSpmsiConfigEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "An entry is created for each S-PMSI configuration." 747 INDEX { vplsConfigIndex, 748 vplsSpmsiCfgCmcastAddressType, 749 vplsSpmsiCfgCmcastGroupAddress, 750 vplsSpmsiCfgCmcastGroupPrefixLen, 751 vplsSpmsiCfgCmcastSrcAddress, 752 vplsSpmsiCfgCmcastSrcPrefixLen } 753 ::= { vplsSpmsiConfigTable 1 } 755 VplsSpmsiConfigEntry ::= SEQUENCE { 756 vplsSpmsiCfgCmcastAddressType InetAddressType, 757 vplsSpmsiCfgCmcastGroupAddress InetAddress, 758 vplsSpmsiCfgCmcastGroupPrefixLen Unsigned32, 759 vplsSpmsiCfgCmcastSrcAddress InetAddress, 760 vplsSpmsiCfgCmcastSrcPrefixLen Unsigned32, 761 vplsSpmsiCfgThreshold Unsigned32, 762 vplsSpmsiCfgPmsiPointer RowPointer, 763 vplsSpmsiCfgRowStatus RowStatus 764 } 766 vplsSpmsiCfgCmcastAddressType OBJECT-TYPE 767 SYNTAX InetAddressType 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "Type of C-multicast address" 772 ::= { vplsSpmsiConfigEntry 1 } 774 vplsSpmsiCfgCmcastGroupAddress OBJECT-TYPE 775 SYNTAX InetAddress 776 MAX-ACCESS not-accessible 777 STATUS current 778 DESCRIPTION 779 "C-multicast group address" 780 ::= { vplsSpmsiConfigEntry 2 } 782 vplsSpmsiCfgCmcastGroupPrefixLen OBJECT-TYPE 783 SYNTAX Unsigned32 784 MAX-ACCESS not-accessible 785 STATUS current 786 DESCRIPTION 787 "C-multicast group address prefix length. 788 A group 0 (or ::0) with prefix length 32 (or 128) 789 indicates wildcard group, while a group 0 (or ::0) 790 with prefix length 0 indicates any group." 791 ::= { vplsSpmsiConfigEntry 3 } 793 vplsSpmsiCfgCmcastSrcAddress OBJECT-TYPE 794 SYNTAX InetAddress 795 MAX-ACCESS not-accessible 796 STATUS current 797 DESCRIPTION 798 "C-multicast source address" 799 ::= { vplsSpmsiConfigEntry 4 } 801 vplsSpmsiCfgCmcastSrcPrefixLen OBJECT-TYPE 802 SYNTAX Unsigned32 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "C-multicast source address prefix length. 807 A source 0 (or ::0) with prefix length 32 (or 128) 808 indicates a wildcard source, while a source 0 (or ::0) 809 with prefix length 0 indicates any source." 810 ::= { vplsSpmsiConfigEntry 5 } 812 vplsSpmsiCfgThreshold OBJECT-TYPE 813 SYNTAX Unsigned32 (0..4294967295) 814 UNITS "kilobits per second" 815 MAX-ACCESS read-create 816 STATUS current 817 DESCRIPTION 818 "The bandwidth threshold value which when exceeded for a 819 multicast routing entry in the given VPLS, triggers usage 820 of S-PMSI." 821 ::= { vplsSpmsiConfigEntry 6 } 823 vplsSpmsiCfgPmsiPointer OBJECT-TYPE 824 SYNTAX RowPointer 825 MAX-ACCESS read-create 826 STATUS current 827 DESCRIPTION 828 "This points to a row in vplsPmsiConfigTable, 829 to specify tunnel attributes." 830 ::= { vplsSpmsiConfigEntry 7 } 832 vplsSpmsiCfgRowStatus OBJECT-TYPE 833 SYNTAX RowStatus 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "Used to create/modify/delete a row in this table." 838 ::= { vplsSpmsiConfigEntry 8 } 840 -- Table of S-PMSIs advertised/received 842 vplsSpmsiTable OBJECT-TYPE 843 SYNTAX SEQUENCE OF VplsSpmsiEntry 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "This table has information about the S-PMSIs sent/received 848 by a device." 849 ::= { vplsMcastStates 4 } 851 vplsSpmsiEntry OBJECT-TYPE 852 SYNTAX VplsSpmsiEntry 853 MAX-ACCESS not-accessible 854 STATUS current 855 DESCRIPTION 856 "An entry in this table is created or updated for every S-PMSI 857 advertised/received in a particular VPLS." 858 INDEX { vplsConfigIndex, 859 vplsSpmsiCmcastAddrType, 860 vplsSpmsiCmcastGroup, 861 vplsSpmsiCmcastGroupPrefixLen, 862 vplsSpmsiCmcastSource, 863 vplsSpmsiCmcastSourcePrefixLen, 864 vplsSpmsiOrigAddrType, 865 vplsSpmsiOrigAddress} 866 ::= { vplsSpmsiTable 1 } 868 VplsSpmsiEntry ::= SEQUENCE { 869 vplsSpmsiCmcastAddrType InetAddressType, 870 vplsSpmsiCmcastGroup InetAddress, 871 vplsSpmsiCmcastGroupPrefixLen Unsigned32, 872 vplsSpmsiCmcastSource InetAddress, 873 vplsSpmsiCmcastSourcePrefixLen InetAddress, 874 vplsSpmsiOrigAddrType InetAddressType, 875 vplsSpmsiOrigAddress InetAddress, 876 vplsSpmsiTunnelAttribute RowPointer, 877 vplsSpmsiUpTime TimeInterval, 878 vplsSpmsiExpTime TimeInterval, 879 vplsSpmsiRefCnt Unsigned32 880 } 882 vplsSpmsiCmcastAddrType OBJECT-TYPE 883 SYNTAX InetAddressType 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "The Internet address type of vplsSpmsiCmcastGroup/Source." 888 ::= { vplsSpmsiEntry 1 } 890 vplsSpmsiCmcastGroup OBJECT-TYPE 891 SYNTAX InetAddress (SIZE (4|16|20)) 892 MAX-ACCESS not-accessible 893 STATUS current 894 DESCRIPTION 895 "S-PMSI C-multicast group address. 896 If it is 0 (or ::0), this is a wildcard group, 897 and vplsSpmsiCmcastGroupPrefixLen must be 32 (or 128)." 898 ::= { vplsSpmsiEntry 2 } 900 vplsSpmsiCmcastGroupPrefixLen OBJECT-TYPE 901 SYNTAX Unsigned32 902 MAX-ACCESS not-accessible 903 STATUS current 904 DESCRIPTION 905 "S-PMSI C-multicast group address prefix length." 906 ::= { vplsSpmsiEntry 3 } 908 vplsSpmsiCmcastSource OBJECT-TYPE 909 SYNTAX InetAddress (SIZE (4|16|20)) 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "S-PMSI C-multicast source address 914 If it is 0 (or ::0), this is a wildcard source, 915 and vplsSpmsiCmcastSourcePrefixLen must be 32 (or 128)." 916 ::= { vplsSpmsiEntry 4 } 918 vplsSpmsiCmcastSourcePrefixLen OBJECT-TYPE 919 SYNTAX InetAddress (SIZE (4|16|20)) 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "S-PMSI C-multicast source address prefix length." 924 ::= { vplsSpmsiEntry 5 } 926 vplsSpmsiOrigAddrType OBJECT-TYPE 927 SYNTAX InetAddressType 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "The Internet address type of vplsSpmsiOrigAddress." 932 ::= { vplsSpmsiEntry 6 } 934 vplsSpmsiOrigAddress OBJECT-TYPE 935 SYNTAX InetAddress 936 MAX-ACCESS not-accessible 937 STATUS current 938 DESCRIPTION 939 "The BGP address of the device that originated the S-PMSI." 940 ::= { vplsSpmsiEntry 7 } 942 vplsSpmsiTunnelAttribute OBJECT-TYPE 943 SYNTAX RowPointer 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "A row pointer to the vplsPmsiTunnelAttributeTable" 948 ::= { vplsSpmsiEntry 8 } 950 vplsSpmsiUpTime OBJECT-TYPE 951 SYNTAX TimeInterval 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "The time since this S-PMSI 956 was first advertised/received by the device." 957 ::= { vplsSpmsiEntry 9 } 959 vplsSpmsiExpTime OBJECT-TYPE 960 SYNTAX TimeInterval 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "For UDP-based S-PMSI signaling for VPLS, 965 the amount of time remaining before this 966 received S-PMSI Join Message expires, 967 or the next S-PMSI Join Message refresh is to be 968 advertised again from the device." 969 ::= { vplsSpmsiEntry 10 } 971 vplsSpmsiRefCnt OBJECT-TYPE 972 SYNTAX Unsigned32 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "The number of c-multicast routes that are mapped to 977 this S-PMSI." 978 ::= { vplsSpmsiEntry 11 } 980 -- Module compliance. 981 vplsMcastCompliances 982 OBJECT IDENTIFIER ::= { vplsMcastConformance 1 } 984 vplsMcastModuleFullCompliance MODULE-COMPLIANCE 985 STATUS current 986 DESCRIPTION 987 "Compliance requirement for implementations that 988 provide full support for VPLS-LDP-DRAFT-01-MIB. 989 Such devices can then be monitored and configured using 990 this MIB module." 992 MODULE -- this module 994 MANDATORY-GROUPS { 995 vplsMcastGroup, 996 vplsMcastNotificationGroup 997 } 999 ::= { vplsMcastCompliances 1 } 1001 -- Units of conformance. 1003 vplsMcastGroups 1004 OBJECT IDENTIFIER ::= { vplsMcastConformance 2 } 1006 vplsMcastGroup OBJECT-GROUP 1007 OBJECTS { 1008 vplsMcastGenOperStatusChange, 1009 vplsMcastGenOperChangeTime, 1010 vplsMcastGenIpmsiConfig, 1011 vplsMcastGenInterasPmsiConfig, 1012 vplsMcastGenRowStatus, 1013 vplsPmsiCfgTunnelType, 1014 vplsPmsiCfgTunnelAuxInfo, 1015 vplsPmsiCfgTunnelOrTemplateName, 1016 vplsPmsiCfgEncapsType, 1017 vplsPmsiCfgSiteType, 1018 vplsPmsiCfgExcludeUnknownUnicast, 1019 vplsPmsiCfgRowStatus, 1020 vplsIpmsiBgpADAttribute, 1021 vplsIpmsiBgpVplsAttribute, 1022 vplsPmsiTunnelPointer, 1023 vplsPmsiTunnelIf, 1024 vplsSpmsiCfgThreshold, 1025 vplsSpmsiCfgPmsiPointer, 1026 vplsSpmsiCfgRowStatus, 1027 vplsSpmsiTunnelAttribute, 1028 vplsSpmsiUpTime, 1029 vplsSpmsiExpTime, 1030 vplsSpmsiRefCnt 1031 } 1032 STATUS current 1033 DESCRIPTION 1034 "TODO" 1035 ::= { vplsMcastGroups 1 } 1037 vplsMcastNotificationGroup OBJECT-GROUP 1038 OBJECTS { vplsMcastNotificationEnable 1039 } 1040 STATUS current 1041 DESCRIPTION 1042 "TODO" 1043 ::= { vplsMcastGroups 2 } 1045 END 1047 8. Security Considerations 1049 TODO 1051 9. IANA Considerations 1053 IANA is requested to root MIB objects in the MIB module contained in 1054 this document under the transmission subtree. 1056 . 1058 10. Contributors 1060 TODO. 1062 11. Acknowledgements 1064 [TODO]. 1066 12. References 1068 12.1. Normative References 1070 [RFC2629] Rose, M., "Writing I-Ds and RFCs using 1071 XML", RFC 2629, June 1999. 1073 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1074 Interfaces Group MIB", RFC 2863, 1075 June 2000. 1077 [RFC3418] Presuhn, R., "Management Information 1078 Base (MIB) for the Simple Network 1079 Management Protocol (SNMP)", STD 62, 1080 RFC 3418, December 2002. 1082 [RFC4181] Heard, C., "Guidelines for Authors and 1083 Reviewers of MIB Documents", BCP 111, 1084 RFC 4181, September 2005. 1086 [RFC2119] Bradner, S., "Key words for use in RFCs 1087 to Indicate Requirement Levels", BCP 14, 1088 RFC 2119, March 1997. 1090 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1091 and J. Schoenwaelder, Ed., "Structure of 1092 Management Information Version 2 1093 (SMIv2)", STD 58, RFC 2578, April 1999. 1095 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1096 and J. Schoenwaelder, Ed., "Textual 1097 Conventions for SMIv2", STD 58, 1098 RFC 2579, April 1999. 1100 [RFC2580] McCloghrie, K., Perkins, D., and J. 1101 Schoenwaelder, "Conformance Statements 1102 for SMIv2", STD 58, RFC 2580, 1103 April 1999. 1105 [I-D.ietf-l2vpn-vpls-mcast] Aggarwal, R., Rekhter, Y., Kamite, Y., 1106 and L. Fang, "Multicast in VPLS", 1107 draft-ietf-l2vpn-vpls-mcast-10 (work in 1108 progress), February 2012. 1110 [I-D.ietf-l2vpn-vpls-mib] Koushik, K., Mediratta, R., and T. 1111 Nadeau, "Virtual Private Lan Services 1112 (VPLS) Management Information Base", 1113 draft-ietf-l2vpn-vpls-mib-06 (work in 1114 progress), October 2011. 1116 12.2. Informative References 1118 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1119 Stewart, "Introduction and Applicability 1120 Statements for Internet-Standard 1121 Management Framework", RFC 3410, 1122 December 2002. 1124 [RFC4761] Kompella, K. and Y. Rekhter, "Virtual 1125 Private LAN Service (VPLS) Using BGP for 1126 Auto-Discovery and Signaling", RFC 4761, 1127 January 2007. 1129 [RFC4762] Lasserre, M. and V. Kompella, "Virtual 1130 Private LAN Service (VPLS) Using Label 1131 Distribution Protocol (LDP) Signaling", 1132 RFC 4762, January 2007. 1134 [RFC3468] Andersson, L. and G. Swallow, "The 1135 Multiprotocol Label Switching (MPLS) 1136 Working Group decision on MPLS signaling 1137 protocols", RFC 3468, February 2003. 1139 [RFC4875] Aggarwal, R., Papadimitriou, D., and S. 1140 Yasukawa, "Extensions to Resource 1141 Reservation Protocol - Traffic 1142 Engineering (RSVP-TE) for Point-to- 1143 Multipoint TE Label Switched Paths 1144 (LSPs)", RFC 4875, May 2007. 1146 Authors' Addresses 1148 Pradeep Jain 1149 Alcatel-Lucent, Inc. 1150 701 E Middlefield Rd 1151 Mountain View, CA 94040 1152 USA 1154 EMail: pradeep.jain@alcatel-lucent.com 1156 Kanwar Singh 1157 Alcatel-Lucent, Inc. 1158 701 E Middlefield Rd 1159 Mountain View, CA 94040 1160 USA 1162 EMail: kanwar.singh@alcatel-lucent.com 1164 Ranganathan Boovaraghavan 1165 Alcatel-Lucent, Inc. 1166 701 E Middlefield Rd 1167 Mountain View, CA 94040 1168 USA 1170 EMail: ranganathan.boovaraghavan@alcatel-lucent.com