Re: [NNTP] Tr: Last Call: draft-elie-nntp-list-additions (Network News Transfer Protocol (NNTP) Additions to LIST Command) to Proposed Standard

Hi all,

Something I had planned to change but I forgot in draft -03:
    https://datatracker.ietf.org/doc/draft-elie-nntp-list-additions/

Section 3.2:

      [C] IHAVE <[email protected]>
      [S] 335 Send it; end with <CR-LF>.<CR-LF>
      [C] Path: demo!.POSTED.somewhere!not-for-mail
      [C] From: "Demo User" <[email protected]>
      [C] Newsgroups: misc.test
      [C] Subject: I am just a test article
      [C] Date: 18 Oct 2009 16:02:45 +0200
      [C] Organization: An example, Paris, FR.
      [C] Message-ID: <[email protected]>
      [C]
      [C] This is just a test article.
      [C] .
      [S] 235 Article transferred OK


      [C] POST
      [S] 340 Input article; end with <CR-LF>.<CR-LF>
      [C] From: "Demo User" <[email protected]>
      [C] Newsgroups: misc.test
      [C] Subject: I am just a test article
      [C]
      [C] This is just a test article.
      [C] .
      [S] 441 Newsgroup "misc.test" has been renamed to "foo.bar"


In both these examples, I will add the header field:

      [C] MIME-Version: 1.0



We had not had yet the discussion that occurred in January 2010
in the ietf-usefor mailing-list when I first wrote these
examples last year.

References:
    http://www.imc.org/ietf-usefor/mail-archive/msg04755.html
    http://www.imc.org/ietf-usefor/mail-archive/msg04759.html
    http://www.imc.org/ietf-usefor/mail-archive/msg04762.html


I believe that's OK to add this header field.  It is a very minor
change in the draft.
Better comply with RFC 5536 in the messages we post :-)
Best practice!

--=20
Julien =C9LIE

=AB First Guy (proudly):  "My wife's an angel!"
  Second Guy:  "You're lucky, mine's still alive." =BB