Re: [Reap] [saag] PSA: New list for discussing EAP related methods

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 27 October 2017 01:43 UTC

Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: reap@ietfa.amsl.com
Delivered-To: reap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C02613A41F; Thu, 26 Oct 2017 18:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jLs4HUtkbAML; Thu, 26 Oct 2017 18:43:34 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::232]) (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 A992013F4CB; Thu, 26 Oct 2017 18:43:34 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id 31so6685974qtz.9; Thu, 26 Oct 2017 18:43:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vybTILVLThz2X/6QS0SVHs/owRIsuBvQ3Emi6X2zfeg=; b=r+UcSx8eWWoHgkzYa0ycah9SJ+xrVNGgSaUQuPlqlRGxMYO3J3gYK++rimoTkOqWIm hXkO7CfmZC7ou2xWossVqA0w58Hdk4Upaof4SURAcG1F4bxodde2elooicstRh2CxyGs VvvBHr3oPv984O/3spPfQTPfiiKFfzrLpUDnIQP1oc7LElqXdQfqVwoGwjZIO3zdEDLH YoEtGmyJ0rMeGd0I6HBDnhAtodwQ1D+ZyaXq+D8Dh2veCaqquvE8rI0AxEKKkDLLudta 5kF5EJWXKgvmjnVQYo5FwppX9flFfgS6eJKh6Icsj0x6dmnFCzqI+zR42j7W+89uQGe4 mNvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vybTILVLThz2X/6QS0SVHs/owRIsuBvQ3Emi6X2zfeg=; b=oUK5ifdW6qlvodoilgC+pVHghuuyVk7u8ncK19YmXO+xXcJKEluTNbS50rbHeSi1bO d1BDQM1RVAhncxfWx+rCbTLTBbQJaxHq/3uX1ElkWFD1B718Uzs3QsJcP/8t1gGd8+mp fQwaA0dRrhceoaQVO3TKwsB463SNKa8/SqA4tMLVdNoKBGQVct/KUDXDkAhLRwHe+vRA kZBtmwGFdtmJfyyksMu0HEicweX7yN/KUA4BCN7neZlBzt1J+9/+WlVPQ40m9oTM0v93 vws6oaeeS2IHFwZmzbfdpToN7oZmnhjwQ8sXYgq6kYg9t08I/44nz6LcwqjqZbKOye5j Fn4g==
X-Gm-Message-State: AMCzsaWNiD1qLYkm0pr+74IkLt3roUXimDVKc0qby3HEmgCiT/BUZ4uk YDOBRYiwLoi0kaT7xHkBPc6TIwO4
X-Google-Smtp-Source: ABhQp+SLoTVxssoa3Va6svRBoU12ahmiw2XRQGk8RO856Jknfdcmt0lYIKwHY62GnSY3wKJaMal43A==
X-Received: by 10.237.34.201 with SMTP id q9mr38829872qtc.198.1509068613406; Thu, 26 Oct 2017 18:43:33 -0700 (PDT)
Received: from [192.168.1.6] (209-6-124-204.s3530.c3-0.arl-ubr1.sbo-arl.ma.cable.rcncustomer.com. [209.6.124.204]) by smtp.gmail.com with ESMTPSA id e62sm4277328qkb.11.2017.10.26.18.43.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Oct 2017 18:43:32 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-2A7FD865-AA95-4AF5-B368-2F44CD914C8B
Mime-Version: 1.0 (1.0)
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <CAOW+2du_08fcfZs2878LsjnLV8L0cmDMa3pLN2cxQeHbFKxOCA@mail.gmail.com>
Date: Thu, 26 Oct 2017 21:43:31 -0400
Cc: Mohit Sethi <mohit.m.sethi@ericsson.com>, reap@ietf.org, "saag@ietf.org" <saag@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <112200E8-0E1D-4A38-800D-54892BFF67F6@gmail.com>
References: <3dbe94b9-4b2d-1479-8433-8b040cb1cfba@ericsson.com> <CAOW+2ds9Sez7otrs682hqzzXR8qbJYAdPwW8A8TEL+ms_a0=UA@mail.gmail.com> <6b3dcad6-f00c-1fb9-4df6-19f3dc744371@ericsson.com> <CAHbuEH74=Ca8oEWS5YpFByP1o3GaC0NajrZ8ChJxQAoffTajUg@mail.gmail.com> <CAOW+2du_08fcfZs2878LsjnLV8L0cmDMa3pLN2cxQeHbFKxOCA@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/reap/gXfdaTV_R62rDvwvp3sqwqSU7kw>
Subject: Re: [Reap] [saag] PSA: New list for discussing EAP related methods
X-BeenThere: reap@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "REAP \(RENEW\) EAP" <reap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/reap>, <mailto:reap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/reap/>
List-Post: <mailto:reap@ietf.org>
List-Help: <mailto:reap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/reap>, <mailto:reap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2017 01:43:37 -0000

That sounds like the best plan.

Thank you,
Kathleen 

Sent from my iPhone

> On Oct 26, 2017, at 9:16 PM, Bernard Aboba <bernard.aboba@gmail.com>; wrote:
> 
> Yes, the EMU WG  list has been used for discussion of EAP methods since the WG closed. 
> 
> That list is a better venue for discussion of EAP  methods than a new REAP list, so as to ensure that proper attention is paid to backward compatibility, IPR, security properties and other critical aspects of EAP method design. 
> 
> After all, we are talking about a protocol that is 20+ years old that is implemented on billions of devices, many of which utilize open-source.  
> 
> 
> 
> 
> 
> 
> 
> 
>> On Thu, Oct 26, 2017 at 11:53 AM, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>; wrote:
>> On Thu, Oct 26, 2017 at 1:16 PM, Mohit Sethi <mohit.m.sethi@ericsson.com>; wrote:
>> > Hi Bernard,
>> >
>> > The EAP-TLS 1.3 document is a very rough drafty version that was submitted
>> > before the cut-off for the last IETF. As you rightly point out, it has the
>> > skeleton and a lot of material from RFC5216, and still many important
>> > details are missing.
>> >
>> > The purpose of this list is to exactly receive these kind of comments.
>> > Should RFC5216 be updated or obsoleted by this draft. And it would be great
>> > if we can have your contributions to the document. We will definitely add an
>> > acknowledgement section and contact the authors of RFC5216 to see if they
>> > can contribute and comment. We plan to have more EAP related contributions
>> > in the near future. We discussed this with the Security ADs and thought that
>> > a separate list would be appropriate to get feedback/criticism and
>> > contributions from the folks interested.
>> 
>> I'm sorry, I didn't realize that a revision of 5216 was involved and
>> that the authors were not notified at the onset as is normal practice
>> in case they want to continue as authors.  Thank you for spotting this
>> issue Bernard.
>> 
>> Is there an existing list that should be used?  Is there adequate
>> overlap in objectives and personnel?
>> 
>> Thank you,
>> Kathleen
>> 
>> >
>> > --Mohit
>> >
>> >
>> > On 10/26/2017 06:51 PM, Bernard Aboba wrote:
>> >
>> > There are existing functioning IETF mailing lists relating to EAP.
>> >
>> > Why are you starting yet another one?
>> >
>> > From what I can tell, the EAP-TLS 1.3 draft is merely a copy of RFC 5216
>> > (with no acknowledgement to the original authors) stating that EAP-TLS
>> > implementations must support TLS 1.3.
>> >
>> > This is ridiculous because there are 1+ Billion existing implementations out
>> > there that
>> >
>> >
>> > On Thu, Oct 26, 2017 at 6:02 AM, Mohit Sethi <mohit.m.sethi@ericsson.com>;
>> > wrote:
>> >>
>> >> Dear all,
>> >>
>> >> We have started a mailing list for discussing new EAP related work that
>> >> currently has no obvious home. The mailing list is called REAP (Renew EAP)
>> >> reap@ietf.org and you can subscribe here:
>> >> https://www.ietf.org/mailman/listinfo/reap
>> >>
>> >> Recently several new EAP methods have been proposed. These include for
>> >> example:
>> >>
>> >> EAP-TLS 1.3: https://tools.ietf.org/html/draft-mattsson-eap-tls13-00
>> >>
>> >> EAP-NOOB: https://tools.ietf.org/html/draft-aura-eap-noob-02
>> >>
>> >> EAP-SASL: https://tools.ietf.org/html/draft-vanrein-eap-sasl-00
>> >>
>> >> The list serves as a venue for discussion of these and other EAP related
>> >> drafts that will be submitted in the near future. As courtesy, we will post
>> >> any new draft to SAAG, but we plan to continue the discussion only on the
>> >> REAP mailing list. We have also asked for a short presentation slot during
>> >> SECDISPATCH at IETF 100 in Singapore.
>> >>
>> >> Comments, early feedback, and discussion on existing or new work is more
>> >> than welcome.
>> >>
>> >> --Mohit
>> >>
>> >> _______________________________________________
>> >> saag mailing list
>> >> saag@ietf.org
>> >> https://www.ietf.org/mailman/listinfo/saag
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > saag mailing list
>> > saag@ietf.org
>> > https://www.ietf.org/mailman/listinfo/saag
>> >
>> >
>> >
>> > _______________________________________________
>> > saag mailing list
>> > saag@ietf.org
>> > https://www.ietf.org/mailman/listinfo/saag
>> >
>> 
>> 
>> 
>> --
>> 
>> Best regards,
>> Kathleen
>