Review requests: application/news-* + message/news
Frank Ellermann
nobody at xyzzy.claranet.de
Thu Aug 28 09:41:52 CEST 2008
Hi, the USEFOR WG is about to finish
<http://tools.ietf.org/html/draft-ietf-usefor-usepro>
Section 4 of this draft -12 contains four MIME types:
message/news (OBSOLETE)
application/news-transmission (update)
application/news-groupinfo (new)
application/news-checkgroups (new)
See the registration templates below,
Frank
---
MIME type name: message
MIME subtype name: news
Required parameters: none
Optional parameters: charset, compare message/rfc822
Encoding considerations: compare message/rfc822 (RFC 2046)
Security considerations: OBSOLETE, use message/rfc822.
Interoperability considerations:
Rarely used; and therefore often
handled as application/octet-stream.
Disposition should by default be inline.
Published specification: [SON-OF-1036], RFCXXXX
Applications that use this media type:
Some old mail and news user agents.
Intended usage: OBSOLETE
Author: Henry Spencer
Change controller: IETF
---
MIME type name: application
MIME subtype name: news-transmission
Required parameters: none
Optional parameters: One and only one of "usage=moderate",
"usage=inject", or "usage=relay".
Encoding considerations: A transfer-encoding different from that
of the article transmitted MAY be
supplied to ensure correct transmission
over some 7bit transport medium.
Security considerations: A news article may be a control message,
which if processed could have effects on
the recipient host's system beyond just
storage of the article.
Published specification: RFCXXXX
Body part: A complete proto-article ready for
injection into Netnews or an article
being relayed to another agent.
Applications that use this media type:
Injecting agents, Netnews moderators.
Intended usage: COMMON
Change controller: IETF
---
MIME type name: application
MIME subtype name: news-groupinfo
Required parameters: none
Optional parameters: charset, which MUST be a charset
registered for use with MIME text types
and has the same syntax as the parameter
defined for text/plain [RFC2046].
Specifies the charset of the body part.
If not given, the charset defaults to
US-ASCII [ASCII].
Encoding considerations: 7bit or 8bit MUST be used to maintain
compatibility.
Security considerations: None.
Interoperability considerations:
Disposition should by default be inline.
Applications that use this media type:
Control message issuers, relaying
agents, serving agents.
Published specification: RFCXXXX
Intended usage: COMMON
Change controller: IETF
---
MIME type name: application
MIME subtype name: news-checkgroups
Required parameters: none
Optional parameters: charset, which MUST be a charset
registered for use with MIME text types
and has the same syntax as the parameter
defined for text/plain [RFC2046].
Specifies the charset of the body part.
If not given, the charset defaults to
US-ASCII [ASCII].
Encoding considerations: 7bit or 8bit MUST be used to maintain
compatibility.
Security considerations: This media type provides only a means
for conveying a list of newsgroups and
does not provide any information
indicating whether the sender is
authorized to state which newsgroups
should exist within a hierarchy. Such
authorization must be accomplished by
other means.
Interoperability considerations:
Disposition should by default be inline.
Applications that use this media type:
Control message issuers, relaying
agents, serving agents.
Published specification: RFCXXXX
Intended usage: COMMON
Change controller: IETF
---
More information about the Ietf-types
mailing list