draft-ietf-bess-mvpn-mib-07.txt   draft-ietf-bess-mvpn-mib-08.txt 
Network Working Group H. Tsunoda Network Working Group H. Tsunoda
Internet-Draft Tohoku Institute of Technology Internet-Draft Tohoku Institute of Technology
Intended status: Standards Track July 23, 2018 Intended status: Standards Track July 30, 2018
Expires: January 24, 2019 Expires: January 31, 2019
BGP/MPLS Layer 3 VPN Multicast Management Information Base BGP/MPLS Layer 3 VPN Multicast Management Information Base
draft-ietf-bess-mvpn-mib-07 draft-ietf-bess-mvpn-mib-08
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 Multicast communication over IP Virtual Private Networks monitor Multicast communication over IP Virtual Private Networks
(VPNs) supported by MultiProtocol Label Switching/Border Gateway (VPNs) supported by MultiProtocol Label Switching/Border Gateway
Protcol (MPLS/BGP) on a Provider Edge router. Protcol (MPLS/BGP) on a Provider Edge router.
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 January 24, 2019. This Internet-Draft will expire on January 31, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 16 skipping to change at page 2, line 16
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 . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . 3
3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 3 3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4
3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . 50 4. Security Considerations . . . . . . . . . . . . . . . . . . . 50
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53
6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 53 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.1. Normative References . . . . . . . . . . . . . . . . . . 53 7.1. Normative References . . . . . . . . . . . . . . . . . . 53
7.2. Informative References . . . . . . . . . . . . . . . . . 55 7.2. Informative References . . . . . . . . . . . . . . . . . 56
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 55 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 56
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 Networks (VPNs). Throughout (BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs). 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) attaching to a particular MVPN exchange Provider Edge routers (PEs) attaching to a particular MVPN exchange
skipping to change at page 3, line 28 skipping to change at page 3, line 28
particular MVPN to transmit a message to all PEs in the same MVPN. particular MVPN to transmit a message to all PEs in the same MVPN.
An S-PMSI enables a PE to transmit a message to a selected set of PEs An S-PMSI enables a PE to transmit a message to a selected set of PEs
in the same MVPN. in the same MVPN.
As described in [RFC4382], each PE maintains one default forwarding As described in [RFC4382], each PE maintains one default forwarding
table and zero or more "Virtual Routing and Forwarding tables" table and zero or more "Virtual Routing and Forwarding tables"
(VRFs). Throughout this document, we will use the term "multicast (VRFs). Throughout this document, we will use the term "multicast
VRF" (MVRF) to refer to a VRF that contains multicast routing VRF" (MVRF) to refer to a VRF that contains multicast routing
information. information.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" in this
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. 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
skipping to change at page 5, line 52 skipping to change at page 5, line 49
mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher
FROM MPLS-L3VPN-STD-MIB -- [RFC4382] FROM MPLS-L3VPN-STD-MIB -- [RFC4382]
IANAipRouteProtocol, IANAipMRouteProtocol IANAipRouteProtocol, IANAipMRouteProtocol
FROM IANA-RTPROTO-MIB -- [RTPROTO] FROM IANA-RTPROTO-MIB -- [RTPROTO]
L2L3VpnMcastProviderTunnelType L2L3VpnMcastProviderTunnelType
FROM L2L3-VPN-MCAST-TC-MIB; FROM L2L3-VPN-MCAST-TC-MIB;
mvpnMIB MODULE-IDENTITY mvpnMIB MODULE-IDENTITY
LAST-UPDATED "201807231200Z" -- 23th July 2018 12:00:00 GMT LAST-UPDATED "201807301200Z" -- 30th July 2018 12:00:00 GMT
ORGANIZATION "IETF BESS Working Group." ORGANIZATION "IETF BESS Working Group."
CONTACT-INFO CONTACT-INFO
" Hiroshi Tsunoda " Hiroshi Tsunoda
Tohoku Institute of Technology Tohoku Institute of Technology
35-1, Yagiyama Kasumi-cho 35-1, Yagiyama Kasumi-cho
Taihaku-ku, Sendai, 982-8577 Taihaku-ku, Sendai, 982-8577
Japan Japan
Email: tsuno@m.ieice.org Email: tsuno@m.ieice.org
Comments and discussion to bess@ietf.org" Comments and discussion to bess@ietf.org"
skipping to change at page 6, line 26 skipping to change at page 6, line 24
"This MIB module contains managed object definitions to "This MIB module contains managed object definitions to
configure and/or monitor Multicast communication over IP configure and/or monitor Multicast communication over IP
Virtual Private Networks (VPNs) supported by MultiProtocol Virtual Private Networks (VPNs) supported by MultiProtocol
Label Switching/Border Gateway Protcol (MPLS/BGP) on a Label Switching/Border Gateway Protcol (MPLS/BGP) on a
Provider Edge router (PE). Provider Edge router (PE).
Copyright (C) The Internet Society (2018). Copyright (C) The Internet Society (2018).
" "
-- Revision history. -- Revision history.
REVISION "201807231200Z" -- 23th July, 2018 REVISION "201807301200Z" -- 30th July, 2018
DESCRIPTION DESCRIPTION
"Initial version, published as RFC XXXX." "Initial version, published as RFC XXXX."
-- RFC Ed. replace XXXX with the actual RFC number and -- RFC Ed. replace XXXX with the actual RFC number and
-- remove this note -- 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
skipping to change at page 45, line 11 skipping to change at page 45, line 11
MANDATORY-GROUPS { MANDATORY-GROUPS {
mvpnScalarGroup, mvpnScalarGroup,
mvpnGenericGroup, mvpnGenericGroup,
mvpnPmsiGroup, mvpnPmsiGroup,
mvpnAdvtStatsGroup, mvpnAdvtStatsGroup,
mvpnMrouteGroup, mvpnMrouteGroup,
mvpnMrouteNextHopGroup, mvpnMrouteNextHopGroup,
mvpnNotificationGroup mvpnNotificationGroup
} }
GROUP mvpnBgpScalarGroup
DESCRIPTION
"This group is mandatory for systems that support
BGP-MVPN.
"
GROUP mvpnBgpGroup GROUP mvpnBgpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for systems that support "This group is mandatory for systems that support
BGP-MVPN. BGP-MVPN.
" "
::= { mvpnCompliances 1 } ::= { mvpnCompliances 1 }
mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
skipping to change at page 45, line 37 skipping to change at page 45, line 43
MANDATORY-GROUPS { MANDATORY-GROUPS {
mvpnScalarGroup, mvpnScalarGroup,
mvpnGenericGroup, mvpnGenericGroup,
mvpnPmsiGroup, mvpnPmsiGroup,
mvpnAdvtStatsGroup, mvpnAdvtStatsGroup,
mvpnMrouteGroup, mvpnMrouteGroup,
mvpnMrouteNextHopGroup, mvpnMrouteNextHopGroup,
mvpnNotificationGroup mvpnNotificationGroup
} }
GROUP mvpnBgpScalarGroup
DESCRIPTION
"This group is mandatory for systems that support
BGP-MVPN.
"
GROUP mvpnBgpGroup GROUP mvpnBgpGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for systems that support "This group is mandatory for systems that support
BGP-MVPN. BGP-MVPN.
" "
OBJECT mvpnSPTunnelLimit OBJECT mvpnSPTunnelLimit
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
skipping to change at page 46, line 50 skipping to change at page 47, line 16
::= { mvpnCompliances 3 } ::= { mvpnCompliances 3 }
-- units of conformance -- units of conformance
mvpnScalarGroup OBJECT-GROUP mvpnScalarGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnMvrfs, mvpnMvrfs,
mvpnV4Mvrfs, mvpnV4Mvrfs,
mvpnV6Mvrfs, mvpnV6Mvrfs,
mvpnMldpMvrfs,
mvpnPimV4Mvrfs, mvpnPimV4Mvrfs,
mvpnPimV6Mvrfs, mvpnPimV6Mvrfs,
mvpnBgpV4Mvrfs,
mvpnBgpV6Mvrfs,
mvpnSPTunnelLimit mvpnSPTunnelLimit
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor/manage "These objects are used to monitor/manage
global MVPN parameters. global statistics and parameters.
" "
::= { mvpnGroups 1 } ::= { mvpnGroups 1 }
mvpnBgpScalarGroup OBJECT-GROUP
OBJECTS {
mvpnMldpMvrfs,
mvpnBgpV4Mvrfs,
mvpnBgpV6Mvrfs,
mvpnBgpCmcastRouteWithdrawalTimer,
mvpnBgpSrcSharedTreeJoinTimer
}
STATUS current
DESCRIPTION
"These objects are used to monitor/manage
BGP-MVPN specific global parameters.
"
::= { mvpnGroups 2 }
mvpnGenericGroup OBJECT-GROUP mvpnGenericGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnGenMvrfLastAction, mvpnGenMvrfLastAction,
mvpnGenMvrfLastActionTime, mvpnGenMvrfLastActionTime,
mvpnGenMvrfCreationTime, mvpnGenMvrfCreationTime,
mvpnGenCmcastRouteProtocol, mvpnGenCmcastRouteProtocol,
mvpnGenIpmsiInfo, mvpnGenIpmsiInfo,
mvpnGenInterAsPmsiInfo, mvpnGenInterAsPmsiInfo,
mvpnGenUmhSelection, mvpnGenUmhSelection,
mvpnGenCustomerSiteType mvpnGenCustomerSiteType
skipping to change at page 47, line 27 skipping to change at page 48, line 4
OBJECTS { OBJECTS {
mvpnGenMvrfLastAction, mvpnGenMvrfLastAction,
mvpnGenMvrfLastActionTime, mvpnGenMvrfLastActionTime,
mvpnGenMvrfCreationTime, mvpnGenMvrfCreationTime,
mvpnGenCmcastRouteProtocol, mvpnGenCmcastRouteProtocol,
mvpnGenIpmsiInfo, mvpnGenIpmsiInfo,
mvpnGenInterAsPmsiInfo, mvpnGenInterAsPmsiInfo,
mvpnGenUmhSelection, mvpnGenUmhSelection,
mvpnGenCustomerSiteType mvpnGenCustomerSiteType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor MVPNs on a PE. "These objects are used to monitor MVPNs on a PE.
" "
::= { mvpnGroups 2 } ::= { mvpnGroups 3 }
mvpnBgpGroup OBJECT-GROUP mvpnBgpGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnBgpMode, mvpnBgpMode,
mvpnBgpVrfRouteImportExtendedCommunity, mvpnBgpVrfRouteImportExtendedCommunity,
mvpnBgpSrcASExtendedCommunity, mvpnBgpSrcASExtendedCommunity,
mvpnBgpCmcastRouteWithdrawalTimer,
mvpnBgpSrcSharedTreeJoinTimer,
mvpnBgpMsgRateLimit, mvpnBgpMsgRateLimit,
mvpnBgpMaxSpmsiAdRoutes, mvpnBgpMaxSpmsiAdRoutes,
mvpnBgpMaxSpmsiAdRouteFreq, mvpnBgpMaxSpmsiAdRouteFreq,
mvpnBgpMaxSrcActiveAdRoutes, mvpnBgpMaxSrcActiveAdRoutes,
mvpnBgpMaxSrcActiveAdRouteFreq mvpnBgpMaxSrcActiveAdRouteFreq
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor BGP-MVPNs on "These objects are used to monitor/manage
a PE and to monitor timers and thresholds related the MVPN-wise BGP specific parameters.
to the BPG-MVPNs.
" "
::= { mvpnGroups 4 }
::= { mvpnGroups 3 }
mvpnPmsiGroup OBJECT-GROUP mvpnPmsiGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnPmsiRD, mvpnPmsiRD,
mvpnPmsiTunnelType, mvpnPmsiTunnelType,
mvpnPmsiTunnelAttribute, mvpnPmsiTunnelAttribute,
mvpnPmsiTunnelPimGroupAddrType, mvpnPmsiTunnelPimGroupAddrType,
mvpnPmsiTunnelPimGroupAddr, mvpnPmsiTunnelPimGroupAddr,
mvpnPmsiEncapsulationType, mvpnPmsiEncapsulationType,
mvpnSpmsiPmsiPointer mvpnSpmsiPmsiPointer
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor "These objects are used to monitor
I-PMSIs and S-PMSIs tunnel on a PE. I-PMSIs and S-PMSIs tunnel on a PE.
" "
::= { mvpnGroups 4 } ::= { mvpnGroups 5 }
mvpnAdvtStatsGroup OBJECT-GROUP mvpnAdvtStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnAdvtSent, mvpnAdvtSent,
mvpnAdvtReceived, mvpnAdvtReceived,
mvpnAdvtReceivedError, mvpnAdvtReceivedError,
mvpnAdvtReceivedMalformedTunnelType, mvpnAdvtReceivedMalformedTunnelType,
mvpnAdvtReceivedMalformedTunnelId, mvpnAdvtReceivedMalformedTunnelId,
mvpnAdvtLastSentTime, mvpnAdvtLastSentTime,
mvpnAdvtLastReceivedTime, mvpnAdvtLastReceivedTime,
mvpnAdvtCounterDiscontinuityTime mvpnAdvtCounterDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor "These objects are used to monitor
the statistics pertaining to I-PMSI and S-PMSI the statistics pertaining to I-PMSI and S-PMSI
advertisements sent/received by a PE. advertisements sent/received by a PE.
" "
::= { mvpnGroups 5 } ::= { mvpnGroups 6 }
mvpnMrouteGroup OBJECT-GROUP mvpnMrouteGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnMrouteUpstreamNeighborAddrType, mvpnMrouteUpstreamNeighborAddrType,
mvpnMrouteUpstreamNeighborAddr, mvpnMrouteUpstreamNeighborAddr,
mvpnMrouteInIfIndex, mvpnMrouteInIfIndex,
mvpnMrouteExpiryTime, mvpnMrouteExpiryTime,
mvpnMrouteProtocol, mvpnMrouteProtocol,
mvpnMrouteRtProtocol, mvpnMrouteRtProtocol,
mvpnMrouteRtAddrType, mvpnMrouteRtAddrType,
skipping to change at page 49, line 22 skipping to change at page 49, line 44
mvpnMroutePmsiPointer, mvpnMroutePmsiPointer,
mvpnMrouteNumberOfLocalReplication, mvpnMrouteNumberOfLocalReplication,
mvpnMrouteNumberOfRemoteReplication, mvpnMrouteNumberOfRemoteReplication,
mvpnMrouteCounterDiscontinuityTime mvpnMrouteCounterDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor multicast routing "These objects are used to monitor multicast routing
information corresponding to the MVRFs on a PE. information corresponding to the MVRFs on a PE.
" "
::= { mvpnGroups 6 } ::= { mvpnGroups 7 }
mvpnMrouteNextHopGroup OBJECT-GROUP mvpnMrouteNextHopGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mvpnMrouteNextHopState, mvpnMrouteNextHopState,
mvpnMrouteNextHopExpiryTime, mvpnMrouteNextHopExpiryTime,
mvpnMrouteNextHopClosestMemberHops, mvpnMrouteNextHopClosestMemberHops,
mvpnMrouteNextHopProtocol, mvpnMrouteNextHopProtocol,
mvpnMrouteNextHopOctets, mvpnMrouteNextHopOctets,
mvpnMrouteNextHopPkts, mvpnMrouteNextHopPkts,
mvpnMrouteNextHopCounterDiscontinuityTime mvpnMrouteNextHopCounterDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"These objects are used to monitor the information on "These objects are used to monitor the information on
next-hops for routing datagrams to MVPNs on a PE. next-hops for routing datagrams to MVPNs on a PE.
" "
::= { mvpnGroups 7 } ::= { mvpnGroups 8 }
mvpnNotificationGroup NOTIFICATION-GROUP mvpnNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
mvpnMvrfActionTaken mvpnMvrfActionTaken
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Objects required for MVPN notifications." "Objects required for MVPN notifications."
::= { mvpnGroups 8 } ::= { mvpnGroups 9 }
END END
4. Security Considerations 4. Security Considerations
This MIB module contains some read-only objects that may be deemed This MIB module contains some read-only objects that may be deemed
senstive. It also contains some read-write objects, whose setting senstive. It also contains some read-write objects, whose setting
will change the device's MVPN related behavior. Appropriate security will change the device's MVPN related behavior. 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
module need to be implemented by concerned operators. module need to be implemented by concerned operators.
skipping to change at page 53, line 5 skipping to change at page 53, line 29
---------- ----------------------- ---------- -----------------------
mvpnMIB { mib-2 YYYY } mvpnMIB { mib-2 YYYY }
Editor's Note (to be removed prior to publication): the IANA is Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "YYYY" under the 'mib-2' subtree and requested to assign a value for "YYYY" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "YYYY" assignment has been made, the RFC Editor is asked to replace "YYYY"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
IANA is requested to root MIB objects in the MIB module contained in
this document under the mib-2 subtree.
6. Acknowledgement 6. Acknowledgement
An earlier draft version of this document was coauthored by Zhaohui An earlier draft version of this document was coauthored by Zhaohui
(Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep (Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep
G. Jain, based on an earlier draft written by Susheela Vaidya, G. Jain, based on an earlier draft written by Susheela Vaidya,
Thomas D. Nadeau, and Harmen Van der Linde. Thomas D. Nadeau, and Harmen Van der Linde.
This document also borrowed the design and descriptions of This document also borrows heavily from the design and descriptions
ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST- of ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST-
MIB[RFC5132]. MIB[RFC5132].
Glenn Mansfield Keeni did the MIB Doctor review and provided valuable Glenn Mansfield Keeni did the MIB Doctor review and provided valuable
comments. comments.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI
 End of changes. 26 change blocks. 
33 lines changed or deleted 50 lines changed or added

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