[Emu] Version Notification for draft-dekok-emu-eap-usability-00.txt

Alan DeKok <aland@deployingradius.com> Mon, 12 July 2021 17:58 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 A5E803A005E for <emu@ietfa.amsl.com>; Mon, 12 Jul 2021 10:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.003
X-Spam-Level:
X-Spam-Status: No, score=0.003 tagged_above=-999 required=5 tests=[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
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 XRQvpdA6zAST for <emu@ietfa.amsl.com>; Mon, 12 Jul 2021 10:58:11 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 900343A0908 for <emu@ietf.org>; Mon, 12 Jul 2021 10:57:41 -0700 (PDT)
Received: from [192.168.46.129] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id 8E0351DA; Mon, 12 Jul 2021 17:57:39 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
From: Alan DeKok <aland@deployingradius.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8A557B51-A6EC-43D7-A819-A513CBF8DEF4"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Mon, 12 Jul 2021 13:57:37 -0400
References: <162611255836.29278.13767587856449885761@ietfa.amsl.com>
To: EMU WG <emu@ietf.org>
Message-Id: <D71E4C2D-53AC-4453-AF26-39D8684CEAF0@deployingradius.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/OFE54P6RVVuaiQTsZ7VrUAvUbLg>
Subject: [Emu] Version Notification for draft-dekok-emu-eap-usability-00.txt
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: Mon, 12 Jul 2021 17:58:17 -0000

  I've submitted an "EAP usability" document.  The title could perhaps be better.

  It gives guidelines, requirements, and practices for making it easier to use TLS-based EAP methods.

  I've asked the chairs for time at the next IETF to discuss this.  Until then, any feedback / comments are welcome.

> Begin forwarded message:
> 
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-dekok-emu-eap-usability-00.txt
> Date: July 12, 2021 at 1:55:58 PM EDT
> To: "Alan DeKok" <aland@networkradius.com>
> 
> 
> A new version of I-D, draft-dekok-emu-eap-usability-00.txt
> has been successfully submitted by Alan DeKok and posted to the
> IETF repository.
> 
> Name:		draft-dekok-emu-eap-usability
> Revision:	00
> Title:		EAP Usability
> Document date:	2021-07-12
> Group:		Individual Submission
> Pages:		58
> URL:            https://www.ietf.org/archive/id/draft-dekok-emu-eap-usability-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-dekok-emu-eap-usability/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dekok-emu-eap-usability
> 
> 
> Abstract:
>   This document defines methods which enable simpler deployment of TLS-
>   based EAP methods.  It defines new certificate fields, and uses
>   existing certificate fields in order describe new methods for
>   bootstrapping security.  The methods defined here change TLS-based
>   EAP supplicant configuration from a complex and insecure process to
>   one that is automated, and is essentially trivial.  These methods are
>   still, however, compatible with existing standards and practices.
> 
> 
> 
> 
> The IETF Secretariat
> 
>