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

Yong-Geun Hong <> Mon, 26 September 2022 02:23 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 22C0AC1522B3 for <>; Sun, 25 Sep 2022 19:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.107
X-Spam-Status: No, score=-4.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, URI_DOTEDU=1.997] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tchKTgW9mD2b for <>; Sun, 25 Sep 2022 19:22:57 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1033]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 73CC0C14CE2E for <>; Sun, 25 Sep 2022 19:22:57 -0700 (PDT)
Received: by with SMTP id g1-20020a17090a708100b00203c1c66ae3so5391885pjk.2 for <>; Sun, 25 Sep 2022 19:22:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=2eckcY5oTxucNATPNay+vWQotN1Cdmr9tZasIRmxVHM=; b=iuWfFxYAJiMqnNWIKe/rrC8PgwTvHtDvSRlWYox223kFsj+3bFlGTRedTEKn9xjYuG ubF9daXlUxfX7B8enGI8n6nYv9tnxgwlVUPknwOMGo3HGwDCNChHzQvtOhl1toWWahJO 91FzGNq39L9RgmCHWUMiN0xWocNlhYfq8sTBX51hMkF9RpL3tfQzTyW8uG0WsZL81Byd AJCx6Jh2tSlhz2Bxwh3naKf9/RrXvkdkfHl1u2LPF1kHRsnJ0Lx6YLzHkDhK48PX9YpV GNr1Y9sKZnwyD6kyVNNpFugPmumO9lqIzIXeqX+luq9cVhCpEtBR1KLandqG1go40ikZ ZwDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=2eckcY5oTxucNATPNay+vWQotN1Cdmr9tZasIRmxVHM=; b=vjfIJt2hQU/ZohS6k11RcsELr15d0lpd4ibutOaZ+1+0VtckJ9qwGV2B/fP4FRqI2K 6tCXLU+OZEGr7Q3pSgsysRmc+nwsQ0W47Aw8Emt8te6bR0ATCLux7sjet0XaWth+IjnV WGHU0hZtPoITS3fvH4FnEa03tV38QBtcdL9nJPqX+pttaiSI98UpjWVcoL0hGKahXRU+ VOFObo/FyQWvej3vS26N1AYpfZ3XA1uSyoOcDOveK+7J59TJClJEjxoDAdIXNdD93eQ7 CkazkeyGGQOGGZECSUKdAd2nq9gmMbxIDuAUoqZbQLX+3pPGGRjhjrtRZ/xv44Haq92b pgjA==
X-Gm-Message-State: ACrzQf13Nga9+UY5rLkZo8dSNiet4b11qPs88nQO50ucsqmhUBX4Di+o 8Bvs3rNUglqginsC9UAg4AHKOMyG9ElyoEiVBQc=
X-Google-Smtp-Source: AMsMyM76d2CUZO1Dc9O4nxikkOD7ar/hNrQNjhmde0mKF2OypwoAf6JtcZND8ixHZcRLfSkjU0ttPR7tRspMIxxs8vE=
X-Received: by 2002:a17:902:6b8b:b0:178:7cf5:ad62 with SMTP id p11-20020a1709026b8b00b001787cf5ad62mr19521222plk.13.1664158976849; Sun, 25 Sep 2022 19:22:56 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Yong-Geun Hong <>
Date: Mon, 26 Sep 2022 11:22:45 +0900
Message-ID: <>
To: "Mr. Jaehoon Paul Jeong" <>
Cc:, "Eric Vyncke (evyncke)" <>, Erik Kline <>, CARLOS JESUS BERNARDOS CANO <>, Russ Housley <>, "Charles E. Perkins" <>, Kaippallimalil John <>, Sri Gundavelli <>, JungSoo Park <>, "Prof. Tom Oh" <>, Younghan Kim <>, "Z.W. Yan" <>, Sandra Céspedes <>, Alexandre PETRESCU <>, Nabil Benamar <>, Jérôme Härri <>, Dapeng Liu <>, Michelle Wetterwald <>, Chris Shen <>, Yunchul Choi <>, Mugabarigira Bien Aime <>, Junhee Kwon <>, Hyeonah Jung <>, Patrick Lingga <>, Jeong Hyeon Kim <>, "Prof. Han-You Jeong" <>, "Prof. PyungSoo Kim" <>, "Prof. Youn-Hee Han" <>, "Mr. Jaehoon Paul Jeong" <>
Content-Type: multipart/alternative; boundary="000000000000aa3c6805e98b3433"
Archived-At: <>
X-Mailman-Approved-At: Mon, 26 Sep 2022 01:19:29 -0700
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: Mon, 26 Sep 2022 02:23:01 -0000


I also support this BoF.

Since autonomous driving, drones, UAM, etc., will be popular services in
the future and communication/networking based on IPv6 are important roles
in these areas.
Until now, the IETF IPWAVE WG has done many excellent efforts, I believe
that some subsequent works are needed to handle new requirements.
I can see many meaningful items in the proposed IPMON BoF and I want to
encourage this work.

Best regards


2022년 9월 23일 (금) 오전 1:09, Mr. Jaehoon Paul Jeong <>님이

> 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:
> <>