< draft-ietf-bess-l2l3-vpn-mcast-mib-07.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-08.txt >
Network Working Group Z. Zhang Network Working Group Z. Zhang
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track H. Tsunoda Intended status: Standards Track H. Tsunoda
Expires: October 14, 2017 Tohoku Institute of Technology Expires: November 27, 2017 Tohoku Institute of Technology
April 12, 2017 May 26, 2017
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-07 draft-ietf-bess-l2l3-vpn-mcast-mib-08
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 common managed objects used by other MIB In particular, it describes two MIB modules which will be used by
modules which are designed for monitoring and/or configuring both other MIB modules for monitoring and/or configuring Layer 2 and Layer
Layer 2 and Layer 3 Virtual Private Networks (VPN) that support 3 Virtual Private Networks that support multicast.
multicast.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 14, 2017. This Internet-Draft will expire on November 27, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 (http://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
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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 Module . . . . . . . . . . . . . . . . . . . . 4 3. Summary of MIB Modules . . . . . . . . . . . . . . . . . . . 4
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 5 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 5
4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 8 4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 10
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
7.1. Normative References . . . . . . . . . . . . . . . . . . 16 7.1. Normative References . . . . . . . . . . . . . . . . . . 17
7.2. Informative References . . . . . . . . . . . . . . . . . 18 7.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
1. Introduction 1. Introduction
[RFC7117] and [RFC6513] specify procedures for supporting multicast The procedures for supporting multicast in Border Gateway Protocol/
in Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) MultiProtocol Label Switching (BGP/MPLS) Layer 3 (L3) Virtual Private
Layer 2 (L2) and Layer 3 (L3) VPN (Virtual Private Network), Network (VPN) are specified in [RFC6513]. The procedures for
respectively. supporting multicast in Border Gateway Protocol/MultiProtocol Label
Switching Layer 2 (L2) Virtual Private Network are specified in
[RFC7117]. Throughout this document, we will use the term
"L2L3VPNMCast" to mean BGP/MPLS L2 and L3 VPN that support multicast.
Multicast service in BGP/MPLS L2 and L3 VPN can be achieved by using This document describes textual conventions (TCs) and common managed
various kinds of transport mechanisms for forwarding a packet to all objects (MOs) which will be used by other Management Information Base
or a subset of Provider Edge routers (PEs) across service provider (MIB) modules for monitoring and/or configuring L2L3VPNMCast.
networks. Such transport mechanisms are referred to as provider
tunnels (P-tunnels).
The signaling of P-tunnel choice is very similar for multicast in L2L3VPNMCast can be achieved by using various kinds of transport
both L2 and L3 VPNs. [RFC7117] and [RFC6513] describe BGP-based mechanisms for forwarding a packet to all or a subset of Provider
mechanisms for Virtual Private LAN Service (VPLS) and Multicast VPN Edge routers (PEs) across service provider networks. Such transport
(MVPN), respectively. [RFC6514] defines the Provider Multicast mechanisms are referred to as provider tunnels (P-tunnels). The
Service Interface (PMSI) tunnel attribute, a BGP attribute that signaling of P-tunnel choice is very similar for multicast in both L2
specifies information of a P-tunnel. The PMSI tunnel attribute is and L3 VPNs. Therefore, TCs and MOs defined in this document will be
advertised/received by PEs in BGP auto-discovery (A-D) routes. used by other MIB modules for monitoring and/or configuring both L2
[RFC6513] also proposes a UDP-based signaling mechanism. and L3 VPNs that support multicast.
This document defines a textual convention (TC) that can be used to The are two type of the signaling mechanisms of P-tunnel choice: BGP-
represent types of P-tunnels used for multicast in BGP/MPLS L2 or L3 based and UDP-based [RFC6513]. BGP-based mechanisms for Virtual
VPN within MIB module specifications. Private LAN Service and Multicast VPN (MVPN) are described in
[RFC7117] and [RFC6513], respectively. In [RFC6513], a UDP-based
signaling mechanism is also specified.
This document also describes common managed objects used by other MIB A BGP attribute that specifies information of a P-tunnel is called
modules which are designed for monitoring and/or configuring both L2 Provider Multicast Service Interface (PMSI) tunnel attribute. The
and L3 VPN that support multicast. PMSI tunnel attribute is advertised/received by PEs in BGP auto-
discovery (A-D) routes. [RFC6514] defines the format of a PMSI
tunnel attribute.
This document defines four TCs to represent
(a) the tunnel type of a P-tunnel,
(b) the identifier of a P-tunnel,
(c) the pointer to a row in some table pertaining to a P-tunnel, and
(d) the type of the pointer in (c) above,
respectively.
This document also describes common MOs that provide the information
in a PMSI tunnel attribute and corresponding tunnel information to
other MIB modules.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
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, L3 VPN, MVPN they refer to. Familiarity with Multicast, MPLS, Layer 3 VPN, MVPN
(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.
The term "Multicast VPN (MVPN)" [RFC6513] refers to a BGP/MPLS L3 The term "Multicast VPN (MVPN)" [RFC6513] refers to a BGP/MPLS Layer
(IP) VPN service that supports multicast. 3 (IP) VPN service that supports multicast.
"Provider Multicast Service Interface (PMSI)" [RFC6513] is a "Provider Multicast Service Interface (PMSI)" [RFC6513] is a
conceptual interface instantiated by a P-tunnel, a transport conceptual interface instantiated by a P-tunnel, a transport
mechanism used to deliver multicast traffic. A PE uses it to send mechanism used to deliver multicast traffic. A PE uses it to send
customer multicast traffic to all or some PEs in the same VPN. customer multicast traffic to all or some PEs in the same VPN.
There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective There are two kinds of PMSIs: "Inclusive PMSI (I-PMSI)" and
PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE "Selective PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that
attached to a particular MVPN to transmit a message to all PEs in the enables a PE attached to a particular MVPN to transmit a message to
same VPN. An S-PMSI is a PMSI that enables a PE attached to a all PEs in the same VPN. An S-PMSI is a PMSI that enables a PE
particular MVPN to transmit a message to some of the PEs in the same attached to a particular MVPN to transmit a message to some of the
VPN. PEs in the same VPN.
Throughout this document, we will use the term "I/S-PMSI" to refer Throughout this document, we will use the term "PMSI" to refer both
both "I-PMSI" and "S-PMSI". "I-PMSI" and "S-PMSI."
[RFC6513] describes the following tunnel setup techniques that can be [RFC6513] describes the following tunnel setup techniques that can be
used to create the P-tunnels that instantiate the PMSIs. used to create the P-tunnels that instantiate the PMSIs.
o Protocol Independent Multicast tree o Protocol Independent Multicast tree
* Sparse Mode (PIM-SM) tree [RFC4601] * Sparse Mode (PIM-SM) tree [RFC4601]
* Source Specific Multicast (PIM-SSM) tree [RFC4601] * Source Specific Multicast (PIM-SSM) tree [RFC4601]
skipping to change at page 4, line 10 skipping to change at page 4, line 29
* Point-to-MultiPoint (mLDP P2MP) * Point-to-MultiPoint (mLDP P2MP)
* Point-to-MultiPoint (mLDP MP2MP) * Point-to-MultiPoint (mLDP MP2MP)
o Resource Reservation Protocol - Traffic Engineering Point-to- o Resource Reservation Protocol - Traffic Engineering Point-to-
Multipoint (RSVP-TE P2MP) Label Switched Path [RFC4875] Multipoint (RSVP-TE P2MP) Label Switched Path [RFC4875]
o Ingress Replication through Unicast Tunnels [RFC6513] o Ingress Replication through Unicast Tunnels [RFC6513]
A created tunnel will be identified by Tunnel Identifier. The length A tunnel is identified by its Tunnel Identifier. The length of the
of the identifier differs depending on the setup technique that is identifier will depend on the setup technique that is used to create
used to create the tunnel. the tunnel.
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
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
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 Module 3. Summary of MIB Modules
This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and
L2L3-VPN-MCAST-MIB. L2L3-VPN-MCAST-MIB.
o L2L3-VPN-MCAST-TC-MIB contains three Textual Conventions: o L2L3-VPN-MCAST-TC-MIB contains four Textual Conventions:
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastPmsiTunnelPointerType, L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelId,
and L2L3VpnMcastPmsiTunnelPointer. L2L3VpnMcastProviderTunnelPointerType, and
L2L3VpnMcastProviderTunnelType provides an enumeration of the L2L3VpnMcastProviderTunnelPointer. L2L3VpnMcastProviderTunnelType
provider tunnel types. L2L3VpnMcastPmsiTunnelPointerType provides an enumeration of the P-tunnel types.
indicates a type of pointer to the row pertaining to a table entry L2L3VpnMcastProviderTunnelId represents an identifier of a
that represents a provider tunnel. L2L3VpnMcastPmsiTunnelPointer P-tunnel. L2L3VpnMcastProviderTunnelPointerType indicates a type
denotes a pointer to the row pertaining to a table entry that of pointer to the row pertaining to a table entry that represents
represents a provider tunnel. a P-tunnel. L2L3VpnMcastProviderTunnelPointer denotes a pointer
to the row pertaining to a table entry that represents a P-tunnel.
o L2L3-VPN-MCAST-MIB defines a table o L2L3-VPN-MCAST-MIB defines a table
l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table
corresponds to a PMSI Tunnel Attribute (PTA) advertised/received corresponds to a PMSI Tunnel Attribute (PTA) advertised/received
by PE routers. The entry of the table will be used by other MIB by a PE router. Entries in this table will be used by other MIB
modules which are designed for monitoring and/or configuring both modules for monitoring and/or configuring L2L3VPNMCast. The table
L2 and L3 VPN that support multicast. index uniquely identifies a tunnel. It is composed of a set of
The table index is composed of multiple attributes that depend on attributes which depend on the tunnel type. The table may also be
the tunnel type and uniquely identify a tunnel. used in conjunction with other MIBs, such as MPLS Traffic
Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to obtain further
The table may also be used in conjunction with other MIBs, such as information of a tunnel by following the row pointer of the
MPLS Traffic Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to corresponding tunnel's row in this table. It may also be used in
obtain the other details of a tunnel by following the row pointer conjunction with Interfaces Group MIB (IF-MIB) [RFC2863] to obtain
of the corresponding tunnel's row in this table. It may also be further information of the interface corresponding to the tunnel
used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863] by following the row pointer of the corresponding tunnel's row in
to obtain the other details of a corresponding interface that this table.
tunnel uses by following the row pointer of the corresponding
tunnel's row in this table.
4. Definitions 4. Definitions
4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions
L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
l2L3VpnMcastTCMIB MODULE-IDENTITY l2L3VpnMcastTCMIB MODULE-IDENTITY
LAST-UPDATED "201702211200Z" -- 21th February, 2017 LAST-UPDATED "201705261200Z" -- 26th May, 2017
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 USA
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" Comments and discussion to bess@ietf.org
"
DESCRIPTION DESCRIPTION
"This MIB module contains a textual convention for "This MIB module specifies textual conventions for
Border Gateway Protocol/MultiProtocol Label Border Gateway Protocol/MultiProtocol Label
Switching (BGP/MPLS) Layer 2 (L2) and Layer 3 Switching Layer 2 and Layer 3 Virtual Private Network
(L3) Virtual Private Network (VPN). that support multicast (L2L3VPNMCast).
Copyright (C) The Internet Society (2017)."
Copyright (C) The Internet Society (2017).
"
-- Revision history. -- Revision history.
REVISION "201702211200Z" -- 21th February, 2017 REVISION "201705261200Z" -- 26th May, 2017
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
-- RFC Ed. replace XXXX with actual RFC number and remove this note -- RFC Ed. replace XXXX with actual RFC number and remove this note
::= { mib-2 AAAA } ::= { mib-2 AAAA }
-- IANA Reg.: Please assign a value for "AAAA" under the -- IANA Reg.: Please assign a value for "AAAA" under the
-- 'mib-2' subtree and record the assignment in the SMI -- 'mib-2' subtree and record the assignment in the SMI
-- Numbers registry. -- Numbers registry.
skipping to change at page 6, line 29 skipping to change at page 6, line 49
-- RFC Ed.: When the above assignment has been made, please -- RFC Ed.: When the above assignment has been made, please
-- remove the above note -- remove the above note
-- replace "AAAA" here with the assigned value and -- replace "AAAA" here with the assigned value and
-- remove this note. -- remove this note.
-- Textual convention -- Textual convention
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention enumerates the values "This textual convention enumerates values
representing a type of a provider tunnel representing the type of a provider tunnel (P-tunnel)
used for multicast in BGP/MPLS L2 or L3 VPN. used for L2L3VPNMCast.
These labelled numbers are aligned based on the definition These labeled numbers are aligned with the definition
of Tunnel types in Section 5 of [RFC6514]. of Tunnel types in Section 5 of [RFC6514].
" "
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
SYNTAX INTEGER SYNTAX INTEGER
{ noTunnelId (0), -- No tunnel information present {
noTunnelId (0), -- No tunnel information
rsvpP2mp (1), -- RSVP-TE P2MP LSP rsvpP2mp (1), -- RSVP-TE P2MP LSP
ldpP2mp (2), -- mLDP P2MP LSP ldpP2mp (2), -- mLDP P2MP LSP
pimSsm (3), -- PIM-SSM Tree pimSsm (3), -- PIM-SSM Tree
pimAsm (4), -- PIM-SM Tree pimAsm (4), -- PIM-SM Tree
pimBidir (5), -- BIDIR-PIM Tree pimBidir (5), -- BIDIR-PIM Tree
ingressReplication (6), -- Ingress Replication ingressReplication (6), -- Ingress Replication
ldpMp2mp (7) -- mLDP MP2MP LSP ldpMp2mp (7) -- mLDP MP2MP LSP
} }
L2L3VpnMcastProviderTunnelId ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention represents the tunnel identifier
of a P-tunnel.
The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of the corresponding
L2L3VpnMcastProviderTunnelType object.
The corresponding L2L3VpnMcastProviderTunnelType object
represents the type of the tunneling technology used
to establish the P-tunnel.
The size of the identifier for each tunneling technology
is summarized below.
L2L3VpnMcastProviderTunnelType Size (in octets)
(tunneling technology) IPv4 IPv6
--------------------------------------------------------
noTunnelId (No tunnel information) 0 0
rsvpP2mp (RSVP-TE P2MP LSP) 12 24
ldpP2mp (mLDP P2MP LSP) 17 29
pimSsm (PIM-SSM Tree) 8 32
pimAsm (PIM-SM Tree) 8 32
pimBidir (BIDIR-PIM Tree) 8 32
ingressReplication (Ingress Replication) 4 16
ldpMp2mp (mLDP MP2MP LSP) 17 29
A L2L3VpnMcastProviderTunnelType object of value
noTunnelId(0) indicates that the corresponding
Provider Multicast Service Interface (PMSI) Tunnel
attribute does not have tunnel information.
The value of the corresponding L2L3VpnMcastProviderTunnelId
object will be a string of length zero.
When the L2L3VpnMcastProviderTunnelType object is of value
rsvpP2mp(1), the corresponding Tunnel Identifier is composed of
Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6),
Reserved (2 octets), Tunnel ID (2 octets), and
P2MP ID (4 octets).
The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 12 octets in IPv4 and 24 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value
ldpP2mp(2), the corresponding Tunnel Identifier is P2MP
Forwarding Equivalence Class (FEC) Element [RFC6388].
The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 17 octets in IPv4 and 29 octets in IPv6
When the L2L3VpnMcastProviderTunnelType object is of value
pimSsm(3), PimAsm(4), or PimBidir(5), the corresponding
Tunnel Identifier is composed of the source IP address
and the group IP address.
The size of the corresponding L2L3VpnMcastProviderTunnelId
object will be 8 octets in IPv4 and 32 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value
ingressReplication(6), the Tunnel Identifier is
the unicast tunnel endpoint IP address of the local PE.
The size of the corresponding L2L3VpnMcastProviderTunnelId
object is 4 octets in IPv4 and 16 octets in IPv6.
When the L2L3VpnMcastProviderTunnelType object is of value
ldpMp2mp(7), the Tunnel Identifier is MP2MP FEC Element
[RFC6388].
The size of the corresponding L2L3VpnMcastProviderTunnelId
object 17 octets in IPv4 and 29 octets in IPv6.
"
REFERENCE
"RFC6514, Section 5
RFC4875, Section 19.1
RFC6388, Section 2.2 and 3.2
"
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
L2L3VpnMcastProviderTunnelPointer ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelPointer ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a pointer to the row pertaining "This textual convention represents a pointer to a row in
to a table entry that represents a a table represented by the following object of type
provider tunnel used for multicast in BGP/MPLS L2 or L3 VPN. L2L3VpnMcastProviderTunnelPointerType.
An L2L3VpnMcastProviderTunnelPointer value is always An L2L3VpnMcastProviderTunnelPointer value is always
interpreted within the context of an interpreted within the context of an
L2L3VpnMcastProviderTunnelPointerType value. L2L3VpnMcastProviderTunnelPointerType value.
Every usage of the L2L3VpnMcastProviderTunnelPointer Every usage of the L2L3VpnMcastProviderTunnelPointer
textual convention MUST specify the textual convention MUST specify the
L2L3VpnMcastProviderTunnelPointerType object which L2L3VpnMcastProviderTunnelPointerType object which
provides the context. provides the context.
Furthermore, MIB authors SHOULD define a separate Furthermore, MIB authors SHOULD define a separate
L2L3VpnMcastProviderTunnelPointerType object for each L2L3VpnMcastProviderTunnelPointerType object for each
L2L3VpnMcastProviderTunnelPointer object. L2L3VpnMcastProviderTunnelPointer object.
The L2L3VpnMcastProviderTunnelPointerType object which The L2L3VpnMcastProviderTunnelPointerType object which
defines the context must be registered immediately before defines the context must be registered immediately before
the object which uses the L2L3VpnMcastProviderTunnelPointer the object which uses the L2L3VpnMcastProviderTunnelPointer
textual convention. textual convention.
"
The value of an L2L3VpnMcastProviderTunnelPointer object
must always be consistent with the value of the associated
L2L3VpnMcastProviderTunnelPointerType object. Attempts
to set a L2L3VpnMcastProviderTunnelPointer object to a value
which is inconsistent with the associated
L2L3VpnMcastProviderTunnelPointerType must fail with
an inconsistentValue error.
"
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
L2L3VpnMcastProviderTunnelPointerType ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelPointerType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention enumerates the types of "This textual convention enumerates the
tables having the row that an L2L3VpnMcastProviderTunnelPointer tables having the row that an L2L3VpnMcastProviderTunnelPointer
object points to. object points to.
The row pertains to the entry that represents a The row pertains to the entry that represents a
provider tunnel used for multicast in BGP/MPLS P-tunnel used for L2L3VPNMCast.
L2 or L3 VPN.
The enumerated values have the following meaning: The enumerated values have the following meanings:
null(0) null(0)
A pointer is null. Default value. This indicates that the corresponding
L2L3VpnMcastProviderTunnelPointer object is not assigned.
pointerToMplsTunnelTable(1) pointerToMplsTunnelTable(1)
A pointer points to the row in mplsTunnelTable defined in The corresponding L2L3VpnMcastProviderTunnelPointer object
[RFC3812]. points to a row in an mplsTunnelTable defined in [RFC3812].
pointerToTunnelIfTableForGRE(2) pointerToTunnelIfTableForGRE(2)
A pointer points to the row in tunnelIfTable defined in The corresponding L2L3VpnMcastProviderTunnelPointer object
[RFC4087] for GRE tunnel. points to a row in a tunnelIfTable defined in [RFC4087] for
GRE tunnel.
" "
REFERENCE REFERENCE
"RFC3812, RFC4087" "RFC3812, RFC4087"
SYNTAX INTEGER SYNTAX INTEGER
{ null (0), -- A pointer is null. {
pointerToMplsTunnelTable (1), -- A pointer to the row null (0), -- Default value
pointerToMplsTunnelTable (1), -- Pointer to a row
-- in mplsTunnelTable -- in mplsTunnelTable
pointerToTunnelIfTableForGRE (2) -- A pointer to the row pointerToTunnelIfTableForGRE (2) -- Pointer to a row
-- in tunnelIfTable -- in tunnelIfTable
-- for GRE tunnel -- for GRE tunnel
} }
END END
4.2. L2L3-VPN-MCAST-MIB Object Definitions 4.2. L2L3-VPN-MCAST-MIB Object Definitions
L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
RowPointer
FROM SNMPv2-TC -- [RFC2579]
MplsLabel
FROM MPLS-TC-STD-MIB -- [RFC3811]
L2L3VpnMcastProviderTunnelType,
L2L3VpnMcastProviderTunnelPointerType,
L2L3VpnMcastProviderTunnelPointer
FROM L2L3-VPN-MCAST-TC-MIB;
l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201702211200Z" -- 21th February, 2017
ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO
" Zhaohui Zhang
Juniper Networks, Inc.
10 Technology Park Drive
Westford, MA 01886
USA
Email: zzhang@juniper.net
Hiroshi Tsunoda
Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577
Japan
Email: tsuno@m.ieice.org
Comments and discussion to bess@ietf.org"
DESCRIPTION
"This MIB module will be used by other MIB modules designed for
monitoring and/or configuring both Layer 2 (L2) and
Layer 3 (L3) Virtual Private Networks (VPN) that support
multicast.
Copyright (C) The Internet Society (2017)."
-- Revision history.
REVISION "201702211200Z" -- 21th February, 2017
DESCRIPTION
"Initial version, published as RFC XXXX."
-- RFC Ed. replace XXXX with actual RFC number and remove this note
::= { mib-2 BBBB } IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2, zeroDotZero
FROM SNMPv2-SMI -- [RFC2578]
-- IANA Reg.: Please assign a value for "BBBB" under the MODULE-COMPLIANCE, OBJECT-GROUP
-- 'mib-2' subtree and record the assignment in the SMI FROM SNMPv2-CONF -- [RFC2580]
-- Numbers registry.
-- RFC Ed.: When the above assignment has been made, please RowPointer
-- remove the above note FROM SNMPv2-TC -- [RFC2579]
-- replace "BBBB" here with the assigned value and
-- remove this note.
-- Top level components of this MIB. MplsLabel
l2L3VpnMcastStates OBJECT IDENTIFIER FROM MPLS-TC-STD-MIB -- [RFC3811]
::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastConformance OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 2 }
-- tables, scalars, conformance information L2L3VpnMcastProviderTunnelType,
-- Table of PMSI Tunnel Attributes L2L3VpnMcastProviderTunnelId,
L2L3VpnMcastProviderTunnelPointerType,
L2L3VpnMcastProviderTunnelPointer
FROM L2L3-VPN-MCAST-TC-MIB;
l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE l2L3VpnMcastMIB MODULE-IDENTITY
SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry LAST-UPDATED "201705261200Z" -- 26th May, 2017
MAX-ACCESS not-accessible ORGANIZATION "IETF BESS Working Group."
STATUS current CONTACT-INFO
DESCRIPTION " Zhaohui Zhang
"An entry of this table corresponds to a Juniper Networks, Inc.
PMSI Tunnel attribute and is created by a PE router 10 Technology Park Drive
that advertises and receives the attribute. Westford, MA 01886
The entry in the table will be referred by other MIB modules USA
which are designed for monitoring and/or configuring Email: zzhang@juniper.net
both L2 and L3 VPN that support multicast." Hiroshi Tsunoda
REFERENCE Tohoku Institute of Technology
"RFC6514, Section 5" 35-1, Yagiyama Kasumi-cho
::= { l2L3VpnMcastStates 1 } Taihaku-ku, Sendai, 982-8577
Japan
Email: tsuno@m.ieice.org
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE Comments and discussion to bess@ietf.org
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry "
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION DESCRIPTION
"A conceptual row corresponding to a PTA "This MIB module will be used by other MIB modules designed for
that is advertised/received on this router." monitoring and/or configuring Border Gateway
REFERENCE Protocol/MultiProtocol Label Switching
"RFC6514, Section 5" Layer 2 and Layer 3 Virtual Private
INDEX { Network that support multicast (L2L3VPNMCast).
l2L3VpnMcastPmsiTunnelAttributeFlags, Copyright (C) The Internet Society (2017).
l2L3VpnMcastPmsiTunnelAttributeType, "
l2L3VpnMcastPmsiTunnelAttributeLabel, -- Revision history.
l2L3VpnMcastPmsiTunnelAttributeId
}
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId
OCTET STRING,
l2L3VpnMcastPmsiTunnelPointerType
L2L3VpnMcastProviderTunnelPointerType,
l2L3VpnMcastPmsiTunnelPointer
L2L3VpnMcastProviderTunnelPointer,
l2L3VpnMcastPmsiTunnelIf
RowPointer
}
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE REVISION "201705261200Z" -- 26th May, 2017
SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION DESCRIPTION
"Denotes the Flags field in a PMSI Tunnel attribute "Initial version, published as RFC XXXX."
with the following format.
0 1 2 3 4 5 6 7 -- RFC Ed. replace XXXX with actual RFC number and remove this note
+-+-+-+-+-+-+-+-+
| reserved |L|
+-+-+-+-+-+-+-+-+
L: Leaf Information Required ::= { mib-2 BBBB }
When BGP-based I/S-PMSI signaling is used, the value of -- IANA Reg.: Please assign a value for "BBBB" under the
this object corresponds to the Flags field in -- 'mib-2' subtree and record the assignment in the SMI
an advertised/received I/S-PMSI auto-discovery (A-D) route. -- Numbers registry.
When UDP-based S-PMSI signaling is used, the value of -- RFC Ed.: When the above assignment has been made, please
this object is zero." -- remove the above note
REFERENCE -- replace "BBBB" here with the assigned value and
"RFC6514, Section 5" -- remove this note.
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE -- Top level components of this MIB.
SYNTAX L2L3VpnMcastProviderTunnelType l2L3VpnMcastStates OBJECT IDENTIFIER
MAX-ACCESS not-accessible ::= { l2L3VpnMcastMIB 1 }
STATUS current l2L3VpnMcastConformance OBJECT IDENTIFIER
DESCRIPTION ::= { l2L3VpnMcastMIB 2 }
"Denotes the Tunnel Type field that identifies
the type of the tunneling technology used to
establish the provider tunnel, in a PMSI Tunnel
attribute.
When BGP-based I/S-PMSI signaling is used, the value of -- tables, scalars, conformance information
this object corresponds to the Tunnel Type field in -- Table of PMSI Tunnel Attributes
an advertised/received I/S-PMSI A-D route.
When UDP-based S-PMSI signaling is used, the value of l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE
this object will be one of pimAsm (3), pimSsm (4), or SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
pimBidir (5)." MAX-ACCESS not-accessible
REFERENCE STATUS current
"RFC6514, Section 5" DESCRIPTION
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } "An entry in this table corresponds to a
(Provider Multicast Service Interface) PMSI Tunnel
attribute and is maintained by a PE router
that advertises and receives the attribute.
The entries will be referred to by other MIB modules
for monitoring and/or configuring L2L3VPNMCast.
"
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
SYNTAX MplsLabel SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the MPLS Label field that contains "A conceptual row corresponding to a PTA
an MPLS label, in a PMSI Tunnel attribute. that is advertised/received on this router.
"
REFERENCE
"RFC6514, Section 5"
INDEX {
l2L3VpnMcastPmsiTunnelAttributeFlags,
l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeLabel,
l2L3VpnMcastPmsiTunnelAttributeId
}
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
When BGP-based I/S-PMSI signaling is used, the value of L2L3VpnMcastPmsiTunnelAttributeEntry ::=
this object corresponds to the MPLS Label field in SEQUENCE {
an advertised/received I/S-PMSI A-D route. l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId
L2L3VpnMcastProviderTunnelId,
l2L3VpnMcastPmsiTunnelPointerType
L2L3VpnMcastProviderTunnelPointerType,
l2L3VpnMcastPmsiTunnelPointer
L2L3VpnMcastProviderTunnelPointer,
l2L3VpnMcastPmsiTunnelIf
RowPointer
}
When UDP-based S-PMSI signaling is used, the value of l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
this object is zero that indicates absence of MPLS SYNTAX OCTET STRING (SIZE (1))
Label." MAX-ACCESS not-accessible
REFERENCE STATUS current
"RFC6514, Section 5" DESCRIPTION
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } "This object represents the Flags field in the PMSI Tunnel
attribute. The Flags field has the following format.
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE 0 1 2 3 4 5 6 7
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) ) +-+-+-+-+-+-+-+-+
MAX-ACCESS not-accessible | reserved |L|
STATUS current +-+-+-+-+-+-+-+-+
DESCRIPTION
"Denotes the Tunnel Identifier field that uniquely
identifies a created tunnel, in a PMSI Tunnel
attribute.
The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of
l2L3VpnMcastPmsiTunnelAttributeType, i.e., the type of
the tunneling technology used to establish the provider
tunnel.
The size of the identifier for each tunneling technology L: Leaf Information Required
is summarized below.
Size (in octets) l2L3VpnMcastPmsiTunnelAttributeType When BGP-based PMSI signaling is used, the value of
IPv4 IPv6 (tunneling technology) this object corresponds to the Flags field in
-------------------------------------------------- an advertised/received PMSI auto-discovery (A-D) route.
0 0 noTunnelId (No tunnel information present)
12 24 rsvpP2mp (RSVP-TE P2MP LSP)
17 29 ldpP2mp (mLDP P2MP LSP)
8 32 pimSsm (PIM-SSM Tree)
8 32 pimAsm (PIM-SM Tree)
8 32 pimBidir (BIDIR-PIM Tree)
4 16 ingressReplication
(Ingress Replication)
17 29 ldpMp2mp (mLDP MP2MP LSP)
When l2L3VpnMcastPmsiTunnelAttributeType is set to When UDP-based S-PMSI signaling is used, the value of
noTunnelId(0), the PMSI Tunnel attribute does not have this object is zero.
tunnel information. Thus, the size of this object is zero. "
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
When l2L3VpnMcastPmsiTunnelAttributeType is set to l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
rsvpP2mp(1), the Tunnel Identifier is composed of SYNTAX L2L3VpnMcastProviderTunnelType
Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6), MAX-ACCESS not-accessible
Reserved (2 octets), Tunnel ID (2 octets), and STATUS current
P2MP ID (4 octets). Thus, the size of this object is DESCRIPTION
12 octets in IPv4 and 24 octets in IPv6. "The Tunnel Type field that identifies
the type of the tunneling technology used to
establish the provider tunnel (P-tunnel), in a
PMSI Tunnel attribute.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When BGP-based PMSI signaling is used, the value of
ldpP2mp(2), the Tunnel Identifier is 17 octets this object corresponds to the Tunnel Type field in
(in IPv4) or 29 octets (in IPv6) P2MP Forwarding an advertised/received PMSI auto-discovery (A-D) route.
Equivalence Class (FEC) Element.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When UDP-based S-PMSI signaling is used, the value of
pimSsm(3), PimAsm(4), or PimBidir(5), the Tunnel Identifier is this object will be one of pimAsm (3), pimSsm (4), or
a pair of source and group IP addresses. pimBidir (5).
Thus, the size of this object is 16 octets in IPv4 "
and 32 octets in IPv6. REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
When l2L3VpnMcastPmsiTunnelAttributeType is set to l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
ingressReplication(6), the Tunnel Identifier is SYNTAX MplsLabel
the unicast tunnel endpoint IP address of the local MAX-ACCESS not-accessible
PE. Thus, the size of this object is 4 octets in IPv4 STATUS current
and 16 octets in IPv6. DESCRIPTION
"The MPLS Label field in a PMSI Tunnel attribute.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When BGP-based PMSI signaling is used, the value of
ldpMp2mp(7), the Tunnel Identifier is 17 octets this object corresponds to the MPLS Label field in
(in IPv4) or 29 octets (in IPv6) MP2MP FEC Element. an advertised/received PMSI A-D route.
When BGP-based I/S-PMSI signaling is used, the value of When UDP-based S-PMSI signaling is used, the value of
this object corresponds to the Tunnel this object is zero that indicates the absence of MPLS
Identifier field in an advertised/received I/S-PMSI Label.
A-D route. Thus, the size of this object is determined "
by the above table. REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
When UDP-based S-PMSI signaling is used, the value of l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
this object is a pair of source and group IP addresses. SYNTAX L2L3VpnMcastProviderTunnelId
Thus, the size of this object is 16 octets in IPv4 MAX-ACCESS not-accessible
and 32 octets in IPv6." STATUS current
REFERENCE DESCRIPTION
"RFC6514, Section 5 "The Tunnel Identifier field that uniquely
RFC4875, Section 19.1 identifies a tunnel, in a PMSI Tunnel attribute.
RFC6388, Section 2.2 and 2.3" The size of the identifier depends on the address family
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } (IPv4 or IPv6) and the value of the corresponding
l2L3VpnMcastPmsiTunnelAttributeType object i.e., the type of
the tunneling technology used to establish the provider
tunnel.
"
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointerType OBJECT-TYPE l2L3VpnMcastPmsiTunnelPointerType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelPointerType SYNTAX L2L3VpnMcastProviderTunnelPointerType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of l2L3VpnMcastPmsiTunnelPointer. "The type of l2L3VpnMcastPmsiTunnelPointer.
The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId
may be represented as an entry in other table, e.g, may be represented as an entry in some other table, e.g.,
mplsTunnelTable [RFC3812]. This object specifies mplsTunnelTable [RFC3812]. This object specifies
the type of pointer to the row pertaining to the entry. the type of the pointer to the row pertaining to the entry.
If such an entry does not exist, the value of this object If such an entry does not exist, the value of this object
becomes null(0). MUST be null(0).
" "
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } DEFVAL { null }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelPointer SYNTAX L2L3VpnMcastProviderTunnelPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The pointer to a table entry representing the tunnel "The pointer to a table entry representing the tunnel
identified by l2L3VpnMcastPmsiTunnelAttributeId. identified by l2L3VpnMcastPmsiTunnelAttributeId.
The type of this pointer is specified with The type of this pointer is specified with
the corresponding instance of the the corresponding instance of the
l2L3VpnMcastPmsiTunnelPointerType object. l2L3VpnMcastPmsiTunnelPointerType object.
If the value of the corresponding instance of the If the value of the corresponding instance of the
l2L3VpnMcastPmsiTunnelPointerType is null(0), l2L3VpnMcastPmsiTunnelPointerType is null(0),
the value of this object MUST be null. the value of this object MUST be set to zeroDotZero.
" "
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
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 tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId "If the tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId
has a corresponding entry in the ifXTable [RFC2863], has a corresponding entry in the ifXTable [RFC2863],
this object will point to the row pertaining to the entry this object will point to the row pertaining to the entry
in the ifXTable. Otherwise, the pointer is null." in the ifXTable. Otherwise, this object MUST be set to
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 } zeroDotZero."
DEFVAL { zeroDotZero }
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 7 }
-- Conformance Information -- Conformance Information
l2L3VpnMcastGroups OBJECT IDENTIFIER l2L3VpnMcastGroups OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 1 } ::= { l2L3VpnMcastConformance 1 }
l2L3VpnMcastCompliances OBJECT IDENTIFIER l2L3VpnMcastCompliances OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 2 } ::= { l2L3VpnMcastConformance 2 }
-- Compliance Statements -- Compliance Statements
l2L3VpnMcastCompliance MODULE-COMPLIANCE l2L3VpnMcastCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement: no mandatory groups " "The compliance statement: no mandatory groups "
MODULE -- this module MODULE -- this module
GROUP l2L3VpnMcastOptionalGroup GROUP l2L3VpnMcastOptionalGroup
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
::= { l2L3VpnMcastCompliances 1 } ::= { l2L3VpnMcastCompliances 1 }
-- units of conformance -- units of conformance
l2L3VpnMcastOptionalGroup OBJECT-GROUP l2L3VpnMcastOptionalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
l2L3VpnMcastPmsiTunnelPointerType, l2L3VpnMcastPmsiTunnelPointerType,
l2L3VpnMcastPmsiTunnelPointer, l2L3VpnMcastPmsiTunnelPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Support of these objects is not required." "Support of these objects is not required."
::= { l2L3VpnMcastGroups 1 } ::= { l2L3VpnMcastGroups 1 }
END END
5. Security Considerations 5. Security Considerations
There are no management objects defined in this MIB module that have There are no management objects defined in these MIB modules that
a MAX-ACCESS clause of read-write and/or read-create. So, if this have a MAX-ACCESS clause of read-write and/or read-create. So, if
MIB module is implemented correctly, then there is no risk that an this MIB module is implemented correctly, then there is no risk that
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 this MIB module (i.e., objects with a Some of the readable objects in these MIB modules (i.e., objects with
MAX-ACCESS other than not-accessible) may be considered sensitive or a MAX-ACCESS other than not-accessible) may be considered sensitive
vulnerable in some network environments. It is thus important to or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o l2L3VpnMcastPmsiTunnelPointer and l2L3VpnMcastPmsiTunnelIf in o the l2L3VpnMcastPmsiTunnelAttributeTable collectively show the
l2L3VpnMcastPmsiTunnelAttributeTable will point to the P-tunnel network topology and its performance characteristics.
corresponding entries in other tables containing configuration For instance, l2L3VpnMcastPmsiTunnelAttributeId in this table will
and/or performance information of a tunnel and an interface. If contain the identifier that uniquely identifies a created
an Administrator does not want to reveal this information, then P-tunnel. This identifier may be composed of source and multicast
these objects should be considered sensitive/vulnerable. group IP addresses. l2L3VpnMcastPmsiTunnelPointer and
l2L3VpnMcastPmsiTunnelIf will point to the corresponding entries
in other tables containing configuration and/or performance
information of a tunnel and an interface. If an Administrator
does not want to reveal this information, then these objects
should be considered sensitive/vulnerable.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), Even if the network itself is secure (for example by using IPsec),
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB module. MIB module.
Implementations SHOULD provide the security features described by the Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for compliance to the SNMPv3 standard MUST include full support for
skipping to change at page 17, line 43 skipping to change at page 18, line 37
(TE) Management Information Base (MIB)", RFC 3812, DOI (TE) Management Information Base (MIB)", RFC 3812, DOI
10.17487/RFC3812, June 2004, 10.17487/RFC3812, June 2004,
<http://www.rfc-editor.org/info/rfc3812>. <http://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, DOI 10.17487/
RFC3826, June 2004, RFC3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>. <http://www.rfc-editor.org/info/rfc3826>.
[RFC4087] Thaler, D., "IP Tunnel MIB", RFC 4087, DOI 10.17487/
RFC4087, June 2005,
<http://www.rfc-editor.org/info/rfc4087>.
[RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S.
Yasukawa, Ed., "Extensions to Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) for Point-to-
Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI
10.17487/RFC4875, May 2007,
<http://www.rfc-editor.org/info/rfc4875>.
[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)", STD
78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>. <http://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, <http://www.rfc-editor.org/info/rfc5592>. 2009, <http://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,
<http://www.rfc-editor.org/info/rfc6353>. <http://www.rfc-editor.org/info/rfc6353>.
[RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B.
Thomas, "Label Distribution Protocol Extensions for Point-
to-Multipoint and Multipoint-to-Multipoint Label Switched
Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011,
<http://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, <http://www.rfc-editor.org/info/rfc6513>. 2012, <http://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,
<http://www.rfc-editor.org/info/rfc6514>. <http://www.rfc-editor.org/info/rfc6514>.
[RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and [RFC7117] Aggarwal, R., Ed., Kamite, Y., Fang, L., Rekhter, Y., and
skipping to change at page 18, line 38 skipping to change at page 19, line 49
Standard Management Framework", RFC 3410, DOI 10.17487/ Standard Management Framework", RFC 3410, DOI 10.17487/
RFC3410, December 2002, RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>. <http://www.rfc-editor.org/info/rfc3410>.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM): "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, DOI 10.17487/ Protocol Specification (Revised)", RFC 4601, DOI 10.17487/
RFC4601, August 2006, RFC4601, August 2006,
<http://www.rfc-editor.org/info/rfc4601>. <http://www.rfc-editor.org/info/rfc4601>.
[RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S.
Yasukawa, Ed., "Extensions to Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) for Point-to-
Multipoint TE Label Switched Paths (LSPs)", RFC 4875, DOI
10.17487/RFC4875, May 2007,
<http://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,
<http://www.rfc-editor.org/info/rfc5015>. <http://www.rfc-editor.org/info/rfc5015>.
[RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B.
Thomas, "Label Distribution Protocol Extensions for Point-
to-Multipoint and Multipoint-to-Multipoint Label Switched
Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011,
<http://www.rfc-editor.org/info/rfc6388>.
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 USA
Email: zzhang@juniper.net Email: zzhang@juniper.net
 End of changes. 93 change blocks. 
441 lines changed or deleted 490 lines changed or added

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