Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-26.txt

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Tue, 22 February 2022 22:20 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 CFE143A08DC for <its@ietfa.amsl.com>; Tue, 22 Feb 2022 14:20:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.427
X-Spam-Level:
X-Spam-Status: No, score=-0.427 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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, URIBL_BLOCKED=0.001, URI_DOTEDU=1.659] 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UgG0zsfC3bN for <its@ietfa.amsl.com>; Tue, 22 Feb 2022 14:20:29 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ABAB3A08D7 for <its@ietf.org>; Tue, 22 Feb 2022 14:20:28 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id e17so21844481ljk.5 for <its@ietf.org>; Tue, 22 Feb 2022 14:20:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pvJjtp6uO77r2jYjviV4ECkMA9jTrOmThRXet+RYQtM=; b=LbFNqdYxjxM/DUY+4b5+1MtEZ4J8jwaPib/3Evmj5k6LLN3GBABaD1EELBeW+JBsQ0 kAh6vAv9Z2a8fOBGN1J0RK0dhhZq6DxP0UMyeGVUAaD+dMttweITDQ/eTLsFFXzF5J9N L8doiM1mSobljxm8/v82Evm5ywFuATqGLMqn/1mchqXRbHksyX5mV2n23OgtGd5SX6Mh NnVlVRsBqx8Xq7/uw3F6KqQU4WsfYX2TE5qmmEZvLoecu5D3iFNJ2n5oU/w4yMC9LWiw /HW6UaLIn5ACvvIUjiTpDNdXUerso3JId2y9T6i1rVGRfCuHqnHjp0Gk8luZVADZ3u1H ZonA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pvJjtp6uO77r2jYjviV4ECkMA9jTrOmThRXet+RYQtM=; b=fdMmjXDwyGIDKl45+KGuEqRuwNRe6ZW5thtdN7WnHDB70qFCvF0Fg47KlCQhHsP/m3 RjOkd6bjKqOOlac+C4LU3ZFrFoE4YGo32nwXQ+41+2M3ITpWXaD+9H3OKAqlTN5WjOBN 73APBugbMuY15/SeKeiLVYCcMvwQ4q1eSQBl479Ruz47BUkcZN0mTK/QAT+c2/UIjsu2 vZG4WLOKWj4uEg+AYUmEKBHNm1k7aD9FOInTI3+IGtvOBVfzK0Kpj8eXOCKjnqW4mfvb TAposy5KG97orhTGiq6IiYgHysOfrXUro/paJCNEHw6JdASCcJ8GzEgJLjM3wfxMSAiI u64Q==
X-Gm-Message-State: AOAM530wzwwHloafb1Mq+5dmp1vSt+OKuT8R7wny7BlkasM0+yxFHtDS hS6bdLK+DxrUWFuV4PVNc/O1LYB19nTOfrSWUJE=
X-Google-Smtp-Source: ABdhPJyjOJUnMRUesZGv2+oGrvik3lDC0nFodYvD8+veHPijcG/+nr1Iov5t/Sf8WnZjfC+F5ihEB6h98cNDSC7nGjo=
X-Received: by 2002:a2e:a270:0:b0:245:f51f:354 with SMTP id k16-20020a2ea270000000b00245f51f0354mr19686206ljm.497.1645568425979; Tue, 22 Feb 2022 14:20:25 -0800 (PST)
MIME-Version: 1.0
References: <3532d900b4f441f5a7bfdc1ec1c42b9b@boeing.com> <FR3P281MB05244828DEC381B64BE0F62BD13B9@FR3P281MB0524.DEUP281.PROD.OUTLOOK.COM>
In-Reply-To: <FR3P281MB05244828DEC381B64BE0F62BD13B9@FR3P281MB0524.DEUP281.PROD.OUTLOOK.COM>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Wed, 23 Feb 2022 07:20:14 +0900
Message-ID: <CAPK2DezUB9ovQ5yBVS0pR6L7QtHC4FQysg9EfXkkT8wUEojqSg@mail.gmail.com>
To: Dirk.von-Hugo@telekom.de
Cc: Fred.L.Templin@boeing.com, housley@vigilsec.com, its@ietf.org
Content-Type: multipart/alternative; boundary="0000000000007bf41a05d8a2c11a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/ie0h6c9DpRbaX6WLq3aZtIOknXY>
Subject: Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-26.txt
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: Tue, 22 Feb 2022 22:20:34 -0000

Hi Dirk,
I will address your comments on the revision.

You are right.
AERO uses Automatic instead of Asymmetric in the latest version.

Thanks.

Best Regards,
Paul

2022년 2월 23일 (수) 오전 12:45, <Dirk.von-Hugo@telekom.de>님이 작성:

> Dear Fred, Paul, Russ and all,
>
> From my point of view - only loosely following this discussion - I do
> agree that Paul has achieved a good balance between different protocols
> included/mentioned. Thanks for that!
>
>
>
> Just a small typo: on page 3 it should also read
>
> ‘Automatic Extended Route Optimization (AERO)’ instead of ‘Asymmetric
> Extended Route Optimization (AERO)’
>
> And maybe one could add on p. 14 the sentence
>
> ‘Refer to Appendix A for the description how OMNI can support use of
> multiple radio technologies in V2X’.
>
>
>
> Would that help? What do you think?
>
> Thanks
>
> Best regards
>
> Dirk
>
>
>
> *Von:* its <its-bounces@ietf.org> *Im Auftrag von *Templin (US), Fred L
> *Gesendet:* Dienstag, 22. Februar 2022 15:35
> *An:* Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>; Russ Housley <
> housley@vigilsec.com>
> *Cc:* its@ietf.org
> *Betreff:* Re: [ipwave] I-D Action:
> draft-ietf-ipwave-vehicular-networking-26.txt
>
>
>
> The way the document is now, it reads as an endorsement for a particular
> approach.
>
> The document was good last time I read it (which is a while ago) but I
> guess someone
>
> got you to make drastic changes without my knowing about it. The document
> cannot
>
> go forward in its current form.
>
>
>
> Fred
>
>
>
> *From:* Mr. Jaehoon Paul Jeong [mailto:jaehoon.paul@gmail.com
> <jaehoon.paul@gmail.com>]
> *Sent:* Monday, February 21, 2022 7:50 PM
> *To:* Russ Housley <housley@vigilsec.com>; Templin (US), Fred L <
> Fred.L.Templin@boeing.com>
> *Cc:* its@ietf.org; Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com>
> *Subject:* [EXTERNAL] Re: [ipwave] I-D Action:
> draft-ietf-ipwave-vehicular-networking-26.txt
>
>
>
> EXT email: be mindful of links/attachments.
>
>
>
>
> Hi Russ,
>
> I have replied to Fred's email just before.
>
> As the editor, I tried to balance the two approaches even though the text
> of AERO/OMNI is reduced.
>
>
>
> Fred,
>
> I hope you can understand my position as the editor.
>
>
>
> Thanks.
>
>
>
> Best Regards,
>
> Paul
>
>
>
>
>
> On Tue, Feb 22, 2022 at 5:26 AM Russ Housley <housley@vigilsec.com> wrote:
>
> Paul and Fred:
>
> I think the update is more aligned with the documents that are advancing
> one the IETF stream.  That said, I would not be apposed to the inclusion of
> the 6M's, but not in a way that claims that there is only one approach way
> to address these things.  What do you think about that was a way forward?
>
> Russ
>
>
> > On Feb 21, 2022, at 2:56 PM, Templin (US), Fred L <
> Fred.L.Templin@boeing.com> wrote:
> >
> > Hi, I started reviewing this and found that it has been completely
> overhauled since I put my
> > comments in many months ago. It has in fact been completely rewritten to
> favor the shared
> > IPv6 multilink subnet model over multihop networks, to favor RPL/6LowPan
> over standard
> > MANET routing protocols, to favor IPv6 ND changes over standard IPv6 ND,
> and to favor
> > multilink DAD. None of that is necessary with AERO/OMNI and the
> NBMA-based virtual link
> > created by the OMNI Adaptation. So, I stopped midway through marking up
> the document
> > with my comments because it has taken a complete left turn and started
> down a wrong path.
> >
> > What is mainly at the heart of the divergence is that the document now
> embraces the
> > multilink IPv6 subnet model vs the AERO/OMNI NBMA link model that was
> there the last
> > time I looked. But, there is no need for such complication when there is
> a much simpler
> > alternative at hand. I notice also that in the appendices the AERO/OMNI
> "6M's of Mobile
> > Internetworking" was removed - at the very least that needs to be
> restored.
> >
> > In its current form, this document has been diverted to go down the
> wrong path. It
> > needs to be either re-balanced or re-written.
> >
> > Thanks - Fred
> >
> >> -----Original Message-----
> >> From: its [mailto:its-bounces@ietf.org] On Behalf Of Templin (US),
> Fred L
> >> Sent: Monday, February 21, 2022 7:28 AM
> >> To: its@ietf.org; i-d-announce@ietf.org
> >> Subject: Re: [ipwave] I-D Action:
> draft-ietf-ipwave-vehicular-networking-26.txt
> >>
> >> Hi, it looks like a lot of what was in the draft regarding AERO/OMNI
> has been cut out
> >> so that means I am going to have to re-review it. I will get to this a
> soon as possible;
> >> hopefully in the next couple of days.
> >>
> >> Fred
> >>
> >>> -----Original Message-----
> >>> From: its [mailto:its-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> >>> Sent: Sunday, February 20, 2022 9:00 PM
> >>> To: i-d-announce@ietf.org
> >>> Cc: its@ietf.org
> >>> Subject: [EXTERNAL] [ipwave] I-D Action:
> draft-ietf-ipwave-vehicular-networking-26.txt
> >>>
> >>> EXT email: be mindful of links/attachments.
> >>>
> >>>
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>> This draft is a work item of the IP Wireless Access in Vehicular
> Environments WG of the IETF.
> >>>
> >>>        Title           : IPv6 Wireless Access in Vehicular
> Environments (IPWAVE): Problem Statement and Use Cases
> >>>        Author          : Jaehoon (Paul) Jeong
> >>>     Filename        : draft-ietf-ipwave-vehicular-networking-26.txt
> >>>     Pages           : 49
> >>>     Date            : 2022-02-20
> >>>
> >>> Abstract:
> >>>   This document discusses the problem statement and use cases of
> >>>   IPv6-based vehicular networking for Intelligent Transportation
> >>>   Systems (ITS).  The main scenarios of vehicular communications are
> >>>   vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and
> >>>   vehicle-to-everything (V2X) communications.  First, this document
> >>>   explains use cases using V2V, V2I, and V2X networking.  Next, for
> >>>   IPv6-based vehicular networks, it makes a gap analysis of current
> >>>   IPv6 protocols (e.g., IPv6 Neighbor Discovery, Mobility Management,
> >>>   and Security & Privacy), and then enumerates requirements for the
> >>>   extensions of those IPv6 protocols for IPv6-based vehicular
> >>>   networking.
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>>
> https://datatracker.ietf.org/doc/draft-ietf-ipwave-vehicular-networking/
> >>>
> >>> There is also an htmlized version available at:
> >>>
> https://datatracker.ietf.org/doc/html/draft-ietf-ipwave-vehicular-networking-26
> >>>
> >>> A diff from the previous version is available at:
> >>>
> https://www.ietf.org/rfcdiff?url2=draft-ietf-ipwave-vehicular-networking-26
> >>>
> >>>
> >>> Internet-Drafts are also available by rsync at rsync.ietf.org:
> :internet-drafts
> >>>
> >>>
> >>> _______________________________________________
> >>> its mailing list
> >>> its@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/its
> >>
> >> _______________________________________________
> >> its mailing list
> >> its@ietf.org
> >> https://www.ietf.org/mailman/listinfo/its
> >
> > _______________________________________________
> > its mailing list
> > its@ietf.org
> > 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, jaehoon.paul@gmail.com
Personal Homepage: http://iotlab.skku.edu/people-jaehoon-jeong.php
<http://cpslab.skku.edu/people-jaehoon-jeong.php>