Re: [Json] [rfc-i] v3imp #8 Fragment tagging on sourcecode

Sean Leonard <dev+ietf@seantek.com> Fri, 30 January 2015 11:31 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 219A81A8BB5 for <json@ietfa.amsl.com>; Fri, 30 Jan 2015 03:31:43 -0800 (PST)
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
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 eSLBKVCzIYHq for <json@ietfa.amsl.com>; Fri, 30 Jan 2015 03:31:41 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4904B1A01F4 for <json@ietf.org>; Fri, 30 Jan 2015 03:31:41 -0800 (PST)
Received: from [192.168.123.7] (unknown [23.241.1.22]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 83D6F22E261; Fri, 30 Jan 2015 06:31:39 -0500 (EST)
Message-ID: <54CB6B9A.1080801@seantek.com>
Date: Fri, 30 Jan 2015 03:31:38 -0800
From: Sean Leonard <dev+ietf@seantek.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <54C29891.6040101@alum.mit.edu> <54C3576A.9030206@greenbytes.de> <54C3BE06.8010707@alum.mit.edu> <54C3C6A3.6080003@seantek.com> <54C3CF7F.6090901@seantek.com> <54C4AFF1.6030608@gmx.de> <54C7FAD7.7040500@alum.mit.edu> <54C870B5.7000205@seantek.com> <20150128173229.GC3110@localhost> <54C9632A.2040204@seantek.com> <20150128230227.GG3110@localhost>
In-Reply-To: <20150128230227.GG3110@localhost>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/-MYn0wk_cPEB6eiPzt3JmtogqeI>
Cc: rfc-interest@rfc-editor.org, draft-ietf-json-text-sequence@tools.ietf.org, json@ietf.org
Subject: Re: [Json] [rfc-i] v3imp #8 Fragment tagging on sourcecode
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 11:31:43 -0000

On 1/28/2015 3:02 PM, Nico Williams wrote:
>> As a broader useful point (not directed specifically to
>> draft-ietf-json-text-sequence-13), I think it would be nice if
>> future RFC ABNF can assume that the symbols in RFC 20 for %x00-20 /
>> %x7F are rules that can be used as-is. Hence NUL = %x00, SUB = %x1A,
>> DEL = %x7F, etc.
> I agree.  These should be added to RFC5234 (i.e., we should publish an
> update RFC listing them).

I would be willing to write up/work on a concise RFC (Internet-Draft) 
that does this, prior to IETF 92. I would not mind adding a few 
additional rules to the Core Rules if there is near-unanimous support 
for such rules. (Hard to think of any in particular, except maybe some 
generic UTF8 character rules. Last I checked, ABNF is still 
octet-oriented and US-ASCII focused.)

While I would not say "precondition", it is reasonable to require that 
RFCs after the publication of such an RFC follow it, much like RFCs past 
5234 use RFC 5234 as the basis.

Sean