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

Zhen Cao <zhencao.ietf@gmail.com> Sat, 28 October 2017 09:01 UTC

Return-Path: <zhencao.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 14B6013AB36; Sat, 28 Oct 2017 02:01:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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_LOW=-0.7, 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 QVX38joHEYBv; Sat, 28 Oct 2017 02:01:01 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 194CD1395ED; Sat, 28 Oct 2017 02:01:01 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id h142so2076805vkf.7; Sat, 28 Oct 2017 02:01:01 -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=GQPVS9z3WKVynxCRTm4otDRR2eRsFMWgbwy4vWA7o8U=; b=D1fFb0sGFJ10CLihI+Q1ybwCS9XDhQmD1oq6gEY2rPzdSct7+HHY2wKpMsrd6u4M7t PmNY29JObWUO5GtmwKNLBeD9E8wIkb6Rfn/5YbrbGXfQi6domI3Z+ESqkR4DTGySxJtO aiEeCYCR7Szpe+k3wAE9vKEiCnhEQeUvMYJ0SltmjFGQwbuOIzIk0lF2fHvHPgFpGbI4 dYlOkPa91iDM3MEgp289emR/ps/Q/bAY0m75kc6MeqSGAetOkxEFad03TeLJ7+gMwkA4 GwbaLojGMivWBwqrLQR+pwhEYCH9+iHmLusgYUazGlj413od2lJJbVJDSsFQZ2soPUIp jDQw==
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=GQPVS9z3WKVynxCRTm4otDRR2eRsFMWgbwy4vWA7o8U=; b=nmd/WV9ExnpiJSnZQxEd9/7RuGoDZyOh94MGvM8l+vD3eHG85Nwn7g2CmZNZ1eEGUk Y2HhliwX/iJkMWpHXw8NOpKPuTzb2KABKjrQjlso3lbY9vp5r0VF5TAiTS2LsfKxpS2j Or2SAr+7EGrYNgNDvp5Glt0NJtGsEoyUOrcyIO1vQW4rV3kret9K0lsv/QzVKu2oMAU/ 1G6tKXZIwqWeUz9KaDYqnssXi256TQo/VhyysgPTfa0xO1TWCbcQMU8LJtUldswF60ay R9vasHE60sQE2nwxPBofX5MGyhwRukOjl784BqWmBIgsX7umb9uoDgPwX3bzGfDWgRlB DlAw==
X-Gm-Message-State: AMCzsaV05aDA1yvcFf0I6rYssbJUDSFK5p5q8xPWQt11j8LchegiTHnl PsysD18ndxkDS+Fu24ZTy9kEFXMEyK/57JpCs/E=
X-Google-Smtp-Source: ABhQp+SSWnDZeBWfM97aTgh189/7IMuUbtdCb7dnDOVk80GNXgL6R1cMAt7pxGeJu5TaOBsJj9YfQPQbFGBHuQCaNnc=
X-Received: by 10.31.70.133 with SMTP id t127mr2691863vka.100.1509181260169; Sat, 28 Oct 2017 02:01:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.84.143 with HTTP; Sat, 28 Oct 2017 02:00:59 -0700 (PDT)
In-Reply-To: <CAOW+2du_08fcfZs2878LsjnLV8L0cmDMa3pLN2cxQeHbFKxOCA@mail.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>
From: Zhen Cao <zhencao.ietf@gmail.com>
Date: Sat, 28 Oct 2017 17:00:59 +0800
Message-ID: <CAFxP68yw5sicGEDx-RcQmNX7Jdvhv74Kr6DA9dQKniA-F4LFoA@mail.gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, reap@ietf.org, Mohit Sethi <mohit.m.sethi@ericsson.com>, "saag@ietf.org" <saag@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/reap/DSGnyiFFaeQiERMZQ1WhWjB4KQs>
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: Sat, 28 Oct 2017 09:01:03 -0000

Thanks Bernard for pointing out this, at least new to me. I check the
emu wg conclusion email, not formally stating that emu will be the
only place for eap-related discussion.

The emu list has been quite silent since the wg conclusion, less than
20 messages for three years.  There were occasionally some drafts
posted for comments, but not any follow-up responses.  This leaves an
impression that either the list members are not interested in new
topics or the emu list is not actually adequately subscribed (who has
the ground truth?).    I believe this is not only a motive for Mohit
and I to request a new mailing list, but may also confuse upcoming
people who seek for a place to have discussion.

Regards,
-Zhen
On Fri, Oct 27, 2017 at 9:16 AM, 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
>
>
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
>