draft-ietf-bfd-tc-mib-00.txt   draft-ietf-bfd-tc-mib-01.txt 
Network Working Group T. Nadeau Network Working Group T. Nadeau
Internet Draft BT Internet Draft Juniper Networks
Intended status: Standards Track Z. Ali Intended status: Standards Track Z. Ali
Expires: March 6, 2010 Cisco Systems, Inc. Expires: December 14, 2012 N. Akiya
N. Akiya Cisco Systems
Cisco Systems G.K. June 14, 2012
September 7, 2010
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-00 draft-ietf-bfd-tc-mib-01
Abstract
This draft defines a Management Information Base (MIB) module which
contains Textual Conventions to represent commonly used Bidirectional
Forwarding Detection (BFD) management information. The intent is
that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD
related MIB modules that would otherwise define their own
representations.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
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). Note that other groups may also distribute
other groups may also distribute working documents as Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts. 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."
The list of current Internet-Drafts can be accessed at This Internet-Draft will expire on November 4, 2012.
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at BFD-TC-STD-MIB June 14, 2012
http://www.ietf.org/shadow.html
Copyright and License Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. Copyright (c) 2012 IETF Trust and the persons identified as the
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 carefully, as they describe your rights and restrictions with respect
respect to this document. Code Components extracted from this to this document. Code Components extracted from this document must
document must include Simplified BSD License text as described include Simplified BSD License text as described in Section 4.e of
in Section 4.e of the Trust Legal Provisions and are provided the Trust Legal Provisions and are provided without warranty as
without warranty as described in the Simplified BSD License. described in the Simplified BSD License.
Abstract Requirements Language
This draft defines a Management Information Base (MIB) module which The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
contains Textual Conventions to represent commonly used Bidirectional "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
Forwarding Detection (BFD) management information. The intent is document are to be interpreted as described in RFC-2119 [RFC2119].
that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD
related MIB modules that would otherwise define their own
representations.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3 3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3
4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
6.1. Normative References . . . . . . . . . . . . . . . . . . 8 6.1. Normative References . . . . . . . . . . . . . . . . . . 8
skipping to change at page 3, line 5 skipping to change at page 3, line 5
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.
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
BFD-TC-STD-MIB June 14, 2012
For an introduction to the concepts of BFD, see [BFD], [BFD-1HOP] and For an introduction to the concepts of BFD, see [BFD], [BFD-1HOP] and
[BFD-MH]. [BFD-MH].
2. The Internet-Standard Management Framework 2. The Internet-Standard Management Framework
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
[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,
[RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. BFD Textual Conventions MIB Definitions 3. BFD Textual Conventions MIB Definitions
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]
bfdTCStdMib MODULE-IDENTITY bfdTCStdMib MODULE-IDENTITY
LAST-UPDATED "201009071200Z" -- 7 September 2010 12:00:00 EST LAST-UPDATED "201206141200Z" -- 14 June 2012 12:00:00 EST
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
BT Juniper Networks
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya Nobo Akiya
Cisco Systems, G.K. Cisco Systems, G.K.
BFD-TC-STD-MIB June 14, 2012
Email: nobo@cisco.com" Email: nobo@cisco.com"
DESCRIPTION DESCRIPTION
"This MIB module defines TEXTUAL-CONVENTIONs for concepts "This MIB module defines TEXTUAL-CONVENTIONs for concepts
used in Bidirectional Forwarding Detection (BFD) used in Bidirectional Forwarding Detection (BFD)
protocols." protocols."
REVISION "201009071200Z" -- 7 September 2010 12:00:00 EST REVISION "201206141200Z" -- 14 June 2012 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
BfdSessIndexTC ::= TEXTUAL-CONVENTION BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 4, line 48 skipping to change at page 5, line 4
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)
} }
BFD-TC-STD-MIB June 14, 2012
BfdSessTypeTC ::= TEXTUAL-CONVENTION BfdSessTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD session type" "BFD session type"
REFERENCE REFERENCE
"RFC5880, RFC5881, RFC5883" "Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010.
Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for IPv4 and IPv6 (Single Hop),
RFC 5881, June 2010.
Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for Multihop Paths, RFC 5883,
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 BfdSessOperModeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD session operating mode" "BFD session operating mode"
REFERENCE REFERENCE
"RFC5880, Section 3.2" "Katz, D. and D. Ward, "Bidirectional Forwarding
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 BfdCtrlDestPortNumberTC ::= 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:
BFD-TC-STD-MIB June 14, 2012
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 3784 (RFC5881) and Port 4784 (RFC5883)" "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 IPv4 and IPv6
(Single Hop), RFC 5881, June 2010."
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
BfdCtrlSourcePortNumberTC ::= 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
skipping to change at page 6, line 16 skipping to change at page 6, line 41
REFERENCE REFERENCE
"Port 49152..65535 (RFC5881)" "Port 49152..65535 (RFC5881)"
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
BfdSessStateTC ::= TEXTUAL-CONVENTION BfdSessStateTC ::= 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
"draft-katz-ward-bfd-02.txt, RFC5880" "RFC 5880 - Bidirectional Forwarding Detection (BFD), Katz,
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 BfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"BFD authentication type" "BFD authentication type"
BFD-TC-STD-MIB June 14, 2012
REFERENCE REFERENCE
"RFC5880, Sections 4.2 - 4.4" "Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD),
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)
} }
skipping to change at page 7, line 25 skipping to change at page 8, line 4
The following size constraints for a The following size constraints for a
BfdSessionAuthenticationKeyTC object are defined for the BfdSessionAuthenticationKeyTC object are defined for the
associated BfdSessionAuthenticationTypeTC values show below: associated BfdSessionAuthenticationTypeTC 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)
BFD-TC-STD-MIB June 14, 2012
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
index object, there may be issues with the limit of 128 index object, there may be issues with the limit of 128
sub-identifiers specified in SMIv2, STD 58. In this case, sub-identifiers specified in SMIv2, STD 58. In this case,
the object definition MUST include a 'SIZE' clause to limit the object definition MUST include a 'SIZE' clause to limit
the number of potential instance sub-identifiers; otherwise the number of potential instance sub-identifiers; otherwise
the applicable constraints MUST be stated in the appropriate the applicable constraints MUST be stated in the appropriate
conceptual row DESCRIPTION clauses, or in the surrounding conceptual row DESCRIPTION clauses, or in the surrounding
documentation if there is no single DESCRIPTION clause that documentation if there is no single DESCRIPTION clause that
skipping to change at page 8, line 15 skipping to change at page 8, line 43
5. IANA Considerations 5. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
bfdTCStdMib { mib-2 XXX } bfdTCStdMib { mib-2 XXX }
[Editor's Note (to be removed prior to publication): the IANA is [RFC Editor Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" 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 (here and in the MIB module) with the assigned value and to remove
this note.] this note.]
6. References 6. References
BFD-TC-STD-MIB June 14, 2012
6.1. Normative References 6.1. Normative References
[BFD] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding
Detection (BFD)", RFC 5880, June 2010. Detection (BFD)", RFC 5880, June 2010.
[BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding [BFD-1HOP] 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 8, line 45 skipping to change at page 9, line 27
June 2010. June 2010.
[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", 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,
"Conformance Statements for SMIv2", RFC 2580, STD 58,
April 1999.
6.2. Informative References 6.2. Informative 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.
[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.
[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network
Management Protocol (SNMP) Applications", STD 62,
RFC 3413, December 2002.
Appendix A. Acknowledgments Appendix A. Acknowledgments
We would like to thank David Ward and Jeffrey Haas for their comments We would like to thank David Ward and Jeffrey Haas for their comments
and suggestions. and suggestions.
Authors' Addresses Authors' Addresses
Thomas D. Nadeau Thomas D. Nadeau
BT Juniper Networks
BT Centre
81 Newgate Street
London EC1A 7AJ
United Kingdom
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
BFD-TC-STD-MIB June 14, 2012
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
2000 Innovation Drive 2000 Innovation Drive
Kanata, Ontario K2K 3E8 Kanata, Ontario K2K 3E8
Canada Canada
Email: zali@cisco.com Email: zali@cisco.com
Nobo Akiya Nobo Akiya
 End of changes. 36 change blocks. 
64 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/