Browse Prior Art Database

A Uniform Resource Name (URN) Namespace for Examples (RFC6963)

IP.com Disclosure Number: IPCOM000227893D
Publication Date: 2013-May-25
Document File: 14 page(s) / 12K

Publishing Venue

The IP.com Prior Art Database

Related People

P. Saint-Andre: AUTHOR

Abstract

The Uniform Resource Name (URN) technology [RFC2141] provides a way to generate persistent, location-independent resource identifiers. The primary "scope" of a URN is provided by its namespace identifier (NID). As specified in [RFC3406], there are three kinds of NIDs: formal, informal, and experimental. Most of the NIDs registered to date are formal. As far as is known, the few informal namespaces have not been widely used, and the experimental namespaces are by definition unregistered.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 23% of the total text.

Internet Engineering Task Force (IETF)                    P. Saint-Andre Request for Comments: 6963                           Cisco Systems, Inc. BCP: 183                                                        May 2013 Category: Best Current Practice ISSN: 2070-1721

           A Uniform Resource Name (URN) Namespace for Examples

Abstract

   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.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    BCPs is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6963.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Saint-Andre               Best Current Practice                 [Page 1]
 RFC 6963                      Example URNs                      May 2013

 Table of Contents

   1. Introduction ....................................................2    2. Terminology .....................................................2    3. Completed Namespace Definition Template .........................3    4. Namespace Considerations ........................................4    5. Community Considerations ........................................5    6. Security Considerations .........................................5    7. IANA Considerations .............................................5    8. References ......................................................6    Appendix A. Acknowledgements .......................................7

1.  Introduction

   The Uniform Resource Name (URN) technology [RFC2141] pr...