Re: [ftpext] FWD: I-D Action: draft-yevstifeyev-ftp-uri-scheme-05.txt

Mykyta Yevstifeyev <evnikita2@gmail.com> Sun, 31 July 2011 09:58 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: ftpext@ietfa.amsl.com
Delivered-To: ftpext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2F321F87C5; Sun, 31 Jul 2011 02:58:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.548
X-Spam-Level:
X-Spam-Status: No, score=-3.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fVQfTp4Nd7pI; Sun, 31 Jul 2011 02:58:43 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3380E21F87BD; Sun, 31 Jul 2011 02:58:43 -0700 (PDT)
Received: by fxe6 with SMTP id 6so4192090fxe.31 for <multiple recipients>; Sun, 31 Jul 2011 02:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=L3KBKDYqbgh++YjmziDNDA0Z6aFTB4oQCV+hyiylaMI=; b=WyuwlGqmyrT6kxpUPNOcwCw0LNNs5ojL0qQi4SOI9wZqCMYog+Atp/HsgVTUkjp9Fs 7r8ziRPlJCSoOVcCuq4DIKlIsAHZARB373q5QmDBKbbp7+cPwx61IloTlw1TOtlfwv8b VxztHdLyU+tFNtaK8iPtzeLp7AAycYfJ7fxY0=
Received: by 10.223.14.24 with SMTP id e24mr4645514faa.15.1312106325443; Sun, 31 Jul 2011 02:58:45 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id w11sm2176317faj.14.2011.07.31.02.58.43 (version=SSLv3 cipher=OTHER); Sun, 31 Jul 2011 02:58:44 -0700 (PDT)
Message-ID: <4E35277B.5010708@gmail.com>
Date: Sun, 31 Jul 2011 12:59:23 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: John Cowan <cowan@mercury.ccil.org>
References: <4E34DC83.30504@gmail.com> <20110731083853.GB30568@mercury.ccil.org>
In-Reply-To: <20110731083853.GB30568@mercury.ccil.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: register@uri.arpa, Apps-discuss list <apps-discuss@ietf.org>, "ftpext@ietf.org" <ftpext@ietf.org>, URI <uri@w3.org>, "public-iri@w3.org" <public-iri@w3.org>, "uri-review@ietf.org" <uri-review@ietf.org>
Subject: Re: [ftpext] FWD: I-D Action: draft-yevstifeyev-ftp-uri-scheme-05.txt
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jul 2011 09:58:44 -0000

31.07.2011 11:38, John Cowan wrote:
> Mykyta Yevstifeyev scripsit:
>
>> Sorry for cross-posting to 6 addresses :-); please send
>> all your comments to apps-discuss@ietf.org.  Note to
>> public-iri subscribers: please have a look at Section
>> 6.  Note to register@uri.arpa subscribers: please comment
>> Appendix A of the document.  (The link to HTML version:
>> http://tools.ietf.org/html/draft-yevstifeyev-ftp-uri-scheme.)
> It's inappropriate to say that the client SHALL request a password
> from the user if none is supplied and the server demands one (and
> likewise for accounts).  The client must be free to fail under such
> circumstances, as it may be a robot or otherwise not have a user
> available.  Likewise with SHALL notify the user, etc.  These should be
> changed to MAYs or SHOULDs.

I think such occurrences of SHALL will be replaced with SHOULD or 
non-normative "should".  (I don't think 'ftp' URIs will be used with 
applications that have no UI; so I don't see reasons to assume they will 
be used in such way.  But, anyway, your comment regarding SHALL is 
reasonable).

>
> Editorial notes:  Lots of people don't know what "ibidem" means, or even
> its standard abbreviation "ibid".  I suggest changing the first instance
> to "in RFC 959", the second instance to "below", and the third instance
> to "in the<cwd>".

I'll make the following corrections: 1st instance - "in RFC 959" (as 
currently), 2nd one - "in the same document", 3rd one (I guess this is 
regarding ASCII) - "in RFC 959".

>
> Note error "internalization" for "internationalization", "internalized"
> for "internationalized", etc.

Fixed now.

>
> Note persistent typo "exmaple.com" for "example.com".

ACK.  Thanks for reading the document.  Mykyta

>