Re: [Json] binary data in I-JSON
Carsten Bormann <cabo@tzi.org> Mon, 21 July 2014 19:49 UTC
Return-Path: <cabo@tzi.org>
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 736E21A03C9 for <json@ietfa.amsl.com>; Mon, 21 Jul 2014 12:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] 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 Y-oF4kq020aS for <json@ietfa.amsl.com>; Mon, 21 Jul 2014 12:49:48 -0700 (PDT)
Received: from 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 BA7A41A03C8 for <json@ietf.org>; Mon, 21 Jul 2014 12:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s6LJnfCx001509; Mon, 21 Jul 2014 21:49:41 +0200 (CEST)
Received: from dhcp-9c03.meeting.ietf.org (dhcp-9c03.meeting.ietf.org [31.133.156.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 9BB8F5E9; Mon, 21 Jul 2014 21:49:39 +0200 (CEST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6iur+AQO=ZfxiZ8SkEyzJE_huuiVyP1BtbKUHpv2SGXmOg@mail.gmail.com>
Date: Mon, 21 Jul 2014 15:49:36 -0400
X-Mao-Original-Outgoing-Id: 427664976.55521-c0f8849d61e5b0b3e0b70878f39154b8
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5EF9616-991C-4CE2-B783-A8ACAA96453B@tzi.org>
References: <2EB7C24D-5A94-47DC-877E-E0EFC6F789BA@nic.cz> <CAHBU6iur+AQO=ZfxiZ8SkEyzJE_huuiVyP1BtbKUHpv2SGXmOg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/SVowKckn13WESDQ8ac98QNgNhig
Cc: Ladislav Lhotka <lhotka@nic.cz>, JSON WG <json@ietf.org>
Subject: Re: [Json] binary data in I-JSON
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, 21 Jul 2014 19:49:48 -0000
For this usage, base64 and base64url are exactly equivalent. For other usages, base64url has advantages. If you pick one, it has to be base64url. Of course, then you get problems with the base64 legacy. You can’t win this one. Do it right or do it compatibly. Grüße, Carsten
- [Json] binary data in I-JSON Ladislav Lhotka
- Re: [Json] binary data in I-JSON Tim Bray
- Re: [Json] binary data in I-JSON Carsten Bormann
- Re: [Json] binary data in I-JSON Tim Bray
- Re: [Json] binary data in I-JSON Ladislav Lhotka
- Re: [Json] binary data in I-JSON Carsten Bormann
- Re: [Json] binary data in I-JSON Jacob Davies