draft-ietf-bess-l2l3-vpn-mcast-mib-04.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-05.txt 
L3 VPN Working Group Z. Zhang BESS Working Group Z. Zhang
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track May 18, 2016 Intended status: Standards Track H. Tsunoda
Expires: November 19, 2016 Expires: June 4, 2017 Tohoku Institute of Technology
December 01, 2016
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-04 draft-ietf-bess-l2l3-vpn-mcast-mib-05
Abstract Abstract
This memo defines a portion of the Management Information Base for This memo defines a portion of the Management Information Base for
use with network management protocols in the Internet community. In use with network management protocols in the Internet community. In
particular, it describes common managed objects used to configure particular, it describes common managed objects used by other MIB
and/or monitor both L2 and L3 VPN Multicast. modules which are designed for monitoring and/or configuring both L2
and L3 VPN 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 November 19, 2016. This Internet-Draft will expire on June 4, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 17 skipping to change at page 2, line 19
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . 2
3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 3 3. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 3
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
7.1. Normative References . . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . 9
7.2. Informative References . . . . . . . . . . . . . . . . . 10 7.2. Informative References . . . . . . . . . . . . . . . . . 10
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Multicast in BGP/MPLS Layer 3 (L3) and Layer 2 (L2) VPN (referred to Multicast in BGP/MPLS Layer 3 (L3) and Layer 2 (L2) VPN (referred to
MVPN and L2 VPN Multicast respectively) can be achieved by using as MVPN and L2 VPN Multicast, respectively) can be achieved by using
provider tunnels to deliver to all or a subset of Provider Edges provider tunnels to deliver to all or a subset of Provider Edges
(PEs). An example of L2 VPN is Virtual Private LAN Service (VPLS). (PEs). An example of L2 VPN is Virtual Private LAN Service (VPLS).
The signaling of provider tunnel choice is very similar for both The signaling of provider tunnel choice is very similar for both
cases, and this memo describes managed objects common to both VPLS cases, and this memo describes managed objects common to both VPLS
Multicast [RFC7117] and MVPN [RFC6513] [RFC6514]. Multicast [RFC7117] and MVPN [RFC6513], [RFC6514].
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, L3VPN, MVPN they refer to. Familiarity with Multicast, MPLS, L3 VPN, MVPN
concepts and/or mechanisms is assumed. Some of the terms are listed concepts and/or mechanisms is assumed. Some of the terms are listed
below. below.
o PMSI: P-Multicast Service Interface - a conceptual interface for a o PMSI: P-Multicast Service Interface - a conceptual interface for a
PE to send customer multicast traffic to all or some PEs in the PE to send customer multicast traffic to all or some PEs in the
same VPN. same VPN.
o I-PMSI: Inclusive PMSI - to all PEs in the same VPN. o I-PMSI: Inclusive PMSI - to all PEs in the same VPN.
o S-PMSI: Selective PMSI - to some of the PEs in the same VPN. o S-PMSI: Selective PMSI - to some of the PEs in the same VPN.
skipping to change at page 3, line 16 skipping to change at page 3, line 19
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 L2L3-VPN-MCAST-MIB contains a Textual Convention
L2L3VpnMcastProviderTunnelType, and a L2L3VpnMcastProviderTunnelType, and a
l2L3VpnMcastPmsiTunnelAttributeTable. The table is for PMSI Tunnel l2L3VpnMcastPmsiTunnelAttributeTable. The table is for PMSI Tunnel
Attributes (PTAs) advertised/received in I/S-PSMI Auto-Discovery Attributes (PTAs) advertised/received in I/S-PMSI Auto-Discovery
routes. Other MIB objects (e.g., mvpnMIB in [I-D.ietf-bess-mvpn- routes. Other MIB objects (e.g., mvpnMIB in [I-D.ietf-bess-mvpn-
mib]) may use the L2L3VpnMcastProviderTunnelType and/or point to mib]) may use the L2L3VpnMcastProviderTunnelType and/or point to
entries in the l2L3VpnMcastPmsiTunnelAttributeTable. entries in the l2L3VpnMcastPmsiTunnelAttributeTable.
4. Definitions 4. Definitions
L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental
FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF -- [RFC2580]
TEXTUAL-CONVENTION, RowPointer
FROM SNMPv2-TC -- [RFC2579]
MplsLabel IMPORTS
FROM MPLS-TC-STD-MIB; -- [RFC3811] MODULE-IDENTITY, OBJECT-TYPE, mib-2
FROM SNMPv2-SMI -- [RFC2578]
l2L3VpnMcastMIB MODULE-IDENTITY MODULE-COMPLIANCE, OBJECT-GROUP
LAST-UPDATED "201310141200Z" -- October 14, 2013 FROM SNMPv2-CONF -- [RFC2580]
ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO
" Zhaohui Zhang
Juniper Networks, Inc.
10 Technology Park Drive
Westford, MA 01886
USA
Email: zzhang@juniper.net
Comments and discussion to bess@ietf.org" TEXTUAL-CONVENTION, RowPointer
FROM SNMPv2-TC -- [RFC2579]
DESCRIPTION MplsLabel
"This MIB contains common managed object definitions for FROM MPLS-TC-STD-MIB; -- [RFC3811]
multicast in Layer 2 and Layer 3 VPNs, defined by
[RFC7117] and [RFC6513] [RFC6514] respectively.
Copyright (C) The Internet Society (2013)."
-- Revision history. l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201611301200Z" -- 30th November, 2016
ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO
" Zhaohui Zhang
Juniper Networks, Inc.
10 Technology Park Drive
Westford, MA 01886
USA
Email: zzhang@juniper.net
REVISION "201310141200Z" -- 14 October 2013 12:00:00 GMT Comments and discussion to bess@ietf.org"
DESCRIPTION
"Initial version, published as RFC yyyy."
-- RFC Ed. replace yyyy with actual RFC number and remove this note DESCRIPTION
"This MIB module will be used by other MIB modules designed for
managing multicast in Layer 2 (L2) VPNs [RFC7117] and
Layer 3 (L3) VPNs [RFC6513], [RFC6514].
Copyright (C) The Internet Society (2016)."
::= { experimental 999 } -- Revision history.
-- RFC Ed.: replace 999 with IANA-assigned number and REVISION "201611301200Z" -- 30th November, 2016
-- replace experimental with the subtree under which the module DESCRIPTION
-- will be registered. "Initial version, published as RFC XXXX."
-- Please also remove the ", experimental" text from earlier
-- IMPORTS section.
-- Texual convention -- RFC Ed. replace XXXX with actual RFC number and remove this note
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION ::= { mib-2 YYYY }
STATUS current
DESCRIPTION
"Types of provider tunnels used for multicast in
BGP/MPLS L2 or L3 VPN. Additional types may be defined
in future RFCs, and those will be allowed as
valid types for L2L3VpnMcastProviderTunnelType."
REFERENCE
"Section 5, [RFC6514]"
SYNTAX INTEGER { noTunnelId (0),
rsvpP2mp (1),
ldpP2mp (2),
pimAsm (3),
pimSsm (4),
pimBidir (5),
ingressReplication (6),
ldpMp2mp (7)
}
-- Top level components of this MIB. -- IANA Reg.: Please assign a value for "YYYY" under the
-- tables, scalars, conformance information -- 'mib-2' subtree and record the assignment in the SMI
-- Numbers registry.
l2L3VpnMcastObjects OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 } -- RFC Ed.: When the above assignment has been made, please
l2L3VpnMcastConformance OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 2 } -- remove the above note
l2L3VpnMcastStates OBJECT IDENTIFIER ::= { l2L3VpnMcastObjects 1 } -- replace "YYYY" here with the assigned value and
-- remove this note.
-- Table of PMSI Tunnel Attributes -- Textual convention
l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION
SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry STATUS current
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION DESCRIPTION
"This table is for PMSI Tunnel Attributes (PTAs) "Types of provider tunnels used for multicast in
advertised/received in I/S-PSMI Auto-Discovery routes. BGP/MPLS L2 or L3 VPN."
The entries may be referred to by I-PMSI or S-PMSI table REFERENCE
entries defined in other MIBs, e.g. mvpnMIB in
[I-D.ietf-bess-mvpn-mib]."
REFERENCE
"Section 5, [RFC6514]" "Section 5, [RFC6514]"
::= {l2L3VpnMcastStates 1 } SYNTAX INTEGER { noTunnelId (0),
rsvpP2mp (1),
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE ldpP2mp (2),
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry pimAsm (3),
MAX-ACCESS not-accessible pimSsm (4),
STATUS current pimBidir (5),
DESCRIPTION ingressReplication (6),
"An entry in this table corresponds to a PTA ldpMp2mp (7)
that is advertised/received on this router. }
For BGP-based signaling (for I-PMSI via auto-discovery
procedure, or for S-PMSI via S-PMSI A-D routes),
they are just as signaled by BGP.
For UDP-based S-PMSI signaling for PIM-MVPN,
they're derived from the S-PMSI Join Message.
Note that BGP-based signaling may be used for -- Top level components of this MIB.
PIM-MVPN as well." l2L3VpnMcastObjects OBJECT IDENTIFIER
REFERENCE ::= { l2L3VpnMcastMIB 1 }
"Section 5, [RFC6514]; Section 7.4.2, [RFC6513]" l2L3VpnMcastConformance OBJECT IDENTIFIER
INDEX { ::= { l2L3VpnMcastMIB 2 }
l2L3VpnMcastPmsiTunnelAttributeFlags, l2L3VpnMcastStates OBJECT IDENTIFIER
l2L3VpnMcastPmsiTunnelAttributeType, ::= { l2L3VpnMcastObjects 1 }
l2L3VpnMcastPmsiTunnelAttributeLabel,
l2L3VpnMcastPmsiTunnelAttributeId
}
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::= SEQUENCE { -- tables, scalars, conformance information
l2L3VpnMcastPmsiTunnelAttributeFlags OCTET STRING, -- Table of PMSI Tunnel Attributes
l2L3VpnMcastPmsiTunnelAttributeType L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId OCTET STRING,
l2L3VpnMcastPmsiTunnelPointer RowPointer,
l2L3VpnMcastPmsiTunnelIf RowPointer
}
l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeTable OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1)) SYNTAX SEQUENCE OF L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For UDP-based S-PMSI signaling for PIM-MVPN, this is 0. "This table is for PMSI Tunnel Attributes (PTAs)
For BGP-based I/S-PMSI signaling, this is the Flags advertised/received in I/S-PMSI Auto-Discovery
field in PMSI Tunnel Attribute of the corresponding routes (A-D routes). The entries may be referred to by
I/S-PMSI A-D route with the following format and I-PMSI or S-PMSI table entries defined in other MIBs,
one currently defined bit: e.g. mvpnMIB in [I-D.ietf-bess-mvpn-mib]."
REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastStates 1 }
0 1 2 3 4 5 6 7 l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
+-+-+-+-+-+-+-+-+ SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
| reserved |L| MAX-ACCESS not-accessible
+-+-+-+-+-+-+-+-+ 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 }
L: Leaf Information Required L2L3VpnMcastPmsiTunnelAttributeEntry ::=
SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeFlags
OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType
L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel
MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId
OCTET STRING,
More bits may be defined in the future and l2L3VpnMcastPmsiTunnelPointer
they will be registered in IANA Registry xxxx." RowPointer,
REFERENCE l2L3VpnMcastPmsiTunnelIf
"Section 5, [RFC6514]; RowPointer
IANA Registry xxxx" }
-- RFC Ed. replace xxxx with the actual registry name l2L3VpnMcastPmsiTunnelAttributeFlags OBJECT-TYPE
-- that is being created via [I-D.ietf-bess-mvpn-mib] SYNTAX OCTET STRING (SIZE (1))
-- and remove this note. 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:
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 } 0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
| reserved |L|
+-+-+-+-+-+-+-+-+
l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE L: Leaf Information Required
SYNTAX L2L3VpnMcastProviderTunnelType "
MAX-ACCESS not-accessible REFERENCE
STATUS current "Section 5, [RFC6514]"
DESCRIPTION ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 1 }
"As defined for L2L3VpnMcastProviderTunnelType.
For UDP-based S-PMSI signaling for PIM-MVPN,
this is pim-asm (3), pim-ssm (4), or pim-bidir (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 l2L3VpnMcastPmsiTunnelAttributeType OBJECT-TYPE
SYNTAX MplsLabel SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For UDP-based I/S-PMSI signaling for PIM-MVPN, this is 0. "As defined for L2L3VpnMcastProviderTunnelType.
For BGP-based I/S-PMSI signaling, this is the MPLS Label For UDP-based S-PMSI signaling for PIM-MVPN,
field in PMSI Tunnel Attribute of the corresponding this is pimAsm (3), pimSsm (4), or pimBidir (5).
I/S-PMSI A-D route." For BGP-based I/S-PMSI signaling, this is the Tunnel Type
REFERENCE field in PMSI Tunnel Attribute of the corresponding
"Section 5, [RFC6514]" I/S-PMSI A-D or Leaf A-D route."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 2 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeLabel OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (0|4|8|12|17|24|29) ) SYNTAX MplsLabel
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Different tunnel types will have different sizes for "For UDP-based I/S-PMSI signaling for PIM-MVPN, this is 0.
this object, as listed below: 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 }
IPv4/IPv6 l2L3VpnMcastPmsiTunnelAttributeType l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
------------------------------------------------- SYNTAX OCTET STRING ( SIZE (0|4|8|12|16|17|24|29|32) )
0/0 noTunnelId MAX-ACCESS not-accessible
12/24 rsvpP2mp STATUS current
17/29 ldpP2mp DESCRIPTION
8/32 pimAsm "Different tunnel types will have different sizes for
8/32 pimSsm this object, as listed below:
8/32 pimBidir
4/16 ingressReplication
17/29 ldpMp2mp
For UDP-based S-PMSI signaling for PIM-MVPN, the first Size l2L3VpnMcastPmsiTunnelAttributeType
8 or 32 octets of this attribute are filled with (IPv4/IPv6)
the provider tunnel (source, group) IPv4/IPv6 addresses. --------------------------------------------------
For BGP-based I/S-PMSI signaling, this is the Tunnel 0/0 noTunnelId
Identifier field in PMSI Tunnel Attribute of the 12/24 rsvpP2mp
corresponding I/S-PMSI A-D route." 17/29 ldpP2mp
REFERENCE 8/32 pimAsm
"Section 5, [RFC6514]" 8/32 pimSsm
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } 8/32 pimBidir
4/16 ingressReplication
17/29 ldpMp2mp
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE For UDP-based S-PMSI signaling for PIM-MVPN, the first
SYNTAX RowPointer 8 or 32 octets of this attribute are filled with
MAX-ACCESS read-only the provider tunnel (source, group) IPv4/IPv6 addresses.
STATUS current For BGP-based I/S-PMSI signaling, this is the Tunnel
DESCRIPTION Identifier field in PMSI Tunnel Attribute of the
"If the tunnel exists in some MIB table, e.g. mplsTunnelTable corresponding I/S-PMSI A-D route."
REFERENCE
"Section 5, [RFC6514]"
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
[RFC3812], this is the row pointer to it. Otherwise, the l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
pointer is null." SYNTAX RowPointer
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } 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 l2L3VpnMcastPmsiTunnelIf OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the tunnel has a corresponding interface, this is the "If the tunnel has a corresponding entry in the ifXTable,
row pointer to ifXTable. Otherwise, the pointer is null." this object will point to the row pertaining to the entry
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } in the ifXTable. Otherwise, the pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
-- 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 {
l2L3VpnMcastPmsiTunnelPointer, l2L3VpnMcastPmsiTunnelPointer,
l2L3VpnMcastPmsiTunnelIf l2L3VpnMcastPmsiTunnelIf
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Support of these object is not required." "Support of these objects is not required."
::= { l2L3VpnMcastGroups 1 } ::= { l2L3VpnMcastGroups 1 }
END END
5. Security Considerations 5. Security Considerations
This MIB contains some read-only objects that may be deemed senstive This MIB contains some read-only objects that may be deemed senstive
by some though perhaps not all operators. Appropriate security by some though perhaps not all operators. Appropriate security
procedures related to SNMP in general but not specific to this MIB procedures related to SNMP in general but not specific to this MIB
need to be implemented by concerned operators. need to be implemented by concerned operators.
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
[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, Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/
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", Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
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>.
[RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of
Textual Conventions (TCs) for Multiprotocol Label
Switching (MPLS) Management", RFC 3811,
DOI 10.17487/RFC3811, June 2004,
<http://www.rfc-editor.org/info/rfc3811>.
[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>.
[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
C. Kodeboniya, "Multicast in Virtual Private LAN Service C. Kodeboniya, "Multicast in Virtual Private LAN Service
(VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014, (VPLS)", RFC 7117, DOI 10.17487/RFC7117, February 2014,
<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, Standard Management Framework", RFC 3410, DOI 10.17487/
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] [I-D.ietf-bess-mvpn-mib]
Zhang, J., Asif, S., Green, A., Gulrajani, S., and P. Zhang, J., Asif, S., Green, A., Gulrajani, S., and P.
Jain, "MPLS/BGP Layer 3 VPN Multicast Management Jain, "MPLS/BGP Layer 3 VPN Multicast Management
Information Base", draft-ietf-bess-mvpn-mib-02 (work in Information Base", draft-ietf-bess-mvpn-mib-02 (work in
progress), March 2016. progress), March 2016.
Author's Address 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
Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai 982-8577
Japan
Phone: +81-22-305-3411
Email: tsuno@m.ieice.org
 End of changes. 58 change blocks. 
258 lines changed or deleted 245 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/