draft-ietf-bess-l2l3-vpn-mcast-mib-06.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-07.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: August 25, 2017 Tohoku Institute of Technology Expires: October 14, 2017 Tohoku Institute of Technology
February 21, 2017 April 12, 2017
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-06 draft-ietf-bess-l2l3-vpn-mcast-mib-07
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 common managed objects used by other MIB
modules which are designed for monitoring and/or configuring both modules which are designed for monitoring and/or configuring both
Layer 2 and Layer 3 Virtual Private Networks (VPN) that support Layer 2 and Layer 3 Virtual Private Networks (VPN) that support
multicast. multicast.
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 August 25, 2017. This Internet-Draft will expire on October 14, 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 15 skipping to change at page 2, line 15
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 Module . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . 6 4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
7.1. Normative References . . . . . . . . . . . . . . . . . . 14 7.1. Normative References . . . . . . . . . . . . . . . . . . 16
7.2. Informative References . . . . . . . . . . . . . . . . . 16 7.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
[RFC7117] and [RFC6513] specify procedures for supporting multicast [RFC7117] and [RFC6513] specify procedures for supporting multicast
in Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS) in Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)
Layer 2 (L2) and Layer 3 (L3) VPN (Virtual Private Network), Layer 2 (L2) and Layer 3 (L3) VPN (Virtual Private Network),
respectively. respectively.
Multicast service in BGP/MPLS L2 and L3 VPN can be achieved by using Multicast service in BGP/MPLS L2 and L3 VPN can be achieved by using
various kinds of transport mechanism for forwarding a packet to all various kinds of transport mechanisms for forwarding a packet to all
or a subset of Provider Edge routers (PEs) across service provider or a subset of Provider Edge routers (PEs) across service provider
networks. Such transport mechanisms are referred to as provider networks. Such transport mechanisms are referred to as provider
tunnels (P-tunnels). tunnels (P-tunnels).
The signaling of P-tunnel choice is very similar for multicast in The signaling of P-tunnel choice is very similar for multicast in
both L2 and L3 VPNs. [RFC7117] and [RFC6513] describe BGP-based both L2 and L3 VPNs. [RFC7117] and [RFC6513] describe BGP-based
mechanisms for Virtual Private LAN Service (VPLS) and Multicast VPN mechanisms for Virtual Private LAN Service (VPLS) and Multicast VPN
(MVPN), respectively. [RFC6514] defines the Provider Multicast (MVPN), respectively. [RFC6514] defines the Provider Multicast
Service Interface (PMSI) tunnel attribute, a BGP attribute that Service Interface (PMSI) tunnel attribute, a BGP attribute that
specifies information of a P-tunnel. The PMSI tunnel attribute is specifies information of a P-tunnel. The PMSI tunnel attribute is
advertised/received by PEs in BPG auto-discovery (A-D) routes. advertised/received by PEs in BGP auto-discovery (A-D) routes.
[RFC6513] also proposes a UDP-based signaling mechanism. [RFC6513] also proposes a UDP-based signaling mechanism.
This document defines a textual conventions (TC) that can be used to This document defines a textual convention (TC) that can be used to
represent types of P-tunnels used for multicast in BGP/MPLS L2 or L3 represent types of P-tunnels used for multicast in BGP/MPLS L2 or L3
VPN within MIB module specifications. VPN within MIB module specifications.
This document also describes common managed objects used by other MIB This document also describes common managed objects used by other MIB
modules which are designed for monitoring and/or configuring both L2 modules which are designed for monitoring and/or configuring both L2
and L3 VPN that support multicast. and L3 VPN that support multicast.
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].
skipping to change at page 3, line 22 skipping to change at page 3, line 22
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, L3 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 L3
(IP) VPN service that supports multicast. (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 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 PMSI: "Inclusive PMSI (I-PMSI)" and "Selective
PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE
attached to a particular MVPN to transmit a message to all PEs in the attached to a particular MVPN to transmit a message to all PEs in the
same VPN. An S-PMSI is a PMSI that enables a PE attached to a same VPN. An S-PMSI is a PMSI that enables a PE attached to a
particular MVPN to transmit a message to some of the PEs in the same particular MVPN to transmit a message to some of the PEs in the same
VPN. VPN.
Throughout this document, we will use the term "I/S-PMSI" to refer Throughout this document, we will use the term "I/S-PMSI" to refer
both "I-PMSI" and "S-PMSI". both "I-PMSI" and "S-PMSI".
[RFC6513] describes 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]
* Bidirectional Protocol Independent Multicast (BIDIR-PIM) tree * Bidirectional Protocol Independent Multicast (BIDIR-PIM) tree
[RFC5015] [RFC5015]
skipping to change at page 4, line 34 skipping to change at page 4, line 34
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 Module
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 a Textual Convention o L2L3-VPN-MCAST-TC-MIB contains three Textual Conventions:
L2L3VpnMcastProviderTunnelType that provides an enumeration of the L2L3VpnMcastProviderTunnelType, L2L3VpnMcastPmsiTunnelPointerType,
provider tunnel types. and L2L3VpnMcastPmsiTunnelPointer.
L2L3VpnMcastProviderTunnelType provides an enumeration of the
provider tunnel types. L2L3VpnMcastPmsiTunnelPointerType
indicates a type of pointer to the row pertaining to a table entry
that represents a provider tunnel. L2L3VpnMcastPmsiTunnelPointer
denotes a pointer to the row pertaining to a table entry that
represents a provider tunnel.
o L2L3-VPN-MCAST-MIB defines a table o L2L3-VPN-MCAST-MIB defines a table
l2L3VpnMcastPmsiTunnelAttributeTable. An entry of this table l2L3VpnMcastPmsiTunnelAttributeTable. An entry in this table
corresponds with 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 PE routers. The entry of the table will be used by other MIB
modules which are designed for monitoring and/or configuring both modules which are designed for monitoring and/or configuring both
L2 and L3 VPN that support multicast. L2 and L3 VPN that support multicast.
The table index is composed of multiple attributes that depend on The table index is composed of multiple attributes that depend on
the tunnel type and uniquely identify a tunnel. the tunnel type and uniquely identify a tunnel.
The table may also be used in conjunction with other MIBs, such as The table may also be used in conjunction with other MIBs, such as
MPLS Traffic Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to MPLS Traffic Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to
obtain the other details of a tunnel by following the row pointer obtain the other details of a tunnel by following the row pointer
of the corresponding tunnel's row in this table. It may also be of the corresponding tunnel's row in this table. It may also be
used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863] used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863]
to obtain the other details of a corresponding interface that to obtain the other details of a corresponding interface that
tunnel uses by following the row pointer of the corresponding tunnel uses by following the row pointer of the corresponding
tunnel's row in this table. tunnel's row in this table.
4. Definitions 4. Definitions
skipping to change at page 5, line 11 skipping to change at page 5, line 18
of the corresponding tunnel's row in this table. It may also be of the corresponding tunnel's row in this table. It may also be
used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863] used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863]
to obtain the other details of a corresponding interface that to obtain the other details of a corresponding interface that
tunnel uses by following the row pointer of the corresponding tunnel uses by following the row pointer of the corresponding
tunnel's row in this table. 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 "201702211200Z" -- 21th February, 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 textual conventions for "This MIB module contains a textual convention for
Border Gateway Protocol/MultiProtocol Label Border Gateway Protocol/MultiProtocol Label
Switching (BGP/MPLS) Layer 2 (L2) and Layer 3 Switching (BGP/MPLS) Layer 2 (L2) and Layer 3
(L3) VPN (Virtual Private Network). (L3) Virtual Private Network (VPN).
Copyright (C) The Internet Society (2017)." Copyright (C) The Internet Society (2017)."
-- Revision history. -- Revision history.
REVISION "201702211200Z" -- 21th February, 2017 REVISION "201702211200Z" -- 21th February, 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.
-- 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
"Types of provider tunnels used for multicast in "This textual convention enumerates the values
BGP/MPLS L2 or L3 VPN." representing a type of a provider tunnel
REFERENCE used for multicast in BGP/MPLS L2 or L3 VPN.
"RFC6514, Section 5" These labelled numbers are aligned based on the definition
SYNTAX INTEGER of Tunnel types in Section 5 of [RFC6514].
{ noTunnelId (0), -- No tunnel information present "
rsvpP2mp (1), -- RSVP-TE P2MP LSP REFERENCE
ldpP2mp (2), -- mLDP P2MP LSP "RFC6514, Section 5"
pimSsm (3), -- PIM-SSM Tree SYNTAX INTEGER
pimAsm (4), -- PIM-SM Tree { noTunnelId (0), -- No tunnel information present
pimBidir (5), -- BIDIR-PIM Tree rsvpP2mp (1), -- RSVP-TE P2MP LSP
ingressReplication (6), -- Ingress Replication ldpP2mp (2), -- mLDP P2MP LSP
ldpMp2mp (7) -- mLDP MP2MP LSP pimSsm (3), -- PIM-SSM Tree
} pimAsm (4), -- PIM-SM Tree
pimBidir (5), -- BIDIR-PIM Tree
ingressReplication (6), -- Ingress Replication
ldpMp2mp (7) -- mLDP MP2MP LSP
}
END L2L3VpnMcastProviderTunnelPointer ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a pointer to the row pertaining
to a table entry that represents a
provider tunnel used for multicast in BGP/MPLS L2 or L3 VPN.
An L2L3VpnMcastProviderTunnelPointer value is always
interpreted within the context of an
L2L3VpnMcastProviderTunnelPointerType value.
Every usage of the L2L3VpnMcastProviderTunnelPointer
textual convention MUST specify the
L2L3VpnMcastProviderTunnelPointerType object which
provides the context.
Furthermore, MIB authors SHOULD define a separate
L2L3VpnMcastProviderTunnelPointerType object for each
L2L3VpnMcastProviderTunnelPointer object.
The L2L3VpnMcastProviderTunnelPointerType object which
defines the context must be registered immediately before
the object which uses the L2L3VpnMcastProviderTunnelPointer
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
L2L3VpnMcastProviderTunnelPointerType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention enumerates the types of
tables having the row that an L2L3VpnMcastProviderTunnelPointer
object points to.
The row pertains to the entry that represents a
provider tunnel used for multicast in BGP/MPLS
L2 or L3 VPN.
The enumerated values have the following meaning:
null(0)
A pointer is null.
pointerToMplsTunnelTable(1)
A pointer points to the row in mplsTunnelTable defined in
[RFC3812].
pointerToTunnelIfTableForGRE(2)
A pointer points to the row in tunnelIfTable defined in
[RFC4087] for GRE tunnel.
"
REFERENCE
"RFC3812, RFC4087"
SYNTAX INTEGER
{ null (0), -- A pointer is null.
pointerToMplsTunnelTable (1), -- A pointer to the row
-- in mplsTunnelTable
pointerToTunnelIfTableForGRE (2) -- A pointer to the row
-- in tunnelIfTable
-- for GRE tunnel
}
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 IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2 MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
RowPointer RowPointer
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB -- [RFC3811] FROM MPLS-TC-STD-MIB -- [RFC3811]
L2L3VpnMcastProviderTunnelType L2L3VpnMcastProviderTunnelType,
L2L3VpnMcastProviderTunnelPointerType,
L2L3VpnMcastProviderTunnelPointer
FROM L2L3-VPN-MCAST-TC-MIB; FROM L2L3-VPN-MCAST-TC-MIB;
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201702211200Z" -- 21th February, 2017 LAST-UPDATED "201702211200Z" -- 21th February, 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
skipping to change at page 7, line 32 skipping to change at page 9, line 18
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 will be used by other MIB modules designed for "This MIB module will be used by other MIB modules designed for
managing multicast in Layer 2 (L2) VPNs [RFC7117] and monitoring and/or configuring both Layer 2 (L2) and
Layer 3 (L3) VPNs [RFC6513], [RFC6514]. Layer 3 (L3) Virtual Private Networks (VPN) that support
multicast.
Copyright (C) The Internet Society (2017)." Copyright (C) The Internet Society (2017)."
-- Revision history. -- Revision history.
REVISION "201702211200Z" -- 21th February, 2017 REVISION "201702211200Z" -- 21th February, 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
skipping to change at page 8, line 7 skipping to change at page 9, line 43
-- IANA Reg.: Please assign a value for "BBBB" under the -- IANA Reg.: Please assign a value for "BBBB" 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.
-- 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 "BBBB" here with the assigned value and -- replace "BBBB" here with the assigned value and
-- remove this note. -- remove this note.
-- Top level components of this MIB. -- Top level components of this MIB.
l2L3VpnMcastObjects OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastStates OBJECT IDENTIFIER l2L3VpnMcastStates OBJECT IDENTIFIER
::= { l2L3VpnMcastObjects 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 of this table corresponds with a "An entry of this table corresponds to a
PMSI Tunnel attribute and is created by a PE router PMSI Tunnel attribute and is created by a PE router
that advertises and receives the attribute. that advertises and receives the attribute.
The entry in the table will be referred by other MIB modules The entry in the table will be referred by other MIB modules
which are designed for monitoring and/or configuring which are designed for monitoring and/or configuring
both L2 and L3 VPN that support multicast." both L2 and L3 VPN that support multicast."
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastStates 1 } ::= { l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
skipping to change at page 9, line 11 skipping to change at page 10, line 45
L2L3VpnMcastPmsiTunnelAttributeEntry ::= L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE { SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeFlags l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING, OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel, MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
OCTET STRING, OCTET STRING,
l2L3VpnMcastPmsiTunnelPointerType
L2L3VpnMcastProviderTunnelPointerType,
l2L3VpnMcastPmsiTunnelPointer l2L3VpnMcastPmsiTunnelPointer
RowPointer, L2L3VpnMcastProviderTunnelPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
RowPointer RowPointer
} }
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX OCTET STRING (SIZE (1))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the Flags field in a PMSI Tunnel attribute "Denotes the Flags field in a PMSI Tunnel attribute
with the following format. with the following format.
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| reserved |L| | reserved |L|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
L: Leaf Information Required L: Leaf Information Required
When BGP-based I/S-PMSI signaling is used, the value of When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the Flags field in this object corresponds to the Flags field in
an advertised/received I/S-PMSI auto-discovery (A-D) route. an advertised/received I/S-PMSI auto-discovery (A-D) route.
When UDP-based S-PMSI signaling is used, the value of When UDP-based S-PMSI signaling is used, the value of
this object is zero." this object is zero."
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the Tunnel Type field that identifies "Denotes the Tunnel Type field that identifies
the type of the tunneling technology used to the type of the tunneling technology used to
establish the provider tunnel, in a PMSI Tunnel establish the provider tunnel, in a PMSI Tunnel
attribute. attribute.
When BGP-based I/S-PMSI signaling is used, the value of When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the Tunnel Type field in this object corresponds to the Tunnel Type field in
an advertised/received I/S-PMSI A-D route. an advertised/received I/S-PMSI A-D route.
When UDP-based S-PMSI signaling is used, the value of When UDP-based S-PMSI signaling is used, the value of
this object will be one of pimAsm (3), pimSsm (4), or this object will be one of pimAsm (3), pimSsm (4), or
pimBidir (5)." pimBidir (5)."
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
SYNTAX MplsLabel SYNTAX MplsLabel
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the MPLS Label field that contains "Denotes the MPLS Label field that contains
an MPLS label, in a PMSI Tunnel attribute. an MPLS label, in a PMSI Tunnel attribute.
When BGP-based I/S-PMSI signaling is used, the value of When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the MPLS Label field in this object corresponds to the MPLS Label field in
an advertised/received I/S-PMSI A-D route. an advertised/received I/S-PMSI A-D route.
When UDP-based S-PMSI signaling is used, the value of When UDP-based S-PMSI signaling is used, the value of
this object is zero that indicates absence of MPLS this object is zero that indicates absence of MPLS
Label." Label."
REFERENCE REFERENCE
"RFC6514, Section 5" "RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
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) )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes the Tunnel Identifier field that uniquely "Denotes the Tunnel Identifier field that uniquely
identifies a created tunnel, in a PMSI Tunnel identifies a created tunnel, in a PMSI Tunnel
attribute. attribute.
The size of the identifier depends on address family The size of the identifier depends on the address family
(IPv4 or IPv6) and the value of (IPv4 or IPv6) and the value of
l2L3VpnMcastPmsiTunnelAttributeType, i.e., the type of l2L3VpnMcastPmsiTunnelAttributeType, i.e., the type of
the tunneling technology used to establish the provider the tunneling technology used to establish the provider
tunnel. 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.
Size (in octets) l2L3VpnMcastPmsiTunnelAttributeType Size (in octets) l2L3VpnMcastPmsiTunnelAttributeType
IPv4 IPv6 (tunneling technology) IPv4 IPv6 (tunneling technology)
skipping to change at page 11, line 17 skipping to change at page 13, line 4
12 24 rsvpP2mp (RSVP-TE P2MP LSP) 12 24 rsvpP2mp (RSVP-TE P2MP LSP)
17 29 ldpP2mp (mLDP P2MP LSP) 17 29 ldpP2mp (mLDP P2MP LSP)
8 32 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)
4 16 ingressReplication 4 16 ingressReplication
(Ingress Replication) (Ingress Replication)
17 29 ldpMp2mp (mLDP MP2MP LSP) 17 29 ldpMp2mp (mLDP MP2MP LSP)
When l2L3VpnMcastPmsiTunnelAttributeType is set to When l2L3VpnMcastPmsiTunnelAttributeType is set to
noTunnelId, the PMSI Tunnel attribute does not have noTunnelId(0), the PMSI Tunnel attribute does not have
tunnel information. Thus, the size of this object is zero. tunnel information. Thus, the size of this object is zero.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When l2L3VpnMcastPmsiTunnelAttributeType is set to
rsvpP2mp, the Tunnel Identifier is composed of rsvpP2mp(1), the Tunnel Identifier is composed of
Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6), Extended Tunnel ID (4 octets in IPv4, 16 octets in IPv6),
Reserved (2 octets), Tunnel ID (2 octets), and Reserved (2 octets), Tunnel ID (2 octets), and
P2MP ID (4 octets). Thus, the size of this object is P2MP ID (4 octets). Thus, the size of this object is
12 octets in IPv4 and 24 octets in IPv6. 12 octets in IPv4 and 24 octets in IPv6.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When l2L3VpnMcastPmsiTunnelAttributeType is set to
ldpP2mp, the Tunnel Identifier is a 17 octets ldpP2mp(2), the Tunnel Identifier is 17 octets
(in IPv4) or 29 octets (in IPv6) P2MP Forwarding (in IPv4) or 29 octets (in IPv6) P2MP Forwarding
Equivalence Class (FEC) Element. Equivalence Class (FEC) Element.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When l2L3VpnMcastPmsiTunnelAttributeType is set to
pimSsm, PimAsm, or PimBidir, the Tunnel Identifier is pimSsm(3), PimAsm(4), or PimBidir(5), the Tunnel Identifier is
a pair of source and group IP addresses. a pair of source and group IP addresses.
Thus, the size of this object is 16 octets in IPv4 Thus, the size of this object is 16 octets in IPv4
and 32 octets in IPv6. and 32 octets in IPv6.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When l2L3VpnMcastPmsiTunnelAttributeType is set to
ingressReplication, the Tunnel Identifier is ingressReplication(6), the Tunnel Identifier is
the unicast tunnel endpoint IP address of the local the unicast tunnel endpoint IP address of the local
PE. Thus, the size of this object is 4 octets in IPv4 PE. Thus, the size of this object is 4 octets in IPv4
and 16 octets in IPv6. and 16 octets in IPv6.
When l2L3VpnMcastPmsiTunnelAttributeType is set to When l2L3VpnMcastPmsiTunnelAttributeType is set to
ldpMp2mp, the Tunnel Identifier is a 17 octets ldpMp2mp(7), the Tunnel Identifier is 17 octets
(in IPv4) or 29 octets (in IPv6) MP2MP FEC Element. (in IPv4) or 29 octets (in IPv6) MP2MP FEC Element.
When BGP-based I/S-PMSI signaling is used, the value of When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the the Tunnel this object corresponds to the Tunnel
Identifier field in an advertised/received I/S-PMSI Identifier field in an advertised/received I/S-PMSI
A-D route. Thus, the size of this object is determined A-D route. Thus, the size of this object is determined
by the above table. by the above table.
When UDP-based S-PMSI signaling is used, the value of When UDP-based S-PMSI signaling is used, the value of
this object is a pair of source and group IP addresses. this object is a pair of source and group IP addresses.
Thus, the size of this object is 16 octets in IPv4 Thus, the size of this object is 16 octets in IPv4
and 32 octets in IPv6." and 32 octets in IPv6."
REFERENCE REFERENCE
"RFC6514, Section 5 "RFC6514, Section 5
RFC4875, Section 19.1 RFC4875, Section 19.1
RFC6388, Section 2.2 and 2.3" RFC6388, Section 2.2 and 2.3"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE l2L3VpnMcastPmsiTunnelPointerType OBJECT-TYPE
SYNTAX RowPointer SYNTAX L2L3VpnMcastProviderTunnelPointerType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId "The type of l2L3VpnMcastPmsiTunnelPointer.
The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId
may be represented as an entry in other table, e.g, may be represented as an entry in other table, e.g,
mplsTunnelTable [RFC3812]. If there is such entry, mplsTunnelTable [RFC3812]. This object specifies
this object will point to the row pertaining to the entry. the type of pointer to the row pertaining to the entry.
Otherwise, the pointer is null."
If such an entry does not exist, the value of this object
becomes null(0).
"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The pointer to a table entry representing the tunnel
identified by l2L3VpnMcastPmsiTunnelAttributeId.
The type of this pointer is specified with
the corresponding instance of the
l2L3VpnMcastPmsiTunnelPointerType object.
If the value of the corresponding instance of the
l2L3VpnMcastPmsiTunnelPointerType is null(0),
the value of this object MUST be null.
"
::= { 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, the pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } ::= { 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
skipping to change at page 13, line 16 skipping to change at page 15, line 25
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,
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
skipping to change at page 13, line 43 skipping to change at page 16, line 6
Some of the readable objects in this MIB module (i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to 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 l2L3VpnMcastPmsiTunnelPointer and l2L3VpnMcastPmsiTunnelIf in
l2L3VpnMcastPmsiTunnelAttributeTable will point the corresponding l2L3VpnMcastPmsiTunnelAttributeTable will point to the
entry of in other table containing configuration and/or corresponding entries in other tables containing configuration
performance information of a tunnel and an interface. If an and/or performance information of a tunnel and an interface. If
Administrator does not want to reveal this information, then these an Administrator does not want to reveal this information, then
objects should be considered sensitive/vulnerable. 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
 End of changes. 52 change blocks. 
113 lines changed or deleted 219 lines changed or added

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