idnits 2.17.1 draft-ietf-l3vpn-mvpn-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 28 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (2013-01-07) is 4126 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: 'RFC2119' is mentioned on line 119, but not defined == Missing Reference: 'L3VPN-MIB' is mentioned on line 173, but not defined == Unused Reference: 'KEYWORDS' is defined on line 1162, but no explicit reference was found in the text == Unused Reference: 'RFC4382' is defined on line 1165, but no explicit reference was found in the text == Unused Reference: 'BGP-MVPN' is defined on line 1175, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Saud Asif 3 Intended Status: Proposed Standard AT&T 4 Expires: 2013-07-07 Andy Green 5 BT 6 Sameer Gulrajani 7 Cisco 8 Pradeep Jain 9 Alcatel-Lucent 10 Jeffrey Zhang 11 Juniper 12 2013-01-07 14 MPLS/BGP Layer 3 VPN Multicast 15 Management Information Base 17 draft-ietf-l3vpn-mvpn-mib-01 19 Abstract 21 This memo defines an portion of the Management Information Base (MIB) 22 for use with network management protocols in the Internet community. 24 In particular, it describes managed objects to configure and/or 25 monitor multicast in MPLS/BGP-based Layer-3 VPN (MVPN) on an MVPN 26 router. 28 Status of this Memo 30 This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that 35 other groups may also distribute working documents as 36 Internet-Drafts. 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 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/1id-abstracts.html 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html 49 Copyright and License Notice 51 Copyright (c) 2013 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 0 Draft history . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2 MVPN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 2.1 Summary of MIB Module . . . . . . . . . . . . . . . . . . . 4 71 2.2 MIB Module Definitions . . . . . . . . . . . . . . . . . . 5 72 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 25 73 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 25 74 5 Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 25 75 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 76 6.1 Normative References . . . . . . . . . . . . . . . . . . . 25 77 6.2 Informative References . . . . . . . . . . . . . . . . . . 25 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 80 0 Draft history 82 This draft is a first pass at a MIB document for [MVPN]. As such, it 83 should be considered as a early work. 85 Some aspects of BGP-MVPN (see definition below in "Introduction"), 86 such as exranet, may be specified in future revisions. 88 [note to author/reviewers: conformance groups to be added ] 90 [this section should be removed as soon as its stops being relevant] 92 1 Introduction 94 Multicast in MPLS/BGP L3 VPNs is specified in {[MVPN], [BGP-MVPN]}. 95 These specifications support either PIM or BGP as the protocol for 96 exchanging VPN multicast (referred to as C-multicast states, where 97 'C-' stands for 'VPN Customer-') among PEs. In the rest of this 98 document we'll use the term "PIM-MVPN" to refer to {[MVPN], [BGP- 99 MVPN]} with PIM being used for exchanging C-multicast states, and 100 "BGP-MVPN" to refer to {[MVPN], [BGP-MVPN]} with BGP is used for 101 exchanging C-multicast states. 103 This document defines a standard MIB for MVPN-specific objects that 104 are generic to both PIM-MVPN and BGP-MVPN. 106 This document borrowed some text from Cisco PIM-MVPN MIB [CISCO-MIB]. 107 For PIM-MVPN this document attempts to provide coverage comparable 108 to [CISCO-MIB], but in a generic way that applies to both PIM-MVPN 109 and BGP-MVPN. 111 Comments should be made directly to the Layer-3 VPN (L3VPN) WG at 112 l3vpn@ietf.org. 114 1.1 Terminology 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in RFC 2119 [RFC2119]. 120 This document adopts the definitions, acronyms and mechanisms 121 described in [MVPN] and other documents that [MVPN] refers to. 122 Familiarity with Multicast, MPLS, L3VPN, MVPN concepts and/or 123 mechanisms is assumed. 125 Interchangeably, the term MVRF and MVPN are used to refer to a 126 partiular Multicast VPN instantiation on a particular PE device. 128 2 MVPN MIB 130 This MIB enables configuring and/or monitoring of MVPNs on PE 131 devices: the whole multicast VPN machinery and the per-MVRFs 132 information, including the configuration, status and operational 133 details, such as different PMSIs and the provider tunnels 134 implementing them. 136 2.1 Summary of MIB Module 138 The configuration and states specific to an MVPN include the 139 following: 141 - C-multicast routing exchange protocol (PIM or BGP) 143 - I-PMSI, S-PMSI and corresponding provider tunnels 145 - Mapping of c-multicast states to PMSI/tunnels 147 To represent them, the following tables are defined. 149 +--------------+ 150 | MvpnBgp | 151 | General | 152 +--------------+ +-------------------+ +-----------------+ 153 | MvpnGeneral | -> | MvpnPmsiConfig | <- | MvpnSpmsiConfig | 154 +--------------+ +-------------------+ +-----------------+ 156 +--------------+ +-------------------+ +-----------------+ 157 | MvpnIpmsi | -> | L2L3VpnMcastPmsi | <- | MvpnSpmsi | 158 +--------------+ | TunnelAttribute | +-----------------+ 159 -> +-------------------+ 160 / ^ 161 / | 162 +--------------+ +-------------------+ 163 | MvpnInterAs | | MvpnMroute | 164 | Ipmsi | +-------------------+ 165 +--------------+ 167 - mvpnGeneralTable/Entry 169 An entry in this table is created for every MVRF in the device, for 170 general configuration/states of the MVRF, including I-PMSI 171 configuration. 173 Existence of the corresponding VRF in [L3VPN-MIB] is necessary for 174 a row to exist in this table. 176 - mvpnBgpGeneralTable/Entry 178 This table augments mvpnGeneralTable and is for BGP-MVPN specific 179 information. 181 - mvpnSpmsiConfigTable/Entry 183 This table contains objects for S-PMSI configurations in an MVRF. 185 - mvpnPmsiConfigTable/Entry 187 Both I-PMSI configuration (in mvpnGeneralEntry) and S-PMSI 188 configuration (in mvpnSpmsiConfigEntry) refer to entries in this 189 table. 191 - mvpnIpmsiTable/Entry 193 This table contains all advertised or received intra-as I-PMSIs. 194 With PIM-MVPN, it is applicable only when BGP-Based Autodiscovery 195 of MVPN Membership is used. 197 - mvpnInterAsIpmsiTable/Entry 199 This table contains all advertised or received inter-as I-PMSIs. 200 With PIM-MVPN, it is applicable only when BGP-Based Autodiscovery 201 of MVPN Membership is used. 203 - mvpnSpmsiTable/Etnry 205 This table contains all advertised or received S-PMSIs. 207 - l2l3VpnMcastPmsiTunnelAttributeTable/Entry 209 This table is defined separately in l2L3VpnMcastMIB [L2L3MVPN-MIB], 210 which is common for both VPLS Multicast and MVPN. It contains 211 sent/received PMSI attribute entries referred to by mvpnIpmsiEntry, 212 mvpnSpmsiEntry, mvpnInterAsIpmsiEntry, and other MIB objects (e.g., 213 VPLS Multicast ones). 215 - mvpnMrouteTable/Entry 217 This table augments ipMcastMIB.ipMcast.ipMcastRouteTable, for some 218 MVPN specific information. 219 2.2 MIB Module Definitions 220 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 222 IMPORTS 223 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 224 experimental, Unsigned32 225 FROM SNMPv2-SMI 227 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 228 FROM SNMPv2-CONF 230 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 231 FROM SNMPv2-TC 233 SnmpAdminString 234 FROM SNMP-FRAMEWORK-MIB 236 InetAddress, InetAddressType 237 FROM INET-ADDRESS-MIB 239 MplsLabel 240 FROM MPLS-TC-STD-MIB 242 mplsVpnVrfName, MplsVpnRouteDistinguisher 243 FROM MPLS-L3VPN-STD-MIB 245 ipMcastRouteEntry 246 FROM IPMCAST-MIB 248 L2L3VpnMcastProviderTunnelType 249 FROM L2L3-VPN-MCAST-MIB; 251 mvpnMIB MODULE-IDENTITY 252 LAST-UPDATED "201301071200Z" -- 07 January 2013 12:00:00 GMT 253 ORGANIZATION "IETF Layer-3 Virtual Private 254 Networks Working Group." 255 CONTACT-INFO 256 " Jeffrey (Zhaohui) Zhang 257 zzhang@juniper.net 259 Comments and discussion to l3vpn@ietf.org" 261 DESCRIPTION 262 "This MIB contains managed object definitions for 263 multicast in BGP/MPLS IP VPNs defined by [MVPN]. 264 Copyright (C) The Internet Society (2013)." 266 -- Revision history. 267 REVISION "201301071200Z" -- 07 January 2013 12:00:00 GMT 268 DESCRIPTION 269 "Initial version of the draft." 270 ::= { experimental 99 } -- number to be assigned 272 -- Top level components of this MIB. 273 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 275 -- tables, scalars 276 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 278 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 279 mvpnGeneral OBJECT IDENTIFIER ::= { mvpnObjects 2 } 280 mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } 281 mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } 283 -- Scalar Objects 285 mvpnMvrfNumber OBJECT-TYPE 286 SYNTAX Unsigned32 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of MVRFs that are present in this device." 291 ::= { mvpnScalars 1 } 293 mvpnMvrfNumberPim OBJECT-TYPE 294 SYNTAX Unsigned32 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The number of PIM-MVPN MVRFs that are present in this device." 299 ::= { mvpnScalars 2 } 301 mvpnMvrfNumberBgp OBJECT-TYPE 302 SYNTAX Unsigned32 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "The number of BGP-MVPN MVRFs that are present in this device." 307 ::= { mvpnScalars 3 } 309 mvpnNotificationEnable OBJECT-TYPE 310 SYNTAX TruthValue 311 MAX-ACCESS read-write 312 STATUS current 313 DESCRIPTION 314 "If this object is TRUE, then the generation of all 315 notifications defined in this MIB is enabled." 317 DEFVAL { false } 318 ::= { mvpnScalars 4 } 320 -- General MVRF Information Table 322 mvpnGeneralTable OBJECT-TYPE 323 SYNTAX SEQUENCE OF MvpnGeneralEntry 324 MAX-ACCESS not-accessible 325 STATUS current 326 DESCRIPTION 327 "This table specifies the general information about the MVRFs 328 present in this device." 329 ::= { mvpnGeneral 1 } 331 mvpnGeneralEntry OBJECT-TYPE 332 SYNTAX MvpnGeneralEntry 333 MAX-ACCESS not-accessible 334 STATUS current 335 DESCRIPTION 336 "An entry in this table is created for every MVRF in the 337 device." 338 INDEX { mplsVpnVrfName } 339 ::= { mvpnGeneralTable 1 } 341 MvpnGeneralEntry ::= SEQUENCE { 342 mvpnGenOperStatusChange INTEGER, 343 mvpnGenOperChangeTime TimeStamp, 344 mvpnGenCmcastRouteProtocol INTEGER, 345 mvpnGenIpmsiConfigV4 RowPointer, 346 mvpnGenIpmsiConfigV6 RowPointer, 347 mvpnGenInterAsPmsiConfigV4 RowPointer, 348 mvpnGenInterAsPmsiConfigV6 RowPointer, 349 mvpnGenRowStatus RowStatus 350 } 352 mvpnGenOperStatusChange OBJECT-TYPE 353 SYNTAX INTEGER { createdMvrf(1), 354 deletedMvrf(2), 355 modifiedMvrfIpmsiConfig(3), 356 modifiedMvrfSpmsiConfig(4) 357 } 358 MAX-ACCESS read-only 359 STATUS current 360 DESCRIPTION 361 "This object describes the last operational change that 362 happened for the given MVRF. 364 createdMvrf - indicates that the MVRF was created in the 365 device. 367 deletedMvrf - indicates that the MVRF was deleted from the 368 device. A row in this table will never have 369 mvpnGenOperStatusChange equal to deletedMvrf(2), 370 because in that case the row itself will be deleted from the 371 table. This value for mvpnGenOperStatusChange is defined 372 mainly for use in mvpnMvrfChange notification. 374 modifiedMvrfIpmsiConfig - indicates that the I-PMSI 375 for the MVRF was configured, deleted or changed. 377 modifiedMvrfSpmsiConfig - indicates that the S-PMSI 378 for the MVRF was configured, deleted or changed." 379 DEFVAL { createdMvrf } 380 ::= { mvpnGeneralEntry 1 } 382 mvpnGenOperChangeTime OBJECT-TYPE 383 SYNTAX TimeStamp 384 MAX-ACCESS read-only 385 STATUS current 386 DESCRIPTION 387 "The time at which the last operational change for the MVRF in 388 question took place. The last operational change is specified 389 by mvpnGenOperStatusChange." 390 ::= { mvpnGeneralEntry 2 } 392 mvpnGenCmcastRouteProtocol OBJECT-TYPE 393 SYNTAX INTEGER { pim (1), 394 bgp (2) 395 } 396 MAX-ACCESS read-write 397 STATUS current 398 DESCRIPTION 399 "Protocol used to signal C-multicast states across the 400 provider core. 401 pim(1): PIM (PIM-MVPN). 402 bgp(2): BGP (BGP-MVPN)." 403 ::= { mvpnGeneralEntry 3 } 405 mvpnGenIpmsiConfigV4 OBJECT-TYPE 406 SYNTAX RowPointer 407 MAX-ACCESS read-write 408 STATUS current 409 DESCRIPTION 410 "This points to a row in mvpnPmsiConfigTable, 411 for I-PMSI configuration for IPv4." 412 ::= { mvpnGeneralEntry 4 } 414 mvpnGenIpmsiConfigV6 OBJECT-TYPE 415 SYNTAX RowPointer 416 MAX-ACCESS read-write 417 STATUS current 418 DESCRIPTION 419 "This points to a row in mvpnPmsiConfigTable, 420 for I-PMSI configuration for IPv6." 421 ::= { mvpnGeneralEntry 5 } 423 mvpnGenInterAsPmsiConfigV4 OBJECT-TYPE 424 SYNTAX RowPointer 425 MAX-ACCESS read-write 426 STATUS current 427 DESCRIPTION 428 "This points to a row in mvpnPmsiConfigTable, 429 for inter-as I-PMSI configuration for IPv4, in case of segmented 430 inter-as provider tunnels." 431 ::= { mvpnGeneralEntry 6 } 433 mvpnGenInterAsPmsiConfigV6 OBJECT-TYPE 434 SYNTAX RowPointer 435 MAX-ACCESS read-write 436 STATUS current 437 DESCRIPTION 438 "This points to a row in mvpnPmsiConfigTable, 439 for inter-as I-PMSI configuration for IPv6, in case of segmented 440 inter-as provider tunnels." 441 ::= { mvpnGeneralEntry 7 } 443 mvpnGenRowStatus OBJECT-TYPE 444 SYNTAX RowStatus 445 MAX-ACCESS read-create 446 STATUS current 447 DESCRIPTION 448 "This is used to create or delete a row in this table." 449 ::= { mvpnGeneralEntry 8 } 451 -- General BGP-MVPN table 453 mvpnBgpGeneralTable OBJECT-TYPE 454 SYNTAX SEQUENCE OF MvpnBgpGeneralEntry 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "This table augments the mvpnGeneralTable and is for BGP-MVPN 459 specific information." 460 ::= { mvpnGeneral 2 } 462 mvpnBgpGeneralEntry OBJECT-TYPE 463 SYNTAX MvpnBgpGeneralEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "The mvpnBgpGeneralEntry matches and augments an mvpnGeneralEntry 468 for a BGP-MVPN instance, with BGP-MVPN specific informatoin." 469 AUGMENTS { mvpnGeneralEntry } 470 ::= { mvpnBgpGeneralTable 1 } 472 MvpnBgpGeneralEntry ::= SEQUENCE { 473 mvpnBgpGenMode INTEGER, 474 mvpnBgpGenUmhSelection INTEGER, 475 mvpnBgpGenSiteType INTEGER, 476 mvpnBgpGenCmcastImportRt MplsVpnRouteDistinguisher, 477 mvpnBgpGenSrcAs Unsigned32, 478 mvpnBgpGenSptnlLimit Unsigned32 479 } 481 mvpnBgpGenMode OBJECT-TYPE 482 SYNTAX INTEGER { 483 rpt-spt (1), 484 spt-only (2) 485 } 486 MAX-ACCESS read-write 487 STATUS current 488 DESCRIPTION 489 "For two different BGP-MVPN modes: 490 rpt-spt(1): intersite-site shared tree mode 491 spt-only(2): inter-site source-only tree mode." 492 ::= { mvpnBgpGeneralEntry 1} 494 mvpnBgpGenUmhSelection OBJECT-TYPE 495 SYNTAX INTEGER { 496 highest-pe-address (1), 497 c-root-group-hashing (2), 498 ucast-umh-route (3) 499 } 500 MAX-ACCESS read-write 501 STATUS current 502 DESCRIPTION 503 "The UMH selection method for this mvpn, as specified in section 504 5.1.3 of [MVPN]: 505 highest-pe-address (1): PE with the highest address 506 c-root-group-hashing (2): hashing based on (c-root, c-group) 507 uncast-umh-route (3): per ucast route towards c-root" 509 ::= { mvpnBgpGeneralEntry 2} 511 mvpnBgpGenSiteType OBJECT-TYPE 512 SYNTAX INTEGER { 513 sender-receiver (1), 514 receiver-only (2), 515 sender-only (3) 516 } 517 MAX-ACCESS read-write 518 STATUS current 519 DESCRIPTION 520 "Whether this site is a receiver-only site or not. 521 sender-receiver (1): both sender and receiver site. 522 receiver-only (2): receiver-only site. 523 sender-only (3): sender-only site." 524 ::= { mvpnBgpGeneralEntry 3} 526 mvpnBgpGenCmcastImportRt OBJECT-TYPE 527 SYNTAX MplsVpnRouteDistinguisher 528 MAX-ACCESS read-write 529 STATUS current 530 DESCRIPTION 531 "The C-multicast Import RT that this device adds to 532 unicast vpn routes that it advertises for this mvpn." 533 ::= { mvpnBgpGeneralEntry 4} 535 mvpnBgpGenSrcAs OBJECT-TYPE 536 SYNTAX Unsigned32 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "The Source AS number in Source AS Extended Community that this device 541 adds to the unicast vpn routes that it advertises for this mvpn." 542 ::= { mvpnBgpGeneralEntry 5} 544 mvpnBgpGenSptnlLimit OBJECT-TYPE 545 SYNTAX Unsigned32 546 MAX-ACCESS read-write 547 STATUS current 548 DESCRIPTION 549 "The max number of selective provider tunnels this device allows 550 for this mvpn." 551 ::= { mvpnBgpGeneralEntry 6} 553 -- PMSI Configuration Table 555 mvpnPmsiConfigTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF MvpnPmsiConfigEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "This table specifies the configured PMSIs." 561 ::= { mvpnConfig 1 } 563 mvpnPmsiConfigEntry OBJECT-TYPE 564 SYNTAX MvpnPmsiConfigEntry 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "An entry in this table is created for each PMSI configured 569 on this router. It can be referred to by either I-PMSI 570 configuration (in mvpnGeneralEntry) or S-PMSI configuration 571 (in mvpnSpmsiConfigEntry)" 572 INDEX { mvpnPmsiConfigTunnelType, 573 mvpnPmsiConfigTunnelAuxInfo, 574 mvpnPmsiConfigTunnelPimGroupAddressType, 575 mvpnPmsiConfigTunnelPimGroupAddress, 576 mvpnPmsiConfigTunnelOrTemplateName } 577 ::= { mvpnPmsiConfigTable 1 } 579 MvpnPmsiConfigEntry ::= SEQUENCE { 580 mvpnPmsiConfigTunnelType L2L3VpnMcastProviderTunnelType, 581 mvpnPmsiConfigTunnelAuxInfo Unsigned32, 582 mvpnPmsiConfigTunnelPimGroupAddressType InetAddressType, 583 mvpnPmsiConfigTunnelPimGroupAddress InetAddress, 584 mvpnPmsiConfigTunnelOrTemplateName SnmpAdminString, 585 mvpnPmsiConfigEncapsType INTEGER, 586 mvpnPmsiConfigRowStatus RowStatus 587 } 589 mvpnPmsiConfigTunnelType OBJECT-TYPE 590 SYNTAX L2L3VpnMcastProviderTunnelType 591 MAX-ACCESS read-write 592 STATUS current 593 DESCRIPTION 594 "Type of tunnel used to instantiate the PMSI." 595 ::= { mvpnPmsiConfigEntry 1 } 597 mvpnPmsiConfigTunnelAuxInfo OBJECT-TYPE 598 SYNTAX Unsigned32 599 MAX-ACCESS read-write 600 STATUS current 601 DESCRIPTION 602 "Additional tunnel information depending on the type. 603 pim: In case of S-PMSI, number of groups starting at 604 mvpnPmsiConfigTunnelPimGroupAddress. 605 This allows a range of PIM provider tunnel 606 group addresses to be specified in S-PMSI case. 608 In I-PMSI case, it must be 1. 609 rsvp-p2mp: 1 for statically specified rsvp-p2mp tunnel 610 2 for dynamically created rsvp-p2mp tunnel 611 ingress-replication: 612 1 for using any existing p2p/mp2p lsp 613 2 for dynamically creating new p2p lsp" 614 ::= { mvpnPmsiConfigEntry 2 } 616 mvpnPmsiConfigTunnelPimGroupAddressType OBJECT-TYPE 617 SYNTAX InetAddressType 618 MAX-ACCESS read-write 619 STATUS current 620 DESCRIPTION 621 "In case of PIM provider tunnel, the type of tunnel address." 622 ::= { mvpnPmsiConfigEntry 3 } 624 mvpnPmsiConfigTunnelPimGroupAddress OBJECT-TYPE 625 SYNTAX InetAddress 626 MAX-ACCESS read-write 627 STATUS current 628 DESCRIPTION 629 "In case of PIM provider tunnel, the provider tunnel address." 630 ::= { mvpnPmsiConfigEntry 4 } 632 mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE 633 SYNTAX SnmpAdminString 634 MAX-ACCESS read-write 635 STATUS current 636 DESCRIPTION 637 "The tunnel name or template name used to create tunnels. 638 Depending on mvpnPmsiConfigTunnelType and 639 mvpnPmsiConfigTunnelAuxInfo: 641 dynamically created rsvp-p2mp tunnel: template name 642 statically specified rsvp-p2mp tunnel: tunnel name 643 ingress-replication using 644 dynamically created lsps: template name 645 other: null" 646 ::= { mvpnPmsiConfigEntry 5 } 648 mvpnPmsiConfigEncapsType OBJECT-TYPE 649 SYNTAX INTEGER { greIp (1), 650 ipIp (2), 651 mpls (3) 652 } 653 MAX-ACCESS read-write 654 STATUS current 655 DESCRIPTION 656 "The encapsulation type to be used, in case of PIM tunnel or 657 ingress-replication." 658 ::= { mvpnPmsiConfigEntry 6 } 660 mvpnPmsiConfigRowStatus OBJECT-TYPE 661 SYNTAX RowStatus 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION 665 "Used to create/modify/delete a row in this table." 666 ::= { mvpnPmsiConfigEntry 7 } 668 -- S-PMSI configuration table 670 mvpnSpmsiConfigTable OBJECT-TYPE 671 SYNTAX SEQUENCE OF MvpnSpmsiConfigEntry 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "This table specifies S-PMSI configuration." 676 ::= { mvpnConfig 2 } 678 mvpnSpmsiConfigEntry OBJECT-TYPE 679 SYNTAX MvpnSpmsiConfigEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "An entry is created for each S-PMSI configuration." 684 INDEX { mplsVpnVrfName, 685 mvpnSpmsiConfigCmcastAddressType, 686 mvpnSpmsiConfigCmcastGroupAddress, 687 mvpnSpmsiConfigCmcastGroupPrefixLen, 688 mvpnSpmsiConfigCmcastSourceAddress, 689 mvpnSpmsiConfigCmcastSourcePrefixLen } 690 ::= { mvpnSpmsiConfigTable 1 } 692 MvpnSpmsiConfigEntry ::= SEQUENCE { 693 mvpnSpmsiConfigCmcastAddressType InetAddressType, 694 mvpnSpmsiConfigCmcastGroupAddress InetAddress, 695 mvpnSpmsiConfigCmcastGroupPrefixLen Unsigned32, 696 mvpnSpmsiConfigCmcastSourceAddress InetAddress, 697 mvpnSpmsiConfigCmcastSourcePrefixLen Unsigned32, 698 mvpnSpmsiConfigThreshold Unsigned32, 699 mvpnSpmsiConfigPmsiPointer RowPointer, 700 mvpnSpmsiConfigRowStatus RowStatus 701 } 703 mvpnSpmsiConfigCmcastAddressType OBJECT-TYPE 704 SYNTAX InetAddressType 705 MAX-ACCESS read-write 706 STATUS current 707 DESCRIPTION 708 "Type of C-multicast address" 709 ::= { mvpnSpmsiConfigEntry 1 } 711 mvpnSpmsiConfigCmcastGroupAddress OBJECT-TYPE 712 SYNTAX InetAddress 713 MAX-ACCESS read-write 714 STATUS current 715 DESCRIPTION 716 "C-multicast group address" 717 ::= { mvpnSpmsiConfigEntry 2 } 719 mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE 720 SYNTAX Unsigned32 721 MAX-ACCESS read-write 722 STATUS current 723 DESCRIPTION 724 "C-multicast group address prefix length. 725 A group 0 (or ::0) with prefix length 32 (or 128) 726 indicates wildcard group, while a group 0 (or ::0) 727 with prefix length 0 indicates any group." 728 ::= { mvpnSpmsiConfigEntry 3 } 730 mvpnSpmsiConfigCmcastSourceAddress OBJECT-TYPE 731 SYNTAX InetAddress 732 MAX-ACCESS read-write 733 STATUS current 734 DESCRIPTION 735 "C-multicast source address" 736 ::= { mvpnSpmsiConfigEntry 4 } 738 mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE 739 SYNTAX Unsigned32 740 MAX-ACCESS read-write 741 STATUS current 742 DESCRIPTION 743 "C-multicast source address prefix length. 744 A source 0 (or ::0) with prefix length 32 (or 128) 745 indicates a wildcard source, while a source 0 (or ::0) 746 with prefix length 0 indicates any source." 747 ::= { mvpnSpmsiConfigEntry 5 } 749 mvpnSpmsiConfigThreshold OBJECT-TYPE 750 SYNTAX Unsigned32 (0..4294967295) 751 UNITS "kilobits per second" 752 MAX-ACCESS read-write 753 STATUS current 754 DESCRIPTION 755 "The bandwidth threshold value which when exceeded for a 756 multicast routing entry in the given MVRF, triggers usage 757 of S-PMSI." 758 ::= { mvpnSpmsiConfigEntry 6 } 760 mvpnSpmsiConfigPmsiPointer OBJECT-TYPE 761 SYNTAX RowPointer 762 MAX-ACCESS read-write 763 STATUS current 764 DESCRIPTION 765 "This points to a row in mvpnPmsiConfigTable, 766 to specify tunnel attributes." 767 ::= { mvpnSpmsiConfigEntry 7 } 769 mvpnSpmsiConfigRowStatus OBJECT-TYPE 770 SYNTAX RowStatus 771 MAX-ACCESS read-create 772 STATUS current 773 DESCRIPTION 774 "Used to create/modify/delete a row in this table." 775 ::= { mvpnSpmsiConfigEntry 8 } 777 -- Table of intra-as I-PMSIs advertised/received 779 mvpnIpmsiTable OBJECT-TYPE 780 SYNTAX SEQUENCE OF MvpnIpmsiEntry 781 MAX-ACCESS not-accessible 782 STATUS current 783 DESCRIPTION 784 "This table is for all advertised/received I-PMSI 785 advertisements." 786 ::= { mvpnStates 1 } 788 mvpnIpmsiEntry OBJECT-TYPE 789 SYNTAX MvpnIpmsiEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "An entry in this table corresponds to an I-PMSI 794 advertisement that is advertised/received on this router. 795 This represents all the sender PEs in the MVPN, 796 with the provider tunnel they use to send traffic." 797 INDEX { mplsVpnVrfName, 798 mvpnIpmsiRD, 799 mvpnIpmsiOrigAddrType, 800 mvpnIpmsiOrigAddress } 801 ::= { mvpnIpmsiTable 1 } 803 MvpnIpmsiEntry ::= SEQUENCE { 804 mvpnIpmsiRD MplsVpnRouteDistinguisher, 805 mvpnIpmsiOrigAddrType InetAddressType, 806 mvpnIpmsiOrigAddress InetAddress, 807 mvpnIpmsiUpTime TimeInterval, 808 mvpnIpmsiAttribute RowPointer 809 } 811 mvpnIpmsiRD OBJECT-TYPE 812 SYNTAX MplsVpnRouteDistinguisher 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "The Route Distinguisher in this I-PMSI." 817 ::= { mvpnIpmsiEntry 1 } 819 mvpnIpmsiOrigAddrType OBJECT-TYPE 820 SYNTAX InetAddressType 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "The Internet address type of mvpnIpmsiOrigAddress." 825 ::= { mvpnIpmsiEntry 2 } 827 mvpnIpmsiOrigAddress OBJECT-TYPE 828 SYNTAX InetAddress 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "The BGP address of the device that originated the I-PMSI." 833 ::= { mvpnIpmsiEntry 3 } 835 mvpnIpmsiUpTime OBJECT-TYPE 836 SYNTAX TimeInterval 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The time since this I-PMSI 841 was first advertised/received by the device." 842 ::= { mvpnIpmsiEntry 4 } 844 mvpnIpmsiAttribute OBJECT-TYPE 845 SYNTAX RowPointer 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 850 ::= { mvpnIpmsiEntry 5 } 852 -- Table of inter-as I-PMSIs advertised/received 854 mvpnInterAsIpmsiTable OBJECT-TYPE 855 SYNTAX SEQUENCE OF MvpnInterAsIpmsiEntry 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "This table is for all advertised/received inter-as I-PMSI 860 advertisements." 861 ::= { mvpnStates 2 } 863 mvpnInterAsIpmsiEntry OBJECT-TYPE 864 SYNTAX MvpnInterAsIpmsiEntry 865 MAX-ACCESS not-accessible 866 STATUS current 867 DESCRIPTION 868 "An entry in this table corresponds to an inter-as I-PMSI 869 advertisement that is advertised/received on this router. 870 This represents all the ASes in the MVPN, 871 with the provider tunnel used to send traffic to." 872 INDEX { mplsVpnVrfName, 873 mvpnInterAsIpmsiRD, 874 mvpnInterAsIpmsiSrcAs } 875 ::= { mvpnInterAsIpmsiTable 1 } 877 MvpnInterAsIpmsiEntry ::= SEQUENCE { 878 mvpnInterAsIpmsiRD MplsVpnRouteDistinguisher, 879 mvpnInterAsIpmsiSrcAs Unsigned32, 880 mvpnInterAsIpmsiAttribute RowPointer 881 } 883 mvpnInterAsIpmsiRD OBJECT-TYPE 884 SYNTAX MplsVpnRouteDistinguisher 885 MAX-ACCESS not-accessible 886 STATUS current 887 DESCRIPTION 888 "The Route Distinguisher in this inter-as I-PMSI." 889 ::= { mvpnInterAsIpmsiEntry 1 } 891 mvpnInterAsIpmsiSrcAs OBJECT-TYPE 892 SYNTAX Unsigned32 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "The source-as in this inter-as I-PMSI." 897 ::= { mvpnInterAsIpmsiEntry 2 } 899 mvpnInterAsIpmsiAttribute OBJECT-TYPE 900 SYNTAX RowPointer 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION 904 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 905 ::= { mvpnInterAsIpmsiEntry 3 } 907 -- Table of S-PMSIs advertised/received 909 mvpnSpmsiTable OBJECT-TYPE 910 SYNTAX SEQUENCE OF MvpnSpmsiEntry 911 MAX-ACCESS not-accessible 912 STATUS current 913 DESCRIPTION 914 "This table has information about the S-PMSIs sent/received 915 by a device." 916 ::= { mvpnStates 3 } 918 mvpnSpmsiEntry OBJECT-TYPE 919 SYNTAX MvpnSpmsiEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "An entry in this table is created or updated for every S-PMSI 924 advertised/received in a particular MVRF." 925 INDEX { mplsVpnVrfName, 926 mvpnSpmsiCmcastAddrType, 927 mvpnSpmsiCmcastGroup, 928 mvpnSpmsiCmcastGroupPrefixLen, 929 mvpnSpmsiCmcastSource, 930 mvpnSpmsiCmcastSourcePrefixLen, 931 mvpnSpmsiOrigAddrType, 932 mvpnSpmsiOrigAddress} 933 ::= { mvpnSpmsiTable 1 } 935 MvpnSpmsiEntry ::= SEQUENCE { 936 mvpnSpmsiCmcastAddrType InetAddressType, 937 mvpnSpmsiCmcastGroup InetAddress, 938 mvpnSpmsiCmcastGroupPrefixLen Unsigned32, 939 mvpnSpmsiCmcastSource InetAddress, 940 mvpnSpmsiCmcastSourcePrefixLen Unsigned32, 941 mvpnSpmsiOrigAddrType InetAddressType, 942 mvpnSpmsiOrigAddress InetAddress, 943 mvpnSpmsiTunnelAttribute RowPointer, 944 mvpnSpmsiUpTime TimeInterval, 945 mvpnSpmsiExpTime TimeInterval, 946 mvpnSpmsiRefCnt Unsigned32 947 } 949 mvpnSpmsiCmcastAddrType OBJECT-TYPE 950 SYNTAX InetAddressType 951 MAX-ACCESS not-accessible 952 STATUS current 953 DESCRIPTION 954 "The Internet address type of mvpnSpmsiCmcastGroup/Source." 955 ::= { mvpnSpmsiEntry 1 } 957 mvpnSpmsiCmcastGroup OBJECT-TYPE 958 SYNTAX InetAddress (SIZE (4|16|20)) 959 MAX-ACCESS not-accessible 960 STATUS current 961 DESCRIPTION 962 "S-PMSI C-multicast group address. 963 If it is 0 (or ::0), this is a wildcard group, 964 and mvpnSpmsiCmcastGroupPrefixLen must be 32 (or 128)." 965 ::= { mvpnSpmsiEntry 2 } 967 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 968 SYNTAX Unsigned32 969 MAX-ACCESS not-accessible 970 STATUS current 971 DESCRIPTION 972 "S-PMSI C-multicast group address prefix length." 973 ::= { mvpnSpmsiEntry 3 } 975 mvpnSpmsiCmcastSource OBJECT-TYPE 976 SYNTAX InetAddress (SIZE (4|16|20)) 977 MAX-ACCESS not-accessible 978 STATUS current 979 DESCRIPTION 980 "S-PMSI C-multicast source address 981 If it is 0 (or ::0), this is a wildcard source, 982 and mvpnSpmsiCmcastSourcePrefixLen must be 32 (or 128)." 983 ::= { mvpnSpmsiEntry 4 } 985 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 986 SYNTAX Unsigned32 987 MAX-ACCESS not-accessible 988 STATUS current 989 DESCRIPTION 990 "S-PMSI C-multicast source address prefix length." 991 ::= { mvpnSpmsiEntry 5 } 993 mvpnSpmsiOrigAddrType OBJECT-TYPE 994 SYNTAX InetAddressType 995 MAX-ACCESS not-accessible 996 STATUS current 997 DESCRIPTION 998 "The Internet address type of mvpnSpmsiOrigAddress." 999 ::= { mvpnSpmsiEntry 6 } 1001 mvpnSpmsiOrigAddress OBJECT-TYPE 1002 SYNTAX InetAddress 1003 MAX-ACCESS not-accessible 1004 STATUS current 1005 DESCRIPTION 1006 "The BGP address of the device that originated the S-PMSI." 1007 ::= { mvpnSpmsiEntry 7 } 1009 mvpnSpmsiTunnelAttribute OBJECT-TYPE 1010 SYNTAX RowPointer 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "A row pointer to the l2L3VpnMcastPmsiTunnelAttributeTable" 1015 ::= { mvpnSpmsiEntry 8 } 1017 mvpnSpmsiUpTime OBJECT-TYPE 1018 SYNTAX TimeInterval 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION 1022 "The time since this S-PMSI 1023 was first advertised/received by the device." 1024 ::= { mvpnSpmsiEntry 9 } 1026 mvpnSpmsiExpTime OBJECT-TYPE 1027 SYNTAX TimeInterval 1028 MAX-ACCESS read-only 1029 STATUS current 1030 DESCRIPTION 1031 "For UDP-based S-PMSI signaling for PIM-MVPN, 1032 the amount of time remaining before this 1033 received S-PMSI Join Message expires, 1034 or the next S-PMSI Join Message refresh is to be 1035 advertised again from the device." 1036 ::= { mvpnSpmsiEntry 10 } 1038 mvpnSpmsiRefCnt OBJECT-TYPE 1039 SYNTAX Unsigned32 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "The number of c-multicast routes that are mapped to 1044 this S-PMSI." 1045 ::= { mvpnSpmsiEntry 11 } 1047 -- Table of multicast routes in an MVPN 1049 mvpnMrouteTable OBJECT-TYPE 1050 SYNTAX SEQUENCE OF MvpnMrouteEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "This table augments ipMcastRouteTable, to provide some MVPN 1055 specific information." 1056 ::= { mvpnStates 4 } 1058 mvpnMrouteEntry OBJECT-TYPE 1059 SYNTAX MvpnMrouteEntry 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "The mvpnMrouteEntry matches and augments an ipMcastRouteEntry, 1064 with MVPN specific information, such as PMSI used." 1065 AUGMENTS { ipMcastRouteEntry } 1066 ::= { mvpnMrouteTable 1 } 1068 MvpnMrouteEntry ::= SEQUENCE { 1069 mvpnMroutePmsiPointer RowPointer, 1070 mvpnMrouteNumberOfLocalReplication Unsigned32, 1071 mvpnMrouteNumberOfRemoteReplication Unsigned32, 1072 mvpnMrouteDataRate Unsigned32 1073 } 1075 mvpnMroutePmsiPointer OBJECT-TYPE 1076 SYNTAX RowPointer 1077 MAX-ACCESS read-only 1078 STATUS current 1079 DESCRIPTION 1080 "The I-PMSI or S-PMSI this C-multicast route is using. 1081 This is important because an implementation may not have an 1082 interface corresponding to a provider tunnel, 1083 that can be used in ipMcastRouteNextHopEntry." 1084 ::= { mvpnMrouteEntry 1 } 1086 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1087 SYNTAX Unsigned32 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION 1091 "Number of replications to local receivers." 1092 ::= { mvpnMrouteEntry 2 } 1094 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1095 SYNTAX Unsigned32 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "Number of (local) replications to remote receivers." 1100 ::= { mvpnMrouteEntry 3 } 1102 mvpnMrouteDataRate OBJECT-TYPE 1103 SYNTAX Unsigned32 (0..4294967295) 1104 UNITS "kilobits per second" 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "The data rate for traffic following this route." 1109 ::= { mvpnMrouteDataRate 4 } 1111 -- MVPN Notifications 1113 mvpnMvrfChange NOTIFICATION-TYPE 1114 OBJECTS { 1115 mvpnGenOperStatusChange 1116 } 1117 STATUS current 1118 DESCRIPTION 1119 "A mvpnMvrfChange notification signifies a change about 1120 a MVRF in the device. The change event can be creation of 1121 the MVRF, deletion of the MVRF or an update on the I-PMSI 1122 or S-PMSI configuration of the MVRF. The change event 1123 is indicated by mvpnGenOperStatusChange embedded in 1124 the notification. The user can then query 1125 mvpnGeneralTable, and/or mvpnSpmsiConfigTable to 1126 get the details of the change as necessary. 1128 Note: Since the creation of a MVRF is often followed by 1129 configuration of I-PMSI and/or S-PMSIs for the MVRF, 1130 more than one (three at most) notifications for a MVRF may 1131 be generated serially, and it is really not necessary to 1132 generate all three of them. An agent may choose to generate a 1133 notification for the last event only, that is for S-PMSI 1134 configuration. 1136 Similarly, deletion of I-PMSI and S-PMSI configuration on a 1137 MVRF happens before a MVRF is deleted and it is recommended 1138 that the agent send the notification for MVRF deletion 1139 event only." 1140 ::= { mvpnNotifications 2 } 1141 END 1143 3 Security Considerations 1145 1147 4 IANA Considerations 1149 1151 5 Acknowledgement 1153 Some of the text has been taken almost verbatim from [CISCO-MIB]. 1155 We would like to thank Yakov Rekhter, Jeffrey Haas, Huajin Jeng, 1156 Durga Prasad Velamuri for their helpful comments. 1158 6 References 1160 6.1 Normative References 1162 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 1163 Requirement Levels", BCP 14, RFC 2119, March 1997. 1165 [RFC4382] Nadeau, T., Ed., and H. van der Linde, Ed., "MPLS/BGP 1166 Layer 3 Virtual Private Network (VPN) Management 1167 Information Base", RFC 4382, February 2006. 1169 [MROUTE-MIB]McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 1170 MIB", RFC 5132, December 2007. 1172 [MVPN] Eric C. Rosen, Rahul Aggarwal, et. al., Multicast in MPLS/BGP 1173 IP VPNs, RFC 6513. 1175 [BGP-MVPN] R. Aggarwal, E. Rosen, T. Morin, Y. Rekhter, BGP Encodings 1176 and Procedures for Multicast in MPLS/BGP IP VPNs, RFC 1177 6514. 1179 [L2L3MVPN-MIB] Zhang, J., L2L3 VPN Multicast MIB, draft-zzhang-l2l3- 1180 vpn-mcast-mib, Work In Progress. 1182 6.2 Informative References 1184 [CISCO-MIB] Susheela Vaidya, Thomas D. Nadeau, Harmen Van der Linde, 1185 Multicast in BGP/MPLS IP VPNs Management Information Base, 1186 draft-svaidya-mcast-vpn-mib-02.txt, Work In Progress, 1187 April 2005. 1189 Authors' Addresses 1191 Saud Asif 1192 AT&T 1193 C5-3D30 1194 200 South Laurel Avenue 1195 Middletown, NJ 07748 1196 USA 1197 Email: sasif@att.com 1199 Andy Green 1200 BT Design 21CN Converged Core IP & Data 1201 01473 629360 1202 Adastral Park, Martlesham Heath, Ipswich IP5 3RE 1203 UK 1204 Email: andy.da.green@bt.com 1206 Sameer Gulrajani 1207 Cisco Systems 1208 Tasman Drive 1209 San Jose, CA 95134 1210 USA 1212 EMail: sameerg@cisco.com 1214 Pradeep G. Jain 1215 Alcatel-Lucent Inc 1216 701 E Middlefield road 1217 Mountain view, CA 94043 1218 USA 1219 Email: pradeep.jain@alcatel-lucent.com 1221 Jeffrey (Zhaohui) Zhang 1222 Juniper Networks, Inc. 1223 10 Technology Park Drive 1224 Westford, MA 01886 1225 USA 1226 Email: zzhang@juniper.net