Re: [Emu] EAP-AKA' and Re: WG adoption call for draft-arkko-eap-aka-pfs

Joseph Salowey <joe@salowey.net> Thu, 27 June 2019 16:51 UTC

Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 243F3120125 for <emu@ietfa.amsl.com>; Thu, 27 Jun 2019 09:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=salowey-net.20150623.gappssmtp.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 QbwzstvHgtlk for <emu@ietfa.amsl.com>; Thu, 27 Jun 2019 09:51:19 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 6A2EC120112 for <emu@ietf.org>; Thu, 27 Jun 2019 09:51:19 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id t8so2332388qkt.1 for <emu@ietf.org>; Thu, 27 Jun 2019 09:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=eq9ciiym0IprEnqi/eJoXeoa9nZEW7qN/gl7mwBR9fQ=; b=hJmNLxNPvMH3bP4tQIaXYYCpxCAbtAnlxK9KFN6IgSZ1xTL1nzHuaMin/nGG4xxCZT aMCFTnacIhvQ++TWGEIXr3NU/lKiZAqU16y/W0jJ/ePUWv0XNlCB8JAENVmKgIKBql7q vR7OJILeJ0jrE/htFuJy8H6a2QJ+NalKZrO4uUoGNK+X+Cx2/GrsEpZu1Zzd4TzBvMgi ZijntyJmybClkoBVnjMcABWuivjD0j9hfXBLK6CuKnvNNx4Nn03pReXTF2UNm0N6oOjB OCLGK7xNVo3wm4Aak1225QTQrd33PPz1rtBPu8sTY7vhRltrJCoEALgHzbq8lX2dVIDh rsYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=eq9ciiym0IprEnqi/eJoXeoa9nZEW7qN/gl7mwBR9fQ=; b=MoeevnefixptLKCB7xqsgvbmDzhjH0S+h0G9LIh4MUlJshYWEHkeKSxu+SmOlxAVvf ybUrax01Y9GkI6NOoiCvk49qY+zG8YmEFegwesxtDTijiNT6/x4EUrGZxUbDIq/1wanQ 195BdrxNx0ws4vrMthE8GZ6Ry0lLUKXfouMTA0HR01yJUtG3/E5T7+MRCQJZvJL7Yz7R zjxAuogL2Yn01eR7h09BI7iFIXskoxMybBTaMyHD98EnVgOCF7zgeqBZRs0d42xR02e/ HBJxDZ4xK5FFYhzEZUUOBB7kWWSrWtS21svlZaJpn9eUxMzVrAOraLlHHWvFQs4QDi8v ljug==
X-Gm-Message-State: APjAAAWR7VbKueZhdrfoba2goTo7gyBZBEDD1tVo+bBx73DxPgMH4YBq sdXjNXKhath2yNjUF7zNtVQ1b5gNNRQmqUF8NnoReiDlrDlWFQ==
X-Google-Smtp-Source: APXvYqxI6bdrH6sU+VzeS58VXjE+gTQIA8xrsGmhtBWkc57xMx3skX1f+4bJn0zHyYUlD6lZI/rwvAdemlgSxw7zc0E=
X-Received: by 2002:a37:2d43:: with SMTP id t64mr4169835qkh.472.1561654278296; Thu, 27 Jun 2019 09:51:18 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBGZWbyHYybnMUbKG77Mei3yBOS1HyS4Uso1HKgxq1VNg@mail.gmail.com> <20357.1553893062@dooku.sandelman.ca> <3A358E18-F3C3-40FF-BF87-DEB963549BE8@deployingradius.com> <8549.1553993591@dooku.sandelman.ca> <CAOgPGoAqwTb7f+YXCCK-xn9JNJopbL4TZ_8rD=XJF2=eB9zNJw@mail.gmail.com> <D70048FC-98FA-4AEC-B215-D8DD5F19441F@deployingradius.com>
In-Reply-To: <D70048FC-98FA-4AEC-B215-D8DD5F19441F@deployingradius.com>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 27 Jun 2019 09:51:06 -0700
Message-ID: <CAOgPGoDek68-Rmpz54McNiZDMR1NKQiBXSD0WYQi25Uoab+LaQ@mail.gmail.com>
To: emu@ietf.org
Content-Type: multipart/alternative; boundary="000000000000852806058c50f8ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/xq52qQ4JqkN-3P8IEXNL0lMCjnE>
Subject: Re: [Emu] EAP-AKA' and Re: WG adoption call for draft-arkko-eap-aka-pfs
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2019 16:51:22 -0000

Significant time has passed and no alternate proposals have surfaced.  We
need to decide whether to accept this document into the working group or
not.  It seems that we have support for the view that working on this
informational document in the working group is preferable to the
independent submission track.

Do working group members still have objections to taking this draft into
the working group?   Please respond on this thread by July 5, 2019.

Thanks,

Joe

On Wed, Apr 3, 2019 at 4:59 AM Alan DeKok <aland@deployingradius.com> wrote:

> On Apr 3, 2019, at 1:37 AM, Joseph Salowey <joe@salowey.net> wrote:
> >
> > Thanks for reviving this thread.  I agree this is important work, but we
> need to have consensus to bring the item into the working group.  I think
> the IPR issue is the main sticking point.
> >
> > I'll note that RFC 5448 has a similar IPR declaration and both documents
> are targeted as informational.   Some possible ways forward:
> >
> > 1. Come up with an alternative proposal.  Since no one has already
> stepped forward I don't think this is realistic.
> > 2. Accept the document into the working group.
> > 3. Reject the document, which will force the work to go through the
> independent submission process, which will probably result in less broad
> and thorough review.
> > 4. Amendment to the license terms of the IPR - I have received no
> indication that this will happen
> >
> > The document will likely get published in either case 2 or 3 above.  I'd
> like to work through this discussion over the next few weeks so please
> voice your views on this thread.
>
>   Despite my misgivings, I think (2) is necessary here.
>
>   It would be helpful for the IETF as a whole to acknowledge the
> importance of Open Source in the IETF process.  And, that "RAND" licensing
> isn't necessarily RAND when fees are involved.
>
>   e.g. "Reasonable and Non-Discriminatory License to All Implementers with
> Possible Royalty/Fee"
>
>   OK, *what* is that fee?  A million dollars for a 5G operator / vendor?
> How much should an Open Source implementation pay?
>
>   Alan DeKok.
>
>