From nobody Thu Nov 17 02:11:14 2016 Return-Path: X-Original-To: slim@ietfa.amsl.com Delivered-To: slim@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4523F129875 for ; Thu, 17 Nov 2016 02:11:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shdO8rFv9fb2 for ; Thu, 17 Nov 2016 02:11:11 -0800 (PST) Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDBDB129872 for ; Thu, 17 Nov 2016 02:11:08 -0800 (PST) Received: by mail-qk0-x235.google.com with SMTP id n21so211865210qka.3 for ; Thu, 17 Nov 2016 02:11:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u9lZ3prKhsgCqtXgCIFKXd/tyE0Q/RyVqiDLWOdDAsc=; b=eRdUI4R27tZvFr4VDAoYREqitr34ERpLme4cYpXnvWloCGSGCONbswAD+6dThLSp21 XrGM6fKpx0NHtnH5PHi/Ujcn4isJ2Bvwry9ZO7JsOqJ+OgFt0m+aPVtXDyeAS3wC47Bm 0CDU8Fg3dzGLI1Vj+/06Xu6Q++X0ddM4WrOEcxURk0LE2NMAaPjW3nY0HgS7yJiqcg5p AwaxMnWPjTMNaD5dMHKEsiHelG5MUPDjkYB8qCscGofH3zM65oAgeoK/negoSAmlC2Ro gGQyQtuzXZ5lIEkk9zCtFxHtatjwphpFPFNycNxOoNfPl3yZmR2zlsXbx3e4Yca5bdMq RwIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u9lZ3prKhsgCqtXgCIFKXd/tyE0Q/RyVqiDLWOdDAsc=; b=HyJ8B9bQRSgqeQkaYg1CGI6awzSMGswkDdauBqbZXwOnuThEbm3NLcrH0B4eQPbfsw 3fuBUecAzBsShqUKgO6D87Bo3UwxGg+bJDRvFbwmH11pF7ka3Z1UDr4G3o6UcopDix1C p/S4+WEmJoumAJ2fRyzsjO7iuN51Ii5Mvc4Auip6H3UfQnlzoAikYtTyU50yqt3cmYoU Ava72b3zx9sVZIu1BrCYQODQSzGXL/m4ztj8HrrrzIrLaiDuAWvpyLJqemoIE2aSKp6+ KI6TaTA7TZyPytdRR40c+z4k/QSPJal5nrOKdpzcLW8qWeb28QpEuHcQgWZvfgOFRz2x hnWA== X-Gm-Message-State: AKaTC01cJEPVaMqEgZh4pQ0znMqvN+85aVo0OiuPVwPd9atJSAelHb9RZ/vhcWseX2AefAF3HOz855g2gcM4pQ== X-Received: by 10.55.19.224 with SMTP id 93mr2421037qkt.141.1479377468056; Thu, 17 Nov 2016 02:11:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.176.6 with HTTP; Thu, 17 Nov 2016 02:11:07 -0800 (PST) In-Reply-To: References: From: Nik Tomkinson Date: Thu, 17 Nov 2016 10:11:07 +0000 Message-ID: To: Randall Gellens Content-Type: multipart/alternative; boundary=001a114011ba78eee405417c68f1 Archived-At: Cc: slim@ietf.org, Bernard Aboba Subject: Re: [Slim] Resolution to Issue #19 X-BeenThere: slim@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Selection of Language for Internet Media List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 10:11:13 -0000 --001a114011ba78eee405417c68f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thanks Randall for that suggestion, I will post it to that group today with those suggested changes. Bernard, once I have some feedback from the media-types list, I can submit a new draft and close the ticket. Nik. On 25 October 2016 at 19:44, Randall Gellens wrote: > Please see in-line below for my suggestions. Also, please send a request > for review to the media-types list if you haven't already done so, and > include the full text of the registration template. > > At 10:41 AM -0700 10/25/16, Bernard Aboba wrote: > > Encoding considerations: ? >> > > I'd suggest something such as: > > There are no encoding considerations for this multipart other than that o= f > the embedded body parts. The embedded body parts (typically one text/plai= n > plus one or more message/*) may contain ASCII or binary. > > >> Security considerations: See the Security Considerations section in thi= s >> document >> >> Interoperability considerations: >> >> Existing systems that do not treat unknown multipart subtypes as >> multipart/mixed may not correctly render a >> multipart/multilingual type. >> > > I suggest changing "may not" to "might not" or "might fail to" since the > words "may not" are ambiguous in RFCs. > > >> Published specification: This document >> >> Applications that use this media type: >> Mail Transfer Agents, Mail User Agents, spam detection, virus detectio= n >> 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 >> =C3=90rfc.nik.tomkinson@gmail.com >> >> Nathaniel Borenstein =C3=90nsb@mimecast.com >> >> Intended usage: Common >> >> But I am not sure about the encoding considerations because the IANA >> 'Application for a Media Type' form at > a-types>=C3=90http://www.iana.org/form/media-types includes these option= s: >> >> 7-bit text >> 8-bit text (this media type may require encoding on transports not >> capable of handling 8-bit text) >> binary (this media type may require encoding on transports not capable >> of handling binary) >> but it also refers to RFC 6838 =C2= =A74.8 >> which lists: >> >> 7bit: The content of the media type consists solely of CRLF-delimited >> 7bit US-ASCII text. >> 8bit: The content of the media type consists solely of CRLF-delimited >> 8bit text. >> binary: The content consists of an unrestricted sequence of octets. >> I have seen from examples of other registered MIME types that the >> wording is not always the same as above but, given that there is a >> registration form with strict definitions, I am at a bit of a loss which= I >> should specify. >> >> Can anyone offer a suggestion? >> >> Thanks in advance, >> >> Nik. >> >> >> _______________________________________________ >> SLIM mailing list >> SLIM@ietf.org >> https://www.ietf.org/mailman/listinfo/slim >> > > > -- > Randall Gellens > Opinions are personal; facts are suspect; I speak for myself only > -------------- Randomly selected tag: --------------- > There is only one way to get rid of nuclear weapons -- use them. > --Rush Limbaugh > --=20 ----------------------------------------------------------------- Multiple Language Content Type Internet Draft: https://datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent/ ----------------------------------------------------------------- --001a114011ba78eee405417c68f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thanks Randall for that suggestion, I will post it to that= group today with those suggested changes.

Bernard, once= I have some feedback from the media-types list, I can submit a new draft a= nd close the ticket.

Nik.

On 25 October 2016 at 19:44, R= andall Gellens <rg+ietf@randy.pensive.org> wrote:
Please see in-line below for my suggestions= . Also, please send a request for review to the media-types list if you hav= en't already done so, and include the full text of the registration tem= plate.

At 10:41 AM -0700 10/25/16, Bernard Aboba wrote:

=C2=A0Encoding considerations: ?

I'd suggest something such as:

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.

=C2=A0Security considerations: See the Security Considerations section in t= his document

=C2=A0Interoperability considerations:

=C2=A0Existing systems that do not treat unknown multipart subtypes=C2=A0 a= s multipart/mixed may not correctly render a
=C2=A0multipart/multilingual type.

 I suggest changing "may not" to "might not" or "mi= ght fail to" since the words "may not" are ambiguous in RFCs= .


=C2=A0Published specification: This document

=C2=A0Applications that use this media type:
=C2=A0Mail Transfer Agents, Mail User Agents, spam detection,=C2=A0 virus d= etection modules and message authentication modules.

=C2=A0Additional information:

=C2=A0Deprecated alias names for this type: N/A
=C2=A0Magic number(s): N/A
=C2=A0File extension(s): N/A
=C2=A0Macintosh file type code(s): N/A

=C2=A0Person & email address to contact for further information:

=C2=A0Nik Tomkinson
 =C2=A0<mailto:rfc.nik.tomkinson@gmail.com>=C3=90rfc.nik.tomkinson@gmail.com=

=C2=A0Nathaniel Borenstein=C2=A0 <mailto:nsb@mimecast.com>=C3=90nsb@mimecast.com

=C2=A0Intended usage: Common

=C2=A0But I am not sure about the encoding considerations because the IANA = 'Application for a Media Type' form at <http://www.ia= na.org/form/media-types>=C3=90http://www.iana.org/form/media-types includes these options:

=C2=A07-bit text
=C2=A08-bit text (this media type may require encoding on transports not ca= pable of handling 8-bit text)
=C2=A0binary (this media type may require encoding on transports not capabl= e of handling binary)
 =C2=A0but it also refers to <http://tools.ietf.org/html/rf= c6838>RFC 6838 =C2=A74.8
=C2=A0which lists:

=C2=A07bit: The content of the media type consists solely of CRLF-delimited= 7bit US-ASCII text.
=C2=A08bit: The content of the media type consists solely of CRLF-delimited= 8bit text.
=C2=A0binary: The content consists of an unrestricted sequence of octets. =C2=A0I have seen from examples of other registered MIME types that the wor= ding is not always the same as above but, given that there is a registratio= n form with strict definitions, I am at a bit of a loss which I should spec= ify.

=C2=A0Can anyone offer a suggestion?

=C2=A0Thanks in advance,

=C2=A0Nik.


 =C2=A0_______________________________________________
=C2=A0SLIM mailing list
=C2=A0SLIM@ietf.org<= br> =C2=A0https://www.ietf.org/mailman/listinfo/slim<= span class=3D"HOEnZb">


--
Randall Gellens
Opinions are personal;=C2=A0 =C2=A0 facts are suspect;=C2=A0 =C2=A0 I speak= for myself only
-------------- Randomly selected tag: ---------------
There is only one way to get rid of nuclear weapons -- use them.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0--Rush Limbaugh



-- 
-------------------=
----------------------------------------------
Multiple Language Content=
 Type Internet Draft:
https://= datatracker.ietf.org/doc/draft-ietf-slim-multilangcontent/
-----------------------------=
------------------------------------
--001a114011ba78eee405417c68f1--