--- 1/draft-ietf-mboned-ip-mcast-mib-00.txt 2006-06-06 22:12:32.000000000 +0200 +++ 2/draft-ietf-mboned-ip-mcast-mib-01.txt 2006-06-06 22:12:32.000000000 +0200 @@ -1,21 +1,21 @@ -IETF D. McWalter +MBONED WG D. McWalter Internet-Draft Data Connection Ltd -Expires: September 28, 2006 D. Thaler +Expires: December 7, 2006 D. Thaler Microsoft Corporation Obsoletes (if approved): RFC2932 A. Kessler Cisco Systems - March 27, 2006 + June 5, 2006 IP Multicast MIB - draft-ietf-mboned-ip-mcast-mib-00.txt + draft-ietf-mboned-ip-mcast-mib-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that @@ -26,49 +26,52 @@ and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on September 28, 2006. + This Internet-Draft will expire on December 7, 2006. Copyright Notice Copyright (C) The Internet Society (2006). Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing multicast function, independent of the specific multicast protocol(s) in use. This document obsoletes RFC 2932. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 - 6. Security Considerations . . . . . . . . . . . . . . . . . . . 40 - 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 - 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43 - 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 - 9.1 Normative References . . . . . . . . . . . . . . . . . . . 43 - 9.2 Informative References . . . . . . . . . . . . . . . . . . 44 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 45 - Intellectual Property and Copyright Statements . . . . . . . . 47 + 6. Security Considerations . . . . . . . . . . . . . . . . . . . 41 + 6.1 SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 41 + 6.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 41 + 6.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 42 + 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 + 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 44 + 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45 + 9.1 Normative References . . . . . . . . . . . . . . . . . . . 45 + 9.2 Informative References . . . . . . . . . . . . . . . . . . 45 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 46 + Intellectual Property and Copyright Statements . . . . . . . . 48 1. Introduction This MIB describes objects used for managing IP multicast function, including IP multicast routing. These objects are independent of the specific multicast routing protocol in use. Managed objects specific to particular multicast protocols are defined elsewhere. 2. History @@ -104,21 +107,21 @@ For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, - [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. + ([RFC2578], [RFC2579] and [RFC2580]). 4. Overview This MIB module contains two scalars and seven tables. The tables are: 1. The IP Multicast Interface Table containing multicast information specific to interfaces. 2. The IP Multicast SSM Range Table, which contains one row per @@ -243,21 +246,21 @@ DESCRIPTION "A language tag with all alphabetic characters converted to lowercase. This restriction is intended to make the lexical ordering imposed by SNMP useful when applied to language tags. Note that it is theoretically possible for a valid language tag to exceed the allowed length of this syntax, and thus be impossible to represent with this syntax. Sampling of language tags in current use on the Internet suggests that this limit does not pose a serious problem in practice." - REFERENCE "RFC 1766" + REFERENCE "RFC 3283" SYNTAX OCTET STRING (SIZE (1..99)) -- -- Top-level structure of the MIB -- ipMcastMIBObjects OBJECT IDENTIFIER ::= { ipMcastMIB 1 } ipMcast OBJECT IDENTIFIER ::= { ipMcastMIBObjects 1 } @@ -530,21 +533,21 @@ this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry. For IPv6 SSM address ranges, only ranges within the space FF3x::/32 are permitted (where 'x' is any valid scope). To configure non-global scope SSM range entries within a zone, consistent ipMcastBoundaryTable entries are required on routers at the zone boundary." - REFERENCE "RFC 2373 section 2.7 and RFC 3306 section 6" + REFERENCE "RFC 4291 section 2.7 and RFC 3306 section 6" ::= { ipMcastSsmRangeEntry 2 } ipMcastSsmRangePrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength (4..128) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The multicast group prefix length, which, when combined with ipMcastSsmRangeAddress, gives the group prefix for this SSM range. The InetAddressType is given by the @@ -1131,21 +1134,21 @@ be aged out. If ipMcastRouteNextHopState is pruned(1), the remaining time until the prune expires and the state reverts to forwarding(2). Otherwise, the remaining time until this entry is removed from the table. The time remaining may be copied from ipMcastRouteExpiryTime if the protocol in use for this entry does not specify next-hop timers. The value 0 indicates that the entry is not subject to aging." ::= { ipMcastRouteNextHopEntry 11 } ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE - SYNTAX Unsigned32 (0..2147483647) + SYNTAX Unsigned32 (0..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The minimum number of hops between this router and any member of this IP multicast group reached via this next-hop on this outgoing interface. Any IP multicast datagrams for the group which have a TTL (IPv4) or Hop Count (IPv6) less than this number of hops will not be forwarded to this next-hop. @@ -1218,21 +1221,25 @@ ipMcastBoundaryAddress, ipMcastBoundaryAddressPrefixLength } ::= { ipMcastBoundaryTable 1 } IpMcastBoundaryEntry ::= SEQUENCE { ipMcastBoundaryIfIndex InterfaceIndex, ipMcastBoundaryAddressType InetAddressType, ipMcastBoundaryAddress InetAddress, ipMcastBoundaryAddressPrefixLength InetAddressPrefixLength, ipMcastBoundaryStatus RowStatus, - ipMcastBoundaryStorageType StorageType + ipMcastBoundaryStorageType StorageType, + ipMcastBoundaryDroppedMcastOctets Counter32, + ipMcastBoundaryDroppedMcastPkts Counter32, + ipMcastBoundaryHCDroppedMcastOctets Counter64, + ipMcastBoundaryHCDroppedMcastPkts Counter64 } ipMcastBoundaryIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IfIndex value for the interface to which this boundary applies. Packets with a destination address in the associated address/mask range will not be forwarded out this @@ -1262,21 +1269,21 @@ 239.x.x.x. Scoped IPv6 addresses must come from range ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the scope type and group identifier. This address object is only significant up to ipMcastBoundaryAddressPrefixLength bits. The remainder of the address bits are zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry." - REFERENCE "RFC 2365, RFC 2373" + REFERENCE "RFC 2365, RFC 4291" ::= { ipMcastBoundaryEntry 3 } ipMcastBoundaryAddressPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength (4..128) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The length in bits of the mask which when combined with the corresponding value of ipMcastBoundaryAddress identifies the group range for which the scoped boundary exists." @@ -1301,20 +1308,62 @@ SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "The storage type for this row. Rows having the value 'permanent' need not allow write-access to any columnar objects in the row." DEFVAL { nonVolatile } ::= { ipMcastBoundaryEntry 6 } +ipMcastBoundaryDroppedMcastOctets OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The number of octets of multicast packets that have been + dropped as a result of this zone boundary configuration." + ::= { ipMcastBoundaryEntry 7 } + +ipMcastBoundaryDroppedMcastPkts OBJECT-TYPE + SYNTAX Counter32 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The number of multicast packets that have been dropped as a + result of this zone boundary configuration." + ::= { ipMcastBoundaryEntry 8 } + +ipMcastBoundaryHCDroppedMcastOctets OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The number of octets of multicast packets that have been + dropped as a result of this zone boundary configuration. + + This object is a 64-bit version of + ipMcastBoundaryDroppedMcastOctets." + ::= { ipMcastBoundaryEntry 9 } + +ipMcastBoundaryHCDroppedMcastPkts OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "The number of multicast packets that have been dropped as a + result of this zone boundary configuration. + + This object is a 64-bit version of + ipMcastBoundaryDroppedMcastPkts." + ::= { ipMcastBoundaryEntry 10 } + -- -- The IP Multicast Scope Name Table -- ipMcastScopeNameTable OBJECT-TYPE SYNTAX SEQUENCE OF IpMcastScopeNameEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The (conceptual) table listing multicast scope names." @@ -1367,40 +1416,40 @@ 239.x.x.x. Scoped IPv6 addresses must come from the range ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the scope type and group identifier. This address object is only significant up to ipMcastScopeNameAddressPrefixLength bits. The remainder of the address bits are zero. This is especially important for this index field, which is part of the index of this entry. Any non-zero bits would signify an entirely different entry." - REFERENCE "RFC 2365, RFC 2373" + REFERENCE "RFC 2365, RFC 4291" ::= { ipMcastScopeNameEntry 2 } ipMcastScopeNameAddressPrefixLength OBJECT-TYPE SYNTAX InetAddressPrefixLength (4..128) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The length in bits of the mask which when combined with the corresponding value of ipMcastScopeNameAddress identifies the group range associated with the multicast scope." ::= { ipMcastScopeNameEntry 3 } ipMcastScopeNameLanguage OBJECT-TYPE SYNTAX LanguageTag MAX-ACCESS not-accessible STATUS current DESCRIPTION "Language tag associated with the scope name." - REFERENCE "RFC 1766" + REFERENCE "RFC 3283" ::= { ipMcastScopeNameEntry 4 } ipMcastScopeNameString OBJECT-TYPE SYNTAX SnmpAdminString MAX-ACCESS read-create STATUS current DESCRIPTION "The textual name associated with the multicast scope. The value of this object should be suitable for displaying to end-users, such as when allocating a multicast address in @@ -1625,24 +1675,20 @@ GROUP ipMcastMIBHCInterfaceGroup DESCRIPTION "This group is mandatory only for those network interfaces for which the value of the corresponding instance of ifSpeed is greater than 20,000,000 bits/second." GROUP ipMcastMIBRouteProtoGroup DESCRIPTION "This group is mandatory if the system is a router." - GROUP ipMcastMIBPktsGroup - DESCRIPTION - "This group is optional." - GROUP ipMcastMIBSsmGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBLocalListenerGroup DESCRIPTION "This group is optional." GROUP ipMcastMIBBoundaryIfGroup DESCRIPTION @@ -1738,150 +1782,176 @@ DESCRIPTION "A collection of objects to support management of packet counters for each outgoing interface entry of a route." ::= { ipMcastMIBGroups 3 } ipMcastMIBHCInterfaceGroup OBJECT-GROUP OBJECTS { ipMcastInterfaceHCInMcastOctets, ipMcastInterfaceHCOutMcastOctets, ipMcastInterfaceHCInMcastPkts, ipMcastInterfaceHCOutMcastPkts, - ipMcastRouteHCOctets } + ipMcastRouteHCOctets, + ipMcastBoundaryHCDroppedMcastOctets, + ipMcastBoundaryHCDroppedMcastPkts } STATUS current DESCRIPTION "A collection of objects providing information specific to high speed (greater than 20,000,000 bits/second) network interfaces." ::= { ipMcastMIBGroups 4 } ipMcastMIBRouteProtoGroup OBJECT-GROUP OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, ipMcastRouteRtAddressType, ipMcastRouteRtAddress, ipMcastRouteRtPrefixLength, ipMcastRouteRtType } STATUS current DESCRIPTION "A collection of objects providing information on the relationship between multicast routing information and the IP Forwarding Table." ::= { ipMcastMIBGroups 5 } -ipMcastMIBPktsGroup OBJECT-GROUP - OBJECTS { ipMcastRoutePkts, ipMcastRouteDifferentInIfPackets, - ipMcastRouteOctets } - STATUS current - DESCRIPTION - "A collection of objects to support management of packet - counters for each forwarding entry." - ::= { ipMcastMIBGroups 6 } - ipMcastMIBBasicGroup OBJECT-GROUP OBJECTS { ipMcastEnable, ipMcastRouteEntryCount } STATUS current DESCRIPTION "A collection of objects to support basic management of IP Multicast protocols." - ::= { ipMcastMIBGroups 7 } + ::= { ipMcastMIBGroups 6 } ipMcastMIBRouteGroup OBJECT-GROUP OBJECTS { ipMcastRouteUpstreamNeighborType, ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, + ipMcastRoutePkts, + ipMcastRouteDifferentInIfPackets, + ipMcastRouteOctets, ipMcastRouteNextHopState, ipMcastRouteNextHopTimeStamp, ipMcastRouteNextHopExpiryTime, ipMcastRouteNextHopProtocol, ipMcastRouteNextHopPkts, ipMcastInterfaceTtl, ipMcastInterfaceRateLimit, ipMcastInterfaceInMcastOctets, ipMcastInterfaceOutMcastOctets } STATUS current DESCRIPTION "A collection of objects to support basic management of IP Multicast routing." - ::= { ipMcastMIBGroups 8 } + ::= { ipMcastMIBGroups 7 } ipMcastMIBSsmGroup OBJECT-GROUP OBJECTS { ipMcastSsmRangeRowStatus, ipMcastSsmRangeStorageType } STATUS current DESCRIPTION "A collection of objects to support management of the use of Source-Specific Multicast routing." - ::= { ipMcastMIBGroups 9 } + ::= { ipMcastMIBGroups 8 } ipMcastMIBLocalListenerGroup OBJECT-GROUP OBJECTS { ipMcastLocalListenerRunIndex } STATUS current DESCRIPTION "A collection of objects to support management of local listeners on hosts or routers." - ::= { ipMcastMIBGroups 10 } + ::= { ipMcastMIBGroups 9 } ipMcastMIBBoundaryIfGroup OBJECT-GROUP - OBJECTS { ipMcastBoundaryStatus, ipMcastBoundaryStorageType } + OBJECTS { ipMcastBoundaryStatus, + ipMcastBoundaryStorageType, + ipMcastBoundaryDroppedMcastOctets, + ipMcastBoundaryDroppedMcastPkts } STATUS current DESCRIPTION "A collection of objects to support management of scoped multicast address boundaries." - ::= { ipMcastMIBGroups 11 } + ::= { ipMcastMIBGroups 10 } ipMcastMIBScopeNameGroup OBJECT-GROUP OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, ipMcastScopeNameStatus, ipMcastScopeNameStorageType } STATUS current DESCRIPTION "A collection of objects to support management of multicast address scope names." - ::= { ipMcastMIBGroups 12 } + ::= { ipMcastMIBGroups 11 } ipMcastMIBIfPktsGroup OBJECT-GROUP OBJECTS { ipMcastInterfaceInMcastPkts, ipMcastInterfaceOutMcastPkts } STATUS current DESCRIPTION "A collection of objects to support management of packet counters for each interface entry." - ::= { ipMcastMIBGroups 13 } + ::= { ipMcastMIBGroups 12 } ipMcastMIBRouteOctetsGroup OBJECT-GROUP OBJECTS { ipMcastRouteOctets, ipMcastRouteNextHopOctets, ipMcastRouteDifferentInIfOctets } STATUS current DESCRIPTION "A collection of objects to support management of octet counters for each forwarding entry." - ::= { ipMcastMIBGroups 14 } + ::= { ipMcastMIBGroups 13 } END 6. Security Considerations +6.1 SNMPv2 + + SNMP versions prior to SNMPv3 did not include adequate security. + Even if the network itself is secured (for example by using IPSec), + there is still no control over whom on the secure network is allowed + to access (read/change/create/delete) the objects in this MIB module. + + It is RECOMMENDED that implementers consider the security features as + provided by the SNMPv3 framework (see [RFC3410], section 8), + including full support for the SNMPv3 cryptographic mechanisms (for + authentication and privacy). + + Further, deployment of SNMP versions prior to SNMPv3 is NOT + RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to + enable cryptographic security. It is then a customer/operator + responsibility to ensure that the SNMP entity giving access to an + instance of this MIB module is properly configured to give access to + the objects only to those principals (users) that have legitimate + rights to access (read/change/create/delete) them. + +6.2 Writeable objects + There are a number of management objects defined in this MIB module - with a MAX-ACCESS clause of read-write and/or read-create. Such - objects may be considered sensitive or vulnerable in some network - environments. The support for SET operations in a non-secure + with a MAX-ACCESS clause of read-write and/or read-create. This + section discusses and lists these elements. + + Such objects may be considered sensitive or vulnerable in some + network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on - network operations. These are the tables and objects and their - sensitivity/vulnerability: + network operations. - The following tables and objects could be employed to modify - multicast routing behavior in a way that prevents or disrupts + In this MIB module, possible effects that can be induced by SET + operations on writeable objects include: + + o Modifications multicast routing behavior that prevent or disrupt services provided by the network, including (but not limited to) multicast data traffic delivery. - The following tables and objects may also be used to modify multicast - routing behavior in order to intercept or subvert any information - that is carried by the network. For example, attacks can be - envisaged that would pass nominated multicast data streams through a - nominated location, without the sources or listeners becoming aware - of this subversion. + o Modifications multicast routing behavior that allow interception + or subversion of information that is carried by the network. For + example, attacks can be envisaged that would pass nominated + multicast data streams through a nominated location, without the + sources or listeners becoming aware of this subversion. + + The following are the read-write and read-create objects defined in + this MIB module. ipMcastEnable ipMcastInterfaceTable ipMcastInterfaceEntry ipMcastInterfaceIfIndex ipMcastInterfaceTtl ipMcastInterfaceProtocol ipMcastInterfaceRateLimit ipMcastSsmRangeTable ipMcastSsmRangeEntry @@ -1902,42 +1972,47 @@ ipMcastScopeNameEntry ipMcastScopeNameAddressType ipMcastScopeNameAddress ipMcastScopeNameAddressPrefixLength ipMcastScopeNameLanguage ipMcastScopeNameString ipMcastScopeNameDefault ipMcastScopeNameStatus ipMcastScopeNameStorageType - Some of the readable objects in this MIB module (i.e., objects with a - MAX-ACCESS other than not-accessible) may be considered sensitive or - vulnerable in some network environments. It is thus important to - control even GET and/or NOTIFY access to these objects and possibly - to even encrypt the values of these objects when sending them over - the network via SNMP. These are the tables and objects and their - sensitivity/vulnerability: +6.3 Readable objects - The following tables and objects could be employed to determine the - topology, disposition, and composition of the network. This - information may be commercially sensitive, and may also be used in - preparation for attacks, including any of the attacks described - above. + As well as the writeable objects discussed above, there are a number + of readable objects (i.e., objects with a MAX-ACCESS other than not- + accessible) that may be considered sensitive or vulnerable in some + network environments. It is thus important to control even GET + and/or NOTIFY access to these objects and possibly to even encrypt + the values of these objects when sending them over the network via + SNMP. - The following tables and objects may also be used to determine - whether multicast data is flowing in the network, or has flowed - recently. They may also be used to determine the network location of - senders and recipients. An attacker can apply 'traffic analysis' to - this data. In some cases, the information revealed by traffic - analyses can be as damaging as full knowledge of the data being + In this MIB module, possible effects that can be induced by GET + and/or NOTIFY operations include: + + o Determination of the topology, disposition, and composition of the + network. This information may be commercially sensitive, and may + also be used in preparation for attacks, including any of the + attacks described above. + + o Determinion of whether multicast data is flowing in the network, + or has flowed recently, as well as the locations of senders and + recipients. An attacker can apply 'traffic analysis' to this + data. In some cases, the information revealed by traffic analyses + can be as damaging as full knowledge of the data being transported. + The following are the read-only objects defined in this MIB module. + ipMcastRouteEntryCount ipMcastInterfaceInMcastOctets ipMcastInterfaceOutMcastOctets ipMcastInterfaceInMcastPkts ipMcastInterfaceOutMcastPkts ipMcastInterfaceHCInMcastOctets ipMcastInterfaceHCOutMcastOctets ipMcastInterfaceHCInMcastPkts ipMcastInterfaceHCOutMcastPkts ipMcastRouteTable @@ -1983,38 +2058,20 @@ ipMcastRouteNextHopOctets ipMcastLocalListenerTable ipMcastLocalListenerEntry ipMcastLocalListenerGroupAddressType ipMcastLocalListenerGroupAddress ipMcastLocalListenerSourceAddressType ipMcastLocalListenerSourceAddress ipMcastLocalListenerSourcePrefixLength ipMcastLocalListenerRunIndex - SNMP versions prior to SNMPv3 did not include adequate security. - Even if the network itself is secure (for example by using IPSec), - there is still no control over whom on the secure network is allowed - to access (read/change/create/delete) the objects in this MIB module. - - It is RECOMMENDED that implementers consider the security features as - provided by the SNMPv3 framework (see [RFC3410], section 8), - including full support for the SNMPv3 cryptographic mechanisms (for - authentication and privacy). - - Further, deployment of SNMP versions prior to SNMPv3 is NOT - RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to - enable cryptographic security. It is then a customer/operator - responsibility to ensure that the SNMP entity giving access to an - instance of this MIB module is properly configured to give access to - the objects only to those principals (users) that have legitimate - rights to access (read/change/create/delete) them. - 7. IANA Considerations IP-MCAST-MIB should be rooted under the mib-2 subtree. IANA is requested to assign { mib-2 XXX } to the IP-MCAST-MIB module specified in this document. 8. Acknowledgements This MIB module is based on the original work in [RFC2932] by K. McCloghrie, D. Farinacci and D. Thaler. @@ -2022,61 +2079,61 @@ Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have been used for comparison while editing this MIB module. The authors are also grateful to Bharat Joshi for his input and for several corrections. 9. References 9.1 Normative References - [RFC1766] Alvestrand, H., "Tags for the Identification of - Languages", RFC 1766, March 1995. - [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, RFC 2365, July 1998. - [RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing - Architecture", RFC 2373, July 1998. - [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. + [RFC3283] Mahoney, B., Babics, G., and A. Taler, "Guide to Internet + Calendaring", RFC 3283, June 2002. + [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 Multicast Addresses", RFC 3306, August 2002. [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific Multicast (SSM)", RFC 3569, July 2003. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005. + [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing + Architecture", RFC 4291, February 2006. + 9.2 Informative References [RFC1075] Waitzman, D., Partridge, C., and S. Deering, "Distance Vector Multicast Routing Protocol", RFC 1075, November 1988. [RFC1584] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. [RFC2189] Ballardie, T., "Core Based Trees (CBT version 2) Multicast @@ -2101,22 +2158,22 @@ [I-D.ietf-pim-sm-v2-new] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode PIM-SM): Protocol Specification (Revised)", draft-ietf-pim-sm-v2-new-12 (work in progress), March 2006. [I-D.ietf-pim-bidir] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, "Bi-directional Protocol Independent Multicast (BIDIR- - PIM)", draft-ietf-pim-bidir-07 (work in progress), - March 2005. + PIM)", draft-ietf-pim-bidir-08 (work in progress), + October 2005. Authors' Addresses David McWalter Data Connection Ltd 100 Church Street Enfield EN2 6BQ UK Email: dmcw@dataconnection.com