IETF Logo Mail Archive

Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

Peter Saint-Andre - Filament <peter@filament.com> Fri, 21 July 2017 15:35 UTC

Return-Path: <peter@filament.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1B2131935 for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 08:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-com.20150623.gappssmtp.com
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 2HM9gmJL21LT for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 08:35:23 -0700 (PDT)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42EF912EC57 for <json@ietf.org>; Fri, 21 Jul 2017 08:35:23 -0700 (PDT)
Received: by mail-it0-x231.google.com with SMTP id v127so9106882itd.0 for <json@ietf.org>; Fri, 21 Jul 2017 08:35:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=6APnrobH+ziPTOq/CTHmCf/0GQ4UvGaZOXfLqmueIjQ=; b=GqQEGgYMeATCFUnZpW7xtXXxnII5XT9y6z+x2y6gofl4j730HYotuyzEH8Ba2Aj2oy HDvEpjbLDqozbC45BByl3KOwrVk2YT0Y2z2oGM3zinwQeiTVjF1yxmSDCrcuO8b6vsmJ ikjtOt7PxUj2/hBYj6KbK33WfoXTKo5Gpe1zpt7SXUft767PIeRX101Qyl7DQuTmAWcs AY7N6IVGEaB9FTqAf5mSsZAeemJbuLHd90pTIGwr1FaoqdkY3cPKW2j00H9LlHROkT89 2FE0x0i/wJ9IGX0Tup7CssDMVTAU9fikjpXJZxRYSn8GuJwg0hgW47oYQrrM5TALOP6w SNLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=6APnrobH+ziPTOq/CTHmCf/0GQ4UvGaZOXfLqmueIjQ=; b=Pw16/5j+BDdIPvbJBHHnxxoCciIJVhI1QGT6l6cZGI0wywmIHcipMNA5PWh2MYCn+z f7suIRWbxFd7qiedQ4bV5aJSVWhcRklBwKu80rVHKsBSsKRMBAsJxhYC/yHMZFglI9qc opRHv/gbR2shvCl5bPNQlLRnq8dqJ+H26Vq5GvzVYz09DsW6vrsG4/tIVIVWa0OEeb6J vGqDq6VhLS9u11Lksen2PI+vv1E3BeX4nOwxQbzdwfGYkIFParCuHzbXTRXqTsM1mQUC mD0QLm/GzHupv5joUw1uiNZkRkYcMrQEx2aGYZ+bv3LhcqMZWdNOi4+oXqZgSkfzAhNx OYqg==
X-Gm-Message-State: AIVw110FhUc+bqB9Ds7RHE7B2WWfjyF2GdKKNS3LizVOfCP7G3bTri2d ce2rmY3wZPBLXKOk
X-Received: by 10.36.40.196 with SMTP id h187mr7555076ith.43.1500651321771; Fri, 21 Jul 2017 08:35:21 -0700 (PDT)
Received: from aither.local ([2601:282:4202:67d3:9db5:67cc:4146:d455]) by smtp.gmail.com with ESMTPSA id m27sm2453305ioi.19.2017.07.21.08.35.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Jul 2017 08:35:20 -0700 (PDT)
To: Carsten Bormann <cabo@tzi.org>, Julian Reschke <julian.reschke@gmx.de>
References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <DB9BA7EA-D393-4079-B347-620A09280B26@isode.com> <CAC4RtVBYMrRCrUZ1qqD+_rH4M8N23GOgbbh=921fEYqH+gCm5Q@mail.gmail.com> <c06e583a-965e-9eaf-975f-e6876ac056ed@filament.com> <f1a6b553-c787-e248-67bd-74d68d98a845@gmx.de> <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org>
Cc: json@ietf.org
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <166957c4-26fc-90b5-a798-59280c91b466@filament.com>
Date: Fri, 21 Jul 2017 09:35:20 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/bBAimnTL-EvM9n-iW6PPJph4de8>
Subject: Re: [Json] I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Jul 2017 15:35:24 -0000

On 7/20/17 11:14 PM, Carsten Bormann wrote:
> On Jul 21, 2017, at 06:20, Julian Reschke <julian.reschke@gmx.de>
> wrote:
>> 
>>> 
>>> I suggest: When an entity transmits JSON text over a network,
>>> e.g. as the payload of an application protocol, it MUST encode
>>> that text using UTF-8 [RFC3629].
>> 
>> This gets us back to the suggestion to apply this rule to the use
>> of the application/json media type (and types derived from it).
> 
> The nit-picking opportunity here is that we don’t want to change NFS
> in case someone accesses a file with UTF-32 JSON in it over the
> network protocol NFS.  We could recognize this as nit-picking, or use
> a phrase such as “intended by the protocol to be JSON” — media types
> are not the only way such an intention could take shape.
> 
> (Re the previous discussion: We do not have to define “network
> protocol” further.  Sheesh.  But the point is that any protocol that
> claims to interchange JSON should define the JSON to be used in UTF-8
> format, just as we define application/json to be UTF-8 format.)

Hallo Carsten,

Improvements over my suggested text are welcome. Or do you think that
the text in -04 is good enough? I find it somewhat ambiguous.

Peter

v2.23.0 | Report a Bug | By Email