Network Working Group                                          A. Monrad
Request for Comments: 5279                                     S. Loreto
Category: Informational                                         Ericsson
                                                               July 2008
        
Network Working Group                                          A. Monrad
Request for Comments: 5279                                     S. Loreto
Category: Informational                                         Ericsson
                                                               July 2008
        

A Uniform Resource Name (URN) Namespace for the 3rd Generation Partnership Project (3GPP)

第三代合作伙伴关系项目(3GPP)的统一资源名称(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.

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

Abstract

摘要

This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the 3rd Generation Partnership Project (3GPP). 3GPP defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided by the 3GPP Support Team.

本文档描述了由第三代合作伙伴关系项目(3GPP)发布的统一资源名称空间(URN)资源的名称空间标识符(NID)。3GPP定义并管理利用此URN名称模型的资源。这些和其他资源类型的管理活动由3GPP支持团队提供。

Table of Contents

目录

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  URN Specification for the 3GPP Namespace Identifier (NID) . . . 2
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Namespace Considerations  . . . . . . . . . . . . . . . . . . . 5
   5.  Community Considerations  . . . . . . . . . . . . . . . . . . . 5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 6
        
   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  URN Specification for the 3GPP Namespace Identifier (NID) . . . 2
   3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
   4.  Namespace Considerations  . . . . . . . . . . . . . . . . . . . 5
   5.  Community Considerations  . . . . . . . . . . . . . . . . . . . 5
   6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 6
        
1. Introduction
1. 介绍

3GPP is a cooperation of international telecommunication standards bodies developing technologies for cellular networks. This activity is supported by a membership composed of network operators, equipment vendors, content providers, and other suppliers to the mobile market.

3GPP是国际电信标准机构合作开发蜂窝网络技术。该活动由网络运营商、设备供应商、内容提供商和移动市场的其他供应商组成的成员支持。

Some of the technologies being developed by 3GPP need URN namespaces that are managed so that they are unique and persistent. To assure that the uniqueness is absolute, the registration of a specific NID for use by 3GPP was deemed appropriate. Therefore, a full and complete registration will follow the namespace specification process as defined in RFC 3406 [RFC3406].

3GPP开发的一些技术需要管理URN名称空间,以便它们是唯一和持久的。为了确保唯一性是绝对的,3GPP使用特定NID的注册被认为是适当的。因此,完全注册将遵循RFC 3406[RFC3406]中定义的名称空间规范过程。

2. URN Specification for the 3GPP Namespace Identifier (NID)
2. 3GPP命名空间标识符(NID)的URN规范

Namespace ID:

命名空间ID:

3gpp

3gpp

Registration Information:

注册资料:

registration version number: 1 registration date: 2007-11-16

注册版本号:1注册日期:2007-11-16

Declared registrant of the namespace:

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

Registering organization Name: 3rd Generation Partnership Project Address: ETSI Mobile Competence Centre 650, route des Luciole 06921 Sophia-Antipolis Cedex France

注册机构名称:第三代合作伙伴项目地址:ETSI移动能力中心650,法国索菲亚-安提波利斯赛德斯路06921号

Designated contact Role: Specifications Manager Email: john.meredith@etsi.org

指定联系人角色:规格经理电子邮件:john。meredith@etsi.org

Declaration of syntactic structure:

句法结构声明:

The Namespace Specific String (NSS) of all URNs that use the "3gpp" NID will have the following structure:

使用“3gpp”NID的所有URN的命名空间特定字符串(NSS)将具有以下结构:

            urn:3gpp:{3gpp-urn}
        
            urn:3gpp:{3gpp-urn}
        

where the "3gpp-urn" is a US-ASCII string that conforms to the NSS(Namespace Specific String) Syntax described in RFC 2141 [RFC2141] and defines a specific resource type.

其中,“3gpp urn”是符合RFC 2141[RFC2141]中描述的NSS(命名空间特定字符串)语法并定义特定资源类型的US-ASCII字符串。

Relevant ancillary documentation:

相关辅助文件:

3GPP provides information on registration for each URN. More information about 3GPP and the registration activities and procedures to be followed are available at:

3GPP提供每个URN的注册信息。有关3GPP以及要遵循的注册活动和程序的更多信息,请访问:

            http://www.3gpp.org/tb/Other/URN/URN.htm
        
            http://www.3gpp.org/tb/Other/URN/URN.htm
        

Identifier uniqueness considerations:

标识符唯一性注意事项:

3GPP will manage resources using the "3gpp" NID and will be the authority for managing the "3gpp-urn" strings. In the associated procedures, 3GPP will ensure the uniqueness of the strings themselves or shall permit secondary responsibility for management of well-defined sub-trees.

3GPP将使用“3GPP”NID管理资源,并将成为管理“3GPP urn”字符串的机构。在相关程序中,3GPP将确保字符串本身的唯一性,或者允许对定义良好的子树进行二级管理。

3GPP may permit use of experimental type values that will not be registered. As a consequence, multiple users may end up using the same value for separate uses. Unregistered type values will only be allowed in sub-namespaces clearly marked as experimental, to help implementors avoid "leaking" experimental values into real use.

3GPP可能允许使用未注册的实验类型值。因此,多个用户可能最终使用相同的值进行单独使用。未注册的类型值只允许在明确标记为实验的子名称空间中使用,以帮助实现者避免将实验值“泄漏”到实际使用中。

Identifier persistence considerations:

标识符持久性注意事项:

3GPP will provide clear documentation of the registered uses of the "3gpp" NID. This will be structured such that each "3gpp-urn", if needed, will have a separate description and registration table.

3GPP将提供“3GPP”NID注册使用的清晰文档。其结构将使得每个“3gpp urn”(如果需要)将具有单独的描述和登记表。

The registration tables and information will be published and maintained by 3GPP on its web site.

注册表和信息将由3GPP在其网站上发布和维护。

Process of identifier assignment:

标识符分配过程:

3GPP will provide procedures for registration of each type of resource that it maintains. Each such resource may have three types of registration activities:

3GPP将为其维护的每种类型的资源提供注册程序。每个此类资源可能有三种类型的注册活动:

1. Registered values associated with 3GPP specifications or services

1. 与3GPP规范或服务相关的注册值

2. Registration of values or sub-trees to other entities

2. 将值或子树注册到其他实体

3. Name models for use in experimental purposes

3. 命名用于实验目的的模型

New Namespace Identifier (NID) labels

新名称空间标识符(NID)标签

The Entries in the registration table will be the following:

登记表中的条目如下:

        3gpp-urn:    the registered value;
        Description: description of the registered value;
        Reference:   3GPP spec that defines the value;
        Contact:     person requesting the URN assignment.
        
        3gpp-urn:    the registered value;
        Description: description of the registered value;
        Reference:   3GPP spec that defines the value;
        Contact:     person requesting the URN assignment.
        

Process for identifier resolution:

标识符解析过程:

The namespace is not listed with a Resolution Discovery System (RDS), as this is not relevant.

命名空间未与解析发现系统(RDS)一起列出,因为这与此无关。

Rules for Lexical Equivalence:

词汇对等规则:

No special considerations; the rules for lexical equivalence of RFC 2141 [RFC2141] apply.

没有特别考虑;RFC 2141[RFC2141]的词汇对等规则适用。

Conformance with URN Syntax:

符合URN语法:

No special considerations.

没有特别考虑。

Validation mechanism:

验证机制:

None specified. URN assignment will be handled by procedures supported and maintained by 3GPP.

没有具体说明。URN分配将由3GPP支持和维护的程序处理。

Scope:

范围:

Global

全球的

3. Examples
3. 例子

The following examples are representative URNs that could be assigned by 3GPP. They are not actual strings that are assigned.

以下示例是可由3GPP分配的代表性URN。它们不是指定的实际字符串。

urn:3gpp:featurephones

urn:3gpp:featurephones

Defines the "3gpp-urn" to be used for "featurephones".

定义用于“功能手机”的“3gpp urn”。

urn:3gpp:acme.foo-serv

urn:3gpp:acme.foo-serv

Defines the URN associated with the operator identified by the "3gpp-urn" value "acme", which has decided to register and provide information about its service identified by value "foo-serv".

定义与由“3gpp URN”值“acme”标识的运营商相关联的URN,该运营商已决定注册并提供关于其由值“foo serv”标识的服务的信息。

4. Namespace Considerations
4. 命名空间注意事项

The 3rd Generation Partnership Project is developing a variety of enablers and applications. Some of these require information to be fully specified.

第三代合作伙伴项目正在开发各种使能技术和应用程序。其中一些要求完全指定信息。

For proper operation, descriptions of the needed information must exist for the URNs and be available in a unique, reliable, and persistent manner.

为了正确操作,必须为URN提供所需信息的描述,并以独特、可靠和持久的方式提供。

As 3GPP is ongoing and covers many technical areas, the possibility of binding to various other namespace repositories has been deemed impractical. Each object or description, as defined in 3GPP, could possibly be related to multiple different other namespaces, so further conflicts of association could occur. Thus, the intent is to utilize the 3GPP specifications manager as the naming authority for 3GPP-defined URNs and its descriptions.

由于3GPP正在进行中并涵盖许多技术领域,因此绑定到各种其他名称空间存储库的可能性被认为是不切实际的。3GPP中定义的每个对象或描述可能与多个不同的其他名称空间相关,因此可能会发生进一步的关联冲突。因此,目的是利用3GPP规范管理器作为3GPP定义的URN及其描述的命名机构。

5. Community Considerations
5. 社区考虑

The objects and descriptions required for enablers produced by 3GPP are generally available for use by other organizations. The 3rd Generation Partnership Project Support Office will provide access and support for name requests by these organizations. This support can be enabled in a timely and responsive fashion as new objects and descriptions are produced.

3GPP产生的使能器所需的对象和描述通常可供其他组织使用。第三代合作伙伴关系项目支持办公室将为这些组织的名称请求提供访问和支持。随着新对象和描述的产生,这种支持可以以及时和响应的方式启用。

6. Security Considerations
6. 安全考虑

There are no security considerations other than those normally associated with the use and resolution of URNs in general.

除了通常与骨灰盒的使用和解析相关的安全注意事项外,没有其他安全注意事项。

7. IANA Considerations
7. IANA考虑

This section registers a new URN NID with the registration provided in Section 2.

本节使用第2节中提供的注册来注册新的URN NID。

"3gpp-urn" strings are identified by label managed by 3GPP. Thus, creating a new label does not require any IANA action.

“3gpp urn”字符串由3gpp管理的标签标识。因此,创建新标签不需要任何IANA操作。

8. Normative References
8. 规范性引用文件

[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.

[RFC3406]Daigle,L.,van Gulik,D.,Iannella,R.,和P.Faltstrom,“统一资源名称(URN)命名空间定义机制”,BCP 66,RFC 3406,2002年10月。

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

[RFC2141]Moats,R.,“瓮语法”,RFC 21411997年5月。

Authors' Addresses

作者地址

Atle Monrad Ericsson Televeien 1 Grimstad 4898 Norway

Atle Monrad Ericsson Televien 1 Grimstad 4898挪威

   EMail: atle.monrad@ericsson.com
        
   EMail: atle.monrad@ericsson.com
        

Salvatore Loreto Ericsson Hirsalantie 11 Jorvas 02420 Finland

萨尔瓦托·洛雷托·爱立信·赫萨兰蒂11 Jorvas 02420芬兰

   EMail: Salvatore.Loreto@ericsson.com
        
   EMail: Salvatore.Loreto@ericsson.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.