draft-ietf-bfd-tc-mib-08.txt   rfc7330.txt 
Network Working Group T. Nadeau Internet Engineering Task Force (IETF) T. Nadeau
Internet-Draft Brocade Request for Comments: 7330 Brocade
Intended status: Standards Track Z. Ali Category: Standards Track Z. Ali
Expires: November 15, 2014 N. Akiya ISSN: 2070-1721 N. Akiya
Cisco Systems Cisco Systems
May 14, 2014 August 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-08
Abstract Abstract
This draft defines two Management Information Base (MIB) modules that This document defines two Management Information Base (MIB) modules
contain Textual Conventions to represent commonly used Bidirectional that contain Textual Conventions to represent commonly used
Forwarding Detection (BFD) management information. The intent is Bidirectional Forwarding Detection (BFD) management information. The
that these TEXTUAL CONVENTIONS (TCs) will be imported and used in BFD intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and
related MIB modules that would otherwise define their own used in BFD-related MIB modules that would otherwise define their own
representations. representations.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on November 15, 2014. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7330.
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
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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction ....................................................2
2. The Internet-Standard Management Framework . . . . . . . . . 2 1.1. Requirements Language ......................................2
3. BFD Textual Conventions MIB Definitions . . . . . . . . . . . 3 2. The Internet-Standard Management Framework ......................2
4. Security Considerations . . . . . . . . . . . . . . . . . . . 9 3. BFD Textual Conventions MIB Definitions .........................3
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 4. Security Considerations .........................................9
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10 5. IANA Considerations ............................................10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 6. Acknowledgments ................................................10
7.1. Normative References . . . . . . . . . . . . . . . . . . 10 7. References .....................................................10
7.2. Informative References . . . . . . . . . . . . . . . . . 11 7.1. Normative References ......................................10
7.2. Informative References ....................................11
1. Introduction 1. Introduction
This document defines two MIB modules that contain Textual This document defines two MIB modules that contain Textual
Conventions for Bidirectional Forwarding Detection (BFD) protocols. Conventions for Bidirectional Forwarding Detection (BFD) protocols.
These Textual Conventions should be imported by MIB modules which These Textual Conventions should be imported by MIB modules that
manage BFD protocols. manage BFD protocols.
Note that names of Textual Conventions defined in this document are Note that names of Textual Conventions defined in this document are
prefixed with either "Bfd" or "IANA" to make it obvious to readers prefixed with either "Bfd" or "IANA" to make it obvious to readers
that some are specific to BFD modules, while others are IANA that some are specific to BFD modules, whereas others are IANA
maintained. maintained.
For an introduction to the concepts of BFD, see [RFC5880], [RFC5881], For an introduction to the concepts of BFD, see [RFC5880], [RFC5881],
[RFC5883], [RFC6428] and [RFC7130]. [RFC5883], [RFC6428], and [RFC7130].
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119].
2. The Internet-Standard Management Framework 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].
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], [RFC5883], [RFC6428] and [RFC2578], [RFC2579], [RFC5880], [RFC5881], [RFC5883], [RFC6428], and
[RFC7130]. [RFC7130].
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 -- RFC 2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- RFC 2579
bfdTCStdMib MODULE-IDENTITY bfdTCStdMib MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201404131200Z" -- 13 April 2014 12:00:00 EST "201408120000Z" -- 12 August 2014 00:00:00 GMT
ORGANIZATION "IETF Bidirectional Forwarding Detection ORGANIZATION "IETF Bidirectional Forwarding Detection
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"Thomas D. Nadeau "Thomas D. Nadeau
Brocade Brocade
Email: tnadeau@lucidvision.com Email: tnadeau@lucidvision.com
Zafar Ali Zafar Ali
Cisco Systems, Inc. Cisco Systems, Inc.
skipping to change at page 4, line 4 skipping to change at page 3, line 47
Nobo Akiya Nobo Akiya
Cisco Systems, Inc. Cisco Systems, Inc.
Email: nobo@cisco.com Email: nobo@cisco.com
Comments about this document should be emailed directly Comments about this document should be emailed directly
to the BFD working group mailing list at to the BFD working group mailing list at
rtg-bfd@ietf.org" rtg-bfd@ietf.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial version "Copyright (c) 2014 IETF Trust and the persons identified as
of this MIB module was published in RFC xxxx. For full legal authors of the code. All rights reserved.
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 Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION "201404131200Z" -- 13 April 2014 12:00:00 EST REVISION "201408120000Z" -- 12 August 2014 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC 7330."
-- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 XXX }
-- RFC Ed.: RFC-editor pls fill in XXX, see section 5 for details ::= { mib-2 223 }
BfdSessIndexTC ::= 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 BfdIntervalTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
skipping to change at page 4, line 48 skipping to change at page 4, line 41
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 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.
6784 represents BFD on LAG session. 6784 represents BFD on Link Aggregation Group (LAG) 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 documents.
The value of 0 is a special, reserved value used The value of 0 is a special, reserved value used
to indicate special conditions and should not be considered to indicate special conditions and should not be considered
a valid port number." a valid port number."
REFERENCE REFERENCE
"Use of port 3784 from Katz, D. and D. Ward, "Use of port 3784 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD) for Bidirectional Forwarding Detection (BFD) for
IPv4 and IPv6 (Single Hop), RFC 5881, June 2010. IPv4 and IPv6 (Single Hop), RFC 5881, June 2010.
Use of port 4784 from Katz, D. and D. Ward, Use of port 4784 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD) for Bidirectional Forwarding Detection (BFD) for
Multihop Paths, RFC 5883, June 2010. Multihop Paths, RFC 5883, June 2010.
Use of port 6784 from Bhatia, M., Chen, M., Boutros, S., Use of port 6784 from Bhatia, M., Chen, M., Boutros, S.,
Binderberger, M., and J. Haas, Bidirectional Forwarding Binderberger, M., and J. Haas, Bidirectional Forwarding
Detection (BFD) on Link Aggregation Group (LAG) Detection (BFD) on Link Aggregation Group (LAG)
Interfaces, RFC 7130, February 2014." Interfaces, RFC 7130, February 2014."
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
valid proprietary reason. valid proprietary reason.
2. Potential future extension drafts. 2. Potential future extension documents.
The value of 0 is a special, reserved value used The value of 0 is a special, reserved value used
to indicate special conditions and should not be considered to indicate special conditions and should not be considered
a valid port number." a valid port number."
REFERENCE REFERENCE
"Port 49152..65535 from RFC5881" "Port 49152..65535 from RFC5881"
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
END END
skipping to change at page 6, line 4 skipping to change at page 5, line 45
to indicate special conditions and should not be considered to indicate special conditions and should not be considered
a valid port number." a valid port number."
REFERENCE REFERENCE
"Port 49152..65535 from RFC5881" "Port 49152..65535 from RFC5881"
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
END END
IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2 MODULE-IDENTITY, mib-2
FROM SNMPv2-SMI -- [RFC2578] FROM SNMPv2-SMI -- RFC 2578
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; -- [RFC2579] FROM SNMPv2-TC; -- RFC 2579
ianaBfdTCStdMib MODULE-IDENTITY ianaBfdTCStdMib MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201404131200Z" -- 13 April 2014 12:00:00 EST "201408120000Z" -- 12 August 2014 00:00:00 GMT
ORGANIZATION ORGANIZATION
"IANA" "IANA"
CONTACT-INFO CONTACT-INFO
"Internet Assigned Numbers Authority "Internet Assigned Numbers Authority
Postal: 4676 Admiralty Way, Suite 330 Postal: 12025 Waterfront Drive, Suite 300
Marina del Rey, CA 90292 Los Angeles, CA 90094-2536
Tel: +1 310 823 9358 Tel: +1 310 301 5800
E-Mail: iana@iana.org" EMail: iana@iana.org"
DESCRIPTION DESCRIPTION
"Copyright (C) The IETF Trust (2014). The initial version "Copyright (c) 2014 IETF Trust and the persons identified as
of this MIB module was published in RFC xxxx. For full legal authors of the code. All rights reserved.
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 Redistribution and use in source and binary forms, with or
without modification, is permitted pursuant to, and subject
to the license terms contained in, the Simplified BSD License
set forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents
(http://trustee.ietf.org/license-info)."
REVISION REVISION
"201404131200Z" -- 13 April 2014 12:00:00 EST "201408120000Z" -- 12 August 2014 00:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial version. Published as RFC xxxx." "Initial version. Published as RFC 7330."
-- RFC Ed.: RFC-editor pls fill in xxxx
::= { mib-2 YYY }
-- RFC Ed.: RFC-editor pls fill in YYY, see section 5 for details ::= { mib-2 224 }
IANAbfdDiagTC ::= TEXTUAL-CONVENTION IANAbfdDiagTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A common BFD diagnostic code." "A common BFD diagnostic code."
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.
Allan, D., Swallow, G., and Drake, J., Proactive Connectivity Allan, D., Swallow, G., and Drake, J., Proactive Connectivity
Verification, Continuity Check, and Remote Defect Verification, Continuity Check, and Remote Defect
Indication for the MPLS Transport Profile, RFC 6428, Indication for the MPLS Transport Profile, RFC 6428,
November 2011." 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) 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.
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)
} }
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)
} }
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, "Katz, D. and D. Ward, Bidirectional Forwarding
D., Ward, D., June 2010." Detection (BFD), RFC 5880, 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)
} }
IANAbfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION IANAbfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 9, line 11 skipping to change at page 9, line 5
within the context of an IANAbfdSessAuthenticationTypeTC within the context of an IANAbfdSessAuthenticationTypeTC
value. Every usage of the IANAbfdSessAuthenticationTypeTC value. Every usage of the IANAbfdSessAuthenticationTypeTC
textual convention is required to specify the textual convention is required to specify the
IANAbfdSessAuthenticationKeyTC object that provides the IANAbfdSessAuthenticationKeyTC object that provides the
context. It is suggested that the context. It is suggested that the
IANAbfdSessAuthenticationKeyTC object be logically registered IANAbfdSessAuthenticationKeyTC object be logically registered
before the object(s) that use the before the object(s) that use the
IANAbfdSessAuthenticationKeyTC 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 IANAbfdSessAuthenticationKeyTC must The value of an IANAbfdSessAuthenticationKeyTC must
always be consistent with the value of the associated always be consistent with the value of the associated
IANAbfdSessAuthenticationTypeTC object. Attempts to set a IANAbfdSessAuthenticationTypeTC object. Attempts to set an
IANAbfdSessAuthenticationKeyTC object to a value inconsistent IANAbfdSessAuthenticationKeyTC object to a value inconsistent
with the associated IANAbfdSessAuthenticationTypeTC 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 an
IANAbfdSessAuthenticationKeyTC object are defined for the IANAbfdSessAuthenticationKeyTC object are defined for the
associated IANAbfdSessAuthenticationTypeTC 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
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
is appropriate." is appropriate."
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 OCTET STRING(SIZE(0..252)) SYNTAX OCTET STRING(SIZE(0..252))
END END
4. Security Considerations 4. Security Considerations
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 modules that define management objects. This document has therefore
does not introduce any additional security considerations. no impact on the security of the Internet.
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. See module. This MIB module is under the direct control of IANA. See
Section 3 for the initial contents. Please see the most updated Section 3 for the initial contents. See the most updated version of
version of this MIB at <http://www.iana.org/assignments/ianabfdtcstd- this MIB at <http://www.iana.org/assignments/ianabfdtcstd-mib>.
mib>. [RFC-Editor's Note (to be removed prior to publication): the Assignments of IANA-BFD-TC-STD-MIB are via IETF Review [RFC5226].
IANA is requested to create page pointed to by URL.] Assignments of
IANA-BFD-TC-STD-MIB are via IETF Review [RFC5226].
This MIB makes reference to the following documents: [RFC2578], This MIB makes reference to the following documents: [RFC2578],
[RFC2579], [RFC5880], [RFC5881] and [RFC5883], [RFC6428] and [RFC2579], [RFC5880], [RFC5881] and [RFC5883], [RFC6428], and
[RFC7130]. [RFC7130].
IANA assigned an OID to the BFD-TC-STD-MIB module specified in this 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 document as { mib-2 223 }.
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 YYY }. [RFC-Editor's Note (to be removed this document as { mib-2 224 }.
prior to publication): the IANA is requested to assign a value for
"YYY" 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 "YYY" (here and in the MIB module) with
the assigned value and to remove this note.]
6. Acknowledgments 6. Acknowledgments
Authors would like to thank Adrian Farrel and Jeffrey Haas for The authors would like to thank Adrian Farrel and Jeffrey Haas for
performing thorough reviews and providing number of suggestions. performing thorough reviews and providing a number of suggestions.
Authors would also like to thank David Ward and Christer Holmberg for The authors would also like to thank David Ward and Christer Holmberg
his comments and suggestions. for their 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
 End of changes. 58 change blocks. 
133 lines changed or deleted 119 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/