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

Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> Fri, 27 October 2017 18:08 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 A369413F088; Fri, 27 Oct 2017 11:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 2TUXVOjBGOAu; Fri, 27 Oct 2017 11:08:30 -0700 (PDT)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e:c05::236]) (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 C34E913F3AC; Fri, 27 Oct 2017 11:08:29 -0700 (PDT)
Received: by mail-pg0-x236.google.com with SMTP id y5so5856124pgq.7; Fri, 27 Oct 2017 11:08:29 -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=mfLuGKQymS9Pve+iWDqSwLU/XAqvuuWAL12NUZs79G0=; b=it3+p7qq+tMWWu24Y/lXtbqNbyWlsYlhks9/BN45T40MjVbPzIMmJkvWIk1z5bYoNW Pk2oPLbxaQzIAbQO5UpuN0nzm30jZtiyN4hqCKAxgWBo+LlD6ZyCvUgTIXSrv0YM7K2H Q4TmmQjf3CMgtM+qil7CmS2yc7fGoelopfXTielJFDnLhOGKunckQkNWwfwSAPQyasxQ T/Rju/CEMTzSra4GAwhwvE9MN46hSI9FJx5QQixPJIR/9q6heMa231DHCsrPqUqwVUah xlwgKhDlMK4VOwQOTgJf1L4CQpYcQ+KMrGPMQzy/5pli4w+U1RQ0tefYNr7JncHBZ7i5 Sipg==
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=mfLuGKQymS9Pve+iWDqSwLU/XAqvuuWAL12NUZs79G0=; b=OkgBrotfqyVANY+5tTTf+0bluDN17DAfwJktDfvHNcWPaaJzrB0OugXrYCW1YJ3Xgi f979Y0OMzrWCGhAiF1gtj/Pl6l0Loi87q/YUzXvEB74H/F5z8MKK7PunIMf1lGgOXzA5 cRrVHbJnQ5ojhSPjICVRBqCMRSBwI7f6ryzL9kio69mz3klliuYYmmTfa9fxR3ee+hgg E+dMjWv+CjyTjGKAFqNDN0NWDgLpHox1RXGmORT/uQEOcwVk6PEgdUKerW5sfKpufWWs of1HNPTiwLC0g3zT3KsVtc/WNBm0GpgVH0HxTW9rORep+fY1Kwdv4bEBk9PCUdum2vqS zG9Q==
X-Gm-Message-State: AMCzsaWxgmprggTPlozZBGTQlZv1FI1m64lC3bEWW+K5uYOM7mYk+TMM POawfna2VqM5HAprZjTWcBh0nFpFsAVcZE1FpBk=
X-Google-Smtp-Source: ABhQp+TJw88MYEwrb3/WH/vr73KxRatVu52bcF93PJKkDVnO9VaeD8ryS0f2nffXeiafHytAsHNTuM9vL92znxUh9os=
X-Received: by 10.98.201.87 with SMTP id k84mr1225147pfg.109.1509127709345; Fri, 27 Oct 2017 11:08:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.186.194 with HTTP; Fri, 27 Oct 2017 11:07:48 -0700 (PDT)
In-Reply-To: <dcbfbc1b-1638-57dd-af14-36fcbf848348@cisco.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> <112200E8-0E1D-4A38-800D-54892BFF67F6@gmail.com> <dcbfbc1b-1638-57dd-af14-36fcbf848348@cisco.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Fri, 27 Oct 2017 14:07:48 -0400
Message-ID: <CAHbuEH6Bm=nev2dNgPXsGz3WYMMDtqo2qQQpGWt8eCKRhOQY+g@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: Bernard Aboba <bernard.aboba@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/HaWLlVwbiP8DRsX01XmEBAJvMDQ>
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 18:08:32 -0000

EKR and I chatted and agree using EMU is the best go forward plan.
Thank you for raising the issue that slipped by us.

Best regards,
Kathleen

On Fri, Oct 27, 2017 at 7:55 AM, Eliot Lear <lear@cisco.com>; wrote:
> Kathleen,
>
> So the plan is to close reap and use emu?
>
> Eliot
>
>
> On 10/27/17 3:43 AM, Kathleen Moriarty wrote:
>
> 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
>
>
>
>
> _______________________________________________
> saag mailing list
> saag@ietf.org
> https://www.ietf.org/mailman/listinfo/saag
>
>



-- 

Best regards,
Kathleen