draft-ietf-slim-multilangcontent-06.txt   draft-ietf-slim-multilangcontent-07.txt 
IETF N. Tomkinson IETF N. Tomkinson
Internet-Draft N. Borenstein Internet-Draft N. Borenstein
Intended status: Standards Track Mimecast Ltd Intended status: Standards Track Mimecast Ltd
Expires: April 15, 2017 October 12, 2016 Expires: November 5, 2017 May 4, 2017
Multiple Language Content Type Multiple Language Content Type
draft-ietf-slim-multilangcontent-06 draft-ietf-slim-multilangcontent-07
Abstract Abstract
This document defines an addition to the Multipurpose Internet Mail This document defines an addition to the Multipurpose Internet Mail
Extensions (MIME) standard to make it possible to send one message Extensions (MIME) standard to make it possible to send one message
that contains multiple language versions of the same information. that contains multiple language versions of the same information.
The translations would be identified by a language tag and selected The translations would be identified by a language tag and selected
by the email client based on a user's language settings. by the email client based on a user's language settings.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 15, 2017. This Internet-Draft will expire on November 5, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 7, line 17 skipping to change at page 7, line 17
8. Examples 8. Examples
8.1. An Example of a Simple Multiple language email message 8.1. An Example of a Simple Multiple language email message
Below is a minimal example of a multiple language email message. It Below is a minimal example of a multiple language email message. It
has the multilingual preface and two language message parts. has the multilingual preface and two language message parts.
From: Nik@example.com From: Nik@example.com
To: Nathaniel@example.com To: Nathaniel@example.com
Subject: Example of a message in Spanish and English Subject: Example of a message in Spanish and English
Date: Thu, 7 Jul 2016 21:28:00 +0100 Date: Thu, 7 Apr 2017 21:28:00 +0100
MIME-Version: 1.0 MIME-Version: 1.0
Content-Type: multipart/multilingual; Content-Type: multipart/multilingual;
boundary="01189998819991197253" boundary="01189998819991197253"
--01189998819991197253 --01189998819991197253
Content-Type: text/plain; charset="UTF-8" Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable
This is a message in multiple languages. It says the This is a message in multiple languages. It says the
skipping to change at page 8, line 28 skipping to change at page 8, line 28
8.2. An Example of a Multiple language email message with language 8.2. An Example of a Multiple language email message with language
independent part independent part
Below is an example of a multiple language email message that has the Below is an example of a multiple language email message that has the
multilingual preface followed by two language message parts and then multilingual preface followed by two language message parts and then
a language independent png image. a language independent png image.
From: Nik@example.com From: Nik@example.com
To: Nathaniel@example.com To: Nathaniel@example.com
Subject: Example of a message in Spanish and English Subject: Example of a message in Spanish and English
Date: Thu, 7 Jul 2016 21:08:00 +0100 Date: Thu, 7 Apr 2017 21:08:00 +0100
MIME-Version: 1.0 MIME-Version: 1.0
Content-Type: multipart/multilingual; Content-Type: multipart/multilingual;
boundary="01189998819991197253" boundary="01189998819991197253"
--01189998819991197253 --01189998819991197253
Content-Type: text/plain; charset="UTF-8" Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable
This is a message in multiple languages. It says the This is a message in multiple languages. It says the
skipping to change at page 10, line 16 skipping to change at page 10, line 16
Below is an example of a more complex multiple language email Below is an example of a more complex multiple language email
message. It has the multilingual preface and two language message message. It has the multilingual preface and two language message
parts and then a language independent png image. The language parts and then a language independent png image. The language
message parts have multipart/alternative contents and would therefore message parts have multipart/alternative contents and would therefore
require further processing to determine the content to display. require further processing to determine the content to display.
From: Nik@example.com From: Nik@example.com
To: Nathaniel@example.com To: Nathaniel@example.com
Subject: Example of a message in Spanish and English Subject: Example of a message in Spanish and English
Date: Thu, 7 Jul 2016 20:55:00 +0100 Date: Thu, 7 Apr 2017 20:55:00 +0100
MIME-Version: 1.0 MIME-Version: 1.0
Content-Type: multipart/multilingual; Content-Type: multipart/multilingual;
boundary="01189998819991197253" boundary="01189998819991197253"
--01189998819991197253 --01189998819991197253
Content-Type: text/plain; charset="UTF-8" Content-Type: text/plain; charset="UTF-8"
Content-Disposition: inline Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable Content-Transfer-Encoding: quoted-printable
This is a message in multiple languages. It says the This is a message in multiple languages. It says the
skipping to change at page 14, line 47 skipping to change at page 14, line 47
slim-multilangcontent-06 slim-multilangcontent-06
o Changed parameter Translation-Type back to a new field to reduce o Changed parameter Translation-Type back to a new field to reduce
the risk of breaking existing implementations that don't expect the risk of breaking existing implementations that don't expect
any parameters on Content-Language. any parameters on Content-Language.
o Improved the IANA Considerations section to include the full o Improved the IANA Considerations section to include the full
registration template for the multipart/multilingual type and the registration template for the multipart/multilingual type and the
new Translation-Type field. new Translation-Type field.
9.11. Changes from draft-ietf-slim-multilangcontent-06 to draft-ietf-
slim-multilangcontent-07
o Updated the Encoding Considerations in the IANA Registration
Template.
10. Acknowledgements 10. Acknowledgements
The authors are grateful for the helpful input received from many The authors are grateful for the helpful input received from many
people but would especially like to acknowledge the help of Harald people but would especially like to acknowledge the help of Harald
Alvestrand, Stephane Bortzmeyer, Eric Burger, Mark Davis, Doug Ewell, Alvestrand, Stephane Bortzmeyer, Eric Burger, Mark Davis, Doug Ewell,
Randall Gellens, Gunnar Hellstrom, Barry Leiba, Sean Leonard, John Randall Gellens, Gunnar Hellstrom, Barry Leiba, Sean Leonard, John
Levine, Alexey Melnikov, Addison Phillips, Julian Reschke, Pete Levine, Alexey Melnikov, Addison Phillips, Julian Reschke, Pete
Resnick, Brian Rosen, Fiona Tomkinson, Simon Tyler and Daniel Vargha. Resnick, Brian Rosen, Fiona Tomkinson, Simon Tyler and Daniel Vargha.
The authors would also like to thank Fernando Alvaro and Luis de The authors would also like to thank Fernando Alvaro and Luis de
skipping to change at page 16, line 13 skipping to change at page 16, line 13
template: template:
Media Type name: multipart Media Type name: multipart
Media subtype name: multilingual Media subtype name: multilingual
Required parameters: boundary (defined in RFC2046) Required parameters: boundary (defined in RFC2046)
Optional parameters: N/A Optional parameters: N/A
Encoding considerations: only "7bit", "8bit", or "binary" are Encoding considerations: There are no encoding considerations for
permitted 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 7-bit, 8-bit or binary encodings.
Security considerations: See the Security Considerations section Security considerations: See the Security Considerations section
in this document in this document
Interoperability considerations: Interoperability considerations:
Existing systems that do not treat unknown multipart subtypes Existing systems that do not treat unknown multipart subtypes
as multipart/mixed may not correctly render a as multipart/mixed may not correctly render a
multipart/multilingual type. multipart/multilingual type.
Published specification: This document Published specification: This document
 End of changes. 9 change blocks. 
9 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/