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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Fri, 23 September 2022 04:55 UTC

Return-Path: <jaehoon.paul@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 AF0C7C14CE33 for <its@ietfa.amsl.com>; Thu, 22 Sep 2022 21:55:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.097
X-Spam-Level:
X-Spam-Status: No, score=-0.097 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, 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=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Y4UpmbjoosnS for <its@ietfa.amsl.com>; Thu, 22 Sep 2022 21:55:06 -0700 (PDT)
Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 95BBBC14CE24 for <its@ietf.org>; Thu, 22 Sep 2022 21:55:06 -0700 (PDT)
Received: by mail-pl1-x62c.google.com with SMTP id b21so10740407plz.7 for <its@ietf.org>; Thu, 22 Sep 2022 21:55:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=42gwumDdpPIzRvpZu3ZFGAxYTRBF9V6EKFJJsHaLVrw=; b=BfUby7Y3+ong6EHLGoF1E/kj2wXnhnDbvwmCv5ekp27Ktp6i8C7evtA6KMrn/RafXt n+vg/ved/nicc+ZktZv7rwq1SLes18/iM9mDTwXnTtGf93V2HbjEITSk2Z9EjJz+yyRt NBRGyMKF8ibgXoUnyxAJPJsukPw3j+PcAWDTdv8CXvV+NsSwijrEzVwd3xhoWgCieIof DXDyx8ajK1C91da252WedX2vD0CAjzMUNcs/3HJggodu1BjVE4TBAT95ZuTPvhZ0Mmdh 5Fo5aMjqiSD/gEJ/2PitbOC6T+TWTPI1om1ZZmgWR9ZDbw+CZlvH44+Wgpxpoz2EYkHK OCGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; 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=42gwumDdpPIzRvpZu3ZFGAxYTRBF9V6EKFJJsHaLVrw=; b=lRwMdRRACjT/EvCg7VnvZFJXOJFJreVFu7eMi6gU4B+qu8+Kul/kO35P0jut+lbf2R MeR5w17AwrbZGTDs8r7YqCXDMPW+hlM4sS8PulFBt7NaMQWoAaRwJeIqup8pKYSe7bgb sZsuRku0AXW58PUp2FjoBF1WmiI9h3vvQvz303Wj/07xYNRRyM3GZG5CNdHPN8ZtJNop RWT1rDt2jUl5RSi+rrWIEGAvhap7+e67aVzHpe4LLv5xbm1P68m2eZEbnTB7Gh9nI/D/ xDsDXE8yzyGgtmhU3SWAT46O7uF+MtyhKzzi0NNYT/Sw+OyhREKiy9d8GupYrrtH5+Eh lXTg==
X-Gm-Message-State: ACrzQf3p1/MqeI1AAistYDD9mKQKJ/gGk5VmiGKCGwN/pLveXVzrMdlx gKicHGIdB4MOuFUc4TBtHmXFTdMtk40xnCMEgysHtyJ8
X-Google-Smtp-Source: AMsMyM5fe+jsWw246F+/P0IQEZwVukAYXv+GGMA6Wp595wRut7bdaMup9JNcD/7dSAcxrYz1t13aqiB/Djq4RLOiS14=
X-Received: by 2002:a17:902:7598:b0:178:3f96:4ffc with SMTP id j24-20020a170902759800b001783f964ffcmr6852444pll.53.1663908905752; Thu, 22 Sep 2022 21:55:05 -0700 (PDT)
MIME-Version: 1.0
References: <CAPK2Dewh+bcxDyNniWtqTVidpYXGC8CUv7GMb5RxEhn+hTk6Ag@mail.gmail.com> <e484ebdfdbe44dabbf0a3840ad095552@huawei.com>
In-Reply-To: <e484ebdfdbe44dabbf0a3840ad095552@huawei.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Fri, 23 Sep 2022 13:54:54 +0900
Message-ID: <CAPK2DezkL8Vyrzty7tZqDA72ub82d2vaC02ZH_gWXdAHK2QCZw@mail.gmail.com>
To: "Yanshen(IAS-PSPDept)" <yanshen@huawei.com>
Cc: Linda Dunbar <linda.dunbar@futurewei.com>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Qin Wu <bill.wu@huawei.com>, its@ietf.org, skku-iotlab-members <skku-iotlab-members@googlegroups.com>
Content-Type: multipart/alternative; boundary="000000000000441de805e950fbfe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/s5GFI6PcuuQEuQ3-80e50IvUzz4>
Subject: Re: [ipwave] Request for Your Interest on a New BoF as a Follower of IPWAVE WG
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, 23 Sep 2022 04:55:10 -0000

Hi Shen,
Welcome your proposed work in Huawei to IPMON BoF
since your work seems to belong to the scope of IPMON:
- Protocol Optimization for Different L1/2

If IPMON BoF is approved by the IESG/IAB for IETF 115,
I will assign a time slot for you to introduce
your work in Huawei.
You can present your work remotely in IETF 115
through IETF Meetecho.

Thanks.

Best Regards,
Paul (Jaehoon)

2022년 9월 23일 (금) 오후 1:23, Yanshen(IAS-PSPDept) <yanshen@huawei.com>님이 작성:

> Dear Jaehoon,
>
>
>
> My name is Shen Yan from Huawei Technologies, Intelligent Automotive
> Solution BU. My group work on the high-performance short-range wireless
> communication technologies which names SparkLink. It is a kind of L1/2/3
> technical framework that aims to provide ultra-low latency, ultra-high
> reliability and ultra-high concurrency. I am responsible for the standard
> work of L3.
>
>
>
> I am pretty interested in IPWAVE work and especially interested in IPMON.
> I saw the related statement in your proposal “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”.  A short comment from my side is that I
> think the low layers (L1/2) framework is very important for our L3’s
> design. For example, difference performance on latency and bandwidth may
> influence the protocol design concerns. The 5th deliverable
> “Context-Aware Navigation Protocol for Physical Collision Avoidance in
> Vehicular Networks” has shown the similar considerations. Furthermore, I
> fully believe that there are multiple L1/2 techs in the future IPMON
> scenarios so that to support different requirements due to their features.
> May I suggest to add related deliverables such as “protocol optimization
> for different L1/2” or other similar items?
>
>
>
> Please feel free to consider about this. Just contributive comments. And I
> will follow your work. It is important and needed.
>
>
>
> Best regards,
>
>
>
> Shen
>
>
>
> *发件人:* its <its-bounces@ietf.org> *代表 *Mr. Jaehoon Paul Jeong
> *发送时间:* 2022年9月23日 8:00
> *收件人:* its@ietf.org
> *抄送:* skku-iotlab-members <skku-iotlab-members@googlegroups.com>; Mr.
> Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *主题:* [ipwave] Request for Your Interest on a New BoF as a Follower of
> IPWAVE WG
>
>
>
> 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:
>
> https://datatracker.ietf.org/doc/draft-ietf-ipwave-vehicular-networking/
>
>
>
> I have submitted a BoF request to the IETF on September 8 as follows:
>
>
> https://datatracker.ietf.org/doc/bofreq-jeong-ipv6-moving-object-networking-ipmon/
>
>
>
> 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: pauljeong@skku.edu, jaehoon.paul@gmail.com
> Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
> <http://cpslab.skku.edu/people-jaehoon-jeong.php>
>
-- 
===========================
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, jaehoon.paul@gmail.com
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>