draft-ietf-bess-mvpn-mib-04.txt   draft-ietf-bess-mvpn-mib-05.txt 
Network Working Group Z. Zhang, Ed. Network Working Group Z. Zhang, Ed.
Internet-Draft Juniper Internet-Draft Juniper
Intended status: Standards Track S. Asif Intended status: Standards Track S. Asif
Expires: December 8, 2017 AT&T Expires: June 11, 2018 AT&T
A. Green A. Green
BT BT
S. Gulranjani S. Gulranjani
Cisco Cisco
P. Jain P. Jain
Alcatel-Lucent Alcatel-Lucent
H. Tsunoda, Ed. H. Tsunoda, Ed.
Tohoku Institute of Technology Tohoku Institute of Technology
June 06, 2017 December 08, 2017
BGP/MPLS Layer 3 VPN Multicast Management Information Base BGP/MPLS Layer 3 VPN Multicast Management Information Base
draft-ietf-bess-mvpn-mib-04 draft-ietf-bess-mvpn-mib-05
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects to configure and/or In particular, it describes managed objects to configure and/or
monitor MVPN, Multicast in MultiProtocol Label Switching/Border monitor MVPN, Multicast in MultiProtocol Label Switching/Border
Gateway Protocol (MPLS/BGP) IP Virtual Private Networks (VPNs) on a Gateway Protocol (MPLS/BGP) IP Virtual Private Networks (VPNs) on a
Provider Edge router. Provider Edge router.
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 December 8, 2017. This Internet-Draft will expire on June 11, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 38 skipping to change at page 2, line 38
4. Security Considerations . . . . . . . . . . . . . . . . . . . 36 4. Security Considerations . . . . . . . . . . . . . . . . . . . 36
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 37 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 37
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.1. Normative References . . . . . . . . . . . . . . . . . . 37 7.1. Normative References . . . . . . . . . . . . . . . . . . 37
7.2. Informative References . . . . . . . . . . . . . . . . . 39 7.2. Informative References . . . . . . . . . . . . . . . . . 39
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39
1. Introduction 1. Introduction
[RFC6513] [RFC6514], and [RFC6625] specify procedures for supporting [RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting
multicast in Border Gateway Protocol/MultiProtocol Label Switching multicast in Border Gateway Protocol/MultiProtocol Label Switching
(BGP/MPLS) Layer 3 (IP) Virtual Private Network (VPN). Throughout (BGP/MPLS) Layer 3 (IP) Virtual Private Network (VPN). Throughout
this document, we will use the term "Multicast VPN (MVPN)" [RFC6513] this document, we will use the term "Multicast VPN (MVPN)" [RFC6513]
to refer to a BGP/MPLS IP VPN that supports multicast. to refer to a BGP/MPLS IP VPN that supports multicast.
Provider Edge routers (PEs) exchange the VPN customer multicast Provider Edge routers (PEs) exchange the VPN customer multicast
(C-multicast) routing information with each other. In [RFC6513], two (C-multicast) routing information with each other. In [RFC6513], two
basic methods for exchanging C-multicast routing information are basic methods for exchanging C-multicast routing information are
defined (1) Protocol Independent Multicast (PIM) [RFC4601] and (2) defined (1) Protocol Independent Multicast (PIM) [RFC7761] and (2)
BGP. BGP.
In the rest of this document we will use the term "PIM-MVPN" to refer In the rest of this document we will use the term "PIM-MVPN" to refer
to PIM being used for exchanging C-multicast routing information, and to PIM being used for exchanging C-multicast routing information, and
"BGP-MVPN" to refer to BGP being used for exchanging C-multicast "BGP-MVPN" to refer to BGP being used for exchanging C-multicast
routing information. routing information.
This document describes managed objects to configure and/or monitor This document describes managed objects to configure and/or monitor
MVPN. The managed objects are common to both PIM-MVPN and BGP-MVPN. MVPN. The managed objects are common to both PIM-MVPN and BGP-MVPN.
This document borrowed some text from Cisco PIM-MVPN MIB
[I-D.svaidya-mcast-vpn-mib]. For PIM-MVPN this document attempts to
provide coverage comparable to [I-D.svaidya-mcast-vpn-mib], but in a
generic way that applies to both PIM-MVPN and BGP-MVPN.
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].
Comments should be made directly to the BESS WG at bess@ietf.org. Comments should be made directly to the BESS WG at bess@ietf.org.
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] and other documents that [RFC6513] refers to. described in [RFC6513] and other documents that [RFC6513] refers to.
Familiarity with Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts Familiarity with Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts
and/or mechanisms is assumed. Some terms specifically related to and/or mechanisms is assumed. Some terms specifically related to
this document are explained below. this document are explained below.
skipping to change at page 3, line 46 skipping to change at page 3, line 37
transport mechanism used to deliver multicast traffic. A PE uses to transport mechanism used to deliver multicast traffic. A PE uses to
send customer multicast traffic to all or some PEs in the same VPN. send customer multicast traffic to all or some PEs in the same VPN.
There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective
PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE
attached to a particular MVPN to transmit a message to all PEs in the attached to a particular MVPN to transmit a message to all PEs in the
same VPN. An S-PMSI is a PMSI that enables a PE attached to a same VPN. An S-PMSI is a PMSI that enables a PE attached to a
particular MVPN to transmit a message to some of the PEs in the same particular MVPN to transmit a message to some of the PEs in the same
VPN. VPN.
Interchangeably, the term Multicast Virtual Routing and Forwarding
table (MVRF) and MVPN are used to refer to a particular Multicast VPN
instantiation on a particular PE.
As described in [RFC4382], each PE router maintains one default As described in [RFC4382], each PE router maintains one default
forwarding table and "VPN Routing and Forwarding tables", or "VRFs". forwarding table and "VPN Routing and Forwarding tables", or "VRFs".
Throughout this document, we will use the term "multicast VRF (MVRF)" Throughout this document, we will use the term "multicast VRF (MVRF)"
to refer a VRF that is configured to contain the multicast routing to refer a VRF that is configured to contain the multicast routing
information. information.
Interchangeably, the term MVRF and MVPN are used to refer to a
particular Multicast VPN instantiation on a particular PE.
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].
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
skipping to change at page 4, line 45 skipping to change at page 4, line 41
o I-PMSI, S-PMSI and corresponding P-tunnels o I-PMSI, S-PMSI and corresponding P-tunnels
o Mapping of C-multicast routing information to PMSI tunnels o Mapping of C-multicast routing information to PMSI tunnels
To represent these information elements, MCAST-VPN-MIB defines eight To represent these information elements, MCAST-VPN-MIB defines eight
tables: mvpnGeneralTable, mvpnBgpGeneralTable, mvpnSpmsiConfigTable, tables: mvpnGeneralTable, mvpnBgpGeneralTable, mvpnSpmsiConfigTable,
mvpnPmsiConfigTable, mvpnIpmsiTable, mvpnInterAsIpmsiTable, mvpnPmsiConfigTable, mvpnIpmsiTable, mvpnInterAsIpmsiTable,
mvpnSpmsiTable, mvpnMrouteTable. mvpnSpmsiTable, mvpnMrouteTable.
The following four tables are designed for configuring MVPNs on PEs. The following four tables represent the MVPN configurations on PEs.
o mvpnGeneralTable o mvpnGeneralTable
o mvpnBgpGeneralTable o mvpnBgpGeneralTable
o mvpnSpmsiConfigTable o mvpnSpmsiConfigTable
o mvpnPmsiConfigTable o mvpnPmsiConfigTable
The following diagram shows the relationship among those four tables The following diagram shows the relationship among those four tables
use for configuration. Each box in the diagram represents a table, use for configuration. Each box in the diagram represents a table,
and the label of each box corresponds to a table name. An arrow and the label of each box corresponds to a table name. An arrow
indicates that one table has a pointer to a row in another table. indicates that one table has a pointer to a row in another table.
The entry in mvpnGeneralTable and mvpnSpmsiConfigTable has a pointer The entry in mvpnGeneralTable and mvpnSpmsiConfigTable has a pointer
to the row pertaining to the entry in the mvpnPmsiConfigTable. to the row pertaining to the entry in the mvpnPmsiConfigTable.
+--------------+ +--------------+
skipping to change at page 7, line 16 skipping to change at page 7, line 13
attribute. Th entry in this table is referred by entries in attribute. Th entry in this table is referred by entries in
mvpnIpmsiTable, mvpnInterAsIpmsiTable, mvpnSpmsiTable, and mvpnIpmsiTable, mvpnInterAsIpmsiTable, mvpnSpmsiTable, and
mvpnMrouteTable. mvpnMrouteTable.
3.2. MIB Module Definitions 3.2. MIB Module Definitions
MCAST-VPN-MIB DEFINITIONS ::= BEGIN MCAST-VPN-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Gauge32, Unsigned32, mib-2 -- [RFC2578] Gauge32, Unsigned32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI -- [RFC2578]
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC2571] FROM SNMP-FRAMEWORK-MIB -- [RFC2571]
InetAddress, InetAddressType InetAddress, InetAddressType, InetAddressPrefixLength,
InetAutonomousSystemNumber
FROM INET-ADDRESS-MIB -- [RFC2851] FROM INET-ADDRESS-MIB -- [RFC2851]
mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher
FROM MPLS-L3VPN-STD-MIB -- [RFC4382] FROM MPLS-L3VPN-STD-MIB -- [RFC4382]
ipMcastRouteEntry ipMcastRouteEntry
FROM IPMCAST-MIB -- [RFC5132] FROM IPMCAST-MIB -- [RFC5132]
L2L3VpnMcastProviderTunnelType L2L3VpnMcastProviderTunnelType
FROM L2L3-VPN-MCAST-TC-MIB; FROM L2L3-VPN-MCAST-TC-MIB;
mvpnMIB MODULE-IDENTITY mvpnMIB MODULE-IDENTITY
LAST-UPDATED "201706061200Z" -- 6th June 2017 12:00:00 GMT LAST-UPDATED "201712081200Z" -- 8th December 2017 12:00:00 GMT
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
Saud Asif Saud Asif
skipping to change at page 8, line 45 skipping to change at page 8, line 43
Comments and discussion to bess@ietf.org" Comments and discussion to bess@ietf.org"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for "This MIB contains managed object definitions for
multicast in BGP/MPLS IP VPNs defined by [RFC6513]. multicast in BGP/MPLS IP VPNs defined by [RFC6513].
Copyright (C) The Internet Society (2017)." Copyright (C) The Internet Society (2017)."
-- Revision history. -- Revision history.
REVISION "201706061200Z" -- 6th June, 2017 REVISION "201712081200Z" -- 8th December, 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 YYYY }
-- IANA Reg.: Please assign a value for "YYYY" under the -- IANA Reg.: Please assign a value for "YYYY" 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 "YYYY" here with the assigned value and
-- remove this note. -- remove this note.
-- Top level components of this MIB. -- Top level components of this MIB.
skipping to change at page 13, line 13 skipping to change at page 13, line 12
DEFVAL { createdMvrf } DEFVAL { createdMvrf }
::= { mvpnGeneralEntry 2 } ::= { mvpnGeneralEntry 2 }
mvpnGenMvrfStatusChangeTime OBJECT-TYPE mvpnGenMvrfStatusChangeTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The time at which the last status change for the MVRF in "The time at which the last status change for the MVRF in
question took place. The last operational change is specified question took place. The last operational change is specified
by mvpnGenOperStatusChange. by mvpnGenMvrfStatusChange.
" "
::= { mvpnGeneralEntry 3 } ::= { mvpnGeneralEntry 3 }
mvpnGenCmcastRouteProtocol OBJECT-TYPE mvpnGenCmcastRouteProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pim (1), pim (1),
bgp (2) bgp (2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 15, line 34 skipping to change at page 15, line 32
"The mvpnBgpGeneralEntry matches and augments an "The mvpnBgpGeneralEntry matches and augments an
mvpnGeneralEntry for a BGP-MVPN instance, with BGP-MVPN mvpnGeneralEntry for a BGP-MVPN instance, with BGP-MVPN
specific informatoin. specific informatoin.
" "
AUGMENTS { mvpnGeneralEntry } AUGMENTS { mvpnGeneralEntry }
::= { mvpnBgpGeneralTable 1 } ::= { mvpnBgpGeneralTable 1 }
MvpnBgpGeneralEntry ::= SEQUENCE { MvpnBgpGeneralEntry ::= SEQUENCE {
mvpnBgpGenMode INTEGER, mvpnBgpGenMode INTEGER,
mvpnBgpGenVrfRtImport MplsL3VpnRouteDistinguisher, mvpnBgpGenVrfRtImport MplsL3VpnRouteDistinguisher,
mvpnBgpGenSrcAs Unsigned32 mvpnBgpGenSrcAs InetAutonomousSystemNumber
} }
mvpnBgpGenMode OBJECT-TYPE mvpnBgpGenMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
rptSpt (1), rptSpt (1),
sptOnly (2) sptOnly (2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 16, line 17 skipping to change at page 16, line 15
"The VRF Route Import Extended Community that this PE "The VRF Route Import Extended Community that this PE
adds to unicast vpn routes that it advertises for this mvpn. adds to unicast vpn routes that it advertises for this mvpn.
" "
REFERENCE REFERENCE
"RFC4364, Section 4.2 "RFC4364, Section 4.2
RFC4382, Section 7 RFC4382, Section 7
" "
::= { mvpnBgpGeneralEntry 2} ::= { mvpnBgpGeneralEntry 2}
mvpnBgpGenSrcAs OBJECT-TYPE mvpnBgpGenSrcAs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX InetAutonomousSystemNumber
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Source AS number in Source AS Extended Community that this "The Source AS number in Source AS Extended Community that this
PE adds to the unicast vpn routes that it advertises for PE adds to the unicast vpn routes that it advertises for
this mvpn. this mvpn.
" "
::= { mvpnBgpGeneralEntry 3} ::= { mvpnBgpGeneralEntry 3}
-- PMSI Configuration Table -- PMSI Configuration Table
skipping to change at page 16, line 50 skipping to change at page 16, line 48
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created for each PMSI configured "An entry in this table is created for each PMSI configured
on this router. It can be referred to by either I-PMSI on this router. It can be referred to by either I-PMSI
configuration (in mvpnGeneralEntry) or S-PMSI configuration configuration (in mvpnGeneralEntry) or S-PMSI configuration
(in mvpnSpmsiConfigEntry) (in mvpnSpmsiConfigEntry)
" "
INDEX { INDEX {
mvpnPmsiConfigTunnelType, mvpnPmsiConfigTunnelType,
mvpnPmsiConfigTunnelAuxInfo, mvpnPmsiConfigTunnelAuxInfo,
mvpnPmsiConfigTunnelPimGroupAddressType, mvpnPmsiConfigTunnelPimGroupAddrType,
mvpnPmsiConfigTunnelPimGroupAddress, mvpnPmsiConfigTunnelPimGroupAddr,
mvpnPmsiConfigTunnelOrTemplateName mvpnPmsiConfigTunnelOrTemplateName
} }
::= { mvpnPmsiConfigTable 1 } ::= { mvpnPmsiConfigTable 1 }
MvpnPmsiConfigEntry ::= SEQUENCE { MvpnPmsiConfigEntry ::= SEQUENCE {
mvpnPmsiConfigTunnelType mvpnPmsiConfigTunnelType
L2L3VpnMcastProviderTunnelType, L2L3VpnMcastProviderTunnelType,
mvpnPmsiConfigTunnelAuxInfo Unsigned32, mvpnPmsiConfigTunnelAuxInfo Unsigned32,
mvpnPmsiConfigTunnelPimGroupAddressType mvpnPmsiConfigTunnelPimGroupAddrType
InetAddressType, InetAddressType,
mvpnPmsiConfigTunnelPimGroupAddress mvpnPmsiConfigTunnelPimGroupAddr
InetAddress, InetAddress,
mvpnPmsiConfigTunnelOrTemplateName mvpnPmsiConfigTunnelOrTemplateName
SnmpAdminString, SnmpAdminString,
mvpnPmsiConfigEncapsType INTEGER, mvpnPmsiConfigEncapsType INTEGER,
mvpnPmsiConfigRowStatus RowStatus mvpnPmsiConfigRowStatus RowStatus
} }
mvpnPmsiConfigTunnelType OBJECT-TYPE mvpnPmsiConfigTunnelType OBJECT-TYPE
SYNTAX L2L3VpnMcastProviderTunnelType SYNTAX L2L3VpnMcastProviderTunnelType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 18, line 4 skipping to change at page 17, line 51
group addresses to be specified in S-PMSI case. group addresses to be specified in S-PMSI case.
In I-PMSI case, it must be 1. In I-PMSI case, it must be 1.
rsvpP2mp(1): rsvpP2mp(1):
1 for statically specified rsvp-p2mp tunnel 1 for statically specified rsvp-p2mp tunnel
2 for dynamically created rsvp-p2mp tunnel 2 for dynamically created rsvp-p2mp tunnel
ingressReplication(6): ingressReplication(6):
1 for using any existing p2p/mp2p LSP 1 for using any existing p2p/mp2p LSP
2 for dynamically creating new p2p LSP 2 for dynamically creating new p2p LSP
" "
::= { mvpnPmsiConfigEntry 2 } ::= { mvpnPmsiConfigEntry 2 }
mvpnPmsiConfigTunnelPimGroupAddressType OBJECT-TYPE mvpnPmsiConfigTunnelPimGroupAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In case of PIM provider tunnel, the type of tunnel address." "In case of PIM provider tunnel, the type of tunnel address."
::= { mvpnPmsiConfigEntry 3 } ::= { mvpnPmsiConfigEntry 3 }
mvpnPmsiConfigTunnelPimGroupAddress OBJECT-TYPE mvpnPmsiConfigTunnelPimGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"In case of PIM provider tunnel, the provider tunnel address." "In case of PIM provider tunnel, the provider tunnel address."
::= { mvpnPmsiConfigEntry 4 } ::= { mvpnPmsiConfigEntry 4 }
mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 19, line 34 skipping to change at page 19, line 33
::= { mvpnConfig 2 } ::= { mvpnConfig 2 }
mvpnSpmsiConfigEntry OBJECT-TYPE mvpnSpmsiConfigEntry OBJECT-TYPE
SYNTAX MvpnSpmsiConfigEntry SYNTAX MvpnSpmsiConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry is created for each S-PMSI configuration." "An entry is created for each S-PMSI configuration."
INDEX { INDEX {
mplsL3VpnVrfName, mplsL3VpnVrfName,
mvpnSpmsiConfigCmcastAddressType, mvpnSpmsiConfigCmcastAddrType,
mvpnSpmsiConfigCmcastGroupAddress, mvpnSpmsiConfigCmcastGroupAddr,
mvpnSpmsiConfigCmcastGroupPrefixLen, mvpnSpmsiConfigCmcastGroupPrefixLen,
mvpnSpmsiConfigCmcastSourceAddress, mvpnSpmsiConfigCmcastSourceAddr,
mvpnSpmsiConfigCmcastSourcePrefixLen mvpnSpmsiConfigCmcastSourcePrefixLen
} }
::= { mvpnSpmsiConfigTable 1 } ::= { mvpnSpmsiConfigTable 1 }
MvpnSpmsiConfigEntry ::= SEQUENCE { MvpnSpmsiConfigEntry ::= SEQUENCE {
mvpnSpmsiConfigCmcastAddressType InetAddressType, mvpnSpmsiConfigCmcastAddrType InetAddressType,
mvpnSpmsiConfigCmcastGroupAddress InetAddress, mvpnSpmsiConfigCmcastGroupAddr InetAddress,
mvpnSpmsiConfigCmcastGroupPrefixLen Unsigned32, mvpnSpmsiConfigCmcastGroupPrefixLen InetAddressPrefixLength,
mvpnSpmsiConfigCmcastSourceAddress InetAddress, mvpnSpmsiConfigCmcastSourceAddr InetAddress,
mvpnSpmsiConfigCmcastSourcePrefixLen Unsigned32, mvpnSpmsiConfigCmcastSourcePrefixLen InetAddressPrefixLength,
mvpnSpmsiConfigThreshold Unsigned32, mvpnSpmsiConfigThreshold Unsigned32,
mvpnSpmsiConfigPmsiPointer RowPointer, mvpnSpmsiConfigPmsiPointer RowPointer,
mvpnSpmsiConfigRowStatus RowStatus mvpnSpmsiConfigRowStatus RowStatus
} }
mvpnSpmsiConfigCmcastAddressType OBJECT-TYPE
mvpnSpmsiConfigCmcastAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Type of C-multicast address" "Type of C-multicast address"
::= { mvpnSpmsiConfigEntry 1 } ::= { mvpnSpmsiConfigEntry 1 }
mvpnSpmsiConfigCmcastGroupAddress OBJECT-TYPE mvpnSpmsiConfigCmcastGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"C-multicast group address" "C-multicast group address"
::= { mvpnSpmsiConfigEntry 2 } ::= { mvpnSpmsiConfigEntry 2 }
mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"C-multicast group address prefix length. "C-multicast group address prefix length.
A group 0 (or ::0) with prefix length 32 (or 128) A group 0 (or ::0) with prefix length 32 (or 128)
indicates wildcard group, while a group 0 (or ::0) indicates wildcard group, while a group 0 (or ::0)
with prefix length 0 indicates any group. with prefix length 0 indicates any group.
" "
::= { mvpnSpmsiConfigEntry 3 } ::= { mvpnSpmsiConfigEntry 3 }
mvpnSpmsiConfigCmcastSourceAddress OBJECT-TYPE mvpnSpmsiConfigCmcastSourceAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"C-multicast source address" "C-multicast source address"
::= { mvpnSpmsiConfigEntry 4 } ::= { mvpnSpmsiConfigEntry 4 }
mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"C-multicast source address prefix length. "C-multicast source address prefix length.
A source 0 (or ::0) with prefix length 32 (or 128) A source 0 (or ::0) with prefix length 32 (or 128)
indicates a wildcard source, while a source 0 (or ::0) indicates a wildcard source, while a source 0 (or ::0)
with prefix length 0 indicates any source. with prefix length 0 indicates any source.
" "
::= { mvpnSpmsiConfigEntry 5 } ::= { mvpnSpmsiConfigEntry 5 }
skipping to change at page 22, line 5 skipping to change at page 22, line 4
" "
::= { mvpnStates 1 } ::= { mvpnStates 1 }
mvpnIpmsiEntry OBJECT-TYPE mvpnIpmsiEntry OBJECT-TYPE
SYNTAX MvpnIpmsiEntry SYNTAX MvpnIpmsiEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table corresponds to an I-PMSI "An entry in this table corresponds to an I-PMSI
advertisement that is advertised/received on this router. advertisement that is advertised/received on this router.
This represents all the sender PEs in the MVPN, This represents all the sender PEs in the MVPN,
with the provider tunnel they use to send traffic. with the provider tunnel they use to send traffic.
" "
INDEX { INDEX {
mplsL3VpnVrfName, mplsL3VpnVrfName,
mvpnIpmsiAfi, mvpnIpmsiAfi,
mvpnIpmsiRD, mvpnIpmsiRD,
mvpnIpmsiOrigAddrType, mvpnIpmsiOrigAddrType,
mvpnIpmsiOrigAddress mvpnIpmsiOrigAddr
} }
::= { mvpnIpmsiTable 1 } ::= { mvpnIpmsiTable 1 }
MvpnIpmsiEntry ::= SEQUENCE { MvpnIpmsiEntry ::= SEQUENCE {
mvpnIpmsiAfi INTEGER, mvpnIpmsiAfi INTEGER,
mvpnIpmsiRD MplsL3VpnRouteDistinguisher, mvpnIpmsiRD MplsL3VpnRouteDistinguisher,
mvpnIpmsiOrigAddrType InetAddressType, mvpnIpmsiOrigAddrType InetAddressType,
mvpnIpmsiOrigAddress InetAddress, mvpnIpmsiOrigAddr InetAddress,
mvpnIpmsiUpTime TimeInterval, mvpnIpmsiUpTime TimeInterval,
mvpnIpmsiAttribute RowPointer mvpnIpmsiAttribute RowPointer
} }
mvpnIpmsiAfi OBJECT-TYPE mvpnIpmsiAfi OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ipv4(1), ipv4(1),
ipv6(2) ipv6(2)
} }
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 22, line 50 skipping to change at page 22, line 50
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Route Distinguisher in this I-PMSI." "The Route Distinguisher in this I-PMSI."
::= { mvpnIpmsiEntry 2 } ::= { mvpnIpmsiEntry 2 }
mvpnIpmsiOrigAddrType OBJECT-TYPE mvpnIpmsiOrigAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address type of mvpnIpmsiOrigAddress." "The Internet address type of mvpnIpmsiOrigAddr."
::= { mvpnIpmsiEntry 3 } ::= { mvpnIpmsiEntry 3 }
mvpnIpmsiOrigAddress OBJECT-TYPE mvpnIpmsiOrigAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP address of the PE that originated the I-PMSI." "The BGP address of the PE that originated the I-PMSI."
::= { mvpnIpmsiEntry 4 } ::= { mvpnIpmsiEntry 4 }
mvpnIpmsiUpTime OBJECT-TYPE mvpnIpmsiUpTime OBJECT-TYPE
SYNTAX TimeInterval SYNTAX TimeInterval
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 24, line 14 skipping to change at page 24, line 14
mplsL3VpnVrfName, mplsL3VpnVrfName,
mvpnInterAsIpmsiAfi, mvpnInterAsIpmsiAfi,
mvpnInterAsIpmsiRD, mvpnInterAsIpmsiRD,
mvpnInterAsIpmsiSrcAs mvpnInterAsIpmsiSrcAs
} }
::= { mvpnInterAsIpmsiTable 1 } ::= { mvpnInterAsIpmsiTable 1 }
MvpnInterAsIpmsiEntry ::= SEQUENCE { MvpnInterAsIpmsiEntry ::= SEQUENCE {
mvpnInterAsIpmsiAfi INTEGER, mvpnInterAsIpmsiAfi INTEGER,
mvpnInterAsIpmsiRD MplsL3VpnRouteDistinguisher, mvpnInterAsIpmsiRD MplsL3VpnRouteDistinguisher,
mvpnInterAsIpmsiSrcAs Unsigned32, mvpnInterAsIpmsiSrcAs InetAutonomousSystemNumber,
mvpnInterAsIpmsiAttribute RowPointer mvpnInterAsIpmsiAttribute RowPointer
} }
mvpnInterAsIpmsiAfi OBJECT-TYPE mvpnInterAsIpmsiAfi OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
ipv4(1), ipv4(1),
ipv6(2) ipv6(2)
} }
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 24, line 38 skipping to change at page 24, line 38
mvpnInterAsIpmsiRD OBJECT-TYPE mvpnInterAsIpmsiRD OBJECT-TYPE
SYNTAX MplsL3VpnRouteDistinguisher SYNTAX MplsL3VpnRouteDistinguisher
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Route Distinguisher in this inter-as I-PMSI." "The Route Distinguisher in this inter-as I-PMSI."
::= { mvpnInterAsIpmsiEntry 2 } ::= { mvpnInterAsIpmsiEntry 2 }
mvpnInterAsIpmsiSrcAs OBJECT-TYPE mvpnInterAsIpmsiSrcAs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX InetAutonomousSystemNumber
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The source-as in this inter-as I-PMSI." "The source-as in this inter-as I-PMSI."
::= { mvpnInterAsIpmsiEntry 3 } ::= { mvpnInterAsIpmsiEntry 3 }
mvpnInterAsIpmsiAttribute OBJECT-TYPE mvpnInterAsIpmsiAttribute OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 25, line 28 skipping to change at page 25, line 28
SYNTAX MvpnSpmsiEntry SYNTAX MvpnSpmsiEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created or updated for each S-PMSI "An entry in this table is created or updated for each S-PMSI
advertised/received in a particular MVRF. advertised/received in a particular MVRF.
" "
INDEX { INDEX {
mplsL3VpnVrfName, mplsL3VpnVrfName,
mvpnSpmsiCmcastAddrType, mvpnSpmsiCmcastAddrType,
mvpnSpmsiCmcastGroup, mvpnSpmsiCmcastGroupAddr,
mvpnSpmsiCmcastGroupPrefixLen, mvpnSpmsiCmcastGroupPrefixLen,
mvpnSpmsiCmcastSource, mvpnSpmsiCmcastSourceAddr,
mvpnSpmsiCmcastSourcePrefixLen, mvpnSpmsiCmcastSourcePrefixLen,
mvpnSpmsiOrigAddrType, mvpnSpmsiOrigAddrType,
mvpnSpmsiOrigAddress mvpnSpmsiOrigAddr
} }
::= { mvpnSpmsiTable 1 } ::= { mvpnSpmsiTable 1 }
MvpnSpmsiEntry ::= SEQUENCE { MvpnSpmsiEntry ::= SEQUENCE {
mvpnSpmsiCmcastAddrType InetAddressType, mvpnSpmsiCmcastAddrType InetAddressType,
mvpnSpmsiCmcastGroup InetAddress, mvpnSpmsiCmcastGroupAddr InetAddress,
mvpnSpmsiCmcastGroupPrefixLen Unsigned32, mvpnSpmsiCmcastGroupPrefixLen InetAddressPrefixLength,
mvpnSpmsiCmcastSource InetAddress, mvpnSpmsiCmcastSourceAddr InetAddress,
mvpnSpmsiCmcastSourcePrefixLen Unsigned32, mvpnSpmsiCmcastSourcePrefixLen InetAddressPrefixLength,
mvpnSpmsiOrigAddrType InetAddressType, mvpnSpmsiOrigAddrType InetAddressType,
mvpnSpmsiOrigAddress InetAddress, mvpnSpmsiOrigAddr InetAddress,
mvpnSpmsiTunnelAttribute RowPointer, mvpnSpmsiTunnelAttribute RowPointer,
mvpnSpmsiUpTime TimeInterval, mvpnSpmsiUpTime TimeInterval,
mvpnSpmsiExpTime TimeInterval, mvpnSpmsiExpTime TimeInterval,
mvpnSpmsiRefCnt Unsigned32 mvpnSpmsiRefCnt Unsigned32
} }
mvpnSpmsiCmcastAddrType OBJECT-TYPE mvpnSpmsiCmcastAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address type of mvpnSpmsiCmcastGroup/Source." "The Internet address type of mvpnSpmsiCmcastGroup/Source."
::= { mvpnSpmsiEntry 1 } ::= { mvpnSpmsiEntry 1 }
mvpnSpmsiCmcastGroup OBJECT-TYPE mvpnSpmsiCmcastGroupAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"S-PMSI C-multicast group address. "S-PMSI C-multicast group address.
If it is 0 (or ::0), this is a wildcard group, If it is 0 (or ::0), this is a wildcard group,
and mvpnSpmsiCmcastGroupPrefixLen must be 32 (or 128). and mvpnSpmsiCmcastGroupPrefixLen must be 32 (or 128).
" "
::= { mvpnSpmsiEntry 2 } ::= { mvpnSpmsiEntry 2 }
mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"S-PMSI C-multicast group address prefix length." "S-PMSI C-multicast group address prefix length."
::= { mvpnSpmsiEntry 3 } ::= { mvpnSpmsiEntry 3 }
mvpnSpmsiCmcastSource OBJECT-TYPE mvpnSpmsiCmcastSourceAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"S-PMSI C-multicast source address "S-PMSI C-multicast source address
If it is 0 (or ::0), this is a wildcard source, If it is 0 (or ::0), this is a wildcard source,
and mvpnSpmsiCmcastSourcePrefixLen must be 32 (or 128). and mvpnSpmsiCmcastSourcePrefixLen must be 32 (or 128).
" "
::= { mvpnSpmsiEntry 4 } ::= { mvpnSpmsiEntry 4 }
mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX InetAddressPrefixLength
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"S-PMSI C-multicast source address prefix length." "S-PMSI C-multicast source address prefix length."
::= { mvpnSpmsiEntry 5 } ::= { mvpnSpmsiEntry 5 }
mvpnSpmsiOrigAddrType OBJECT-TYPE mvpnSpmsiOrigAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address type of mvpnSpmsiOrigAddress." "The Internet address type of mvpnSpmsiOrigAddr."
::= { mvpnSpmsiEntry 6 } ::= { mvpnSpmsiEntry 6 }
mvpnSpmsiOrigAddress OBJECT-TYPE mvpnSpmsiOrigAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP address of the PE that originated the S-PMSI." "The BGP address of the PE that originated the S-PMSI."
::= { mvpnSpmsiEntry 7 } ::= { mvpnSpmsiEntry 7 }
mvpnSpmsiTunnelAttribute OBJECT-TYPE mvpnSpmsiTunnelAttribute OBJECT-TYPE
SYNTAX RowPointer SYNTAX RowPointer
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 37, line 34 skipping to change at page 37, line 34
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
5. IANA Considerations 5. 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.
6. Acknowledgement 6. Acknowledgement
Some of the text has been taken almost verbatim from This document borrowed some text from Cisco PIM-MVPN MIB
[I-D.svaidya-mcast-vpn-mib]. We would like to thank Yakov Rekhter, [I-D.svaidya-mcast-vpn-mib]. We would like to thank Yakov Rekhter,
Jeffrey Haas, Huajin Jeng, Durga Prasad Velamuri for their helpful Jeffrey Haas, Huajin Jeng, Durga Prasad Velamuri for their helpful
comments. comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[I-D.ietf-bess-l2l3-vpn-mcast-mib] [I-D.ietf-bess-l2l3-vpn-mcast-mib]
Zhang, Z. and H. Tsunoda, "L2L3 VPN Multicast MIB", draft- Zhang, Z. and H. Tsunoda, "L2L3 VPN Multicast MIB", draft-
ietf-bess-l2l3-vpn-mcast-mib-08 (work in progress), May ietf-bess-l2l3-vpn-mcast-mib-12 (work in progress),
2017. November 2017.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997, RFC2119, March 1997, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc2119>. 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, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc2578>. 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>. <https://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>. <https://www.rfc-editor.org/info/rfc2580>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/
RFC3414, December 2002, RFC3414, December 2002, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc3414>. rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
Advanced Encryption Standard (AES) Cipher Algorithm in the Advanced Encryption Standard (AES) Cipher Algorithm in the
SNMP User-based Security Model", RFC 3826, DOI 10.17487/ SNMP User-based Security Model", RFC 3826, DOI 10.17487/
RFC3826, June 2004, RFC3826, June 2004, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc3826>. rfc3826>.
[RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer
3 Virtual Private Network (VPN) Management Information 3 Virtual Private Network (VPN) Management Information
Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, Base", RFC 4382, DOI 10.17487/RFC4382, February 2006,
<http://www.rfc-editor.org/info/rfc4382>. <https://www.rfc-editor.org/info/rfc4382>.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, DOI 10.17487/
RFC4601, August 2006,
<http://www.rfc-editor.org/info/rfc4601>.
[RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast
MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007,
<http://www.rfc-editor.org/info/rfc5132>. <https://www.rfc-editor.org/info/rfc5132>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model
for the Simple Network Management Protocol (SNMP)", STD for the Simple Network Management Protocol (SNMP)", STD
78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 78, RFC 5591, DOI 10.17487/RFC5591, June 2009,
<http://www.rfc-editor.org/info/rfc5591>. <https://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure
Shell Transport Model for the Simple Network Management Shell Transport Model for the Simple Network Management
Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June
2009, <http://www.rfc-editor.org/info/rfc5592>. 2009, <https://www.rfc-editor.org/info/rfc5592>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport
Model for the Simple Network Management Protocol (SNMP)", Model for the Simple Network Management Protocol (SNMP)",
STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011,
<http://www.rfc-editor.org/info/rfc6353>. <https://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, <https://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>. <https://www.rfc-editor.org/info/rfc6514>.
[RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R.
Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes",
RFC 6625, DOI 10.17487/RFC6625, May 2012, RFC 6625, DOI 10.17487/RFC6625, May 2012,
<http://www.rfc-editor.org/info/rfc6625>. <https://www.rfc-editor.org/info/rfc6625>.
[RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent
Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March
2016, <https://www.rfc-editor.org/info/rfc7761>.
7.2. Informative References 7.2. Informative References
[I-D.svaidya-mcast-vpn-mib] [I-D.svaidya-mcast-vpn-mib]
Vaidya, S., "Multicast in BGP/MPLS IP VPNs Management Vaidya, S., "Multicast in BGP/MPLS IP VPNs Management
Information Base", draft-svaidya-mcast-vpn-mib-02 (work in Information Base", draft-svaidya-mcast-vpn-mib-02 (work in
progress), March 2005. progress), March 2005.
[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, <https://www.rfc-editor.org/info/
<http://www.rfc-editor.org/info/rfc3410>. rfc3410>.
Authors' Addresses Authors' Addresses
Zhaohui (Jeffrey) Zhang (editor) Zhaohui (Jeffrey) Zhang (editor)
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. 70 change blocks. 
98 lines changed or deleted 96 lines changed or added

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