draft-ietf-slim-multilangcontent-02.txt   draft-ietf-slim-multilangcontent-03.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: January 21, 2017 July 20, 2016 Expires: January 22, 2017 July 21, 2016
Multiple Language Content Type Multiple Language Content Type
draft-ietf-slim-multilangcontent-02 draft-ietf-slim-multilangcontent-03
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 January 21, 2017. This Internet-Draft will expire on January 22, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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 35 skipping to change at page 4, line 35
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 Translation-Type parameter applied to the Content-Language have a Translation-Type parameter applied to the Content-Language
field. 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. Each language support for message/global becomes more commonplace. Each language
message part SHOULD have a Subject field in the appropriate language message part SHOULD have a Subject field in the appropriate language
for that language part and SHOULD NOT have a From field. for that language part. If there is a From field present, its value
MUST include the same email address as the top-level From header
although 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 be a language independent graphic.
When this part is present, it MUST be the last part, MUST have a When this part is present, it MUST be the last part, MUST have a
Content-Language field with a value of "zxx" (as described in BCP 47/ Content-Language field with a value of "zxx" (as described in BCP 47/
skipping to change at page 13, line 48 skipping to change at page 14, line 5
9.6. Changes from draft-ietf-slim-multilangcontent-01 to draft-ietf- 9.6. Changes from draft-ietf-slim-multilangcontent-01 to draft-ietf-
slim-multilangcontent-02 slim-multilangcontent-02
o Restricted the use of a From field in the language message parts o Restricted the use of a From field in the language message parts
and the language independent part. and the language independent part.
o Updated the security considerations to highlight the risk of an o Updated the security considerations to highlight the risk of an
unmatched sender addresses that could be set in the language unmatched sender addresses that could be set in the language
message parts. message parts.
9.7. Changes from draft-ietf-slim-multilangcontent-02 to draft-ietf-
slim-multilangcontent-03
o Relaxed the restriction on the use of the From field in the
language message parts to allow a localised version of the
sender's display name.
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, Sean Leonard, John Levine, Alexey Randall Gellens, Gunnar Hellstrom, Sean Leonard, John Levine, Alexey
Melnikov, Addison Phillips, Pete Resnick, Fiona Tomkinson, Simon Melnikov, Addison Phillips, Pete Resnick, Brian Rosen, Fiona
Tyler and Daniel Vargha. 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.
11. IANA Considerations 11. IANA Considerations
The multipart/multilingual MIME type will be registered with IANA. The multipart/multilingual MIME type will be registered with IANA.
12. Security Considerations 12. Security Considerations
 End of changes. 6 change blocks. 
6 lines changed or deleted 15 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/