Re: [EXTERNAL] Re: AERO/OMNI dropping support for SEND/CGA

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 02 December 2020 22:21 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C34E3A1585 for <ipv6@ietfa.amsl.com>; Wed, 2 Dec 2020 14:21:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level:
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=no 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 gGKE8uxI2ZQw for <ipv6@ietfa.amsl.com>; Wed, 2 Dec 2020 14:21:06 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FD8E3A157F for <ipv6@ietf.org>; Wed, 2 Dec 2020 14:21:03 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0B2MKwke031075; Wed, 2 Dec 2020 23:20:58 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5B6FD208663; Wed, 2 Dec 2020 23:20:58 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4D689201788; Wed, 2 Dec 2020 23:20:58 +0100 (CET)
Received: from [10.11.240.159] ([10.11.240.159]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0B2MKvvN009122; Wed, 2 Dec 2020 23:20:57 +0100
Subject: Re: [EXTERNAL] Re: AERO/OMNI dropping support for SEND/CGA
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, "ipv6@ietf.org" <ipv6@ietf.org>
References: <e9d391655a124688a121db7a6664d7bb@boeing.com> <efdbcaedd3264c00bd435abdb0ea5c3a@huawei.com> <6e8e4889-bba6-f1ce-b765-3a28a7b86f0d@gmail.com> <c16ce2b2b1284290b7bf39bfb798c2b0@boeing.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e6fcda7d-b48d-1d08-1a81-d2971413a99b@gmail.com>
Date: Wed, 02 Dec 2020 23:20:57 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <c16ce2b2b1284290b7bf39bfb798c2b0@boeing.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/db-zZd9DjNjxCst2MtQ5M8yXAvE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Dec 2020 22:21:07 -0000


Le 02/12/2020 à 20:07, Templin (US), Fred L a écrit :
>>> As Fernando pointed many times: many things in ND could be
>>> resolved only by digital signature (he calls it "untrusted
>>> model").
>> 
>> YEs yes.
> 
> Our plan and intention is to inherit the digital signature methods in
> Teredo. If there is anything wrong with that short of
> quantum-robustness, please speak up.

I am not a specialist of crypto but I heard of a contest at NIST(?)
about quantum resistant algorithms.  If I remember correctly, three
candidates were selected in July.  I am not sure where are they now;
maybe they already stepped further in the selection process.

But some of these candidates do have open source implementations, and
are not specified in RFCs.  If one has a crystal ball, one can decide
which of these algorithms will be the AES of the future and bring that
to OMNI.

(I hope I did not say too naïve things)

A respected crypto oppinion also says that it might be not necessary to
consider these as of now, or that it is too early.  For my part I think
it is never too early for these things.

Alex

> 
> We could have called what we are doing "TereTAP", or "ISAdo" but it
> is more than just that. So, we called it OMNI.
> 
> Fred
>