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

Alan DeKok <aland@deployingradius.com> Wed, 03 April 2019 11:59 UTC

Return-Path: <aland@deployingradius.com>
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 87C89120089 for <emu@ietfa.amsl.com>; Wed, 3 Apr 2019 04:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, LOTS_OF_MONEY=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 geQbtLe7AsQn for <emu@ietfa.amsl.com>; Wed, 3 Apr 2019 04:59:46 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) by ietfa.amsl.com (Postfix) with ESMTP id D970F1200D5 for <emu@ietf.org>; Wed, 3 Apr 2019 04:59:45 -0700 (PDT)
Received: from [192.168.46.58] (198-84-237-221.cpe.teksavvy.com [198.84.237.221]) by mail.networkradius.com (Postfix) with ESMTPSA id A69595A3; Wed, 3 Apr 2019 11:59:43 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <CAOgPGoAqwTb7f+YXCCK-xn9JNJopbL4TZ_8rD=XJF2=eB9zNJw@mail.gmail.com>
Date: Wed, 03 Apr 2019 07:59:37 -0400
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, emu@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D70048FC-98FA-4AEC-B215-D8DD5F19441F@deployingradius.com>
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>
To: Joseph Salowey <joe@salowey.net>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/mTcX4wLwcsS5zOmMdGrGGbWvoMQ>
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: Wed, 03 Apr 2019 11:59:49 -0000

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.