From nobody Mon Jan 30 10:12:50 2023 Return-Path: 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 195ABC16B5B5 for ; Mon, 30 Jan 2023 10:12:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.094 X-Spam-Level: X-Spam-Status: No, score=-2.094 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXHq2WPj4yjv for ; Mon, 30 Jan 2023 10:12:45 -0800 (PST) Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D05C16B5B4 for ; Mon, 30 Jan 2023 10:12:45 -0800 (PST) Received: by mail-wm1-x334.google.com with SMTP id j29-20020a05600c1c1d00b003dc52fed235so3271419wms.1 for ; Mon, 30 Jan 2023 10:12:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=W9a+6amXkrfOXUs470q8KIbhBGWvuHav/G3gQvvfnDY=; b=QhU1psjg3l1/8Acl7SVioeHSwgLAd/2URMrBHMSYV8lfh0AAvl1jppBORsk+vpPCtY /BdwhKwEbO2j8hSzdGGzQlAdom1XQUzRR3pyP8xCAWhX7YjUoMyUWK1CXwaf/kL06m/1 q4dCsA4sr/yAWCZTpg6lqByjFXHYJYDbuyeJp6YoZ9A6bFoSWnaAcEwJNo5ccvWRjNLY 7TV8vBqHnI6VhTtq+cU6ca79tQFU/I0/juysLhSxTC3Prow5/CEEbl1N/hGG2iz72Idg XfDEuhYt9JfCoGJ1D5bGO2j+T4hDOpXKGHuLO/jwvRjtWWBvZMUBfs2342BVEYPC+CCu ULFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=W9a+6amXkrfOXUs470q8KIbhBGWvuHav/G3gQvvfnDY=; b=MTURf0PzK/Ib1YbrjF0Qs3BJior5BukjCH5Br4tTMMcy6uXko4Fn6opBygYcQ06FQg IyV+9r+XxrOy7Vh2bdU6Zi66m5UTtw1MFIv7fkb/e5nEQnXAJZuHGTIpe3I8Y4IqdSDu 7fQOteRPbnmXfG0AFv/2A3Hav9xYR0Em06qq6f+36CGzJnmHAUVEWl22Cq+PpQKGc72P yksbWaSDVgeZfwZIyhDMQqNVTXlJO3KfI3zbUy7JQxp8oF7igw1Xq1glN+wWhYM8ds4+ Td4JU7iMPgxZLjunUyKLUJFpM050CMATHnYKK+X0SM88HfxwUHhsq9aks4LDnxUYjNF0 dj7w== X-Gm-Message-State: AO0yUKWDmq97BnthU/+yTMzhlRh9/b9iaX8fmtXokQk5TA69pCQgJwTF ylmi5gUxlxG0pXh6ar7PxZOpbR9CyKTyyT38n0w= X-Google-Smtp-Source: AK7set+O7B8te65WkLRJpq2vTxflDKJn6G2gvz6BsseSD+MODXZ2D3wyr/ITeStRRxS77XEXmrBnTDHS/7VCWbeQXlE= X-Received: by 2002:a1c:2b01:0:b0:3dc:20e9:8f0d with SMTP id r1-20020a1c2b01000000b003dc20e98f0dmr1187070wmr.54.1675102363516; Mon, 30 Jan 2023 10:12:43 -0800 (PST) MIME-Version: 1.0 References: <5E5CAC37F6AB415CA3A8CF2D55120412@Ultrabook1> <9955924b-85d4-3165-b40a-ab53b7a5f61d@aol.com> <150CA19C7723490D8075BBF5E9F76E24@Ultrabook1> In-Reply-To: <150CA19C7723490D8075BBF5E9F76E24@Ultrabook1> From: Rifaat Shekh-Yusef Date: Mon, 30 Jan 2023 13:12:32 -0500 Message-ID: To: Markus Cc: oauth@ietf.org, George Fletcher Content-Type: multipart/alternative; boundary="00000000000057028805f37f290e" Archived-At: Subject: Re: [OAUTH-WG] OAUTH for Web Proxy authentication X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jan 2023 18:12:49 -0000 --00000000000057028805f37f290e Content-Type: text/plain; charset="UTF-8" Hi Markus, As Goerge mentioned, there is no such document that covers this. What use case(s) do you have in mind for this? Regards, Rifaat On Sat, Jan 28, 2023 at 7:50 PM Markus wrote: > Thank you. > > Regards > Markus > *From:* George Fletcher > *Sent:* Saturday, January 28, 2023 1:43 PM > *To:* Markus; oauth@ietf.org > *Subject:* Re: [OAUTH-WG] OAUTH for Web Proxy authentication > > To my knowledge that spec doesn't exist. I'll let others chime in if they > have seen a proposal in that regard. > > In regards to which working group, given the core topic is OAuth > authorization, I would present it here at a minimum. > > Thanks, > George > > On 1/22/23 7:06 AM, Markus PlusNet wrote: > > Dear WG, > > I am new to oauth and wonder which WG would be responsible for > reviewing a Spec for Proxy authentication > https://httpwg.org/specs/rfc9110.html#auth.client.proxy using oauth or > does that spec already exist ? > > Thank you > Markus > > > _______________________________________________ > OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth > > > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > --00000000000057028805f37f290e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Markus,

As Goerge mentioned, th= ere is no such document that covers this.
What use case(s) do you= have in mind for this?

Regards,
=C2=A0R= ifaat


On Sat, Jan 28, 2023 at 7:50 PM Markus <markus@moeller.plus.com> wrote:=
Thank you.
=C2=A0
Regards
Markus
Sent: Saturday, January 28, 2023 1:43 PM
To: Markus; oauth@ietf.org
Subject: Re: [OAUTH-WG] OAUTH for Web Proxy=20 authentication
=C2=A0
To my knowledge that spec doesn't ex= ist.=20 I'll let others chime in if they have seen a proposal in that regard.
In=20 regards to which working group, given the core topic is OAuth authorization= , I=20 would present it here at a minimum.

Thanks,
George

On 1/22/23 7:06 AM, Markus PlusNet wrote:
Dear WG,
=C2=A0
=C2=A0=C2=A0=C2=A0 I am new to oauth and wonder which WG would be=20 responsible for reviewing a Spec for Proxy authentication https://httpw= g.org/specs/rfc9110.html#auth.client.proxy=20 using oauth or does that spec already exist ?
=C2=A0
Thank you
Markus
=C2=A0

______________________________________________=
_
OAuth mailing list
OAuth@ietf.org
h=
ttps://www.ietf.org/mailman/listinfo/oauth

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth
--00000000000057028805f37f290e--