RFC Series publishes first RFC with non-ASCII characters
"Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org> Thu, 14 September 2017 21:07 UTC
Return-Path: <rse@rfc-editor.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7BC813208E for <ietf@ietfa.amsl.com>; Thu, 14 Sep 2017 14:07:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 lEFDvkxl41lw for <ietf@ietfa.amsl.com>; Thu, 14 Sep 2017 14:07:06 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3DBA120724 for <ietf@ietf.org>; Thu, 14 Sep 2017 14:07:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3EDCA1C2CBA; Thu, 14 Sep 2017 14:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xGwXBXBEZniK; Thu, 14 Sep 2017 14:06:46 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (c-73-181-135-61.hsd1.wa.comcast.net [73.181.135.61]) by c8a.amsl.com (Postfix) with ESMTPSA id 0D4761C1D11; Thu, 14 Sep 2017 14:06:46 -0700 (PDT)
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
To: ietf@ietf.org, rfc-interest@rfc-editor.org
Subject: RFC Series publishes first RFC with non-ASCII characters
Message-ID: <09b0ed8b-c47a-83c3-9174-cce990bdb145@rfc-editor.org>
Date: Thu, 14 Sep 2017 14:07:05 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jic8bRvwu8cJB0EgFtoHVQq14TM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2017 21:07:08 -0000
Hello all, RFC 8187, "Indicating Character Encoding and Language for HTTP Header Field Parameters", is the first RFC to be published with UTF-8 encoding and include characters not in the basic ASCII character set. This document has been, with the author's consent, patience, and support, used to test the existing tool chain to produce RFCs to see where the environment has difficulty in handling non-ASCII characters. The RPC is continues this testing with the PRECIS document cluster (C326), which is currently in AUTH48. The RPC and the Tools Team has identified several areas that need to be modified to support these characters. Some of those areas will ultimately be handled with the new format tools; others have been modified as part of the more general work to prepare for the new RFC format. For the documents being used to test the toolchain, a significant amount of manual processing is required to publish the RFCs with non-ASCII characters in the final text. In order to keep overall processing times down, leave staff enough time to test the other tools that are being developed as part of the RFC format project, and allow the editors time to create and/or update new procedures as the v3 tools are released, no additional non-ASCII documents outside of RFC 8187 and the PRECIS cluster will be published until the new format tools are in production. Many thanks go out to Julian Reschke and Peter Saint-Andre for their support, the Tools Team for answering a variety of technical questions, and to the RPC staff who worked to ensure that the RFC publication process resulted in readable RFCs. Heather Flanagan, RSE
- Re: Should the IETF be condoning, even promoting,… John C Klensin
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Phillip Hallam-Baker
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Matthew Kerwin
- RFC Series publishes first RFC with non-ASCII cha… Heather Flanagan (RFC Series Editor)
- Re: RFC Series publishes first RFC with non-ASCII… Masataka Ohta
- Re: RFC Series publishes first RFC with non-ASCII… Heather Flanagan (RFC Series Editor)
- Re: [rfc-i] RFC Series publishes first RFC with n… HANSEN, TONY L
- Re: RFC Series publishes first RFC with non-ASCII… tom p.
- Re: RFC Series publishes first RFC with non-ASCII… Denis Ovsienko
- Re: [rfc-i] RFC Series publishes first RFC with n… Patrik Fältström
- Re: RFC Series publishes first RFC with non-ASCII… Carsten Bormann
- Re: Re: RFC Series publishes first RFC with non-A… Denis Ovsienko
- Re: [rfc-i] RFC Series publishes first RFC with n… Mark Nottingham
- Re: [rfc-i] RFC Series publishes first RFC with n… Martin J. Dürst
- Re: RFC Series publishes first RFC with non-ASCII… Martin J. Dürst
- Re: [rfc-i] RFC Series publishes first RFC with n… Patrik Fältström
- Re: RFC Series publishes first RFC with non-ASCII… Masataka Ohta
- Brief history against non-ASCII RFCs (was Re: RFC… Masataka Ohta
- Re: RFC Series publishes first RFC with non-ASCII… Carsten Bormann
- Re: RFC Series publishes first RFC with non-ASCII… Lyndon Nerenberg
- Re: RFC Series publishes first RFC with non-ASCII… Stephane Bortzmeyer
- Re: RFC Series publishes first RFC with non-ASCII… Stephane Bortzmeyer
- Re: Re: RFC Series publishes first RFC with non-A… Denis Ovsienko
- Re: RFC Series publishes first RFC with non-ASCII… Masataka Ohta
- Re: RFC Series publishes first RFC with non-ASCII… Benjamin Kaduk
- Re: RFC Series publishes first RFC with non-ASCII… Masataka Ohta
- Re: RFC Series publishes first RFC with non-ASCII… Masataka Ohta
- Re: RFC Series publishes first RFC with non-ASCII… Brian E Carpenter
- Re: RFC Series publishes first RFC with non-ASCII… tom p.
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: [rfc-i] RFC Series publishes first RFC with n… Tim Bray
- Should the IETF be condoning, even promoting, BOM… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Tim Bray
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: [rfc-i] RFC Series publishes first RFC with n… Jari Arkko
- Re: RFC Series publishes first RFC with non-ASCII… Toerless Eckert
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: RFC Series publishes first RFC with non-ASCII… Stephane Bortzmeyer
- Re: RFC Series publishes first RFC with non-ASCII… Toerless Eckert
- Re: RFC Series publishes first RFC with non-ASCII… Toerless Eckert
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Viktor Dukhovni
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Ted Hardie
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Matthew Kerwin
- Re: Should the IETF be condoning, even promoting,… Adam Roach
- Re: Should the IETF be condoning, even promoting,… Lyndon Nerenberg
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- BOM-free tests [was Should the IETF be condoning,… Brian E Carpenter
- Re: BOM-free tests [was Should the IETF be condon… Ted Lemon
- Re: BOM-free tests [was Should the IETF be condon… tom p.
- Re: Should the IETF be condoning, even promoting,… tom p.
- Re: Should the IETF be condoning, even promoting,… Heather Flanagan (RFC Series Editor)
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Paul Hoffman
- Re: Should the IETF be condoning, even promoting,… Carsten Bormann
- Re: Should the IETF be condoning, even promoting,… John C Klensin
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… John C Klensin
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Lyndon Nerenberg
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Julian Reschke
- Re: BOM-free tests [was Should the IETF be condon… Doug Royer
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: BOM-free tests [was Should the IETF be condon… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… Brian E Carpenter
- Re: Should the IETF be condoning, even promoting,… Matthew Kerwin
- Re: Should the IETF be condoning, even promoting,… George Michaelson
- Re: Should the IETF be condoning, even promoting,… Ted Lemon
- Re: Should the IETF be condoning, even promoting,… tom p.
- So do both [was Re: Should the IETF be condoning,… Brian E Carpenter
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: RFC Series publishes first RFC with non-ASCII… Heather Flanagan (RFC Series Editor)
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: Should the IETF be condoning, even promoting,… Martin Thomson
- Re: Should the IETF be condoning, even promoting,… Matthew Kerwin
- Re: So do both [was Re: Should the IETF be condon… Matthew Kerwin
- Re: So do both [was Re: Should the IETF be condon… Carsten Bormann
- Re: So do both [was Re: Should the IETF be condon… Matthew Kerwin
- Re: So do both [was Re: Should the IETF be condon… Brian E Carpenter
- Re: So do both [was Re: Should the IETF be condon… tom p.
- Re: So do both [was Re: Should the IETF be condon… Matthew Kerwin
- Re: So do both [was Re: Should the IETF be condon… Julian Reschke
- Re: So do both [was Re: Should the IETF be condon… tom p.
- FTP and file transfers (was: Re: So do both [was … John C Klensin
- Re: FTP and file transfers (was: Re: So do both [… Phillip Hallam-Baker
- Re: FTP and file transfers Joe Touch
- Re: FTP and file transfers Nick Hilliard
- Re: FTP and file transfers John C Klensin
- Re: FTP and file transfers John C Klensin
- Re: FTP and file transfers Nick Hilliard
- Re: FTP and file transfers Phillip Hallam-Baker
- Re: FTP and file transfers Joe Touch
- Re: FTP and file transfers Phillip Hallam-Baker
- Re: FTP and file transfers Joe Touch
- Re: FTP and file transfers Phillip Hallam-Baker
- Re: FTP and file transfers Keith Moore
- Re: FTP and file transfers Phillip Hallam-Baker
- Re: FTP and file transfers Doug Royer
- Re: Should the IETF be condoning, even promoting,… Keith Moore
- Re: RFC Series publishes first RFC with non-ASCII… Keith Moore
- Re: Should the IETF be condoning, even promoting,… Randy Bush
- Re: Should the IETF be condoning, even promoting,… Keith Moore
- Re: Should the IETF be condoning, even promoting,… Leif Johansson
- Re: So do both [was Re: Should the IETF be condon… John C Klensin
- Re: RFC Series publishes first RFC with non-ASCII… John Levine
- Re: RFC Series publishes first RFC with non-ASCII… Keith Moore
- Re: RFC Series publishes first RFC with non-ASCII… John R Levine
- Re: RFC Series publishes first RFC with non-ASCII… Keith Moore
- Re: RFC Series publishes first RFC with non-ASCII… Viktor Dukhovni
- Re: So do both [was Re: Should the IETF be condon… Brian E Carpenter
- Re: So do both [was Re: Should the IETF be condon… Heather Flanagan (RFC Series Editor)
- Re: So do both [was Re: Should the IETF be condon… John C Klensin
- Re: So do both [was Re: Should the IETF be condon… Yoav Nir
- Re: So do both [was Re: Should the IETF be condon… Andrew G. Malis
- Re: page numbers or not, was So do both John Levine
- Re: So do both [was Re: Should the IETF be condon… Stewart Bryant
- Re: So do both [was Re: Should the IETF be condon… Joel M. Halpern
- Re: [rfc-i] RFC Series publishes first RFC with n… Frank Ellermann
- Re: RFC Series publishes first RFC with non-ASCII… Julian Reschke
- Re: [rfc-i] RFC Series publishes first RFC with n… Henrik Levkowetz