draft-ietf-idmr-multicast-routmib-03.txt   draft-ietf-idmr-multicast-routmib-04.txt 
IDMR Working Group Keith McCloghrie IDMR Working Group Keith McCloghrie
INTERNET-DRAFT Dino Farinacci INTERNET-DRAFT Dino Farinacci
Expires December 1996 cisco Systems Expires May 1997 cisco Systems
Dave Thaler Dave Thaler
University of Michigan University of Michigan
9 June 1996 26 November 1996
IP Multicast Routing MIB IP Multicast Routing MIB
<draft-ietf-idmr-multicast-routmib-03.txt> <draft-ietf-idmr-multicast-routmib-04.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are valid for a maximum of six months and may be Internet Drafts are valid for a maximum of six months and may be
updated, replaced, or obsoleted by other documents at any time. It is updated, replaced, or obsoleted by other documents at any time. It is
inappropriate to use Internet Drafts as reference material or to cite inappropriate to use Internet Drafts as reference material or to cite
them other than as a "work in progress". them other than as a "work in progress".
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing IP Multicast Routing [5], independent of the specific multicast managing IP Multicast Routing [5], independent of the specific multicast
routing protocol [6,7,8,9] in use. Managed objects specific to routing protocol [6,7,8,9,10] in use. Managed objects specific to
particular multicast routing protocols are specified elsewhere. particular multicast routing protocols are specified elsewhere.
Draft IP Multicast Routing MIB June 1996 Draft IP Multicast Routing MIB June 1996
2. Revision History 2. Revision History
A record of changes which will be removed before publication. A record of changes which will be removed before publication.
26 November
(1) moved ipMRouteNextHopPkts to its own conformance group.
9 June 9 June
(1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts. (1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts.
(2) updated references, etc. (2) updated references, etc.
28 March 28 March
(1) renamed ipMRouteNextHopClosestMember to (1) renamed ipMRouteNextHopClosestMember to
ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes
skipping to change at page 2, line 47 skipping to change at page 3, line 5
4 February 4 February
(1) removed ipMRouteOutList (1) removed ipMRouteOutList
(2) Modified ipMRouteNextHopTable to be INDEX-ed by (2) Modified ipMRouteNextHopTable to be INDEX-ed by
ipMRouteNextHopGroup, ipMRouteNextHopSource, ipMRouteNextHopGroup, ipMRouteNextHopSource,
ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex. ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex.
(3) added ipMRouteProtocol (3) added ipMRouteProtocol
Draft IP Multicast Routing MIB June 1996
(4) replaced "RPF" terminology with "Upstream neighbor". (4) replaced "RPF" terminology with "Upstream neighbor".
15 July - initial version. 15 July - initial version.
Draft IP Multicast Routing MIB June 1996 Draft IP Multicast Routing MIB June 1996
3. The SNMP Network Management Framework 3. The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of three major The SNMP Network Management Framework presently consists of three major
components. They are: components. They are:
skipping to change at page 17, line 48 skipping to change at page 18, line 48
ipMRouteMIBBasicGroup OBJECT-GROUP ipMRouteMIBBasicGroup OBJECT-GROUP
OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor, OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor,
ipMRouteInIfIndex, ipMRouteInIfIndex,
ipMRouteUpTime, ipMRouteExpiryTime, ipMRouteUpTime, ipMRouteExpiryTime,
ipMRoutePkts, ipMRouteDifferentInIfPackets, ipMRoutePkts, ipMRouteDifferentInIfPackets,
ipMRouteOctets, ipMRouteOctets,
ipMRouteNextHopState, ipMRouteNextHopState,
ipMRouteNextHopUpTime, ipMRouteNextHopUpTime,
ipMRouteNextHopExpiryTime, ipMRouteNextHopExpiryTime,
ipMRouteNextHopProtocol, ipMRouteNextHopProtocol,
ipMRouteNextHopPkts,
ipMRouteInterfaceTtl, ipMRouteInterfaceTtl,
ipMRouteProtocol
Draft IP Multicast Routing MIB June 1996 Draft IP Multicast Routing MIB June 1996
ipMRouteProtocol
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support basic management of "A collection of objects to support basic management of
IP Multicast routing." IP Multicast routing."
::= { ipMRouteMIBGroups 1 } ::= { ipMRouteMIBGroups 1 }
ipMRouteMIBHopCountGroup OBJECT-GROUP ipMRouteMIBHopCountGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopClosestMemberHops } OBJECTS { ipMRouteNextHopClosestMemberHops }
STATUS current STATUS current
skipping to change at page 18, line 31 skipping to change at page 19, line 30
::= { ipMRouteMIBGroups 2 } ::= { ipMRouteMIBGroups 2 }
ipMRouteMIBBoundaryGroup OBJECT-GROUP ipMRouteMIBBoundaryGroup OBJECT-GROUP
OBJECTS { ipMRouteBoundaryStatus } OBJECTS { ipMRouteBoundaryStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of scoped "A collection of objects to support management of scoped
multicast address boundaries." multicast address boundaries."
::= { ipMRouteMIBGroups 3 } ::= { ipMRouteMIBGroups 3 }
ipMRouteMIBPktsOutGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopPkts }
STATUS current
DESCRIPTION
"A collection of objects to support management of packet
counters for each outgoing interface entry of a route."
::= { ipMRouteMIBGroups 4 }
END END
Draft IP Multicast Routing MIB June 1996 Draft IP Multicast Routing MIB June 1996
6. Acknowledgements 6. Acknowledgements
This MIB module was updated based on feedback from the IETF's Inter- This MIB module was updated based on feedback from the IETF's Inter-
Domain Multicast Routing (IDMR) Working Group. Domain Multicast Routing (IDMR) Working Group.
7. References 7. References
skipping to change at page 19, line 38 skipping to change at page 20, line 38
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[5] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD [5] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD
thesis, Electrical Engineering Dept., Stanford University, December thesis, Electrical Engineering Dept., Stanford University, December
1991. 1991.
[6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector
Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman, Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman,
Stanford University, November 1988. Stanford University, November 1988.
[7] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and [7] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
L. Wei, "Protocol Independent Multicast (PIM): Protocol Handley, M., Jacobson, V., Liu, C., and P. Sharma, "Protocol
Specification", Xerox, University of Southern California, Cisco Independent Multicast - Sparse Mode (PIM-SM): Protocol
Systems, Lawrence Berkeley Laboratory, January 1995. Specification", November 1996.
[8] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March [8] Estrin, D., Farinacci, D., Jacobson, V., Liu, C., Wei, L., Sharma,
1994. P, and Helmy, A., "Protocol Independent Multicast-Dense Mode (PIM-
DM): Protocol Specification", January 1996.
[9] Ballardie, A. J., "Core Based Trees (CBT) Multicast: Architectural [9] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March
Overview and Specification", University College London, November
1994. 1994.
Draft IP Multicast Routing MIB June 1996 Draft IP Multicast Routing MIB June 1996
[10] Ballardie, A. J., "Core Based Trees (CBT) Multicast: Architectural
Overview and Specification", University College London, November
1994.
8. Security Considerations 8. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
9. Authors' Address 9. Authors' Address
Keith McCloghrie Keith McCloghrie
cisco Systems, Inc. cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
skipping to change at page 21, line 11 skipping to change at page 22, line 11
Ann Arbor, MI 48109-2122 Ann Arbor, MI 48109-2122
Phone: +1 313 763 5243 Phone: +1 313 763 5243
EMail: thalerd@eecs.umich.edu EMail: thalerd@eecs.umich.edu
Draft IP Multicast Routing MIB June 1996 Draft IP Multicast Routing MIB June 1996
Table of Contents Table of Contents
1 Introduction .................................................... 1 1 Introduction .................................................... 1
2 Revision History ................................................ 2 2 Revision History ................................................ 2
3 The SNMP Network Management Framework ........................... 3 3 The SNMP Network Management Framework ........................... 4
3.1 Object Definitions ............................................ 3 3.1 Object Definitions ............................................ 4
4 Overview ........................................................ 4 4 Overview ........................................................ 5
5 Definitions ..................................................... 5 5 Definitions ..................................................... 6
6 Acknowledgements ................................................ 19 6 Acknowledgements ................................................ 20
7 References ...................................................... 19 7 References ...................................................... 20
8 Security Considerations ......................................... 20 8 Security Considerations ......................................... 21
9 Authors' Address ................................................ 20 9 Authors' Address ................................................ 21
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/