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

Joseph Salowey <joe@salowey.net> Wed, 03 April 2019 05:37 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 2E152120499 for <emu@ietfa.amsl.com>; Tue, 2 Apr 2019 22:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 Aa2aLxK7ZNPz for <emu@ietfa.amsl.com>; Tue, 2 Apr 2019 22:37:40 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 AB880120019 for <emu@ietf.org>; Tue, 2 Apr 2019 22:37:40 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id v32so17859801qtc.10 for <emu@ietf.org>; Tue, 02 Apr 2019 22:37:40 -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 :cc; bh=L1qirsiO7qLSu88vtq6zX7PE4zJmiATrx/MkSzZ3CRs=; b=DLfF87jImqIjy9Eh52PeDiyD0jXTa68mlAztfVYd1kuElLVrWF5MSYJEYPEWqKBANZ 92uKoVzlrr9CAlOYT52UqQpV5dSQnV3Uzj3WX1OY2N8jiOeM3q2ZIZkf/vWLptKHu1SM Qeh7nYkU2qv9jr7vr1EeIM/11OArWJ00wfVi+4e6vaMV9xDMQvmtgvce/Pi5+rXzVoh2 LZjJ28DeyBVqhh1wL+Sxaz5CLo0mi4hMZ/AsdfsNl6y6PwVeRsgpft9rdNwKO018/FAE cs13hiIKX5bHXg1pSztZogvZuGXWTanUnTANVIrlVEZe21SBvzDLb7FMdq2VRijC2WtB zMjw==
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:cc; bh=L1qirsiO7qLSu88vtq6zX7PE4zJmiATrx/MkSzZ3CRs=; b=S4rtk2275FqkhUMpqH2/4Tw18Ct4s92b6qGeJ9cPdo41M3QO6rP5yG1rXh86qzpo9F nP2CmTJ2L3RunE1jQ5fYcSaMx6/J484VfA0Y3qgyNIA8gIRE2Hz4MomMxThh4ybfpwNV PTumNvSVBUThSA0k/PnFRZvfu/eFWZnx5VYSRhCFvusW4fGNarYY2+lvphuoDJ/co/vb C30d2TQU6dUb6gpJlS4SysV3XKUi3dBkmGwGz1G9XNDIycY1EgxNT8RFXyOYyhKNNf+i U2kp46D1zIFIJH7IvHuMKqRo1n2/3pd27Kh+iUX5VjcuDMIFQuNGTtLfknTnetqDl8k4 4LDQ==
X-Gm-Message-State: APjAAAXpvLrraQ3I0bFir22zVoizqVTdmMfOLVjM7A8fm8hhDAhRjqY9 kkebiz4RVv8PFrEnQqkkF9B8/uHC+HmaEoQsYfYqVHj7lpuWVg==
X-Google-Smtp-Source: APXvYqwpZV2tvPBPu0qVjO9nPZUc9WtNwYjJg1XnsiCsp0+DeAF2Vd7xNMkXM2cb7egMukbY+2dNw6zErU6W+5jIeQc=
X-Received: by 2002:a0c:949c:: with SMTP id j28mr14222820qvj.18.1554269859660; Tue, 02 Apr 2019 22:37:39 -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>
In-Reply-To: <8549.1553993591@dooku.sandelman.ca>
From: Joseph Salowey <joe@salowey.net>
Date: Tue, 02 Apr 2019 22:37:28 -0700
Message-ID: <CAOgPGoAqwTb7f+YXCCK-xn9JNJopbL4TZ_8rD=XJF2=eB9zNJw@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: Alan DeKok <aland@deployingradius.com>, emu@ietf.org
Content-Type: multipart/alternative; boundary="000000000000dee34a058599a66c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/F1-pRqi6FrYk_rMT2YJbf3ZI8VQ>
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 05:37:45 -0000

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.

Thanks,
Joe



On Sat, Mar 30, 2019 at 5:53 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Alan DeKok <aland@deployingradius.com> wrote:
>     >   Let's be realistic about the IETF.  While we pretend that we have
>     > individual contributors, the reality is that large companies fund
> huge
>     > chunks of it.  Those companies effectively shield individual
>     > contributors from patent lawsuits.  i.e. no one will sue an employee
> of
>     > Cisco about a standard, they will instead sue Cisco directly.
>
> Actually, nobody seems to sue the majors except other majors.
> Nobody seems to sue small entities that have no money except patent trolls.
>
>     >   Michael and I have no such protection.  As an implementor of
> EAP-SIM
>     > and EAP-AKA, he may be personally liable.  As the person hosting the
>     > web site and source code, I may also be personally liable.
>
> I don't think you can be sued for patent infringemenet for writing about
> the patent, only for using it.    Copyright, yes, but not patents.
>
>     >   And realistically, Open Source has driven the explosion of tech
>     > companies in the past 10 years.  I think few companies could have
> been
>     > profitable if they had paid license fees for an OS, web server, etc.
>     > So there should be a vested interest in protecting open source as
> part
>     > of the IETF standardization process.
>
> I agree with you, and so it borders on seriously insulting to open source
> authors to have these super-vague IPR claims show up from non-technical
> lawyers.
>
> Let me restate my original opinion:
>    - if this is important to 5G, then anything that gets in the way of
>      adoption is a problem.  If it's not important enough to fix the IPR,
>      then it's actually that important.
>    - adopting AKA is very important.
>
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
> rails    [
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>