Multiple Language Content Type
draft-ietf-slim-multilangcontent-06

Document Type Active Internet-Draft (slim WG)
Last updated 2016-10-12
Replaces draft-tomkinson-slim-multilangcontent
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state In WG Last Call
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IETF                                                        N. Tomkinson
Internet-Draft                                             N. Borenstein
Intended status: Standards Track                            Mimecast Ltd
Expires: April 15, 2017                                 October 12, 2016

                     Multiple Language Content Type
                  draft-ietf-slim-multilangcontent-06

Abstract

   This document defines an addition to the Multipurpose Internet Mail
   Extensions (MIME) standard to make it possible to send one message
   that contains multiple language versions of the same information.
   The translations would be identified by a language tag and selected
   by the email client based on a user's language settings.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 15, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Tomkinson & Borenstein   Expires April 15, 2017                 [Page 1]
Internet-Draft       Multiple Language Content Type         October 2016

1.  Introduction

   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
   countries and in more and more languages.  But during this time of
   technological evolution, email has remained a single-language
   communication tool, whether it is English to English, Spanish to
   Spanish or Japanese to Japanese.

   Also during this time, many corporations have established their
   offices in multi-cultural cities and formed departments and teams
   that span continents, cultures and languages, so the need to
   communicate efficiently with little margin for miscommunication has
   grown significantly.

   The objective of this document is to define an addition to the
   Multipurpose Internet Mail Extensions (MIME) standard, to make it
   possible to send a single message to a group of people in such a way
   that all of the recipients can read the email in their preferred
   language.  The methods of translation of the message content are
   beyond the scope of this document, but the structure of the email
   itself is defined herein.

   Whilst this document depends on identification of language in message
   parts for non-real-time communication, there is a companion document
   that is concerned with a similar problem for real-time communication:
   [I-D.ietf-slim-negotiating-human-language]

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].

2.  The Content-Type Header Field

   The "multipart/multilingual" MIME subtype allows the sending of a
   message in a number of different languages with the translations
   embedded in the same message.  This MIME subtype helps the receiving
   email client make sense of the message structure.

   The multipart subtype "multipart/multilingual" has similar semantics
   to "multipart/alternative" (as discussed in RFC 2046 [RFC2046]) in
   that each of the message parts is an alternative version of the same
   information.  The primary difference between "multipart/multilingual"
   and "multipart/alternative" is that when using "multipart/
   multilingual", the message part to select for rendering is chosen
Show full document text