Re: [GNAP] Editors Update

Yaron Sheffer <> Sat, 26 February 2022 18:34 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ABF253A0B38 for <>; Sat, 26 Feb 2022 10:34:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.106
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3W9oeYqrxx7J for <>; Sat, 26 Feb 2022 10:33:58 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::434]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5E33C3A0B3C for <>; Sat, 26 Feb 2022 10:32:31 -0800 (PST)
Received: by with SMTP id v21so9228054wrv.5 for <>; Sat, 26 Feb 2022 10:32:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version; bh=/s+AoahfEsTDATRH2vSrjuYNtAD9Ods3k6dDr3O+plA=; b=BXha4BrPWxDIriktHgrjYIIjeEAZJRfTmskHiImX1aNYpG5vo5jiD+79fI44DUoVo8 BjYcpIHjBxiZsen9/P/g1f5jgSf837yoI3GOBA4rE23oGuJlT30jwCnEmI9nL+nvgMRV GnrO6vc7piSZzDur0LU0ErJPDIp/b+Lxq9BqYvsS9BEhEME7uEDan2GWd1bimj0Df6dg vPEPAopCFOSoRfgJ8+OwRLnc3bMG1ngixSmVwV1vQpeTQA9hpzvC7Aj20FkL7p9Wfh8c SxKD1ykIqcR1E2W1lCdQHqkWgjtatTLWBhWCREIr2+i0XuIE4c5OEvBgK5Z9LL1HqBOT xlXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version; bh=/s+AoahfEsTDATRH2vSrjuYNtAD9Ods3k6dDr3O+plA=; b=NdUdSeib6K1kGs5evjEN3QsKZS+eViG0Qe/KBm9uehNtzptI4WWryB6M1wmzsaHAxA 4RPv6m8MyQTGxi7pvEiVxfXeXbdC3hASso364TmmgOUVdWis1Jc1iJ8gE5zgFudTkT7M Vj0cCOD2bQRlVm/IPGylWwzPPsFhXN9c8BRvej6DoSuzaqbGu3ZEKxNA0rWLm04jy/Jx j/kWUfQ4A32F2ue7vUIZHFXi04AnlP/Uxyprxzhv70WyihqNcgWOV6cm+o5EamoZbBhZ lvPg9kVZ4o5T7IoyvBOf/XVtmyTLQllkBaX5h0tLGgDuDW7SLhbnh9hZgJe1FUuT5f5J 3HfA==
X-Gm-Message-State: AOAM5322B8l61P98xkEfGFiiCUjzpIZ76q32hPCmQYQTH9wJX06MlWtV GTBg5QFBdeXVw3NiBEfLeK8ofTzp56I=
X-Google-Smtp-Source: ABdhPJyl9/cmxnHP6dN41MyvpQF23VPjeRwgMTLfLhOrF3w32AXHrYb1xIJGL+e1Vi4Z8AD5oEp8ZA==
X-Received: by 2002:adf:ba4b:0:b0:1ed:9dff:4f5e with SMTP id t11-20020adfba4b000000b001ed9dff4f5emr10295091wrg.637.1645900349149; Sat, 26 Feb 2022 10:32:29 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id k10-20020adfe3ca000000b001e3894ee3aasm5486495wrm.98.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 Feb 2022 10:32:28 -0800 (PST)
User-Agent: Microsoft-MacOutlook/16.58.22021501
Date: Sat, 26 Feb 2022 20:32:27 +0200
From: Yaron Sheffer <>
To: Justin Richer <>, GNAP Mailing List <>
Message-ID: <>
Thread-Topic: [GNAP] Editors Update
References: <>
In-Reply-To: <>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3728752347_353659245"
Archived-At: <>
Subject: Re: [GNAP] Editors Update
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: GNAP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 26 Feb 2022 18:34:03 -0000

Thanks editors.


I would like to encourage the editorial team to stabilize the protocol by defining must-implement mechanisms where it makes sense. 


In my opinion, we should consider a single MTI for:

Key formats
Key proof of possession (a.k.a.) message signatures.

But maybe also for:
Start interaction modes
Finish interaction modes

Eventually the market will decide. But at this stage of the protocol’s development, we should narrow the field somewhat to enable interoperability between minimal Client and minimal AS implementations.





From: TXAuth <> on behalf of Justin Richer <>
Date: Thursday, February 24, 2022 at 02:39
To: GNAP Mailing List <>
Subject: [GNAP] Editors Update


Ahead of the IETF113 meeting, the editors have been working hard at putting together a set of targeted changes for a new revision. There are currently 13 pull requests tagged for inclusion in one week. Please review these and comment as you find things that need to be improved. Some of these are relatively minor syntax changes, some are mostly editorial, and some add or call out requirements where previously they had been implied. We know there’s a lot to cover here, but please take a look when you can.


Harmonize URL/URI


Assertions as array


Data URI for logo


Strengthened normative requirements for continue timeout


Redefine user code interaction methods


Clarified user presence on interaction finish methods


Specify the content type for Discovery’s endpoint response (thanks, Andrii!)


New 7.1.2 section on key protection


Consistent formatting of parameter lists


Cleanup issue 43




Rename overall diagram



Plus one tagged editorial:


Minor edits (thanks, Yaron!)



These will stay open for comment for one week from today. The editors intend to create a new draft based on acceptance of all of these PRs, ahead of the deadlines for IETF113.


Thanks, and we hope to see you there!


 — Justin, Aaron, and Fabien



-- TXAuth mailing list