Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3 (draft-ietf-emu-eap-tls13-17)

Joseph Salowey <joe@salowey.net> Wed, 07 July 2021 05:08 UTC

Return-Path: <joe@salowey.net>
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 B644D3A044F for <emu@ietfa.amsl.com>; Tue, 6 Jul 2021 22:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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 (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 A3CAFuLXZHD4 for <emu@ietfa.amsl.com>; Tue, 6 Jul 2021 22:08:27 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18DC3A0442 for <emu@ietf.org>; Tue, 6 Jul 2021 22:08:26 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id s18so1062482ljg.7 for <emu@ietf.org>; Tue, 06 Jul 2021 22:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wVxq67hcPjr9GP49Koa2LAInh1OJh/Js32SSjL0tWqM=; b=kPIqecHQej1Hgxmhp4RtAuiLD/5SFsWVpUmnsMxLo+kOAvn08CvaXqz+jzMunDRph2 EDzG8ajmPtPNe0WGm1sHQbQSx6S91qrGWwVvX9Zo+YUXdpRydHb5iMtkErAHbcCJSLiQ Q4eYBYryTSxlKiDztFvgPjMj2jHkd/4QqJh+i7mpkBi3AWDP0yLeoB82PXnXrFvVjG+V uAwjZhuJy2ymXih/F7jWT5yCYyVows4P+JAQ2naI0c9phx01TGaHINVhvrWMBZxQ/UHQ zKTnC+vSm7pCuuS84dLd57kAAWuZaNYS7kCdt8A27ku8V9bj3HLfuuqPoBXpLQXflCCm w6ag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wVxq67hcPjr9GP49Koa2LAInh1OJh/Js32SSjL0tWqM=; b=CeBOIqg2EA1iLYdB5GVXxolO8i2gwg908Vs0k6oQTcbRSd9salVBjNOPUPIPfSb+UO PtcGjdlhTWyTa8YxDHHmhZDEDumL4BsklC2tOogAupzOMLgnrzwMQDFiuYmZeqQXbNbk QUVo+30hDVD13QRzcW12CTc9h19NZ1w/tzLAJ1sgad6Kj+7N/louZeJcV1WFGvrpfTLf 6lOTjXk6uRsi2Ia0AXRbOA56VKD7/85N/Q0BpHz2GYxlzHIq9duT0fDk0c8lnMG+7e7h 9jVjon/Y0uYv1otbpvSTV1LtgtgKFT61w1PPlg7NoEHx2FUkhyqYyDD3pXWKE+m4Nn11 5zSw==
X-Gm-Message-State: AOAM531F7l8Z4N1SUfcFw1vRnrL/783AVKv9Us21J9qbdkcdQqR6TVjn uTW2k43diH9NoDY+PxTItC1oLcW+OVuzBCIA57EMjA==
X-Google-Smtp-Source: ABdhPJw80tuA2i8LaA5pOp8uIIdThXiKUKUSpuC2VFNmN/xS7v6WyS2KgK5YX/LrwIAZEPrTG2dYG+LN1bHzlH4Nars=
X-Received: by 2002:a2e:3510:: with SMTP id z16mr1183507ljz.366.1625634504146; Tue, 06 Jul 2021 22:08:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDX9HdmgvmnWz_xUTqXMM7pd4_T9W3opFR77ce8CNWdQQ@mail.gmail.com> <CABXxEz9GSgGof6t_3w3AngH6-FrMbKzDGKpDS90-N2gtmgqgnA@mail.gmail.com>
In-Reply-To: <CABXxEz9GSgGof6t_3w3AngH6-FrMbKzDGKpDS90-N2gtmgqgnA@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Tue, 6 Jul 2021 22:08:13 -0700
Message-ID: <CAOgPGoBLb-70jynH7o26nyF4T=+ZcCk6GMb6zyXk6E8+erTjqQ@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002795a205c6818711"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/cAbwbb4V3zhzFQT5upsXGpgKy9A>
Subject: Re: [Emu] WG Last Call for Using EAP-TLS with TLS 1.3 (draft-ietf-emu-eap-tls13-17)
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jul 2021 05:08:33 -0000

On Mon, Jun 28, 2021 at 8:11 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> I still see unclearness in Section "2.2. Identity Verification", I'm
> trying to look from the implementer's perspective.
>
> 1) "Since EAP-TLS deployments may use more than one EAP
>    server, each with a different certificate, EAP peer implementations
>    SHOULD allow for the configuration of a unique trusted root (CA
>    certificate) to authenticate the server certificate and one or more
>    server names to match against the SubjectAltName (SAN) extension in
>    the server certificate.  To simplify name matching, an EAP-TLS
>    deployment can assign a name to represent an authorized EAP server
>    and EAP Server certificates can include this name in the list of SANs
>    for each certificate that represents an EAP-TLS server."
>
> --- question: Should the server name match *any* of SAN extensions in the
> server certificate? If so - then suggest to say this explicitly.
>
>
[Joe] yes the behavior is to match any.


> 2) "If server
>    name matching is not used, then peers may end up trusting servers for
>    EAP authentication that are not intended to be EAP servers for the
>    network."
>
> --- question: It looks like a warning, right? Suggest to make it more
> explicit. Something like "If server name matching is not used, then it
> essentially decreases the level of security of peer's authentication since
> the peer may end up trusting servers for EAP authentication that are not
> intended to be EAP servers for the network."
>
>
[Joe] Thanks, I think that is better wording.


> Regards,
> Oleg
>
> On Mon, Jun 28, 2021 at 2:26 AM Joseph Salowey <joe@salowey.net> wrote:
>
>> This is the working group last-call (WGLC) for draft-ietf-emu-eap-tls13.
>> Please review the draft, focus on the changes since the last WGLC and
>> submit your comments to the list by July 8, 2021.
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-emu-eap-tls13/
>>
>> There is also an htmlized version available at:
>> https://datatracker.ietf.org/doc/html/draft-ietf-emu-eap-tls13-17
>>
>> A diff from the previous WGLC version (-15):
>>
>> https://www.ietf.org//rfcdiff?url1=draft-ietf-emu-eap-tls13-17&url2=draft-ietf-emu-eap-tls13-15
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-eap-tls13-17
>>
>> Thanks,
>>
>> Joe
>> _______________________________________________
>> Emu mailing list
>> Emu@ietf.org
>> https://www.ietf.org/mailman/listinfo/emu
>>
>