idnits 2.17.1 draft-jain-l2vpn-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 30 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 (June 05, 2012) is 4305 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 138, but not defined == Missing Reference: 'SNMP-CONTEXT-MAP-MIB' is mentioned on line 152, but not defined == Missing Reference: 'L2VPN' is mentioned on line 307, but not defined == Missing Reference: 'TODO' is mentioned on line 1059, but not defined == Unused Reference: 'RFC2629' is defined on line 1065, but no explicit reference was found in the text == Unused Reference: 'RFC2863' is defined on line 1068, but no explicit reference was found in the text == Unused Reference: 'RFC3418' is defined on line 1072, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 1077, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-l2vpn-vpls-mib' is defined on line 1105, but no explicit reference was found in the text == Unused Reference: 'RFC4761' is defined on line 1119, but no explicit reference was found in the text == Unused Reference: 'RFC4762' is defined on line 1124, but no explicit reference was found in the text == Unused Reference: 'RFC3468' is defined on line 1129, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2629 (Obsoleted by RFC 7749) == Outdated reference: A later version (-16) exists of draft-ietf-l2vpn-vpls-mcast-10 == Outdated reference: A later version (-15) exists of draft-ietf-l2vpn-vpls-mib-06 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: December 7, 2012 Alcatel-Lucent, Inc. 6 J. Zhang 7 Juniper Networks, Inc. 8 June 05, 2012 10 VPLS with Point-To-Multipoint LSPs Management Information Base 11 draft-jain-l2vpn-mcast-vpls-mib-00 13 Abstract 15 This memo defines an experimental portion of the Management 16 Information Base for use with network management protocols in the 17 Internet community. 19 In particular, it describes managed objects to configure and/or 20 monitor multicast in VPLS using Point-to-Multipoint LSPs or VPLS- 21 MCAST [I-D.ietf-l2vpn-vpls-mcast]. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on December 7, 2012. 40 Copyright Notice 42 Copyright (c) 2012 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. The Internet-Standard Management Framework . . . . . . . . . . 3 59 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 62 5.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 63 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 64 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 65 8. Security Considerations . . . . . . . . . . . . . . . . . . . 23 66 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 23 67 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 23 68 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 24 69 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 24 70 12.1. Normative References . . . . . . . . . . . . . . . . . . . 24 71 12.2. Informative References . . . . . . . . . . . . . . . . . . 25 73 1. Introduction 75 VPLS using Point-to-Multipoint LSPs or [VPLS-MCAST] describes 76 procedures for VPLS multicast that utilize multicast trees in the 77 sevice provider (SP) network. The multicase tree is typically formed 78 using point-to-multipoint LSPs and is used to flood broadcast, 79 multicast, and unknown unicast traffic across a VPLS core network to 80 all the PE routers. 82 This memo describes managed objects to configure and/or monitor 83 multicast in VPLS using Point-to-Multipoint LSPs or VPLS-MCAST 84 [I-D.ietf-l2vpn-vpls-mcast]. 86 In the current version of this memo does not address MIB Objects for 87 Inter-AS VPLS Multicast. Objects related to this would be adressed 88 in subscequent updates of this proposal. 90 2. The Internet-Standard Management Framework 92 For a detailed overview of the documents that describe the current 93 Internet-Standard Management Framework, please refer to section 7 of 94 RFC 3410 [RFC3410]. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. MIB objects are generally 98 accessed through the Simple Network Management Protocol (SNMP). 99 Objects in the MIB are defined using the mechanisms defined in the 100 Structure of Management Information (SMI). This memo specifies a MIB 101 module that is compliant to the SMIv2, which is described in STD 58, 102 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 103 [RFC2580]. 105 3. Conventions 107 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 108 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 109 document are to be interpreted as described in RFC 2119 [RFC2119]. 111 4. Terminology 113 Terminology used in this document: 115 VPLS : Virtual Provider LAN Service. 117 P2MP : Point-to-Multipoint. 119 MLDP : Multicast Label Distribution Protocol. 121 SNMP : Simple Network Management Protocol. 123 MIB : Management Information Base. 125 PE Router: Provider Edge Router. 127 P Router : Provider Core Router. 129 I-PMSI : Inclusive-Provider Multicast Service Interface. 131 S-PMSI : Selective-Provider Multicast Service Interface. 133 MVPN : Multicast Virtual Private Networks. 135 5. Structure of the MIB Module 137 The MIB Structure for defining VPLS using Point-to-Multipoint LSPs or 138 [VPLS-MCAST] would be based off the existing VPLS-MIB [I-D.ietf- 139 l2vpn-vpls-mib] defination. 141 Following is the relation of the VPLS-MCAST MIB with existing VPLS- 142 MIB 144 +--------+ +-----------------+ 145 PW Mapping | | | | 146 -----> | PW-MIB |-->|PW-ENET/MPLS-MIB | 147 __________ / | | | | 148 | | / +--------+ +-----------------+ 149 | VPLS MIB | / +------------+ 150 | |----------------------> | | 151 +----------- MAC addr. mapping using | BRIDGE-MIB | 152 | [SNMP-CONTEXT-MAP-MIB] | | 153 | +------------+ 154 | 155 +-----------+ 156 | | 157 | VPLS-MCAST| 158 | MIB | 159 +-----------+ 161 5.1. Summary of MIB Module 163 The configuration and states specific to an VPLS-MCAST include the 164 following: 166 - C-multicast routing exchange protocol BGP 168 - I-PMSI, S-PMSI and corresponding provider tunnels 170 - Mapping of c-multicast states to PMSI/tunnels 172 To represent them, the following tables defined. 174 VplsMcastGeneral ----> VplsPmsiConfig <----- VplsSpmsiConfig 176 VplsIpmsi ----> VplsPmsiTunnelAttribute <----- VplsSpmsi 177 | 178 +-VplsIpmsiBgpADAttribute 179 +-VplsIpmsiBgpVplsAttribute 181 - vplsMcastGeneralTable 183 An entry in this table contains general informaion about VPLS-PMSI 184 created on the device. 186 - vplsPmsiConfigTable 188 An entry in this table is created for each PMSI configured on this 189 router. It can be referred to by base VPLS configuration (in 190 vplsConfigEntry) or S-PMSI configuration (in vplsSpmsiConfigEntry). 192 - vplsIpmsiBgpADTable 194 This table specifies all advertised and received I-PMSI 195 advertisements. An entry is created in this table for each IPMSI 196 attribute advertised/ received in BGP-AD 198 - vplsIpmsiBgpVplsTable 200 An entry is created in this table for each IPMSI attribute 201 advertised/ received in BGP-VPLS 203 - vplsPmsiTunnelAttributeTable 205 This table is specified for advertised/received PMSI attributes to be 206 referred to by I-PMSI or S-PMSI table entries. 208 - vplsSpmsiConfigTable 209 This table specifies S-PMSI configuration for each VPLS entry 211 - vplsSpmsiTable 213 This table contains information about the VPLS S-PMSIs advertised/ 214 received for a given VPLS instance 216 6. Relationship to Other MIB Modules 218 This section provides an overview of the relationship between the 219 VPLS-MCAST MIB module and other VPLS MIB modules. 221 The arrows in the following diagram show a 'depends on' relationship. 222 A relationship "MIB module A depends on MIB module B" means that MIB 223 module A uses an object, object identifier, or textual convention 224 defined in MIB module B, or that MIB module A contains a pointer 225 (index or RowPointer) to an object in MIB module B. 227 VPLS-GENERIC-DRAFT-01-MIB VPLS-BGP-DRAFT-01-MIB 228 | | 229 +--------------------------+ 230 | 231 V 232 VPLS-MCAST-MIB 234 7. Definitions 236 VPLS-MCAST-MIB DEFINITIONS ::= BEGIN 238 IMPORTS 239 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 240 experimental, Unsigned32 241 FROM SNMPv2-SMI 243 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 244 FROM SNMPv2-CONF 246 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 247 FROM SNMPv2-TC 249 SnmpAdminString 250 FROM SNMP-FRAMEWORK-MIB 252 InetAddress, InetAddressType 253 FROM INET-ADDRESS-MIB 255 MplsLabel 256 FROM MPLS-TC-STD-MIB 258 vplsConfigIndex, 259 vplsBgpADConfigRouteDistinguisher, 260 vplsBgpADConfigPrefix, 261 vplsBgpADConfigVplsId 262 FROM VPLS-GENERIC-DRAFT-01-MIB 264 vplsBgpVEName 265 FROM VPLS-BGP-DRAFT-01-MIB; 267 vplsMcastMIB MODULE-IDENTITY 268 LAST-UPDATED "201203141200Z" -- 14 March 2012 12:00:00 GMT 269 ORGANIZATION "IETF Layer-2 Virtual Private 270 Networks Working Group." 271 CONTACT-INFO 273 " 274 Comments and discussion to l2vpn@ietf.org 275 Pradeep Jain 276 Alcatel-Lucent, Inc. 277 701 E Middlefield Rd 278 Mountain View, CA 94040 279 USA 280 Email: pradeep.jain@alcatel-lucent.com 282 Kanwar Singh 283 Alcatel-Lucent, Inc. 284 701 E Middlefield Rd 285 Mountain View, CA 94040 286 USA 287 Email: kanwar.singh@alcatel-lucent.com 289 Ranganathan Boovaraghavan 290 Alcatel-Lucent, Inc. 291 701 E Middlefield Rd 292 Mountain View, CA 94040 293 USA 294 Email: ranganathan.boovaraghavan@alcatel-lucent.com 296 Jeffrey (Zhaohui) Zhang 297 Juniper Networks, Inc. 298 10 Technology Park Drive 299 Westford, MA 01886 300 USA 301 Email: zzhang@juniper.net 303 " 305 DESCRIPTION 306 "This MIB contains managed object definitions for 307 multicast in Layer 2 VPLS defined by [L2VPN]. 308 Copyright (C) The Internet Society (2012)." 310 -- Revision history. 311 REVISION "201203141200Z" -- 14 March 2012 12:00:00 GMT 312 DESCRIPTION 313 "Initial version of the draft." 314 ::= { experimental 99 } -- number to be assigned 316 -- Top level components of this MIB. 317 -- Traps 318 vplsMcastNotifications OBJECT IDENTIFIER ::= { vplsMcastMIB 0 } 320 -- tables, scalars 321 vplsMcastObjects OBJECT IDENTIFIER ::= { vplsMcastMIB 1 } 323 -- conformance 324 vplsMcastConformance OBJECT IDENTIFIER ::= { vplsMcastMIB 2 } 326 vplsMcastScalars OBJECT IDENTIFIER ::= { vplsMcastObjects 1 } 327 vplsMcastGeneral OBJECT IDENTIFIER ::= { vplsMcastObjects 2 } 328 vplsMcastConfig OBJECT IDENTIFIER ::= { vplsMcastObjects 3 } 329 vplsMcastStates OBJECT IDENTIFIER ::= { vplsMcastObjects 4 } 331 -- Scalar Objects 333 vplsMcastNotificationEnable OBJECT-TYPE 334 SYNTAX TruthValue 335 MAX-ACCESS read-write 336 STATUS current 337 DESCRIPTION 338 "If this object is TRUE, then the generation of all 339 notifications defined in this MIB is enabled." 340 DEFVAL { false } 341 ::= { vplsMcastScalars 1 } 343 vplsMcastGeneralTable OBJECT-TYPE 344 SYNTAX SEQUENCE OF VplsMcastGeneralEntry 345 MAX-ACCESS not-accessible 346 STATUS current 347 DESCRIPTION 348 "This table specifies the general information about the VPLS-PMSI 349 present in this device." 350 ::= { vplsMcastGeneral 1 } 352 vplsMcastGeneralEntry OBJECT-TYPE 353 SYNTAX VplsMcastGeneralEntry 354 MAX-ACCESS not-accessible 355 STATUS current 356 DESCRIPTION 357 "An entry in this table is created for every VPLS Instance in the 358 device." 359 INDEX { vplsConfigIndex } 360 ::= { vplsMcastGeneralTable 1 } 362 VplsMcastGeneralEntry ::= SEQUENCE { 363 vplsMcastGenOperStatusChange INTEGER, 364 vplsMcastGenOperChangeTime TimeStamp, 365 vplsMcastGenIpmsiConfig RowPointer, 366 vplsMcastGenInterasPmsiConfig RowPointer, 367 vplsMcastGenSiteType INTEGER, 368 vplsMcastGenExcludeUnknownUnicast TruthValue, 369 vplsMcastGenRowStatus RowStatus 370 } 372 vplsMcastGenOperStatusChange OBJECT-TYPE 373 SYNTAX INTEGER { createdVplsPmsi(1), 374 deletedVplsPmsi(2), 375 modifiedVplsIpmsiConfig(3), 376 modifiedVplsSpmsiConfig(4) 377 } 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "This object describes the last operational change that 382 happened for the given VPLS-PMSI. 384 createdVplsPmsi - indicates that VPLS PMSI was created in the 385 device. 387 deletedVplsPmsi - indicates that the VPLS PMSI was deleted from the 388 device. A row in this table will never have 389 vplsMcastGenOperStatusChange equal to deletedVplsPmsi(2), 390 because in that case the row itself will be deleted from the 391 table. This value for vplsMcastGenOperStatusChange is defined 392 mainly for use in vplsMcastPmsiChange notification. 394 modifiedVplsIpmsiConfig - indicates that the I-PMSI 395 for the VPLS was configured, deleted or changed. 397 modifiedVplsSpmsiConfig - indicates that the S-PMSI 398 for the VPLS was configured, deleted or changed." 399 DEFVAL { createdVplsPmsi } 400 ::= { vplsMcastGeneralEntry 1 } 402 vplsMcastGenOperChangeTime OBJECT-TYPE 403 SYNTAX TimeStamp 404 MAX-ACCESS read-only 405 STATUS current 406 DESCRIPTION 407 "The time at which the last operational change for the VPLS-PMSI in 408 question took place. The last operational change is specified 409 by vplsMcastGenOperStatusChange." 410 ::= { vplsMcastGeneralEntry 2 } 412 vplsMcastGenIpmsiConfig OBJECT-TYPE 413 SYNTAX RowPointer 414 MAX-ACCESS read-create 415 STATUS current 416 DESCRIPTION 417 "This points to a row in vplsMcastPmsiConfigTable, 418 for I-PMSI configuration." 419 ::= { vplsMcastGeneralEntry 3 } 421 vplsMcastGenInterasPmsiConfig OBJECT-TYPE 422 SYNTAX RowPointer 423 MAX-ACCESS read-create 424 STATUS current 425 DESCRIPTION 426 "This points to a row in vplsMcastPmsiConfigTable, 427 for inter-as I-PMSI configuration in case of segmented 428 inter-as provider tunnels." 429 ::= { vplsMcastGeneralEntry 4 } 431 vplsMcastGenSiteType OBJECT-TYPE 432 SYNTAX INTEGER { 433 senderReceiver (1), 434 receiverOnly (2), 435 senderOnly (3) 436 } 437 MAX-ACCESS read-write 438 STATUS current 439 DESCRIPTION 440 "Whether this site is a receiver-only site or not. 441 sender-receiver (1): both sender and receiver site. 442 receiver-only (2): receiver-only site. 443 sender-only (3): sender only site." 444 ::= { vplsMcastGeneralEntry 5 } 446 vplsMcastGenExcludeUnknownUnicast OBJECT-TYPE 447 SYNTAX TruthValue 448 MAX-ACCESS read-write 449 STATUS current 450 DESCRIPTION 451 "If this object is TRUE, then Unknown Unicast will not 452 be mapped to the provider tunnel. 453 If this object is FALSE, then Uknown Unicast will be 454 mapped to the provider tunnel." 455 DEFVAL { false } 456 ::= { vplsMcastGeneralEntry 6 } 458 vplsMcastGenRowStatus OBJECT-TYPE 459 SYNTAX RowStatus 460 MAX-ACCESS read-create 461 STATUS current 462 DESCRIPTION 463 "This is used to create or delete a row in this table." 464 ::= { vplsMcastGeneralEntry 7 } 466 -- VPLS PMSI Configuration Table 468 vplsPmsiConfigTable OBJECT-TYPE 469 SYNTAX SEQUENCE OF VplsPmsiConfigEntry 470 MAX-ACCESS not-accessible 471 STATUS current 472 DESCRIPTION 473 "An entry in this table is created for each PMSI configured 474 on this router. It can be referred to by base VPLS 475 configuration (in vplsConfigEntry) or S-PMSI configuration 476 (in vplsSpmsiConfigEntry)" 477 ::= { vplsMcastConfig 1 } 479 vplsPmsiConfigEntry OBJECT-TYPE 480 SYNTAX VplsPmsiConfigEntry 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "An entry in this table is created for each PMSI configured 485 on this router under VPLS Service" 486 INDEX { vplsConfigIndex } 487 ::= { vplsPmsiConfigTable 1 } 489 VplsPmsiConfigEntry ::= SEQUENCE { 490 vplsPmsiCfgTunnelType INTEGER, 491 vplsPmsiCfgTunnelAuxInfo Unsigned32, 492 vplsPmsiCfgTunnelOrTemplateName SnmpAdminString, 493 vplsPmsiCfgRowStatus RowStatus 494 } 496 vplsPmsiCfgTunnelType OBJECT-TYPE 497 SYNTAX INTEGER { rsvpP2mp (1), 498 ldpP2mp (2), 499 ingressReplication (3) 500 } 501 MAX-ACCESS read-write 502 STATUS current 503 DESCRIPTION 504 "Type of tunnel used to instantiate the PMSI." 505 ::= { vplsPmsiConfigEntry 1 } 507 vplsPmsiCfgTunnelAuxInfo OBJECT-TYPE 508 SYNTAX Unsigned32 509 MAX-ACCESS read-write 510 STATUS current 511 DESCRIPTION 512 "Additional tunnel information depending on the type. 513 rsvp-p2mp: 1 for statically specified rsvp-p2mp tunnel 514 2 for dynamically created rsvp-p2mp tunnel 515 ingress-replication: 516 1 for using any existing p2p/mp2p lsp 517 2 for dynamically creating new p2p lsp" 518 ::= { vplsPmsiConfigEntry 2 } 520 vplsPmsiCfgTunnelOrTemplateName OBJECT-TYPE 521 SYNTAX SnmpAdminString 522 MAX-ACCESS read-write 523 STATUS current 524 DESCRIPTION 525 "The tunnel name or template name used to create tunnels. 526 Depending on vplsPmsiCfgTunnelType and 527 vplsPmsiCfgTunnelAuxInfo: 529 dynamically created rsvp-p2mp tunnel: template name 530 statically specified rsvp-p2mp tunnel: tunnel name 531 ingress-replication using 532 dynamically created lsps: template name 533 other: null" 534 ::= { vplsPmsiConfigEntry 3 } 536 vplsPmsiCfgRowStatus OBJECT-TYPE 537 SYNTAX RowStatus 538 MAX-ACCESS read-create 539 STATUS current 540 DESCRIPTION 541 "Used to create/modify/delete a row in this table." 542 ::= { vplsPmsiConfigEntry 4 } 544 -- Table of IPMSI BGP-AD Advertised/Received. 546 vplsPmsiBgpADTable OBJECT-TYPE 547 SYNTAX SEQUENCE OF VplsPmsiBgpADEntry 548 MAX-ACCESS not-accessible 549 STATUS current 550 DESCRIPTION 551 "This table specifies all advertised and received IPmsi advertisements." 552 ::= { vplsMcastStates 1 } 554 vplsPmsiBgpADEntry OBJECT-TYPE 555 SYNTAX VplsPmsiBgpADEntry 556 MAX-ACCESS not-accessible 557 STATUS current 558 DESCRIPTION 559 "An entry is created in this table for each IPMSI attribute advertised/received in BGP-AD" 560 INDEX { vplsConfigIndex, 561 vplsBgpADConfigRouteDistinguisher, 562 vplsBgpADConfigPrefix, 563 vplsBgpADConfigVplsId } 564 ::= { vplsPmsiBgpADTable 1 } 566 VplsPmsiBgpADEntry ::= SEQUENCE { 567 vplsPmsiBgpADAttribute RowPointer 568 } 570 vplsPmsiBgpADAttribute OBJECT-TYPE 571 SYNTAX RowPointer 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "Points to a row in the vplsIpmsiTunnelAttributeTable." 576 ::= { vplsPmsiBgpADEntry 1 } 578 -- Table of IPMSI BGP-VPLS Advertised/Received. 580 vplsPmsiBgpVplsTable OBJECT-TYPE 581 SYNTAX SEQUENCE OF VplsPmsiBgpVplsEntry 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "This table specifies the all advertised and received IPmsi advertisements." 586 ::= { vplsMcastStates 2 } 588 vplsPmsiBgpVplsEntry OBJECT-TYPE 589 SYNTAX VplsPmsiBgpVplsEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "An entry is created in this table for each IPMSI attribute advertised/received in BGP-VPLS" 594 INDEX { vplsConfigIndex, 595 vplsBgpVEName} 596 ::= { vplsPmsiBgpVplsTable 1 } 598 VplsPmsiBgpVplsEntry ::= SEQUENCE { 599 vplsPmsiBgpVplsAttribute RowPointer 600 } 602 vplsPmsiBgpVplsAttribute OBJECT-TYPE 603 SYNTAX RowPointer 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "Points to a row in the vplsPmsiTunnelAttributeTable." 608 ::= { vplsPmsiBgpVplsEntry 1 } 610 -- Table of VPLS PMSI attributes 612 vplsPmsiTunnelAttributeTable OBJECT-TYPE 613 SYNTAX SEQUENCE OF VplsPmsiTunnelAttributeEntry 614 MAX-ACCESS not-accessible 615 STATUS current 616 DESCRIPTION 617 "This table is for advertised/received PMSI attributes, 618 to be referred to by I-PMSI or S-PMSI table entries" 619 ::= { vplsMcastStates 3 } 621 vplsPmsiTunnelAttributeEntry OBJECT-TYPE 622 SYNTAX VplsPmsiTunnelAttributeEntry 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "An entry in this table corresponds to an PMSI attribute 627 that is advertised/received on this router. 628 For BGP-based signaling (for I-PMSI via auto-discovery 629 procedure, or for S-PMSI via S-PMSI A-D routes), 630 they are just as signaled by BGP." 631 INDEX { 632 vplsPmsiTunnelAttributeType, 633 vplsPmsiTunnelAttributeLabel, 634 vplsPmsiTunnelAttributeFlags, 635 vplsPmsiTunnelAttributeId 636 } 637 ::= { vplsPmsiTunnelAttributeTable 1 } 639 VplsPmsiTunnelAttributeEntry ::= SEQUENCE { 640 vplsPmsiTunnelAttributeType Unsigned32, 641 vplsPmsiTunnelAttributeLabel MplsLabel, 642 vplsPmsiTunnelAttributeFlags OCTET STRING, 643 vplsPmsiTunnelAttributeId OCTET STRING, 644 vplsPmsiTunnelPointer RowPointer, 645 vplsPmsiTunnelIf RowPointer 646 } 648 vplsPmsiTunnelAttributeType OBJECT-TYPE 649 SYNTAX Unsigned32 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "The tunnel type identifies the type of tunneling technology 654 used to establish the PMSI tunnel. This document discusses the 655 following tunnel types: 656 0 - No tunnel information present 657 1 - RSVP-TE P2MP LSP 658 2 - mLDP P2MP LSP 659 " 660 ::= { vplsPmsiTunnelAttributeEntry 1 } 662 vplsPmsiTunnelAttributeLabel OBJECT-TYPE 663 SYNTAX MplsLabel 664 MAX-ACCESS not-accessible 665 STATUS current 666 DESCRIPTION 667 "If the MPLS Label field is non-zero, then it contains an MPLS 668 label encoded as 3 octets, where the high-order 20 bits contain the label 669 value. Absence of MPLS Label is indicated by setting the MPLS Label 670 field to zero." 671 ::= { vplsPmsiTunnelAttributeEntry 2 } 673 vplsPmsiTunnelAttributeFlags OBJECT-TYPE 674 SYNTAX OCTET STRING (SIZE (1)) 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "The Flags field has the following format: 679 0 1 2 3 4 5 6 7 680 +-+-+-+-+-+-+-+-+ 681 | reserved |L| 682 +-+-+-+-+-+-+-+-+ 683 This document defines the following flags: 684 + Leaf Information Required (L)" 685 ::= { vplsPmsiTunnelAttributeEntry 3 } 687 vplsPmsiTunnelAttributeId OBJECT-TYPE 688 SYNTAX OCTET STRING ( SIZE (4|8|12) ) 689 MAX-ACCESS not-accessible 690 STATUS current 691 DESCRIPTION 692 "When the type is set to 'No tunnel information present', the PMSI 693 Tunnel attribute carries no tunnel information (no Tunnel 694 Identifier). This type is to be used only in the following case: to 695 enable explicit tracking for a particular customer multicast flow (by 696 setting the Leaf Information Required flag to 1), but without binding 697 this flow to a particular provider tunnel (by omitting any tunnel 698 information). 700 When the type is set to RSVP-TE P2MP LSP, the Tunnel Identifier is 701 (Extended Tunnel ID, Reserved, Tunnel ID, P2MP ID) as carried in the 702 RSVP-TE P2MP LSP SESSION Object [RFC4875]. 704 When the type is set to mLDP P2MP LSP, the Tunnel Identifier is a 705 P2MP FEC Element [mLDP]." 706 ::= { vplsPmsiTunnelAttributeEntry 4 } 708 vplsPmsiTunnelPointer OBJECT-TYPE 709 SYNTAX RowPointer 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "If the tunnel exists in some MIB table, this is the row pointer 714 to it." 715 ::= { vplsPmsiTunnelAttributeEntry 5 } 717 vplsPmsiTunnelIf OBJECT-TYPE 718 SYNTAX RowPointer 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "If the tunnel has a corresponding interface, this is the 723 row pointer to the ifName table." 724 ::= { vplsPmsiTunnelAttributeEntry 6 } 726 -- S-PMSI configuration table 728 vplsSpmsiConfigTable OBJECT-TYPE 729 SYNTAX SEQUENCE OF VplsSpmsiConfigEntry 730 MAX-ACCESS not-accessible 731 STATUS current 732 DESCRIPTION 733 "This table specifies S-PMSI configuration." 734 ::= { vplsMcastConfig 2 } 736 vplsSpmsiConfigEntry OBJECT-TYPE 737 SYNTAX VplsSpmsiConfigEntry 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "An entry is created for each S-PMSI configuration." 742 INDEX { vplsConfigIndex, 743 vplsSpmsiCfgCmcastAddressType, 744 vplsSpmsiCfgCmcastGroupAddress, 745 vplsSpmsiCfgCmcastGroupPrefixLen, 746 vplsSpmsiCfgCmcastSrcAddress, 747 vplsSpmsiCfgCmcastSrcPrefixLen } 748 ::= { vplsSpmsiConfigTable 1 } 750 VplsSpmsiConfigEntry ::= SEQUENCE { 751 vplsSpmsiCfgCmcastAddressType InetAddressType, 752 vplsSpmsiCfgCmcastGroupAddress InetAddress, 753 vplsSpmsiCfgCmcastGroupPrefixLen Unsigned32, 754 vplsSpmsiCfgCmcastSrcAddress InetAddress, 755 vplsSpmsiCfgCmcastSrcPrefixLen Unsigned32, 756 vplsSpmsiCfgThreshold Unsigned32, 757 vplsSpmsiCfgPmsiPointer RowPointer, 758 vplsSpmsiCfgRowStatus RowStatus 759 } 761 vplsSpmsiCfgCmcastAddressType OBJECT-TYPE 762 SYNTAX InetAddressType 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "Type of C-multicast address" 767 ::= { vplsSpmsiConfigEntry 1 } 769 vplsSpmsiCfgCmcastGroupAddress OBJECT-TYPE 770 SYNTAX InetAddress 771 MAX-ACCESS not-accessible 772 STATUS current 773 DESCRIPTION 774 "C-multicast group address" 775 ::= { vplsSpmsiConfigEntry 2 } 777 vplsSpmsiCfgCmcastGroupPrefixLen OBJECT-TYPE 778 SYNTAX Unsigned32 779 MAX-ACCESS not-accessible 780 STATUS current 781 DESCRIPTION 782 "C-multicast group address prefix length. 783 A group 0 (or ::0) with prefix length 32 (or 128) 784 indicates wildcard group, while a group 0 (or ::0) 785 with prefix length 0 indicates any group." 786 ::= { vplsSpmsiConfigEntry 3 } 788 vplsSpmsiCfgCmcastSrcAddress OBJECT-TYPE 789 SYNTAX InetAddress 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "C-multicast source address" 794 ::= { vplsSpmsiConfigEntry 4 } 796 vplsSpmsiCfgCmcastSrcPrefixLen OBJECT-TYPE 797 SYNTAX Unsigned32 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "C-multicast source address prefix length. 802 A source 0 (or ::0) with prefix length 32 (or 128) 803 indicates a wildcard source, while a source 0 (or ::0) 804 with prefix length 0 indicates any source." 805 ::= { vplsSpmsiConfigEntry 5 } 807 vplsSpmsiCfgThreshold OBJECT-TYPE 808 SYNTAX Unsigned32 (0..4294967295) 809 UNITS "kilobits per second" 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "The bandwidth threshold value which when exceeded for a 814 multicast routing entry in the given VPLS, triggers usage 815 of S-PMSI." 816 ::= { vplsSpmsiConfigEntry 6 } 818 vplsSpmsiCfgPmsiPointer OBJECT-TYPE 819 SYNTAX RowPointer 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "This points to a row in vplsPmsiConfigTable, 824 to specify tunnel attributes." 825 ::= { vplsSpmsiConfigEntry 7 } 827 vplsSpmsiCfgRowStatus OBJECT-TYPE 828 SYNTAX RowStatus 829 MAX-ACCESS read-create 830 STATUS current 831 DESCRIPTION 832 "Used to create/modify/delete a row in this table." 833 ::= { vplsSpmsiConfigEntry 8 } 835 -- Table of S-PMSIs advertised/received 837 vplsSpmsiTable OBJECT-TYPE 838 SYNTAX SEQUENCE OF VplsSpmsiEntry 839 MAX-ACCESS not-accessible 840 STATUS current 841 DESCRIPTION 842 "This table has information about the S-PMSIs sent/received 843 by a device." 844 ::= { vplsMcastStates 4 } 846 vplsSpmsiEntry OBJECT-TYPE 847 SYNTAX VplsSpmsiEntry 848 MAX-ACCESS not-accessible 849 STATUS current 850 DESCRIPTION 851 "An entry in this table is created or updated for every S-PMSI 852 advertised/received in a particular VPLS." 853 INDEX { vplsConfigIndex, 854 vplsSpmsiCmcastAddrType, 855 vplsSpmsiCmcastGroup, 856 vplsSpmsiCmcastGroupPrefixLen, 857 vplsSpmsiCmcastSource, 858 vplsSpmsiCmcastSourcePrefixLen, 859 vplsSpmsiOrigAddrType, 860 vplsSpmsiOrigAddress} 861 ::= { vplsSpmsiTable 1 } 863 VplsSpmsiEntry ::= SEQUENCE { 864 vplsSpmsiCmcastAddrType InetAddressType, 865 vplsSpmsiCmcastGroup InetAddress, 866 vplsSpmsiCmcastGroupPrefixLen Unsigned32, 867 vplsSpmsiCmcastSource InetAddress, 868 vplsSpmsiCmcastSourcePrefixLen InetAddress, 869 vplsSpmsiOrigAddrType InetAddressType, 870 vplsSpmsiOrigAddress InetAddress, 871 vplsSpmsiTunnelAttribute RowPointer, 872 vplsSpmsiUpTime TimeInterval, 873 vplsSpmsiExpTime TimeInterval, 874 vplsSpmsiRefCnt Unsigned32 875 } 877 vplsSpmsiCmcastAddrType OBJECT-TYPE 878 SYNTAX InetAddressType 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "The Internet address type of vplsSpmsiCmcastGroup/Source." 883 ::= { vplsSpmsiEntry 1 } 885 vplsSpmsiCmcastGroup OBJECT-TYPE 886 SYNTAX InetAddress (SIZE (4|16|20)) 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "S-PMSI C-multicast group address. 891 If it is 0 (or ::0), this is a wildcard group, 892 and vplsSpmsiCmcastGroupPrefixLen must be 32 (or 128)." 893 ::= { vplsSpmsiEntry 2 } 895 vplsSpmsiCmcastGroupPrefixLen OBJECT-TYPE 896 SYNTAX Unsigned32 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "S-PMSI C-multicast group address prefix length." 901 ::= { vplsSpmsiEntry 3 } 903 vplsSpmsiCmcastSource OBJECT-TYPE 904 SYNTAX InetAddress (SIZE (4|16|20)) 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "S-PMSI C-multicast source address 909 If it is 0 (or ::0), this is a wildcard source, 910 and vplsSpmsiCmcastSourcePrefixLen must be 32 (or 128)." 911 ::= { vplsSpmsiEntry 4 } 913 vplsSpmsiCmcastSourcePrefixLen OBJECT-TYPE 914 SYNTAX InetAddress (SIZE (4|16|20)) 915 MAX-ACCESS not-accessible 916 STATUS current 917 DESCRIPTION 918 "S-PMSI C-multicast source address prefix length." 919 ::= { vplsSpmsiEntry 5 } 921 vplsSpmsiOrigAddrType OBJECT-TYPE 922 SYNTAX InetAddressType 923 MAX-ACCESS not-accessible 924 STATUS current 925 DESCRIPTION 926 "The Internet address type of vplsSpmsiOrigAddress." 927 ::= { vplsSpmsiEntry 6 } 929 vplsSpmsiOrigAddress OBJECT-TYPE 930 SYNTAX InetAddress 931 MAX-ACCESS not-accessible 932 STATUS current 933 DESCRIPTION 934 "The BGP address of the device that originated the S-PMSI." 935 ::= { vplsSpmsiEntry 7 } 937 vplsSpmsiTunnelAttribute OBJECT-TYPE 938 SYNTAX RowPointer 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "A row pointer to the vplsPmsiTunnelAttributeTable" 943 ::= { vplsSpmsiEntry 8 } 945 vplsSpmsiUpTime OBJECT-TYPE 946 SYNTAX TimeInterval 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "The time since this S-PMSI 951 was first advertised/received by the device." 952 ::= { vplsSpmsiEntry 9 } 954 vplsSpmsiExpTime OBJECT-TYPE 955 SYNTAX TimeInterval 956 MAX-ACCESS read-only 957 STATUS current 958 DESCRIPTION 959 "For UDP-based S-PMSI signaling for VPLS, 960 the amount of time remaining before this 961 received S-PMSI Join Message expires, 962 or the next S-PMSI Join Message refresh is to be 963 advertised again from the device." 965 ::= { vplsSpmsiEntry 10 } 967 vplsSpmsiRefCnt OBJECT-TYPE 968 SYNTAX Unsigned32 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The number of c-multicast routes that are mapped to 973 this S-PMSI." 974 ::= { vplsSpmsiEntry 11 } 976 -- Module compliance. 977 vplsMcastCompliances 978 OBJECT IDENTIFIER ::= { vplsMcastConformance 1 } 980 vplsMcastModuleFullCompliance MODULE-COMPLIANCE 981 STATUS current 982 DESCRIPTION 983 "Compliance requirement for implementations that 984 provide full support for VPLS-LDP-DRAFT-01-MIB. 985 Such devices can then be monitored and configured using 986 this MIB module." 988 MODULE -- this module 990 MANDATORY-GROUPS { 991 vplsMcastGroup, 992 vplsMcastNotificationGroup 993 } 995 ::= { vplsMcastCompliances 1 } 997 -- Units of conformance. 999 vplsMcastGroups 1000 OBJECT IDENTIFIER ::= { vplsMcastConformance 2 } 1002 vplsMcastGroup OBJECT-GROUP 1003 OBJECTS { 1004 vplsMcastGenOperStatusChange, 1005 vplsMcastGenOperChangeTime, 1006 vplsMcastGenIpmsiConfig, 1007 vplsMcastGenInterasPmsiConfig, 1008 vplsMcastGenCfgSiteType, 1009 vplsMcastGenCfgExcludeUnknownUnicast, 1010 vplsMcastGenRowStatus, 1011 vplsPmsiCfgTunnelType, 1012 vplsPmsiCfgTunnelAuxInfo, 1013 vplsPmsiCfgTunnelOrTemplateName, 1014 vplsPmsiCfgRowStatus, 1015 vplsPmsiBgpADAttribute, 1016 vplsPmsiBgpVplsAttribute, 1017 vplsPmsiTunnelPointer, 1018 vplsPmsiTunnelIf, 1019 vplsSpmsiCfgThreshold, 1020 vplsSpmsiCfgPmsiPointer, 1021 vplsSpmsiCfgRowStatus, 1022 vplsSpmsiTunnelAttribute, 1023 vplsSpmsiUpTime, 1024 vplsSpmsiExpTime, 1025 vplsSpmsiRefCnt 1026 } 1027 STATUS current 1028 DESCRIPTION 1029 "TODO" 1030 ::= { vplsMcastGroups 1 } 1032 vplsMcastNotificationGroup OBJECT-GROUP 1033 OBJECTS { vplsMcastNotificationEnable 1034 } 1035 STATUS current 1036 DESCRIPTION 1037 "TODO" 1038 ::= { vplsMcastGroups 2 } 1040 END 1042 8. Security Considerations 1044 TODO 1046 9. IANA Considerations 1048 IANA is requested to root MIB objects in the MIB module contained in 1049 this document under the transmission subtree. 1051 . 1053 10. Contributors 1055 TODO. 1057 11. Acknowledgements 1059 [TODO]. 1061 12. References 1063 12.1. Normative References 1065 [RFC2629] Rose, M., "Writing I-Ds and RFCs using 1066 XML", RFC 2629, June 1999. 1068 [RFC2863] McCloghrie, K. and F. Kastenholz, "The 1069 Interfaces Group MIB", RFC 2863, 1070 June 2000. 1072 [RFC3418] Presuhn, R., "Management Information 1073 Base (MIB) for the Simple Network 1074 Management Protocol (SNMP)", STD 62, 1075 RFC 3418, December 2002. 1077 [RFC4181] Heard, C., "Guidelines for Authors and 1078 Reviewers of MIB Documents", BCP 111, 1079 RFC 4181, September 2005. 1081 [RFC2119] Bradner, S., "Key words for use in RFCs 1082 to Indicate Requirement Levels", BCP 14, 1083 RFC 2119, March 1997. 1085 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., 1086 and J. Schoenwaelder, Ed., "Structure of 1087 Management Information Version 2 1088 (SMIv2)", STD 58, RFC 2578, April 1999. 1090 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., 1091 and J. Schoenwaelder, Ed., "Textual 1092 Conventions for SMIv2", STD 58, 1093 RFC 2579, April 1999. 1095 [RFC2580] McCloghrie, K., Perkins, D., and J. 1096 Schoenwaelder, "Conformance Statements 1097 for SMIv2", STD 58, RFC 2580, 1098 April 1999. 1100 [I-D.ietf-l2vpn-vpls-mcast] Aggarwal, R., Rekhter, Y., Kamite, Y., 1101 and L. Fang, "Multicast in VPLS", 1102 draft-ietf-l2vpn-vpls-mcast-10 (work in 1103 progress), February 2012. 1105 [I-D.ietf-l2vpn-vpls-mib] Koushik, K., Mediratta, R., and T. 1106 Nadeau, "Virtual Private Lan Services 1107 (VPLS) Management Information Base", 1108 draft-ietf-l2vpn-vpls-mib-06 (work in 1109 progress), October 2011. 1111 12.2. Informative References 1113 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 1114 Stewart, "Introduction and Applicability 1115 Statements for Internet-Standard 1116 Management Framework", RFC 3410, 1117 December 2002. 1119 [RFC4761] Kompella, K. and Y. Rekhter, "Virtual 1120 Private LAN Service (VPLS) Using BGP for 1121 Auto-Discovery and Signaling", RFC 4761, 1122 January 2007. 1124 [RFC4762] Lasserre, M. and V. Kompella, "Virtual 1125 Private LAN Service (VPLS) Using Label 1126 Distribution Protocol (LDP) Signaling", 1127 RFC 4762, January 2007. 1129 [RFC3468] Andersson, L. and G. Swallow, "The 1130 Multiprotocol Label Switching (MPLS) 1131 Working Group decision on MPLS signaling 1132 protocols", RFC 3468, February 2003. 1134 [RFC4875] Aggarwal, R., Papadimitriou, D., and S. 1135 Yasukawa, "Extensions to Resource 1136 Reservation Protocol - Traffic 1137 Engineering (RSVP-TE) for Point-to- 1138 Multipoint TE Label Switched Paths 1139 (LSPs)", RFC 4875, May 2007. 1141 Authors' Addresses 1143 Pradeep Jain 1144 Alcatel-Lucent, Inc. 1145 701 E Middlefield Rd 1146 Mountain View, CA 94040 1147 USA 1149 EMail: pradeep.jain@alcatel-lucent.com 1150 Kanwar Singh 1151 Alcatel-Lucent, Inc. 1152 701 E Middlefield Rd 1153 Mountain View, CA 94040 1154 USA 1156 EMail: kanwar.singh@alcatel-lucent.com 1158 Ranganathan Boovaraghavan 1159 Alcatel-Lucent, Inc. 1160 701 E Middlefield Rd 1161 Mountain View, CA 94040 1162 USA 1164 EMail: ranganathan.boovaraghavan@alcatel-lucent.com 1166 Jeffrey (Zhaohui) Zhang 1167 Juniper Networks, Inc. 1168 10 Technology Park Drive 1169 Westford, MA 01886 1170 USA 1172 EMail: zzhang@juniper.net