[Wimse] Re: Token Translation Requirements
"McAdams, Darin" <darinm@amazon.com> Tue, 13 August 2024 02:28 UTC
Return-Path: <prvs=948192ff4=darinm@amazon.com>
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 38CFBC151520 for <wimse@ietfa.amsl.com>; Mon, 12 Aug 2024 19:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level:
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.148, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=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 (1024-bit key) header.d=amazon.com
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 t9iWZ9vzVzAo for <wimse@ietfa.amsl.com>; Mon, 12 Aug 2024 19:28:36 -0700 (PDT)
Received: from smtp-fw-80007.amazon.com (smtp-fw-80007.amazon.com [99.78.197.218]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49F72C15109C for <wimse@ietf.org>; Mon, 12 Aug 2024 19:28:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1723516116; x=1755052116; h=from:to:subject:date:message-id:mime-version; bh=27L9AwNCJikzos1HUxQGBHj3mnEtcc9z5qGI9ePL8gw=; b=Q/2KtyTbLS6b/LbrRz0D3VLcmdEebvuhf09qjK6rLeBUyoBPOcanCrJn 1tjlYUYA+96w5A8vBsHp5ONhs2IPSvVco4Ap6AF95tZxZ/5x+1cySHn/n i/u9IQUD9p7qwlHgrFS8Mc4yFZhT4s/BR0zwKamS0OKaLxMJMhj6j3WpC I=;
X-IronPort-AV: E=Sophos;i="6.09,284,1716249600"; d="scan'208,217";a="320396807"
Received: from pdx4-co-svc-p1-lb2-vlan2.amazon.com (HELO smtpout.prod.us-west-2.prod.farcaster.email.amazon.dev) ([10.25.36.210]) by smtp-border-fw-80007.pdx80.corp.amazon.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Aug 2024 02:28:36 +0000
Received: from EX19MTAUWB002.ant.amazon.com [10.0.7.35:33980] by smtpin.naws.us-west-2.prod.farcaster.email.amazon.dev [10.0.15.23:2525] with esmtp (Farcaster) id 064d738a-3e29-4053-90f5-383d850e848f; Tue, 13 Aug 2024 02:28:35 +0000 (UTC)
X-Farcaster-Flow-ID: 064d738a-3e29-4053-90f5-383d850e848f
Received: from EX19D008UWA002.ant.amazon.com (10.13.138.240) by EX19MTAUWB002.ant.amazon.com (10.250.64.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1258.34; Tue, 13 Aug 2024 02:28:34 +0000
Received: from EX19D008UWA004.ant.amazon.com (10.13.138.220) by EX19D008UWA002.ant.amazon.com (10.13.138.240) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.2.1258.34; Tue, 13 Aug 2024 02:28:34 +0000
Received: from EX19D008UWA004.ant.amazon.com ([fe80::d946:a53:e254:7768]) by EX19D008UWA004.ant.amazon.com ([fe80::d946:a53:e254:7768%5]) with mapi id 15.02.1258.034; Tue, 13 Aug 2024 02:28:34 +0000
From: "McAdams, Darin" <darinm@amazon.com>
To: Justin Richer <jricher@mit.edu>, "wimse@ietf.org" <wimse@ietf.org>
Thread-Topic: [Wimse] Token Translation Requirements
Thread-Index: AQHa7Sh+I3H2jcyq3E+nedAvoy3CUA==
Date: Tue, 13 Aug 2024 02:28:33 +0000
Message-ID: <9BFB6E35-E3F4-4318-9EAE-A148D0849AED@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.86.24062313
x-originating-ip: [10.13.138.67]
Content-Type: multipart/alternative; boundary="_000_9BFB6E35E3F443189EAEA148D0849AEDamazoncom_"
MIME-Version: 1.0
Message-ID-Hash: MI3IGLDP6RTPAMZPEGINOIP5XDFCB7LV
X-Message-ID-Hash: MI3IGLDP6RTPAMZPEGINOIP5XDFCB7LV
X-MailFrom: prvs=948192ff4=darinm@amazon.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Wimse] Re: Token Translation Requirements
List-Id: WIMSE Workload Identity in Multi-Service Environment <wimse.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wimse/yvlNlQhnwICXzv2ows2jh19h7BM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wimse>
List-Help: <mailto:wimse-request@ietf.org?subject=help>
List-Owner: <mailto:wimse-owner@ietf.org>
List-Post: <mailto:wimse@ietf.org>
List-Subscribe: <mailto:wimse-join@ietf.org>
List-Unsubscribe: <mailto:wimse-leave@ietf.org>
Vote (D) - You need more information… +1 to other comments on sharing representative use cases & requirements, and also answering Brian’s Campbells feedback at IETF regarding why requirements aren’t met by Token Exchange. From: Justin Richer <jricher@mit.edu> Date: Monday, July 29, 2024 at 7:03 AM To: "wimse@ietf.org" <wimse@ietf.org> Subject: [EXTERNAL] [Wimse] Token Translation Requirements CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Following discussion in Vancouver, the chairs would like to begin discussion on what the next steps should be for the Token Translation Requirements document [1], an output of the Token Exchange Design Team. This is not a call for adoption as there was a clear indication in the room that the document was not yet ready for this stage. As this is a requirements document, and it is unusual for a requirements document to be codified as an RFC, the chairs would like the group to discuss what the intended direction of this document should be. Please reply to the list to indicate that: A: You believe this document should be developed into a state that the WG can adopt it. (Please discuss what you believe would be required changes for this. Please keep in mind that a call for adoption is a starting point for a document, not a finished document.) B: You believe this document should be developed by the WG as something other than a WG / RFC-track document. (Please discuss what you think the right format or forum would be - a wiki page, a web page, an eternal I-D, a blog post, etc) C: You believe this document should NOT be developed further by the WG. (Please indicate why if possible) D: You need more information before making this decision. (Please indicate what information you’d need) D: You don’t give a flying rat about this document (i.e., this is not a topic you care strongly about) Please reply to the list by August 12th, 2024. — Justin and Pieter [1] https://datatracker.ietf.org/doc/draft-rosomakho-wimse-tokentranslation-reqs/
- [Wimse] Re: Token Translation Requirements McAdams, Darin
- [Wimse] Token Translation Requirements Justin Richer
- [Wimse] Re: Token Translation Requirements Flemming Andreasen (fandreas)
- [Wimse] Re: Token Translation Requirements Dean Saxe
- [Wimse] Re: Token Translation Requirements Dmitry Izumskiy
- [Wimse] Re: Token Translation Requirements Joseph Salowey