[Slim] Resolution to Issue #19
Bernard Aboba <bernard.aboba@gmail.com> Tue, 25 October 2016 17:41 UTC
Return-Path: <bernard.aboba@gmail.com>
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 F3F4C129863 for <slim@ietfa.amsl.com>; Tue, 25 Oct 2016 10:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level:
X-Spam-Status: No, score=-0.989 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=no 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 6lpQU4VHPL9y for <slim@ietfa.amsl.com>; Tue, 25 Oct 2016 10:41:24 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 5A91C12954C for <slim@ietf.org>; Tue, 25 Oct 2016 10:41:24 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id m11so60787223uab.3 for <slim@ietf.org>; Tue, 25 Oct 2016 10:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=eFeicTPpRct1eKI6zIYbzIwT54kdJ8JhV6ZOb0qbydc=; b=Ty80vMsnf0TEDrZM2z8ch7U3R+g0h1TgWXv9jr6EXlVW1+YiHWYZKpvy8Yr7s6XRH5 Z6Woia+HTyxsXPNrG48AP02nhozoU8Ec3s4cMT+zz7MRyoCxsBmydILutNaG4OKl1DPg KH1p64AsOX1OXU6u60dpBKc5/ffF2Sbos7+JCQ3N1OuNsNqw0HdTbrPQOLQWnbrApekT pPoUM8uusznGILViHlH+DKHYjfFqsRLo79iTnqi+vQJ10lNs1umiYDw3cx6tNPHyrC1g b/xllX5cNacphx49VzSQhzkqOGalm2VZ/y7P/aA7ukhFkgIC2j1hlOdPNSKI8SYKAcuq fb+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=eFeicTPpRct1eKI6zIYbzIwT54kdJ8JhV6ZOb0qbydc=; b=ckPqVgLiDVT2bij/JSOyfA7SC8G6kjJO+3Yu9Vg6myFcGziiqas08+FOUuBKXv29Me 6KMFzBlYhg1m6iLQ1PUY5MHTaZ7304GV14dIa0W9R9FjOyAXMVpUUMOOxCOlMoIRGN+6 M1Ab8kXZmXCBW+d5kuWEt29VfrmUCmEX4TUMgqDJ8ZwRXuy4EBFpM306zZncrFGexqgU MPGs7JsBImecPIlBLCKEJIRZakWsQ12FOWuxxgdCmzx0/bRiWoSSA/BMfllan1GFAuxv vYzXPK/I4GaP97fn1D6f3E6HsNT0+/9A+zFNChp28K6y/lOwiV4sgloiKd/HOiodRHsu U/8A==
X-Gm-Message-State: ABUngvdBckclhhFFuInzrVsYIk+WTQZoF+K5k8InPngno4Gs3rvXDp+5Ef8JLRLbsiK8iDMjLC1yb1Z95pRaJw==
X-Received: by 10.176.66.103 with SMTP id i94mr13308599uai.166.1477417282991; Tue, 25 Oct 2016 10:41:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.16.88 with HTTP; Tue, 25 Oct 2016 10:41:02 -0700 (PDT)
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 25 Oct 2016 10:41:02 -0700
Message-ID: <CAOW+2dtHqnby7zzSxtymquERK9kCji=Nia0nat5QA-sa4GC==g@mail.gmail.com>
To: slim@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c05f262567d90053fb40464"
Archived-At: <https://mailarchive.ietf.org/arch/msg/slim/sJo9d8VrvBkvbcGKPbmjWu_EfrU>
Subject: [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 <slim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/slim>, <mailto:slim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/slim/>
List-Post: <mailto:slim@ietf.org>
List-Help: <mailto:slim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/slim>, <mailto:slim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2016 17:41:31 -0000
Ticket #19 relates to the template included in Section 11.1 of https://trac.tools.ietf.org/wg/slim/trac/ticket/19 Nik - Does the latest update ( https://tools.ietf.org/html/draft-ietf-slim-multilangcontent-06) resolve this issue? Bernard ===================================== Text of Issue 19 am working on this template but I need some advice from anyone who knows this sort of this thing well and has experience in this area. My initial suggestion would be: Media Type name: multipart Media subtype name: multilingual Required parameters: boundary (defined in RFC2046 <http://tools.ietf.org/html/rfc2046>) Optional parameters: N/A Encoding considerations: ? Security considerations: See the Security Considerations section in this document Interoperability considerations: Existing systems that do not treat unknown multipart subtypes as multipart/mixed may 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 rfc.nik.tomkinson@gmail.com Nathaniel Borenstein nsb@mimecast.com Intended usage: Common But I am not sure about the encoding considerations because the IANA 'Application for a Media Type' form at http://www.iana.org/form/media-types includes these options: - 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 <http://tools.ietf.org/html/rfc6838> §4.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] Resolution to Issue #19 Bernard Aboba
- Re: [Slim] Resolution to Issue #19 Randall Gellens
- Re: [Slim] Resolution to Issue #19 Nik Tomkinson