- From: John Cowan <cowan@mercury.ccil.org>
- Date: Sun, 31 Jul 2011 04:38:53 -0400
- To: Apps-discuss list <apps-discuss@ietf.org>
- Cc: "uri-review@ietf.org" <uri-review@ietf.org>, URI <uri@w3.org>, "ftpext@ietf.org" <ftpext@ietf.org>, register@uri.arpa, "public-iri@w3.org" <public-iri@w3.org>
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. 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>". Note error "internalization" for "internationalization", "internalized" for "internationalized", etc. Note persistent typo "exmaple.com" for "example.com". -- Do what you will, John Cowan this Life's a Fiction cowan@ccil.org And is made up of http://www.ccil.org/~cowan Contradiction. --William Blake
Received on Sunday, 31 July 2011 08:39:17 UTC