idnits 2.17.1 draft-ietf-bess-l2l3-vpn-mcast-mib-15.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 date (August 11, 2018) is 2078 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: 'RFCXXXX' is mentioned on line 398, but not defined Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Z. Zhang 3 Internet-Draft Juniper Networks, Inc. 4 Intended status: Standards Track H. Tsunoda 5 Expires: February 12, 2019 Tohoku Institute of Technology 6 August 11, 2018 8 L2L3 VPN Multicast MIB 9 draft-ietf-bess-l2l3-vpn-mcast-mib-15 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 for use with network management protocols in the Internet community. 15 In particular, it describes two MIB modules which will be used by 16 other MIB modules for monitoring and/or configuring Layer 2 and Layer 17 3 Virtual Private Networks that support multicast. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on February 12, 2019. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 55 2. The Internet-Standard Management Framework . . . . . . . . . 4 56 3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4 57 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 58 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 4 59 4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 9 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 62 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17 63 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 64 8.1. Normative References . . . . . . . . . . . . . . . . . . 17 65 8.2. Informative References . . . . . . . . . . . . . . . . . 19 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 68 1. Introduction 70 In BGP/MPLS Virtual Private Networks (VPNs), Border Gateway Protocol 71 (BGP) is used for distributing routes and MultiProtocol Label 72 Switching (MPLS) is used for forwarding packets accross service 73 provider networks. 75 The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN 76 are specified in [RFC6513]. The procedures for supporting multicast 77 in BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117]. Throughout 78 this document, we will use the term "L2L3VpnMCast network" to mean 79 BGP/MPLS L2 and L3 VPN that support multicast. 81 L2L3VpnMCast networks use various transport mechanisms for forwarding 82 a packet to all or a subset of Provider Edge routers (PEs) across 83 service provider networks. These transport mechanisms are abstracted 84 as provider tunnels (P-tunnels). The type of a P-tunnel indicates 85 the type of the tunneling technology used to establish the P-tunnel. 86 The syntax and semantics of a Tunnel identifier is determined by the 87 corresponding P-tunnel type [RFC6514]. P-tunnel type and P-tunnel 88 identifier together identify a P-tunnel. 90 A BGP attribute that specifies information of a P-tunnel is called 91 Provider Multicast Service Interface (PMSI) tunnel attribute. The 92 PMSI tunnel attribute is advertised/received by PEs in BGP auto- 93 discovery (A-D) routes. [RFC6514] defines the format of a PMSI 94 tunnel attribute. P-tunnel type and the P-tunnel identifier are 95 included in the corresponding PMSI tunnel attribute. 97 This document describes textual conventions (TCs) and common managed 98 objects (MOs) which will be used by other Management Information Base 99 (MIB) modules for monitoring and/or configuring L2L3VpnMCast 100 networks. 102 This document defines two TCs to represent 104 (a) the type of a P-tunnel and 105 (b) the identifier of a P-tunnel 107 respectively. 109 The document also defines MOs that will provide the information 110 contained in a PMSI tunnel attribute and corresponding P-tunnel 111 information. 113 1.1. Terminology 115 This document adopts the definitions, acronyms and mechanisms 116 described in [RFC6513] [RFC6514] [RFC7117] and other documents that 117 they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN, 118 Multicast VPN concepts and/or mechanisms is assumed. Some terms 119 specifically related to this document are explained below. 121 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 122 conceptual interface instantiated by a P-tunnel, a transport 123 mechanism used to deliver multicast traffic. A PE uses it to send 124 customer multicast traffic to all or some PEs in the same VPN. 126 There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and 127 "Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that 128 enables a PE attached to a particular Multicast VPN to transmit a 129 message to all PEs in the same VPN. An S-PMSI is a PMSI that enables 130 a PE attached to a particular Multicast VPN to transmit a message to 131 some of the PEs in the same VPN. 133 Throughout this document, we will use the term "PMSI" to refer both 134 "I-PMSI" and "S-PMSI." 136 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 137 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 138 "OPTIONAL" in this document are to be interpreted as described in BCP 139 14 [RFC2119] [RFC8174] when, and only when, they appear in all 140 capitals, as shown here. 142 2. The Internet-Standard Management Framework 144 For a detailed overview of the documents that describe the current 145 Internet-Standard Management Framework, please refer to section 7 of 146 RFC 3410 [RFC3410]. 148 Managed objects are accessed via a virtual information store, termed 149 the Management Information Base or MIB. MIB objects are generally 150 accessed through the Simple Network Management Protocol (SNMP). 151 Objects in the MIB are defined using the mechanisms defined in the 152 Structure of Management Information (SMI). This memo specifies a MIB 153 module that is compliant to the SMIv2, which is described in STD 58, 154 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 155 [RFC2580]. 157 3. Summary of MIB Modules 159 This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and 160 L2L3-VPN-MCAST-MIB. 162 o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions: 163 L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId. 164 L2L3VpnMcastProviderTunnelType provides an enumeration of the 165 P-tunnel types. L2L3VpnMcastProviderTunnelId represents an 166 identifier of a P-tunnel. 168 o L2L3-VPN-MCAST-MIB defines a table 169 l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table 170 corresponds to the attribute information of a specific P-tunnel on 171 a PE router. Entries in this table will be used by other MIB 172 modules for monitoring and/or configuring L2L3VpnMCast network. 173 The table index uniquely identifies a P-tunnel. It is composed of 174 a type and indentifier of a P-tunnel. The table may also be used 175 in conjunction with other MIBs, such as MPLS Traffic Engineering 176 MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information 177 about a P-tunnel. It may also be used in conjunction with the 178 Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further 179 information about the interface corresponding to a P-tunnel. 181 4. Definitions 183 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 185 L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN 187 IMPORTS 188 MODULE-IDENTITY, mib-2 189 FROM SNMPv2-SMI -- [RFC2578] 191 TEXTUAL-CONVENTION 192 FROM SNMPv2-TC; -- [RFC2579] 194 l2L3VpnMcastTCMIB MODULE-IDENTITY 195 LAST-UPDATED "201808101200Z" -- 10th August, 2018 196 ORGANIZATION "IETF BESS Working Group." 197 CONTACT-INFO 198 " Zhaohui Zhang 199 Juniper Networks, Inc. 200 10 Technology Park Drive 201 Westford, MA 01886 202 USA 203 Email: zzhang@juniper.net 205 Hiroshi Tsunoda 206 Tohoku Institute of Technology 207 35-1, Yagiyama Kasumi-cho 208 Taihaku-ku, Sendai, 982-8577 209 Japan 210 Email: tsuno@m.ieice.org 212 Comments and discussion to bess@ietf.org 213 " 214 DESCRIPTION 215 "This MIB module specifies textual conventions for 216 Border Gateway Protocol/MultiProtocol Label 217 Switching Layer 2 and Layer 3 Virtual Private Networks 218 that support multicast (L2L3VpnMCast networks). 220 Copyright (C) The Internet Society (2018). 221 " 223 -- Revision history. 225 REVISION "201808101200Z" -- 10th August, 2018 226 DESCRIPTION 227 "Initial version, published as RFC XXXX." 229 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 231 ::= { mib-2 AAAA } 233 -- IANA Reg.: Please assign a value for "AAAA" under the 234 -- 'mib-2' subtree and record the assignment in the SMI 235 -- Numbers registry. 237 -- RFC Ed.: When the above assignment has been made, please 238 -- remove the above note 239 -- replace "AAAA" here with the assigned value and 240 -- remove this note. 242 -- Textual convention 244 L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION 245 STATUS current 246 DESCRIPTION 247 "This textual convention enumerates values 248 representing the type of a provider tunnel (P-tunnel) 249 used for L2L3VpnMCast networks. 250 These labeled numbers are aligned with the definition 251 of Tunnel types in Section 5 of [RFC6514] and 252 Section 14.1 of [RFC7524]. 254 The enumerated values and the corresponding P-tunnel types 255 are as follows: 257 noTunnelInfo (0) : no tunnel information present 258 [RFC6514] 259 rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875] 260 ldpP2mp (2) : mLDP P2MP LSP [RFC6388] 261 pimSsm (3) : PIM-SSM Tree [RFC7761] 262 pimAsm (4) : PIM-SM Tree [RFC7761] 263 pimBidir (5) : BIDIR-PIM Tree [RFC5015] 264 ingressReplication (6) : Ingress Replication [RFC6513] 265 ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388] 266 transportTunnel (8) : Transport Tunnel [RFC7524] 268 These numbers are registered at IANA. 269 A current list of assignments can be found at 270 . 272 " 273 REFERENCE 274 "RFC4875 275 RFC5015 276 RFC6388 277 RFC6513 278 RFC6514, Section 5 279 RFC7524, Section 14.1 280 RFC7761 281 " 283 SYNTAX INTEGER 284 { 285 noTunnelInfo (0), 286 rsvpP2mp (1), 287 ldpP2mp (2), 288 pimSsm (3), 289 pimAsm (4), 290 pimBidir (5), 291 ingressReplication (6), 292 ldpMp2mp (7), 293 transportTunnel (8) 294 } 296 L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION 297 STATUS current 298 DESCRIPTION 299 "This textual convention represents the tunnel identifier 300 of a P-tunnel. 302 The size of the identifier depends on the address family 303 (IPv4 or IPv6) and the value of the corresponding 304 L2L3VpnMcastProviderTunnelType object. 306 The corresponding L2L3VpnMcastProviderTunnelType object 307 represents the type of the tunneling technology used 308 to establish the P-tunnel. 310 The size of the identifier for each tunneling technology 311 is summarized below. 313 L2L3VpnMcastProviderTunnelType Size (in octets) 314 (tunneling technology) IPv4 IPv6 315 ----------------------------------------------------------- 316 noTunnelInfo (No tunnel information) 0 0 317 rsvpP2mp (RSVP-TE P2MP LSP) 12 24 318 ldpP2mp (mLDP P2MP LSP) 17 29 319 pimSsm (PIM-SSM Tree) 8 32 320 pimAsm (PIM-SM Tree) 8 32 321 pimBidir (BIDIR-PIM Tree) 8 32 322 ingressReplication (Ingress Replication) 4 16 323 ldpMp2mp (mLDP MP2MP LSP) 17 29 324 transportTunnel (Transport Tunnel) 8 32 326 Tunnel type is set to 'No tunnel information present' 327 when the PMSI Tunnel attribute carries no tunnel 328 information (there is no Tunnel Identifier). 329 The value of the corresponding L2L3VpnMcastProviderTunnelId 330 object will be a string of length zero. 332 For tunnel type rsvpP2mp(1), the corresponding Tunnel 333 Identifier is composed of Extended Tunnel ID (4 octets in IPv4, 334 16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets), 335 and P2MP ID (4 octets). 336 The size of the corresponding L2L3VpnMcastProviderTunnelId 337 object will be 12 octets in IPv4 and 24 octets in IPv6. 339 For tunnel type ldpP2mp(2), the corresponding Tunnel Identifier 340 is the P2MP Forwarding Equivalence Class (FEC) Element 341 [RFC6388]. The size of the corresponding 342 L2L3VpnMcastProviderTunnelId object will be 17 octets 343 in IPv4 and 29 octets in IPv6. 345 For tunnel type pimSsm(3), PimAsm(4), and PimBidir(5), the 346 corresponding Tunnel Identifier is composed of the source IP 347 address and the group IP address. 348 The size of the corresponding L2L3VpnMcastProviderTunnelId 349 object will be 8 octets in IPv4 and 32 octets in IPv6. 351 For tunnel type ingressReplication(6), the Tunnel Identifier is 352 the unicast tunnel endpoint IP address of the local PE. 353 The size of the corresponding L2L3VpnMcastProviderTunnelId 354 object will be 4 octets in IPv4 and 16 octets in IPv6. 356 For tunnel type ldpMp2mp(7), the Tunnel Identifier is 357 MP2MP FEC Element [RFC6388]. 358 The size of the corresponding L2L3VpnMcastProviderTunnelId 359 object will be 17 octets in IPv4 and 29 octets in IPv6. 361 For tunnel type transportTunnel(8), the Tunnel Identifier 362 is a tuple of Source PE Address and Local Number, 363 which is a number that is unique to the Source PE [RFC7524]. 364 Both Source PE Address and Local Number are 4 octets in IPv4 365 and 16 octets in IPv6. 366 The size of the corresponding L2L3VpnMcastProviderTunnelId 367 object will be 8 octets in IPv4 and 32 octets in IPv6. 368 " 369 REFERENCE 370 "RFC6514, Section 5 371 RFC4875, Section 19.1 372 RFC6388, Section 2.2 and 3.2 373 RFC7524, Section 14.1 374 " 375 SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) 377 END 379 4.2. L2L3-VPN-MCAST-MIB Object Definitions 381 L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN 383 IMPORTS 384 MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero 385 FROM SNMPv2-SMI -- [RFC2578] 387 MODULE-COMPLIANCE, OBJECT-GROUP 388 FROM SNMPv2-CONF -- [RFC2580] 390 RowPointer 391 FROM SNMPv2-TC -- [RFC2579] 393 MplsLabel 394 FROM MPLS-TC-STD-MIB -- [RFC3811] 396 L2L3VpnMcastProviderTunnelType, 397 L2L3VpnMcastProviderTunnelId 398 FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX] 400 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 402 l2L3VpnMcastMIB MODULE-IDENTITY 403 LAST-UPDATED "201808101200Z" -- 10th August, 2018 404 ORGANIZATION "IETF BESS Working Group." 405 CONTACT-INFO 406 " Zhaohui Zhang 407 Juniper Networks, Inc. 408 10 Technology Park Drive 409 Westford, MA 01886 410 USA 411 Email: zzhang@juniper.net 413 Hiroshi Tsunoda 414 Tohoku Institute of Technology 415 35-1, Yagiyama Kasumi-cho 416 Taihaku-ku, Sendai, 982-8577 417 Japan 418 Email: tsuno@m.ieice.org 420 Comments and discussion to bess@ietf.org 421 " 423 DESCRIPTION 424 "This MIB module defines a table representing the attribute 425 information of the provider tunnels (P-tunnels) on a PE router. 426 This MIB module will be used by other MIB modules designed for 427 monitoring and/or configuring Border Gateway 428 Protocol/MultiProtocol Label Switching 429 Layer 2 and Layer 3 Virtual Private 430 Network that support multicast (L2L3VpnMCast network). 431 Copyright (C) The Internet Society (2018). 432 " 433 -- Revision history. 435 REVISION "201808101200Z" -- 10th August, 2018 436 DESCRIPTION 437 "Initial version, published as RFC XXXX." 439 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 441 ::= { mib-2 BBBB } 443 -- IANA Reg.: Please assign a value for "BBBB" under the 444 -- 'mib-2' subtree and record the assignment in the SMI 445 -- Numbers registry. 447 -- RFC Ed.: When the above assignment has been made, please 448 -- remove the above note 449 -- replace "BBBB" here with the assigned value and 450 -- remove this note. 452 -- Top level components of this MIB. 453 l2L3VpnMcastStates OBJECT IDENTIFIER 454 ::= { l2L3VpnMcastMIB 1 } 456 l2L3VpnMcastConformance OBJECT IDENTIFIER 457 ::= { l2L3VpnMcastMIB 2 } 459 -- tables, scalars, conformance information 460 -- Table of PMSI Tunnel Attributes 462 l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE 463 SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "An entry in this table corresponds to 468 the attribute information of a specific 469 P-tunnel on a PE router. 470 A part of attributes correspond to fields in 471 a Provider Multicast Service Interface (PMSI) Tunnel 472 attribute advertised and received by a PE router. 473 The entries will be referred to by other MIB modules 474 for monitoring and/or configuring L2L3VpnMCast networks. 475 " 476 REFERENCE 477 "RFC6514, Section 5" 478 ::= { l2L3VpnMcastStates 1 } 480 l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE 481 SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry 482 MAX-ACCESS not-accessible 483 STATUS current 484 DESCRIPTION 485 "A conceptual row corresponding to a specific 486 P-tunnel on this router. 487 " 488 REFERENCE 489 "RFC6514, Section 5" 490 INDEX { 491 l2L3VpnMcastPmsiTunnelAttributeType, 492 l2L3VpnMcastPmsiTunnelAttributeId 493 } 494 ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } 496 L2L3VpnMcastPmsiTunnelAttributeEntry ::= 497 SEQUENCE { 498 l2L3VpnMcastPmsiTunnelAttributeType 499 L2L3VpnMcastProviderTunnelType, 500 l2L3VpnMcastPmsiTunnelAttributeId 501 L2L3VpnMcastProviderTunnelId, 502 l2L3VpnMCastPmsiTunnelLeafInfoRequired 503 INTEGER, 504 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 505 MplsLabel, 506 l2L3VpnMcastPmsiTunnelPointer 507 RowPointer, 508 l2L3VpnMcastPmsiTunnelIf 509 RowPointer 510 } 512 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE 513 SYNTAX L2L3VpnMcastProviderTunnelType 514 MAX-ACCESS not-accessible 515 STATUS current 516 DESCRIPTION 517 "This object indicates the type of the tunneling technology 518 used to establish the P-tunnel corresponding to this entry. 520 When BGP-based PMSI signaling is used, the value of 521 this object corresponds to the Tunnel Type field 522 in the PMSI Tunnel attribute advertised/received 523 in a PMSI auto-discovery (A-D) route. 524 " 525 REFERENCE 526 "RFC6514, Section 5" 527 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 529 l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 530 SYNTAX L2L3VpnMcastProviderTunnelId 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "This object represents the Tunnel Identifier field, which 535 uniquely identifies a P-tunnel, in the PMSI Tunnel attribute 536 of the P-tunnel corresponding to this entry. 538 The size of the identifier depends on the address family 539 (IPv4 or IPv6) and the value of the corresponding 540 l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of 541 the tunneling technology used to establish the P-tunnel. 542 " 543 REFERENCE 544 "RFC6514, Section 5" 545 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } 547 l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE 548 SYNTAX INTEGER { 549 false (0), 550 true (1), 551 notAvailable (2) 552 } 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "When the value of this object is set to 1 (true), 557 it indicates that the PE which originated the 558 PMSI Tunnel attribute of the P-tunnel corresponding 559 to this entry requests receivers to originate 560 a new Leaf A-D (Auto-Discovery) route. 562 A value of 0 (false) indicates that there is no such 563 request. 565 When the P-tunnel does not have a corresponding PMSI 566 tunnel attribute, the value of this object will be 567 2 (notAvailable). 569 In the case of Multicast in MPLS/BGP IP VPNs, 570 this object represents the 'Leaf Information Required flag' 571 [RFC6514] in the Flags field in the PMSI Tunnel attribute 572 of the P-tunnel corresponding to this entry. 573 " 574 REFERENCE 575 "RFC6514, Section 5 576 " 577 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } 579 l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE 580 SYNTAX MplsLabel 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "This object represents the MPLS Label in the PMSI Tunnel 585 attribute of the P-tunnel corresponding to this entry. 587 When BGP-based PMSI signaling is used, the PMSI Tunnel 588 attribute of the P-tunnel will be advertised/received 589 in a PMSI auto-discovery (A-D) route. The value of 590 this object corresponds to the MPLS Label in the attribute. 592 When the P-tunnel does not have a PMSI tunnel 593 attribute, the value of this object will be 0. 594 " 595 REFERENCE 596 "RFC6514, Section 5" 597 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 599 l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE 600 SYNTAX RowPointer 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "Details of a P-tunnel identified by 605 l2L3VpnMcastPmsiTunnelAttributeId may be present 606 in some other table, e.g., 607 mplsTunnelTable [RFC3812]. This object specifies 608 the pointer to the row that pertains to the entry 609 in the table. 611 If no such entry exists, the value of this object 612 will be zeroDotZero. 613 " 614 REFERENCE 615 "RFC3812, Section 6.1 and Section 11" 616 DEFVAL { zeroDotZero } 618 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 620 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE 621 SYNTAX RowPointer 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "If the P-tunnel identified by 626 l2L3VpnMcastPmsiTunnelAttributeId has a corresponding 627 entry in ifXTable [RFC2863], this object will 628 point to the row in ifXTable that pertains to the entry. 629 Otherwise, the value of this object will be zeroDotZero. 630 " 631 REFERENCE 632 "RFC2863, Section 6" 633 DEFVAL { zeroDotZero } 634 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } 636 -- Conformance Information 638 l2L3VpnMcastCompliances OBJECT IDENTIFIER 639 ::= { l2L3VpnMcastConformance 1 } 640 l2L3VpnMcastGroups OBJECT IDENTIFIER 641 ::= { l2L3VpnMcastConformance 2 } 643 -- Compliance Statements 645 l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE 646 STATUS current 647 DESCRIPTION 648 "The core compliance statement for SNMP entities 649 which implement the L2L3-VPN-MCAST-MIB Module." 650 MODULE -- this module 652 MANDATORY-GROUPS { 653 l2L3VpnMcastCoreGroup 654 } 655 ::= { l2L3VpnMcastCompliances 1 } 657 l2L3VpnMcastFullCompliance MODULE-COMPLIANCE 658 STATUS current 659 DESCRIPTION 660 "The full compliance statement for SNMP entities 661 which implement the L2L3-VPN-MCAST-MIB Module." 662 MODULE -- this module 664 MANDATORY-GROUPS { 665 l2L3VpnMcastCoreGroup, 666 l2L3VpnMcastOptionalGroup 667 } 668 ::= { l2L3VpnMcastCompliances 2 } 670 -- units of conformance 672 l2L3VpnMcastCoreGroup OBJECT-GROUP 673 OBJECTS { 674 l2L3VpnMCastPmsiTunnelLeafInfoRequired, 675 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 676 } 677 STATUS current 678 DESCRIPTION 679 "Support of these objects is required." 680 ::= { l2L3VpnMcastGroups 1 } 682 l2L3VpnMcastOptionalGroup OBJECT-GROUP 683 OBJECTS { 684 l2L3VpnMcastPmsiTunnelPointer, 685 l2L3VpnMcastPmsiTunnelIf 686 } 687 STATUS current 688 DESCRIPTION 689 "Support of these objects is optional." 690 ::= { l2L3VpnMcastGroups 2 } 692 END 694 5. Security Considerations 696 There are no management objects defined in these MIB modules that 697 have a MAX-ACCESS clause of read-write and/or read-create. So, if 698 this MIB module is implemented correctly, then there is no risk that 699 an intruder can alter or create any management objects of this MIB 700 module via direct SNMP SET operations. 702 Some of the readable objects in these MIB modules (i.e., objects with 703 a MAX-ACCESS other than not-accessible) may be considered sensitive 704 or vulnerable in some network environments. It is thus important to 705 control even GET and/or NOTIFY access to these objects and possibly 706 to even encrypt the values of these objects when sending them over 707 the network via SNMP. These are the tables and objects and their 708 sensitivity/vulnerability: 710 o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the 711 P-tunnel network topology and its performance characteristics. 712 For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will 713 contain the identifier that uniquely identifies a P-tunnel. This 714 identifier may be composed of source and multicast group IP 715 addresses. l2L3VpnMcastPmsiTunnelPointer and 716 l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries 717 in other tables containing configuration and/or performance 718 information of a P-tunnel and its interface. If an Administrator 719 does not want to reveal this information, then these objects 720 should be considered sensitive/vulnerable. 722 SNMP versions prior to SNMPv3 did not include adequate security. 723 Even if the network itself is secure (for example by using IPsec), 724 there is no control as to who on the secure network is allowed to 725 access and GET/SET (read/change/create/delete) the objects in this 726 MIB module. 728 Implementations SHOULD provide the security features described by the 729 SNMPv3 framework (see [RFC3410]), and implementations claiming 730 compliance to the SNMPv3 standard MUST include full support for 731 authentication and privacy via the User-based Security Model (USM) 732 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 733 MAY also provide support for the Transport Security Model (TSM) 734 [RFC5591] in combination with a secure transport such as SSH 735 [RFC5592] or TLS/DTLS [RFC6353]. 737 Further, deployment of SNMP versions prior to SNMPv3 is NOT 738 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 739 enable cryptographic security. It is then a customer/operator 740 responsibility to ensure that the SNMP entity giving access to an 741 instance of this MIB module is properly configured to give access to 742 the objects only to those principals (users) that have legitimate 743 rights to indeed GET or SET (change/create/delete) them. 745 6. IANA Considerations 747 The MIB module in this document uses the following IANA-assigned 748 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 750 Descriptor OBJECT IDENTIFIER value 751 ---------- ----------------------- 752 l2L3VpnMcastTCMIB { mib-2 AAAA } 753 l2L3VpnMcastMIB { mib-2 BBBB } 755 Editor's Note (to be removed prior to publication): the IANA is 756 requested to assign a value for "AAAA" and "BBBB" under the 'mib-2' 757 subtree and to record the assignment in the SMI Numbers registry. 758 When the assignment has been made, the RFC Editor is asked to replace 759 "AAAA" and "BBBB" (here and in the MIB module) with the assigned 760 value and to remove this note. 762 7. Acknowledgement 764 Glenn Mansfield Keeni did the MIB Doctor review and provided valuable 765 comments. 767 8. References 769 8.1. Normative References 771 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 772 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 773 RFC2119, March 1997, . 776 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 777 Schoenwaelder, Ed., "Structure of Management Information 778 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 779 RFC2578, April 1999, . 782 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 783 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 784 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 785 . 787 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 788 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 789 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 790 . 792 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 793 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 794 . 796 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 797 (USM) for version 3 of the Simple Network Management 798 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 799 RFC3414, December 2002, . 802 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 803 Textual Conventions (TCs) for Multiprotocol Label 804 Switching (MPLS) Management", RFC 3811, DOI 10.17487/ 805 RFC3811, June 2004, . 808 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 809 "Multiprotocol Label Switching (MPLS) Traffic Engineering 810 (TE) Management Information Base (MIB)", RFC 3812, DOI 811 10.17487/RFC3812, June 2004, . 814 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 815 Advanced Encryption Standard (AES) Cipher Algorithm in the 816 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 817 RFC3826, June 2004, . 820 [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. 821 Yasukawa, Ed., "Extensions to Resource Reservation 822 Protocol - Traffic Engineering (RSVP-TE) for Point-to- 823 Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI 824 10.17487/RFC4875, May 2007, . 827 [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 828 "Bidirectional Protocol Independent Multicast (BIDIR- 829 PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, 830 . 832 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 833 for the Simple Network Management Protocol (SNMP)", STD 834 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 835 . 837 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 838 Shell Transport Model for the Simple Network Management 839 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 840 2009, . 842 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 843 Model for the Simple Network Management Protocol (SNMP)", 844 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 845 . 847 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 848 Thomas, "Label Distribution Protocol Extensions for Point- 849 to-Multipoint and Multipoint-to-Multipoint Label Switched 850 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 851 . 853 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 854 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 855 2012, . 857 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 858 Encodings and Procedures for Multicast in MPLS/BGP IP 859 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 860 . 862 [RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and 863 C. Kodeboniya, "Multicast in Virtual Private LAN Service 864 (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014, 865 . 867 [RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T., 868 Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area 869 Point-to-Multipoint (P2MP) Segmented Label Switched Paths 870 (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, 871 . 873 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 874 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 875 Multicast - Sparse Mode (PIM-SM): Protocol Specification 876 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 877 2016, . 879 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 880 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 881 May 2017, . 883 8.2. Informative References 885 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 886 "Introduction and Applicability Statements for Internet- 887 Standard Management Framework", RFC 3410, DOI 10.17487/ 888 RFC3410, December 2002, . 891 Authors' Addresses 893 Zhaohui (Jeffrey) Zhang 894 Juniper Networks, Inc. 895 10 Technology Park Drive 896 Westford, MA 01886 897 USA 899 Email: zzhang@juniper.net 901 Hiroshi Tsunoda 902 Tohoku Institute of Technology 903 35-1, Yagiyama Kasumi-cho 904 Taihaku-ku, Sendai 982-8577 905 Japan 907 Phone: +81-22-305-3411 908 Email: tsuno@m.ieice.org