Network Working Group S. Legg
Request for Comments: 4792 eB2Bcom
Updates: 3641 January 2007
Category: Standards Track
Network Working Group S. Legg
Request for Comments: 4792 eB2Bcom
Updates: 3641 January 2007
Category: Standards Track
Encoding Instructions for the Generic String Encoding Rules (GSER)
通用字符串编码规则（GSER）的编码说明
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
摘要
Abstract Syntax Notation One (ASN.1) defines a general framework for annotating types in an ASN.1 specification with encoding instructions that alter how values of those types are encoded according to ASN.1 encoding rules. This document defines the supporting notation for encoding instructions that apply to the Generic String Encoding Rules (GSER) and, in particular, defines an encoding instruction to provide a machine-processable representation for the declaration of a GSER ChoiceOfStrings type.
抽象语法表示法1（ASN.1）定义了一个通用框架，用于在ASN.1规范中对类型进行注释，该框架使用编码指令根据ASN.1编码规则改变这些类型的值的编码方式。本文档定义了适用于通用字符串编码规则（GSER）的编码指令的支持符号，特别是定义了一条编码指令，以提供GSER ChoiceofString类型声明的机器可处理表示。
Table of Contents
目录
1. Introduction ....................................................2
2. Conventions .....................................................2
3. Notation for GSER Encoding Instructions .........................2
4. The CHOICE-OF-STRINGS Encoding Instruction ......................3
4.1. Effect on GSER Encodings ...................................5
4.2. Replacement of Existing ChoiceOfStrings Declarations .......6
5. Security Considerations .........................................7
6. Normative References ............................................7
1. Introduction ....................................................2
2. Conventions .....................................................2
3. Notation for GSER Encoding Instructions .........................2
4. The CHOICE-OF-STRINGS Encoding Instruction ......................3
4.1. Effect on GSER Encodings ...................................5
4.2. Replacement of Existing ChoiceOfStrings Declarations .......6
5. Security Considerations .........................................7
6. Normative References ............................................7
Abstract Syntax Notation One (ASN.1) [X.680] defines a general framework for annotating types in an ASN.1 specification with encoding instructions [X.680-1] that alter how values of those types are encoded according to ASN.1 encoding rules. This document defines the supporting notation for encoding instructions that apply to the Generic String Encoding Rules (GSER) [GSER], and in particular defines an encoding instruction, the CHOICE-OF-STRINGS encoding instruction, to provide a machine-processable representation for the declaration of a GSER ChoiceOfStrings type.
抽象语法表示法1（ASN.1）[X.680]定义了一个通用框架，用于在ASN.1规范中使用编码指令[X.680-1]对类型进行注释，该指令根据ASN.1编码规则改变这些类型的值的编码方式。本文档定义了适用于通用字符串编码规则（GSER）[GSER]的编码指令的支持符号，特别是定义了编码指令，即字符串选择编码指令，以提供GSER ChoiceofString类型声明的机器可处理表示。
The CHOICE-OF-STRINGS encoding instruction SHOULD be used instead of simply declaring a ChoiceOfStrings type.
应该使用CHOICE-OF-STRINGS编码指令，而不是简单地声明ChoiceOfStrings类型。
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 [BCP14].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照BCP 14、RFC 2119[BCP14]中的说明进行解释。
Throughout this document, "type" shall be taken to mean an ASN.1 type, and "value" shall be taken to mean an ASN.1 abstract value, unless qualified otherwise.
在本文件中，“类型”应指ASN.1类型，“值”应指ASN.1抽象值，除非另有限定。
A reference to an ASN.1 production [X.680] (e.g., Type, NamedType) is a reference to text in an ASN.1 specification corresponding to that production.
对ASN.1产品[X.680]（例如，Type，NamedType）的引用是对与该产品对应的ASN.1规范中文本的引用。
The grammar of ASN.1 permits the application of encoding instructions [X.680-1], through type prefixes and encoding control sections, that modify how abstract values are encoded by nominated encoding rules.
ASN.1的语法允许应用编码指令[X.680-1]，通过类型前缀和编码控制部分修改指定编码规则对抽象值的编码方式。
The generic notation for type prefixes and encoding control sections is defined by the ASN.1 basic notation [X.680] [X.680-1], and includes an encoding reference to identify the specific encoding rules that are affected by the encoding instruction.
类型前缀和编码控制部分的通用表示法由ASN.1基本表示法[X.680][X.680-1]定义，并包括一个编码引用，用于标识受编码指令影响的特定编码规则。
The encoding reference that identifies the Generic String Encoding Rules is literally GSER.
标识通用字符串编码规则的编码引用实际上是GSER。
The specific notation for an encoding instruction for a particular set of encoding rules is left to the specification of those encoding rules. Consequently, this companion document to the GSER specification [GSER] defines the notation for GSER encoding
特定编码规则集的编码指令的特定符号留待这些编码规则的规范决定。因此，GSER规范[GSER]的本配套文件定义了GSER编码的符号
instructions. Specifically, it elaborates the EncodingInstruction and EncodingInstructionAssignmentList placeholder productions of the ASN.1 basic notation.
说明书具体来说，它阐述了ASN.1基本符号的EncodingInstruction和EncodingInstructionAssignmentList占位符产品。
In the context of the GSER encoding reference the EncodingInstruction production is defined as follows, using the conventions of the ASN.1 basic notation:
在GSER编码参考的上下文中，使用ASN.1基本符号的约定，编码指令生成定义如下：
EncodingInstruction ::=
ChoiceOfStringsInstruction
EncodingInstruction ::=
ChoiceOfStringsInstruction
In the context of the GSER encoding reference the EncodingInstructionAssignmentList production (which only appears in an encoding control section) is empty:
在GSER编码引用的上下文中，EncodingInstructionAssignmentList产品（仅出现在编码控制部分）为空：
EncodingInstructionAssignmentList ::= empty
EncodingInstructionAssignmentList ::= empty
The CHOICE-OF-STRINGS encoding instruction allows a GSER encoder to encode the alternative of a CHOICE (of restricted string types) without the leading identifier. The optional PrecedenceList also allows a specification writer to alter the order in which a GSER decoder will consider the alternatives of the CHOICE as it determines which alternative has been encoded when the identifier is absent.
CHOICE-OF-STRINGS编码指令允许GSER编码器在不使用前导标识符的情况下对选项（受限字符串类型）进行编码。可选的优先权也允许规范写入器改变GSER解码器将考虑选择的替代品的顺序，因为它确定当标识符不存在时已编码了哪个备选方案。
The notation for a CHOICE-OF-STRINGS encoding instruction is defined as follows:
字符串选择编码指令的符号定义如下：
UnionInstruction ::= "CHOICE-OF-STRINGS" AlternativesPrecedence ?
UnionInstruction ::= "CHOICE-OF-STRINGS" AlternativesPrecedence ?
AlternativesPrecedence ::= "PRECEDENCE" PrecedenceList
AlternativesPrecedence ::= "PRECEDENCE" PrecedenceList
PrecedenceList ::= identifier PrecedenceList ?
PrecedenceList ::= identifier PrecedenceList ?
The Type in the EncodingPrefixedType for a CHOICE-OF-STRINGS encoding instruction SHALL be:
字符串选择编码指令的EncodingPrefixedType中的类型应为：
(a) a BuiltinType that is a ChoiceType, or
(a) 选择类型的内置类型，或
(b) a ConstrainedType that is not a TypeWithConstraint where the Type in the ConstrainedType is one of (a) to (d), or
(b) 不是TypeWithConstraint的ConstrainedType，其中ConstrainedType中的类型为（a）到（d）之一，或
(c) a BuiltinType that is a PrefixedType that is a TaggedType where the Type in the TaggedType is one of (a) to (d), or
(c) 一种内置类型，其前缀类型为TaggedType，其中TaggedType中的类型为（a）到（d）之一，或
(d) a BuiltinType that is a PrefixedType that is an EncodingPrefixedType where the Type in the EncodingPrefixedType is one of (a) to (d).
(d) 一种内置类型，它是一种PrefixedType，它是一种EncodingPrefixedType，其中EncodingPrefixedType中的类型是（a）到（d）之一。
The effect of this condition is to force the CHOICE-OF-STRINGS encoding instruction to be textually co-located with the CHOICE type definition to which it applies. This makes it clear to a reader that the encoding instruction applies to every use of the CHOICE type no matter how it might be referenced.
此条件的效果是强制字符串选择编码指令在文本上与其应用的选择类型定义位于同一位置。这向读者清楚地表明，编码指令适用于选择类型的每一次使用，无论它可能被如何引用。
The ChoiceType in case (a) is said to be "subject to" the CHOICE-OF-STRINGS encoding instruction.
案例（a）中的ChoiceType被称为“服从”字符串选择编码指令。
The Type of each NamedType of the ChoiceType in case (a) MUST be:
案例（a）中所选类型的每个NamedType的类型必须为：
(1) the NumericString, PrintableString, TeletexString (T61String), VideotexString, IA5String, GraphicString, VisibleString (ISO646String), GeneralString, BMPString, UniversalString, or UTF8String type, or
(1) 数字字符串、可打印字符串、电传字符串（T61String）、可视文本字符串、IA5String、图形字符串、可视字符串（ISO646String）、通用字符串、BMPSString、通用字符串或UTF8String类型，或
(2) a type notation that references a type that is one of (1) to (4), or
(2) 引用（1）到（4）之一类型的类型表示法，或
(3) a constrained type where the type that is constrained is one of (1) to (4), or
(3) 一种受约束类型，其中受约束的类型是（1）到（4）中的一种，或
(4) a prefixed type where the type that is prefixed is one of (1) to (4).
(4) 一种带前缀的类型，其中带前缀的类型是（1）到（4）中的一种。
ASIDE: A tagged type is a special case of a prefixed type. An effect of case (4) is that tagging is not significant.
旁白：标记类型是前缀类型的特例。案例（4）的一个影响是标记不显著。
The ASN.1 restricted string type in case (1) MUST be different for each NamedType in the ChoiceType, i.e., no two alternatives have the same restricted string type.
对于ChoiceType中的每个NamedType，案例（1）中的ASN.1受限字符串类型必须不同，即，没有两个备选方案具有相同的受限字符串类型。
If case (3) applies to any NamedType, then the constraint in case (3) MUST be the same for each NamedType, i.e., either none of the alternatives has a constraint, or all of the alternatives have exactly the same constraint.
如果案例（3）适用于任何NamedType，那么案例（3）中的约束对于每个NamedType都必须相同，即，要么没有一个备选方案具有约束，要么所有备选方案都具有完全相同的约束。
Each identifier in the PrecedenceList MUST be the identifier of a NamedType of the ChoiceType.
PrecenceList中的每个标识符都必须是ChoiceType的NamedType的标识符。
A particular identifier SHALL NOT appear more than once in the same PrecedenceList.
特定标识符在同一优先列表中不得出现多次。
A value of a CHOICE type is encoded according to the <ChoiceValue> [GSER] Augmented Backus-Naur Form [ABNF] rule. The ABNF for <ChoiceValue> is reproduced here for convenience:
选择类型的值根据<ChoiceValue>[GSER]增广的巴科斯-诺尔形式[ABNF]规则进行编码。为方便起见，此处复制了<ChoiceValue>的ABNF：
ChoiceValue = IdentifiedChoiceValue / ChoiceOfStringsValue
ChoiceValue=IdentifiedChoiceValue/ChoiceOfString值
IdentifiedChoiceValue = identifier ":" Value ChoiceOfStringsValue = StringValue
IdentifiedChoiceValue=identifier:“值ChoiceOfStringsValue=StringValue
The <IdentifiedChoiceValue> rule MUST be used to encode values of a CHOICE type where the ChoiceType is not subject to a CHOICE-OF-STRINGS encoding instruction.
必须使用<IdentifiedChoiceValue>规则对ChoiceType不受字符串选择编码指令约束的ChoiceType的值进行编码。
The chosen alternative of a value of a CHOICE type corresponds to some NamedType in the definition of the type. The <identifier> in the <IdentifiedChoiceValue> is the identifier of this NamedType.
选择的选项类型的值对应于类型定义中的某个NamedType。<IdentifiedChoiceValue>中的<identifier>是此NamedType的标识符。
Either the <IdentifiedChoiceValue> rule or the <ChoiceOfStringsValue> rule is used to encode values of a CHOICE type where the ChoiceType is subject to a CHOICE-OF-STRINGS encoding instruction.
<IdentifiedChoiceValue>规则或<ChoiceOffstringValue>规则用于对CHOICE类型的值进行编码，其中ChoiceType受CHOICE-of-String编码指令的约束。
If <ChoiceOfStringsValue> has been used, then a GSER decoder MUST determine the chosen alternative by considering the alternatives of the CHOICE in the order prescribed below and accepting the first alternative that allows all of the characters in the <StringValue>.
如果使用了<ChoiceOfStringsValue>，则GSER解码器必须按照以下规定的顺序考虑选择的备选方案，并接受允许<StringValue>中所有字符的第一个备选方案，从而确定选择的备选方案。
If the CHOICE-OF-STRINGS encoding instruction has a PrecedenceList, then the alternatives of the ChoiceType referenced by the PrecedenceList are considered in the order identified by that PrecedenceList, and then the remaining alternatives are considered in the order of their definition in the ChoiceType. If the CHOICE-OF-STRINGS encoding instruction does not have a PrecedenceList, then all the alternatives of the ChoiceType are considered in the order of their definition in the ChoiceType.
如果CHOICE-OF-STRINGS编码指令具有PrecenceList，则PrecenceList引用的ChoiceType的备选方案将按照该PrecenceList标识的顺序考虑，其余备选方案将按照其在ChoiceType中的定义顺序考虑。如果CHOICE-OF-STRINGS编码指令没有PreferenceList，则ChoiceType的所有替代项都将按照其在ChoiceType中的定义顺序考虑。
A GSER encoder MUST use <IdentifiedChoiceValue> if a GSER decoder would determine the chosen alternative to be something other than the chosen alternative of the CHOICE value being encoded; otherwise, <ChoiceOfStringsValue> MAY be used.
GSER编码器必须使用<IdentifiedChoiceValue>，如果GSER解码器将确定所选备选方案不是所编码的选择值的所选备选方案；否则，可以使用<ChoiceOfStringsValue>。
Example
实例
Consider this type definition:
考虑这种类型定义：
[GSER:CHOICE-OF-STRINGS PRECEDENCE basicName] CHOICE {
extendedName UTF8String,
basicName PrintableString
}
[GSER:CHOICE-OF-STRINGS PRECEDENCE basicName] CHOICE {
extendedName UTF8String,
basicName PrintableString
}
If a <ChoiceOfStringsValue> has been used, then a GSER decoder would first consider whether the <StringValue> was a valid basicName (a PrintableString) before considering whether it was a valid extendedName (a UTF8String).
如果使用了<CaseOfStutssValue>，那么在考虑是否是有效扩展名（UTF8Stand）之前，GSER解码器将首先考虑< StrugValue>是否是一个有效的基本名称（PrimTable Stand）。
In line with the previous declaration [GSER] of the DirectoryString type as a ChoiceOfStrings type, applications using GSER MUST add this encoding instruction:
根据之前将DirectoryString类型声明为ChoiceOfStrings类型的[GSER]，使用GSER的应用程序必须添加以下编码指令：
[GSER:CHOICE-OF-STRINGS PRECEDENCE printableString uTF8String]
[GSER:CHOICE-OF-STRINGS优先级可打印字符串uTF8String]
immediately before the "CHOICE" keyword in the definition of the DirectoryString type in the third and every subsequent edition of the SelectedAttributeTypes ASN.1 module of X.520 [X.520-3] [X.520-4] [X.520-5].
在X.520[X.520-3][X.520-4][X.520-5]的SelectedAttributeType ASN.1模块的第三版和后续各版中DirectoryString类型定义中的“CHOICE”关键字之前。
For example, this is how the DirectoryString definition would appear in the third, fourth and fifth editions:
例如，这就是DirectoryString定义在第三、第四和第五版中的显示方式：
DirectoryString{INTEGER:maxSize} ::=
[GSER:CHOICE-OF-STRINGS PRECEDENCE printableString uTF8String]
CHOICE {
teletexString TeletexString(SIZE (1..maxSize)),
printableString PrintableString(SIZE (1..maxSize)),
universalString UniversalString(SIZE (1..maxSize)),
bmpString BMPString(SIZE (1..maxSize)),
uTF8String UTF8String(SIZE (1..maxSize))
}
DirectoryString{INTEGER:maxSize} ::=
[GSER:CHOICE-OF-STRINGS PRECEDENCE printableString uTF8String]
CHOICE {
teletexString TeletexString(SIZE (1..maxSize)),
printableString PrintableString(SIZE (1..maxSize)),
universalString UniversalString(SIZE (1..maxSize)),
bmpString BMPString(SIZE (1..maxSize)),
uTF8String UTF8String(SIZE (1..maxSize))
}
The uTF8String alternative did not appear in the second edition of the SelectedAttributeTypes ASN.1 module of X.520 [X.520-2]. For compatibility, applications using GSER with the second edition of X.520 MUST add this encoding instruction:
uTF8String替代品未出现在X.520[X.520-2]的SelectedAttributeType ASN.1模块的第二版中。为了兼容性，使用GSER和第二版X.520的应用程序必须添加以下编码指令：
[GSER:CHOICE-OF-STRINGS PRECEDENCE printableString]
[GSER:CHOICE-OF-String优先打印字符串]
immediately before the "CHOICE" keyword in the definition of the DirectoryString type.
在DirectoryString类型定义中紧靠“CHOICE”关键字之前。
For example, this is how the DirectoryString definition would appear in the second edition:
例如，这是DirectoryString定义在第二版中的显示方式：
DirectoryString{INTEGER:maxSize} ::=
[GSER:CHOICE-OF-STRINGS PRECEDENCE printableString]
CHOICE {
teletexString TeletexString(SIZE (1..maxSize)),
printableString PrintableString(SIZE (1..maxSize)),
universalString UniversalString(SIZE (1..maxSize))
}
DirectoryString{INTEGER:maxSize} ::=
[GSER:CHOICE-OF-STRINGS PRECEDENCE printableString]
CHOICE {
teletexString TeletexString(SIZE (1..maxSize)),
printableString PrintableString(SIZE (1..maxSize)),
universalString UniversalString(SIZE (1..maxSize))
}
This specification changes the manner in which ChoiceOfStrings types are declared but does not alter the existing behaviour of GSER implementations. The security considerations for GSER are unchanged (see [GSER]).
该规范改变了ChoiceOffString类型的声明方式，但不改变GSER实现的现有行为。GSER的安全注意事项保持不变（参见[GSER]）。
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[BCP14]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[GSER] Legg, S., "Generic String Encoding Rules (GSER) for ASN.1 Types", RFC 3641, October 2003.
[GSER]Legg，S.，“ASN.1类型的通用字符串编码规则（GSER）”，RFC 36412003年10月。
[ABNF] Crocker, D., Ed., and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005.
[ABNF]Crocker，D.，Ed.，和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 42342005年10月。
[X.520-2] ITU-T Recommendation X.520 (1993) | ISO/IEC 9594-6:1994,
Information Technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-2] ITU-T Recommendation X.520 (1993) | ISO/IEC 9594-6:1994,
Information Technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-3] ITU-T Recommendation X.520 (08/97) | ISO/IEC 9594-6:1998,
Information Technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-3] ITU-T Recommendation X.520 (08/97) | ISO/IEC 9594-6:1998,
Information Technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-4] ITU-T Recommendation X.520 (02/01) | ISO/IEC 9594-6:2001,
Information technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-4] ITU-T Recommendation X.520 (02/01) | ISO/IEC 9594-6:2001,
Information technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-5] ITU-T Recommendation X.520 (08/05) | ISO/IEC 9594-6:2005,
Information technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.520-5] ITU-T Recommendation X.520 (08/05) | ISO/IEC 9594-6:2005,
Information technology - Open Systems Interconnection -
The Directory: Selected attribute types
[X.680] ITU-T Recommendation X.680 (07/02) | ISO/IEC 8824-1, Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation.
[X.680]ITU-T建议X.680（07/02）| ISO/IEC 8824-1，信息技术-抽象语法符号一（ASN.1）：基本符号规范。
[X.680-1] ITU-T Recommendation X.680 (2002) Amendment 1 (10/03) | ISO/IEC 8824-1:2002/Amd 1:2004, Support for EXTENDED-XER.
[X.680-1]ITU-T建议X.680（2002）修改件1（10/03）| ISO/IEC 8824-1:2002/Amd 1:2004，对扩展XER的支持。
Author's Address
作者地址
Dr. Steven Legg eB2Bcom Suite 3, Woodhouse Corporate Centre 935 Station Street Box Hill North, Victoria 3129 AUSTRALIA
Steven Legg博士eB2Bcom澳大利亚维多利亚州博克斯山北站街935号伍德豪斯企业中心3号套房，邮编：3129
Phone: +61 3 9896 7830
Fax: +61 3 9896 7801
EMail: steven.legg@eb2bcom.com
Phone: +61 3 9896 7830
Fax: +61 3 9896 7801
EMail: steven.legg@eb2bcom.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编辑功能的资金目前由互联网协会提供。