RFC 8255 on Multiple Language Content Type

rfc-editor@rfc-editor.org Tue, 10 October 2017 19:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC691331D2; Tue, 10 Oct 2017 12:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VPkOqkApYzOD; Tue, 10 Oct 2017 12:53:06 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EC9A126D0C; Tue, 10 Oct 2017 12:53:03 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0C21BB8117D; Tue, 10 Oct 2017 12:52:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8255 on Multiple Language Content Type
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, slim@ietf.org
Message-Id: <20171010195251.0C21BB8117D@rfc-editor.org>
Date: Tue, 10 Oct 2017 12:52:51 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/TKJJ6nl5zlaqs39ZfYdAuyYj1nY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Oct 2017 19:53:09 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8255

        Title:      Multiple Language Content Type 
        Author:     N. Tomkinson,
                    N. Borenstein
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2017
        Mailbox:    rfc.nik.tomkinson@gmail.com, 
                    nsb@mimecast.com
        Pages:      19
        Characters: 36982
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-slim-multilangcontent-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8255

        DOI:        10.17487/RFC8255

This document defines the 'multipart/multilingual' content type,
which is an addition to the Multipurpose Internet Mail Extensions
(MIME) standard.  This content type makes 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.

This document is a product of the Selection of Language for Internet Media Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC