draft-ietf-manet-smf-mib-12.txt   draft-ietf-manet-smf-mib-13.txt 
Internet Engineering Task Force R. Cole Internet Engineering Task Force R. Cole
Internet-Draft US Army CERDEC Internet-Draft US Army CERDEC
Intended status: Experimental J. Macker Intended status: Experimental J. Macker
Expires: January 31, 2015 B. Adamson Expires: February 13, 2015 B. Adamson
Naval Research Laboratory Naval Research Laboratory
July 30, 2014 August 12, 2014
Definition of Managed Objects for the Manet Simplified Multicast Definition of Managed Objects for the Manet Simplified Multicast
Framework Relay Set Process Framework Relay Set Process
draft-ietf-manet-smf-mib-12 draft-ietf-manet-smf-mib-13
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 for configuring aspects of the In particular, it describes objects for configuring aspects of the
Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc Simplified Multicast Forwarding (SMF) process for Mobile Ad-Hoc
Networks (MANETs). The SMF-MIB module also reports state Networks (MANETs). The SMF-MIB module also reports state
information, performance information, and notifications. In addition information, performance information, and notifications. In addition
to configuration, the additional state and performance information is to configuration, the additional state and performance information is
skipping to change at page 1, line 40 skipping to change at page 1, line 40
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 31, 2015. This Internet-Draft will expire on February 13, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 36 skipping to change at page 2, line 36
5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8 5.7. Tables and Indexing . . . . . . . . . . . . . . . . . . . 8
6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 9
6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9 6.1. Relationship to the SNMPv2-MIB . . . . . . . . . . . . . . 9
6.2. Relationship to the IP-MIB . . . . . . . . . . . . . . . . 9 6.2. Relationship to the IP-MIB . . . . . . . . . . . . . . . . 9
6.3. Relationship to the IPMCAST-MIB . . . . . . . . . . . . . 10 6.3. Relationship to the IPMCAST-MIB . . . . . . . . . . . . . 10
6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 10 6.4. MIB modules required for IMPORTS . . . . . . . . . . . . . 10
6.5. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10 6.5. Relationship to the Future RSSA-MIB Moduless . . . . . . . 10
7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 11 7. SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . . . 11
8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 52 8. IANA-SMF-MIB Definitions . . . . . . . . . . . . . . . . . . . 52
9. Security Considerations . . . . . . . . . . . . . . . . . . . 56 9. Security Considerations . . . . . . . . . . . . . . . . . . . 56
10. Applicability Statement . . . . . . . . . . . . . . . . . . . 59 10. Applicability Statement . . . . . . . . . . . . . . . . . . . 60
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 62
12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63 12. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 63
13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63 13. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 63
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 63
14.1. Normative References . . . . . . . . . . . . . . . . . . . 63 14.1. Normative References . . . . . . . . . . . . . . . . . . . 63
14.2. Informative References . . . . . . . . . . . . . . . . . . 64 14.2. Informative References . . . . . . . . . . . . . . . . . . 64
Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . 65
1. Introduction 1. Introduction
skipping to change at page 3, line 38 skipping to change at page 3, line 38
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,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Conventions 3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in RFC
2119 [RFC2119].
4. Overview 4. Overview
SMF provides methods for implementing Duplicate Packet Detection SMF provides methods for implementing Duplicate Packet Detection
(DPD)-based multicast forwarding with the optional use of Connected (DPD)-based multicast forwarding with the optional use of Connected
Dominating Set (CDS)-based relay sets. The CDS provides a complete Dominating Set (CDS)-based relay sets. The CDS provides a complete
connected coverage of the nodes comprising the MANET. The Minimum connected coverage of the nodes comprising the MANET. The Minimum
CDS (MCDS) is the smallest set of MANET nodes (comprising a connected CDS (MCDS) is the smallest set of MANET nodes (comprising a connected
cluster) which cover all the nodes in the cluster with their cluster) which cover all the nodes in the cluster with their
transmissions. As the density of the MANET nodes increase, the transmissions. As the density of the MANET nodes increase, the
skipping to change at page 11, line 40 skipping to change at page 11, line 40
FROM INET-ADDRESS-MIB -- [RFC4001] FROM INET-ADDRESS-MIB -- [RFC4001]
IANAsmfOpModeIdTC IANAsmfOpModeIdTC
FROM IANA-SMF-MIB FROM IANA-SMF-MIB
IANAsmfRssaIdTC IANAsmfRssaIdTC
FROM IANA-SMF-MIB FROM IANA-SMF-MIB
; ;
smfMIB MODULE-IDENTITY smfMIB MODULE-IDENTITY
LAST-UPDATED "201407301300Z" -- July 30, 2014 LAST-UPDATED "201408121300Z" -- August 12, 2014
ORGANIZATION "IETF MANET Working Group" ORGANIZATION "IETF MANET Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-Mail: manet@ietf.org "WG E-Mail: manet@ietf.org
WG Chairs: sratliff@cisco.com WG Chairs: sratliff@cisco.com
jmacker@nrl.navy.mil jmacker@nrl.navy.mil
Editors: Robert G. Cole Editors: Robert G. Cole
US Army CERDEC US Army CERDEC
Space and Terrestrial Communications Space and Terrestrial Communications
skipping to change at page 12, line 27 skipping to change at page 12, line 27
Brian Adamson Brian Adamson
Naval Research Laboratory Naval Research Laboratory
Washington, D.C. 20375 Washington, D.C. 20375
USA USA
adamson@itd.nrl.navy.mil" adamson@itd.nrl.navy.mil"
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
the Manet SMF RSSA process defined in: the Manet SMF RSSA process defined in:
[SMF] Macker, J.(ed.), Macker, J.(ed.),
Simplified Multicast Forwarding, RFC 6621, Simplified Multicast Forwarding, RFC 6621,
May 2012. May 2012.
Copyright (C) The IETF Trust (2014). This version Copyright (C) The IETF Trust (2014). This version
of this MIB module is part of RFC xxxx; see the RFC of this MIB module is part of RFC xxxx; see the RFC
itself for full legal notices." itself for full legal notices."
-- Revision History -- Revision History
REVISION "201407301300Z" -- July 30, 2014 REVISION "201408121300Z" -- August 12, 2014
DESCRIPTION DESCRIPTION
"The first version of this MIB module, "The first version of this MIB module,
published as RFC xxxx. published as RFC xxxx.
" "
-- RFC-Editor assigns xxxx -- RFC-Editor assigns xxxx
::= { experimental xxxx } -- to be assigned by IANA ::= { experimental xxxx } -- to be assigned by IANA
-- --
-- TEXTUAL CONVENTIONs -- TEXTUAL CONVENTIONs
-- --
skipping to change at page 25, line 37 skipping to change at page 25, line 37
::= { smfCfgAddrForwardingEntry 2 } ::= { smfCfgAddrForwardingEntry 2 }
smfCfgAddrForwardingAddrType OBJECT-TYPE smfCfgAddrForwardingAddrType OBJECT-TYPE
SYNTAX InetAddressType { ipv4(1), ipv6(2) } SYNTAX InetAddressType { ipv4(1), ipv6(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the addresses in the multicast "The type of the addresses in the multicast
forwarding ranges identified by this table. forwarding ranges identified by this table.
Only the values ipv4(1) and ipv6(2) are Only the values ipv4(1) and ipv6(2) are
supported. supported.
This object is persistent and when written This object is persistent and when written
the entity SHOULD save the change to the entity SHOULD save the change to
non-volatile storage." non-volatile storage."
::= { smfCfgAddrForwardingEntry 3 } ::= { smfCfgAddrForwardingEntry 3 }
smfCfgAddrForwardingAddress OBJECT-TYPE smfCfgAddrForwardingAddress OBJECT-TYPE
SYNTAX InetAddress (SIZE(4|16)) SYNTAX InetAddress (SIZE(4|16))
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 52, line 32 skipping to change at page 52, line 32
operations mode. operations mode.
The IANAsmfRssaIdTC defines an index that identifies through The IANAsmfRssaIdTC defines an index that identifies through
reference to a specific Reduced Set Selection Algorithm (RSSA). The reference to a specific Reduced Set Selection Algorithm (RSSA). The
index is an integer valued named-number enumeration consisting of an index is an integer valued named-number enumeration consisting of an
integer and label. IANA is to create and maintain this textual integer and label. IANA is to create and maintain this textual
convention. convention.
Future assignments to the IANAsmfRssaIdTC for the index range 5-127 Future assignments to the IANAsmfRssaIdTC for the index range 5-127
require an RFC publication (either as an IETF submission or as an RFC require an RFC publication (either as an IETF submission or as an RFC
Editor Independent submission [RFC3932]). The type of RFC MUST be Editor Independent submission [RFC5742]). The type of RFC MUST be
Standards Track. The specific RSSA algorithms MUST be documented in Standards Track. The specific RSSA algorithms MUST be documented in
sufficient detail so that interoperability between independent sufficient detail so that interoperability between independent
implementations is possible. implementations is possible.
Future assignments to the IANAsmfRssaIdTC for the index range 128-239 Future assignments to the IANAsmfRssaIdTC for the index range 128-239
are private or local use only, with the type and purpose defined by are private or local use only, with the type and purpose defined by
the local site. No attempt is made to prevent multiple sites from the local site. No attempt is made to prevent multiple sites from
using the same value in different (and incompatible) ways. There is using the same value in different (and incompatible) ways. There is
no need for IANA to review such assignments (since IANA will not no need for IANA to review such assignments (since IANA will not
record these) and assignments are not generally useful for broad record these) and assignments are not generally useful for broad
interoperability. It is the responsibility of the sites making use interoperability. It is the responsibility of the sites making use
of the Private Use range to ensure that no conflicts occur (within of the Private Use range to ensure that no conflicts occur (within
the intended scope of use). the intended scope of use).
Future assignments to the IANAsmfRssaIdTC for the index range 240-255 Future assignments to the IANAsmfRssaIdTC for the index range 240-255
are to facilitate experimentation. These require an RFC publication are to facilitate experimentation. These require an RFC publication
(either as an IETF submission or as an RFC Editor Independent (either as an IETF submission or as an RFC Editor Independent
submission [RFC3932]). The type of RFC MUST be Experimental. The submission [RFC5742]). The type of RFC MUST be Experimental. The
RSSA algorithms MUST be documented in sufficient detail so that RSSA algorithms MUST be documented in sufficient detail so that
interoperability between independent implementations is possible. interoperability between independent implementations is possible.
IANA-SMF-MIB DEFINITIONS ::= BEGIN IANA-SMF-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
ianaSmfMIB MODULE-IDENTITY ianaSmfMIB MODULE-IDENTITY
LAST-UPDATED "201407301300Z" -- July 30, 2014 LAST-UPDATED "201408121300Z" -- August 12, 2014
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO "Internet Assigned Numbers Authority CONTACT-INFO "Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 823 9358 Tel: +1 310 823 9358
E-Mail: iana@iana.org" E-Mail: iana@iana.org"
DESCRIPTION "This MIB module defines the DESCRIPTION "This MIB module defines the
IANAsmfOpModeIdTC and IANAsmfRssaIdTC IANAsmfOpModeIdTC and IANAsmfRssaIdTC
Textual Conventions, and thus the Textual Conventions, and thus the
enumerated values of the enumerated values of the
smfCapabilitiesOpModeID and smfCapabilitiesOpModeID and
smfCapabilitiesRssaID objects defined smfCapabilitiesRssaID objects defined
in the SMF-MIB." in the SMF-MIB."
REVISION "201407301300Z" -- July 30, 2014 REVISION "201408121300Z" -- August 12, 2014
DESCRIPTION "Initial version of this MIB as published in DESCRIPTION "Initial version of this MIB as published in
RFC KKKK." RFC KKKK."
::= { mib-2 kkkk } ::= { mib-2 kkkk }
IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION IANAsmfOpModeIdTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index that identifies through reference to a specific "An index that identifies through reference to a specific
SMF operations mode. There are basically three styles SMF operations mode. There are basically three styles
of SMF operation with reduced relay sets currently of SMF operation with reduced relay sets currently
skipping to change at page 55, line 49 skipping to change at page 55, line 49
REFERENCE REFERENCE
"See, e.g., "See, e.g.,
Section 8.1.1. 'SMF Message TLV Type', Section 8.1.1. 'SMF Message TLV Type',
Appendix A. 'Essential Connecting Dominating Set (E-CDS) Appendix A. 'Essential Connecting Dominating Set (E-CDS)
Algorithm', Algorithm',
Appendix B. 'Source-Based Multipoint Relay (S-MPR) Appendix B. 'Source-Based Multipoint Relay (S-MPR)
Algorithm', and Algorithm', and
Appendix C. 'Multipoint Relay Connected Dominating Set Appendix C. 'Multipoint Relay Connected Dominating Set
(MPR-CDS) Algorithm' (MPR-CDS) Algorithm'
in RFC 6621 - Macker, J., `Simplified Multicast
Forwarding (SMF)', May 2012.
in RFC 6621 - Simplified Multicast Forwarding RFC 3626 - Clausen, T., and P. Jacquet, `Optimized Link
(SMF), Macker, J., May 2012." State Routing Protocol (OLSR)', October 2003.
RFC 5614 - Ogier, R. and P. Spagnolo, `Mobile Ad Hoc
Network (MANET) Extension of OSPF Using Connected
Dominating Set (CDS) Flooding', August 2009.
"
SYNTAX INTEGER { SYNTAX INTEGER {
cF(1), cF(1),
sMPR(2), sMPR(2),
eCDS(3), eCDS(3),
mprCDS(4) mprCDS(4)
-- future(5-127) -- future(5-127)
-- noStdAction(128-239) -- noStdAction(128-239)
-- experimental(240-255) -- experimental(240-255)
} }
skipping to change at page 57, line 42 skipping to change at page 57, line 47
forwarding of IPv4 multicast packets. Forwarders may operate with forwarding of IPv4 multicast packets. Forwarders may operate with
mixed H-DPD and I-DPD modes as long as they consistently perform mixed H-DPD and I-DPD modes as long as they consistently perform
the appropriate DPD routines outlined [RFC6621]. However, it is the appropriate DPD routines outlined [RFC6621]. However, it is
RECOMMENDED that a deployment be configured with a common mode for RECOMMENDED that a deployment be configured with a common mode for
operational consistency. operational consistency.
o 'smfCfgIpv6Dpd' - this writable configuration object sets the o 'smfCfgIpv6Dpd' - this writable configuration object sets the
duplicate packet detection method for forwarding of IPv6 multicast duplicate packet detection method for forwarding of IPv6 multicast
packets. Since IPv6 SMF does specifies an option header, the packets. Since IPv6 SMF does specifies an option header, the
interoperability constraints are not as loose as in the IPv4 interoperability constraints are not as loose as in the IPv4
version, and forwarders SHOULD not operate with mixed H-DPD and version, and forwarders SHOULD NOT operate with mixed H-DPD and
I-DPD modes. Hence the value for this object SHOULD be I-DPD modes. Hence the value for this object SHOULD be
consistently set within the forwarders comprising the MANET, else consistently set within the forwarders comprising the MANET, else
inconsistent forwarding may result unnecessary multicast packet inconsistent forwarding may result unnecessary multicast packet
dropping. dropping.
o 'smfCfgMaxPktLifetime' - this writable configuration object sets o 'smfCfgMaxPktLifetime' - this writable configuration object sets
the estimate of the network packet traversal time. If set too the estimate of the network packet traversal time. If set too
small, this could lead to poor multicast data delivery ratios small, this could lead to poor multicast data delivery ratios
throughout the MANET domain. This could serve as a form of DOS throughout the MANET domain. This could serve as a form of DOS
attack if this object value is set too small. attack if this object value is set too small.
skipping to change at page 61, line 10 skipping to change at page 61, line 18
MANET nodes are to be configured in the context of the Parking Lot MANET nodes are to be configured in the context of the Parking Lot
Initialization case above. Then the SMF-MIB module defines ten Initialization case above. Then the SMF-MIB module defines ten
configuration OIDs and two configuration tables, i.e., the configuration OIDs and two configuration tables, i.e., the
smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten smfCfgAddrForwardingTable and the smfCfgInterfaceTable. Of the ten
OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL OIDs defined, all but one, i.e., the smfCfgRouterID, have DEFVAL
clauses which allow for a functional configuration of the SMF process clauses which allow for a functional configuration of the SMF process
within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the within the MANET. The smfCfgRouterIDType defaults to 'ipv4' so the
smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP smfCfgRouterID can be set as, e.g. (assuming the use of the Net-SNMP
toolkit),: toolkit),:
snmpset [options] <smfCfgRouterID_OID>.0 a 192.168.1.100 snmpset [options] <smfCfgRouterID_OID>.0 a 192.0.2.100
If the smfCfgAddrForwardingTable is left empty, then the SMF local If the smfCfgAddrForwardingTable is left empty, then the SMF local
forwarder will forward all multicast addresses. So this table does forwarder will forward all multicast addresses. So this table does
not require configuration if you want to have the MANET forward all not require configuration if you want to have the MANET forward all
multicast addresses. multicast addresses.
All that remains is to configure at least one row in the All that remains is to configure at least one row in the
smfCfgInterfaceTable. Assume that the node has a wireless interface smfCfgInterfaceTable. Assume that the node has a wireless interface
with an <ifName>='wlan0' and an <ifIndex>='1'. All of the objects in with an <ifName>='wlan0' and an <ifIndex>='1'. All of the objects in
the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only the rows of the smfCfgInterfaceTable have a DEFVAL clause, hence only
skipping to change at page 64, line 17 skipping to change at page 64, line 24
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC3626] Clausen, T. and P. Jacquet, "Optimized Link State Routing
Protocol (OLSR)", RFC 3626, October 2003.
[RFC5742] Alvestrand, H. and R. Housley, "IESG Procedures for
Handling of Independent and IRTF Stream Submissions",
BCP 92, RFC 5742, December 2009.
[RFC5614] Ogier, R. and P. Spagnolo, "Mobile Ad Hoc Network (MANET)
Extension of OSPF Using Connected Dominating Set (CDS)
Flooding", RFC 5614, August 2009.
[RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621, [RFC6621] Macker, J., "Simplified Multicast Forwarding", RFC 6621,
May 2012. May 2012.
14.2. Informative References 14.2. Informative References
[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, December 2002. Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The
 End of changes. 19 change blocks. 
19 lines changed or deleted 38 lines changed or added

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