draft-ietf-bess-l2l3-vpn-mcast-mib-05.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-06.txt 
BESS 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: June 4, 2017 Tohoku Institute of Technology Expires: August 25, 2017 Tohoku Institute of Technology
December 01, 2016 February 21, 2017
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-05 draft-ietf-bess-l2l3-vpn-mcast-mib-06
Abstract Abstract
This memo defines a portion of the Management Information Base for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community. In for use with network management protocols in the Internet community.
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 L2 modules which are designed for monitoring and/or configuring both
and L3 VPN Multicast. Layer 2 and Layer 3 Virtual Private Networks (VPN) that support
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 June 4, 2017. This Internet-Draft will expire on August 25, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . 4
3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 3 3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 4
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4.2. L2L3-VPN-MCAST-MIB Object Definitions . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . 10 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . 14
7.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
Multicast in BGP/MPLS Layer 3 (L3) and Layer 2 (L2) VPN (referred to [RFC7117] and [RFC6513] specify procedures for supporting multicast
as MVPN and L2 VPN Multicast, respectively) can be achieved by using in Border Gateway Protocol/MultiProtocol Label Switching (BGP/MPLS)
provider tunnels to deliver to all or a subset of Provider Edges Layer 2 (L2) and Layer 3 (L3) VPN (Virtual Private Network),
(PEs). An example of L2 VPN is Virtual Private LAN Service (VPLS). respectively.
The signaling of provider tunnel choice is very similar for both
cases, and this memo describes managed objects common to both VPLS Multicast service in BGP/MPLS L2 and L3 VPN can be achieved by using
Multicast [RFC7117] and MVPN [RFC6513], [RFC6514]. various kinds of transport mechanism for forwarding a packet to all
or a subset of Provider Edge routers (PEs) across service provider
networks. Such transport mechanisms are referred to as provider
tunnels (P-tunnels).
The signaling of P-tunnel choice is very similar for multicast in
both L2 and L3 VPNs. [RFC7117] and [RFC6513] describe BGP-based
mechanisms for Virtual Private LAN Service (VPLS) and Multicast VPN
(MVPN), respectively. [RFC6514] defines the Provider Multicast
Service Interface (PMSI) tunnel attribute, a BGP attribute that
specifies information of a P-tunnel. The PMSI tunnel attribute is
advertised/received by PEs in BPG auto-discovery (A-D) routes.
[RFC6513] also proposes a UDP-based signaling mechanism.
This document defines a textual conventions (TC) that can be used to
represent types of P-tunnels used for multicast in BGP/MPLS L2 or L3
VPN within MIB module specifications.
This document also describes common managed objects used by other MIB
modules which are designed for monitoring and/or configuring both L2
and L3 VPN that support multicast.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
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, L3 VPN, MVPN
concepts and/or mechanisms is assumed. Some of the terms are listed (Multicast VPN) concepts and/or mechanisms is assumed. Some terms
below. specifically related to this document are explained below.
o PMSI: P-Multicast Service Interface - a conceptual interface for a The term "Multicast VPN (MVPN)" [RFC6513] refers to a BGP/MPLS L3
PE to send customer multicast traffic to all or some PEs in the (IP) VPN service that supports multicast.
same VPN.
o I-PMSI: Inclusive PMSI - to all PEs in the same VPN. "Provider Multicast Service Interface (PMSI)" [RFC6513] is a
conceptual interface instantiated by a P-tunnel, a transport
mechanism used to deliver multicast traffic. A PE uses to send
customer multicast traffic to all or some PEs in the same VPN.
o S-PMSI: Selective PMSI - to some of the PEs in the same VPN. 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
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
particular MVPN to transmit a message to some of the PEs in the same
VPN.
Throughout this document, we will use the term "I/S-PMSI" to refer
both "I-PMSI" and "S-PMSI".
[RFC6513] describes following tunnel setup techniques that can be
used to create the P-tunnels that instantiate the PMSIs.
o Protocol Independent Multicast tree
* Sparse Mode (PIM-SM) tree [RFC4601]
* Source Specific Multicast (PIM-SSM) tree [RFC4601]
* Bidirectional Protocol Independent Multicast (BIDIR-PIM) tree
[RFC5015]
o Label Distribution Protocol Extension for Multipoint Label
Switched Paths (mLDP) [RFC6388]
* Point-to-MultiPoint (mLDP P2MP)
* Point-to-MultiPoint (mLDP MP2MP)
o Resource Reservation Protocol - Traffic Engineering Point-to-
Multipoint (RSVP-TE P2MP) Label Switched Path [RFC4875]
o Ingress Replication through Unicast Tunnels [RFC6513]
A created tunnel will be identified by Tunnel Identifier. The length
of the identifier differs depending on the setup technique that is
used to create 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 Module
L2L3-VPN-MCAST-MIB contains a Textual Convention This document defines two MIB modules: L2L3-VPN-MCAST-TC-MIB and
L2L3VpnMcastProviderTunnelType, and a L2L3-VPN-MCAST-MIB.
l2L3VpnMcastPmsiTunnelAttributeTable. The table is for PMSI Tunnel
Attributes (PTAs) advertised/received in I/S-PMSI Auto-Discovery o L2L3-VPN-MCAST-TC-MIB contains a Textual Convention
routes. Other MIB objects (e.g., mvpnMIB in [I-D.ietf-bess-mvpn- L2L3VpnMcastProviderTunnelType that provides an enumeration of the
mib]) may use the L2L3VpnMcastProviderTunnelType and/or point to provider tunnel types.
entries in the l2L3VpnMcastPmsiTunnelAttributeTable.
o L2L3-VPN-MCAST-MIB defines a table
l2L3VpnMcastPmsiTunnelAttributeTable. An entry of this table
corresponds with a PMSI Tunnel Attribute (PTA) advertised/received
by PE routers. The entry of the table will be used by other MIB
modules which are designed for monitoring and/or configuring both
L2 and L3 VPN that support multicast.
The table index is composed of multiple attributes that depend on
the tunnel type and uniquely identify a tunnel.
The table may also be used in conjunction with other MIBs, such as
MPLS Traffic Engineering MIB (MPLS-TE-STD-MIB) [RFC3812], to
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
used in conjunction with Interfaces Group MIB (IF-MIB) [RFC2863]
to obtain the other details of a corresponding interface that
tunnel uses by following the row pointer of the corresponding
tunnel's row in this table.
4. Definitions 4. Definitions
L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN 4.1. L2L3-VPN-MCAST-TC-MIB Object Definitions
L2L3-VPN-MCAST-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP TEXTUAL-CONVENTION
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-TC; -- [RFC2579]
TEXTUAL-CONVENTION, RowPointer
FROM SNMPv2-TC -- [RFC2579]
MplsLabel
FROM MPLS-TC-STD-MIB; -- [RFC3811]
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastTCMIB MODULE-IDENTITY
LAST-UPDATED "201611301200Z" -- 30th November, 2016 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
Comments and discussion to bess@ietf.org" 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 DESCRIPTION
"This MIB module will be used by other MIB modules designed for "This MIB module contains textual conventions for
managing multicast in Layer 2 (L2) VPNs [RFC7117] and Border Gateway Protocol/MultiProtocol Label
Layer 3 (L3) VPNs [RFC6513], [RFC6514]. Switching (BGP/MPLS) Layer 2 (L2) and Layer 3
Copyright (C) The Internet Society (2016)." (L3) VPN (Virtual Private Network).
Copyright (C) The Internet Society (2017)."
-- Revision history. -- Revision history.
REVISION "201611301200Z" -- 30th November, 2016 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 YYYY } ::= { mib-2 AAAA }
-- IANA Reg.: Please assign a value for "YYYY" 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 "YYYY" 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 "Types of provider tunnels used for multicast in
BGP/MPLS L2 or L3 VPN." BGP/MPLS L2 or L3 VPN."
REFERENCE REFERENCE
"Section 5, [RFC6514]" "RFC6514, Section 5"
SYNTAX INTEGER { noTunnelId (0), SYNTAX INTEGER
rsvpP2mp (1), { noTunnelId (0), -- No tunnel information present
ldpP2mp (2), rsvpP2mp (1), -- RSVP-TE P2MP LSP
pimAsm (3), ldpP2mp (2), -- mLDP P2MP LSP
pimSsm (4), pimSsm (3), -- PIM-SSM Tree
pimBidir (5), pimAsm (4), -- PIM-SM Tree
ingressReplication (6), pimBidir (5), -- BIDIR-PIM Tree
ldpMp2mp (7) ingressReplication (6), -- Ingress Replication
} ldpMp2mp (7) -- mLDP MP2MP LSP
}
-- Top level components of this MIB. END
l2L3VpnMcastObjects OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastConformance OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 2 }
l2L3VpnMcastStates OBJECT IDENTIFIER
::= { l2L3VpnMcastObjects 1 }
-- tables, scalars, conformance information 4.2. L2L3-VPN-MCAST-MIB Object Definitions
-- Table of PMSI Tunnel Attributes
l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN
SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is for PMSI Tunnel Attributes (PTAs)
advertised/received in I/S-PMSI Auto-Discovery
routes (A-D routes). The entries may be referred to by
I-PMSI or S-PMSI table entries defined in other MIBs,
e.g. mvpnMIB in [I-D.ietf-bess-mvpn-mib]."
REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE IMPORTS
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry MODULE-IDENTITY, OBJECT-TYPE, mib-2
MAX-ACCESS not-accessible FROM SNMPv2-SMI -- [RFC2578]
STATUS current
DESCRIPTION
"A conceptual row corresponding to a PTA
that is advertised/received on this router."
REFERENCE
"Section 5, [RFC6514]"
INDEX {
l2L3VpnMcastPmsiTunnelAttributeFlags,
l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeLabel,
l2L3VpnMcastPmsiTunnelAttributeId
}
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::= MODULE-COMPLIANCE, OBJECT-GROUP
SEQUENCE { FROM SNMPv2-CONF -- [RFC2580]
l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId
OCTET STRING,
l2L3VpnMcastPmsiTunnelPointer RowPointer
RowPointer, FROM SNMPv2-TC -- [RFC2579]
l2L3VpnMcastPmsiTunnelIf
RowPointer
}
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE MplsLabel
SYNTAX OCTET STRING (SIZE (1)) FROM MPLS-TC-STD-MIB -- [RFC3811]
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"For UDP-based S-PMSI signaling for Protocol Independent
Multicast - MVPN (PIM-MVPN), the value of this object is 0.
For BGP-based I/S-PMSI signaling, this is the Flags
field in PMSI Tunnel Attribute of the corresponding
I/S-PMSI A-D route with the following format and
one currently defined bit:
0 1 2 3 4 5 6 7 L2L3VpnMcastProviderTunnelType
+-+-+-+-+-+-+-+-+ FROM L2L3-VPN-MCAST-TC-MIB;
| reserved |L|
+-+-+-+-+-+-+-+-+
L: Leaf Information Required l2L3VpnMcastMIB MODULE-IDENTITY
" LAST-UPDATED "201702211200Z" -- 21th February, 2017
REFERENCE ORGANIZATION "IETF BESS Working Group."
"Section 5, [RFC6514]" CONTACT-INFO
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } " Zhaohui Zhang
Juniper Networks, Inc.
10 Technology Park Drive
Westford, MA 01886
USA
Email: zzhang@juniper.net
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE Hiroshi Tsunoda
SYNTAX L2L3VpnMcastProviderTunnelType Tohoku Institute of Technology
MAX-ACCESS not-accessible 35-1, Yagiyama Kasumi-cho
STATUS current Taihaku-ku, Sendai, 982-8577
DESCRIPTION Japan
"As defined for L2L3VpnMcastProviderTunnelType. Email: tsuno@m.ieice.org
For UDP-based S-PMSI signaling for PIM-MVPN,
this is pimAsm (3), pimSsm (4), or pimBidir (5).
For BGP-based I/S-PMSI signaling, this is the Tunnel Type
field in PMSI Tunnel Attribute of the corresponding
I/S-PMSI A-D or Leaf A-D route."
REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE Comments and discussion to bess@ietf.org"
SYNTAX MplsLabel DESCRIPTION
MAX-ACCESS not-accessible "This MIB module will be used by other MIB modules designed for
STATUS current managing multicast in Layer 2 (L2) VPNs [RFC7117] and
DESCRIPTION Layer 3 (L3) VPNs [RFC6513], [RFC6514].
"For UDP-based I/S-PMSI signaling for PIM-MVPN, this is 0. Copyright (C) The Internet Society (2017)."
For BGP-based I/S-PMSI signaling, this is the MPLS Label
field in PMSI Tunnel Attribute of the corresponding
I/S-PMSI A-D route."
REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE -- Revision history.
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Different tunnel types will have different sizes for
this object, as listed below:
Size l2L3VpnMcastPmsiTunnelAttributeType REVISION "201702211200Z" -- 21th February, 2017
(IPv4/IPv6) DESCRIPTION
-------------------------------------------------- "Initial version, published as RFC XXXX."
0/0 noTunnelId
12/24 rsvpP2mp
17/29 ldpP2mp
8/32 pimAsm
8/32 pimSsm
8/32 pimBidir
4/16 ingressReplication
17/29 ldpMp2mp
For UDP-based S-PMSI signaling for PIM-MVPN, the first -- RFC Ed. replace XXXX with actual RFC number and remove this note
8 or 32 octets of this attribute are filled with
the provider tunnel (source, group) IPv4/IPv6 addresses.
For BGP-based I/S-PMSI signaling, this is the Tunnel
Identifier field in PMSI Tunnel Attribute of the
corresponding I/S-PMSI A-D route."
REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE ::= { mib-2 BBBB }
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the tunnel exists in some MIB table, e.g. mplsTunnelTable
[RFC3812], this is the row pointer to it. Otherwise, the
pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE -- IANA Reg.: Please assign a value for "BBBB" under the
SYNTAX RowPointer -- 'mib-2' subtree and record the assignment in the SMI
MAX-ACCESS read-only -- Numbers registry.
STATUS current
DESCRIPTION
"If the tunnel has a corresponding entry in the ifXTable,
this object will point to the row pertaining to the entry
in the ifXTable. Otherwise, the pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
-- Conformance Information -- RFC Ed.: When the above assignment has been made, please
-- remove the above note
-- replace "BBBB" here with the assigned value and
-- remove this note.
l2L3VpnMcastGroups OBJECT IDENTIFIER -- Top level components of this MIB.
::= {l2L3VpnMcastConformance 1} l2L3VpnMcastObjects OBJECT IDENTIFIER
l2L3VpnMcastCompliances OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 }
::= {l2L3VpnMcastConformance 2} l2L3VpnMcastStates OBJECT IDENTIFIER
::= { l2L3VpnMcastObjects 1 }
l2L3VpnMcastConformance OBJECT IDENTIFIER
::= { l2L3VpnMcastMIB 2 }
-- Compliance Statements -- tables, scalars, conformance information
-- Table of PMSI Tunnel Attributes
l2L3VpnMcastCompliance MODULE-COMPLIANCE l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE
STATUS current SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
DESCRIPTION MAX-ACCESS not-accessible
"The compliance statement: no mandatory groups " STATUS current
MODULE -- this module DESCRIPTION
"An entry of this table corresponds with a
PMSI Tunnel attribute and is created by a PE router
that advertises and receives the attribute.
The entry in the table will be referred by other MIB modules
which are designed for monitoring and/or configuring
both L2 and L3 VPN that support multicast."
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastStates 1 }
GROUP l2L3VpnMcastOptionalGroup l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
DESCRIPTION SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
"This group is optional." MAX-ACCESS not-accessible
::= { l2L3VpnMcastCompliances 1 } STATUS current
DESCRIPTION
"A conceptual row corresponding to a PTA
that is advertised/received on this router."
REFERENCE
"RFC6514, Section 5"
INDEX {
l2L3VpnMcastPmsiTunnelAttributeFlags,
l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeLabel,
l2L3VpnMcastPmsiTunnelAttributeId
}
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
-- units of conformance L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId
OCTET STRING,
l2L3VpnMcastPmsiTunnelPointer
RowPointer,
l2L3VpnMcastPmsiTunnelIf
RowPointer
}
l2L3VpnMcastOptionalGroup OBJECT-GROUP l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
OBJECTS { SYNTAX OCTET STRING (SIZE (1))
l2L3VpnMcastPmsiTunnelPointer, MAX-ACCESS not-accessible
l2L3VpnMcastPmsiTunnelIf STATUS current
} DESCRIPTION
STATUS current "Denotes the Flags field in a PMSI Tunnel attribute
DESCRIPTION with the following format.
"Support of these objects is not required."
::= { l2L3VpnMcastGroups 1 }
END 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| reserved |L|
+-+-+-+-+-+-+-+-+
L: Leaf Information Required
When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the Flags field in
an advertised/received I/S-PMSI auto-discovery (A-D) route.
When UDP-based S-PMSI signaling is used, the value of
this object is zero."
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"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
this object corresponds with the Tunnel Type field in
an advertised/received I/S-PMSI A-D route.
When UDP-based S-PMSI signaling is used, the value of
this object will be one of pimAsm (3), pimSsm (4), or
pimBidir (5)."
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
SYNTAX MplsLabel
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Denotes the MPLS Label field that contains
an MPLS label, in a PMSI Tunnel attribute.
When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the MPLS Label field in
an advertised/received I/S-PMSI A-D route.
When UDP-based S-PMSI signaling is used, the value of
this object is zero that indicates absence of MPLS
Label."
REFERENCE
"RFC6514, Section 5"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
MAX-ACCESS not-accessible
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 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
is summarized below.
Size (in octets) l2L3VpnMcastPmsiTunnelAttributeType
IPv4 IPv6 (tunneling technology)
--------------------------------------------------
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
noTunnelId, the PMSI Tunnel attribute does not have
tunnel information. Thus, the size of this object is zero.
When l2L3VpnMcastPmsiTunnelAttributeType is set to
rsvpP2mp, the 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). Thus, the size of this object is
12 octets in IPv4 and 24 octets in IPv6.
When l2L3VpnMcastPmsiTunnelAttributeType is set to
ldpP2mp, the Tunnel Identifier is a 17 octets
(in IPv4) or 29 octets (in IPv6) P2MP Forwarding
Equivalence Class (FEC) Element.
When l2L3VpnMcastPmsiTunnelAttributeType is set to
pimSsm, PimAsm, or PimBidir, the Tunnel Identifier is
a pair of source and group IP addresses.
Thus, the size of this object is 16 octets in IPv4
and 32 octets in IPv6.
When l2L3VpnMcastPmsiTunnelAttributeType is set to
ingressReplication, the Tunnel Identifier is
the unicast tunnel endpoint IP address of the local
PE. Thus, the size of this object is 4 octets in IPv4
and 16 octets in IPv6.
When l2L3VpnMcastPmsiTunnelAttributeType is set to
ldpMp2mp, the Tunnel Identifier is a 17 octets
(in IPv4) or 29 octets (in IPv6) MP2MP FEC Element.
When BGP-based I/S-PMSI signaling is used, the value of
this object corresponds with the the Tunnel
Identifier field in an advertised/received I/S-PMSI
A-D route. Thus, the size of this object is determined
by the above table.
When UDP-based S-PMSI signaling is used, the value of
this object is a pair of source and group IP addresses.
Thus, the size of this object is 16 octets in IPv4
and 32 octets in IPv6."
REFERENCE
"RFC6514, Section 5
RFC4875, Section 19.1
RFC6388, Section 2.2 and 2.3"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId
may be represented as an entry in other table, e.g,
mplsTunnelTable [RFC3812]. If there is such entry,
this object will point to the row pertaining to the entry.
Otherwise, the pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 }
l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE
SYNTAX RowPointer
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the tunnel identified by l2L3VpnMcastPmsiTunnelAttributeId
has a corresponding entry in the ifXTable [RFC2863],
this object will point to the row pertaining to the entry
in the ifXTable. Otherwise, the pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
-- Conformance Information
l2L3VpnMcastGroups OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 1 }
l2L3VpnMcastCompliances OBJECT IDENTIFIER
::= { l2L3VpnMcastConformance 2 }
-- Compliance Statements
l2L3VpnMcastCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement: no mandatory groups "
MODULE -- this module
GROUP l2L3VpnMcastOptionalGroup
DESCRIPTION
"This group is optional."
::= { l2L3VpnMcastCompliances 1 }
-- units of conformance
l2L3VpnMcastOptionalGroup OBJECT-GROUP
OBJECTS {
l2L3VpnMcastPmsiTunnelPointer,
l2L3VpnMcastPmsiTunnelIf
}
STATUS current
DESCRIPTION
"Support of these objects is not required."
::= { l2L3VpnMcastGroups 1 }
END
5. Security Considerations 5. Security Considerations
This MIB contains some read-only objects that may be deemed senstive There are no management objects defined in this MIB module that have
by some though perhaps not all operators. Appropriate security a MAX-ACCESS clause of read-write and/or read-create. So, if this
procedures related to SNMP in general but not specific to this MIB MIB module is implemented correctly, then there is no risk that an
need to be implemented by concerned operators. intruder can alter or create any management objects of this MIB
module via direct SNMP SET operations.
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
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
o l2L3VpnMcastPmsiTunnelPointer and l2L3VpnMcastPmsiTunnelIf in
l2L3VpnMcastPmsiTunnelAttributeTable will point the corresponding
entry of in other table 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.
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
access and GET/SET (read/change/create/delete) the objects in this
MIB module.
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
6. IANA Considerations 6. IANA Considerations
IANA is requested to root MIB objects in the MIB module contained in IANA is requested to root MIB objects in the MIB module contained in
this document under the mib-2 subtree. this document under the mib-2 subtree.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/
RFC2578, April 1999, RFC2578, April 1999,
<http://www.rfc-editor.org/info/rfc2578>. <http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 58, RFC 2579, DOI 10.17487/RFC2579, April 1999,
<http://www.rfc-editor.org/info/rfc2579>. <http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Conformance Statements for SMIv2", Schoenwaelder, Ed., "Conformance Statements for SMIv2",
STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999,
<http://www.rfc-editor.org/info/rfc2580>. <http://www.rfc-editor.org/info/rfc2580>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000,
<http://www.rfc-editor.org/info/rfc2863>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/
RFC3414, December 2002,
<http://www.rfc-editor.org/info/rfc3414>.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau,
"Multiprotocol Label Switching (MPLS) Traffic Engineering
(TE) Management Information Base (MIB)", RFC 3812, DOI
10.17487/RFC3812, June 2004,
<http://www.rfc-editor.org/info/rfc3812>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, DOI 10.17487/
RFC3826, June 2004,
<http://www.rfc-editor.org/info/rfc3826>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD
78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <http://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>.
[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 10, line 13 skipping to change at page 16, line 23
<http://www.rfc-editor.org/info/rfc7117>. <http://www.rfc-editor.org/info/rfc7117>.
7.2. Informative References 7.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, DOI 10.17487/ Standard Management Framework", RFC 3410, DOI 10.17487/
RFC3410, December 2002, RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>. <http://www.rfc-editor.org/info/rfc3410>.
[I-D.ietf-bess-mvpn-mib] [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
Zhang, J., Asif, S., Green, A., Gulrajani, S., and P. "Protocol Independent Multicast - Sparse Mode (PIM-SM):
Jain, "MPLS/BGP Layer 3 VPN Multicast Management Protocol Specification (Revised)", RFC 4601, DOI 10.17487/
Information Base", draft-ietf-bess-mvpn-mib-02 (work in RFC4601, August 2006,
progress), March 2016. <http://www.rfc-editor.org/info/rfc4601>.
Authors' Addresses [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,
"Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, DOI 10.17487/RFC5015, October 2007,
<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
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
Hiroshi Tsunoda Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
 End of changes. 55 change blocks. 
253 lines changed or deleted 568 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/