[ietf-nntp] Re: OVER message-id

[Clive D.W. Feather]

I wrote:
> At some point we put "OVER message-id" back into the protocol.
> 
> Andrew from Supernews is objecting to this, saying that it's impractical
> in "every major server design".

In the absence of any further discussion, I have added text to make this
optional, with response code 503 if unsupported.

> For the same technical reasons, he suggests that:
> 
>     HDR Xref <message-id>
>     HDR :lines <message-id>
> 
> may be problematical.

Again, in the absence of further discussion, I've added wording to HDR to
allow it to have different lists of available headers/metadata for the
message-id and article number versions. I've also added an optional MSGID
parameter to LIST HEADERS, indicating that the former rather than the
latter list should be returned.

If people are seriously unhappy with this latter change, I'll provide my
wording [*] and we can discuss it further. But there seems to have been
silence for weeks now.

[*] I am planning to produce a pre-release draft 21 as soon as we've nailed
down the issues from public review. Hopefully that will be sometime next
week.

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <clive at davros.org>  | *** NOTE CHANGE ***
Demon Internet      | WWW: http://www.davros.org | Fax:    +44 870 051 9937
Thus plc            |                            | Mobile: +44 7973 377646