BCP 190

RFC 8820

URI Design and Ownership, June 2020

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Status:
BEST CURRENT PRACTICE
Obsoletes:
RFC 7320
Updates:
RFC 3986
Author:
M. Nottingham
Stream:
IETF
Source:
NON WORKING GROUP

Cite this BCP: TXT  |  XML

Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC


Abstract

Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme." In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of substructure in URIs is often problematic.

This document provides guidance on the specification of URI substructure in standards.

This document obsoletes RFC 7320 and updates RFC 3986.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search