Re: [ieee-ietf-coord] RFC8691 and 802.11bd

Alexandre Petrescu <alexandre.petrescu@gmail.com> Wed, 20 October 2021 07:05 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9FCC3A074E for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 20 Oct 2021 00:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.666
X-Spam-Level:
X-Spam-Status: No, score=0.666 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_MSPIKE_H2=-0.001, 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 0Rt6ivkyE5Er for <ieee-ietf-coord@ietfa.amsl.com>; Wed, 20 Oct 2021 00:05:00 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 64C8C3A05A7 for <ieee-ietf-coord@ietf.org>; Wed, 20 Oct 2021 00:05:00 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 19K74sdg008445; Wed, 20 Oct 2021 09:04:54 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 1C124202743; Wed, 20 Oct 2021 09:04:54 +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 0E839202744; Wed, 20 Oct 2021 09:04:54 +0200 (CEST)
Received: from [10.14.0.60] ([10.14.0.60]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 19K74rr7027483; Wed, 20 Oct 2021 09:04:53 +0200
To: Peter Yee <peter@akayla.com>
Cc: ieee-ietf-coord@ietf.org
References: <22460712-eacf-8b13-dd65-4347801fc348@gmail.com> <84ba94ac-2575-376a-37c2-52fb23dff289@gmail.com> <006801d7c50a$3732f430$a598dc90$@akayla.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <9ce956b9-f9f9-a9b7-17f1-f98319955134@gmail.com>
Date: Wed, 20 Oct 2021 09:04:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <006801d7c50a$3732f430$a598dc90$@akayla.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/ieee-ietf-coord/zLyjZWwdrcsH-T4FUcYFw6fQq1U>
Subject: Re: [ieee-ietf-coord] RFC8691 and 802.11bd
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2021 07:05:06 -0000

Peter,

Thanks for the clarification.  Sorry missing a first reply back in July,
despite careful attention.

It makes sense at MAC layer to stay independent of the upper layers,
including IP.

Some interactions might be helpful, though.  RFC8691 conditions the use
of .11 QoS headers for using IPv6, and as such one would like to make
sure .11bd is able to do these .11 QoS headers.  Otherwise IPv6 wont
work on .11bd, unhappily.

.11 documents often mention 'MIB' and sometimes might mention 'IP' or
'192.'.  That is a sign that .11 might depend on SNMP and further on IP,
even though not very explicitly.  If so (if .11bd D2 mentions 'MIB' or
'SNMP' or '192.') then one would like to make sure the current version
of IP is supported, explicitely.

Can I check that?

Alex



Le 19/10/2021 à 18:56, Peter Yee a écrit :
> Alex,
> 
> As I replied to your original message back in July, IEEE 802.11bd
> D2.0 does not mention IPv6 at all. It doesn't contain the term
> "Internet" either or any obvious reference to IPv6 through other
> terms such as "upper layer" or "higher layer".
> 
> -Peter
> 
> -----Original Message----- From: ieee-ietf-coord
> <ieee-ietf-coord-bounces@ietf.org> On Behalf Of Alexandre Petrescu 
> Sent: Tuesday, October 19, 2021 6:51 AM To: ieee-ietf-coord@ietf.org 
> Subject: Re: [ieee-ietf-coord] RFC8691 and 802.11bd
> 
> Does the 802.11bd D2.0 of July 2021 mention 'IPv6'?
> 
> Alex
> 
> Le 15/07/2021 à 21:24, Alexandre Petrescu a écrit :
>> Hi, participants to the IEEE-IETF coordination,
>> 
>> RFC8691 "IPv6 over OCB" is produced by the IPWAVE WG of IETF.  It 
>> describes the layering of the IPv6 network protocol on top of the 
>> 802.11 MAC in OCB mode.  This mode is the preferred mode of
>> operation for automobile networks that involve 802.11.  This OCB
>> mode is also known as 802.11p, and will be used in the future
>> 802.11bd to be released by IEEE in 2022.
>> 
>> I would like to say that it will be a great idea if the 802.11bd 
>> document cited RFC8691 whenever the former said 'IPv6'.  It would
>> be a perfect match.
>> 
>> How to achieve that goal?
>> 
>> I think there might be a few hurdles in achieving it:
>> 
>> - I do not have regular access to the 802.11bd ongoing
>> developments, and the latest documents.  I am not a member of the
>> IEEE respective group.
>> 
>> - some IEEE people often think that _if_ there is a network layer
>> in automobile networks, then that would first be the IEEE's
>> networking layer for it, which is IEEE 1609.3, and 'WSMP', which is
>> a different thing than the IP networking layer.  It might be that
>> IEEE gives preference to that networking layer instead of IP.
>> 
>> From an architecture point of view, I think there is no comparison
>> to be made between those two networking layers.  The IP networking
>> layer clearly has several advantages, scuh as its addressability
>> capacity and the forwarding of datagrams for scalability.
>> 
>> From an implementation point of view, I did see many
>> implementations of this IPv6-over-OCB (802.11p) running in many
>> automobile networks. An implementation of IPv6-over-OCB of 802.11bd
>> is only around the corner, not posing any significant challenge in
>> realization.
>> 
>> Maybe these worries are not really founded, and maybe it is
>> extremely easy to cite RFC8691 in 802.11bd.  But how to do it?
>> 
>> Alex
>> 
>> 
>> _______________________________________________ ieee-ietf-coord
>> mailing list ieee-ietf-coord@ietf.org 
>> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
>> 
> 
> _______________________________________________ ieee-ietf-coord
> mailing list ieee-ietf-coord@ietf.org 
> https://www.ietf.org/mailman/listinfo/ieee-ietf-coord
>