Browse Prior Art Database

An IETF URN Sub-namespace for Registered Protocol Parameters (RFC3553)

IP.com Disclosure Number: IPCOM000016526D
Original Publication Date: 2003-Jun-01
Included in the Prior Art Database: 2003-Jun-27
Document File: 9 page(s) / 15K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Mealling: AUTHOR [+4]

Abstract

This document describes a new sub-delegation for the 'ietf' URN namespace for registered protocol items. The 'ietf' URN namespace is defined in RFC 2648 as a root for persistent URIs that refer to IETF-defined resources.

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

Network Working Group                                        M. Mealling

Request for Comments: 3553                                      VeriSign

BCP: 73                                                      L. Masinter

Category: Best Current Practice                            Adobe Systems

                                                               T. Hardie

                                                                Qualcomm

                                                                G. Klyne

                                                            Nine by Nine

                                                               June 2003

      An IETF URN Sub-namespace for Registered Protocol Parameters

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

Abstract

   This document describes a new sub-delegation for the 'ietf' URN

   namespace for registered protocol items.  The 'ietf' URN namespace is

   defined in RFC 2648 as a root for persistent URIs that refer to

   IETF-defined resources.

1.  Introduction

   From time to time IETF standards require the registration of various

   protocol elements in well known central repository.  The Internet

   Assigned Numbers Authority maintains this central repository and

   takes direction from the IETF on what, how and when to add items to

   it.  The IANA maintains lists of items such as all assigned port

   numbers, MIME media types, enterprise numbers, etc.

   Over time there has developed a need to be able to reference these

   elements as URIs in various schema.  In the past this was done in a

   very ad hoc way that easily led to interoperability problems.  This

   document creates a new sub-delegation below the "ietf" [2]URN

   namespace [1] called 'params' which acts as a standardized mechanism

   for naming the items registered for IETF standards.  Any assignments

   below that are specified in an RFC according to the IETF consensus

   process and which include the template found in Section 4.

Mealling, et. al.        Best Current Practice                  [Page 1]

RFC 3553                   IANA URN Namespace                  June 2003

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"...