Re: URL generic syntax draft to last call?

Larry Masinter <masinter@parc.xerox.com> Fri, 02 May 1997 18:17 UTC

Received: from cnri by ietf.org id aa29684; 2 May 97 14:17 EDT
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa17485; 2 May 97 14:17 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id NAA07948 for uri-out; Fri, 2 May 1997 13:54:49 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id NAA07943 for <uri@services.bunyip.com>; Fri, 2 May 1997 13:54:45 -0400 (EDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id NAA22597 for <uri@bunyip.com>; Fri, 2 May 1997 13:54:22 -0400 (EDT)
Received: from casablanca.parc.xerox.com ([13.2.16.111]) by alpha.xerox.com with SMTP id <18496(10)>; Fri, 2 May 1997 10:47:54 PDT
Received: from bronze-208.parc.xerox.com ([13.0.209.122]) by casablanca.parc.xerox.com with SMTP id <74495>; Fri, 2 May 1997 10:47:49 PDT
Message-ID: <336A28BF.4897@parc.xerox.com>
Date: Fri, 2 May 1997 10:47:43 PDT
From: Larry Masinter <masinter@parc.xerox.com>
Organization: Xerox PARC
X-Mailer: Mozilla 3.01Gold (Win95; I)
MIME-Version: 1.0
To: "Martin J. Duerst" <mduerst@ifi.unizh.ch>
CC: Chris Newman <Chris.Newman@innosoft.com>, IETF URI list <uri@bunyip.com>
Subject: Re: URL generic syntax draft to last call?
References: <Pine.SUN.3.96.970502104821.245S-100000@enoshima>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-uri@bunyip.com
Precedence: bulk

> I definitely agree that we have made a lot of progress.
> However, because there have been several cases where people on
> the list, including myself, have had different impressions about
> the nature and degree of consensus achieved, which has led to
> some very unfortunate message exchanges, it would be very
> helpful if you could:
> 
> - Shortly state what, in your oppinion, has been resolved
>         (and what may not yet have been resolved).

I don't think the latest draft will please everyone, but I think
that by toning down the explanation that "URLs are limited to ASCII",
pointing out that the definition of non-ASCII URLs is handled
outside of this document, and starting on the process of actually
resolving how non-ASCII URLs can be made to work, we've dealt with
the requirements of starting the work on Internationalization and
leaving enough space to come to a resolution on the issues.

> - Explain how you intend this to be reflected (or not) in
>         the URL generic syntax draft.

Please review the latest I-D submission.