Protocol Action: 'Internationalized Resource Identifiers (IRIs)' to Proposed Standard

The IESG <> Wed, 08 December 2004 15:24 UTC

Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id KAA04833; Wed, 8 Dec 2004 10:24:41 -0500 (EST)
Received: from ([]) by with esmtp (Exim 4.33) id 1Cc3n6-00084E-Is; Wed, 08 Dec 2004 10:31:44 -0500
Received: from localhost.localdomain ([] by with esmtp (Exim 4.32) id 1Cc3Xw-0001SJ-S9; Wed, 08 Dec 2004 10:16:04 -0500
Received: from ([] by with esmtp (Exim 4.32) id 1Cc3Kp-0003be-2j; Wed, 08 Dec 2004 10:02:31 -0500
Received: from ( []) by (8.9.1a/8.9.1a) with ESMTP id KAA01730; Wed, 8 Dec 2004 10:02:29 -0500 (EST)
Received: from ([]) by with esmtp (Exim 4.33) id 1Cc3Rc-0007Xf-Ey; Wed, 08 Dec 2004 10:09:32 -0500
Received: from apache by with local (Exim 4.32) id 1Cc3Do-00010M-F1; Wed, 08 Dec 2004 09:55:16 -0500
X-test-idtracker: no
From: The IESG <>
To: IETF-Announce <>
Message-Id: <>
Date: Wed, 08 Dec 2004 09:55:16 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Internet Architecture Board <>, RFC Editor <>
Subject: Protocol Action: 'Internationalized Resource Identifiers (IRIs)' to Proposed Standard
X-Mailman-Version: 2.1.5
Precedence: list
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

The IESG has approved the following document:

- 'Internationalized Resource Identifiers (IRIs) '
   <draft-duerst-iri-11.txt> as a Proposed Standard

This document has been reviewed in the IETF but is not the product of an
IETF Working Group. 

The IESG contact person is Ted Hardie.

Technical Summary
This document describes Internationalized Resource Identifiers and their
relationship to URIs.     While the character limitations of URIs are not 
usually an issue for protocol processing, they may restrict the usefulness of
the identifiers presented to end users or systems expecting a different range of
characters.  Rather than extend URIs, this document introduces a  new identifier
type and a describes a relationship to URIs.    Within an IETF context, IRIs
will likely be  used as presentation elements.  There are cases, such as XML
namespaces, in which an IRI may be used as a token, because
character-by-character equivalence is the only property used for protocol
processing.  In no case should an implementor assume that an IRI may be
substituted for a URI in an existing protocol grammar; either the generative
grammar associated with the protocol must be updated to specify IRIs or the
implementation must transform an IRI into a URI before use.

Working Group Summary
This work was initiated in the W3C, and it has been broadly accepted in that
context.  It has also been discussed on the URI mailing list and a public, open
list ( dedicated to the topic.  Considerable care has been
taken to keep this specification well-synchronized with the URI specification.
There were issues raised during IETF Last Call, and a new document version
resolving those issues was submitted.

IETF-Announce mailing list