[abnf-discuss] Unicode in ABNF (in RFC) draft-seantek-unicode-in-abnf-01.txt
Sean Leonard <dev+ietf@seantek.com> Mon, 03 October 2016 06:26 UTC
Return-Path: <dev+ietf@seantek.com>
X-Original-To: abnf-discuss@ietfa.amsl.com
Delivered-To: abnf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4296C12B093 for <abnf-discuss@ietfa.amsl.com>; Sun, 2 Oct 2016 23:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 whf8_mWpMZWp for <abnf-discuss@ietfa.amsl.com>; Sun, 2 Oct 2016 23:26:57 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3F5D12B01E for <abnf-discuss@ietf.org>; Sun, 2 Oct 2016 23:26:57 -0700 (PDT)
Received: from [192.168.123.7] (unknown [75.83.2.34]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 24483509B6; Mon, 3 Oct 2016 02:26:54 -0400 (EDT)
References: <147539145843.2906.13032756764513250005.idtracker@ietfa.amsl.com>
To: "abnf-discuss@ietf.org" <abnf-discuss@ietf.org>
From: Sean Leonard <dev+ietf@seantek.com>
X-Forwarded-Message-Id: <147539145843.2906.13032756764513250005.idtracker@ietfa.amsl.com>
Message-ID: <1c5eb0fa-c6bd-ef6a-320a-8eaf28559d9e@seantek.com>
Date: Sun, 02 Oct 2016 23:28:37 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <147539145843.2906.13032756764513250005.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/abnf-discuss/XzBHN1CjaF9RKgNM0hu7Ic5CJFY>
Cc: Chris Newman <chris.newman@oracle.com>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Subject: [abnf-discuss] Unicode in ABNF (in RFC) draft-seantek-unicode-in-abnf-01.txt
X-BeenThere: abnf-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "General discussion about tools, activities and capabilities involving the ABNF meta-language" <abnf-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/abnf-discuss/>
List-Post: <mailto:abnf-discuss@ietf.org>
List-Help: <mailto:abnf-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/abnf-discuss>, <mailto:abnf-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2016 06:26:59 -0000
Dear ABNF-Discuss (and rfc-interest): This draft by Chris Newman and I addresses an interesting topic: how to do Unicode in ABNF. Unicode has showed up in several different ways in protocols that are described in ABNF. These ways are not consistent across the RFC series, but now that Unicode is a pretty stable standard (for its basic parts) and now that UTF-8 RFCs are becoming a reality per draft-iab-rfc-nonascii-02, it is a good time to look at this issue. This is a fork from draft-seantek-abnf-more-core-rules. This draft is currently proposed as Experimental. Special thanks to Paul Kyzivat for discussing the matters in this draft, although he is not formally a co-author. The draft tries to be very conservative in its approach. Please read the draft for details. Some stuff was intentionally omitted as out-of-scope or too complicated for a general-purpose ABNF syntax parser, whether humans or machines. Comments and feedback are appreciated. Regards, Sean ******** A new version of I-D, draft-seantek-unicode-in-abnf-01.txt has been successfully submitted by Sean Leonard and posted to the IETF repository. Name: draft-seantek-unicode-in-abnf Revision: 01 Title: Unicode in ABNF Document date: 2016-10-01 Group: Individual Submission Pages: 11 URL: https://www.ietf.org/internet-drafts/draft-seantek-unicode-in-abnf-01.txt Status: https://datatracker.ietf.org/doc/draft-seantek-unicode-in-abnf/ Htmlized: https://tools.ietf.org/html/draft-seantek-unicode-in-abnf-01 Diff: https://www.ietf.org/rfcdiff?url2=draft-seantek-unicode-in-abnf-01 Abstract: This experimental document adds support for Unicode strings in ABNF (Augmented Backus-Naur Form), and provides certain symbols related to Unicode code point ranges.
- [abnf-discuss] Unicode in ABNF (in RFC) draft-sea… Sean Leonard
- Re: [abnf-discuss] [rfc-i] Unicode in ABNF (in RF… Martin J. Dürst
- Re: [abnf-discuss] [rfc-i] Unicode in ABNF (in RF… Sean Leonard
- Re: [abnf-discuss] [rfc-i] Unicode in ABNF (in RF… Martin J. Dürst
- Re: [abnf-discuss] [rfc-i] Unicode in ABNF (in RF… Sean Leonard