idnits 2.17.1 draft-ietf-bess-mvpn-mib-05.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 (December 08, 2017) is 2329 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 301, but not defined ** Obsolete undefined reference: RFC 2571 (Obsoleted by RFC 3411) == Missing Reference: 'RFC2851' is mentioned on line 305, 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-12 Summary: 2 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: June 11, 2018 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 December 08, 2017 16 BGP/MPLS Layer 3 VPN Multicast Management Information Base 17 draft-ietf-bess-mvpn-mib-05 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 June 11, 2018. 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) [RFC7761] 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 Comments should be made directly to the BESS WG at bess@ietf.org. 100 1.1. Terminology 102 This document adopts the definitions, acronyms and mechanisms 103 described in [RFC6513] and other documents that [RFC6513] refers to. 104 Familiarity with Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts 105 and/or mechanisms is assumed. Some terms specifically related to 106 this document are explained below. 108 MVPN can be achieved by using various kinds of transport mechanisms 109 for forwarding a packet to all or a subset of PEs across service 110 provider networks. Such transport mechanisms are referred to as 111 provider tunnels (P-tunnels). 113 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 114 conceptual interface instantiated by a provider tunnel (P-tunnel), a 115 transport mechanism used to deliver multicast traffic. A PE uses to 116 send customer multicast traffic to all or some PEs in the same VPN. 118 There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective 119 PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE 120 attached to a particular MVPN to transmit a message to all PEs in the 121 same VPN. An S-PMSI is a PMSI that enables a PE attached to a 122 particular MVPN to transmit a message to some of the PEs in the same 123 VPN. 125 As described in [RFC4382], each PE router maintains one default 126 forwarding table and "VPN Routing and Forwarding tables", or "VRFs". 127 Throughout this document, we will use the term "multicast VRF (MVRF)" 128 to refer a VRF that is configured to contain the multicast routing 129 information. 131 Interchangeably, the term MVRF and MVPN are used to refer to a 132 particular Multicast VPN instantiation on a particular PE. 134 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 135 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 136 document are to be interpreted as described in [RFC2119]. 138 2. The Internet-Standard Management Framework 140 For a detailed overview of the documents that describe the current 141 Internet-Standard Management Framework, please refer to section 7 of 142 RFC 3410 [RFC3410]. 144 Managed objects are accessed via a virtual information store, termed 145 the Management Information Base or MIB. MIB objects are generally 146 accessed through the Simple Network Management Protocol (SNMP). 147 Objects in the MIB are defined using the mechanisms defined in the 148 Structure of Management Information (SMI). This memo specifies a MIB 149 module that is compliant to the SMIv2, which is described in STD 58, 150 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 151 [RFC2580]. 153 3. MCAST-VPN-MIB 155 This document defines MCAST-VPN-MIB, a MIB module for monitoring and/ 156 or configuring MVPNs on PEs. 158 3.1. Summary of MIB Module 160 The configuration and states specific to an MVPN include the 161 following information elements: 163 o C-multicast routing information exchange protocol (PIM or BGP) 165 o I-PMSI, S-PMSI and corresponding P-tunnels 167 o Mapping of C-multicast routing information to PMSI tunnels 169 To represent these information elements, MCAST-VPN-MIB defines eight 170 tables: mvpnGeneralTable, mvpnBgpGeneralTable, mvpnSpmsiConfigTable, 171 mvpnPmsiConfigTable, mvpnIpmsiTable, mvpnInterAsIpmsiTable, 172 mvpnSpmsiTable, mvpnMrouteTable. 174 The following four tables represent the MVPN configurations on PEs. 176 o mvpnGeneralTable 178 o mvpnBgpGeneralTable 180 o mvpnSpmsiConfigTable 182 o mvpnPmsiConfigTable 184 The following diagram shows the relationship among those four tables 185 use for configuration. Each box in the diagram represents a table, 186 and the label of each box corresponds to a table name. An arrow 187 indicates that one table has a pointer to a row in another table. 188 The entry in mvpnGeneralTable and mvpnSpmsiConfigTable has a pointer 189 to the row pertaining to the entry in the mvpnPmsiConfigTable. 191 +--------------+ 192 | mvpnBgp | 193 | GeneralTable | 194 +--------------+ +-------------------+ +-----------------+ 195 | mvpnGeneral | | mvpnPmsiConfig | | mvpnSpmsiConfig | 196 | Table | -> | Table | <- | Table | 197 +--------------+ +-------------------+ +-----------------+ 199 o mvpnGeneralTable 201 This table represents MVPNs that are configured on a PE. Each 202 entry in this table is created for each MVRF representing an 203 instance of MVPN. The entry represetns general configuration/ 204 states of the MVRF, including Inclusive PMSI (I-PMSI) 205 configuration. The MVPN represented by the entry in this table 206 must have the corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. 208 o mvpnBgpGeneralTable 210 This table augments the aformentioned mvpnGeneralTable. This 211 table contains BGP-MVPN specific managed objects. 213 o mvpnSpmsiConfigTable 215 This table contains managed objects necessary for configure 216 Selective PMSI (S-PMSI) associated with an MVRF on a PE. 218 o mvpnPmsiConfigTable 220 This table contains managed objects common to both I-PMSI and 221 S-PMSI configurations. Both I-PMSI configuration (in the entry in 222 mvpnGeneralTable) and S-PMSI configuration (in the entry in 223 mvpnSpmsiConfigTable) refer to an entry in this table. 225 The following four tables are designed for monitoring MVPNs on PEs. 227 o mvpnIpmsiTable 229 o mvpnInterAsIpmsiTable 231 o mvpnSpmsiTable 233 o mvpnMrouteTable 234 The following diagram shows the relationship among these four tables 235 and the l2l3VpnMcastPmsiTunnelAttributeTable defined separately in 236 L2L3-VPN-MCAST-MIB [I-D.ietf-bess-l2l3-vpn-mcast-mib]. The entry in 237 every table has a pointer to the row pertaining to the entry in the 238 l2l3VpnMcastPmsiTunnelAttributeTable. 240 +--------------+ +-------------------+ +-----------------+ 241 | mvpnIpmsi | -> | l2L3VpnMcastPmsi | <- | mvpnSpmsi | 242 | Table | | TunnelAttribute | | Table | 243 +--------------+ | Table | +-----------------+ 244 -> +-------------------+ 245 / ^ 246 / | 247 +--------------+ +-------------------+ 248 | mvpnInterAs | | mvpnMrouteTable | 249 | IpmsiTable | +-------------------+ 250 +--------------+ 252 o mvpnIpmsiTable 254 This table contains managed objects for monitoring all Intra-AS 255 I-PMSIs advertised and received by a PE. This table contains all 256 advertised and received Intra-AS I-PMSIs. With PIM-MVPN, it is 257 applicable only when BGP-Based Autodiscovery of MVPN Membership is 258 used. 260 o mvpnInterAsIpmsiTable 262 This table contains all advertised and received Inter-AS I-PMSIs. 263 With PIM-MVPN, it is applicable only when BGP-Based Autodiscovery 264 of MVPN Membership is used. 266 o mvpnSpmsiTable 268 This table contains managed objects for monitoring all S-PMSIs 269 advertised and received by a PE. 271 o mvpnMrouteTable 273 This table augments 274 ipMcastMIB.ipMcast.ipMcastRouteTable [RFC5132], for some MVPN 275 specific information. 277 o l2l3VpnMcastPmsiTunnelAttributeTable 279 An entry of this table corresponds to a PMSI Tunnel attribute and 280 is maintained by a PE router that advertises and receives the 281 attribute. Th entry in this table is referred by entries in 282 mvpnIpmsiTable, mvpnInterAsIpmsiTable, mvpnSpmsiTable, and 283 mvpnMrouteTable. 285 3.2. MIB Module Definitions 287 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 289 IMPORTS 290 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 291 Gauge32, Unsigned32, mib-2 292 FROM SNMPv2-SMI -- [RFC2578] 294 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 295 FROM SNMPv2-CONF -- [RFC2580] 297 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 298 FROM SNMPv2-TC -- [RFC2579] 300 SnmpAdminString 301 FROM SNMP-FRAMEWORK-MIB -- [RFC2571] 303 InetAddress, InetAddressType, InetAddressPrefixLength, 304 InetAutonomousSystemNumber 305 FROM INET-ADDRESS-MIB -- [RFC2851] 307 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 308 FROM MPLS-L3VPN-STD-MIB -- [RFC4382] 310 ipMcastRouteEntry 311 FROM IPMCAST-MIB -- [RFC5132] 313 L2L3VpnMcastProviderTunnelType 314 FROM L2L3-VPN-MCAST-TC-MIB; 316 mvpnMIB MODULE-IDENTITY 317 LAST-UPDATED "201712081200Z" -- 8th December 2017 12:00:00 GMT 318 ORGANIZATION "IETF BESS Working Group." 319 CONTACT-INFO 320 " Zhaohui Zhang 321 Juniper Networks, Inc. 322 10 Technology Park Drive 323 Westford, MA 01886 324 USA 325 Email: zzhang@juniper.net 327 Saud Asif 328 AT&T 329 C5-3D30 200 South Laurel Avenue 330 Middletown, NJ 07748 331 USA 332 Email: sasif@att.com 334 Andy Green 335 BT Design 21CN Converged Core IP & Data 336 01473 629360 Adastral Park, Martlesham Heath, 337 Ipswich IP5 3RE 338 UK 339 Email: andy.da.green@bt.com 341 Sameer Gulrajani 342 Cisco Systems 343 Tasman Drive San Jose, CA 95134 344 USA 345 Email: sameerg@cisco.com 347 Pradeep G. Jain 348 Alcatel-Lucent Inc 349 701 E Middlefield road Mountain view, CA 94043 350 USA 351 Email: pradeep.jain@alcatel-lucent.com 353 Hiroshi Tsunoda 354 Tohoku Institute of Technology 355 35-1, Yagiyama Kasumi-cho 356 Taihaku-ku, Sendai, 982-8577 357 Japan 358 Email: tsuno@m.ieice.org 360 Comments and discussion to bess@ietf.org" 362 DESCRIPTION 363 "This MIB contains managed object definitions for 364 multicast in BGP/MPLS IP VPNs defined by [RFC6513]. 365 Copyright (C) The Internet Society (2017)." 367 -- Revision history. 369 REVISION "201712081200Z" -- 8th December, 2017 370 DESCRIPTION 371 "Initial version, published as RFC XXXX." 373 -- RFC Ed. replace XXXX with actual RFC number and remove this note 375 ::= { mib-2 YYYY } 377 -- IANA Reg.: Please assign a value for "YYYY" under the 378 -- 'mib-2' subtree and record the assignment in the SMI 379 -- Numbers registry. 381 -- RFC Ed.: When the above assignment has been made, please 382 -- remove the above note 383 -- replace "YYYY" here with the assigned value and 384 -- remove this note. 386 -- Top level components of this MIB. 387 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 389 -- tables, scalars 390 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 392 -- conformance information 393 mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 395 -- mvpn Objects 396 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 397 mvpnGeneral OBJECT IDENTIFIER ::= { mvpnObjects 2 } 398 mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } 399 mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } 401 -- Scalar Objects 403 mvpnMvrfs OBJECT-TYPE 404 SYNTAX Gauge32 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The total number of MVRFs that are present on 409 this Provider Edge router (PE), whether 410 for IPv4, IPv6, or mLDP C-Multicast." 411 ::= { mvpnScalars 1 } 413 mvpnV4Mvrfs OBJECT-TYPE 414 SYNTAX Gauge32 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The number of MVRFs for IPv4 C-Multicast that are 419 present in this PE." 420 ::= { mvpnScalars 2 } 422 mvpnV6Mvrfs OBJECT-TYPE 423 SYNTAX Gauge32 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION 427 "The number of MVRFs for IPv6 C-Multicast that are 428 present in this PE." 429 ::= { mvpnScalars 3 } 431 mvpnPimV4Mvrfs OBJECT-TYPE 432 SYNTAX Gauge32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The number of PIM-MVPN MVRFs for IPv4 C-Multicast that are 437 present in this PE." 438 ::= { mvpnScalars 4 } 440 mvpnPimV6Mvrfs OBJECT-TYPE 441 SYNTAX Gauge32 442 MAX-ACCESS read-only 443 STATUS current 444 DESCRIPTION 445 "The number of PIM-MVPN MVRFs for IPv6 C-Multicast that are 446 present in this PE." 447 ::= { mvpnScalars 5 } 449 mvpnBgpV4Mvrfs OBJECT-TYPE 450 SYNTAX Gauge32 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "The number of BGP-MVPN MVRFs for IPv4 C-Multicast that are 455 present in this PE." 456 ::= { mvpnScalars 6 } 458 mvpnBgpV6Mvrfs OBJECT-TYPE 459 SYNTAX Gauge32 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION 463 "The number of BGP-MVPN MVRFs for IPv6 C-Multicast that are 464 present in this PE." 465 ::= { mvpnScalars 7 } 467 mvpnMldpMvrfs OBJECT-TYPE 468 SYNTAX Gauge32 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "The number of BGP-MVPN MVRFs for mLDP C-Multicast that are 473 present in this PE." 474 ::= { mvpnScalars 8 } 476 mvpnNotificationEnable OBJECT-TYPE 477 SYNTAX TruthValue 478 MAX-ACCESS read-write 479 STATUS current 480 DESCRIPTION 481 "If this object is TRUE, then the generation of all 482 notifications defined in this MIB is enabled." 483 DEFVAL { false } 484 ::= { mvpnScalars 9 } 486 -- General MVRF Information Table 488 mvpnGeneralTable OBJECT-TYPE 489 SYNTAX SEQUENCE OF MvpnGeneralEntry 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "This table specifies the general information about the MVRFs 494 present in this PE." 495 ::= { mvpnGeneral 1 } 497 mvpnGeneralEntry OBJECT-TYPE 498 SYNTAX MvpnGeneralEntry 499 MAX-ACCESS not-accessible 500 STATUS current 501 DESCRIPTION 502 "An entry in this table is created for each MVRF in the 503 PE." 504 INDEX { 505 mplsL3VpnVrfName, 506 mvpnGenAddressFamily 507 } 508 ::= { mvpnGeneralTable 1 } 510 MvpnGeneralEntry ::= SEQUENCE { 511 mvpnGenAddressFamily INTEGER, 512 mvpnGenMvrfStatusChange INTEGER, 513 mvpnGenMvrfStatusChangeTime TimeStamp, 514 mvpnGenCmcastRouteProtocol INTEGER, 515 mvpnGenIpmsiConfig RowPointer, 516 mvpnGenInterAsPmsiConfig RowPointer, 517 mvpnGenUmhSelection INTEGER, 518 mvpnGenSiteType INTEGER, 519 mvpnGenSptnlLimit Unsigned32, 520 mvpnGenRowStatus RowStatus 522 } 524 mvpnGenAddressFamily OBJECT-TYPE 525 SYNTAX INTEGER { 526 ipv4(1), 527 ipv6(2) 528 } 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "The Address Family that this entry is for" 533 ::= { mvpnGeneralEntry 1 } 535 mvpnGenMvrfStatusChange OBJECT-TYPE 536 SYNTAX INTEGER { 537 createdMvrf(1), 538 deletedMvrf(2), 539 modifiedMvrfIpmsiConfig(3), 540 modifiedMvrfSpmsiConfig(4) 541 } 542 MAX-ACCESS read-only 543 STATUS current 544 DESCRIPTION 545 "This object describes the last status change that 546 happened for the given MVRF. 548 createdMvrf(1): 549 indicates that the MVRF was created in the PE. 551 deletedMvrf(2): 552 indicates that the MVRF was deleted from the PE. 553 A row in this table will never have 554 mvpnGenMvrfStatusChange equal to deletedMvrf(2), 555 because in that case the row itself will be deleted 556 from the table. 557 This value for mvpnGenMvrfStatusChange is defined mainly 558 for use in mvpnMvrfStatusChange notification. 560 modifiedMvrfIpmsiConfig(3): 561 indicates that the I-PMSI for the MVRF was configured, 562 deleted or changed. 564 modifiedMvrfSpmsiConfig(4): 565 indicates that the S-PMSI for the MVRF was configured, 566 deleted or changed. 567 " 568 DEFVAL { createdMvrf } 569 ::= { mvpnGeneralEntry 2 } 571 mvpnGenMvrfStatusChangeTime OBJECT-TYPE 572 SYNTAX TimeStamp 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The time at which the last status change for the MVRF in 577 question took place. The last operational change is specified 578 by mvpnGenMvrfStatusChange. 579 " 580 ::= { mvpnGeneralEntry 3 } 582 mvpnGenCmcastRouteProtocol OBJECT-TYPE 583 SYNTAX INTEGER { 584 pim (1), 585 bgp (2) 586 } 587 MAX-ACCESS read-create 588 STATUS current 589 DESCRIPTION 590 "The protocol used to signal C-multicast states across the 591 provider core. 592 pim(1): PIM (PIM-MVPN). 593 bgp(2): BGP (BGP-MVPN). 594 " 595 ::= { mvpnGeneralEntry 4 } 597 mvpnGenIpmsiConfig OBJECT-TYPE 598 SYNTAX RowPointer 599 MAX-ACCESS read-create 600 STATUS current 601 DESCRIPTION 602 "This points to a row in mvpnPmsiConfigTable, 603 for I-PMSI configuration. 604 " 605 ::= { mvpnGeneralEntry 5 } 607 mvpnGenInterAsPmsiConfig OBJECT-TYPE 608 SYNTAX RowPointer 609 MAX-ACCESS read-create 610 STATUS current 611 DESCRIPTION 612 "This points to a row in mvpnPmsiConfigTable, 613 for inter-as I-PMSI configuration, in case of segmented 614 inter-as provider tunnels. 615 " 616 ::= { mvpnGeneralEntry 6 } 618 mvpnGenUmhSelection OBJECT-TYPE 619 SYNTAX INTEGER { 620 highestPeAddress (1), 621 cRootGroupHashing (2), 622 ucastUmhRoute (3) 623 } 624 MAX-ACCESS read-create 625 STATUS current 626 DESCRIPTION 627 "The UMH selection method for this mvpn, as specified in 628 section 5.1.3 of [RFC6513]: 629 highestPeAddress (1): PE with the highest address 630 cRootGroupHashing (2): hashing based on (c-root, c-group) 631 uncastUmhRoute (3): per ucast route towards c-root 632 " 633 ::= { mvpnGeneralEntry 7 } 635 mvpnGenSiteType OBJECT-TYPE 636 SYNTAX INTEGER { 637 senderReceiver (1), 638 receiverOnly (2), 639 senderOnly (3) 640 } 641 MAX-ACCESS read-create 642 STATUS current 643 DESCRIPTION 644 "Whether this site is a receiver-only site or not. 645 senderReceiver (1): both sender and receiver site. 646 receiverOnly (2): receiver-only site. 647 senderOnly (3): sender-only site. 648 " 649 ::= { mvpnGeneralEntry 8 } 651 mvpnGenSptnlLimit OBJECT-TYPE 652 SYNTAX Unsigned32 653 MAX-ACCESS read-create 654 STATUS current 655 DESCRIPTION 656 "The max number of selective provider tunnels this PE 657 allows for this mvpn." 658 ::= { mvpnGeneralEntry 9 } 660 mvpnGenRowStatus OBJECT-TYPE 661 SYNTAX RowStatus 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "This is used to create or delete a row in this table." 666 ::= { mvpnGeneralEntry 10 } 668 -- General BGP-MVPN table 670 mvpnBgpGeneralTable OBJECT-TYPE 671 SYNTAX SEQUENCE OF MvpnBgpGeneralEntry 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "This table augments the mvpnGeneralTable and is for BGP-MVPN 676 specific information. 677 " 678 ::= { mvpnGeneral 2 } 680 mvpnBgpGeneralEntry OBJECT-TYPE 681 SYNTAX MvpnBgpGeneralEntry 682 MAX-ACCESS not-accessible 683 STATUS current 684 DESCRIPTION 685 "The mvpnBgpGeneralEntry matches and augments an 686 mvpnGeneralEntry for a BGP-MVPN instance, with BGP-MVPN 687 specific informatoin. 688 " 689 AUGMENTS { mvpnGeneralEntry } 690 ::= { mvpnBgpGeneralTable 1 } 692 MvpnBgpGeneralEntry ::= SEQUENCE { 693 mvpnBgpGenMode INTEGER, 694 mvpnBgpGenVrfRtImport MplsL3VpnRouteDistinguisher, 695 mvpnBgpGenSrcAs InetAutonomousSystemNumber 696 } 698 mvpnBgpGenMode OBJECT-TYPE 699 SYNTAX INTEGER { 700 rptSpt (1), 701 sptOnly (2) 702 } 703 MAX-ACCESS read-write 704 STATUS current 705 DESCRIPTION 706 "For two different BGP-MVPN modes: 707 rptSpt(1): inter-site shared tree mode 708 sptOnly(2): inter-site source-only tree mode. 709 " 710 ::= { mvpnBgpGeneralEntry 1} 712 mvpnBgpGenVrfRtImport OBJECT-TYPE 713 SYNTAX MplsL3VpnRouteDistinguisher 714 MAX-ACCESS read-write 715 STATUS current 716 DESCRIPTION 717 "The VRF Route Import Extended Community that this PE 718 adds to unicast vpn routes that it advertises for this mvpn. 719 " 720 REFERENCE 721 "RFC4364, Section 4.2 722 RFC4382, Section 7 723 " 724 ::= { mvpnBgpGeneralEntry 2} 726 mvpnBgpGenSrcAs OBJECT-TYPE 727 SYNTAX InetAutonomousSystemNumber 728 MAX-ACCESS read-only 729 STATUS current 730 DESCRIPTION 731 "The Source AS number in Source AS Extended Community that this 732 PE adds to the unicast vpn routes that it advertises for 733 this mvpn. 734 " 735 ::= { mvpnBgpGeneralEntry 3} 737 -- PMSI Configuration Table 739 mvpnPmsiConfigTable OBJECT-TYPE 740 SYNTAX SEQUENCE OF MvpnPmsiConfigEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "This table specifies the configured PMSIs." 745 ::= { mvpnConfig 1 } 747 mvpnPmsiConfigEntry OBJECT-TYPE 748 SYNTAX MvpnPmsiConfigEntry 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "An entry in this table is created for each PMSI configured 753 on this router. It can be referred to by either I-PMSI 754 configuration (in mvpnGeneralEntry) or S-PMSI configuration 755 (in mvpnSpmsiConfigEntry) 756 " 757 INDEX { 758 mvpnPmsiConfigTunnelType, 759 mvpnPmsiConfigTunnelAuxInfo, 760 mvpnPmsiConfigTunnelPimGroupAddrType, 761 mvpnPmsiConfigTunnelPimGroupAddr, 762 mvpnPmsiConfigTunnelOrTemplateName 763 } 765 ::= { mvpnPmsiConfigTable 1 } 767 MvpnPmsiConfigEntry ::= SEQUENCE { 768 mvpnPmsiConfigTunnelType 769 L2L3VpnMcastProviderTunnelType, 770 mvpnPmsiConfigTunnelAuxInfo Unsigned32, 771 mvpnPmsiConfigTunnelPimGroupAddrType 772 InetAddressType, 773 mvpnPmsiConfigTunnelPimGroupAddr 774 InetAddress, 775 mvpnPmsiConfigTunnelOrTemplateName 776 SnmpAdminString, 777 mvpnPmsiConfigEncapsType INTEGER, 778 mvpnPmsiConfigRowStatus RowStatus 779 } 781 mvpnPmsiConfigTunnelType OBJECT-TYPE 782 SYNTAX L2L3VpnMcastProviderTunnelType 783 MAX-ACCESS not-accessible 784 STATUS current 785 DESCRIPTION 786 "Type of tunnel used to instantiate the PMSI." 787 ::= { mvpnPmsiConfigEntry 1 } 789 mvpnPmsiConfigTunnelAuxInfo OBJECT-TYPE 790 SYNTAX Unsigned32 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "Additional tunnel information depending on the value of 795 mvpnPmsiConfigTunnelType object. 797 pimSsm(3), pimAsm(4), pimBidir(5): 798 In case of S-PMSI, number of groups starting at 799 mvpnPmsiConfigTunnelPimGroupAddress. 800 This allows a range of PIM provider tunnel 801 group addresses to be specified in S-PMSI case. 802 In I-PMSI case, it must be 1. 804 rsvpP2mp(1): 805 1 for statically specified rsvp-p2mp tunnel 806 2 for dynamically created rsvp-p2mp tunnel 808 ingressReplication(6): 809 1 for using any existing p2p/mp2p LSP 810 2 for dynamically creating new p2p LSP 811 " 813 ::= { mvpnPmsiConfigEntry 2 } 815 mvpnPmsiConfigTunnelPimGroupAddrType OBJECT-TYPE 816 SYNTAX InetAddressType 817 MAX-ACCESS not-accessible 818 STATUS current 819 DESCRIPTION 820 "In case of PIM provider tunnel, the type of tunnel address." 821 ::= { mvpnPmsiConfigEntry 3 } 823 mvpnPmsiConfigTunnelPimGroupAddr OBJECT-TYPE 824 SYNTAX InetAddress 825 MAX-ACCESS not-accessible 826 STATUS current 827 DESCRIPTION 828 "In case of PIM provider tunnel, the provider tunnel address." 829 ::= { mvpnPmsiConfigEntry 4 } 831 mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE 832 SYNTAX SnmpAdminString 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "The tunnel name or template name used to create tunnels. 837 The value of this object depends on the values of 838 mvpnPmsiConfigTunnelType and mvpnPmsiConfigTunnelAuxInfo 839 objects: 841 dynamically created rsvp-p2mp tunnel: template name 842 statically specified rsvp-p2mp tunnel: tunnel name 843 ingress-replication using 844 dynamically created LSPs: template name 845 other: null 846 " 847 ::= { mvpnPmsiConfigEntry 5 } 849 mvpnPmsiConfigEncapsType OBJECT-TYPE 850 SYNTAX INTEGER { 851 greIp (1), 852 ipIp (2), 853 mpls (3) 854 } 855 MAX-ACCESS read-create 856 STATUS current 857 DESCRIPTION 858 "The encapsulation type to be used, in case of PIM tunnel or 859 ingress-replication. 860 " 862 ::= { mvpnPmsiConfigEntry 6 } 864 mvpnPmsiConfigRowStatus OBJECT-TYPE 865 SYNTAX RowStatus 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "Used to create/modify/delete a row in this table." 870 ::= { mvpnPmsiConfigEntry 7 } 872 -- S-PMSI configuration table 874 mvpnSpmsiConfigTable OBJECT-TYPE 875 SYNTAX SEQUENCE OF MvpnSpmsiConfigEntry 876 MAX-ACCESS not-accessible 877 STATUS current 878 DESCRIPTION 879 "This table specifies S-PMSI configuration." 880 ::= { mvpnConfig 2 } 882 mvpnSpmsiConfigEntry OBJECT-TYPE 883 SYNTAX MvpnSpmsiConfigEntry 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "An entry is created for each S-PMSI configuration." 888 INDEX { 889 mplsL3VpnVrfName, 890 mvpnSpmsiConfigCmcastAddrType, 891 mvpnSpmsiConfigCmcastGroupAddr, 892 mvpnSpmsiConfigCmcastGroupPrefixLen, 893 mvpnSpmsiConfigCmcastSourceAddr, 894 mvpnSpmsiConfigCmcastSourcePrefixLen 895 } 896 ::= { mvpnSpmsiConfigTable 1 } 898 MvpnSpmsiConfigEntry ::= SEQUENCE { 899 mvpnSpmsiConfigCmcastAddrType InetAddressType, 900 mvpnSpmsiConfigCmcastGroupAddr InetAddress, 901 mvpnSpmsiConfigCmcastGroupPrefixLen InetAddressPrefixLength, 902 mvpnSpmsiConfigCmcastSourceAddr InetAddress, 903 mvpnSpmsiConfigCmcastSourcePrefixLen InetAddressPrefixLength, 904 mvpnSpmsiConfigThreshold Unsigned32, 905 mvpnSpmsiConfigPmsiPointer RowPointer, 906 mvpnSpmsiConfigRowStatus RowStatus 907 } 909 mvpnSpmsiConfigCmcastAddrType OBJECT-TYPE 910 SYNTAX InetAddressType 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "Type of C-multicast address" 915 ::= { mvpnSpmsiConfigEntry 1 } 917 mvpnSpmsiConfigCmcastGroupAddr OBJECT-TYPE 918 SYNTAX InetAddress 919 MAX-ACCESS not-accessible 920 STATUS current 921 DESCRIPTION 922 "C-multicast group address" 923 ::= { mvpnSpmsiConfigEntry 2 } 925 mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE 926 SYNTAX InetAddressPrefixLength 927 MAX-ACCESS not-accessible 928 STATUS current 929 DESCRIPTION 930 "C-multicast group address prefix length. 931 A group 0 (or ::0) with prefix length 32 (or 128) 932 indicates wildcard group, while a group 0 (or ::0) 933 with prefix length 0 indicates any group. 934 " 935 ::= { mvpnSpmsiConfigEntry 3 } 937 mvpnSpmsiConfigCmcastSourceAddr OBJECT-TYPE 938 SYNTAX InetAddress 939 MAX-ACCESS not-accessible 940 STATUS current 941 DESCRIPTION 942 "C-multicast source address" 943 ::= { mvpnSpmsiConfigEntry 4 } 945 mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE 946 SYNTAX InetAddressPrefixLength 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "C-multicast source address prefix length. 951 A source 0 (or ::0) with prefix length 32 (or 128) 952 indicates a wildcard source, while a source 0 (or ::0) 953 with prefix length 0 indicates any source. 954 " 955 ::= { mvpnSpmsiConfigEntry 5 } 957 mvpnSpmsiConfigThreshold OBJECT-TYPE 958 SYNTAX Unsigned32 (0..4294967295) 959 UNITS "kilobits per second" 960 MAX-ACCESS read-create 961 STATUS current 962 DESCRIPTION 963 "The bandwidth threshold value which when exceeded for a 964 multicast routing entry in the given MVRF, triggers usage 965 of S-PMSI. 966 " 967 ::= { mvpnSpmsiConfigEntry 6 } 969 mvpnSpmsiConfigPmsiPointer OBJECT-TYPE 970 SYNTAX RowPointer 971 MAX-ACCESS read-create 972 STATUS current 973 DESCRIPTION 974 "This points to a row in mvpnPmsiConfigTable, 975 to specify tunnel attributes. 976 " 977 ::= { mvpnSpmsiConfigEntry 7 } 979 mvpnSpmsiConfigRowStatus OBJECT-TYPE 980 SYNTAX RowStatus 981 MAX-ACCESS read-create 982 STATUS current 983 DESCRIPTION 984 "Used to create/modify/delete a row in this table." 985 ::= { mvpnSpmsiConfigEntry 8 } 987 -- Table of intra-as I-PMSIs advertised/received 989 mvpnIpmsiTable OBJECT-TYPE 990 SYNTAX SEQUENCE OF MvpnIpmsiEntry 991 MAX-ACCESS not-accessible 992 STATUS current 993 DESCRIPTION 994 "This table is for all advertised/received I-PMSI 995 advertisements. 996 " 997 ::= { mvpnStates 1 } 999 mvpnIpmsiEntry OBJECT-TYPE 1000 SYNTAX MvpnIpmsiEntry 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "An entry in this table corresponds to an I-PMSI 1005 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 mvpnIpmsiOrigAddr 1016 } 1017 ::= { mvpnIpmsiTable 1 } 1019 MvpnIpmsiEntry ::= SEQUENCE { 1020 mvpnIpmsiAfi INTEGER, 1021 mvpnIpmsiRD MplsL3VpnRouteDistinguisher, 1022 mvpnIpmsiOrigAddrType InetAddressType, 1023 mvpnIpmsiOrigAddr 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 mvpnIpmsiOrigAddr." 1053 ::= { mvpnIpmsiEntry 3 } 1055 mvpnIpmsiOrigAddr 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 InetAutonomousSystemNumber, 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 InetAutonomousSystemNumber 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 mvpnSpmsiCmcastGroupAddr, 1176 mvpnSpmsiCmcastGroupPrefixLen, 1177 mvpnSpmsiCmcastSourceAddr, 1178 mvpnSpmsiCmcastSourcePrefixLen, 1179 mvpnSpmsiOrigAddrType, 1180 mvpnSpmsiOrigAddr 1181 } 1182 ::= { mvpnSpmsiTable 1 } 1184 MvpnSpmsiEntry ::= SEQUENCE { 1185 mvpnSpmsiCmcastAddrType InetAddressType, 1186 mvpnSpmsiCmcastGroupAddr InetAddress, 1187 mvpnSpmsiCmcastGroupPrefixLen InetAddressPrefixLength, 1188 mvpnSpmsiCmcastSourceAddr InetAddress, 1189 mvpnSpmsiCmcastSourcePrefixLen InetAddressPrefixLength, 1190 mvpnSpmsiOrigAddrType InetAddressType, 1191 mvpnSpmsiOrigAddr 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 mvpnSpmsiCmcastGroupAddr 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 InetAddressPrefixLength 1219 MAX-ACCESS not-accessible 1220 STATUS current 1221 DESCRIPTION 1222 "S-PMSI C-multicast group address prefix length." 1223 ::= { mvpnSpmsiEntry 3 } 1225 mvpnSpmsiCmcastSourceAddr 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 InetAddressPrefixLength 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 mvpnSpmsiOrigAddr." 1250 ::= { mvpnSpmsiEntry 6 } 1252 mvpnSpmsiOrigAddr 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 This document borrowed some text from Cisco PIM-MVPN MIB 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-12 (work in progress), 1768 November 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, . 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, . 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, . 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, . 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 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 1809 MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, 1810 . 1812 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 1813 for the Simple Network Management Protocol (SNMP)", STD 1814 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 1815 . 1817 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 1818 Shell Transport Model for the Simple Network Management 1819 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 1820 2009, . 1822 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 1823 Model for the Simple Network Management Protocol (SNMP)", 1824 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 1825 . 1827 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 1828 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 1829 2012, . 1831 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 1832 Encodings and Procedures for Multicast in MPLS/BGP IP 1833 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 1834 . 1836 [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. 1837 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", 1838 RFC 6625, DOI 10.17487/RFC6625, May 2012, 1839 . 1841 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 1842 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 1843 Multicast - Sparse Mode (PIM-SM): Protocol Specification 1844 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 1845 2016, . 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, . 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