draft-ietf-slim-multilangcontent-13.txt   draft-ietf-slim-multilangcontent-14.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: February 12, 2018 August 11, 2017 Expires: February 19, 2018 August 18, 2017
Multiple Language Content Type Multiple Language Content Type
draft-ietf-slim-multilangcontent-13 draft-ietf-slim-multilangcontent-14
Abstract Abstract
This document defines an addition to the Multipurpose Internet Mail This document defines the multipart/multilingual content type, which
Extensions (MIME) standard to make it possible to send one message is an addition to the Multipurpose Internet Mail Extensions (MIME)
that contains multiple language versions of the same information. standard to make it possible to send one message that contains
The translations would be identified by a language tag and selected multiple language versions of the same information. The translations
by the email client based on a user's language settings. would be identified by a language tag and selected by the email
client based on a user's language settings.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 February 12, 2018. This Internet-Draft will expire on February 19, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. The Content-Type Header Field . . . . . . . . . . . . . . . . 3
3. The Message Parts . . . . . . . . . . . . . . . . . . . . . . 3
3.1. The Multilingual Preface . . . . . . . . . . . . . . . . 4
3.2. The Language Message Parts . . . . . . . . . . . . . . . 5
3.3. The Language Independent Message Part . . . . . . . . . . 5
4. Message Part Selection . . . . . . . . . . . . . . . . . . . 5
5. The Content-Language Field . . . . . . . . . . . . . . . . . 6
6. The Content-Translation-Type Field . . . . . . . . . . . . . 7
7. The Subject Field in the Language Message parts . . . . . . . 7
8. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. An Example of a Simple Multiple language email message . 8
8.2. An Example of a Multiple language email message with
language independent part . . . . . . . . . . . . . . . . 9
8.3. An Example of a complex Multiple language email message
with language independent part . . . . . . . . . . . . . 11
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
10.1. The multipart/multilingual MIME type . . . . . . . . . . 13
10.2. The Content-Translation-Type Field . . . . . . . . . . . 15
10.3. The Content-Translation-Type Field Values . . . . . . . 15
11. Security Considerations . . . . . . . . . . . . . . . . . . . 16
12. Changes from Previous Versions . . . . . . . . . . . . . . . 16
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
13.1. Normative References . . . . . . . . . . . . . . . . . . 21
13.2. Informational References . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
Since the invention of email and the rapid spread of the Internet, Since the invention of email and the rapid spread of the Internet,
more and more people have been able to communicate in more and more more and more people have been able to communicate in more and more
countries and in more and more languages. But during this time of countries and in more and more languages. But during this time of
technological evolution, email has remained a single-language technological evolution, email has remained a single-language
communication tool, whether it is English to English, Spanish to communication tool, whether it is English to English, Spanish to
Spanish or Japanese to Japanese. Spanish or Japanese to Japanese.
Also during this time, many corporations have established their Also during this time, many corporations have established their
offices in multi-cultural cities and formed departments and teams offices in multi-cultural cities and formed departments and teams
that span continents, cultures and languages, so the need to that span continents, cultures and languages, so the need to
communicate efficiently with little margin for miscommunication has communicate efficiently with little margin for miscommunication has
grown significantly. grown significantly.
The objective of this document is to define an addition to the This document defines the multipart/multilingual content type, which
Multipurpose Internet Mail Extensions (MIME) standard, to make it is an addition to the Multipurpose Internet Mail Extensions (MIME)
possible to send a single message to a group of people in such a way standard, to make it possible to send a single message to a group of
that all of the recipients can read the email in their preferred people in such a way that all of the recipients can read the email in
language. The methods of translation of the message content are their preferred language. The methods of translation of the message
beyond the scope of this document, but the structure of the email content are beyond the scope of this document, but the structure of
itself is defined herein. the email itself is defined herein.
Whilst this document depends on identification of language in message Whilst this document depends on identification of language in message
parts for non-real-time communication, there is a companion document parts for non-real-time communication, there is a companion document
that is concerned with a similar problem for real-time communication: that is concerned with a similar problem for real-time communication:
[I-D.ietf-slim-negotiating-human-language] [I-D.ietf-slim-negotiating-human-language]
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 4, line 34 skipping to change at page 5, line 21
constitute the default part when language negotiation fails and there constitute the default part when language negotiation fails and there
is no Language Independent part. All of the language message parts is no Language Independent part. All of the language message parts
MUST have a Content-Language field and a Content-Type field and MAY MUST have a Content-Language field and a Content-Type field and MAY
have a Content-Translation-Type field. have a Content-Translation-Type field.
The Content-Type for each individual language message part SHOULD be The Content-Type for each individual language message part SHOULD be
message/rfc822 to provide good support with non-conforming email message/rfc822 to provide good support with non-conforming email
clients. However, an implementation MAY use message/global as clients. However, an implementation MAY use message/global as
support for message/global becomes more commonplace. See RFC 6532 support for message/global becomes more commonplace. See RFC 6532
[RFC6532] for details of message/global. Each language message part [RFC6532] for details of message/global. Each language message part
SHOULD have a Subject field in the appropriate language for that should have a Subject field in the appropriate language for that
language part. If there is a From field present, its value MUST language part. If there is a From field present, its value MUST
include the same email address as the top-level From header although include the same email address as the top-level From header although
the display name MAY be a localised version. the display name MAY be a localised version. If there is a mismatch
of sender email address, the top-level From header value SHOULD be
used to show to the recipient.
3.3. The Language Independent Message Part 3.3. The Language Independent Message Part
If there is language independent content intended for the recipient If there is language independent content for the recipient to see if
to see if they have a preferred language other than one of those they have a preferred language other than one of those specified in
specified in the language message parts and the default language the language message parts and the default language message part is
message part is unlikely to be understood, another part MAY be unlikely to be understood, another part MAY be provided. This part
provided. This could typically include a language independent could typically include one or more language independent graphics.
graphic. When this part is present, it MUST be the last part and When this part is present, it MUST be the last part and MUST have a
MUST have a Content-Language field with a value of "zxx" (as Content-Language field with a value of "zxx" (as described in BCP 47/
described in BCP 47/RFC 5646 [RFC5646]). The part SHOULD have a RFC 5646 [RFC5646]). The part SHOULD have a Content-Type of message/
Content-Type of message/rfc822 or message/global (to match the rfc822 or message/global (to match the language message parts).
language message parts).
4. Message Part Selection 4. Message Part Selection
The logic for selecting the message part to render and present to the The logic for selecting the message part to render and present to the
recipient is summarised in the next few paragraphs. recipient is summarised in the next few paragraphs.
Firstly, if the email client does not understand multipart/ Firstly, if the email client does not understand multipart/
multilingual then it will treat the message as if it was multipart/ multilingual then it will treat the message as if it was multipart/
mixed and render message parts accordingly (in accordance with mixed and render message parts accordingly (in accordance with
sections 5.1.3 and 5.1.7 of RFC 2046 [RFC2046]). sections 5.1.3 and 5.1.7 of RFC 2046 [RFC2046]).
skipping to change at page 5, line 37 skipping to change at page 6, line 23
If there is no match for the user's preferred language (or there is If there is no match for the user's preferred language (or there is
no preferred language information available) the email client SHOULD no preferred language information available) the email client SHOULD
select the language independent part (if one exists) or the first select the language independent part (if one exists) or the first
language part (directly after the multilingual preface) if a language language part (directly after the multilingual preface) if a language
independent part does not exist. independent part does not exist.
If there is no translation type preference information available, the If there is no translation type preference information available, the
values of the Content-Translation-Type field may be ignored. values of the Content-Translation-Type field may be ignored.
Additionally, interactive implementations MAY offer the user a choice Additionally, interactive implementations MAY offer the user a choice
from among the available languages. from among the available languages or the option to see them all.
5. The Content-Language Field 5. The Content-Language Field
The Content-Language field in the individual language message parts The Content-Language field in the individual language message parts
is used to identify the language in which the message part is is used to identify the language in which the message part is
written. Based on the value of this field, a conforming email client written. Based on the value of this field, a conforming email client
can determine which message part to display (given the user's can determine which message part to display (given the user's
language settings). language settings).
The Content-Language MUST comply with RFC 3282 [RFC3282] (which The Content-Language MUST comply with RFC 3282 [RFC3282] (which
defines the Content-Language field) and BCP 47/RFC 5646 [RFC5646] defines the Content-Language field) and BCP 47/RFC 5646 [RFC5646]
(which defines the structure and semantics for the language code (which defines the structure and semantics for the language tag
values). values).
Examples of this field for English, German and an instruction manual Examples of this field could look like the following:
in Spanish and French, could look like the following:
Content-Language: en Content-Language: en-GB
Content-Language: de Content-Language: de
Content-Language: es, fr Content-Language: es-MX, fr
Content-Language: sr-Cyrl
6. The Content-Translation-Type Field 6. The Content-Translation-Type Field
The Content-Translation-Type field can be used in the individual The Content-Translation-Type field can be used in the individual
language message parts to identify the type of translation. Based on language message parts to identify the type of translation. Based on
the value of this parameter and the user's preferences, a conforming the value of this parameter and the user's preferences, a conforming
email client can determine which message part to display. email client can determine which message part to display.
This field can have one of three possible values: 'original', 'human' This field can have one of three possible values: 'original', 'human'
or 'automated' although other values may be added in the future. A or 'automated' although other values may be added in the future. A
skipping to change at page 7, line 22 skipping to change at page 8, line 14
US-ASCII and 'encoded-word' examples of this field include: US-ASCII and 'encoded-word' examples of this field include:
Subject: A really simple email subject Subject: A really simple email subject
Subject: =?UTF-8?Q?Un_asunto_de_correo_electr=C3=b3nico_ Subject: =?UTF-8?Q?Un_asunto_de_correo_electr=C3=b3nico_
realmente_sencillo?= realmente_sencillo?=
See RFC 2047 [RFC2047] for the specification of 'encoded-word'. See RFC 2047 [RFC2047] for the specification of 'encoded-word'.
The subject to be presented to the recipient should be selected from The subject to be presented to the recipient SHOULD be selected from
the message part identified during the message part selection stage. the message part identified during the message part selection stage.
If no Subject field is found the top-level Subject header field value If no Subject field is found the top-level Subject header field value
should be used. should be used.
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.
skipping to change at page 8, line 10 skipping to change at page 8, line 51
you can ignore the other translations. The other translations may be you can ignore the other translations. The other translations may be
presented as attachments or grouped together. presented as attachments or grouped together.
Este es un mensaje en varios idiomas. Dice lo mismo en Este es un mensaje en varios idiomas. Dice lo mismo en
cada idioma. Si puede leerlo en un idioma, puede ignorar las otras cada idioma. Si puede leerlo en un idioma, puede ignorar las otras
traducciones. Las otras traducciones pueden presentarse como archivos traducciones. Las otras traducciones pueden presentarse como archivos
adjuntos o agrupados. adjuntos o agrupados.
--01189998819991197253 --01189998819991197253
Content-Type: message/rfc822 Content-Type: message/rfc822
Content-Language: en Content-Language: en-GB
Content-Translation-Type: original Content-Translation-Type: original
Content-Disposition: inline Content-Disposition: inline
Subject: Example of a message in Spanish and English Subject: Example of a message in Spanish and English
Content-Type: text/plain; charset="US-ASCII" Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 MIME-Version: 1.0
Hello, this message content is provided in your language. Hello, this message content is provided in your language.
--01189998819991197253 --01189998819991197253
Content-Type: message/rfc822 Content-Type: message/rfc822
Content-Language: es Content-Language: es-ES
Content-Translation-Type: human Content-Translation-Type: human
Content-Disposition: inline Content-Disposition: inline
Subject: =?UTF-8?Q?Ejemplo_pr=C3=A1ctico_de_mensaje_?= Subject: =?UTF-8?Q?Ejemplo_pr=C3=A1ctico_de_mensaje_?=
=?UTF-8?Q?en_espa=C3=B1ol_e_ingl=C3=A9s?= =?UTF-8?Q?en_espa=C3=B1ol_e_ingl=C3=A9s?=
Content-Type: text/plain; charset="US-ASCII" Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 MIME-Version: 1.0
Hola, el contenido de este mensaje esta disponible en su idioma. Hola, el contenido de este mensaje esta disponible en su idioma.
skipping to change at page 9, line 22 skipping to change at page 10, line 13
you can ignore the other translations. The other translations may be you can ignore the other translations. The other translations may be
presented as attachments or grouped together. presented as attachments or grouped together.
Este es un mensaje en varios idiomas. Dice lo mismo en Este es un mensaje en varios idiomas. Dice lo mismo en
cada idioma. Si puede leerlo en un idioma, puede ignorar las otras cada idioma. Si puede leerlo en un idioma, puede ignorar las otras
traducciones. Las otras traducciones pueden presentarse como archivos traducciones. Las otras traducciones pueden presentarse como archivos
adjuntos o agrupados. adjuntos o agrupados.
--01189998819991197253 --01189998819991197253
Content-Type: message/rfc822 Content-Type: message/rfc822
Content-Language: en Content-Language: en-GB
Content-Translation-Type: original Content-Translation-Type: original
Content-Disposition: inline Content-Disposition: inline
Subject: Example of a message in Spanish and English Subject: Example of a message in Spanish and English
Content-Type: text/plain; charset="US-ASCII" Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 MIME-Version: 1.0
Hello, this message content is provided in your language. Hello, this message content is provided in your language.
--01189998819991197253 --01189998819991197253
Content-Type: message/rfc822 Content-Type: message/rfc822
Content-Language: es Content-Language: es-ES
Content-Translation-Type: human Content-Translation-Type: human
Content-Disposition: inline Content-Disposition: inline
Subject: =?UTF-8?Q?Ejemplo_pr=C3=A1ctico_de_mensaje_?= Subject: =?UTF-8?Q?Ejemplo_pr=C3=A1ctico_de_mensaje_?=
=?UTF-8?Q?en_espa=C3=B1ol_e_ingl=C3=A9s?= =?UTF-8?Q?en_espa=C3=B1ol_e_ingl=C3=A9s?=
Content-Type: text/plain; charset="US-ASCII" Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 MIME-Version: 1.0
Hola, el contenido de este mensaje esta disponible en su idioma. Hola, el contenido de este mensaje esta disponible en su idioma.
skipping to change at page 10, line 46 skipping to change at page 11, line 38
you can ignore the other translations. The other translations may be you can ignore the other translations. The other translations may be
presented as attachments or grouped together. presented as attachments or grouped together.
Este es un mensaje en varios idiomas. Dice lo mismo en Este es un mensaje en varios idiomas. Dice lo mismo en
cada idioma. Si puede leerlo en un idioma, puede ignorar las otras cada idioma. Si puede leerlo en un idioma, puede ignorar las otras
traducciones. Las otras traducciones pueden presentarse como archivos traducciones. Las otras traducciones pueden presentarse como archivos
adjuntos o agrupados. adjuntos o agrupados.
--01189998819991197253 --01189998819991197253
Content-Type: message/rfc822 Content-Type: message/rfc822
Content-Language: en Content-Language: en-GB
Content-Translation-Type: original Content-Translation-Type: original
Content-Disposition: inline Content-Disposition: inline
Subject: Example of a message in Spanish and English Subject: Example of a message in Spanish and English
Content-Type: multipart/alternative; Content-Type: multipart/alternative;
boundary="72530118999911999881"; charset="US-ASCII" boundary="72530118999911999881"; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 MIME-Version: 1.0
--72530118999911999881 --72530118999911999881
skipping to change at page 11, line 24 skipping to change at page 12, line 16
--72530118999911999881 --72530118999911999881
Content-Type: text/html; charset="US-ASCII" Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
<html><body>Hello, this message content is <b>provided</b> in <html><body>Hello, this message content is <b>provided</b> in
<i>your</i> language.</body></html> <i>your</i> language.</body></html>
--72530118999911999881-- --72530118999911999881--
--01189998819991197253 --01189998819991197253
Content-Type: message/rfc822 Content-Type: message/rfc822
Content-Language: es Content-Language: es-ES
Content-Translation-Type: human Content-Translation-Type: human
Content-Disposition: inline Content-Disposition: inline
Subject: =?UTF-8?Q?Ejemplo_pr=C3=A1ctico_de_mensaje_?= Subject: =?UTF-8?Q?Ejemplo_pr=C3=A1ctico_de_mensaje_?=
=?UTF-8?Q?en_espa=C3=B1ol_e_ingl=C3=A9s?= =?UTF-8?Q?en_espa=C3=B1ol_e_ingl=C3=A9s?=
Content-Type: multipart/alternative; Content-Type: multipart/alternative;
boundary="53011899989991197281"; charset="US-ASCII" boundary="53011899989991197281"; charset="US-ASCII"
Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit
MIME-Version: 1.0 MIME-Version: 1.0
skipping to change at page 12, line 27 skipping to change at page 13, line 19
SA2dlndUU1... shortened for brevity ...7yxfd1SNsEy+OXr76qr SA2dlndUU1... shortened for brevity ...7yxfd1SNsEy+OXr76qr
997zF2hvZYeDEP5ftGV6Xzx2o9MAAAAASUVORK5CYII= 997zF2hvZYeDEP5ftGV6Xzx2o9MAAAAASUVORK5CYII=
--99911972530118999881-- --99911972530118999881--
--01189998819991197253-- --01189998819991197253--
9. Acknowledgements 9. 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, Ben Campbell, Mark
Ned Freed, Randall Gellens, Gunnar Hellstrom, Barry Leiba, Sean Davis, Doug Ewell, Ned Freed, Randall Gellens, Gunnar Hellstrom,
Leonard, John Levine, Alexey Melnikov, Addison Phillips, Julian Mirja Kuehlewind, Barry Leiba, Sean Leonard, John Levine, Alexey
Reschke, Pete Resnick, Brian Rosen, Fiona Tomkinson, Simon Tyler and Melnikov, Addison Phillips, Julian Reschke, Pete Resnick, Adam Roach,
Daniel Vargha. 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
Pablo for their work on the Spanish translations. Pablo for their work on the Spanish translations.
10. IANA Considerations 10. IANA Considerations
10.1. The multipart/multilingual MIME type 10.1. The multipart/multilingual MIME type
The multipart/multilingual MIME type will be registered with IANA The multipart/multilingual MIME type will be registered with IANA
including a reference to this document. This is the registration including a reference to this document. This is the registration
skipping to change at page 15, line 17 skipping to change at page 16, line 17
Whilst it is intended that each language message part is a direct Whilst it is intended that each language message part is a direct
translation of the original message, this may not always be the case translation of the original message, this may not always be the case
and these parts could contain undesirable content. Therefore there and these parts could contain undesirable content. Therefore there
is a possible risk that undesirable text or images could be shown to is a possible risk that undesirable text or images could be shown to
the recipient if the message is passed through a spam filter that the recipient if the message is passed through a spam filter that
does not check all of the message parts. The risk should be minimal does not check all of the message parts. The risk should be minimal
due to the fact that an unknown multipart subtype should be treated due to the fact that an unknown multipart subtype should be treated
as multipart/mixed and so each message part should be subsequently as multipart/mixed and so each message part should be subsequently
scanned. scanned.
If the email contains undesirable content in a language that the
recipient cannot understand and this unknown content is assumed to be
a direct translation of the content that the recipient can
understand, the recipient may unintentionally forward undesirable
content to a recipient that can understand it. To mitigate this
risk, an interactive implementation may allow the recipient to see
all of the translations for comparison.
Because the language message parts have a Content-Type of message/ Because the language message parts have a Content-Type of message/
rfc822 or message/global, they might contain From fields which could rfc822 or message/global, they might contain From fields which could
have different values to that of the top-level From field and may not have different values to that of the top-level From field and may not
reflect the actual sender. The inconsistent From field values might reflect the actual sender. The inconsistent From field values might
get shown to the recipient in a non-conforming email client and may get shown to the recipient in a non-conforming email client and may
mislead the recipient into thinking that the email came from someone mislead the recipient into thinking that the email came from someone
other than the real sender. other than the real sender.
12. Changes from Previous Versions 12. Changes from Previous Versions
skipping to change at page 20, line 5 skipping to change at page 21, line 5
12.17. Changes from draft-ietf-slim-multilangcontent-12 to draft-ietf- 12.17. Changes from draft-ietf-slim-multilangcontent-12 to draft-ietf-
slim-multilangcontent-13 slim-multilangcontent-13
o Changed the field name Translation-Type to Content-Translation- o Changed the field name Translation-Type to Content-Translation-
Type. Type.
o Explicitly specified the 3 initial values for Content-Translation- o Explicitly specified the 3 initial values for Content-Translation-
Type in the IANA Considerations section. Type in the IANA Considerations section.
12.18. Changes from draft-ietf-slim-multilangcontent-13 to draft-ietf-
slim-multilangcontent-14
o Added table of contents.
o Added notes about the risk of unwittingly forwarding undesirable
content to the Security Considerations section.
o Updated 'language code' to 'language tag' in section 5 to make it
clear that language tag values including country codes and script
codes are allowed.
o Updated the examples to use language tag values that include a
country code.
o Added a note into section 3.2 to specify what should happen if
mismatched sender addresses are found in the language parts.
o Many wording improvements and clarifications throughout the
document.
13. References 13. References
13.1. Normative References 13.1. Normative References
[RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [RFC2046] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046, Extensions (MIME) Part Two: Media Types", RFC 2046,
DOI 10.17487/RFC2046, November 1996, DOI 10.17487/RFC2046, November 1996,
<http://www.rfc-editor.org/info/rfc2046>. <http://www.rfc-editor.org/info/rfc2046>.
[RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions) [RFC2047] Moore, K., "MIME (Multipurpose Internet Mail Extensions)
skipping to change at page 20, line 36 skipping to change at page 22, line 11
Content-Disposition Header Field", RFC 2183, Content-Disposition Header Field", RFC 2183,
DOI 10.17487/RFC2183, August 1997, DOI 10.17487/RFC2183, August 1997,
<http://www.rfc-editor.org/info/rfc2183>. <http://www.rfc-editor.org/info/rfc2183>.
[RFC3282] Alvestrand, H., "Content Language Headers", RFC 3282, [RFC3282] Alvestrand, H., "Content Language Headers", RFC 3282,
DOI 10.17487/RFC3282, May 2002, DOI 10.17487/RFC3282, May 2002,
<http://www.rfc-editor.org/info/rfc3282>. <http://www.rfc-editor.org/info/rfc3282>.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November 10646", STD 63, RFC 3629, DOI 10.17487/RFC3629, November
2003, <http://www.rfc-editor.org/info/rfc3629>. 2003, <https://www.rfc-editor.org/info/rfc3629>.
[RFC4647] Phillips, A. and M. Davis, "Matching of Language Tags", [RFC4647] Phillips, A. and M. Davis, "Matching of Language Tags",
BCP 47, RFC 4647, DOI 10.17487/RFC4647, September 2006, BCP 47, RFC 4647, DOI 10.17487/RFC4647, September 2006,
<http://www.rfc-editor.org/info/rfc4647>. <http://www.rfc-editor.org/info/rfc4647>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5234>. editor.org/info/rfc5234>.
[RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322, [RFC5322] Resnick, P., Ed., "Internet Message Format", RFC 5322,
DOI 10.17487/RFC5322, October 2008, DOI 10.17487/RFC5322, October 2008, <https://www.rfc-
<http://www.rfc-editor.org/info/rfc5322>. editor.org/info/rfc5322>.
[RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying [RFC5646] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646, Languages", BCP 47, RFC 5646, DOI 10.17487/RFC5646,
September 2009, <http://www.rfc-editor.org/info/rfc5646>. September 2009, <https://www.rfc-editor.org/info/rfc5646>.
[RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized [RFC6532] Yang, A., Steele, S., and N. Freed, "Internationalized
Email Headers", RFC 6532, DOI 10.17487/RFC6532, February Email Headers", RFC 6532, DOI 10.17487/RFC6532, February
2012, <http://www.rfc-editor.org/info/rfc6532>. 2012, <http://www.rfc-editor.org/info/rfc6532>.
13.2. Informational References 13.2. Informational References
[I-D.ietf-slim-negotiating-human-language] [I-D.ietf-slim-negotiating-human-language]
Gellens, R., "Negotiating Human Language in Real-Time Gellens, R., "Negotiating Human Language in Real-Time
Communications", draft-ietf-slim-negotiating-human- Communications", draft-ietf-slim-negotiating-human-
 End of changes. 28 change blocks. 
51 lines changed or deleted 114 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/