news-message-ID review request

[Frank Ellermann]

Hi, the following is probably (I'm new to this list) unusual, it will be
published in the "IANA considerations" of I-D.ellermann-news-nntp-uri-05,
see <http://purl.net/xyzzy/home/test/draft-ellermann-news-nntp-uri-05.txt>

~~~ cut ~~~
8.3.  'news-message-ID' access type

   The MIME 'news-message-ID' access type was erroneously listed as
   subtype.  IANA should remove 'news-message-ID' from the application
   subtype registry, and add it to the access type registry defined in
   [RFC4289]: <http://www.iana.org/assignments/access-types>.

   [RFC4289] requires an RFC for the access types registry.  Because
   [son-of-1036] was never published as RFC the following paragraph
   quotes the relevant definition:

      NOTE: In the specific case where it is desired to essentially make
      another article PART of the current one, e.g. for annotation of
      the other article, MIME's "message/external-body" convention can
      be used to do so without actual inclusion. "news-message-ID" was
      registered as a standard external-body access method, with a
      mandatory NAME parameter giving the message ID and an optional
      SITE parameter suggesting an NNTP site that might have the article
      available (if it is not available locally), by IANA 22 June 1993.

   Please note that 'news' URLs offer a very similar and (today) more
   common way to access articles by their Message-ID, compare [RFC2017].

~~~ end ~~~

Is that good enough to fix this (very old, 1993) mess ?

Frank