idnits 2.17.1 draft-ietf-bess-l2l3-vpn-mcast-mib-11.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 (October 20, 2017) is 2378 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. 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 390, but not defined == Missing Reference: 'RFCXXXX' is mentioned on line 394, but not defined == Unused Reference: 'RFC4087' is defined on line 850, but no explicit reference was found in the text == Unused Reference: 'RFC7385' is defined on line 901, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 6 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: April 23, 2018 Tohoku Institute of Technology 6 October 20, 2017 8 L2L3 VPN Multicast MIB 9 draft-ietf-bess-l2l3-vpn-mcast-mib-11 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 April 23, 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 . . . . . . . . . . . . . . . . . . . 17 61 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 63 7.1. Normative References . . . . . . . . . . . . . . . . . . 18 64 7.2. Informative References . . . . . . . . . . . . . . . . . 20 65 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 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 an identifier of the established are 86 determined by the type of the P-tunnel [RFC6514]. The P-tunnel type 87 and the P-tunnel 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. The P-tunnel type and the P-tunnel identifier are 94 in a 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 network. 100 This document defines two TCs to represent 102 (a) the type of a P-tunnel and 103 (b) the identifier of a P-tunnel 105 respectively. 107 The document also defines MOs that will provide the information 108 contained in a PMSI tunnel attribute and corresponding P-tunnel 109 information. 111 1.1. Terminology 113 This document adopts the definitions, acronyms and mechanisms 114 described in [RFC6513] [RFC6514] [RFC7117] and other documents that 115 they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN, 116 Multicast VPN concepts and/or mechanisms is assumed. Some terms 117 specifically related to this document are explained below. 119 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 120 conceptual interface instantiated by a P-tunnel, a transport 121 mechanism used to deliver multicast traffic. A PE uses it to send 122 customer multicast traffic to all or some PEs in the same VPN. 124 There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and 125 "Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that 126 enables a PE attached to a particular Multicast VPN to transmit a 127 message to all PEs in the same VPN. An S-PMSI is a PMSI that enables 128 a PE attached to a particular Multicast VPN to transmit a message to 129 some of the PEs in the same VPN. 131 Throughout this document, we will use the term "PMSI" to refer both 132 "I-PMSI" and "S-PMSI." 134 The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" in this 135 document are to be interpreted as described in [RFC2119]. 137 2. The Internet-Standard Management Framework 139 For a detailed overview of the documents that describe the current 140 Internet-Standard Management Framework, please refer to section 7 of 141 RFC 3410 [RFC3410]. 143 Managed objects are accessed via a virtual information store, termed 144 the Management Information Base or MIB. MIB objects are generally 145 accessed through the Simple Network Management Protocol (SNMP). 146 Objects in the MIB are defined using the mechanisms defined in the 147 Structure of Management Information (SMI). This memo specifies a MIB 148 module that is compliant to the SMIv2, which is described in STD 58, 149 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 150 [RFC2580]. 152 3. Summary of MIB Modules 154 This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and 155 L2L3-VPN-MCAST-MIB. 157 o L2L3-VPN-MCAST-TC-MIB contains two Textual Conventions: 158 L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId. 159 L2L3VpnMcastProviderTunnelType provides an enumeration of the 160 P-tunnel types. L2L3VpnMcastProviderTunnelId represents an 161 identifier of a P-tunnel. 163 o L2L3-VPN-MCAST-MIB defines a table 164 l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table 165 corresponds to the attribute information of a specific P-tunnel on 166 a PE router. Entries in this table will be used by other MIB 167 modules for monitoring and/or configuring L2L3VpnMCast network. 168 The table index uniquely identifies a P-tunnel. It is composed of 169 a type and indentifier of a P-tunnel. The table may also be used 170 in conjunction with other MIBs, such as MPLS Traffic Engineering 171 MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information 172 about a P-tunnel. It may also be used in conjunction with the 173 Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further 174 information about the interface corresponding to a P-tunnel. 176 4. Definitions 178 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 180 L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN 182 IMPORTS 183 MODULE-IDENTITY, mib-2 184 FROM SNMPv2-SMI -- [RFC2578] 186 TEXTUAL-CONVENTION 187 FROM SNMPv2-TC; -- [RFC2579] 189 l2L3VpnMcastTCMIB MODULE-IDENTITY 190 LAST-UPDATED "201710041200Z" -- 4th October, 2017 191 ORGANIZATION "IETF BESS Working Group." 192 CONTACT-INFO 193 " Zhaohui Zhang 194 Juniper Networks, Inc. 195 10 Technology Park Drive 196 Westford, MA 01886 197 USA 198 Email: zzhang@juniper.net 200 Hiroshi Tsunoda 201 Tohoku Institute of Technology 202 35-1, Yagiyama Kasumi-cho 203 Taihaku-ku, Sendai, 982-8577 204 Japan 205 Email: tsuno@m.ieice.org 207 Comments and discussion to bess@ietf.org 208 " 209 DESCRIPTION 210 "This MIB module specifies textual conventions for 211 Border Gateway Protocol/MultiProtocol Label 212 Switching Layer 2 and Layer 3 Virtual Private Network 213 that support multicast (L2L3VpnMCast network). 215 Copyright (C) The Internet Society (2017). 216 " 218 -- Revision history. 220 REVISION "201710041200Z" -- 4th October, 2017 221 DESCRIPTION 222 "Initial version, published as RFC XXXX." 224 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 226 ::= { mib-2 AAAA } 228 -- IANA Reg.: Please assign a value for "AAAA" under the 229 -- 'mib-2' subtree and record the assignment in the SMI 230 -- Numbers registry. 232 -- RFC Ed.: When the above assignment has been made, please 233 -- remove the above note 234 -- replace "AAAA" here with the assigned value and 235 -- remove this note. 237 -- Textual convention 239 L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION 240 STATUS current 241 DESCRIPTION 242 "This textual convention enumerates values 243 representing the type of a provider tunnel (P-tunnel) 244 used for L2L3VpnMCast network. 245 These labeled numbers are aligned with the definition 246 of Tunnel types in Section 5 of [RFC6514] and 247 Section 14.1 of [RFC7524]. 249 The enumerated values and the corresponding P-tunnel type 250 are as follows: 252 noTunnelInfo (0) : no tunnel information present 253 [RFC6514] 254 rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875] 255 ldpP2mp (2) : mLDP P2MP LSP [RFC6388] 256 pimSsm (3) : PIM-SSM Tree [RFC7761] 257 pimAsm (4) : PIM-SM Tree [RFC7761] 258 pimBidir (5) : BIDIR-PIM Tree [RFC5015] 259 ingressReplication (6) : Ingress Replication [RFC6513] 260 ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388] 261 transportTunnel (8) : Transport Tunnel [RFC7524] 263 These numbers are registered at IANA. 264 A current list of assignments can be found at 265 . 267 " 268 REFERENCE 269 "RFC4875 270 RFC5015 271 RFC6388 272 RFC6513 273 RFC6514, Section 5 274 RFC7385 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 (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 "201710041200Z" -- 4th October, 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 "201710041200Z" -- 4th October, 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 network. 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 l2L3VpnMcastPmsiTunnelAttributeFlags 499 OCTET STRING, 500 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 501 MplsLabel, 502 l2L3VpnMcastPmsiTunnelPointer 503 RowPointer, 504 l2L3VpnMcastPmsiTunnelIf 505 RowPointer, 506 l2L3VpnMcastPmsiTunnelAttributeAddlFlags 507 OCTET STRING 508 } 510 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE 511 SYNTAX L2L3VpnMcastProviderTunnelType 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "This object indicates the type of the tunneling technology 516 used to establish the P-tunnel corresponding to this entry. 518 When BGP-based PMSI signaling is used, the value of 519 this object corresponds to the Tunnel Type field 520 in the PMSI Tunnel attribute advertised/received 521 in an PMSI auto-discovery (A-D) route. 522 " 523 REFERENCE 524 "RFC6514, Section 5" 525 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 527 l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 528 SYNTAX L2L3VpnMcastProviderTunnelId 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "This object represents the Tunnel Identifier field, which 533 uniquely identifies a P-tunnel, in the PMSI Tunnel attribute 534 of the P-tunnel corresponding to this entry. 536 The size of the identifier depends on the address family 537 (IPv4 or IPv6) and the value of the corresponding 538 l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of 539 the tunneling technology used to establish the P-tunnel. 540 " 541 REFERENCE 542 "RFC6514, Section 5" 543 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } 545 l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE 546 SYNTAX OCTET STRING (SIZE (1)) 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION 550 "This object represents the Flags field in the PMSI Tunnel 551 attribute of the P-tunnel corresponding to this entry. 552 The Flags field has the following format. 554 0 1 2 3 4 5 6 7 555 +-+-+-+-+-+-+-+-+ 556 |U|E| U |L| 557 +-+-+-+-+-+-+-+-+ 558 E: Extension flag [RFC7902] 559 U: Unassigned 560 L: Leaf Information Required flag [RFC6514] 562 When BGP-based PMSI signaling is used, the PMSI Tunnel 563 attribute of the P-tunnel will be advertised/received 564 in an PMSI auto-discovery (A-D) route. The value of 565 this object corresponds to the Flags field in the attribute. 567 When the P-tunnel does not have a correspondent PMSI tunnel 568 attribute, the value of this object will be 0. 570 These flags are registered at IANA. 571 A current list of assignments can be found at 572 . 574 " 575 REFERENCE 576 "RFC6514, Section 5 577 RFC7902, Section 3 578 " 579 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } 581 l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE 582 SYNTAX MplsLabel 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "This object represents the MPLS Label in the PMSI Tunnel 587 attribute of the P-tunnel corresponding to this entry. 589 When BGP-based PMSI signaling is used, the PMSI Tunnel 590 attribute of the P-tunnel will be advertised/received 591 in an PMSI auto-discovery (A-D) route. The value of 592 this object corresponds to the MPLS Label in the attribute. 594 When the P-tunnel does not have correspondent PMSI tunnel 595 attribute, the value of this object will be 0 that 596 indicates the absence of any MPLS Label. 598 " 599 REFERENCE 600 "RFC6514, Section 5" 601 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 603 l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE 604 SYNTAX RowPointer 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION 608 "The P-tunnel identified by 609 l2L3VpnMcastPmsiTunnelAttributeId may be represented 610 as an entry in some other table, e.g., 611 mplsTunnelTable [RFC3812]. This object specifies 612 the pointer to the row pertaining to the entry. 614 If such an entry does not exist, the value of this object 615 MUST be zeroDotZero. 616 " 617 REFERENCE 618 "RFC3812, Section 6.1 and Section 11" 619 DEFVAL { zeroDotZero } 621 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 623 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE 624 SYNTAX RowPointer 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "If the P-tunnel identified by 629 l2L3VpnMcastPmsiTunnelAttributeId has a corresponding 630 entry in the ifXTable [RFC2863], this object will 631 point to the row pertaining to the entry in the ifXTable. 632 Otherwise, this object MUST be set to zeroDotZero. 633 " 634 REFERENCE 635 "RFC2863, Section 6" 636 DEFVAL { zeroDotZero } 637 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } 639 l2L3VpnMcastPmsiTunnelAttributeAddlFlags OBJECT-TYPE 640 SYNTAX OCTET STRING (SIZE (6)) 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "This object represents BGP Additional PMSI Tunnel 645 Attribute Flags Extended Community defined in [RFC7902]. 647 The Additional PMSI Tunnel Attribute Flags is a string 648 of 48 one-bit Flags and has the following format. 650 0 1 2 651 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 652 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 653 | | | | 654 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 656 3 4 657 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 658 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 659 | | | | 660 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 662 When BGP-based PMSI signaling is used, the PMSI Tunnel 663 attribute of the P-tunnel will be advertised/received 664 in an PMSI auto-discovery (A-D) route. 665 When the Extension flag of 666 l2L3VpnMcastPmsiTunnelAttributeFlags object is set, 667 the value of this object corresponds to the value of 668 Additional PMSI Tunnel Attribute Flags Extended 669 Community in the advertised/received PMSI 670 auto-discovery (A-D) route. 672 When the Extension flag of 673 l2L3VpnMcastPmsiTunnelAttributeFlags object is not set, 674 the value of this object will be 0. 676 These flags are registered at IANA. 677 A current list of assignments can be found at 678 . 681 " 682 REFERENCE 683 "RFC6514, Section 5 684 RFC7902, Section 2 685 " 686 ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 } 688 -- Conformance Information 689 l2L3VpnMcastCompliances OBJECT IDENTIFIER 690 ::= { l2L3VpnMcastConformance 1 } 691 l2L3VpnMcastGroups OBJECT IDENTIFIER 692 ::= { l2L3VpnMcastConformance 2 } 694 -- Compliance Statements 696 l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE 697 STATUS current 698 DESCRIPTION 699 "The core compliance statement for SNMP entities 700 which implement this L2L3-VPN-MCAST-MIB Module." 701 MODULE -- this module 703 MANDATORY-GROUPS { 704 l2L3VpnMcastPmsiFieldGroup 705 } 706 ::= { l2L3VpnMcastCompliances 1 } 708 l2L3VpnMcastFullCompliance MODULE-COMPLIANCE 709 STATUS current 710 DESCRIPTION 711 "The full compliance statement for SNMP entities 712 which implement this L2L3-VPN-MCAST-MIB Module." 713 MODULE -- this module 715 MANDATORY-GROUPS { 716 l2L3VpnMcastPmsiFieldGroup, 717 l2L3VpnMcastOptionalGroup 718 } 719 ::= { l2L3VpnMcastCompliances 2 } 721 -- units of conformance 723 l2L3VpnMcastPmsiFieldGroup OBJECT-GROUP 724 OBJECTS { 725 l2L3VpnMcastPmsiTunnelAttributeFlags, 726 l2L3VpnMcastPmsiTunnelAttributeAddlFlags, 727 l2L3VpnMcastPmsiTunnelAttributeMplsLabel 728 } 729 STATUS current 730 DESCRIPTION 731 "Support of these objects is required." 732 ::= { l2L3VpnMcastGroups 1 } 734 l2L3VpnMcastOptionalGroup OBJECT-GROUP 735 OBJECTS { 736 l2L3VpnMcastPmsiTunnelPointer, 737 l2L3VpnMcastPmsiTunnelIf 738 } 739 STATUS current 740 DESCRIPTION 741 "Support of these objects is optional." 742 ::= { l2L3VpnMcastGroups 2 } 744 END 746 5. Security Considerations 748 There are no management objects defined in these MIB modules that 749 have a MAX-ACCESS clause of read-write and/or read-create. So, if 750 this MIB module is implemented correctly, then there is no risk that 751 an intruder can alter or create any management objects of this MIB 752 module via direct SNMP SET operations. 754 Some of the readable objects in these MIB modules (i.e., objects with 755 a MAX-ACCESS other than not-accessible) may be considered sensitive 756 or vulnerable in some network environments. It is thus important to 757 control even GET and/or NOTIFY access to these objects and possibly 758 to even encrypt the values of these objects when sending them over 759 the network via SNMP. These are the tables and objects and their 760 sensitivity/vulnerability: 762 o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the 763 P-tunnel network topology and its performance characteristics. 764 For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will 765 contain the identifier that uniquely identifies a created 766 P-tunnel. This identifier may be composed of source and multicast 767 group IP addresses. l2L3VpnMcastPmsiTunnelPointer and 768 l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries 769 in other tables containing configuration and/or performance 770 information of a P-tunnel and its interface. If an Administrator 771 does not want to reveal this information, then these objects 772 should be considered sensitive/vulnerable. 774 SNMP versions prior to SNMPv3 did not include adequate security. 775 Even if the network itself is secure (for example by using IPsec), 776 there is no control as to who on the secure network is allowed to 777 access and GET/SET (read/change/create/delete) the objects in this 778 MIB module. 780 Implementations SHOULD provide the security features described by the 781 SNMPv3 framework (see [RFC3410]), and implementations claiming 782 compliance to the SNMPv3 standard MUST include full support for 783 authentication and privacy via the User-based Security Model (USM) 785 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 786 MAY also provide support for the Transport Security Model (TSM) 787 [RFC5591] in combination with a secure transport such as SSH 788 [RFC5592] or TLS/DTLS [RFC6353]. 790 Further, deployment of SNMP versions prior to SNMPv3 is NOT 791 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 792 enable cryptographic security. It is then a customer/operator 793 responsibility to ensure that the SNMP entity giving access to an 794 instance of this MIB module is properly configured to give access to 795 the objects only to those principals (users) that have legitimate 796 rights to indeed GET or SET (change/create/delete) them. 798 6. IANA Considerations 800 IANA is requested to root MIB objects in the MIB module contained in 801 this document under the mib-2 subtree. 803 7. References 805 7.1. Normative References 807 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 808 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 809 RFC2119, March 1997, . 812 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 813 Schoenwaelder, Ed., "Structure of Management Information 814 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 815 RFC2578, April 1999, . 818 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 819 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 820 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 821 . 823 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 824 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 825 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 826 . 828 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 829 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 830 . 832 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 833 (USM) for version 3 of the Simple Network Management 834 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 835 RFC3414, December 2002, . 838 [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, 839 "Multiprotocol Label Switching (MPLS) Traffic Engineering 840 (TE) Management Information Base (MIB)", RFC 3812, DOI 841 10.17487/RFC3812, June 2004, . 844 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 845 Advanced Encryption Standard (AES) Cipher Algorithm in the 846 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 847 RFC3826, June 2004, . 850 [RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, DOI 10.17487/ 851 RFC4087, June 2005, . 854 [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. 855 Yasukawa, Ed., "Extensions to Resource Reservation 856 Protocol - Traffic Engineering (RSVP-TE) for Point-to- 857 Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI 858 10.17487/RFC4875, May 2007, . 861 [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 862 "Bidirectional Protocol Independent Multicast (BIDIR- 863 PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, 864 . 866 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 867 for the Simple Network Management Protocol (SNMP)", STD 868 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 869 . 871 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 872 Shell Transport Model for the Simple Network Management 873 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 874 2009, . 876 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 877 Model for the Simple Network Management Protocol (SNMP)", 878 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 879 . 881 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 882 Thomas, "Label Distribution Protocol Extensions for Point- 883 to-Multipoint and Multipoint-to-Multipoint Label Switched 884 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 885 . 887 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 888 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 889 2012, . 891 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 892 Encodings and Procedures for Multicast in MPLS/BGP IP 893 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 894 . 896 [RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and 897 C. Kodeboniya, "Multicast in Virtual Private LAN Service 898 (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014, 899 . 901 [RFC7385] Andersson, L. and G. Swallow, "IANA Registry for 902 P-Multicast Service Interface (PMSI) Tunnel Type Code 903 Points", RFC 7385, DOI 10.17487/RFC7385, October 2014, 904 . 906 [RFC7524] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T., 907 Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area 908 Point-to-Multipoint (P2MP) Segmented Label Switched Paths 909 (LSPs)", RFC 7524, DOI 10.17487/RFC7524, May 2015, 910 . 912 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 913 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 914 Multicast - Sparse Mode (PIM-SM): Protocol Specification 915 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 916 2016, . 918 [RFC7902] Rosen, E. and T. Morin, "Registry and Extensions for 919 P-Multicast Service Interface Tunnel Attribute Flags", RFC 920 7902, DOI 10.17487/RFC7902, June 2016, . 923 7.2. Informative References 925 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 926 "Introduction and Applicability Statements for Internet- 927 Standard Management Framework", RFC 3410, DOI 10.17487/ 928 RFC3410, December 2002, . 931 Authors' Addresses 933 Zhaohui (Jeffrey) Zhang 934 Juniper Networks, Inc. 935 10 Technology Park Drive 936 Westford, MA 01886 937 USA 939 Email: zzhang@juniper.net 941 Hiroshi Tsunoda 942 Tohoku Institute of Technology 943 35-1, Yagiyama Kasumi-cho 944 Taihaku-ku, Sendai 982-8577 945 Japan 947 Phone: +81-22-305-3411 948 Email: tsuno@m.ieice.org