]> Filament

P.O. Box 787 Parker CO 80134 USA peter@filament.com https://filament.com/

1770 Massachusetts Ave, Ste 322 Cambridge MA 02140 USA +1 617 245 1457 john-ietf@jck.com

Applications URNBIS Uniform Resource Name URN Uniform Resource Identifier URI A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier. With regard to URN syntax, this document defines the canonical syntax for URNs (in a way that is consistent with URI syntax), specifies methods for determining URN-equivalence, and discusses URI conformance. With regard to URN namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and describes procedures for registering namespace identifiers with the Internet Assigned Numbers Authority (IANA). This document obsoletes both RFC 2141 and RFC 3406.

A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the "urn" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier. A URN namespace is a collection of such URNs, each of which is (1) unique, (2) assigned in a consistent and managed way, and (3) assigned according to a common definition. (Some URN namespaces create names that exist only as URNs, whereas others assign URNs based on names that were already created in non-URN identifier systems, such as ISBNs , ISSNs , or RFCs .) The assignment of URNs is done by an organization (or, in some cases, according to an algorithm or other automated process) that has been formally delegated a URN namespace within the "urn" scheme (e.g., a URN in the 'example' URN namespace might be of the form "urn:example:foo"). This document rests on two key assumptions: Assignment of a URN is a managed process. The space of URN namespaces is itself managed. While other URI schemes may allow resource identifiers to be freely chosen and assigned, such is not the case for URNs. The syntactical correctness of a name starting with "urn:" is not sufficient to make it a URN. In order for the name to be a valid URN, the namespace identifier (NID) needs to be registered in accordance with the rules defined here and the remaining parts of the assigned-name portion of the URN need to be generated in accordance with the rules for the registered URN namespace. So that information about both URN syntax and URN namespaces is available in one place, this document does the following: Defines the canonical syntax for URNs in general (in a way that is consistent with URI syntax), specifies methods for determining URN-equivalence, and discusses URI conformance. Specifies a method for defining a URN namespace and associating it with a namespace identifier (NID), and describes procedures for registering URN NIDs with the Internet Assigned Numbers Authority (IANA). For URN syntax and URN namespaces, this document modernizes and replaces the original specifications for URN syntax and for the definition and registration of URN namespaces . These modifications build on the key requirements provided in the original functional description for URNs and on the lessons of many years of experience. In those original documents and in the present one, the intent is to define URNs in a consistent manner so that, wherever practical, the parsing, handling, and resolution of URNs can be independent of the URN namespace within which a given URN is assigned. Together with input from several key user communities, the history and experiences with URNs dictated expansion of the URN definition to support new functionality, including the use of syntax explicitly reserved for future standardization in RFC 2141. All URN namespaces and URNs that were valid under the earlier specifications remain valid even though it may be useful to update some of them to take advantage of new features. The foregoing considerations, together with various differences between URNs and URIs that are locators (specifically URLs) as well as the greater focus on URLs in RFC 3986 as the ultimate successor to and , may lead to some interpretations of RFC 3986 and this specification that appear (or perhaps actually are) not completely consistent, especially with regard to actions or semantics other than the basic syntax itself. If such situations arise, discussions of URNs and URN namespaces should be interpreted according to this document and not by extrapolation from RFC 3986. Summaries of changes from RFC 2141 and RFC 3406 appear in and respectively. This document obsoletes both and . While it does not explicitly update or replace or , the reader who references those documents should be aware that the conceptual model of URNs in this document is slightly different from those older specifications.

The following terms are distinguished from each other as described below: A URI (as defined in RFC 3986) using the "urn" scheme and with the properties of a "name" as described in that document as well as the properties described in this one. The term applies to the entire URI including its optional components. Note to the reader: the term "URN" has been used in other contexts to refer to a URN namespace, the namespace identifier (NID), the Assigned-name, and to URIs that do not use the "urn" scheme. All but the last of these is described using more specific terminology elsewhere in this document, but, because of those other uses, the term should be used and interpreted with care. An identifier that provides a means of accessing a resource. A managed collection of names. This document refers to identifier systems outside the context of URNs as "non-URN identifier systems". An identifier system that is associated with a URN namespace identifier (NID). The identifier associated with a URN namespace. The URN-namespace-specific part of a URN. The combination of the 'urn:' scheme, the NID, and the NSS. An "Assigned-name" is consequently a substring of a URN (as defined above) if that URN contains any additional components (see ). The term "name" is deliberately not defined here and should be (and in practice, is) used only very informally. RFC 3986 uses the term as a category of URI distinguished from "locator" (Section 1.1.3) but also uses it in other contexts. If those uses are treated as definitions, they conflict with, e.g., the idea of the name of a URN namespace, i.e., a NID or terms associated with non-URN identifier systems. This document uses the terms "resource", "identifier", "identify", "dereference", "representation", and "metadata" roughly as defined in the URI specification . This document uses the terms "resolution" and "resolver" in roughly the sense in which they were used in the original discussion of architectural principles for URNs , i.e., "resolution" is the act of supplying services related to the identified resource, such as translating the persistent URN into one or more current locators for the resource, delivering metadata about the resource in an appropriate format, or even delivering a representation of the resource (e.g., a document) without requiring further intermediaries. At the time of this writing, resolution services are described in . On the distinction between representations and metadata, see Section 1.2.2 of . Several other terms related to "normalization" operations that are not part of the Unicode Standard are also used here as they are in RFC 3986. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

To a degree much greater than when URNs were first considered and their uses outlined (see ), issues of persistent identifiers on the Internet involve fundamental design tradeoffs that are much broader than URNs or the URN approach, and even touch on open research questions within the information sciences community. Ideal and comprehensive specifications about what should be done or required across the entire universe of URNs would require general agreement about, and solutions to, a wide range of such issues. Although some of those issues were introduced by the Internet or computer-age approaches to character encodings and data abstraction, others predate the Internet and computer systems by centuries; there is unlikely to be agreement about comprehensive solutions in the near future. Although this specification consequently contains some requirements and flexibility that would not be present in a more perfect world, this has been necessary in order to produce a consensus specification that provides a modernized definition of URNs (the unattractive alternative would have been to not modernize the definition in spite of widespread deployment). The following sub-sections describe two of the relevant issues in greater detail.

One issue that is specific to URNs (as opposed to naming systems in general) is the fairly difficult topic of "resolution", discussed in , , , and elsewhere below. With traditional Uniform Resource Locators (URLs), i.e., with most URIs that are locators, resolution is relatively straightforward because it is used to determine an access mechanism which in turn is used to dereference the locator by (typically) retrieving a representation of the associated resource, such as a document (see Section 1.2.2 of ). By contrast, resolution for URNs is more flexible and varied. One important case involves the mapping of a URN to one or more locators. In this case, the end result is still a matter of dereferencing the mapped locator(s) to one or more representations. The primary difference here is persistence: even if a mapped locator has changed (e.g., a DNS domain name has changed hands and a URL has not been modified to point to a new location or, in a more extreme and hypothetical case, the DNS is replaced entirely), a URN user will be able to obtain the correct representation (e.g., a document) as long as the resolver has kept its URN-to-locator mappings up to date. Consequently, the relevant relationships can be defined quite precisely for URNs that resolve to locators which in turn are dereferenced to a representation. However, this specification permits several other cases of URN resolution as well as URNs for resources that do not involve information retrieval systems. This is true either individually for particular URNs or (as defined below) collectively for entire URN namespaces. Consider a namespace of URNs that resolve to locators which in turn are dereferenced only to metadata about resources because the underlying systems contain no representations of those resources; an example might be a URN namespace for International Standard Name Identifiers (ISNI) as that identifier system is defined in , wherein by default a URN would be resolved only to a metadata record describing the individual identified by the ISNI. Consider also URNs that resolve to representations only if the requesting entity is authorized to obtain the representation, whereas other entities can obtain only metadata about the resource; an example might be documents held within the legal depository collection of a national library. Finally, some URNs might not be intended to resolve to locators at all; examples might include URNs identifying XML namespace names (e.g., the 'dgiwg' URN namespace specified by ), URNs identifying application features that can be supported within a communications protocol (e.g., the 'alert' URN namespace specified by ), and URNs identifying enumerated types such as values in a registry (e.g., a URN namespace could be used to individually identify the values in all IANA registries, as provisionally proposed in ). Various types of URNs and multiple resolution services which may be available for them leave the concept of "resolution" more complicated but also much richer for URNs than the straightforward case of resolution to a locator that is dereferenced to a representation.

A similar set of considations apply to character sets and encodings. URNs, especially URNs that will be used as user-facing identifiers, should be convenient to use in local languages and writing systems, easily specified with a wide range of keyboards and local conventions, and unambiguous. There are tradeoffs among those goals and it is impossible at present to see how a simple and readily-understandable set of rules could be developed that would be optimal, or even reasonable, for all URNs. The discussion in defines an overall framework that should make generalized parsing and processing possible, but also makes recommendations about rules for individual URN namespaces.

As discussed above, the syntax for URNs in this specification allows significantly more functionality than was the case in the earlier specifications, most recently . It is also harmonized with the general URI syntax (which, it must be noted, was completed after the earlier URN specifications). However, this specification does not extend the URN syntax to allow direct use of characters outside the ASCII range . That restriction implies that any such characters need to be percent-encoded as described in Section 2.1 of the URI specification . The basic syntax for a URN is defined using the Augmented Backus-Naur Form (ABNF) as specified in . Rules not defined here (specifically: alphanum, fragment, and pchar) are defined as part of the URI syntax and used here to point out the syntactic relationship with the terms used there. The definitions of some of the terms used below are not comprehensive; additional restrictions are imposed by the prose that can be found in sections of this document that are specific to those terms (especially r-component in and q-component in ).

The question mark character "?" can be used without percent-encoding inside r-components, q-components, and f-components. Other than inside those components a "?" that is not immediately followed by "=" or "+" is not defined for URNs and SHOULD be treated as a syntax error by URN-specific parsers and other processors. The following sections provide additional information about the syntactic elements of URNs.

Namespace identifiers (NIDs) are case insensitive (e.g., "ISBN" and "isbn" are equivalent). Characters outside the ASCII range are not permitted in NIDs, and no encoding mechanism for such characters is supported. and impose additional constraints on the strings that can be used as NIDs, i.e., the syntax shown above is not comprehensive.

The namespace specific string (NSS) is a string, unique within a URN namespace, that is assigned and managed in a consistent way and that conforms to the definition of the relevant URN namespace. The combination of the NID (unique across the entire "urn" scheme) and the NSS (unique within the URN namespace) ensures that the resulting URN is globally unique. The NSS as specified in this document allows several characters not permitted by earlier specifications (see ). In particular, the "/" character, which is now allowed, effectively makes it possible to encapsulate hierarchical names from non-URN identifier systems. For instance, consider the hypothetical example of a hierarchical identifier system in which the names take the form of a sequence of numbers separated by the "/" character, such as "1/406/47452/2". If the authority for such names were to use URNs, it would be natural to place the existing name in the NSS, resulting in URNs such as "urn:example:1/406/47452/2". Those changes to the syntax for the NSS do not modify the encoding rules for URN namespaces that were defined in accordance with . If any such URN namespace whose names are used outside of the URN context (i.e., in a non-URN identifier system) also allows the use of "/", "~", or "&" in the native form within that identifier system, then the encoding rules for that URN namespace are not changed by this specification. Depending on the rules governing a non-URN identifier system and its associated URN namespace, names that are valid in that identifier system might contain characters that are not allowed by the "pchar" production referenced above (e.g., characters outside the ASCII range or, consistent with the restrictions in RFC 3986, the characters "/", "?", "#", "[", and "]"). While such a name might be valid within the non-URN identifier system, it is not a valid URN until it has been translated into an NSS that conforms to the rules of that particular URN namespace. In the case of URNs that are formed from names that exist separately in a non-URN identifier system, translation of a name from its "native" format to URN format is accomplished by using the canonicalization and encoding methods defined for URNs in general or specific rules for that URN namespace. Software that is not aware of namespace-specific canonicalization and encoding rules MUST NOT construct URNs from the name in the non-URN identifier system. In particular, with regard to characters outside the ASCII range, URNs that appear in protocols or that are passed between systems MUST use only Unicode characters encoded in UTF-8 and further encoded as required by RFC 3986. To the extent feasible consistent with the requirements of names defined and standardized elsewhere, as well as the principles discussed in , the characters used to represent names SHOULD be restricted to either ASCII letters and digits or to the characters and syntax of some widely-used model such as those of IDNA , PRECIS , or the Unicode Identifier and Pattern Syntax specification . In order to make URNs as stable and persistent as possible when protocols evolve and the environment around them changes, URN namespaces SHOULD NOT allow characters outside the basic Latin repertoire unless the nature of the particular URN namespace makes such characters necessary.

This specification includes three optional components in the URN syntax. They are known as r-component, q-component, and f-component and are described in more detail below. Because this specification focuses almost exclusively on URN syntax, it does not define detailed semantics of these components for URNs in general. However, each of these components has a distinct role that is independent of any given URN and its URN namespace. It is intended that clients will be able to handle these components uniformly for all URNs. These components MAY be used with URNs from existing URN namespaces, whether or not a URN namespace explicitly supports them. However, consistent with the approach taken in RFC 3986, the behavior of a URN that contains components that are undefined or meaningless for a particular URN namespace or resource is not defined. The following sections describe these optional components and their interpretation in greater detail.

The r-component is intended for passing parameters to URN resolution services (taken broadly, see ) and interpreted by those services. (By contrast, passing parameters to the resources identified by a URN, or to applications that manage such resources, is handled by q-components as described in the next section.) The URN r-component has no syntactic counterpart in any other known URI scheme. The sequence "?+" introduces the r-component. The r-component ends with a "?=" sequence (which begins a q-component) or a "#" character (number sign, which begins an f-component). If neither of those appear, the r-component continues to the end of the URN. Note that characters outside the ASCII range MUST be percent-encoded using the method defined in Section 2.1 of the generic URI specification . As described under , the r-component SHALL NOT be taken into account when determining URN-equivalence. However, the r-component SHALL be supplied along with the URN when presenting a request to a URN resolution service. This document defines only the syntax of the r-component and reserves it for future use. The exact semantics of the r-component and its use in URN resolution protocols are a matter for potential standardization in separate specifications, presumably including specifications that define conventions and a registry for resolution service identifiers. Consider the hypothetical example of passing parameters to a resolution service (say, an ISO alpha-2 country code in order to select the preferred country in which to search for a physical copy of a book). This could perhaps be accomplished by specifying the country code in the r-component, resulting in URNs such as: urn:example:foo-bar-baz-qux?+CCResolve:cc=uk While the above should serve as a general explanation and illustration of the intent for r-components, there are many open issues with them, including their relationship to resolution mechanisms associated with the particular URN namespace at registration time. Thus r-components SHOULD NOT be used for actual URNs until additional development and standardization work is complete, including specification of any necessary registration mechanisms.

The q-component is intended for passing parameters to either the named resource or a system that can supply the requested service, for interpretation by that resource or system. (By contrast, passing parameters to URN resolution services is handled by r-components as described in the previous section.) The URN q-component has the same syntax as the URI query component, but is introduced by "?=", not "?" alone. For a URN that may be resolved to a URI that is a locator, the semantics of the q-component are identical to those for the query component of that URI. Thus URN resolvers returning a URI that is a locator for a URN with a q-component do this by copying the q-component from the URN to the query component of the URI. An example of the copying operation appears below. This specification does not specify a required behavior in the case of URN resolution to a URI that is a locator when the original URN has a q-component and the URI has a query string. Different circumstance may require different approaches. Resolvers SHOULD document their strategy in such cases. If the URN does not resolve to a URI that is a locator, the interpretation of the q-component is undefined by this specification. For URNs which may be resolved to a URI that is a locator, the semantics of the q-component are identical to those for queries to the resource located via that URI. For the sake of consistency with RFC 3986, the general syntax and the semantics of q-components are not defined by, or dependent on, the URN namespace of the URN. In parallel with RFC 3896, specifics of syntax and semantics, e.g., which keywords or terms are meaningful, of course may depend on a particular URN namespace or even a particular resource. The sequence "?=" introduces the q-component. The q-component terminates when a "#" character (number sign, which begins an f-component) appears. If that character does not appear, the q-component continues to the end of the URN. The characters slash ("/") and question mark ("?") may represent data within the q-component. Note that characters outside the ASCII range MUST be percent-encoded using the method defined in Section 2.1 of the generic URI specification . As described in , the q-component SHALL NOT be taken into account when determining URN-equivalence. URN namespaces and associated information placement in syntax SHOULD be designed to avoid any need for a resolution service to consider the q-component. Namespace-specific and more generic resolution systems MUST NOT require that q-component information be passed to them for processing. Consider the hypothetical example of passing parameters to an application that returns weather reports from different regions or for different time periods. This could perhaps be accomplished by specifying latitude and longitude coordinates and datetimes in the URN's q-component, resulting in URNs such as the following. &lon=-104.85&datetime=1969-07-21T02:56:15Z If this example resolved to an HTTP URI, the result might look like: &lon=-104.85&datetime=1969-07-21T02:56:15Z

The f-component is intended to be interpreted by the client as a specification for a location within, or region of, the named resource. It distinguishes the constituent parts of a resource named by a URN. For a URN that resolves to one or more locators which can be dereferenced to a representation, or where the URN resolver directly returns a representation of the resource, the semantics of an f-component are defined by the media type of the representation. The URN f-component has the same syntax as the URI fragment component. If a URN containing an f-component resolves to a single URI that is a locator associated with the named resource, the f-component from the URN can be applied (usually by the client) as the fragment of that URI. If the URN does not resolve to a URI that is a locator, the interpretation of the f-component is undefined by this specification. Thus, for URNs which may be resolved to a URI that is a locator, the semantics of f-components are identical to those of fragments for that resource. For the sake of consistency with RFC 3986, neither the general syntax nor the semantics of f-components are defined by, or dependent on, the URN namespace of the URN. In parallel with RFC 3896, specifics of syntax and semantics, e.g., which keywords or terms are meaningful, of course may depend on a particular URN namespace or even a particular resource. The f-component is introduced by the number sign ("#") character and terminated by the end of the URI. Any characters outside the ASCII range that appear in the f-component MUST be percent-encoded using the method defined in Section 2.1 of the generic URI specification . As described under , the f-component SHALL NOT be taken into account when determining URN-equivalence. Clients SHOULD NOT pass f-components to resolution services unless those services also perform object retrieval and interpretation functions. Consider the hypothetical example of obtaining resources that are part of a larger entity (say, the chapters of a book). Each part could be specified in the f-component, resulting in URNs such as: urn:example:foo-bar-baz-qux#somepart

For various purposes such as caching, it is often desirable to determine if two URNs are "the same". This is done most generally (i.e., independent of the scheme) by testing for equivalence (see Section 6.1 of ). The generic URI specification is very flexible about equality comparisons, putting the focus on allowing false negatives and avoiding false positives. If comparisons are made in a scheme-independent way, i.e., as URI comparisons only, many URNs that this specification considers equal would be rejected. The discussion below applies when the URIs involved are known to be URNs, and thus uses the terms "URN-equivalent" and "URN-equivalence" to refer to equivalence as specified in this document. Two URNs are URN-equivalent if their <assigned-name> portions are octet-by-octet equal after applying case normalization (as specified in Section 6.2.2.1 of ) to the following constructs: the URI scheme "urn", by conversion to lower case the NID, by conversion to lower case any percent-encoded characters in the NSS (that is, all character triplets that match the <pct-encoding> production found in Section 2.1 of the base URI specification ), by conversion to upper case for the digits A-F. Percent-encoded characters MUST NOT be decoded, i.e., percent-encoding normalization (as specified in Section 6.2.2.2 of ) MUST NOT be applied as part of the comparison process. If an r-component, q-component, or f-component (or any combination thereof) is included in a URN, it MUST be ignored for purposes of determining URN-equivalence. URN namespace definitions MAY include additional rules for URN-equivalence, such as case-insensitivity of the NSS (or parts thereof). Such rules MUST always have the effect of eliminating some of the false negatives obtained by the procedure above and MUST NOT result in treating two URNs as not "the same" if the procedure here says they are URN-equivalent. For related considerations with regard to NID registration, see below.

This section shows a variety of URNs (using the "example" NID defined in ) that highlight the URN-equivalence rules. First, because the scheme and NID are case-insensitive, the following three URNs are URN-equivalent to each other: urn:example:a123,z456 URN:example:a123,z456 urn:EXAMPLE:a123,z456 Second, because the r-component, q-component, and f-component are not taken into account for purposes of testing URN-equivalence, the following three URNs are URN-equivalent to the first three examples above: urn:example:a123,z456?+abc urn:example:a123,z456?=xyz urn:example:a123,z456#789 Third, because the "/" character (and anything that follows it) in the NSS is taken into account for purposes of URN-equivalence, the following URNs are not URN-equivalent to each other or to the six preceding URNs: urn:example:a123,z456/foo urn:example:a123,z456/bar urn:example:a123,z456/baz Fourth, because of percent-encoding, the following URNs are URN-equivalent only to each other and not to any of those above (note that, although %2C is the percent-encoded transformation of "," from the previous examples, such sequences are not decoded for purposes of testing URN-equivalence): urn:example:a123%2Cz456 URN:EXAMPLE:a123%2cz456 Fifth, because characters in the NSS other than percent-encoded sequences are treated in a case-sensitive manner (unless otherwise specified for the URN namespace in question), the following URNs are not URN-equivalent to the first three URNs: urn:example:A123,z456 urn:example:a123,Z456 Sixth, on casual visual inspection of a URN presented in a human-oriented interface the following URN might appear the same as the first three URNs (because U+0430 CYRILLIC SMALL LETTER A can be confused with U+0061 LATIN SMALL LETTER A), but it is not URN-equivalent to the first three URNs: urn:example:%D0%B0123,z456

Because a URN is, syntactically, a URI under the "urn" scheme, in theory a URN can be placed in any protocol slot that allows for a URI (to name just a few, the 'href' and 'src' attributes in HTML, the <base/> element in HTML, the 'xml:base' attribute in XML , and the 'xmlns' attribute in XML for XML namespace names ). However, this does not imply that, semantically, it always makes sense in practice to place a URN in a given URI protocol slot; in particular, because a URN might not specify the location of a resource or even point indirectly to one, it might not be appropriate to place a URN in a URI protocol slot that points to a resource (e.g., the aforementioned 'href' and 'src' attributes). Ultimately, guidelines regarding when it is appropriate to use URIs under the "urn" scheme (or any other scheme) are the responsibility of specifications for individual URI protocol slots (e.g., the specification for the 'xml:base' attribute in XML might recommend that it is inappropriate to use URNs in that protocol slot). This specification cannot possibly anticipate all of the relevant cases, and it is not the place of this specification to require or restrict usage for individual protocol slots.

In part because of the separation of URN semantics from more general URI syntax , generic URI processors need to pay special attention to the parsing and analysis rules of RFC 3986 and, in particular, must treat the URI as opaque unless the scheme and its requirements are recognized. In the latter case, such processors may be in a position to invoke scheme-appropriate processing, e.g., by a URN resolver. A URN resolver can either be an external resolver that the URI resolver knows of, or it can be functionality built into the URI resolver. Note that this requirement might impose constraints on the contexts in which URNs are appropriately used; see .

Section 5.2 of describes an algorithm for converting a URI reference that might be relative to a given base URI into "parsed components" of the target of that reference, which can then be recomposed per RFC 3986 Section 5.3 into a target URI. This algorithm is problematic for URNs because their syntax does not support the necessary path components. However, if the algorithm is applied independent of a particular scheme, it should work predictably for URNs as well, with the following understandings (syntax production terminology taken from RFC 3986): A system that encounters a <URI-reference> that obeys the syntax for <relative-ref>, whether it explicitly has the scheme "urn" or not, will convert it into a target URI as specified in RFC 3986. Because of the persistence and stability expectations of URNs, authors of documents, etc., that utilize URNs should generally avoid the use of the "urn" scheme in any <URI-reference> that is not strictly a <URI> as specified in RFC 3986, specifically including those that would require processing of <relative-ref>.

When URNs are transported and exchanged, they MUST be represented in the format defined herein. Further, all URN-aware applications MUST offer the option of displaying URNs in this canonical form to allow for direct transcription (for example by copy-and-paste techniques). Such applications might support display of URNs in a more human-friendly form and might use a character set that includes characters that are not permitted in URN syntax as defined in this specification (e.g., when displaying URNs to humans, such applications might replace percent-encoded strings with characters from an extended character repertoire such as Unicode ). To minimize user confusion, any application displaying URIs SHOULD display the complete URI (including, for URNs, the "urn" scheme and any components) to ensure that there is no confusion between URN NIDs and URI scheme identifiers. For example, a URI beginning with "urn:xmpp:" is very different from a URI beginning with "xmpp:" . Similarly, a potential DOI URI scheme is different from, and possibly completely unrelated to, a possible DOI URN namespace.

As mentioned, the assignment of URNs within a URN namespace is a managed process, as is the assignment of URN namespaces themselves. Although design of the URNs to be assigned within a given URN namespace is ceded by this specification to the URN namespace manager, doing so in a managed way avoids the problems inherent in unmanaged generation of URIs as described in the recommendations regarding URI design and ownership .

A URN namespace is a collection of names that obey three constraints: each name is (1) unique, (2) assigned in a consistent way, and (3) assigned according to a common definition. The "uniqueness" constraint means that a name within the URN namespace is never assigned to more than one resource and never reassigned to a different resource (for the kind of "resource" identified by URNs assigned within the URN namespace). This holds true even if the name itself is deprecated or becomes obsolete. The "consistent assignment" constraint means that a name within the URN namespace is assigned by an organization or created in accordance with a process or algorithm that is always followed. The "common definition" constraint means that there are clear definitions for the syntax of names within the URN namespace and for the process of assigning or creating them. A URN namespace is identified by a particular NID in order to ensure the global uniqueness of URNs and, optionally, to provide a cue regarding the structure of URNs assigned within a URN namespace. With regard to global uniqueness, using different NIDs for different collections of names ensures that no two URNs will be the same for different resources, because each collection is required to uniquely assign each name. However, a single resource MAY have more than one URN assigned to it, either in the same URN namespace (if the URN namespace permits it) or in different URN namespaces, and either for similar purposes or different purposes. (For example, if a publisher assigns an ISBN to an electronic publication and that publication is later incorporated into a digital long-term archive operated by a national library, the library might assign the publication an NBN , resulting in two URNs referring to the same book.) Subject to other constraints, such as those imposed by the URI syntax , the rules of the URN scheme are intended to allow preserving the normal and natural form of names specified in non-URN identifier systems when they are treated as URNs. With regard to the structure of names assigned within a URN namespace, the development of a naming structure (and thereby a collection of names) depends on the requirements of the community defining the names, how the names will be assigned and used, etc. These issues are beyond the scope of URN syntax and the general rules for URN namespaces, because they are specific to the community defining a non-URN identifier system or a particular URN namespace (e.g., the bibliographic and publishing communities in the case of the 'ISBN' URN namespace and the 'ISSN' URN namespace , or the developers of extensions to the Extensible Messaging and Presence Protocol in the case of the 'XMPP' URN namespace ). URN namespaces inherit certain rights and responsibilities by the nature of URNs, in particular: They uphold the general principles of a well-managed URN namespace by providing persistent identification of resources and unique assignment of names in accordance with a common definition. Optionally, they can be registered in global registration services such as those described in . There are two types of URN namespace: formal and informal. These are distinguished by the expected level of service, the information needed to define the URN namespace, and the procedures for registration. Because the majority of the URN namespaces registered so far have been formal, this document concentrates on formal URN namespaces.

A formal URN namespace provides benefit to some subset of users on the Internet. In particular, it would not make sense for a formal URN namespace to be used only by a community or network that is not connected to the Internet. For example, it would be inappropriate for a URN namespace to effectively force someone to use a proprietary network or service not open to the general Internet user. The intent is that, while the community of those who might actively use the URNs assigned within that URN namespace might be small, the potential use of names within that URN namespace is open to any user on the Internet. Formal URN namespaces might be appropriate even when some aspects are not fully open. For example, a URN namespace might make use of a fee-based, privately managed, or proprietary registry for assignment of URNs in the URN namespace. However, it might still benefit some Internet users if the associated services have openly-published names. An organization that will assign URNs within a formal URN namespace SHOULD meet the following criteria: Organizational stability and the ability to maintain the URN namespace for a long time; absent such evidence, it ought to be clear how the URN namespace can remain viable if the organization can no longer maintain the URN namespace. Competency in URN assignment. This will improve the likelihood of persistence (e.g., to minimize the likelihood of conflicts). Commitment to not reassigning existing URNs and to allowing old URNs to continue to be valid (e.g., if the assignee of a URN is no longer a member or customer of the assigning organization, if various information about the assignee or named entity happens to change, or even if the assignee or the named entity itself is no longer in existence; in all these cases, the URN is still valid). A formal URN namespace establishes a particular NID, subject to the following constraints (above and beyond the syntax rules already specified): It MUST NOT be an already-registered NID. It MUST NOT start with "urn-" (which is reserved for informal URN namespaces). It MUST be more than two characters long and it MUST NOT start with ALPHA ALPHA "-", i.e., any string consisting of two letters followed by one hyphen; such strings are reserved for potential use as NIDs based on ISO alpha-2 country codes for eventual national registrations of URN namespaces (however, the definition and scoping of rules for allocation of responsibility for such country-code-based URN namespaces are beyond the scope of this document). As a consequence, it MUST NOT start with the string "xn--" or any other string consisting of two letters followed by two hyphens; such strings are reserved for potential representation of DNS A-labels and similar strings in the future . It MUST NOT start with the string "X-" so that it will not be confused with or conflict any experimental URN namespace previously permitted by . Applicants and reviewers considering new NIDs should also be aware that they may have semantic implications and hence be a source of conflict. Particular attention should be paid to strings that might be construed as identifiers for, or registered under the authority of, countries (including ISO 3166-1 alpha-3 codes) and to strings that might imply association with existing URI schemes, non-URN identifier systems, or trademarks. However, in line with traditional policies, disputes about "ownership" of particular strings are disagreements among the parties involved; neither IANA nor the IETF will become involved in such disputes except in response to orders from a court of competent jurisdiction.

Informal URN namespaces are full-fledged URN namespaces, with all the associated rights and responsibilities. Informal URN namespaces differ from formal URN namespaces in the process for assigning a NID: for an informal URN namespace, the registrant does not designate the NID; instead, IANA assigns a NID consisting of the string 'urn-' followed by one or more digits (e.g., "urn-7") where the digits consist of the next available number in the sequence of positive integers assigned to informal URN namespaces. Thus the syntax of an informal URN namespace identifier is:

The only restrictions on <Number> are that it (1) consist strictly of ASCII digits, that it (2) not have leading zeros, and that it (3) not cause the NID to exceed the length limitations defined for the URN syntax (see ).

Because the space of URN namespaces is itself managed, the definition of a URN namespace SHOULD pay particular attention to: The purpose of the URN namespace. The syntax of URNs assigned within the URN namespace, including the internal syntax and anticipated effects of r-components or q-components. (The syntax and interpretation of f-components are defined in RFC 3986.) The process for assigning URNs within the URN namespace. The security implications of assigning URNs within the URN namespace and of using the assigned URNs. Any potential interoperability issues with URNs assigned within the URN namespace. Optionally, the process for resolving URNs issued within the URN namespace. The section on completing the template () explains these matters in greater detail. Although the registration templates are the same in all cases, slightly different procedures are used depending on the source of the registration.

The basic registration policy for URN namespaces is Expert Review as defined in the "IANA Considerations" document . For URN namespaces or their definitions that are intended to become standards or constituent parts of standards, the output of the Expert Review process is intended to be a report, rather than instructions to IANA to take action (see below). The key steps are: Fill out the URN namespace registration template (see and ). This can be done as part of an Internet-Draft or a specification in another series, although that is not a requirement. Send the completed template to the urn@ietf.org discussion list for review. If necessary to address comments received, repeat steps 1 and 2. If the designated experts approve the request and no standardization action is involved, the IANA will register the requested NID. If standardization is anticipated, the designated experts will prepare a report and forward it to the appropriate standards approval body (the IESG in the case of the IETF); IANA will register the requested NID only after receiving directions from that body and a copy of the expert review report. A URN namespace registration can be revised by updating the registration template, following the same steps outlined above for new registrations. A revised registration MUST describe differences from prior versions and SHOULD make special note of any relevant changes in the underlying technologies or URN namespace management processes. Experience to date with URN namespace registration requests has shown that registrants sometimes do not initially understand some of the subtleties of URN namespaces, and that defining the URN namespace in the form of a specification enables the registrants to clearly formulate their "contract" with the intended user community. Therefore, although the registration policy for formal URN namespaces is Expert Review and a specification (as distinct from the registration template) is not strictly required, registrants SHOULD provide a stable specification documenting the URN namespace definition and expanding upon the issues described herein. Because naming can be difficult and contentious, URN namespace registrants and the designated experts are strongly encouraged to work together in a spirit of good faith and mutual understanding to achieve rough consensus (see ) on handling registration requests. They are also encouraged to bring additional expertise into the discussion if that would be helpful in providing perspective or otherwise resolving issues. Especially when iterations in the registration process are prolonged, designated experts are expected to take reasonable precautions to avoid "race conditions" on proposed NIDs and, if such situations arise, to encourage applicants to work out any conflicts among themselves.

The IETF recognizes that situations will arise in which URN namespaces will be created to either embed existing and established standards, particularly identifier standards, or to reflect knowledge, terminology, or methods of organizing information that lie well outside the IETF's scope or the likely subject matter knowledge of its designated experts. In situations in which the registration request originates from, or is authorized by, a recognized standards-related organization, scientific society, or similar body, a somewhat different procedure is available at the option of that body: The URN namespace registration template is filled out and submitted as in steps 1 and 2 of . A specification is required that reflects or points to the needed external standards or specifications. Publication in the RFC Series or through an IETF process (e.g., posting as an Internet Draft) is not expected and would be appropriate only under very unusual circumstances. The reviews on the discussion list and by the designated experts are strictly advisory, with the decisions about what advice to accept and the length of time to allocate to the process strictly under the control of the external body. When that body concludes that the application is sufficiently mature, its representative(s) will request that IANA complete the registration for the NID, and IANA will do so. Decisions about whether to recognize the requesting entity as a standards-related organization, scientific society, or similar body are the responsibility of the IESG. A model similar to this has already been defined for recognized standards-related organizations that wish to register Media Types. The document describing that mechanism provides somewhat more information about the general approach.

A template for defining and registering a URN namespace is provided in . This section describes considerations for completing the template.

The "Purpose" section of the template describes matters such as: The kinds of resources identified by URNs assigned within the URN namespace. The scope and applicability of the URNs assigned within the URN namespace; this might include information about the community of use (e.g., a particular nation, industry, technology, or organization), whether the assigned URNs will be used on public networks or private networks, etc. How the intended community (and the Internet community at large) will benefit from using or resolving the assigned URNs. How the URN namespace relates to and complements existing URN namespaces, URI schemes, and non-URN identifier systems. The kinds of software applications that can use or resolve the assigned URNs (e.g., by differentiating among disparate URN namespaces, identifying resources in a persistent fashion, or meaningfully resolving and accessing services associated with the URN namespace). Whether resolution services are available or will be available (and, if so, the nature or identity of the services). Examples of q-component and (when they are standardized) r-component semantics and syntax are helpful here, even if detailed definitions are provided elsewhere or later. Whether the URN namespace or its definition is expected to become a constituent part of a standard being developed in the IETF or some other recognized standards body.

The "Syntax" section of the template contains: A description of the structure of URNs within the URN namespace, in conformance with the fundamental URN syntax. The structure might be described in terms of a formal definition (e.g., using Augmented BNF for Syntax Specifications (ABNF) ), an algorithm for generating conformant URNs, or a regular expression for parsing the name into consituent parts; alternatively, the structure might be opaque. Any special character encoding rules for assigned URNs (e.g., which character ought to always be used for quotes). Rules for determining URN-equivalence between two names in the URN namespace. Such rules ought to always have the effect of eliminating false negatives that might otherwise result from comparison. If it is appropriate and helpful, reference can be made to particular equivalence rules defined in the URI specification or to of this document. Examples of URN-equivalence rules include equivalence between uppercase and lowercase characters in the NSS, between hyphenated and non-hyphenated groupings in the name, or between single-quotes and double-quotes. There may also be namespace-specific special encoding considerations, especially for URNs that contain embedded forms of names from non-URN identifier systems. (Note that these are not normative statements for any kind of best practice related to handling of relationships between characters in general; such statements are limited to one particular URN namespace only.) Any special considerations necessary for conforming with the URN syntax. This is particularly applicable in the case of existing, non-URN identifier systems that are used in the context of URNs. For example, if a non-URN identifier system is used in contexts other than URNs, it might make use of characters that are reserved in the URN syntax. This section ought to note any such characters, and outline necessary mappings to conform to URN syntax. Normally, this will be handled by percent-encoding the character as specified in Section 2.1 of the URI specification and as discussed in of this specification. Any special considerations for the meaning of q-components (e.g., keywords) or f-components (e.g., predefined terms) in the context of this URN namespace.

The "Assignment" section of the template describes matters such as: Mechanisms or authorities for assigning URNs to resources. It ought to make clear whether assignment is completely open (e.g., following a particular procedure such as first-come, first-served (FCFS)), completely closed (e.g., for a private organization), or limited in various ways (e.g., delegated to authorities recognized by a particular organization); if limited, it ought to explain how to become an assigner of names or how to request assignment of names from existing assignment authorities. Methods for ensuring that URNs within the URN namespace are unique. For example, names might be assigned sequentially or in accordance with some well-defined process by a single authority, assignment might be partitioned among delegated authorities that are individually responsible for respecting uniqueness rules, or URNs might be created independently following an algorithm that itself guarantees uniqueness.

The "Security and Privacy" section of the template describes any potential issues related to security and privacy with regard to assignment, use, and resolution of names within the URN namespace. Examples of such issues include: The consequences of producing false negatives and false positives during comparison for URN-equivalence (see of this specification and "Issues in Identifier Comparison for Security Purposes" ). Leakage of private information when names are communicated on the public Internet. The potential for directory harvesting. Various issues discussed in the guidelines for security considerations in RFCs and the privacy considerations for Internet protocols .

The "Interoperability" section MUST specify any known potential issues related to interoperability. Examples include possible confusion with other URN namespaces, non-URN identifier systems, or URI schemes because of syntax (e.g., percent-encoding of certain characters) or scope (e.g., overlapping areas of interest). If at all possible, concerns that arise during the registration of a URN namespace (e.g., due to the syntax or scope of a non-URN identifier system) should be resolved as part of or in parallel to the registration process.

The "Resolution" section MUST specify whether resolution mechanisms are intended or anticipated for URNs assigned within the URN namespace. If resolution is intended, then this section SHOULD specify whether the organization that assigns URNs within the URN namespace intends to operate or recommend any resolution services for URNs within that URN namespace. In addition, if the assigning organization intends to implement registration for publicly advertised resolution services (for example using a system based on principles similar to those described in and ), then this section SHOULD list or reference the requirements for being publicly advertised by the assigning organization. In addition, this section SHOULD describe any special considerations for the handling of r-components in the context of this URN namespace.

The "Additional Information" section includes information that would be useful to those trying to understand this registration or its relationship to other registrations, such as comparisons to existing URN namespaces that might seem to overlap. This section of the template is optional.

This section updates the registration of the 'urn' URI scheme in the Permanent URI Registry . [Note to RFC Editor: please replace "[ &ThisDoc; ]" with "RFC" and the number assigned to this document upon publication.] urn permanent See of [ &ThisDoc; ]. The 'urn' scheme identifies Uniform Resource Names, which are persistent, location-independent resource identifiers. See of [ &ThisDoc; ]. Uniform Resource Names are used in a wide variety of applications, including bibliographic reference systems and as names for Extensible Markup Language (XML) namespaces. See of [ &ThisDoc; ]. See and of [ &ThisDoc; ]. URNBIS WG [mailto:urn@ietf.org] This scheme is registered under the IETF tree. As such, the IETF maintains change control. None.

This document outlines the processes for registering URN namespaces, and has implications for the IANA in terms of registries to be maintained (see especially ). In all cases, the IANA ought to assign the appropriate NID (formal or informal) once the procedures outlined in above have been completed.

The definition of a URN namespace needs to account for potential security and privacy issues related to assignment, use, and resolution of names within the URN namespace (e.g., some URN resolvers might assign special meaning to certain characters in the NSS); see for further discussion. In most cases, URN namespaces provide a way to declare public information. Normally, these declarations will have a relatively low security profile, however there is always the danger of "spoofing" and providing misinformation. Information in these declarations ought to be taken as advisory.

University California Los Angeles (UCLA) For concreteness, we suggest the use of standard 7-bit ASCII embedded in an 8 bit byte whose high order bit is always 0. Harvard University

1350 Mass. Ave. Cambridge MA 02138 - +1 617 495 3864 sob@harvard.edu

General keyword In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. Authors who follow these guidelines should incorporate this phrase near the beginning of their document: 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 RFC 2119. Note that the force of these words is modified by the requirement level of the document in which they are used. World Wide Web Consortium

Massachusetts Institute of Technology 77 Massachusetts Avenue Cambridge MA 02139 USA +1-617-253-5702 +1-617-258-5999 timbl@w3.org http://www.w3.org/People/Berners-Lee/

Day Software

5251 California Ave., Suite 110 Irvine CA 92617 USA +1-949-679-2960 +1-949-679-2972 fielding@gbiv.com http://roy.gbiv.com/

Adobe Systems Incorporated

345 Park Ave San Jose CA 95110 USA +1-408-536-3024 LMM@acm.org http://larry.masinter.net/

Applications uniform resource identifier URI URL URN WWW resource A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA).</t><t> In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA.</t><t> This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity with reasonable representational power. The differences between standard BNF and ABNF involve naming rules, repetition, alternatives, order-independence, and value ranges. This specification also supplies additional rule definitions and encoding for a core lexical analyzer of the type common to several Internet specifications. [STANDARDS-TRACK] Experience has shown that identifiers associated with persistent names have properties and requirements that may be somewhat different from identifiers associated with the locations of objects. This is especially true when such names are expected to be stable for a very long time or when they identify large and complex entities. In order to allow Uniform Resource Names (URNs) to evolve to meet the needs of the Library, Museum, Publisher, and Informational Sciences communities and other users, this specification separates URNs from the semantic constraints that many people believe are part of the specification for Uniform Resource Identifiers (URIs) specified in RFC 3986, updating that document accordingly. The syntax of URNs is still constrained to that of RFC 3986, so generic URI parsers are unaffected by this change. This document defines a Uniform Resource Name (URN) namespace for uniquely identifying information contained in registries maintained by the Internet Assigned Numbers Authority (IANA). ISO Technical Committee ISO/TC 46, Information and documentation, Subcommittee SC 9, Identification and description. IANA MIT Laboratory for Computer Science

545 Technology Square Cambridge MA 02139 US +1 617 253 2673 sollins@lcs.mit.edu

Xerox Palo Alto Research Center

3333 Coyote Hill Road Palo Alto CA 94304 US +1 415 812 4365 +1 415 812 4333 masinter@parc.xerox.com

This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet. [STANDARDS-TRACK] In situations where the base URL is well-defined and known to the parser (human or machine), it is useful to be able to embed URL references which inherit that context rather than re-specifying it in every instance. This document defines the syntax and semantics for such Relative Uniform Resource Locators. [STANDARDS-TRACK] AT&T

15621 Drexel Circle Omaha NE 68135-2358 USA +1 402 894-9456 jayhawk@ds.internic.net

Applications URN uniform resource Uniform Resource Names (URNs) are intended to serve as persistent, location-independent, resource identifiers. This document sets forward the canonical syntax for URNs. A discussion of both existing legacy and new namespaces and requirements for URN presentation and transmission are presented. Finally, there is a discussion of URN equivalence and how to determine it. MIT Laboratory for Computer Science

545 Technology Sq. Cambridge MA 02139 +1 617 253 6006 sollins@lcs.mit.edu

Applications security uniform resource This document addresses the issues of the discovery of URN (Uniform Resource Name) resolver services that in turn will directly translate URNs into URLs (Uniform Resource Locators) and URCs (Uniform Resource Characteristics). The document falls into three major parts, the assumptions underlying the work, the guidelines in order to be a viable Resolver Discovery Service or RDS, and a framework for designing RDSs. The guidelines fall into three principle areas: evolvability, usability, and security and privacy. An RDS that is compliant with the framework will not necessarily be compliant with the guidelines. Compliance with the guidelines will need to be validated separately. Network Solutions

505 Huntmar Park Drive Herndon VA 22070 USA +1 703 742 0400 +1 703 742 9552 michaelm@rwhois.net

Los Alamos National Laboratory, ,Advanced Computing Lab

MS B287 Los Alamos NM 87545 USA +1 505 665 0597 +1 505 665 4939 rdaniel@lanl.gov

Applications uniform resource identifier URI Retrieving the resource identified by a Uniform Resource Identifier (URI) is only one of the operations that can be performed on a URI. One might also ask for and get a list of other identifiers that are aliases for the original URI or a bibliographic description of the resource the URI denotes, for example. This applies to both Uniform Resource Names (URNs) and Uniform Resource Locators (URLs). Uniform Resource Characteristics (URCs) are discussed in this document but only as descriptions of resources rather than identifiers. A service in the network providing access to a resource may provide one or some of these options, but it need not provide all of them. This memo specifies an initial set of these operations that can be used to describe the interactions provided by a given access service. It also suggests guidelines that should be adhered to when those operations are encoded in a protocol. &rfc2648; This document presents how the ISSN - International Standard Serial Number - which is a persistent number for unique identification of serials widely recognised and used in the bibliographic world, can be supported within the Uniform Resource Name (URN) framework as a specific URN namespace identifier. This memo provides information for the Internet community. This document discusses how International Standard Book Numbers (ISBN) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion below is based on the ideas expressed in RFC 2288. This memo provides information for the Internet community. This document discusses how national bibliography numbers (persistent and unique identifiers assigned by the national libraries) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion is based on the ideas expressed in RFC 2288. This memo provides information for the Internet community. This document lays out general definitions of and mechanisms for establishing Uniform Resource Names (URN) "namespaces". The URN WG has defined a syntax for URNs in RFC 2141, as well as some proposed mechanisms for their resolution and use in Internet applications in RFC 3401 and RFC 3405. 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 in RFC 2288. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. XMPP Standards Foundation

P.O. Box 1641 Denver CO 80201 USA stpeter@jabber.org xmpp:stpeter@jabber.org

Applications Extensible Messaging and Presence Protocol XMPP Jabber Instant Messaging Presence Uniform Resource Name URN This document describes a Uniform Resource Name (URN) namespace for uniquely identifying Extensible Markup Language (XML) formats and protocols that provide extensions to the Extensible Messaging and Presence Protocol (XMPP) and are defined in specifications published by the XMPP Standards Foundation (XSF). This document defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP). [STANDARDS-TRACK] This document is one of a collection that, together, describe the protocol and usage context for a revision of Internationalized Domain Names for Applications (IDNA), superseding the earlier version. It describes the document collection and provides definitions and other material that are common to the set. [STANDARDS-TRACK] The Extensible Messaging and Presence Protocol (XMPP) is an application profile of the Extensible Markup Language (XML) that enables the near-real-time exchange of structured yet extensible data between any two or more network entities. This document defines XMPP's core protocol methods: setup and teardown of XML streams, channel encryption, authentication, error handling, and communication primitives for messaging, network availability ("presence"), and request-response interactions. This document obsoletes RFC 3920. [STANDARDS-TRACK] This document describes the Namespace Identifier (NID) for Uniform Resource Name (URN) Namespace resources published by the Defence Geospatial Information Working Group (DGIWG). The DGIWG defines and manages resources that utilize this URN name model.Management activities for these and other resource types are provided by the DGIWG Registry System (DRS). This document is not an Internet Standards Track specification; it is published for informational purposes. Historically, designers and implementers of application protocols have often distinguished between standardized and unstandardized parameters by prefixing the names of unstandardized parameters with the string "X-" or similar constructs. In practice, that convention causes more problems than it solves. Therefore, this document deprecates the convention for newly defined parameters with textual (as opposed to numerical) names in application protocols. This memo documents an Internet Best Current Practice. This document defines procedures for the specification and registration of media types for use in HTTP, MIME, and other Internet protocols. This memo documents an Internet Best Current Practice. Identifiers such as hostnames, URIs, IP addresses, and email addresses are often used in security contexts to identify security principals and resources. In such contexts, an identifier presented via some protocol is often compared using some policy to make security decisions such as whether the security principal may access the resource, what level of authentication or encryption is required, etc. If the parties involved in a security decision use different algorithms to compare identifiers, then failure scenarios ranging from denial of service to elevation of privilege can result. This document provides a discussion of these issues that designers should consider when defining identifiers and protocols, and when constructing architectures that use multiple protocols. This document defines a Uniform Resource Name (URN) namespace identifier enabling the generation of URNs that are appropriate for use in documentation and in URN-related testing and experimentation. This document offers guidance for developing privacy considerations for inclusion in protocol specifications. It aims to make designers, implementers, and users of Internet protocols aware of privacy-related design choices. It suggests that whether any individual RFC warrants a specific privacy considerations section will depend on the document's content. The IETF has had a long tradition of doing its technical work through a consensus process, taking into account the different views among IETF participants and coming to (at least rough) consensus on technical matters. In particular, the IETF is supposed not to be run by a "majority rule" philosophy. This is why we engage in rituals like "humming" instead of voting. However, more and more of our actions are now indistinguishable from voting, and quite often we are letting the majority win the day without consideration of minority concerns. This document explains some features of rough consensus, what is not rough consensus, how we have gotten away from it, how we might think about it differently, and the things we can do in order to really achieve rough consensus.</t><t> Note: This document is quite consciously being put forward as Informational. It does not propose to change any IETF processes and is therefore not a BCP. It is simply a collection of principles, hopefully around which the IETF can come to (at least rough) consensus. Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme." In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of URI substructure is inappropriate, because that essentially usurps ownership. This document further describes this problematic practice and provides some acceptable alternatives for use in standards. The Session Initiation Protocol (SIP) supports the capability to provide a reference to a specific rendering to be used by the User Agent (UA) as an alerting signal (e.g., a ring tone or ringback tone) when the user is alerted. This is done using the Alert-Info header field. However, the reference (typically a URL) addresses only a specific network resource with specific rendering properties. There is currently no support for standard identifiers for describing the semantics of the alerting situation or the characteristics of the alerting signal, without being tied to a particular rendering. To overcome these limitations and support new applications, a new family of URNs for use in Alert-Info header fields (and situations with similar requirements) is defined in this specification.This document normatively updates RFC 3261, which defines the Session Initiation Protocol (SIP). It changes the usage of the Alert-Info header field defined in RFC 3261 by additionally allowing its use in any non-100 provisional response to INVITE. This document also permits proxies to add or remove an Alert-Info header field and to add or remove Alert-Info header field values. &rfc7613; The Unicode Consortium The Unicode Consortium

Requested of IANA (formal) or assigned by IANA (informal). The version of the registration, starting with 1 and incrementing by 1 with each new version. The date when the registration is requested of IANA, using the format YYYY-MM-DD. The person or organization that has registered the NID, including the name and address of the registering organization, as well as the name and contact information (email, phone number, or postal address) of the designated contact person. If the registrant is a recognized standards development organization, scientific society, or similar body requesting the fast track registration procedure (see ), that information should be clearly indicated in this section of the template. Described under of this document. Described under of this document. Unless the registration explicitly describes the semantics of r-components, q-components, and f-components in the context of this URN namespace, those semantics are undefined. Described under of this document. Described under of this document. Described under of this document. Described under of this document. A pointer to an RFC, a specification published by another standards development organization, or another stable document that provides further information about this URN namespace. Described under of this document. Description of changes from prior version(s). (Applicable only when earlier registrations have been revised.)

This document makes substantive changes from the syntax and semantics of :

The syntax of URNs as provided in was defined before the updated specification of URIs in . The definition of URN syntax is updated in this document to do the following: Ensure consistency with the URI syntax. Facilitate the use of URNs with parameters similar to URI queries and fragments. Permit parameters influencing URN resolution. Ease the use of URNs with non-URN identifier systems that include the '/' character. In particular, this specification does the following: Extends URN syntax to explicitly allow the characters '/', "?", and "#", which were reserved for future use by RFC 2141. This change effectively also allows several components of the URI syntax although without necessarily tying those components to URI semantics. Defines general syntax for an additional component that can be used in interactions with a URN resolution service. Disallows "-" at the end of a NID. Allows the "/", "~", and "&" characters in the namespace-specific string (NSS). Makes several smaller syntax adjustments.

Formally registers 'urn' as a URI scheme. Allows what are now called r-components, q-components, and f-components. In addition, some of the text has been updated to be consistent with the definition of Uniform Resource Identifiers (URIs) and the processes for registering information with the IANA , as well as more modern guidance with regard to security , privacy , and identifier comparison .

This document makes the following substantive changes from : Relaxes the registration policy for formal URN namespaces from "IETF Review" to "Expert Review" as discussed in . Removes the category of experimental URN namespaces, consistent with . Experimental URN namespaces were denoted by prefixing the namespace identifier with the string "X-". Because experimental URN namespaces were never registered, removing the experimental category has no impact on the existing registries. Because experimental URN namespaces are not managed, strings conforming to URN syntax within experimental URN namespaces are not valid URNs. Truly experimental usages MAY, of course, employ the 'example' namespace . Adds some information to, but generally simplifies, the URN namespace registration template.

RFC 2141, which provided the basis for the syntax portion of this document, was authored by Ryan Moats. RFC 3406, which provided the basis for the namespace portion of this document, was authored by Leslie Daigle, Dirk-Willem van Gulik, Renato Iannella, and Patrik Faltstrom. Their work is gratefully acknowledged.

Many thanks to Marc Blanchet, Leslie Daigle, Martin Duerst, Juha Hakala, Ted Hardie, Alfred Hoenes, Paul Jones, Barry Leiba, Sean Leonard, Larry Masinter, Keith Moore, Mark Nottingham, Julian Reschke, Lars Svensson, Henry S. Thompson, Dale Worley, and other participants in the URNBIS WG for their input. Alfred Hoenes in particular edited an earlier version of this document and served as co-chair of the URNBIS WG. Juha Hakala deserves special recognition for his dedication to successfully completing this work, as do Andrew Newton and Melinda Shore in their roles as working group co-chairs and Barry Leiba in his role as area director and then as co-chair.

[[RFC Editor: please remove this appendix before publication.]]

Altered the text in to reflect list discussions about the earlier phrasing. Also added DOI example and citation to that section. Clarified the naming rules for formal namespaces and their relationship to ISO 3166, IDNA, etc., reserved strings. Added an explicit statement about use of URNs in various protocols and contexts to . Clarified that experimental namespace NIDs, which were explicitly not registered, are not valid URNs (in . Transformed the partial production in into valid ABNF. Added more text about p-/q-/f-components and recommendations about use. Added clarifying note about "?" within q-components and f-components. Added explicit requirement that revisions of existing registrations document the changes and added a slot for that description to the template. Many small editorial changes and adjustments including adding additional references and cross-references for clarification. Inserted a placeholder for additional examples.

Several clarifying editorial changes, most suggested by Ted Hardie and Henry S. Thompson (some of them off-list). Added a large number of placeholders that identify issues that require WG consideration and resolution (or WG delegation to the editors).

Removed most of the placeholders added in -10. Supplied new text as required or suggested by on-list discussion of those issues. Replaced the conformance examples with a more complete collection and discussion. Revised and consolidated the registration procedure, and added provisions for NIDs that are the subject of standards and for avoiding race conditions about NID strings. In response to independent comments from Ted Hardie and Henry S. Thompson, called attention to the possibility of conflicts between NID strings and various claims of national, corporate, and other perogatives. Changed the production for assigned-name as suggested by Lars Svensson. Several clarifying editorial changes including correcting a glitch in instructions to the RFC Editor.

Removed p-components as a standalone construct, and instead folded them into the NSS. Defined syntax for r-components as a way to pass information to resolvers, but left the semantics for future standardization efforts. Further tuned the discussion of interoperability and related registration issues. Made a number of editorial corrections and reorganized the syntax material in somewhat to make it internally consistent and keep the relationship to RFC 3986 clear.

More precisely defined the semantics of the optional components. Defined the term "resolution" and clarified several related matters throughout the text. Clarified terminological relationship to RFC 3986. Further cleansed the document of p-components. Corrected several examples to avoid confusion with existing identifier systems. Improved text regarding the purpose of namespaces being registered.

Reverted the ABNF to what had been defined in version -12. Added fast-track approval process for standards-related organizations, scientific societies, and similar bodies (similar to RFC 6838 for Media Types).

Reorganized the Introduction slightly, adding new subsection 1.1 and making Terminology (the former Section 2) Section 1.2. Tightened the discussion of "resolution" somewhat to try to mitigate some on-list confusion. Added some text about character set choices and repertoires (consistent with the Section 1.1 explanation). Moved away from "?" and "??" for q-component and r-component delimiters and went to two-character sequences for each. This includes several changes to the text to remove or modify discussions of string termination and the role of a question mark not followed by one of the new delimiters. Redefined r-component to be an ASCII resolver ID and a string. Neither is further defined in this specification and text has been added to say that. Several editorial changes to improve clarity, most following up on comments made on the list. These included modifying the table of contents so that the subsections on optional components now appear there.

Rewrote the introductory material to make the relationship to other specifications more clear and allow removing or altering text that was stated in terms of changes from 2141. The specification is now self-contained with regard to the earlier definitions and descriptions of URNs. Removed the parts of Section 2 that were really a description of changes from RFC 2141 to Appendix B, where such changes are enumerated. Similarly, removed most material describing changes from RFC 3406 to Appendix C. Replaced one example. Rearranged and rewrote text to improve clarity and relationships to other documents and to reduce redundant material. Made it more clear that r-components, despite the partial syntax specification, are reserved for future standardization. Clarified that there can be URNs that do not resolve to URLs. Added pointers to make it clear that the Syntax material in is not self-contained, e.g., that its subsections and other sections further restrict strings that can be used for NIDs and so on. Added an "Additional Information" section to the registration template. See list discussion on and about 2016-03-18. Minor editorial/ typographic fixes (per comment from Lars).

Clarified material about copying q-components, including adding an example. Modified the document in several places to try to respond to concerns about the unqualified use of the term "equivalence". The term has been eliminated in one or two places and changed to "URN-equivalence" in situations in which the scheme is known and URN-specific rules are being applied. Editorial and typographic fixes. Temporarily (this version only) added [[CREF...]] placeholders to identify outstanding issues that might usefully be discussed during the 2016-06-29 virtual meeting but that must be resolved in some way for the document to move forward.

Removed "cref placeholders" inserted for -17 and the 2016-06-29 virtual meeting. Per interim meeting 2016-06-29, changed "equivalent" and "equivalence" to "URN-equivalent" and "URN-equivalence" in a number of locations. Per interim meeting 2016-06-29 and previous list discussion, clarified the usage of the terms 'name', 'namespace', 'URN namespace', 'identifier system', 'URN', and 'NSS'. Per interim meeting 2016-06-29, changed syntax so that r-component precedes q-component.

Small editorial changes to improve clarity. Added cross-references to material, especially in Section 6 and as derived from RFC 3406. Replaced material on relative references to reflect the on-list discussions in August and September and generally to say less here and leave more to RFC 3986. Expanded the discussion of resolution, dereferencing, representations, metadata, and intended uses for URNs. Removed the term "abstract designator". Replaced the term "URL" in most instances with the term "locator" or the phrase "URI that is a locator". Rearranged and partially rewrote the "Terminology" section to reflect the above change to "URL" usage, reflect the actual use of the term "URN" in the document, and be clear about the meaning (or lack thereof) of "name".