Re: [ipwave] Request for Your Interest on a New BoF as a Follower of IPWAVE WG

Alexandre Petrescu <> Fri, 23 September 2022 07:44 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4BCA2C1524AF for <>; Fri, 23 Sep 2022 00:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: 1.357
X-Spam-Level: *
X-Spam-Status: No, score=1.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1.997] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Bjwzfj5GbsTP for <>; Fri, 23 Sep 2022 00:44:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 76F3CC14CE43 for <>; Fri, 23 Sep 2022 00:44:11 -0700 (PDT)
Received: from ( []) by (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 28N7i8I3051501 for <>; Fri, 23 Sep 2022 09:44:08 +0200
Received: from (localhost []) by localhost (Postfix) with SMTP id C44DF202ACA for <>; Fri, 23 Sep 2022 09:44:08 +0200 (CEST)
Received: from ( []) by (Postfix) with ESMTP id BB71220284E for <>; Fri, 23 Sep 2022 09:44:08 +0200 (CEST)
Received: from [] ([]) by (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 28N7i820034112 for <>; Fri, 23 Sep 2022 09:44:08 +0200
Message-ID: <>
Date: Fri, 23 Sep 2022 09:44:08 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
Content-Language: fr
References: <>
From: Alexandre Petrescu <>
In-Reply-To: <>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [ipwave] Request for Your Interest on a New BoF as a Follower of IPWAVE WG
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IPWAVE - IP Wireless Access in Vehicular Environments WG at IETF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Sep 2022 07:44:15 -0000

Hi, Paul,

Thank you for the proposal.

I am interested in this work.

I am happy to see this work as more than automobiles.  Because some
automotive manufacturers consider automobiles together with other pods
(moving objects) - automobiles assisted by drones, or automobiles
connected to multi-level hierarchies of airborne objects up to space.
Or automobiles that might fly themselves in Urban Air Mobility.

With respect to 5G: there is also a notion of 6G and automotive
verticals that is being developped.

So, yes, I am interested in IPMON.


Le 23/09/2022 à 01:59, Mr. Jaehoon Paul Jeong a écrit :
> Hi IPWAVE WG, I want to notify you of the effort of a new BoF to
> work on the problems and solutions that are addressed on our IPWAVE 
> Problem Statement Draft: 
> <>
I have submitted a BoF request to the IETF on September 8 as
> follows: 
> This BoF is called IPv6 Moving Object Networking (ipmon) and it tries
> to accommodate more moving objects (e.g., terrestrial vehicles,
> aerial vehicles, and marine vehicles) for safe driving with IPv6
> wireless networking.
> Here is the Charter of IPMON BoF: 
> ---------------------------------------------- IPv6 Moving Object 
> Networking (ipmon)
> --- Charter for Working Group
> Moving objects of terrestrial vehicles (e.g., automobiles, 
> motorcycles, and electric scooters), aircrafts (e.g., unmanned
> aerial vehicle (UAV) like drones, airplanes, and helicopters),
> watercrafts (e.g., boats, ships, and submarines), and mobile robots
> for smart buildings are increasingly connected to the Internet
> through various wireless communications.  Comfort-enhancing
> entertainment applications, driving/flying/sailing safety
> applications using bidirectional data flows, and connected automated
> maneuvering are some of the new features expected in moving objects
> (denoted as vehicles in this charter) to hit the movement spaces
> (e.g., roadway, street, sky, river, and sea) from now to year 2022.
> Today, there is Vehicle-to-Everything (V2X) communications that
> makes use of embedded Internet modules, or an occupant's cellular 
> smartphone in vehicular networks. Vehicle-to-Infrastructure (V2I) 
> communications is used for wireless exchange of critical safety and 
> operational data between vehicles and infrastructure nodes (e.g., 
> road-side units and edge computing devices), intended primarily to 
> avoid vehicle crashes and road hazards.  Similarly, 
> Vehicle-to-Vehicle (V2V) communications is used for short-range 
> communications between vehicles to exchange vehicle information such 
> as vehicle speed, heading, braking status, and collision situations.
>  Also, Vehicle-to-Pedestrian (V2P) communications is used for 
> short-range communications between vehicles and pedestrians' mobile 
> devices (e.g., smartphone and smart watch) to exchange street
> context information such as the existence of moving objects (e.g.,
> cars, trucks, pedestrians, bikes, motorcycles, and electric scooters)
> and collision situations.
> This group will work on use cases of V2X (e.g., V2V, V2I, and V2P) 
> where IPv6 is well-suited as a networking technology and will
> develop IPv6-based solutions to establish direct and secure
> connectivity among moving objects or among moving objects and
> stationary systems. These vehicular networks are characterized by
> dynamically changing network topologies and connectivity.
> V2V and V2I communications may involve various kinds of link layers: 
> 802.11-OCB (Outside the Context of a Basic Service Set), 802.15.4 
> with 6lowpan, 802.11ad, VLC (Visible Light Communications), IrDA, 
> LTE-D, LP-WAN, UWB, and 5G V2X.  One of the most used link layers
> for vehicular networks is IEEE 802.11-OCB, as a basis for Dedicated 
> short-range communications (DSRC). Several of these link-layers 
> already provide support for IPv6. IPv6 on 802.11-OCB has been fully 
> defined by IPWAVE WG since 2019. However, IPv6 on 5G V2X needs to be 
> fully defined by this working group. Some aspects of the IPv6 over
> 5G V2X have been already defined at 3GPP specification and the 
> specification produced by this working group is expected to be 
> compatible with these aspects.
> This group's primary deliverable (and the only Standards track item) 
> will be a document that will specify the mechanisms for transmission 
> of IPv6 datagrams over 3GPP 5G V2X. Once this document is completed, 
> it will also be reviewed by the 6man working group. Along with this 
> work, the following key technologies, which are identified by IPWAVE 
> WG's problem statement and use cases document, need to be 
> standardized for moving objects as follows.
> Program of Work ===============
> The IPMON working group's deliverables include:
> 1. Basic Support for IPv6 over 5G V2X 2. Vehicular Neighbor Discovery
> 3. Vehicular Mobility Management 4. Vehicular Security and Privacy 5.
> Context-Aware Navigation Protocol for Physical Collision Avoidance in
> Vehicular Networks 6. Service Discovery for Moving Objects 7. DNS
> Naming for Moving Objects 
> ----------------------------------------------
> My SKKU team is working for IETF-115 Hackathon Project for "Basic 
> Support for IPv6 over 5G V2X" and "Context-Aware Navigation Protocol"
> for drones in London.
> Let's gather NEW ENERGY for this new BoF.
> If you have interest and support in this new BoF, please let us 
> know.
> Thanks.
> Best Regards, Paul -- =========================== Mr. Jaehoon (Paul) 
> Jeong, Ph.D. Associate Professor Department Head Department of 
> Computer Science and Engineering Sungkyunkwan University Office: 
> +82-31-299-4957 Email: 
> <>, 
> <> Personal Homepage: 
> <>
> _______________________________________________ its mailing list