draft-ietf-mboned-ip-mcast-mib-02.txt   draft-ietf-mboned-ip-mcast-mib-03.txt 
MBONED WG D. McWalter MBONED WG D. McWalter
Internet-Draft Data Connection Ltd Internet-Draft Data Connection Ltd
Expires: January 18, 2007 D. Thaler Expires: February 3, 2007 D. Thaler
Microsoft Corporation Microsoft Corporation
Obsoletes (if approved): RFC2932 A. Kessler Obsoletes (if approved): RFC2932 A. Kessler
Cisco Systems Cisco Systems
July 17, 2006 August 2, 2006
IP Multicast MIB IP Multicast MIB
draft-ietf-mboned-ip-mcast-mib-02.txt draft-ietf-mboned-ip-mcast-mib-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 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. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 18, 2007. This Internet-Draft will expire on February 3, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
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 objects used for managing multicast In particular, it describes objects used for managing multicast
function, independent of the specific multicast protocol(s) in use. function, independent of the specific multicast protocol(s) in use.
This document obsoletes RFC 2932. This document obsoletes RFC 2932.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Internet-Standard Management Framework . . . . . . . . . . 3 3. The Internet-Standard Management Framework . . . . . . . . . . 3
4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 45 6. Security Considerations . . . . . . . . . . . . . . . . . . . 46
6.1 SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 46 6.1 SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 46
6.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 46 6.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 46
6.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 47 6.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 47
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 48
9.1 Normative References . . . . . . . . . . . . . . . . . . . 48 9.1 Normative References . . . . . . . . . . . . . . . . . . . 48
9.2 Informative References . . . . . . . . . . . . . . . . . . 49 9.2 Informative References . . . . . . . . . . . . . . . . . . 49
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 50 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 50
Intellectual Property and Copyright Statements . . . . . . . . 52 Intellectual Property and Copyright Statements . . . . . . . . 52
skipping to change at page 3, line 18 skipping to change at page 3, line 18
including IP multicast routing. These objects are independent of the including IP multicast routing. These objects are independent of the
specific multicast routing protocol in use. Managed objects specific specific multicast routing protocol in use. Managed objects specific
to particular multicast protocols are defined elsewhere. to particular multicast protocols are defined elsewhere.
2. History 2. History
This document obsoletes [RFC2932]. The MIB module defined by this This document obsoletes [RFC2932]. The MIB module defined by this
document is a re-working of the MIB module from [RFC2932], with document is a re-working of the MIB module from [RFC2932], with
changes that include the following. changes that include the following.
o This MIB module is includes support for IPv6 addressing and the o This MIB module includes support for IPv6 addressing and the IPv6
IPv6 scoped address architecture. [RFC2932] supported only IPv4. scoped address architecture. [RFC2932] supported only IPv4.
o This MIB module allows several multicast protocols to perform o This MIB module allows several multicast protocols to perform
routing on a single interface, where [RFC2932] assumed each routing on a single interface, where [RFC2932] assumed each
interface supported at most one multicast routing protocol. interface supported at most one multicast routing protocol.
o This MIB module includes objects that are not specific to o This MIB module includes objects that are not specific to
multicast routing. It allows management of multicast function on multicast routing. It allows management of multicast function on
systems that do not perform routing, whereas RFC 2932 was systems that do not perform routing, whereas RFC 2932 was
restricted to multicast routing. restricted to multicast routing.
skipping to change at page 4, line 10 skipping to change at page 4, line 10
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
([RFC2578], [RFC2579] and [RFC2580]). ([RFC2578], [RFC2579] and [RFC2580]).
4. Overview 4. Overview
This MIB module contains two scalars and seven tables. The tables This MIB module contains two scalars and eight tables. The tables
are: are:
1. The IP Multicast Interface Table containing multicast information 1. The IP Multicast Interface Table, which contains multicast
specific to interfaces. information specific to interfaces.
2. The IP Multicast SSM Range Table, which contains one row per 2. The IP Multicast SSM Range Table, which contains one row per
range of multicast group addresses to which Source-Specific range of multicast group addresses to which Source-Specific
Multicast semantics [RFC3569] should be applied. Multicast semantics [RFC3569] should be applied.
3. The IP Multicast Route Table containing multicast routing 3. The IP Multicast Route Table, which contains multicast routing
information for IP datagrams sent by particular sources to the IP information for IP datagrams sent by particular sources to the IP
multicast groups known to a system. multicast groups known to a system.
4. The IP Multicast Routing Next Hop Table containing information on 4. The IP Multicast Routing Next Hop Table, which contains
next-hops for the routing of IP multicast datagrams. Each entry information about next-hops for the routing of IP multicast
is one of a list of next-hops on outgoing interfaces for datagrams. Each entry is one of a list of next-hops on outgoing
particular sources sending to a particular multicast group interfaces for particular sources sending to a particular
address. multicast group address.
5. The IP Multicast Scope Boundary Table containing the boundaries 5. The IP Multicast Scope Boundary Table, which contains the
configured for multicast scopes [RFC2365]. boundaries configured for multicast scopes [RFC2365].
6. The IP Multicast Scope Name Table containing human-readable names 6. The IP Multicast Scope Name Table, which contains human-readable
of multicast scope. names for multicast scopes.
7. The IP Multicast Local Listener Table containing identifiers for 7. The IP Multicast Local Listener Table, which contains identifiers
local applications that are receiving multicast data. for local applications that are receiving multicast data.
8. The IP Multicast Zone Table, which contains an entry for each
scope zone known to a system, and maps each zone to the multicast
address range that is the corresponding scope.
This MIB module uses textual conventions defined in the IF-MIB This MIB module uses textual conventions defined in the IF-MIB
[RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB.
5. Definitions 5. Definitions
IPMCAST-MIB DEFINITIONS ::= BEGIN IPMCAST-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
skipping to change at page 5, line 16 skipping to change at page 5, line 20
SnmpAdminString FROM SNMP-FRAMEWORK-MIB SnmpAdminString FROM SNMP-FRAMEWORK-MIB
InterfaceIndexOrZero, InterfaceIndexOrZero,
InterfaceIndex FROM IF-MIB InterfaceIndex FROM IF-MIB
IANAipRouteProtocol, IANAipRouteProtocol,
IANAipMRouteProtocol FROM IANA-RTPROTO-MIB IANAipMRouteProtocol FROM IANA-RTPROTO-MIB
InetAddress, InetAddressType, InetAddress, InetAddressType,
InetAddressPrefixLength, InetAddressPrefixLength,
InetZoneIndex FROM INET-ADDRESS-MIB; InetZoneIndex FROM INET-ADDRESS-MIB;
ipMcastMIB MODULE-IDENTITY ipMcastMIB MODULE-IDENTITY
LAST-UPDATED "200608020000Z" -- 2 August 2006
ORGANIZATION "IETF MBONED Working Group" ORGANIZATION "IETF MBONED Working Group"
CONTACT-INFO "David McWalter CONTACT-INFO "David McWalter
Data Connection Limited Data Connection Limited
100 Church Street 100 Church Street
Enfield, EN2 6BQ Enfield, EN2 6BQ
UK UK
Phone: +44 208 366 1177 Phone: +44 208 366 1177
EMail: dmcw@dataconnection.com EMail: dmcw@dataconnection.com
skipping to change at page 6, line 9 skipping to change at page 6, line 12
This MIB module contains information about IP Multicast This MIB module contains information about IP Multicast
routing, data forwarding, and data reception. This MIB routing, data forwarding, and data reception. This MIB
module is independent of the multicast protocol(s) and module is independent of the multicast protocol(s) and
address type(s) that are in use. address type(s) that are in use.
Copyright (C) The Internet Society (2006). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC yyyy; see the RFC itself for this MIB module is part of RFC yyyy; see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
REVISION "200608020000Z" -- 2 August 2006
DESCRIPTION DESCRIPTION
"Changes from RFC 2932: "Changes from RFC 2932:
1) This MIB module is independent of address type, whereas 1) This MIB module is independent of address type, whereas
RFC 2932 only supported IPv4. RFC 2932 only supported IPv4.
2) This MIB module allows several multicast protocols to 2) This MIB module allows several multicast protocols to
perform routing on a single interface, whereas RFC 2932 perform routing on a single interface, whereas RFC 2932
assumed each interface supported at most one multicast assumed each interface supported at most one multicast
routing protocol. This MIB module retains but deprecates routing protocol. This MIB module retains but deprecates
the object ipMcastInterfaceProtocol. the object ipMcastInterfaceProtocol.
3) This MIB module includes objects that are not specific to 3) This MIB module includes objects that are not specific to
multicast routing. It allows management of multicast multicast routing. It allows management of multicast
function on systems that do not perform routing, whereas function on systems that do not perform routing, whereas
RFC 2932 was restricted to multicast routing. RFC 2932 was restricted to multicast routing.
4) This MIB module includes a table of Source-Specific 4) This MIB module includes a table of Source-Specific
Multicast (SSM) address ranges to which RFC 3569 SSM Multicast (SSM) address ranges to which RFC 3569 SSM
semantics should be applied. semantics should be applied.
5) This MIB module includes a table of local applications 5) This MIB module includes a table of local applications
that are receiving multicast data. that are receiving multicast data.
6) This MIB module includes a table of multicast scope
zones.
Published as RFC yyyy." Published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this note -- RFC Ed.: replace yyyy with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
-- --
-- Textual conventions -- Textual conventions
-- --
skipping to change at page 29, line 35 skipping to change at page 29, line 45
"The group address which, when combined with the "The group address which, when combined with the
corresponding value of ipMcastBoundaryAddressPrefixLength, corresponding value of ipMcastBoundaryAddressPrefixLength,
identifies the group range for which the scoped boundary identifies the group range for which the scoped boundary
exists. Scoped IPv4 multicast address ranges must be exists. Scoped IPv4 multicast address ranges must be
prefixed by 239.0.0.0/4. Scoped IPv6 multicast address prefixed by 239.0.0.0/4. Scoped IPv6 multicast address
ranges are FF0x::/16, where x is a valid RFC 4291 multicast ranges are FF0x::/16, where x is a valid RFC 4291 multicast
scope. scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix based multicast addresses. A zone boundary a unicast-prefix-based multicast addresses. A zone boundary
for FF0x::/16 implies an identical boundary for these other for FF0x::/16 implies an identical boundary for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table. in this table.
This address object is only significant up to This address object is only significant up to
ipMcastBoundaryAddressPrefixLength bits. The remainder of ipMcastBoundaryAddressPrefixLength bits. The remainder of
the address bits are zero. This is especially important for the address bits are zero. This is especially important for
this index field, which is part of the index of this entry. this index field, which is part of the index of this entry.
Any non-zero bits would signify an entirely different Any non-zero bits would signify an entirely different
entry." entry."
skipping to change at page 30, line 13 skipping to change at page 30, line 23
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which when, combined with "The length in bits of the mask which when, combined with
the corresponding value of ipMcastBoundaryAddress, the corresponding value of ipMcastBoundaryAddress,
identifies the group range for which the scoped boundary identifies the group range for which the scoped boundary
exists. exists.
The InetAddressType is given by ipMcastBoundaryAddressType. The InetAddressType is given by ipMcastBoundaryAddressType.
For 'ipv4' this object must be in the range 4..32. For For 'ipv4' this object must be in the range 4..32. For
'ipv6', this object must be 32." 'ipv6', this object must be 16."
::= { ipMcastBoundaryEntry 4 } ::= { ipMcastBoundaryEntry 4 }
ipMcastBoundaryStatus OBJECT-TYPE ipMcastBoundaryStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which rows in this table can "The status of this row, by which rows in this table can
be created and destroyed. be created and destroyed.
skipping to change at page 33, line 4 skipping to change at page 33, line 14
"The group address which, when combined with the "The group address which, when combined with the
corresponding value of ipMcastScopeNameAddressPrefixLength, corresponding value of ipMcastScopeNameAddressPrefixLength,
identifies the group range associated with the multicast identifies the group range associated with the multicast
scope. Scoped IPv4 multicast address ranges must be scope. Scoped IPv4 multicast address ranges must be
prefixed by 239.0.0.0/4. Scoped IPv6 multicast address prefixed by 239.0.0.0/4. Scoped IPv6 multicast address
ranges are FF0x::/16, where x is a valid RFC 4291 multicast ranges are FF0x::/16, where x is a valid RFC 4291 multicast
scope. scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix based multicast addresses. A scope a unicast-prefix-based multicast addresses. A scope
FF0x::/16 implies an identical scope name for these other FF0x::/16 implies an identical scope name for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table. in this table.
This address object is only significant up to This address object is only significant up to
ipMcastScopeNameAddressPrefixLength bits. The remainder of ipMcastScopeNameAddressPrefixLength bits. The remainder of
the address bits are zero. This is especially important for the address bits are zero. This is especially important for
this index field, which is part of the index of this entry. this index field, which is part of the index of this entry.
Any non-zero bits would signify an entirely different Any non-zero bits would signify an entirely different
entry." entry."
skipping to change at page 33, line 30 skipping to change at page 33, line 40
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, when combined with "The length in bits of the mask which, when combined with
the corresponding value of ipMcastScopeNameAddress, the corresponding value of ipMcastScopeNameAddress,
identifies the group range associated with the multicast identifies the group range associated with the multicast
scope. scope.
The InetAddressType is given by ipMcastScopeNameAddressType. The InetAddressType is given by ipMcastScopeNameAddressType.
For 'ipv4' this object must be in the range 4..32. For For 'ipv4' this object must be in the range 4..32. For
'ipv6', this object must be 32." 'ipv6', this object must be 16."
::= { ipMcastScopeNameEntry 3 } ::= { ipMcastScopeNameEntry 3 }
ipMcastScopeNameLanguage OBJECT-TYPE ipMcastScopeNameLanguage OBJECT-TYPE
SYNTAX LanguageTag SYNTAX LanguageTag
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Language tag associated with the scope name." "Language tag associated with the scope name."
REFERENCE "RFC 3283" REFERENCE "RFC 3283"
::= { ipMcastScopeNameEntry 4 } ::= { ipMcastScopeNameEntry 4 }
skipping to change at page 34, line 16 skipping to change at page 34, line 26
for IPv4 should is the string 239.x.x.x/y with x and y for IPv4 should is the string 239.x.x.x/y with x and y
replaced with decimal values to describe the address and replaced with decimal values to describe the address and
mask length associated with the scope. mask length associated with the scope.
When no name is specified, the default value of this object When no name is specified, the default value of this object
for IPv6 should is the string FF0x::/16, with x replaced by for IPv6 should is the string FF0x::/16, with x replaced by
the hexadecimal value for the RFC 4291 multicast scope. the hexadecimal value for the RFC 4291 multicast scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix based multicast addresses. A scope a unicast-prefix-based multicast addresses. A scope
FF0x::/16 implies an identical scope name for these other FF0x::/16 implies an identical scope name for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table." in this table."
REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7"
::= { ipMcastScopeNameEntry 5 } ::= { ipMcastScopeNameEntry 5 }
ipMcastScopeNameDefault OBJECT-TYPE ipMcastScopeNameDefault OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 38, line 28 skipping to change at page 38, line 38
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This zone index uniquely identifies a zone on a device. "This zone index uniquely identifies a zone on a device.
Each zone is for a given scope. Scope-level information in Each zone is for a given scope. Scope-level information in
this table is for the unique scope that corresponds to this this table is for the unique scope that corresponds to this
zone. zone.
Zero is a special value used to request the default zone for Zero is a special value used to request the default zone for
a given scope. Zero is not a valid value for this object." a given scope. Zero is not a valid value for this object.
To test whether ipMcastZoneIndex is the default zone for
this scope, test whether ipMcastZoneIndex is equal to
ipMcastZoneScopeDefaultZoneIndex."
::= { ipMcastZoneEntry 1 } ::= { ipMcastZoneEntry 1 }
ipMcastZoneScopeDefaultZoneIndex OBJECT-TYPE ipMcastZoneScopeDefaultZoneIndex OBJECT-TYPE
SYNTAX InetZoneIndex (1..4294967295) SYNTAX InetZoneIndex (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The default zone index for this scope. This is the zone "The default zone index for this scope. This is the zone
that this device will use if the default (zero) zone is that this device will use if the default (zero) zone is
requested for this scope. requested for this scope.
skipping to change at page 39, line 11 skipping to change at page 39, line 25
::= { ipMcastZoneEntry 3 } ::= { ipMcastZoneEntry 3 }
ipMcastZoneScopeAddress OBJECT-TYPE ipMcastZoneScopeAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE (4|16)) SYNTAX InetAddress (SIZE (4|16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The multicast group address which, when combined with "The multicast group address which, when combined with
ipMcastZoneScopeAddressPrefixLength, gives the multicast ipMcastZoneScopeAddressPrefixLength, gives the multicast
address range for this scope. The InetAddressType is given address range for this scope. The InetAddressType is given
given by ipMcastZoneScopeAddressType. by ipMcastZoneScopeAddressType.
Scoped IPv4 multicast address ranges are prefixed by Scoped IPv4 multicast address ranges are prefixed by
prefixed by 239.0.0.0/4. Scoped IPv6 multicast address 239.0.0.0/4. Scoped IPv6 multicast address ranges are
ranges are FF0x::/16, where x is a valid RFC 4291 multicast FF0x::/16, where x is a valid RFC 4291 multicast scope.
scope.
An IPv6 address prefixed by FF1x::/16 is a non-permanently- An IPv6 address prefixed by FF1x::/16 is a non-permanently-
assigned address. An IPv6 address prefixed by FF3x::/16 is assigned address. An IPv6 address prefixed by FF3x::/16 is
a unicast-prefix based multicast addresses. A scope a unicast-prefix-based multicast addresses. A scope
FF0x::/16 implies an identical scope for these other FF0x::/16 implies an identical scope for these other
prefixes. No separate FF1x::/16 or FF3x::/16 entries exist prefixes. No separate FF1x::/16 or FF3x::/16 entries exist
in this table. in this table.
This address object is only significant up to This address object is only significant up to
ipMcastSsmRangePrefixLength bits. The remainder of the ipMcastZoneScopeAddressPrefixLength bits. The remainder of
address bits are zero." the address bits are zero."
REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7"
::= { ipMcastZoneEntry 4 } ::= { ipMcastZoneEntry 4 }
ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE
SYNTAX InetAddressPrefixLength (4..32) SYNTAX InetAddressPrefixLength (4..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The length in bits of the mask which, when combined "The length in bits of the mask which, when combined
with ipMcastZoneScopeAddress, gives the multicast address with ipMcastZoneScopeAddress, gives the multicast address
prefix for this scope. prefix for this scope.
The InetAddressType is given by ipMcastZoneAddressType. The InetAddressType is given by ipMcastZoneAddressType.
For 'ipv4' this object must be in the range 4..32. For For 'ipv4' this object must be in the range 4..32. For
'ipv6', this object must be 32." 'ipv6', this object must be 16."
::= { ipMcastZoneEntry 5 } ::= { ipMcastZoneEntry 5 }
-- --
-- Conformance information -- Conformance information
-- --
ipMcastMIBConformance ipMcastMIBConformance
OBJECT IDENTIFIER ::= { ipMcastMIB 2 } OBJECT IDENTIFIER ::= { ipMcastMIB 2 }
ipMcastMIBCompliances ipMcastMIBCompliances
OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 }
 End of changes. 27 change blocks. 
36 lines changed or deleted 47 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/