ietf-nntp draft-ietf-nntpext-base-19
Ken Murchison
ken at oceana.com
Wed Aug 13 09:46:26 PDT 2003
Clive D.W. Feather wrote:
> Existing wording in 3.1:
>
> Commands may have variants, using a second keyword immediately
> after the first to indicate which variant is required. The only
> such commands in this specification are LIST and MODE.
>
> to which I have appended:
[...]
OK. This seems clearer to me.
>
>>5.2.2: This says that MODE READER should be used before using any
>>extensions advertised by LIST EXTENSIONS. Well, some of those
>>extensions may not be reader-type commands, eg. CHECK/TAKETHIS. I'd
>>suggest that the text be changed to say "or any reader-only commands
>>advertised via LIST EXTENSIONS".
>
>
> You're misreading that text, though I can see why. It actually means the
> opposite: "a command advertised by the server as available via LIST
> EXTENSIONS" is meant to be the last entry in the list that begins "IHAVE".
>
> New wording for 5.2.2:
>
[...]
> Clearer?
Yes.
>>8.6.1.1: Just for consistency, the usage section should probably be
>>changed to use the same format as ARTICLE/HEAD/BODY/STAT/OVER, eg. only
>>two forms:
>>
>> HDR message-id
>> HDR [range]
>
>
> Actually, I think it's better to change the former to match HDR; it saves
> weasel-footnotes (which turned out to be incomplete) about which response
> can happen when.
OK. Either way is fine with me, as long as its consistent.
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
More information about the ietf-nntp
mailing list