Re: [ipwave] IPWAVE WG will not meet in Singapore

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 09 September 2019 13:50 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 ACCE312025D for <its@ietfa.amsl.com>; Mon, 9 Sep 2019 06:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level:
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, 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 jCzkpnwrNsLv for <its@ietfa.amsl.com>; Mon, 9 Sep 2019 06:50:37 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 767D1120047 for <its@ietf.org>; Mon, 9 Sep 2019 06:50:37 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x89DoZXU048082 for <its@ietf.org>; Mon, 9 Sep 2019 15:50:35 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E1512207C10 for <its@ietf.org>; Mon, 9 Sep 2019 15:50:34 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id DB656201626 for <its@ietf.org>; Mon, 9 Sep 2019 15:50:34 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x89DoYMY029516 for <its@ietf.org>; Mon, 9 Sep 2019 15:50:34 +0200
To: its@ietf.org
References: <DB2176AC-393A-418D-8319-FCF9B899BF6F@vigilsec.com> <92B3C3FD-4555-4BBB-9586-6997ABD409FB@kaloom.com> <A0DE2C48-7E00-4CBB-B543-99F28D4F12A4@vigilsec.com> <ACAE2C8D-B0DD-4BE3-BE97-8F2DC945046E@vigilsec.com> <F5850185-6835-47DB-A7F9-FED44EE3F7FB@vigilsec.com> <CAPK2DezKRY0m5BABmsR-8YXVYj_0Uc1Wr+XzifWmm3GrNS=Vww@mail.gmail.com> <7852218d-49e5-b9b8-deec-980caae9c90d@earthlink.net> <CAPK2DewmGPeyOfaa_CuPTFy9iuXAFKj=woU-VK3jgBHYRnQ+ew@mail.gmail.com> <CAPK2Dewkn+ydWx2ro5bbHmsKYBw529JrQGawdpU1+hMVDST93Q@mail.gmail.com> <5A511B20-00AD-40F4-864C-B54AFD444F7B@vigilsec.com> <CAPK2DezZdR=qDh5nNQmjDJXZXfi2G+pAjVRyfSpNGtmbvyj8xA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <498ddd27-96b9-f33f-6b63-8ee0b6c1435b@gmail.com>
Date: Mon, 09 Sep 2019 15:50:34 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CAPK2DezZdR=qDh5nNQmjDJXZXfi2G+pAjVRyfSpNGtmbvyj8xA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/o0LEjGomzOeq7N9sb5fLsWB3Bv0>
Subject: Re: [ipwave] IPWAVE WG will not meet in Singapore
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 09 Sep 2019 13:50:41 -0000


Le 08/09/2019 à 13:32, Mr. Jaehoon Paul Jeong a écrit :
> Hi Russ, You are right.
> 
> However, as you know, the IPWAVE PS draft focuses on the three work 
> items such as the Vehicular Neighbor Discovery (VND), Vehicular
> Mobility Management (VMM), Security and Privacy. The first two work
> items have been posted before along with the IETF Hackathons and will
> be revised before the I-D submission due for the IETF-106 meeting. -
> VND 
> https://datatracker.ietf.org/doc/draft-jeong-ipwave-vehicular-neighbor-discovery/

Thanks for this draft.

The draft says:

> 6.1.  Vehicular Prefix Information Option
> 
>    The VPI option contains IPv6 prefix informations in the internal
>    network.  Figure 4 shows the format of the VPI option.
 >
>       0                   1                   2                   3
>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |     Type      |    Length     | Prefix Length |   Distance    |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                           Reserved                            |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>      |                                                               |
>      :                            Prefix                             :
>      |                                                               |
>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
> 
>         Figure 4: Vehicular Prefix Information (VPI) Option Format
> 
>    Fields:
>     Type           8-bit identifier of the VPI option type as assigned
>                    by the IANA: TBD

For the value of the TBD, I propose we use the number decimal 24.  It is 
the Type for Route Information Option of RFC4191.

This is what we use in our cars.  If we bring these cars to another 
country, or connect them to other cars, I dont want them to fail because 
of wrong Type number.

Alex

>
>  - VMM 
> https://datatracker.ietf.org/doc/draft-jeong-ipwave-vehicular-mobility-management/
>
>  The security and privacy draft will be prepared by my SKKU group
> with our previous research and will be posted this month.
> 
> As a possible work item, the DNS name auto configuration (DNSNA)
> draft for in-vehicle IoT devices has been revised so far. - DNSNA 
> https://datatracker.ietf.org/doc/draft-jeong-ipwave-iot-dns-autoconf/
>
>  I believe that the other IPWAVE drafts will be revised and posted
> before the I-D submission due.
> 
> IPWAVE WG, if you have the existing IPWAVE drafts and new ideas,
> could you post your drafts before the I-D submission due in order to
> discuss next work items for the IPWAVE rechartering in the IETF-106
> IPWAVE WG session?
> 
> Thanks.
> 
> Best Regards, Paul
> 
> 2019년 9월 8일 (일) 오전 12:44, Russ Housley <housley@vigilsec.com 
> <mailto:housley@vigilsec.com>>님이 작성:
> 
> Paul:
> 
> As I said in my note that started this thread, we will measure energy
> for potential work items by individual Internet-Draft posting and
> mail list discussion of them.  So far, we have not seen any 
> Internet-Drafts.
> 
> Russ
> 
> 
>> On Sep 5, 2019, at 8:41 PM, Mr. Jaehoon Paul Jeong 
>> <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>> wrote:
>> 
>> Hi Russ and Carlos, It seems like Charlie cannot afford to review
>> the revised IPWAVE PS draft due to his work.
>> 
>> Could you review the IPWAVE PS draft as chairs for the WGLC?
>> 
>> BTW, could we have a short WG session in this Singapore meeting to 
>> report the progress of the IPWAVE PS draft?
>> 
>> My SKKU team are preparing for IPWAVE Hackathon Project for IPWAVE 
>> mobility management in IETF-106 Singapore meeting. This experience
>> will be useful to discuss our next step. Also, I am planning to
>> implement the IPWAVE basic protocols such as IPv6 over 802.11-OCB,
>> Vehicular Neighbor Discovery, and Vehicular Mobility Management in
>> Ubuntu Linux early next year. In this IETF-106 meeting, we can
>> discuss our next step. If there is no official IPWAVE WG meeting, I
>> want to have a bar meeting with IPWAVE WG members during the
>> IETF-106 meeting..
>> 
>> Recently, I had a meeting with a principal engineer (Mr. Zeung-il 
>> Kim) from Hyundai Motor, which is the major automotive company in 
>> Korea. His team has interest in implementing IPv6 over 802.11-OCB
>> for the vehicular services such as remote charging system, 
>> context-aware navigator and infotainment for electric vehicles. I
>> will have a meeting with his team this September again.
>> 
>> As you want, our IPWAVE WG need to go to the next step for the 
>> realization of IPWAVE for the industry's demands in the coming
>> autonomous vehicle era.
>> 
>> Thanks for your kind considerations on my request.
>> 
>> Best Regards, Paul
>> 
>> 
>> On Tue, Sep 3, 2019 at 10:31 PM Mr. Jaehoon Paul Jeong 
>> <jaehoon.paul@gmail.com <mailto:jaehoon.paul@gmail.com>> wrote:
>> 
>> Hi Charlie, Do you need more time to finish the review?
>> 
>> Thanks.
>> 
>> Best Regards, Paul
>> 
>> 
>> On Sun, Aug 25, 2019 at 2:52 AM Charlie Perkins 
>> <charles.perkins@earthlink.net 
>> <mailto:charles.perkins@earthlink.net>> wrote:
>> 
>> Hello Paul,
>> 
>> Please excuse my delay.  I will get the review done in the next
>> week.
>> 
>> Regards, Charlie P.
>> 
>> On 8/24/2019 1:55 AM, Mr. Jaehoon Paul Jeong wrote:
>>> Hi Russ and Carlos, My SKKU team have been working for IPWAVE
>>> Neighbor Discovery for IETF-104 and IETF-105. For IETF-106, my
>>> team are working for IPWAVE Mobility Management. The IPWAVE
>>> Neighbor Discovery draft will be coauthored by my SKKU team and
>>> Sandra Cespedes for next revision. 
>>> https://datatracker.ietf.org/doc/draft-jeong-ipwave-vehicular-neighbor-discovery/
>>>
>>>
>>>
>>> 
The IPWAVE Mobility Management draft will be coauthored
>>> by my SKKU team and Sri Gundavelli for next revision. 
>>> https://datatracker.ietf.org/doc/draft-jeong-ipwave-vehicular-mobility-management/
>>>
>>> 
<https://datatracker..ietf.org/doc/draft-jeong-ipwave-vehicular-mobility-management/>
>>> 
>>> 
>>> For the IPWAVE PS draft, Charlie Perkins was supposed to confirm
>>> whether my revision satisfies his comments or not. For one month,
>>> there was no feedback from him. It seems like he cannot afford to
>>> review it due to his personal issues.
>>> 
>>> I would like to ask you as IPWAVE WG chairs to be able to lead
>>> our group more actively by reviewing the PS draft and submitting
>>> it to the IESG through the WG last call..
>>> 
>>> After the completion of the IPWAVE PS draft, our group will be
>>> able to discuss the rechartering and new work items.
>>> 
>>> By the way, I met an engineer from the Hyundai automotive to
>>> discuss IPWAVE-based applications for vehicles. His team
>>> implemented a remote charging system control protocol for
>>> electric vehicles using IEEE 802.11n, and will use IEEE
>>> 802.11-OCB for this system. His team are looking for use cases of
>>> IPWAVE protocols such as context-aware navigator to show neighbor
>>> vehicles and pedestrians.
>>> 
>>> If IPWAVE WG is closed, we will lose the opportunity to enable
>>> our IPWAVE work items described in the PS draft that are the
>>> near-future demands in automotive industry.
>>> 
>>> As my personal request, it will be great to have a short IPWAVE
>>> WG session this Singapore meeting.
>>> 
>>> Thanks.
>>> 
>>> Best Regards, Paul
>>> 
>>> On Sat, Aug 24, 2019 at 12:22 AM Russ Housley 
>>> <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
>>> 
>>> Dear IPWAVE WG:
>>> 
>>> We do not see the need for a meeting in Singapore. We believe
>>> that mail list discussion is needed to wrap up the Problem
>>> Statement document.
>>> 
>>> We observe that the energy in this WG is pretty low. As a result,
>>> we are quite reluctant to re-charter to tackle new work items.
>>> The Problem Statement document includes many potential topics,
>>> but without a great deal more energy, this WG does not seem to
>>> be the right place to tackle them..  This means that the IPWAVE
>>> WG will be closed down once the current charter is complete
>>> unless the chairs and our AD see a significant increase in energy
>>> for one or more potential work items.  This will be measured by 
>>> individual Internet-Draft posting and mail list discussion of
>>> them.
>>> 
>>> Russ and Carlos
>>> 
>>> _______________________________________________ its mailing list 
>>> its@ietf.org <mailto:its@ietf.org> 
>>> https://www.ietf.org/mailman/listinfo/its
>>> 
>>> 
>>> 
>>> -- =========================== Mr. Jaehoon (Paul) Jeong, Ph.D. 
>>> Associate Professor Department of Software Sungkyunkwan
>>> University Office: +82-31-299-4957 Email: jaehoon.paul@gmail.com 
>>> <mailto:jaehoon.paul@gmail.com>, pauljeong@skku.edu 
>>> <mailto:pauljeong@skku.edu> Personal Homepage: 
>>> http://iotlab.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
>> 
>> 
>> 
>> -- =========================== Mr. Jaehoon (Paul) Jeong, Ph.D. 
>> Associate Professor Department of Software Sungkyunkwan University 
>> Office: +82-31-299-4957 Email: jaehoon.paul@gmail.com
>> <mailto:jaehoon.paul@gmail.com>, pauljeong@skku.edu
>> <mailto:pauljeong@skku.edu> 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 of Software Sungkyunkwan University 
>> Office: +82-31-299-4957 Email: jaehoon.paul@gmail.com
>> <mailto:jaehoon.paul@gmail..com>, pauljeong@skku.edu
>> <mailto:pauljeong@skku.edu> Personal Homepage:
>> http://iotlab.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
> 
> 
> _______________________________________________ its mailing list 
> its@ietf.org https://www.ietf.org/mailman/listinfo/its
>