[ipwave] RFC8691 and RFC8902
Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 26 April 2021 15:33 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 376553A2548 for <its@ietfa.amsl.com>; Mon, 26 Apr 2021 08:33:51 -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, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, 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 8xUQZzgZDsaU for <its@ietfa.amsl.com>; Mon, 26 Apr 2021 08:33:48 -0700 (PDT)
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 59DE33A2547 for <its@ietf.org>; Mon, 26 Apr 2021 08:33:48 -0700 (PDT)
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 13QFXk5Y002748 for <its@ietf.org>; Mon, 26 Apr 2021 17:33:46 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3A2DE206C12 for <its@ietf.org>; Mon, 26 Apr 2021 17:33:46 +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 27C74206C0B for <its@ietf.org>; Mon, 26 Apr 2021 17:33:46 +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 13QFXjFR010896 for <its@ietf.org>; Mon, 26 Apr 2021 17:33:45 +0200
To: IPWAVE WG <its@ietf.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <3ef672fb-0eda-aad3-0bbd-31836f99acf2@gmail.com>
Date: Mon, 26 Apr 2021 17:33:45 +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
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/hFChtIv4tLNxdE19ksNhrFJnwXs>
Subject: [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 15:33:51 -0000
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
- [ipwave] RFC8691 and RFC8902 Alexandre Petrescu
- Re: [ipwave] RFC8691 and RFC8902 Mounira MSAHLI
- Re: [ipwave] RFC8691 and RFC8902 Alexandre Petrescu