Re: [ieee-ietf-coord] RFC8691 and 802.11bd
Peter Yee <peter@akayla.com> Thu, 15 July 2021 20:39 UTC
Return-Path: <peter@akayla.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 D28173A1704 for <ieee-ietf-coord@ietfa.amsl.com>; Thu, 15 Jul 2021 13:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 zCnoGLxmTeJ1 for <ieee-ietf-coord@ietfa.amsl.com>; Thu, 15 Jul 2021 13:39:06 -0700 (PDT)
Received: from p3plsmtpa12-03.prod.phx3.secureserver.net (p3plsmtpa12-03.prod.phx3.secureserver.net [68.178.252.232]) (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 C20083A1703 for <ieee-ietf-coord@ietf.org>; Thu, 15 Jul 2021 13:39:06 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with ESMTPSA id 488Pma0wAPx4U488PmNCkJ; Thu, 15 Jul 2021 13:39:06 -0700
X-CMAE-Analysis: v=2.4 cv=ZazYiuZA c=1 sm=1 tr=0 ts=60f09cea a=PF7/PIuz6ZQ4FM3W1XNKAQ==:117 a=PF7/PIuz6ZQ4FM3W1XNKAQ==:17 a=DAwyPP_o2Byb1YXLmDAA:9 a=dHJOhkScAAAA:8 a=o83nqyVRAAAA:8 a=1RTuLK3dAAAA:8 a=48vgC7mUAAAA:8 a=5R2cvvbXnyDgmQ8DCM0A:9 a=QEXdDO2ut3YA:10 a=cjb5Hk3kT-kA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=3Sk6hF-tu6dG4sQdUUAA:9 a=xYqZEZ0eU9ozuwO3:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=0Jc9p3VZYLcdQ-t9l-12:22 a=kRpfLKi8w9umh8uBmg1i:22 a=w1C3t2QeGrPiZgrLijVG:22
X-SECURESERVER-ACCT: peter@akayla.com
From: Peter Yee <peter@akayla.com>
To: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, ieee-ietf-coord@ietf.org
Cc: 'Thierry Ernst' <thierry.ernst@yogoko.fr>
References: <22460712-eacf-8b13-dd65-4347801fc348@gmail.com>
In-Reply-To: <22460712-eacf-8b13-dd65-4347801fc348@gmail.com>
Date: Thu, 15 Jul 2021 13:39:12 -0700
Message-ID: <008201d779b9$78ab93a0$6a02bae0$@akayla.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0083_01D7797E.CC4DCD10"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFaAJ/HiABAkBewPlDu9fAjmVG/b6w/YDkQ
Content-Language: en-us
X-CMAE-Envelope: MS4xfB+rIGfwVPL5cx0V2JQXSxlf+2xDTOkNuc+JY5M/t6I9/vNIqahgvsv2RyPldPzRKLfAeKECcKqegeGJuZEO5ZTNsqDPaPBE2wzkRiQ4fdKiAmFCqoiJ bqnl4jNhKdp3obQZu69CZvXVcizCHkLLE0St68zz/Yup1c/eeNoYROdXqPUJbWGxw8SiBphDayTVKXSCVSmQSDbrsG/sIJTgdyX4lzYkCNzj3SlhO+eAD2+D LacCfNHsW+g9OnTdpXfQFQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/ATX7T3X_Vbafe5FOhedSxtG0Aac>
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: Thu, 15 Jul 2021 20:39:12 -0000
Hi, Alex, I’m the IEEE 802.11 liaison to the IETF. I just checked Draft 2.0 of IEEE 802.11, which was made available to IEEE 802.11 members today. It makes no mention of IPv6 at all. There are no mentions of Internet Protocol either. That’s not surprising given that IEEE 802.11bd focuses on the MAC and PHY layers. If you feel that IEEE 802.11bd ought to have a concrete tie to IPv6 and RFC 8691, you are certainly welcome to pitch the idea to IEEE 802.11 Task Group bd. The task group holds frequent teleconferences and there’s no registration or payment required to participate at that level. The calendar of meetings can be found at https://www.ieee802.org/11/. The next TGbd meeting appears to be 27 July. Unfortunately, you just missed their sessions earlier this week during the IEEE 802 plenary meeting. As for your hurdles below, let me reply by saying: 1. Please check with Dorothy Stanley (IEEE 802.11 WG chair) and see if she will make a dispensation to grant you access to the latest IEEE 802.11bd draft. The task group working documents (i.e., anything that is not the draft itself) are openly available at https://mentor.ieee.org/802.11/documents?is_dcn=DCN%2C%20Title%2C%20Author%20or%20Affiliation <https://mentor.ieee.org/802.11/documents?is_dcn=DCN%2C%20Title%2C%20Author%20or%20Affiliation&is_group=00bd> &is_group=00bd. 2. I don’t believe that IEEE 802.11 explicitly gives preference to IEEE 1609.3. While there is some overlap between the groups, I’m not aware of a required or de facto preference. Many in IEEE 802.11 are also members of the IETF and are quite aware of the strong ties between the protocol families. Should you wish to be put on the agenda for an upcoming IEEE 802.11 TGbd teleconference to discuss this topic, please send an email to the task group chair, Bo Sun, at sun.bo1@zte.com.cn <mailto:sun.bo1@zte.com.cn> . If you need additional assistance, please feel free to reach out to me directly as well. I will also mention this topic during my liaison report on the IETF during the IEEE 802.11 closing plenary session next Tuesday. Kind regards, -Peter Yee From: ieee-ietf-coord <ieee-ietf-coord-bounces@ietf.org> On Behalf Of Alexandre Petrescu Sent: Thursday, July 15, 2021 12:24 PM To: ieee-ietf-coord@ietf.org Cc: Thierry Ernst <thierry.ernst@yogoko.fr> Subject: [ieee-ietf-coord] RFC8691 and 802.11bd 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] RFC8691 and 802.11bd Alexandre Petrescu
- Re: [ieee-ietf-coord] RFC8691 and 802.11bd Peter Yee
- Re: [ieee-ietf-coord] RFC8691 and 802.11bd Alexandre Petrescu
- Re: [ieee-ietf-coord] RFC8691 and 802.11bd Peter Yee
- Re: [ieee-ietf-coord] RFC8691 and 802.11bd Alexandre Petrescu
- Re: [ieee-ietf-coord] RFC8691 and 802.11bd Peter Yee