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

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Thu, 26 October 2017 18:54 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 0A29713F442; Thu, 26 Oct 2017 11:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 iqcuwA1g0TPf; Thu, 26 Oct 2017 11:54:17 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (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 6AA1913942C; Thu, 26 Oct 2017 11:54:17 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id a192so3391733pge.9; Thu, 26 Oct 2017 11:54:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=13mn0BAYaGa/4VJjztteIkV69s2qxIIZtitzpGcDEuY=; b=CJjj7Yj8wTN7qRe/nV8AV7LYyyuIGOHVVd4zBdekavMfC0Zgf8ZLB+LEFKIE+X6+CC FRmxFNjt2W1C7dkrsueAF3Wx2OJJ4npgn4+t3CNuI7kqOUcfD/8Dim/EfUxtEO2KRxpr MNnRe+WgERJSzzsQ36p5JVtDYrS8Hgw1QdHQNY8LjBElASho3AYw/Qhpofmj9wvDbmpF fjpLVfu8tg5niD5oiaScrBcrAywp30GnMOdSMlJsi7X3onI9UTTii6LX+8HcP4dwY1kn GjiacYoFoE+z3Zb389SYhBQJEi2TMRhW6FgFFuzyhKGSdcr2vLHgpHwxZBVKvZPOV383 jzBA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=13mn0BAYaGa/4VJjztteIkV69s2qxIIZtitzpGcDEuY=; b=Vaj0PS0pSpSQdzucbqiV92Ge5ah3WPKxlOEFMCEmOi3Y5pETUcGAsNORwunIEO1rzX XT/UkiSj/yzBVjrAihiLfNIxmZ8FReMDy+EqjXslsvMXM3zn2BjFqI8YZiv5BPOCEHas UN344OVL4bk3McvIc56v7xQbAlkBQzg/uzfAz+elX8USQPPBSEbTH+MBftdbk5cVdHnv 57tspwGAhSO96w63h8A2Djh592lM6BKV4bY9UCx4brM/hqKxv3VBm+DmZGrUW8V2nEqD P+1PDSPPi1Qvv9fli7xUKZySouDETZVWnNvp17FsKSxm3JqfHe1ZiwnUxjPsjN5ja1PC wRyQ==
X-Gm-Message-State: AMCzsaUOCHjalp/IrD/2KHl/SrjLuEB0DH+FLYuxNjIBLyHGwmgSFTox h3iqZVwJcn0J9uSMBrm1otTPcwlx8bTNweuOnIU=
X-Google-Smtp-Source: ABhQp+Sc7EizZrEDR6ttng7dEkdx2CFPlVikI8Svdo2OzKjBbKY3EUVz4x2a7XKEOlnDqwle42xiPysBOoMCAAHNXnc=
X-Received: by 10.98.214.76 with SMTP id r73mr6198747pfg.261.1509044056806; Thu, 26 Oct 2017 11:54:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.186.194 with HTTP; Thu, 26 Oct 2017 11:53:36 -0700 (PDT)
In-Reply-To: <6b3dcad6-f00c-1fb9-4df6-19f3dc744371@ericsson.com>
References: <3dbe94b9-4b2d-1479-8433-8b040cb1cfba@ericsson.com> <CAOW+2ds9Sez7otrs682hqzzXR8qbJYAdPwW8A8TEL+ms_a0=UA@mail.gmail.com> <6b3dcad6-f00c-1fb9-4df6-19f3dc744371@ericsson.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Thu, 26 Oct 2017 14:53:36 -0400
Message-ID: <CAHbuEH74=Ca8oEWS5YpFByP1o3GaC0NajrZ8ChJxQAoffTajUg@mail.gmail.com>
To: Mohit Sethi <mohit.m.sethi@ericsson.com>
Cc: Bernard Aboba <bernard.aboba@gmail.com>, reap@ietf.org, "saag@ietf.org" <saag@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/reap/lfYNV9EnqYLcFzFaTgDQ0-KAJwc>
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: Thu, 26 Oct 2017 18:54:20 -0000

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