Internet Engineering Task Force (IETF) T. Nadeau
Request for Comments: 7330 Brocade
Category: Standards Track Z. Ali
ISSN: 2070-1721 N. Akiya
Cisco Systems
August 2014
Internet Engineering Task Force (IETF) T. Nadeau
Request for Comments: 7330 Brocade
Category: Standards Track Z. Ali
ISSN: 2070-1721 N. Akiya
Cisco Systems
August 2014
Definitions of Textual Conventions (TCs) for Bidirectional Forwarding Detection (BFD) Management
双向转发检测（BFD）管理的文本约定（TC）定义
Abstract
摘要
This document defines two Management Information Base (MIB) modules that contain 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.
本文档定义了两个管理信息库（MIB）模块，其中包含表示常用双向转发检测（BFD）管理信息的文本约定。其目的是将这些文本约定（TC）导入并在BFD相关的MIB模块中使用，否则这些模块将定义它们自己的表示。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
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.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7330.
Copyright Notice
版权公告
Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2014 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................2
1.1. Requirements Language ......................................2
2. The Internet-Standard Management Framework ......................2
3. BFD Textual Conventions MIB Definitions .........................3
4. Security Considerations .........................................9
5. IANA Considerations ............................................10
6. Acknowledgments ................................................10
7. References .....................................................10
7.1. Normative References ......................................10
7.2. Informative References ....................................11
1. Introduction ....................................................2
1.1. Requirements Language ......................................2
2. The Internet-Standard Management Framework ......................2
3. BFD Textual Conventions MIB Definitions .........................3
4. Security Considerations .........................................9
5. IANA Considerations ............................................10
6. Acknowledgments ................................................10
7. References .....................................................10
7.1. Normative References ......................................10
7.2. Informative References ....................................11
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 that manage BFD protocols.
本文档定义了两个MIB模块，其中包含双向转发检测（BFD）协议的文本约定。这些文本约定应由管理BFD协议的MIB模块导入。
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, whereas others are IANA maintained.
请注意，本文档中定义的文本约定名称的前缀为“Bfd”或“IANA”，以便读者清楚地看到，一些特定于Bfd模块，而另一些是IANA维护的。
For an introduction to the concepts of BFD, see [RFC5880], [RFC5881], [RFC5883], [RFC6428], and [RFC7130].
有关BFD概念的介绍，请参阅[RFC5880]、[RFC5881]、[RFC5883]、[RFC6428]和[RFC7130]。
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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[RFC2119]中的说明进行解释。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。此备忘录指定了一个MIB
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 [RFC2580].
符合SMIv2的模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This MIB module makes references to the following documents: [RFC2578], [RFC2579], [RFC5880], [RFC5881], [RFC5883], [RFC6428], and [RFC7130].
此MIB模块参考以下文档：[RFC2578]、[RFC2579]、[RFC5880]、[RFC5881]、[RFC5883]、[RFC6428]和[RFC7130]。
BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2, Unsigned32 FROM SNMPv2-SMI -- RFC 2578
从SNMPv2 SMI--RFC 2578导入模块标识、mib-2、无符号32
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC 2579
SNMPv2 TC的文本约定；——RFC2579
bfdTCStdMib MODULE-IDENTITY LAST-UPDATED "201408120000Z" -- 12 August 2014 00:00:00 GMT
bfdTCStdMib模块标识最后更新的“201408120000Z”-2014年8月12日00:00:00 GMT
ORGANIZATION "IETF Bidirectional Forwarding Detection Working Group" CONTACT-INFO "Thomas D. Nadeau Brocade Email: tnadeau@lucidvision.com
组织“IETF双向转发检测工作组”联系方式“Thomas D.Nadeau Brocade电子邮件：tnadeau@lucidvision.com
Zafar Ali Cisco Systems, Inc. Email: zali@cisco.com
Zafar Ali Cisco Systems，Inc.电子邮件：zali@cisco.com
Nobo Akiya Cisco Systems, Inc. Email: nobo@cisco.com
Nobo Akiya Cisco Systems，Inc.电子邮件：nobo@cisco.com
Comments about this document should be emailed directly to the BFD working group mailing list at rtg-bfd@ietf.org"
有关本文件的意见应通过电子邮件直接发送至rtg的BFD工作组邮件列表-bfd@ietf.org"
DESCRIPTION "Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved.
说明“版权所有（c）2014 IETF信托基金和被确定为代码作者的人员。保留所有权利。
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)."
根据IETF信托公司与IETF文件相关的法律规定第4.c节中规定的简化BSD许可证中包含的许可条款(http://trustee.ietf.org/license-info)."
REVISION "201408120000Z" -- 12 August 2014 00:00:00 GMT DESCRIPTION "Initial version. Published as RFC 7330."
修订版“2014081200000Z”-2014年8月12日00:00:00 GMT描述“初始版本。发布为RFC 7330。”
::= { mib-2 223 }
::= { mib-2 223 }
BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An index used to uniquely identify BFD sessions."
SYNTAX Unsigned32 (1..4294967295)
BfdSessIndexTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An index used to uniquely identify BFD sessions."
SYNTAX Unsigned32 (1..4294967295)
BfdIntervalTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The BFD interval in microseconds."
SYNTAX Unsigned32 (0..4294967295)
BfdIntervalTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The BFD interval in microseconds."
SYNTAX Unsigned32 (0..4294967295)
BfdMultiplierTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The BFD failure detection multiplier."
SYNTAX Unsigned32 (1..255)
BfdMultiplierTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"The BFD failure detection multiplier."
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 Link Aggregation Group (LAG) session.
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 Link Aggregation Group (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 documents.
然而，出于两个原因，语法故意对更大范围的值开放：1。由于有效的专有原因，实现使用了不兼容的端口号。2.未来可能的扩展文档。
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.
0的值是一个特殊的保留值，用于指示特殊情况，不应视为有效的端口号。“参考”使用Katz，D.和D.Ward提供的端口3784，IPv4和IPv6的双向转发检测（BFD）（单跳），RFC 58812010年6月。
Use of port 4784 from Katz, D. and D. Ward, Bidirectional Forwarding Detection (BFD) for Multihop Paths, RFC 5883, June 2010.
使用Katz，D.和D.Ward的4784端口，用于多跳路径的双向转发检测（BFD），RFC 5883，2010年6月。
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)
使用来自Bhatia，M.，Chen，M.，Boutros，S.，Binderberger，M.，和J.Haas的6784端口，链路聚合组（LAG）接口上的双向转发检测（BFD），RFC 71302014年2月。“语法无符号32（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 documents.
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 documents.
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"
0的值是一个特殊的保留值，用于指示特殊情况，不应视为有效的端口号。“参考”RFC5881中的端口49152..65535
SYNTAX Unsigned32 (0..65535)
语法Unsigned32（0..65535）
END
终止
IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IANA-BFD-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- RFC 2578
从SNMPv2 SMI——RFC 2578导入模块标识mib-2
TEXTUAL-CONVENTION FROM SNMPv2-TC; -- RFC 2579
SNMPv2 TC的文本约定；——RFC2579
ianaBfdTCStdMib MODULE-IDENTITY
IANABFFDTCSTDMIB模块标识
LAST-UPDATED "201408120000Z" -- 12 August 2014 00:00:00 GMT ORGANIZATION "IANA" CONTACT-INFO "Internet Assigned Numbers Authority Postal: 12025 Waterfront Drive, Suite 300 Los Angeles, CA 90094-2536 Tel: +1 310 301 5800 EMail: iana@iana.org"
最新更新的“2014081200000Z”-2014年8月12日00:00:00 GMT组织“IANA”联系方式“互联网分配号码管理局邮政：12025 Waterfront Drive，Suite 300 Los Angeles，CA 90094-2536电话：+1 310 301 5800电子邮件：iana@iana.org"
DESCRIPTION "Copyright (c) 2014 IETF Trust and the persons identified as authors of the code. All rights reserved.
说明“版权所有（c）2014 IETF信托基金和被确定为代码作者的人员。保留所有权利。
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)."
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info)."
REVISION "201408120000Z" -- 12 August 2014 00:00:00 GMT DESCRIPTION "Initial version. Published as RFC 7330."
修订版“2014081200000Z”-2014年8月12日00:00:00 GMT描述“初始版本。发布为RFC 7330。”
::= { mib-2 224 }
::= { mib-2 224 }
IANAbfdDiagTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A common BFD diagnostic code."
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010.
IANAbfdDiagTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"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."
Allan，D.，Swallow，G.，和Drake，J.，MPLS传输配置文件的主动连接验证、连续性检查和远程缺陷指示，RFC 64282011年11月。”
SYNTAX INTEGER { noDiagnostic(0), controlDetectionTimeExpired(1), echoFunctionFailed(2),
语法整数{noDiagnostic（0），controlDetectionTimeExpired（1），echoFunctionFailed（2），
neighborSignaledSessionDown(3), forwardingPlaneReset(4), pathDown(5), concatenatedPathDown(6), administrativelyDown(7), reverseConcatenatedPathDown(8), misConnectivityDefect(9) }
邻居指定的会话下降（3）、转发平面重置（4）、路径下降（5）、连接路径下降（6）、管理路径下降（7）、反向连接路径下降（8）、错误连接结果（9）}
IANAbfdSessTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD session type"
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010.
IANAbfdSessTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD session type"
REFERENCE
"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.和D.Ward，IPv4和IPv6（单跳）的双向转发检测（BFD），RFC 58812010年6月。
Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for Multihop Paths, RFC 5883,
June 2010."
SYNTAX INTEGER {
singleHop(1),
multiHopTotallyArbitraryPaths(2),
multiHopOutOfBandSignaling(3),
multiHopUnidirectionalLinks(4)
}
Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD) for Multihop Paths, RFC 5883,
June 2010."
SYNTAX INTEGER {
singleHop(1),
multiHopTotallyArbitraryPaths(2),
multiHopOutOfBandSignaling(3),
multiHopUnidirectionalLinks(4)
}
IANAbfdSessOperModeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD session operating mode"
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010."
SYNTAX INTEGER {
asyncModeWEchoFunction(1),
asynchModeWOEchoFunction(2),
demandModeWEchoFunction(3),
demandModeWOEchoFunction(4)
}
IANAbfdSessOperModeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD session operating mode"
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010."
SYNTAX INTEGER {
asyncModeWEchoFunction(1),
asynchModeWOEchoFunction(2),
demandModeWEchoFunction(3),
demandModeWOEchoFunction(4)
}
IANAbfdSessStateTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
IANAbfdSessStateTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD session state. State failing(5) is only applicable if corresponding session is running in BFD version 0."
“BFD会话状态。状态失败（5）仅适用于在BFD版本0中运行相应会话的情况。”
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010."
SYNTAX INTEGER {
adminDown(1),
down(2),
init(3),
up(4),
failing(5)
}
REFERENCE
"Katz, D. and D. Ward, Bidirectional Forwarding
Detection (BFD), RFC 5880, June 2010."
SYNTAX INTEGER {
adminDown(1),
down(2),
init(3),
up(4),
failing(5)
}
IANAbfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD authentication type"
REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD),
RFC 5880, June 2010."
SYNTAX INTEGER {
noAuthentication(-1),
reserved(0),
simplePassword(1),
keyedMD5(2),
meticulousKeyedMD5(3),
keyedSHA1(4),
meticulousKeyedSHA1(5)
}
IANAbfdSessAuthenticationTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"BFD authentication type"
REFERENCE
"Sections 4.2 - 4.4 from Katz, D. and D. Ward,
Bidirectional Forwarding Detection (BFD),
RFC 5880, June 2010."
SYNTAX INTEGER {
noAuthentication(-1),
reserved(0),
simplePassword(1),
keyedMD5(2),
meticulousKeyedMD5(3),
keyedSHA1(4),
meticulousKeyedSHA1(5)
}
IANAbfdSessAuthenticationKeyTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x "
STATUS current
DESCRIPTION
"BFD authentication key type.
IANAbfdSessAuthenticationKeyTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1x "
STATUS current
DESCRIPTION
"BFD authentication key type.
An IANAbfdSessAuthenticationKeyTC is always interpreted within the context of an IANAbfdSessAuthenticationTypeTC value. Every usage of the IANAbfdSessAuthenticationTypeTC textual convention is required to specify the IANAbfdSessAuthenticationKeyTC object that provides the context. It is suggested that the IANAbfdSessAuthenticationKeyTC object be logically registered before the object(s) that use the IANAbfdSessAuthenticationKeyTC textual convention, if they appear in the same logical row.
IANABFDSAUTHENTICAtionKeyTC始终在IANABFDSAUTHENTICAtionTypeTC值的上下文中解释。每次使用IANABFDSAUTHENTICAtionTypeTC文本约定都需要指定提供上下文的IANABFDSAUTHENTICAtionKeyTC对象。建议在使用IANABBFDSESSAUTHENTICAtionKeyTC文本约定的对象（如果它们出现在同一逻辑行中）之前，逻辑上注册IANABBFDSESSAUTHENTICAtionKeyTC对象。
The value of an IANAbfdSessAuthenticationKeyTC must always be consistent with the value of the associated IANAbfdSessAuthenticationTypeTC object. Attempts to set an IANAbfdSessAuthenticationKeyTC object to a value inconsistent with the associated IANAbfdSessAuthenticationTypeTC must fail with an inconsistentValue error.
IANABFDSASAUTHENTICAtionKeyTC的值必须始终与关联的IANABFDSAUTHENTICAtionTypeTC对象的值一致。尝试将IANABFDSasAuthenticationKeyTC对象设置为与关联的IANABFDSasAuthenticationTypeTC不一致的值必须失败，并出现值不一致错误。
The following size constraints for an IANAbfdSessAuthenticationKeyTC object are defined for the associated IANAbfdSessAuthenticationTypeTC values show below:
为关联的IANABBFDSESSAUTHENTICAtionTypeTC值定义了IANABBFDSESSAUTHENTICAtionKeyTC对象的以下大小约束，如下所示：
noAuthentication(-1): SIZE(0)
reserved(0): SIZE(0)
simplePassword(1): SIZE(1..16)
keyedMD5(2): SIZE(16)
meticulousKeyedMD5(3): SIZE(16)
keyedSHA1(4): SIZE(20)
meticulousKeyedSHA1(5): SIZE(20)
noAuthentication(-1): SIZE(0)
reserved(0): SIZE(0)
simplePassword(1): SIZE(1..16)
keyedMD5(2): SIZE(16)
meticulousKeyedMD5(3): SIZE(16)
keyedSHA1(4): SIZE(20)
meticulousKeyedSHA1(5): SIZE(20)
When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise, the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate." REFERENCE "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))
当此文本约定用作索引对象的语法时，SMIv2，STD 58中指定的128个子标识符的限制可能会出现问题。在这种情况下，对象定义必须包括一个“SIZE”子句，以限制潜在实例子标识符的数量；否则，适用的约束条件必须在适当的概念行描述条款中说明，如果没有合适的单一描述条款，则必须在周围的文档中说明。“参考”Katz，D.和D.Ward，双向转发检测（BFD），RFC 58802010年6月的“语法八位字符串”第4.2-4.4节（尺寸（0..252））
END
终止
This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other BFD MIB modules to define management objects.
此模块不定义任何管理对象。相反，它定义了一组文本约定，其他BFD MIB模块可以使用这些约定来定义管理对象。
Meaningful security considerations can only be written in the MIB modules that define management objects. This document has therefore no impact on the security of the Internet.
有意义的安全注意事项只能写入定义管理对象的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 Section 3 for the initial contents. See the most updated version of this MIB at <http://www.iana.org/assignments/ianabfdtcstd-mib>. Assignments of IANA-BFD-TC-STD-MIB are via IETF Review [RFC5226].
本文件提供了IANA-BFD-TC-STD-MIB模块的基本定义。该MIB模块由IANA直接控制。初始内容见第3节。有关此MIB的最新版本，请参阅<http://www.iana.org/assignments/ianabfdtcstd-mib>. IANA-BFD-TC-STD-MIB的分配通过IETF审查[RFC5226]进行。
This MIB makes reference to the following documents: [RFC2578], [RFC2579], [RFC5880], [RFC5881] and [RFC5883], [RFC6428], and [RFC7130].
本MIB参考了以下文件：[RFC2578]、[RFC2579]、[RFC5880]、[RFC5881]和[RFC5883]、[RFC6428]和[RFC7130]。
IANA assigned an OID to the BFD-TC-STD-MIB module specified in this document as { mib-2 223 }.
IANA将OID分配给本文件中指定为{MIB-223}的BFD-TC-STD-MIB模块。
IANA assigned an OID to the IANA-BFD-TC-STD-MIB module specified in this document as { mib-2 224 }.
IANA将OID分配给本文档中指定为{MIB-2 224}的IANA-BFD-TC-STD-MIB模块。
The authors would like to thank Adrian Farrel and Jeffrey Haas for performing thorough reviews and providing a number of suggestions. The authors would also like to thank David Ward and Christer Holmberg for their comments and suggestions.
作者要感谢Adrian Farrel和Jeffrey Haas进行了全面的审查并提出了一些建议。作者还要感谢David Ward和Christer Holmberg的评论和建议。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD)", RFC 5880, June 2010.
[RFC5880]Katz，D.和D.Ward，“双向转发检测（BFD）”，RFC 58802010年6月。
[RFC5881] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June 2010.
[RFC5881]Katz，D.和D.Ward，“IPv4和IPv6（单跳）的双向转发检测（BFD）”，RFC 58812010年6月。
[RFC5883] Katz, D. and D. Ward, "Bidirectional Forwarding Detection (BFD) for Multihop Paths", RFC 5883, June 2010.
[RFC5883]Katz，D.和D.Ward，“多跳路径的双向转发检测（BFD）”，RFC 5883，2010年6月。
[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.
[RFC6428]Allan，D.，Swallow Ed.，G.，和J.Drake Ed.，“MPLS传输配置文件的主动连接验证、连续性检查和远程缺陷指示”，RFC 6428，2011年11月。
[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.
[RFC7130]Bhatia，M.，Chen，M.，Boutros，S.，Binderberger，M.，和J.Haas，“链路聚合组（LAG）接口上的双向转发检测（BFD）”，RFC 7130，2014年2月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，2008年5月。
Authors' Addresses
作者地址
Thomas D. Nadeau Brocade
托马斯·纳多·博科
EMail: tnadeau@lucidvision.com
EMail: tnadeau@lucidvision.com
Zafar Ali Cisco Systems
扎法尔·阿里思科系统公司
EMail: zali@cisco.com
EMail: zali@cisco.com
Nobo Akiya Cisco Systems
Nobo Akiya思科系统公司
EMail: nobo@cisco.com
EMail: nobo@cisco.com