draft-ietf-bess-l2l3-vpn-mcast-mib-16.txt   rfc8502.txt 
Network Working Group Z. Zhang Internet Engineering Task Force (IETF) Z. Zhang
Internet-Draft Juniper Networks, Inc. Request for Comments: 8502 Juniper Networks, Inc.
Intended status: Standards Track H. Tsunoda Category: Standards Track H. Tsunoda
Expires: March 11, 2019 Tohoku Institute of Technology ISSN: 2070-1721 Tohoku Institute of Technology
September 07, 2018 December 2018
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-16
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes two MIB modules which will be used by In particular, it describes two MIB modules that will be used by
other MIB modules for monitoring and/or configuring Layer 2 and Layer other MIB modules for monitoring and/or configuring Layer 2 and Layer
3 Virtual Private Networks that support multicast. 3 Virtual Private Networks that support multicast.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on March 11, 2019. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8502.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . 4 2. The Internet-Standard Management Framework . . . . . . . . . 4
3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4 3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. L2L3-VPN-MULTICAST-TC-MIB Object Definitions . . . . . . 4 4.1. L2L3-VPN-MULTICAST-TC-MIB Object Definitions . . . . . . 4
4.2. L2L3-VPN-MULTICAST-MIB Object Definitions . . . . . . . . 9 4.2. L2L3-VPN-MULTICAST-MIB Object Definitions . . . . . . . . 9
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 17 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 7.1. Normative References . . . . . . . . . . . . . . . . . . 17
8.1. Normative References . . . . . . . . . . . . . . . . . . 17 7.2. Informative References . . . . . . . . . . . . . . . . . 19
8.2. Informative References . . . . . . . . . . . . . . . . . 19 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
In BGP/MPLS Virtual Private Networks (VPNs), Border Gateway Protocol In BGP/MPLS Virtual Private Networks (VPNs), the Border Gateway
(BGP) is used for distributing routes and MultiProtocol Label Protocol (BGP) is used for distributing routes and Multiprotocol
Switching (MPLS) is used for forwarding packets across service Label Switching (MPLS) is used for forwarding packets across service
provider networks. provider networks.
The procedures for supporting multicast in BGP/MPLS Layer 3 (L3) VPN The procedures for supporting multicast in a BGP/MPLS Layer 3 (L3)
are specified in [RFC6513]. The procedures for supporting multicast VPN are specified in [RFC6513]. The procedures for supporting
in BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117]. Throughout multicast in a BGP/MPLS Layer 2 (L2) VPN are specified in [RFC7117].
this document, we will use the term "L2L3VpnMCast network" to mean Throughout this document, we will use the term "L2L3VpnMCast network"
BGP/MPLS L2 and L3 VPN that support multicast. to mean a BGP/MPLS L2 and L3 VPN that supports multicast.
L2L3VpnMCast networks use various transport mechanisms for forwarding L2L3VpnMCast networks use various transport mechanisms for forwarding
a packet to all or a subset of Provider Edge routers (PEs) across a packet to all or a subset of Provider Edge (PE) routers across
service provider networks. These transport mechanisms are abstracted service provider networks. These transport mechanisms are abstracted
as provider tunnels (P-tunnels). The type of a P-tunnel indicates as provider tunnels (P-tunnels). The type of P-tunnel indicates the
the type of the tunneling technology used to establish the P-tunnel. type of tunneling technology used to establish the P-tunnel. The
The syntax and semantics of a Tunnel identifier is determined by the syntax and semantics of a Tunnel Identifier are determined by the
corresponding P-tunnel type [RFC6514]. P-tunnel type and P-tunnel corresponding P-tunnel type [RFC6514]. The P-tunnel type and
identifier together identify a P-tunnel. P-tunnel identifier together identify a P-tunnel.
A BGP attribute that specifies information of a P-tunnel is called A BGP attribute that specifies information of a P-tunnel is called a
Provider Multicast Service Interface (PMSI) tunnel attribute. The Provider Multicast Service Interface (PMSI) Tunnel attribute. The
PMSI tunnel attribute is advertised/received by PEs in BGP auto- PMSI Tunnel attribute is advertised/received by PEs in BGP auto-
discovery (A-D) routes. [RFC6514] defines the format of a PMSI discovery (A-D) routes. [RFC6514] defines the format of a PMSI
tunnel attribute. P-tunnel type and the P-tunnel identifier are Tunnel attribute. The P-tunnel type and the P-tunnel identifier are
included in the corresponding PMSI tunnel attribute. included in the corresponding PMSI Tunnel attribute.
This document describes textual conventions (TCs) and common managed This document describes textual conventions (TCs) and common managed
objects (MOs) which will be used by other Management Information Base objects (MOs) that will be used by other Management Information Base
(MIB) modules for monitoring and/or configuring L2L3VpnMCast (MIB) modules for monitoring and/or configuring L2L3VpnMCast
networks. networks.
This document defines two TCs to represent This document defines two TCs to represent
(a) the type of a P-tunnel and (a) the type of a P-tunnel and
(b) the identifier of a P-tunnel (b) the identifier of a P-tunnel
respectively.
The document also defines MOs that will provide the information The document also defines MOs that will provide the information
contained in a PMSI tunnel attribute and corresponding P-tunnel contained in a PMSI Tunnel attribute and corresponding P-tunnel.
information.
1.1. Terminology 1.1. Terminology
This document adopts the definitions, acronyms and mechanisms This document adopts the definitions, acronyms, and mechanisms
described in [RFC6513] [RFC6514] [RFC7117] and other documents that described in [RFC6513] [RFC6514] [RFC7117] and other documents that
they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN, they refer to. Familiarity with multicast, MPLS, Layer 3 VPN, and
Multicast VPN concepts and/or mechanisms is assumed. Some terms Multicast VPN concepts and/or mechanisms is assumed. Some terms
specifically related to this document are explained below. specifically related to this document are explained below.
"Provider Multicast Service Interface (PMSI)" [RFC6513] is a PMSI [RFC6513] is a conceptual interface instantiated by a P-tunnel,
conceptual interface instantiated by a P-tunnel, a transport which is a transport mechanism used to deliver multicast traffic. A
mechanism used to deliver multicast traffic. A PE uses it to send PE uses it to send customer multicast traffic to all or some PEs in
customer multicast traffic to all or some PEs in the same VPN. the same VPN.
There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and There are two kinds of PMSIs: Inclusive PMSI (I-PMSI) and Selective
"Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that PMSI (S-PMSI) [RFC6513]. An I-PMSI is a PMSI that enables a PE
enables a PE attached to a particular Multicast VPN to transmit a attached to a particular Multicast VPN to transmit a message to all
message to all PEs in the same VPN. An S-PMSI is a PMSI that enables PEs in the same VPN. An S-PMSI is a PMSI that enables a PE attached
a PE attached to a particular Multicast VPN to transmit a message to to a particular Multicast VPN to transmit a message to some of the
some of the PEs in the same VPN. PEs in the same VPN.
Throughout this document, we will use the term "PMSI" to refer both Throughout this document, we will use the term "PMSI" to refer to
"I-PMSI" and "S-PMSI." both "I-PMSI" and "S-PMSI".
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in
14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
skipping to change at page 4, line 25 skipping to change at page 4, line 25
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Summary of MIB Modules 3. Summary of MIB Modules
This document defines two MIB modules: L2L3-VPN-MULTICAST-TC-MIB and This document defines two MIB modules: L2L3-VPN-MULTICAST-TC-MIB and
L2L3-VPN-MULTICAST-MIB. L2L3-VPN-MULTICAST-MIB.
o L2L3-VPN-MULTICAST-TC-MIB contains two Textual Conventions: o L2L3-VPN-MULTICAST-TC-MIB contains two textual conventions:
L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId. L2L3VpnMcastProviderTunnelType and L2L3VpnMcastProviderTunnelId.
L2L3VpnMcastProviderTunnelType provides an enumeration of the L2L3VpnMcastProviderTunnelType provides an enumeration of the
P-tunnel types. L2L3VpnMcastProviderTunnelId represents an P-tunnel types. L2L3VpnMcastProviderTunnelId represents an
identifier of a P-tunnel. identifier of a P-tunnel.
o L2L3-VPN-MULTICAST-MIB defines a table o L2L3-VPN-MULTICAST-MIB defines the following table:
l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table
corresponds to the attribute information of a specific P-tunnel on corresponds to the attribute information of a specific P-tunnel on
a PE router. Entries in this table will be used by other MIB a PE router. Entries in this table will be used by other MIB
modules for monitoring and/or configuring L2L3VpnMCast network. modules for monitoring and/or configuring an L2L3VpnMCast network.
The table index uniquely identifies a P-tunnel. It is composed of The table index uniquely identifies a P-tunnel. It is composed of
a type and identifier of a P-tunnel. The table may also be used a type and identifier of a P-tunnel. The table may also be used
in conjunction with other MIBs, such as MPLS Traffic Engineering in conjunction with other MIBs, such as the MPLS Traffic
MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further information Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further
about a P-tunnel. It may also be used in conjunction with the information about a P-tunnel. It may also be used in conjunction
Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further with the Interfaces Group MIB (IF-MIB) [RFC2863] to obtain further
information about the interface corresponding to a P-tunnel. information about the interface corresponding to a P-tunnel.
4. Definitions 4. Definitions
4.1. L2L3-VPN-MULTICAST-TC-MIB Object Definitions 4.1. L2L3-VPN-MULTICAST-TC-MIB Object Definitions
L2L3-VPN-MULTICAST-TC-MIB DEFINITIONS ::= BEGIN This MIB module makes reference to the following documents:
[RFC4875], [RFC5015], [RFC6388], [RFC7524], and [RFC7761].
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION L2L3-VPN-MULTICAST-TC-MIB DEFINITIONS ::= BEGIN
FROM SNMPv2-TC; -- [RFC2579]
l2L3VpnMcastTCMIB MODULE-IDENTITY IMPORTS
LAST-UPDATED "201809071200Z" -- 7th September, 2018 MODULE-IDENTITY, mib-2
ORGANIZATION "IETF BESS Working Group." FROM SNMPv2-SMI -- RFC 2578
CONTACT-INFO
" Zhaohui Zhang
Juniper Networks, Inc.
10 Technology Park Drive
Westford, MA 01886
USA
Email: zzhang@juniper.net
Hiroshi Tsunoda TEXTUAL-CONVENTION
Tohoku Institute of Technology FROM SNMPv2-TC; -- RFC 2579
35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577
Japan
Email: tsuno@m.ieice.org
Comments and discussion to bess@ietf.org l2L3VpnMcastTCMIB MODULE-IDENTITY
" LAST-UPDATED "201812140000Z" -- 14 December 2018
DESCRIPTION ORGANIZATION "IETF BESS Working Group"
"This MIB module specifies textual conventions for CONTACT-INFO
Border Gateway Protocol/MultiProtocol Label "Zhaohui Zhang
Switching Layer 2 and Layer 3 Virtual Private Networks Juniper Networks, Inc.
that support multicast (L2L3VpnMCast networks). 10 Technology Park Drive
Westford, MA 01886
United States of America
Email: zzhang@juniper.net
Copyright (C) The Internet Society (2018). Hiroshi Tsunoda
" Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577
Japan
Email: tsuno@m.ieice.org"
-- Revision history. DESCRIPTION
"This MIB module specifies textual conventions for
Border Gateway Protocol/Multiprotocol Label
Switching Layer 2 and Layer 3 Virtual Private Networks
that support multicast (L2L3VpnMCast networks).
REVISION "201809071200Z" -- 7th September, 2018 Copyright (c) 2018 IETF Trust and the persons identified
DESCRIPTION as authors of the code. All rights reserved.
"Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this note Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD
License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info).
"
::= { mib-2 AAAA } -- Revision History
-- IANA Reg.: Please assign a value for "AAAA" under the REVISION "201812140000Z" -- 14 December 2018
-- 'mib-2' subtree and record the assignment in the SMI DESCRIPTION
-- Numbers registry. "Initial version, published as RFC 8502."
-- RFC Ed.: When the above assignment has been made, please ::= { mib-2 244 }
-- remove the above note
-- replace "AAAA" here with the assigned value and
-- remove this note.
-- Textual convention -- Textual Convention
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention enumerates values "This textual convention enumerates values
representing the type of a provider tunnel (P-tunnel) representing the type of a provider tunnel (P-tunnel)
used for L2L3VpnMCast networks. used for L2L3VpnMCast networks.
These labeled numbers are aligned with the definition These labeled numbers are aligned with the definition
of Tunnel types in Section 5 of [RFC6514] and of Tunnel Types in Section 5 of RFC 6514 and
Section 14.1 of [RFC7524]. Section 14.1 of RFC 7524.
The enumerated values and the corresponding P-tunnel types The enumerated values and the corresponding P-tunnel types
are as follows: are as follows:
noTunnelInfo (0) : no tunnel information present noTunnelInfo (0) : No tunnel information RFC 6514
[RFC6514] rsvpP2mp (1) : RSVP-TE P2MP LSP RFC 4875
rsvpP2mp (1) : RSVP-TE P2MP LSP [RFC4875] ldpP2mp (2) : mLDP P2MP LSP RFC 6388
ldpP2mp (2) : mLDP P2MP LSP [RFC6388] pimSsm (3) : PIM-SSM Tree RFC 7761
pimSsm (3) : PIM-SSM Tree [RFC7761] pimAsm (4) : PIM-SM Tree RFC 7761
pimAsm (4) : PIM-SM Tree [RFC7761] pimBidir (5) : BIDIR-PIM Tree RFC 5015
pimBidir (5) : BIDIR-PIM Tree [RFC5015] ingressReplication (6) : Ingress Replication RFC 6513
ingressReplication (6) : Ingress Replication [RFC6513] ldpMp2mp (7) : mLDP MP2MP LSP RFC 6388
ldpMp2mp (7) : mLDP MP2MP LSP [RFC6388] transportTunnel (8) : Transport Tunnel RFC 7524
transportTunnel (8) : Transport Tunnel [RFC7524]
These numbers are registered at IANA. These numbers are registered at IANA.
A current list of assignments can be found at A current list of assignments can be found at
<https://www.iana.org/assignments/bgp-parameters/ <https://www.iana.org/assignments/bgp-parameters/>.
bgp-parameters.xhtml#pmsi-tunnel-types>. "
" REFERENCE
REFERENCE "RFC 4875
"RFC4875 RFC 5015
RFC5015 RFC 6388
RFC6388 RFC 6513
RFC6513 RFC 6514, Section 5
RFC6514, Section 5 RFC 7524, Section 14.1
RFC7524, Section 14.1 RFC 7761
RFC7761 "
"
SYNTAX INTEGER SYNTAX INTEGER
{ {
noTunnelInfo (0), noTunnelInfo (0),
rsvpP2mp (1), rsvpP2mp (1),
ldpP2mp (2), ldpP2mp (2),
pimSsm (3), pimSsm (3),
pimAsm (4), pimAsm (4),
pimBidir (5), pimBidir (5),
ingressReplication (6), ingressReplication (6),
ldpMp2mp (7), ldpMp2mp (7),
transportTunnel (8) transportTunnel (8)
} }
L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention represents the tunnel identifier "This textual convention represents the Tunnel Identifier
of a P-tunnel. of a P-tunnel.
The size of the identifier depends on the address family The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of the corresponding (IPv4 or IPv6) and the value of the corresponding
L2L3VpnMcastProviderTunnelType object. L2L3VpnMcastProviderTunnelType object.
The corresponding L2L3VpnMcastProviderTunnelType object The corresponding L2L3VpnMcastProviderTunnelType object
represents the type of the tunneling technology used represents the type of tunneling technology used
to establish the P-tunnel. to establish the P-tunnel.
The size of the identifier for each tunneling technology The size of the identifier for each tunneling technology
is summarized below. is summarized below.
L2L3VpnMcastProviderTunnelType Size (in octets) L2L3VpnMcastProviderTunnelType Size (in octets)
(tunneling technology) IPv4 IPv6 (tunneling technology) IPv4 IPv6
----------------------------------------------------------- -----------------------------------------------------------
noTunnelInfo (No tunnel information) 0 0 noTunnelInfo (No tunnel information) 0 0
rsvpP2mp (RSVP-TE P2MP LSP) 12 24 rsvpP2mp (RSVP-TE P2MP LSP) 12 24
ldpP2mp (mLDP P2MP LSP) 17 29 ldpP2mp (mLDP P2MP LSP) 17 29
pimSsm (PIM-SSM Tree) 8 32 pimSsm (PIM-SSM Tree) 8 32
pimAsm (PIM-SM Tree) 8 32 pimAsm (PIM-SM Tree) 8 32
pimBidir (BIDIR-PIM Tree) 8 32 pimBidir (BIDIR-PIM Tree) 8 32
ingressReplication (Ingress Replication) 4 16 ingressReplication (Ingress Replication) 4 16
ldpMp2mp (mLDP MP2MP LSP) 17 29 ldpMp2mp (mLDP MP2MP LSP) 17 29
transportTunnel (Transport Tunnel) 8 32 transportTunnel (Transport Tunnel) 8 32
Tunnel type is set to 'No tunnel information present' The Tunnel Type is set to 'No tunnel information'
when the PMSI Tunnel attribute carries no tunnel when the PMSI Tunnel attribute carries no tunnel
information (there is no Tunnel Identifier). information (there is no Tunnel Identifier).
The value of the corresponding L2L3VpnMcastProviderTunnelId The value of the corresponding L2L3VpnMcastProviderTunnelId
object will be a string of length zero. object will be a string of length zero.
For tunnel type rsvpP2mp(1), the corresponding Tunnel For Tunnel Type rsvpP2mp(1), the corresponding Tunnel
Identifier is composed of Extended Tunnel ID (4 octets in IPv4, Identifier is composed of an Extended Tunnel ID (4 octets in
16 octets in IPv6), Reserved (2 octets), Tunnel ID (2 octets), IPv4, 16 octets in IPv6), 2 unused (Reserved) octets that of
and P2MP ID (4 octets). value zero, a Tunnel ID (2 octets), and a Point-to-Multipoint
The size of the corresponding L2L3VpnMcastProviderTunnelId (P2MP) ID (4 octets). The size of the corresponding
object will be 12 octets in IPv4 and 24 octets in IPv6. L2L3VpnMcastProviderTunnelId object will be 12 octets in IPv4
and 24 octets in IPv6.
For tunnel type ldpP2mp(2), the corresponding Tunnel Identifier For Tunnel Type ldpP2mp(2), the corresponding Tunnel
is the P2MP Forwarding Equivalence Class (FEC) Element Identifier is the P2MP Forwarding Equivalence Class (FEC)
[RFC6388]. The size of the corresponding Element (RFC 6388). The size of the corresponding
L2L3VpnMcastProviderTunnelId object will be 17 octets L2L3VpnMcastProviderTunnelId object will be 17 octets
in IPv4 and 29 octets in IPv6. in IPv4 and 29 octets in IPv6.
For tunnel type pimSsm(3), PimAsm(4), and PimBidir(5), the For Tunnel Types pimSsm(3), PimAsm(4), and PimBidir(5), the
corresponding Tunnel Identifier is composed of the source IP corresponding Tunnel Identifier is composed of the source IP
address and the group IP address. address and the group IP address.
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 8 octets in IPv4 and 32 octets in IPv6. object will be 8 octets in IPv4 and 32 octets in IPv6.
For tunnel type ingressReplication(6), the Tunnel Identifier is For Tunnel Type ingressReplication(6), the Tunnel Identifier
the unicast tunnel endpoint IP address of the local PE. is the unicast tunnel endpoint IP address of the local PE.
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 4 octets in IPv4 and 16 octets in IPv6. object will be 4 octets in IPv4 and 16 octets in IPv6.
For tunnel type ldpMp2mp(7), the Tunnel Identifier is For Tunnel Type ldpMp2mp(7), the Tunnel Identifier is
MP2MP FEC Element [RFC6388]. a Multipoint-to-Multipoint (MP2MP) FEC Element (RFC 6388).
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 17 octets in IPv4 and 29 octets in IPv6. object will be 17 octets in IPv4 and 29 octets in IPv6.
For tunnel type transportTunnel(8), the Tunnel Identifier For Tunnel Type transportTunnel(8), the Tunnel Identifier
is a tuple of Source PE Address and Local Number, is a tuple of Source PE Address and Local Number,
which is a number that is unique to the Source PE [RFC7524]. which is a number that is unique to the Source PE (RFC 7524).
Both Source PE Address and Local Number are 4 octets in IPv4 Both Source PE Address and Local Number are 4 octets in IPv4
and 16 octets in IPv6. and 16 octets in IPv6.
The size of the corresponding L2L3VpnMcastProviderTunnelId The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 8 octets in IPv4 and 32 octets in IPv6. object will be 8 octets in IPv4 and 32 octets in IPv6.
" "
REFERENCE REFERENCE
"RFC6514, Section 5 "RFC 6514, Section 5
RFC4875, Section 19.1 RFC 4875, Section 19.1
RFC6388, Section 2.2 and 3.2 RFC 6388, Sections 2.2 and 3.2
RFC7524, Section 14.1 RFC 7524, Section 14.1
" "
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
END END
4.2. L2L3-VPN-MULTICAST-MIB Object Definitions 4.2. L2L3-VPN-MULTICAST-MIB Object Definitions
This MIB module makes reference to the following documents:
[RFC3811].
L2L3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- RFC 2580
RowPointer RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- RFC 2579
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- RFC 3811
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
L2L3VpnMcastProviderTunnelId L2L3VpnMcastProviderTunnelId
FROM L2L3-VPN-MULTICAST-TC-MIB; -- [RFCXXXX] FROM L2L3-VPN-MULTICAST-TC-MIB; -- RFC 8502
-- RFC Ed.: replace XXXX with actual RFC number and remove this note
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201809071200Z" -- 7th September, 2018 LAST-UPDATED "201812140000Z" -- 14 December 2018
ORGANIZATION "IETF BESS Working Group." ORGANIZATION "IETF BESS Working Group"
CONTACT-INFO CONTACT-INFO
" Zhaohui Zhang "Zhaohui Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA United States of America
Email: zzhang@juniper.net Email: zzhang@juniper.net
Hiroshi Tsunoda Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho 35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577 Taihaku-ku, Sendai, 982-8577
Japan Japan
Email: tsuno@m.ieice.org Email: tsuno@m.ieice.org"
Comments and discussion to bess@ietf.org
"
DESCRIPTION DESCRIPTION
"This MIB module defines a table representing the attribute "This MIB module defines a table representing the attribute
information of the provider tunnels (P-tunnels) on a PE router. information of the provider tunnels (P-tunnels) on a PE router.
This MIB module will be used by other MIB modules designed for This MIB module will be used by other MIB modules designed for
monitoring and/or configuring Border Gateway monitoring and/or configuring Border Gateway
Protocol/MultiProtocol Label Switching Protocol/Multiprotocol Label Switching
Layer 2 and Layer 3 Virtual Private Layer 2 and Layer 3 Virtual Private
Network that support multicast (L2L3VpnMCast network). Network that support multicast (L2L3VpnMCast network).
Copyright (C) The Internet Society (2018).
"
-- Revision history.
REVISION "201809071200Z" -- 7th September, 2018 Copyright (c) 2018 IETF Trust and the persons identified
DESCRIPTION as authors of the code. All rights reserved.
"Initial version, published as RFC XXXX."
-- RFC Ed.: replace XXXX with actual RFC number and remove this note Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info).
"
::= { mib-2 BBBB } -- Revision History
-- IANA Reg.: Please assign a value for "BBBB" under the REVISION "201812140000Z" -- 14 December 2018
-- 'mib-2' subtree and record the assignment in the SMI DESCRIPTION
-- Numbers registry. "Initial version, published as RFC 8502."
-- RFC Ed.: When the above assignment has been made, please ::= { mib-2 245 }
-- remove the above note
-- replace "BBBB" here with the assigned value and
-- remove this note.
-- Top level components of this MIB. -- Top-level components of this MIB.
l2L3VpnMcastStates OBJECT IDENTIFIER l2L3VpnMcastStates OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 1 } ::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastConformance OBJECT IDENTIFIER l2L3VpnMcastConformance OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 2 } ::= { l2L3VpnMcastMIB 2 }
-- tables, scalars, conformance information -- Tables, Scalars, Conformance Information
-- Table of PMSI Tunnel Attributes -- Table of PMSI Tunnel Attributes
l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE
SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table corresponds to "An entry in this table corresponds to
the attribute information of a specific the attribute information of a specific
P-tunnel on a PE router. P-tunnel on a PE router.
A part of attributes correspond to fields in A part of the attributes corresponds to fields in
a Provider Multicast Service Interface (PMSI) Tunnel a Provider Multicast Service Interface (PMSI) Tunnel
attribute advertised and received by a PE router. attribute advertised and received by a PE router.
The entries will be referred to by other MIB modules The entries will be referred to by other MIB modules
for monitoring and/or configuring L2L3VpnMCast networks. for monitoring and/or configuring L2L3VpnMCast networks.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC 6514, Section 5"
::= { l2L3VpnMcastStates 1 } ::= { l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row corresponding to a specific "A conceptual row corresponding to a specific
P-tunnel on this router. P-tunnel on this router.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC 6514, Section 5"
INDEX { INDEX {
l2L3VpnMcastPmsiTunnelAttributeType, l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
} }
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::= L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE { SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeType l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
skipping to change at page 12, line 7 skipping to change at page 11, line 46
RowPointer, RowPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
RowPointer RowPointer
} }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the type of the tunneling technology "This object indicates the type of tunneling technology
used to establish the P-tunnel corresponding to this entry. used to establish the P-tunnel corresponding to this entry.
When BGP-based PMSI signaling is used, the value of When BGP-based PMSI signaling is used, the value of
this object corresponds to the Tunnel Type field this object corresponds to the Tunnel Type field
in the PMSI Tunnel attribute advertised/received in the PMSI Tunnel attribute advertised/received
in a PMSI auto-discovery (A-D) route. in a PMSI auto-discovery (A-D) route.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC 6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelId SYNTAX L2L3VpnMcastProviderTunnelId
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the Tunnel Identifier field, which "This object represents the Tunnel Identifier field, which
uniquely identifies a P-tunnel, in the PMSI Tunnel attribute uniquely identifies a P-tunnel, in the PMSI Tunnel attribute
of the P-tunnel corresponding to this entry. of the P-tunnel corresponding to this entry.
The size of the identifier depends on the address family The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of the corresponding (IPv4 or IPv6) and the value of the corresponding
l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of l2L3VpnMcastPmsiTunnelAttributeType object, i.e., the type of
the tunneling technology used to establish the P-tunnel. tunneling technology used to establish the P-tunnel.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC 6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE l2L3VpnMCastPmsiTunnelLeafInfoRequired OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
false (0), false (0),
true (1), true (1),
notAvailable (2) notAvailable (2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When the value of this object is set to 1 (true), "When the value of this object is set to 1 (true),
it indicates that the PE which originated the it indicates that the PE that originated the
PMSI Tunnel attribute of the P-tunnel corresponding PMSI Tunnel attribute of the P-tunnel corresponding
to this entry requests receivers to originate to this entry requests receivers to originate
a new Leaf A-D (Auto-Discovery) route. a new Leaf A-D route.
A value of 0 (false) indicates that there is no such A value of zero (false) indicates that there is no such
request. request.
When the P-tunnel does not have a corresponding PMSI When the P-tunnel does not have a corresponding PMSI
tunnel attribute, the value of this object will be Tunnel attribute, the value of this object will be
2 (notAvailable). 2 (notAvailable).
In the case of Multicast in MPLS/BGP IP VPNs, In the case of multicast in MPLS/BGP IP VPNs,
this object represents the 'Leaf Information Required flag' this object represents the 'Leaf Information Required flag'
[RFC6514] in the Flags field in the PMSI Tunnel attribute (RFC 6514) in the Flags field in the PMSI Tunnel attribute
of the P-tunnel corresponding to this entry. of the P-tunnel corresponding to this entry.
" "
REFERENCE REFERENCE
"RFC6514, Section 5 "RFC 6514, Section 5
" "
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeMplsLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object represents the MPLS Label in the PMSI Tunnel "This object represents the MPLS Label in the PMSI Tunnel
attribute of the P-tunnel corresponding to this entry. attribute of the P-tunnel corresponding to this entry.
When BGP-based PMSI signaling is used, the PMSI Tunnel When BGP-based PMSI signaling is used, the PMSI Tunnel
attribute of the P-tunnel will be advertised/received attribute of the P-tunnel will be advertised/received
in a PMSI auto-discovery (A-D) route. The value of in a PMSI A-D route. The value of
this object corresponds to the MPLS Label in the attribute. this object corresponds to the MPLS Label in the attribute.
When the P-tunnel does not have a PMSI tunnel When the P-tunnel does not have a PMSI tunnel
attribute, the value of this object will be 0. attribute, the value of this object will be zero.
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC 6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Details of a P-tunnel identified by "Details of a P-tunnel identified by
l2L3VpnMcastPmsiTunnelAttributeId may be present l2L3VpnMcastPmsiTunnelAttributeId may be present
in some other table, e.g., in some other table, e.g.,
mplsTunnelTable [RFC3812]. This object specifies mplsTunnelTable (RFC 3812). This object specifies
the pointer to the row that pertains to the entry the pointer to the row that pertains to the entry
in the table. in the table.
If no such entry exists, the value of this object If no such entry exists, the value of this object
will be zeroDotZero. will be zeroDotZero.
" "
REFERENCE REFERENCE
"RFC3812, Section 6.1 and Section 11" "RFC 3812, Sections 6.1 and 11"
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the P-tunnel identified by "If the P-tunnel identified by
l2L3VpnMcastPmsiTunnelAttributeId has a corresponding l2L3VpnMcastPmsiTunnelAttributeId has a corresponding
entry in ifXTable [RFC2863], this object will entry in ifXTable (RFC 2863), this object will
point to the row in ifXTable that pertains to the entry. point to the row in ifXTable that pertains to the entry.
Otherwise, the value of this object will be zeroDotZero. Otherwise, the value of this object will be zeroDotZero.
" "
REFERENCE REFERENCE
"RFC2863, Section 6" "RFC 2863, Section 6"
DEFVAL { zeroDotZero } DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
-- Conformance Information -- Conformance Information
l2L3VpnMcastCompliances OBJECT IDENTIFIER l2L3VpnMcastCompliances OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 1 } ::= { l2L3VpnMcastConformance 1 }
l2L3VpnMcastGroups OBJECT IDENTIFIER l2L3VpnMcastGroups OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 2 } ::= { l2L3VpnMcastConformance 2 }
-- Compliance Statements -- Compliance Statements
l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE l2L3VpnMcastCoreCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The core compliance statement for SNMP entities "The core compliance statement for SNMP entities
which implement the L2L3-VPN-MULTICAST-MIB Module." that implement the L2L3-VPN-MULTICAST-MIB module.
"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
l2L3VpnMcastCoreGroup l2L3VpnMcastCoreGroup
} }
::= { l2L3VpnMcastCompliances 1 } ::= { l2L3VpnMcastCompliances 1 }
l2L3VpnMcastFullCompliance MODULE-COMPLIANCE l2L3VpnMcastFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The full compliance statement for SNMP entities "The full compliance statement for SNMP entities
which implement the L2L3-VPN-MULTICAST-MIB Module." that implement the L2L3-VPN-MULTICAST-MIB module.
"
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
l2L3VpnMcastCoreGroup, l2L3VpnMcastCoreGroup,
l2L3VpnMcastOptionalGroup l2L3VpnMcastOptionalGroup
} }
::= { l2L3VpnMcastCompliances 2 } ::= { l2L3VpnMcastCompliances 2 }
-- units of conformance -- Units of Conformance
l2L3VpnMcastCoreGroup OBJECT-GROUP l2L3VpnMcastCoreGroup OBJECT-GROUP
OBJECTS { OBJECTS {
l2L3VpnMCastPmsiTunnelLeafInfoRequired, l2L3VpnMCastPmsiTunnelLeafInfoRequired,
l2L3VpnMcastPmsiTunnelAttributeMplsLabel l2L3VpnMcastPmsiTunnelAttributeMplsLabel
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Support of these objects is required." "Support of these objects is required.
"
::= { l2L3VpnMcastGroups 1 } ::= { l2L3VpnMcastGroups 1 }
l2L3VpnMcastOptionalGroup OBJECT-GROUP l2L3VpnMcastOptionalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
l2L3VpnMcastPmsiTunnelPointer, l2L3VpnMcastPmsiTunnelPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Support of these objects is optional." "Support of these objects is optional.
"
::= { l2L3VpnMcastGroups 2 } ::= { l2L3VpnMcastGroups 2 }
END END
5. Security Considerations 5. Security Considerations
There are no management objects defined in these MIB modules that There are no management objects defined in these MIB modules that
have a MAX-ACCESS clause of read-write and/or read-create. So, if have a MAX-ACCESS clause of read-write and/or read-create. So, if
this MIB module is implemented correctly, then there is no risk that this MIB module is implemented correctly, then there is no risk that
an intruder can alter or create any management objects of this MIB an intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations. module via direct SNMP SET operations.
Some of the readable objects in these MIB modules (i.e., objects with Some of the objects in these MIB modules may be considered sensitive
a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. This includes INDEX
or vulnerable in some network environments. It is thus important to objects with a MAX-ACCESS of not-accessible, and any indices from
control even GET and/or NOTIFY access to these objects and possibly other modules exposed via AUGMENTS. It is thus important to control
to even encrypt the values of these objects when sending them over even GET and/or NOTIFY access to these objects and possibly to even
the network via SNMP. These are the tables and objects and their encrypt the values of these objects when sending them over the
network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the o the l2L3VpnMcastPmsiTunnelAttributeTable collectively shows the
P-tunnel network topology and its performance characteristics. P-tunnel network topology and its performance characteristics.
For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will
contain the identifier that uniquely identifies a P-tunnel. This contain the identifier that uniquely identifies a P-tunnel. This
identifier may be composed of source and multicast group IP identifier may be composed of source and multicast group IP
addresses. l2L3VpnMcastPmsiTunnelPointer and addresses. l2L3VpnMcastPmsiTunnelPointer and
l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries
in other tables containing configuration and/or performance in other tables containing configuration and/or performance
skipping to change at page 16, line 47 skipping to change at page 16, line 43
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the "SMI Network Management MGMT
Codes Internet-standard MIB" registry:
Name Description OBJECT IDENTIFIER value Name Description OBJECT-IDENTIFIER value
----------------- -------------------------- ---------------------- ----------------- -------------------------- ----------------------
l2L3VpnMcastTCMIB L2L3-VPN-MULTICAST-TC-MIB { mib-2 AAAA } l2L3VpnMcastTCMIB L2L3-VPN-MULTICAST-TC-MIB { mib-2 244 }
l2L3VpnMcastMIB L2L3-VPN-MULTICAST-MIB { mib-2 BBBB } l2L3VpnMcastMIB L2L3-VPN-MULTICAST-MIB { mib-2 245 }
Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "AAAA" and "BBBB" under the 'mib-2'
subtree and to record the assignment in the SMI Numbers registry.
When the assignment has been made, the RFC Editor is asked to replace
"AAAA" and "BBBB" (here and in the MIB module) with the assigned
value and to remove this note.
7. Acknowledgement
Glenn Mansfield Keeni did the MIB Doctor review and provided valuable
comments.
8. References 7. References
8.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2119, March 1997,
rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and
Schoenwaelder, Ed., "Structure of Management Information J. Schoenwaelder, Ed., "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ Information Version 2 (SMIv2)", STD 58, RFC 2578,
RFC2578, April 1999, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC2578, April 1999,
rfc2578>. <https://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD J. Schoenwaelder, Ed., "Textual Conventions for SMIv2",
58, RFC 2579, DOI 10.17487/RFC2579, April 1999, STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<https://www.rfc-editor.org/info/rfc2579>. <https://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and
Schoenwaelder, Ed., "Conformance Statements for SMIv2", J. Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<https://www.rfc-editor.org/info/rfc2580>. <https://www.rfc-editor.org/info/rfc2580>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<https://www.rfc-editor.org/info/rfc2863>. <https://www.rfc-editor.org/info/rfc2863>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ Protocol (SNMPv3)", STD 62, RFC 3414,
RFC3414, December 2002, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3414, December 2002,
rfc3414>. <https://www.rfc-editor.org/info/rfc3414>.
[RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of
Textual Conventions (TCs) for Multiprotocol Label Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811, DOI 10.17487/ Switching (MPLS) Management", RFC 3811,
RFC3811, June 2004, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3811, June 2004,
rfc3811>. <https://www.rfc-editor.org/info/rfc3811>.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering "Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, DOI (TE) Management Information Base (MIB)", RFC 3812,
10.17487/RFC3812, June 2004, <https://www.rfc- DOI 10.17487/RFC3812, June 2004,
editor.org/info/rfc3812>. <https://www.rfc-editor.org/info/rfc3812>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, DOI 10.17487/ SNMP User-based Security Model", RFC 3826,
RFC3826, June 2004, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3826, June 2004,
rfc3826>. <https://www.rfc-editor.org/info/rfc3826>.
[RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and
Yasukawa, Ed., "Extensions to Resource Reservation S. Yasukawa, Ed., "Extensions to Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) for Point-to- Protocol - Traffic Engineering (RSVP-TE) for Point-to-
Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI Multipoint TE Label Switched Paths (LSPs)", RFC 4875,
10.17487/RFC4875, May 2007, <https://www.rfc- DOI 10.17487/RFC4875, May 2007,
editor.org/info/rfc4875>. <https://www.rfc-editor.org/info/rfc4875>.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, [RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR- "Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007, PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,
<https://www.rfc-editor.org/info/rfc5015>. <https://www.rfc-editor.org/info/rfc5015>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD for the Simple Network Management Protocol (SNMP)",
78, RFC 5591, DOI 10.17487/RFC5591, June 2009, STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<https://www.rfc-editor.org/info/rfc5591>. <https://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <https://www.rfc-editor.org/info/rfc5592>. 2009, <https://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
<https://www.rfc-editor.org/info/rfc6353>. <https://www.rfc-editor.org/info/rfc6353>.
[RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and
Thomas, "Label Distribution Protocol Extensions for Point- B. Thomas, "Label Distribution Protocol Extensions for
to-Multipoint and Multipoint-to-Multipoint Label Switched Point- to-Multipoint and Multipoint-to-Multipoint Label
Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, Switched Paths", RFC 6388, DOI 10.17487/RFC6388, November
<https://www.rfc-editor.org/info/rfc6388>. 2011, <https://www.rfc-editor.org/info/rfc6388>.
[RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/
BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February
2012, <https://www.rfc-editor.org/info/rfc6513>. 2012, <https://www.rfc-editor.org/info/rfc6513>.
[RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP
Encodings and Procedures for Multicast in MPLS/BGP IP Encodings and Procedures for Multicast in MPLS/BGP IP
VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012,
<https://www.rfc-editor.org/info/rfc6514>. <https://www.rfc-editor.org/info/rfc6514>.
skipping to change at page 19, line 46 skipping to change at page 19, line 26
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <https://www.rfc-editor.org/info/rfc7761>. 2016, <https://www.rfc-editor.org/info/rfc7761>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 7.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, DOI 10.17487/ Standard Management Framework", RFC 3410,
RFC3410, December 2002, <https://www.rfc-editor.org/info/ DOI 10.17487/RFC3410, December 2002,
rfc3410>. <https://www.rfc-editor.org/info/rfc3410>.
Acknowledgements
Glenn Mansfield Keeni did the MIB Doctor review and provided valuable
comments.
Authors' Addresses Authors' Addresses
Zhaohui (Jeffrey) Zhang Zhaohui (Jeffrey) Zhang
Juniper Networks, Inc. Juniper Networks, Inc.
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA United States of America
Email: zzhang@juniper.net Email: zzhang@juniper.net
Hiroshi Tsunoda Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho 35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai 982-8577 Taihaku-ku, Sendai 982-8577
Japan Japan
Phone: +81-22-305-3411 Phone: +81-22-305-3411
 End of changes. 128 change blocks. 
362 lines changed or deleted 348 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/