Uniform Resource Identifiers (URI): Generic Syntax
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 40
- Abstract
- This document defines a grammar that is a superset of all valid URI, such that an implementation can parse the common components of a URI reference without knowing the scheme-specific requirements of every possible identifier type. [STANDARDS-TRACK]
- Publication Date
- 1998-08-01
- Status Note
- Draft Standard
- DOI
10.17487/RFC2396- ISSN
2070-1721- Link
- https://doi.org/10.17487/RFC2396
- Author(s)
- Tim Berners-LeeLarry M MasinterRoy T. Fielding
- Keyword(s)
- URI-GEN, Characters, String, Absolute, Relative
Latest version of IETF RFC 2396
Document Versions — IETF RFC 2396
-
▶ IETF RFC 2396 (1998-08-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Bibliographic Reference(s)
- ANSI/INCITS X3.4:1986 (R1997) [Active]
- IETF RFC 822 [Superseded*]
- IETF RFC 1034 [Active*]
- IETF RFC 1123 [Active*]
- IETF RFC 1630 [Active*]
- IETF RFC 1736 [Active*]
- IETF RFC 1737 [Active*]
- IETF RFC 1738 [Superseded*]
- IETF RFC 1808 [Superseded*]
- IETF RFC 1866 [Superseded*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2110 [Superseded*]
- IETF RFC 2141 [Superseded*]
- IETF RFC 2277 [Active*]
- IETF RFC 2279 [Superseded*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC2396.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 2396, Uniform Resource Identifiers (URI): Generic Syntax. Available at https://doi.org/10.17487/RFC2396
Snippet:
IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax. Available at https://doi.org/10.17487/RFC2396
HTML (ISO 690 compliant)
Preview:
IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax. Available at https://doi.org/10.17487/RFC2396
Snippet:
<span class="citation"><cite>IETF RFC 2396</cite>, Uniform Resource Identifiers (URI): Generic Syntax. Available at <a href="https://doi.org/10.17487/RFC2396" target="_blank" rel="noopener">https://doi.org/10.17487/RFC2396</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax
doi: 10.17487/RFC2396
url: https://doi.org/10.17487/RFC2396
doi: 10.17487/RFC2396
url: https://doi.org/10.17487/RFC2396
Snippet:
<li> <cite id="bib-rfc2396">IETF RFC 2396</cite>, Uniform Resource Identifiers (URI): Generic Syntax <span class="doi">10.17487/RFC2396</span> </li>
Referenced By
- Rich Metadata Description for Interactivity and Dynamic User-Generated Information [Active]
- ISO 26429-10:2009 [Active]
- ISO 26429-7:2008 [Active, Reaffirmed]
- ISO 26429-8:2009 [Active, Reaffirmed]
- ISO 26429-9:2009 [Active]
- ISO 26430-9:2009 [Active, Reaffirmed]
- IETF RFC 2397 [Active*]
- IETF RFC 2518 [Superseded*]
- IETF RFC 2538 [Superseded*]
- IETF RFC 2565 [Superseded*]
- IETF RFC 2566 [Superseded*]
- IETF RFC 2608 [Active*]
- IETF RFC 2609 [Active*]
- IETF RFC 2616 [Superseded*]
- IETF RFC 2617 [Superseded*]
- IETF RFC 2629 [Superseded*]
- IETF RFC 2717 [Superseded*]
- IETF RFC 2718 [Superseded*]
- IETF RFC 2732 [Superseded*]
- IETF RFC 2756 [Active*]
- IETF RFC 2774 [Active*]
- IETF RFC 2802 [Active*]
- IETF RFC 2803 [Active*]
- IETF RFC 2806 [Superseded*]
- IETF RFC 2807 [Active*]
- IETF RFC 2817 [Active*]
- IETF RFC 2838 [Active*]
- IETF RFC 2848 [Active*]
- IETF RFC 2854 [Active*]
- IETF RFC 2915 [Superseded*]
- IETF RFC 2916 [Superseded*]
- IETF RFC 2938 [Active*]
- IETF RFC 2965 [Superseded*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 3075 [Superseded*]
- IETF RFC 3076 [Active*]
- IETF RFC 3080 [Active*]
- IETF RFC 3111 [Active*]
- IETF RFC 3151 [Active*]
- IETF RFC 3236 [Active*]
- IETF RFC 3253 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3275 [Active*]
- IETF RFC 3305 [Active*]
- IETF RFC 3367 [Active*]
- IETF RFC 3368 [Active*]
- IETF RFC 3403 [Active*]
- IETF RFC 3404 [Active*]
- IETF RFC 3405 [Active*]
- IETF RFC 3419 [Active*]
- IETF RFC 3467 [Active*]
- IETF RFC 3470 [Active*]
- IETF RFC 3546 [Superseded*]
- IETF RFC 3588 [Superseded*]
- IETF RFC 3617 [Active*]
- IETF RFC 3648 [Active*]
- IETF RFC 3688 [Active*]
- IETF RFC 3696 [Active*]
- IETF RFC 3741 [Active*]
- IETF RFC 3830 [Active*]
- IETF RFC 3840 [Active*]
- IETF RFC 3859 [Active*]
- IETF RFC 3860 [Active*]
- IETF RFC 3862 [Active*]
- IETF RFC 3863 [Active*]
- IETF RFC 3864 [Active*]
- IETF RFC 3875 [Active*]
- IETF RFC 3887 [Active*]
- IETF RFC 3920 [Superseded*]
- IETF RFC 3958 [Active*]
- IETF RFC 3966 [Active*]
- IETF RFC 3981 [Active*]
- IETF RFC 3983 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 3987 [Active*]
- IETF RFC 4051 [Superseded*]
- IETF RFC 4516 [Active*]
- SMPTE ST 2001-1:2013 [Superseded]
- SMPTE ST 2001-1:2015 [Active]
- SMPTE ST 2052-1:2010 [Superseded]
- SMPTE ST 2052-1:2013 [Active, Stabilized]
- SMPTE ST 2067-3:2013 [Superseded]
- SMPTE ST 2067-3:2016 [Superseded]
- SMPTE ST 2098-2:2018 [Superseded]
- SMPTE ST 2098-2:2019 [Superseded]
- SMPTE ST 343:2002 [Active, Stabilized]
- SMPTE ST 363-2:2002 [Active, Stabilized]
- SMPTE ST 428-10:2008 [Active]
- SMPTE ST 428-7:2010 [Superseded]
- SMPTE ST 428-7:2014 [Active, Reaffirmed]
- SMPTE ST 429-10:2008 [Superseded]
- SMPTE ST 429-12:2008 [Active]
- SMPTE ST 429-14:2014 [Superseded]
- SMPTE ST 429-18:2019 [Superseded]
- SMPTE ST 429-5:2009 [Superseded]
- SMPTE ST 429-5:2017 [Superseded]
- SMPTE ST 429-7:2006 [Active, Reaffirmed]
- SMPTE ST 429-8:2007 [Active]
- SMPTE ST 429-9:2007 [Superseded]
- SMPTE ST 430-11:2010 [Active]
- SMPTE ST 430-7:2008 [Withdrawn*]
- SMPTE ST 430-9:2008 [Active, Amended]
- SMPTE ST 430-9:2008 Am1:2011 [Active]