idnits 2.17.1 draft-ietf-bess-l2l3-vpn-mcast-mib-14.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 lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (February 28, 2018) is 2248 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 394, but not defined Summary: 0 errors (**), 0 flaws (~~), 3 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: September 1, 2018 Tohoku Institute of Technology 6 February 28, 2018 8 L2L3 VPN Multicast MIB 9 draft-ietf-bess-l2l3-vpn-mcast-mib-14 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 September 1, 2018. 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 . . . . . . . . . 3 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. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 63 7.1. Normative References . . . . . . . . . . . . . . . . . . 17 64 7.2. Informative References . . . . . . . . . . . . . . . . . 19 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 67 1. Introduction 69 In BGP/MPLS Virtual Private Networks (VPNs), Border Gateway Protocol 70 (BGP) is used for distributing routes and MultiProtocol Label 71 Switching (MPLS) is used for forwarding packets accross service 72 provider networks. 74 The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN 75 are specified in [RFC6513]. The procedures for supporting multicast 76 in BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117]. Throughout 77 this document, we will use the term "L2L3VpnMCast network" to mean 78 BGP/MPLS L2 and L3 VPN that support multicast. 80 L2L3VpnMCast networks use various transport mechanisms for forwarding 81 a packet to all or a subset of Provider Edge routers (PEs) across 82 service provider networks. These transport mechanisms are abstracted 83 as provider tunnels (P-tunnels). The type of a P-tunnel indicates 84 the type of the tunneling technology used to establish the P-tunnel. 85 The syntax and semantics of a Tunnel identifier is determined by the 86 corresponding P-tunnel type [RFC6514]. P-tunnel type and P-tunnel 87 identifier together identify a P-tunnel. 89 A BGP attribute that specifies information of a P-tunnel is called 90 Provider Multicast Service Interface (PMSI) tunnel attribute. The 91 PMSI tunnel attribute is advertised/received by PEs in BGP auto- 92 discovery (A-D) routes. [RFC6514] defines the format of a PMSI 93 tunnel attribute. P-tunnel type and the P-tunnel identifier are 94 included in the corresponding PMSI tunnel attribute. 96 This document describes textual conventions (TCs) and common managed 97 objects (MOs) which will be used by other Management Information Base 98 (MIB) modules for monitoring and/or configuring L2L3VpnMCast 99 networks. 101 This document defines two TCs to represent 103 (a) the type of a P-tunnel and 104 (b) the identifier of a P-tunnel 106 respectively. 108 The document also defines MOs that will provide the information 109 contained in a PMSI tunnel attribute and corresponding P-tunnel 110 information. 112 1.1. Terminology 114 This document adopts the definitions, acronyms and mechanisms 115 described in [RFC6513] [RFC6514] [RFC7117] and other documents that 116 they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN, 117 Multicast VPN concepts and/or mechanisms is assumed. Some terms 118 specifically related to this document are explained below. 120 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 121 conceptual interface instantiated by a P-tunnel, a transport 122 mechanism used to deliver multicast traffic. A PE uses it to send 123 customer multicast traffic to all or some PEs in the same VPN. 125 There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and 126 "Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that 127 enables a PE attached to a particular Multicast VPN to transmit a 128 message to all PEs in the same VPN. An S-PMSI is a PMSI that enables 129 a PE attached to a particular Multicast VPN to transmit a message to 130 some of the PEs in the same VPN. 132 Throughout this document, we will use the term "PMSI" to refer both 133 "I-PMSI" and "S-PMSI." 135 The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" 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. Summary of MIB Modules 155 This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and 156 L2L3-VPN-MCAST-MIB. 158 o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions: 159 L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId. 160 L2L3VpnMcastProviderTunnelType provides an enumeration of the 161 P-tunnel types. L2L3VpnMcastProviderTunnelId represents an 162 identifier of a P-tunnel. 164 o L2L3-VPN-MCAST-MIB defines a table 165 l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table 166 corresponds to the attribute information of a specific P-tunnel on 167 a PE router. Entries in this table will be used by other MIB 168 modules for monitoring and/or configuring L2L3VpnMCast network. 169 The table index uniquely identifies a P-tunnel. It is composed of 170 a type and indentifier of a P-tunnel. The table may also be used 171 in conjunction with other MIBs, such as MPLS Traffic Engineering 172 MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information 173 about a P-tunnel. It may also be used in conjunction with the 174 Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further 175 information about the interface corresponding to a P-tunnel. 177 4. Definitions 179 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 181 L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN 183 IMPORTS 184 MODULE-IDENTITY, mib-2 185 FROM SNMPv2-SMI -- [RFC2578] 187 TEXTUAL-CONVENTION 188 FROM SNMPv2-TC; -- [RFC2579] 190 l2L3VpnMcastTCMIB MODULE-IDENTITY 191 LAST-UPDATED "201802281200Z" -- 28th February, 2018 192 ORGANIZATION "IETF BESS Working Group." 193 CONTACT-INFO 194 " Zhaohui Zhang 195 Juniper Networks, Inc. 196 10 Technology Park Drive 197 Westford, MA 01886 198 USA 199 Email: zzhang@juniper.net 201 Hiroshi Tsunoda 202 Tohoku Institute of Technology 203 35-1, Yagiyama Kasumi-cho 204 Taihaku-ku, Sendai, 982-8577 205 Japan 206 Email: tsuno@m.ieice.org 208 Comments and discussion to bess@ietf.org 209 " 210 DESCRIPTION 211 "This MIB module specifies textual conventions for 212 Border Gateway Protocol/MultiProtocol Label 213 Switching Layer 2 and Layer 3 Virtual Private Networks 214 that support multicast (L2L3VpnMCast networks). 216 Copyright (C) The Internet Society (2017). 217 " 219 -- Revision history. 221 REVISION "201802281200Z" -- 28th February, 2018 222 DESCRIPTION 223 "Initial version, published as RFC XXXX." 225 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 227 ::= { mib-2 AAAA } 229 -- IANA Reg.: Please assign a value for "AAAA" under the 230 -- 'mib-2' subtree and record the assignment in the SMI 231 -- Numbers registry. 233 -- RFC Ed.: When the above assignment has been made, please 234 -- remove the above note 235 -- replace "AAAA" here with the assigned value and 236 -- remove this note. 238 -- Textual convention 240 L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION 241 STATUS current 242 DESCRIPTION 243 "This textual convention enumerates values 244 representing the type of a provider tunnel (P-tunnel) 245 used for L2L3VpnMCast networks. 246 These labeled numbers are aligned with the definition 247 of Tunnel types in Section 5 of [RFC6514] and 248 Section 14.1 of [RFC7524]. 250 The enumerated values and the corresponding P-tunnel types 251 are as follows: 253 noTunnelInfo (0) : no tunnel information present 254 [RFC6514] 255 rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875] 256 ldpP2mp (2) : mLDP P2MP LSP [RFC6388] 257 pimSsm (3) : PIM-SSM Tree [RFC7761] 258 pimAsm (4) : PIM-SM Tree [RFC7761] 259 pimBidir (5) : BIDIR-PIM Tree [RFC5015] 260 ingressReplication (6) : Ingress Replication [RFC6513] 261 ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388] 262 transportTunnel (8) : Transport Tunnel [RFC7524] 264 These numbers are registered at IANA. 265 A current list of assignments can be found at 266 . 268 " 269 REFERENCE 270 "RFC4875 271 RFC5015 272 RFC6388 273 RFC6513 274 RFC6514, Section 5 275 RFC7524, Section 14.1 276 RFC7761 277 " 279 SYNTAX INTEGER 280 { 281 noTunnelInfo (0), 282 rsvpP2mp (1), 283 ldpP2mp (2), 284 pimSsm (3), 285 pimAsm (4), 286 pimBidir (5), 287 ingressReplication (6), 288 ldpMp2mp (7), 289 transportTunnel (8) 290 } 292 L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION 293 STATUS current 294 DESCRIPTION 295 "This textual convention represents the tunnel identifier 296 of a P-tunnel. 298 The size of the identifier depends on the address family 299 (IPv4 or IPv6) and the value of the corresponding 300 L2L3VpnMcastProviderTunnelType object. 302 The corresponding L2L3VpnMcastProviderTunnelType object 303 represents the type of the tunneling technology used 304 to establish the P-tunnel. 306 The size of the identifier for each tunneling technology 307 is summarized below. 309 L2L3VpnMcastProviderTunnelType Size (in octets) 310 (tunneling technology) IPv4 IPv6 311 ----------------------------------------------------------- 312 noTunnelInfo (No tunnel information) 0 0 313 rsvpP2mp (RSVP-TE P2MP LSP) 12 24 314 ldpP2mp (mLDP P2MP LSP) 17 29 315 pimSsm (PIM-SSM Tree) 8 32 316 pimAsm (PIM-SM Tree) 8 32 317 pimBidir (BIDIR-PIM Tree) 8 32 318 ingressReplication (Ingress Replication) 4 16 319 ldpMp2mp (mLDP MP2MP LSP) 17 29 320 transportTunnel (Transport Tunnel) 8 32 322 Tunnel type is set to 'No tunnel information present' 323 when the PMSI Tunnel attribute carries no tunnel 324 information (there is no Tunnel Identifier). 325 The value of the corresponding L2L3VpnMcastProviderTunnelId 326 object will be a string of length zero. 328 For tunnel type rsvpP2mp(1), the corresponding Tunnel 329 Identifier is composed of Extended Tunnel ID (4 octets in IPv4, 330 16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets), 331 and P2MP ID (4 octets). 332 The size of the corresponding L2L3VpnMcastProviderTunnelId 333 object will be 12 octets in IPv4 and 24 octets in IPv6. 335 For tunnel type ldpP2mp(2), the corresponding Tunnel Identifier 336 is the P2MP Forwarding Equivalence Class (FEC) Element 337 [RFC6388]. The size of the corresponding 338 L2L3VpnMcastProviderTunnelId object will be 17 octets 339 in IPv4 and 29 octets in IPv6. 341 For tunnel type pimSsm(3), PimAsm(4), and PimBidir(5), the 342 corresponding Tunnel Identifier is composed of the source IP 343 address and the group IP address. 344 The size of the corresponding L2L3VpnMcastProviderTunnelId 345 object will be 8 octets in IPv4 and 32 octets in IPv6. 347 For tunnel type ingressReplication(6), the Tunnel Identifier is 348 the unicast tunnel endpoint IP address of the local PE. 349 The size of the corresponding L2L3VpnMcastProviderTunnelId 350 object will be 4 octets in IPv4 and 16 octets in IPv6. 352 For tunnel type ldpMp2mp(7), the Tunnel Identifier is 353 MP2MP FEC Element [RFC6388]. 354 The size of the corresponding L2L3VpnMcastProviderTunnelId 355 object will be 17 octets in IPv4 and 29 octets in IPv6. 357 For tunnel type transportTunnel(8), the Tunnel Identifier 358 is a tuple of Source PE Address and Local Number, 359 which is a number that is unique to the Source PE [RFC7524]. 360 Both Source PE Address and Local Number are 4 octets in IPv4 361 and 16 octets in IPv6. 362 The size of the corresponding L2L3VpnMcastProviderTunnelId 363 object will be 8 octets in IPv4 and 32 octets in IPv6. 364 " 365 REFERENCE 366 "RFC6514, Section 5 367 RFC4875, Section 19.1 368 RFC6388, Section 2.2 and 3.2 369 RFC7524, Section 14.1 370 " 371 SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) 373 END 375 4.2. L2L3-VPN-MCAST-MIB Object Definitions 377 L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN 379 IMPORTS 380 MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero 381 FROM SNMPv2-SMI -- [RFC2578] 383 MODULE-COMPLIANCE, OBJECT-GROUP 384 FROM SNMPv2-CONF -- [RFC2580] 386 RowPointer 387 FROM SNMPv2-TC -- [RFC2579] 389 MplsLabel 390 FROM MPLS-TC-STD-MIB -- [RFC3811] 392 L2L3VpnMcastProviderTunnelType, 393 L2L3VpnMcastProviderTunnelId 394 FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX] 396 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 398 l2L3VpnMcastMIB MODULE-IDENTITY 399 LAST-UPDATED "201712121200Z" -- 12th December, 2017 400 ORGANIZATION "IETF BESS Working Group." 401 CONTACT-INFO 402 " Zhaohui Zhang 403 Juniper Networks, Inc. 404 10 Technology Park Drive 405 Westford, MA 01886 406 USA 407 Email: zzhang@juniper.net 409 Hiroshi Tsunoda 410 Tohoku Institute of Technology 411 35-1, Yagiyama Kasumi-cho 412 Taihaku-ku, Sendai, 982-8577 413 Japan 414 Email: tsuno@m.ieice.org 416 Comments and discussion to bess@ietf.org 417 " 419 DESCRIPTION 420 "This MIB module defines a table representing the attribute 421 information of the provider tunnels (P-tunnels) on a PE router. 422 This MIB module will be used by other MIB modules designed for 423 monitoring and/or configuring Border Gateway 424 Protocol/MultiProtocol Label Switching 425 Layer 2 and Layer 3 Virtual Private 426 Network that support multicast (L2L3VpnMCast network). 427 Copyright (C) The Internet Society (2017). 428 " 429 -- Revision history. 431 REVISION "201712121200Z" -- 12th December, 2017 432 DESCRIPTION 433 "Initial version, published as RFC XXXX." 435 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 437 ::= { mib-2 BBBB } 439 -- IANA Reg.: Please assign a value for "BBBB" under the 440 -- 'mib-2' subtree and record the assignment in the SMI 441 -- Numbers registry. 443 -- RFC Ed.: When the above assignment has been made, please 444 -- remove the above note 445 -- replace "BBBB" here with the assigned value and 446 -- remove this note. 448 -- Top level components of this MIB. 449 l2L3VpnMcastStates OBJECT IDENTIFIER 450 ::= { l2L3VpnMcastMIB 1 } 452 l2L3VpnMcastConformance OBJECT IDENTIFIER 453 ::= { l2L3VpnMcastMIB 2 } 455 -- tables, scalars, conformance information 456 -- Table of PMSI Tunnel Attributes 458 l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE 459 SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry 460 MAX-ACCESS not-accessible 461 STATUS current 462 DESCRIPTION 463 "An entry in this table corresponds to 464 the attribute information of a specific 465 P-tunnel on a PE router. 466 A part of attributes correspond to fields in 467 a Provider Multicast Service Interface (PMSI) Tunnel 468 attribute advertised and received by a PE router. 469 The entries will be referred to by other MIB modules 470 for monitoring and/or configuring L2L3VpnMCast networks. 471 " 472 REFERENCE 473 "RFC6514, Section 5" 474 ::= { l2L3VpnMcastStates 1 } 476 l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE 477 SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "A conceptual row corresponding to a specific 482 P-tunnel on this router. 483 " 484 REFERENCE 485 "RFC6514, Section 5" 486 INDEX { 487 l2L3VpnMcastPmsiTunnelAttributeType, 488 l2L3VpnMcastPmsiTunnelAttributeId 489 } 490 ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } 492 L2L3VpnMcastPmsiTunnelAttributeEntry ::= 493 SEQUENCE { 494 l2L3VpnMcastPmsiTunnelAttributeType 495 L2L3VpnMcastProviderTunnelType, 496 l2L3VpnMcastPmsiTunnelAttributeId 497 L2L3VpnMcastProviderTunnelId, 498 l2L3VpnMCastPmsiTunnelLeafInfoRequired 499 INTEGER, 500 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 501 MplsLabel, 502 l2L3VpnMcastPmsiTunnelPointer 503 RowPointer, 504 l2L3VpnMcastPmsiTunnelIf 505 RowPointer 506 } 508 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE 509 SYNTAX L2L3VpnMcastProviderTunnelType 510 MAX-ACCESS not-accessible 511 STATUS current 512 DESCRIPTION 513 "This object indicates the type of the tunneling technology 514 used to establish the P-tunnel corresponding to this entry. 516 When BGP-based PMSI signaling is used, the value of 517 this object corresponds to the Tunnel Type field 518 in the PMSI Tunnel attribute advertised/received 519 in a PMSI auto-discovery (A-D) route. 520 " 521 REFERENCE 522 "RFC6514, Section 5" 523 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 525 l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 526 SYNTAX L2L3VpnMcastProviderTunnelId 527 MAX-ACCESS not-accessible 528 STATUS current 529 DESCRIPTION 530 "This object represents the Tunnel Identifier field, which 531 uniquely identifies a P-tunnel, in the PMSI Tunnel attribute 532 of the P-tunnel corresponding to this entry. 534 The size of the identifier depends on the address family 535 (IPv4 or IPv6) and the value of the corresponding 536 l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of 537 the tunneling technology used to establish the P-tunnel. 538 " 539 REFERENCE 540 "RFC6514, Section 5" 541 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } 543 l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE 544 SYNTAX INTEGER { 545 false (0), 546 true (1), 547 notAvailable (2) 548 } 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "When the value of this object is set to 1 (true), 553 it indicates that the PE which originated the 554 PMSI Tunnel attribute of the P-tunnel corresponding 555 to this entry requests receivers to originate 556 a new Leaf A-D (Auto-Discovery) route. 558 A value of 0 (false) indicates that there is no such 559 request. 561 When the P-tunnel does not have a corresponding PMSI 562 tunnel attribute, the value of this object will be 563 2 (notAvailable). 565 In the case of Multicast in MPLS/BGP IP VPNs, 566 this object represents the 'Leaf Information Required flag' 567 [RFC6514] in the Flags field in the PMSI Tunnel attribute 568 of the P-tunnel corresponding to this entry. 569 " 570 REFERENCE 571 "RFC6514, Section 5 572 " 573 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } 575 l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE 576 SYNTAX MplsLabel 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "This object represents the MPLS Label in the PMSI Tunnel 581 attribute of the P-tunnel corresponding to this entry. 583 When BGP-based PMSI signaling is used, the PMSI Tunnel 584 attribute of the P-tunnel will be advertised/received 585 in a PMSI auto-discovery (A-D) route. The value of 586 this object corresponds to the MPLS Label in the attribute. 588 When the P-tunnel does not have a PMSI tunnel 589 attribute, the value of this object will be 0. 590 " 591 REFERENCE 592 "RFC6514, Section 5" 593 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 595 l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE 596 SYNTAX RowPointer 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "Details of a P-tunnel identified by 601 l2L3VpnMcastPmsiTunnelAttributeId may be present 602 in some other table, e.g., 603 mplsTunnelTable [RFC3812]. This object specifies 604 the pointer to the row that pertains to the entry 605 in the table. 607 If no such entry exists, the value of this object 608 will be zeroDotZero. 609 " 610 REFERENCE 611 "RFC3812, Section 6.1 and Section 11" 612 DEFVAL { zeroDotZero } 614 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 616 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE 617 SYNTAX RowPointer 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "If the P-tunnel identified by 622 l2L3VpnMcastPmsiTunnelAttributeId has a corresponding 623 entry in ifXTable [RFC2863], this object will 624 point to the row in ifXTable that pertains to the entry. 625 Otherwise, the value of this object will be zeroDotZero. 626 " 627 REFERENCE 628 "RFC2863, Section 6" 629 DEFVAL { zeroDotZero } 630 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } 632 -- Conformance Information 634 l2L3VpnMcastCompliances OBJECT IDENTIFIER 635 ::= { l2L3VpnMcastConformance 1 } 636 l2L3VpnMcastGroups OBJECT IDENTIFIER 637 ::= { l2L3VpnMcastConformance 2 } 639 -- Compliance Statements 641 l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE 642 STATUS current 643 DESCRIPTION 644 "The core compliance statement for SNMP entities 645 which implement the L2L3-VPN-MCAST-MIB Module." 646 MODULE -- this module 648 MANDATORY-GROUPS { 649 l2L3VpnMcastCoreGroup 650 } 651 ::= { l2L3VpnMcastCompliances 1 } 653 l2L3VpnMcastFullCompliance MODULE-COMPLIANCE 654 STATUS current 655 DESCRIPTION 656 "The full compliance statement for SNMP entities 657 which implement the L2L3-VPN-MCAST-MIB Module." 658 MODULE -- this module 660 MANDATORY-GROUPS { 661 l2L3VpnMcastCoreGroup, 662 l2L3VpnMcastOptionalGroup 663 } 664 ::= { l2L3VpnMcastCompliances 2 } 666 -- units of conformance 668 l2L3VpnMcastCoreGroup OBJECT-GROUP 669 OBJECTS { 670 l2L3VpnMCastPmsiTunnelLeafInfoRequired, 671 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 672 } 673 STATUS current 674 DESCRIPTION 675 "Support of these objects is required." 676 ::= { l2L3VpnMcastGroups 1 } 678 l2L3VpnMcastOptionalGroup OBJECT-GROUP 679 OBJECTS { 680 l2L3VpnMcastPmsiTunnelPointer, 681 l2L3VpnMcastPmsiTunnelIf 682 } 683 STATUS current 684 DESCRIPTION 685 "Support of these objects is optional." 686 ::= { l2L3VpnMcastGroups 2 } 688 END 690 5. Security Considerations 692 There are no management objects defined in these MIB modules that 693 have a MAX-ACCESS clause of read-write and/or read-create. So, if 694 this MIB module is implemented correctly, then there is no risk that 695 an intruder can alter or create any management objects of this MIB 696 module via direct SNMP SET operations. 698 Some of the readable objects in these MIB modules (i.e., objects with 699 a MAX-ACCESS other than not-accessible) may be considered sensitive 700 or vulnerable in some network environments. It is thus important to 701 control even GET and/or NOTIFY access to these objects and possibly 702 to even encrypt the values of these objects when sending them over 703 the network via SNMP. These are the tables and objects and their 704 sensitivity/vulnerability: 706 o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the 707 P-tunnel network topology and its performance characteristics. 708 For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will 709 contain the identifier that uniquely identifies a P-tunnel. This 710 identifier may be composed of source and multicast group IP 711 addresses. l2L3VpnMcastPmsiTunnelPointer and 712 l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries 713 in other tables containing configuration and/or performance 714 information of a P-tunnel and its interface. If an Administrator 715 does not want to reveal this information, then these objects 716 should be considered sensitive/vulnerable. 718 SNMP versions prior to SNMPv3 did not include adequate security. 719 Even if the network itself is secure (for example by using IPsec), 720 there is no control as to who on the secure network is allowed to 721 access and GET/SET (read/change/create/delete) the objects in this 722 MIB module. 724 Implementations SHOULD provide the security features described by the 725 SNMPv3 framework (see [RFC3410]), and implementations claiming 726 compliance to the SNMPv3 standard MUST include full support for 727 authentication and privacy via the User-based Security Model (USM) 728 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 729 MAY also provide support for the Transport Security Model (TSM) 730 [RFC5591] in combination with a secure transport such as SSH 731 [RFC5592] or TLS/DTLS [RFC6353]. 733 Further, deployment of SNMP versions prior to SNMPv3 is NOT 734 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 735 enable cryptographic security. It is then a customer/operator 736 responsibility to ensure that the SNMP entity giving access to an 737 instance of this MIB module is properly configured to give access to 738 the objects only to those principals (users) that have legitimate 739 rights to indeed GET or SET (change/create/delete) them. 741 6. IANA Considerations 743 The MIB module in this document uses the following IANA-assigned 744 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 746 Descriptor OBJECT IDENTIFIER value 747 ---------- ----------------------- 748 l2L3VpnMcastTCMIB { mib-2 AAA } 749 l2L3VpnMcastMIB { mib-2 BBB } 751 Editor's Note (to be removed prior to publication): the IANA is 752 requested to assign a value for "AAA" and "BBB" under the 'mib-2' 753 subtree and to record the assignment in the SMI Numbers registry. 754 When the assignment has been made, the RFC Editor is asked to replace 755 "AAA" and "BBB" (here and in the MIB module) with the assigned value 756 and to remove this note. 758 7. References 760 7.1. Normative References 762 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 763 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 764 RFC2119, March 1997, . 767 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 768 Schoenwaelder, Ed., "Structure of Management Information 769 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 770 RFC2578, April 1999, . 773 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 774 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 775 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 776 . 778 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 779 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 780 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 781 . 783 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 784 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 785 . 787 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 788 (USM) for version 3 of the Simple Network Management 789 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 790 RFC3414, December 2002, . 793 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 794 Textual Conventions (TCs) for Multiprotocol Label 795 Switching (MPLS) Management", RFC 3811, DOI 10.17487/ 796 RFC3811, June 2004, . 799 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 800 "Multiprotocol Label Switching (MPLS) Traffic Engineering 801 (TE) Management Information Base (MIB)", RFC 3812, DOI 802 10.17487/RFC3812, June 2004, . 805 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 806 Advanced Encryption Standard (AES) Cipher Algorithm in the 807 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 808 RFC3826, June 2004, . 811 [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. 812 Yasukawa, Ed., "Extensions to Resource Reservation 813 Protocol - Traffic Engineering (RSVP-TE) for Point-to- 814 Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI 815 10.17487/RFC4875, May 2007, . 818 [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 819 "Bidirectional Protocol Independent Multicast (BIDIR- 820 PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, 821 . 823 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 824 for the Simple Network Management Protocol (SNMP)", STD 825 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 826 . 828 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 829 Shell Transport Model for the Simple Network Management 830 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 831 2009, . 833 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 834 Model for the Simple Network Management Protocol (SNMP)", 835 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 836 . 838 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 839 Thomas, "Label Distribution Protocol Extensions for Point- 840 to-Multipoint and Multipoint-to-Multipoint Label Switched 841 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 842 . 844 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 845 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 846 2012, . 848 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 849 Encodings and Procedures for Multicast in MPLS/BGP IP 850 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 851 . 853 [RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and 854 C. Kodeboniya, "Multicast in Virtual Private LAN Service 855 (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014, 856 . 858 [RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T., 859 Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area 860 Point-to-Multipoint (P2MP) Segmented Label Switched Paths 861 (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, 862 . 864 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 865 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 866 Multicast - Sparse Mode (PIM-SM): Protocol Specification 867 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 868 2016, . 870 7.2. Informative References 872 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 873 "Introduction and Applicability Statements for Internet- 874 Standard Management Framework", RFC 3410, DOI 10.17487/ 875 RFC3410, December 2002, . 878 Authors' Addresses 879 Zhaohui (Jeffrey) Zhang 880 Juniper Networks, Inc. 881 10 Technology Park Drive 882 Westford, MA 01886 883 USA 885 Email: zzhang@juniper.net 887 Hiroshi Tsunoda 888 Tohoku Institute of Technology 889 35-1, Yagiyama Kasumi-cho 890 Taihaku-ku, Sendai 982-8577 891 Japan 893 Phone: +81-22-305-3411 894 Email: tsuno@m.ieice.org