IETF Logo Mail Archive

Re: [Json] The text in draft-ietf-json-text-sequence

Nico Williams <nico@cryptonector.com> Tue, 15 July 2014 06:30 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 68B491A0309 for <json@ietfa.amsl.com>; Mon, 14 Jul 2014 23:30:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 jo2-TddwaXpE for <json@ietfa.amsl.com>; Mon, 14 Jul 2014 23:30:25 -0700 (PDT)
Received: from homiemail-a112.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id E05381A0308 for <json@ietf.org>; Mon, 14 Jul 2014 23:30:25 -0700 (PDT)
Received: from homiemail-a112.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a112.g.dreamhost.com (Postfix) with ESMTP id BB7C920078716; Mon, 14 Jul 2014 23:30:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=iiU/SDbKaQbOQC Tds1l1aNwlYR8=; b=E3cYIs6drIdaBIrGAjN9Vq0mBl/jLREttzJz15/8H5T66c KY5rPePMImEXlgYTkuyBMoT/Vc93xyIwRrYFK2CWECCSDLteJqN8kD/EHJyFqUle TNLqenDtspJAhnQU3HV3FRbP9IEAfBO76w5o/ArmcY0CsXwI6qfTstlrOOSiE=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a112.g.dreamhost.com (Postfix) with ESMTPA id 610D520078710; Mon, 14 Jul 2014 23:30:25 -0700 (PDT)
Date: Tue, 15 Jul 2014 01:30:24 -0500
From: Nico Williams <nico@cryptonector.com>
To: "Manger, James" <James.H.Manger@team.telstra.com>
Message-ID: <20140715063023.GB2256@localhost>
References: <FD9026FF-BDC5-451C-ABBC-0608AB63B819@vpnc.org> <255B9BB34FB7D647A506DC292726F6E11549A8F764@WSMSG3153V.srv.dir.telstra.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E11549A8F764@WSMSG3153V.srv.dir.telstra.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/NjtwMwKFw7dJLzkAT727-TzvRlo
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] The text in 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: Tue, 15 Jul 2014 06:30:26 -0000

On Tue, Jul 08, 2014 at 09:43:10AM +1000, Manger, James wrote:
> - Do you feel that the protocol will be significantly broken if it uses LF as the text separator?
> 
> No
> 
> - Do you feel that the protocol will be significantly broken if it uses RS as the text separator?
> 
> Yes

I agree.  I think RS will hurt and won't help.

To begin with: there exists running code using LF as the separator.  I
just demonstrated (separate post, new sub-thread) that RS/LF are
equivalent in terms of functionality, semantics, and cost.  So why break
running code??

And then there's all the text-oriented tools that won't handle RS.
Examples have been given in past posts.  There's no value to using RS or
anything other than LF.

Nico
--

v2.23.0 | Report a Bug | By Email