Re: [Wimse] Document Adoption: Best Current Practice for Workload Identity

hannes.tschofenig@gmx.net Fri, 05 April 2024 18:30 UTC

Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: wimse@ietfa.amsl.com
Delivered-To: wimse@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 478CCC180B6A for <wimse@ietfa.amsl.com>; Fri, 5 Apr 2024 11:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.092
X-Spam-Level:
X-Spam-Status: No, score=-2.092 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmx.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1X7tWN6_fnTQ for <wimse@ietfa.amsl.com>; Fri, 5 Apr 2024 11:30:28 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E090BC14F707 for <wimse@ietf.org>; Fri, 5 Apr 2024 11:30:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.net; s=s31663417; t=1712341824; x=1712946624; i=hannes.tschofenig@gmx.net; bh=pJDhFvQT8xiWsLhnMlxgLSOVyl9E6GksL+BL7l9mvm4=; h=X-UI-Sender-Class:From:To:References:In-Reply-To:Subject:Date; b=IYtjohYeL2Gk9XvsTD3kypFzwvl1tLMxw2J2RIhf7iodUMgP0W4AIiKVO2+x1COG rwy+huulpGja0crtyiAiY/nDcg3xHPk7G2UH2fUlRQCSkc7Yj1KBHhmaCGbA6qK3q qGz9NE2U5ZRsXat2ONWkjfa514rYNBY4l8jGUoUfOhOXTujObpEm0gG0OITdkkg0w BMQfXE8UWsNpQLZcSo4HDOwXbOxCF0l5r4tXyXjUNIDsVAxkN7VrYKhnmZvDL8rPe 7SEm5k58yvEb9IekKofKbm9Cj1p1iQ+DMpDtS/wd0nq7pthz7haPZByIIThnCPPbn 46MXo4e+QrsYu5bT2A==
X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a
Received: from Surface ([87.122.57.72]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MFbVu-1s17fy0Tz4-00HBKw; Fri, 05 Apr 2024 20:30:24 +0200
From: hannes.tschofenig@gmx.net
To: 'Justin Richer' <jricher@mit.edu>, wimse@ietf.org
References: <2EBDB77D-0AC9-4E6C-A279-7FACF9A47856@mit.edu>
In-Reply-To: <2EBDB77D-0AC9-4E6C-A279-7FACF9A47856@mit.edu>
Date: Fri, 05 Apr 2024 20:30:23 +0200
Message-ID: <008b01da8787$52b4b440$f81e1cc0$@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_008C_01DA8798.163FF540"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGRFODpcPt85tbJUncpxZauEcgKH7Hs40Mg
Content-Language: de-at
X-Provags-ID: V03:K1:/QuE9MmbFDiE8IrbNA2UXRt0HQ4KXOSb5Z8sahV+l8r6XYCFwvG L/SNkpc6XnWr2joHz7to2vadwv/r1Y9P0161vkcUgcvaGenPLlY/OAPtzg7y/azN3xybk7y CrYcAUppy/5IPjKJfn+tm+MnvW653UbAvM6O/gzhOOaQrpgL/wmdwe2rSslH2CMh3CcVaaS TD22QhM39QW0mOoDNuFbw==
UI-OutboundReport: notjunk:1;M01:P0:UfUvV7494WI=;NRnH4+JnENDRNPQ10mQKOxZXG1a Apyt3pklgkQglIkMv8jBfZgu+hC4KF0LmiZCnFXK7vAafLKCYA8OLz3ZlIicdNliZ9g5HI2tU 4FJrvoYopRt3q12I1JvdaHAyGDN5YMI8mxjiaoM/xOKPnPZwZ+MdW+Ny42fxUK6c2kOFKbaro WuOXpMjSis8xRdcy1pJ8qt5dcWbNxAB9TfgpYx4V+cnTKBHZ6Hv5/zlPuEPa8sYFXgPnIN35f hxLvpO+OFSKIpEc++soK+km2gDDrqRAJMbJNyoBN9IlU8LEDbU1XIbA7EwNTiQuNwifINvAKy NBHJEjMg4R4dXQrk9FQu1Madhz+zbFEW7KZwRqXFQBPtYlJgfuHDX49cwUHn5/35Rznbmijgt jGCAZVobcTFbM95j+pez7gG8FaP30Rwb9dR4Ia+ZVP6W1isGXMMiqRJqEMjmY1kP+ZZmuSiI3 68ZZmSg0dBCGnttCZQj/42zsyb33mr5agATS7rqIllVjF/NObBDaREe+KQLNCV0CkktJCY5+P YNuckmzpGxl0SMbN1Lyv0nhIIp+i4wLN508/a0RHEx0vqvz4VkHqv+2rjnitFAL3An1a3Y/au OF8DQx2jNkUhwLzeyUc6+TjOLcPU+Df00YDg+W2pjYLknrnjERZ9mH93uc2Z5dp3E4rAupiP8 Z2/cE167w4nhphe2JXjq4wTDHNkJkenn5W4Ijx1UT9rk10gvEmLehmgrgJSOYlyfWbrc9BBra f2ZJ0621YezC8idd/qCO6avOfrUpUYUaO7rPjun76A9ueehbh/vUO1+ZtJKqfbflX8nQ4ZB36 RXisQTcTVa3GiPk40PuZGeSQeZ5poU76M2ySGHa+fpNNc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/wimse/bJSyIKRQIBXrlqUtJTWD_89cTW8>
Subject: Re: [Wimse] Document Adoption: Best Current Practice for Workload Identity
X-BeenThere: wimse@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: WIMSE Workload Identity in Multi-Service Environment <wimse.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wimse>, <mailto:wimse-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wimse/>
List-Post: <mailto:wimse@ietf.org>
List-Help: <mailto:wimse-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wimse>, <mailto:wimse-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Apr 2024 18:30:32 -0000

Hi Justin, Hi Pieter,

 

as requested, I just submitted <draft-ietf-wimse-workload-identity-bcp> with the same content as the current I-D.

 

I would like to note that during conference calls before the Brisbane IETF meeting several persons (Yaroslav, Edoardo and Arndt) expressed interest to join as co-authors and, with the permission of the chairs, I would like to add them to the upcoming version of the document. I am convinced that their support will ensure faster completion of the work.

 

Ciao

Hannes

 

From: Wimse <wimse-bounces@ietf.org> On Behalf Of Justin Richer
Sent: Freitag, 5. April 2024 19:14
To: wimse@ietf.org
Subject: [Wimse] Document Adoption: Best Current Practice for Workload Identity

 

Based on feedback from the call for adoption, the chairs declare that the document draft-hofmann-wimse-workload-identity-bcp-00 has been adopted by the WIMSE working group.

 

Authors, please submit a -00 version as a WG document with the same content as the current I-D at your earliest convenience. The chairs will be in touch to move the document’s source files to a GitHub repository under the ietf-wg-wimse organization, or to set up a new repository with the document contents if necessary.

 

The chairs note that during the call for adoption, there was strong support for the document to remain narrowly focused on "the use of the use of JWTs for client credentials in container orchestration systems", but that several WG members expressed the need for the document to provide clarity of the scope and focus of the document going forward[1]. The chairs ask that the WG focus on this topic as a first issue when the new document has been submitted by the authors.

 

Thank you all for your feedback,

 

— Justin & Pieter

 

 

[1] https://mailarchive.ietf.org/arch/msg/wimse/QIRNRqG3BnTOkGjtsX3HizfkHBY/