draft-ietf-bess-l2l3-vpn-mcast-mib-02.txt   draft-ietf-bess-l2l3-vpn-mcast-mib-03.txt 
L3 VPN Working Group Z. Zhang L3 VPN Working Group Z. Zhang
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track March 14, 2016 Intended status: Standards Track April 16, 2016
Expires: September 15, 2016 Expires: October 18, 2016
L2L3 VPN Multicast MIB L2L3 VPN Multicast MIB
draft-ietf-bess-l2l3-vpn-mcast-mib-02 draft-ietf-bess-l2l3-vpn-mcast-mib-03
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. use with network management protocols in the Internet community.
In particular, it describes managed objects common to both L2 and IP In particular, it describes common managed objects used to configure
VPN Multicast. and/or monitor 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 September 15, 2016. This Internet-Draft will expire on October 18, 2016.
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 12 skipping to change at page 2, line 12
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 . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . 7 5. Security Considerations . . . . . . . . . . . . . . . . . . . 8
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . 8 7.1. Normative References . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . 8 7.2. Informative References . . . . . . . . . . . . . . . . . 9
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
Multicast in BGP/MPLS IP or L2 VPN (referred to MVPN and L2 VPN Multicast in BGP/MPLS Layer 3 (L3) and Layer 2 (L2) VPN (referred to
Multicast respectively) can be achieved by using provider tunnels to MVPN and L2 VPN Multicast respectively) can be achieved by using
deliver to all or a subset of PEs. An example of L2 VPN is VPLS. provider tunnels to deliver to all or a subset of Provider Edges
(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, RFC 7117] 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, L3VPN, 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 o PMSI: P-Multicast Service Interface - a conceptual interface for a
PE to send customer multicast traffic to all or some PEs in the
same VPN.
o I-PMSI: Inclusive PMSI o I-PMSI: Inclusive PMSI - to all PEs in the same VPN.
o S-PMSI: Selective PMSI o S-PMSI: Selective PMSI - to some of the PEs in the same VPN.
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, L2L3-VPN-MCAST-MIB contains a Textual Convention
L2L3VpnMcastProviderTunnelType, and a L2L3VpnMcastProviderTunnelType, and a
l2L3VpnMcastPmsiTunnelAttributeTable. Other MIB objects ([I-D. ietf- l2L3VpnMcastPmsiTunnelAttributeTable. The table is for PMSI Tunnel
bess-mvpn-mib]) may point to entries in the Attributes (PTAs) advertised/received in I/S-PSMI Auto-Discovery
routes. Other MIB objects (e.g., mvpnMIB in [I-D.ietf-bess-mvpn-
mib]) may point to entries in the
l2L3VpnMcastPmsiTunnelAttributeTable. l2L3VpnMcastPmsiTunnelAttributeTable.
4. Definitions 4. 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, experimental
experimental, Unsigned32 FROM SNMPv2-SMI -- [RFC2578]
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowPointer, RowStatus,
TimeStamp, TimeInterval
FROM SNMPv2-TC
SnmpAdminString MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMP-FRAMEWORK-MIB FROM SNMPv2-CONF -- [RFC2580]
InetAddress, InetAddressType TEXTUAL-CONVENTION, RowPointer
FROM INET-ADDRESS-MIB FROM SNMPv2-TC -- [RFC2579]
MplsLabel MplsLabel
FROM MPLS-TC-STD-MIB; FROM MPLS-TC-STD-MIB; -- [RFC3811]
l2L3VpnMcastMIB MODULE-IDENTITY l2L3VpnMcastMIB MODULE-IDENTITY
LAST-UPDATED "201310141200Z" -- 14 October 2013 12:00:00 GMT LAST-UPDATED "201310141200Z" -- 14 October 2013 12:00:00 GMT
ORGANIZATION "IETF BESS Working Group." ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO CONTACT-INFO
" Jeffrey (Zhaohui) Zhang
zzhang@juniper.net
" Comments and discussion to bess@ietf.org"
Comments and discussion to bess@ietf.org
Jeffrey (Zhaohui) Zhang
Juniper Networks, Inc.
10 Technology Park Drive
Westford, MA 01886
USA
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
RFC 7117 and RFC 6513/6514. [RFC7117] and [RFC6513, RFC6514].
Copyright (C) The Internet Society (2013)." Copyright (C) The Internet Society (2013)."
-- Revision history. -- Revision history.
REVISION "201310141200Z" -- 14 October 2013 12:00:00 GMT REVISION "201310141200Z" -- 14 October 2013 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version of the draft." "Initial version, published as RFC yyyy."
::= { experimental 99 } -- number to be assigned
-- RFC Ed. replace yyyy with actual RFC number and remove this note
::= { experimental 99 }
-- RFC Ed.: replace 999 with IANA-assigned number and
-- replace experimental with the subtree under which the module
-- will be registered.
-- Please also remove the ", experimental" text from earlier
-- IMPORTS section.
-- Texual convention -- Texual 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 IP VPN." BGP/MPLS L2 or L3 VPN, as defined in Section 5,
[RFC6514]. Additional types may be defined
in future RFCs, and those will be allowed as
valid types for L2L3VpnMcastProviderTunnelType."
SYNTAX INTEGER { unconfigured (0), SYNTAX INTEGER { unconfigured (0),
rsvp-p2mp (1), rsvpP2mp (1),
ldp-p2mp (2), ldpP2mp (2),
pim-asm (3), pimAsm (3),
pim-ssm (4), pimSsm (4),
pim-bidir (5), pimBidir (5),
ingress-replication (6), ingressReplication (6),
ldp-mp2mp (7) ldpMp2mp (7)
} }
-- Top level components of this MIB. -- Top level components of this MIB.
-- tables, scalars, conformance information -- tables, scalars, conformance information
l2L3VpnMcastObjects OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 } l2L3VpnMcastObjects OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 1 }
l2L3VpnMcastConformance OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 2 } l2L3VpnMcastConformance OBJECT IDENTIFIER ::= { l2L3VpnMcastMIB 2 }
l2L3VpnMcastStates OBJECT IDENTIFIER ::= { l2L3VpnMcastObjects 1 } l2L3VpnMcastStates OBJECT IDENTIFIER ::= { l2L3VpnMcastObjects 1 }
-- Table of PMSI 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
"This table is for advertised/received PMSI attributes, "This table is for PMSI Tunnel Attributes (PTAs,
to be referred to by I-PMSI or S-PMSI table entries" Section 5, [RFC6514]) advertised/received in I/S-PSMI
Auto-Discovery 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]."
::= {l2L3VpnMcastStates 1 } ::= {l2L3VpnMcastStates 1 }
l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeEntry OBJECT-TYPE
SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry SYNTAX L2L3VpnMcastPmsiTunnelAttributeEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table corresponds to an PMSI attribute "An entry in this table corresponds to a PTA
that is advertised/received on this router. that is advertised/received on this router.
For BGP-based signaling (for I-PMSI via auto-discovery For BGP-based signaling (for I-PMSI via auto-discovery
procedure, or for S-PMSI via S-PMSI A-D routes), procedure, or for S-PMSI via S-PMSI A-D routes),
they are just as signaled by BGP (RFC 6514 section 5, they are just as signaled by BGP ([RFC6514] section 5,
'PMSI Tunnel attribute'). 'PMSI Tunnel Attribute').
For UDP-based S-PMSI signaling for PIM-MVPN, For UDP-based S-PMSI signaling for PIM-MVPN,
they're derived from S-PMSI Join Message they're derived from S-PMSI Join Message
(RFC 6513 section 7.4.2, 'UDP-based Protocol').. ([RFC6513] section 7.4.2, 'UDP-based Protocol').
Note that BGP-based signaling may be used for Note that BGP-based signaling may be used for
PIM-MVPN as well." PIM-MVPN as well."
INDEX { INDEX {
l2L3VpnMcastPmsiTunnelAttributeFlags, l2L3VpnMcastPmsiTunnelAttributeFlags,
l2L3VpnMcastPmsiTunnelAttributeType, l2L3VpnMcastPmsiTunnelAttributeType,
l2L3VpnMcastPmsiTunnelAttributeLabel, l2L3VpnMcastPmsiTunnelAttributeLabel,
l2L3VpnMcastPmsiTunnelAttributeId l2L3VpnMcastPmsiTunnelAttributeId
} }
::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 } ::= { l2L3VpnMcastPmsiTunnelAttributeTable 1 }
skipping to change at page 6, line 4 skipping to change at page 6, line 10
} }
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, this is the Flags For BGP-based I/S-PMSI signaling, this is the Flags
field in PMSI Tunnel Attribute of the corresponding field in PMSI Tunnel Attribute of the corresponding
I/S-PMSI A-D route." I/S-PMSI A-D route, as defined in Section 5, [RFC6514]."
::= { 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
"As defined for L2L3VpnMcastProviderTunnelType. "As defined for L2L3VpnMcastProviderTunnelType.
For UDP-based S-PMSI signaling for PIM-MVPN, For UDP-based S-PMSI signaling for PIM-MVPN,
this is pim-asm (3), pim-ssm (4), or pim-bidir (5). this is pim-asm (3), pim-ssm (4), or pim-bidir (5).
For BGP-based I/S-PMSI signaling, this is the Tunnel Type For BGP-based I/S-PMSI signaling, this is the Tunnel Type
field in PMSI Tunnel Attribute of the corresponding I/S-PMSI field in PMSI Tunnel Attribute of the corresponding
A-D or Leaf A-D route." I/S-PMSI A-D or Leaf A-D route, as defined in Section 5,
[RFC6514]."
::= { 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
"For UDP-based I/S-PMSI signaling for PIM-MVPN, this is 0. "For UDP-based I/S-PMSI signaling for PIM-MVPN, this is 0.
For BGP-based I/S-PMSI signaling, this is the MPLS Label For BGP-based I/S-PMSI signaling, this is the MPLS Label
field in PMSI Tunnel Attribute of the corresponding field in PMSI Tunnel Attribute of the corresponding
I/S-PMSI A-D route." I/S-PMSI A-D route, as defined in Section 5, [RFC6514]."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 3 }
l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE l2L3VpnMcastPmsiTunnelAttributeId OBJECT-TYPE
SYNTAX OCTET STRING ( SIZE (0..37) ) SYNTAX OCTET STRING ( SIZE (0..50) )
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For UDP-based S-PMSI signaling for PIM-MVPN, the first "Different tunnel types will have different sizes for
this object.
For UDP-based S-PMSI signaling for PIM-MVPN, the first
four or sixteen octets of this attribute are filled with four or sixteen octets of this attribute are filled with
the provider tunnel group address (IPv4 or IPv6).. the provider tunnel group address (IPv4 or IPv6).
For BGP-based I/S-PMSI signaling, this is the Tunnel Identifier For BGP-based I/S-PMSI signaling, this is the Tunnel
Field in PMSI Tunnel Attribute of the corresponding I/S-PMSI Identifier field in PMSI Tunnel Attribute of the
A-D route." corresponding I/S-PMSI A-D route, as defined in
Section 5, [RFC6514]."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 4 }
l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE l2L3VpnMcastPmsiTunnelPointer OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If the tunnel exists in some MIB table, this is the "If the tunnel exists in some MIB table, e.g. mplsTunnelTable
row pointer to it." [RFC3812], this is the row pointer to it. Otherwise, the
pointer is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 5 } ::= { 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 interface, this is the
row pointer to the ifName table." row pointer to the ifName table. Otherwise, the pointer
is null."
::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 } ::= { l2L3VpnMcastPmsiTunnelAttributeEntry 6 }
-- Conformance Information -- Conformance Information
l2L3VpnMcastGroups OBJECT IDENTIFIER ::= {l2L3VpnMcastConformance 1} l2L3VpnMcastGroups OBJECT IDENTIFIER ::= {l2L3VpnMcastConformance 1}
l2L3VpnMcastCompliances OBJECT IDENTIFIER ::= {l2L3VpnMcastConformance 2} l2L3VpnMcastCompliances OBJECT IDENTIFIER ::= {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
DESCRIPTION
"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
skipping to change at page 8, line 30 skipping to change at page 8, line 42
[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 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, STD 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
skipping to change at page 9, line 5 skipping to change at page 9, line 33
<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/RFC3410, December 2002, DOI 10.17487/RFC3410, December 2002,
<http://www.rfc-editor.org/info/rfc3410>. <http://www.rfc-editor.org/info/rfc3410>.
[I-D.ietf-bess-mvpn-mib]
Zhang, J., Asif, S., Green, A., Gulrajani, S., and P.
Jain, "MPLS/BGP Layer 3 VPN Multicast Management
Information Base", draft-ietf-bess-mvpn-mib-02 (work in
progress), March 2016.
Author's Address Author's Address
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
 End of changes. 39 change blocks. 
74 lines changed or deleted 109 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/