idnits 2.17.1 draft-ietf-bess-mvpn-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (June 06, 2017) is 2488 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2571' is mentioned on line 306, but not defined ** Obsolete undefined reference: RFC 2571 (Obsoleted by RFC 3411) == Missing Reference: 'RFC2851' is mentioned on line 309, but not defined ** Obsolete undefined reference: RFC 2851 (Obsoleted by RFC 3291) == Missing Reference: 'TBD' is mentioned on line 1725, but not defined == Outdated reference: A later version (-16) exists of draft-ietf-bess-l2l3-vpn-mcast-mib-08 ** Obsolete normative reference: RFC 4601 (Obsoleted by RFC 7761) Summary: 3 errors (**), 0 flaws (~~), 6 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Z. Zhang, Ed. 3 Internet-Draft Juniper 4 Intended status: Standards Track S. Asif 5 Expires: December 8, 2017 AT&T 6 A. Green 7 BT 8 S. Gulranjani 9 Cisco 10 P. Jain 11 Alcatel-Lucent 12 H. Tsunoda, Ed. 13 Tohoku Institute of Technology 14 June 06, 2017 16 BGP/MPLS Layer 3 VPN Multicast Management Information Base 17 draft-ietf-bess-mvpn-mib-04 19 Abstract 21 This memo defines a portion of the Management Information Base (MIB) 22 for use with network management protocols in the Internet community. 23 In particular, it describes managed objects to configure and/or 24 monitor MVPN, Multicast in MultiProtocol Label Switching/Border 25 Gateway Protocol (MPLS/BGP) IP Virtual Private Networks (VPNs) on a 26 Provider Edge router. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on December 8, 2017. 45 Copyright Notice 47 Copyright (c) 2017 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. The Internet-Standard Management Framework . . . . . . . . . 4 65 3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 4 66 3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 67 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 7 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 36 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 70 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 37 71 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 72 7.1. Normative References . . . . . . . . . . . . . . . . . . 37 73 7.2. Informative References . . . . . . . . . . . . . . . . . 39 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 76 1. Introduction 78 [RFC6513] [RFC6514], and [RFC6625] specify procedures for supporting 79 multicast in Border Gateway Protocol/MultiProtocol Label Switching 80 (BGP/MPLS) Layer 3 (IP) Virtual Private Network (VPN). Throughout 81 this document, we will use the term "Multicast VPN (MVPN)" [RFC6513] 82 to refer to a BGP/MPLS IP VPN that supports multicast. 84 Provider Edge routers (PEs) exchange the VPN customer multicast 85 (C-multicast) routing information with each other. In [RFC6513], two 86 basic methods for exchanging C-multicast routing information are 87 defined (1) Protocol Independent Multicast (PIM) [RFC4601] and (2) 88 BGP. 90 In the rest of this document we will use the term "PIM-MVPN" to refer 91 to PIM being used for exchanging C-multicast routing information, and 92 "BGP-MVPN" to refer to BGP being used for exchanging C-multicast 93 routing information. 95 This document describes managed objects to configure and/or monitor 96 MVPN. The managed objects are common to both PIM-MVPN and BGP-MVPN. 98 This document borrowed some text from Cisco PIM-MVPN MIB 99 [I-D.svaidya-mcast-vpn-mib]. For PIM-MVPN this document attempts to 100 provide coverage comparable to [I-D.svaidya-mcast-vpn-mib], but in a 101 generic way that applies to both PIM-MVPN and BGP-MVPN. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in [RFC2119]. 107 Comments should be made directly to the BESS WG at bess@ietf.org. 109 1.1. Terminology 111 This document adopts the definitions, acronyms and mechanisms 112 described in [RFC6513] and other documents that [RFC6513] refers to. 113 Familiarity with Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts 114 and/or mechanisms is assumed. Some terms specifically related to 115 this document are explained below. 117 MVPN can be achieved by using various kinds of transport mechanisms 118 for forwarding a packet to all or a subset of PEs across service 119 provider networks. Such transport mechanisms are referred to as 120 provider tunnels (P-tunnels). 122 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 123 conceptual interface instantiated by a provider tunnel (P-tunnel), a 124 transport mechanism used to deliver multicast traffic. A PE uses to 125 send customer multicast traffic to all or some PEs in the same VPN. 127 There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective 128 PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE 129 attached to a particular MVPN to transmit a message to all PEs in the 130 same VPN. An S-PMSI is a PMSI that enables a PE attached to a 131 particular MVPN to transmit a message to some of the PEs in the same 132 VPN. 134 Interchangeably, the term Multicast Virtual Routing and Forwarding 135 table (MVRF) and MVPN are used to refer to a particular Multicast VPN 136 instantiation on a particular PE. 138 As described in [RFC4382], each PE router maintains one default 139 forwarding table and "VPN Routing and Forwarding tables", or "VRFs". 141 Throughout this document, we will use the term "multicast VRF (MVRF)" 142 to refer a VRF that is configured to contain the multicast routing 143 information. 145 2. The Internet-Standard Management Framework 147 For a detailed overview of the documents that describe the current 148 Internet-Standard Management Framework, please refer to section 7 of 149 RFC 3410 [RFC3410]. 151 Managed objects are accessed via a virtual information store, termed 152 the Management Information Base or MIB. MIB objects are generally 153 accessed through the Simple Network Management Protocol (SNMP). 154 Objects in the MIB are defined using the mechanisms defined in the 155 Structure of Management Information (SMI). This memo specifies a MIB 156 module that is compliant to the SMIv2, which is described in STD 58, 157 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 158 [RFC2580]. 160 3. MCAST-VPN-MIB 162 This document defines MCAST-VPN-MIB, a MIB module for monitoring and/ 163 or configuring MVPNs on PEs. 165 3.1. Summary of MIB Module 167 The configuration and states specific to an MVPN include the 168 following information elements: 170 o C-multicast routing information exchange protocol (PIM or BGP) 172 o I-PMSI, S-PMSI and corresponding P-tunnels 174 o Mapping of C-multicast routing information to PMSI tunnels 176 To represent these information elements, MCAST-VPN-MIB defines eight 177 tables: mvpnGeneralTable, mvpnBgpGeneralTable, mvpnSpmsiConfigTable, 178 mvpnPmsiConfigTable, mvpnIpmsiTable, mvpnInterAsIpmsiTable, 179 mvpnSpmsiTable, mvpnMrouteTable. 181 The following four tables are designed for configuring MVPNs on PEs. 183 o mvpnGeneralTable 185 o mvpnBgpGeneralTable 187 o mvpnSpmsiConfigTable 188 o mvpnPmsiConfigTable 190 The following diagram shows the relationship among those four tables 191 use for configuration. Each box in the diagram represents a table, 192 and the label of each box corresponds to a table name. An arrow 193 indicates that one table has a pointer to a row in another table. 194 The entry in mvpnGeneralTable and mvpnSpmsiConfigTable has a pointer 195 to the row pertaining to the entry in the mvpnPmsiConfigTable. 197 +--------------+ 198 | mvpnBgp | 199 | GeneralTable | 200 +--------------+ +-------------------+ +-----------------+ 201 | mvpnGeneral | | mvpnPmsiConfig | | mvpnSpmsiConfig | 202 | Table | -> | Table | <- | Table | 203 +--------------+ +-------------------+ +-----------------+ 205 o mvpnGeneralTable 207 This table represents MVPNs that are configured on a PE. Each 208 entry in this table is created for each MVRF representing an 209 instance of MVPN. The entry represetns general configuration/ 210 states of the MVRF, including Inclusive PMSI (I-PMSI) 211 configuration. The MVPN represented by the entry in this table 212 must have the corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. 214 o mvpnBgpGeneralTable 216 This table augments the aformentioned mvpnGeneralTable. This 217 table contains BGP-MVPN specific managed objects. 219 o mvpnSpmsiConfigTable 221 This table contains managed objects necessary for configure 222 Selective PMSI (S-PMSI) associated with an MVRF on a PE. 224 o mvpnPmsiConfigTable 226 This table contains managed objects common to both I-PMSI and 227 S-PMSI configurations. Both I-PMSI configuration (in the entry in 228 mvpnGeneralTable) and S-PMSI configuration (in the entry in 229 mvpnSpmsiConfigTable) refer to an entry in this table. 231 The following four tables are designed for monitoring MVPNs on PEs. 233 o mvpnIpmsiTable 235 o mvpnInterAsIpmsiTable 236 o mvpnSpmsiTable 238 o mvpnMrouteTable 240 The following diagram shows the relationship among these four tables 241 and the l2l3VpnMcastPmsiTunnelAttributeTable defined separately in 242 L2L3-VPN-MCAST-MIB [I-D.ietf-bess-l2l3-vpn-mcast-mib]. The entry in 243 every table has a pointer to the row pertaining to the entry in the 244 l2l3VpnMcastPmsiTunnelAttributeTable. 246 +--------------+ +-------------------+ +-----------------+ 247 | mvpnIpmsi | -> | l2L3VpnMcastPmsi | <- | mvpnSpmsi | 248 | Table | | TunnelAttribute | | Table | 249 +--------------+ | Table | +-----------------+ 250 -> +-------------------+ 251 / ^ 252 / | 253 +--------------+ +-------------------+ 254 | mvpnInterAs | | mvpnMrouteTable | 255 | IpmsiTable | +-------------------+ 256 +--------------+ 258 o mvpnIpmsiTable 260 This table contains managed objects for monitoring all Intra-AS 261 I-PMSIs advertised and received by a PE. This table contains all 262 advertised and received Intra-AS I-PMSIs. With PIM-MVPN, it is 263 applicable only when BGP-Based Autodiscovery of MVPN Membership is 264 used. 266 o mvpnInterAsIpmsiTable 268 This table contains all advertised and received Inter-AS I-PMSIs. 269 With PIM-MVPN, it is applicable only when BGP-Based Autodiscovery 270 of MVPN Membership is used. 272 o mvpnSpmsiTable 274 This table contains managed objects for monitoring all S-PMSIs 275 advertised and received by a PE. 277 o mvpnMrouteTable 279 This table augments 280 ipMcastMIB.ipMcast.ipMcastRouteTable [RFC5132], for some MVPN 281 specific information. 283 o l2l3VpnMcastPmsiTunnelAttributeTable 284 An entry of this table corresponds to a PMSI Tunnel attribute and 285 is maintained by a PE router that advertises and receives the 286 attribute. Th entry in this table is referred by entries in 287 mvpnIpmsiTable, mvpnInterAsIpmsiTable, mvpnSpmsiTable, and 288 mvpnMrouteTable. 290 3.2. MIB Module Definitions 292 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 294 IMPORTS 295 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 296 Gauge32, Unsigned32, mib-2 -- [RFC2578] 297 FROM SNMPv2-SMI 299 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 300 FROM SNMPv2-CONF -- [RFC2580] 302 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 303 FROM SNMPv2-TC -- [RFC2579] 305 SnmpAdminString 306 FROM SNMP-FRAMEWORK-MIB -- [RFC2571] 308 InetAddress, InetAddressType 309 FROM INET-ADDRESS-MIB -- [RFC2851] 311 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 312 FROM MPLS-L3VPN-STD-MIB -- [RFC4382] 314 ipMcastRouteEntry 315 FROM IPMCAST-MIB -- [RFC5132] 317 L2L3VpnMcastProviderTunnelType 318 FROM L2L3-VPN-MCAST-TC-MIB; 320 mvpnMIB MODULE-IDENTITY 321 LAST-UPDATED "201706061200Z" -- 6th June 2017 12:00:00 GMT 322 ORGANIZATION "IETF BESS Working Group." 323 CONTACT-INFO 324 " Zhaohui Zhang 325 Juniper Networks, Inc. 326 10 Technology Park Drive 327 Westford, MA 01886 328 USA 329 Email: zzhang@juniper.net 331 Saud Asif 332 AT&T 333 C5-3D30 200 South Laurel Avenue 334 Middletown, NJ 07748 335 USA 336 Email: sasif@att.com 338 Andy Green 339 BT Design 21CN Converged Core IP & Data 340 01473 629360 Adastral Park, Martlesham Heath, 341 Ipswich IP5 3RE 342 UK 343 Email: andy.da.green@bt.com 345 Sameer Gulrajani 346 Cisco Systems 347 Tasman Drive San Jose, CA 95134 348 USA 349 Email: sameerg@cisco.com 351 Pradeep G. Jain 352 Alcatel-Lucent Inc 353 701 E Middlefield road Mountain view, CA 94043 354 USA 355 Email: pradeep.jain@alcatel-lucent.com 357 Hiroshi Tsunoda 358 Tohoku Institute of Technology 359 35-1, Yagiyama Kasumi-cho 360 Taihaku-ku, Sendai, 982-8577 361 Japan 362 Email: tsuno@m.ieice.org 364 Comments and discussion to bess@ietf.org" 366 DESCRIPTION 367 "This MIB contains managed object definitions for 368 multicast in BGP/MPLS IP VPNs defined by [RFC6513]. 369 Copyright (C) The Internet Society (2017)." 371 -- Revision history. 373 REVISION "201706061200Z" -- 6th June, 2017 374 DESCRIPTION 375 "Initial version, published as RFC XXXX." 377 -- RFC Ed. replace XXXX with actual RFC number and remove this note 379 ::= { mib-2 YYYY } 380 -- IANA Reg.: Please assign a value for "YYYY" under the 381 -- 'mib-2' subtree and record the assignment in the SMI 382 -- Numbers registry. 384 -- RFC Ed.: When the above assignment has been made, please 385 -- remove the above note 386 -- replace "YYYY" here with the assigned value and 387 -- remove this note. 389 -- Top level components of this MIB. 390 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 392 -- tables, scalars 393 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 395 -- conformance information 396 mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 398 -- mvpn Objects 399 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 400 mvpnGeneral OBJECT IDENTIFIER ::= { mvpnObjects 2 } 401 mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } 402 mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } 404 -- Scalar Objects 406 mvpnMvrfs OBJECT-TYPE 407 SYNTAX Gauge32 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The total number of MVRFs that are present on 412 this Provider Edge router (PE), whether 413 for IPv4, IPv6, or mLDP C-Multicast." 414 ::= { mvpnScalars 1 } 416 mvpnV4Mvrfs OBJECT-TYPE 417 SYNTAX Gauge32 418 MAX-ACCESS read-only 419 STATUS current 420 DESCRIPTION 421 "The number of MVRFs for IPv4 C-Multicast that are 422 present in this PE." 423 ::= { mvpnScalars 2 } 425 mvpnV6Mvrfs OBJECT-TYPE 426 SYNTAX Gauge32 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION 430 "The number of MVRFs for IPv6 C-Multicast that are 431 present in this PE." 432 ::= { mvpnScalars 3 } 434 mvpnPimV4Mvrfs OBJECT-TYPE 435 SYNTAX Gauge32 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The number of PIM-MVPN MVRFs for IPv4 C-Multicast that are 440 present in this PE." 441 ::= { mvpnScalars 4 } 443 mvpnPimV6Mvrfs OBJECT-TYPE 444 SYNTAX Gauge32 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The number of PIM-MVPN MVRFs for IPv6 C-Multicast that are 449 present in this PE." 450 ::= { mvpnScalars 5 } 452 mvpnBgpV4Mvrfs OBJECT-TYPE 453 SYNTAX Gauge32 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "The number of BGP-MVPN MVRFs for IPv4 C-Multicast that are 458 present in this PE." 459 ::= { mvpnScalars 6 } 461 mvpnBgpV6Mvrfs OBJECT-TYPE 462 SYNTAX Gauge32 463 MAX-ACCESS read-only 464 STATUS current 465 DESCRIPTION 466 "The number of BGP-MVPN MVRFs for IPv6 C-Multicast that are 467 present in this PE." 468 ::= { mvpnScalars 7 } 470 mvpnMldpMvrfs OBJECT-TYPE 471 SYNTAX Gauge32 472 MAX-ACCESS read-only 473 STATUS current 474 DESCRIPTION 475 "The number of BGP-MVPN MVRFs for mLDP C-Multicast that are 476 present in this PE." 477 ::= { mvpnScalars 8 } 479 mvpnNotificationEnable OBJECT-TYPE 480 SYNTAX TruthValue 481 MAX-ACCESS read-write 482 STATUS current 483 DESCRIPTION 484 "If this object is TRUE, then the generation of all 485 notifications defined in this MIB is enabled." 486 DEFVAL { false } 487 ::= { mvpnScalars 9 } 489 -- General MVRF Information Table 491 mvpnGeneralTable OBJECT-TYPE 492 SYNTAX SEQUENCE OF MvpnGeneralEntry 493 MAX-ACCESS not-accessible 494 STATUS current 495 DESCRIPTION 496 "This table specifies the general information about the MVRFs 497 present in this PE." 498 ::= { mvpnGeneral 1 } 500 mvpnGeneralEntry OBJECT-TYPE 501 SYNTAX MvpnGeneralEntry 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION 505 "An entry in this table is created for each MVRF in the 506 PE." 507 INDEX { 508 mplsL3VpnVrfName, 509 mvpnGenAddressFamily 510 } 511 ::= { mvpnGeneralTable 1 } 513 MvpnGeneralEntry ::= SEQUENCE { 514 mvpnGenAddressFamily INTEGER, 515 mvpnGenMvrfStatusChange INTEGER, 516 mvpnGenMvrfStatusChangeTime TimeStamp, 517 mvpnGenCmcastRouteProtocol INTEGER, 518 mvpnGenIpmsiConfig RowPointer, 519 mvpnGenInterAsPmsiConfig RowPointer, 520 mvpnGenUmhSelection INTEGER, 521 mvpnGenSiteType INTEGER, 522 mvpnGenSptnlLimit Unsigned32, 523 mvpnGenRowStatus RowStatus 524 } 526 mvpnGenAddressFamily OBJECT-TYPE 527 SYNTAX INTEGER { 528 ipv4(1), 529 ipv6(2) 530 } 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "The Address Family that this entry is for" 535 ::= { mvpnGeneralEntry 1 } 537 mvpnGenMvrfStatusChange OBJECT-TYPE 538 SYNTAX INTEGER { 539 createdMvrf(1), 540 deletedMvrf(2), 541 modifiedMvrfIpmsiConfig(3), 542 modifiedMvrfSpmsiConfig(4) 543 } 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "This object describes the last status change that 548 happened for the given MVRF. 550 createdMvrf(1): 551 indicates that the MVRF was created in the PE. 553 deletedMvrf(2): 554 indicates that the MVRF was deleted from the PE. 555 A row in this table will never have 556 mvpnGenMvrfStatusChange equal to deletedMvrf(2), 557 because in that case the row itself will be deleted 558 from the table. 559 This value for mvpnGenMvrfStatusChange is defined mainly 560 for use in mvpnMvrfStatusChange notification. 562 modifiedMvrfIpmsiConfig(3): 563 indicates that the I-PMSI for the MVRF was configured, 564 deleted or changed. 566 modifiedMvrfSpmsiConfig(4): 567 indicates that the S-PMSI for the MVRF was configured, 568 deleted or changed. 569 " 570 DEFVAL { createdMvrf } 571 ::= { mvpnGeneralEntry 2 } 573 mvpnGenMvrfStatusChangeTime OBJECT-TYPE 574 SYNTAX TimeStamp 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The time at which the last status change for the MVRF in 579 question took place. The last operational change is specified 580 by mvpnGenOperStatusChange. 581 " 582 ::= { mvpnGeneralEntry 3 } 584 mvpnGenCmcastRouteProtocol OBJECT-TYPE 585 SYNTAX INTEGER { 586 pim (1), 587 bgp (2) 588 } 589 MAX-ACCESS read-create 590 STATUS current 591 DESCRIPTION 592 "The protocol used to signal C-multicast states across the 593 provider core. 594 pim(1): PIM (PIM-MVPN). 595 bgp(2): BGP (BGP-MVPN). 596 " 597 ::= { mvpnGeneralEntry 4 } 599 mvpnGenIpmsiConfig OBJECT-TYPE 600 SYNTAX RowPointer 601 MAX-ACCESS read-create 602 STATUS current 603 DESCRIPTION 604 "This points to a row in mvpnPmsiConfigTable, 605 for I-PMSI configuration. 606 " 607 ::= { mvpnGeneralEntry 5 } 609 mvpnGenInterAsPmsiConfig OBJECT-TYPE 610 SYNTAX RowPointer 611 MAX-ACCESS read-create 612 STATUS current 613 DESCRIPTION 614 "This points to a row in mvpnPmsiConfigTable, 615 for inter-as I-PMSI configuration, in case of segmented 616 inter-as provider tunnels. 617 " 618 ::= { mvpnGeneralEntry 6 } 620 mvpnGenUmhSelection OBJECT-TYPE 621 SYNTAX INTEGER { 622 highestPeAddress (1), 623 cRootGroupHashing (2), 624 ucastUmhRoute (3) 625 } 626 MAX-ACCESS read-create 627 STATUS current 628 DESCRIPTION 629 "The UMH selection method for this mvpn, as specified in 630 section 5.1.3 of [RFC6513]: 631 highestPeAddress (1): PE with the highest address 632 cRootGroupHashing (2): hashing based on (c-root, c-group) 633 uncastUmhRoute (3): per ucast route towards c-root 634 " 635 ::= { mvpnGeneralEntry 7 } 637 mvpnGenSiteType OBJECT-TYPE 638 SYNTAX INTEGER { 639 senderReceiver (1), 640 receiverOnly (2), 641 senderOnly (3) 642 } 643 MAX-ACCESS read-create 644 STATUS current 645 DESCRIPTION 646 "Whether this site is a receiver-only site or not. 647 senderReceiver (1): both sender and receiver site. 648 receiverOnly (2): receiver-only site. 649 senderOnly (3): sender-only site. 650 " 651 ::= { mvpnGeneralEntry 8 } 653 mvpnGenSptnlLimit OBJECT-TYPE 654 SYNTAX Unsigned32 655 MAX-ACCESS read-create 656 STATUS current 657 DESCRIPTION 658 "The max number of selective provider tunnels this PE 659 allows for this mvpn." 660 ::= { mvpnGeneralEntry 9 } 662 mvpnGenRowStatus OBJECT-TYPE 663 SYNTAX RowStatus 664 MAX-ACCESS read-create 665 STATUS current 666 DESCRIPTION 667 "This is used to create or delete a row in this table." 669 ::= { mvpnGeneralEntry 10 } 671 -- General BGP-MVPN table 673 mvpnBgpGeneralTable OBJECT-TYPE 674 SYNTAX SEQUENCE OF MvpnBgpGeneralEntry 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "This table augments the mvpnGeneralTable and is for BGP-MVPN 679 specific information. 680 " 681 ::= { mvpnGeneral 2 } 683 mvpnBgpGeneralEntry OBJECT-TYPE 684 SYNTAX MvpnBgpGeneralEntry 685 MAX-ACCESS not-accessible 686 STATUS current 687 DESCRIPTION 688 "The mvpnBgpGeneralEntry matches and augments an 689 mvpnGeneralEntry for a BGP-MVPN instance, with BGP-MVPN 690 specific informatoin. 691 " 692 AUGMENTS { mvpnGeneralEntry } 693 ::= { mvpnBgpGeneralTable 1 } 695 MvpnBgpGeneralEntry ::= SEQUENCE { 696 mvpnBgpGenMode INTEGER, 697 mvpnBgpGenVrfRtImport MplsL3VpnRouteDistinguisher, 698 mvpnBgpGenSrcAs Unsigned32 699 } 701 mvpnBgpGenMode OBJECT-TYPE 702 SYNTAX INTEGER { 703 rptSpt (1), 704 sptOnly (2) 705 } 706 MAX-ACCESS read-write 707 STATUS current 708 DESCRIPTION 709 "For two different BGP-MVPN modes: 710 rptSpt(1): inter-site shared tree mode 711 sptOnly(2): inter-site source-only tree mode. 712 " 713 ::= { mvpnBgpGeneralEntry 1} 715 mvpnBgpGenVrfRtImport OBJECT-TYPE 716 SYNTAX MplsL3VpnRouteDistinguisher 717 MAX-ACCESS read-write 718 STATUS current 719 DESCRIPTION 720 "The VRF Route Import Extended Community that this PE 721 adds to unicast vpn routes that it advertises for this mvpn. 722 " 723 REFERENCE 724 "RFC4364, Section 4.2 725 RFC4382, Section 7 726 " 727 ::= { mvpnBgpGeneralEntry 2} 729 mvpnBgpGenSrcAs OBJECT-TYPE 730 SYNTAX Unsigned32 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "The Source AS number in Source AS Extended Community that this 735 PE adds to the unicast vpn routes that it advertises for 736 this mvpn. 737 " 738 ::= { mvpnBgpGeneralEntry 3} 740 -- PMSI Configuration Table 742 mvpnPmsiConfigTable OBJECT-TYPE 743 SYNTAX SEQUENCE OF MvpnPmsiConfigEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "This table specifies the configured PMSIs." 748 ::= { mvpnConfig 1 } 750 mvpnPmsiConfigEntry OBJECT-TYPE 751 SYNTAX MvpnPmsiConfigEntry 752 MAX-ACCESS not-accessible 753 STATUS current 754 DESCRIPTION 755 "An entry in this table is created for each PMSI configured 756 on this router. It can be referred to by either I-PMSI 757 configuration (in mvpnGeneralEntry) or S-PMSI configuration 758 (in mvpnSpmsiConfigEntry) 759 " 760 INDEX { 761 mvpnPmsiConfigTunnelType, 762 mvpnPmsiConfigTunnelAuxInfo, 763 mvpnPmsiConfigTunnelPimGroupAddressType, 764 mvpnPmsiConfigTunnelPimGroupAddress, 765 mvpnPmsiConfigTunnelOrTemplateName 766 } 767 ::= { mvpnPmsiConfigTable 1 } 769 MvpnPmsiConfigEntry ::= SEQUENCE { 770 mvpnPmsiConfigTunnelType 771 L2L3VpnMcastProviderTunnelType, 772 mvpnPmsiConfigTunnelAuxInfo Unsigned32, 773 mvpnPmsiConfigTunnelPimGroupAddressType 774 InetAddressType, 775 mvpnPmsiConfigTunnelPimGroupAddress 776 InetAddress, 777 mvpnPmsiConfigTunnelOrTemplateName 778 SnmpAdminString, 779 mvpnPmsiConfigEncapsType INTEGER, 780 mvpnPmsiConfigRowStatus RowStatus 781 } 783 mvpnPmsiConfigTunnelType OBJECT-TYPE 784 SYNTAX L2L3VpnMcastProviderTunnelType 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "Type of tunnel used to instantiate the PMSI." 789 ::= { mvpnPmsiConfigEntry 1 } 791 mvpnPmsiConfigTunnelAuxInfo OBJECT-TYPE 792 SYNTAX Unsigned32 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "Additional tunnel information depending on the value of 797 mvpnPmsiConfigTunnelType object. 799 pimSsm(3), pimAsm(4), pimBidir(5): 800 In case of S-PMSI, number of groups starting at 801 mvpnPmsiConfigTunnelPimGroupAddress. 802 This allows a range of PIM provider tunnel 803 group addresses to be specified in S-PMSI case. 804 In I-PMSI case, it must be 1. 806 rsvpP2mp(1): 807 1 for statically specified rsvp-p2mp tunnel 808 2 for dynamically created rsvp-p2mp tunnel 810 ingressReplication(6): 811 1 for using any existing p2p/mp2p LSP 812 2 for dynamically creating new p2p LSP 814 " 816 ::= { mvpnPmsiConfigEntry 2 } 818 mvpnPmsiConfigTunnelPimGroupAddressType OBJECT-TYPE 819 SYNTAX InetAddressType 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 "In case of PIM provider tunnel, the type of tunnel address." 824 ::= { mvpnPmsiConfigEntry 3 } 826 mvpnPmsiConfigTunnelPimGroupAddress OBJECT-TYPE 827 SYNTAX InetAddress 828 MAX-ACCESS not-accessible 829 STATUS current 830 DESCRIPTION 831 "In case of PIM provider tunnel, the provider tunnel address." 832 ::= { mvpnPmsiConfigEntry 4 } 834 mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE 835 SYNTAX SnmpAdminString 836 MAX-ACCESS not-accessible 837 STATUS current 838 DESCRIPTION 839 "The tunnel name or template name used to create tunnels. 840 The value of this object depends on the values of 841 mvpnPmsiConfigTunnelType and mvpnPmsiConfigTunnelAuxInfo 842 objects: 844 dynamically created rsvp-p2mp tunnel: template name 845 statically specified rsvp-p2mp tunnel: tunnel name 846 ingress-replication using 847 dynamically created LSPs: template name 848 other: null 849 " 850 ::= { mvpnPmsiConfigEntry 5 } 852 mvpnPmsiConfigEncapsType OBJECT-TYPE 853 SYNTAX INTEGER { 854 greIp (1), 855 ipIp (2), 856 mpls (3) 857 } 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "The encapsulation type to be used, in case of PIM tunnel or 862 ingress-replication. 863 " 864 ::= { mvpnPmsiConfigEntry 6 } 866 mvpnPmsiConfigRowStatus OBJECT-TYPE 867 SYNTAX RowStatus 868 MAX-ACCESS read-create 869 STATUS current 870 DESCRIPTION 871 "Used to create/modify/delete a row in this table." 872 ::= { mvpnPmsiConfigEntry 7 } 874 -- S-PMSI configuration table 876 mvpnSpmsiConfigTable OBJECT-TYPE 877 SYNTAX SEQUENCE OF MvpnSpmsiConfigEntry 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "This table specifies S-PMSI configuration." 882 ::= { mvpnConfig 2 } 884 mvpnSpmsiConfigEntry OBJECT-TYPE 885 SYNTAX MvpnSpmsiConfigEntry 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "An entry is created for each S-PMSI configuration." 890 INDEX { 891 mplsL3VpnVrfName, 892 mvpnSpmsiConfigCmcastAddressType, 893 mvpnSpmsiConfigCmcastGroupAddress, 894 mvpnSpmsiConfigCmcastGroupPrefixLen, 895 mvpnSpmsiConfigCmcastSourceAddress, 896 mvpnSpmsiConfigCmcastSourcePrefixLen 897 } 898 ::= { mvpnSpmsiConfigTable 1 } 900 MvpnSpmsiConfigEntry ::= SEQUENCE { 901 mvpnSpmsiConfigCmcastAddressType InetAddressType, 902 mvpnSpmsiConfigCmcastGroupAddress InetAddress, 903 mvpnSpmsiConfigCmcastGroupPrefixLen Unsigned32, 904 mvpnSpmsiConfigCmcastSourceAddress InetAddress, 905 mvpnSpmsiConfigCmcastSourcePrefixLen Unsigned32, 906 mvpnSpmsiConfigThreshold Unsigned32, 907 mvpnSpmsiConfigPmsiPointer RowPointer, 908 mvpnSpmsiConfigRowStatus RowStatus 909 } 910 mvpnSpmsiConfigCmcastAddressType OBJECT-TYPE 911 SYNTAX InetAddressType 912 MAX-ACCESS not-accessible 913 STATUS current 914 DESCRIPTION 915 "Type of C-multicast address" 916 ::= { mvpnSpmsiConfigEntry 1 } 918 mvpnSpmsiConfigCmcastGroupAddress OBJECT-TYPE 919 SYNTAX InetAddress 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "C-multicast group address" 924 ::= { mvpnSpmsiConfigEntry 2 } 926 mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE 927 SYNTAX Unsigned32 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "C-multicast group address prefix length. 932 A group 0 (or ::0) with prefix length 32 (or 128) 933 indicates wildcard group, while a group 0 (or ::0) 934 with prefix length 0 indicates any group. 935 " 936 ::= { mvpnSpmsiConfigEntry 3 } 938 mvpnSpmsiConfigCmcastSourceAddress OBJECT-TYPE 939 SYNTAX InetAddress 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "C-multicast source address" 944 ::= { mvpnSpmsiConfigEntry 4 } 946 mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE 947 SYNTAX Unsigned32 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 "C-multicast source address prefix length. 952 A source 0 (or ::0) with prefix length 32 (or 128) 953 indicates a wildcard source, while a source 0 (or ::0) 954 with prefix length 0 indicates any source. 955 " 956 ::= { mvpnSpmsiConfigEntry 5 } 958 mvpnSpmsiConfigThreshold OBJECT-TYPE 959 SYNTAX Unsigned32 (0..4294967295) 960 UNITS "kilobits per second" 961 MAX-ACCESS read-create 962 STATUS current 963 DESCRIPTION 964 "The bandwidth threshold value which when exceeded for a 965 multicast routing entry in the given MVRF, triggers usage 966 of S-PMSI. 967 " 968 ::= { mvpnSpmsiConfigEntry 6 } 970 mvpnSpmsiConfigPmsiPointer OBJECT-TYPE 971 SYNTAX RowPointer 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "This points to a row in mvpnPmsiConfigTable, 976 to specify tunnel attributes. 977 " 978 ::= { mvpnSpmsiConfigEntry 7 } 980 mvpnSpmsiConfigRowStatus OBJECT-TYPE 981 SYNTAX RowStatus 982 MAX-ACCESS read-create 983 STATUS current 984 DESCRIPTION 985 "Used to create/modify/delete a row in this table." 986 ::= { mvpnSpmsiConfigEntry 8 } 988 -- Table of intra-as I-PMSIs advertised/received 990 mvpnIpmsiTable OBJECT-TYPE 991 SYNTAX SEQUENCE OF MvpnIpmsiEntry 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "This table is for all advertised/received I-PMSI 996 advertisements. 997 " 998 ::= { mvpnStates 1 } 1000 mvpnIpmsiEntry OBJECT-TYPE 1001 SYNTAX MvpnIpmsiEntry 1002 MAX-ACCESS not-accessible 1003 STATUS current 1004 DESCRIPTION 1005 "An entry in this table corresponds to an I-PMSI 1006 advertisement that is advertised/received on this router. 1007 This represents all the sender PEs in the MVPN, 1008 with the provider tunnel they use to send traffic. 1009 " 1010 INDEX { 1011 mplsL3VpnVrfName, 1012 mvpnIpmsiAfi, 1013 mvpnIpmsiRD, 1014 mvpnIpmsiOrigAddrType, 1015 mvpnIpmsiOrigAddress 1016 } 1017 ::= { mvpnIpmsiTable 1 } 1019 MvpnIpmsiEntry ::= SEQUENCE { 1020 mvpnIpmsiAfi INTEGER, 1021 mvpnIpmsiRD MplsL3VpnRouteDistinguisher, 1022 mvpnIpmsiOrigAddrType InetAddressType, 1023 mvpnIpmsiOrigAddress InetAddress, 1024 mvpnIpmsiUpTime TimeInterval, 1025 mvpnIpmsiAttribute RowPointer 1026 } 1028 mvpnIpmsiAfi OBJECT-TYPE 1029 SYNTAX INTEGER { 1030 ipv4(1), 1031 ipv6(2) 1032 } 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "The address family this I-PMSI is for." 1037 ::= { mvpnIpmsiEntry 1 } 1039 mvpnIpmsiRD OBJECT-TYPE 1040 SYNTAX MplsL3VpnRouteDistinguisher 1041 MAX-ACCESS not-accessible 1042 STATUS current 1043 DESCRIPTION 1044 "The Route Distinguisher in this I-PMSI." 1045 ::= { mvpnIpmsiEntry 2 } 1047 mvpnIpmsiOrigAddrType OBJECT-TYPE 1048 SYNTAX InetAddressType 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "The Internet address type of mvpnIpmsiOrigAddress." 1053 ::= { mvpnIpmsiEntry 3 } 1055 mvpnIpmsiOrigAddress OBJECT-TYPE 1056 SYNTAX InetAddress 1057 MAX-ACCESS not-accessible 1058 STATUS current 1059 DESCRIPTION 1060 "The BGP address of the PE that originated the I-PMSI." 1061 ::= { mvpnIpmsiEntry 4 } 1063 mvpnIpmsiUpTime OBJECT-TYPE 1064 SYNTAX TimeInterval 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The time since this I-PMSI 1069 was first advertised/received by the PE. 1070 " 1071 ::= { mvpnIpmsiEntry 5 } 1073 mvpnIpmsiAttribute OBJECT-TYPE 1074 SYNTAX RowPointer 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 1079 ::= { mvpnIpmsiEntry 6 } 1081 -- Table of inter-as I-PMSIs advertised/received 1083 mvpnInterAsIpmsiTable OBJECT-TYPE 1084 SYNTAX SEQUENCE OF MvpnInterAsIpmsiEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "This table is for all advertised/received inter-as I-PMSI 1089 advertisements." 1090 ::= { mvpnStates 2 } 1092 mvpnInterAsIpmsiEntry OBJECT-TYPE 1093 SYNTAX MvpnInterAsIpmsiEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "An entry in this table corresponds to an inter-as I-PMSI 1098 advertisement that is advertised/received on this router. 1099 This represents all the ASes in the MVPN, 1100 with the provider tunnel used to send traffic to. 1101 " 1102 INDEX { 1103 mplsL3VpnVrfName, 1104 mvpnInterAsIpmsiAfi, 1105 mvpnInterAsIpmsiRD, 1106 mvpnInterAsIpmsiSrcAs 1107 } 1108 ::= { mvpnInterAsIpmsiTable 1 } 1110 MvpnInterAsIpmsiEntry ::= SEQUENCE { 1111 mvpnInterAsIpmsiAfi INTEGER, 1112 mvpnInterAsIpmsiRD MplsL3VpnRouteDistinguisher, 1113 mvpnInterAsIpmsiSrcAs Unsigned32, 1114 mvpnInterAsIpmsiAttribute RowPointer 1115 } 1117 mvpnInterAsIpmsiAfi OBJECT-TYPE 1118 SYNTAX INTEGER { 1119 ipv4(1), 1120 ipv6(2) 1121 } 1122 MAX-ACCESS not-accessible 1123 STATUS current 1124 DESCRIPTION 1125 "The address family this I-PMSI is for." 1126 ::= { mvpnInterAsIpmsiEntry 1 } 1128 mvpnInterAsIpmsiRD OBJECT-TYPE 1129 SYNTAX MplsL3VpnRouteDistinguisher 1130 MAX-ACCESS not-accessible 1131 STATUS current 1132 DESCRIPTION 1133 "The Route Distinguisher in this inter-as I-PMSI." 1134 ::= { mvpnInterAsIpmsiEntry 2 } 1136 mvpnInterAsIpmsiSrcAs OBJECT-TYPE 1137 SYNTAX Unsigned32 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "The source-as in this inter-as I-PMSI." 1142 ::= { mvpnInterAsIpmsiEntry 3 } 1144 mvpnInterAsIpmsiAttribute OBJECT-TYPE 1145 SYNTAX RowPointer 1146 MAX-ACCESS read-only 1147 STATUS current 1148 DESCRIPTION 1149 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 1150 ::= { mvpnInterAsIpmsiEntry 4 } 1152 -- Table of S-PMSIs advertised/received 1154 mvpnSpmsiTable OBJECT-TYPE 1155 SYNTAX SEQUENCE OF MvpnSpmsiEntry 1156 MAX-ACCESS not-accessible 1157 STATUS current 1158 DESCRIPTION 1159 "This table has information about the S-PMSIs sent/received 1160 by a PE. 1161 " 1162 ::= { mvpnStates 3 } 1164 mvpnSpmsiEntry OBJECT-TYPE 1165 SYNTAX MvpnSpmsiEntry 1166 MAX-ACCESS not-accessible 1167 STATUS current 1168 DESCRIPTION 1169 "An entry in this table is created or updated for each S-PMSI 1170 advertised/received in a particular MVRF. 1171 " 1172 INDEX { 1173 mplsL3VpnVrfName, 1174 mvpnSpmsiCmcastAddrType, 1175 mvpnSpmsiCmcastGroup, 1176 mvpnSpmsiCmcastGroupPrefixLen, 1177 mvpnSpmsiCmcastSource, 1178 mvpnSpmsiCmcastSourcePrefixLen, 1179 mvpnSpmsiOrigAddrType, 1180 mvpnSpmsiOrigAddress 1181 } 1182 ::= { mvpnSpmsiTable 1 } 1184 MvpnSpmsiEntry ::= SEQUENCE { 1185 mvpnSpmsiCmcastAddrType InetAddressType, 1186 mvpnSpmsiCmcastGroup InetAddress, 1187 mvpnSpmsiCmcastGroupPrefixLen Unsigned32, 1188 mvpnSpmsiCmcastSource InetAddress, 1189 mvpnSpmsiCmcastSourcePrefixLen Unsigned32, 1190 mvpnSpmsiOrigAddrType InetAddressType, 1191 mvpnSpmsiOrigAddress InetAddress, 1192 mvpnSpmsiTunnelAttribute RowPointer, 1193 mvpnSpmsiUpTime TimeInterval, 1194 mvpnSpmsiExpTime TimeInterval, 1195 mvpnSpmsiRefCnt Unsigned32 1196 } 1198 mvpnSpmsiCmcastAddrType OBJECT-TYPE 1199 SYNTAX InetAddressType 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "The Internet address type of mvpnSpmsiCmcastGroup/Source." 1204 ::= { mvpnSpmsiEntry 1 } 1206 mvpnSpmsiCmcastGroup OBJECT-TYPE 1207 SYNTAX InetAddress 1208 MAX-ACCESS not-accessible 1209 STATUS current 1210 DESCRIPTION 1211 "S-PMSI C-multicast group address. 1212 If it is 0 (or ::0), this is a wildcard group, 1213 and mvpnSpmsiCmcastGroupPrefixLen must be 32 (or 128). 1214 " 1215 ::= { mvpnSpmsiEntry 2 } 1217 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 1218 SYNTAX Unsigned32 1219 MAX-ACCESS not-accessible 1220 STATUS current 1221 DESCRIPTION 1222 "S-PMSI C-multicast group address prefix length." 1223 ::= { mvpnSpmsiEntry 3 } 1225 mvpnSpmsiCmcastSource OBJECT-TYPE 1226 SYNTAX InetAddress 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "S-PMSI C-multicast source address 1231 If it is 0 (or ::0), this is a wildcard source, 1232 and mvpnSpmsiCmcastSourcePrefixLen must be 32 (or 128). 1233 " 1234 ::= { mvpnSpmsiEntry 4 } 1236 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 1237 SYNTAX Unsigned32 1238 MAX-ACCESS not-accessible 1239 STATUS current 1240 DESCRIPTION 1241 "S-PMSI C-multicast source address prefix length." 1242 ::= { mvpnSpmsiEntry 5 } 1244 mvpnSpmsiOrigAddrType OBJECT-TYPE 1245 SYNTAX InetAddressType 1246 MAX-ACCESS not-accessible 1247 STATUS current 1248 DESCRIPTION 1249 "The Internet address type of mvpnSpmsiOrigAddress." 1250 ::= { mvpnSpmsiEntry 6 } 1252 mvpnSpmsiOrigAddress OBJECT-TYPE 1253 SYNTAX InetAddress 1254 MAX-ACCESS not-accessible 1255 STATUS current 1256 DESCRIPTION 1257 "The BGP address of the PE that originated the S-PMSI." 1258 ::= { mvpnSpmsiEntry 7 } 1260 mvpnSpmsiTunnelAttribute OBJECT-TYPE 1261 SYNTAX RowPointer 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "A row pointer to the l2L3VpnMcastPmsiTunnelAttributeTable" 1266 ::= { mvpnSpmsiEntry 8 } 1268 mvpnSpmsiUpTime OBJECT-TYPE 1269 SYNTAX TimeInterval 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The time since this S-PMSI 1274 was first advertised/received by the PE. 1275 " 1276 ::= { mvpnSpmsiEntry 9 } 1278 mvpnSpmsiExpTime OBJECT-TYPE 1279 SYNTAX TimeInterval 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "For UDP-based S-PMSI signaling for PIM-MVPN, 1284 the amount of time remaining before this 1285 received S-PMSI Join Message expires, 1286 or the next S-PMSI Join Message refresh is to be 1287 advertised again from the PE. 1288 Otherwise, it is 0. 1289 " 1290 ::= { mvpnSpmsiEntry 10 } 1292 mvpnSpmsiRefCnt OBJECT-TYPE 1293 SYNTAX Unsigned32 1294 MAX-ACCESS read-only 1295 STATUS current 1296 DESCRIPTION 1297 "The number of c-multicast routes that are mapped to 1298 this S-PMSI. 1299 " 1300 ::= { mvpnSpmsiEntry 11 } 1302 -- Table of multicast routes in an MVPN 1304 mvpnMrouteTable OBJECT-TYPE 1305 SYNTAX SEQUENCE OF MvpnMrouteEntry 1306 MAX-ACCESS not-accessible 1307 STATUS current 1308 DESCRIPTION 1309 "This table augments ipMcastRouteTable, to provide some MVPN 1310 specific information. 1311 " 1312 ::= { mvpnStates 4 } 1314 mvpnMrouteEntry OBJECT-TYPE 1315 SYNTAX MvpnMrouteEntry 1316 MAX-ACCESS not-accessible 1317 STATUS current 1318 DESCRIPTION 1319 "The mvpnMrouteEntry matches and augments an ipMcastRouteEntry, 1320 with MVPN specific information, such as PMSI used. 1321 " 1322 AUGMENTS { ipMcastRouteEntry } 1323 ::= { mvpnMrouteTable 1 } 1325 MvpnMrouteEntry ::= SEQUENCE { 1326 mvpnMroutePmsiPointer RowPointer, 1327 mvpnMrouteNumberOfLocalReplication Unsigned32, 1328 mvpnMrouteNumberOfRemoteReplication Unsigned32 1329 } 1331 mvpnMroutePmsiPointer OBJECT-TYPE 1332 SYNTAX RowPointer 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "The I-PMSI or S-PMSI this C-multicast route is using. 1337 This is important because an implementation may not have an 1338 interface corresponding to a provider tunnel, 1339 that can be used in ipMcastRouteNextHopEntry. 1340 " 1341 ::= { mvpnMrouteEntry 1 } 1343 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1344 SYNTAX Unsigned32 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "Number of replications for local receivers. 1349 For example, if an ingress PE needs to send traffic out of 1350 N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication 1351 is N. 1352 " 1353 ::= { mvpnMrouteEntry 2 } 1355 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1356 SYNTAX Unsigned32 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "Number of local replications for remote PEs. For example, 1361 if the number of remote PEs that need to receive traffic is N, 1362 then mvpnMrouteNumberOfRemoteReplication is N in case of 1363 Ingress Replication, but may be less than N in case of RSVP-TE 1364 or mLDP P2MP tunnels, depending on the actual number of 1365 replications the PE needs do. 1366 " 1367 ::= { mvpnMrouteEntry 3 } 1369 -- MVPN Notifications 1371 mvpnMvrfChange NOTIFICATION-TYPE 1372 OBJECTS { 1373 mvpnGenMvrfStatusChange 1374 } 1375 STATUS current 1376 DESCRIPTION 1377 "A mvpnMvrfChange notification signifies a change about 1378 a MVRF in the PE. The change event can be creation of 1379 the MVRF, deletion of the MVRF or an update on the I-PMSI 1380 or S-PMSI configuration of the MVRF. The change event 1381 is indicated by mvpnGenMvrfStatusChange embedded in 1382 the notification. The user can then query 1383 mvpnGeneralTable, and/or mvpnSpmsiConfigTable to 1384 get the details of the change as necessary. 1386 Note: Since the creation of a MVRF is often followed by 1387 configuration of I-PMSI and/or S-PMSIs for the MVRF, 1388 more than one (three at most) notifications for a MVRF may 1389 be generated serially, and it is really not necessary to 1390 generate all three of them. An agent may choose to generate a 1391 notification for the last event only, that is for S-PMSI 1392 configuration. 1394 Similarly, deletion of I-PMSI and S-PMSI configuration on a 1395 MVRF happens before a MVRF is deleted and it is recommended 1396 that the agent send the notification for MVRF deletion 1397 event only. 1398 " 1399 ::= { mvpnNotifications 1 } 1401 -- MVPN MIB Conformance Information 1403 mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } 1404 mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } 1406 -- Compliance Statements 1408 mvpnModuleFullCompliance MODULE-COMPLIANCE 1409 STATUS current 1410 DESCRIPTION 1411 "Compliance statement for agents that provide full support 1412 for the MCAST-VPN-MIB 1413 " 1414 MODULE -- this module 1415 MANDATORY-GROUPS { 1416 mvpnScalarGroup, 1417 mvpnGeneralGroup, 1418 mvpnPmsiConfigGroup, 1419 mvpnSpmsiConfigGroup, 1420 mvpnSpmsiGroup, 1421 mvpnMrouteGroup, 1422 mvpnNotificationGroup 1423 } 1425 GROUP mvpnIpmsiGroup 1426 DESCRIPTION 1427 "This group is mandatory for systems that support 1428 BGP signaling for I-PMSI. 1429 " 1431 GROUP mvpnInterAsIpmsiGroup 1432 DESCRIPTION 1433 "This group is mandatory for systems that support 1434 Inter-AS Segmented I-PMSI. 1435 " 1437 GROUP mvpnBgpGeneralGroup 1438 DESCRIPTION 1439 "This group is mandatory for systems that support 1440 BGP-MVPN. 1441 " 1443 GROUP mvpnOptionalGroup 1444 DESCRIPTION 1445 "This group is optional. 1446 " 1448 ::= { mvpnCompliances 1 } 1450 mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE 1451 STATUS current 1452 DESCRIPTION "Compliance requirement for implementations that 1453 only provide read-only support for MCAST-VPN-MIB. 1454 Such devices can then be monitored but cannot be 1455 configured using this MIB module. 1456 " 1457 MODULE -- this module 1458 MANDATORY-GROUPS { 1459 mvpnScalarGroup, 1460 mvpnGeneralGroup, 1461 mvpnPmsiConfigGroup, 1462 mvpnSpmsiConfigGroup, 1463 mvpnSpmsiGroup, 1464 mvpnMrouteGroup, 1465 mvpnNotificationGroup 1466 } 1468 GROUP mvpnIpmsiGroup 1469 DESCRIPTION 1470 "This group is mandatory for systems that support 1471 BGP signaling for I-PMSI. 1472 " 1474 GROUP mvpnInterAsIpmsiGroup 1475 DESCRIPTION 1476 "This group is mandatory for systems that support 1477 Inter-AS Segmented I-PMSI. 1478 " 1480 GROUP mvpnBgpGeneralGroup 1481 DESCRIPTION 1482 "This group is mandatory for systems that support 1483 BGP-MVPN. 1484 " 1486 GROUP mvpnOptionalGroup 1487 DESCRIPTION 1488 "This group is optional. 1489 " 1491 OBJECT mvpnNotificationEnable 1492 MIN-ACCESS read-only 1493 DESCRIPTION "Write access is not required." 1495 OBJECT mvpnGenCmcastRouteProtocol 1496 MIN-ACCESS read-only 1497 DESCRIPTION "Write access is not required." 1499 OBJECT mvpnGenIpmsiConfig 1500 MIN-ACCESS read-only 1501 DESCRIPTION "Write access is not required." 1503 OBJECT mvpnGenInterAsPmsiConfig 1504 MIN-ACCESS read-only 1505 DESCRIPTION "Write access is not required." 1507 OBJECT mvpnGenUmhSelection 1508 MIN-ACCESS read-only 1509 DESCRIPTION "Write access is not required." 1511 OBJECT mvpnGenSiteType 1512 MIN-ACCESS read-only 1513 DESCRIPTION "Write access is not required." 1515 OBJECT mvpnGenSptnlLimit 1516 MIN-ACCESS read-only 1517 DESCRIPTION "Write access is not required." 1519 OBJECT mvpnPmsiConfigEncapsType 1520 MIN-ACCESS read-only 1521 DESCRIPTION "Write access is not required." 1523 OBJECT mvpnSpmsiConfigThreshold 1524 MIN-ACCESS read-only 1525 DESCRIPTION "Write access is not required." 1527 OBJECT mvpnSpmsiConfigPmsiPointer 1528 MIN-ACCESS read-only 1529 DESCRIPTION "Write access is not required." 1531 OBJECT mvpnGenRowStatus 1532 SYNTAX RowStatus { active(1) } 1533 MIN-ACCESS read-only 1534 DESCRIPTION "Write access is not required." 1535 OBJECT mvpnPmsiConfigRowStatus 1536 SYNTAX RowStatus { active(1) } 1537 MIN-ACCESS read-only 1538 DESCRIPTION "Write access is not required." 1540 OBJECT mvpnSpmsiConfigRowStatus 1541 SYNTAX RowStatus { active(1) } 1542 MIN-ACCESS read-only 1543 DESCRIPTION "Write access is not required." 1545 ::= { mvpnCompliances 2 } 1547 -- units of conformance 1549 mvpnScalarGroup OBJECT-GROUP 1550 OBJECTS { 1551 mvpnMvrfs, 1552 mvpnV4Mvrfs, 1553 mvpnV6Mvrfs, 1554 mvpnPimV4Mvrfs, 1555 mvpnPimV6Mvrfs, 1556 mvpnBgpV4Mvrfs, 1557 mvpnBgpV6Mvrfs, 1558 mvpnMldpMvrfs, 1559 mvpnNotificationEnable 1560 } 1561 STATUS current 1562 DESCRIPTION 1563 "These objects are used to monitor/manage 1564 global MVPN parameters. 1565 " 1566 ::= { mvpnGroups 1 } 1568 mvpnGeneralGroup OBJECT-GROUP 1569 OBJECTS { 1570 mvpnGenMvrfStatusChange, 1571 mvpnGenMvrfStatusChangeTime, 1572 mvpnGenCmcastRouteProtocol, 1573 mvpnGenIpmsiConfig, 1574 mvpnGenInterAsPmsiConfig, 1575 mvpnGenUmhSelection, 1576 mvpnGenSiteType, 1577 mvpnGenSptnlLimit, 1578 mvpnGenRowStatus 1579 } 1580 STATUS current 1581 DESCRIPTION 1582 "These objects are used to monitor/manage 1583 per-VRF MVPN parameters. 1584 " 1585 ::= { mvpnGroups 2 } 1587 mvpnPmsiConfigGroup OBJECT-GROUP 1588 OBJECTS { 1589 mvpnPmsiConfigEncapsType, 1590 mvpnPmsiConfigRowStatus 1591 } 1592 STATUS current 1593 DESCRIPTION 1594 "These objects are used to monitor/manage 1595 PMSI tunnel configurations. 1596 " 1597 ::= { mvpnGroups 3 } 1599 mvpnSpmsiConfigGroup OBJECT-GROUP 1600 OBJECTS { 1601 mvpnSpmsiConfigThreshold, 1602 mvpnSpmsiConfigPmsiPointer, 1603 mvpnSpmsiConfigRowStatus 1604 } 1605 STATUS current 1606 DESCRIPTION 1607 "These objects are used to monitor/manage 1608 S-PMSI configurations. 1609 " 1610 ::= { mvpnGroups 4 } 1612 mvpnIpmsiGroup OBJECT-GROUP 1613 OBJECTS { 1614 mvpnIpmsiUpTime, 1615 mvpnIpmsiAttribute 1616 } 1617 STATUS current 1618 DESCRIPTION 1619 "These objects are used to monitor/manage 1620 Intra-AS I-PMSI attributes. 1621 " 1622 ::= { mvpnGroups 5 } 1624 mvpnInterAsIpmsiGroup OBJECT-GROUP 1625 OBJECTS { 1626 mvpnInterAsIpmsiAttribute 1627 } 1628 STATUS current 1629 DESCRIPTION 1630 "These objects are used to monitor/manage 1631 Inter-AS I-PMSI attributes. 1632 " 1633 ::= { mvpnGroups 6 } 1635 mvpnSpmsiGroup OBJECT-GROUP 1636 OBJECTS { 1637 mvpnSpmsiTunnelAttribute, 1638 mvpnSpmsiUpTime, 1639 mvpnSpmsiExpTime, 1640 mvpnSpmsiRefCnt 1641 } 1642 STATUS current 1643 DESCRIPTION 1644 "These objects are used to monitor/manage 1645 S-PMSI attributes. 1646 " 1647 ::= { mvpnGroups 7 } 1649 mvpnMrouteGroup OBJECT-GROUP 1650 OBJECTS { 1651 mvpnMrouteNumberOfLocalReplication, 1652 mvpnMrouteNumberOfRemoteReplication 1653 } 1654 STATUS current 1655 DESCRIPTION 1656 "These objects are used to monitor/manage 1657 VPN multicast forwarding states. 1658 " 1659 ::= { mvpnGroups 8 } 1661 mvpnBgpGeneralGroup OBJECT-GROUP 1662 OBJECTS { 1663 mvpnBgpGenMode, 1664 mvpnBgpGenVrfRtImport, 1665 mvpnBgpGenSrcAs 1666 } 1667 STATUS current 1668 DESCRIPTION 1669 "These objects are used to monitor/manage BGP-MVPN." 1670 ::= { mvpnGroups 9 } 1672 mvpnOptionalGroup OBJECT-GROUP 1673 OBJECTS { 1674 mvpnMroutePmsiPointer 1675 } 1676 STATUS current 1677 DESCRIPTION 1678 "Support of these object is not required." 1679 ::= { mvpnGroups 10 } 1681 mvpnNotificationGroup NOTIFICATION-GROUP 1682 NOTIFICATIONS { 1683 mvpnMvrfChange 1684 } 1685 STATUS current 1686 DESCRIPTION 1687 "Objects required for MVPN notifications." 1688 ::= { mvpnGroups 11 } 1690 END 1692 4. Security Considerations 1694 This MIB contains some read-only objects that may be deemed senstive 1695 by some though perhaps not all operators. It also contains some 1696 read- write objects, whose setting will change the device's behavior 1697 related to MVPN. Appropriate security procedures related to SNMP in 1698 general but not specific to this MIB need to be implemented by 1699 concerned operators. 1701 There are a number of management objects defined in this MIB module 1702 with a MAX-ACCESS clause of read-write and/or read-create. Such 1703 objects may be considered sensitive or vulnerable in some network 1704 environments. The support for SET operations in a non-secure 1705 environment without proper protection opens devices to attack. These 1706 are the tables and objects and their sensitivity/vulnerability: 1708 o mvpnNotificationEnable, mvpnGenCmcastRouteProtocol, 1709 mvpnGenIpmsiConfig, mvpnGenInterAsPmsiConfig, mvpnGenUmhSelection, 1710 mvpnGenSiteType, mvpnGenSptnlLimit, mvpnBgpGenMode, 1711 mvpnBgpGenVrfRtImport, mvpnPmsiConfigEncapsType, 1712 mvpnSpmsiConfigThreshold, mvpnSpmsiConfigPmsiPointer 1714 o mvpnGenRowStatus, mvpnPmsiConfigRowStatus, 1715 mvpnSpmsiConfigRowStatus 1717 Some of the readable objects in this MIB module (i.e., objects with a 1718 MAX-ACCESS other than not-accessible) may be considered sensitive or 1719 vulnerable in some network environments. It is thus important to 1720 control even GET and/or NOTIFY access to these objects and possibly 1721 to even encrypt the values of these objects when sending them over 1722 the network via SNMP. These are the tables and objects and their 1723 sensitivity/vulnerability: 1725 o [TBD] 1726 SNMP versions prior to SNMPv3 did not include adequate security. 1727 Even if the network itself is secure (for example by using IPsec), 1728 there is no control as to who on the secure network is allowed to 1729 access and GET/SET (read/change/create/delete) the objects in this 1730 MIB module. 1732 Implementations SHOULD provide the security features described by the 1733 SNMPv3 framework (see [RFC3410]), and implementations claiming 1734 compliance to the SNMPv3 standard MUST include full support for 1735 authentication and privacy via the User-based Security Model (USM) 1736 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1737 MAY also provide support for the Transport Security Model (TSM) 1738 [RFC5591] in combination with a secure transport such as SSH 1739 [RFC5592] or TLS/DTLS [RFC6353]. 1741 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1742 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1743 enable cryptographic security. It is then a customer/operator 1744 responsibility to ensure that the SNMP entity giving access to an 1745 instance of this MIB module is properly configured to give access to 1746 the objects only to those principals (users) that have legitimate 1747 rights to indeed GET or SET (change/create/delete) them. 1749 5. IANA Considerations 1751 IANA is requested to root MIB objects in the MIB module contained in 1752 this document under the mib-2 subtree. 1754 6. Acknowledgement 1756 Some of the text has been taken almost verbatim from 1757 [I-D.svaidya-mcast-vpn-mib]. We would like to thank Yakov Rekhter, 1758 Jeffrey Haas, Huajin Jeng, Durga Prasad Velamuri for their helpful 1759 comments. 1761 7. References 1763 7.1. Normative References 1765 [I-D.ietf-bess-l2l3-vpn-mcast-mib] 1766 Zhang, Z. and H. Tsunoda, "L2L3 VPN Multicast MIB", draft- 1767 ietf-bess-l2l3-vpn-mcast-mib-08 (work in progress), May 1768 2017. 1770 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1771 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 1772 RFC2119, March 1997, 1773 . 1775 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1776 Schoenwaelder, Ed., "Structure of Management Information 1777 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 1778 RFC2578, April 1999, 1779 . 1781 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1782 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 1783 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1784 . 1786 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1787 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1788 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1789 . 1791 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 1792 (USM) for version 3 of the Simple Network Management 1793 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 1794 RFC3414, December 2002, 1795 . 1797 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 1798 Advanced Encryption Standard (AES) Cipher Algorithm in the 1799 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 1800 RFC3826, June 2004, 1801 . 1803 [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer 1804 3 Virtual Private Network (VPN) Management Information 1805 Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, 1806 . 1808 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 1809 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 1810 Protocol Specification (Revised)", RFC 4601, DOI 10.17487/ 1811 RFC4601, August 2006, 1812 . 1814 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 1815 MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, 1816 . 1818 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1819 for the Simple Network Management Protocol (SNMP)", STD 1820 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 1821 . 1823 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1824 Shell Transport Model for the Simple Network Management 1825 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 1826 2009, . 1828 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1829 Model for the Simple Network Management Protocol (SNMP)", 1830 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 1831 . 1833 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 1834 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 1835 2012, . 1837 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 1838 Encodings and Procedures for Multicast in MPLS/BGP IP 1839 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 1840 . 1842 [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. 1843 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", 1844 RFC 6625, DOI 10.17487/RFC6625, May 2012, 1845 . 1847 7.2. Informative References 1849 [I-D.svaidya-mcast-vpn-mib] 1850 Vaidya, S., "Multicast in BGP/MPLS IP VPNs Management 1851 Information Base", draft-svaidya-mcast-vpn-mib-02 (work in 1852 progress), March 2005. 1854 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1855 "Introduction and Applicability Statements for Internet- 1856 Standard Management Framework", RFC 3410, DOI 10.17487/ 1857 RFC3410, December 2002, 1858 . 1860 Authors' Addresses 1862 Zhaohui (Jeffrey) Zhang (editor) 1863 Juniper Networks, Inc. 1864 10 Technology Park Drive 1865 Westford, MA 01886 1866 USA 1868 Email: zzhang@juniper.net 1869 Saud Asif 1870 AT&T 1871 C5-3D30 200 South Laurel Avenue 1872 Middletown, NJ 07748 1873 USA 1875 Email: sasif@att.com 1877 Andy Green 1878 BT Design 21CN Converged Core IP & Data 1879 01473 629360 Adastral Park, Martlesham Heath, Ipswich IP5 3RE 1880 UK 1882 Email: andy.da.green@bt.com 1884 Sameer Gulrajani 1885 Cisco Systems 1886 Tasman Drive San Jose, CA 95134 1887 USA 1889 Email: sameerg@cisco.com 1891 Pradeep G. Jain 1892 Alcatel-Lucent Inc 1893 701 E Middlefield road Mountain view, CA 94043 1894 USA 1896 Email: pradeep.jain@alcatel-lucent.com 1898 Hiroshi Tsunoda (editor) 1899 Tohoku Institute of Technology 1900 35-1, Yagiyama Kasumi-cho, Taihaku-ku 1901 Sendai 982-8577 1902 Japan 1904 Phone: +81-22-305-3411 1905 Email: tsuno@m.ieice.org