IETF Logo Mail Archive

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

"Manger, James" <James.H.Manger@team.telstra.com> Mon, 07 July 2014 23:43 UTC

Return-Path: <James.H.Manger@team.telstra.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 A61131B298E for <json@ietfa.amsl.com>; Mon, 7 Jul 2014 16:43:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.202
X-Spam-Level:
X-Spam-Status: No, score=-0.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RCVD_IN_DNSWL_NONE=-0.0001, RELAY_IS_203=0.994] 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 gpQ9A-pU4oFY for <json@ietfa.amsl.com>; Mon, 7 Jul 2014 16:43:13 -0700 (PDT)
Received: from ipxano.tcif.telstra.com.au (ipxano.tcif.telstra.com.au [203.35.82.200]) by ietfa.amsl.com (Postfix) with ESMTP id 44A4B1B298C for <json@ietf.org>; Mon, 7 Jul 2014 16:43:13 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.01,621,1399989600"; d="scan'208";a="212202611"
Received: from unknown (HELO ipcbni.tcif.telstra.com.au) ([10.97.216.204]) by ipoani.tcif.telstra.com.au with ESMTP; 08 Jul 2014 09:36:09 +1000
X-IronPort-AV: E=McAfee;i="5600,1067,7492"; a="233625231"
Received: from wsmsg3701.srv.dir.telstra.com ([172.49.40.169]) by ipcbni.tcif.telstra.com.au with ESMTP; 08 Jul 2014 09:43:12 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3701.srv.dir.telstra.com ([172.49.40.169]) with mapi; Tue, 8 Jul 2014 09:43:11 +1000
From: "Manger, James" <James.H.Manger@team.telstra.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
Date: Tue, 08 Jul 2014 09:43:10 +1000
Thread-Topic: [Json] The text in draft-ietf-json-text-sequence
Thread-Index: Ac+aJiAFSw9SX2AIQl6FhPN9pEw23wAFt/3g
Message-ID: <255B9BB34FB7D647A506DC292726F6E11549A8F764@WSMSG3153V.srv.dir.telstra.com>
References: <FD9026FF-BDC5-451C-ABBC-0608AB63B819@vpnc.org>
In-Reply-To: <FD9026FF-BDC5-451C-ABBC-0608AB63B819@vpnc.org>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/eP6wcNX2BNXtZNXSdYbbT6opXnE
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: Mon, 07 Jul 2014 23:43:14 -0000

- 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

- Do you feel that using LF or RF as the text separator is essentially the same for the protocol?

No

--
James Manger

v2.23.0 | Report a Bug | By Email