draft-ietf-slim-multilangcontent-08.txt   draft-ietf-slim-multilangcontent-09.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: December 14, 2017 June 12, 2017 Expires: January 25, 2018 July 24, 2017
Multiple Language Content Type Multiple Language Content Type
draft-ietf-slim-multilangcontent-08 draft-ietf-slim-multilangcontent-09
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 December 14, 2017. This Internet-Draft will expire on January 25, 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
skipping to change at page 4, line 45 skipping to change at page 4, line 45
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.
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 intended for the recipient
to see if they have a preferred language other than one of those to see if they have a preferred language other than one of those
specified in the language message parts and the default language specified in the language message parts and the default language
message part is unlikely to be understood, another part MAY be message part is unlikely to be understood, another part MAY be
provided. This could typically be a language independent graphic. provided. This could typically include a language independent
When this part is present, it MUST be the last part, MUST have a graphic. When this part is present, it MUST be the last part and
Content-Language field with a value of "zxx" (as described in BCP 47/ MUST have a Content-Language field with a value of "zxx" (as
RFC 5646 [RFC5646]) and SHOULD NOT have a Subject field and SHOULD described in BCP 47/RFC 5646 [RFC5646]). The part SHOULD have a
NOT have a From field. The part SHOULD have a Content-Type of Content-Type of message/rfc822 or message/global (to match the
message/rfc822 or message/global (to match the language message language message parts).
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 should treat the message as if it was multipart/ multilingual then it should treat the message as if it was multipart/
mixed and render message parts accordingly. mixed and render message parts accordingly.
skipping to change at page 6, line 52 skipping to change at page 7, line 4
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 (for example if the language independent
part is selected) the top-level Subject header field value should be If no Subject field is found the top-level Subject header field value
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.
From: Nik@example.com From: Nik@example.com
To: Nathaniel@example.com To: Nathaniel@example.com
 End of changes. 5 change blocks. 
13 lines changed or deleted 12 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/