draft-ietf-bfd-tc-mib-03.txt   draft-ietf-bfd-tc-mib-04.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: May 15, 2014 N. Akiya Expires: May 25, 2014 N. Akiya
Cisco Systems Cisco Systems
November 11, 2013 November 21, 2013
Definitions of Textual Conventions (TCs) for Definitions of Textual Conventions (TCs) for
Bidirectional Forwarding Detection (BFD) Management Bidirectional Forwarding Detection (BFD) Management
draft-ietf-bfd-tc-mib-03 draft-ietf-bfd-tc-mib-04
Abstract Abstract
This draft defines a Management Information Base (MIB) module which This draft defines a Management Information Base (MIB) module which
contains Textual Conventions to represent commonly used Bidirectional contains Textual Conventions to represent commonly used Bidirectional
Forwarding Detection (BFD) management information. The intent is Forwarding Detection (BFD) management information. The intent is
that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD
related MIB modules that would otherwise define their own related MIB modules that would otherwise define their own
representations. representations.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 May 15, 2014. This Internet-Draft will expire on May 25, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 2, line 24 skipping to change at page 2, line 24
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3 3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.2. Informative References . . . . . . . . . . . . . . . . . 9 7.1. Normative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . 9
1. The Internet-Standard Management Framework 1. 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
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 3, line 5 skipping to change at page 3, line 5
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].
2. Introduction 2. Introduction
This document defines a MIB module which contains Textual Conventions This document defines a MIB module which contains Textual Conventions
for Bidirectional Forwarding Detection (BFD) protocols. These for Bidirectional Forwarding Detection (BFD) protocols. These
Textual Conventions should be imported by MIB modules which manage Textual Conventions should be imported by MIB modules which manage
BFD protocols. BFD protocols.
Note that names of Textual Conventions defined in this document are
prefixed with "IANA" to make it obvious to readers that they are IANA
maintained.
For an introduction to the concepts of BFD, see [RFC5880], [RFC5881] For an introduction to the concepts of BFD, see [RFC5880], [RFC5881]
and [RFC5883]. and [RFC5883].
3. BFD Textual Conventions MIB Definitions 3. BFD Textual Conventions MIB Definitions
This MIB module makes references to the following documents. This MIB module makes references to the following documents:
[RFC2579], [RFC2580], [RFC2863], [RFC4001], and [RFC3413]. [RFC2578], [RFC2579], [RFC5880], [RFC5881] and [RFC5883].
BFD-TC-STD-MIB DEFINITIONS ::= BEGIN IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, Unsigned32 MODULE-IDENTITY, mib-2, Unsigned32
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- [RFC2579]
bfdTCStdMib MODULE-IDENTITY ianaBfdTCStdMib MODULE-IDENTITY
LAST-UPDATED "201306191200Z" -- 19 June 2013 12:00:00 EST LAST-UPDATED
ORGANIZATION "IETF Bidirectional Forwarding Detection "201311211200Z" -- 21 Nov. 2013 12:00:00 EST
Working Group" ORGANIZATION
"IANA"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Internet Assigned Numbers Authority
Juniper Networks Postal: 4676 Admiralty Way, Suite 330
Email: tnadeau@lucidvision.com Marina del Rey, CA 90292
Tel: +1 310 823 9358
Zafar Ali E-Mail: iana@iana.org"
Cisco Systems, Inc.
Email: zali@cisco.com
Nobo Akiya
Cisco Systems, Inc.
Email: nobo@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB module defines TEXTUAL-CONVENTIONs for concepts "Copyright (C) The IETF Trust (2013). The initial version
used in Bidirectional Forwarding Detection (BFD) of this MIB module was published in RFC xxxx. For full legal
protocols." notices see the RFC itself. Supplementary information
REVISION "201306191200Z" -- 19 June 2013 12:00:00 EST may be available on:
http://www.ietf.org/copyrights/ianamib.html"
-- RFC Ed.: RFC-editor pls fill in xxxx
REVISION
"201311211200Z" -- 21 Nov. 2013 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx -- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: assigned by IANA, see section 5 for details -- RFC Ed.: assigned by IANA, see section 5 for details
IANAbfdSessIndexTC ::= TEXTUAL-CONVENTION
BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An index used to uniquely identify BFD sessions." "An index used to uniquely identify BFD sessions."
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
BfdIntervalTC ::= TEXTUAL-CONVENTION IANAbfdIntervalTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD interval in microseconds." "The BFD interval in microseconds."
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
BfdMultiplierTC ::= TEXTUAL-CONVENTION IANAbfdMultiplierTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BFD failure detection multiplier." "The BFD failure detection multiplier."
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
BfdDiagTC ::= TEXTUAL-CONVENTION IANAbfdDiagTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A common BFD diagnostic code." "A common BFD diagnostic code."
SYNTAX INTEGER { SYNTAX INTEGER {
noDiagnostic(0), noDiagnostic(0),
controlDetectionTimeExpired(1), controlDetectionTimeExpired(1),
echoFunctionFailed(2), echoFunctionFailed(2),
neighborSignaledSessionDown(3), neighborSignaledSessionDown(3),
forwardingPlaneReset(4), forwardingPlaneReset(4),
pathDown(5), pathDown(5),
concatenatedPathDown(6), concatenatedPathDown(6),
administrativelyDown(7), administrativelyDown(7),
reverseConcatenatedPathDown(8) reverseConcatenatedPathDown(8)
} }
BfdSessTypeTC ::= TEXTUAL-CONVENTION IANAbfdSessTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD session type" "BFD session type"
REFERENCE REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010. Detection (BFD), RFC 5880, June 2010.
Katz, D. and D. Ward, Bidirectional Forwarding Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop), Detection (BFD) for IPv4 and IPv6 (Single Hop),
RFC 5881, June 2010. RFC 5881, June 2010.
skipping to change at page 5, line 4 skipping to change at page 5, line 8
"Katz, D. and D. Ward, Bidirectional Forwarding "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010. Detection (BFD), RFC 5880, June 2010.
Katz, D. and D. Ward, Bidirectional Forwarding Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop), Detection (BFD) for IPv4 and IPv6 (Single Hop),
RFC 5881, June 2010. RFC 5881, June 2010.
Katz, D. and D. Ward, Bidirectional Forwarding Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for Multihop Paths, RFC 5883, Detection (BFD) for Multihop Paths, RFC 5883,
June 2010." June 2010."
SYNTAX INTEGER { SYNTAX INTEGER {
singleHop(1), singleHop(1),
multiHopTotallyArbitraryPaths(2), multiHopTotallyArbitraryPaths(2),
multiHopOutOfBandSignaling(3), multiHopOutOfBandSignaling(3),
multiHopUnidirectionalLinks(4), multiHopUnidirectionalLinks(4),
multiPointHead(5), multiPointHead(5),
multiPointTail(6) multiPointTail(6)
} }
BfdSessOperModeTC ::= TEXTUAL-CONVENTION IANAbfdSessOperModeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD session operating mode" "BFD session operating mode"
REFERENCE REFERENCE
"Katz, D. and D. Ward, "Bidirectional Forwarding "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD)", RFC 5880, June 2010." Detection (BFD), RFC 5880, June 2010."
SYNTAX INTEGER { SYNTAX INTEGER {
asyncModeWEchoFunction(1), asyncModeWEchoFunction(1),
asynchModeWOEchoFunction(2), asynchModeWOEchoFunction(2),
demandModeWEchoFunction(3), demandModeWEchoFunction(3),
demandModeWOEchoFunction(4) demandModeWOEchoFunction(4)
} }
BfdCtrlDestPortNumberTC ::= TEXTUAL-CONVENTION IANAbfdCtrlDestPortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"UDP destination port number of BFD control packets. "UDP destination port number of BFD control packets.
3784 represents single hop BFD session. 3784 represents single hop BFD session.
4784 represents multi hop BFD session. 4784 represents multi hop BFD session.
However, syntax is left open to wider range of values However, syntax is left open to wider range of values
purposely for two reasons: purposely for two reasons:
1. implementation uses non-compliant port number for 1. implementation uses non-compliant port number for
valid proprietary reason. valid proprietary reason.
2. potential future extension drafts." 2. potential future extension drafts."
REFERENCE REFERENCE
"Use of port 3784 from Katz, D. and D. Ward, "Use of port 3784 from Katz, D. and D. Ward,
Bidirectional Forwarding Bidirectional Forwarding Detection (BFD) for
Detection (BFD) for IPv4 and IPv6 (Single Hop)", IPv4 and IPv6 (Single Hop), RFC 5881, June 2010.
RFC 5881, June 2010.
Use of port 4784 from Katz, D. and D. Ward, Bidirectional Use of port 4784 from Katz, D. and D. Ward,
Forwarding Detection (BFD) for IPv4 and IPv6 Bidirectional Forwarding Detection (BFD) for
(Single Hop), RFC 5881, June 2010." Multihop Paths, RFC 5883, June 2010."
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
IANAbfdCtrlSourcePortNumberTC ::= TEXTUAL-CONVENTION
BfdCtrlSourcePortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"UDP source port number of BFD control packets. "UDP source port number of BFD control packets.
However, syntax is left open to wider range of values However, syntax is left open to wider range of values
purposely for two reasons: purposely for two reasons:
1. implementation uses non-compliant port number for 1. implementation uses non-compliant port number for
valid proprietary reason. valid proprietary reason.
2. potential future extension drafts." 2. potential future extension drafts."
REFERENCE REFERENCE
"Port 49152..65535 (RFC5881)" "Port 49152..65535 (RFC5881)"
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
BfdSessStateTC ::= TEXTUAL-CONVENTION IANAbfdSessStateTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD session state. State failing(5) is only applicable if "BFD session state. State failing(5) is only applicable if
corresponding session is running in BFD version 0." corresponding session is running in BFD version 0."
REFERENCE REFERENCE
"RFC 5880 - Bidirectional Forwarding Detection (BFD), Katz, "RFC 5880 - Bidirectional Forwarding Detection (BFD), Katz,
D., Ward, D., June 2010." D., Ward, D., June 2010."
SYNTAX INTEGER { SYNTAX INTEGER {
adminDown(1), adminDown(1),
down(2), down(2),
init(3), init(3),
up(4), up(4),
failing(5) failing(5)
} }
BfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION IANAbfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD authentication type" "BFD authentication type"
REFERENCE REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward, "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD), Bidirectional Forwarding Detection (BFD),
RFC 5880, June 2010." RFC 5880, June 2010."
SYNTAX INTEGER { SYNTAX INTEGER {
noAuthentication(-1), noAuthentication(-1),
reserved(0), reserved(0),
simplePassword(1), simplePassword(1),
keyedMD5(2), keyedMD5(2),
meticulousKeyedMD5(3), meticulousKeyedMD5(3),
keyedSHA1(4), keyedSHA1(4),
meticulousKeyedSHA1(5) meticulousKeyedSHA1(5)
} }
IANAbfdSessAuthenticationKeyTC ::= TEXTUAL-CONVENTION
BfdSessionAuthenticationKeyTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x " DISPLAY-HINT "1x "
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD authentication key type. "BFD authentication key type.
A BfdSessionAuthenticationKeyTC is always interpreted within An IANAbfdSessAuthenticationKeyTC is always interpreted
the context of an BfdSessAuthenticationTypeTC value. Every within the context of an IANAbfdSessAuthenticationTypeTC
usage of the BfdSessionAuthenticationTypeTC textual value. Every usage of the IANAbfdSessAuthenticationTypeTC
convention is required to specify the textual convention is required to specify the
BfdSessionAuthenticationKeyTC object that provides the IANAbfdSessAuthenticationKeyTC object that provides the
context. It is suggested that the context. It is suggested that the
BfdSessionAuthentcationTypeTC object be logically registered IANAbfdSessAuthenticationKeyTC object be logically registered
before the object(s) that use the before the object(s) that use the
BfdSessionAuthenticationKeyTC textual convention, if they IANAbfdSessAuthenticationKeyTC textual convention, if they
appear in the same logical row. appear in the same logical row.
The value of a BfdSessionAuthenticationKeyTC must always be The value of a IANAbfdSessAuthenticationKeyTC must
consistent with the value of the associated always be consistent with the value of the associated
BfdSessionAuthencationTypeTC object. Attempts to set a IANAbfdSessAuthenticationTypeTC object. Attempts to set a
BfdSessionAuthenticationKeyTC object to a value inconsistent IANAbfdSessAuthenticationKeyTC object to a value inconsistent
with the associated BfdSessionAuthenticationTypeTC must fail with the associated IANAbfdSessAuthenticationTypeTC must fail
with an inconsistentValue error. with an inconsistentValue error.
The following size constraints for a The following size constraints for a
BfdSessionAuthenticationKeyTC object are defined for the IANAbfdSessAuthenticationKeyTC object are defined for the
associated BfdSessionAuthenticationTypeTC values show below: associated IANAbfdSessAuthenticationTypeTC values show below:
noAuthentication(-1): SIZE(0) noAuthentication(-1): SIZE(0)
reserved(0): SIZE(0) reserved(0): SIZE(0)
simplePassword(1): SIZE(1..16) simplePassword(1): SIZE(1..16)
keyedMD5(2): SIZE(16) keyedMD5(2): SIZE(16)
meticulousKeyedMD5(3): SIZE(16) meticulousKeyedMD5(3): SIZE(16)
keyedSHA1(4): SIZE(20) keyedSHA1(4): SIZE(20)
meticulousKeyedSHA1(5): SIZE(20) meticulousKeyedSHA1(5): SIZE(20)
When this textual convention is used as the syntax of an When this textual convention is used as the syntax of an
skipping to change at page 8, line 17 skipping to change at page 8, line 18
This module does not define any management objects. Instead, it This module does not define any management objects. Instead, it
defines a set of textual conventions which may be used by other BFD defines a set of textual conventions which may be used by other BFD
MIB modules to define management objects. MIB modules to define management objects.
Meaningful security considerations can only be written in the MIB Meaningful security considerations can only be written in the MIB
modules that define management objects. Therefore, this document has modules that define management objects. Therefore, this document has
no impact on the security of the Internet. no impact on the security of the Internet.
5. IANA Considerations 5. IANA Considerations
The MIB module in this document uses the following IANA-assigned This document provides the base definition of the IANA-BFD-TC-STD-MIB
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: module. This MIB module is under the direct control of IANA. Please
see the most updated version of this MIB at <http://www.iana.org/
assignments/bfdtc-mib>. [RFC-Editor's Note (to be removed prior to
publication): the IANA is requested to create page pointed to by
URL.]
Descriptor OBJECT IDENTIFIER value This MIB makes reference to the following documents: [RFC2578],
---------- ----------------------- [RFC2579], [RFC5880], [RFC5881] and [RFC5883].
bfdTCStdMib { mib-2 XXX } IANA assigned an OID to the IANA-BFD-TC-STD-MIB module specified in
this document as { mib-2 XXX }. [RFC-Editor's Note (to be removed
prior to publication): the IANA is requested to assign a value for
"XXX" under the 'mib-2' subtree and to record the assignment in the
SMI Numbers registry. When the assignment has been made, the RFC
Editor is asked to replace "XXX" (here and in the MIB module) with
the assigned value and to remove this note.]
[Editor's Note (to be removed prior to publication): the IANA is 6. Acknowledgments
requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove
this note.]
6. References Authors would like to thank David Ward and Jeffrey Haas for their
comments and suggestions.
6.1. Normative References 7. References
7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
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", STD Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD
skipping to change at page 9, line 15 skipping to change at page 9, line 23
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, June 2010.
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
2010. 2010.
[RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD) for Multihop Paths", RFC 5883, June 2010. (BFD) for Multihop Paths", RFC 5883, June 2010.
6.2. Informative References 7.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62, RFC
3413, December 2002.
Appendix A. Acknowledgments
Authors would like to thank David Ward and Jeffrey Haas for their
comments and suggestions.
Authors' Addresses Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Juniper Networks
EMail: tnadeau@juniper.net EMail: tnadeau@juniper.net
Zafar Ali Zafar Ali
Cisco Systems Cisco Systems
 End of changes. 41 change blocks. 
97 lines changed or deleted 89 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/