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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Tue, 22 February 2022 03:50 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 6A6043A09B2 for <its@ietfa.amsl.com>; Mon, 21 Feb 2022 19:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.087
X-Spam-Level:
X-Spam-Status: No, score=-7.087 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_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HK_NAME_FM_MR_MRS=0.01, URIBL_BLOCKED=0.001] autolearn=ham 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 Jx-X63Mg4I0F for <its@ietfa.amsl.com>; Mon, 21 Feb 2022 19:50:21 -0800 (PST)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 ABF0F3A09AD for <its@ietf.org>; Mon, 21 Feb 2022 19:50:20 -0800 (PST)
Received: by mail-lf1-x136.google.com with SMTP id w27so4480476lfa.5 for <its@ietf.org>; Mon, 21 Feb 2022 19:50:20 -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=Fh3zomr/nUh4NYmZx8dqdDe02QFZP81tdd1Ay9EIClQ=; b=bj/NE82kgQOaTq7Jb8kCaaxFlPvev1TmRw/zQ2jbbhyENEbBd9tvIHCvwTPQugXqAp ZwlRtoX2/rwT9DCZxMG5s4oCilgdQFSdy1I48d6Baf/CV4m8zUKV2F8qSijRg1kNJ9wl C6cG6uITN4gleDQAhdWytx0rUWUscFxtCLLqaqXSpcdNBNtUqWMYH8b8aqYXSUTpt//+ VNPpeA1oOEa+1VhDNjTrhKQU56cJ9AM6tU4ZkFwZQrBLdfwGa0pIWDx8nq7rnHGz/1e4 nNYslI9jN7tuaEnAwTstD1kZhZfzkAvJTmwojJNPZDnNuzubOFS5g56WgBFdopzIXQSo tc+w==
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=Fh3zomr/nUh4NYmZx8dqdDe02QFZP81tdd1Ay9EIClQ=; b=Mqne47VMTabVJsN9TWsOMiYyhZb8oQKO9cV4exx8Hmbgn0XNAkOZUBf35Hg6Fr0qEs TBuJf7eTkY3Z8nICjP6PTlEK/gyObf/wPLitwa3WLS+BBrOc5bhn9lWHeyW4tuQEg5jj BZthyUDIbfuyFwSPKW1oGQs+me2lkLljjTzxH9ESJDGRpMsRiliv30DaH8qN/rxU2ncH LHfSn/SdMQLX6fctqR8HZB7azKPlEALU1tQC2D3ErSAh89DJmEHhNCPxREeoBT2FbuIx dDa8GPI/c7xUheo/gv9Uq8N90F5AItSdw3wXaeVGFaYhxjab/+8DWhUDaIkkkR+4zB8L DVfQ==
X-Gm-Message-State: AOAM532Bifd69iiaPfFl+VQF0OSQ3NqMt/aB+eCZqj5jSjrQsCkcKacH npuK6YdqHSemPNv3BaFa16fSUqHMPC5iuoyDIoY=
X-Google-Smtp-Source: ABdhPJzS3BrubOjEgWpHBi0PdV9xXP4kKcPijJgxigiepS/0R3H1p5u81J672XW4xuN/cayA/FFoZimWn/mQ65Aamfk=
X-Received: by 2002:a05:6512:220a:b0:443:1140:7ffc with SMTP id h10-20020a056512220a00b0044311407ffcmr15308547lfu.566.1645501818327; Mon, 21 Feb 2022 19:50:18 -0800 (PST)
MIME-Version: 1.0
References: <30f9e373e5574b9387137379b31ecd0e@boeing.com> <083f1894c6144529ba7021b75d234719@boeing.com> <C6ACB817-A07D-4357-96A9-CF79134D8F05@vigilsec.com>
In-Reply-To: <C6ACB817-A07D-4357-96A9-CF79134D8F05@vigilsec.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Date: Tue, 22 Feb 2022 12:49:36 +0900
Message-ID: <CAPK2DezJXHqEqTY9GOYaO81TYYg_YSSxbyGCi6s+pUUSXX3nKA@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>, "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: "its@ietf.org" <its@ietf.org>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000005bd8c005d8933f8a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/3BJSdpNrzfSj1rp-jai7J0ahDhk>
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 03:50:25 -0000

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