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

Carsten Bormann <cabo@tzi.org> Fri, 21 July 2017 13:35 UTC

Return-Path: <cabo@tzi.org>
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 C6B1B129B43 for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 06:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 OGSealo7c0uA for <json@ietfa.amsl.com>; Fri, 21 Jul 2017 06:35:12 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3925131E0F for <json@ietf.org>; Fri, 21 Jul 2017 06:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v6LDZ5Mm016779; Fri, 21 Jul 2017 15:35:05 +0200 (CEST)
Received: from client-0032.vpn.uni-bremen.de (client-0032.vpn.uni-bremen.de [134.102.107.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3xDWwT1RP1z3ZSK; Fri, 21 Jul 2017 15:35:05 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <899d8a84-a46e-e95a-6fe0-e5812655f5b8@codalogic.com>
Date: Fri, 21 Jul 2017 15:35:04 +0200
Cc: Julian Reschke <julian.reschke@gmx.de>, Peter Saint-Andre - Filament <peter@filament.com>, json@ietf.org
X-Mao-Original-Outgoing-Id: 522336904.172077-1aff39e27ee7f00d0df90273867f802c
Content-Transfer-Encoding: quoted-printable
Message-Id: <2C2529CA-2F7F-422B-9DD7-4144F05AF88E@tzi.org>
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> <2e6f5ead-1c20-d727-87a7-bbfe75ed4896@codalogic.com> <82da41d9-ab0b-ae9b-55f8-d17dc65bb61f@gmx.de> <899d8a84-a46e-e95a-6fe0-e5812655f5b8@codalogic.com>
To: Pete Cordell <petejson@codalogic.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/MJtlEUzLdBXf1ya7AxWQVJmuNwg>
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 13:35:21 -0000

On Jul 21, 2017, at 10:27, Pete Cordell <petejson@codalogic.com> wrote:
> 
> Good point.  How about:
> 
>     IETF-specified protocols and media associated with the
>     application/json media type, MUST encode JSON text using UTF-8
>     [RFC3629].

This is not about the IETF.

If I buy a Mercedes, I want to get a car built by Daimler-Benz.
If people send me JSON, I want to get JSON (the UTF-8 form that everyone uses).

Now, there are other areas where, say, Mercedes is a woman’s name.  There might even be a restaurant called “Mercedes’ kitchen".  The objective cannot be that women or their restaurants no longer be called Mercedes (that the use of UTF-16 encoded JSON in C# or JavaScript becomes illegal).  It’s just when you sell a car as a Mercedes (send me an object as JSON), I want to get a Mercedes (JSON).

Consult a trade mark lawyer if that wasn’t clear :-)

Grüße, Carsten