Network Working Group T. Nadeau, Ed.
Request for Comment: 4801 Cisco Systems, Inc.
Category: Standards Track A. Farrel, Ed.
Old Dog Consulting
February 2007
Network Working Group T. Nadeau, Ed.
Request for Comment: 4801 Cisco Systems, Inc.
Category: Standards Track A. Farrel, Ed.
Old Dog Consulting
February 2007
Definitions of Textual Conventions for Generalized Multiprotocol Label Switching (GMPLS) Management
通用多协议标签交换（GMPLS）管理的文本约定定义
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document defines a Management Information Base (MIB) module that contains textual conventions (TCs) to represent commonly used Generalized Multiprotocol Label Switching (GMPLS) management information. The intent is that these textual conventions will be imported and used in GMPLS-related MIB modules that would otherwise define their own representations.
本文档定义了一个管理信息库（MIB）模块，该模块包含文本约定（TC），以表示常用的通用多协议标签交换（GMPLS）管理信息。其目的是将这些文本约定导入并在GMPLS相关MIB模块中使用，否则这些模块将定义它们自己的表示。
Table of Contents
目录
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. GMPLS Textual Conventions MIB Definitions .......................3
4. Security Considerations .........................................5
5. IANA Considerations .............................................6
6. References ......................................................6
6.1. Normative References .......................................6
6.2. Informative References .....................................7
7. Acknowledgements ................................................7
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. GMPLS Textual Conventions MIB Definitions .......................3
4. Security Considerations .........................................5
5. IANA Considerations .............................................6
6. References ......................................................6
6.1. Normative References .......................................6
6.2. Informative References .....................................7
7. Acknowledgements ................................................7
This document defines a MIB module that contains textual conventions (TCs) for Generalized Multiprotocol Label Switching (GMPLS) networks. These textual conventions should be imported by MIB modules that manage GMPLS networks.
本文档定义了一个MIB模块，该模块包含通用多协议标签交换（GMPLS）网络的文本约定（TC）。这些文本约定应由管理GMPLS网络的MIB模块导入。
This MIB module supplements the MIB module in [RFC3811] that defines textual conventions for Multiprotocol Label Switching (MPLS) management. [RFC3811] may continue to be used without this MIB module in networks that support only MPLS.
此MIB模块补充了[RFC3811]中定义多协议标签交换（MPLS）管理文本约定的MIB模块。[RFC3811]可以在不使用此MIB模块的情况下继续在仅支持MPLS的网络中使用。
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 an introduction to the concepts of GMPLS, see [RFC3945].
有关GMPLS概念的介绍，请参见[RFC3945]。
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 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].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
This MIB module makes reference to the following documents: [RFC2578], [RFC2579], [RFC3471], and [RFC3811].
此MIB模块参考以下文档：[RFC2578]、[RFC2579]、[RFC3471]和[RFC3811]。
GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY FROM SNMPv2-SMI -- RFC 2578 TEXTUAL-CONVENTION FROM SNMPv2-TC -- RFC 2579 mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 ;
从SNMPv2 SMI导入模块标识——从SNMPv2 TC导入RFC 2578文本约定——从MPLS-TC-STD-MIB导入RFC 2579 MPLSTDMIB——从RFC 3811导入；
gmplsTCStdMIB MODULE-IDENTITY LAST-UPDATED "200702280000Z" -- 28 February 2007 00:00:00 GMT ORGANIZATION "IETF Common Control and Measurement Plane (CCAMP) Working Group" CONTACT-INFO " Thomas D. Nadeau Cisco Systems, Inc. Email: tnadeau@cisco.com
gmplsTCStdMIB模块标识最后更新“200702280000Z”-2007年2月28日00:00:00 GMT组织“IETF通用控制和测量平面（CCAMP）工作组”联系方式“Thomas D.Nadeau Cisco Systems，Inc.电子邮件：tnadeau@cisco.com
Adrian Farrel Old Dog Consulting Email: adrian@olddog.co.uk
Adrian Farrel老狗咨询电子邮件：adrian@olddog.co.uk
Comments about this document should be emailed directly to the CCAMP working group mailing list at ccamp@ops.ietf.org" DESCRIPTION "Copyright (C) The IETF Trust (2007). This version of this MIB module is part of RFC 4801; see the RFC itself for full legal notices.
有关本文件的意见应通过电子邮件直接发送至CCAMP工作组邮件列表，地址为ccamp@ops.ietf.org“说明”版权所有（C）IETF信托基金（2007年）。此版本的MIB模块是RFC 4801的一部分；有关完整的法律通知，请参见RFC本身。
This MIB module defines TEXTUAL-CONVENTIONs for concepts used in
Generalized Multiprotocol Label Switching (GMPLS) networks."
REVISION
"200702280000Z" -- 28 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version published as part of RFC 4801."
::= { mplsStdMIB 12 }
This MIB module defines TEXTUAL-CONVENTIONs for concepts used in
Generalized Multiprotocol Label Switching (GMPLS) networks."
REVISION
"200702280000Z" -- 28 February 2007 00:00:00 GMT
DESCRIPTION
"Initial version published as part of RFC 4801."
::= { mplsStdMIB 12 }
GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
GmplsFreeformLabelTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This TEXTUAL-CONVENTION can be used as the syntax of an object that contains any GMPLS Label. Objects with this syntax can be used to represent labels that have label types that are not defined in any RFCs. The freeform GMPLS Label may also be used by systems that do not wish to represent labels that have label types defined in RFCs using type-specific syntaxes." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 3.2." SYNTAX OCTET STRING (SIZE (0..64))
“此文本约定可用作包含任何GMPLS标签的对象的语法。具有此语法的对象可用于表示具有任何RFC中未定义的标签类型的标签。自由格式GMPLS标签也可用于不希望表示具有使用类型sp在RFC中定义的标签类型的系统具体语法。“参考”1.通用多协议标签交换（GMPLS）信令功能描述，RFC 3471，第3.2节。“语法八位字符串（大小（0..64））
GmplsLabelTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Determines the interpretation that should be applied to an
object that encodes a label. The possible types are:
GmplsLabelTypeTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Determines the interpretation that should be applied to an
object that encodes a label. The possible types are:
gmplsMplsLabel(1) - The label is an MPLS Packet, Cell, or Frame Label and is encoded as described for the TEXTUAL-CONVENTION MplsLabel defined in RFC 3811.
GMPLSMPLSLLabel（1）-标签是MPLS数据包、小区或帧标签，按照RFC 3811中定义的文本约定MplsLabel进行编码。
gmplsPortWavelengthLabel(2) - The label is a Port or Wavelength Label as defined in RFC 3471.
gmplsPortWavelengthLabel（2）-该标签是RFC 3471中定义的端口或波长标签。
gmplsFreeformLabel(3) - The label is any form of label encoded as an OCTET STRING using the TEXTUAL-CONVENTION GmplsFreeformLabel.
gmplsFreeformLabel（3）-标签是使用文本约定gmplsFreeformLabel编码为八位字符串的任何形式的标签。
gmplsSonetLabel(4) - The label is a Synchronous Optical Network (SONET) Label as defined in RFC 4606.
gmplsSonetLabel（4）-该标签是RFC 4606中定义的同步光网络（SONET）标签。
gmplsSdhLabel(5) - The label is a Synchronous Digital Hierarchy (SDH) Label as defined in RFC 4606.
gmplsSdhLabel（5）-该标签是RFC 4606中定义的同步数字体系（SDH）标签。
gmplsWavebandLabel(6) - The label is a Waveband Label as defined in RFC 3471." REFERENCE "1. Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description, RFC 3471, section 3. 2. Definition of Textual Conventions and for Multiprotocol Label Switching (MPLS) Management, RFC 3811, section 3. 3. Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous
gmplsWavebandLabel（6）-该标签是RFC 3471中定义的波段标签。“参考”1。通用多协议标签交换（GMPLS）信令功能描述，RFC 3471，第3节。2.多协议标签交换（MPLS）管理的文本约定和定义，RFC 3811，第3节。3.同步光网络（SONET）和同步光网络的通用多协议标签交换（GMPLS）扩展
Digital Hierarchy (SDH) Control, RFC 4606."
SYNTAX INTEGER {
gmplsMplsLabel(1),
gmplsPortWavelengthLabel(2),
gmplsFreeformGeneralizedLabel(3),
gmplsSonetLabel(4),
gmplsSdhLabel(5),
gmplsWavebandLabel(6)
}
Digital Hierarchy (SDH) Control, RFC 4606."
SYNTAX INTEGER {
gmplsMplsLabel(1),
gmplsPortWavelengthLabel(2),
gmplsFreeformGeneralizedLabel(3),
gmplsSonetLabel(4),
gmplsSdhLabel(5),
gmplsWavebandLabel(6)
}
GmplsSegmentDirectionTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The direction of data flow on an Label Switched Path (LSP)
segment with respect to the head of the LSP.
GmplsSegmentDirectionTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The direction of data flow on an Label Switched Path (LSP)
segment with respect to the head of the LSP.
Where an LSP is signaled using a conventional signaling protocol, the 'head' of the LSP is the source of the signaling (also known as the ingress) and the 'tail' is the destination (also known as the egress). For unidirectional LSPs, this usually matches the direction of flow of data.
在使用常规信令协议向LSP发送信令的情况下，LSP的“头”是信令的源（也称为入口），而“尾”是目的地（也称为出口）。对于单向LSP，这通常与数据流的方向相匹配。
For manually configured unidirectional LSPs, the direction of
the LSP segment matches the direction of flow of data. For
manually configured bidirectional LSPs, an arbitrary decision
must be made about which LER is the 'head'."
SYNTAX INTEGER {
forward(1), -- data flows from head-end of LSP toward tail-end
reverse(2) -- data flows from tail-end of LSP toward head-end
}
For manually configured unidirectional LSPs, the direction of
the LSP segment matches the direction of flow of data. For
manually configured bidirectional LSPs, an arbitrary decision
must be made about which LER is the 'head'."
SYNTAX INTEGER {
forward(1), -- data flows from head-end of LSP toward tail-end
reverse(2) -- data flows from tail-end of LSP toward head-end
}
END
终止
This module does not define any management objects. Instead, it defines a set of textual conventions which may be used by other GMPLS MIB modules to define management objects.
此模块不定义任何管理对象。相反，它定义了一组文本约定，其他GMPLS MIB模块可以使用这些文本约定来定义管理对象。
Meaningful security considerations can only be written in the MIB modules that define management objects. Therefore, this document has no impact on the security of the Internet.
有意义的安全注意事项只能写入定义管理对象的MIB模块中。因此，本文件不影响互联网的安全。
IANA has rooted MIB objects in this MIB module under the mplsStdMIB subtree by assigning an OID to gmplsTCStdMIB.
IANA通过将OID分配给gmplsTCStdMIB，在MPLSTDMIB子树下的MIB模块中建立了MIB对象的根。
IANA has made the following assignments in the "NETWORK MANAGEMENT PARAMETERS" registry located at http://www.iana.org/assignments/smi-numbers in table:
IANA在位于的“网络管理参数”注册表中进行了以下分配：http://www.iana.org/assignments/smi-numbers 在表中：
...mib-2.transmission.mplsStdMIB (1.3.6.1.2.1.10.166)
…mib-2.transmission.mplsStdMIB（1.3.6.1.2.1.10.166）
Decimal Name References
------- ----- ----------
12 GMPLS-TC-STD-MIB [RFC4801]
Decimal Name References
------- ----- ----------
12 GMPLS-TC-STD-MIB [RFC4801]
In the future, GMPLS-related standards-track MIB modules should be rooted under the mplsStdMIB (sic) subtree. IANA has been requested to manage that namespace in the SMI Numbers registry [RFC3811]. New assignments can only be made via a Standards Action as specified in [RFC2434].
将来，GMPLS相关标准跟踪MIB模块应植根于MPLSTDMIB（sic）子树下。已请求IANA在SMI编号注册表[RFC3811]中管理该命名空间。新分配只能通过[RFC2434]中规定的标准行动进行。
[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月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“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月。
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, January 2003.
[RFC3471]Berger，L.“通用多协议标签交换（GMPLS）信令功能描述”，RFC 3471，2003年1月。
[RFC3811] Nadeau, T. and J. Cucchiara, "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, June 2004.
[RFC3811]Nadeau，T.和J.Cucchiara，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，2004年6月。
[RFC4606] Mannie, E. and D. Papadimitriou, "Generalized Multi-Protocol Label Switching (GMPLS) Extensions for Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) Control", RFC 4606, August 2006.
[RFC4606]Mannie，E.和D.Papadimitriou，“同步光网络（SONET）和同步数字体系（SDH）控制的通用多协议标签交换（GMPLS）扩展”，RFC 4606，2006年8月。
[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月。
[RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching (GMPLS) Architecture", RFC 3945, October 2004.
[RFC3945]Mannie，E.“通用多协议标签交换（GMPLS）体系结构”，RFC 39452004年10月。
This document is a product of the CCAMP Working Group.
本文件是CCAMP工作组的成果。
Special thanks to Joan Cucchiara for her help with compilation issues and her very thorough MIB Doctor review. Thanks also to Lars Eggert, David Harrington, Harrie Hazewinkel, Dan Romascanu, and Bert Wijnen for their review comments.
特别感谢Joan Cucchiara在编译问题上的帮助以及她对MIB医生的全面审查。还要感谢拉尔斯·艾格特、大卫·哈林顿、哈里·哈泽文克尔、丹·罗马斯坎努和伯特·维恩的评论。
Contact Information
联系方式
Thomas D. Nadeau Cisco Systems, Inc. 1414 Massachusetts Ave. Boxborough, MA 01719
Thomas D.Nadeau Cisco Systems，Inc.马萨诸塞州Boxborough大道1414号，邮编01719
EMail: tnadeau@cisco.com
EMail: tnadeau@cisco.com
Adrian Farrel Old Dog Consulting
阿德里安·法雷尔老狗咨询公司
Phone: +44 1978 860944
EMail: adrian@olddog.co.uk
Phone: +44 1978 860944
EMail: adrian@olddog.co.uk
Cheenu Srinivasan Bloomberg L.P. 731 Lexington Ave. New York, NY 10022
Cheenu Srinivasan Bloomberg L.P.纽约州纽约市列克星敦大道731号，邮编10022
Phone: +1-212-617-3682
EMail: cheenu@bloomberg.net
Phone: +1-212-617-3682
EMail: cheenu@bloomberg.net
Tim Hall Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK
蒂姆·霍尔数据连接有限公司，英国米德尔塞克斯郡恩菲尔德教堂街100号，EN2 6BQ
Phone: +44 20 8366 1177
EMail: tim.hall@dataconnection.com
Phone: +44 20 8366 1177
EMail: tim.hall@dataconnection.com
Ed Harrison Data Connection Ltd. 100 Church Street Enfield, Middlesex EN2 6BQ, UK
英国米德尔塞克斯郡恩菲尔德教堂街100号Ed Harrison数据连接有限公司EN2 6BQ
Phone: +44 20 8366 1177
EMail: ed.harrison@dataconnection.com
Phone: +44 20 8366 1177
EMail: ed.harrison@dataconnection.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。