[Txauth] AD review of post IETF 107 charter for TXAuth

Roman Danyliw <rdd@cert.org> Thu, 30 April 2020 19:52 UTC

Return-Path: <rdd@cert.org>
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 98FBB3A126D for <txauth@ietfa.amsl.com>; Thu, 30 Apr 2020 12:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, SPF_HELO_NONE=0.001, SPF_PASS=-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=cert.org
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 ED-nczwR0MGn for <txauth@ietfa.amsl.com>; Thu, 30 Apr 2020 12:52:29 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 CD3293A125C for <txauth@ietf.org>; Thu, 30 Apr 2020 12:52:28 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 03UJqR1C032233 for <txauth@ietf.org>; Thu, 30 Apr 2020 15:52:27 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 03UJqR1C032233
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1588276347; bh=DOUPJO9Ttkl6W4f5JWyf4ErkZ5K+yiJ7ByKQRSeB4Nw=; h=From:To:Subject:Date:From; b=KBSIVfD0x+dTZ0ErDA3pNvIUcO9WKfagz0vDEUPUNbAs6ed3O5P5UNuaAXW9AWZbr qL7dojYPjo5hPnK+YfkrjJBK5xiKG6hICUduB7pamoVr2BKiwIh5F/OWARvdo14kqQ ZxlharWOXrvh8229dU02aHAY+W9F0Wfe0QZf8a9s=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 03UJqHZA009614 for <txauth@ietf.org>; Thu, 30 Apr 2020 15:52:22 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by CASCADE.ad.sei.cmu.edu (10.64.28.248) with Microsoft SMTP Server (TLS) id 14.3.487.0; Thu, 30 Apr 2020 15:52:17 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MORRIS.ad.sei.cmu.edu (147.72.252.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1847.3; Thu, 30 Apr 2020 15:52:17 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%22]) with mapi id 15.01.1847.007; Thu, 30 Apr 2020 15:52:17 -0400
From: Roman Danyliw <rdd@cert.org>
To: "txauth@ietf.org" <txauth@ietf.org>
Thread-Topic: AD review of post IETF 107 charter for TXAuth
Thread-Index: AdYfIwxSTEVM1mO0SouIA0SK25TKyQ==
Date: Thu, 30 Apr 2020 19:52:16 +0000
Message-ID: <e455ccfc21a547688d71d3f7b41da4bb@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.203.39]
Content-Type: multipart/alternative; boundary="_000_e455ccfc21a547688d71d3f7b41da4bbcertorg_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/txauth/dPakK9hedhmq7CQgBAa8WOSXZAI>
Subject: [Txauth] AD review of post IETF 107 charter for TXAuth
X-BeenThere: txauth@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <txauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/txauth>, <mailto:txauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/txauth/>
List-Post: <mailto:txauth@ietf.org>
List-Help: <mailto:txauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/txauth>, <mailto:txauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Apr 2020 19:52:41 -0000

Hi!

Coming out of the discussion at the virtual IETF 107 meeting [2], these items of feedback were identified with the proposed charter [1]:

==[ snip from the minutes [2] ]==
  * what use cases? what parts of OpenID?
  * what is meant by identity?
  * what is being done by reference, what is being invented?
  * is session management in scope?
==[ snip ]==

Subsequent updates to the charter appear to address this feedback.  The latest version being 00-04 [3].  The diff from the pre-IETF consensus call version [1] and this new version [3] can be reviewed at [4].

We already got a sense of interest from the first consensus call [5].  I see there is a discussion about exploring a new name.  Let's let that finish, but not run too long before proceeding for an initial IESG review.

Regards,
Roman

PS, if you're wondering why there are so many version of the charter now in the datatracker, I had some difficulties uploading the text.  I thought my submission were not being accepted when I got an error, but in fact they were.  The legend for the datatracker charter versions is:

00-00 = pre IETF 107 consensus call
00-01, 02, 03 = Dick+Yaron's post IETF 107 edits from https://mailarchive.ietf.org/arch/msg/txauth/UgGztdOx0lR9NvzBgmp8OMelABw/
00-04 = Justin's edits from https://mailarchive.ietf.org/arch/msg/txauth/LJL5fjngEA9WaXzWacM0S-fD1Jc/

[1] https://datatracker.ietf.org/doc/charter-ietf-txauth/00-00/
[2] https://datatracker.ietf.org/doc/minutes-107-txauth/
[3] https://datatracker.ietf.org/doc/charter-ietf-txauth/
[4] https://www.ietf.org/rfcdiff?url1=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-txauth%2Fwithmilestones-00-00.txt&url2=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fcharter-ietf-txauth%2Fwithmilestones-00-04.txt
[5] https://mailarchive.ietf.org/arch/msg/txauth/G7kcSqApAkKrdjnr0NfKOTu1eRg/