Network Working Group M. Mealling
Request for Comments: 5134 Refactored Networks, LLC
Category: Informational January 2008
Network Working Group M. Mealling
Request for Comments: 5134 Refactored Networks, LLC
Category: Informational January 2008
A Uniform Resource Name Namespace for the EPCglobal Electronic Product Code (EPC) and Related Standards
EPCglobal电子产品代码（EPC）和相关标准的统一资源名称命名空间
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Abstract
摘要
This document describes URN namespaces that will identify various objects within the EPCglobal system for identifying products within ecommerce and supply chain management applications.
本文档描述了URN名称空间，该名称空间将标识EPCglobal系统中的各种对象，用于标识电子商务和供应链管理应用程序中的产品。
The EPCglobal Architecture Framework [6] is a set of specifications for reading, managing, and acting on object codes and other sensor data as physical objects pass through a supply chain. Events and metadata about physical objects are exchanged via EPCglobal Electronic Product Code Information Services (EPCIS) that are essentially web services that implement agreed upon schema and interfaces.
EPCglobal体系结构框架[6]是一套规范，用于在物理对象通过供应链时读取、管理和处理对象代码和其他传感器数据。有关物理对象的事件和元数据通过EPCglobal电子产品代码信息服务（EPCI）进行交换，EPCI本质上是实现约定模式和接口的web服务。
Each object that is tracked by the EPCglobal Architecture Framework is identified by one or more managed identifiers. In many cases, these identification systems existed prior to the Internet becoming widely used. One such namespace is the Global Trade Item Number, or GTIN [7]. GTINs are widely used in global commerce and are managed by GS1. In order for the EPCglobal Architecture Framework to leverage the Internet to the fullest extent possible, the GTIN namespace (and others, such as Global Location Numbers (GLNs), Serialized Shipping Container Code (SSCC), etc. [7]) need to be directly compatible with the URI family of identifiers.
EPCglobal体系结构框架跟踪的每个对象都由一个或多个托管标识符标识。在许多情况下，这些识别系统存在于互联网广泛使用之前。一个这样的名称空间是全球贸易商品编号，或GTIN[7]。GTIN广泛应用于全球商业，由GS1管理。为了使EPCglobal体系结构框架尽可能充分利用互联网，GTIN名称空间（以及其他名称空间，如全局位置号（GLN）、序列化装运集装箱代码（SSCC）等[7]）需要与URI标识符系列直接兼容。
The use of GTINs, GLNs, and SSCCs are all managed by GS1. Their use within the EPCglobal Architecture Framework is managed by the GS1 subsidiary known as EPCglobal, Inc. For these, and possibly future
GTIN、GLN和SSCC的使用均由GS1管理。它们在EPCglobal体系结构框架内的使用由GS1子公司EPCglobal，Inc.管理，以实现这些目标，并可能在未来实现
identification systems, a single Uniform Resource Name (URN) Namespace ID (NID) is being requested: 'epc'. Each of the identifier namespaces mentioned will have a separate sub-space beneath the top level 'epc' NID.
在标识系统中，正在请求单个统一资源名（URN）命名空间ID（NID）：“epc”。提到的每个标识符名称空间在顶级“epc”NID下都有一个单独的子空间。
In addition to physical object identifiers, the EPCglobal Architecture Framework requires new namespaces for naming system components. In many cases, an interface within the EPCglobal Architecture Framework is XML [11] based and as such will require naming schemes for its XML schema [9] and various namespaces [10]. For these uses, another Uniform Resource Name (URN) Namespace ID (NID) is being requested: 'epcglobal'. Each specification or system component within the EPCglobal Architecture Framework will have a separate sub-space beneath the top level 'epcglobal' NID.
除了物理对象标识符之外，EPCglobal体系结构框架还需要新的名称空间来命名系统组件。在许多情况下，EPCglobal体系结构框架内的接口是基于XML[11]的，因此需要为其XML模式[9]和各种名称空间[10]提供命名方案。对于这些使用，将请求另一个统一资源名称（URN）命名空间ID（NID）：“epcglobal”。EPCglobal架构（Architecture）框架内的每个规范或系统组件将在顶级“EPCglobal”NID下有一个单独的子空间。
Since the EPCglobal Architecture Framework is engineered for widespread and general use, this namespace specification is a formal one, and the namespace IDs that are being requested are 'epc' and 'epcglobal'. It is important to note that it is the explicit intent that various sub-namespaces of the 'epc' NID actually name real, physical objects and/or corporeal entities. In contrast, sub-namespaces of the 'epcglobal' NID name logical or software constructs, such as schema namespaces.
由于EPCglobal体系结构框架是为广泛和通用而设计的，因此此命名空间规范是一个正式规范，请求的命名空间ID是“epc”和“EPCglobal”。需要注意的是，“epc”NID的各个子名称空间实际命名真实、物理对象和/或实体是明确的意图。相反，“epcglobal”NID的子名称空间命名为逻辑或软件构造，例如模式名称空间。
Namespace ID:
命名空间ID:
"epc"
“epc”
Registration Information:
注册资料：
Registration Version Number: 1 Registration Date: 2008-01-16
注册版本号：1注册日期：2008-01-16
Declared registrant of the namespace:
已声明命名空间的注册人：
EPCglobal, Inc. is a subsidiary of GS1 Princeton Pike Corporate Center 1009 Lenox Drive, Suite 202 Lawrenceville, NJ 08648, USA bhogan@epcglobalinc.org Tel: +1-609-620-4585
EPCglobal，Inc.是GS1普林斯顿派克公司中心的子公司，地址：美国新泽西州劳伦斯维尔202室莱诺克斯大道1009号，邮编：08648bhogan@epcglobalinc.org电话：+1-609-620-4585
Declaration of structure:
结构声明：
The normative specification of the structure of the 'epc' namespace is "EPC Tag Data Standards" [5]. The examples given below are not normative.
“epc”名称空间结构的规范性规范为“epc标签数据标准”[5]。下面给出的示例不具有规范性。
The 'epc' namespace is a set of sub-namespaces that can be extended in the future. The following ABNF [2] defines how the sub-namespaces are identified and any restrictions on their syntax (definitions not specified below can be found in RFC 2141 [1]):
“epc”命名空间是一组子命名空间，将来可以扩展。以下ABNF[2]定义了子名称空间的标识方式以及对其语法的任何限制（以下未指定的定义可在RFC 2141[1]中找到）：
EPC-URN = "urn:epc:" sub-ns-name ":" sub-ns
sub-ns-name = let-num [ 1*let-num-hyp ]
sub-ns = 1*<URN chars>
let-num = upper / lower / number
let-num-hyp = upper / lower / number / "-"
upper = %x41-5A ; "A" - "Z"
lower = %x61-7A ; "a" - "z"
number = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" /
"8" / "9"
EPC-URN = "urn:epc:" sub-ns-name ":" sub-ns
sub-ns-name = let-num [ 1*let-num-hyp ]
sub-ns = 1*<URN chars>
let-num = upper / lower / number
let-num-hyp = upper / lower / number / "-"
upper = %x41-5A ; "A" - "Z"
lower = %x61-7A ; "a" - "z"
number = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" /
"8" / "9"
For example, the sub-namespace 'sgtin' has the following definition (this ABNF is non-normative):
例如，子命名空间“sgtin”具有以下定义（此ABNF是非规范性的）：
SGTIN-URI = "urn:epc:id:sgtin:" SGTINURIBody
SGTINURIBody = 2*(PaddedNumericComponent ".") NumericComponent
NumericComponent = ZeroComponent / NonZeroComponent
ZeroComponent = "0"
NonZeroComponent = NonZeroDigit *Digit
PaddedNumericComponent = *Digit
Digit = "0" / NonZeroDigit
NonZeroDigit = "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9"
SGTIN-URI = "urn:epc:id:sgtin:" SGTINURIBody
SGTINURIBody = 2*(PaddedNumericComponent ".") NumericComponent
NumericComponent = ZeroComponent / NonZeroComponent
ZeroComponent = "0"
NonZeroComponent = NonZeroDigit *Digit
PaddedNumericComponent = *Digit
Digit = "0" / NonZeroDigit
NonZeroDigit = "1" / "2" / "3" / "4" / "5" / "6" / "7" / "8" / "9"
This equates to a namespace that has three period separated series of digits:
这相当于具有三个周期分隔的数字序列的命名空间：
urn:epc:id:sgtin:900100.0003456.1234567
urn:epc:id:sgtin:900100.0003456.1234567
The first series is a company prefix, the second denotes a product reference assigned by that company, and the third is a serial number for a specific instance of their product. Note that leading zeros are significant.
第一个系列是公司前缀，第二个系列表示该公司分配的产品参考，第三个系列是其产品特定实例的序列号。请注意，前导零是重要的。
Relevant ancillary documentation:
相关辅助文件：
The standards that define the EPCglobal Architecture Framework and the processes for creating new sub-namespaces are managed by EPCglobal, Inc. and can be found on its website. Several sub-namespaces are defined in the "EPC Tag Data Standards" [5].
定义EPCglobal体系结构框架的标准以及创建新子名称空间的过程由EPCglobal，Inc.管理，可在其网站上找到。“EPC标签数据标准”[5]中定义了若干子名称空间。
Identifier uniqueness considerations:
标识符唯一性注意事项：
The namespaces that make up the 'epc' namespace are all managed by an organization with almost 50 years of namespace management experience. In all cases (existing or new), the uniqueness of each namespace is an inherent part of the EPCglobal Architecture Framework.
构成“epc”名称空间的名称空间都由具有近50年名称空间管理经验的组织管理。在所有情况下（现有或新），每个名称空间的唯一性都是EPCglobal体系结构框架的固有部分。
Identifier persistence considerations:
标识符持久性注意事项：
The assignment process guarantees that names are not reassigned and that the binding between the name and its resource is permanent, regardless of any standards or organizational changes.
分配过程保证不会重新分配名称，并且名称与其资源之间的绑定是永久性的，而不考虑任何标准或组织更改。
Process of identifier assignment:
标识符分配过程：
Names are assigned by the EPCglobal standards publication process and by any entities that are sub-delegated by EPCglobal. It is important to note that in many cases the names assigned will explicitly denote physical objects and not an electronic representation of that object.
名称由EPCglobal标准发布流程和EPCglobal委托的任何实体指定。重要的是要注意，在许多情况下，指定的名称将明确表示物理对象，而不是该对象的电子表示。
Process of identifier resolution:
标识符解析过程：
Certain sub-namespaces are resolved via the Object Naming Service, defined in "Object Naming Service (ONS) Version 1.0" [4], which is a valid implementation of the Dynamic Delegation Discovery System that is defined in RFC 3401 [3].
某些子名称空间通过“对象命名服务（ONS）1.0版”[4]中定义的对象命名服务解析，该服务是RFC 3401[3]中定义的动态委派发现系统的有效实现。
Rules for Lexical Equivalence:
词汇对等规则：
The entire URN is case-sensitive.
整个URN区分大小写。
Conformance with URN Syntax:
符合URN语法：
There are no additional characters reserved except as noted in the ABNF above.
除上述ABNF中的说明外，没有保留其他字符。
Validation mechanism:
验证机制：
In the case of each sub-namespace, there will be namespace-specific rules for determining validity. In each case, the reader is referred to the appropriate EPCglobal-maintained documentation.
对于每个子名称空间，都有特定于名称空间的规则来确定有效性。在每种情况下，读者都会参考适当的EPCglobal维护文档。
Scope:
范围：
Global
全球的
Namespace ID:
命名空间ID:
"epcglobal"
“epcglobal”
Registration Information:
注册资料：
Registration Version Number: 1 Registration Date: 2007-03-06
注册版本号：1注册日期：2007-03-06
Declared registrant of the namespace:
已声明命名空间的注册人：
EPCglobal, Inc. is a subsidiary of GS1 Princeton Pike Corporate Center 1009 Lenox Drive, Suite 202 Lawrenceville, NJ 08648, USA bhogan@epcglobalinc.org Tel: +1-609-620-4585
EPCglobal，Inc.是GS1普林斯顿派克公司中心的子公司，地址：美国新泽西州劳伦斯维尔202室莱诺克斯大道1009号，邮编：08648bhogan@epcglobalinc.org电话：+1-609-620-4585
Declaration of structure:
结构声明：
The normative specifications for the structure of the 'epcglobal' namespace are various standards available at EPCglobal's public website. The examples given below are not normative.
“epcglobal”命名空间结构的规范性规范是在epcglobal的公共网站上提供的各种标准。下面给出的示例不具有规范性。
The 'epcglobal' namespace is a set of sub-namespaces that can be extended in the future. The following ABNF defines how the sub-namespaces are identified and any restrictions on their syntax (definitions not specified below can be found in RFC 2141 [1]):
“epcglobal”命名空间是一组将来可以扩展的子命名空间。以下ABNF定义了如何识别子名称空间以及对其语法的任何限制（以下未指定的定义可在RFC 2141[1]中找到）：
EPCGLOBAL-URN = "urn:epcglobal:" subnsname ":" subns
subnsname = let-num [ 1*let-num-hyp ]
subns = 1*<URN chars>
let-num = upper / lower / number
let-num-hyp = upper / lower / number / "-"
upper = %x41-5A ; "A" - "Z"
lower = %x61-7A ; "a" - "z"
number = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" /
"8" / "9"
EPCGLOBAL-URN = "urn:epcglobal:" subnsname ":" subns
subnsname = let-num [ 1*let-num-hyp ]
subns = 1*<URN chars>
let-num = upper / lower / number
let-num-hyp = upper / lower / number / "-"
upper = %x41-5A ; "A" - "Z"
lower = %x61-7A ; "a" - "z"
number = "0" / "1" / "2" / "3" / "4" / "5" / "6" / "7" /
"8" / "9"
For example, the identifier "urn:epcglobal:ale:xsd:1" is defined in the "Application Level Events 1.0 Specification" [8] for use as an XML namespace identifier for XML documents conforming to that specification.
例如，标识符“urn:epcglobal:ale:xsd:1”在“应用程序级别事件1.0规范”[8]中定义，用作符合该规范的XML文档的XML命名空间标识符。
Relevant ancillary documentation:
相关辅助文件：
The standards that define the EPCglobal Architecture Framework and the processes for creating new sub-namespaces are managed by EPCglobal, Inc. and can be found on its website.
定义EPCglobal体系结构框架的标准以及创建新子名称空间的过程由EPCglobal，Inc.管理，可在其网站上找到。
Identifier uniqueness considerations:
标识符唯一性注意事项：
The namespaces that make up the 'epcglobal' namespace are all managed by an organization with almost 50 years of namespace management experience. In all cases, the uniqueness of each namespace is an inherent part of the EPCglobal Architecture Framework.
构成“epcglobal”名称空间的名称空间都由具有近50年名称空间管理经验的组织管理。在所有情况下，每个名称空间的唯一性都是EPCglobal体系结构框架的固有部分。
Identifier persistence considerations:
标识符持久性注意事项：
The assignment process guarantees that names are not reassigned and that the binding between the name and its resource is permanent, regardless of any standards or organizational changes.
分配过程保证不会重新分配名称，并且名称与其资源之间的绑定是永久性的，而不考虑任何标准或组织更改。
Process of identifier assignment:
标识符分配过程：
Names are assigned by the EPCglobal, Inc. standards publication process.
名称由EPCglobal，Inc.标准发布流程指定。
Process of identifier resolution:
标识符解析过程：
No resolution mechanism is required or provided.
不需要或不提供解决机制。
Rules for Lexical Equivalence:
词汇对等规则：
The entire URN is case-sensitive.
整个URN区分大小写。
Conformance with URN Syntax:
符合URN语法：
There are no additional characters reserved except as noted in the ABNF above.
除上述ABNF中的说明外，没有保留其他字符。
Validation mechanism:
验证机制：
In the case of each sub-namespace, there will be namespace-specific rules for determining validity. In each case, the reader is referred to the appropriate EPCglobal-maintained documentation.
对于每个子名称空间，都有特定于名称空间的规则来确定有效性。在每种情况下，读者都会参考适当的EPCglobal维护文档。
Scope:
范围：
Global
全球的
This document includes two URN Namespace registrations that have been entered into the IANA registry for URN NIDs.
本文档包括两个URN名称空间注册，它们已输入到URN NID的IANA注册表中。
Due to EPCglobal, Inc. being a subsidiary of an internationally recognized authority for the identifiers embedded within the 'epc' namespace, as well as being the internationally recognized standards body for the standards that define identifiers in the 'epcglobal' namespace, these namespaces represent the best approach to naming products and entities within the world of supply chain management and ecommerce in general. There are no other alternative namespaces that have the level of authority and industry acceptance that the EPC does.
由于EPCglobal，Inc.是“epc”名称空间中嵌入标识符的国际公认权威机构的子公司，也是定义“EPCglobal”名称空间中标识符的国际公认标准机构，这些名称空间代表了在供应链管理和电子商务领域中命名产品和实体的最佳方法。没有其他替代名称空间具有EPC所具有的权限级别和行业认可度。
The EPCglobal Architecture Framework is intended to bring the Internet to the world of supply chain management and beyond. It can be used to tie physical objects to their virtual descriptions and as such has many wide ranging applications for the average Internet use. Thus, it is very much the intent that this namespace, and the entire EPCglobal Architecture Framework, considers the entire Internet as the scope of its community.
EPCglobal体系结构框架旨在将互联网带入供应链管理的世界以及其他领域。它可以用来将物理对象与其虚拟描述联系起来，因此在互联网上有着广泛的应用。因此，这个名称空间和整个EPCglobal体系结构框架将整个Internet视为其社区的范围，这是非常重要的。
The EPCglobal Architecture Framework is based almost exclusively on Internet and Web standards. Thus, the security impacts of each of its underlying technologies should be examined for weaknesses and threats. The primary threats will come from the fact that these names will identify physical things that can be of high value, thus the temptation to spoof metadata about that identifier (its cost, size, etc) will be much greater. Therefore, the role of digital signatures, secure resolution mechanisms, and trust relationships is very fundamental to the system.
EPCglobal架构框架几乎完全基于Internet和Web标准。因此，应检查其每项基础技术的安全影响，以确定弱点和威胁。主要威胁来自这样一个事实，即这些名称将标识可能具有高价值的物理对象，因此欺骗该标识符的元数据（其成本、大小等）的诱惑将更大。因此，数字签名、安全解析机制和信任关系的作用对于系统来说非常重要。
[1] Moats, R., "URN Syntax", RFC 2141, May 1997.
[1] 护城河，R.，“瓮语法”，RFC 21411997年5月。
[2] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 4234, October 2005.
[2] Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 42342005年10月。
[3] Mealling, M., "Dynamic Delegation Discovery System (DDDS) Part One: The Comprehensive DDDS", RFC 3401, October 2002.
[3] Mealling，M，“动态委托发现系统（DDDS）第一部分：综合DDDS”，RFC 3401，2002年10月。
[4] EPCglobal, Inc., "EPCglobal Network Object Name Service (ONS) 1.0", August 2003.
[4] EPCglobal公司，“EPCglobal网络对象名称服务（ONS）1.0”，2003年8月。
[5] EPCglobal, Inc., "EPC(tm) Tag Data Standards Version 1.3", February 2004.
[5] EPCglobal，Inc.“EPC（tm）标签数据标准1.3版”，2004年2月。
[6] Traub, K., Allgair, G., Barthe, H., Burstein, L., Garrett, J., Hogan, B., Rodrigues, B., Sarma, S., Schmidt, J., Schramek, C., Stewart, R., and K. Suen, "The EPCglobal Architecture Framework", July 2005.
[6] 特拉布，K.，奥尔盖尔，G.，巴特，H.，伯斯坦，L.，加勒特，J.，霍根，B.，罗德里格斯，B.，萨尔马，S.，施密特，J.，施拉梅克，C.，斯图尔特，R.，和K.孙，“EPCglobal架构框架”，2005年7月。
[7] GS1, "GS1 General Specifications v7.1", January 2007.
[7] GS1，“GS1通用规范v7.1”，2007年1月。
[8] EPCglobal, Inc., "The Application Level Events (ALE) Specification, Version 1.0", September 2005.
[8] EPCglobal，Inc.，“应用程序级事件（ALE）规范，版本1.0”，2005年9月。
[9] Thompson, H., Maloney, M., Beech, D., and N. Mendelsohn, "XML Schema Part 1: Structures Second Edition", World Wide Web Consortium Recommendation REC-xmlschema-1-20041028, October 2004, <http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[9] Thompson，H.，Maloney，M.，Beech，D.，和N.Mendelsohn，“XML模式第1部分：结构第二版”，万维网联盟建议REC-xmlschema-1-20041028，2004年10月<http://www.w3.org/TR/2004/REC-xmlschema-1-20041028>.
[10] Layman, A., Tobin, R., Bray, T., and D. Hollander, "Namespaces in XML 1.1", World Wide Web Consortium FirstEdition REC-xml-names11-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-names11-20040204>.
[10] Layman，A.，Tobin，R.，Bray，T.，和D.Hollander，“XML 1.1中的名称空间”，万维网联盟第一版REC-XML-names11-200402042004年2月<http://www.w3.org/TR/2004/REC-xml-names11-20040204>.
[11] Bray, T., Maler, E., Yergeau, F., Sperberg-McQueen, C., and J. Paoli, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-20040204>.
[11] Bray，T.，Maler，E.，Yergeau，F.，Sperberg McQueen，C.，和J.Paoli，“可扩展标记语言（XML）1.0（第三版）”，万维网联盟第一版REC-XML-200402042004年2月<http://www.w3.org/TR/2004/REC-xml-20040204>.
Author's Address
作者地址
Michael Mealling Refactored Networks, LLC 1635 Old Hwy 41 Suite 112, Box 138 Kennesaw, GA 30152 US
迈克尔·米林重构网络有限责任公司美国佐治亚州肯尼索市41号老公路1635号112室138号信箱30152
Phone: +1 678 581 9656
EMail: michael@refactored-networks.com
URI: http://www.refactored-networks.com
Phone: +1 678 581 9656
EMail: michael@refactored-networks.com
URI: http://www.refactored-networks.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2008).
版权所有（C）IETF信托基金（2008年）。
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.