news-message-ID review request
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
* Frank Ellermann wrote:
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>.
I think the terminology here is very confusing, you are writing about an Internet Media Type but never mention that. As I read RFC 4288, it isn't possible to remove a media type from the registry, and it seems you are simply saying there is an error in the registry. In that case it seems more appropriate to have IANA fix the registry without going through the standards process. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Bjoern Hoehrmann wrote:
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>.
I think the terminology here is very confusing, you are writing aboutn an Internet Media Type but never mention that.
I'm writing about an "access type" apparently registered under the rules in RFC 1341 appendix F.3. For unknown reasons that's now erroneously listed as an application subtype.
it seems you are simply saying there is an error in the registry.
Yes.
it seems more appropriate to have IANA fix the registry without going through the standards process.
Maybe I could claim that "RFC to be" was good enough 1993 for RFC 1341. But I guess it's more straight forward to have a proper RFC as spec. in the registry, instead of the pointer to RFC 1036 (which doesn't contain any MIME access types or media types) + mailto Henry Spencer link. RFC 4289 demands that anyway for "new" access-types, or actually for "all" access types minus this one grandfathered exception. It also fits into the context of news URLs. Frank
participants (2)
-
Bjoern Hoehrmann -
Frank Ellermann