RFC 3987: Internationalized Resource Identifiers (IRIs)
In plain English — editorial summary, not part of the RFC
This document defines a new protocol element, the Internationalized Resource Identifier (IRI), as a complement of the Uniform Resource Identifier (URI). An IRI is a sequence of characters from the Universal Character Set (Unicode/ISO 10646). A mapping from IRIs to URIs is defined, which means that IRIs can be used instead of URIs, where appropriate, to identify resources. The approach of defining a new protocol element was chosen instead of extending or changing the definition of URIs. This was done in order to allow a clear distinction and to avoid incompatibilities with existing software. Guidelines are provided for the use and deployment of IRIs in various protocols, formats, and software components that currently deal with URIs.
Document record
- Document ID
- RFC3987
- Published
- January 2005
- Authors
- M. Duerst; M. Suignard
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 46
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
- RFC 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 3953Telephone Number Mapping (ENUM) Service Registration for Presence ServicesUpdated
January 2005
- RFC 4078The TV-Anytime Content Reference Identifier (CRID)Current
May 2005
- RFC 4095Attaching Meaning to Solicitation Class KeywordsCurrent
May 2005
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
- RFC 4575A Session Initiation Protocol (SIP) Event Package for Conference StateCurrent
August 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?