[OAUTH-WG] Fwd: New Version Notification for draft-ietf-oauth-par-06.txt

Brian Campbell <bcampbell@pingidentity.com> Tue, 02 February 2021 16:38 UTC

Return-Path: <bcampbell@pingidentity.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 475773A1E3A for <oauth@ietfa.amsl.com>; Tue, 2 Feb 2021 08:38:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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=pingidentity.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 auIYM__OEgiD for <oauth@ietfa.amsl.com>; Tue, 2 Feb 2021 08:38:37 -0800 (PST)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 28B823A1E32 for <oauth@ietf.org>; Tue, 2 Feb 2021 08:38:37 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id u25so28823115lfc.2 for <oauth@ietf.org>; Tue, 02 Feb 2021 08:38:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Kx1DVI2ipWWR1E1bOoCNTJgrgbopMXJvdIFKPuNt3wE=; b=VyOWnMIYFiS5lQZPI9c4nlrrLnVPUj3jbo94NHmIDFRjrj5bvcX5pBIA0a1NcAKS86 s6vGQVX+tIfOWGN286Q3eMle6kp6MW4O3kaxNwMNI6qlLizfNIHD5XLjsDZG27R5oBdn t8JCufZPyjWeJtnk+7h42ZDI0j0emdazxRbgGSN8Ibei18kKmIbWtYYh+o1/V35CkR4q 8prYsHkm6sXwnymZoydDgtivRaO3XWYniTrWZzNeiCvsk4eIIq6LZij+taFZGevgPiKZ h3r4YfrX1UAuak2Lnau+VOzdD0487kW3NV1TaTw7p/TfTU7zaq3aXgBZzF99W2etLp6e weNw==
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; bh=Kx1DVI2ipWWR1E1bOoCNTJgrgbopMXJvdIFKPuNt3wE=; b=sRlDi0uzQ9gT66jLlcAjXA2Z1LIn+1vVcojaTJ0xsyuYpn/1bgPXB+0SjBjBYXtnF3 ZnAtfiW1K5HywbuzhjI85tCLH+X0OTv1k60aXgckCr+Et6NxqCKZBFGBk4WJtm/xySmo COh3xxGdMn03sSpp4YPsvN0Dty/6pn91q1TxevdcR9KnHTIdP1yludb5a/TY91aTWZoi wFMpPFuTHDRs/32nNcrULWCN74mFmvqyXmRRj80OmRn6r/SmfZf60RGgNj+hrN7XnxUY krhBNEMC7pG5kubL7Vc/FEgLkkD9dDurfVhY12/Igb3x/1KsI0LOCiXXybz8VfKr38I8 jumg==
X-Gm-Message-State: AOAM531Z2U5LZ8uX5wMdWq8MOdiiNIEziXSnZQ7T0d8VRLUs7IabjmWf PPSpUnnBiFuFqfhsQ9Ara4gUsWr8aVWbQNrWdv5f109i+msGsmS1NfkNlc1gO93ZI66jGZa08UN p+a021WKfa5KZzye3VTQ=
X-Google-Smtp-Source: ABdhPJzymE4zRDfZz/Z7h5IFh+Eb4lDYWjQQRFGPhgFNcJI51e37MwYRcJ0WfCYatLzioTnTY4tzkcVxIPbBcYnArt0=
X-Received: by 2002:a05:6512:22c3:: with SMTP id g3mr10797935lfu.376.1612283915040; Tue, 02 Feb 2021 08:38:35 -0800 (PST)
MIME-Version: 1.0
References: <161228304270.14351.8018650885407574191@ietfa.amsl.com>
In-Reply-To: <161228304270.14351.8018650885407574191@ietfa.amsl.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Tue, 02 Feb 2021 09:38:08 -0700
Message-ID: <CA+k3eCTn+1d68DQ_DrXQ8wQLkmy9Gw0Lb+O51en6wnPeXihvHQ@mail.gmail.com>
To: oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000089b4b05ba5d1aa5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/_-eNnV3yHNVM9vnNLYZQbBY2yQo>
Subject: [OAUTH-WG] Fwd: New Version Notification for draft-ietf-oauth-par-06.txt
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: Tue, 02 Feb 2021 16:38:40 -0000

This new revision only adds a brief note clarifying that the presence of
"pushed_authorization_request_endpoint" in AS metadata is sufficient for a
client to know that it can use the PAR flow.


---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Tue, Feb 2, 2021 at 9:24 AM
Subject: New Version Notification for draft-ietf-oauth-par-06.txt



A new version of I-D, draft-ietf-oauth-par-06.txt
has been successfully submitted by Brian Campbell and posted to the
IETF repository.

Name:           draft-ietf-oauth-par
Revision:       06
Title:          OAuth 2.0 Pushed Authorization Requests
Document date:  2021-02-02
Group:          oauth
Pages:          22
URL:            https://www.ietf.org/archive/id/draft-ietf-oauth-par-06.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-oauth-par/
Html:           https://www.ietf.org/archive/id/draft-ietf-oauth-par-06.html
Htmlized:       https://tools.ietf.org/html/draft-ietf-oauth-par-06
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-par-06

Abstract:
   This document defines the pushed authorization request endpoint,
   which allows clients to push the payload of an OAuth 2.0
   authorization request to the authorization server via a direct
   request and provides them with a request URI that is used as
   reference to the data in a subsequent call to the authorization
   endpoint.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._