Network Working Group                                        M. Mealling
Request for Comments: 3622                                VeriSign, Inc.
Category: Informational                                    February 2004
        
Network Working Group                                        M. Mealling
Request for Comments: 3622                                VeriSign, Inc.
Category: Informational                                    February 2004

A Uniform Resource Name (URN) Namespace for the Liberty Alliance Project

Liberty Alliance项目的统一资源名称（URN）命名空间

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.

本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2004). All Rights Reserved.

版权所有（C）互联网协会（2004年）。版权所有。

Abstract

摘要

This document describes a Uniform Resource Name (URN) namespace that will identify various objects within the Liberty Architecture for federated network identity.

本文档描述了一个统一资源名（URN）命名空间，该命名空间将标识Liberty体系结构中用于联邦网络标识的各种对象。

1. Introduction
1. 介绍

The Liberty Architecture seeks to provide federated network identity in such a way that enhances security, privacy and trust; thus creating a networked world across which individuals and businesses can engage in virtually any transaction without compromising the privacy and security of vital identity information.

Liberty架构寻求以增强安全、隐私和信任的方式提供联邦网络身份；从而创造了一个网络世界，个人和企业可以在不损害重要身份信息的隐私和安全的情况下进行几乎任何交易。

One fundamental component of this architecture is its use of XML [5], and specifically, XML Schema [7] and Namespaces [6]. These components require identifiers that will live far beyond the lifetime of the organization that produced them. As such, a URN namespace for those components that adheres to the assumptions and policies of the Liberty specification is required.

该体系结构的一个基本组件是使用XML[5]，特别是XML模式[7]和名称空间[6]。这些组件需要的标识符将远远超过生成它们的组织的生命周期。因此，对于那些遵循Liberty规范的假设和策略的组件，需要一个URN命名空间。

This namespace specification is for a formal namespace.

此名称空间规范适用于正式名称空间。

2. Specification Template
2. 规范模板

Namespace ID:

命名空间ID:

"liberty" requested.

要求“自由”。

Registration Information:

注册资料：

Registration Version Number: 1

注册版本号：1

Registration Date: 2003-04-01

注册日期：2003-04-01

Declared registrant of the namespace:

已声明命名空间的注册人：

Liberty Alliance Project

自由联盟项目

c/o IEEE-ISTO

c/o IEEE-ISTO

445 Hoes Lane

霍斯巷445号

Piscataway, NJ 08855-1331, USA

美国新泽西州皮斯卡塔韦08855-1331

info@projectliberty.org

info@projectliberty.org

Declaration of structure:

结构声明：

The Namespace Specific Strings (NSS) of all URNs assigned by Liberty will conform to the syntax defined in section 2.2 of RFC 2141 [1]. In addition, all Liberty URN NSSs will consist of a left-to-right series of tokens delimited by colons. The left-to-right sequence of colon-delimited tokens corresponds to descending nodes in a tree. To the right of the lowest naming authority node there may be zero, one or more levels of hierarchical (although not in the RFC 2396 [2] sense of 'hierarchy') naming nodes terminating in a rightmost leaf node. See the section entitled "Identifier assignment" below for more on the semantics of NSSs. This syntax convention is captured in the following normative ABNF [4] rules for Liberty NSSs:

Liberty分配的所有URN的命名空间特定字符串（NSS）将符合RFC 2141[1]第2.2节中定义的语法。此外，所有Liberty URN NSS将由一系列由左至右的标记组成，标记由冒号分隔。从左到右的冒号分隔标记序列对应于树中的降序节点。在最低命名机构节点的右侧，可能有零个、一个或多个层次（尽管不是RFC 2396[2]意义上的“层次”）命名节点终止于最右边的叶节点。有关NSS语义的更多信息，请参阅下面标题为“标识符分配”的部分。Liberty NSSs的以下规范性ABNF[4]规则中包含了该语法约定： 

      Liberty-NSS        =   1*(subStChar) 0*(":" 1*(subStChar))
      subStChar       =   trans / "%" HEXDIG HEXDIG
      trans           =   ALPHA / DIGIT / other / reserved
      other           =   "(" / ")" / "+" / "," / "-" / "." /
                          "=" / "@" / ";" / "$" /
                          "_" / "!" / "*" / "'"
      reserved        =   "%" / "/" / "?" / "#"
        
      Liberty-NSS        =   1*(subStChar) 0*(":" 1*(subStChar))
      subStChar       =   trans / "%" HEXDIG HEXDIG
      trans           =   ALPHA / DIGIT / other / reserved
      other           =   "(" / ")" / "+" / "," / "-" / "." /
                          "=" / "@" / ";" / "$" /
                          "_" / "!" / "*" / "'"
      reserved        =   "%" / "/" / "?" / "#"

The exclusion of the colon from the list of "other" characters means that the colon can only occur as a delimiter between string tokens. Note that this ABNF rule set guarantees that any valid Liberty NSS is also a valid RFC 2141 NSS.

从“其他”字符列表中排除冒号意味着冒号只能作为字符串标记之间的分隔符出现。请注意，此ABNF规则集保证任何有效的Liberty NSS也是有效的RFC 2141 NSS。

For example:

例如： 

         urn:liberty:schemas:authctx:2002:05
         urn:liberty:schemas:core:2002:12
        
         urn:liberty:schemas:authctx:2002:05
         urn:liberty:schemas:core:2002:12

Relevant ancillary documentation:

相关辅助文件：

Liberty Architecture Overview [3]

Liberty建筑概述[3]

Version 1.1

版本1.1

Liberty Alliance Project

自由联盟项目

January 15, 2003

二○○三年一月十五日

Identifier uniqueness considerations:

标识符唯一性注意事项：

Identifiers are assigned by the Liberty Project within its various standards. In the process of publishing a specification all newly minted names are checked against the record of previously assigned names.

标识符由Liberty项目在其各种标准中分配。在发布规范的过程中，所有新创建的名称都会对照以前指定的名称的记录进行检查。

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 Liberty standards publication process.

名称由Liberty标准发布过程指定。

Process of identifier resolution:

标识符解析过程：

At this time no resolution mechanism is specified.

此时未指定解析机制。

Rules for Lexical Equivalence:

词汇对等规则：

Lexical equivalence of two Liberty namespace specific strings (NSSs) is defined as an exact, case-sensitive string match. The Liberty Alliance will assign names of immediately subordinate

两个Liberty命名空间特定字符串（NSSs）的词汇等价性定义为精确的、区分大小写的字符串匹配。自由联盟将指定直接下属的姓名

naming authorities in a case-insensitive fashion, so that there will not be two Liberty-subordinate naming authorities whose names differ only in case.

命名机构不区分大小写，因此不会有两个名称仅大小写不同的Liberty下属命名机构。

Conformance with URN Syntax:

符合URN语法：

There are no additional characters reserved.

没有保留其他字符。

Validation mechanism:

验证机制：

None other than verifying with the correct Liberty specifications.

只能验证Liberty规范是否正确。

Scope:

范围：

Global

全球的

3. IANA Considerations
3. IANA考虑

This document includes a URN Namespace registration that has been entered into the IANA registry for URN NIDs.

本文档包括已输入到URN NID的IANA注册表中的URN命名空间注册。

4. Community Considerations
4. 社区考虑

While there is no resolution mechanism for this namespace, the names themselves are used in public implementations of the Liberty specifications. There are circumstances where objects from the Liberty system will become exposed to the general Internet. In these cases, the use of the Liberty namespace will provide general interoperability benefits to the Internet at large. Additionally, there may be subcomponents of the Liberty specifications that may be adopted by other standards, in which case the URNs used to identify those components and specifications can be easily used to enhance other, non-Liberty based, systems.

虽然这个名称空间没有解析机制，但名称本身在Liberty规范的公共实现中使用。在某些情况下，自由系统中的对象将暴露在普通互联网上。在这些情况下，Liberty名称空间的使用将为整个Internet提供通用的互操作性好处。此外，其他标准可能采用Liberty规范的子组件，在这种情况下，用于识别这些组件和规范的URN可轻松用于增强其他非Liberty系统。

5. Security Considerations
5. 安全考虑

Since there is no defined resolution mechanism for Liberty URNs it is difficult to authenticate the fact that a given namespace actually adheres to the standard, thus applications should be careful to not take some unverified sources assertion that what it is sending adheres to what the actual URN is assigned to.

由于Liberty URN没有定义的解析机制，因此很难验证给定名称空间实际遵守标准的事实，因此应用程序应小心不要采用一些未经验证的源断言，即它发送的内容遵守实际URN分配的内容。

6. References
6. 工具书类
6.1. Normative References
6.1. 规范性引用文件

[1] Moats, R., "URN Syntax", RFC 2141, May 1997.

[1] 护城河，R.，“瓮语法”，RFC 21411997年5月。

[2] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.

[2] Berners Lee，T.，Fielding，R.和L.Masinter，“统一资源标识符（URI）：通用语法”，RFC 2396，1998年8月。

[3] Hodges, J. and T. Watson, "Liberty Architecture Overview", Liberty 1.1, January 2003, <http://www.projectliberty.org/specs/liberty-architecture-overview-v1.1.pdf>.

[3] Hodges，J.和T.Watson，“自由建筑概述”，自由1.11903年1月<http://www.projectliberty.org/specs/liberty-architecture-overview-v1.1.pdf>.

6.2. Informative References
6.2. 资料性引用

[4] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.

[4] Crocker，D.，Ed.和P.Overell，“语法规范的扩充BNF:ABNF”，RFC 2234，1997年11月。

[5] Bray, T., Paoli, J., Sperberg-McQueen, C. and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, <http://www.w3.org/TR/REC-xml>.

[5] Bray，T.，Paoli，J.，Sperberg McQueen，C.和E.Maler，“可扩展标记语言（XML）1.0（第二版）”，W3C REC XML，2000年10月<http://www.w3.org/TR/REC-xml>.

[6] Bray, T., Hollander, D. and A. Layman, "Namespaces in XML", W3C REC-xml-names, January 1999, <http://www.w3.org/TR/REC-xml-names>.

[6] Bray，T.，Hollander，D.和A.Layman，“XML中的名称空间”，W3C REC XML名称，1999年1月<http://www.w3.org/TR/REC-xml-names>.

[7] Thompson, H., Beech, D., Maloney, M. and N. Mendelsohn, "XML Schema Part 1: Structures", W3C REC-xmlschema-1, May 2001, <http://www.w3.org/TR/xmlschema-1/>.

[7] Thompson，H.，Beech，D.，Maloney，M.和N.Mendelsohn，“XML模式第1部分：结构”，W3C REC-xmlschema-12001年5月<http://www.w3.org/TR/xmlschema-1/>.

7. Intellectual Property Statement
7. 知识产权声明

The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat.

IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。

The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.

IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。

8. Author's Address
8. 作者地址

Michael Mealling VeriSign, Inc. 21345 Ridgetop Circle Dulles, VA 20166 USA

美国弗吉尼亚州杜勒斯市Ridgetop Circle Dulles 21345号迈克尔·米林·威瑞辛公司，邮编20166 

   Phone: +1 678 581 9656
   EMail: michael@neonym.net
   URI:   http://www.verisignlabs.com
        
   Phone: +1 678 581 9656
   EMail: michael@neonym.net
   URI:   http://www.verisignlabs.com
9. Full Copyright Statement
9. 完整版权声明

Copyright (C) The Internet Society (2004). All Rights Reserved.

版权所有（C）互联网协会（2004年）。版权所有。

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.

上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS 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.

本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。

Acknowledgement

确认

Funding for the RFC Editor function is currently provided by the Internet Society.

RFC编辑功能的资金目前由互联网协会提供。