File formats:

Status:

BEST CURRENT PRACTICE

Obsoleted by:

RFC 8820

Updates:

RFC 3986

Author:

M. Nottingham

Stream:

IETF

Source:

appsawg (app)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC7320

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

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

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 URI substructure is inappropriate, because that essentially usurps ownership. This document further describes this problematic practice and provides some acceptable alternatives for use in standards.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.