Re: [OAUTH-WG] Question regarding RFC 7592

Travis Spencer <travis.spencer@curity.io> Wed, 18 September 2019 08:56 UTC

Return-Path: <travis.spencer@curity.io>
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 8FAEB12008D for <oauth@ietfa.amsl.com>; Wed, 18 Sep 2019 01:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=curity-io.20150623.gappssmtp.com
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 irEvnMjBi1p3 for <oauth@ietfa.amsl.com>; Wed, 18 Sep 2019 01:56:33 -0700 (PDT)
Received: from mail-yw1-xc2d.google.com (mail-yw1-xc2d.google.com [IPv6:2607:f8b0:4864:20::c2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B3C31200F7 for <oauth@ietf.org>; Wed, 18 Sep 2019 01:56:33 -0700 (PDT)
Received: by mail-yw1-xc2d.google.com with SMTP id 201so2168668ywn.13 for <oauth@ietf.org>; Wed, 18 Sep 2019 01:56:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=curity-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jIRY+X5R78ay1YxAcQhAgXfwkLIX25JJYGhNG/Botpg=; b=Vyj0AUUTbDYy/dMTWZOjnJVkUoFRPleUCu3HBEbQLkWMz5pskncM8sbiRO4NLZmPM5 O1pobymEOHgpFNl/2lqoM6KV7ZASP6KKQm3YMZaul2z3ES/tVmzTiYtka7RuxPlLlHMs q+aL6zcW5LH1yymEjSIRiN5Xqo55N/DlcDzMON5nGxTdwUwqsX7ac5b1oGTByykhQ2OX 9k9Yg3ARlg+tNi3etrg4JIGGpixz5wI5S/2mwh5OmHN65Sj8y7B4DdykgDmMpvDb70zr pKNOMOFsyIZqMYU25NWlcDO4ErYmYqfDSYjiAMJQdPgK36/yVUTjcCAryHEQCkH3C90P wixg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jIRY+X5R78ay1YxAcQhAgXfwkLIX25JJYGhNG/Botpg=; b=oD867bSpbOVzo3opLf0r34Jtk7yrWwd2Wwi3J4QqX1TN4mvOoDziMnFhmgTl1hcUnA ObaznkTD5NDIynwIzCvkWe2w0Jc6NiagKgi4M/LHbgH26J+NVBfKO1LWSL4cWSOEObyC NZzkCX06JONqLjGnSTDCap/3voqqN6cCaOcVJLvZGrzQss+79xZta6P6b29tkTz8Z5IC ffEdvuBHrIrF5EzpqomHg1F6njWYwbMhk6SRiSfRiNVSWLIGCspdOhDNeb2RYUlC21F7 RS/wX0p1eHKvgkqtOIKR5zjreviPtWDD9wMeVGJOsvCGGaCe2L4OLkhtEPaDWSGjDtKh OEmA==
X-Gm-Message-State: APjAAAV718ocTcfs6C1l/8k13svKmN9PZe8dO3SaEtZsPUsvOX7EXRxB nCDghYycVizVg/dQj024KMvRGXe7YI7yEO1t4i6i7w==
X-Google-Smtp-Source: APXvYqxRTEW6ENZVbQ1o3f/FreYN2B56OC1HK7ZlMEx1B0gwy+0bSTendwPurtdi7URQXk5BK2Pw0V/VWe1RsxoiQoA=
X-Received: by 2002:a81:990e:: with SMTP id q14mr2426021ywg.47.1568796992789; Wed, 18 Sep 2019 01:56:32 -0700 (PDT)
MIME-Version: 1.0
References: <ae35a0f3b9f74618add918d9339be753@STEMES002.steteu.corp> <CAEKOcs3EtjLHRaRmpCa_GrpuXtqVMWHrmH0oPBB-b+2yzhKHaw@mail.gmail.com> <db205bcad6ac495bb558e2b6181ba546@STEMES002.steteu.corp> <CAEKOcs1ZmnjJ=DXjG2yvAOwy3jbAnGaXQLEK0TeU0qD7p88Z0A@mail.gmail.com>
In-Reply-To: <CAEKOcs1ZmnjJ=DXjG2yvAOwy3jbAnGaXQLEK0TeU0qD7p88Z0A@mail.gmail.com>
From: Travis Spencer <travis.spencer@curity.io>
Date: Wed, 18 Sep 2019 10:56:21 +0200
Message-ID: <CAEKOcs3Oqfp19LEGdKwwqzv_OTPOVZb5zLfZez5DLhfu9TfMjw@mail.gmail.com>
To: =?UTF-8?Q?Robache_Herv=C3=A9?= <herve.robache@stet.eu>
Cc: "oauth@ietf.org" <oauth@ietf.org>, Mark Dobrinic <mark.dobrinic@curity.io>
Content-Type: multipart/related; boundary="0000000000007b4e890592d00312"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/zfSTPwNdIX_5NBIOLpA2pAmO69c>
Subject: Re: [OAUTH-WG] Question regarding RFC 7592
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: Wed, 18 Sep 2019 08:56:36 -0000

On Fri, Sep 13, 2019 at 3:18 PM Travis Spencer <travis.spencer@curity.io>
wrote:

> Ya, this part is confusing. I didn't get it at first either.
>

Seems I'm still a bit confused ;-)

this metadata isn't defined in RFC 7591 but discussed in section 1.3; that
> spec leaves the metadata out of scope. It is, however, profiled in section
> 3.2 of OIDC DCR (see registration_access_token in section 3.2
>

Mark Dobrinic pointed out to me this morning that RFC 7591 (DCR) is updated
by 7592 (DCRM) in section 3 to include the same registration_access_token
response metadata that OIDC defines.