Re: [media-types] Registration for multipart/multilingual type

[Gunnar Hellström <[e-mail]>]

Nik,

In the "Encoding Considerations", you mention ASCII. Why?

Reading RFC 6838 section 4.8, where the encoding considerations field is 
defined, only 7-bit, 8-bit, binary and framed are mentioned as possible 
values.

It seems that you just want to expess total freedom for encoding, so 
therefore I suggest that you replace "may contain ASCII or binary." with 
"may contain 7-bit, 8-bit or binary encodings".

(or mention all four if also "framed" is possible.  )

Regards

Gunnar


Den 2016-11-17 kl. 11:24, skrev Nik Tomkinson:
> The location of the latest/correct Internet Draft is this: 
> https://datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent
> On 17 November 2016 at 10:21, Nik Tomkinson 
> <[e-mail] <mailto:[e-mail]>> wrote:
>
>     Hello all,
>
>     I am going to be registering a new multipart
>     (multipart/multilingual) with IANA and want to run the
>     registration template past this group for final suggestions:
>
>        Media Type name: multipart
>
>        Media subtype name: multilingual
>
>        Required parameters: boundary (defined in RFC2046)
>
>        Optional parameters: N/A
>
>        Encoding considerations: There are no encoding considerations for
>            this multipart other than that of the embedded body parts.
>            The embedded body parts (typically one text/plain plus one or
>            more message/*) may contain ASCII or binary.
>
>        Security considerations: See the Security Considerations section
>                                 in this document
>
>        Interoperability considerations:
>            Existing systems that do not treat unknown multipart subtypes
>            as multipart/mixed might not correctly render a
>            multipart/multilingual type.
>
>        Published specification: This document
>
>        Applications that use this media type:
>            Mail Transfer Agents, Mail User Agents, spam detection,
>            virus detection modules and message authentication modules.
>
>        Additional information:
>            Deprecated alias names for this type: N/A
>            Magic number(s): N/A
>            File extension(s): N/A
>            Macintosh file type code(s): N/A
>
>        Person & email address to contact for further information:
>            Nik Tomkinson
>     [e-mail] <mailto:[e-mail]>
>
>            Nathaniel Borenstein
>     [e-mail] <mailto:[e-mail]>
>
>        Intended usage: Common
>
>     -- 
>     This relates to the following Internet Draft:
>
>     Multiple Language Content Type Internet Draft:
>
>     <http://datatracker.ietf.org/doc/draft-tomkinson-multilangcontent/>https://datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent/
>     <http://datatracker.ietf.org/doc/draft-tomkinson-slim-multilangcontent/>
>
>     The Internet Draft currently shows the template with the major
>     difference:
>
>        Encoding considerations: only "7bit", "8bit", or "binary" are
>                                 permitted
>
>     Thanks in advance for your suggestions,
>
>     Nik Tomkinson.
>
>
>
>
> -- 
> ----------------------------------------------------------------- 
> Multiple Language Content Type Internet Draft:
> <http://datatracker.ietf.org/doc/draft-tomkinson-multilangcontent/>https://datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent/ 
> <http://datatracker.ietf.org/doc/draft-tomkinson-slim-multilangcontent/>
> -----------------------------------------------------------------
>
>
> _______________________________________________
> media-types mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/media-types

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
[e-mail]
[phone]