RFC 7997 on The Use of Non-ASCII Characters in RFCs
rfc-editor@rfc-editor.org Fri, 16 December 2016 16:01 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 7EAD412A1B6 for <ietf-announce@ietfa.amsl.com>; Fri, 16 Dec 2016 08:01:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.098
X-Spam-Level:
X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 RV0BSJWO1n5l for <ietf-announce@ietfa.amsl.com>; Fri, 16 Dec 2016 08:01:08 -0800 (PST)
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 0ECA4129FAC for <ietf-announce@ietf.org>; Fri, 16 Dec 2016 07:55:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0D69BB80303; Fri, 16 Dec 2016 07:55:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7997 on The Use of Non-ASCII Characters in RFCs
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161216155541.0D69BB80303@rfc-editor.org>
Date: Fri, 16 Dec 2016 07:55:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/qOTFjQweP-69CXtM3_ZQhO3pr1w>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 16 Dec 2016 16:01:12 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7997
Title: The Use of Non-ASCII Characters in RFCs
Author: H. Flanagan, Ed.
Status: Informational
Stream: IAB
Date: December 2016
Mailbox: rse@rfc-editor.org
Pages: 15
Characters: 27637
Updates: RFC 7322
I-D Tag: draft-iab-rfc-nonascii-02.txt
URL: https://www.rfc-editor.org/info/rfc7997
DOI: 10.17487/RFC7997
In order to support the internationalization of protocols and a more
diverse Internet community, the RFC Series must evolve to allow for
the use of non-ASCII characters in RFCs. While English remains the
required language of the Series, the encoding of future RFCs will be
in UTF-8, allowing for a broader range of characters than typically
used in the English language. This document describes the RFC Editor
requirements and gives guidance regarding the use of non-ASCII
characters in RFCs.
This document updates RFC 7322. Please view this document in PDF
form to see the full text.
This document is a product of the Internet Architecture Board.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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