Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-token-exchange (version 19)

Vladimir Dzhuvinov <vladimir@connect2id.com> Mon, 04 November 2019 20:12 UTC

Return-Path: <vladimir@connect2id.com>
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 D9688120832 for <oauth@ietfa.amsl.com>; Mon, 4 Nov 2019 12:12:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 WGTsGJITX9rY for <oauth@ietfa.amsl.com>; Mon, 4 Nov 2019 12:12:52 -0800 (PST)
Received: from p3plsmtpa08-04.prod.phx3.secureserver.net (p3plsmtpa08-04.prod.phx3.secureserver.net [173.201.193.105]) (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 3351512082E for <oauth@ietf.org>; Mon, 4 Nov 2019 12:12:52 -0800 (PST)
Received: from [192.168.0.102] ([94.155.17.54]) by :SMTPAUTH: with ESMTPSA id RiiWikdkpPReBRiiYiAvS9; Mon, 04 Nov 2019 13:12:51 -0700
To: oauth@ietf.org
References: <CAPiTtb73FQ0d4H31-hFJPUVnPmnpnsznw-SdYWgM5qCBaZ84sw@mail.gmail.com>
From: Vladimir Dzhuvinov <vladimir@connect2id.com>
Openpgp: preference=signencrypt
Organization: Connect2id Ltd.
Message-ID: <04d91af7-502b-fbd8-8cd6-0edd96d85b97@connect2id.com>
Date: Mon, 4 Nov 2019 22:12:47 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAPiTtb73FQ0d4H31-hFJPUVnPmnpnsznw-SdYWgM5qCBaZ84sw@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms050909070609060200030109"
X-CMAE-Envelope: MS4wfB4nSdEYKUDKT2bzZqbEyCj52qWgZwjp+jpWrXNMGdpXnPT6HmYq8WQ8S5UD41cTeBSZJ0K4dFGAHwZMhM7HJPEhPrIMSGaF4A53bk+JpfY1TiH7wg5M Rzrpqays9OPugnPa66vwqVc90ZcmSJUNneGu7XnuiNv36wDVSBdZdJzK
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/voHo4ETHMSxyl-Q0TokqgDhbbhU>
Subject: Re: [OAUTH-WG] Mail regarding draft-ietf-oauth-token-exchange (version 19)
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, 04 Nov 2019 20:12:55 -0000

From what I see -19 hasn't expired:

Expires: January 21, 2020


Perhaps somebody else could answer your second question, but for me it's
essentially at a stage when it's a done deal.

Vladimir

On 04/11/2019 20:26, Luke Synnestvedt (US - ADVS) wrote:
> Hello IETF OAuth team,
>
> I'm drafting some internal reference architecture guidance on the
> topic of Token Exchange within an OAuth 2.0
> authentication/authorization flow and have relied heavily on the most
> recent draft
> <https://tools.ietf.org/html/draft-ietf-oauth-token-exchange-19> which
> I know has since expired. I also see that this document has been sent
> for publication approval - is there an update from the team regarding
> when this document may be published?
>
> Thanks,
> Luke Synnestvedt