Re: [OAUTH-WG] draft-ietf-oauth-json-web-token-19 - Examples

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 28 April 2014 08:27 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA6B21A08EC for <oauth@ietfa.amsl.com>; Mon, 28 Apr 2014 01:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level:
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 X1ANgdSOFSOg for <oauth@ietfa.amsl.com>; Mon, 28 Apr 2014 01:27:21 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9771A07C9 for <oauth@ietf.org>; Mon, 28 Apr 2014 01:27:20 -0700 (PDT)
Received: from [192.168.131.128] ([80.92.122.106]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MH0eg-1WiYmi1Dvu-00Ds5D; Mon, 28 Apr 2014 10:27:18 +0200
Message-ID: <535E1010.6000006@gmx.net>
Date: Mon, 28 Apr 2014 10:23:44 +0200
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian Campbell <bcampbell@pingidentity.com>
References: <535A3AF4.4060506@gmx.net> <5E2E0F9B-AB61-43AA-B182-E776C97C83FE@adobe.com> <535A5819.2030805@gmx.net> <CA+k3eCTRwPB-BNAoSkzsPCYjP-tuynLLxxHMJcvA4kDFj3aRLQ@mail.gmail.com>
In-Reply-To: <CA+k3eCTRwPB-BNAoSkzsPCYjP-tuynLLxxHMJcvA4kDFj3aRLQ@mail.gmail.com>
X-Enigmail-Version: 1.5.2
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="kB7IkPuSAwR1EEC2xFJ7alQLxCQ4HOhbW"
X-Provags-ID: V03:K0:5NDBoh5eacfsVzCu443fmk5LLokYzg2bx/FC2SDLZDAY5wTKoE6 lbJiYJfVLpESxuUx7UrbAvUtMSckpsMBlqBNOpePrgrWDl5KYEPOxpmbDqKAnlGG+mG0qK7 lLKzwJffjs8GT7xsauWLvvTGTnTDB3C1sshzSi6wFIGrvU7Km1mvIGPiYKKAdH1YPo+jcO5 oMzkeE9ffW52KBmv5lMLQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/wVqO4v4AR712ZhHwnvPXzxE3wSw
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] draft-ietf-oauth-json-web-token-19 - Examples
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 28 Apr 2014 08:27:23 -0000

Hi Brian,

you are entirely correct. I believe I read the paragraph not carefully
enough. For some reason I read octal rather than octet and that makes,
of course, a huge difference.

Sorry. My fault.

Ciao
Hannes

On 04/25/2014 04:22 PM, Brian Campbell wrote:
> Note that the draft is showing an *octet sequence* with each individual
> octet being shown as decimal value. It doesn't state anything about
> using octal, the base-8 number system. Those octets also show
> unambiguously what is being base64url encoded (including the line
> endings via "13, 10") - no matter how the unencoded headers or bodies
> are shown in the draft, there's going to be potential confusion about
> what white space and line breaks is or is not to be included in the
> encoding and serialization so giving the octet sequence alleviates that.
> It's maybe also worth noting that the JOSE suite of specs all use the
> same notation and text in their examples.