Re: [OAUTH-WG] Your opinion about draft-ideskog-assisted-token

Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com> Tue, 16 February 2021 23:53 UTC

Return-Path: <rifaat.s.ietf@gmail.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 8B78D3A12F4; Tue, 16 Feb 2021 15:53:48 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=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=gmail.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 uyIwUD-JPvBR; Tue, 16 Feb 2021 15:53:46 -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 79E733A12F8; Tue, 16 Feb 2021 15:53:46 -0800 (PST)
Received: by mail-lf1-x12f.google.com with SMTP id d3so18696059lfg.10; Tue, 16 Feb 2021 15:53:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mEaEvD4I0M1y38cj3LRzGWbxz8pjwEbnkPW9OvARtK0=; b=eNbYQ5CXr9HPLCcKy8gitFhq7PhBzNCNN7QbSJn9HY0JaGRb36Mxg0hcq2Chym1i9R oQj4xrJQ69fqIDxAoWdMPVVoG9mFhuxBjM2H38hrcgObZAyrN/nAsUgqIiyC1Aa9J686 LL3XODNObQVisZk8WYVDaSFG0+kaudTttS5cHwfeGNqzjJnd1jPyXxZ9G5OwqLo3cc3K d0IsrJcPfgqIGrEYoiplZS6gyR++NTcr/sKTY8ZJNiCh/sqOxgu1a6yWvLKPjg5esRHO 5FiCjtFXywhqFxJxjuivHHa7HvcbxooxDnP+TLDAvp0+idrhmz/zIfXNf3X8Xt8rpB66 R+iA==
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=mEaEvD4I0M1y38cj3LRzGWbxz8pjwEbnkPW9OvARtK0=; b=m15FiOB5vG+NjGPihh8eoPLtENoP8AcnSOLHUYfxlxoaHyE4/+f0w+2KIICbHyPR95 DUcsUvzVn8Ro8yyl7Pa+2kbQA+rIwyEXBEIonhsJdyPhqrWRDO1UEsXbipzuizLBkYMj AQZ4qtn66+R3an11cS4y8N4WHuBPM5r9UHREkVY+Znh/OgYcY5QCJ25kJO0WWHGft/WQ HUYcCtGzfLRQWVhL5Y+n+s1EANxc1PDeMsNTQIUu1rcB2aB0kqgsls7B2ihC92fXhJt1 I8NumZQildgirhZQmqALDyhDago0uiPnken1JMjrk4V3nneuCU4k5onWZN5sFamDqodd UYGA==
X-Gm-Message-State: AOAM5330LFK7Lt4Wbzv3xjHBI3HF4KY4WcVprmFV3cGXTCkcOarGBcLd YdYWQdP/+rExMz84a1NpaL0NMtFrEV7e2ynRjWr8I2O/O9Y=
X-Google-Smtp-Source: ABdhPJwjDork1kJKRI2QygwlviHit+waOm6PBfYBAla0Uak5bgzGpCK+73TVD4xUOq+YAPguNOxwwFbHJCu0StIexRA=
X-Received: by 2002:a19:9c1:: with SMTP id 184mr12770178lfj.582.1613519624660; Tue, 16 Feb 2021 15:53:44 -0800 (PST)
MIME-Version: 1.0
References: <1e5f0e825a2580f68c92aa5a1d798090.squirrel@www.rfc-editor.org> <702cf2e8d762ba733becdb5c735f72a9.squirrel@www.rfc-editor.org>
In-Reply-To: <702cf2e8d762ba733becdb5c735f72a9.squirrel@www.rfc-editor.org>
From: Rifaat Shekh-Yusef <rifaat.s.ietf@gmail.com>
Date: Tue, 16 Feb 2021 18:53:33 -0500
Message-ID: <CADNypP9HjpeW1RCfn8udFawTeWY9pD0t6KTb_T=Bc=c8kLzwmQ@mail.gmail.com>
To: rfc-ise@rfc-editor.org
Cc: draft-ideskog-assisted-token@ietf.org, oauth <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000010ebb805bb7cd05e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/s5TGeRPdzc0X8hfw3qi41PUJyY0>
Subject: Re: [OAUTH-WG] Your opinion about draft-ideskog-assisted-token
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, 16 Feb 2021 23:53:49 -0000

Hi Adrian,

This document is definitely in scope for the OAuth WG.
We are planning a series of virtual interim meetings after the coming IETF
conference, and we would be happy to schedule one of these meetings to
discuss this document.

Regards,
 Rifaat


On Mon, Feb 15, 2021 at 1:59 PM RFC ISE (Adrian Farrel) <
rfc-ise@rfc-editor.org> wrote:

> Hi OAuth,
>
> The authors of draft-ideskog-assisted-token [1] have approached me
> requesting that the draft be published as an Informational RFC in the
> Independent Submission Stream [2].
>
> The draft extends the OAuth 2.0 framework to include an additional
> authorization flow for single page applications called the assisted token
> flow. It is intended to enable OAuth clients that are written in
> scripting languages (such as JavaScript) to request user authorization
> using a simplified method. Communication leverages HTML's iframe element,
> child windows, and the postMessage interface. This communication is done
> using an additional endpoint, the assisted token endpoint.
>
> It is clear to me that this work could be in scope for OAuth and I want to
> be sure that both:
> - there is no interest within the WG in pursuing this approach
> - there is no perceived harm to existing OAuth work if this goes ahead
>
> I'd appreciate any opinions.
>
> Many thanks,
> Adrian
> --
> Adrian Farrel (Independent Submissions Editor),
> rfc-ise@rfc-editor.org
>
> [1] https://datatracker.ietf.org/doc/draft-ideskog-assisted-token/
> [2] https://www.rfc-editor.org/about/independent/
> >
> >
>
>
> --
> Adrian Farrel (ISE),
> rfc-ise@rfc-editor.org
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>