Re: [ipwave] RFC8691 and RFC8902

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 26 April 2021 16:55 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: its@ietfa.amsl.com
Delivered-To: its@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDD13A289E for <its@ietfa.amsl.com>; Mon, 26 Apr 2021 09:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.632
X-Spam-Level:
X-Spam-Status: No, score=-1.632 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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] 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 m9lSzgq1SZZf for <its@ietfa.amsl.com>; Mon, 26 Apr 2021 09:55:06 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 28C213A289C for <its@ietf.org>; Mon, 26 Apr 2021 09:55:05 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 13QGt2SL010533; Mon, 26 Apr 2021 18:55:02 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0062D206D92; Mon, 26 Apr 2021 18:55:02 +0200 (CEST)
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 E4003206D57; Mon, 26 Apr 2021 18:55:01 +0200 (CEST)
Received: from [10.14.5.141] ([10.14.5.141]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 13QGt1Yk007030; Mon, 26 Apr 2021 18:55:01 +0200
To: Mounira MSAHLI <msahli1717@gmail.com>
Cc: IPWAVE WG <its@ietf.org>
References: <3ef672fb-0eda-aad3-0bbd-31836f99acf2@gmail.com> <CAA2OGZAbwmgVw2w2p_1FAMjz0Z4_5Wknds+1v-NqbYbM1YJJcg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <970faf67-00b1-24b1-a2b0-7847491dd3a4@gmail.com>
Date: Mon, 26 Apr 2021 18:55:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <CAA2OGZAbwmgVw2w2p_1FAMjz0Z4_5Wknds+1v-NqbYbM1YJJcg@mail.gmail.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/its/GPid_NjyiVzOQ_COiOxsYcDza14>
Subject: Re: [ipwave] RFC8691 and RFC8902
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <its.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/its>, <mailto:its-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/its/>
List-Post: <mailto:its@ietf.org>
List-Help: <mailto:its-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/its>, <mailto:its-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 16:55:10 -0000


Le 26/04/2021 à 18:21, Mounira MSAHLI a écrit :
>>> Can TLS v2 run over IPv6 over 802.11 in OCB mode and use 1609.2
> certificates?
> 
> Why: IPv6 over 802.11 in OCB is not compatible with TLS 1.3 ?

In principle it should be, but has one tried it?

Then, if one tried it, did her (or him) try the RFC8902 extension?

Alex

> 
> Mounira
> 
> Le lun. 26 avr. 2021 à 17:33, Alexandre Petrescu 
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
> a écrit :
> 
> Can TLS v2 run over IPv6 over 802.11 in OCB mode and use 1609.2 
> certificates?
> 
> Until then, one cant publish text that says that "it is anticipated 
> that its [TLS extension's] use will be widespread."
> 
> I still wonder how could this document have been published as an
> RFC... it is way beyond my understanding... sorry to say so.
> 
> Alex
> 
> _______________________________________________ its mailing list 
> its@ietf.org <mailto:its@ietf.org> 
> https://www.ietf.org/mailman/listinfo/its 
> <https://www.ietf.org/mailman/listinfo/its>
>