Re: [GNAP] Design team formed

Justin Richer <> Wed, 12 August 2020 16:05 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0E8913A120C for <>; Wed, 12 Aug 2020 09:05:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qduW6-_D38ON for <>; Wed, 12 Aug 2020 09:05:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0C75A3A1156 for <>; Wed, 12 Aug 2020 09:05:15 -0700 (PDT)
Received: from [] ( []) (authenticated bits=0) (User authenticated as jricher@ATHENA.MIT.EDU) by (8.14.7/8.12.4) with ESMTP id 07CG5Cp8024691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 12 Aug 2020 12:05:13 -0400
From: Justin Richer <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C43FB935-AE6E-424B-A0B5-FBDAD95C3493"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Wed, 12 Aug 2020 12:05:12 -0400
In-Reply-To: <>
Cc: Yaron Sheffer <>, GNAP Mailing List <>
To: Francis Pouatcha <>
References: <> <> <> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [GNAP] Design team formed
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 12 Aug 2020 16:05:18 -0000

The goal of the design team is to take a step aside from the public mailing list and, hopefully, get more done in a short time period. Discussion on a public mailing list is powerful, but slow and prone to derailing and miscommunication. The design team will discuss things more directly to avoid those problems in the short term, much the way that a small subcommittee can bring targeted expertise to a group’s problem by using higher bandwidth communication channels and regular interaction. The results will be brought back to the list to be discussed and, hopefully, adopted as a starting point. That starting point document will then be debated, edited, and refined by the working group. Nothing in the starting document is sacred, but at least it will be something concrete to build on.

While the design team is working, discussion will continue on the list, and all the design team members are still participating on the list. This ongoing conversation is still very valuable for the group as a whole, including the design team, even if it’s not a direct feed of the design team’s discussions. 

There are a LOT of amazing people in this group — I see that as a testament to how important this problem space is and how much of an appetite there is for solving things in that space. This process is going to take a while, maybe years of debate and engineering before we reach a final standard. There is going to be a lot of opportunity to contribute, and I look forward to your continuing contributions.

The IETF has this writeup on the nature and utility of design teams, which you might find useful: <>

 — Justin

> On Aug 12, 2020, at 11:31 AM, Francis Pouatcha <> wrote:
> Justin,
> Thanks for your response. I hope the design team will keep addressing essential topics on the list so we can contribute.
> Best regards.
> /Francis
> On Wed, Aug 12, 2020 at 11:24 AM Justin Richer < <>> wrote:
> Francis,
> The design team is just a temporary construct to get things started here, and it will dissolve back into the WG when the task is over. I, for one, am really thankful to have you bring your experience to this working group. I’ve appreciated your contributions greatly so far, and I look forward to continuing to work with you.
> We still have a long way to go and a lot of work to do. The output of the design team is just the start of the working group, and there are many more things to figure out.
>  — Justin
>> On Aug 11, 2020, at 1:25 PM, Francis Pouatcha < <>> wrote:
>> It is unfortunate I didn't make it. Would have liked to bring in my 22 years of experience in building authz applications.
>> Best regards.
>> /Francis
>> On Tue, Aug 11, 2020 at 6:43 AM Yaron Sheffer < <>> wrote:
>> Thank you all for attending the inaugural GNAP meeting at IETF-108. We had quite a few volunteers, and the chairs picked the following people for the design team:
>> * Kathleen Moriarty
>> * Justin Richer
>> * Dick Hardt
>> * Mike Jones
>> * Fabien Imbault
>> Kathleen has graciously agreed to convene the sessions and report on the team's outcome. Thank you all who volunteered!
>> We expect the design team to decide on a solution outline that combines the best of both proposals, and present this outline by Sep. 15. Anything is as usual subject to approval by the whole working group.
>> Thanks,
>>         Leif and Yaron
>> -- 
>> TXAuth mailing list
>> <>
>> <>
>> -- 
>> Francis Pouatcha
>> Co-Founder and Technical Lead
>> adorsys GmbH & Co. KG
>> <>-- 
>> TXAuth mailing list
>> <>
>> <>
> -- 
> Francis Pouatcha
> Co-Founder and Technical Lead
> adorsys GmbH & Co. KG
> <>