Browse Prior Art Database

Registration Procedures for URL Scheme Names (RFC2717) Disclosure Number: IPCOM000003312D
Original Publication Date: 1999-Nov-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 8 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Petke: AUTHOR [+1]


This document defines the process by which new URL scheme names are registered.

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 15% of the total text.

Network Working Group R. Petke

Request for Comments: 2717 UUNET Technologies

BCP: 35 I. King

Category: Best Current Practice Microsoft Corporation

November 1999

Registration Procedures for URL Scheme Names

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


This document defines the process by which new URL scheme names are


1.0 Introduction

A Uniform Resource Locator (URL) is a compact string representation

of the location for a resource that is available via the Internet.

RFC 2396 [1] defines the general syntax and semantics of URIs, and,

by inclusion, URLs. URLs are designated by including a ":"

and then a "". Many URL schemes are already

defined, however, new schemes may need to be defined in the future in

order to accommodate new Internet protocols and/or procedures.

A registration process is needed to ensure that the names of all such

new schemes are guaranteed not to collide. Further, the registration

process ensures that URL schemes intended for wide spread, public use

are developed in an orderly, well-specified, and public manner.

This document defines the registration procedures to be followed when

new URL schemes are created. A separate document, RFC 2718,

Guidelines for URL Schemes [2], provides guidelines for the creation

of new URL schemes. The primary focus of this document is on the

portion of new URL schemes, referred to as the "scheme name"

throughout this document.

1.1 Notation

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


document are to be interpreted as described in RFC 2119.

2.0 URL Scheme Name Registration Trees

2.1 General

In order to increase the efficiency and flexibility of the URL scheme

name registration process, the need is recognized for multiple

registration "trees". The registration requirements and specific

registration procedures for each tree differ, allowing the overall

registration procedure to accommodate the different natural

requirements for URL schemes. For example, a scheme that will be

recommended for wide ...