draft-ietf-bfd-tc-mib-04.txt   draft-ietf-bfd-tc-mib-05.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet-Draft Juniper Networks Internet-Draft Brocade
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: May 25, 2014 N. Akiya Expires: October 16, 2014 N. Akiya
Cisco Systems Cisco Systems
November 21, 2013 April 14, 2014
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-04 draft-ietf-bfd-tc-mib-05
Abstract Abstract
This draft defines a Management Information Base (MIB) module which This draft defines two Management Information Base (MIB) modules that
contains Textual Conventions to represent commonly used Bidirectional contain 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.
Requirements Language Requirements Language
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
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 25, 2014. This Internet-Draft will expire on October 16, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2013 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. The Internet-Standard Management Framework . . . . . . . . . 2
3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3 3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8 4. Security Considerations . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.1. Normative References . . . . . . . . . . . . . . . . . . 8 7.1. Normative References . . . . . . . . . . . . . . . . . . 10
7.2. Informative References . . . . . . . . . . . . . . . . . 9 7.2. Informative References . . . . . . . . . . . . . . . . . 11
1. The Internet-Standard Management Framework 1. Introduction
This document defines two MIB modules that contain Textual
Conventions for Bidirectional Forwarding Detection (BFD) protocols.
These Textual Conventions should be imported by MIB modules which
manage BFD protocols.
Note that names of Textual Conventions defined in this document are
prefixed with either "Bfd" or "IANA" to make it obvious to readers
that some are specific to BFD modules, while others are IANA
maintained.
For an introduction to the concepts of BFD, see [RFC5880], [RFC5881],
[RFC5883], [RFC6428] and [RFC7130].
2. 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).
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].
2. Introduction
This document defines a MIB module which contains Textual Conventions
for Bidirectional Forwarding Detection (BFD) protocols. These
Textual Conventions should be imported by MIB modules which manage
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]
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:
[RFC2578], [RFC2579], [RFC5880], [RFC5881] and [RFC5883]. [RFC2578], [RFC2579], [RFC5880], [RFC5881], [RFC5883], [RFC6428] and
[RFC7130].
IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN 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]
ianaBfdTCStdMib MODULE-IDENTITY bfdTCStdMib MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201311211200Z" -- 21 Nov. 2013 12:00:00 EST "201404131200Z" -- 13 April 2014 12:00:00 EST
ORGANIZATION
"IANA" ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group"
CONTACT-INFO CONTACT-INFO
"Internet Assigned Numbers Authority "Thomas D. Nadeau
Postal: 4676 Admiralty Way, Suite 330 Brocade
Marina del Rey, CA 90292 Email: tnadeau@lucidvision.com
Tel: +1 310 823 9358
E-Mail: iana@iana.org" Zafar Ali
Cisco Systems, Inc.
Email: zali@cisco.com
Nobo Akiya
Cisco Systems, Inc.
Email: nobo@cisco.com
Comments about this document should be emailed directly
to the BFD working group mailing list at
rtg-bfd@ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2013). The initial version "Copyright (C) The IETF Trust (2014). The initial version
of this MIB module was published in RFC xxxx. For full legal of this MIB module was published in RFC xxxx. For full legal
notices see the RFC itself. Supplementary information notices see the RFC itself. Supplementary information
may be available on: may be available on:
http://www.ietf.org/copyrights/ianamib.html" http://www.ietf.org/copyrights/ianamib.html"
-- RFC Ed.: RFC-editor pls fill in xxxx
REVISION -- RFC Ed.: RFC-editor pls fill in xxxx
"201311211200Z" -- 21 Nov. 2013 12:00:00 EST
REVISION "201404131200Z" -- 13 April 2014 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
IANAbfdSessIndexTC ::= TEXTUAL-CONVENTION -- RFC Ed.: RFC-editor pls fill in XXX, see section 5 for details
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)
IANAbfdIntervalTC ::= TEXTUAL-CONVENTION BfdIntervalTC ::= 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)
IANAbfdMultiplierTC ::= TEXTUAL-CONVENTION BfdMultiplierTC ::= 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)
BfdCtrlDestPortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"UDP destination port number of BFD control packets.
3784 represents single hop BFD session.
4784 represents multi hop BFD session.
6784 represents BFD on LAG session.
However, syntax is left open to wider range of values
purposely for two reasons:
1. Implementation uses non-compliant port number for
valid proprietary reason.
2. Potential future extension drafts.
The value of 0 is a special, reserved value used
to indicate special conditions and should not be considered
a valid port number."
REFERENCE
"Use of port 3784 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD) for
IPv4 and IPv6 (Single Hop), RFC 5881, June 2010.
Use of port 4784 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD) for
Multihop Paths, RFC 5883, June 2010.
Use of port 6784 from Bhatia, M., Chen, M., Boutros, S.,
Binderberger, M., and J. Haas, Bidirectional Forwarding
Detection (BFD) on Link Aggregation Group (LAG)
Interfaces, RFC 7130, February 2014."
SYNTAX Unsigned32 (0..65535)
BfdCtrlSourcePortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"UDP source port number of BFD control packets.
However, syntax is left open to wider range of values
purposely for two reasons:
1. Implementation uses non-compliant port number for
valid proprietary reason.
2. Potential future extension drafts.
The value of 0 is a special, reserved value used
to indicate special conditions and should not be considered
a valid port number."
REFERENCE
"Port 49152..65535 from RFC5881"
SYNTAX Unsigned32 (0..65535)
END
IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578]
TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579]
ianaBfdTCStdMib MODULE-IDENTITY
LAST-UPDATED
"201404131200Z" -- 13 April 2014 12:00:00 EST
ORGANIZATION
"IANA"
CONTACT-INFO
"Internet Assigned Numbers Authority
Postal: 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292
Tel: +1 310 823 9358
E-Mail: iana@iana.org"
DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial version
of this MIB module was published in RFC xxxx. For full legal
notices see the RFC itself. Supplementary information
may be available on:
http://www.ietf.org/copyrights/ianamib.html"
-- RFC Ed.: RFC-editor pls fill in xxxx
REVISION
"201404131200Z" -- 13 April 2014 12:00:00 EST
DESCRIPTION
"Initial version. Published as RFC xxxx."
-- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX }
-- RFC Ed.: RFC-editor pls fill in XXX, see section 5 for details
IANAbfdDiagTC ::= TEXTUAL-CONVENTION IANAbfdDiagTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A common BFD diagnostic code." "A common BFD diagnostic code."
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010.
Allan, D., Swallow, G., and Drake, J., Proactive Connectivity
Verification, Continuity Check, and Remote Defect
Indication for the MPLS Transport Profile, RFC 6428,
November 2011."
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),
misConnectivityDefect(9)
} }
IANAbfdSessTypeTC ::= 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.
skipping to change at page 5, line 12 skipping to change at page 7, line 39
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),
multiPointTail(6)
} }
IANAbfdSessOperModeTC ::= 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)
} }
IANAbfdCtrlDestPortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"UDP destination port number of BFD control packets.
3784 represents single hop BFD session.
4784 represents multi hop BFD session.
However, syntax is left open to wider range of values
purposely for two reasons:
1. implementation uses non-compliant port number for
valid proprietary reason.
2. potential future extension drafts."
REFERENCE
"Use of port 3784 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD) for
IPv4 and IPv6 (Single Hop), RFC 5881, June 2010.
Use of port 4784 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD) for
Multihop Paths, RFC 5883, June 2010."
SYNTAX Unsigned32 (0..65535)
IANAbfdCtrlSourcePortNumberTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"UDP source port number of BFD control packets.
However, syntax is left open to wider range of values
purposely for two reasons:
1. implementation uses non-compliant port number for
valid proprietary reason.
2. potential future extension drafts."
REFERENCE
"Port 49152..65535 (RFC5881)"
SYNTAX Unsigned32 (0..65535)
IANAbfdSessStateTC ::= 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),
skipping to change at page 8, line 26 skipping to change at page 10, line 19
5. IANA Considerations 5. IANA Considerations
This document provides the base definition of the IANA-BFD-TC-STD-MIB This document provides the base definition of the IANA-BFD-TC-STD-MIB
module. This MIB module is under the direct control of IANA. Please 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/ 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 assignments/bfdtc-mib>. [RFC-Editor's Note (to be removed prior to
publication): the IANA is requested to create page pointed to by publication): the IANA is requested to create page pointed to by
URL.] URL.]
This MIB makes reference to the following documents: [RFC2578], This MIB makes reference to the following documents: [RFC2578],
[RFC2579], [RFC5880], [RFC5881] and [RFC5883]. [RFC2579], [RFC5880], [RFC5881] and [RFC5883], [RFC6428] and
[RFC7130].
IANA assigned an OID to the 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.]
IANA assigned an OID to the IANA-BFD-TC-STD-MIB module specified in 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 this document as { mib-2 YYY }. [RFC-Editor's Note (to be removed
prior to publication): the IANA is requested to assign a value for 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 "YYY" under the 'mib-2' subtree and to record the assignment in the
SMI Numbers registry. When the assignment has been made, the RFC SMI Numbers registry. When the assignment has been made, the RFC
Editor is asked to replace "XXX" (here and in the MIB module) with Editor is asked to replace "YYY" (here and in the MIB module) with
the assigned value and to remove this note.] the assigned value and to remove this note.]
6. Acknowledgments 6. Acknowledgments
Authors would like to thank David Ward and Jeffrey Haas for their Authors would like to thank Adrian Farrel and Jeffrey Haas for
comments and suggestions. performing thorough reviews and providing number of suggestions.
Authors would also like to thank David Ward for his comments and
suggestions.
7. References 7. References
7.1. Normative 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
skipping to change at page 9, line 23 skipping to change at page 11, line 27
[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.
[RFC6428] Allan, D., Swallow Ed. , G., and J. Drake Ed. , "Proactive
Connectivity Verification, Continuity Check, and Remote
Defect Indication for the MPLS Transport Profile", RFC
6428, November 2011.
[RFC7130] Bhatia, M., Chen, M., Boutros, S., Binderberger, M., and
J. Haas, "Bidirectional Forwarding Detection (BFD) on Link
Aggregation Group (LAG) Interfaces", RFC 7130, February
2014.
7.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.
Authors' Addresses Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
Juniper Networks Brocade
EMail: tnadeau@juniper.net
EMail: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems Cisco Systems
EMail: zali@cisco.com EMail: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems Cisco Systems
EMail: nobo@cisco.com EMail: nobo@cisco.com
 End of changes. 39 change blocks. 
100 lines changed or deleted 204 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/