draft-ietf-slim-multilangcontent-10.txt   draft-ietf-slim-multilangcontent-11.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 2, 2018 August 1, 2017 Expires: February 8, 2018 August 7, 2017
Multiple Language Content Type Multiple Language Content Type
draft-ietf-slim-multilangcontent-10 draft-ietf-slim-multilangcontent-11
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 February 2, 2018. This Internet-Draft will expire on February 8, 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 6, line 22 skipping to change at page 6, line 22
Content-Language: es, fr Content-Language: es, fr
6. The Translation-Type Field 6. The Translation-Type Field
The Translation-Type field can be used in the individual language The Translation-Type field can be used in the individual language
message parts to identify the type of translation. Based on the message parts to identify the type of translation. Based on the
value of this parameter and the user's preferences, a conforming 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 in
value of 'original' is given in the language message part that is in updated specification documents. A value of 'original' is given in
the original language. A value of 'human' is used when a language the language message part that is in the original language. A value
message part is translated by a human translator or a human has of 'human' is used when a language message part is translated by a
checked and corrected an automated translation. A value of human translator or a human has checked and corrected an automated
'automated' is used when a language message part has been translated translation. A value of 'automated' is used when a language message
by an electronic agent without proofreading or subsequent correction. part has been translated by an electronic agent without proofreading
or subsequent correction.
Examples of this field include: Examples of this field include:
Translation-Type: original Translation-Type: original
Translation-Type: human Translation-Type: human
The syntax of the Translation-Type field in ABNF RFC 5234 [RFC5234] The syntax of the Translation-Type field in ABNF RFC 5234 [RFC5234]
is: is:
skipping to change at page 14, line 13 skipping to change at page 14, line 13
Intended usage: Common Intended usage: Common
10.2. The Translation-Type field 10.2. The Translation-Type field
The Translation-Type field will be added to the IANA "Permanent The Translation-Type field will be added to the IANA "Permanent
Message Header Field Names" registry. That entry will reference this Message Header Field Names" registry. That entry will reference this
document. This is the registration template: document. This is the registration template:
Header field name: Translation-Type Header field name: Translation-Type
Applicable protocol: mail Applicable protocol: mime
Status: Standard Status: Standard
Author/Change controller: IETF Author/Change controller: IETF
Specification document(s): RFC XXXX Specification document(s): RFC XXXX
Related information: none Related information: none
11. Security Considerations 11. Security Considerations
skipping to change at page 18, line 31 skipping to change at page 18, line 31
o Updated example 2 to contain a image/png language independent o Updated example 2 to contain a image/png language independent
image directly rather than it being nested inside multipart/mixed image directly rather than it being nested inside multipart/mixed
content. content.
o Inserted Change Controller into IANA template for multipart/ o Inserted Change Controller into IANA template for multipart/
multilingual. multilingual.
o Replaced references to "This document" with RFC XXXX in the IANA o Replaced references to "This document" with RFC XXXX in the IANA
considerations. considerations.
12.15. Changes from draft-ietf-slim-multilangcontent-10 to draft-ietf-
slim-multilangcontent-11
o Updated the applicable protocol for the Translation-Type field in
the IANA registration template to be 'mime' rather than 'mail'.
o Added that updated specification documents would be the source of
new values for the Translation-Type field.
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)
 End of changes. 6 change blocks. 
11 lines changed or deleted 21 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/