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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 21 February 2022 19:56 UTC

Return-Path: <Fred.L.Templin@boeing.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 DBD883A0CBB; Mon, 21 Feb 2022 11:56:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.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 UKDVa-Tx3rzN; Mon, 21 Feb 2022 11:56:21 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 0C5933A0CBC; Mon, 21 Feb 2022 11:56:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 21LJuBD8015574; Mon, 21 Feb 2022 14:56:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1645473373; bh=VKmU7knc4oFamOtjRtBqp+GIaARWnoF6Ay6Y+FOhr6A=; h=From:To:Subject:Date:References:In-Reply-To:From; b=mpimSmK+8Eg0wWFejUchGKw9I7uIdQclRKkMQx23F7IyAhleTO6GHxRAdJ126q0j8 PniwRuI89o7kPHqRNlGal8aqtSeAcFMP349Wn2issrNE5sV7liHfoGyAIxgF1k0YFZ vpnaDRyW0+t/Rm62w+tKJzKUsWIv6v+t8MzVqTxp4vvcA8wwwabNwIwFLX7tCJZ2xa gTZvUuTigbg4EFFhsM/lZQikfkrhMU1/W6GxS2a3xJ0+gAbP2mpOPN3AfuyF3oFM5z PQMq0WqAZDHyjrEphMrHxS65EN1UPn6d/RlCM1AT/mOxBOxdGlbeaT0YxpElgOgRzn FjPSjb9CwRMyw==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 21LJu8ts015528 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 21 Feb 2022 14:56:08 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-09.nos.boeing.com (144.115.66.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2375.18; Mon, 21 Feb 2022 11:56:06 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.2375.018; Mon, 21 Feb 2022 11:56:06 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "its@ietf.org" <its@ietf.org>, "i-d-announce@ietf.org" <i-d-announce@ietf.org>
Thread-Topic: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-26.txt
Thread-Index: AdgnN1+RBlmE8Q07SoaNFuuBoIVBmgAI0tXQ
Date: Mon, 21 Feb 2022 19:56:06 +0000
Message-ID: <083f1894c6144529ba7021b75d234719@boeing.com>
References: <30f9e373e5574b9387137379b31ecd0e@boeing.com>
In-Reply-To: <30f9e373e5574b9387137379b31ecd0e@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: F7570664A07F1D6906EDBB977C829011D0E4376E45B8FFB482A14DB9B9DB469B2000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/rHYQ9yurjXM3T4paFiAhc0UPvr4>
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: Mon, 21 Feb 2022 19:56:26 -0000

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