[Emu] Quick comments on draft-sawant-eap-ppt-00
Alan DeKok <aland@deployingradius.com> Tue, 23 July 2024 19:50 UTC
Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B25BC14CF1C for <emu@ietfa.amsl.com>; Tue, 23 Jul 2024 12:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 ucoXzS_fITCJ for <emu@ietfa.amsl.com>; Tue, 23 Jul 2024 12:50:04 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CA88C19ECB3 for <emu@ietf.org>; Tue, 23 Jul 2024 12:50:02 -0700 (PDT)
Received: from smtpclient.apple (dhcp-911c.meeting.ietf.org [31.133.145.28]) by mail.networkradius.com (Postfix) with ESMTPSA id F3B308D for <emu@ietf.org>; Tue, 23 Jul 2024 19:49:59 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
From: Alan DeKok <aland@deployingradius.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
Message-Id: <5E353188-8203-4150-BB76-5A3E555555A5@deployingradius.com>
Date: Tue, 23 Jul 2024 12:49:57 -0700
To: EMU WG <emu@ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Message-ID-Hash: D6XQSMQS3MAGO5MMZJB2H4D64CZJCQTJ
X-Message-ID-Hash: D6XQSMQS3MAGO5MMZJB2H4D64CZJCQTJ
X-MailFrom: aland@deployingradius.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-emu.ietf.org-0; 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: [Emu] Quick comments on draft-sawant-eap-ppt-00
List-Id: "EAP Methods Update (EMU)" <emu.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/KqcZVHsEGVjyPnRNvJLm5QRbVlM>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Owner: <mailto:emu-owner@ietf.org>
List-Post: <mailto:emu@ietf.org>
List-Subscribe: <mailto:emu-join@ietf.org>
List-Unsubscribe: <mailto:emu-leave@ietf.org>
These are just some notes which come from skimming the document: * what is used for the outer identity? Should it be in NAI form? What are the privacy implications of using a domain in the outer NAI? i.e. the EAP conversation should be routable in an AAA framework. So the outer identity should be something like @example.com. What privacy implication does this have for EAP-PPT? * what certificate is used for the outer TLS session? How is it validated? * what happens with session resumption? Presumably that's a way to correlated multiple sessions. So even if the PII changes per sessions, the use of resumption will tie two sessions together Alan DeKok.