RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax

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…

Read RFC 2396 on the RFC Editor

Outgoing relationships (14 related RFCs)

Updates, Informative reference — RFC 1738: Uniform Resource Locators (URL)
Updates, Informative reference — RFC 1808: Relative Uniform Resource Locators
Informative reference — RFC 1034: Domain names - concepts and facilities
Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Informative reference — RFC 1123: Requirements for Internet Hosts - Application and Support
Informative reference — RFC 2141: URN Syntax
Informative reference — RFC 2279: UTF-8, a transformation format of ISO 10646
Informative reference — RFC 2277: IETF Policy on Character Sets and Languages
Informative reference — RFC 1866: Hypertext Markup Language - 2.0
Informative reference — RFC 1737: Functional Requirements for Uniform Resource Names
Informative reference — RFC 1630: Universal Resource Identifiers in WWW: A Unifying Syntax for the Expression of Names and Addresses of Objects on the Network as used in the World-Wide Web
Informative reference — RFC 1736: Functional Recommendations for Internet Resource Locators
Informative reference — RFC 2110: MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)

Incoming relationships (52 related RFCs)

Showing 50 of 52 related RFCs.

Updated by — RFC 2732: Format for Literal IPv6 Addresses in URL's
Obsoleted by — RFC 3986: Uniform Resource Identifier (URI): Generic Syntax
Normatively referenced by — RFC 3261: SIP: Session Initiation Protocol
Normatively referenced by — RFC 3688: The IETF XML Registry
Normatively referenced by — RFC 3840: Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)
Normatively referenced by — RFC 3862: Common Presence and Instant Messaging (CPIM): Message Format
Normatively referenced by — RFC 3546: Transport Layer Security (TLS) Extensions
Normatively referenced by — RFC 3887: Message Tracking Query Protocol
Normatively referenced by — RFC 3296: Named Subordinate References in Lightweight Directory Access Protocol (LDAP) Directories
Normatively referenced by — RFC 3467: Role of the Domain Name System (DNS)
Normatively referenced by — RFC 3520: Session Authorization Policy Element
Normatively referenced by — RFC 3696: Application Techniques for Checking and Transformation of Names
Normatively referenced by — RFC 3764: enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record
Normatively referenced by — RFC 3648: Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol
Normatively referenced by — RFC 3995: Internet Printing Protocol (IPP): Event Notifications and Subscriptions
Normatively referenced by — RFC 4037: Open Pluggable Edge Services (OPES) Callout Protocol (OCP) Core
Normatively referenced by — RFC 3620: The TUNNEL Profile
Normatively referenced by — RFC 3660: Basic Media Gateway Control Protocol (MGCP) Packages
Informatively referenced by — RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
Informatively referenced by — RFC 2617: HTTP Authentication: Basic and Digest Access Authentication
Informatively referenced by — RFC 3966: The tel URI for Telephone Numbers
Informatively referenced by — RFC 2608: Service Location Protocol, Version 2
Informatively referenced by — RFC 3958: Domain-Based Application Service Location Using SRV RRs and the Dynamic Delegation Discovery Service (DDDS)
Informatively referenced by — RFC 3080: The Blocks Extensible Exchange Protocol Core
Informatively referenced by — RFC 3720: Internet Small Computer Systems Interface (iSCSI)
Informatively referenced by — RFC 2817: Upgrading to TLS Within HTTP/1.1
Informatively referenced by — RFC 2565: Internet Printing Protocol/1.0: Encoding and Transport
Informatively referenced by — RFC 4516: Lightweight Directory Access Protocol (LDAP): Uniform Resource Locator
Informatively referenced by — RFC 2397: The "data" URL scheme
Informatively referenced by — RFC 3196: Internet Printing Protocol/1.1: Implementor's Guide
Informatively referenced by — RFC 2609: Service Templates and Service: Schemes
Informatively referenced by — RFC 3076: Canonical XML Version 1.0
Informatively referenced by — RFC 2538: Storing Certificates in the Domain Name System (DNS)
Informatively referenced by — RFC 3419: Textual Conventions for Transport Addresses
Informatively referenced by — RFC 2802: Digital Signatures for the v1.0 Internet Open Trading Protocol (IOTP)
Informatively referenced by — RFC 2806: URLs for Telephone Calls
Informatively referenced by — RFC 3075: XML-Signature Syntax and Processing
Informatively referenced by — RFC 3805: Printer MIB v2
Informatively referenced by — RFC 3953: Telephone Number Mapping (ENUM) Service Registration for Presence Services
Informatively referenced by — RFC 2592: Definitions of Managed Objects for the Delegation of Management Script
Informatively referenced by — RFC 3111: Service Location Protocol Modifications for IPv6
Informatively referenced by — RFC 8089: The "file" URI Scheme
Informatively referenced by — RFC 2614: An API for Service Location
Informatively referenced by — RFC 2774: An HTTP Extension Framework
Informatively referenced by — RFC 2807: XML Signature Requirements
Informatively referenced by — RFC 3675: .sex Considered Dangerous
Informatively referenced by — RFC 4156: The wais URI Scheme
Informatively referenced by — RFC 6560: One-Time Password (OTP) Pre-Authentication
Informatively referenced by — RFC 2594: Definitions of Managed Objects for WWW Services
Informatively referenced by — RFC 3117: On the Design of Application Protocols