W3C home > Mailing lists > Public > public-iri@w3.org > October 2010

Re: Fwd: I-D Action:draft-ietf-iri-3987bis-02.txt

From: Peter Saint-Andre <stpeter@stpeter.im>
Date: Sun, 17 Oct 2010 19:42:44 -0600
Message-ID: <4CBBA614.6030307@stpeter.im>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
CC: "public-iri@w3.org" <public-iri@w3.org>
It *was* sent to the list:

> CC: public-iri@w3.org

But seemingly it was not delivered.

Perhaps the public-iri@w3.org list is not configured to automatically
allow posts from "Internet-Drafts@ietf.org"?

On 10/17/10 7:38 PM, "Martin J. Dürst" wrote:
> This is the official announcement of the publication of
> draft-ietf-iri-3987bis-02.txt.
> Chairs, ADs, any idea why such an announcement isn't sent to this list
> automatically? That's done for most of the WGs I know.
> Regards,   Martin.
> -------- Original Message --------
> Subject: I-D Action:draft-ietf-iri-3987bis-02.txt
> Date: Sat, 16 Oct 2010 21:15:01 -0700 (PDT)
> From: Internet-Drafts@ietf.org
> Reply-To: internet-drafts@ietf.org
> To: i-d-announce@ietf.org
> CC: public-iri@w3.org
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the Internationalized Resource Identifiers
> Working Group of the IETF.
>     Title           : Internationalized Resource Identifiers (IRIs)
>     Author(s)       : M. Duerst, et al.
>     Filename        : draft-ietf-iri-3987bis-02.txt
>     Pages           : 56
>     Date            : 2010-10-16
> This document defines the Internationalized Resource Identifier (IRI)
> protocol element, as an extension of the Uniform Resource Identifier
> (URI).  An IRI is a sequence of characters from the Universal
> Character Set (Unicode/ISO 10646).  Grammar and processing rules are
> given for IRIs and related syntactic forms.
> In addition, this document provides named additional rule sets for
> processing otherwise invalid IRIs, in a way that supports other
> specifications that wish to mandate common behavior for 'error'
> handling.  In particular, rules used in some XML languages (LEIRI)
> and web applications are given.
> Defining IRI as new protocol element (rather than updating or
> extending the definition of URI) allows independent orderly
> transitions: other protocols and languages that use URIs must
> explicitly choose to allow IRIs.
> Guidelines are provided for the use and deployment of IRIs and
> related protocol elements when revising protocols, formats, and
> software components that currently deal only with URIs.
> RFC Editor: Please remove the next paragraph before publication.
> This document is intended to update RFC 3987 and move towards IETF
> Draft Standard.  For discussion and comments on this draft, please
> join the IETF IRI WG by subscribing to the mailing list
> public-iri@w3.org.  For a list of open issues, please see the issue
> tracker of the WG at http://trac.tools.ietf.org/wg/iri/trac/report/1.
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-iri-3987bis-02.txt
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.

Peter Saint-Andre

Received on Monday, 18 October 2010 01:43:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:39:41 UTC