Re: [GNAP] [OAUTH-WG] Publication has been requested for draft-ietf-gnap-core-protocol-15

Fabien Imbault <fabien.imbault@gmail.com> Thu, 29 June 2023 07:14 UTC

Return-Path: <fabien.imbault@gmail.com>
X-Original-To: txauth@ietfa.amsl.com
Delivered-To: txauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47C8C151530; Thu, 29 Jun 2023 00:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_BLOCKED=0.001, 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 zPp7Z2OjV8vU; Thu, 29 Jun 2023 00:14:48 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 4E334C14CEED; Thu, 29 Jun 2023 00:14:48 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id d2e1a72fcca58-66872d4a141so303292b3a.1; Thu, 29 Jun 2023 00:14:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688022888; x=1690614888; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AxReaP8uumFohmqP9vyJrso9AcLyKpBR6gcoq2id1Xo=; b=nLF84wszFWFyvHVc/6ScpCDsorOXZk0fRXoHv9npOuxeHTlu7rU5YhvNkSqIBKehN/ Le8LmjmMe62Am91ZJsoHjjDHgKYznbl4iJ0a8xdfrLLeFZoN1lat1onfBfKNJ7z109Qd XLJzbWZYQpGOOtGK/ZNLXANV66zkyhcyJF7ScKqoIvZyjBqwmYEDqR3sDpyCMhNrooym nrg1wcuSLTWwNmq5B0kLuai4p3W1egNbCl7/VD3gFK7cUcKyKEoxzuu+2zmnoP3oy8nu qFO6wFpLyTikDuyXe2OLydl1oDRjUzZZTdY1unCSg1lmGTIPNtd1z6YSCeVnFxKpUvLB A0dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688022888; x=1690614888; 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=AxReaP8uumFohmqP9vyJrso9AcLyKpBR6gcoq2id1Xo=; b=CbDvgFVJTD0sSOdNSbG0wWdI/MDufbxeEQncaNbA5R+dwwqGnCJcVmSvJGWUxt117p 7sgq8ZtPmG9+6ezfby1ZodQB82OFMIGgX5rQVCrtcd3swYoaJVMkT8sdO5JY14n6ZXjk xgz/KBmuPEheLz8OoALIXZkNdcDwmywUwFawkLLNf2PaFHXcvrbXW6iIhd466dRlHn4w mgnPJ2VEIyNVWwzrTsTnomHWNE9K0YWS/W1gPq8LSZmdnXHeZYbF/1bQbQNwIW5qRYtw SLyG148wrk89iODKbR5/zaWPU0gE4xcPu8NI5Ji8NWW2jEx81EvEFYcy2J6w9A3+/1HB vKcA==
X-Gm-Message-State: AC+VfDwBZ8+zHTRKxVYiGKNXEJn8EG/nN8hVaTQ58qkX8MMOv84JnrKH AyrEvmtju0zAybq9DPfVl3T2n2h9HZg4OCI/d7I=
X-Google-Smtp-Source: ACHHUZ4j343BR9ZWZnEfeC8gQLUtrWJTXuA6VXFdOzN7/rWQzFvNvRQsZSO1gbDc1JbWtd41llmrFR+8pskx4iKs6fg=
X-Received: by 2002:a17:90a:3dc1:b0:262:d20e:78a7 with SMTP id i59-20020a17090a3dc100b00262d20e78a7mr9134330pjc.2.1688022887546; Thu, 29 Jun 2023 00:14:47 -0700 (PDT)
MIME-Version: 1.0
References: <168781058231.21029.12700863560443453669@ietfa.amsl.com> <CAD9ie-t3pwJog-Kbwnx=sGcDsLgqKwSz_1UFP1LBbN7ucwCrow@mail.gmail.com> <SJ0PR00MB13180A125B0207E6F5914FA9E524A@SJ0PR00MB1318.namprd00.prod.outlook.com>
In-Reply-To: <SJ0PR00MB13180A125B0207E6F5914FA9E524A@SJ0PR00MB1318.namprd00.prod.outlook.com>
From: Fabien Imbault <fabien.imbault@gmail.com>
Date: Thu, 29 Jun 2023 09:14:36 +0200
Message-ID: <CAM8feuSdJsN_0AvZX9FH=Ptb9sO+gJF+VJ20YWWaG1xNJJFzAA@mail.gmail.com>
To: Kristina Yasuda <Kristina.Yasuda=40microsoft.com@dmarc.ietf.org>
Cc: Dick Hardt <Dick.Hardt@gmail.com>, Yaron Sheffer via Datatracker <noreply@ietf.org>, gnap-chairs@ietf.org, Yaron Sheffer <yaronf.ietf@gmail.com>, iesg-secretary@ietf.org, GNAP Mailing List <txauth@ietf.org>, oauth@ietf.org
Content-Type: multipart/alternative; boundary="00000000000095c4c005ff3f7489"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/S9rwmxoR6LbRo_AqekCZxtYlYh8>
Subject: Re: [GNAP] [OAUTH-WG] Publication has been requested for draft-ietf-gnap-core-protocol-15
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: GNAP <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2023 07:14:52 -0000

Dear Dick and Kristina,

Indeed there has been an interim meeting to discuss the PR related to the
last issue raised during IETF116. The change had been previously advertised
by Justin on the mailing list for open review, as always. The discussion
during the interim went through the diff and no outstanding question was
raised.

Best regards
Fabien

On Thu, 29 Jun 2023, 01:14 Kristina Yasuda, <Kristina.Yasuda=
40microsoft.com@dmarc.ietf.org> wrote:

> I would like to get some context too.
>
> After WGLC that started on Jan-07
> <https://mailarchive.ietf.org/arch/browse/txauth/>, I could only find one
> email
> <https://mailarchive.ietf.org/arch/msg/txauth/TohrHLdZXnzCi49vvE8Xi9QcLqE/>
> on the mailing list <https://mailarchive.ietf.org/arch/browse/txauth/>.
> Not sure who else’s feedback has been addressed in the changes mentioned in
> this email
> <https://mailarchive.ietf.org/arch/msg/txauth/nT8wHCJqLrZrJDR30I7TL5xyYUs/>
> .
>
> IETF116 meeting notes
> <https://notes.ietf.org/notes-ietf-116-gnap#GNAP-core-status> mention
> that there are some issues (token rotation) that need to be discussed and
> looks like there was an interim mtg, but there is nothing on the outcome of
> that mtg in the ML. (at least I can’t find the minutes).
>
>
>
> I also noticed that out of 8 implementations listed in the implementation
> statu
> <https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/504/files#diff-7b8259b080e6bc43f36d8a9a56f271c41f6a6471e088496ea8e25c2c6fec98acR5760>s
> as of Mar-06, four mention production, and other four are prototype (and
> given one of those is SecureKey and another one is Gen Digital (ex. Secure
> Key), that relationship should probably be clarified).
>
>
>
> Best,
>
> Kristina
>
>
>
> *From:* OAuth <oauth-bounces@ietf.org> *On Behalf Of * Dick Hardt
> *Sent:* Wednesday, June 28, 2023 2:05 PM
> *To:* Yaron Sheffer via Datatracker <noreply@ietf.org>
> *Cc:* gnap-chairs@ietf.org; yaronf.ietf@gmail.com; iesg-secretary@ietf.org;
> txauth@ietf.org; oauth@ietf.org
> *Subject:* Re: [OAUTH-WG] [GNAP] Publication has been requested for
> draft-ietf-gnap-core-protocol-15
>
>
>
> I just noticed this doc is up for publication.
>
>
>
> I did a quick search on the last call discussion, and did not see any +1s,
> nor any review by any of the active members of the OAuth WG.
>
>
>
> This is very surprising given the functional overlap with OAuth 2.0, and
> the years of deployment experience in the group.
>
>
>
>
>
>
>
> On Mon, Jun 26, 2023 at 1:16 PM Yaron Sheffer via Datatracker <
> noreply@ietf.org> wrote:
>
> Yaron Sheffer has requested publication of
> draft-ietf-gnap-core-protocol-15 as Proposed Standard on behalf of the GNAP
> working group.
>
> Please verify the document's state at
> https://datatracker.ietf.org/doc/draft-ietf-gnap-core-protocol/
>
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>