idnits 2.17.1 draft-ietf-bess-l2l3-vpn-mcast-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (February 21, 2017) is 2621 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: 'RFC3811' is mentioned on line 292, but not defined -- Obsolete informational reference (is this intentional?): RFC 4601 (Obsoleted by RFC 7761) Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). 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: August 25, 2017 Tohoku Institute of Technology 6 February 21, 2017 8 L2L3 VPN Multicast MIB 9 draft-ietf-bess-l2l3-vpn-mcast-mib-06 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 common managed objects used by other MIB 16 modules which are designed for monitoring and/or configuring both 17 Layer 2 and Layer 3 Virtual Private Networks (VPN) that support 18 multicast. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on August 25, 2017. 37 Copyright Notice 39 Copyright (c) 2017 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. The Internet-Standard Management Framework . . . . . . . . . 4 57 3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 4 58 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 5 60 4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 6 61 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 62 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 63 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 64 7.1. Normative References . . . . . . . . . . . . . . . . . . 14 65 7.2. Informative References . . . . . . . . . . . . . . . . . 16 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 68 1. Introduction 70 [RFC7117] and [RFC6513] specify procedures for supporting multicast 71 in Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) 72 Layer 2 (L2) and Layer 3 (L3) VPN (Virtual Private Network), 73 respectively. 75 Multicast service in BGP/MPLS L2 and L3 VPN can be achieved by using 76 various kinds of transport mechanism for forwarding a packet to all 77 or a subset of Provider Edge routers (PEs) across service provider 78 networks. Such transport mechanisms are referred to as provider 79 tunnels (P-tunnels). 81 The signaling of P-tunnel choice is very similar for multicast in 82 both L2 and L3 VPNs. [RFC7117] and [RFC6513] describe BGP-based 83 mechanisms for Virtual Private LAN Service (VPLS) and Multicast VPN 84 (MVPN), respectively. [RFC6514] defines the Provider Multicast 85 Service Interface (PMSI) tunnel attribute, a BGP attribute that 86 specifies information of a P-tunnel. The PMSI tunnel attribute is 87 advertised/received by PEs in BPG auto-discovery (A-D) routes. 88 [RFC6513] also proposes a UDP-based signaling mechanism. 90 This document defines a textual conventions (TC) that can be used to 91 represent types of P-tunnels used for multicast in BGP/MPLS L2 or L3 92 VPN within MIB module specifications. 94 This document also describes common managed objects used by other MIB 95 modules which are designed for monitoring and/or configuring both L2 96 and L3 VPN that support multicast. 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 1.1. Terminology 104 This document adopts the definitions, acronyms and mechanisms 105 described in [RFC6513] [RFC6514] [RFC7117] and other documents that 106 they refer to. Familiarity with Multicast, MPLS, L3 VPN, MVPN 107 (Multicast VPN) concepts and/or mechanisms is assumed. Some terms 108 specifically related to this document are explained below. 110 The term "Multicast VPN (MVPN)" [RFC6513] refers to a BGP/MPLS L3 111 (IP) VPN service that supports multicast. 113 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 114 conceptual interface instantiated by a P-tunnel, a transport 115 mechanism used to deliver multicast traffic. A PE uses to send 116 customer multicast traffic to all or some PEs in the same VPN. 118 There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective 119 PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE 120 attached to a particular MVPN to transmit a message to all PEs in the 121 same VPN. An S-PMSI is a PMSI that enables a PE attached to a 122 particular MVPN to transmit a message to some of the PEs in the same 123 VPN. 125 Throughout this document, we will use the term "I/S-PMSI" to refer 126 both "I-PMSI" and "S-PMSI". 128 [RFC6513] describes following tunnel setup techniques that can be 129 used to create the P-tunnels that instantiate the PMSIs. 131 o Protocol Independent Multicast tree 133 * Sparse Mode (PIM-SM) tree [RFC4601] 135 * Source Specific Multicast (PIM-SSM) tree [RFC4601] 137 * Bidirectional Protocol Independent Multicast (BIDIR-PIM) tree 138 [RFC5015] 140 o Label Distribution Protocol Extension for Multipoint Label 141 Switched Paths (mLDP) [RFC6388] 143 * Point-to-MultiPoint (mLDP P2MP) 145 * Point-to-MultiPoint (mLDP MP2MP) 147 o Resource Reservation Protocol - Traffic Engineering Point-to- 148 Multipoint (RSVP-TE P2MP) Label Switched Path [RFC4875] 150 o Ingress Replication through Unicast Tunnels [RFC6513] 152 A created tunnel will be identified by Tunnel Identifier. The length 153 of the identifier differs depending on the setup technique that is 154 used to create the tunnel. 156 2. The Internet-Standard Management Framework 158 For a detailed overview of the documents that describe the current 159 Internet-Standard Management Framework, please refer to section 7 of 160 RFC 3410 [RFC3410]. 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. MIB objects are generally 164 accessed through the Simple Network Management Protocol (SNMP). 165 Objects in the MIB are defined using the mechanisms defined in the 166 Structure of Management Information (SMI). This memo specifies a MIB 167 module that is compliant to the SMIv2, which is described in STD 58, 168 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 169 [RFC2580]. 171 3. Summary of MIB Module 173 This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and 174 L2L3-VPN-MCAST-MIB. 176 o L2L3-VPN-MCAST-TC-MIB contains a Textual Convention 177 L2L3VpnMcastProviderTunnelType that provides an enumeration of the 178 provider tunnel types. 180 o L2L3-VPN-MCAST-MIB defines a table 181 l2L3VpnMcastPmsiTunnelAttributeTable. An entry of this table 182 corresponds with a PMSI Tunnel Attribute (PTA) advertised/received 183 by PE routers. The entry of the table will be used by other MIB 184 modules which are designed for monitoring and/or configuring both 185 L2 and L3 VPN that support multicast. 186 The table index is composed of multiple attributes that depend on 187 the tunnel type and uniquely identify a tunnel. 188 The table may also be used in conjunction with other MIBs, such as 189 MPLS Traffic Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to 190 obtain the other details of a tunnel by following the row pointer 191 of the corresponding tunnel's row in this table. It may also be 192 used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863] 193 to obtain the other details of a corresponding interface that 194 tunnel uses by following the row pointer of the corresponding 195 tunnel's row in this table. 197 4. Definitions 199 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 201 L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN 203 IMPORTS 204 MODULE-IDENTITY, mib-2 205 FROM SNMPv2-SMI -- [RFC2578] 207 TEXTUAL-CONVENTION 208 FROM SNMPv2-TC; -- [RFC2579] 210 l2L3VpnMcastTCMIB MODULE-IDENTITY 211 LAST-UPDATED "201702211200Z" -- 21th February, 2017 212 ORGANIZATION "IETF BESS Working Group." 213 CONTACT-INFO 214 " Zhaohui Zhang 215 Juniper Networks, Inc. 216 10 Technology Park Drive 217 Westford, MA 01886 218 USA 219 Email: zzhang@juniper.net 221 Hiroshi Tsunoda 222 Tohoku Institute of Technology 223 35-1, Yagiyama Kasumi-cho 224 Taihaku-ku, Sendai, 982-8577 225 Japan 226 Email: tsuno@m.ieice.org 228 Comments and discussion to bess@ietf.org" 229 DESCRIPTION 230 "This MIB module contains textual conventions for 231 Border Gateway Protocol/MultiProtocol Label 232 Switching (BGP/MPLS) Layer 2 (L2) and Layer 3 233 (L3) VPN (Virtual Private Network). 234 Copyright (C) The Internet Society (2017)." 236 -- Revision history. 238 REVISION "201702211200Z" -- 21th February, 2017 239 DESCRIPTION 240 "Initial version, published as RFC XXXX." 242 -- RFC Ed. replace XXXX with actual RFC number and remove this note 244 ::= { mib-2 AAAA } 246 -- IANA Reg.: Please assign a value for "AAAA" under the 247 -- 'mib-2' subtree and record the assignment in the SMI 248 -- Numbers registry. 250 -- RFC Ed.: When the above assignment has been made, please 251 -- remove the above note 252 -- replace "AAAA" here with the assigned value and 253 -- remove this note. 255 -- Textual convention 257 L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION 258 STATUS current 259 DESCRIPTION 260 "Types of provider tunnels used for multicast in 261 BGP/MPLS L2 or L3 VPN." 262 REFERENCE 263 "RFC6514, Section 5" 264 SYNTAX INTEGER 265 { noTunnelId (0), -- No tunnel information present 266 rsvpP2mp (1), -- RSVP-TE P2MP LSP 267 ldpP2mp (2), -- mLDP P2MP LSP 268 pimSsm (3), -- PIM-SSM Tree 269 pimAsm (4), -- PIM-SM Tree 270 pimBidir (5), -- BIDIR-PIM Tree 271 ingressReplication (6), -- Ingress Replication 272 ldpMp2mp (7) -- mLDP MP2MP LSP 273 } 275 END 277 4.2. L2L3-VPN-MCAST-MIB Object Definitions 279 L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN 281 IMPORTS 282 MODULE-IDENTITY, OBJECT-TYPE, mib-2 283 FROM SNMPv2-SMI -- [RFC2578] 285 MODULE-COMPLIANCE, OBJECT-GROUP 286 FROM SNMPv2-CONF -- [RFC2580] 288 RowPointer 289 FROM SNMPv2-TC -- [RFC2579] 291 MplsLabel 292 FROM MPLS-TC-STD-MIB -- [RFC3811] 294 L2L3VpnMcastProviderTunnelType 295 FROM L2L3-VPN-MCAST-TC-MIB; 297 l2L3VpnMcastMIB MODULE-IDENTITY 298 LAST-UPDATED "201702211200Z" -- 21th February, 2017 299 ORGANIZATION "IETF BESS Working Group." 300 CONTACT-INFO 301 " Zhaohui Zhang 302 Juniper Networks, Inc. 303 10 Technology Park Drive 304 Westford, MA 01886 305 USA 306 Email: zzhang@juniper.net 308 Hiroshi Tsunoda 309 Tohoku Institute of Technology 310 35-1, Yagiyama Kasumi-cho 311 Taihaku-ku, Sendai, 982-8577 312 Japan 313 Email: tsuno@m.ieice.org 315 Comments and discussion to bess@ietf.org" 316 DESCRIPTION 317 "This MIB module will be used by other MIB modules designed for 318 managing multicast in Layer 2 (L2) VPNs [RFC7117] and 319 Layer 3 (L3) VPNs [RFC6513], [RFC6514]. 320 Copyright (C) The Internet Society (2017)." 322 -- Revision history. 324 REVISION "201702211200Z" -- 21th February, 2017 325 DESCRIPTION 326 "Initial version, published as RFC XXXX." 328 -- RFC Ed. replace XXXX with actual RFC number and remove this note 330 ::= { mib-2 BBBB } 332 -- IANA Reg.: Please assign a value for "BBBB" under the 333 -- 'mib-2' subtree and record the assignment in the SMI 334 -- Numbers registry. 336 -- RFC Ed.: When the above assignment has been made, please 337 -- remove the above note 338 -- replace "BBBB" here with the assigned value and 339 -- remove this note. 341 -- Top level components of this MIB. 342 l2L3VpnMcastObjects OBJECT IDENTIFIER 343 ::= { l2L3VpnMcastMIB 1 } 344 l2L3VpnMcastStates OBJECT IDENTIFIER 345 ::= { l2L3VpnMcastObjects 1 } 346 l2L3VpnMcastConformance OBJECT IDENTIFIER 347 ::= { l2L3VpnMcastMIB 2 } 349 -- tables, scalars, conformance information 350 -- Table of PMSI Tunnel Attributes 352 l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE 353 SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry 354 MAX-ACCESS not-accessible 355 STATUS current 356 DESCRIPTION 357 "An entry of this table corresponds with a 358 PMSI Tunnel attribute and is created by a PE router 359 that advertises and receives the attribute. 360 The entry in the table will be referred by other MIB modules 361 which are designed for monitoring and/or configuring 362 both L2 and L3 VPN that support multicast." 363 REFERENCE 364 "RFC6514, Section 5" 365 ::= { l2L3VpnMcastStates 1 } 367 l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE 368 SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry 369 MAX-ACCESS not-accessible 370 STATUS current 371 DESCRIPTION 372 "A conceptual row corresponding to a PTA 373 that is advertised/received on this router." 374 REFERENCE 375 "RFC6514, Section 5" 376 INDEX { 377 l2L3VpnMcastPmsiTunnelAttributeFlags, 378 l2L3VpnMcastPmsiTunnelAttributeType, 379 l2L3VpnMcastPmsiTunnelAttributeLabel, 380 l2L3VpnMcastPmsiTunnelAttributeId 381 } 382 ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } 384 L2L3VpnMcastPmsiTunnelAttributeEntry ::= 385 SEQUENCE { 386 l2L3VpnMcastPmsiTunnelAttributeFlags 387 OCTET STRING, 388 l2L3VpnMcastPmsiTunnelAttributeType 389 L2L3VpnMcastProviderTunnelType, 390 l2L3VpnMcastPmsiTunnelAttributeLabel 391 MplsLabel, 392 l2L3VpnMcastPmsiTunnelAttributeId 393 OCTET STRING, 394 l2L3VpnMcastPmsiTunnelPointer 395 RowPointer, 396 l2L3VpnMcastPmsiTunnelIf 397 RowPointer 398 } 400 l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE 401 SYNTAX OCTET STRING (SIZE (1)) 402 MAX-ACCESS not-accessible 403 STATUS current 404 DESCRIPTION 405 "Denotes the Flags field in a PMSI Tunnel attribute 406 with the following format. 408 0 1 2 3 4 5 6 7 409 +-+-+-+-+-+-+-+-+ 410 | reserved |L| 411 +-+-+-+-+-+-+-+-+ 413 L: Leaf Information Required 415 When BGP-based I/S-PMSI signaling is used, the value of 416 this object corresponds with the Flags field in 417 an advertised/received I/S-PMSI auto-discovery (A-D) route. 419 When UDP-based S-PMSI signaling is used, the value of 420 this object is zero." 421 REFERENCE 422 "RFC6514, Section 5" 423 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 425 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE 426 SYNTAX L2L3VpnMcastProviderTunnelType 427 MAX-ACCESS not-accessible 428 STATUS current 429 DESCRIPTION 430 "Denotes the Tunnel Type field that identifies 431 the type of the tunneling technology used to 432 establish the provider tunnel, in a PMSI Tunnel 433 attribute. 435 When BGP-based I/S-PMSI signaling is used, the value of 436 this object corresponds with the Tunnel Type field in 437 an advertised/received I/S-PMSI A-D route. 439 When UDP-based S-PMSI signaling is used, the value of 440 this object will be one of pimAsm (3), pimSsm (4), or 441 pimBidir (5)." 442 REFERENCE 443 "RFC6514, Section 5" 444 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } 446 l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE 447 SYNTAX MplsLabel 448 MAX-ACCESS not-accessible 449 STATUS current 450 DESCRIPTION 451 "Denotes the MPLS Label field that contains 452 an MPLS label, in a PMSI Tunnel attribute. 454 When BGP-based I/S-PMSI signaling is used, the value of 455 this object corresponds with the MPLS Label field in 456 an advertised/received I/S-PMSI A-D route. 458 When UDP-based S-PMSI signaling is used, the value of 459 this object is zero that indicates absence of MPLS 460 Label." 461 REFERENCE 462 "RFC6514, Section 5" 463 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } 465 l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 466 SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "Denotes the Tunnel Identifier field that uniquely 471 identifies a created tunnel, in a PMSI Tunnel 472 attribute. 473 The size of the identifier depends on address family 474 (IPv4 or IPv6) and the value of 475 l2L3VpnMcastPmsiTunnelAttributeType, i.e., the type of 476 the tunneling technology used to establish the provider 477 tunnel. 479 The size of the identifier for each tunneling technology 480 is summarized below. 482 Size (in octets) l2L3VpnMcastPmsiTunnelAttributeType 483 IPv4 IPv6 (tunneling technology) 484 -------------------------------------------------- 485 0 0 noTunnelId (No tunnel information present) 486 12 24 rsvpP2mp (RSVP-TE P2MP LSP) 487 17 29 ldpP2mp (mLDP P2MP LSP) 488 8 32 pimSsm (PIM-SSM Tree) 489 8 32 pimAsm (PIM-SM Tree) 490 8 32 pimBidir (BIDIR-PIM Tree) 491 4 16 ingressReplication 492 (Ingress Replication) 493 17 29 ldpMp2mp (mLDP MP2MP LSP) 495 When l2L3VpnMcastPmsiTunnelAttributeType is set to 496 noTunnelId, the PMSI Tunnel attribute does not have 497 tunnel information. Thus, the size of this object is zero. 499 When l2L3VpnMcastPmsiTunnelAttributeType is set to 500 rsvpP2mp, the Tunnel Identifier is composed of 501 Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6), 502 Reserved (2 octets), Tunnel ID (2 octets), and 503 P2MP ID (4 octets). Thus, the size of this object is 504 12 octets in IPv4 and 24 octets in IPv6. 506 When l2L3VpnMcastPmsiTunnelAttributeType is set to 507 ldpP2mp, the Tunnel Identifier is a 17 octets 508 (in IPv4) or 29 octets (in IPv6) P2MP Forwarding 509 Equivalence Class (FEC) Element. 511 When l2L3VpnMcastPmsiTunnelAttributeType is set to 512 pimSsm, PimAsm, or PimBidir, the Tunnel Identifier is 513 a pair of source and group IP addresses. 514 Thus, the size of this object is 16 octets in IPv4 515 and 32 octets in IPv6. 517 When l2L3VpnMcastPmsiTunnelAttributeType is set to 518 ingressReplication, the Tunnel Identifier is 519 the unicast tunnel endpoint IP address of the local 520 PE. Thus, the size of this object is 4 octets in IPv4 521 and 16 octets in IPv6. 523 When l2L3VpnMcastPmsiTunnelAttributeType is set to 524 ldpMp2mp, the Tunnel Identifier is a 17 octets 525 (in IPv4) or 29 octets (in IPv6) MP2MP FEC Element. 527 When BGP-based I/S-PMSI signaling is used, the value of 528 this object corresponds with the the Tunnel 529 Identifier field in an advertised/received I/S-PMSI 530 A-D route. Thus, the size of this object is determined 531 by the above table. 533 When UDP-based S-PMSI signaling is used, the value of 534 this object is a pair of source and group IP addresses. 535 Thus, the size of this object is 16 octets in IPv4 536 and 32 octets in IPv6." 537 REFERENCE 538 "RFC6514, Section 5 539 RFC4875, Section 19.1 540 RFC6388, Section 2.2 and 2.3" 541 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 543 l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE 544 SYNTAX RowPointer 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId 549 may be represented as an entry in other table, e.g, 550 mplsTunnelTable [RFC3812]. If there is such entry, 551 this object will point to the row pertaining to the entry. 552 Otherwise, the pointer is null." 553 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 555 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE 556 SYNTAX RowPointer 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "If the tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId 561 has a corresponding entry in the ifXTable [RFC2863], 562 this object will point to the row pertaining to the entry 563 in the ifXTable. Otherwise, the pointer is null." 564 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } 566 -- Conformance Information 568 l2L3VpnMcastGroups OBJECT IDENTIFIER 569 ::= { l2L3VpnMcastConformance 1 } 570 l2L3VpnMcastCompliances OBJECT IDENTIFIER 571 ::= { l2L3VpnMcastConformance 2 } 573 -- Compliance Statements 575 l2L3VpnMcastCompliance MODULE-COMPLIANCE 576 STATUS current 577 DESCRIPTION 578 "The compliance statement: no mandatory groups " 580 MODULE -- this module 582 GROUP l2L3VpnMcastOptionalGroup 583 DESCRIPTION 584 "This group is optional." 585 ::= { l2L3VpnMcastCompliances 1 } 587 -- units of conformance 589 l2L3VpnMcastOptionalGroup OBJECT-GROUP 590 OBJECTS { 591 l2L3VpnMcastPmsiTunnelPointer, 592 l2L3VpnMcastPmsiTunnelIf 593 } 594 STATUS current 595 DESCRIPTION 596 "Support of these objects is not required." 597 ::= { l2L3VpnMcastGroups 1 } 599 END 601 5. Security Considerations 603 There are no management objects defined in this MIB module that have 604 a MAX-ACCESS clause of read-write and/or read-create. So, if this 605 MIB module is implemented correctly, then there is no risk that an 606 intruder can alter or create any management objects of this MIB 607 module via direct SNMP SET operations. 609 Some of the readable objects in this MIB module (i.e., objects with a 610 MAX-ACCESS other than not-accessible) may be considered sensitive or 611 vulnerable in some network environments. It is thus important to 612 control even GET and/or NOTIFY access to these objects and possibly 613 to even encrypt the values of these objects when sending them over 614 the network via SNMP. These are the tables and objects and their 615 sensitivity/vulnerability: 617 o l2L3VpnMcastPmsiTunnelPointer and l2L3VpnMcastPmsiTunnelIf in 618 l2L3VpnMcastPmsiTunnelAttributeTable will point the corresponding 619 entry of in other table containing configuration and/or 620 performance information of a tunnel and an interface. If an 621 Administrator does not want to reveal this information, then these 622 objects should be considered sensitive/vulnerable. 624 SNMP versions prior to SNMPv3 did not include adequate security. 625 Even if the network itself is secure (for example by using IPsec), 626 there is no control as to who on the secure network is allowed to 627 access and GET/SET (read/change/create/delete) the objects in this 628 MIB module. 630 Implementations SHOULD provide the security features described by the 631 SNMPv3 framework (see [RFC3410]), and implementations claiming 632 compliance to the SNMPv3 standard MUST include full support for 633 authentication and privacy via the User-based Security Model (USM) 634 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 635 MAY also provide support for the Transport Security Model (TSM) 636 [RFC5591] in combination with a secure transport such as SSH 637 [RFC5592] or TLS/DTLS [RFC6353]. 639 Further, deployment of SNMP versions prior to SNMPv3 is NOT 640 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 641 enable cryptographic security. It is then a customer/operator 642 responsibility to ensure that the SNMP entity giving access to an 643 instance of this MIB module is properly configured to give access to 644 the objects only to those principals (users) that have legitimate 645 rights to indeed GET or SET (change/create/delete) them. 647 6. IANA Considerations 649 IANA is requested to root MIB objects in the MIB module contained in 650 this document under the mib-2 subtree. 652 7. References 654 7.1. Normative References 656 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 657 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 658 RFC2119, March 1997, 659 . 661 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 662 Schoenwaelder, Ed., "Structure of Management Information 663 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 664 RFC2578, April 1999, 665 . 667 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 668 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 669 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 670 . 672 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 673 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 674 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 675 . 677 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 678 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 679 . 681 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 682 (USM) for version 3 of the Simple Network Management 683 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 684 RFC3414, December 2002, 685 . 687 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 688 "Multiprotocol Label Switching (MPLS) Traffic Engineering 689 (TE) Management Information Base (MIB)", RFC 3812, DOI 690 10.17487/RFC3812, June 2004, 691 . 693 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 694 Advanced Encryption Standard (AES) Cipher Algorithm in the 695 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 696 RFC3826, June 2004, 697 . 699 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 700 for the Simple Network Management Protocol (SNMP)", STD 701 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 702 . 704 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 705 Shell Transport Model for the Simple Network Management 706 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 707 2009, . 709 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 710 Model for the Simple Network Management Protocol (SNMP)", 711 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 712 . 714 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 715 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 716 2012, . 718 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 719 Encodings and Procedures for Multicast in MPLS/BGP IP 720 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 721 . 723 [RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and 724 C. Kodeboniya, "Multicast in Virtual Private LAN Service 725 (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014, 726 . 728 7.2. Informative References 730 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 731 "Introduction and Applicability Statements for Internet- 732 Standard Management Framework", RFC 3410, DOI 10.17487/ 733 RFC3410, December 2002, 734 . 736 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 737 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 738 Protocol Specification (Revised)", RFC 4601, DOI 10.17487/ 739 RFC4601, August 2006, 740 . 742 [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. 743 Yasukawa, Ed., "Extensions to Resource Reservation 744 Protocol - Traffic Engineering (RSVP-TE) for Point-to- 745 Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI 746 10.17487/RFC4875, May 2007, 747 . 749 [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 750 "Bidirectional Protocol Independent Multicast (BIDIR- 751 PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, 752 . 754 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 755 Thomas, "Label Distribution Protocol Extensions for Point- 756 to-Multipoint and Multipoint-to-Multipoint Label Switched 757 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 758 . 760 Authors' Addresses 761 Zhaohui (Jeffrey) Zhang 762 Juniper Networks, Inc. 763 10 Technology Park Drive 764 Westford, MA 01886 765 USA 767 Email: zzhang@juniper.net 769 Hiroshi Tsunoda 770 Tohoku Institute of Technology 771 35-1, Yagiyama Kasumi-cho 772 Taihaku-ku, Sendai 982-8577 773 Japan 775 Phone: +81-22-305-3411 776 Email: tsuno@m.ieice.org