lib/nntp-objects.html uses the term "article id"
several times.  This term is ambiguous though.  Either
"article number" or "message id" should be used.

Logged In: YES 
user_id=1014490

Same problem for the docstrings in the source file
Lib/nntplib.py.

Logged In: YES 
user_id=80475

Patches are welcome.  If you have a link to authoritive
guidance, that would be nice also.

Logged In: YES 
user_id=1014490

> Patches are welcome.

I don't have enough time (and I don't care enough) to write
a patch for this, currently.

> If you have a link to authoritive
> guidance, that would be nice also.

The only occurence of the case-insensitive regex
'article.id' in all RFCs is in RFC 977, which says:

223 n a article retrieved - request text separately
        (n = article number, a = unique article id)

(Here, it probably means message-id.)

There are frequent occurences of 'article number' and
'message-id' in the NNTP related RFCs 977 and 2980.

So 'article id' probably should be avoided, as it is
ambiguous.  (The docs sometimes use it in the sense of
'message-id' and sometimes as 'article number', from what I
could see.)

Logged In: YES 
user_id=1188172

Corrected in docs and docstrings as
Lib/nntplib.py r1.40, r1.39.2.1
Doc/lib/libnntplib.tex r1.33, r1.32.2.1