draft-ietf-l3vpn-l2l3-vpn-mcast-mib-00.txt   draft-ietf-l3vpn-l2l3-vpn-mcast-mib-01.txt 
L3 VPN Working Group J. Zhang L3 VPN Working Group Z. Zhang
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track October 14, 2013 Intended status: Standards Track October 14, 2013
Expires: April 17, 2014 Expires: April 17, 2014
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-l3vpn-l2l3-vpn-mcast-mib-00 draft-ietf-l3vpn-l2l3-vpn-mcast-mib-01
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the Information Base for use with network management protocols in the
Internet community. Internet community.
In particular, it describes managed objects common to both VPLS and In particular, it describes managed objects common to both VPLS and
VPN Multicast. VPN Multicast.
skipping to change at page 2, line 8 skipping to change at page 2, line 8
(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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . . 3 4. Summary of MIB Module . . . . . . . . . . . . . . . . . . . . 3
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Multicast in VPLS and VPN can be achieved by using provider tunnels Multicast in VPLS and VPN can be achieved by using provider tunnels
to deliver to all or a subset of PEs. The signaling of provider to deliver to all or a subset of PEs. The signaling of provider
tunnel choice is very similar for both VPLS and VPN multicast (aka tunnel choice is very similar for both VPLS and VPN multicast (aka
MVPN), and this memo describes managed objects common to both VPLS MVPN), and this memo describes managed objects common to both VPLS
Multicast [I-D.ietf-l2vpn-vpls-mcast] and MVPN [RFC 6513/6514]. Multicast [I-D.ietf-l2vpn-vpls-mcast] and MVPN [RFC 6513/6514].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
skipping to change at page 3, line 36 skipping to change at page 3, line 36
[RFC2580]. [RFC2580].
3. Conventions 3. Conventions
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 RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
4. Summary of MIB Module 4. Summary of MIB Module
L2L3-VPN-MCAST-MIB ontains a Textual Convention, L2L3-VPN-MCAST-MIB contains a Textual Convention,
L2L3VpnMcastProviderTunnelType, and a L2L3VpnMcastProviderTunnelType, and a
l2L3VpnMcastPmsiTunnelAttributeTable. Other MIB objects ([I-D.ietf- l2L3VpnMcastPmsiTunnelAttributeTable. Other MIB objects ([I-D.ietf-
l2vpn-vpls-mcast], [I-D. ietf-l3vpn-mvpn-mib]) may point to entries l2vpn-vpls-mcast], [I-D. ietf-l3vpn-mvpn-mib]) may point to entries
in the l2L3VpnMcastPmsiTunnelAttributeTable. in the l2L3VpnMcastPmsiTunnelAttributeTable.
5. Definitions 5. Definitions
L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN L2L3-VPN-MCAST-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Unsigned32 experimental, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval TEXTUAL-CONVENTION, TruthValue, RowPointer, RowStatus,
TimeStamp, TimeInterval
FROM SNMPv2-TC FROM SNMPv2-TC
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
InetAddress, InetAddressType InetAddress, InetAddressType
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB;
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201301071200Z" -- 07 January 2013 12:00:00 GMT LAST-UPDATED "201310141200Z" -- 14 October 2013 12:00:00 GMT
ORGANIZATION "IETF Layer-3 Virtual Private ORGANIZATION "IETF Layer-3 Virtual Private Networks Working Group."
Networks Working Group."
CONTACT-INFO CONTACT-INFO
" "
Comments and discussion to l3vpn@ietf.org Comments and discussion to l3vpn@ietf.org
Jeffrey (Zhaohui) Zhang Jeffrey (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
" "
DESCRIPTION DESCRIPTION
"This MIB contains common managed object definitions for "This MIB contains common managed object definitions for
multicast in Layer 2 and Layer 3 VPNs, defined by multicast in Layer 2 and Layer 3 VPNs, defined by
[I-D.ietf-l2vpn-vpls-mcast] and RFC 6513/6514. [I-D.ietf-l2vpn-vpls-mcast] and RFC 6513/6514.
Copyright (C) The Internet Society (2013)." Copyright (C) The Internet Society (2013)."
-- Revision history. -- Revision history.
REVISION "201301071200Z" -- 07 January 2013 12:00:00 GMT REVISION "201310141200Z" -- 14 October 2013 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version of the draft." "Initial version of the draft."
::= { experimental 99 } -- number to be assigned ::= { experimental 99 } -- number to be assigned
-- Texual convention -- Texual convention
L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION L2L3VpnMcastProviderTunnelType ::= TEXTUAL-CONVENTION
SYNTAX INTEGER { unconfigured (0),
pim-asm (1),
pim-ssm (2),
pim-bidir (3),
rsvp-p2mp (4),
ldp-p2mp (5),
ingress-replication (6),
ldp-mp2mp (7)
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Types of provider tunnels used for multicast in a l2/l3vpn." "Types of provider tunnels used for multicast in a l2/l3vpn."
REFERENCE SYNTAX INTEGER { unconfigured (0),
"[RFC6514]" rsvp-p2mp (1),
ldp-p2mp (2),
pim-asm (3),
pim-ssm (4),
pim-bidir (5),
ingress-replication (6),
ldp-mp2mp (7)
}
-- Top level components of this MIB. -- Top level components of this MIB.
-- tables, scalars -- tables, scalars, conformance information
l2L3VpnMcastObjects OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastConformance OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 2 }
l2L3VpnMcastObjects OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastStates OBJECT IDENTIFIER ::= { l2L3VpnMcastObjects 1 } l2L3VpnMcastStates OBJECT IDENTIFIER ::= { l2L3VpnMcastObjects 1 }
-- Table of PMSI attributes -- Table of PMSI 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
"This table is for advertised/received PMSI attributes, "This table is for advertised/received PMSI attributes,
to be referred to by I-PMSI or S-PMSI table entries" to be referred to by I-PMSI or S-PMSI table entries"
::= {l2L3VpnMcastStates 1 } ::= {l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 6, line 12 skipping to change at page 6, line 12
PIM-MVPN as well." PIM-MVPN as well."
INDEX { INDEX {
l2L3VpnMcastPmsiTunnelAttributeFlags, l2L3VpnMcastPmsiTunnelAttributeFlags,
l2L3VpnMcastPmsiTunnelAttributeType, l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeLabel, l2L3VpnMcastPmsiTunnelAttributeLabel,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
} }
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
L2L3VpnMcastPmsiTunnelAttributeEntry ::= SEQUENCE { L2L3VpnMcastPmsiTunnelAttributeEntry ::= SEQUENCE {
l2L3VpnMcastPmsiTunnelAttributeFlags OCTET STRING, l2L3VpnMcastPmsiTunnelAttributeFlags OCTET STRING,
l2L3VpnMcastPmsiTunnelAttributeType Unsigned32, l2L3VpnMcastPmsiTunnelAttributeType L2L3VpnMcastProviderTunnelType,
l2L3VpnMcastPmsiTunnelAttributeLabel MplsLabel, l2L3VpnMcastPmsiTunnelAttributeLabel MplsLabel,
l2L3VpnMcastPmsiTunnelAttributeId OCTET STRING, l2L3VpnMcastPmsiTunnelAttributeId OCTET STRING,
l2L3VpnMcastPmsiTunnelPointer RowPointer, l2L3VpnMcastPmsiTunnelPointer RowPointer,
l2L3VpnMcastPmsiTunnelIf RowPointer l2L3VpnMcastPmsiTunnelIf 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
"For UDP-based S-PMSI signaling for PIM-MVPN, this is 0. "For UDP-based S-PMSI signaling for PIM-MVPN, this is 0.
For BGP-based I/S-PMSI signaling, For BGP-based I/S-PMSI signaling,
per RFC 6514 section 5, 'PMSI Tunnel Attribute': per RFC 6514 section 5, 'PMSI Tunnel Attribute':
skipping to change at page 7, line 41 skipping to change at page 7, line 41
value. Absence of MPLS Label is indicated by setting the MPLS Label value. Absence of MPLS Label is indicated by setting the MPLS Label
field to zero. field to zero.
For UDP-based S-PMSI signaling for PIM-MVPN, this is not For UDP-based S-PMSI signaling for PIM-MVPN, this is not
applicable for now, as RFC 6513 does not specify applicable for now, as RFC 6513 does not specify
mpls encapsulation and tunnel aggregation with UDP-based mpls encapsulation and tunnel aggregation with UDP-based
signaling." signaling."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (4|8|12) ) SYNTAX OCTET STRING ( SIZE (0..37) )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For BGP-based signaling, as defined in RFC 6514 section 5, "For BGP-based signaling, as defined in RFC 6514 section 5,
'PMSI Tunnel Attribute'. 'PMSI Tunnel Attribute'.
For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 only For UDP-based S-PMSI signaling for PIM-MVPN, RFC 6513 only
specifies the 'P-Group' address, and that is filled into specifies the 'P-Group' address, and that is filled into
the first four octets of this field." the first four octets of this field."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
skipping to change at page 8, line 23 skipping to change at page 8, line 23
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 interface, this is the
row pointer to the ifName table." row pointer to the ifName table."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } ::= { 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
::= { l2L3VpnMcastCompliances 1 }
-- units of conformance
l2L3VpnMcastOptionalGroup OBJECT-GROUP
OBJECTS {
l2L3VpnMcastPmsiTunnelPointer,
l2L3VpnMcastPmsiTunnelIf
}
STATUS current
DESCRIPTION
"Support of these object is not required."
::= { l2L3VpnMcastGroups 1 }
END END
6. Security Considerations 6. Security Considerations
N/A N/A
7. IANA Considerations 7. 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 transmission subtree. this document under the transmission subtree.
 End of changes. 16 change blocks. 
40 lines changed or deleted 66 lines changed or added

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