Visual RFC.
ALL RFCs / RFC 3986
Read the RFC ↗
RFC 3986 / AUTHORITY

Authority has its own structure

04

User information, host, and port are separate subcomponents; IP literals need brackets.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 3.2 ↗
RFC 3986 · § 3.2EXAMPLE
4 / 4
Authority has its own structureAuthority subcomponents separate userinfo, host, and port, with bracket strokes around an IPv6 literal.Authority is not just a host stringname @ example.org : 443userinfohostportname is not the destination[2001:db8::7] : 443brackets contain the IPv6 addressThe scheme defines what the port means.
04
Apply scheme-specific meaning.

The generic grammar identifies the port component; the scheme defines defaults.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 2396RFC 3986 Appendix D.1

The revised generic syntax incorporates bracketed IP-literal hosts from RFC 2732 and expands normalization and comparison guidance.

Read the updated RFC section ↗
KEY POINT

Read the host after parsing, not by guessing from the text.

  • The generic authority form is [userinfo@]host[:port].
  • IPv6 address literals are enclosed in square brackets in a URI host.
  • Use of a password in userinfo is deprecated.
DETAILS

The examples simplify the wire representation. Follow the linked specification and application profile for implementation.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. The five URI components
  2. Escape data, preserve delimiters
  3. Resolve a relative reference
  4. Authority has its own structure
  5. Normalize only what is safe
  6. An identifier can mislead
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗