ietf-nntp Charles's nitpicks

[Clive D.W. Feather]

Charles Lindsey said:
>>> 	{split infinitive}
>> What is wrong with a split infinitive ? This is English, not Latin.
> If you split them, you annoy some people. If you don't split them, you
> annoy nobody.

No, you annoy a different set of people.

>>> P15-18	503 -> 502
>>> 	{I think so; certainly not 503}
>> Which command is this ?
> LIST EXTENSIONS

502 is "you are not authorized to do this"
503 is "no plans to implement this"
403 is "optional feature not available right this moment"

See my other message. I think 503 is wrong because LIST EXTENSIONS uses 402
to mean "no extensions". 403 might be the right code.

>>> P46+7	211 2000 3000234 3002322 -> 211 6 300234 3002322
>>> 	{since you give only 6 groups in the example, the "2000" is hardly
>>> 	realistic; moreover 2000 is impossible given those high/low
>>> 	watermarks}
>> Um, 3002322-3000234 = 2088, according to my calculator.
> Ah! The dangers of doing arithmetic in one's head :-) .
> But I still think it should be '6'.

Actually he only gives 5 articles in the example. But we say that the count
may be anything between actual number and HWM-LWM+1, so 2000 is a
reasonable thing to demonstrate this.

>>> P53-1 It needs to say what timezone is to be used in the
>>> DATE response.
>> DATE always returns UTC.
> Then it needs to say so.

Um:

  DATE    
  This command exists to help clients find out the current Coordinated
  Universal Time[7] from the server's perspective.

However, the response wording "Local date" is then wrong.

>>> P55-20	It says there is no way to establish the server's timezone. This
>>> 	would not be correct if the DATE command used the server's local
>>> 	time.
>> Only true if you (a) know this, (b) know the current time in UTC, and (c)
>> know that the result from DATE is reasonably accurate.
> Within 30 minutes would be accurate enough.

Why ? If DATE says it's 10:50 and I know it's 01:00 UTC, is the server in
zone +1000 (eastern Australia) or zone +0930 (northern Australia) ? Are you
sure there are no XX15 zones left ? ISO 8601 assumes that zones may be
aligned to any whole minute.

>> I thought we were ignoring the syntax section until the rest of the
>> document was about done.
> I had hoped that we "were about done". Anyway, now they are pointed out,
> they may as well be fixed. And the syntax of msg-id is a serious matter.

True.

I was assuming that draft 15 would be the "all major issues resolved, start
work on the tidying up" draft. So I was going to look at its syntax section
in order to get it fixed in draft 16.

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:  +44 20 8371 1138
Internet Expert     | Home:  <clive at davros.org>  | Fax:  +44 20 8371 4037
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc            |                            |