RFC 6963: A Uniform Resource Name (URN) Namespace for Examples
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6963
- Published
- May 2013
- Authors
- P. Saint-Andre
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- BCP183
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7163URN for Country-Specific Emergency ServicesCurrent
March 2014
- RFC 6755An IETF URN Sub-Namespace for OAuthCurrent
October 2012
- RFC 7302Entertainment Identifier Registry (EIDR) URN Namespace DefinitionObsoleted
July 2014
- RFC 8057Uniform Resource Name (URN) Namespaces for Broadband ForumCurrent
January 2017
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
- RFC 8631Link Relation Types for Web ServicesCurrent
July 2019
- RFC 5174A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)Current
May 2008
- RFC 5165A Uniform Resource Name (URN) Namespace for the Open Geospatial Consortium (OGC)Current
April 2008
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?