Re: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-26.txt
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 22 February 2022 14:35 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 556A33A10D1 for <its@ietfa.amsl.com>; Tue, 22 Feb 2022 06:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.396
X-Spam-Level:
X-Spam-Status: No, score=-4.396 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 k-Ew_cnbARHZ for <its@ietfa.amsl.com>; Tue, 22 Feb 2022 06:35:00 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 881303A10A8 for <its@ietf.org>; Tue, 22 Feb 2022 06:34:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 21MEYvaT028230; Tue, 22 Feb 2022 09:34:58 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1645540498; bh=5+7G0joIuR3HBBVsOKOIeuTss3xTwotKC7exvYpfZM4=; h=From:To:CC:Subject:Date:From; b=FBvcWD3uOqqAny3Gu/N5pkyZ0d+g+CyDHd03zcAbBuTlnyhLS20aJUFDNyv33Tcqk SMcJnPLDFrXfkcCWbM3hPDRZssujBPJyMT2o79JutewKRVUaHC0WIvCMwwTrXRPzga 23N/H8W3AyThS6YGrC+K1cnxglUI0m3gi4TU1tN1HELgd+B4h59t0C2dSUyo8d+mU1 e+nz/zdIxdKfutgXwtNAdPWkHkKHkLgIpGEZ80LermIT0IHY4OyApiNwiQqiUiJ/lv TFyKL2xR/5uazFIN8YEPwDE7jXK0wrIJY2R45lA7Sdp0h6zMPjQ7KwhXRN7JDjaCya 6AFLz6oAvCIXA==
Received: from XCH16-07-09.nos.boeing.com (xch16-07-09.nos.boeing.com [144.115.66.111]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 21MEYlOg028088 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 22 Feb 2022 09:34:47 -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; Tue, 22 Feb 2022 06:34:46 -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; Tue, 22 Feb 2022 06:34:46 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Russ Housley <housley@vigilsec.com>
CC: "its@ietf.org" <its@ietf.org>
Thread-Topic: [ipwave] I-D Action: draft-ietf-ipwave-vehicular-networking-26.txt
Thread-Index: Adgn+QchHahVfkvWSjyBIUBX+/2yUQ==
Date: Tue, 22 Feb 2022 14:34:45 +0000
Message-ID: <3532d900b4f441f5a7bfdc1ec1c42b9b@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: B8A8A9076A5ECEFC27E89F73C018C8D531FE6C1108E01894788F2ED59AD932DA2000:8
Content-Type: multipart/alternative; boundary="_000_3532d900b4f441f5a7bfdc1ec1c42b9bboeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/TuV-9DtEB0_BDKsABfg_GW58MJQ>
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 14:35:07 -0000
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] 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<mailto: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<mailto: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<mailto:its-bounces@ietf.org>] On Behalf Of Templin (US), Fred L >> Sent: Monday, February 21, 2022 7:28 AM >> To: its@ietf.org<mailto:its@ietf.org>; i-d-announce@ietf.org<mailto: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<mailto:its-bounces@ietf.org>] On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> >>> Sent: Sunday, February 20, 2022 9:00 PM >>> To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org> >>> Cc: its@ietf.org<mailto: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<mailto:its@ietf.org> >>> https://www.ietf.org/mailman/listinfo/its >> >> _______________________________________________ >> its mailing list >> its@ietf.org<mailto:its@ietf.org> >> https://www.ietf.org/mailman/listinfo/its > > _______________________________________________ > its mailing list > its@ietf.org<mailto: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