Charset in newgroup sample

Hi,

In the sample of newgroup control message:

      Control: newgroup example.admin.info moderated
      MIME-Version: 1.0
      Content-Type: multipart/mixed; boundary="nxtprt"
      Content-Transfer-Encoding: 8bit

      This is a MIME control message.
      --nxtprt
      Content-Type: application/news-groupinfo

      For your newsgroups file:
      example.admin.info      About the example.* groups (Moderated)

      --nxtprt
      Content-Type: text/plain

      A moderated newsgroup for announcements about new newsgroups in
      the example.* hierarchy.

      --nxtprt--

wouldn't it be better to put the charsets in order to highlight the
fact they are useful (though it is said the default is US-ASCII)?
I fear people might still forget it...

      Content-Type: multipart/mixed; boundary="nxtprt"; charset=us-ascii
      Content-Type: application/news-groupinfo; charset=us-ascii
      Content-Type: text/plain; charset=us-ascii

or another one if you want (iso-8858-1 and utf-8 are also fine for instance
but RFC 2046 states it SHOULD be the lowest common denominator us-ascii,
enough for that sample).

Why mention the charset?  RFC 2046 also states:

   In order to eliminate such ambiguity and variations in the
   future, it is strongly recommended that new user agents explicitly
   specify a character set as a media type parameter in the Content-Type
   header field.



In our case, the most important is the second one.  Incidentally,
I wonder what happens when the first one is defined to utf-8 and
the second one is undefined.  Is it utf-8 (out of transitivity)
or us-ascii?

-- 
Julien ÉLIE

« Plus un ordinateur possède de RAM, plus vite il peut générer un message d'erreur. »