Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Uniform Resource Names (URN) Namespace Definition Mechanisms (RFC3406)

IP.com Disclosure Number: IPCOM000010081D
Original Publication Date: 2002-Oct-01
Included in the Prior Art Database: 2002-Oct-17
Document File: 23 page(s) / 44K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

L. Daigle: AUTHOR [+4]

Abstract

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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Network Working Group� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � L. Daigle

Request for Comments: 3406� � � � � � � � � � � � � � � � � � � � � Thinking Cat Enterprises

BCP: 66� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � D.W. van Gulik

Obsoletes: 2611� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � WebWeaving

Category: Best Current Practice� � � � � � � � � � � � � � � � � � � � � � � � � � � � � R. Iannella

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � IPR Systems

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � P. Faltstrom

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � Cisco

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � October 2002

� � � � � Uniform Resource Names (URN) Namespace Definition Mechanisms

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 (2002).� All Rights Reserved.

Abstract

� � 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.

Table of Contents

� � 1.0 Introduction ................................................. 2

� � 2.0 What is a URN Namespace? ..................................... 3

� � 3.0 URN Namespace (Registration) Types ........................... 3

� � 3.1 Experimental Namespaces .....................................� 4

� � 3.2 Informal Namespaces .........................................� 4

� � 3.3 Formal Namespaces ...........................................� 4

� � 4.0 URN Namespace Registration, Update, and NID Assignment

� � � � � � Process .....................................................� 6

� � 4.1 Experimental ................................................� 6

� � 4.2 Informal ....................................................� 6

� � 4.3 Formal ......................................................� 7

� � 5.0 Security Considerations .....................................� 9

Daigle, et. al.� � � � � � � � � Best Current Practice� � � � � � � � � � � � � � � � � [Page 1]

RFC 3406� � � � � � � � �...