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

Dick Hardt <dick.hardt@gmail.com> Fri, 07 July 2023 05:44 UTC

Return-Path: <dick.hardt@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 45F48C15153F; Thu, 6 Jul 2023 22:44:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 Oxq5tr4avsoc; Thu, 6 Jul 2023 22:44:31 -0700 (PDT)
Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (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 55C23C14CE54; Thu, 6 Jul 2023 22:44:31 -0700 (PDT)
Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-57045429f76so18666537b3.0; Thu, 06 Jul 2023 22:44:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1688708670; x=1691300670; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=JWS1/KioMdOM9+CnMCq9K3qRBQYBpKQEHYb6JDyVTzU=; b=hUHh7Rr2cGyNz0dncyZVnyMwj3/rgA/3YpSyd9mU51qc8MIODVSApWWfholthNV/0J vMVgwZNCWiwkxAFsnsg8aDNQNOFutG7XeHs3RLJEz7q/l24XL3095S9bujWcp+zr1sOE CyBv2X9KxNmuhP7m1FY9Oua6seeFvVEOuEfC3H+JeChGo1ihhYMYXsTVWj5NTknD2eS1 moc3b2pZph78QLYPGPBYaDyd21+mVn4Bu6WsUU8UCb/dvJ4RL8BQHkdqqiO2p4WvjZIW R22mJQH8hOO8jJe8zYkvpLaNmdhjXnkP4YcvBJ6yPnQ1c3InVodwdFKjJqdm/8kwen+l H5Zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688708670; x=1691300670; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=JWS1/KioMdOM9+CnMCq9K3qRBQYBpKQEHYb6JDyVTzU=; b=Eh+SpIpLwBpoQK/CBTUDsylxzlLiWr6+rmTuXmFWTiEqdxe/FNOPwlU/sncz+fuXkp +j+jjjPKQCYed1KDUrpPC+e5M6IKaD3nrUsXOSD48HpNll7fAXGTGdRclxDqu1gQ4N0U vKooxDStiSzphtriPnwFHUmoDTUeOMWfL9RAHBM+l/EBIMNaVsIF5zbUz6udBJ3Pm+ig wv1fQMVYGMLl90C0yWP4PyA9LrbkKFUanbw31re3djrSUT+qiNMp7EOJva3UpEVbfl/k cIa31Bqe2FjtMr0wp9nUQIduUWe/usO50NfAeB5oP7Zzdq1edXnuKwvn7YuriU/96Vy/ EsGw==
X-Gm-Message-State: ABy/qLbP/3fqQP0jIH779LrIp2LBUJCJfCejL4Q5RCKOr4QV5aYWYPYV t9P2YnVeEAY7E+Wlk6jxqTmn9ZPH1kGGNuLVPJJTnC66TNRnoQ==
X-Google-Smtp-Source: APBJJlGffx4r9NV+WiPuTN0kQyUTl3Ese2CJR7H/ZsQrrbDwWBR/aolsgbvGgL6+tZuk5NR1aiw0eauFWIzxH+UsINA=
X-Received: by 2002:a0d:d9c3:0:b0:57a:4fe1:d0e0 with SMTP id b186-20020a0dd9c3000000b0057a4fe1d0e0mr2630148ywe.52.1688708670030; Thu, 06 Jul 2023 22:44:30 -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>
Reply-To: Dick.Hardt@gmail.com
From: Dick Hardt <dick.hardt@gmail.com>
Date: Thu, 06 Jul 2023 22:43:53 -0700
Message-ID: <CAD9ie-sVaa6YByjqA_9qy7Ra+OQpd-h2syxa+N3cywn=XuC75g@mail.gmail.com>
To: Kristina Yasuda <Kristina.Yasuda@microsoft.com>
Cc: Yaron Sheffer via Datatracker <noreply@ietf.org>, "gnap-chairs@ietf.org" <gnap-chairs@ietf.org>, "yaronf.ietf@gmail.com" <yaronf.ietf@gmail.com>, "iesg-secretary@ietf.org" <iesg-secretary@ietf.org>, "txauth@ietf.org" <txauth@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006808cb05ffdf20d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/QCXTyIoWqpIQEo31Ya_o5oe_0L8>
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: Fri, 07 Jul 2023 05:44:35 -0000

I was looking over the upcoming SF agenda and was very surprised to see
that the gnap session overlaps with the oauth session,

Is the GNAP WG intentionally wanting to avoid engaging with members of the
OAUTH WG?


On Wed, Jun 28, 2023 at 4:13 PM Kristina Yasuda <
Kristina.Yasuda@microsoft.com> 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
>
>