Re: URL generic syntax draft to last call?
Larry Masinter <email@example.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 [184.108.40.206]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id NAA07943 for <firstname.lastname@example.org>; Fri, 2 May 1997 13:54:45 -0400 (EDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [220.127.116.11]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id NAA22597 for <email@example.com>; Fri, 2 May 1997 13:54:22 -0400 (EDT)
Received: from casablanca.parc.xerox.com ([18.104.22.168]) by alpha.xerox.com with SMTP id <18496(10)>; Fri, 2 May 1997 10:47:54 PDT
Received: from bronze-208.parc.xerox.com ([22.214.171.124]) by casablanca.parc.xerox.com with SMTP id <74495>; Fri, 2 May 1997 10:47:49 PDT
Date: Fri, 2 May 1997 10:47:43 PDT
From: Larry Masinter <firstname.lastname@example.org>
Organization: Xerox PARC
X-Mailer: Mozilla 3.01Gold (Win95; I)
To: "Martin J. Duerst" <email@example.com>
CC: Chris Newman <Chris.Newman@innosoft.com>, IETF URI list <firstname.lastname@example.org>
Subject: Re: URL generic syntax draft to last call?
Content-Type: text/plain; charset=us-ascii
> 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.