Re: [Json] Seeking more input on draft-ietf-json-text-sequence

Nico Williams <nico@cryptonector.com> Wed, 21 May 2014 01:28 UTC

Return-Path: <nico@cryptonector.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 F058C1A03FB for <json@ietfa.amsl.com>; Tue, 20 May 2014 18:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 GDS9wsUB9pjS for <json@ietfa.amsl.com>; Tue, 20 May 2014 18:28:20 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 57DED1A03F6 for <json@ietf.org>; Tue, 20 May 2014 18:28:20 -0700 (PDT)
Received: from homiemail-a28.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTP id CD1401B405F for <json@ietf.org>; Tue, 20 May 2014 18:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=7U9dRy5tDL8/5bj4uBhe 3PXsBpo=; b=E+CQP5cHt/WWFxsCc/vUosGbT0FgDxkSdzW7QTiuU5FmeveEObR4 f3t7mZDMN6Nj3BNiNEgU/lnhiZOtnw2zowYaZxLZkj8Bd+uElrn6evccv2fyIswD o9uHFeb3k6/ybKl+mzSjqlkOw7On2etAFIiqddmBvNB6tqusYCvwKmI=
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a28.g.dreamhost.com (Postfix) with ESMTPSA id 80C0A1B4056 for <json@ietf.org>; Tue, 20 May 2014 18:28:19 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id bs8so1904089wib.12 for <json@ietf.org>; Tue, 20 May 2014 18:28:18 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.185.244 with SMTP id ff20mr7351333wic.42.1400635698486; Tue, 20 May 2014 18:28:18 -0700 (PDT)
Received: by 10.216.29.200 with HTTP; Tue, 20 May 2014 18:28:18 -0700 (PDT)
In-Reply-To: <CAK3OfOhp9NexrHcDq-SmBsV+LxTbmM3w--L9vf2AeC6sYRr5zg@mail.gmail.com>
References: <20140509173159.28855.94523.idtracker@ietfa.amsl.com> <A89181FF-2FAB-4C17-86AC-685D09AD0CA4@vpnc.org> <537875D8.1080807@drees.name> <CAK3OfOhp9NexrHcDq-SmBsV+LxTbmM3w--L9vf2AeC6sYRr5zg@mail.gmail.com>
Date: Tue, 20 May 2014 20:28:18 -0500
Message-ID: <CAK3OfOjTSsadRhPvwoKskNK0UDLZJ+P3wxC3U6opE_g8viY8UA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "stefan@drees.name" <stefan@drees.name>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/-0rkE0dKQBQc2nseDg7edKzldUo
Cc: "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Seeking more input on draft-ietf-json-text-sequence
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: Wed, 21 May 2014 01:28:23 -0000

On Tue, May 20, 2014 at 8:17 PM, Nico Williams <nico@cryptonector.com> wrote:
>   ws-no-LF = SP HTAB CR

Missing alternators...  Anyways, my final offer:

  JSON-sequence = *ws-lf *(JSON-text *ws-no-lf LF *ws-no-lf)
  ws-no-lf = SP / HTAB / CR
  ws = <given by RFC7159>
  JSON-text = <given by RFC7159>

and

 boundary = endchar *ws-no-lf LF *ws-lf startchar
 endchar = ( "}" / "]" / DQUOTE / "e" / "l" / DIGIT )
 startchar =  ( "{" / "[" / DQUOTE / "t" / "f" / "n" / "-" / DIGIT )

I was already using DIGIT from RFC5234, so using DQUOTE, SP, HTAB, CR,
and LF seems right, including the upper case (though it doesn't
matter).  I'm surprised RFC7159 doesn't use them (it uses DIGIT, oddly
enough, but not the others).

Nico
--