Protocol Action: 'Uniform Resource Identifier (URI): Generic Syntax' to Full Standard
The IESG <iesg-secretary@ietf.org> Mon, 18 October 2004 23:17 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05117; Mon, 18 Oct 2004 19:17:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJgxF-0004Tw-RL; Mon, 18 Oct 2004 19:30:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJgJH-0004lq-FG; Mon, 18 Oct 2004 18:48:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CJfva-0007wN-1P; Mon, 18 Oct 2004 18:24:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00762; Mon, 18 Oct 2004 18:24:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CJg7e-0003FW-PP; Mon, 18 Oct 2004 18:36:58 -0400
Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CJff0-0000zr-Tn; Mon, 18 Oct 2004 18:07:22 -0400
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CJff0-0000zr-Tn@megatron.ietf.org>
Date: Mon, 18 Oct 2004 18:07:22 -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Protocol Action: 'Uniform Resource Identifier (URI): Generic Syntax' to Full Standard
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
The IESG has approved the following document: - 'Uniform Resource Identifier (URI): Generic Syntax ' <draft-fielding-uri-rfc2396bis-07.txt> as a Full 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 advances the URI specification to Full Standard. It defines the generic syntax for URIs and describes a process for resolving URI references that are in relative form. It also contains guidelines for the use of URIs on the Internet and security considerations which are common to the use of URIs. The grammar it defines is a superset of valid URIs, so that a common parser or similar component can be built without scheme-specific data. Working Group Summary The URI working group is not active at this time, but the mailing list (uri@w3.org) remains active. Members of the mailing list reviewed this document extensively, and a comprehensive issues list was maintained, with recorded resolutions of each of the issues raised. The document also received editorial comments during Last Call; a new version of the document with additional explanatory text was generated in response to the issues raised. URIs are widely in used many Internet context, and there has been no dissent that a Full Standard updating RFC 2396 would be valuable. Protocol Quality This document was reviewed for the IESG by Ted Hardie. RFC Editor Note: OLD: URI comparison is performed in respect to some particular purpose, and implementations with differing purposes will often be subject to differing design trade-offs in regards to how much effort should be spent in reducing aliased identifiers. NEW: URI comparison is performed in respect to some particular purpose, and protocols or implementations comparing for purposes will often be subject to differing design trade-offs in regards to how much effort should be spent in reducing aliased identifiers. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce