Re: [Emu] I-D Action: draft-ietf-emu-eap-tls13-16.txt

Alan DeKok <> Fri, 11 June 2021 14:17 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A26173A45F4 for <>; Fri, 11 Jun 2021 07:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4of2eissCrUc for <>; Fri, 11 Jun 2021 07:17:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B5E8D3A4605 for <>; Fri, 11 Jun 2021 07:17:09 -0700 (PDT)
Received: from [] ( []) by (Postfix) with ESMTPSA id 3B5613FF; Fri, 11 Jun 2021 14:17:06 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Alan DeKok <>
In-Reply-To: <>
Date: Fri, 11 Jun 2021 10:17:05 -0400
Cc: "" <>, Joseph Salowey <>, Roman Danyliw <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <>
To: Mohit Sethi M <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Emu] I-D Action: draft-ietf-emu-eap-tls13-16.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 11 Jun 2021 14:17:28 -0000

On Jun 11, 2021, at 9:56 AM, Mohit Sethi M <> wrote:
> I guess you know that there are several implementations of the draft 
> some of which are already deployed.

   While that's a nice comment telling me what I already know, it doesn't address my point.  The fact that implementations exist does not mean that the specification is sufficient to create an implementation.

  The implementors have had many "behind the scenes" discussions about how to implement EAP-TLS 1.3.   The outcome of those discussions was shared among implementors.  That information is largely what enabled inter-operability.  Information which is not all reflected in the document.

  I have suggested repeatedly that the document contain sufficient information to create a secure and inter-operable implementation.  It's not clear to me why these suggestions have been ignored, or rejected.

> It is of course nice to strive for perfection.

  That comment misrepresents my position.

> Could you please submit a pull request addressing your 
> unaddressed comments.

  I gave suggested text in my messages.  These comments were largely ignored across multiple reviews.  This is not how we should work towards consensus.

  If the goal of this document is simply to get it published, then I withdraw all of my objections.  Implementors will then share extra knowledge behind the scenes.

  If the goal of this document is to enable secure and inter-operable implementations, then it would be useful to address comments from major implementors.

  Alan DeKok.