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

Bernard Aboba <bernard.aboba@gmail.com> Fri, 27 October 2017 01:07 UTC

Return-Path: <bernard.aboba@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 5BE9A13F415; Thu, 26 Oct 2017 18:07:49 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 l1oOMAE51T4m; Thu, 26 Oct 2017 18:07:47 -0700 (PDT)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (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 4F176138BD2; Thu, 26 Oct 2017 18:07:47 -0700 (PDT)
Received: by mail-vk0-x231.google.com with SMTP id i133so3268093vke.9; Thu, 26 Oct 2017 18:07:47 -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=7xscIoFwlMC67u0AA3Ulx2NzYi/JbjgEbyiahTdRJ3Q=; b=W26h6xSFa7m5qhMgUxkrvOSmToyTyiJ/gHc1xpqC+3bBWNUoka/LdL2iW+JoXo65sK 1EDlUIOyVXbWDLvZD6b8VchWBfxDZGv8ucd5pdF7jr26KdOIa2xjTv9aRMrswNEPPyet 3zBy1XeVHriMlTpA7ahwdDsKETfzfMrWleE2DNVuYbVwG8jgR5ZixN4fM6sk/FFIuOfQ HX6OSM0SFQ8MCQ6LTMHFWT1BIyDcEE/kIJCQAhuvEkVBfMU98WlIw17Typ8ZRwXtsP4V GANfx086/h0FCQhrn2XBfUgT3j0pGJf18P7cqp01yaBpMItvJ+AtvBfqgYOP8Ls4mwa1 1/eA==
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=7xscIoFwlMC67u0AA3Ulx2NzYi/JbjgEbyiahTdRJ3Q=; b=d3Rim0duW6NfSJxT1vNJeIUyWngdCe64GdGFvwbA1ep7lTkyJW+XiqhgI7ML1kax55 3IgmBntuX7tB7U74VpicWCUwVNIO49+yZw3v/1l6vyaimvhVqHRigVw4iHze/3w9LvIn GcRVQOu5jqHcc10AREQetU9/MNmMU4OYO8rsJ39n97AgT1obIFb/sF7LZsNXOOpgWWXb gytUt/iRRG1gTVm9DMIG/EICMPx9XJs5pKJQzxeyVQMCNwKhQudhSAfmD7MXlcoWWmUj aCCayW0gtK+4vImLz+cRCIUmrRnaubQe/acZelzq0QcK+clyc5Ri4esrG6LKtKD2H/n2 A43w==
X-Gm-Message-State: AMCzsaVWllnUW9+TECWJVFoIiXaYmYEjQjqR7JzMSD8mmNiKFTpyS2tG PPdyGZ9jYlVrw1kwIt6+ppvVqg7Hbgu2yKRl3bc=
X-Google-Smtp-Source: ABhQp+R9D7zwTalHeqYbMa5tdpp4xMDx7b0UpkG0SPq5vHdWO7SfcPySkirK2ymrOOJU/SJChPNiHfPKqAvT/OWemR4=
X-Received: by 10.31.157.7 with SMTP id g7mr5599537vke.130.1509066466115; Thu, 26 Oct 2017 18:07:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.38.130 with HTTP; Thu, 26 Oct 2017 18:07:25 -0700 (PDT)
In-Reply-To: <4c6c9bc8-6056-c03d-a0f6-f1f32fabef39@ericsson.com>
References: <3dbe94b9-4b2d-1479-8433-8b040cb1cfba@ericsson.com> <CAOW+2ds9Sez7otrs682hqzzXR8qbJYAdPwW8A8TEL+ms_a0=UA@mail.gmail.com> <ACE2CDE6-4D04-4049-BB15-1E82C214A553@gmail.com> <4c6c9bc8-6056-c03d-a0f6-f1f32fabef39@ericsson.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 26 Oct 2017 18:07:25 -0700
Message-ID: <CAOW+2dtzq4d5p3JxwbbdwHqrS+0TpRveJkGb3vYzmdmLVvdcFQ@mail.gmail.com>
To: Mohit Sethi <mohit.m.sethi@ericsson.com>
Cc: Yoav Nir <ynir.ietf@gmail.com>, reap@ietf.org, Security Area Advisory Group <saag@ietf.org>
Content-Type: multipart/alternative; boundary="001a1142d8d2a7c521055c7ceaf2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/reap/H9IC4qaN0Aj4sIDvMqGrWPZsI5Q>
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:07:49 -0000

Creating a separate list has real drawbacks and very little in the way of
benefits.

If your desire is to get feedback from EAP implementers, why not post on a
list they already subscribe to (such as EMU)?

Creating a new list is in effect requiring those people to actively decide
to pay attention to your work, rather than you bringing the work to them.

For a protocol that is more than 20 years old, with dozens of
implementations and billions of existing devices, this is not a sound way
to move forward.



On Thu, Oct 26, 2017 at 12:51 PM, Mohit Sethi <mohit.m.sethi@ericsson.com>;
wrote:

> Hi Yoav,
>
> Thanks for the feedback. This issue about the list had come up a short
> while back when Rick posted his draft on EAP-SASL to SAAG:
> https://mailarchive.ietf.org/arch/msg/saag/stEf0BxTPKGEJq-2RDrlKj1rxRc
>
> We thought that it would make sense to have a separate mailing list on all
> new EAP related work. This would also allow us to gauge the community
> interest in the new work.
> At the end of the day, I believe our objectives are the same: we want to
> work on things that the IETF as a community is interested in, and make sure
> that the work progresses at an acceptable pace.
>
> --Mohit
>
>
> On 10/26/2017 08:55 PM, Yoav Nir wrote:
>
>
>
> On 26 Oct 2017, at 18:51, Bernard Aboba <bernard.aboba@gmail.com>; wrote:
>
> There are existing functioning IETF mailing lists relating to EAP.
>
> Why are you starting yet another one?
>
>
> +1
>
> The EMU mailing list seems appropriate.
>
> Yoav
>
> https://tools.ietf.org/wg/emu/
> https://www.ietf.org/mail-archive/web/emu/current/maillist.html
>
>
>
> _______________________________________________
> REAP mailing listREAP@ietf.orghttps://www.ietf.org/mailman/listinfo/reap
>
>
>