Re: [Lake] Protocol name change from EDHOC to LAKE?

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 24 August 2022 19:31 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: lake@ietfa.amsl.com
Delivered-To: lake@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74868C14F75F for <lake@ietfa.amsl.com>; Wed, 24 Aug 2022 12:31:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.007
X-Spam-Level:
X-Spam-Status: No, score=-4.007 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (OpenSSL error: data too large for modulus)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVnE1U3NeIgv for <lake@ietfa.amsl.com>; Wed, 24 Aug 2022 12:31:36 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94838C14F72D for <lake@ietf.org>; Wed, 24 Aug 2022 12:31:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C925518017; Wed, 24 Aug 2022 15:51:37 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mSnuwbbRmEuD; Wed, 24 Aug 2022 15:51:36 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5DD8118010; Wed, 24 Aug 2022 15:51:36 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1661370696; bh=RWPXo4AHGOPH3SrTDxRwZpM4d9HhVEOozu9ipSeNyEE=; h=From:To:cc:Subject:In-Reply-To:References:Date:From; b=2yHb5O0iUx6/Z0CgTeD0DwVlngdWCmb3NqFlX9nsyApksYpdz2iy3Cm4y8VnfIuRV A5n3AuQecIW3bG0st8SGoNe9DXrYveqJOrz2mv9Yggj2iXzL4KbgOnJ8KJd4ok5D6g FemeD04lux39gL5kHuSWOPBFDEgPR6keDoLhOoknQ1FMR0K8RcmdeiccIoRU83fw0f ck9Uy/Pjny2PlMvbBCOYPPUUzjnZE3nDS7YkU23/CGVxw/yLEiR+yW9vag7uH7P5QA kGk//8KfX0WQIEw50IHM8BpKXkvPN0dogF7hbCsIQYhSz73ZrhuAp+/2sBbt4vO61F zquV4mrW3lDhA==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B7DFCFC; Wed, 24 Aug 2022 15:31:33 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: =?utf-8?B?TWFsacWhYSBWdcSNaW5pxIc=?= <malisa.vucinic@inria.fr>
cc: lake@ietf.org
In-Reply-To: <20FE188B-BC22-4D68-BAAF-A3C7ABCFB422@inria.fr>
References: <20FE188B-BC22-4D68-BAAF-A3C7ABCFB422@inria.fr>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 24 Aug 2022 15:31:33 -0400
Message-ID: <22862.1661369493@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/lake/UGMhD9XU1RoQ4eJiRBnuTLJXwWU>
Subject: Re: [Lake] Protocol name change from EDHOC to LAKE?
X-BeenThere: lake@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Lightweight Authenticated Key Exchange <lake.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lake>, <mailto:lake-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lake/>
List-Post: <mailto:lake@ietf.org>
List-Help: <mailto:lake-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lake>, <mailto:lake-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Aug 2022 19:31:41 -0000

Mališa Vučinić <malisa.vucinic@inria.fr> wrote:
    > The goal of this email is to seek input from the mailing list on the
    > subject of the protocol name change from EDHOC to LAKE.

    > For some time now, we noticed that people external to the working group
    > have been referring to EDHOC simply as LAKE. One example is the paper
    > at [1].

I don't object to changing the name.

But, I think the storey of the brown-M&Ms is relevant, and RFC4301 has an
equivalent of brown M&Ms for _IPsec_ in the Introduction.

https://en.wikipedia.org/wiki/Van_Halen#Contract_riders
https://www.entrepreneur.com/article/232420

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide