Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-26.txt
Russ Housley <housley@vigilsec.com> Mon, 21 February 2022 20:26 UTC
Return-Path: <housley@vigilsec.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 A56073A0DD4 for <its@ietfa.amsl.com>; Mon, 21 Feb 2022 12:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NONE=0.001, 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 yFH-h2N8H6Gw for <its@ietfa.amsl.com>; Mon, 21 Feb 2022 12:26:49 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (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 74A8C3A0DD1 for <its@ietf.org>; Mon, 21 Feb 2022 12:26:49 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 347DAE4A39; Mon, 21 Feb 2022 15:26:48 -0500 (EST)
Received: from [10.0.1.2] (pfs.iad.rg.net [198.180.150.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 1EFACE4B94; Mon, 21 Feb 2022 15:26:48 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <083f1894c6144529ba7021b75d234719@boeing.com>
Date: Mon, 21 Feb 2022 15:26:47 -0500
Cc: "its@ietf.org" <its@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6ACB817-A07D-4357-96A9-CF79134D8F05@vigilsec.com>
References: <30f9e373e5574b9387137379b31ecd0e@boeing.com> <083f1894c6144529ba7021b75d234719@boeing.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/27jRZU0BG01ztQw0C5QYr1nSBkE>
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 20:26:55 -0000
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
- [ipwave] I-D Action: draft-ietf-ipwave-vehicular-… internet-drafts
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Russ Housley
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Dirk.von-Hugo
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Erik Kline
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Erik Kline
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Dirk.von-Hugo
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Erik Kline
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Rex Buddenberg
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Templin (US), Fred L
- Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] [EXTERNAL] Re: I-D Action: draft-iet… Templin (US), Fred L