IETF Logo Mail Archive

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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 08 July 2014 11:51 UTC

Return-Path: <jhildebr@cisco.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 EB7491B2853 for <json@ietfa.amsl.com>; Tue, 8 Jul 2014 04:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 F0NBjlCiGOwK for <json@ietfa.amsl.com>; Tue, 8 Jul 2014 04:50:56 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C2EB1B2810 for <json@ietf.org>; Tue, 8 Jul 2014 04:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1560; q=dns/txt; s=iport; t=1404820256; x=1406029856; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=T9aPEm7Du5eD0MHWRcvYh4MJe47uXFZS4eB40TlBq6o=; b=V3/K9U5dEilM3+ea5tBbjTCjyja/uDM9A4seINZGb+AI0moth9MW8Dgz MkazSNM9ZCoKgpMY13bjxEsPZ2Nz/kxjXmbVqitlaE2QpkV6lHLnUlzGa khDmuxsn8hAcGnmykO4Zr5bMn9NHnfA4wwEA/lvZyymC4GYLztDIJPQTJ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAAbau1OtJV2P/2dsb2JhbABZgw6BLIJvw0gBGX0WdYQEAQEEIxFVAgEIGgImAgICMBUQAgQBEohCr3OZOheBLI1DOoJ3gUwBBJZchBqUDINDgjA
X-IronPort-AV: E=Sophos;i="5.01,625,1400025600"; d="scan'208";a="59091422"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-6.cisco.com with ESMTP; 08 Jul 2014 11:50:55 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s68BotOf011439 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Jul 2014 11:50:55 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0123.003; Tue, 8 Jul 2014 06:50:55 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, IETF JSON WG <json@ietf.org>
Thread-Topic: [Json] The text in draft-ietf-json-text-sequence
Thread-Index: AQHPmiYfnAd3ORqBrkmbNTIJ/4t2Z5uWhsqA
Date: Tue, 08 Jul 2014 11:50:54 +0000
Message-ID: <CFE1A78C.52DE5%jhildebr@cisco.com>
References: <FD9026FF-BDC5-451C-ABBC-0608AB63B819@vpnc.org>
In-Reply-To: <FD9026FF-BDC5-451C-ABBC-0608AB63B819@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.147.19.77]
Content-Type: text/plain; charset="utf-8"
Content-ID: <2E691393B9AACA42926C52562F8A2166@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/t0Y0c1FTioge4QLcQ44I1k1jYuY
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, 08 Jul 2014 11:51:01 -0000

On 7/7/14, 10:57 PM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>Greetings again. There is still disagreement in the WG about what the
>text separator should be for draft-ietf-json-text-sequence. The current
>draft, draft-ietf-json-text-sequence-04, specifies it as the LF
>character, and gives rationale for that decision in Section 2.2. Many
>people in the WG have expressed a preference for a different character,
>one that would not require any stripping from the normal whitespace that
>can exist inside the JSON text. There were many suggestions for such a
>different character; the one that seemed most favored was the ASCII
>record separator (RS) character, U+001e.
>
>In order to simplify the decision, I'd like to ask a few simple questions:
>
>- Do you feel that the protocol will be significantly broken if it uses
>LF as the text separator?

Somewhat.

>- Do you feel that the protocol will be significantly broken if it uses
>RS as the text separator?

No.

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

No.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email