Network Working Group L. Daigle
Request for Comments: 2611 Thinking Cat Enterprises
BCP: 33 D. van Gulik
Category: Best Current Practice ISIS/CEO, JRC Ispra
R. Iannella
DSTC Pty Ltd
P. Faltstrom
Tele2/Swipnet
June 1999
Network Working Group L. Daigle
Request for Comments: 2611 Thinking Cat Enterprises
BCP: 33 D. van Gulik
Category: Best Current Practice ISIS/CEO, JRC Ispra
R. Iannella
DSTC Pty Ltd
P. Faltstrom
Tele2/Swipnet
June 1999
URN Namespace Definition Mechanisms
URN命名空间定义机制
Status of this Memo
本备忘录的状况
This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited.
本文件规定了互联网社区的最佳现行做法，并要求进行讨论和提出改进建议。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
The URN WG has defined a syntax for Uniform Resource Names (URNs) [RFC2141], as well as some proposed mechanisms for their resolution and use in Internet applications ([RFC2168, RFC2169]). The whole rests on the concept of individual "namespaces" within the URN structure. Apart from proof-of-concept namespaces, the use of existing identifiers in URNs has been discussed ([RFC2288]), and this document lays out general definitions of and mechanisms for establishing URN "namespaces".
URN工作组定义了统一资源名称（URN）[RFC2141]的语法，以及在Internet应用程序中解析和使用这些名称的一些建议机制（[RFC2168，RFC2169]）。整体基于URN结构中单个“名称空间”的概念。除了概念验证名称空间外，还讨论了URN中现有标识符的使用（[RFC2288]），本文档列出了建立URN“名称空间”的一般定义和机制。
Uniform Resource Names (URNs) are resource identifiers with the specific requirements for enabling location independent identification of a resource, as well as longevity of reference. There are 2 assumptions that are key to this document:
统一资源名称（URN）是资源标识符，具有实现资源位置独立标识以及引用寿命的特定要求。本文件有两个关键假设：
Assumption #1:
假设#1：
Assignment of a URN is a managed process.
URN的分配是一个托管过程。
I.e., not all strings that conform to URN syntax are necessarily valid URNs. A URN is assigned according to the rules of a particular namespace (in terms of syntax, semantics, and process).
也就是说，并非所有符合URN语法的字符串都必须是有效的URN。URN是根据特定名称空间的规则（在语法、语义和过程方面）分配的。
Assumption #2:
假设2：
The space of URN namespaces is managed.
URN名称空间的空间是受管理的。
I.e., not all syntactically correct URN namespaces (per the URN syntax definition) are valid URN namespaces. A URN namespace must have a recognized definition in order to be valid.
也就是说，并非所有语法正确的URN命名空间（根据URN语法定义）都是有效的URN命名空间。URN命名空间必须具有可识别的定义才能有效。
The purpose of this document is to outline a mechanism and provide a template for explicit namespace definition, along with the mechanism for associating an identifier (called a "Namespace ID", or NID) which is registered with the Internet Assigned Numbers Authority, IANA.
本文档旨在概述一种机制，并为显式命名空间定义提供一个模板，以及用于关联在互联网分配号码管理局IANA注册的标识符（称为“命名空间ID”或NID）的机制。
Note that this document restricts itself to the description of processes for the creation of URN namespaces. If "resolution" of any so-created URN identifiers is desired, a separate process of registration in a global NID directory, such as that provided by the NAPTR system [RFC2168], is necessary. See [NAPTR-REG] for information on obtaining registration in the NAPTR global NID directory.
请注意，本文档仅限于描述创建URN命名空间的过程。如果需要“解析”任何这样创建的URN标识符，则需要在全局NID目录中进行单独的注册过程，如NAPTR系统[RFC2168]提供的注册过程。有关在NAPTR全局NID目录中获得注册的信息，请参阅[NAPTR-REG]。
For the purposes of URNs, a "namespace" is a collection of uniquely-assigned identifiers. A URN namespace itself has an identifier in order to
就URN而言，“名称空间”是唯一分配的标识符的集合。URN命名空间本身有一个标识符，以便
- ensure global uniqueness of URNs - (where desired) provide a cue for the structure of the identifier
- 确保URN的全局唯一性-（如果需要）为标识符的结构提供提示
For example, ISBNs and ISSNs are both collections of identifiers used in the traditional publishing world; while there may be some number (or numbers) that is both a valid ISBN identifier and ISSN identifier, using different designators for the two collections ensures that no two URNs will be the same for different resources.
例如，ISBN和ISSN都是传统出版界使用的标识符集合；虽然可能有一些数字（或多个数字）同时是有效的ISBN标识符和ISSN标识符，但对这两个集合使用不同的标识符可确保不同资源的两个URN不会相同。
The development of an identifier structure, and thereby a collection of identifiers, is a process that is inherently dependent on the requirements of the community defining the identifier, how they will be assigned, and the uses to which they will be put. All of these issues are specific to the individual community seeking to define a namespace (e.g., publishing community, association of booksellers, protocol developers, etc); they are beyond the scope of the IETF URN work.
标识符结构的开发，以及标识符集合的开发，是一个内在地依赖于定义标识符的社区的需求、如何分配标识符以及标识符的用途的过程。所有这些问题都是特定于寻求定义名称空间的单个社区（例如，发布社区、书商协会、协议开发人员等）；它们超出了IETF URN工作的范围。
This document outlines the processes by which a collection of identifiers satisfying certain constraints (uniqueness of assignment, etc) can become a bona fide URN namespace by obtaining a NID. In a nutshell, a template for the definition of the namespace is completed for deposit with IANA, and a NID is assigned. The details of the process and possibilities for NID strings are outlined below; first, a template for the definition is provided.
本文档概述了通过获取NID，满足某些约束（分配的唯一性等）的标识符集合可以成为真正的URN命名空间的过程。简言之，名称空间定义的模板已完成，存放在IANA中，并分配了NID。NID字符串的过程细节和可能性概述如下；首先，提供了定义的模板。
Definition of a URN namespace is accomplished by completing the following information template. Apart from providing a mechanism for disclosing structure of the URN namespace, this information is designed to be useful for
URN命名空间的定义是通过完成以下信息模板来完成的。除了提供一种公开URN名称空间结构的机制外，此信息还可用于
- entities seeking to have a URN assigned in a namespace (if applicable) - entities seeking to provide URN resolvers for a namespace (if applicable)
- 寻求在命名空间中分配URN的实体（如果适用）-寻求为命名空间提供URN解析器的实体（如果适用）
This is particularly important for communities evaluating the possibility of using a portion of an existing URN namespace rather than creating their own.
这对于社区评估使用现有URN名称空间的一部分而不是创建自己的名称空间的可能性尤为重要。
Information in the template is as follows:
模板中的信息如下所示：
Namespace ID: Assigned by IANA. In some contexts, a particular one may be requested (see below).
名称空间ID：由IANA分配。在某些情况下，可能会请求特定的一个（见下文）。
Registration Information:
注册资料：
This is information to identify the particular version of registration information:
此信息用于识别特定版本的注册信息：
- registration version number: starting with 1, incrementing by 1 with each new version - registration date: date submitted to the IANA, using the format YYYY-MM-DD as outlined in [ISO8601].
- 注册版本号：从1开始，每个新版本递增1-注册日期：提交给IANA的日期，使用[ISO8601]中概述的格式YYYY-MM-DD。
Declared registrant of the namespace:
已声明命名空间的注册人：
Required: Name and e-mail address. Recommended: Affiliation, address, etc.
必填项：姓名和电子邮件地址。推荐：隶属关系、地址等。
Declaration of syntactic structure:
句法结构声明：
This section should outline any structural features of identifiers in this namespace. At the very least, this description may be used to introduce terminology used in other sections. This structure may also be used for determining realistic caching/shortcuts approaches; suitable caveats should be provided. If there are any specific character encoding rules (e.g., which character should always be used for single-quotes), these should be listed here.
本节应概述此命名空间中标识符的任何结构特征。至少，本说明可用于介绍其他章节中使用的术语。该结构还可用于确定实际的缓存/快捷方式方法；应提供适当的注意事项。如果有任何特定的字符编码规则（例如，哪个字符应始终用于单引号），则应在此处列出这些规则。
Answers might include, but are not limited to:
答案可能包括但不限于：
- the structure is opaque (no exposition) - a regular expression for parsing the identifier into components, including naming authorities
- 该结构是不透明的（没有公开）——用于将标识符解析为组件（包括命名权限）的正则表达式
Relevant ancillary documentation:
相关辅助文件：
This section should list any RFCs, standards, or other published documentation that defines or explains all or part of the namespace structure.
本节应列出定义或解释全部或部分命名空间结构的所有RFC、标准或其他已发布文档。
Answers might include, but are not limited to:
答案可能包括但不限于：
- RFCs outlining syntax of the namespace - Other of the defining community's (e.g., ISO) documents outlining syntax of the identifiers in the namespace - Explanatory material introducing the namespace
- RFC概述名称空间的语法-定义社区的其他（如ISO）文档概述名称空间中标识符的语法-介绍名称空间的解释性材料
Identifier uniqueness considerations: This section should address the requirement that URN identifiers be assigned uniquely -- they are assigned to at most one resource, and are not reassigned.
标识符唯一性注意事项：本节应解决唯一分配URN标识符的要求——它们最多分配给一个资源，并且不会重新分配。
(Note that the definition of "resource" is fairly broad; for example, information on "Today's Weather" might be considered a single resource, although the content is dynamic.)
（请注意，“资源”的定义相当宽泛；例如，“今天的天气”信息可能被视为单一资源，尽管内容是动态的。）
Possible answers include, but are not limited to:
可能的答案包括但不限于：
- exposition of the structure of the identifiers, and partitioning of the space of identifiers amongst assignment authorities which are individually responsible for respecting uniqueness rules - identifiers are assigned sequentially - information is withheld; the namespace is opaque
- 说明标识符的结构，以及分配机构之间标识符空间的划分，分配机构单独负责遵守唯一性规则-标识符按顺序分配-信息被保留；名称空间是不透明的
Identifier persistence considerations:
标识符持久性注意事项：
Although non-reassignment of URN identifiers ensures that a URN will persist in identifying a particular resource even after the "lifetime of the resource", some consideration should be given to the persistence of the usability of the URN. This is particularly important in the case of URN namespaces providing global resolution.
尽管不重新分配URN标识符可确保URN即使在“资源生命周期”之后仍能持续标识特定资源，但仍应考虑URN可用性的持续性。对于提供全局解析的URN命名空间，这一点尤为重要。
Possible answers include, but are not limited to:
可能的答案包括但不限于：
- quality of service considerations
- 服务质素考虑
Process of identifier assignment:
标识符分配过程：
This section should detail the mechanisms and/or authorities for assigning URNs to resources. It should make clear whether assignment is completely open, or if limited, how to become an assigner of identifiers, and/or get one assigned by existing assignment authorities. Answers could include, but are not limited to:
本节应详细说明将URN分配给资源的机制和/或权限。应明确转让是否完全开放，或者如果有限，如何成为标识符的转让人，和/或获得现有转让机构的转让。答案可能包括但不限于：
- assignment is completely open, following a particular algorithm - assignment is delegated to authorities recognized by a particular organization (e.g., the Digital Object Identifier Foundation controls the DOI assignment space and its delegation) - assignment is completely closed (e.g., for a private organization)
- 赋值是完全开放的，遵循特定的算法-赋值被委派给特定组织认可的权威机构（例如，数字对象标识符基金会控制DOI分配空间及其委托）-分配完全关闭（例如，对于私有组织）
Process for identifier resolution:
标识符解析过程：
If a namespace is intended to be accessible for global resolution, it must be registerd in an RDS (Resolution Discovery System, see [RFC2276]) such as NAPTR. Resolution then proceeds according to standard URI resolution processes, and the mechanisms of the RDS. What this section should outline is the requirements for becoming a recognized resolver of URNs in this namespace (and being so-listed in the RDS registry).
如果一个名称空间打算用于全局解析，则必须在RDS（解析发现系统，请参见[RFC2276]）中注册，如NAPTR。然后根据标准URI解析过程和RDS的机制进行解析。本节应概述成为此名称空间中的URN的公认解析器的要求（并在RDS注册表中列出）。
Answers may include, but are not limited to:
答案可能包括但不限于：
- the namespace is not listed with an RDS; this is not relevant - resolution mirroring is completely open, with a mechanism for updating an appropriate RDS - resolution is controlled by entities to which assignment has been delegated
- 名称空间未与RDS一起列出；这与此无关-解决方案镜像是完全开放的，具有更新适当RDS的机制-解决方案由已委派任务的实体控制
Rules for Lexical Equivalence:
词汇对等规则：
If there are particular algorithms for determining equivalence between two identifiers in the underlying namespace (hence, in the URN string itself), rules can be provided here.
如果有特定的算法来确定基础命名空间（因此，在URN字符串本身中）中两个标识符之间的等价性，那么可以在这里提供规则。
Some examples include:
一些例子包括：
- equivalence between hyphenated and non-hyphenated groupings in the identifier string - equivalence between single-quotes and double-quotes - Namespace-defined equivalences between specific characters, such as "character X with or without diacritic marks".
- 标识符字符串中连字符和非连字符分组之间的等效性-单引号和双引号之间的等效性-特定字符之间命名空间定义的等效性，例如“带或不带变音符号的字符X”。
Note that these are not normative statements for any kind of best practice for handling equivalences between characters; they are statements limited to reflecting the namespace's own rules.
请注意，这些不是处理字符之间等价关系的任何类型最佳实践的规范性陈述；它们是仅限于反映名称空间自身规则的语句。
Conformance with URN Syntax:
符合URN语法：
This section should outline any special considerations required for conforming with the URN syntax. This is particularly applicable in the case of legacy naming systems that are used in the context of URNs.
本节应概述符合URN语法所需的任何特殊注意事项。这尤其适用于在URN上下文中使用的传统命名系统。
For example, if a namespace is used in contexts other than URNs, it may make use of characters that are reserved in the URN syntax. This section should flag any such characters, and outline necessary mappings to conform to URN syntax. Normally, this will be handled by hex encoding the symbol.
例如，如果命名空间用于URN以外的上下文，则它可能会使用URN语法中保留的字符。本节应标记任何此类字符，并概述符合URN语法的必要映射。通常，这将通过十六进制编码符号来处理。
For example, see the section on SICIs in [RFC2288].
例如，请参见[RFC2288]中有关SICIs的部分。
Validation mechanism:
验证机制：
Apart from attempting resolution of a URN, a URN namespace may provide mechanism for "validating" a URN -- i.e., determining whether a given string is currently a validly-assigned URN. For example, even if an ISBN URN namespace is created, it is not clear that all ISBNs will translate directly into "assigned URNs".
除了尝试解析URN外，URN命名空间还可以提供“验证”URN的机制——即，确定给定字符串当前是否是有效分配的URN。例如，即使创建了ISBN URN名称空间，也不清楚是否所有ISBN都将直接转换为“分配的URN”。
A validation mechanims might be:
验证机制可能是：
- a syntax grammar - an on-line service - an off-line service
- 语法-在线服务-离线服务
Scope:
范围：
This section should outline the scope of the use of the identifiers in this namespace. Apart from considerations of private vs. public namespaces, this section is critical in evaluating the applicability of a requested NID. For example, a namespace claiming to deal in "social security numbers" should have a global scope and address all social security number structures (unlikely). On the other hand, at a national level, it is reasonable to propose a URN namespace for "this nation's social security numbers".
本节应概述此命名空间中标识符的使用范围。除了考虑私有名称空间和公共名称空间之外，本节对于评估所请求NID的适用性至关重要。例如，一个声称处理“社会安全号码”的名称空间应该具有全局范围，并处理所有社会安全号码结构（不太可能）。另一方面，在国家一级，为“这个国家的社会保障号码”提议一个URN名称空间是合理的。
Different levels of disclosure are expected/defined for namespaces. According to the level of open-forum discussion surrounding the disclosure, a URN namespace may be assigned or may request a particular identifier. The [RFC2434] document suggests the need to specify update mechanisms for registrations -- who is given the authority to do so, from time to time, and what are the processes. Since URNs are meant to be persistently useful, few (if any) changes should be made to the structural interpretation of URN strings (e.g., adding or removing rules for lexical equivalence that might affect the interpretation of URN IDs already assigned). However, it may be important to introduce clarifications, expand the list of authorized URN assigners, etc, over the natural course of a namespace's lifetime. Specific processes are outlined below.
名称空间需要/定义不同级别的公开。根据围绕本公开的公开论坛讨论的级别，可以分配URN名称空间或请求特定标识符。[RFC2434]文件建议需要指定注册的更新机制——不时授予谁这样做的权限，以及流程是什么。由于URN是持久有用的，因此应该对URN字符串的结构解释进行少量（如果有）更改（例如，添加或删除可能影响已分配URN ID解释的词汇等效规则）。但是，在名称空间生命周期的自然过程中，引入澄清、扩展授权URN分配者的列表等可能很重要。具体过程概述如下。
There are 3 categories of URN namespaces defined here, distinguished by expected level of service and required procedures for registration. Furthermore, registration maintenance procedures vary slightly from one category to another.
这里定义了3类URN名称空间，根据预期的服务级别和注册所需的过程进行区分。此外，登记维护程序因类别而异。
I. Experimental: These are not explicitly registered with IANA. They take the form
I.实验性：这些未在IANA明确注册。他们采取这种形式
X-<NID>
X-<NID>
No provision is made for avoiding collision of experimental NIDs; they are intended for use within internal or limited experimental contexts.
没有关于避免实验NID碰撞的规定；它们用于内部或有限的实验环境。
As there is no registration, no registration maintenance procedures are needed.
由于没有注册，因此不需要注册维护程序。
II. Informal: These are registered with IANA and are assigned a number sequence as an identifier, in the format:
二,。非正式：这些文件在IANA注册，并分配一个编号序列作为标识符，格式如下：
"urn-" <number>
“urn-”<number>
where <number> is chosen by the IANA on a First Come First Served basis (see [RFC2434]).
其中，<number>由IANA根据先到先得的原则选择（见[RFC2434]）。
Registrants should send a copy of the registration template (see section 3.0), duly completed, to the
注册人应将正式填写的注册模板副本（见第3.0节）发送至
urn-nid@apps.ietf.org
瓮-nid@apps.ietf.org
mailing and allow for a 2 week discussion period for clarifying the expression of the registration information and suggestions for improvements to the namespace proposal.
邮寄，并留出2周的讨论时间，以澄清注册信息的表达，以及对名称空间提案的改进建议。
After suggestions for clarification of the registration information have been incorporated, the template may be submitted to: iana@iana.org
纳入注册信息澄清建议后，可将模板提交至：iana@iana.org
for assignment of a NID.
用于分配NID。
The only restrictions on <number> are that it consist strictly of digits and that it not cause the NID to exceed length limitations outlined in the URN syntax ([RFC2168]).
<number>的唯一限制是它严格由数字组成，并且不会导致NID超过URN语法（[RFC2168]）中概述的长度限制。
Registrations may be updated by the original registrant, or an entity designated by the registrant, by updating the registration template, submitting it to the discussion list for a further 2 week discussion period, and finally resubmitting it to IANA, as described above.
如上文所述，原始注册人或注册人指定的实体可通过更新注册模板，将其提交至讨论列表再进行2周的讨论，并最终将其重新提交给IANA来更新注册。
III. Formal: These are processed through an RFC review process. The RFC need not be standards-track. The template defined in section 3.0 may be included as part of an RFC defining some other aspect of the namespace, or it may be put forward as an RFC in its own right. The proposed template should be sent to the
三、 正式：通过RFC审查流程进行处理。RFC不需要是标准轨道。第3.0节中定义的模板可以作为定义名称空间其他方面的RFC的一部分，也可以作为RFC单独提出。建议的模板应发送至
urn-nid@apps.ietf.org
瓮-nid@apps.ietf.org
mailing list to allow for a 2 week discussion period for clarifying the expression of the registration information, before the IESG progresses the document to RFC status.
邮件列表，以便在IESG将文件进展至RFC状态之前，有两周的讨论时间澄清注册信息的表达。
A particular NID string is requested, and is assigned by IETF consensus (as defined in [RFC2434]), with the additional constraints that the NID string must
请求一个特定的NID字符串，并由IETF consensus（如[RFC2434]中所定义）分配，NID字符串必须具有附加约束
- not be an already-registered NID - not start with "x-" (see Type I above) - not start with "urn-" (see Type II above) - not start with "XY-", where XY is any combination of 2 ASCII letters (see NOTE, below) - be more than 2 letters long
- 不是已注册的NID-不以“x-”开头（见上文类型I）-不以“urn-”开头（见上文类型II）-不以“XY-”开头，其中XY是2个ASCII字母的任意组合（见下文注释）-长度超过2个字母
NOTE: ALL two-letter combinations, and two-letter combinations followed by "-" and any sequence of valid NID characters, are reserved for potential use as countrycode-based NIDs for eventual national registrations of URN namespaces. The definition and scoping of rules for allocation of responsibility for such namespaces is beyond the scope of this document.
注：所有两个字母组合，以及后跟“-”的两个字母组合和任何有效的NID字符序列，都保留作为基于国家代码的NID用于最终的URN名称空间国家注册。此类名称空间责任分配规则的定义和范围超出了本文档的范围。
Registrations may be updated by updating the RFC through standard IETF RFC update mechanisms. Thus, proposals for updates may be made by the original authors, other IETF participants, or the IESG. In any case, the proposed updated template must be circulated on the urn-nid discussion list, allowing for a 2 week review period.
可以通过标准IETF RFC更新机制更新RFC来更新注册。因此，更新建议可由原始作者、其他IETF参与者或IESG提出。在任何情况下，建议的更新模板必须在urn nid讨论列表上分发，允许有2周的审查期。
URN namespace registrations will be posted in the anonymous FTP directory "ftp://ftp.isi.edu/in-notes/iana/assignments/URN-namespaces/".
URN命名空间注册将发布在匿名FTP目录中“ftp://ftp.isi.edu/in-notes/iana/assignments/URN-namespaces/".
The following example is provided for the purposes of illustration of the URN NID template described in section 3.0. Although it is based on a hypothetical "generic Internet namespace" that has been discussed informally within the URN WG, there are still technical and infrastructural issues that would have to be resolved before such a namespace could be properly and completely described.
以下示例用于说明第3.0节中描述的URN NID模板。尽管它是基于一个假设的“通用互联网名称空间”，该名称空间已在URN工作组中进行了非正式讨论，但在正确完整地描述该名称空间之前，仍有一些技术和基础设施问题需要解决。
Namespace ID: To be assigned
名称空间ID：要分配的名称空间ID
Registration Information:
注册资料：
Version 1 Date: <when submitted>
版本1日期：<提交时>
Declared registrant of the namespace:
已声明命名空间的注册人：
Required: Name and e-mail address. Recommended: Affiliation, address, etc.
必填项：姓名和电子邮件地址。推荐：隶属关系、地址等。
Declared registrant of the namespace:
已声明命名空间的注册人：
Name: T. Cat E-mail: leslie@thinkingcat.com Affiliation: Thinking Cat Enterprises Address: 1 ThinkingCat Way Trupville, NewCountry
姓名：T.Cat电子邮件：leslie@thinkingcat.com联系：Thinking Cat企业地址：1 Thinking Cat Way Trupville，NewCountry
Declaration of structure:
结构声明：
The identifier structure is as follows:
标识符结构如下所示：
URN:<assigned number>:<FQDN>:<assigned US-ASCII string>
URN:<assigned number>:<FQDN>:<assigned US-ASCII string>
where FQDN is a fully-qualified domain name, and the assigned string is conformant to URN syntax requirements.
其中FQDN是一个完全限定的域名，分配的字符串符合URN语法要求。
Relevant ancillary documentation:
相关辅助文件：
Definition of domain names, found in:
域名的定义，见：
P. Mockapetris, "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION", RFC1035, November 1987.
P.Mockapetris，“域名-实现和规范”，RFC1035，1987年11月。
Identifier uniqueness considerations: Uniqueness is guaranteed as long as the assigned string is never reassigned for a given FQDN, and that the FQDN is never reassigned.
标识符唯一性注意事项：只要从未为给定FQDN重新分配分配的字符串，并且从未重新分配FQDN，就可以保证唯一性。
N.B.: operationally, there is nothing that prevents a domain name from being reassigned; indeed, it is not an uncommon occurrence. This is one of the reasons that this example makes a poor URN namespace in practice, and is therefore not seriously being proposed as it stands. Identifier persistence considerations:
注意：在操作上，没有任何东西可以阻止域名被重新分配；事实上，这种情况并不罕见。这是该示例在实践中使用较差的URN名称空间的原因之一，因此目前没有认真地提出。标识符持久性注意事项：
Persistence of identifiers is dependent upon suitable delegation of resolution at the level of "FQDN"s, and persistence of FQDN assignment.
标识符的持久性取决于“FQDN”级别上适当的解析委派以及FQDN分配的持久性。
Same note as above.
同上。
Process of identifier assignment:
标识符分配过程：
Assignment of these URNs delegated to individual domain name holders (for FQDNs). The holder of the FQDN registration is required to maintain an entry (or delegate it) in the NAPTR RDS. Within each of these delegated name partitions, the string may be assigned per local requirements.
将这些URN分配给各个域名持有者（对于FQDN）。FQDN注册持有人需要在NAPTR RDS中维护（或委派）一个条目。在每个委托名称分区中，可以根据本地需求分配字符串。
e.g. urn:<assigned number>:thinkingcat.com:001203
e.g. urn:<assigned number>:thinkingcat.com:001203
Process for identifier resolution:
标识符解析过程：
Domain name holders are responsible for operating or delegating resolution servers for the FQDN in which they have assigned URNs.
域名持有者负责为其已分配URN的FQDN操作或委派解析服务器。
Rules for Lexical Equivalence:
词汇对等规则：
FQDNs are case-insensitive. Thus, the portion of the URN
FQDN不区分大小写。因此，骨灰盒的部分
urn:<assigned number>:<FQDN>:
urn:<assigned number>：<FQDN>：
is case-insenstive for matches. The remainder of the identifier must be considered case-sensitve.
这是一个不支持匹配的案例。标识符的其余部分必须视为区分大小写。
Conformance with URN Syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation mechanism:
验证机制：
None specified.
没有具体说明。
Scope:
范围：
Global.
全球的
This document largely focuses on providing mechanisms for the declaration of public information. Nominally, these declarations should be of relatively low security profile, however there is always the danger of "spoofing" and providing mis-information. Information in these declarations should be taken as advisory.
本文件主要侧重于提供公布公共信息的机制。名义上，这些声明应该具有相对较低的安全性，但是始终存在“欺骗”和提供错误信息的危险。这些声明中的信息应被视为咨询信息。
[RFC2168] Daniel, R. and M. Mealling, "Resolution of Uniform Resource Identifiers using the Domain Name System", RFC 2168, June 1997.
[RFC2168]Daniel，R.和M.Mealling，“使用域名系统解析统一资源标识符”，RFC 2168，1997年6月。
[RFC2169] Daniel, R., "A Trivial Convention for using HTTP in URN Resolution", RFC 2169, June 1997.
[RFC2169]Daniel，R.，“在URN解析中使用HTTP的简单约定”，RFC2169，1997年6月。
[ISO8601] ISO 8601 : 1988 (E), "Data elements and interchange formats - Information interchange - Representation of dates and times"
[ISO8601]ISO 8601:1988（E），“数据元素和交换格式-信息交换-日期和时间的表示”
[RFC2288] Lynch, C., Preston, C. and R. Daniel, "Using Existing Bibliographic Identifiers as Uniform Resource Names", RFC 2288, February 1998.
[RFC2288]Lynch，C.，Preston，C.和R.Daniel，“使用现有书目标识符作为统一资源名”，RFC 2288，1998年2月。
[NAPTR-REG] Mealling, M., "Assignment Procedures for NAPTR DNS URI Resolution", Work in Progress.
[NAPTR-REG]Mealling，M.，“NAPTR DNS URI解析的分配程序”，正在进行的工作。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[RFC2434]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, December 1994.
[RFC1737]Sollins，K.和L.Masinter，“统一资源名称的功能要求”，RFC 1737，1994年12月。
[RFC2276] Sollins, K., "Architectural Principles of Uniform Resource Name Resolution", RFC 2276, January 1998.
[RFC2276]Sollins，K.，“统一资源名称解析的架构原则”，RFC 2276，1998年1月。
Leslie L. Daigle Thinking Cat Enterprises
莱斯利·L·戴格尔思维猫企业
EMail: leslie@thinkingcat.com
EMail: leslie@thinkingcat.com
Dirk-Willem van Gulik ISIS/STA/CEO - TP 270 Joint Research Centre Ispra 21020 Ispra (Va) Italy.
Dirk Willem van Gulik ISIS/STA/CEO-TP 270联合研究中心Ispra 21020 Ispra（弗吉尼亚州）意大利。
Phone: +39 332 78 9549 or 5044
Fax: +39 332 78 9185
EMail: Dirk.vanGulik@jrc.it
Phone: +39 332 78 9549 or 5044
Fax: +39 332 78 9185
EMail: Dirk.vanGulik@jrc.it
Renato Iannella DSTC Pty Ltd Gehrmann Labs, The Uni of Queensland AUSTRALIA, 4072
Renato Iannella DSTC私人有限公司Gehrmann实验室，澳大利亚昆士兰大学，4072
Phone: +61 7 3365 4310
Fax: +61 7 3365 4311
EMail: renato@dstc.edu.au
Phone: +61 7 3365 4310
Fax: +61 7 3365 4311
EMail: renato@dstc.edu.au
Patrik Faltstrom Tele2/Swipnet Borgarfjordsgatan 16 P.O. Box 62 S-164 94 Kista SWEDEN
Patrik Faltstrom Tele2/Swipnet Borgarfjordsgatan 16号邮政信箱62 S-164 94瑞典基斯塔
Phone: +46-5626 4000
Fax: +46-5626 4200
EMail: paf@swip.net
Phone: +46-5626 4000
Fax: +46-5626 4200
EMail: paf@swip.net
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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 assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
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编辑功能的资金目前由互联网协会提供。