RFC 2718: Guidelines for new URL Schemes
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4395.
Current document in this lineage: RFC 7595 — Guidelines and Registration Procedures for URI Schemes
In plain English — editorial summary, not part of the RFC
This document provides guidelines for the definition of new URL schemes. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2718
- Published
- November 1999
- Authors
- L. Masinter; H. Alvestrand; D. Zigmond; R. Petke
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- app
- Pages
- 10
- Also known as
- —
- Obsoleted by:
- RFC 4395
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2717 (1999)
- RFC 2718 (1999)
- RFC 4395 (2006)
- RFC 7595 (2015) ✓
Read the full history of Guidelines and Registration Procedures for URI Schemes →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2717Registration Procedures for URL Scheme NamesObsoleted
November 1999
- RFC 2611URN Namespace Definition MechanismsObsoleted
June 1999
- RFC 1959An LDAP URL FormatObsoleted
June 1996
- RFC 2703Protocol-independent Content Negotiation FrameworkCurrent
September 1999
- RFC 2648A URN Namespace for IETF DocumentsUpdated
August 1999
- RFC 2806URLs for Telephone CallsObsoleted
April 2000
- RFC 2296HTTP Remote Variant Selection Algorithm -- RVSA/1.0Current
March 1998
- RFC 2276Architectural Principles of Uniform Resource Name ResolutionUpdated
January 1998
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?