Network Working Group D. McWalter, Ed.
Request for Comments: 5131 Data Connection Ltd
Category: Standards Track December 2007
Network Working Group D. McWalter, Ed.
Request for Comments: 5131 Data Connection Ltd
Category: Standards Track December 2007
A MIB Textual Convention for Language Tags
语言标记的MIB文本约定
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）。本备忘录的分发不受限制。
Abstract
摘要
This MIB module defines a textual convention to represent BCP 47 language tags. The intent is that this textual convention will be imported and used in MIB modules that would otherwise define their own representation.
此MIB模块定义一个文本约定来表示BCP 47语言标记。其目的是导入此文本约定并在MIB模块中使用，否则这些模块将定义它们自己的表示。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. The Internet-Standard Management Framework . . . . . . . . . . 2
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
8.1. Normative References . . . . . . . . . . . . . . . . . . . 4
8.2. Informative References . . . . . . . . . . . . . . . . . . 5
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. The Internet-Standard Management Framework . . . . . . . . . . 2
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 4
8.1. Normative References . . . . . . . . . . . . . . . . . . . 4
8.2. Informative References . . . . . . . . . . . . . . . . . . 5
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. It defines a textual convention to represent BCP 47 [RFC4646] language tags.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。它定义了一个文本约定来表示BCP 47[RFC4646]语言标记。
The LangTag TEXTUAL-CONVENTION defined by this RFC replaces the similar LanguageTag TEXTUAL-CONVENTION defined by RFC 2932 [RFC2932].
此RFC定义的LangTag文本约定取代了RFC 2932[RFC2932]定义的类似LangTag文本约定。
The old LanguageTag TEXTUAL-CONVENTION is used by some existing MIB modules. New MIB modules should use the LangTag TEXTUAL-CONVENTION, which has been created (and is to be preferred) for the following reasons:
一些现有的MIB模块使用旧的LanguageTag文本约定。新的MIB模块应使用LangTag文本约定，该约定已创建（并且是首选），原因如下：
o Its syntax description is current, and is more comprehensive.
o 它的语法描述是最新的，并且更全面。
o It is short enough to use as an index object without subtyping, yet is of adequate length to represent any language tag in practice.
o 它足够短，可以用作索引对象而无需子类型，但在实践中，它的长度足以表示任何语言标记。
o It is provided in a dedicated MIB module to simplify module dependencies.
o 它在专用MIB模块中提供，以简化模块依赖关系。
It is not possible to apply changes in syntax and length to an existing textual convention. This is why the creation of a new textual convention with a new name was necessary.
不可能将语法和长度的更改应用于现有的文本约定。这就是为什么需要用新名称创建新的文本约定的原因。
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 RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照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 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]所述。
LANGTAG-TC-MIB DEFINITIONS ::= BEGIN
LANGTAG-TC-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI -- [RFC2578] TEXTUAL-CONVENTION FROM SNMPv2-TC; -- [RFC2579]
从SNMPv2 SMI导入模块标识mib-2--[RFC2578]从SNMPv2 TC导入文本约定；--[RFC2579]
langTagTcMIB MODULE-IDENTITY LAST-UPDATED "200711090000Z" -- 9 November 2007 ORGANIZATION "IETF Operations and Management (OPS) Area" CONTACT-INFO "EMail: ops-area@ietf.org Home page: http://www.ops.ietf.org/" DESCRIPTION "This MIB module defines a textual convention for representing BCP 47 language tags." REVISION "200711090000Z" -- 9 November 2007 DESCRIPTION "Initial revision, published as RFC 5131.
langTagTcMIB模块标识最后更新的“200711090000Z”-2007年11月9日组织“IETF运行和管理（OPS）区域”联系信息电子邮件：OPS-area@ietf.org主页：http://www.ops.ietf.org/“说明”此MIB模块定义了表示BCP 47语言标记的文本约定。“修订版”200711090000Z--2007年11月9日描述“初始修订版，作为RFC 5131出版。
Copyright (C) The IETF Trust (2007). This version of this
MIB module is part of RFC 5131; see the RFC itself for full
legal notices."
::= { mib-2 165 }
Copyright (C) The IETF Trust (2007). This version of this
MIB module is part of RFC 5131; see the RFC itself for full
legal notices."
::= { mib-2 165 }
LangTag ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1a"
STATUS current
DESCRIPTION
"A language tag, constructed in accordance with BCP 47.
LangTag ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1a"
STATUS current
DESCRIPTION
"A language tag, constructed in accordance with BCP 47.
Only lowercase characters are allowed. The purpose of this restriction is to provide unique language tags for use as indexes. BCP 47 recommends case conventions for user interfaces, but objects using this TEXTUAL-CONVENTION MUST use only lowercase.
只允许使用小写字符。此限制的目的是提供用作索引的唯一语言标记。BCP 47建议用户界面使用大小写约定，但使用这种文本约定的对象只能使用小写。
Values MUST be well-formed language tags, in conformance with the definition of well-formed tags in BCP 47. An implementation MAY further limit the values it accepts to those permitted by a 'validating' processor, as defined in BCP 47.
值必须是格式良好的语言标记，符合BCP 47中格式良好标记的定义。实现可以进一步将其接受的值限制为“验证”处理器允许的值，如BCP 47中所定义。
In theory, BCP 47 language tags are of unlimited length. The language tag described in this TEXTUAL-CONVENTION is of limited length. The analysis of language tag lengths in BCP 47 confirms that this limit will not pose a problem in practice. In particular, this length is greater than the
理论上，BCP 47语言标记的长度是无限的。本文本约定中描述的语言标记长度有限。BCP 47中对语言标记长度的分析证实，这一限制在实践中不会造成问题。特别是，此长度大于
minimum requirements set out in Section 4.3.1.
第4.3.1节中规定的最低要求。
A zero-length language tag is not a valid language tag. This can be used to express 'language tag absent' where required, for example, when used as an index field." REFERENCE "RFC 4646 BCP 47" SYNTAX OCTET STRING (SIZE (0 | 2..63))
长度为零的语言标记不是有效的语言标记。这可用于在需要时表示“语言标记缺失”，例如，当用作索引字段时。“参考”RFC 4646 BCP 47“语法八位字节字符串（大小（0 | 2..63））
END
终止
This MIB module does not define any management objects. Instead, it defines a textual convention that may be imported by other MIB modules and used for object definitions.
此MIB模块不定义任何管理对象。相反，它定义了一个文本约定，可以由其他MIB模块导入并用于对象定义。
Meaningful security considerations can only be written in the MIB modules that define management objects. This document therefore has no impact on the security of the Internet.
有意义的安全注意事项只能写入定义管理对象的MIB模块中。因此，本文件不影响互联网的安全。
LANGTAG-TC-MIB is rooted under the mib-2 subtree. IANA has assigned { mib-2 165 } to the LANGTAG-TC-MIB module specified in this document.
LANGTAG-TC-MIB根在MIB-2子树下。IANA已将{mib-2 165}分配给本文档中指定的LANGTAG-TC-mib模块。
This MIB module is a reworking of existing material from RFC 2932.
该MIB模块是对RFC 2932现有材料的返工。
This module was generated by editing together contributions from Randy Presuhn, Dan Romascanu, Bill Fenner, Juergen Schoenwaelder, Bert Wijnen, Doug Ewell, and Ira McDonald.
本模块是由兰迪·普雷森、丹·罗马斯坎努、比尔·芬纳、尤尔根·舍恩瓦埃尔德、伯特·维伊南、道格·埃威尔和艾拉·麦克唐纳共同编辑的。
[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月。
[RFC4646] Phillips, A. and M. Davis, "Tags for Identifying Languages", BCP 47, RFC 4646, September 2006.
[RFC4646]Phillips，A.和M.Davis，“识别语言的标记”，BCP 47，RFC 46462006年9月。
[RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 Multicast Routing MIB", RFC 2932, October 2000.
[RFC2932]McCloghrie，K.，Farinaci，D.，和D.Thaler，“IPv4多播路由MIB”，RFC 2932，2000年10月。
[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月。
Author's Address
作者地址
David McWalter (editor) Data Connection Ltd 100 Church Street Enfield EN2 6BQ United Kingdom
David McWalter（编辑）数据连接有限公司英国恩菲尔德教堂街100号EN2 6BQ
EMail: dmcw@dataconnection.com
EMail: dmcw@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.