Re: [ipwave] Should the IPWAVE WG adopt draft-jeong-ipwave-vehicular-networking-survey?

tony.li@tony.li Wed, 21 June 2017 16:08 UTC

Return-Path: <tony.li@tony.li>
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 3C9AC12EC23 for <its@ietfa.amsl.com>; Wed, 21 Jun 2017 09:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 t2iegFo2Ztkb for <its@ietfa.amsl.com>; Wed, 21 Jun 2017 09:08:47 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (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 9EB7312EC30 for <its@ietf.org>; Wed, 21 Jun 2017 09:08:02 -0700 (PDT)
Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-07v.sys.comcast.net with SMTP id NiAMd7SntU9z5NiAkdVYg7; Wed, 21 Jun 2017 16:08:02 +0000
Received: from [10.120.1.157] ([12.1.72.210]) by resomta-ch2-09v.sys.comcast.net with SMTP id Ni8Yd1Hjoh8eeNi8bdTLO5; Wed, 21 Jun 2017 16:06:00 +0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: tony.li@tony.li
In-Reply-To: <1498059404.2400.175.camel@gmail.com>
Date: Wed, 21 Jun 2017 09:05:46 -0700
Cc: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Russ Housley <housley@vigilsec.com>, its <its@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4B80FAD-885E-42CE-8F88-F552931C0645@tony.li>
References: <CA50A382-F591-4A33-BAF9-1903E107BE02@vigilsec.com> <1497977954.2400.149.camel@gmail.com> <CAPK2DewLqSLVvOy5TFz3JaZKKJnKBCbuzm8xUh+sdWdivSm3Tg@mail.gmail.com> <1498018725.2400.166.camel@gmail.com> <827A92DD-1EFB-4D65-A431-D1D23914D5E1@tony.li> <1498059404.2400.175.camel@gmail.com>
To: Rex Buddenberg <buddenbergr@gmail.com>
X-Mailer: Apple Mail (2.3273)
X-CMAE-Envelope: MS4wfEZ+4eheDgCkdg4BO6fMuBM25Y4Cdc2mwvwXjXJ2a8cHt4RaDJrPNa/RfDCfT9Rz8ae5cW/sxOKAPYenLfxh2m2/yIKh5M+rNy9FbHwY3C5ejd37PfJl 2ViX/g0mAUddmp3ifDNUVFRsV8NnBCRgYYHUmbJRiqjgS7uDPLiuDoPFt7Ds3dXnhuApm9R8YQ5c5RC7SexQkBhXyz7630kysceITy5qU36dZi+MbeDPeAjJ 9MEA1sV0K+W49zfMseXwrw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/-G0HgmkksU1dKMnAnAOyjE-2CP8>
Subject: Re: [ipwave] Should the IPWAVE WG adopt draft-jeong-ipwave-vehicular-networking-survey?
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 21 Jun 2017 16:08:50 -0000

Rex,

A few more questions, if I may:


> IP.  The telemetering of data to the hospital is an example of at least
> a three-segment internetwork.  Terrestrial WAN, radio-WAN and LANs.  In
> my book that makes a pretty good case for IP.  (The emergency services
> comms folks tend to view the 'backhaul', the terrestrial WAN, as an
> afterthought.)


Those of us from the Internet infrastructure world are used to being an afterthought.  Except at the IETF. ;-)

I think that we can easily stipulate IP connectivity as a requirement, otherwise we wouldn’t be here, so I’m interested in more details.

> Different.  Volatile topology and security.  


We’ve dealt with volatile last-hop topology before (e.g., Wi-Fi).  What’s different here? Does your use case require multiple radio hops? 

On the security front, we won’t be fixing the security infrastructure of the entire Internet here, so there’s a limit to what we can do.  What do you see as the requirements that come out of your use case and how do existing IP security mechanisms align with or fail to meet those requirements?

Tony