RFC 7595: Guidelines and Registration Procedures for URI Schemes
In plain English — editorial summary, not part of the RFC
This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes. It obsoletes RFC 4395.
Document record
- Document ID
- RFC7595
- Published
- June 2015
- Authors
- D. Thaler; T. Hansen; T. Hardie
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- art
- Pages
- 19
- Also known as
- BCP35
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 6570URI TemplateCurrent
March 2012
- RFC 5122Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)Current
February 2008
- RFC 4622Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)Obsoleted
August 2006
- RFC 6068The 'mailto' URI SchemeCurrent
October 2010
- RFC 7565The 'acct' URI SchemeCurrent
May 2015
- RFC 8089The "file" URI SchemeUpdated
February 2017
- RFC 8124The Session Description Protocol (SDP) WebSocket Connection URI AttributeCurrent
March 2017
- RFC 8141Uniform Resource Names (URNs)Current
April 2017
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?