Re: [ipwave] 802.11bd and Re: RFC 8691 on Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 17 March 2023 15:44 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 BC9E0C15152E for <its@ietfa.amsl.com>; Fri, 17 Mar 2023 08:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.33
X-Spam-Level:
X-Spam-Status: No, score=-2.33 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1.999] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6L1AmIXQj0y0 for <its@ietfa.amsl.com>; Fri, 17 Mar 2023 08:44:07 -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 9B2E0C15154F for <its@ietf.org>; Fri, 17 Mar 2023 08:44:07 -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 32HFi4mV036576; Fri, 17 Mar 2023 16:44:04 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 2AE1D207FE6; Fri, 17 Mar 2023 16:44:04 +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 19203207F49; Fri, 17 Mar 2023 16:44:04 +0100 (CET)
Received: from [10.8.32.70] (is156570.intra.cea.fr [10.8.32.70]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 32HFi3DF063637; Fri, 17 Mar 2023 16:44:04 +0100
Message-ID: <7f53c932-7fc5-ec8f-3f0f-11267db45b45@gmail.com>
Date: Fri, 17 Mar 2023 16:44:03 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
Content-Language: fr
To: Hesham ElBakoury <helbakoury@gmail.com>
Cc: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, IPWAVE WG <its@ietf.org>
References: <20191227182344.7B001F40742@rfc-editor.org> <b65ae582-e34f-d6b2-4543-e246d32b594b@gmail.com> <CAPK2DexjVcdsrW6re7-O1fRJF3RXj+NUMQ_ahu-2BcGJo9bAfQ@mail.gmail.com> <8dd2aab0-2674-c217-4b2d-ccba688bbbe7@gmail.com> <CAFvDQ9q1xXMkHMYa6nOAGwKF82ydmQRKHfYZoYehE9k=WXKL5g@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <CAFvDQ9q1xXMkHMYa6nOAGwKF82ydmQRKHfYZoYehE9k=WXKL5g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/41ddwWxiunUR8VNsu9SyW4efJVs>
Subject: Re: [ipwave] 802.11bd and Re: RFC 8691 on Basic Support for IPv6 Networks Operating Outside the Context of a Basic Service Set over IEEE Std 802.11
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 17 Mar 2023 15:44:12 -0000


Le 17/03/2023 à 15:45, Hesham ElBakoury a écrit :
> Dorthy 802.11 chair announced the availability of 802.11bd spec using 
> this link
> https://ieee-sa.imeetcentral.com/p/eAAAAAAASZngAAAAAAEc-8c 
> <https://ieee-sa.imeetcentral.com/p/eAAAAAAASZngAAAAAAEc-8c>

Thanks for the link.  It worked for me, I can see the document.  I 
suspect that access is only for standards work, which is good.

I searched for keywords such as IP, or RFC, but could not find anything. 
  The only relevant protocol keyword I could find is SNMP.

In a sense, this is good, meaning that IP will work on it ok.

In another sense, one can legitimately ask why SNMPv2 is there without 
saying which RFC (just another acronym among the thousand other 
acronyms), without telling whether SNMP runs over IP over 802.11bd or 
maybe SNMP/IP over another link towards that computer with .bd interface.

Thanks again for the link.

Alex


> 
> Hesham
> 
> On Fri, Mar 17, 2023, 7:39 AM Alexandre Petrescu 
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
> 
>     Hi,
> 
>     I learn today that the  IEEE 802.11bd spec is out, with a fee-based
>     availability at
>     https://www.techstreet.com/standards/ieee-802-11bd-2022?product_id=2251332 <https://www.techstreet.com/standards/ieee-802-11bd-2022?product_id=2251332>
> 
>     A brief description of its status comes from CITS of ITU today, freely
>     available at this URL
>     https://www.itu.int/en/ITU-T/extcoop/cits/Documents/Meeting-20230317-e-meeting/17_IEEE_802-11_TGbd_status_report.pdf <https://www.itu.int/en/ITU-T/extcoop/cits/Documents/Meeting-20230317-e-meeting/17_IEEE_802-11_TGbd_status_report.pdf>
> 
>     One might note 10 and 20MHz channel widhts, 256QAM code capability, and
>     others, all meaning a significant increase in bandwidth for end users
>     (more than .11p at around 16mibt/s).  It is probably in the range of the
>     gbit/s.
> 
>     Hopefully the implementations of RFC8691 IPv6-over-OCB work equally well
>     on 802.11bd MAC implementations, as they worked on older 802.11p.
> 
>     Alex
> 
>     Le 23/09/2022 à 14:52, Mr. Jaehoon Paul Jeong a écrit :
>      > Alex, Sure, it will be valuable to check the latest 802.11bd
>      > specification for RFC8691 even though the current RFC8691 will be
>      > okay for both 802.11-OCB and 802.11bd. I will upload the IPMON
>      > Charter to include 802.11bd as a possible L2/L1 protocol.
>      >
>      > Thanks.
>      >
>      > Best Regards, Paul
>      >
>      > 2022년 9월 23일 (금) 오후 9:39, Alexandre Petrescu
>      > <alexandre.petrescu@gmail.com
>     <mailto:alexandre.petrescu@gmail.com>
>     <mailto:alexandre.petrescu@gmail.com
>     <mailto:alexandre.petrescu@gmail.com>>>님
>      > 이 작성:
>      >
>      > Hi, IPWAVErs,
>      >
>      > The IEEE 802.11bd is an evolution along the lines of 802.11-OCB.
>      >
>      > It might be worthwhile to check whether RFC 8691 "IPv6 over OCB"
>      > works ok over an 802.11bd SAP interface with upper layers.
>      >
>      > To that end, it might be worth checking the most recent 802.11bd
>      > specification text.
>      >
>      > Do you think this check would be appropriate?
>      >
>      > Alex
>      >
>      > Le 27/12/2019 à 19:23, rfc-editor@rfc-editor.org
>     <mailto:rfc-editor@rfc-editor.org>
>      > <mailto:rfc-editor@rfc-editor.org
>     <mailto:rfc-editor@rfc-editor.org>> a écrit :
>      >> A new Request for Comments is now available in online RFC
>      >> libraries.
>      >>
>      >>
>      >> RFC 8691
>      >>
>      >> Title:      Basic Support for IPv6 Networks Operating Outside the
>      >> Context of a Basic Service Set over IEEE Std 802.11 Author:     N.
>      >> Benamar, J. Härri, J. Lee, T. Ernst Status:     Standards Track
>      >> Stream:     IETF Date:       December 2019 Mailbox:
>      >> n.benamar@est.umi.ac.ma <mailto:n.benamar@est.umi.ac.ma>
>      > <mailto:n.benamar@est.umi.ac.ma <mailto:n.benamar@est.umi.ac.ma>>,
>      >> jerome.haerri@eurecom.fr <mailto:jerome.haerri@eurecom.fr>
>     <mailto:jerome.haerri@eurecom.fr <mailto:jerome.haerri@eurecom.fr>>,
>      >> jonghyouk@smu.ac.kr <mailto:jonghyouk@smu.ac.kr>
>     <mailto:jonghyouk@smu.ac.kr <mailto:jonghyouk@smu.ac.kr>>,
>      >> thierry.ernst@yogoko.fr <mailto:thierry.ernst@yogoko.fr>
>     <mailto:thierry.ernst@yogoko.fr <mailto:thierry.ernst@yogoko.fr>> Pages:
>      >> 29 Updates/Obsoletes/SeeAlso:   None
>      >>
>      >> I-D Tag:    draft-ietf-ipwave-ipv6-over-80211ocb-52.txt
>      >>
>      >> URL: https://www.rfc-editor.org/info/rfc8691
>     <https://www.rfc-editor.org/info/rfc8691>
>      > <https://www.rfc-editor.org/info/rfc8691
>     <https://www.rfc-editor.org/info/rfc8691>>
>      >>
>      >> DOI:        10.17487/RFC8691
>      >>
>      >> This document provides methods and settings for using IPv6 to
>      >> communicate among nodes within range of one another over a single
>      >> IEEE 802.11-OCB link. Support for these methods and settings
>      >> require minimal changes to existing stacks. This document also
>      >> describes limitations associated with using these methods.
>      >> Optimizations and usage of IPv6 over more complex scenarios are not
>      >> covered in this specification and are a subject for future work.
>      >>
>      >> This document is a product of the IP Wireless Access in Vehicular
>      > Environments Working Group of the IETF.
>      >>
>      >> This is now a Proposed Standard.
>      >>
>      >> STANDARDS TRACK: This document specifies an Internet Standards
>      >> Track protocol for the Internet community, and requests discussion
>      >> and
>      > suggestions
>      >> for improvements.  Please refer to the current edition of the
>      > Official
>      >> Internet Protocol Standards
>     (https://www.rfc-editor.org/standards
>     <https://www.rfc-editor.org/standards>
>      > <https://www.rfc-editor.org/standards
>     <https://www.rfc-editor.org/standards>>) for the
>      >> standardization state and status of this protocol.  Distribution
>      > of this
>      >> memo is unlimited.
>      >>
>      >> This announcement is sent to the IETF-Announce and rfc-dist lists.
>      >> To subscribe or unsubscribe, see
>      >> https://www.ietf.org/mailman/listinfo/ietf-announce
>     <https://www.ietf.org/mailman/listinfo/ietf-announce>
>      > <https://www.ietf.org/mailman/listinfo/ietf-announce
>     <https://www.ietf.org/mailman/listinfo/ietf-announce>>
>      >> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>     <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>
>      > <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>     <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>>
>      >>
>      >> For searching the RFC series, see
>      > https://www.rfc-editor.org/search <https://www.rfc-editor.org/search>
>      > <https://www.rfc-editor.org/search
>     <https://www.rfc-editor.org/search>>
>      >> For downloading RFCs, see
>      > https://www.rfc-editor.org/retrieve/bulk
>     <https://www.rfc-editor.org/retrieve/bulk>
>      > <https://www.rfc-editor.org/retrieve/bulk
>     <https://www.rfc-editor.org/retrieve/bulk>>
>      >>
>      >> Requests for special distribution should be addressed to either
>      >> the author of the RFC in question, or to
>     rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>
>      > <mailto:rfc-editor@rfc-editor.org
>     <mailto:rfc-editor@rfc-editor.org>>.  Unless
>      >> specifically noted otherwise on the RFC itself, all RFCs are for
>      >> unlimited distribution.
>      >>
>      >>
>      >> The RFC Editor Team Association Management Solutions, LLC
>      >>
>      >>
>      >> _______________________________________________ IETF-Announce
>      >> mailing list IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>
>      >> <mailto:IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>>
>      >> https://www.ietf.org/mailman/listinfo/ietf-announce
>     <https://www.ietf.org/mailman/listinfo/ietf-announce>
>      > <https://www.ietf.org/mailman/listinfo/ietf-announce
>     <https://www.ietf.org/mailman/listinfo/ietf-announce>>
>      >
>      > _______________________________________________ its mailing list
>      > its@ietf.org <mailto:its@ietf.org> <mailto:its@ietf.org
>     <mailto:its@ietf.org>>
>      > https://www.ietf.org/mailman/listinfo/its
>     <https://www.ietf.org/mailman/listinfo/its>
>      > <https://www.ietf.org/mailman/listinfo/its
>     <https://www.ietf.org/mailman/listinfo/its>>
>      >
>      > -- =========================== Mr. Jaehoon (Paul) Jeong, Ph.D.
>      > Associate Professor Department Head Department of Computer Science
>      > and Engineering Sungkyunkwan University Office: +82-31-299-4957
>      > Email: pauljeong@skku.edu <mailto:pauljeong@skku.edu>
>     <mailto:pauljeong@skku.edu <mailto:pauljeong@skku.edu>>,
>      > jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>
>     <mailto:jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>> Personal
>      > Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
>     <http://iotlab.skku.edu/people-jaehoon-jeong.php>
>      > <http://cpslab.skku.edu/people-jaehoon-jeong.php
>     <http://cpslab.skku.edu/people-jaehoon-jeong.php>>
> 
>     _______________________________________________
>     its mailing list
>     its@ietf.org <mailto:its@ietf.org>
>     https://www.ietf.org/mailman/listinfo/its
>     <https://www.ietf.org/mailman/listinfo/its>
>