IETF Logo Mail Archive

Re: [OAUTH-WG] OAuth Request JSON Encoding

Carsten Bormann <cabo@tzi.org> Mon, 13 July 2020 15:32 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24443A13CD for <oauth@ietfa.amsl.com>; Mon, 13 Jul 2020 08:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-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 zty21uBG1esd for <oauth@ietfa.amsl.com>; Mon, 13 Jul 2020 08:32:55 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 426FA3A13BD for <oauth@ietf.org>; Mon, 13 Jul 2020 08:32:54 -0700 (PDT)
Received: from [172.16.42.100] (p5089ae91.dip0.t-ipconnect.de [80.137.174.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4B572D40mCz17pd; Mon, 13 Jul 2020 17:32:52 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAK2Cwb4XLL0gWwY8XCSmfe=hGE0G5RFFUf-FQE_DhHR1KYtb_w@mail.gmail.com>
Date: Mon, 13 Jul 2020 17:32:51 +0200
Cc: Justin Richer <jricher@mit.edu>, oauth <oauth@ietf.org>
X-Mao-Original-Outgoing-Id: 616347170.994398-81ce565bf2b0eb1a90aa3892f14042d5
Content-Transfer-Encoding: quoted-printable
Message-Id: <C876645D-657C-448E-87CE-9A794549A175@tzi.org>
References: <0E71D133-A516-4F1C-92CB-36F181B1BA4A@mit.edu> <CAK2Cwb4XLL0gWwY8XCSmfe=hGE0G5RFFUf-FQE_DhHR1KYtb_w@mail.gmail.com>
To: Tom Jones <thomasclinganjones@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/AZ2ytFK_lsVQZrOJ6lJGz7LWitU>
Subject: Re: [OAUTH-WG] OAuth Request JSON Encoding
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2020 15:32:58 -0000

On 2020-07-13, at 17:19, Tom Jones <thomasclinganjones@gmail.com> wrote:
> 
> What, exactly is json encoding?

JSON is defined in RFC 8259.
The term “encoding” is ambiguous here, it could be used for the encoding of a JSON text (which employs UTF-8) or the representation of an application data model using the JSON generic data model.

> It sounds like a python or java method.

Many languages and platforms support JSON.

> Afaik json can be encoded in utf 8 16 or 32.

Early definitions of JSON said so, even though that practically never happened in interchange.  RFC 8259 supports UTF-8 encoding only.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email