[ipwave] Comments on draft-ietf-ipwave-vehicular-networking-23
"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 24 September 2021 14:06 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 A7EBB3A2A06 for <its@ietfa.amsl.com>; Fri, 24 Sep 2021 07:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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_MSPIKE_H2=-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 C0VIWIDbRfm5 for <its@ietfa.amsl.com>; Fri, 24 Sep 2021 07:06:37 -0700 (PDT)
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 522443A2CA2 for <its@ietf.org>; Fri, 24 Sep 2021 07:05:45 -0700 (PDT)
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 18OE5fpE019532; Fri, 24 Sep 2021 10:05:43 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1632492344; bh=54iRm8pRMojOy+9Uq8sCoWYyFdxSPQo6qFBTZ97wkh4=; h=From:To:CC:Subject:Date:From; b=HjZo5cYdHz4B3NeBDFCkExgc1t6HRZgLKhQFrlXufIsBGveQ6evXAtkq2Vxp9Wgti B8F76Ro+Muw3hXDd+HvoR2WfCgcn/Pbf9fZTwcIXmr/GohCnDWrIpXajN4fNUKk6YL vMNwKheldMp/YAC2/PlAOfhstdQel97ISmLdE8xvOj+lQYBMebGw2eylC2jmyzDH3q FVk17Tju5iZuu9vbf/l6E4ucwG/N0uLZorfw4jzijKYbn5hbWpnUitoU3reFCZbzFc DTUwg+GTfai5kvWQyPVqJ0slVYeyyMfsXei8cy+nMYaLomxOQwIbW2dWWbtY6Zbjnb 7tVzG0IWrN9AA==
Received: from XCH16-07-10.nos.boeing.com (xch16-07-10.nos.boeing.com [144.115.66.112]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 18OE5equ019525 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 24 Sep 2021 10:05:40 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-10.nos.boeing.com (144.115.66.112) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2308.14; Fri, 24 Sep 2021 07:05:34 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2308.014; Fri, 24 Sep 2021 07:05:34 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
CC: its <its@ietf.org>
Thread-Topic: Comments on draft-ietf-ipwave-vehicular-networking-23
Thread-Index: AdexSt/92ZhVYtziTMCAe5lbSvWx+g==
Date: Fri, 24 Sep 2021 14:05:34 +0000
Message-ID: <e60add66f857478da782de2a536b9062@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: 33723540EDD7E37AA8DC7C19B94214B151198039ECABB34C7ECEA43C44892B622000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/7abJIdAYjZIyMxuSOrG-SXC8F40>
Subject: [ipwave] Comments on draft-ietf-ipwave-vehicular-networking-23
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: Fri, 24 Sep 2021 14:06:42 -0000
Paul, a couple of comments on the -23 draft version: 1) For AERO, change the title expansion to “Automatic Extended Route Optimization”. 2) The correct references for AERO and OMNI are: https://datatracker.ietf.org/doc/draft-templin-6man-aero/34/ https://datatracker.ietf.org/doc/draft-templin-6man-omni/47/ 3) Appendix B now seems to say a lot about RPL and not much about AERO/OMNI. Please add the following to Appendix B: "AERO and OMNI together securely and efficiently address the “6 M’s of Modern Internetworking” for mobile V2V, V2I and V2X Clients, including: 1. Multilink – a Client's ability to coordinate multiple diverse underlying data links as a single logical unit (i.e., the OMNI interface) to achieve the required communications performance and reliability objectives. 2. Multinet - the ability to span the OMNI link over a segment routing topology with multiple diverse administrative domain network segments while maintaining seamless end-to-end communications between mobile Clients and correspondents such as air traffic controllers, fleet administrators, etc. 3. Mobility - a Client's ability to change network points of attachment (e.g., moving between wireless base stations) which may result in an underlying interface address change, but without disruptions to ongoing communication sessions with peers over the OMNI link. 4. Multicast - the ability to send a single network transmission that reaches multiple Clients belonging to the same interest group, but without disturbing other Clients not subscribed to the interest group. 5. Multihop - a mobile Client vehicle-to-vehicle relaying capability useful when multiple forwarding hops between vehicles may be necessary to "reach back" to an infrastructure access point connection to the OMNI link. 6. MTU assurance - the ability to deliver packets of various robust sizes between peers without loss due to a link size restriction, and to dynamically adjust packets sizes to achieve the optimal performance for each independent traffic flow." That is all I have for now, but will let you know if I notice anything else. Thanks - Fred
- [ipwave] Comments on draft-ietf-ipwave-vehicular-… Templin (US), Fred L
- Re: [ipwave] Comments on draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Comments on draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong
- Re: [ipwave] Comments on draft-ietf-ipwave-vehicu… Alexandre Petrescu
- Re: [ipwave] Comments on draft-ietf-ipwave-vehicu… Mr. Jaehoon Paul Jeong