| 1 |
<pre>Internet Engineering Task Force (IETF) Z. Zhang |
| 2 |
Request for Comments: 8502 Juniper Networks, Inc. |
| 3 |
Category: Standards Track H. Tsunoda |
| 4 |
ISSN: 2070-1721 Tohoku Institute of Technology |
| 5 |
December 2018 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">L2L3 VPN Multicast MIB</span> |
| 9 |
|
| 10 |
Abstract |
| 11 |
|
| 12 |
This memo defines a portion of the Management Information Base (MIB) |
| 13 |
for use with network management protocols in the Internet community. |
| 14 |
In particular, it describes two MIB modules that will be used by |
| 15 |
other MIB modules for monitoring and/or configuring Layer 2 and Layer |
| 16 |
3 Virtual Private Networks that support multicast. |
| 17 |
|
| 18 |
Status of This Memo |
| 19 |
|
| 20 |
This is an Internet Standards Track document. |
| 21 |
|
| 22 |
This document is a product of the Internet Engineering Task Force |
| 23 |
(IETF). It represents the consensus of the IETF community. It has |
| 24 |
received public review and has been approved for publication by the |
| 25 |
Internet Engineering Steering Group (IESG). Further information on |
| 26 |
Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>. |
| 27 |
|
| 28 |
Information about the current status of this document, any errata, |
| 29 |
and how to provide feedback on it may be obtained at |
| 30 |
<a href="https://www.rfc-editor.org/info/rfc8502">https://www.rfc-editor.org/info/rfc8502</a>. |
| 31 |
|
| 32 |
Copyright Notice |
| 33 |
|
| 34 |
Copyright (c) 2018 IETF Trust and the persons identified as the |
| 35 |
document authors. All rights reserved. |
| 36 |
|
| 37 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 38 |
Provisions Relating to IETF Documents |
| 39 |
(<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of |
| 40 |
publication of this document. Please review these documents |
| 41 |
carefully, as they describe your rights and restrictions with respect |
| 42 |
to this document. Code Components extracted from this document must |
| 43 |
include Simplified BSD License text as described in Section 4.e of |
| 44 |
the Trust Legal Provisions and are provided without warranty as |
| 45 |
described in the Simplified BSD License. |
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 60 |
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 61 |
<a href="#section-2">2</a>. The Internet-Standard Management Framework . . . . . . . . . <a href="#page-4">4</a> |
| 62 |
<a href="#section-3">3</a>. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 63 |
<a href="#section-4">4</a>. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a> |
| 64 |
<a href="#section-4.1">4.1</a>. L2L3-VPN-MULTICAST-TC-MIB Object Definitions . . . . . . <a href="#page-4">4</a> |
| 65 |
<a href="#section-4.2">4.2</a>. L2L3-VPN-MULTICAST-MIB Object Definitions . . . . . . . . <a href="#page-9">9</a> |
| 66 |
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a> |
| 67 |
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a> |
| 68 |
<a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 69 |
<a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a> |
| 70 |
<a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-19">19</a> |
| 71 |
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 72 |
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a> |
| 73 |
|
| 74 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 75 |
|
| 76 |
In BGP/MPLS Virtual Private Networks (VPNs), the Border Gateway |
| 77 |
Protocol (BGP) is used for distributing routes and Multiprotocol |
| 78 |
Label Switching (MPLS) is used for forwarding packets across service |
| 79 |
provider networks. |
| 80 |
|
| 81 |
The procedures for supporting multicast in a BGP/MPLS Layer 3 (L3) |
| 82 |
VPN are specified in [<a href="./rfc6513" title=""Multicast in MPLS/ BGP IP VPNs"">RFC6513</a>]. The procedures for supporting |
| 83 |
multicast in a BGP/MPLS Layer 2 (L2) VPN are specified in [<a href="./rfc7117" title=""Multicast in Virtual Private LAN Service (VPLS)"">RFC7117</a>]. |
| 84 |
Throughout this document, we will use the term "L2L3VpnMCast network" |
| 85 |
to mean a BGP/MPLS L2 and L3 VPN that supports multicast. |
| 86 |
|
| 87 |
L2L3VpnMCast networks use various transport mechanisms for forwarding |
| 88 |
a packet to all or a subset of Provider Edge (PE) routers across |
| 89 |
service provider networks. These transport mechanisms are abstracted |
| 90 |
as provider tunnels (P-tunnels). The type of P-tunnel indicates the |
| 91 |
type of tunneling technology used to establish the P-tunnel. The |
| 92 |
syntax and semantics of a Tunnel Identifier are determined by the |
| 93 |
corresponding P-tunnel type [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>]. The P-tunnel type and |
| 94 |
P-tunnel identifier together identify a P-tunnel. |
| 95 |
|
| 96 |
A BGP attribute that specifies information of a P-tunnel is called a |
| 97 |
Provider Multicast Service Interface (PMSI) Tunnel attribute. The |
| 98 |
PMSI Tunnel attribute is advertised/received by PEs in BGP auto- |
| 99 |
discovery (A-D) routes. [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>] defines the format of a PMSI |
| 100 |
Tunnel attribute. The P-tunnel type and the P-tunnel identifier are |
| 101 |
included in the corresponding PMSI Tunnel attribute. |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 111 |
|
| 112 |
|
| 113 |
This document describes textual conventions (TCs) and common managed |
| 114 |
objects (MOs) that will be used by other Management Information Base |
| 115 |
(MIB) modules for monitoring and/or configuring L2L3VpnMCast |
| 116 |
networks. |
| 117 |
|
| 118 |
This document defines two TCs to represent |
| 119 |
|
| 120 |
(a) the type of a P-tunnel and |
| 121 |
(b) the identifier of a P-tunnel |
| 122 |
|
| 123 |
The document also defines MOs that will provide the information |
| 124 |
contained in a PMSI Tunnel attribute and corresponding P-tunnel. |
| 125 |
|
| 126 |
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span> |
| 127 |
|
| 128 |
This document adopts the definitions, acronyms, and mechanisms |
| 129 |
described in [<a href="./rfc6513" title=""Multicast in MPLS/ BGP IP VPNs"">RFC6513</a>] [<a href="./rfc6514" title=""BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs"">RFC6514</a>] [<a href="./rfc7117" title=""Multicast in Virtual Private LAN Service (VPLS)"">RFC7117</a>] and other documents that |
| 130 |
they refer to. Familiarity with multicast, MPLS, Layer 3 VPN, and |
| 131 |
Multicast VPN concepts and/or mechanisms is assumed. Some terms |
| 132 |
specifically related to this document are explained below. |
| 133 |
|
| 134 |
PMSI [<a href="./rfc6513" title=""Multicast in MPLS/ BGP IP VPNs"">RFC6513</a>] is a conceptual interface instantiated by a P-tunnel, |
| 135 |
which is a transport mechanism used to deliver multicast traffic. A |
| 136 |
PE uses it to send customer multicast traffic to all or some PEs in |
| 137 |
the same VPN. |
| 138 |
|
| 139 |
There are two kinds of PMSIs: Inclusive PMSI (I-PMSI) and Selective |
| 140 |
PMSI (S-PMSI) [<a href="./rfc6513" title=""Multicast in MPLS/ BGP IP VPNs"">RFC6513</a>]. An I-PMSI is a PMSI that enables a PE |
| 141 |
attached to a particular Multicast VPN to transmit a message to all |
| 142 |
PEs in the same VPN. An S-PMSI is a PMSI that enables a PE attached |
| 143 |
to a particular Multicast VPN to transmit a message to some of the |
| 144 |
PEs in the same VPN. |
| 145 |
|
| 146 |
Throughout this document, we will use the term "PMSI" to refer to |
| 147 |
both "I-PMSI" and "S-PMSI". |
| 148 |
|
| 149 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 150 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and |
| 151 |
"OPTIONAL" in this document are to be interpreted as described in |
| 152 |
<a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>] [<a href="./rfc8174" title=""Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"">RFC8174</a>] when, and only when, they appear in all |
| 153 |
capitals, as shown here. |
| 154 |
|
| 155 |
|
| 156 |
|
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 167 |
|
| 168 |
|
| 169 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. The Internet-Standard Management Framework</span> |
| 170 |
|
| 171 |
For a detailed overview of the documents that describe the current |
| 172 |
Internet-Standard Management Framework, please refer to <a href="./rfc3410#section-7">section 7 of |
| 173 |
RFC 3410</a> [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>]. |
| 174 |
|
| 175 |
Managed objects are accessed via a virtual information store, termed |
| 176 |
the Management Information Base or MIB. MIB objects are generally |
| 177 |
accessed through the Simple Network Management Protocol (SNMP). |
| 178 |
Objects in the MIB are defined using the mechanisms defined in the |
| 179 |
Structure of Management Information (SMI). This memo specifies a MIB |
| 180 |
module that is compliant to the SMIv2, which is described in STD 58, |
| 181 |
<a href="./rfc2578">RFC 2578</a> [<a href="./rfc2578" title=""Structure of Management Information Version 2 (SMIv2)"">RFC2578</a>], STD 58, <a href="./rfc2579">RFC 2579</a> [<a href="./rfc2579" title=""Textual Conventions for SMIv2"">RFC2579</a>] and STD 58, <a href="./rfc2580">RFC 2580</a> |
| 182 |
[<a href="./rfc2580" title=""Conformance Statements for SMIv2"">RFC2580</a>]. |
| 183 |
|
| 184 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Summary of MIB Modules</span> |
| 185 |
|
| 186 |
This document defines two MIB modules: L2L3-VPN-MULTICAST-TC-MIB and |
| 187 |
L2L3-VPN-MULTICAST-MIB. |
| 188 |
|
| 189 |
o L2L3-VPN-MULTICAST-TC-MIB contains two textual conventions: |
| 190 |
L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId. |
| 191 |
L2L3VpnMcastProviderTunnelType provides an enumeration of the |
| 192 |
P-tunnel types. L2L3VpnMcastProviderTunnelId represents an |
| 193 |
identifier of a P-tunnel. |
| 194 |
|
| 195 |
o L2L3-VPN-MULTICAST-MIB defines the following table: |
| 196 |
l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table |
| 197 |
corresponds to the attribute information of a specific P-tunnel on |
| 198 |
a PE router. Entries in this table will be used by other MIB |
| 199 |
modules for monitoring and/or configuring an L2L3VpnMCast network. |
| 200 |
The table index uniquely identifies a P-tunnel. It is composed of |
| 201 |
a type and identifier of a P-tunnel. The table may also be used |
| 202 |
in conjunction with other MIBs, such as the MPLS Traffic |
| 203 |
Engineering MIB (MPLS-TE-STD-MIB) [<a href="./rfc3812" title=""Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)"">RFC3812</a>], to obtain further |
| 204 |
information about a P-tunnel. It may also be used in conjunction |
| 205 |
with the Interfaces Group MIB (IF-MIB) [<a href="./rfc2863" title=""The Interfaces Group MIB"">RFC2863</a>] to obtain further |
| 206 |
information about the interface corresponding to a P-tunnel. |
| 207 |
|
| 208 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Definitions</span> |
| 209 |
|
| 210 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. L2L3-VPN-MULTICAST-TC-MIB Object Definitions</span> |
| 211 |
|
| 212 |
This MIB module makes reference to the following documents: |
| 213 |
[<a href="./rfc4875" title=""Extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for Point-to- Multipoint TE Label Switched Paths (LSPs)"">RFC4875</a>], [<a href="./rfc5015" title=""Bidirectional Protocol Independent Multicast (BIDIR- PIM)"">RFC5015</a>], [<a href="./rfc6388" title=""Label Distribution Protocol Extensions for Point- to-Multipoint and Multipoint-to-Multipoint Label Switched Paths"">RFC6388</a>], [<a href="./rfc7524" title=""Inter-Area Point-to-Multipoint (P2MP) Segmented Label Switched Paths (LSPs)"">RFC7524</a>], and [<a href="./rfc7761" title=""Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)"">RFC7761</a>]. |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 223 |
|
| 224 |
|
| 225 |
L2L3-VPN-MULTICAST-TC-MIB DEFINITIONS ::= BEGIN |
| 226 |
|
| 227 |
IMPORTS |
| 228 |
MODULE-IDENTITY, mib-2 |
| 229 |
FROM SNMPv2-SMI -- <a href="./rfc2578">RFC 2578</a> |
| 230 |
|
| 231 |
TEXTUAL-CONVENTION |
| 232 |
FROM SNMPv2-TC; -- <a href="./rfc2579">RFC 2579</a> |
| 233 |
|
| 234 |
l2L3VpnMcastTCMIB MODULE-IDENTITY |
| 235 |
LAST-UPDATED "201812140000Z" -- 14 December 2018 |
| 236 |
ORGANIZATION "IETF BESS Working Group" |
| 237 |
CONTACT-INFO |
| 238 |
"Zhaohui Zhang |
| 239 |
Juniper Networks, Inc. |
| 240 |
10 Technology Park Drive |
| 241 |
Westford, MA 01886 |
| 242 |
United States of America |
| 243 |
Email: [email protected] |
| 244 |
|
| 245 |
Hiroshi Tsunoda |
| 246 |
Tohoku Institute of Technology |
| 247 |
35-1, Yagiyama Kasumi-cho |
| 248 |
Taihaku-ku, Sendai, 982-8577 |
| 249 |
Japan |
| 250 |
Email: [email protected]" |
| 251 |
|
| 252 |
DESCRIPTION |
| 253 |
"This MIB module specifies textual conventions for |
| 254 |
Border Gateway Protocol/Multiprotocol Label |
| 255 |
Switching Layer 2 and Layer 3 Virtual Private Networks |
| 256 |
that support multicast (L2L3VpnMCast networks). |
| 257 |
|
| 258 |
Copyright (c) 2018 IETF Trust and the persons identified |
| 259 |
as authors of the code. All rights reserved. |
| 260 |
|
| 261 |
Redistribution and use in source and binary forms, with or |
| 262 |
without modification, is permitted pursuant to, and subject |
| 263 |
to the license terms contained in, the Simplified BSD |
| 264 |
License set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's Legal |
| 265 |
Provisions Relating to IETF Documents |
| 266 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). |
| 267 |
" |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 279 |
|
| 280 |
|
| 281 |
-- Revision History |
| 282 |
|
| 283 |
REVISION "201812140000Z" -- 14 December 2018 |
| 284 |
DESCRIPTION |
| 285 |
"Initial version, published as <a href="./rfc8502">RFC 8502</a>." |
| 286 |
|
| 287 |
::= { mib-2 244 } |
| 288 |
|
| 289 |
-- Textual Convention |
| 290 |
|
| 291 |
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION |
| 292 |
STATUS current |
| 293 |
DESCRIPTION |
| 294 |
"This textual convention enumerates values |
| 295 |
representing the type of a provider tunnel (P-tunnel) |
| 296 |
used for L2L3VpnMCast networks. |
| 297 |
These labeled numbers are aligned with the definition |
| 298 |
of Tunnel Types in <a href="./rfc6514#section-5">Section 5 of RFC 6514</a> and |
| 299 |
<a href="./rfc7524#section-14.1">Section 14.1 of RFC 7524</a>. |
| 300 |
|
| 301 |
The enumerated values and the corresponding P-tunnel types |
| 302 |
are as follows: |
| 303 |
|
| 304 |
noTunnelInfo (0) : No tunnel information <a href="./rfc6514">RFC 6514</a> |
| 305 |
rsvpP2mp (1) : RSVP-TE P2MP LSP <a href="./rfc4875">RFC 4875</a> |
| 306 |
ldpP2mp (2) : mLDP P2MP LSP <a href="./rfc6388">RFC 6388</a> |
| 307 |
pimSsm (3) : PIM-SSM Tree <a href="./rfc7761">RFC 7761</a> |
| 308 |
pimAsm (4) : PIM-SM Tree <a href="./rfc7761">RFC 7761</a> |
| 309 |
pimBidir (5) : BIDIR-PIM Tree <a href="./rfc5015">RFC 5015</a> |
| 310 |
ingressReplication (6) : Ingress Replication <a href="./rfc6513">RFC 6513</a> |
| 311 |
ldpMp2mp (7) : mLDP MP2MP LSP <a href="./rfc6388">RFC 6388</a> |
| 312 |
transportTunnel (8) : Transport Tunnel <a href="./rfc7524">RFC 7524</a> |
| 313 |
|
| 314 |
These numbers are registered at IANA. |
| 315 |
A current list of assignments can be found at |
| 316 |
<<a href="https://www.iana.org/assignments/bgp-parameters/">https://www.iana.org/assignments/bgp-parameters/</a>>. |
| 317 |
" |
| 318 |
REFERENCE |
| 319 |
"<a href="./rfc4875">RFC 4875</a> |
| 320 |
<a href="./rfc5015">RFC 5015</a> |
| 321 |
<a href="./rfc6388">RFC 6388</a> |
| 322 |
<a href="./rfc6513">RFC 6513</a> |
| 323 |
<a href="./rfc6514#section-5">RFC 6514, Section 5</a> |
| 324 |
<a href="./rfc7524#section-14.1">RFC 7524, Section 14.1</a> |
| 325 |
<a href="./rfc7761">RFC 7761</a> |
| 326 |
" |
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 335 |
|
| 336 |
|
| 337 |
SYNTAX INTEGER |
| 338 |
{ |
| 339 |
noTunnelInfo (0), |
| 340 |
rsvpP2mp (1), |
| 341 |
ldpP2mp (2), |
| 342 |
pimSsm (3), |
| 343 |
pimAsm (4), |
| 344 |
pimBidir (5), |
| 345 |
ingressReplication (6), |
| 346 |
ldpMp2mp (7), |
| 347 |
transportTunnel (8) |
| 348 |
} |
| 349 |
|
| 350 |
L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION |
| 351 |
STATUS current |
| 352 |
DESCRIPTION |
| 353 |
"This textual convention represents the Tunnel Identifier |
| 354 |
of a P-tunnel. |
| 355 |
|
| 356 |
The size of the identifier depends on the address family |
| 357 |
(IPv4 or IPv6) and the value of the corresponding |
| 358 |
L2L3VpnMcastProviderTunnelType object. |
| 359 |
|
| 360 |
The corresponding L2L3VpnMcastProviderTunnelType object |
| 361 |
represents the type of tunneling technology used |
| 362 |
to establish the P-tunnel. |
| 363 |
|
| 364 |
The size of the identifier for each tunneling technology |
| 365 |
is summarized below. |
| 366 |
|
| 367 |
L2L3VpnMcastProviderTunnelType Size (in octets) |
| 368 |
(tunneling technology) IPv4 IPv6 |
| 369 |
----------------------------------------------------------- |
| 370 |
noTunnelInfo (No tunnel information) 0 0 |
| 371 |
rsvpP2mp (RSVP-TE P2MP LSP) 12 24 |
| 372 |
ldpP2mp (mLDP P2MP LSP) 17 29 |
| 373 |
pimSsm (PIM-SSM Tree) 8 32 |
| 374 |
pimAsm (PIM-SM Tree) 8 32 |
| 375 |
pimBidir (BIDIR-PIM Tree) 8 32 |
| 376 |
ingressReplication (Ingress Replication) 4 16 |
| 377 |
ldpMp2mp (mLDP MP2MP LSP) 17 29 |
| 378 |
transportTunnel (Transport Tunnel) 8 32 |
| 379 |
|
| 380 |
The Tunnel Type is set to 'No tunnel information' |
| 381 |
when the PMSI Tunnel attribute carries no tunnel |
| 382 |
information (there is no Tunnel Identifier). |
| 383 |
The value of the corresponding L2L3VpnMcastProviderTunnelId |
| 384 |
object will be a string of length zero. |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 391 |
|
| 392 |
|
| 393 |
For Tunnel Type rsvpP2mp(1), the corresponding Tunnel |
| 394 |
Identifier is composed of an Extended Tunnel ID (4 octets in |
| 395 |
IPv4, 16 octets in IPv6), 2 unused (Reserved) octets that of |
| 396 |
value zero, a Tunnel ID (2 octets), and a Point-to-Multipoint |
| 397 |
(P2MP) ID (4 octets). The size of the corresponding |
| 398 |
L2L3VpnMcastProviderTunnelId object will be 12 octets in IPv4 |
| 399 |
and 24 octets in IPv6. |
| 400 |
|
| 401 |
For Tunnel Type ldpP2mp(2), the corresponding Tunnel |
| 402 |
Identifier is the P2MP Forwarding Equivalence Class (FEC) |
| 403 |
Element (<a href="./rfc6388">RFC 6388</a>). The size of the corresponding |
| 404 |
L2L3VpnMcastProviderTunnelId object will be 17 octets |
| 405 |
in IPv4 and 29 octets in IPv6. |
| 406 |
|
| 407 |
For Tunnel Types pimSsm(3), PimAsm(4), and PimBidir(5), the |
| 408 |
corresponding Tunnel Identifier is composed of the source IP |
| 409 |
address and the group IP address. |
| 410 |
The size of the corresponding L2L3VpnMcastProviderTunnelId |
| 411 |
object will be 8 octets in IPv4 and 32 octets in IPv6. |
| 412 |
|
| 413 |
For Tunnel Type ingressReplication(6), the Tunnel Identifier |
| 414 |
is the unicast tunnel endpoint IP address of the local PE. |
| 415 |
The size of the corresponding L2L3VpnMcastProviderTunnelId |
| 416 |
object will be 4 octets in IPv4 and 16 octets in IPv6. |
| 417 |
|
| 418 |
For Tunnel Type ldpMp2mp(7), the Tunnel Identifier is |
| 419 |
a Multipoint-to-Multipoint (MP2MP) FEC Element (<a href="./rfc6388">RFC 6388</a>). |
| 420 |
The size of the corresponding L2L3VpnMcastProviderTunnelId |
| 421 |
object will be 17 octets in IPv4 and 29 octets in IPv6. |
| 422 |
|
| 423 |
For Tunnel Type transportTunnel(8), the Tunnel Identifier |
| 424 |
is a tuple of Source PE Address and Local Number, |
| 425 |
which is a number that is unique to the Source PE (<a href="./rfc7524">RFC 7524</a>). |
| 426 |
Both Source PE Address and Local Number are 4 octets in IPv4 |
| 427 |
and 16 octets in IPv6. |
| 428 |
The size of the corresponding L2L3VpnMcastProviderTunnelId |
| 429 |
object will be 8 octets in IPv4 and 32 octets in IPv6. |
| 430 |
" |
| 431 |
REFERENCE |
| 432 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a> |
| 433 |
<a href="./rfc4875#section-19.1">RFC 4875, Section 19.1</a> |
| 434 |
<a href="./rfc6388">RFC 6388</a>, Sections <a href="#section-2.2">2.2</a> and <a href="#section-3.2">3.2</a> |
| 435 |
<a href="./rfc7524#section-14.1">RFC 7524, Section 14.1</a> |
| 436 |
" |
| 437 |
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) |
| 438 |
|
| 439 |
END |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. L2L3-VPN-MULTICAST-MIB Object Definitions</span> |
| 450 |
|
| 451 |
This MIB module makes reference to the following documents: |
| 452 |
[<a href="./rfc3811" title=""Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management"">RFC3811</a>]. |
| 453 |
|
| 454 |
L2L3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN |
| 455 |
|
| 456 |
IMPORTS |
| 457 |
MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero |
| 458 |
FROM SNMPv2-SMI -- <a href="./rfc2578">RFC 2578</a> |
| 459 |
|
| 460 |
MODULE-COMPLIANCE, OBJECT-GROUP |
| 461 |
FROM SNMPv2-CONF -- <a href="./rfc2580">RFC 2580</a> |
| 462 |
|
| 463 |
RowPointer |
| 464 |
FROM SNMPv2-TC -- <a href="./rfc2579">RFC 2579</a> |
| 465 |
|
| 466 |
MplsLabel |
| 467 |
FROM MPLS-TC-STD-MIB -- <a href="./rfc3811">RFC 3811</a> |
| 468 |
|
| 469 |
L2L3VpnMcastProviderTunnelType, |
| 470 |
L2L3VpnMcastProviderTunnelId |
| 471 |
FROM L2L3-VPN-MULTICAST-TC-MIB; -- <a href="./rfc8502">RFC 8502</a> |
| 472 |
|
| 473 |
l2L3VpnMcastMIB MODULE-IDENTITY |
| 474 |
LAST-UPDATED "201812140000Z" -- 14 December 2018 |
| 475 |
ORGANIZATION "IETF BESS Working Group" |
| 476 |
CONTACT-INFO |
| 477 |
"Zhaohui Zhang |
| 478 |
Juniper Networks, Inc. |
| 479 |
10 Technology Park Drive |
| 480 |
Westford, MA 01886 |
| 481 |
United States of America |
| 482 |
Email: [email protected] |
| 483 |
|
| 484 |
Hiroshi Tsunoda |
| 485 |
Tohoku Institute of Technology |
| 486 |
35-1, Yagiyama Kasumi-cho |
| 487 |
Taihaku-ku, Sendai, 982-8577 |
| 488 |
Japan |
| 489 |
Email: [email protected]" |
| 490 |
|
| 491 |
DESCRIPTION |
| 492 |
"This MIB module defines a table representing the attribute |
| 493 |
information of the provider tunnels (P-tunnels) on a PE router. |
| 494 |
This MIB module will be used by other MIB modules designed for |
| 495 |
monitoring and/or configuring Border Gateway |
| 496 |
Protocol/Multiprotocol Label Switching |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 503 |
|
| 504 |
|
| 505 |
Layer 2 and Layer 3 Virtual Private |
| 506 |
Network that support multicast (L2L3VpnMCast network). |
| 507 |
|
| 508 |
Copyright (c) 2018 IETF Trust and the persons identified |
| 509 |
as authors of the code. All rights reserved. |
| 510 |
|
| 511 |
Redistribution and use in source and binary forms, with or |
| 512 |
without modification, is permitted pursuant to, and subject |
| 513 |
to the license terms contained in, the Simplified BSD License |
| 514 |
set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's Legal Provisions |
| 515 |
Relating to IETF Documents |
| 516 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). |
| 517 |
" |
| 518 |
|
| 519 |
-- Revision History |
| 520 |
|
| 521 |
REVISION "201812140000Z" -- 14 December 2018 |
| 522 |
DESCRIPTION |
| 523 |
"Initial version, published as <a href="./rfc8502">RFC 8502</a>." |
| 524 |
|
| 525 |
::= { mib-2 245 } |
| 526 |
|
| 527 |
-- Top-level components of this MIB. |
| 528 |
l2L3VpnMcastStates OBJECT IDENTIFIER |
| 529 |
::= { l2L3VpnMcastMIB 1 } |
| 530 |
|
| 531 |
l2L3VpnMcastConformance OBJECT IDENTIFIER |
| 532 |
::= { l2L3VpnMcastMIB 2 } |
| 533 |
|
| 534 |
-- Tables, Scalars, Conformance Information |
| 535 |
-- Table of PMSI Tunnel Attributes |
| 536 |
|
| 537 |
l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE |
| 538 |
SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry |
| 539 |
MAX-ACCESS not-accessible |
| 540 |
STATUS current |
| 541 |
DESCRIPTION |
| 542 |
"An entry in this table corresponds to |
| 543 |
the attribute information of a specific |
| 544 |
P-tunnel on a PE router. |
| 545 |
A part of the attributes corresponds to fields in |
| 546 |
a Provider Multicast Service Interface (PMSI) Tunnel |
| 547 |
attribute advertised and received by a PE router. |
| 548 |
The entries will be referred to by other MIB modules |
| 549 |
for monitoring and/or configuring L2L3VpnMCast networks. |
| 550 |
" |
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 559 |
|
| 560 |
|
| 561 |
REFERENCE |
| 562 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a>" |
| 563 |
::= { l2L3VpnMcastStates 1 } |
| 564 |
|
| 565 |
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE |
| 566 |
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry |
| 567 |
MAX-ACCESS not-accessible |
| 568 |
STATUS current |
| 569 |
DESCRIPTION |
| 570 |
"A conceptual row corresponding to a specific |
| 571 |
P-tunnel on this router. |
| 572 |
" |
| 573 |
REFERENCE |
| 574 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a>" |
| 575 |
INDEX { |
| 576 |
l2L3VpnMcastPmsiTunnelAttributeType, |
| 577 |
l2L3VpnMcastPmsiTunnelAttributeId |
| 578 |
} |
| 579 |
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } |
| 580 |
|
| 581 |
L2L3VpnMcastPmsiTunnelAttributeEntry ::= |
| 582 |
SEQUENCE { |
| 583 |
l2L3VpnMcastPmsiTunnelAttributeType |
| 584 |
L2L3VpnMcastProviderTunnelType, |
| 585 |
l2L3VpnMcastPmsiTunnelAttributeId |
| 586 |
L2L3VpnMcastProviderTunnelId, |
| 587 |
l2L3VpnMCastPmsiTunnelLeafInfoRequired |
| 588 |
INTEGER, |
| 589 |
l2L3VpnMcastPmsiTunnelAttributeMplsLabel |
| 590 |
MplsLabel, |
| 591 |
l2L3VpnMcastPmsiTunnelPointer |
| 592 |
RowPointer, |
| 593 |
l2L3VpnMcastPmsiTunnelIf |
| 594 |
RowPointer |
| 595 |
} |
| 596 |
|
| 597 |
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE |
| 598 |
SYNTAX L2L3VpnMcastProviderTunnelType |
| 599 |
MAX-ACCESS not-accessible |
| 600 |
STATUS current |
| 601 |
DESCRIPTION |
| 602 |
"This object indicates the type of tunneling technology |
| 603 |
used to establish the P-tunnel corresponding to this entry. |
| 604 |
|
| 605 |
When BGP-based PMSI signaling is used, the value of |
| 606 |
this object corresponds to the Tunnel Type field |
| 607 |
in the PMSI Tunnel attribute advertised/received |
| 608 |
in a PMSI auto-discovery (A-D) route. |
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 615 |
|
| 616 |
|
| 617 |
" |
| 618 |
REFERENCE |
| 619 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a>" |
| 620 |
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } |
| 621 |
|
| 622 |
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE |
| 623 |
SYNTAX L2L3VpnMcastProviderTunnelId |
| 624 |
MAX-ACCESS not-accessible |
| 625 |
STATUS current |
| 626 |
DESCRIPTION |
| 627 |
"This object represents the Tunnel Identifier field, which |
| 628 |
uniquely identifies a P-tunnel, in the PMSI Tunnel attribute |
| 629 |
of the P-tunnel corresponding to this entry. |
| 630 |
|
| 631 |
The size of the identifier depends on the address family |
| 632 |
(IPv4 or IPv6) and the value of the corresponding |
| 633 |
l2L3VpnMcastPmsiTunnelAttributeType object, i.e., the type of |
| 634 |
tunneling technology used to establish the P-tunnel. |
| 635 |
" |
| 636 |
REFERENCE |
| 637 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a>" |
| 638 |
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } |
| 639 |
|
| 640 |
|
| 641 |
l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE |
| 642 |
SYNTAX INTEGER { |
| 643 |
false (0), |
| 644 |
true (1), |
| 645 |
notAvailable (2) |
| 646 |
} |
| 647 |
MAX-ACCESS read-only |
| 648 |
STATUS current |
| 649 |
DESCRIPTION |
| 650 |
"When the value of this object is set to 1 (true), |
| 651 |
it indicates that the PE that originated the |
| 652 |
PMSI Tunnel attribute of the P-tunnel corresponding |
| 653 |
to this entry requests receivers to originate |
| 654 |
a new Leaf A-D route. |
| 655 |
|
| 656 |
A value of zero (false) indicates that there is no such |
| 657 |
request. |
| 658 |
|
| 659 |
When the P-tunnel does not have a corresponding PMSI |
| 660 |
Tunnel attribute, the value of this object will be |
| 661 |
2 (notAvailable). |
| 662 |
|
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 671 |
|
| 672 |
|
| 673 |
In the case of multicast in MPLS/BGP IP VPNs, |
| 674 |
this object represents the 'Leaf Information Required flag' |
| 675 |
(<a href="./rfc6514">RFC 6514</a>) in the Flags field in the PMSI Tunnel attribute |
| 676 |
of the P-tunnel corresponding to this entry. |
| 677 |
" |
| 678 |
REFERENCE |
| 679 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a> |
| 680 |
" |
| 681 |
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } |
| 682 |
|
| 683 |
l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE |
| 684 |
SYNTAX MplsLabel |
| 685 |
MAX-ACCESS read-only |
| 686 |
STATUS current |
| 687 |
DESCRIPTION |
| 688 |
"This object represents the MPLS Label in the PMSI Tunnel |
| 689 |
attribute of the P-tunnel corresponding to this entry. |
| 690 |
|
| 691 |
When BGP-based PMSI signaling is used, the PMSI Tunnel |
| 692 |
attribute of the P-tunnel will be advertised/received |
| 693 |
in a PMSI A-D route. The value of |
| 694 |
this object corresponds to the MPLS Label in the attribute. |
| 695 |
|
| 696 |
When the P-tunnel does not have a PMSI tunnel |
| 697 |
attribute, the value of this object will be zero. |
| 698 |
" |
| 699 |
REFERENCE |
| 700 |
"<a href="./rfc6514#section-5">RFC 6514, Section 5</a>" |
| 701 |
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } |
| 702 |
|
| 703 |
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE |
| 704 |
SYNTAX RowPointer |
| 705 |
MAX-ACCESS read-only |
| 706 |
STATUS current |
| 707 |
DESCRIPTION |
| 708 |
"Details of a P-tunnel identified by |
| 709 |
l2L3VpnMcastPmsiTunnelAttributeId may be present |
| 710 |
in some other table, e.g., |
| 711 |
mplsTunnelTable (<a href="./rfc3812">RFC 3812</a>). This object specifies |
| 712 |
the pointer to the row that pertains to the entry |
| 713 |
in the table. |
| 714 |
|
| 715 |
If no such entry exists, the value of this object |
| 716 |
will be zeroDotZero. |
| 717 |
" |
| 718 |
REFERENCE |
| 719 |
"<a href="./rfc3812">RFC 3812</a>, Sections <a href="#section-6.1">6.1</a> and <a href="#section-11">11</a>" |
| 720 |
DEFVAL { zeroDotZero } |
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 727 |
|
| 728 |
|
| 729 |
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } |
| 730 |
|
| 731 |
l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE |
| 732 |
SYNTAX RowPointer |
| 733 |
MAX-ACCESS read-only |
| 734 |
STATUS current |
| 735 |
DESCRIPTION |
| 736 |
"If the P-tunnel identified by |
| 737 |
l2L3VpnMcastPmsiTunnelAttributeId has a corresponding |
| 738 |
entry in ifXTable (<a href="./rfc2863">RFC 2863</a>), this object will |
| 739 |
point to the row in ifXTable that pertains to the entry. |
| 740 |
Otherwise, the value of this object will be zeroDotZero. |
| 741 |
" |
| 742 |
REFERENCE |
| 743 |
"<a href="./rfc2863#section-6">RFC 2863, Section 6</a>" |
| 744 |
DEFVAL { zeroDotZero } |
| 745 |
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } |
| 746 |
|
| 747 |
-- Conformance Information |
| 748 |
|
| 749 |
l2L3VpnMcastCompliances OBJECT IDENTIFIER |
| 750 |
::= { l2L3VpnMcastConformance 1 } |
| 751 |
l2L3VpnMcastGroups OBJECT IDENTIFIER |
| 752 |
::= { l2L3VpnMcastConformance 2 } |
| 753 |
|
| 754 |
-- Compliance Statements |
| 755 |
|
| 756 |
l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE |
| 757 |
STATUS current |
| 758 |
DESCRIPTION |
| 759 |
"The core compliance statement for SNMP entities |
| 760 |
that implement the L2L3-VPN-MULTICAST-MIB module. |
| 761 |
" |
| 762 |
MODULE -- this module |
| 763 |
|
| 764 |
MANDATORY-GROUPS { |
| 765 |
l2L3VpnMcastCoreGroup |
| 766 |
} |
| 767 |
::= { l2L3VpnMcastCompliances 1 } |
| 768 |
|
| 769 |
l2L3VpnMcastFullCompliance MODULE-COMPLIANCE |
| 770 |
STATUS current |
| 771 |
DESCRIPTION |
| 772 |
"The full compliance statement for SNMP entities |
| 773 |
that implement the L2L3-VPN-MULTICAST-MIB module. |
| 774 |
" |
| 775 |
MODULE -- this module |
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 783 |
|
| 784 |
|
| 785 |
MANDATORY-GROUPS { |
| 786 |
l2L3VpnMcastCoreGroup, |
| 787 |
l2L3VpnMcastOptionalGroup |
| 788 |
} |
| 789 |
::= { l2L3VpnMcastCompliances 2 } |
| 790 |
|
| 791 |
-- Units of Conformance |
| 792 |
|
| 793 |
l2L3VpnMcastCoreGroup OBJECT-GROUP |
| 794 |
OBJECTS { |
| 795 |
l2L3VpnMCastPmsiTunnelLeafInfoRequired, |
| 796 |
l2L3VpnMcastPmsiTunnelAttributeMplsLabel |
| 797 |
} |
| 798 |
STATUS current |
| 799 |
DESCRIPTION |
| 800 |
"Support of these objects is required. |
| 801 |
" |
| 802 |
::= { l2L3VpnMcastGroups 1 } |
| 803 |
|
| 804 |
l2L3VpnMcastOptionalGroup OBJECT-GROUP |
| 805 |
OBJECTS { |
| 806 |
l2L3VpnMcastPmsiTunnelPointer, |
| 807 |
l2L3VpnMcastPmsiTunnelIf |
| 808 |
} |
| 809 |
STATUS current |
| 810 |
DESCRIPTION |
| 811 |
"Support of these objects is optional. |
| 812 |
" |
| 813 |
::= { l2L3VpnMcastGroups 2 } |
| 814 |
|
| 815 |
END |
| 816 |
|
| 817 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 818 |
|
| 819 |
There are no management objects defined in these MIB modules that |
| 820 |
have a MAX-ACCESS clause of read-write and/or read-create. So, if |
| 821 |
this MIB module is implemented correctly, then there is no risk that |
| 822 |
an intruder can alter or create any management objects of this MIB |
| 823 |
module via direct SNMP SET operations. |
| 824 |
|
| 825 |
Some of the objects in these MIB modules may be considered sensitive |
| 826 |
or vulnerable in some network environments. This includes INDEX |
| 827 |
objects with a MAX-ACCESS of not-accessible, and any indices from |
| 828 |
other modules exposed via AUGMENTS. It is thus important to control |
| 829 |
even GET and/or NOTIFY access to these objects and possibly to even |
| 830 |
encrypt the values of these objects when sending them over the |
| 831 |
network via SNMP. These are the tables and objects and their |
| 832 |
sensitivity/vulnerability: |
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 839 |
|
| 840 |
|
| 841 |
o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the |
| 842 |
P-tunnel network topology and its performance characteristics. |
| 843 |
For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will |
| 844 |
contain the identifier that uniquely identifies a P-tunnel. This |
| 845 |
identifier may be composed of source and multicast group IP |
| 846 |
addresses. l2L3VpnMcastPmsiTunnelPointer and |
| 847 |
l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries |
| 848 |
in other tables containing configuration and/or performance |
| 849 |
information of a P-tunnel and its interface. If an Administrator |
| 850 |
does not want to reveal this information, then these objects |
| 851 |
should be considered sensitive/vulnerable. |
| 852 |
|
| 853 |
SNMP versions prior to SNMPv3 did not include adequate security. |
| 854 |
Even if the network itself is secure (for example by using IPsec), |
| 855 |
there is no control as to who on the secure network is allowed to |
| 856 |
access and GET/SET (read/change/create/delete) the objects in this |
| 857 |
MIB module. |
| 858 |
|
| 859 |
Implementations SHOULD provide the security features described by the |
| 860 |
SNMPv3 framework (see [<a href="./rfc3410" title=""Introduction and Applicability Statements for Internet- Standard Management Framework"">RFC3410</a>]), and implementations claiming |
| 861 |
compliance to the SNMPv3 standard MUST include full support for |
| 862 |
authentication and privacy via the User-based Security Model (USM) |
| 863 |
[<a href="./rfc3414" title=""User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)"">RFC3414</a>] with the AES cipher algorithm [<a href="./rfc3826" title=""The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model"">RFC3826</a>]. Implementations |
| 864 |
MAY also provide support for the Transport Security Model (TSM) |
| 865 |
[<a href="./rfc5591" title=""Transport Security Model for the Simple Network Management Protocol (SNMP)"">RFC5591</a>] in combination with a secure transport such as SSH |
| 866 |
[<a href="./rfc5592" title=""Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)"">RFC5592</a>] or TLS/DTLS [<a href="./rfc6353" title=""Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)"">RFC6353</a>]. |
| 867 |
|
| 868 |
Further, deployment of SNMP versions prior to SNMPv3 is NOT |
| 869 |
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to |
| 870 |
enable cryptographic security. It is then a customer/operator |
| 871 |
responsibility to ensure that the SNMP entity giving access to an |
| 872 |
instance of this MIB module is properly configured to give access to |
| 873 |
the objects only to those principals (users) that have legitimate |
| 874 |
rights to indeed GET or SET (change/create/delete) them. |
| 875 |
|
| 876 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 877 |
|
| 878 |
The MIB module in this document uses the following IANA-assigned |
| 879 |
OBJECT IDENTIFIER values recorded in the "SMI Network Management MGMT |
| 880 |
Codes Internet-standard MIB" registry: |
| 881 |
|
| 882 |
Name Description OBJECT-IDENTIFIER value |
| 883 |
----------------- -------------------------- ---------------------- |
| 884 |
l2L3VpnMcastTCMIB L2L3-VPN-MULTICAST-TC-MIB { mib-2 244 } |
| 885 |
l2L3VpnMcastMIB L2L3-VPN-MULTICAST-MIB { mib-2 245 } |
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span> |
| 898 |
|
| 899 |
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span> |
| 900 |
|
| 901 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 902 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, |
| 903 |
DOI 10.17487/RFC2119, March 1997, |
| 904 |
<<a href="https://www.rfc-editor.org/info/rfc2119">https://www.rfc-editor.org/info/rfc2119</a>>. |
| 905 |
|
| 906 |
[<a id="ref-RFC2578">RFC2578</a>] McCloghrie, K., Ed., Perkins, D., Ed., and |
| 907 |
J. Schoenwaelder, Ed., "Structure of Management |
| 908 |
Information Version 2 (SMIv2)", STD 58, <a href="./rfc2578">RFC 2578</a>, |
| 909 |
DOI 10.17487/RFC2578, April 1999, |
| 910 |
<<a href="https://www.rfc-editor.org/info/rfc2578">https://www.rfc-editor.org/info/rfc2578</a>>. |
| 911 |
|
| 912 |
[<a id="ref-RFC2579">RFC2579</a>] McCloghrie, K., Ed., Perkins, D., Ed., and |
| 913 |
J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", |
| 914 |
STD 58, <a href="./rfc2579">RFC 2579</a>, DOI 10.17487/RFC2579, April 1999, |
| 915 |
<<a href="https://www.rfc-editor.org/info/rfc2579">https://www.rfc-editor.org/info/rfc2579</a>>. |
| 916 |
|
| 917 |
[<a id="ref-RFC2580">RFC2580</a>] McCloghrie, K., Ed., Perkins, D., Ed., and |
| 918 |
J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", |
| 919 |
STD 58, <a href="./rfc2580">RFC 2580</a>, DOI 10.17487/RFC2580, April 1999, |
| 920 |
<<a href="https://www.rfc-editor.org/info/rfc2580">https://www.rfc-editor.org/info/rfc2580</a>>. |
| 921 |
|
| 922 |
[<a id="ref-RFC2863">RFC2863</a>] McCloghrie, K. and F. Kastenholz, "The Interfaces Group |
| 923 |
MIB", <a href="./rfc2863">RFC 2863</a>, DOI 10.17487/RFC2863, June 2000, |
| 924 |
<<a href="https://www.rfc-editor.org/info/rfc2863">https://www.rfc-editor.org/info/rfc2863</a>>. |
| 925 |
|
| 926 |
[<a id="ref-RFC3414">RFC3414</a>] Blumenthal, U. and B. Wijnen, "User-based Security Model |
| 927 |
(USM) for version 3 of the Simple Network Management |
| 928 |
Protocol (SNMPv3)", STD 62, <a href="./rfc3414">RFC 3414</a>, |
| 929 |
DOI 10.17487/RFC3414, December 2002, |
| 930 |
<<a href="https://www.rfc-editor.org/info/rfc3414">https://www.rfc-editor.org/info/rfc3414</a>>. |
| 931 |
|
| 932 |
[<a id="ref-RFC3811">RFC3811</a>] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of |
| 933 |
Textual Conventions (TCs) for Multiprotocol Label |
| 934 |
Switching (MPLS) Management", <a href="./rfc3811">RFC 3811</a>, |
| 935 |
DOI 10.17487/RFC3811, June 2004, |
| 936 |
<<a href="https://www.rfc-editor.org/info/rfc3811">https://www.rfc-editor.org/info/rfc3811</a>>. |
| 937 |
|
| 938 |
[<a id="ref-RFC3812">RFC3812</a>] Srinivasan, C., Viswanathan, A., and T. Nadeau, |
| 939 |
"Multiprotocol Label Switching (MPLS) Traffic Engineering |
| 940 |
(TE) Management Information Base (MIB)", <a href="./rfc3812">RFC 3812</a>, |
| 941 |
DOI 10.17487/RFC3812, June 2004, |
| 942 |
<<a href="https://www.rfc-editor.org/info/rfc3812">https://www.rfc-editor.org/info/rfc3812</a>>. |
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 951 |
|
| 952 |
|
| 953 |
[<a id="ref-RFC3826">RFC3826</a>] Blumenthal, U., Maino, F., and K. McCloghrie, "The |
| 954 |
Advanced Encryption Standard (AES) Cipher Algorithm in the |
| 955 |
SNMP User-based Security Model", <a href="./rfc3826">RFC 3826</a>, |
| 956 |
DOI 10.17487/RFC3826, June 2004, |
| 957 |
<<a href="https://www.rfc-editor.org/info/rfc3826">https://www.rfc-editor.org/info/rfc3826</a>>. |
| 958 |
|
| 959 |
[<a id="ref-RFC4875">RFC4875</a>] Aggarwal, R., Ed., Papadimitriou, D., Ed., and |
| 960 |
S. Yasukawa, Ed., "Extensions to Resource Reservation |
| 961 |
Protocol - Traffic Engineering (RSVP-TE) for Point-to- |
| 962 |
Multipoint TE Label Switched Paths (LSPs)", <a href="./rfc4875">RFC 4875</a>, |
| 963 |
DOI 10.17487/RFC4875, May 2007, |
| 964 |
<<a href="https://www.rfc-editor.org/info/rfc4875">https://www.rfc-editor.org/info/rfc4875</a>>. |
| 965 |
|
| 966 |
[<a id="ref-RFC5015">RFC5015</a>] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, |
| 967 |
"Bidirectional Protocol Independent Multicast (BIDIR- |
| 968 |
PIM)", <a href="./rfc5015">RFC 5015</a>, DOI 10.17487/RFC5015, October 2007, |
| 969 |
<<a href="https://www.rfc-editor.org/info/rfc5015">https://www.rfc-editor.org/info/rfc5015</a>>. |
| 970 |
|
| 971 |
[<a id="ref-RFC5591">RFC5591</a>] Harrington, D. and W. Hardaker, "Transport Security Model |
| 972 |
for the Simple Network Management Protocol (SNMP)", |
| 973 |
STD 78, <a href="./rfc5591">RFC 5591</a>, DOI 10.17487/RFC5591, June 2009, |
| 974 |
<<a href="https://www.rfc-editor.org/info/rfc5591">https://www.rfc-editor.org/info/rfc5591</a>>. |
| 975 |
|
| 976 |
[<a id="ref-RFC5592">RFC5592</a>] Harrington, D., Salowey, J., and W. Hardaker, "Secure |
| 977 |
Shell Transport Model for the Simple Network Management |
| 978 |
Protocol (SNMP)", <a href="./rfc5592">RFC 5592</a>, DOI 10.17487/RFC5592, June |
| 979 |
2009, <<a href="https://www.rfc-editor.org/info/rfc5592">https://www.rfc-editor.org/info/rfc5592</a>>. |
| 980 |
|
| 981 |
[<a id="ref-RFC6353">RFC6353</a>] Hardaker, W., "Transport Layer Security (TLS) Transport |
| 982 |
Model for the Simple Network Management Protocol (SNMP)", |
| 983 |
STD 78, <a href="./rfc6353">RFC 6353</a>, DOI 10.17487/RFC6353, July 2011, |
| 984 |
<<a href="https://www.rfc-editor.org/info/rfc6353">https://www.rfc-editor.org/info/rfc6353</a>>. |
| 985 |
|
| 986 |
[<a id="ref-RFC6388">RFC6388</a>] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and |
| 987 |
B. Thomas, "Label Distribution Protocol Extensions for |
| 988 |
Point- to-Multipoint and Multipoint-to-Multipoint Label |
| 989 |
Switched Paths", <a href="./rfc6388">RFC 6388</a>, DOI 10.17487/RFC6388, November |
| 990 |
2011, <<a href="https://www.rfc-editor.org/info/rfc6388">https://www.rfc-editor.org/info/rfc6388</a>>. |
| 991 |
|
| 992 |
[<a id="ref-RFC6513">RFC6513</a>] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ |
| 993 |
BGP IP VPNs", <a href="./rfc6513">RFC 6513</a>, DOI 10.17487/RFC6513, February |
| 994 |
2012, <<a href="https://www.rfc-editor.org/info/rfc6513">https://www.rfc-editor.org/info/rfc6513</a>>. |
| 995 |
|
| 996 |
[<a id="ref-RFC6514">RFC6514</a>] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP |
| 997 |
Encodings and Procedures for Multicast in MPLS/BGP IP |
| 998 |
VPNs", <a href="./rfc6514">RFC 6514</a>, DOI 10.17487/RFC6514, February 2012, |
| 999 |
<<a href="https://www.rfc-editor.org/info/rfc6514">https://www.rfc-editor.org/info/rfc6514</a>>. |
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
[<a id="ref-RFC7117">RFC7117</a>] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and |
| 1010 |
C. Kodeboniya, "Multicast in Virtual Private LAN Service |
| 1011 |
(VPLS)", <a href="./rfc7117">RFC 7117</a>, DOI 10.17487/RFC7117, February 2014, |
| 1012 |
<<a href="https://www.rfc-editor.org/info/rfc7117">https://www.rfc-editor.org/info/rfc7117</a>>. |
| 1013 |
|
| 1014 |
[<a id="ref-RFC7524">RFC7524</a>] Rekhter, Y., Rosen, E., Aggarwal, R., Morin, T., |
| 1015 |
Grosclaude, I., Leymann, N., and S. Saad, "Inter-Area |
| 1016 |
Point-to-Multipoint (P2MP) Segmented Label Switched Paths |
| 1017 |
(LSPs)", <a href="./rfc7524">RFC 7524</a>, DOI 10.17487/RFC7524, May 2015, |
| 1018 |
<<a href="https://www.rfc-editor.org/info/rfc7524">https://www.rfc-editor.org/info/rfc7524</a>>. |
| 1019 |
|
| 1020 |
[<a id="ref-RFC7761">RFC7761</a>] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., |
| 1021 |
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent |
| 1022 |
Multicast - Sparse Mode (PIM-SM): Protocol Specification |
| 1023 |
(Revised)", STD 83, <a href="./rfc7761">RFC 7761</a>, DOI 10.17487/RFC7761, March |
| 1024 |
2016, <<a href="https://www.rfc-editor.org/info/rfc7761">https://www.rfc-editor.org/info/rfc7761</a>>. |
| 1025 |
|
| 1026 |
[<a id="ref-RFC8174">RFC8174</a>] Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a> |
| 1027 |
<a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174, |
| 1028 |
May 2017, <<a href="https://www.rfc-editor.org/info/rfc8174">https://www.rfc-editor.org/info/rfc8174</a>>. |
| 1029 |
|
| 1030 |
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span> |
| 1031 |
|
| 1032 |
[<a id="ref-RFC3410">RFC3410</a>] Case, J., Mundy, R., Partain, D., and B. Stewart, |
| 1033 |
"Introduction and Applicability Statements for Internet- |
| 1034 |
Standard Management Framework", <a href="./rfc3410">RFC 3410</a>, |
| 1035 |
DOI 10.17487/RFC3410, December 2002, |
| 1036 |
<<a href="https://www.rfc-editor.org/info/rfc3410">https://www.rfc-editor.org/info/rfc3410</a>>. |
| 1037 |
|
| 1038 |
|
| 1039 |
|
| 1040 |
|
| 1041 |
|
| 1042 |
|
| 1043 |
|
| 1044 |
|
| 1045 |
|
| 1046 |
|
| 1047 |
|
| 1048 |
|
| 1049 |
|
| 1050 |
|
| 1051 |
|
| 1052 |
|
| 1053 |
|
| 1054 |
|
| 1055 |
|
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Zhang & Tsunoda Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc8502">RFC 8502</a> L2L3-VPN-MCAST MIB December 2018</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
Acknowledgements |
| 1066 |
|
| 1067 |
Glenn Mansfield Keeni did the MIB Doctor review and provided valuable |
| 1068 |
comments. |
| 1069 |
|
| 1070 |
Authors' Addresses |
| 1071 |
|
| 1072 |
Zhaohui (Jeffrey) Zhang |
| 1073 |
Juniper Networks, Inc. |
| 1074 |
10 Technology Park Drive |
| 1075 |
Westford, MA 01886 |
| 1076 |
United States of America |
| 1077 |
|
| 1078 |
Email: [email protected] |
| 1079 |
|
| 1080 |
|
| 1081 |
Hiroshi Tsunoda |
| 1082 |
Tohoku Institute of Technology |
| 1083 |
35-1, Yagiyama Kasumi-cho |
| 1084 |
Taihaku-ku, Sendai 982-8577 |
| 1085 |
Japan |
| 1086 |
|
| 1087 |
Phone: +81-22-305-3411 |
| 1088 |
Email: [email protected] |
| 1089 |
|
| 1090 |
|
| 1091 |
|
| 1092 |
|
| 1093 |
|
| 1094 |
|
| 1095 |
|
| 1096 |
|
| 1097 |
|
| 1098 |
|
| 1099 |
|
| 1100 |
|
| 1101 |
|
| 1102 |
|
| 1103 |
|
| 1104 |
|
| 1105 |
|
| 1106 |
|
| 1107 |
|
| 1108 |
|
| 1109 |
|
| 1110 |
|
| 1111 |
|
| 1112 |
|
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
Zhang & Tsunoda Standards Track [Page 20] |
| 1117 |
</pre> |