Uniform Resource Identifier (URI): Generic Syntax
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 61
- Abstract
- A Uniform Resource Identifier (URI) is a compact sequence of characters that identifies an abstract or physical resource. This specification defines the generic URI syntax and a process for resolving URI references that might be in relative form, along with guidelines and security considerations for the use of URIs on the Internet. The URI syntax defines a grammar that is a superset of all valid URIs, allowing an implementation to parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier. This specification does not define a generative grammar for URIs; that task is performed by the individual specifications of each URI scheme. [STANDARDS-TRACK]
- Publication Date
- 2005-01-01
- Status Note
- Internet Standard
- DOI
10.17487/RFC3986- Link
- https://doi.org/10.17487/RFC3986
- Author(s)
- Tim Berners-LeeRoy T. FieldingLarry M Masinter
- Keyword(s)
- IP, Uniform Resource Identifier, URI, World Wide Web
Latest version of IETF RFC 3986
Document Versions — IETF RFC 3986
-
▶ IETF RFC 3986 (2005-01-01)THIS DOC [ACTIVE] [AMENDED] [LATEST VERSION]
Normative Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- ISO 10646:2003 [Withdrawn]
- IETF RFC 2234 [Superseded*]
- IETF RFC 3629 [Active*]
Bibliographic Reference(s)
- Siedzik, R., "Semantic Attacks: What's in a URL?", April 2001, < http://www.giac.org/practical/gsec/ Richard_Siedzik_GSEC.pdf >. EXTERNAL
- IETF RFC 952 [Active*]
- IETF RFC 1034 [Active*]
- IETF RFC 1123 [Active*]
- IETF RFC 1535 [Active*]
- IETF RFC 1630 [Active*]
- IETF RFC 1736 [Active*]
- IETF RFC 1737 [Active*]
- IETF RFC 1738 [Superseded*]
- IETF RFC 1808 [Superseded*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2141 [Superseded*]
- IETF RFC 2396 [Superseded*]
- IETF RFC 2518 [Superseded*]
- IETF RFC 2557 [Active*]
- IETF RFC 2717 [Superseded*]
- IETF RFC 2718 [Superseded*]
- IETF RFC 2732 [Superseded*]
- IETF RFC 2978 [Active*]
- IETF RFC 3305 [Active*]
- IETF RFC 3490 [Superseded*]
- IETF RFC 3513 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3986.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax. Available at https://doi.org/10.17487/RFC3986
Snippet:
IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax. Available at https://doi.org/10.17487/RFC3986
HTML (ISO 690 compliant)
Preview:
IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax. Available at https://doi.org/10.17487/RFC3986
Snippet:
<span class="citation"><cite>IETF RFC 3986</cite>, Uniform Resource Identifier (URI): Generic Syntax. Available at <a href="https://doi.org/10.17487/RFC3986" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3986</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3986, Uniform Resource Identifier (URI): Generic Syntax
doi: 10.17487/RFC3986
url: https://doi.org/10.17487/RFC3986
doi: 10.17487/RFC3986
url: https://doi.org/10.17487/RFC3986
Snippet:
<li> <cite id="bib-rfc3986">IETF RFC 3986</cite>, Uniform Resource Identifier (URI): Generic Syntax <span class="doi">10.17487/RFC3986</span> </li>
Referenced By
- Workflow as a Service Delivered by the Dynamic Media Services Architecture [Active]
- Configuring Versatile Video Coding: Technical Guidelines for Broadcast and Streaming Applications [Active]
- IETF draft-bhutton-json-schema-00 [Draft*]
- IETF draft-bhutton-json-schema-01 [Active*]
- IETF draft-bhutton-json-schema-validation-00 [Active*]
- IETF draft-bhutton-json-schema-validation-01 [Active*]
- IETF draft-clemm-netmod-mount-06.txt [Active*]
- IETF draft-handrews-json-schema-hyperschema-02 [Active*]
- IETF draft-ietf-core-object-security-08 [Active*]
- IETF draft-silverajan-core-coap-alternative-transports-10 [Active*]
- IETF draft-thaler-appsawg-multi-transport-uris-01 [Active*]
- IETF RFC 3987 [Active*]
- IETF RFC 4007 [Active*]
- IETF RFC 4133 [Superseded*]
- IETF RFC 4151 [Active*]
- IETF RFC 4158 [Active*]
- IETF RFC 4227 [Active*]
- IETF RFC 4240 [Active*]
- IETF RFC 4287 [Active*]
- IETF RFC 4288 [Superseded*]
- IETF RFC 4325 [Superseded*]
- IETF RFC 4329 [Superseded*]
- IETF RFC 4353 [Active*]
- IETF RFC 4366 [Superseded*]
- IETF RFC 4395 [Superseded*]
- IETF RFC 4408 [Superseded*]
- IETF RFC 4452 [Active*]
- IETF RFC 4511 [Active*]
- IETF RFC 4516 [Active*]
- IETF RFC 4566 [Superseded*]
- IETF RFC 4567 [Active*]
- IETF RFC 4648 [Active*]
- IETF RFC 4690 [Active*]
- IETF RFC 4741 [Superseded*]
- IETF RFC 4790 [Active*]
- IETF RFC 4825 [Active*]
- IETF RFC 4918 [Active*]
- IETF RFC 4975 [Active*]
- IETF RFC 4992 [Active*]
- IETF RFC 5017 [Active*]
- IETF RFC 5023 [Active*]
- IETF RFC 5122 [Active*]
- IETF RFC 5147 [Active*]
- IETF RFC 5280 [Active, Amended*]
- IETF RFC 5456 [Active*]
- IETF RFC 5545 [Active*]
- IETF RFC 5592 [Active*]
- IETF RFC 5785 [Superseded*]
- IETF RFC 5890 [Active*]
- IETF RFC 5891 [Active*]
- IETF RFC 5934 [Active*]
- IETF RFC 5952 [Active*]
- IETF RFC 5987 [Superseded*]
- IETF RFC 5988 [Superseded*]
- IETF RFC 5996 [Superseded*]
- IETF RFC 6020 [Active*]
- IETF RFC 6021 [Superseded*]
- IETF RFC 6042 [Active*]
- IETF RFC 6066 [Active*]
- IETF RFC 6068 [Active*]
- IETF RFC 6120 [Active*]
- IETF RFC 6125 [Superseded*]
- IETF RFC 6241 [Active*]
- IETF RFC 6266 [Active*]
- IETF RFC 6350 [Active*]
- IETF RFC 6415 [Active*]
- IETF RFC 6443 [Active*]
- IETF RFC 6454 [Active*]
- IETF RFC 6455 [Active*]
- IETF RFC 6570 [Active*]
- IETF RFC 6596 [Active*]
- IETF RFC 6648 [Active*]
- IETF RFC 6690 [Active*]
- IETF RFC 6726 [Active*]
- IETF RFC 6733 [Active*]
- IETF RFC 6749 [Active*]
- IETF RFC 6750 [Active*]
- IETF RFC 6797 [Active*]
- IETF RFC 6838 [Active*]
- IETF RFC 6874 [Superseded*]
- IETF RFC 6901 [Active*]
- IETF RFC 6920 [Active*]
- IETF RFC 6931 [Superseded*]
- IETF RFC 6933 [Active*]
- IETF RFC 6943 [Active*]
- IETF RFC 6960 [Active*]
- IETF RFC 6983 [Active*]
- IETF RFC 6991 [Superseded*]
- IETF RFC 7030 [Active*]
- IETF RFC 7049 [Superseded*]
- IETF RFC 7230 [Superseded*]
- IETF RFC 7231 [Superseded*]
- IETF RFC 7235 [Superseded*]
- IETF RFC 7238 [Superseded*]
- IETF RFC 7252 [Active*]
- IETF RFC 7296 [Active*]
- IETF RFC 7303 [Active*]
- IETF RFC 7320 [Superseded*]
- IETF RFC 7390 [Active*]
- IETF RFC 7515 [Active*]
- IETF RFC 7519 [Active*]
- IETF RFC 7540 [Superseded*]
- IETF RFC 7595 [Active*]
- IETF RFC 7616 [Active*]
- IETF RFC 7617 [Active*]
- IETF RFC 7636 [Active*]
- IETF RFC 7807 [Superseded*]
- IETF RFC 7838 [Active*]
- IETF RFC 7950 [Active, Amended*]
- IETF RFC 8040 [Active*]
- IETF RFC 8075 [Active*]
- IETF RFC 8141 [Active*]
- IETF RFC 8187 [Active*]
- IETF RFC 8216 [Active*]
- IETF RFC 8285 [Active*]
- IETF RFC 8288 [Active*]
- IETF RFC 8323 [Active*]
- IETF RFC 8615 [Active*]
- IETF RFC 8820 [Active*]
- IETF RFC 8949 [Active*]
- IETF RFC 9113 [Active*]
- IETF RFC 9231 [Active*]
- IETF RFC 9725 [Active*]
- SMPTE AG 05 [Active, Versionless]
- SMPTE AG 21 [Active, Versionless]
- SMPTE AG 25 [Active, Versionless]
- SMPTE AG 29 [Active, Versionless]
- SMPTE RDD 18:2010 [Superseded]
- SMPTE RDD 18:2012 [Superseded]
- SMPTE RDD 42:2016 [Active]
- SMPTE RDD 43:2016 [Active]
- SMPTE ST 2021-1:2015 [Superseded]
- SMPTE ST 2021:2008 [Active]
- SMPTE ST 2029:2022 [Active]
- SMPTE ST 2029:2023 [Active]
- SMPTE ST 2034-1:2017 [Active]
- SMPTE ST 2053:2011 [Active, Stabilized]
- SMPTE ST 2067-100:2014 [Active]
- SMPTE ST 2067-101:2014 [Superseded]
- SMPTE ST 2067-101:2018 [Active]
- SMPTE ST 2071-1:2012 [Superseded]
- SMPTE ST 2071-1:2014 [Superseded]
- SMPTE ST 2071-1:2016 [Active, Stabilized]
- SMPTE ST 2098-2:2022 [Active]
- SMPTE ST 377-1:2011 [Superseded]
- SMPTE ST 429-10:2023-09 [Active]
- SMPTE ST 429-14:2023-09 [Active]
- SMPTE ST 429-18:2023-09 [Active]
- SMPTE ST 429-5:2023-09 [Active]
- SMPTE ST 429-9:2014 [Active]
- SMPTE ST 430-14:2015 [Superseded]
- SMPTE ST 430-14:2021 [Active]
- SMPTE ST 430-15:2017 [Active]