
From nobody Tue Mar  1 03:37:49 2022
Return-Path: <denis.ietf@free.fr>
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 DAAF83A07CD for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 03:37:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.129
X-Spam-Level: 
X-Spam-Status: No, score=-6.129 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 cCfySSOpZvSk for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 03:37:45 -0800 (PST)
Received: from smtp.smtpout.orange.fr (smtp06.smtpout.orange.fr [80.12.242.128]) (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 2AB4B3A07B4 for <txauth@ietf.org>; Tue,  1 Mar 2022 03:37:20 -0800 (PST)
Received: from [192.168.1.11] ([82.121.202.228]) by smtp.orange.fr with ESMTPA id P0obnUXIKuCn2P0ocnOnlR; Tue, 01 Mar 2022 12:37:17 +0100
X-ME-Helo: [192.168.1.11]
X-ME-Auth: OWU3ZmVkYWM0M2UwZWM1YifxM2Q3ZDk1YiUzNWJiZTM2MiliMTI0N2YxZmQ=
X-ME-Date: Tue, 01 Mar 2022 12:37:17 +0100
X-ME-IP: 82.121.202.228
Content-Type: multipart/alternative; boundary="------------wmd5QdRYmEXkCiBRCIqkLTQW"
Message-ID: <7873a7d0-d0ab-d11d-27e3-488bc5a9157d@free.fr>
Date: Tue, 1 Mar 2022 12:37:15 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-GB
To: draft-ietf-secevent-subject-identifiers.all@ietf.org
References: <ADF91B96-C390-48EF-A5BE-F68D482EF5CE@gmail.com>
From: Denis <denis.ietf@free.fr>
Cc: txauth@ietf.org
In-Reply-To: <ADF91B96-C390-48EF-A5BE-F68D482EF5CE@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/kY9e8J2mg6CzM09H45jf7NQsyQg>
Subject: Re: [GNAP] Subject Identifiers draft - request for volunteers
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 11:37:48 -0000

This is a multi-part message in MIME format.
--------------wmd5QdRYmEXkCiBRCIqkLTQW
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Yaron,

This WG is not really active any more. Apparently there is a lack of 
participation. Adding one or more editors is unlikely to solve the problem.
The key question to be raised is how many people who are registered in 
the WG are still interested.
A key point is to understand in which contexts this specification would 
be used.

I have been one of the very few who has posted a message to this WG: my 
message was posted on 2021-05-27.
It raises important concerns which are related to subject identifiers. 
It proposes solutions to address them.
I would appreciate to have a technical discussion about it, but if no 
one is still interested in this work item, this is unlikely to happen.

Denis

Note: Archive of the mailing list: 
https://mailarchive.ietf.org/arch/browse/id-event/

> Hi,
>
> The GNAP protocol has a dependency on the Subject Identifiers draft [1] from the SecEvent working group. That draft has been around for a long time and in fact has just been updated by the authors (much appreciated!), but we’ve had a hard time moving it across the finish line at the SecEvent group. I am looking for one or more volunteers to join as co-authors, preferably people who are *not* authors on the GNAP protocol.
>
> The Subject ID draft should go into an abbreviated second WG last call, and then assuming everything goes well, into IETF last call and IESG review. The main task of the new author(s) would be to address IESG comments in a timely manner and move the draft to publication.
>
> If you are new to the IETF, this is a great opportunity to familiarize yourself with its publication process.
>
> Please get back to me or Leif for any additional details.
>
> Thanks,
> 	Yaron
>
>
> [1]https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/
>
>

--------------wmd5QdRYmEXkCiBRCIqkLTQW
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Hi Yaron,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">This WG is not really active any more.
      Apparently there is a lack of participation. Adding one or more
      editors is unlikely to solve the problem. <br>
    </div>
    <div class="moz-cite-prefix">The key question to be raised is how
      many people who are registered in the WG are still interested.</div>
    <div class="moz-cite-prefix">A key point is to understand in which
      contexts this specification would be used.<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">I have been one of the very few who has
      posted a message to this WG: my message was posted on 2021-05-27.<br>
      It raises important concerns which are related to subject
      identifiers. It proposes solutions to address them.<br>
      I would appreciate to have a technical discussion about it, but if
      no one is still interested in this work item, this is unlikely to
      happen.<br>
      <br>
    </div>
    <div class="moz-cite-prefix">Denis</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">Note: Archive of the mailing list: <font
        color="#0000ff"><a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/browse/id-event/">https://mailarchive.ietf.org/arch/browse/id-event/</a></font><br>
    </div>
    <br>
    <blockquote type="cite"
      cite="mid:ADF91B96-C390-48EF-A5BE-F68D482EF5CE@gmail.com">
      <pre class="moz-quote-pre" wrap="">Hi,

The GNAP protocol has a dependency on the Subject Identifiers draft [1] from the SecEvent working group. That draft has been around for a long time and in fact has just been updated by the authors (much appreciated!), but we’ve had a hard time moving it across the finish line at the SecEvent group. I am looking for one or more volunteers to join as co-authors, preferably people who are *not* authors on the GNAP protocol.

The Subject ID draft should go into an abbreviated second WG last call, and then assuming everything goes well, into IETF last call and IESG review. The main task of the new author(s) would be to address IESG comments in a timely manner and move the draft to publication.

If you are new to the IETF, this is a great opportunity to familiarize yourself with its publication process.

Please get back to me or Leif for any additional details.

Thanks,
	Yaron


[1] <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/">https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/</a>


</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------wmd5QdRYmEXkCiBRCIqkLTQW--


From nobody Tue Mar  1 03:48:54 2022
Return-Path: <denis.ietf@free.fr>
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 0953A3A07D9 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 03:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.128
X-Spam-Level: 
X-Spam-Status: No, score=-6.128 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 UDk0570TcRPS for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 03:48:48 -0800 (PST)
Received: from smtp.smtpout.orange.fr (smtp06.smtpout.orange.fr [80.12.242.128]) (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 08BA13A03C9 for <txauth@ietf.org>; Tue,  1 Mar 2022 03:48:47 -0800 (PST)
Received: from [192.168.1.11] ([82.121.202.228]) by smtp.orange.fr with ESMTPA id P0zlnUd0luCn2P0zmnOq9k; Tue, 01 Mar 2022 12:48:46 +0100
X-ME-Helo: [192.168.1.11]
X-ME-Auth: OWU3ZmVkYWM0M2UwZWM1YifxM2Q3ZDk1YiUzNWJiZTM2MiliMTI0N2YxZmQ=
X-ME-Date: Tue, 01 Mar 2022 12:48:46 +0100
X-ME-IP: 82.121.202.228
Content-Type: multipart/alternative; boundary="------------YMe9xZdm09rf8txBSDwwXRim"
Message-ID: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr>
Date: Tue, 1 Mar 2022 12:48:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-GB
To: "txauth@ietf.org" <txauth@ietf.org>
From: Denis <denis.ietf@free.fr>
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/eK27HuOgEFjlaI_6inln0-s7l6o>
Subject: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 11:48:53 -0000

This is a multi-part message in MIME format.
--------------YMe9xZdm09rf8txBSDwwXRim
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello everybody,

GNAP has four main components : users, clients, ASs and RSs.

GNAP is supposed to describe a protocol. A protocol is a set of rules 
that control the way data is exchanged between computers.
A reader would expect to find the description of the data sent by a 
client to a RS (which are indeed described in ietf-wg-gnap/core-protocol),
but also find how that data *shall be handled by a RS* which is supposed 
to be described in draft-ietf-gnap-resource-servers. Unfortunately,
this is not the case.

The focus has been placed on the "core" protocol, leaving aside the the RS.

The core document (ietf-wg-gnap/core-protocol) has now got more than 400 
issues !

Besides the editors (and the chair), very few members are active and at 
this time it is unlikely that more members will participate
since *the main driving line for the construction of GNAP has been los**t*.

The recent message called "embedding GNAP" got no reply from the WG, 
except one from a co-editor.
IMO, this demonstrates that *GNAP is still a **moving target* *after 20 
months of work.*

Does this mean that all the WG members agree with the very few emails 
that are exchanged or that the WG members are
no longer really able to participate to the discussion since such 
participation would involve a lot of days to get "up to speed" again ?
I would guess that the right answer is the latter.

The core document has still *no security model *and hence its security 
is more than questionable.

The core document is AS centric and hence *the **privacy concerns of the 
users cannot be addressed*. Is this deliberate ?
When the work started, privacy was supposed to be a major concern to be 
taken into consideration, but in practice, this is not the case.

The core document still does not address the general use case.

There are so many options that *interoperability will not be possible*.

*draft-ietf-gnap-resource-servers-01**expired on 13 January 2022*.  We 
are now close to an IETF meeting and no draft is available.

The milestones are outdated and, anyway, are not observed 
(seehttps://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/)

Milestones:

   Jul 2021 - Core delegation protocol in WGLC

   Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, to WGLC

   Oct 2021 - Key presentation mechanism binding to the core protocol, detached HTTP signatures, to WGLC

   Oct 2021 - Key presentation mechanism binding to the core protocol, embedded HTTP signature, to WGLC

   Dec 2021 - Guidelines for use of protocol extension points to WGLC

   Feb 2022 - Guidelines on migration paths, implementation, and operations to WGLC

At the next IETF meeting, rather than addressing, /as usual,/ the last 
technical issues that no one or very few people will be able to follow 
or understand,
I would suggest that the editors address the following topics: 
*interoperability*, *privacy *and *security *at a level that will allow 
everybody to understand
the real issues behind these three words and by presenting *a balanced 
view*.

Denis

PS: If we were working within ISO, this WG would already have been closed.

--------------YMe9xZdm09rf8txBSDwwXRim
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hello everybody,<br>
      <span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48"></span></span></p>
    <p><span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">GNAP has four main components : users,
          clients, ASs and RSs.</span></span></p>
    <p>GNAP is supposed to describe a protocol. A protocol is <span
        class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">a set of rules that control the way data is
          exchanged between computers.<br>
          A reader would expect to find the description of the data sent
          by a client to a RS (which are indeed described in </span></span><span
        class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48"><span class="sn-gs" id="protocol__14"><span
              class="def" id="protocol__48">ietf-wg-gnap/core-protocol)</span></span>,
          <br>
          but also find how that data <b>shall be handled by a RS</b>
          which is supposed to be described in </span></span><span
        class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">draft-ietf-gnap-resource-servers.
          Unfortunately, <br>
          this is not the case. </span></span></p>
    <p><span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">The focus has been placed on the "core"
          protocol, leaving aside the the RS.<br>
        </span></span><br>
      <span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">The core document
          (ietf-wg-gnap/core-protocol) has now got more than 400 issues
          ! <br>
        </span></span></p>
    <p><span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">Besides the editors (and the chair), very
          few members are active and at this time it is unlikely that
          more members will participate <br>
          since <b>the main driving line for the construction of GNAP
            has been los</b><b>t</b>.<br>
        </span></span></p>
    <p>The recent message called "embedding GNAP" got no reply from the
      WG, except one from a co-editor.<br>
      IMO, this demonstrates that <font color="#0000ff"><b>GNAP is
          still a </b><b>moving target</b> </font><b><font
          color="#0000ff">after 20 months of work</font>.</b><br>
      <br>
      Does this mean that all the WG members agree with the very few
      emails that are exchanged or that the WG members are <br>
      no longer really able to participate to the discussion since such
      participation would involve a lot of days to get "up to speed"
      again ? <br>
      I would guess that the right answer is the latter.</p>
    <p><span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">The core document has still <b>no security
            model </b>and hence its security is more than questionable.<br>
          <br>
          The core document is AS centric and hence <b>the </b><b>privacy
            concerns of the users cannot be addressed</b>. Is this
          deliberate ?<br>
        </span></span><span class="sn-gs" id="protocol__14"><span
          class="def" id="protocol__48">When the work started, privacy
          was supposed to be a major concern to be taken into
          consideration, but in practice, this is not the case.</span></span><br>
      <span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48"><span class="sn-gs" id="protocol__14"><span
              class="def" id="protocol__48"><span class="sn-gs"
                id="protocol__14"><span class="def" id="protocol__48"><br>
                  The core document</span></span> still does not address
              the general use case.</span></span></span></span></p>
    <p><span class="sn-gs" id="protocol__14"><span class="def"
          id="protocol__48">There are so many options that <b>interoperability
            will not be possible</b>. <br>
        </span></span></p>
    <p><b>draft-ietf-gnap-resource-servers-01</b><b> expired on 13
        January 2022</b>.  We are now close to an IETF meeting and no
      draft is available.</p>
    The milestones are outdated and, anyway, are not observed (see<font
      color="#0000ff"> <a class="moz-txt-link-freetext"
        href="https://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/">https://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/</a></font>)<br>
    <pre>Milestones:

  Jul 2021 - Core delegation protocol in WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, detached HTTP signatures, to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, embedded HTTP signature, to WGLC

  Dec 2021 - Guidelines for use of protocol extension points to WGLC

  Feb 2022 - Guidelines on migration paths, implementation, and operations to WGLC

</pre>
    <p>At the next IETF meeting, rather than addressing, <i>as usual,</i>
      the last technical issues that no one or very few people will be
      able to follow or understand, <br>
      I would suggest that the editors address the following topics: <b>interoperability</b>,
      <b>privacy </b>and <b>security </b>at a level that will allow
      everybody to understand <br>
      the real issues behind these three words and by presenting <font
        color="#0000ff"><b>a balanced view</b></font>.<br>
    </p>
    Denis
    <p>PS: If we were working within ISO, this WG would already have
      been closed.<br>
      <br>
    </p>
  </body>
</html>

--------------YMe9xZdm09rf8txBSDwwXRim--


From nobody Tue Mar  1 04:34:31 2022
Return-Path: <prachi.jain1288@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 DF8683A087B; Tue,  1 Mar 2022 04:34:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.856
X-Spam-Level: 
X-Spam-Status: No, score=-1.856 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 WSCF0ZjCmTrW; Tue,  1 Mar 2022 04:34:28 -0800 (PST)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 3E4423A0872; Tue,  1 Mar 2022 04:34:28 -0800 (PST)
Received: by mail-yb1-xb31.google.com with SMTP id j2so26988654ybu.0; Tue, 01 Mar 2022 04:34:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bl7WuftBDC6OLYUf64TB5xNRdqxxvlKQzUss/HxIBHg=; b=XUnwPGX5m6fLde3LAt7V1NWLv+YlXWCnYdwE/iS5V1UZtyTFayduAPHcXJHYuHsJDL znO7GjXubZGUKymyIsc4l57atqfMj591yT1jTOhOIi2EJQGJNJH2Hdj1uEwZlqApMIER jS1CbF+Jk/iui+sEWoMNIVD5nOneptmPHbExhLUTMwV5N92BjMtf02mN6EL7lcGg6cbg UnO6yzqjsFvfpqo3Hr3+xjMyFEvAQEsppW5QFcqRd91h1UFwNsy3gLLXshv0F8MsbPKh 2o1QWdsW3ytEv2Aza2vigsWAn5pVQipG4QS5WYls7ooJn4vUEXFShBXOJnyKUOl2ZF5w PbfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bl7WuftBDC6OLYUf64TB5xNRdqxxvlKQzUss/HxIBHg=; b=UgprregK44PYSc4HGuZIQ0n+KlDVbUx6rAvPa4Baki+Clo7pebxNzj8GhrEiytES5/ 8jZPZG+jfHBNhlb8Y88C8CR7YF2xchzPFuZ9qoWjAhEm78UycgLwBGMPOoaix/+002MZ 7INMr3wz+bFpXsaQRiq/zQkQwkxov5l91JWcrEyWgwgQJkuWYev98pbrk8LWNDcqsgSM bb2DgB/RrTggBQBLpKRn9TxkOUH84DhtmTftZcr0hpBBwyH1UpDI3yJEYXOQWzKkA9fb 6j8pGPiQm3V3KZw1P1kzyJQVPmvGLpi3wx/yhc9itLGli8zkdgWNVt9nVIwI4xN0tqIc 97vg==
X-Gm-Message-State: AOAM533NDQDQKVzvqnVVFRPK24Yj9mcGN6lil3My/iQtFR/cc3OT68Mb AWlm/eKo6ebViC3SxiCqO78MM4fSO9Ol+1Gi3rHoa5G0
X-Google-Smtp-Source: ABdhPJwQ6KZjZoJkUlprRbRrEXsqKTJlOTR+u954w/qHSUAL2T4Mut45Dz25VXujuA0RZaKNzVc+Wl1dn0qGIEZ12dA=
X-Received: by 2002:a25:2482:0:b0:622:72e1:5203 with SMTP id k124-20020a252482000000b0062272e15203mr22888401ybk.350.1646138066794; Tue, 01 Mar 2022 04:34:26 -0800 (PST)
MIME-Version: 1.0
References: <ADF91B96-C390-48EF-A5BE-F68D482EF5CE@gmail.com> <7873a7d0-d0ab-d11d-27e3-488bc5a9157d@free.fr>
In-Reply-To: <7873a7d0-d0ab-d11d-27e3-488bc5a9157d@free.fr>
From: Prachi Jain <prachi.jain1288@gmail.com>
Date: Tue, 1 Mar 2022 06:34:16 -0600
Message-ID: <CAA1-vB3r5cftH7gnspVTCm82w=CgRvz9gUe2eaVUqjEA=HvPiQ@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: draft-ietf-secevent-subject-identifiers.all@ietf.org, txauth@ietf.org
Content-Type: multipart/alternative; boundary="000000000000b8fea605d92762ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/GViITh8Zb_FQiEvV-oJSQHtwWbw>
Subject: Re: [GNAP] Subject Identifiers draft - request for volunteers
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 12:34:30 -0000

--000000000000b8fea605d92762ea
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Denis,

Thank you for your email and raising these concerns.

I volunteered to take up this draft and drive it past the finish line along
with the other authors. I am in mid of identifying all the comments and
concerns that still need to be addressed after draft-09. I will take a look
at your review comments today and get back to you as soon as possible =F0=
=9F=98=8A

Thanks,
Prachi

On Tue, Mar 1, 2022 at 5:38 AM Denis <denis.ietf@free.fr> wrote:

> Hi Yaron,
>
> This WG is not really active any more. Apparently there is a lack of
> participation. Adding one or more editors is unlikely to solve the proble=
m.
> The key question to be raised is how many people who are registered in th=
e
> WG are still interested.
> A key point is to understand in which contexts this specification would b=
e
> used.
>
> I have been one of the very few who has posted a message to this WG: my
> message was posted on 2021-05-27.
> It raises important concerns which are related to subject identifiers. It
> proposes solutions to address them.
> I would appreciate to have a technical discussion about it, but if no one
> is still interested in this work item, this is unlikely to happen.
>
> Denis
>
> Note: Archive of the mailing list:
> https://mailarchive.ietf.org/arch/browse/id-event/
>
> Hi,
>
> The GNAP protocol has a dependency on the Subject Identifiers draft [1] f=
rom the SecEvent working group. That draft has been around for a long time =
and in fact has just been updated by the authors (much appreciated!), but w=
e=E2=80=99ve had a hard time moving it across the finish line at the SecEve=
nt group. I am looking for one or more volunteers to join as co-authors, pr=
eferably people who are *not* authors on the GNAP protocol.
>
> The Subject ID draft should go into an abbreviated second WG last call, a=
nd then assuming everything goes well, into IETF last call and IESG review.=
 The main task of the new author(s) would be to address IESG comments in a =
timely manner and move the draft to publication.
>
> If you are new to the IETF, this is a great opportunity to familiarize yo=
urself with its publication process.
>
> Please get back to me or Leif for any additional details.
>
> Thanks,
> 	Yaron
>
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-identifi=
ers/
>
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>

--000000000000b8fea605d92762ea
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Hi Denis,</div><div dir=3D"auto"><br></div><div dir=3D"au=
to">Thank you for=C2=A0your email and raising these concerns.=C2=A0</div><d=
iv dir=3D"auto"><br></div><div dir=3D"auto">I volunteered to take up this d=
raft and drive it past the finish line along with the other authors. I am i=
n mid of identifying all the comments and concerns that still=C2=A0need to =
be addressed after draft-09. I will take a look at your review comments tod=
ay and get back to you as=C2=A0soon as possible =F0=9F=98=8A</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Thanks,</div><div dir=3D"auto">Prachi=
</div><div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_a=
ttr">On Tue, Mar 1, 2022 at 5:38 AM Denis &lt;<a href=3D"mailto:denis.ietf@=
free.fr">denis.ietf@free.fr</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-l=
eft-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">
 =20
   =20
 =20
  <div>
    <div>Hi Yaron,</div>
    <div><br>
    </div>
    <div>This WG is not really active any more.
      Apparently there is a lack of participation. Adding one or more
      editors is unlikely to solve the problem. <br>
    </div>
    <div>The key question to be raised is how
      many people who are registered in the WG are still interested.</div>
    <div>A key point is to understand in which
      contexts this specification would be used.<br>
    </div>
    <div><br>
    </div>
    <div>I have been one of the very few who has
      posted a message to this WG: my message was posted on 2021-05-27.<br>
      It raises important concerns which are related to subject
      identifiers. It proposes solutions to address them.<br>
      I would appreciate to have a technical discussion about it, but if
      no one is still interested in this work item, this is unlikely to
      happen.<br>
      <br>
    </div>
    <div>Denis</div>
    <div><br>
    </div>
    <div>Note: Archive of the mailing list: <font style=3D"color:rgb(0,0,25=
5)"><a href=3D"https://mailarchive.ietf.org/arch/browse/id-event/" target=
=3D"_blank">https://mailarchive.ietf.org/arch/browse/id-event/</a></font><b=
r>
    </div></div><div>
    <br>
    <blockquote type=3D"cite">
      <pre style=3D"font-family:monospace">Hi,

The GNAP protocol has a dependency on the Subject Identifiers draft [1] fro=
m the SecEvent working group. That draft has been around for a long time an=
d in fact has just been updated by the authors (much appreciated!), but we=
=E2=80=99ve had a hard time moving it across the finish line at the SecEven=
t group. I am looking for one or more volunteers to join as co-authors, pre=
ferably people who are *not* authors on the GNAP protocol.

The Subject ID draft should go into an abbreviated second WG last call, and=
 then assuming everything goes well, into IETF last call and IESG review. T=
he main task of the new author(s) would be to address IESG comments in a ti=
mely manner and move the draft to publication.

If you are new to the IETF, this is a great opportunity to familiarize your=
self with its publication process.

Please get back to me or Leif for any additional details.

Thanks,
	Yaron


[1] <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-secevent-subject=
-identifiers/" target=3D"_blank" style=3D"font-family:monospace">https://da=
tatracker.ietf.org/doc/draft-ietf-secevent-subject-identifiers/</a>


</pre>
    </blockquote>
    <p><br>
    </p>
  </div>

-- <br>
TXAuth mailing list<br>
<a href=3D"mailto:TXAuth@ietf.org" target=3D"_blank">TXAuth@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/txauth" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/txauth</a><br>
</blockquote></div></div>

--000000000000b8fea605d92762ea--


From nobody Tue Mar  1 04:48:59 2022
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 6A93D3A0897 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 04:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.107
X-Spam-Level: 
X-Spam-Status: No, score=-7.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 5kkHO8FlcWSl for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 04:48:55 -0800 (PST)
Received: from mail-il1-x134.google.com (mail-il1-x134.google.com [IPv6:2607:f8b0:4864:20::134]) (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 F0CC43A0881 for <txauth@ietf.org>; Tue,  1 Mar 2022 04:48:54 -0800 (PST)
Received: by mail-il1-x134.google.com with SMTP id f2so12454364ilq.1 for <txauth@ietf.org>; Tue, 01 Mar 2022 04:48:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JklxEtzj4pkpHBfVv/ZoVfb3bSW9qbFe7M9Mc3SF4hE=; b=bxbLflPtMJt9TB4FJocrUpZDXNgk/cdtQaO12Gf5gg8yIryctvPIgOI3bCgGqv/uD2 JT2h3EzkUQJVy2+KzuFewwbPQk8HKMrsmjYSyfKZlyM3onyEqY3gYJFel+XuDXt7X/Lq BiR/PbeI32xmb2KIaLQ3larmzfNbsjSZxt2pIZNtGX5lvRic7hCg+1DzAcqY+qqEWRKd ZSe8CvkJYi14ATzIOSQsMBBm+l6QZnquaXt5gWLX/4UB9CBC4xOPHc0LVOCYPjhRmiAL Oxgcn68dBZD8KyaYwQ72LloH9Tf9uPAUS3rbhC1sGk8NN70PIZxsi3FRCl2U35MUa4Ra mRxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JklxEtzj4pkpHBfVv/ZoVfb3bSW9qbFe7M9Mc3SF4hE=; b=7IiU1vNeh8ihzJEKntpqBOAiuONN/EYu+oEUhuhNBVHG93hp4Fqsag3XcK6U9tkfs+ DmRdks/PdujzEpjpDrxcty2og+Av66XsjVxlc5p08Jlg+YBnkcrST/OzGgqIC/yqM/U3 rgPA1hO8XcBR5qcZkdLiiYjPmF5Q4MeFfPXt2XD5Rjga5Rnz9kPlBS8n02ucAv+tVxaa rzLpbygxG1f8rx575RaMhOirUXlD9VP4XbPcVvNRqAPTaKLm0gkN8NP0a/Fpke1B8wBe 782GJL3sRHfFj7CKuRFmrkGnciq1tXwW2BUf/bdgg3rFHfBUiCivJgWiIue/ICTRaMcE Owfg==
X-Gm-Message-State: AOAM533d590eP6LQPJ5Nn0beDi++YvUU+2PbAmBRpVbgRgvMys7A47Pm yRJziA3i64Gn7ZhS6zMLYrc4OIw2yPkYvJcEVuk=
X-Google-Smtp-Source: ABdhPJw0ctQuAk6e26/BgPSyjCgnNYE2GVthalJA/WOfc5tSm1hZq12kVLclqjhsE18XroVIdGoeO86LBHU/cNTJcTo=
X-Received: by 2002:a05:6e02:1585:b0:2c2:5b2c:e3e5 with SMTP id m5-20020a056e02158500b002c25b2ce3e5mr24731475ilu.76.1646138934007; Tue, 01 Mar 2022 04:48:54 -0800 (PST)
MIME-Version: 1.0
References: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr>
In-Reply-To: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr>
From: Fabien Imbault <fabien.imbault@gmail.com>
Date: Tue, 1 Mar 2022 13:48:42 +0100
Message-ID: <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: GNAP Mailing List <txauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000699c6005d9279668"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/y7GDcLJz3EpinoZuWxs7DYt4tfA>
Subject: Re: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 12:48:58 -0000

--000000000000699c6005d9279668
Content-Type: text/plain; charset="UTF-8"

Dear Denis,

Sorry I have to say this, but repeating your misconceptions don't make them
true. That's currently not helping anyone going forward.

The editors and chairs welcome anyone with helpful contribution.
Already the spec had many great improvements, from many outstanding
individuals cited in the text. Including on security and privacy.

We are now stabilizing the core draft and focusing on real world
implementations to demonstrate the value and interoperability.

Best regards,
Fabien (speaking only in my own name)




On Tue, 1 Mar 2022, 12:49 Denis, <denis.ietf@free.fr> wrote:

> Hello everybody,
>
> GNAP has four main components : users, clients, ASs and RSs.
>
> GNAP is supposed to describe a protocol. A protocol is a set of rules
> that control the way data is exchanged between computers.
> A reader would expect to find the description of the data sent by a client
> to a RS (which are indeed described in ietf-wg-gnap/core-protocol),
> but also find how that data *shall be handled by a RS* which is supposed
> to be described in draft-ietf-gnap-resource-servers. Unfortunately,
> this is not the case.
>
> The focus has been placed on the "core" protocol, leaving aside the the RS.
>
> The core document (ietf-wg-gnap/core-protocol) has now got more than 400
> issues !
>
> Besides the editors (and the chair), very few members are active and at
> this time it is unlikely that more members will participate
> since *the main driving line for the construction of GNAP has been los**t*
> .
>
> The recent message called "embedding GNAP" got no reply from the WG,
> except one from a co-editor.
> IMO, this demonstrates that *GNAP is still a **moving target* *after 20
> months of work.*
>
> Does this mean that all the WG members agree with the very few emails that
> are exchanged or that the WG members are
> no longer really able to participate to the discussion since such
> participation would involve a lot of days to get "up to speed" again ?
> I would guess that the right answer is the latter.
>
> The core document has still *no security model *and hence its security is
> more than questionable.
>
> The core document is AS centric and hence *the **privacy concerns of the
> users cannot be addressed*. Is this deliberate ?
> When the work started, privacy was supposed to be a major concern to be
> taken into consideration, but in practice, this is not the case.
>
> The core document still does not address the general use case.
>
> There are so many options that *interoperability will not be possible*.
>
> *draft-ietf-gnap-resource-servers-01** expired on 13 January 2022*.  We
> are now close to an IETF meeting and no draft is available.
> The milestones are outdated and, anyway, are not observed (see
> https://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/)
>
> Milestones:
>
>   Jul 2021 - Core delegation protocol in WGLC
>
>   Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, to WGLC
>
>   Oct 2021 - Key presentation mechanism binding to the core protocol, detached HTTP signatures, to WGLC
>
>   Oct 2021 - Key presentation mechanism binding to the core protocol, embedded HTTP signature, to WGLC
>
>   Dec 2021 - Guidelines for use of protocol extension points to WGLC
>
>   Feb 2022 - Guidelines on migration paths, implementation, and operations to WGLC
>
>
> At the next IETF meeting, rather than addressing, *as usual,* the last
> technical issues that no one or very few people will be able to follow or
> understand,
> I would suggest that the editors address the following topics:
> *interoperability*, *privacy *and *security *at a level that will allow
> everybody to understand
> the real issues behind these three words and by presenting *a balanced
> view*.
> Denis
>
> PS: If we were working within ISO, this WG would already have been closed.
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>

--000000000000699c6005d9279668
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>Dear Denis,<div dir=3D"auto"><br></div><div dir=3D"a=
uto">Sorry I have to say this, but repeating your misconceptions don&#39;t =
make them true. That&#39;s currently not helping anyone going forward.</div=
><div dir=3D"auto"><br></div><div dir=3D"auto">The editors and chairs welco=
me anyone with helpful contribution.=C2=A0</div><div dir=3D"auto">Already t=
he spec had many great improvements, from many outstanding individuals cite=
d in the text. Including on security and privacy.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">We are now stabilizing the core draft and focusin=
g on real world implementations to demonstrate the value and interoperabili=
ty.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Best regards,<=
/div><div dir=3D"auto">Fabien (speaking only in my own name)</div><div dir=
=3D"auto"><br></div><div dir=3D"auto"><br></div><br><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, 1 Mar 2022, 12:49 Den=
is, &lt;<a href=3D"mailto:denis.ietf@free.fr" rel=3D"noreferrer noreferrer"=
 target=3D"_blank">denis.ietf@free.fr</a>&gt; wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
 =20

   =20
 =20
  <div>
    <p>Hello everybody,<br>
      <span id=3D"m_7161345808286313555m_6066375261535833907m_6506138452035=
884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907m=
_6506138452035884450protocol__48"></span></span></p>
    <p><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203=
5884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907=
m_6506138452035884450protocol__48">GNAP has four main components : users,
          clients, ASs and RSs.</span></span></p>
    <p>GNAP is supposed to describe a protocol. A protocol is <span id=3D"m=
_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"=
><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203588445=
0protocol__48">a set of rules that control the way data is
          exchanged between computers.<br>
          A reader would expect to find the description of the data sent
          by a client to a RS (which are indeed described in </span></span>=
<span id=3D"m_7161345808286313555m_6066375261535833907m_6506138452035884450=
protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907m_65061=
38452035884450protocol__48"><span id=3D"m_7161345808286313555m_606637526153=
5833907m_6506138452035884450protocol__14"><span id=3D"m_7161345808286313555=
m_6066375261535833907m_6506138452035884450protocol__48">ietf-wg-gnap/core-p=
rotocol)</span></span>,
          <br>
          but also find how that data <b>shall be handled by a RS</b>
          which is supposed to be described in </span></span><span id=3D"m_=
7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14">=
<span id=3D"m_7161345808286313555m_6066375261535833907m_6506138452035884450=
protocol__48">draft-ietf-gnap-resource-servers.
          Unfortunately, <br>
          this is not the case. </span></span></p>
    <p><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203=
5884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907=
m_6506138452035884450protocol__48">The focus has been placed on the &quot;c=
ore&quot;
          protocol, leaving aside the the RS.<br>
        </span></span><br>
      <span id=3D"m_7161345808286313555m_6066375261535833907m_6506138452035=
884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907m=
_6506138452035884450protocol__48">The core document
          (ietf-wg-gnap/core-protocol) has now got more than 400 issues
          ! <br>
        </span></span></p>
    <p><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203=
5884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907=
m_6506138452035884450protocol__48">Besides the editors (and the chair), ver=
y
          few members are active and at this time it is unlikely that
          more members will participate <br>
          since <b>the main driving line for the construction of GNAP
            has been los</b><b>t</b>.<br>
        </span></span></p>
    <p>The recent message called &quot;embedding GNAP&quot; got no reply fr=
om the
      WG, except one from a co-editor.<br>
      IMO, this demonstrates that <font color=3D"#0000ff"><b>GNAP is
          still a </b><b>moving target</b> </font><b><font color=3D"#0000ff=
">after 20 months of work</font>.</b><br>
      <br>
      Does this mean that all the WG members agree with the very few
      emails that are exchanged or that the WG members are <br>
      no longer really able to participate to the discussion since such
      participation would involve a lot of days to get &quot;up to speed&qu=
ot;
      again ? <br>
      I would guess that the right answer is the latter.</p>
    <p><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203=
5884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907=
m_6506138452035884450protocol__48">The core document has still <b>no securi=
ty
            model </b>and hence its security is more than questionable.<br>
          <br>
          The core document is AS centric and hence <b>the </b><b>privacy
            concerns of the users cannot be addressed</b>. Is this
          deliberate ?<br>
        </span></span><span id=3D"m_7161345808286313555m_606637526153583390=
7m_6506138452035884450protocol__14"><span id=3D"m_7161345808286313555m_6066=
375261535833907m_6506138452035884450protocol__48">When the work started, pr=
ivacy
          was supposed to be a major concern to be taken into
          consideration, but in practice, this is not the case.</span></spa=
n><br>
      <span id=3D"m_7161345808286313555m_6066375261535833907m_6506138452035=
884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907m=
_6506138452035884450protocol__48"><span id=3D"m_7161345808286313555m_606637=
5261535833907m_6506138452035884450protocol__14"><span id=3D"m_7161345808286=
313555m_6066375261535833907m_6506138452035884450protocol__48"><span id=3D"m=
_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"=
><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203588445=
0protocol__48"><br>
                  The core document</span></span> still does not address
              the general use case.</span></span></span></span></p>
    <p><span id=3D"m_7161345808286313555m_6066375261535833907m_650613845203=
5884450protocol__14"><span id=3D"m_7161345808286313555m_6066375261535833907=
m_6506138452035884450protocol__48">There are so many options that <b>intero=
perability
            will not be possible</b>. <br>
        </span></span></p>
    <p><b>draft-ietf-gnap-resource-servers-01</b><b> expired on 13
        January 2022</b>.=C2=A0 We are now close to an IETF meeting and no
      draft is available.</p>
    The milestones are outdated and, anyway, are not observed (see<font col=
or=3D"#0000ff"> <a href=3D"https://datatracker.ietf.org/doc/charter-ietf-gn=
ap/writeup/" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">htt=
ps://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/</a></font>)<br>
    <pre>Milestones:

  Jul 2021 - Core delegation protocol in WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, =
to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, detac=
hed HTTP signatures, to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, embed=
ded HTTP signature, to WGLC

  Dec 2021 - Guidelines for use of protocol extension points to WGLC

  Feb 2022 - Guidelines on migration paths, implementation, and operations =
to WGLC

</pre>
    <p>At the next IETF meeting, rather than addressing, <i>as usual,</i>
      the last technical issues that no one or very few people will be
      able to follow or understand, <br>
      I would suggest that the editors address the following topics: <b>int=
eroperability</b>,
      <b>privacy </b>and <b>security </b>at a level that will allow
      everybody to understand <br>
      the real issues behind these three words and by presenting <font colo=
r=3D"#0000ff"><b>a balanced view</b></font>.<br>
    </p>
    Denis
    <p>PS: If we were working within ISO, this WG would already have
      been closed.<br>
      <br>
    </p>
  </div>

-- <br>
TXAuth mailing list<br>
<a href=3D"mailto:TXAuth@ietf.org" rel=3D"noreferrer noreferrer noreferrer"=
 target=3D"_blank">TXAuth@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/txauth" rel=3D"noreferrer =
noreferrer noreferrer noreferrer" target=3D"_blank">https://www.ietf.org/ma=
ilman/listinfo/txauth</a><br>
</blockquote></div>
</div></div>

--000000000000699c6005d9279668--


From nobody Tue Mar  1 05:30:33 2022
Return-Path: <denis.ietf@free.fr>
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 217333A092B for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 05:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.128
X-Spam-Level: 
X-Spam-Status: No, score=-1.128 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Tyk9UZjuY0-J for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 05:30:30 -0800 (PST)
Received: from smtp.smtpout.orange.fr (smtp04.smtpout.orange.fr [80.12.242.126]) (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 AE3FB3A0925 for <txauth@ietf.org>; Tue,  1 Mar 2022 05:30:29 -0800 (PST)
Received: from [192.168.1.11] ([82.121.202.228]) by smtp.orange.fr with ESMTPA id P2aAnnD2GVKleP2aAnJar5; Tue, 01 Mar 2022 14:30:27 +0100
X-ME-Helo: [192.168.1.11]
X-ME-Auth: OWU3ZmVkYWM0M2UwZWM1YifxM2Q3ZDk1YiUzNWJiZTM2MiliMTI0N2YxZmQ=
X-ME-Date: Tue, 01 Mar 2022 14:30:27 +0100
X-ME-IP: 82.121.202.228
Content-Type: multipart/alternative; boundary="------------Igdbm0000VR6wE8cEh0De008"
Message-ID: <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr>
Date: Tue, 1 Mar 2022 14:30:27 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-GB
To: Fabien Imbault <fabien.imbault@gmail.com>
Cc: GNAP Mailing List <txauth@ietf.org>
References: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr> <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com>
From: Denis <denis.ietf@free.fr>
In-Reply-To: <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/Q7dZrOffyJoi_wfelVCd2BS2kXM>
Subject: Re: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 13:30:32 -0000

This is a multi-part message in MIME format.
--------------Igdbm0000VR6wE8cEh0De008
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Fabien,

It is not useful to send flames.

It would be much better that you spend time to respond to the issues 
raised on draft-ietf-gnap-resource-servers-01
and publish a new draft that addresses these issues and in the mean time 
provide a summary of the way these issues have
been addressed (including the issues you don't agree with).

"Stabilizing the core draft" and "focusing on real world 
implementations" without progressing the resource-servers draft
looks like a headlong rush.

Denis


> Dear Denis,
>
> Sorry I have to say this, but repeating your misconceptions don't make 
> them true. That's currently not helping anyone going forward.
>
> The editors and chairs welcome anyone with helpful contribution.
> Already the spec had many great improvements, from many outstanding 
> individuals cited in the text. Including on security and privacy.
>
> We are now stabilizing the core draft and focusing on real world 
> implementations to demonstrate the value and interoperability.
>
> Best regards,
> Fabien (speaking only in my own name)
>
>
>
>
> On Tue, 1 Mar 2022, 12:49 Denis, <denis.ietf@free.fr> wrote:
>
>     Hello everybody,
>
>     GNAP has four main components : users, clients, ASs and RSs.
>
>     GNAP is supposed to describe a protocol. A protocol is a set of
>     rules that control the way data is exchanged between computers.
>     A reader would expect to find the description of the data sent by
>     a client to a RS (which are indeed described in
>     ietf-wg-gnap/core-protocol),
>     but also find how that data *shall be handled by a RS* which is
>     supposed to be described in draft-ietf-gnap-resource-servers.
>     Unfortunately,
>     this is not the case.
>
>     The focus has been placed on the "core" protocol, leaving aside
>     the the RS.
>
>     The core document (ietf-wg-gnap/core-protocol) has now got more
>     than 400 issues !
>
>     Besides the editors (and the chair), very few members are active
>     and at this time it is unlikely that more members will participate
>     since *the main driving line for the construction of GNAP has been
>     los**t*.
>
>     The recent message called "embedding GNAP" got no reply from the
>     WG, except one from a co-editor.
>     IMO, this demonstrates that *GNAP is still a **moving target*
>     *after 20 months of work.*
>
>     Does this mean that all the WG members agree with the very few
>     emails that are exchanged or that the WG members are
>     no longer really able to participate to the discussion since such
>     participation would involve a lot of days to get "up to speed"
>     again ?
>     I would guess that the right answer is the latter.
>
>     The core document has still *no security model *and hence its
>     security is more than questionable.
>
>     The core document is AS centric and hence *the **privacy concerns
>     of the users cannot be addressed*. Is this deliberate ?
>     When the work started, privacy was supposed to be a major concern
>     to be taken into consideration, but in practice, this is not the case.
>
>     The core document still does not address the general use case.
>
>     There are so many options that *interoperability will not be
>     possible*.
>
>     *draft-ietf-gnap-resource-servers-01**expired on 13 January
>     2022*.  We are now close to an IETF meeting and no draft is available.
>
>     The milestones are outdated and, anyway, are not observed
>     (seehttps://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/)
>
>     Milestones:
>
>        Jul 2021 - Core delegation protocol in WGLC
>
>        Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, to WGLC
>
>        Oct 2021 - Key presentation mechanism binding to the core protocol, detached HTTP signatures, to WGLC
>
>        Oct 2021 - Key presentation mechanism binding to the core protocol, embedded HTTP signature, to WGLC
>
>        Dec 2021 - Guidelines for use of protocol extension points to WGLC
>
>        Feb 2022 - Guidelines on migration paths, implementation, and operations to WGLC
>
>     At the next IETF meeting, rather than addressing, /as usual,/ the
>     last technical issues that no one or very few people will be able
>     to follow or understand,
>     I would suggest that the editors address the following topics:
>     *interoperability*, *privacy *and *security *at a level that will
>     allow everybody to understand
>     the real issues behind these three words and by presenting *a
>     balanced view*.
>
>     Denis
>
>     PS: If we were working within ISO, this WG would already have been
>     closed.
>
>     -- 
>     TXAuth mailing list
>     TXAuth@ietf.org
>     https://www.ietf.org/mailman/listinfo/txauth
>

--------------Igdbm0000VR6wE8cEh0De008
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Fabien,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">It is not useful to send flames.</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">It would be much better that you spend
      time to respond to the issues raised on
      draft-ietf-gnap-resource-servers-01 <br>
      and publish a new draft that addresses these issues and in the
      mean time provide a summary of the way these issues have <br>
      been addressed (including the issues you don't agree with).</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">"Stabilizing the core draft" and
      "focusing on real world implementations" without progressing the
      resource-servers draft <br>
      looks like a headlong rush.<br>
      <br>
      Denis<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix"> <br>
    </div>
    <blockquote type="cite"
cite="mid:CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div>Dear Denis,
          <div dir="auto"><br>
          </div>
          <div dir="auto">Sorry I have to say this, but repeating your
            misconceptions don't make them true. That's currently not
            helping anyone going forward.</div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">The editors and chairs welcome anyone with
            helpful contribution. </div>
          <div dir="auto">Already the spec had many great improvements,
            from many outstanding individuals cited in the text.
            Including on security and privacy.</div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">We are now stabilizing the core draft and
            focusing on real world implementations to demonstrate the
            value and interoperability. </div>
          <div dir="auto"><br>
          </div>
          <div dir="auto">Best regards,</div>
          <div dir="auto">Fabien (speaking only in my own name)</div>
          <div dir="auto"><br>
          </div>
          <div dir="auto"><br>
          </div>
          <br>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Tue, 1 Mar 2022, 12:49
              Denis, &lt;<a href="mailto:denis.ietf@free.fr"
                rel="noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">denis.ietf@free.fr</a>&gt;
              wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div>
                <p>Hello everybody,<br>
                  <span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48"></span></span></p>
                <p><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">GNAP
                      has four main components : users, clients, ASs and
                      RSs.</span></span></p>
                <p>GNAP is supposed to describe a protocol. A protocol
                  is <span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">a
                      set of rules that control the way data is
                      exchanged between computers.<br>
                      A reader would expect to find the description of
                      the data sent by a client to a RS (which are
                      indeed described in </span></span><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">ietf-wg-gnap/core-protocol)</span></span>,
                      <br>
                      but also find how that data <b>shall be handled
                        by a RS</b> which is supposed to be described in
                    </span></span><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">draft-ietf-gnap-resource-servers.
                      Unfortunately, <br>
                      this is not the case. </span></span></p>
                <p><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">The
                      focus has been placed on the "core" protocol,
                      leaving aside the the RS.<br>
                    </span></span><br>
                  <span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">The
                      core document (ietf-wg-gnap/core-protocol) has now
                      got more than 400 issues ! <br>
                    </span></span></p>
                <p><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">Besides
                      the editors (and the chair), very few members are
                      active and at this time it is unlikely that more
                      members will participate <br>
                      since <b>the main driving line for the
                        construction of GNAP has been los</b><b>t</b>.<br>
                    </span></span></p>
                <p>The recent message called "embedding GNAP" got no
                  reply from the WG, except one from a co-editor.<br>
                  IMO, this demonstrates that <font color="#0000ff"><b>GNAP
                      is still a </b><b>moving target</b> </font><b><font
                      color="#0000ff">after 20 months of work</font>.</b><br>
                  <br>
                  Does this mean that all the WG members agree with the
                  very few emails that are exchanged or that the WG
                  members are <br>
                  no longer really able to participate to the discussion
                  since such participation would involve a lot of days
                  to get "up to speed" again ? <br>
                  I would guess that the right answer is the latter.</p>
                <p><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">The
                      core document has still <b>no security model </b>and
                      hence its security is more than questionable.<br>
                      <br>
                      The core document is AS centric and hence <b>the
                      </b><b>privacy concerns of the users cannot be
                        addressed</b>. Is this deliberate ?<br>
                    </span></span><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">When
                      the work started, privacy was supposed to be a
                      major concern to be taken into consideration, but
                      in practice, this is not the case.</span></span><br>
                  <span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48"><br>
                              The core document</span></span> still does
                          not address the general use case.</span></span></span></span></p>
                <p><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><span
id="m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__48">There
                      are so many options that <b>interoperability will
                        not be possible</b>. <br>
                    </span></span></p>
                <p><b>draft-ietf-gnap-resource-servers-01</b><b> expired
                    on 13 January 2022</b>.  We are now close to an IETF
                  meeting and no draft is available.</p>
                The milestones are outdated and, anyway, are not
                observed (see<font color="#0000ff"> <a
                    href="https://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/"
                    rel="noreferrer noreferrer noreferrer"
                    target="_blank" moz-do-not-send="true"
                    class="moz-txt-link-freetext">https://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/</a></font>)<br>
                <pre>Milestones:

  Jul 2021 - Core delegation protocol in WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, detached HTTP signatures, to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, embedded HTTP signature, to WGLC

  Dec 2021 - Guidelines for use of protocol extension points to WGLC

  Feb 2022 - Guidelines on migration paths, implementation, and operations to WGLC

</pre>
                <p>At the next IETF meeting, rather than addressing, <i>as
                    usual,</i> the last technical issues that no one or
                  very few people will be able to follow or understand,
                  <br>
                  I would suggest that the editors address the following
                  topics: <b>interoperability</b>, <b>privacy </b>and
                  <b>security </b>at a level that will allow everybody
                  to understand <br>
                  the real issues behind these three words and by
                  presenting <font color="#0000ff"><b>a balanced view</b></font>.<br>
                </p>
                Denis
                <p>PS: If we were working within ISO, this WG would
                  already have been closed.<br>
                  <br>
                </p>
              </div>
              -- <br>
              TXAuth mailing list<br>
              <a href="mailto:TXAuth@ietf.org" rel="noreferrer
                noreferrer noreferrer" target="_blank"
                moz-do-not-send="true" class="moz-txt-link-freetext">TXAuth@ietf.org</a><br>
              <a href="https://www.ietf.org/mailman/listinfo/txauth"
                rel="noreferrer noreferrer noreferrer noreferrer"
                target="_blank" moz-do-not-send="true"
                class="moz-txt-link-freetext">https://www.ietf.org/mailman/listinfo/txauth</a><br>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------Igdbm0000VR6wE8cEh0De008--


From nobody Tue Mar  1 05:40:06 2022
Return-Path: <yaronf.ietf@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 7259A3A0938 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 05:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level: 
X-Spam-Status: No, score=-2.106 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 fZA7jbQeHIoI for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 05:40:02 -0800 (PST)
Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 B3AEA3A0933 for <txauth@ietf.org>; Tue,  1 Mar 2022 05:40:02 -0800 (PST)
Received: by mail-il1-x131.google.com with SMTP id x14so7422018ill.12 for <txauth@ietf.org>; Tue, 01 Mar 2022 05:40:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version:content-transfer-encoding; bh=H/exNrPCe5JpD9M5X4q0qw3sscMWdXrv5doU93XNU9g=; b=QlHBeuHFsZ5NfAff9M32M7sN7WgVe6COLFy5yqbmzyfV7TMxcXap0yRq6k2/Nll/zd MNIx72IbnCgzJjEPwc9U0jgjQTJNiSokmg7E3Dca1idjGCviTwDDK+i+DbkoG0+A3hV0 8K5iBlPIbUTZQqOqXeVmFkn+Cg/wzbCAj3K5k2l/RvvR/4/N17scpnUzP8plmtV6MGvj rf01osQPEV8/IVQ5z9Da1En61wVStVy/BZMUMmJ8NImdrrKED8qhS8NZpdlh+oljq/+h CcvHV0NXPxpWR9Fh7Fo0fbYuQr/+0hgkxCIw2gbfyDQuoCxTgoW+w8QzeTyFzC1yw7U1 GKWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=H/exNrPCe5JpD9M5X4q0qw3sscMWdXrv5doU93XNU9g=; b=VAPXtmrtj+ZuwJZjVNLZkE3WjqaFeLQ1DViqnq9E8hG9ocLtAUm0h19y7IhMsiO2zh 3ooPiM4jbMVMUWzbBzZAz3xEMrxcaZpl3ycWCcZb6p/ewpm49M/sxQbjg180aeOu7Qdm SITze4hQ4w/Vny6iI8fgGs6ucQ5+ZmAx3G0Gfrt2QXHKaiLTAISalmgdkAZ1jMiLWp07 B7C0a5sm2AuZj467QYxjuBWKH1+/r3P+6JrccG/qpSpifGQcfGYeSIL9a5xoDdTjamLb xyHlAxAvg9I0/2oPO1erZI20ae+h9bCTKZX1R+T7UY60s+dF8XD2dXkfFfgYvr9M0EzR +geg==
X-Gm-Message-State: AOAM5331Fn5jy5Qh6rWpnvhjBjb8T++vbwSO5J19Rln5ydpNDNP1bX3G ruO7sHlD/QsPHfV5XvSSOF7x7iX5yTU=
X-Google-Smtp-Source: ABdhPJwiiPiSUZooFj0NUJ4q/i0yEHtdKrTCQ2sRcAmEK2xWRo/Soy40gFoo2tHC8YEMR3ydEp7Y4Q==
X-Received: by 2002:a92:b0b:0:b0:2c2:74db:9630 with SMTP id b11-20020a920b0b000000b002c274db9630mr22904675ilf.170.1646142001228;  Tue, 01 Mar 2022 05:40:01 -0800 (PST)
Received: from [192.168.68.108] (IGLD-84-229-146-220.inter.net.il. [84.229.146.220]) by smtp.gmail.com with ESMTPSA id e17-20020a5d8ad1000000b00644d51bbffcsm3868710iot.36.2022.03.01.05.39.59 for <txauth@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Mar 2022 05:40:00 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.58.22021501
Date: Tue, 01 Mar 2022 15:39:57 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: GNAP Mailing List <txauth@ietf.org>
Message-ID: <E6947722-1B97-405D-84ED-2FC35A247CF9@gmail.com>
Thread-Topic: [GNAP] Subject Identifiers draft - request for volunteers
References: <ADF91B96-C390-48EF-A5BE-F68D482EF5CE@gmail.com> <CALkShcs5c3XsW2W=1z1E0LWJt-qjwdDVchAFQQ8VtL-hf89kvQ@mail.gmail.com>
In-Reply-To: <CALkShcs5c3XsW2W=1z1E0LWJt-qjwdDVchAFQQ8VtL-hf89kvQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/QCTVS2DnnwYZ1toCTpKlVe0p-DU>
Subject: Re: [GNAP] Subject Identifiers draft - request for volunteers
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 13:40:06 -0000

Thank you to all who volunteered to help, this is very much appreciated.

Prachi will be joining the author team for this draft and I hope we can con=
clude and publish it soon.

Best,

	Yaron

    On Sun, Feb 27, 2022 at 8:34 AM Yaron Sheffer <yaronf.ietf@gmail.com> w=
rote:
    >
    > Hi,
    >
    > The GNAP protocol has a dependency on the Subject Identifiers draft [=
1] from the SecEvent working group. That draft has been around for a long ti=
me and in fact has just been updated by the authors (much appreciated!), but=
 we=E2=80=99ve had a hard time moving it across the finish line at the SecEvent gr=
oup. I am looking for one or more volunteers to join as co-authors, preferab=
ly people who are *not* authors on the GNAP protocol.
    >
    > The Subject ID draft should go into an abbreviated second WG last cal=
l, and then assuming everything goes well, into IETF last call and IESG revi=
ew. The main task of the new author(s) would be to address IESG comments in =
a timely manner and move the draft to publication.
    >
    > If you are new to the IETF, this is a great opportunity to familiariz=
e yourself with its publication process.
    >
    > Please get back to me or Leif for any additional details.
    >
    > Thanks,
    >         Yaron
    >
    >
    > [1] https://datatracker.ietf.org/doc/draft-ietf-secevent-subject-iden=
tifiers/
    >
   =20




From nobody Tue Mar  1 05:46:39 2022
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 CC1153A0942 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 05:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 ZlSB5hP2PXIf for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 05:46:33 -0800 (PST)
Received: from mail-il1-x136.google.com (mail-il1-x136.google.com [IPv6:2607:f8b0:4864:20::136]) (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 764883A094B for <txauth@ietf.org>; Tue,  1 Mar 2022 05:46:33 -0800 (PST)
Received: by mail-il1-x136.google.com with SMTP id k7so5567969ilo.8 for <txauth@ietf.org>; Tue, 01 Mar 2022 05:46:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BNunR/QlIojszKaQCmPReSbnVJ+yJh/8Aa/0xbBctWE=; b=UjSm71ZtvqeiirSTdPvNF9DAEY4J4Bxo0xcNrulm8wMYuyMTIwbLaqei8d95aik0XK cRFKCQ72oOW/TFVhpV4SKFaCGODrnDJf0LwRU275P5egGzjEJiQ7pTGzDvFBi2McAqil TGLwrhJofdnEJqoVvV3CB8JxG/diPPm8zwrVXEVE87NiGVbXIkY8fkBUWVqJ8NutxMYD kjn853XsalCT2mrZ298uLvBjqF/TglZAkMst/QfkArLXCmw26d9tzgw7vwF1eYhOCxv2 z9oyUs69EhrfqAZ18GxZDOmWIprGl9UqelKQAEPPe2hkyMjv4WHE4DlC1kfLRb7LYqum YkTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BNunR/QlIojszKaQCmPReSbnVJ+yJh/8Aa/0xbBctWE=; b=39kHp6NPLAxHrinhCbAxvdgNYJtoxTv363rbKrIB0X/b/8Iugt0IVInimX2dMzsgeu cWwY8E6NjhWO9JpT/013cSRIJ9YKdYUNgTE3X+4vNPXhh1MNME1A7Ed2TukL/M+5btFU TWyXhIMCqzWX+yyVVE7b6UrKjbCm0/e51wuF4GiOQleuAmgJT+sB/2TFdwuuofGKvKmc z9w6wqjB1dqBb1lTdGNYIMxNzKEV5UiMucvQrDu1yg2JX6msm9E8jnvTE+jLoPF/zEXy 1/G1O8K97+B5pPQyQtxLxJ99qBRXiofRs5gxk+GvSW6GnK81hQz0nloom2aANTZliuSN jIQA==
X-Gm-Message-State: AOAM532X+pvJbjsGpw1OImP8YmOO4M1CdX3DQy1JovAESn26FGfd1jd7 TvUsXnV1ImoZS8WNAgYvzY+5e0lum/PVih8RY0aXlPX/9JA=
X-Google-Smtp-Source: ABdhPJyBvVMS2FS90ypwgXpZWcbR5cMZoB2oFr7pTNsbUV1iDlEi3mXWUtUjgHOe+tKREi0/AJp8fVJ3BOzmCecy5gs=
X-Received: by 2002:a92:dc90:0:b0:2be:f994:7dcf with SMTP id c16-20020a92dc90000000b002bef9947dcfmr22946116iln.160.1646142392403; Tue, 01 Mar 2022 05:46:32 -0800 (PST)
MIME-Version: 1.0
References: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr> <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com> <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr>
In-Reply-To: <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr>
From: Fabien Imbault <fabien.imbault@gmail.com>
Date: Tue, 1 Mar 2022 14:46:20 +0100
Message-ID: <CAM8feuTbKhAaniZfB4Fs5nJ35dSrb9_YTyP3dZuzvGM=sVH2HQ@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: GNAP Mailing List <txauth@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008c8e9605d92864aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/0i0nisJtxuEQQaVoIxbRwWs3lOo>
Subject: Re: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 13:46:37 -0000

--0000000000008c8e9605d92864aa
Content-Type: text/plain; charset="UTF-8"

Denis,

The RS draft is important, but the priority has been put into resolving the
open items of the main draft. As seen in the related PRs.

Please list the GitHub issues related to the RS draft that you'd like us to
focus on next.

Best regards,
Fabien

On Tue, 1 Mar 2022, 14:30 Denis, <denis.ietf@free.fr> wrote:

> Fabien,
>
> It is not useful to send flames.
>
> It would be much better that you spend time to respond to the issues
> raised on draft-ietf-gnap-resource-servers-01
> and publish a new draft that addresses these issues and in the mean time
> provide a summary of the way these issues have
> been addressed (including the issues you don't agree with).
>
> "Stabilizing the core draft" and "focusing on real world implementations"
> without progressing the resource-servers draft
> looks like a headlong rush.
>
> Denis
>
>
> Dear Denis,
>
> Sorry I have to say this, but repeating your misconceptions don't make
> them true. That's currently not helping anyone going forward.
>
> The editors and chairs welcome anyone with helpful contribution.
> Already the spec had many great improvements, from many outstanding
> individuals cited in the text. Including on security and privacy.
>
> We are now stabilizing the core draft and focusing on real world
> implementations to demonstrate the value and interoperability.
>
> Best regards,
> Fabien (speaking only in my own name)
>
>
>
>
> On Tue, 1 Mar 2022, 12:49 Denis, <denis.ietf@free.fr> wrote:
>
>> Hello everybody,
>>
>> GNAP has four main components : users, clients, ASs and RSs.
>>
>> GNAP is supposed to describe a protocol. A protocol is a set of rules
>> that control the way data is exchanged between computers.
>> A reader would expect to find the description of the data sent by a
>> client to a RS (which are indeed described in ietf-wg-gnap/core-protocol),
>>
>> but also find how that data *shall be handled by a RS* which is supposed
>> to be described in draft-ietf-gnap-resource-servers. Unfortunately,
>> this is not the case.
>>
>> The focus has been placed on the "core" protocol, leaving aside the the
>> RS.
>>
>> The core document (ietf-wg-gnap/core-protocol) has now got more than 400
>> issues !
>>
>> Besides the editors (and the chair), very few members are active and at
>> this time it is unlikely that more members will participate
>> since *the main driving line for the construction of GNAP has been los*
>> *t*.
>>
>> The recent message called "embedding GNAP" got no reply from the WG,
>> except one from a co-editor.
>> IMO, this demonstrates that *GNAP is still a **moving target* *after 20
>> months of work.*
>>
>> Does this mean that all the WG members agree with the very few emails
>> that are exchanged or that the WG members are
>> no longer really able to participate to the discussion since such
>> participation would involve a lot of days to get "up to speed" again ?
>> I would guess that the right answer is the latter.
>>
>> The core document has still *no security model *and hence its security
>> is more than questionable.
>>
>> The core document is AS centric and hence *the **privacy concerns of the
>> users cannot be addressed*. Is this deliberate ?
>> When the work started, privacy was supposed to be a major concern to be
>> taken into consideration, but in practice, this is not the case.
>>
>> The core document still does not address the general use case.
>>
>> There are so many options that *interoperability will not be possible*.
>>
>> *draft-ietf-gnap-resource-servers-01** expired on 13 January 2022*.  We
>> are now close to an IETF meeting and no draft is available.
>> The milestones are outdated and, anyway, are not observed (see
>> https://datatracker.ietf.org/doc/charter-ietf-gnap/writeup/)
>>
>> Milestones:
>>
>>   Jul 2021 - Core delegation protocol in WGLC
>>
>>   Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, to WGLC
>>
>>   Oct 2021 - Key presentation mechanism binding to the core protocol, detached HTTP signatures, to WGLC
>>
>>   Oct 2021 - Key presentation mechanism binding to the core protocol, embedded HTTP signature, to WGLC
>>
>>   Dec 2021 - Guidelines for use of protocol extension points to WGLC
>>
>>   Feb 2022 - Guidelines on migration paths, implementation, and operations to WGLC
>>
>>
>> At the next IETF meeting, rather than addressing, *as usual,* the last
>> technical issues that no one or very few people will be able to follow or
>> understand,
>> I would suggest that the editors address the following topics:
>> *interoperability*, *privacy *and *security *at a level that will allow
>> everybody to understand
>> the real issues behind these three words and by presenting *a balanced
>> view*.
>> Denis
>>
>> PS: If we were working within ISO, this WG would already have been closed.
>>
>> --
>> TXAuth mailing list
>> TXAuth@ietf.org
>> https://www.ietf.org/mailman/listinfo/txauth
>>
>
>

--0000000000008c8e9605d92864aa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Denis,<div dir=3D"auto"><br></div><div dir=3D"auto">The R=
S draft is important, but the priority has been put into resolving the open=
 items of the main draft. As seen in the related PRs.<br><div dir=3D"auto">=
<br></div><div dir=3D"auto">Please list the GitHub issues related to the RS=
 draft that you&#39;d like us to focus on next.</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">Best regards,</div><div dir=3D"auto">Fabien</div></=
div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Tue, 1 Mar 2022, 14:30 Denis, &lt;<a href=3D"mailto:denis.ietf@free.=
fr" target=3D"_blank" rel=3D"noreferrer">denis.ietf@free.fr</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>Fabien,</div>
    <div><br>
    </div>
    <div>It is not useful to send flames.</div>
    <div><br>
    </div>
    <div>It would be much better that you spend
      time to respond to the issues raised on
      draft-ietf-gnap-resource-servers-01 <br>
      and publish a new draft that addresses these issues and in the
      mean time provide a summary of the way these issues have <br>
      been addressed (including the issues you don&#39;t agree with).</div>
    <div><br>
    </div>
    <div>&quot;Stabilizing the core draft&quot; and
      &quot;focusing on real world implementations&quot; without progressin=
g the
      resource-servers draft <br>
      looks like a headlong rush.<br>
      <br>
      Denis<br>
    </div>
    <div><br>
    </div>
    <div> <br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"auto">
        <div>Dear Denis,
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">Sorry I have to say this, but repeating your
            misconceptions don&#39;t make them true. That&#39;s currently n=
ot
            helping anyone going forward.</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">The editors and chairs welcome anyone with
            helpful contribution.=C2=A0</div>
          <div dir=3D"auto">Already the spec had many great improvements,
            from many outstanding individuals cited in the text.
            Including on security and privacy.</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">We are now stabilizing the core draft and
            focusing on real world implementations to demonstrate the
            value and interoperability.=C2=A0</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto">Best regards,</div>
          <div dir=3D"auto">Fabien (speaking only in my own name)</div>
          <div dir=3D"auto"><br>
          </div>
          <div dir=3D"auto"><br>
          </div>
          <br>
          <br>
          <div class=3D"gmail_quote">
            <div dir=3D"ltr" class=3D"gmail_attr">On Tue, 1 Mar 2022, 12:49
              Denis, &lt;<a href=3D"mailto:denis.ietf@free.fr" rel=3D"noref=
errer noreferrer noreferrer noreferrer" target=3D"_blank">denis.ietf@free.f=
r</a>&gt;
              wrote:<br>
            </div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div>
                <p>Hello everybody,<br>
                  <span id=3D"m_4852462029087906556m_2566016931783242226m_7=
161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><=
span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555m=
_6066375261535833907m_6506138452035884450protocol__48"></span></span></p>
                <p><span id=3D"m_4852462029087906556m_2566016931783242226m_=
7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14">=
<span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555=
m_6066375261535833907m_6506138452035884450protocol__48">GNAP
                      has four main components : users, clients, ASs and
                      RSs.</span></span></p>
                <p>GNAP is supposed to describe a protocol. A protocol
                  is <span id=3D"m_4852462029087906556m_2566016931783242226=
m_7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14=
"><span id=3D"m_4852462029087906556m_2566016931783242226m_71613458082863135=
55m_6066375261535833907m_6506138452035884450protocol__48">a
                      set of rules that control the way data is
                      exchanged between computers.<br>
                      A reader would expect to find the description of
                      the data sent by a client to a RS (which are
                      indeed described in </span></span><span id=3D"m_48524=
62029087906556m_2566016931783242226m_7161345808286313555m_60663752615358339=
07m_6506138452035884450protocol__14"><span id=3D"m_4852462029087906556m_256=
6016931783242226m_7161345808286313555m_6066375261535833907m_650613845203588=
4450protocol__48"><span id=3D"m_4852462029087906556m_2566016931783242226m_7=
161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><=
span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555m=
_6066375261535833907m_6506138452035884450protocol__48">ietf-wg-gnap/core-pr=
otocol)</span></span>,
                      <br>
                      but also find how that data <b>shall be handled
                        by a RS</b> which is supposed to be described in
                    </span></span><span id=3D"m_4852462029087906556m_256601=
6931783242226m_7161345808286313555m_6066375261535833907m_650613845203588445=
0protocol__14"><span id=3D"m_4852462029087906556m_2566016931783242226m_7161=
345808286313555m_6066375261535833907m_6506138452035884450protocol__48">draf=
t-ietf-gnap-resource-servers.
                      Unfortunately, <br>
                      this is not the case. </span></span></p>
                <p><span id=3D"m_4852462029087906556m_2566016931783242226m_=
7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14">=
<span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555=
m_6066375261535833907m_6506138452035884450protocol__48">The
                      focus has been placed on the &quot;core&quot; protoco=
l,
                      leaving aside the the RS.<br>
                    </span></span><br>
                  <span id=3D"m_4852462029087906556m_2566016931783242226m_7=
161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><=
span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555m=
_6066375261535833907m_6506138452035884450protocol__48">The
                      core document (ietf-wg-gnap/core-protocol) has now
                      got more than 400 issues ! <br>
                    </span></span></p>
                <p><span id=3D"m_4852462029087906556m_2566016931783242226m_=
7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14">=
<span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555=
m_6066375261535833907m_6506138452035884450protocol__48">Besides
                      the editors (and the chair), very few members are
                      active and at this time it is unlikely that more
                      members will participate <br>
                      since <b>the main driving line for the
                        construction of GNAP has been los</b><b>t</b>.<br>
                    </span></span></p>
                <p>The recent message called &quot;embedding GNAP&quot; got=
 no
                  reply from the WG, except one from a co-editor.<br>
                  IMO, this demonstrates that <font color=3D"#0000ff"><b>GN=
AP
                      is still a </b><b>moving target</b> </font><b><font c=
olor=3D"#0000ff">after 20 months of work</font>.</b><br>
                  <br>
                  Does this mean that all the WG members agree with the
                  very few emails that are exchanged or that the WG
                  members are <br>
                  no longer really able to participate to the discussion
                  since such participation would involve a lot of days
                  to get &quot;up to speed&quot; again ? <br>
                  I would guess that the right answer is the latter.</p>
                <p><span id=3D"m_4852462029087906556m_2566016931783242226m_=
7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14">=
<span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555=
m_6066375261535833907m_6506138452035884450protocol__48">The
                      core document has still <b>no security model </b>and
                      hence its security is more than questionable.<br>
                      <br>
                      The core document is AS centric and hence <b>the
                      </b><b>privacy concerns of the users cannot be
                        addressed</b>. Is this deliberate ?<br>
                    </span></span><span id=3D"m_4852462029087906556m_256601=
6931783242226m_7161345808286313555m_6066375261535833907m_650613845203588445=
0protocol__14"><span id=3D"m_4852462029087906556m_2566016931783242226m_7161=
345808286313555m_6066375261535833907m_6506138452035884450protocol__48">When
                      the work started, privacy was supposed to be a
                      major concern to be taken into consideration, but
                      in practice, this is not the case.</span></span><br>
                  <span id=3D"m_4852462029087906556m_2566016931783242226m_7=
161345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><=
span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555m=
_6066375261535833907m_6506138452035884450protocol__48"><span id=3D"m_485246=
2029087906556m_2566016931783242226m_7161345808286313555m_606637526153583390=
7m_6506138452035884450protocol__14"><span id=3D"m_4852462029087906556m_2566=
016931783242226m_7161345808286313555m_6066375261535833907m_6506138452035884=
450protocol__48"><span id=3D"m_4852462029087906556m_2566016931783242226m_71=
61345808286313555m_6066375261535833907m_6506138452035884450protocol__14"><s=
pan id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555m_=
6066375261535833907m_6506138452035884450protocol__48"><br>
                              The core document</span></span> still does
                          not address the general use case.</span></span></=
span></span></p>
                <p><span id=3D"m_4852462029087906556m_2566016931783242226m_=
7161345808286313555m_6066375261535833907m_6506138452035884450protocol__14">=
<span id=3D"m_4852462029087906556m_2566016931783242226m_7161345808286313555=
m_6066375261535833907m_6506138452035884450protocol__48">There
                      are so many options that <b>interoperability will
                        not be possible</b>. <br>
                    </span></span></p>
                <p><b>draft-ietf-gnap-resource-servers-01</b><b> expired
                    on 13 January 2022</b>.=C2=A0 We are now close to an IE=
TF
                  meeting and no draft is available.</p>
                The milestones are outdated and, anyway, are not
                observed (see<font color=3D"#0000ff"> <a href=3D"https://da=
tatracker.ietf.org/doc/charter-ietf-gnap/writeup/" rel=3D"noreferrer norefe=
rrer noreferrer noreferrer noreferrer" target=3D"_blank">https://datatracke=
r.ietf.org/doc/charter-ietf-gnap/writeup/</a></font>)<br>
                <pre>Milestones:

  Jul 2021 - Core delegation protocol in WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, TLS, =
to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, detac=
hed HTTP signatures, to WGLC

  Oct 2021 - Key presentation mechanism binding to the core protocol, embed=
ded HTTP signature, to WGLC

  Dec 2021 - Guidelines for use of protocol extension points to WGLC

  Feb 2022 - Guidelines on migration paths, implementation, and operations =
to WGLC

</pre>
                <p>At the next IETF meeting, rather than addressing, <i>as
                    usual,</i> the last technical issues that no one or
                  very few people will be able to follow or understand,
                  <br>
                  I would suggest that the editors address the following
                  topics: <b>interoperability</b>, <b>privacy </b>and
                  <b>security </b>at a level that will allow everybody
                  to understand <br>
                  the real issues behind these three words and by
                  presenting <font color=3D"#0000ff"><b>a balanced view</b>=
</font>.<br>
                </p>
                Denis
                <p>PS: If we were working within ISO, this WG would
                  already have been closed.<br>
                  <br>
                </p>
              </div>
              -- <br>
              TXAuth mailing list<br>
              <a href=3D"mailto:TXAuth@ietf.org" rel=3D"noreferrer
                noreferrer noreferrer noreferrer noreferrer" target=3D"_bla=
nk">TXAuth@ietf.org</a><br>
              <a href=3D"https://www.ietf.org/mailman/listinfo/txauth" rel=
=3D"noreferrer noreferrer noreferrer noreferrer noreferrer noreferrer" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/txauth</a><br>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
  </div>

</blockquote></div>

--0000000000008c8e9605d92864aa--


From nobody Tue Mar  1 08:36:23 2022
Return-Path: <leifj@sunet.se>
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 A35CC3A0D06 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 08:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.11
X-Spam-Level: 
X-Spam-Status: No, score=-7.11 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sunet.se
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 vysjdjUPYBKS for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 08:36:15 -0800 (PST)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (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 511C23A0D0E for <txauth@ietf.org>; Tue,  1 Mar 2022 08:36:14 -0800 (PST)
Received: by mail-lj1-x22b.google.com with SMTP id l12so10727112ljh.12 for <txauth@ietf.org>; Tue, 01 Mar 2022 08:36:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sunet.se; s=google; h=message-id:date:mime-version:user-agent:from:subject:to:references :content-language:in-reply-to:content-transfer-encoding; bh=XLtLwjrTGt7LcIvtuySwP7agB/ExLIEVAV40affqS3I=; b=daqKMxoXgiMILjTiblp9pcq1hsVeBf5/L8h2UXsRyjf/SD+vwBrz1VWuct1U+ETDJ0 tc4dR/2Tn97U46iyf1m5rM8H4F5jpZq/e4E0MButtQxsD+1ftCiqiIjzVBDFo7IdoLH8 gLPSGRMlkEy1io01hnJaNF9p+tpi3KZMKpOOWyyBJ1s/vNvxKOiMjufVELvNZYtHffNW DJE0aqPsZXEmKp5+T49oaot5jXeATfhyFLotAYqQeFcKSrML7mNjQ/ADaiBFCs6CjuZq vT/4irPu/xBvn/fUGqDNUK0L2rrBXYbU90uLvppssQVEgfxVv0wFyqT5N6b8mmBFgHKZ Knsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:from :subject:to:references:content-language:in-reply-to :content-transfer-encoding; bh=XLtLwjrTGt7LcIvtuySwP7agB/ExLIEVAV40affqS3I=; b=Sbs3tQtoZ51Pito0w0uDyGydGPAJ6PilFRnCzmBlp4DV+q9rQIvBSux01n47Ppi6+9 PfQcH1qu2F0PSqmdvKA6kYVxvD9x2JAaj6/PxYgWjo/A8xVxW8fs523JjSOfYOB33vvy df6t8pV5pNHWehv7p5bVvhVYQR2Oy5NUntwT5Gvqwa+dL2V8NT70IhDlIbfP4GuGLPzE k9bXlH4OOlzbbl6fnQBuCzTPnwRC699ZIlYQF0ukTfKljEZOAG0Q3CeZijFBZvUe8Tjk QZ2y0BPGkXsxCCg9dD7RvBx7+21IZJn46F9o3SEcGNWkV9NFaCTGWRRVUg1jV6UrUy38 8hMA==
X-Gm-Message-State: AOAM533N3M+3UHTxQgivqbyBfiLRLdXX2hbD7E0FxJ5FzVLMOT2sl/mH OpCoCsHn9AVNpxAnZ0E7mqD4/Bd/I772VQ==
X-Google-Smtp-Source: ABdhPJxvcwQmCXmtnysC21klCNeC2teyiNVgZ0K1M8D+cORO4HctXY1r6Z40cRE5POqV9nQIKu/7AA==
X-Received: by 2002:a2e:b525:0:b0:246:204c:3392 with SMTP id z5-20020a2eb525000000b00246204c3392mr17441450ljm.179.1646152571519;  Tue, 01 Mar 2022 08:36:11 -0800 (PST)
Received: from [10.10.2.77] ([81.228.115.53]) by smtp.gmail.com with ESMTPSA id u8-20020ac251c8000000b004458c1d1462sm1309890lfm.142.2022.03.01.08.36.10 for <txauth@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 01 Mar 2022 08:36:11 -0800 (PST)
Message-ID: <5e490ca9-bd66-f844-7271-f9d4ee6e9a6b@sunet.se>
Date: Tue, 1 Mar 2022 17:36:09 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
From: Leif Johansson <leifj@sunet.se>
To: txauth@ietf.org
References: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr> <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com> <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr>
Content-Language: en-US
In-Reply-To: <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/3meqRjENIMyJslPlnVhYPyfIJj0>
Subject: Re: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 16:36:22 -0000

On 2022-03-01 14:30, Denis wrote:
> Fabien,
> 
> It is not useful to send flames.
> 

Denis,

As chair I am wary of unsubstantiated comments in WG discussions. This is one such
case: Fabien was not "sending flames" by any reasonable definition of the term.

As a chair I am also aqutely aware of the fact that while you have written up your
comments as an I-D (as we advised you to do) there have not been any indication
of substantive support from the WG of this work whatsoever.

This means that you are in the rough here. I am not telling you to stop making
contributions but it is pretty clear that the WG does not agree with your views
and you can't force people to agree with you in the IETF.

If you wish to continue talking about your draft I encourage that but the txauth
list is not the place for that. If you want to make contributions to the current
active drafts in txauth that do not assume adoption of your draft or your point
of view then pls continue.

	Best R
	Leif


From nobody Tue Mar  1 09:00:38 2022
Return-Path: <denis.ietf@free.fr>
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 D80553A0D4E for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 09:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.944
X-Spam-Level: 
X-Spam-Status: No, score=-0.944 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.186, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 uYyBQFWn4rWZ for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 09:00:32 -0800 (PST)
Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (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 734DA3A0D50 for <txauth@ietf.org>; Tue,  1 Mar 2022 09:00:32 -0800 (PST)
Received: from [192.168.1.11] ([82.121.202.228]) by smtp.orange.fr with ESMTPA id P5rPnATC7u3WEP5rQnyhGW; Tue, 01 Mar 2022 18:00:30 +0100
X-ME-Helo: [192.168.1.11]
X-ME-Auth: OWU3ZmVkYWM0M2UwZWM1YifxM2Q3ZDk1YiUzNWJiZTM2MiliMTI0N2YxZmQ=
X-ME-Date: Tue, 01 Mar 2022 18:00:30 +0100
X-ME-IP: 82.121.202.228
Content-Type: multipart/alternative; boundary="------------TzKoF1zufimJtVTaN1ecu8DA"
Message-ID: <3fffdbfa-945e-57bd-3e67-03feaaa108ad@free.fr>
Date: Tue, 1 Mar 2022 18:00:28 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-GB
To: Leif Johansson <leifj@sunet.se>, txauth@ietf.org
References: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr> <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com> <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr> <5e490ca9-bd66-f844-7271-f9d4ee6e9a6b@sunet.se>
From: Denis <denis.ietf@free.fr>
In-Reply-To: <5e490ca9-bd66-f844-7271-f9d4ee6e9a6b@sunet.se>
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/P6WfMUitLYbnBaBVKtKqGspDlUY>
Subject: Re: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 17:00:36 -0000

This is a multi-part message in MIME format.
--------------TzKoF1zufimJtVTaN1ecu8DA
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Leif,

My initial email from this morning raised numerous issues. Instead of 
replying to them using technical or factual arguments,
they have all been swept by using a single sentence by using the wording 
"repeating your misconceptions" which is an offence
(or taken as such). Using such wording is not constructive.

A message with the topic"embedding GNAP" got no reply from the WG, 
except one from a co-editor.
Do you interpret such response as a support from the WG ?

The key question is whether the model should only be *AS-centric *(as it 
currently is) or should also allow to be *RS-centric*.
The first model is adequate for an enterprise or a closed community 
while the later is adequate for the WWW.
This is an important issue.

Denis

> On 2022-03-01 14:30, Denis wrote:
>> Fabien,
>>
>> It is not useful to send flames.
>>
>
> Denis,
>
> As chair I am wary of unsubstantiated comments in WG discussions. This 
> is one such
> case: Fabien was not "sending flames" by any reasonable definition of 
> the term.
>
> As a chair I am also aqutely aware of the fact that while you have 
> written up your
> comments as an I-D (as we advised you to do) there have not been any 
> indication
> of substantive support from the WG of this work whatsoever.
>
> This means that you are in the rough here. I am not telling you to 
> stop making
> contributions but it is pretty clear that the WG does not agree with 
> your views
> and you can't force people to agree with you in the IETF.
>
> If you wish to continue talking about your draft I encourage that but 
> the txauth
> list is not the place for that. If you want to make contributions to 
> the current
> active drafts in txauth that do not assume adoption of your draft or 
> your point
> of view then pls continue.
>
>     Best R
>     Leif
>

--------------TzKoF1zufimJtVTaN1ecu8DA
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Leif,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">My initial email from this morning
      raised numerous issues. Instead of replying to them using
      technical or factual arguments, <br>
      they have all been swept by using a single sentence by using the
      wording "repeating your misconceptions" which is an offence <br>
      (or taken as such). Using such wording is not constructive.<br>
    </div>
    <br>
    A message with the topic"embedding GNAP" got no reply from the WG,
    except one from a co-editor.<br>
    Do you interpret such response as a support from the WG ? <br>
    <p>The key question is whether the model should only be <b>AS-centric
      </b>(as it currently is) or should also allow to be <b>RS-centric</b>.<br>
      The first model is adequate for an enterprise or a closed
      community while the later is adequate for the WWW. <br>
      This is an important issue.<br>
    </p>
    <p>Denis<br>
      <br>
    </p>
    <blockquote type="cite"
      cite="mid:5e490ca9-bd66-f844-7271-f9d4ee6e9a6b@sunet.se">On
      2022-03-01 14:30, Denis wrote:
      <br>
      <blockquote type="cite">Fabien,
        <br>
        <br>
        It is not useful to send flames.
        <br>
        <br>
      </blockquote>
      <br>
      Denis,
      <br>
      <br>
      As chair I am wary of unsubstantiated comments in WG discussions.
      This is one such
      <br>
      case: Fabien was not "sending flames" by any reasonable definition
      of the term.
      <br>
      <br>
      As a chair I am also aqutely aware of the fact that while you have
      written up your
      <br>
      comments as an I-D (as we advised you to do) there have not been
      any indication
      <br>
      of substantive support from the WG of this work whatsoever.
      <br>
      <br>
      This means that you are in the rough here. I am not telling you to
      stop making
      <br>
      contributions but it is pretty clear that the WG does not agree
      with your views
      <br>
      and you can't force people to agree with you in the IETF.
      <br>
      <br>
      If you wish to continue talking about your draft I encourage that
      but the txauth
      <br>
      list is not the place for that. If you want to make contributions
      to the current
      <br>
      active drafts in txauth that do not assume adoption of your draft
      or your point
      <br>
      of view then pls continue.
      <br>
      <br>
          Best R
      <br>
          Leif
      <br>
      <br>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------TzKoF1zufimJtVTaN1ecu8DA--


From nobody Tue Mar  1 09:51:54 2022
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 552923A07A9 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 09:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 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, T_SCC_BODY_TEXT_LINE=-0.01, 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 o2J51HS0FYUk for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 09:51:50 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 1A2D13A07A3 for <txauth@ietf.org>; Tue,  1 Mar 2022 09:51:50 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id y5so13109525ill.13 for <txauth@ietf.org>; Tue, 01 Mar 2022 09:51:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4o1l340COPc5vthkuPDSCd+qyP9m7JQqehKrmWWNKH8=; b=h5DYyktSG2qCV5Wdh8/imkSwMKnqXGDoA9Sf7c/ZblAfhFk9M8gmWqpbWL6CN2Uhk5 xuZBbZ3mZfduU/SPL0WLY7NHgv5kIsoHGTqiJLlr+fta9mxU7Hz/Aa7r/B9oHx4Gz7rz gFbGDNesUQMSBZZe5/J7GuUqwlZC47hFGdLV8+l/qUfexhvBh2Fc6U75W4EuYFFnDdgv K2J5Z9HNmKjegI+Rm/ofSbjR0ABjpYjUp9ZDG+5cyFHEjyoLDaPxFIZhbzSNZyoAM44d Yv2LWk3W5WRpf69dj9JQ8sohIoiPy5AK1DlaqKkgLeZ2N53BedCcqOgTRXwQRRe6iYG2 XdRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4o1l340COPc5vthkuPDSCd+qyP9m7JQqehKrmWWNKH8=; b=IWPzZWXd37R15afTqqD80JsmHSamdOu9dpV2+XfyTb+XWCH0C5bswUDm2jZK/dldDG UAgm8qTnJ0aZHAjgepUcuSjDVf5fnHfquyQ+FJF65zQ+Lk1uEr3lIK709s0yTkEvKE+E 9uBFbsXtBeqehM4ENwkABMH/Kg6qBjZg6myU2h8g2SnGO5fhl44ey0LG5dSCrDYnxo4i 568ksZnUVgXUR61UFLkuOz+blCYCjmDWlVcEM5hckpyGUN71u+zVX768DFHAwlTgisHu uCXg6LO62gGJ18eGHZ9Vg6lm6w4LpRVberKmeYH+CqVS4j64DmMS4zZ6JMY3MJSS10uT EeNw==
X-Gm-Message-State: AOAM5318W0BgqdNt2zgqM4/O8HJYDew77X+OW1GZFc0cHnJFJU7FITKu ggImi2SlDm/hmLYb7j0JMwiZkk3pK43TxIIwlVc=
X-Google-Smtp-Source: ABdhPJx1n8C65V8UTXMvz99E2avIZlIe2Rb30anpVBljskNRejiEyOi1m81AgNvjb7z/1NiDVh9XEdaJfMp4Soz+VYo=
X-Received: by 2002:a05:6e02:4c9:b0:2c4:906e:df82 with SMTP id f9-20020a056e0204c900b002c4906edf82mr1533647ils.317.1646157108888; Tue, 01 Mar 2022 09:51:48 -0800 (PST)
MIME-Version: 1.0
References: <5d89f969-2e67-32f4-e06b-e230453a906f@free.fr> <CAM8feuQ84ECPZnTsWcbrt4sqR2kS5bgP8m3=RSO9bq-4qJngFg@mail.gmail.com> <58fdd803-00ad-519c-0781-b0b7259d4098@free.fr> <5e490ca9-bd66-f844-7271-f9d4ee6e9a6b@sunet.se> <3fffdbfa-945e-57bd-3e67-03feaaa108ad@free.fr>
In-Reply-To: <3fffdbfa-945e-57bd-3e67-03feaaa108ad@free.fr>
From: Fabien Imbault <fabien.imbault@gmail.com>
Date: Tue, 1 Mar 2022 18:51:37 +0100
Message-ID: <CAM8feuQkpN-d3Vn02Yj0-rNdUQmu_FZDu+RRCnGRzh=Lwd+B0Q@mail.gmail.com>
To: Denis <denis.ietf@free.fr>
Cc: Leif Johansson <leifj@sunet.se>, GNAP Mailing List <txauth@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b8508a05d92bd131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/gs8z9nGEEOH6aoKO3Musygs1eDQ>
Subject: Re: [GNAP] Concerns with the lack of progression of GNAP after 20 months of work
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 17:51:53 -0000

--000000000000b8508a05d92bd131
Content-Type: text/plain; charset="UTF-8"

Denis,

All of your issues on the core draft already got their answers, in full and
extensive details both in writing and during public calls. The "repeating"
part is a fact visible in the tracking issues.

I agree that there is remaining work on the RS draft and can commit working
on that.

Best regards
Fabien

On Tue, 1 Mar 2022, 18:00 Denis, <denis.ietf@free.fr> wrote:

> Leif,
>
> My initial email from this morning raised numerous issues. Instead of
> replying to them using technical or factual arguments,
> they have all been swept by using a single sentence by using the wording
> "repeating your misconceptions" which is an offence
> (or taken as such). Using such wording is not constructive.
>
> A message with the topic"embedding GNAP" got no reply from the WG, except
> one from a co-editor.
> Do you interpret such response as a support from the WG ?
>
> The key question is whether the model should only be *AS-centric *(as it
> currently is) or should also allow to be *RS-centric*.
> The first model is adequate for an enterprise or a closed community while
> the later is adequate for the WWW.
> This is an important issue.
>
> Denis
>
> On 2022-03-01 14:30, Denis wrote:
>
> Fabien,
>
> It is not useful to send flames.
>
>
> Denis,
>
> As chair I am wary of unsubstantiated comments in WG discussions. This is
> one such
> case: Fabien was not "sending flames" by any reasonable definition of the
> term.
>
> As a chair I am also aqutely aware of the fact that while you have written
> up your
> comments as an I-D (as we advised you to do) there have not been any
> indication
> of substantive support from the WG of this work whatsoever.
>
> This means that you are in the rough here. I am not telling you to stop
> making
> contributions but it is pretty clear that the WG does not agree with your
> views
> and you can't force people to agree with you in the IETF.
>
> If you wish to continue talking about your draft I encourage that but the
> txauth
> list is not the place for that. If you want to make contributions to the
> current
> active drafts in txauth that do not assume adoption of your draft or your
> point
> of view then pls continue.
>
>     Best R
>     Leif
>
>
> --
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth
>

--000000000000b8508a05d92bd131
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">Denis,<div dir=3D"auto"><div dir=3D"auto"><br></div><div =
dir=3D"auto">All of your issues on the core draft already got their answers=
, in full and extensive details both in writing and during public calls. Th=
e &quot;repeating&quot; part is a fact visible in the tracking issues.=C2=
=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">I agree that there i=
s remaining work on the RS draft and can commit working on that.</div><div =
dir=3D"auto"><br></div><div dir=3D"auto">Best regards</div><div dir=3D"auto=
">Fabien=C2=A0</div></div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Tue, 1 Mar 2022, 18:00 Denis, &lt;<a href=3D"m=
ailto:denis.ietf@free.fr">denis.ietf@free.fr</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
 =20
   =20
 =20
  <div>
    <div>Leif,</div>
    <div><br>
    </div>
    <div>My initial email from this morning
      raised numerous issues. Instead of replying to them using
      technical or factual arguments, <br>
      they have all been swept by using a single sentence by using the
      wording &quot;repeating your misconceptions&quot; which is an offence=
 <br>
      (or taken as such). Using such wording is not constructive.<br>
    </div>
    <br>
    A message with the topic&quot;embedding GNAP&quot; got no reply from th=
e WG,
    except one from a co-editor.<br>
    Do you interpret such response as a support from the WG ? <br>
    <p>The key question is whether the model should only be <b>AS-centric
      </b>(as it currently is) or should also allow to be <b>RS-centric</b>=
.<br>
      The first model is adequate for an enterprise or a closed
      community while the later is adequate for the WWW. <br>
      This is an important issue.<br>
    </p>
    <p>Denis<br>
      <br>
    </p>
    <blockquote type=3D"cite">On
      2022-03-01 14:30, Denis wrote:
      <br>
      <blockquote type=3D"cite">Fabien,
        <br>
        <br>
        It is not useful to send flames.
        <br>
        <br>
      </blockquote>
      <br>
      Denis,
      <br>
      <br>
      As chair I am wary of unsubstantiated comments in WG discussions.
      This is one such
      <br>
      case: Fabien was not &quot;sending flames&quot; by any reasonable def=
inition
      of the term.
      <br>
      <br>
      As a chair I am also aqutely aware of the fact that while you have
      written up your
      <br>
      comments as an I-D (as we advised you to do) there have not been
      any indication
      <br>
      of substantive support from the WG of this work whatsoever.
      <br>
      <br>
      This means that you are in the rough here. I am not telling you to
      stop making
      <br>
      contributions but it is pretty clear that the WG does not agree
      with your views
      <br>
      and you can&#39;t force people to agree with you in the IETF.
      <br>
      <br>
      If you wish to continue talking about your draft I encourage that
      but the txauth
      <br>
      list is not the place for that. If you want to make contributions
      to the current
      <br>
      active drafts in txauth that do not assume adoption of your draft
      or your point
      <br>
      of view then pls continue.
      <br>
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0Best R
      <br>
      =C2=A0=C2=A0=C2=A0=C2=A0Leif
      <br>
      <br>
    </blockquote>
    <p><br>
    </p>
  </div>

-- <br>
TXAuth mailing list<br>
<a href=3D"mailto:TXAuth@ietf.org" target=3D"_blank" rel=3D"noreferrer">TXA=
uth@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/txauth" rel=3D"noreferrer =
noreferrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/txauth<=
/a><br>
</blockquote></div>

--000000000000b8508a05d92bd131--


From nobody Tue Mar  1 12:26:27 2022
Return-Path: <yaronf.ietf@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 96D3D3A0D22 for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 12:26:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 3cj_kSDQj0Qj for <txauth@ietfa.amsl.com>; Tue,  1 Mar 2022 12:26:24 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 381263A0D27 for <txauth@ietf.org>; Tue,  1 Mar 2022 12:26:24 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id w7so19867948ioj.5 for <txauth@ietf.org>; Tue, 01 Mar 2022 12:26:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=6MI/nWlP8gW+XYbVF+6hoypc9xSBj8lXXGa+VLC6A9Y=; b=HMDsycsg3E1JQylN4n2mW1YHZI+L/q73Z/Bym/p8fjekkyrLdTbdDdciXHPIbWxbvc b8syU++yGak0Ye2KzNgfljqzinU8nfXAyaLmD86NmY1guorWoP/Jc+t4J39qgVNmUm8+ znmh5CWgE87kcedPonuGlhf7Klgg+a7WvUN7i41P9lx+DO2gOBzCQKsVc+BY3LcprMaf wnnVnuUarLn4pU9LzsyyMHwRBR1PFAkZgK63wo3D7CBhfx50OOPM6FiRgn1ubNQzpPO3 LzcnL8Xcqrp2vfEJzUvXqBGj7gV70go7Iz8C+2rQLDLW5TYttlrafuxWpzjT9MANRe6W pLyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=6MI/nWlP8gW+XYbVF+6hoypc9xSBj8lXXGa+VLC6A9Y=; b=Q8h3bOKmkmBmrl7jMVbhnuCc2O6h5vKngU4eBj1qR2/K/4JZRH85lr5BkBvQ7SbtCO Uys6rbxVF150IYm7owHDkPNDed/XkYJZeZQIQm3xeE+Yd7OUNW/JaLo7GNC9CquZS/Dz /yJ3hwmt7TYYh1qchXxhTAX3a+u8QvvOW8QTN/NtQC1khipNPNjlqSRv88O0FM6Ci5U3 O31IUrtP5/BfmQ/UbhNNxYrrgkhRfq3QYvOjjWxeC8esGrV9SOs8c3hLRI9JM44HlBSW ugVqLq1vJ1mdO9bf9SReYQ0AGymTJZdiiw42DlPR2w9QE1MlALAvGfVtH5zQmHQJUAnv LShQ==
X-Gm-Message-State: AOAM531rL13AKkZHCsJea9y8Fk6wI5A/Xd2WPGrG51pFUQ4yJd1bHNsE QajnOvWZX5acRyEX6c00Hn5Zn3sUEso=
X-Google-Smtp-Source: ABdhPJw1kEIGDmk+CmiipBfiNpZ8QihA2R4wzKXLk7wloUTcWWL0Cw5kfAPuwWk6R0XAfw9RxqHy5g==
X-Received: by 2002:a05:6638:164a:b0:314:e841:c9f8 with SMTP id a10-20020a056638164a00b00314e841c9f8mr22422194jat.193.1646166382970;  Tue, 01 Mar 2022 12:26:22 -0800 (PST)
Received: from [192.168.68.108] (IGLD-84-229-146-220.inter.net.il. [84.229.146.220]) by smtp.gmail.com with ESMTPSA id u15-20020a056e021a4f00b002c27332ef9dsm8704078ilv.47.2022.03.01.12.26.21 for <txauth@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Mar 2022 12:26:22 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.58.22021501
Date: Tue, 01 Mar 2022 22:26:20 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: GNAP Mailing List <txauth@ietf.org>
Message-ID: <A634F09C-A25C-49C0-8C8E-00748CDA2E36@gmail.com>
Thread-Topic: GNAP agenda items
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3729018381_405449963"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/zHeFUOe1mWQCMJggeS9GhX33r7k>
Subject: [GNAP] GNAP agenda items
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 01 Mar 2022 20:26:26 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3729018381_405449963
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Hi,

=20

We will be meeting on March 25. Please send Leif and myself any requests fo=
r agenda items by March 8.

=20

Thanks,

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Yaron


--B_3729018381_405449963
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equiv=3DC=
ontent-Type content=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D=
"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-US link=3D"#0563C1" vlink=3D"#954F72" style=3D'wo=
rd-wrap:break-word'><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt'>We will be meeting on March 25. Please send Leif and myse=
lf any requests for agenda items by March 8.<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt'>Thanks,<o:p></o:p></span></p><p cl=
ass=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 =
Yaron<o:p></o:p></span></p></div></body></html>

--B_3729018381_405449963--



From nobody Fri Mar  4 02:24:59 2022
Return-Path: <jricher@mit.edu>
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 134BF3A129D for <txauth@ietfa.amsl.com>; Fri,  4 Mar 2022 02:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 vEf2VLsa2DJP for <txauth@ietfa.amsl.com>; Fri,  4 Mar 2022 02:24:55 -0800 (PST)
Received: from outgoing-exchange-7.mit.edu (outgoing-exchange-7.mit.edu [18.9.28.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B073B3A147B for <txauth@ietf.org>; Fri,  4 Mar 2022 02:24:26 -0800 (PST)
Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 224ANl6S019171; Fri, 4 Mar 2022 05:24:22 -0500
Received: from w92expo18.exchange.mit.edu (18.7.74.72) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.28; Fri, 4 Mar 2022 05:23:16 -0500
Received: from oc11expo18.exchange.mit.edu (18.9.4.49) by w92expo18.exchange.mit.edu (18.7.74.72) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 4 Mar 2022 05:23:48 -0500
Received: from oc11expo18.exchange.mit.edu ([18.9.4.49]) by oc11expo18.exchange.mit.edu ([18.9.4.49]) with mapi id 15.00.1497.023; Fri, 4 Mar 2022 05:23:48 -0500
From: Justin Richer <jricher@mit.edu>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, GNAP Mailing List <txauth@ietf.org>
Thread-Topic: GNAP agenda items
Thread-Index: AQHYLaqmQFPPnzXEz0ap2E3TLYt2AayvCE1H
Date: Fri, 4 Mar 2022 10:23:48 +0000
Message-ID: <801adfd4c0b0441680d9b6e79b6b25e7@oc11expo18.exchange.mit.edu>
References: <A634F09C-A25C-49C0-8C8E-00748CDA2E36@gmail.com>
In-Reply-To: <A634F09C-A25C-49C0-8C8E-00748CDA2E36@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [71.174.62.56]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/sZ__OGtFGMTeLwMjQ3NXfJG8G7c>
Subject: Re: [GNAP] GNAP agenda items
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Mar 2022 10:24:57 -0000

I would like about 20 min to discuss the protocol embedding idea that's com=
e up recently.

-Justin=20
________________________________________
From: TXAuth [txauth-bounces@ietf.org] on behalf of Yaron Sheffer [yaronf.i=
etf@gmail.com]
Sent: Tuesday, March 1, 2022 3:26 PM
To: GNAP Mailing List
Subject: [GNAP] GNAP agenda items

Hi,

We will be meeting on March 25. Please send Leif and myself any requests fo=
r agenda items by March 8.

Thanks,
                Yaron


From nobody Sun Mar  6 01:30:58 2022
Return-Path: <do_not_reply@mnot.net>
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 339973A08F6 for <txauth@ietfa.amsl.com>; Sun,  6 Mar 2022 01:30:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.709
X-Spam-Level: 
X-Spam-Status: No, score=-1.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=mnot.net header.b=vvPZdQj+; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=XstatrxW
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 Ro0PU4l5OcKT for <txauth@ietfa.amsl.com>; Sun,  6 Mar 2022 01:30:50 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DD913A08CF for <txauth@ietf.org>; Sun,  6 Mar 2022 01:30:50 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id AF4B85C029B for <txauth@ietf.org>; Sun,  6 Mar 2022 02:39:21 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 06 Mar 2022 02:39:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-type:date:from:from:in-reply-to:mime-version:reply-to :sender:subject:subject:to:to; s=fm2; bh=PTdVNFIqsGVBofX5P9HVaC+ xCABP37rrmrgIRLScSuA=; b=vvPZdQj+WFJfG8IxFnxESo5z1XDto/x7YYIqJqp IehFcy5RP0QLvCJ98G5OOZqy9Fwn2hji+Ft2mATMiTkBA9YZWxnejjBeWBqB85Kc 1jjSY2dIUsAdHmIvk9eP3bu4CaOWlgptmvV65wJ5/yzCkcaPZ3bZpyfw+Sy7PzMq 70eptnXxtLVqAsmoklDNny9TaMpnowJrtckViJ/mxwMD0YI52D1RaLZlZgXdxxBk wcABUSZa4A+ImIFnbiVt9H+PzIIifn7jCDoIOYHa3p2EKvuwbDrEG/3Ba39sVK1D 7GlScNzSn8wlXfx2IhOoJ8uyZ3cXE7nndEO0Cq8fn/iZ/8A==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:from :in-reply-to:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=PTdVNFIqsGVBofX5P9HVaC+xCABP37rrmrgIRLScSuA=; b=XstatrxW yA43tbR406qCqxXuveNwcZ9IGJj55GbWvJSuhuQCjxr2NK7fKYW9VFHxlJsvl13T hLXs0zhz8qjYI1X2hCPFzYr4XkYtAkPtCY5oTNuPNbIuH4Z01Oydh9PcDAQqSlmm 8rdAGjxeZQ3sf8CixouF7zW0J9kXDbQb1OXQBI83j30qTdgVaYgBNZNjqPnN2/+I glVhquqb992lcS0s+Oe9OR2dNUYXBeZIQtBsS0ajwUgsLvAmOeuVCcjBYegZZmkv fe+Uga6EUbK8GvohtT045DDbQT+II8NJTaPgDRrHjgYoi44qAkPzKixTADuvro3w ozXN7FMvs3KfHQ==
X-ME-Sender: <xms:KWUkYtZGkAcNeUKdgBsB1QAfV3cxTU4PjmkbLKMoaUfUY_a8Vk8hYQ> <xme:KWUkYkaJUAEsBzqgxLetVdQ4Id1zZoXnUDm6y9hY21iExWH7gkpCwu1z8snzoucMw m-Fsd9laGb54NaBDQ>
X-ME-Received: <xmr:KWUkYv-uhyK9ZGfpooWvy_H0ICHWIT6P0SSDbLZouWLYnckw5kCHcjA-CgvmBaWwuCfK6LRlnXz7qfX3L27HTYBhPietlibNtcjTM_pDsNvyXAD9ibST-JZNFJ2k3a7x4Rk>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudduuddguddutdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:KWUkYroI9lTQgAA1R_uuzAn-kJ05fqL1C55-Si53bpWh84ZKfGHcXA> <xmx:KWUkYoqXVMyT0neW_NvAMoAwKEikshITcMrqWvysorspaOJEpfDhLA> <xmx:KWUkYhQeSeAc6o6gQtcFk0hlLKx0c0Tv1TM7igkw_uV2CyMDI-OpkA> <xmx:KWUkYv1LwzrsIAr4KE5332kOC4j9g9Hr64t_-Ibixy7zH7v1YO7rdw>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <txauth@ietf.org>; Sun, 6 Mar 2022 02:39:21 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============9147696567591931908=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20220306093050.3DD913A08CF@ietfa.amsl.com>
Date: Sun,  6 Mar 2022 01:30:50 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/JfRlBL_RtkUQYVluY_TUd0Uetlg>
Subject: [GNAP] Weekly github digest (GNAP Weekly GitHub Activity Summary)
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 06 Mar 2022 09:30:56 -0000

--===============9147696567591931908==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* ietf-wg-gnap/core-protocol (+2/-15/=F0=9F=92=AC6)
  2 issues created:
  - Please take a look a BCP 107 (a.k.a. RFC 4107).  You may need a referen=
ce here. (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/412=20
  - Discuss ways to find the grant endpoint (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/411=20

  3 issues received 6 new comments:
  - #412 Please take a look a BCP 107 (a.k.a. RFC 4107).  You may need a re=
ference here. (3 by fimbault, russhousley)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/412=20
  - #408 grant_request_endpoint - URL matching? (2 by jricher, yaronf)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/408=20
  - #407 Access rights by reference (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/407=20

  15 issues closed:
  - Format of defining REQUIRED vs OPTIONAL request/response elements https=
://github.com/ietf-wg-gnap/gnap-core-protocol/issues/257 [Editorial]=20
  - Awkward wording around Client Instance Identifiers https://github.com/i=
etf-wg-gnap/gnap-core-protocol/issues/396=20
  - User information request items https://github.com/ietf-wg-gnap/gnap-cor=
e-protocol/issues/43 [Pending Close]=20
  - Why do we even support symmetric keys? https://github.com/ietf-wg-gnap/=
gnap-core-protocol/issues/299=20
  - End user/client instance mix-up attack https://github.com/ietf-wg-gnap/=
gnap-core-protocol/issues/364=20
  - How to ensure that the end-user is present? https://github.com/ietf-wg-=
gnap/gnap-core-protocol/issues/361=20
  - Being "Present on the Request" https://github.com/ietf-wg-gnap/gnap-cor=
e-protocol/issues/22=20
  - Clarify User-Code Interaction https://github.com/ietf-wg-gnap/gnap-core=
-protocol/issues/9=20
  - Stable URL for =E2=80=9CDisplay of a Short User Code=E2=80=9D https://g=
ithub.com/ietf-wg-gnap/gnap-core-protocol/issues/123=20
  - Default polling wait time https://github.com/ietf-wg-gnap/gnap-core-pro=
tocol/issues/86=20
  - Logo by value https://github.com/ietf-wg-gnap/gnap-core-protocol/issues=
/48=20
  - Assertion format names https://github.com/ietf-wg-gnap/gnap-core-protoc=
ol/issues/41=20
  - Use of the terms URI and URL https://github.com/ietf-wg-gnap/gnap-core-=
protocol/issues/341=20
  - Name the first sequence https://github.com/ietf-wg-gnap/gnap-core-proto=
col/issues/392=20
  - grant_request_endpoint - URL matching? https://github.com/ietf-wg-gnap/=
gnap-core-protocol/issues/408=20



Pull requests
-------------
* ietf-wg-gnap/core-protocol (+1/-14/=F0=9F=92=AC2)
  1 pull requests submitted:
  - removed closed issues (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/413=20

  2 pull requests received 2 new comments:
  - #413 removed closed issues (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/413 [Editorial]=
=20
  - #380 data URI for logo (1 by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/380 [Pending Me=
rge]=20

  14 pull requests merged:
  - removed closed issues
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/413 [Editorial]=
=20
  - Consistent formatting of parameter lists
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/400 [Pending Me=
rge]=20
  - rewording
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/402 [Pending Me=
rge]=20
  - cleanup issue 43
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/401 [Pending Me=
rge]=20
  - new 7.1.2 section on key protection
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/399 [Pending Me=
rge]=20
  - Minor edits
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/394 [Editorial]=
=20
  - Specify the content type for Discovery's endpoint response
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/398 [Pending Me=
rge]=20
  - Clarified user presence on interaction finish methods
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/390 [Pending Me=
rge]=20
  - Redefine user code interaction methods
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/389 [Pending Me=
rge]=20
  - Strengthened normative requirements for continue timeout
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/388 [Pending Me=
rge]=20
  - data URI for logo
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/380 [Pending Me=
rge]=20
  - assertions as array
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/379 [Pending Me=
rge]=20
  - harmonize URL/URI
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/377 [Pending Me=
rge]=20
  - Rename overall diagram
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/403 [Pending Me=
rge]=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-gnap/core-protocol
* https://github.com/ietf-wg-gnap/gnap-resource-servers

--===============9147696567591931908==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (GNAP Weekly GitHub Activity Summary)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday March 06, 2022</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>ietf-wg-gnap/core-protocol (+2/-15/=F0=9F=92=AC6)</h3>
  <p class=3D"new">2 issues created:</p>
  <ul>
  <li>#412 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/412">Please take a look a BCP 107 (a.k.a. RFC 4107).  You may need a r=
eference here.</a> (by jricher) </li>
 =20
  <li>#411 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/411">Discuss ways to find the grant endpoint</a> (by jricher) </li>
  </ul>

  <p>3 issues received 6 new comments:</p>
  <ul>
  <li>#412 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/412">Please take a look a BCP 107 (a.k.a. RFC 4107).  You may need a r=
eference here.</a> (3 by fimbault, russhousley) </li>
 =20
  <li>#408 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/408">grant_request_endpoint - URL matching?</a> (2 by jricher, yaronf)=
 </li>
 =20
  <li>#407 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/407">Access rights by reference</a> (1 by fimbault) </li>
  </ul>

  <p>15 issues closed:</p>
  <ul>
  <li>#257 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/257">Format of defining REQUIRED vs OPTIONAL request/response elements=
</a> <span class=3D"label" style=3D"background-color: #bfd4f2; color: #0000=
00">Editorial</span> </li>
 =20
  <li>#396 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/396">Awkward wording around Client Instance Identifiers</a> </li>
 =20
  <li>#43 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/iss=
ues/43">User information request items</a> <span class=3D"label" style=3D"b=
ackground-color: #f2c276; color: #000000">Pending Close</span> </li>
 =20
  <li>#299 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/299">Why do we even support symmetric keys?</a> </li>
 =20
  <li>#364 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/364">End user/client instance mix-up attack</a> </li>
 =20
  <li>#361 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/361">How to ensure that the end-user is present?</a> </li>
 =20
  <li>#22 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/iss=
ues/22">Being &quot;Present on the Request&quot;</a> </li>
 =20
  <li>#9 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/issu=
es/9">Clarify User-Code Interaction</a> </li>
 =20
  <li>#123 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/123">Stable URL for =E2=80=9CDisplay of a Short User Code=E2=80=9D</a>=
 </li>
 =20
  <li>#86 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/iss=
ues/86">Default polling wait time</a> </li>
 =20
  <li>#48 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/iss=
ues/48">Logo by value</a> </li>
 =20
  <li>#41 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/iss=
ues/41">Assertion format names</a> </li>
 =20
  <li>#341 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/341">Use of the terms URI and URL</a> </li>
 =20
  <li>#392 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/392">Name the first sequence</a> </li>
 =20
  <li>#408 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/408">grant_request_endpoint - URL matching?</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>ietf-wg-gnap/core-protocol (+1/-14/=F0=9F=92=AC2)</h3>
  <p class=3D"new">1 pull requests submitted:</p>
  <ul>
  <li>#413 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/413">removed closed issues</a> (by jricher) </li>
  </ul>

  <p>2 pull requests received 2 new comments:</p>
  <ul>
  <li>#413 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/413">removed closed issues</a> (1 by netlify) <span class=3D"label" styl=
e=3D"background-color: #bfd4f2; color: #000000">Editorial</span> </li>
 =20
  <li>#380 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/380">data URI for logo</a> (1 by jricher) <span class=3D"label" style=3D=
"background-color: #a6f490; color: #000000">Pending Merge</span> </li>
  </ul>

  <p>14 pull requests merged:</p>
  <ul>
  <li>#413 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/413">removed closed issues</a> <span class=3D"label" style=3D"background=
-color: #bfd4f2; color: #">Editorial</span> </li>
 =20
  <li>#400 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/400">Consistent formatting of parameter lists</a> <span class=3D"label" =
style=3D"background-color: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#402 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/402">rewording</a> <span class=3D"label" style=3D"background-color: #a6f=
490; color: #">Pending Merge</span> </li>
 =20
  <li>#401 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/401">cleanup issue 43</a> <span class=3D"label" style=3D"background-colo=
r: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#399 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/399">new 7.1.2 section on key protection</a> <span class=3D"label" style=
=3D"background-color: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#394 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/394">Minor edits</a> <span class=3D"label" style=3D"background-color: #b=
fd4f2; color: #">Editorial</span> </li>
 =20
  <li>#398 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/398">Specify the content type for Discovery&#x27;s endpoint response</a>=
 <span class=3D"label" style=3D"background-color: #a6f490; color: #">Pendin=
g Merge</span> </li>
 =20
  <li>#390 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/390">Clarified user presence on interaction finish methods</a> <span cla=
ss=3D"label" style=3D"background-color: #a6f490; color: #">Pending Merge</s=
pan> </li>
 =20
  <li>#389 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/389">Redefine user code interaction methods</a> <span class=3D"label" st=
yle=3D"background-color: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#388 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/388">Strengthened normative requirements for continue timeout</a> <span =
class=3D"label" style=3D"background-color: #a6f490; color: #">Pending Merge=
</span> </li>
 =20
  <li>#380 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/380">data URI for logo</a> <span class=3D"label" style=3D"background-col=
or: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#379 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/379">assertions as array</a> <span class=3D"label" style=3D"background-c=
olor: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#377 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/377">harmonize URL/URI</a> <span class=3D"label" style=3D"background-col=
or: #a6f490; color: #">Pending Merge</span> </li>
 =20
  <li>#403 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/403">Rename overall diagram</a> <span class=3D"label" style=3D"backgroun=
d-color: #a6f490; color: #">Pending Merge</span> </li>
  </ul>


  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-wg-gnap/core-protocol">https://git=
hub.com/ietf-wg-gnap/core-protocol</a></li>
  <li><a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers">htt=
ps://github.com/ietf-wg-gnap/gnap-resource-servers</a></li>
</ul>
</details>
</body>
</html>

--===============9147696567591931908==--


From nobody Sun Mar  6 10:20:19 2022
Return-Path: <internet-drafts@ietf.org>
X-Original-To: txauth@ietf.org
Delivered-To: txauth@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E1D3A085D; Sun,  6 Mar 2022 10:20:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: txauth@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: txauth@ietf.org
Message-ID: <164659081053.9161.12035800802969687954@ietfa.amsl.com>
Date: Sun, 06 Mar 2022 10:20:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/AwKSDBI4dkvmrV4JL6rnfvcH0Es>
Subject: [GNAP] I-D Action: draft-ietf-gnap-core-protocol-09.txt
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 06 Mar 2022 18:20:11 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Grant Negotiation and Authorization Protocol WG of the IETF.

        Title           : Grant Negotiation and Authorization Protocol
        Authors         : Justin Richer
                          Aaron Parecki
                          Fabien Imbault
	Filename        : draft-ietf-gnap-core-protocol-09.txt
	Pages           : 168
	Date            : 2022-03-06

Abstract:
   GNAP defines a mechanism for delegating authorization to a piece of
   software, and conveying that delegation to the software.  This
   delegation can include access to a set of APIs as well as information
   passed directly to the software.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-gnap-core-protocol/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-gnap-core-protocol-09

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-gnap-core-protocol-09


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Mon Mar  7 08:22:43 2022
Return-Path: <denis.ietf@free.fr>
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 3BC723A0D40 for <txauth@ietfa.amsl.com>; Mon,  7 Mar 2022 08:22:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.057
X-Spam-Level: 
X-Spam-Status: No, score=0.057 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.186, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 btyebuouJTFn for <txauth@ietfa.amsl.com>; Mon,  7 Mar 2022 08:22:39 -0800 (PST)
Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) (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 705503A0E3A for <txauth@ietf.org>; Mon,  7 Mar 2022 08:21:50 -0800 (PST)
Received: from [192.168.1.11] ([82.121.202.228]) by smtp.orange.fr with ESMTPA id RG7GnNFbCBzeERG7GnWXDe; Mon, 07 Mar 2022 17:21:48 +0100
X-ME-Helo: [192.168.1.11]
X-ME-Auth: OWU3ZmVkYWM0M2UwZWM1YifxM2Q3ZDk1YiUzNWJiZTM2MiliMTI0N2YxZmQ=
X-ME-Date: Mon, 07 Mar 2022 17:21:48 +0100
X-ME-IP: 82.121.202.228
Content-Type: multipart/alternative; boundary="------------ruw7gk1n0ewNVSZKxlhcS6gh"
Message-ID: <ca3743e2-c38e-449c-635a-616aba4ec78f@free.fr>
Date: Mon, 7 Mar 2022 17:21:46 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1
Content-Language: en-GB
To: Yaron Sheffer <yaronf.ietf@gmail.com>, Leif Johansson <leifj@sunet.se>
References: <A634F09C-A25C-49C0-8C8E-00748CDA2E36@gmail.com> <801adfd4c0b0441680d9b6e79b6b25e7@oc11expo18.exchange.mit.edu>
Cc: GNAP Mailing List <txauth@ietf.org>
From: Denis <denis.ietf@free.fr>
In-Reply-To: <801adfd4c0b0441680d9b6e79b6b25e7@oc11expo18.exchange.mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/2xJjkGFo7pzrcN96JXJ9is5VJQs>
Subject: Re: [GNAP] GNAP agenda items
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 07 Mar 2022 16:22:41 -0000

This is a multi-part message in MIME format.
--------------ruw7gk1n0ewNVSZKxlhcS6gh
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Yaron and Leif,

I would like about 25 minutes (not including questions/responses) to 
present the following topics :

  * AS-centric model and RS-centric model,
  * Interoperability,
  * Privacy, and
  * Security.

Denis

> I would like about 20 min to discuss the protocol embedding idea that's come up recently.
>
> -Justin
> ________________________________________
> From: TXAuth [txauth-bounces@ietf.org] on behalf of Yaron Sheffer [yaronf.ietf@gmail.com]
> Sent: Tuesday, March 1, 2022 3:26 PM
> To: GNAP Mailing List
> Subject: [GNAP] GNAP agenda items
>
> Hi,
>
> We will be meeting on March 25. Please send Leif and myself any requests for agenda items by March 8.
>
> Thanks,
>                  Yaron
>

--------------ruw7gk1n0ewNVSZKxlhcS6gh
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">Hi Yaron and Leif,</div>
    <div class="moz-cite-prefix"><br>
    </div>
    <div class="moz-cite-prefix">I would like about 25 minutes (not
      including questions/responses) to present the following topics :</div>
    <ul>
      <li>AS-centric model and RS-centric model,</li>
      <li>Interoperability,</li>
      <li>Privacy, and</li>
      <li>Security.</li>
    </ul>
    <div class="moz-cite-prefix">Denis<br>
    </div>
    <div class="moz-cite-prefix"><br>
    </div>
    <blockquote type="cite"
      cite="mid:801adfd4c0b0441680d9b6e79b6b25e7@oc11expo18.exchange.mit.edu">
      <pre class="moz-quote-pre" wrap="">I would like about 20 min to discuss the protocol embedding idea that's come up recently.

-Justin 
________________________________________
From: TXAuth [<a class="moz-txt-link-abbreviated" href="mailto:txauth-bounces@ietf.org">txauth-bounces@ietf.org</a>] on behalf of Yaron Sheffer [<a class="moz-txt-link-abbreviated" href="mailto:yaronf.ietf@gmail.com">yaronf.ietf@gmail.com</a>]
Sent: Tuesday, March 1, 2022 3:26 PM
To: GNAP Mailing List
Subject: [GNAP] GNAP agenda items

Hi,

We will be meeting on March 25. Please send Leif and myself any requests for agenda items by March 8.

Thanks,
                Yaron

</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------ruw7gk1n0ewNVSZKxlhcS6gh--


From nobody Wed Mar  9 13:58:38 2022
Return-Path: <jricher@mit.edu>
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 EC1463A0D2D for <txauth@ietfa.amsl.com>; Wed,  9 Mar 2022 13:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.461
X-Spam-Level: 
X-Spam-Status: No, score=-1.461 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 7fM8RQklB_I2 for <txauth@ietfa.amsl.com>; Wed,  9 Mar 2022 13:58:34 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ACD43A0A79 for <txauth@ietf.org>; Wed,  9 Mar 2022 13:58:34 -0800 (PST)
Received: from smtpclient.apple (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 229LwSs3027860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <txauth@ietf.org>; Wed, 9 Mar 2022 16:58:30 -0500
From: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3F199500-FA4D-4F1A-9854-3A855C4FDDCC"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Message-Id: <EB4E5E5B-E4E1-44B4-9983-391DCBEB0E1A@mit.edu>
Date: Wed, 9 Mar 2022 16:58:28 -0500
To: GNAP Mailing List <txauth@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/gQ_-pZXhL4u8Mjx0Lj_D5XW0gv0>
Subject: [GNAP] IETF 113 Hackathon
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 09 Mar 2022 21:58:37 -0000

--Apple-Mail=_3F199500-FA4D-4F1A-9854-3A855C4FDDCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

IETF 113 is just a couple weeks away! GNAP will be participating the =
Hackathon this year, and the editors have started a wiki page to collect =
the libraries and implementations that are available:

=
=E2=80=8Bhttps://github.com/ietf-wg-gnap/general/wiki/Implementations-and-=
Libraries =
<https://github.com/ietf-wg-gnap/general/wiki/Implementations-and-Librarie=
s>

Please add to this list!

Our goals for the Hackathon are here, we=E2=80=99ve layered them so that =
people will be able to participate at different levels of completion:

Hackathon Project Goals: =
=E2=80=8Bhttps://github.com/ietf-wg-gnap/general/wiki/Hackathon-113-Goals =
<https://github.com/ietf-wg-gnap/general/wiki/Hackathon-113-Goals>

And finally there are new versions of the core specifications that we =
will be working with:

 - GNAP Core: =
=E2=80=8Bhttps://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-09.=
html =
<https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-09.html>
 - HTTP Message Signatures: =
=E2=80=8Bhttps://www.ietf.org/archive/id/draft-ietf-httpbis-message-signat=
ures-09.html =
<https://www.ietf.org/archive/id/draft-ietf-httpbis-message-signatures-09.=
html>


We hope to see you at the Hackathon and the meeting in Vienna!


=E2=80=94 Justin, Aaron, and Fabien


--Apple-Mail=_3F199500-FA4D-4F1A-9854-3A855C4FDDCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">IETF =
113 is just a couple weeks away! GNAP will be participating the =
Hackathon this year, and the editors have started a wiki page to collect =
the libraries and implementations that are available:<div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><div class=3D"">=E2=80=8B=
<a =
href=3D"https://github.com/ietf-wg-gnap/general/wiki/Implementations-and-L=
ibraries" =
class=3D"">https://github.com/ietf-wg-gnap/general/wiki/Implementations-an=
d-Libraries</a><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Please add to this list!</div><div =
class=3D""><br class=3D""></div><div class=3D"">Our goals for the =
Hackathon are here, we=E2=80=99ve layered them so that people will be =
able to participate at different levels of completion:</div><div =
class=3D""><br class=3D""></div><div class=3D"">Hackathon Project =
Goals:&nbsp;=E2=80=8B<a =
href=3D"https://github.com/ietf-wg-gnap/general/wiki/Hackathon-113-Goals" =
class=3D"">https://github.com/ietf-wg-gnap/general/wiki/Hackathon-113-Goal=
s</a><br class=3D""></div></div><div class=3D""><br class=3D""></div><div =
class=3D"">And finally there are new versions of the core specifications =
that we will be working with:</div><div class=3D""><br =
class=3D""></div><div class=3D"">&nbsp;- GNAP Core:&nbsp;=E2=80=8B<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-09.h=
tml" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-gnap-core-protocol-0=
9.html</a></div><div class=3D"">&nbsp;- HTTP Message =
Signatures:&nbsp;=E2=80=8B<a =
href=3D"https://www.ietf.org/archive/id/draft-ietf-httpbis-message-signatu=
res-09.html" =
class=3D"">https://www.ietf.org/archive/id/draft-ietf-httpbis-message-sign=
atures-09.html</a></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D"">We hope to see you at =
the Hackathon and the meeting in Vienna!</div><div class=3D""><br =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D"">=E2=80=
=94 Justin, Aaron, and Fabien</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_3F199500-FA4D-4F1A-9854-3A855C4FDDCC--


From nobody Fri Mar 11 03:06:08 2022
Return-Path: <fett@danielfett.de>
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 D49693A10E7; Fri, 11 Mar 2022 03:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level: 
X-Spam-Status: No, score=-7.108 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_HI=-5, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=danielfett.de
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 0E4ctDrb60as; Fri, 11 Mar 2022 03:05:37 -0800 (PST)
Received: from d3f.me (redstone.d3f.me [5.9.29.41]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57A113A10CE; Fri, 11 Mar 2022 03:05:37 -0800 (PST)
Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by d3f.me (Postfix) with ESMTPA id 3A18C1A417; Fri, 11 Mar 2022 11:05:34 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=dkim; t=1646996734; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jh3QHqjgTp71i+4cPSzl0nqnHnpjrqHQQpvde0B4FYw=; b=ZqDiC7EWSulSZDYmcsgFZkWIaMQgHucGRIQFnP8xJtKWzgKXgDIfKNVrTsYJNto5W/jG34 U8h3o8CHJpDvutk63fCQ59zqyMeyCkYlINg/WeuYxYIN2XuZZzmpLAbaHShcfsj6Aa2+BM quFOasOWlAVjv9qjDX2V+o8e3dO9JNI=
Content-Type: multipart/alternative; boundary="------------LJFTjVV6K0ZxZGYGDIwR99JH"
Message-ID: <44be7fac-0a09-da49-1891-044ba5bc4d89@danielfett.de>
Date: Fri, 11 Mar 2022 12:05:33 +0100
MIME-Version: 1.0
Content-Language: de-DE
From: Daniel Fett <fett@danielfett.de>
To: openid-specs-ab@lists.openid.net, openid-specs-ekyc-ida@lists.openid.net,  "oauth@ietf.org" <oauth@ietf.org>, txauth@ietf.org, openid-specs-fapi@lists.openid.net
References: <65435b42-3246-a51f-8bfb-eb55374d09da@danielfett.de>
In-Reply-To: <65435b42-3246-a51f-8bfb-eb55374d09da@danielfett.de>
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de;  s=dkim; t=1646996734; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=jh3QHqjgTp71i+4cPSzl0nqnHnpjrqHQQpvde0B4FYw=; b=vr2e6SCJYcxpOBkgDg/aOC86JYikqZaUqR1tXbUSeiKpK3mMOuj4gUGw9WXcvrEZIqluMs 6q4vzE/hm+T8MnpoGzhqs/VxcxW5cv5fWJdDd3Lt8Ak4RDJ0Qi5jfIhHUC1GRdDT4/lz5l DwGebzZMVfXG5Ufx3eKwd+9dYkzKAHc=
ARC-Seal: i=1; s=dkim; d=danielfett.de; t=1646996734; a=rsa-sha256; cv=none; b=kWhp5JD+FlrZcaYa49XD1y3gWgGUgFdW0y/n2CfbnYZjkNMw7G7kZ83xY/v4/UYiCyVykO JkTweyQhq31p2ZG91TRJCdW+HbUA1UF3+RYHNrpmGhlrKgdVlSKGqOKmEyUgZbw95Rsanl ZZMyqbRGl4j2vR8Oj8TRkiF0GhnlxIQ=
ARC-Authentication-Results: i=1; d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
Authentication-Results: d3f.me; auth=pass smtp.auth=fett@danielfett.de smtp.mailfrom=fett@danielfett.de
X-Spamd-Bar: -
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/_Ai7KRZs5wDedQg3ygan3jHhvF4>
Subject: Re: [GNAP] [OAUTH-WG] OAuth Security Workshop 2022 - Tickets now available
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Mar 2022 11:05:45 -0000

This is a multi-part message in MIME format.
--------------LJFTjVV6K0ZxZGYGDIwR99JH
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi everyone,

as a quick reminder, there's less than a week left to book early bird 
tickets. If you want to submit a session proposal, please do so until 
March 23.

Thanks,
Daniel

Am 11.02.22 um 22:27 schrieb Daniel Fett:
>
> Hi everyone,
>
> I'm pleased to announce that the website for the OAuth Security 
> Workshop 2022 is now up: https://oauth.secworkshop.events/osw2022
>
> The three-day event takes place in Trondheim, Norway, from May 4 to 
> May 6, 2022.
>
> This workshop will *not* be a hybrid event. We might provide 
> recordings or a live stream, but to ask questions and partake in 
> discussions, on-site participation is required.
>
> Please visit the website for
>
>  * tickets - a limited amount of early bird tickets is available until 
> no later than March 17
>  * the Call for Sessions
>  * venue and schedule information
>  * hotel deals
>  * travel information
>  * sponsoring opportunities
>
> If you have any questions, feel free to contact me!
>
> -Daniel
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

-- 
https://danielfett.de

--------------LJFTjVV6K0ZxZGYGDIwR99JH
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi everyone,</p>
    <p>as a quick reminder, there's less than a week left to book early
      bird tickets. If you want to submit a session proposal, please do
      so until March 23.</p>
    <p>Thanks,<br>
      Daniel<br>
    </p>
    <div class="moz-cite-prefix">Am 11.02.22 um 22:27 schrieb Daniel
      Fett:<br>
    </div>
    <blockquote type="cite"
      cite="mid:65435b42-3246-a51f-8bfb-eb55374d09da@danielfett.de">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <p>Hi everyone,<br>
        <br>
        I'm pleased to announce that the website for the OAuth Security
        Workshop 2022 is now up: <a moz-do-not-send="true"
          href="https://oauth.secworkshop.events/osw2022"
          class="moz-txt-link-freetext">https://oauth.secworkshop.events/osw2022</a><br>
        <br>
        The three-day event takes place in Trondheim, Norway, from May 4
        to May 6, 2022.<br>
        <br>
        This workshop will *not* be a hybrid event. We might provide
        recordings or a live stream, but to ask questions and partake in
        discussions, on-site participation is required.<br>
        <br>
        Please visit the website for<br>
        <br>
         * tickets - a limited amount of early bird tickets is available
        until no later than March 17<br>
         * the Call for Sessions<br>
         * venue and schedule information<br>
         * hotel deals<br>
         * travel information <br>
         * sponsoring opportunities<br>
        <br>
        If you have any questions, feel free to contact me!<br>
        <br>
        -Daniel<br>
        <br>
      </p>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
OAuth mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OAuth@ietf.org">OAuth@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/oauth">https://www.ietf.org/mailman/listinfo/oauth</a>
</pre>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
<a class="moz-txt-link-freetext" href="https://danielfett.de">https://danielfett.de</a></pre>
  </body>
</html>

--------------LJFTjVV6K0ZxZGYGDIwR99JH--


From nobody Sat Mar 12 23:51:40 2022
Return-Path: <do_not_reply@mnot.net>
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 3366D3A0D61 for <txauth@ietfa.amsl.com>; Sat, 12 Mar 2022 23:51:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level: 
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=mnot.net header.b=h6kreIYv; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=RgBJF3Rl
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 PqjbJPB5YKvY for <txauth@ietfa.amsl.com>; Sat, 12 Mar 2022 23:51:16 -0800 (PST)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B3843A0D5A for <txauth@ietf.org>; Sat, 12 Mar 2022 23:51:16 -0800 (PST)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 288663200E5D for <txauth@ietf.org>; Sun, 13 Mar 2022 03:39:21 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Sun, 13 Mar 2022 03:39:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-type:date:from:from:in-reply-to:mime-version:reply-to :sender:subject:subject:to:to; s=fm2; bh=MgXyVjKxhIMKpDkbRFdyvmK hj1reFj3tSGzRwVXkugc=; b=h6kreIYvpKoUim485/pKaVM/qBYqQPW02GeNuHt pI9uTzCAj1ggl/rqYycexRwiWCga8N65QzG33VLOk4Yfn0K++Aab5g5hp/JsMVaR PsUMmrtS5VT4Urd0OIRFidl1ERNkPD2GLX/9CEpGm72nIUNznfitTG7cLykA70+7 8uCWR4KQgcxAoMJ1caddwjLPnKUo3WHrCxXBpiLgT/TikLGjW5Ec8oDc2oSNSeKW 7Qc9FIW6SeJAZ82c5n3AvhnvbG6h71v8ORGsg26BiXR53n8FzNI6BStClnlLTz5F GOaCsTh+EVKeEQlkfxXV/4lt6u7x89FRwrUDqsUmuKZwx1g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:from :in-reply-to:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=MgXyVjKxhIMKpDkbRFdyvmKhj1reFj3tSGzRwVXkugc=; b=RgBJF3Rl L52QBK0Au6MYhQz2Vwx+bmtY1sMyNvevWYRke6alCE3wl5JAsSngTWLMrhAujXdl 4S/8S9xclWd038tFRIutJBTobQeZ3OSwCQbHlVExUts6qVCUGy66ux7MdE6UEULg 3FyJ2eb5w3Ocg4rBWxpKDtwtHY3wyT3Y+ChLiPIt9BH82wJ0vrDjitSR74JhNUAM mzn6AUEguKNFV3+oF+kTXyoHlolxaFn3YD7nEIx56QS231wNKa3nT/JXyGYUeiFt zN4V6sOTPzuDeaHQ3IEFLA3XNMSFvVB8j8NG2trEJ5aerYlaTMmRCRT1m/o/cRcm 777MvN55t9MYxg==
X-ME-Sender: <xms:qJ8tYv28TQDUMqrRResqJu_yU5gvOOtsWF8DNQpACFT3VI9-SnxHlQ> <xme:qJ8tYuHhFuDS479QNJqi2s3SKPoAx8h5OESCUgM71Yult3PLGyn3G42XnQfqOT8AI PeMIkuK3I7rgnR82g>
X-ME-Received: <xmr:qJ8tYv6qekkZH3xnJoVOsN9Z5RbDmjVTt2Dvi1n8w7S9_aQg3JquLObo1rbiQni2xhueDaLn3_H1zE2BzRuRyK34H4Rxz4sE9sYtAQ0np5Z9KEDrQYNKX_PKFSQMUrJRVPU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddvhedguddtlecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:qJ8tYk1u5qndmlG6Fz7ikoZAjZCXX3rqzLTjScf1dj9zGTBihhSRFA> <xmx:qJ8tYiHpdQ8l0E_BnH-6xLI-yQ7FLCiNyvGs-4L9USbzZjRzL1ef-g> <xmx:qJ8tYl-F-o1_yQExjitCe7C0eZnBO6mRwnN37GXd68n2oTjtTyODBQ> <xmx:qJ8tYnSZjiflvWyOQBZdYvXAIkwltOFfIG0bEyb66X-2RDI1sKgt2Q>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <txauth@ietf.org>; Sun, 13 Mar 2022 03:39:20 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============6104669995611165880=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20220313075116.9B3843A0D5A@ietfa.amsl.com>
Date: Sat, 12 Mar 2022 23:51:16 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/AuxL83FcfYRJEdR62B-hf9IhAjs>
Subject: [GNAP] Weekly github digest (GNAP Weekly GitHub Activity Summary)
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 13 Mar 2022 07:51:22 -0000

--===============6104669995611165880==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* ietf-wg-gnap/gnap-resource-servers (+0/-0/=F0=9F=92=AC3)
  3 issues received 3 new comments:
  - #41 In section 3.4,  "token_format_required" should be changed into"tok=
en_formats_supported" (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/41=20
  - #15 Propose an access token model (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/15=20
  - #12 More precision in Abstract (1 by fimbault)
    https://github.com/ietf-wg-gnap/gnap-resource-servers/issues/12=20



Pull requests
-------------
* ietf-wg-gnap/core-protocol (+1/-1/=F0=9F=92=AC1)
  1 pull requests submitted:
  - Prepare and release -09 (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/414=20

  1 pull requests received 1 new comments:
  - #414 Prepare and release -09 (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/414 [Editorial]=
=20

  1 pull requests merged:
  - Prepare and release -09
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/414 [Editorial]=
=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-gnap/core-protocol
* https://github.com/ietf-wg-gnap/gnap-resource-servers

--===============6104669995611165880==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (GNAP Weekly GitHub Activity Summary)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday March 13, 2022</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>ietf-wg-gnap/gnap-resource-servers (+0/-0/=F0=9F=92=AC3)</h3>

  <p>3 issues received 3 new comments:</p>
  <ul>
  <li>#41 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/41">In section 3.4,  &quot;token_format_required&quot; should be cha=
nged into&quot;token_formats_supported&quot;</a> (1 by fimbault) </li>
 =20
  <li>#15 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/15">Propose an access token model</a> (1 by fimbault) </li>
 =20
  <li>#12 <a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers/=
issues/12">More precision in Abstract</a> (1 by fimbault) </li>
  </ul>




<h2>Pull requests</h2>
<h3>ietf-wg-gnap/core-protocol (+1/-1/=F0=9F=92=AC1)</h3>
  <p class=3D"new">1 pull requests submitted:</p>
  <ul>
  <li>#414 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/414">Prepare and release -09</a> (by jricher) </li>
  </ul>

  <p>1 pull requests received 1 new comments:</p>
  <ul>
  <li>#414 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/414">Prepare and release -09</a> (1 by netlify) <span class=3D"label" st=
yle=3D"background-color: #bfd4f2; color: #000000">Editorial</span> </li>
  </ul>

  <p>1 pull requests merged:</p>
  <ul>
  <li>#414 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/414">Prepare and release -09</a> <span class=3D"label" style=3D"backgrou=
nd-color: #bfd4f2; color: #">Editorial</span> </li>
  </ul>


  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-wg-gnap/core-protocol">https://git=
hub.com/ietf-wg-gnap/core-protocol</a></li>
  <li><a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers">htt=
ps://github.com/ietf-wg-gnap/gnap-resource-servers</a></li>
</ul>
</details>
</body>
</html>

--===============6104669995611165880==--


From nobody Sat Mar 19 02:21:18 2022
Return-Path: <jricher@mit.edu>
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 C33873A0D63 for <txauth@ietfa.amsl.com>; Sat, 19 Mar 2022 02:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.72
X-Spam-Level: 
X-Spam-Status: No, score=-1.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 N8zzNYndd7MP for <txauth@ietfa.amsl.com>; Sat, 19 Mar 2022 02:21:13 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B88A3A0D6F for <txauth@ietf.org>; Sat, 19 Mar 2022 02:21:12 -0700 (PDT)
Received: from smtpclient.apple (dhcp-8079.meeting.ietf.org [31.133.128.121]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 22J9L8Hx015560 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <txauth@ietf.org>; Sat, 19 Mar 2022 05:21:10 -0400
From: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_CA28BA7D-A10F-430B-AE08-65BAA6EDEC3E"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Message-Id: <9D0286D7-D9D9-41AA-8ACB-0A40AE997B76@mit.edu>
Date: Sat, 19 Mar 2022 10:21:00 +0100
To: GNAP Mailing List <txauth@ietf.org>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/UMjtJIsTLDB3zZ_uZtWhaW4VIJI>
Subject: [GNAP] IETF 113 Hackathon
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 19 Mar 2022 09:21:15 -0000

--Apple-Mail=_CA28BA7D-A10F-430B-AE08-65BAA6EDEC3E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The IETF 113 Hackathon is underway. Aaron and I are camped out at a =
table working on things, if you=E2=80=99re in town come join us! If =
you=E2=80=99re remote, there=E2=80=99s a space in the IETF Gather where =
we=E2=80=99ll be hanging out as well.

More info on the hackathon wiki:

https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon =
<https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon>

 =E2=80=94 Justin


--Apple-Mail=_CA28BA7D-A10F-430B-AE08-65BAA6EDEC3E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">The =
IETF 113 Hackathon is underway. Aaron and I are camped out at a table =
working on things, if you=E2=80=99re in town come join us! If you=E2=80=99=
re remote, there=E2=80=99s a space in the IETF Gather where we=E2=80=99ll =
be hanging out as well.<div class=3D""><br class=3D""></div><div =
class=3D"">More info on the hackathon wiki:</div><div class=3D""><br =
class=3D""></div><div class=3D""><a =
href=3D"https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon" =
class=3D"">https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon</a></=
div><div class=3D""><br class=3D""></div><div class=3D"">&nbsp;=E2=80=94 =
Justin<br class=3D""><div class=3D"">
<br class=3D""></div></div></body></html>=

--Apple-Mail=_CA28BA7D-A10F-430B-AE08-65BAA6EDEC3E--


From nobody Sun Mar 20 07:01:23 2022
Return-Path: <jricher@mit.edu>
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 876813A0B48 for <txauth@ietfa.amsl.com>; Sun, 20 Mar 2022 07:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.72
X-Spam-Level: 
X-Spam-Status: No, score=-1.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Z1m35mzNsIlb for <txauth@ietfa.amsl.com>; Sun, 20 Mar 2022 07:01:16 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D67F3A0B28 for <txauth@ietf.org>; Sun, 20 Mar 2022 07:01:15 -0700 (PDT)
Received: from smtpclient.apple (dhcp-8079.meeting.ietf.org [31.133.128.121]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 22KE1CYK024001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <txauth@ietf.org>; Sun, 20 Mar 2022 10:01:14 -0400
From: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_744FFF2A-C4C4-4AB6-B79B-20F5BD8C2358"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Sun, 20 Mar 2022 15:01:11 +0100
References: <9D0286D7-D9D9-41AA-8ACB-0A40AE997B76@mit.edu>
To: GNAP Mailing List <txauth@ietf.org>
In-Reply-To: <9D0286D7-D9D9-41AA-8ACB-0A40AE997B76@mit.edu>
Message-Id: <FA7FD3E6-AA2B-4FD6-B6C5-5A7DE627A901@mit.edu>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/LDZwRegPxkSIgMa2JSMBtWC1swc>
Subject: Re: [GNAP] IETF 113 Hackathon
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 14:01:21 -0000

--Apple-Mail=_744FFF2A-C4C4-4AB6-B79B-20F5BD8C2358
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Aaron and I just finished presenting our results from the Hackathon. We =
made some pretty great progress this weekend across a variety of =
platforms. Our presentation is available here, and we=E2=80=99ll be =
giving this as part of the GNAP meeting editors=E2=80=99 update on =
Friday as well.

=
https://github.com/IETF-Hackathon/ietf113-project-presentations/blob/main/=
GNAP%20IETF%20113%20Hackathon.pdf =
<https://github.com/IETF-Hackathon/ietf113-project-presentations/blob/main=
/GNAP%20IETF%20113%20Hackathon.pdf>

If you=E2=80=99re feeling adventurous, we=E2=80=99ve also got two GNAP =
clients and a GNAP AS online for you to play with. The Java web client =
is here, and you can configure this to start a fairly arbitrary GNAP =
Request against an arbitrary AS:

https://gnap-c.herokuapp.com/ <https://gnap-c.herokuapp.com/>

And there=E2=80=99s a browser-only SPA published here:

https://gnap-c.herokuapp.com/spa <https://gnap-c.herokuapp.com/spa>

And the AS is here, and you should be able to point your clients at it:

https://gnap-as.herokuapp.com/ <https://gnap-as.herokuapp.com/>

All of these are hackathon-quality, so they=E2=80=99re pretty breakable =
and the failures are not graceful when they do happen. :)

Hopefully we=E2=80=99ll see many of you on Friday,
 =E2=80=94 Justin

> On Mar 19, 2022, at 10:21 AM, Justin Richer <jricher@mit.edu> wrote:
>=20
> The IETF 113 Hackathon is underway. Aaron and I are camped out at a =
table working on things, if you=E2=80=99re in town come join us! If =
you=E2=80=99re remote, there=E2=80=99s a space in the IETF Gather where =
we=E2=80=99ll be hanging out as well.
>=20
> More info on the hackathon wiki:
>=20
> https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon =
<https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon>
>=20
>  =E2=80=94 Justin
>=20
> --=20
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth


--Apple-Mail=_744FFF2A-C4C4-4AB6-B79B-20F5BD8C2358
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Aaron=
 and I just finished presenting our results from the Hackathon. We made =
some pretty great progress this weekend across a variety of platforms. =
Our presentation is available here, and we=E2=80=99ll be giving this as =
part of the GNAP meeting editors=E2=80=99 update on Friday as well.<div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://github.com/IETF-Hackathon/ietf113-project-presentations/bl=
ob/main/GNAP IETF 113 Hackathon.pdf" =
class=3D"">https://github.com/IETF-Hackathon/ietf113-project-presentations=
/blob/main/GNAP%20IETF%20113%20Hackathon.pdf</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">If you=E2=80=99re feeling adventurous, =
we=E2=80=99ve also got two GNAP clients and a GNAP AS online for you to =
play with. The Java web client is here, and you can configure this to =
start a fairly arbitrary GNAP Request against an arbitrary AS:</div><div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://gnap-c.herokuapp.com/" =
class=3D"">https://gnap-c.herokuapp.com/</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">And there=E2=80=99s a browser-only SPA =
published here:</div><div class=3D""><br class=3D""></div><div =
class=3D""><a href=3D"https://gnap-c.herokuapp.com/spa" =
class=3D"">https://gnap-c.herokuapp.com/spa</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">And the AS is here, and you should be =
able to point your clients at it:</div><div class=3D""><br =
class=3D""></div><div class=3D""><a =
href=3D"https://gnap-as.herokuapp.com/" =
class=3D"">https://gnap-as.herokuapp.com/</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">All of these are hackathon-quality, so =
they=E2=80=99re pretty breakable and the failures are not graceful when =
they do happen. :)</div><div class=3D""><br class=3D""></div><div =
class=3D"">Hopefully we=E2=80=99ll see many of you on Friday,</div><div =
class=3D"">&nbsp;=E2=80=94 Justin<br class=3D""><div class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Mar =
19, 2022, at 10:21 AM, Justin Richer &lt;<a =
href=3D"mailto:jricher@mit.edu" class=3D"">jricher@mit.edu</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">The IETF 113 Hackathon =
is underway. Aaron and I are camped out at a table working on things, if =
you=E2=80=99re in town come join us! If you=E2=80=99re remote, there=E2=80=
=99s a space in the IETF Gather where we=E2=80=99ll be hanging out as =
well.<div class=3D""><br class=3D""></div><div class=3D"">More info on =
the hackathon wiki:</div><div class=3D""><br class=3D""></div><div =
class=3D""><a =
href=3D"https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon" =
class=3D"">https://trac.ietf.org/trac/ietf/meeting/wiki/113hackathon</a></=
div><div class=3D""><br class=3D""></div><div class=3D"">&nbsp;=E2=80=94 =
Justin<br class=3D""><div class=3D"">
<br class=3D""></div></div></div>-- <br class=3D"">TXAuth mailing =
list<br class=3D""><a href=3D"mailto:TXAuth@ietf.org" =
class=3D"">TXAuth@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/txauth<br =
class=3D""></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_744FFF2A-C4C4-4AB6-B79B-20F5BD8C2358--


From nobody Sun Mar 20 07:51:58 2022
Return-Path: <yaronf.ietf@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 1F5A63A0C95 for <txauth@ietfa.amsl.com>; Sun, 20 Mar 2022 07:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level: 
X-Spam-Status: No, score=-2.106 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 wu-V61RyWZYm for <txauth@ietfa.amsl.com>; Sun, 20 Mar 2022 07:51:49 -0700 (PDT)
Received: from mail-wm1-x32a.google.com (mail-wm1-x32a.google.com [IPv6:2a00:1450:4864:20::32a]) (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 988293A0C9C for <txauth@ietf.org>; Sun, 20 Mar 2022 07:51:47 -0700 (PDT)
Received: by mail-wm1-x32a.google.com with SMTP id r190-20020a1c2bc7000000b0038a1013241dso7166930wmr.1 for <txauth@ietf.org>; Sun, 20 Mar 2022 07:51:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=LRtFB7BZIXVqU8L6ntpvodRnTj0HJqGCx+UE8VUvA4A=; b=JzUkeub1SmwW08t/9maiQyjVSlO67TAF0EOwWjBOYPXWddmtjRDY9PY3U+nFiKc2A+ DVVMftXtXZtGYD+HR5rJ0n2B0g6ReWMc7N+HdO0VHMnGoK9cNXin+B9BOxYQ0+v4UsyR 3T7YA/4ygxEjtTFRG6LEsKhTWtpMBXZuL79CcXoRF10Y56xjTs4VN44AjZnDTQwJF3AB vuMG7vTwBXJdVZiMJeB64WyC0IlRttzuJyKbPWNybx3iaU3VdwWzhkuf3Cj+NMCQDsEj mUlhULbO7qTcd9h+fVEzDYeK6s/JpAhNJcDPIsNfTpuHQ+/qbmPt+cCIzPHC/j9F5z4c IpJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=LRtFB7BZIXVqU8L6ntpvodRnTj0HJqGCx+UE8VUvA4A=; b=X6nbKesJwzo/ze26OTmLtD4XhDEme7+CcbKP3WBZ9wIPOKIj1icmzcOex+lH/opDnS sHmdhQ8WgYLSSNwBaGbOX/WOAt49BuKRHphkFC+ZFlIgPZGx+eMit6D9XWUmR3bfSIX7 Lb841q2WB6pLFm9Gu/d3gy199tbIvNT3gTFDaRCi2MBW2rN/qcn7enbpQHfotUoaLMLK UJ4WhTZR562yYSMNxpVHK3fCejDCgfBS+hpya21Vu8d1sktmQ/i4bCSTXgJyeUcCus88 Xq6ypgT1rVQJ3U8Nn63e45LuPsU3WcGr22BqzxU9eSc0j6AutQX9uC6We8jzfisTQQvG L3dQ==
X-Gm-Message-State: AOAM531C17gYT+QhQiOAOKYq7iB3voPtdvukZp794GvoNhAdVSR4piMZ /Z6DLATrP9EGphybaMNP+N4F5ryCCSM=
X-Google-Smtp-Source: ABdhPJz2ZkoX6y+EjBWww7AbjrOhuELN79XndwUPLo8rO0Jwi8ZO7fZ6FvlQzFtVl4OnHs2bCMnLrw==
X-Received: by 2002:a05:600c:378d:b0:38b:e12f:edde with SMTP id o13-20020a05600c378d00b0038be12feddemr15941332wmr.69.1647787905121;  Sun, 20 Mar 2022 07:51:45 -0700 (PDT)
Received: from [192.168.68.104] ([77.125.223.117]) by smtp.gmail.com with ESMTPSA id u11-20020a056000038b00b00203e5c9aa09sm14120830wrf.27.2022.03.20.07.51.44 for <txauth@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 Mar 2022 07:51:44 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.59.22031300
Date: Sun, 20 Mar 2022 16:51:43 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: GNAP Mailing List <txauth@ietf.org>
Message-ID: <D138E63E-7A1A-4102-8922-5B0114116C02@gmail.com>
Thread-Topic: GNAP session agenda
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3730639904_452024451"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/FDu5AJO-uJTwNuuqgOEeSB1cy_M>
Subject: [GNAP] GNAP session agenda
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 20 Mar 2022 14:51:55 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3730639904_452024451
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Hi,

=20

We have just published the agenda for Friday.

=20

March 25, 2022 (all times Vienna local)

=20

10:00-10:10 Chair slides

10:10-10:50 Protocol updates - Editors

10:50-11:10 Hackathon and implementation updates - Editors

11:10-11:20 Future work - Editors

11:20-11:40 Protocol embedding - Justin

11:40-12:00 AOB

=20

See you all there!

=20

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Leif and Yaron

=20


--B_3730639904_452024451
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equiv=3DC=
ontent-Type content=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D=
"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-US link=3D"#0563C1" vlink=3D"#954F72" style=3D'wo=
rd-wrap:break-word'><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt'>We have just published the agenda for Friday.<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Co=
urier New";color:black'>March 25, 2022 (all times Vienna local)<o:p></o:p></=
span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Couri=
er New";color:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span st=
yle=3D'font-size:10.0pt;font-family:"Courier New";color:black'>10:00-10:10 Cha=
ir slides<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Courier New";color:black'>10:10-10:50 Protocol updates - Ed=
itors<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New";color:black'>10:50-11:10 Hackathon and implementat=
ion updates - Editors<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>11:10-11:20 Future wo=
rk - Editors<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Courier New";color:black'>11:20-11:40 Protocol embedding=
 - Justin<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.=
0pt;font-family:"Courier New";color:black'>11:40-12:00 AOB<o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>See you all there!<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&=
nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Leif and Yaron<o:p></o:p></span></p><p class=3DMsoN=
ormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></bod=
y></html>

--B_3730639904_452024451--



From nobody Fri Mar 25 10:03:43 2022
Return-Path: <yaronf.ietf@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 5304D3A1756 for <txauth@ietfa.amsl.com>; Fri, 25 Mar 2022 10:03:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level: 
X-Spam-Status: No, score=-7.106 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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 zHV7Deb16iDh for <txauth@ietfa.amsl.com>; Fri, 25 Mar 2022 10:03:37 -0700 (PDT)
Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 23C403A1750 for <txauth@ietf.org>; Fri, 25 Mar 2022 10:03:37 -0700 (PDT)
Received: by mail-io1-xd2b.google.com with SMTP id d62so9562053iog.13 for <txauth@ietf.org>; Fri, 25 Mar 2022 10:03:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=user-agent:date:subject:from:to:message-id:thread-topic :mime-version; bh=Cw2oBL+MOc3lUwjGpLohf2jdSSPbO/3bKZV/ROoap90=; b=l6y0ZtduZzI5AteQ5XYA6A77Dz4slCt7qQNHBcl8XLHVh3rZ/X/SH9m9c89nFKE733 np/Twd90sIC6Jhzxex5NJ4iFJF8O9CwvS57xQ6cyIXe61Z09YxwDxX7XjSAjPYVZ62tG wVjeM9Wrw5ani+fUCIbL4I71N/jEcRey9iJHkJ6pPKn8l6uGefw1YHhZSDQGF1U+4Ycj O2hgzelPenaZ5mchs+9jGNAbDFI15nBf5+k2Spl+B3EIJkBg7BPL+wo92vgXb5KfVA82 kR0X3ApH41DGullFcyJzNPfWQXVAFQvtqrFhN/yhXzNqyO2kzYTJCA/bmkLhuTOCVBbp 2T1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:mime-version; bh=Cw2oBL+MOc3lUwjGpLohf2jdSSPbO/3bKZV/ROoap90=; b=zowokKU7GXOYE8IiEu9Qhma7aAWwJHPY08ERUpbIadY+AmaFewEKyAU6ASPzc3quF+ CkioTZHjDvbiuQ0NWKYJLcOYOvL4rKblE1EEjQrzjEtG3IhRke5vIl/BV90oCILfFtFE zbTM2UXE4q4QUe3wj7SMYpN7CuXi/V+cVZOpHv8ar/fldwFKJOT9rggS/b4NgJcCmSUc nJo/uim8CyUf5H48RzJKhW/ixbLKtFOUKCt9m40ldV+Woapnafu/t9a2d7hG6P51k+Xo fhEbfik6PcDZCh05+thbK9oobI0FihyA8XIrHugJhrdBqjsltXvYujnSds5hK8hEgdbL VT/Q==
X-Gm-Message-State: AOAM531O+bIcGmBUpsteIIowUA2X0X5OG3hMRZ/8eAbr9QaPOWoh7aHy P/qTpGvfGZQZksrVEeiN3SN7wbplcf4CdA==
X-Google-Smtp-Source: ABdhPJww0jUiT5imevfkhrEllyy9/RHB9kewxhtPoJz9eNY85TOCD0ZakvJbo9aOWAbOchiPEilwiQ==
X-Received: by 2002:a5d:8b47:0:b0:649:a70a:5715 with SMTP id c7-20020a5d8b47000000b00649a70a5715mr6022015iot.5.1648227815796;  Fri, 25 Mar 2022 10:03:35 -0700 (PDT)
Received: from [192.168.68.104] ([77.125.223.117]) by smtp.gmail.com with ESMTPSA id x8-20020a0566022c4800b006464119d985sm3242723iov.43.2022.03.25.10.03.34 for <txauth@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 25 Mar 2022 10:03:34 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/16.59.22031300
Date: Fri, 25 Mar 2022 20:03:31 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: GNAP Mailing List <txauth@ietf.org>
Message-ID: <91565092-4BE1-42F5-BDBC-F6D3F8711545@gmail.com>
Thread-Topic: Minutes of today's meeting
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3731083414_4180101845"
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/VR19jUm6cJ9yacUNdcuVG5XjRaY>
Subject: [GNAP] Minutes of today's meeting
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Mar 2022 17:03:42 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3731083414_4180101845
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Just uploaded, thank you Chris for taking notes!

=20

https://datatracker.ietf.org/meeting/113/materials/minutes-113-gnap-00

=20

And thank you all for a very productive meeting!

=20

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Yaron

=20


--B_3731083414_4180101845
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equiv=3DC=
ontent-Type content=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D=
"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:12.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-US link=3D"#0563C1" vlink=3D"#954F72" style=3D'wo=
rd-wrap:break-word'><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt'>Just uploaded, thank you Chris for taking notes!<o:p></o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><a href=3D"htt=
ps://datatracker.ietf.org/meeting/113/materials/minutes-113-gnap-00">https:/=
/datatracker.ietf.org/meeting/113/materials/minutes-113-gnap-00</a><o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>And thank y=
ou all for a very productive meeting!<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Yaron<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbs=
p;</o:p></span></p></div></body></html>

--B_3731083414_4180101845--



From nobody Sun Mar 27 00:46:08 2022
Return-Path: <do_not_reply@mnot.net>
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 D001A3A0907 for <txauth@ietfa.amsl.com>; Sun, 27 Mar 2022 00:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.707
X-Spam-Level: 
X-Spam-Status: No, score=-1.707 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=mnot.net header.b=NHLmF9pu; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=H43A03R6
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 O6IvZboTSKYM for <txauth@ietfa.amsl.com>; Sun, 27 Mar 2022 00:45:50 -0700 (PDT)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52B583A08F6 for <txauth@ietf.org>; Sun, 27 Mar 2022 00:45:50 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 887943200B25 for <txauth@ietf.org>; Sun, 27 Mar 2022 03:39:37 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 27 Mar 2022 03:39:37 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-type:date:from:from:in-reply-to:mime-version:reply-to :sender:subject:subject:to:to; s=fm2; bh=WQYcyTO5mG8FLkWxo55tIeS ZRnEnv8nlBoyLNgBqHJY=; b=NHLmF9puWtgXSeiIi601dv5YLvISlCRRSsq1QjD Wut2a+vg3jCLBh6wkTjuwM2Hz6yO07bVFHfoNA71h2McRarSa4eNESAw2oHWH92P c5a/zRmAP40rjAxmiWBy1niHEcgma24Grqo7AYzS6LzqKuMm4ypqlxQBK3duUAGs MeJ7GBd0gURHRS73Qw4BQgab0mV79MG+rPILQg/bEIdWvvZH2ZwbmpAjf4dcVe8c bHQpBFD9rTwLGPjfzqrVcFnmmrIJivb3+IXa7UvBsWv9O3R2ZecrnINEkp2b5sqi VeMbY2CHeeUFW5PziNfcPGKBQvSP+pEK1emtC+yH060/WQg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:from :in-reply-to:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=WQYcyTO5mG8FLkWxo55tIeSZRnEnv8nlBoyLNgBqHJY=; b=H43A03R6 zwmYH2OhV2Oi112BFC+BNlMNczkIOzaPrEZgz8O5JvPA2UGnxia6L3KA6z6FNpft mCQxRFq1gvGhatEYZ/+H5YwUOu/BA9NBT/DGZfA3al+Qgow1RWrf4DKcbdFu8TsH qhb+VNOFroEja+bS871e0/wgb430sL7cjryN/QXozA9JZ+BcxRhAxDeVa/jEnnZ5 OWRQgqxf79rdwg1sNm5TqNdIwiWD/4E6++wSQNnpw+kU0lIAVwqaM1stbxvFQl+b tMqv6jE9q2oQSMNPHgRR5JIPaLhxK3ouStz3MunMmRnsMprZS8H0+uA21477Qfda EGNQd1H0vZIRuA==
X-ME-Sender: <xms:uRRAYvZSMbq75NBfJT3b92Kgf30xH9nJg4iCBH36PmYFANoi6XPNhg> <xme:uRRAYuZyR65JAXMjlCbIT_psPBAj58-QHvVWhsD8ZXQAC7n6LeriYnIM7tpkiiv7f o8KO3QfenjVtnf9Kg>
X-ME-Received: <xmr:uRRAYh_oDr2Hg-K6xQdO4dzN9XDGeQSEbM-XtBO2THzmlnrv8G3m8uKaWimIHOrqgc44ogB68216Mf2GimrL0jGNGNVjFU3A6l2eE7ncp0Q5yZC9AZ_18uGF6hEJ-bBL>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudehgedguddtiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:uRRAYlobXAdXSCvx7k9T-aLLNUOR5suZZRbyNwRQZYhY-VmZ_Ba-pw> <xmx:uRRAYqpFBmJRSPuc4ES7Ed7nRp48gdstUlWMOFaKYO_Sz7qCSD9aJw> <xmx:uRRAYrQB4YQ5T4lX1_SOCOZkUDFIS8v6LMBRRTWjg7yUzyL4cqMnlg> <xmx:uRRAYhRK35bDiZJPOPboUovKMzRjOz3RyqiuC3JnenhjPsZFjHjzIQ>
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <txauth@ietf.org>; Sun, 27 Mar 2022 03:39:36 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============6925021312214947790=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: txauth@ietf.org
Message-Id: <20220327074550.52B583A08F6@ietfa.amsl.com>
Date: Sun, 27 Mar 2022 00:45:50 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/kg-XgdJFUM28NUQblicHxNUudB8>
Subject: [GNAP] Weekly github digest (GNAP Weekly GitHub Activity Summary)
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 27 Mar 2022 07:45:55 -0000

--===============6925021312214947790==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* ietf-wg-gnap/core-protocol (+2/-0/=F0=9F=92=AC2)
  2 issues created:
  - Key Proofing Parameters (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/417=20
  - Interaction Timeout (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/416=20

  1 issues received 2 new comments:
  - #417 Key Proofing Parameters (2 by jricher, yaronf)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/issues/417=20



Pull requests
-------------
* ietf-wg-gnap/core-protocol (+1/-0/=F0=9F=92=AC1)
  1 pull requests submitted:
  - add diagram for session attack (by jricher)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/415=20

  1 pull requests received 1 new comments:
  - #415 add diagram for session attack (1 by netlify)
    https://github.com/ietf-wg-gnap/gnap-core-protocol/pull/415=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-gnap/core-protocol
* https://github.com/ietf-wg-gnap/gnap-resource-servers

--===============6925021312214947790==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (GNAP Weekly GitHub Activity Summary)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
details {
	margin-top: 8em;
	}
summary {
	margin-bottom: 1em;
	cursor: pointer;
}
</style>
</head>

<body>
<h1>Sunday March 27, 2022</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>ietf-wg-gnap/core-protocol (+2/-0/=F0=9F=92=AC2)</h3>
  <p class=3D"new">2 issues created:</p>
  <ul>
  <li>#417 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/417">Key Proofing Parameters</a> (by jricher) </li>
 =20
  <li>#416 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/416">Interaction Timeout</a> (by jricher) </li>
  </ul>

  <p>1 issues received 2 new comments:</p>
  <ul>
  <li>#417 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/is=
sues/417">Key Proofing Parameters</a> (2 by jricher, yaronf) </li>
  </ul>




<h2>Pull requests</h2>
<h3>ietf-wg-gnap/core-protocol (+1/-0/=F0=9F=92=AC1)</h3>
  <p class=3D"new">1 pull requests submitted:</p>
  <ul>
  <li>#415 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/415">add diagram for session attack</a> (by jricher) </li>
  </ul>

  <p>1 pull requests received 1 new comments:</p>
  <ul>
  <li>#415 <a href=3D"https://github.com/ietf-wg-gnap/gnap-core-protocol/pu=
ll/415">add diagram for session attack</a> (1 by netlify) </li>
  </ul>



  <details>
    <summary>Repositories tracked by this digest:</summary>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/ietf-wg-gnap/core-protocol">https://git=
hub.com/ietf-wg-gnap/core-protocol</a></li>
  <li><a href=3D"https://github.com/ietf-wg-gnap/gnap-resource-servers">htt=
ps://github.com/ietf-wg-gnap/gnap-resource-servers</a></li>
</ul>
</details>
</body>
</html>

--===============6925021312214947790==--


From nobody Tue Mar 29 08:28:00 2022
Return-Path: <jricher@mit.edu>
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 1E80A3A17B0 for <txauth@ietfa.amsl.com>; Tue, 29 Mar 2022 08:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.72
X-Spam-Level: 
X-Spam-Status: No, score=-1.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.186, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 Ne2nNcO7XXKL for <txauth@ietfa.amsl.com>; Tue, 29 Mar 2022 08:27:55 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8CF73A1533 for <txauth@ietf.org>; Tue, 29 Mar 2022 08:27:54 -0700 (PDT)
Received: from smtpclient.apple (static-71-174-62-56.bstnma.fios.verizon.net [71.174.62.56]) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 22TFRqHc029729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <txauth@ietf.org>; Tue, 29 Mar 2022 11:27:53 -0400
From: Justin Richer <jricher@mit.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D6045DFF-C97B-4164-9463-2A218407E6DD"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
Date: Tue, 29 Mar 2022 11:27:52 -0400
References: <9B662493-2636-41B4-AF00-396D4E09A995@mit.edu>
To: GNAP Mailing List <txauth@ietf.org>
In-Reply-To: <9B662493-2636-41B4-AF00-396D4E09A995@mit.edu>
Message-Id: <9E3AE9F9-6072-4D4F-BC1A-505A80B9F599@mit.edu>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/XI0u9FW9IQ_6D2RVvYQTxSjIQN0>
Subject: Re: [GNAP] Embedding GNAP
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 29 Mar 2022 15:27:59 -0000

--Apple-Mail=_D6045DFF-C97B-4164-9463-2A218407E6DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi everyone,

I presented this topic (as an individual) at the 113 IETF meeting, and =
you can see the slides here:

=
https://datatracker.ietf.org/meeting/113/materials/slides-113-gnap-embeddi=
ng-gnap-00 =
<https://datatracker.ietf.org/meeting/113/materials/slides-113-gnap-embedd=
ing-gnap-00>

During the meeting, there wasn=E2=80=99t really any support for taking =
on this embedding work within the WG. As such, I=E2=80=99m personally =
suspending pushing this idea. If someone else wants to take this up, =
I=E2=80=99m happy to provide background and support.

 =E2=80=94 Justin

> On Feb 9, 2022, at 3:27 PM, Justin Richer <jricher@mit.edu> wrote:
>=20
> Dmitri Z=E2=80=99s presentation at the interim has had me thinking =
about how GNAP connects with other protocols, including other security =
and identity systems. In particular, I think it brings to light two =
different ways of looking at GNAP that have been in the system=E2=80=99s =
design from the beginning but hasn=E2=80=99t gotten a lot of discussion. =
I=E2=80=99m hoping we can start that discussion on this thread. While =
it=E2=80=99s VC=E2=80=99s that spawned this discussion most recently, =
there were also use cases early on about using GNAP for things like =
mid-protocol step-up authentication and interaction.
>=20
> First I want to show the more =E2=80=9Ctraditional=E2=80=9D model that =
allows for a full separation of the security and authorization layer =
from the API. This should be of zero surprise to anyone who=E2=80=99s =
worked with GNAP, OAuth, UMA, or any number of similar systems for many =
years, but I=E2=80=99m including it as a baseline for discussion:
>=20
>=20
>=20
> =
https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1iZWQgR05=
BUCBpbiBQcm90b2NvbCAobmF0aXZlKQoKQ0ktPkZvbzogU3RhcnQgdGhlIEZvbwAhCQpGb28tP=
kNJOiBXV1ctQXV0aDoASQUKb3B0AAMGQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTADAGcwBRBWl=
udGVyYWN0ICJmb28iACQPY29udGludWUAKwlhY2Nlc3MgdG9rZW4vaWRlbnRpdHkvZXRjCmVuZ=
CBvcHQAgSsKRm9vIHAAgU0Idy8ALgwKCg&s=3Ddefault =
<https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1iZWQgR0=
5BUCBpbiBQcm90b2NvbCAobmF0aXZlKQoKQ0ktPkZvbzogU3RhcnQgdGhlIEZvbwAhCQpGb28t=
PkNJOiBXV1ctQXV0aDoASQUKb3B0AAMGQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTADAGcwBRBW=
ludGVyYWN0ICJmb28iACQPY29udGludWUAKwlhY2Nlc3MgdG9rZW4vaWRlbnRpdHkvZXRjCmVu=
ZCBvcHQAgSsKRm9vIHAAgU0Idy8ALgwKCg&s=3Ddefault>
>=20
> Second, we can embed a protocol inside of GNAP. GNAP=E2=80=99s =
=E2=80=9Cinteraction=E2=80=9D mechanism is inherently more flexible much =
of what=E2=80=99s come before, so it=E2=80=99s entirely possible, if =
you=E2=80=99re already doing GNAP, to embed a whole new protocol in the =
middle as part of the interact/continue-grant process, especially if =
it=E2=80=99s dealing with identity and user information.  We can even =
include the =E2=80=9CFoo=E2=80=9D protocol information in our response =
from the AS, and OpenID Connect showed us the power of this by including =
the ID Token assertion alongside the access token of an OAuth response.
>=20
>=20
>=20
> =
https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1iZWQgcHJ=
vdG9jb2wgaW4gR05BUAoKQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTLT5DSTogc3RhcnQgaW50Z=
XJhY3QgImZvbyIKb3B0IFRoZSBGb28gUABKBwpDSTwtPkZvbzogRG8gdAAPDyBpbiBDb250ZXh=
0CkZvbwBWBgBNCWZpbmlzaAplbmQgb3B0AIEDD2NvbnRpbnVlAIEKCWFjY2VzcyB0b2tlbi9pZ=
GVudGl0eS9mb28vZXRjCg&s=3Ddefault =
<https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1iZWQgcH=
JvdG9jb2wgaW4gR05BUAoKQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTLT5DSTogc3RhcnQgaW50=
ZXJhY3QgImZvbyIKb3B0IFRoZSBGb28gUABKBwpDSTwtPkZvbzogRG8gdAAPDyBpbiBDb250ZX=
h0CkZvbwBWBgBNCWZpbmlzaAplbmQgb3B0AIEDD2NvbnRpbnVlAIEKCWFjY2VzcyB0b2tlbi9p=
ZGVudGl0eS9mb28vZXRjCg&s=3Ddefault>
>=20
> This is something I think that would be particularly valuable to use =
VC-API in, since the context of the ongoing grant request adds =
everything that the VC API would need to make its decisions. And =
especially with VC-API, we can provide the ultimate VC generated as part =
of the response from the AS in the last step, in the subject information =
block. This is something I=E2=80=99ve proposed to the VC-API working =
group to take up, but there hasn=E2=80=99t been interest there to date. =
I do think it makes a lot of sense, though.
>=20
> Finally, and this is where Dmitri=E2=80=99s work is heading, is the =
idea that you could embed a portion of GNAP inside of a completely =
separate protocol. The result would be specific to whatever protocol =
you=E2=80=99re using to wrap things, but it could look something like =
this:
>=20
>=20
>=20
> =
https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1iZWQgR05=
BUCBpbiBQcm90b2NvbCAob3B0aW1pemVkKQoKQ0ktPkZvby1BUzogRm9vABwKUmVxdWVzdAoAF=
wYtPkNJOiBlbWJlZGRlZCBncmFudCByZXNwb25zZQpvcHQAYQZzbmlwcGV0AEkNACYGY29udGl=
udWUKQ0k8AGgKaW50ZXJhY3QvABcIL2V0YwAiHGVuZCBvcACBCA5Gb28gcACBVQgAgQsJCg&s=3D=
default =
<https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1iZWQgR0=
5BUCBpbiBQcm90b2NvbCAob3B0aW1pemVkKQoKQ0ktPkZvby1BUzogRm9vABwKUmVxdWVzdAoA=
FwYtPkNJOiBlbWJlZGRlZCBncmFudCByZXNwb25zZQpvcHQAYQZzbmlwcGV0AEkNACYGY29udG=
ludWUKQ0k8AGgKaW50ZXJhY3QvABcIL2V0YwAiHGVuZCBvcACBCA5Gb28gcACBVQgAgQsJCg&s=
=3Ddefault>
>=20
> What I find interesting about this last model is the concept that the =
=E2=80=9CFoo=E2=80=9D API responds with its own wrapped version of the =
GNAP response, including information about accessing a GNAP Grant =
Continuation Endpoint (including access token). The client can =
communicate with whatever endpoints and protocols the Foo-AS needs, but =
importantly they=E2=80=99re all wrapped up in otherwise standard GNAP =
=E2=80=9Cinteraction=E2=80=9D hooks. And finally, at some point, the =
client makes a =E2=80=9Cgrant continuation=E2=80=9D call but instead of =
getting back a GNAP response, it gets back the Foo response it asked for =
back in step 1.
>=20
> Now, this is weird for a lot of reasons, and it certainly is not GNAP, =
not really anyway. So it=E2=80=99s not for this WG to decide what this =
would look like for every protocol =E2=80=94 but my question to this =
group is twofold: do we want to write guidance about how to do this kind =
of embedding? Is the proposed VC-API work a good candidate for this kind =
of thing with a concrete protocol?
>=20
>  =E2=80=94 Justin
> --=20
> TXAuth mailing list
> TXAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/txauth


--Apple-Mail=_D6045DFF-C97B-4164-9463-2A218407E6DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi =
everyone,<div class=3D""><br class=3D""></div><div class=3D"">I =
presented this topic (as an individual) at the 113 IETF meeting, and you =
can see the slides here:</div><div class=3D""><br class=3D""></div><div =
class=3D""><a =
href=3D"https://datatracker.ietf.org/meeting/113/materials/slides-113-gnap=
-embedding-gnap-00" =
class=3D"">https://datatracker.ietf.org/meeting/113/materials/slides-113-g=
nap-embedding-gnap-00</a></div><div class=3D""><br class=3D""></div><div =
class=3D"">During the meeting, there wasn=E2=80=99t really any support =
for taking on this embedding work within the WG. As such, I=E2=80=99m =
personally suspending pushing this idea. If someone else wants to take =
this up, I=E2=80=99m happy to provide background and support.</div><div =
class=3D""><br class=3D""></div><div class=3D"">&nbsp;=E2=80=94 =
Justin<br class=3D""><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Feb 9, 2022, at 3:27 PM, Justin Richer =
&lt;<a href=3D"mailto:jricher@mit.edu" class=3D"">jricher@mit.edu</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">Dmitri Z=E2=80=99s =
presentation at the interim has had me thinking about how GNAP connects =
with other protocols, including other security and identity systems. In =
particular, I think it brings to light two different ways of looking at =
GNAP that have been in the system=E2=80=99s design from the beginning =
but hasn=E2=80=99t gotten a lot of discussion. I=E2=80=99m hoping we can =
start that discussion on this thread. While it=E2=80=99s VC=E2=80=99s =
that spawned this discussion most recently, there were also use cases =
early on about using GNAP for things like mid-protocol step-up =
authentication and interaction.<br class=3D""><div class=3D""><br =
class=3D""></div><div class=3D"">First I want to show the more =
=E2=80=9Ctraditional=E2=80=9D model that allows for a full separation of =
the security and authorization layer from the API. This should be of =
zero surprise to anyone who=E2=80=99s worked with GNAP, OAuth, UMA, or =
any number of similar systems for many years, but I=E2=80=99m including =
it as a baseline for discussion:</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><img =
src=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1i=
ZWQgR05BUCBpbiBQcm90b2NvbCAobmF0aXZlKQoKQ0ktPkZvbzogU3RhcnQgdGhlIEZvbwAhCQ=
pGb28tPkNJOiBXV1ctQXV0aDoASQUKb3B0AAMGQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTADAG=
cwBRBWludGVyYWN0ICJmb28iACQPY29udGludWUAKwlhY2Nlc3MgdG9rZW4vaWRlbnRpdHkvZX=
RjCmVuZCBvcHQAgSsKRm9vIHAAgU0Idy8ALgwKCg&amp;s=3Ddefault" =
alt=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1i=
ZWQgR05BUCBpbiBQcm90b2NvbCAobmF0aXZlKQoKQ0ktPkZvbzogU3RhcnQgdGhlIEZvbwAhCQ=
pGb28tPkNJOiBXV1ctQXV0aDoASQUKb3B0AAMGQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTADAG=
cwBRBWludGVyYWN0ICJmb28iACQPY29udGludWUAKwlhY2Nlc3MgdG9rZW4vaWRlbnRpdHkvZX=
RjCmVuZCBvcHQAgSsKRm9vIHAAgU0Idy8ALgwKCg&amp;s=3Ddefault" =
class=3D""></div><div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1=
iZWQgR05BUCBpbiBQcm90b2NvbCAobmF0aXZlKQoKQ0ktPkZvbzogU3RhcnQgdGhlIEZvbwAhC=
QpGb28tPkNJOiBXV1ctQXV0aDoASQUKb3B0AAMGQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTADA=
GcwBRBWludGVyYWN0ICJmb28iACQPY29udGludWUAKwlhY2Nlc3MgdG9rZW4vaWRlbnRpdHkvZ=
XRjCmVuZCBvcHQAgSsKRm9vIHAAgU0Idy8ALgwKCg&amp;s=3Ddefault" =
class=3D"">https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUg=
RW1iZWQgR05BUCBpbiBQcm90b2NvbCAobmF0aXZlKQoKQ0ktPkZvbzogU3RhcnQgdGhlIEZvbw=
AhCQpGb28tPkNJOiBXV1ctQXV0aDoASQUKb3B0AAMGQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFT=
ADAGcwBRBWludGVyYWN0ICJmb28iACQPY29udGludWUAKwlhY2Nlc3MgdG9rZW4vaWRlbnRpdH=
kvZXRjCmVuZCBvcHQAgSsKRm9vIHAAgU0Idy8ALgwKCg&amp;s=3Ddefault</a></div></di=
v><div class=3D""><br class=3D""></div><div class=3D"">Second, we can =
embed a protocol inside of GNAP. GNAP=E2=80=99s =E2=80=9Cinteraction=E2=80=
=9D mechanism is inherently more flexible much of what=E2=80=99s come =
before, so it=E2=80=99s entirely possible, if you=E2=80=99re already =
doing GNAP, to embed a whole new protocol in the middle as part of the =
interact/continue-grant process, especially if it=E2=80=99s dealing with =
identity and user information. &nbsp;We can even include the =E2=80=9CFoo=E2=
=80=9D protocol information in our response from the AS, and OpenID =
Connect showed us the power of this by including the ID Token assertion =
alongside the access token of an OAuth response.</div><div class=3D""><br =
class=3D""></div><div class=3D""><img =
src=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1i=
ZWQgcHJvdG9jb2wgaW4gR05BUAoKQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTLT5DSTogc3Rhcn=
QgaW50ZXJhY3QgImZvbyIKb3B0IFRoZSBGb28gUABKBwpDSTwtPkZvbzogRG8gdAAPDyBpbiBD=
b250ZXh0CkZvbwBWBgBNCWZpbmlzaAplbmQgb3B0AIEDD2NvbnRpbnVlAIEKCWFjY2VzcyB0b2=
tlbi9pZGVudGl0eS9mb28vZXRjCg&amp;s=3Ddefault" =
alt=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1i=
ZWQgcHJvdG9jb2wgaW4gR05BUAoKQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTLT5DSTogc3Rhcn=
QgaW50ZXJhY3QgImZvbyIKb3B0IFRoZSBGb28gUABKBwpDSTwtPkZvbzogRG8gdAAPDyBpbiBD=
b250ZXh0CkZvbwBWBgBNCWZpbmlzaAplbmQgb3B0AIEDD2NvbnRpbnVlAIEKCWFjY2VzcyB0b2=
tlbi9pZGVudGl0eS9mb28vZXRjCg&amp;s=3Ddefault" class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1=
iZWQgcHJvdG9jb2wgaW4gR05BUAoKQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTLT5DSTogc3Rhc=
nQgaW50ZXJhY3QgImZvbyIKb3B0IFRoZSBGb28gUABKBwpDSTwtPkZvbzogRG8gdAAPDyBpbiB=
Db250ZXh0CkZvbwBWBgBNCWZpbmlzaAplbmQgb3B0AIEDD2NvbnRpbnVlAIEKCWFjY2VzcyB0b=
2tlbi9pZGVudGl0eS9mb28vZXRjCg&amp;s=3Ddefault" =
class=3D"">https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUg=
RW1iZWQgcHJvdG9jb2wgaW4gR05BUAoKQ0ktPkFTOiBncmFudCByZXF1ZXN0CkFTLT5DSTogc3=
RhcnQgaW50ZXJhY3QgImZvbyIKb3B0IFRoZSBGb28gUABKBwpDSTwtPkZvbzogRG8gdAAPDyBp=
biBDb250ZXh0CkZvbwBWBgBNCWZpbmlzaAplbmQgb3B0AIEDD2NvbnRpbnVlAIEKCWFjY2Vzcy=
B0b2tlbi9pZGVudGl0eS9mb28vZXRjCg&amp;s=3Ddefault</a></div><div =
class=3D""><br class=3D""></div><div class=3D"">This is something I =
think that would be particularly valuable to use VC-API in, since the =
context of the ongoing grant request adds everything that the VC API =
would need to make its decisions. And especially with VC-API, we can =
provide the ultimate VC generated as part of the response from the AS in =
the last step, in the subject information block. This is something =
I=E2=80=99ve proposed to the VC-API working group to take up, but there =
hasn=E2=80=99t been interest there to date. I do think it makes a lot of =
sense, though.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Finally, and this is where Dmitri=E2=80=99s work is heading, =
is the idea that you could embed a portion of GNAP inside of a =
completely separate protocol. The result would be specific to whatever =
protocol you=E2=80=99re using to wrap things, but it could look =
something like this:</div><div class=3D""><br class=3D""></div><div =
class=3D""><img =
src=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1i=
ZWQgR05BUCBpbiBQcm90b2NvbCAob3B0aW1pemVkKQoKQ0ktPkZvby1BUzogRm9vABwKUmVxdW=
VzdAoAFwYtPkNJOiBlbWJlZGRlZCBncmFudCByZXNwb25zZQpvcHQAYQZzbmlwcGV0AEkNACYG=
Y29udGludWUKQ0k8AGgKaW50ZXJhY3QvABcIL2V0YwAiHGVuZCBvcACBCA5Gb28gcACBVQgAgQ=
sJCg&amp;s=3Ddefault" =
alt=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1i=
ZWQgR05BUCBpbiBQcm90b2NvbCAob3B0aW1pemVkKQoKQ0ktPkZvby1BUzogRm9vABwKUmVxdW=
VzdAoAFwYtPkNJOiBlbWJlZGRlZCBncmFudCByZXNwb25zZQpvcHQAYQZzbmlwcGV0AEkNACYG=
Y29udGludWUKQ0k8AGgKaW50ZXJhY3QvABcIL2V0YwAiHGVuZCBvcACBCA5Gb28gcACBVQgAgQ=
sJCg&amp;s=3Ddefault" class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D""><a =
href=3D"https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUgRW1=
iZWQgR05BUCBpbiBQcm90b2NvbCAob3B0aW1pemVkKQoKQ0ktPkZvby1BUzogRm9vABwKUmVxd=
WVzdAoAFwYtPkNJOiBlbWJlZGRlZCBncmFudCByZXNwb25zZQpvcHQAYQZzbmlwcGV0AEkNACY=
GY29udGludWUKQ0k8AGgKaW50ZXJhY3QvABcIL2V0YwAiHGVuZCBvcACBCA5Gb28gcACBVQgAg=
QsJCg&amp;s=3Ddefault" =
class=3D"">https://www.websequencediagrams.com/cgi-bin/cdraw?lz=3DdGl0bGUg=
RW1iZWQgR05BUCBpbiBQcm90b2NvbCAob3B0aW1pemVkKQoKQ0ktPkZvby1BUzogRm9vABwKUm=
VxdWVzdAoAFwYtPkNJOiBlbWJlZGRlZCBncmFudCByZXNwb25zZQpvcHQAYQZzbmlwcGV0AEkN=
ACYGY29udGludWUKQ0k8AGgKaW50ZXJhY3QvABcIL2V0YwAiHGVuZCBvcACBCA5Gb28gcACBVQ=
gAgQsJCg&amp;s=3Ddefault</a></div><div class=3D""><br =
class=3D""></div><div class=3D"">What I find interesting about this last =
model is the concept that the =E2=80=9CFoo=E2=80=9D API responds with =
its own wrapped version of the GNAP response, including information =
about accessing a GNAP Grant Continuation Endpoint (including access =
token). The client can communicate with whatever endpoints and protocols =
the Foo-AS needs, but importantly they=E2=80=99re all wrapped up in =
otherwise standard GNAP =E2=80=9Cinteraction=E2=80=9D hooks. And =
finally, at some point, the client makes a =E2=80=9Cgrant =
continuation=E2=80=9D call but instead of getting back a GNAP response, =
it gets back the Foo response it asked for back in step 1.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Now, this is weird for a =
lot of reasons, and it certainly is not GNAP, not really anyway. So =
it=E2=80=99s not for this WG to decide what this would look like for =
every protocol =E2=80=94 but my question to this group is twofold: do we =
want to write guidance about how to do this kind of embedding? Is the =
proposed VC-API work a good candidate for this kind of thing with a =
concrete protocol?</div><div class=3D""><br class=3D""></div><div =
class=3D"">&nbsp;=E2=80=94 Justin</div></div>-- <br class=3D"">TXAuth =
mailing list<br class=3D""><a href=3D"mailto:TXAuth@ietf.org" =
class=3D"">TXAuth@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/txauth<br =
class=3D""></div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_D6045DFF-C97B-4164-9463-2A218407E6DD--

