draft-ietf-nntpext-imp: Ambiguities in description of XHDR

[Jonathan I. Kamens]

The section about XHDR in draft-ietf-nntpext-imp-00.txt is vague, in
that it doesn't specify the exact format of the data returned by the
server.  That is, it doesn't say anywhere, "Each line of the data
returned by the server has an article number (or message ID, if a
message ID was specified in the command), then whitespace, then the
value of the requested header in that article."  At least not as far
as I can tell.

It also doesn't mention that many servers sometimes return "(none)",
so clients need to check for that.

Finally, it doesn't specify whether the server can return multi-line
headers as multi-line responses with lines after the first indented to
show continuation.  Until recently, no server ever did that, but
Microsoft went ahead and did it in their server, and I would like a
standards document to specify that they shouldn't be doing it so that
I can bash them over the head with it and refuse to support their
brokenness in my News reader. :-)

Jonathan Kamens