idnits 2.17.1 draft-ietf-bess-l2l3-vpn-mcast-mib-13.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 (December 12, 2017) is 2298 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 391, but not defined == Missing Reference: 'RFCXXXX' is mentioned on line 395, but not defined == Unused Reference: 'RFC4087' is defined on line 794, but no explicit reference was found in the text == Unused Reference: 'RFC7385' is defined on line 845, but no explicit reference was found in the text == Unused Reference: 'RFC7902' is defined on line 862, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 7 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: June 15, 2018 Tohoku Institute of Technology 6 December 12, 2017 8 L2L3 VPN Multicast MIB 9 draft-ietf-bess-l2l3-vpn-mcast-mib-13 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 June 15, 2018. 36 Copyright Notice 38 Copyright (c) 2017 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 "201711071200Z" -- 7th November, 2017 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 "201711071200Z" -- 7th November, 2017 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 RFC7385 276 RFC7524, Section 14.1 277 RFC7761 278 " 280 SYNTAX INTEGER 281 { 282 noTunnelInfo (0), 283 rsvpP2mp (1), 284 ldpP2mp (2), 285 pimSsm (3), 286 pimAsm (4), 287 pimBidir (5), 288 ingressReplication (6), 289 ldpMp2mp (7), 290 transportTunnel (8) 291 } 293 L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION 294 STATUS current 295 DESCRIPTION 296 "This textual convention represents the tunnel identifier 297 of a P-tunnel. 299 The size of the identifier depends on the address family 300 (IPv4 or IPv6) and the value of the corresponding 301 L2L3VpnMcastProviderTunnelType object. 303 The corresponding L2L3VpnMcastProviderTunnelType object 304 represents the type of the tunneling technology used 305 to establish the P-tunnel. 307 The size of the identifier for each tunneling technology 308 is summarized below. 310 L2L3VpnMcastProviderTunnelType Size (in octets) 311 (tunneling technology) IPv4 IPv6 312 ----------------------------------------------------------- 313 noTunnelInfo (No tunnel information) 0 0 314 rsvpP2mp (RSVP-TE P2MP LSP) 12 24 315 ldpP2mp (mLDP P2MP LSP) 17 29 316 pimSsm (PIM-SSM Tree) 8 32 317 pimAsm (PIM-SM Tree) 8 32 318 pimBidir (BIDIR-PIM Tree) 8 32 319 ingressReplication (Ingress Replication) 4 16 320 ldpMp2mp (mLDP MP2MP LSP) 17 29 321 transportTunnel (Transport Tunnel) 8 32 323 Tunnel type is set to 'No tunnel information present' 324 when the PMSI Tunnel attribute carries no tunnel 325 information (there is no Tunnel Identifier). 326 The value of the corresponding L2L3VpnMcastProviderTunnelId 327 object will be a string of length zero. 329 For tunnel type rsvpP2mp(1), the corresponding Tunnel 330 Identifier is composed of Extended Tunnel ID (4 octets in IPv4, 331 16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets), 332 and P2MP ID (4 octets). 333 The size of the corresponding L2L3VpnMcastProviderTunnelId 334 object will be 12 octets in IPv4 and 24 octets in IPv6. 336 For tunnel type ldpP2mp(2), the corresponding Tunnel Identifier 337 is the P2MP Forwarding Equivalence Class (FEC) Element 338 [RFC6388]. The size of the corresponding 339 L2L3VpnMcastProviderTunnelId object will be 17 octets 340 in IPv4 and 29 octets in IPv6. 342 For tunnel type pimSsm(3), PimAsm(4), and PimBidir(5), the 343 corresponding Tunnel Identifier is composed of the source IP 344 address and the group IP address. 345 The size of the corresponding L2L3VpnMcastProviderTunnelId 346 object will be 8 octets in IPv4 and 32 octets in IPv6. 348 For tunnel type ingressReplication(6), the Tunnel Identifier is 349 the unicast tunnel endpoint IP address of the local PE. 350 The size of the corresponding L2L3VpnMcastProviderTunnelId 351 object will be 4 octets in IPv4 and 16 octets in IPv6. 353 For tunnel type ldpMp2mp(7), the Tunnel Identifier is 354 MP2MP FEC Element [RFC6388]. 355 The size of the corresponding L2L3VpnMcastProviderTunnelId 356 object will be 17 octets in IPv4 and 29 octets in IPv6. 358 For tunnel type transportTunnel(8), the Tunnel Identifier 359 is a tuple of Source PE Address and Local Number, 360 which is a number that is unique to the Source PE [RFC7524]. 361 Both Source PE Address and Local Number are 4 octets in IPv4 362 and 16 octets in IPv6. 363 The size of the corresponding L2L3VpnMcastProviderTunnelId 364 object will be 8 octets in IPv4 and 32 octets in IPv6. 365 " 366 REFERENCE 367 "RFC6514, Section 5 368 RFC4875, Section 19.1 369 RFC6388, Section 2.2 and 3.2 370 RFC7524, Section 14.1 371 " 372 SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) 374 END 376 4.2. L2L3-VPN-MCAST-MIB Object Definitions 378 L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN 380 IMPORTS 381 MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero 382 FROM SNMPv2-SMI -- [RFC2578] 384 MODULE-COMPLIANCE, OBJECT-GROUP 385 FROM SNMPv2-CONF -- [RFC2580] 387 RowPointer 388 FROM SNMPv2-TC -- [RFC2579] 390 MplsLabel 391 FROM MPLS-TC-STD-MIB -- [RFC3811] 393 L2L3VpnMcastProviderTunnelType, 394 L2L3VpnMcastProviderTunnelId 395 FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX] 397 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 399 l2L3VpnMcastMIB MODULE-IDENTITY 400 LAST-UPDATED "201712121200Z" -- 12th December, 2017 401 ORGANIZATION "IETF BESS Working Group." 402 CONTACT-INFO 403 " Zhaohui Zhang 404 Juniper Networks, Inc. 405 10 Technology Park Drive 406 Westford, MA 01886 407 USA 408 Email: zzhang@juniper.net 410 Hiroshi Tsunoda 411 Tohoku Institute of Technology 412 35-1, Yagiyama Kasumi-cho 413 Taihaku-ku, Sendai, 982-8577 414 Japan 415 Email: tsuno@m.ieice.org 417 Comments and discussion to bess@ietf.org 418 " 420 DESCRIPTION 421 "This MIB module defines a table representing the attribute 422 information of the provider tunnels (P-tunnels) on a PE router. 423 This MIB module will be used by other MIB modules designed for 424 monitoring and/or configuring Border Gateway 425 Protocol/MultiProtocol Label Switching 426 Layer 2 and Layer 3 Virtual Private 427 Network that support multicast (L2L3VpnMCast network). 428 Copyright (C) The Internet Society (2017). 429 " 430 -- Revision history. 432 REVISION "201712121200Z" -- 12th December, 2017 433 DESCRIPTION 434 "Initial version, published as RFC XXXX." 436 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 438 ::= { mib-2 BBBB } 440 -- IANA Reg.: Please assign a value for "BBBB" under the 441 -- 'mib-2' subtree and record the assignment in the SMI 442 -- Numbers registry. 444 -- RFC Ed.: When the above assignment has been made, please 445 -- remove the above note 446 -- replace "BBBB" here with the assigned value and 447 -- remove this note. 449 -- Top level components of this MIB. 450 l2L3VpnMcastStates OBJECT IDENTIFIER 451 ::= { l2L3VpnMcastMIB 1 } 453 l2L3VpnMcastConformance OBJECT IDENTIFIER 454 ::= { l2L3VpnMcastMIB 2 } 456 -- tables, scalars, conformance information 457 -- Table of PMSI Tunnel Attributes 459 l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE 460 SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry 461 MAX-ACCESS not-accessible 462 STATUS current 463 DESCRIPTION 464 "An entry in this table corresponds to 465 the attribute information of a specific 466 P-tunnel on a PE router. 467 A part of attributes correspond to fields in 468 a Provider Multicast Service Interface (PMSI) Tunnel 469 attribute advertised and received by a PE router. 470 The entries will be referred to by other MIB modules 471 for monitoring and/or configuring L2L3VpnMCast networks. 472 " 473 REFERENCE 474 "RFC6514, Section 5" 475 ::= { l2L3VpnMcastStates 1 } 477 l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE 478 SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry 479 MAX-ACCESS not-accessible 480 STATUS current 481 DESCRIPTION 482 "A conceptual row corresponding to a specific 483 P-tunnel on this router. 484 " 485 REFERENCE 486 "RFC6514, Section 5" 487 INDEX { 488 l2L3VpnMcastPmsiTunnelAttributeType, 489 l2L3VpnMcastPmsiTunnelAttributeId 490 } 491 ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } 493 L2L3VpnMcastPmsiTunnelAttributeEntry ::= 494 SEQUENCE { 495 l2L3VpnMcastPmsiTunnelAttributeType 496 L2L3VpnMcastProviderTunnelType, 497 l2L3VpnMcastPmsiTunnelAttributeId 498 L2L3VpnMcastProviderTunnelId, 499 l2L3VpnMCastPmsiTunnelLeafInfoRequired 500 INTEGER, 501 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 502 MplsLabel, 503 l2L3VpnMcastPmsiTunnelPointer 504 RowPointer, 505 l2L3VpnMcastPmsiTunnelIf 506 RowPointer 507 } 509 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE 510 SYNTAX L2L3VpnMcastProviderTunnelType 511 MAX-ACCESS not-accessible 512 STATUS current 513 DESCRIPTION 514 "This object indicates the type of the tunneling technology 515 used to establish the P-tunnel corresponding to this entry. 517 When BGP-based PMSI signaling is used, the value of 518 this object corresponds to the Tunnel Type field 519 in the PMSI Tunnel attribute advertised/received 520 in a PMSI auto-discovery (A-D) route. 521 " 522 REFERENCE 523 "RFC6514, Section 5" 524 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 526 l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 527 SYNTAX L2L3VpnMcastProviderTunnelId 528 MAX-ACCESS not-accessible 529 STATUS current 530 DESCRIPTION 531 "This object represents the Tunnel Identifier field, which 532 uniquely identifies a P-tunnel, in the PMSI Tunnel attribute 533 of the P-tunnel corresponding to this entry. 535 The size of the identifier depends on the address family 536 (IPv4 or IPv6) and the value of the corresponding 537 l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of 538 the tunneling technology used to establish the P-tunnel. 539 " 540 REFERENCE 541 "RFC6514, Section 5" 542 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } 544 l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE 545 SYNTAX INTEGER { 546 false (0), 547 true (1), 548 notAvailable (2) 549 } 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "When the value of this object is set to 1 (true), 554 it indicates that the PE which originated the 555 PMSI Tunnel attribute of the P-tunnel corresponding 556 to this entry requests receivers to originate 557 a new Leaf A-D (Auto-Discovery) route. 559 A value of 0 (false) indicates that there is no such 560 request. 562 When the P-tunnel does not have a corresponding PMSI 563 tunnel attribute, the value of this object will be 564 2 (notAvailable). 566 In the case of Multicast in MPLS/BGP IP VPNs, 567 this object represents the 'Leaf Information Required flag' 568 [RFC6514] in the Flags field in the PMSI Tunnel attribute 569 of the P-tunnel corresponding to this entry. 570 " 571 REFERENCE 572 "RFC6514, Section 5 573 " 574 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } 576 l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE 577 SYNTAX MplsLabel 578 MAX-ACCESS read-only 579 STATUS current 580 DESCRIPTION 581 "This object represents the MPLS Label in the PMSI Tunnel 582 attribute of the P-tunnel corresponding to this entry. 584 When BGP-based PMSI signaling is used, the PMSI Tunnel 585 attribute of the P-tunnel will be advertised/received 586 in a PMSI auto-discovery (A-D) route. The value of 587 this object corresponds to the MPLS Label in the attribute. 589 When the P-tunnel does not have a PMSI tunnel 590 attribute, the value of this object will be 0. 591 " 592 REFERENCE 593 "RFC6514, Section 5" 594 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 596 l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE 597 SYNTAX RowPointer 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "Details of a P-tunnel identified by 602 l2L3VpnMcastPmsiTunnelAttributeId may be present 603 in some other table, e.g., 604 mplsTunnelTable [RFC3812]. This object specifies 605 the pointer to the row that pertains to the entry 606 in the table. 608 If no such entry exists, the value of this object 609 will be zeroDotZero. 610 " 611 REFERENCE 612 "RFC3812, Section 6.1 and Section 11" 613 DEFVAL { zeroDotZero } 615 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 617 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE 618 SYNTAX RowPointer 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "If the P-tunnel identified by 623 l2L3VpnMcastPmsiTunnelAttributeId has a corresponding 624 entry in ifXTable [RFC2863], this object will 625 point to the row in ifXTable that pertains to the entry. 626 Otherwise, the value of this object will be zeroDotZero. 627 " 628 REFERENCE 629 "RFC2863, Section 6" 630 DEFVAL { zeroDotZero } 631 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } 633 -- Conformance Information 635 l2L3VpnMcastCompliances OBJECT IDENTIFIER 636 ::= { l2L3VpnMcastConformance 1 } 637 l2L3VpnMcastGroups OBJECT IDENTIFIER 638 ::= { l2L3VpnMcastConformance 2 } 640 -- Compliance Statements 642 l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE 643 STATUS current 644 DESCRIPTION 645 "The core compliance statement for SNMP entities 646 which implement the L2L3-VPN-MCAST-MIB Module." 647 MODULE -- this module 649 MANDATORY-GROUPS { 650 l2L3VpnMcastCoreGroup 651 } 652 ::= { l2L3VpnMcastCompliances 1 } 654 l2L3VpnMcastFullCompliance MODULE-COMPLIANCE 655 STATUS current 656 DESCRIPTION 657 "The full compliance statement for SNMP entities 658 which implement the L2L3-VPN-MCAST-MIB Module." 659 MODULE -- this module 661 MANDATORY-GROUPS { 662 l2L3VpnMcastCoreGroup, 663 l2L3VpnMcastOptionalGroup 664 } 665 ::= { l2L3VpnMcastCompliances 2 } 667 -- units of conformance 669 l2L3VpnMcastCoreGroup OBJECT-GROUP 670 OBJECTS { 671 l2L3VpnMCastPmsiTunnelLeafInfoRequired, 672 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 673 } 674 STATUS current 675 DESCRIPTION 676 "Support of these objects is required." 677 ::= { l2L3VpnMcastGroups 1 } 679 l2L3VpnMcastOptionalGroup OBJECT-GROUP 680 OBJECTS { 681 l2L3VpnMcastPmsiTunnelPointer, 682 l2L3VpnMcastPmsiTunnelIf 683 } 684 STATUS current 685 DESCRIPTION 686 "Support of these objects is optional." 687 ::= { l2L3VpnMcastGroups 2 } 689 END 691 5. Security Considerations 693 There are no management objects defined in these MIB modules that 694 have a MAX-ACCESS clause of read-write and/or read-create. So, if 695 this MIB module is implemented correctly, then there is no risk that 696 an intruder can alter or create any management objects of this MIB 697 module via direct SNMP SET operations. 699 Some of the readable objects in these MIB modules (i.e., objects with 700 a MAX-ACCESS other than not-accessible) may be considered sensitive 701 or vulnerable in some network environments. It is thus important to 702 control even GET and/or NOTIFY access to these objects and possibly 703 to even encrypt the values of these objects when sending them over 704 the network via SNMP. These are the tables and objects and their 705 sensitivity/vulnerability: 707 o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the 708 P-tunnel network topology and its performance characteristics. 709 For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will 710 contain the identifier that uniquely identifies a P-tunnel. This 711 identifier may be composed of source and multicast group IP 712 addresses. l2L3VpnMcastPmsiTunnelPointer and 713 l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries 714 in other tables containing configuration and/or performance 715 information of a P-tunnel and its interface. If an Administrator 716 does not want to reveal this information, then these objects 717 should be considered sensitive/vulnerable. 719 SNMP versions prior to SNMPv3 did not include adequate security. 720 Even if the network itself is secure (for example by using IPsec), 721 there is no control as to who on the secure network is allowed to 722 access and GET/SET (read/change/create/delete) the objects in this 723 MIB module. 725 Implementations SHOULD provide the security features described by the 726 SNMPv3 framework (see [RFC3410]), and implementations claiming 727 compliance to the SNMPv3 standard MUST include full support for 728 authentication and privacy via the User-based Security Model (USM) 729 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 730 MAY also provide support for the Transport Security Model (TSM) 731 [RFC5591] in combination with a secure transport such as SSH 732 [RFC5592] or TLS/DTLS [RFC6353]. 734 Further, deployment of SNMP versions prior to SNMPv3 is NOT 735 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 736 enable cryptographic security. It is then a customer/operator 737 responsibility to ensure that the SNMP entity giving access to an 738 instance of this MIB module is properly configured to give access to 739 the objects only to those principals (users) that have legitimate 740 rights to indeed GET or SET (change/create/delete) them. 742 6. IANA Considerations 744 IANA is requested to root MIB objects in the MIB module contained in 745 this document under the mib-2 subtree. 747 7. References 749 7.1. Normative References 751 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 752 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 753 RFC2119, March 1997, . 756 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 757 Schoenwaelder, Ed., "Structure of Management Information 758 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 759 RFC2578, April 1999, . 762 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 763 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 764 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 765 . 767 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 768 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 769 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 770 . 772 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 773 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 774 . 776 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 777 (USM) for version 3 of the Simple Network Management 778 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 779 RFC3414, December 2002, . 782 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 783 "Multiprotocol Label Switching (MPLS) Traffic Engineering 784 (TE) Management Information Base (MIB)", RFC 3812, DOI 785 10.17487/RFC3812, June 2004, . 788 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 789 Advanced Encryption Standard (AES) Cipher Algorithm in the 790 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 791 RFC3826, June 2004, . 794 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, DOI 10.17487/ 795 RFC4087, June 2005, . 798 [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. 799 Yasukawa, Ed., "Extensions to Resource Reservation 800 Protocol - Traffic Engineering (RSVP-TE) for Point-to- 801 Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI 802 10.17487/RFC4875, May 2007, . 805 [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 806 "Bidirectional Protocol Independent Multicast (BIDIR- 807 PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, 808 . 810 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 811 for the Simple Network Management Protocol (SNMP)", STD 812 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 813 . 815 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 816 Shell Transport Model for the Simple Network Management 817 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 818 2009, . 820 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 821 Model for the Simple Network Management Protocol (SNMP)", 822 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 823 . 825 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 826 Thomas, "Label Distribution Protocol Extensions for Point- 827 to-Multipoint and Multipoint-to-Multipoint Label Switched 828 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 829 . 831 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 832 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 833 2012, . 835 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 836 Encodings and Procedures for Multicast in MPLS/BGP IP 837 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 838 . 840 [RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and 841 C. Kodeboniya, "Multicast in Virtual Private LAN Service 842 (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014, 843 . 845 [RFC7385] Andersson, L. and G. Swallow, "IANA Registry for 846 P-Multicast Service Interface (PMSI) Tunnel Type Code 847 Points", RFC 7385, DOI 10.17487/RFC7385, October 2014, 848 . 850 [RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T., 851 Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area 852 Point-to-Multipoint (P2MP) Segmented Label Switched Paths 853 (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, 854 . 856 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 857 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 858 Multicast - Sparse Mode (PIM-SM): Protocol Specification 859 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 860 2016, . 862 [RFC7902] Rosen, E. and T. Morin, "Registry and Extensions for 863 P-Multicast Service Interface Tunnel Attribute Flags", RFC 864 7902, DOI 10.17487/RFC7902, June 2016, . 867 7.2. Informative References 869 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 870 "Introduction and Applicability Statements for Internet- 871 Standard Management Framework", RFC 3410, DOI 10.17487/ 872 RFC3410, December 2002, . 875 Authors' Addresses 877 Zhaohui (Jeffrey) Zhang 878 Juniper Networks, Inc. 879 10 Technology Park Drive 880 Westford, MA 01886 881 USA 883 Email: zzhang@juniper.net 884 Hiroshi Tsunoda 885 Tohoku Institute of Technology 886 35-1, Yagiyama Kasumi-cho 887 Taihaku-ku, Sendai 982-8577 888 Japan 890 Phone: +81-22-305-3411 891 Email: tsuno@m.ieice.org