Re: [Ace] Resource, Audience, and req_aud

Jim Schaad <ietf@augustcellars.com> Mon, 11 February 2019 04:33 UTC

Return-Path: <ietf@augustcellars.com>
X-Original-To: ace@ietfa.amsl.com
Delivered-To: ace@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 003C4130F8E for <ace@ietfa.amsl.com>; Sun, 10 Feb 2019 20:33:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 waNFfNik-f69 for <ace@ietfa.amsl.com>; Sun, 10 Feb 2019 20:33:03 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8ADE130F89 for <ace@ietf.org>; Sun, 10 Feb 2019 20:33:02 -0800 (PST)
Received: from Jude (50.224.60.41) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Sun, 10 Feb 2019 20:32:57 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'Ludwig Seitz' <ludwig.seitz@ri.se>, 'Hannes Tschofenig' <Hannes.Tschofenig@arm.com>, <ace@ietf.org>
References: <VI1PR0801MB21126944E558E53992EB7FD3FA680@VI1PR0801MB2112.eurprd08.prod.outlook.com> <c62835cb-6d98-f5dc-d8d8-fe80181a8a5c@ri.se> <VI1PR0801MB2112BA5A6A6AC736575BC19BFA680@VI1PR0801MB2112.eurprd08.prod.outlook.com> <a8821e81-1819-5af8-7630-f61681476987@ri.se>
In-Reply-To: <a8821e81-1819-5af8-7630-f61681476987@ri.se>
Date: Sun, 10 Feb 2019 20:32:54 -0800
Message-ID: <064c01d4c1c2$dcdfaed0$969f0c70$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQDnZAU1sxpdIS46HQPOj9sBDOpqFQIGfyaKA1aPYOQBfBp92qd99D5Q
Content-Language: en-us
X-Originating-IP: [50.224.60.41]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ace/SSl4N4LhZRlCtwNajcVSw1mwFZI>
Subject: Re: [Ace] Resource, Audience, and req_aud
X-BeenThere: ace@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Authentication and Authorization for Constrained Environments \(ace\)" <ace.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ace>, <mailto:ace-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ace/>
List-Post: <mailto:ace@ietf.org>
List-Help: <mailto:ace-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ace>, <mailto:ace-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2019 04:33:05 -0000


> -----Original Message-----
> From: Ace <ace-bounces@ietf.org> On Behalf Of Ludwig Seitz
> Sent: Thursday, February 7, 2019 11:33 PM
> To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>om>; ace@ietf.org; ace-
> chairs@ietf.org
> Subject: Re: [Ace] Resource, Audience, and req_aud
> 
> On 07/02/2019 17:12, Hannes Tschofenig wrote:
> > Hi Ludwig,
> >
> >> What I understood from the feed-back is that using a parameter called
> >> "aud" in a request to the token endpoint would be interpreted as a
> >> restriction on the audience of authorization servers that are
> >> addressed by this request.
> >
> > I am not talking about a parameter called 'aud'. Take a look at the
> > token exchange spec -- the parameter is called 'audience'. 'aud' is
> > the name of the claim.
> >
> > Ciao Hannes
> >
> >
> 
> Ok I see, I had that mixed up.
> 
> Let me just note that having an "audience" parameter and an "aud"
> parameter (which is also referred to as 'audience') is not ideal when one
> wants to avoid confusion.
> 
> It seems the token-exchange draft is quite advanced, so referring to its
> "audience" parameter instead of defining "req_aud" (with more or less the
> same semantics) seems reasonable to me.
> 
> Do the chairs think that this would unduly delay the progress of draft-ietf-
> ace-oauth-params?

It looks like the are about the same point as we are.  So no I don't think it would slow things down to make this change.

Jim

> 
> /Ludwig
> 
> 
> --
> Ludwig Seitz, PhD
> Security Lab, RISE
> Phone +46(0)70-349 92 51