Re: [ipwave] MAC Address minor textual issue

Russ Housley <housley@vigilsec.com> Thu, 18 May 2017 15:27 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 3969C1294A4 for <its@ietfa.amsl.com>; Thu, 18 May 2017 08:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 cXpapbILL8sL for <its@ietfa.amsl.com>; Thu, 18 May 2017 08:27:49 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E02712EA97 for <its@ietf.org>; Thu, 18 May 2017 08:22:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 89CAD300538 for <its@ietf.org>; Thu, 18 May 2017 11:22:23 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6nFD0AtOYrzW for <its@ietf.org>; Thu, 18 May 2017 11:22:22 -0400 (EDT)
Received: from [5.5.33.143] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id C2F1B300265; Thu, 18 May 2017 11:22:21 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <81C61671-C468-4841-B097-15C6328F4A2C@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_23123A59-E758-4510-A6DB-EF627D67D361"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 18 May 2017 11:22:23 -0400
In-Reply-To: <846437B4-BE7D-4DF2-9C37-26D60180E82B@tony.li>
Cc: "its@ietf.org" <its@ietf.org>
To: Tony Li <tony.li@tony.li>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <b7d0f246-da90-ac56-db69-40e9e929900d@gmail.com> <13CE99A5-4B32-472A-B793-3ADC2E530409@vigilsec.com> <009601d2cfde$ad5abce0$081036a0$@eurecom.fr> <CAP6QOWQkSod0JxSdN9U+ztPwhLu0z35w-=O=WMQL1EOi_UzwpQ@mail.gmail.com> <846437B4-BE7D-4DF2-9C37-26D60180E82B@tony.li>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/8rZ5jbeBWepLrowSzT_XCUnznGw>
Subject: Re: [ipwave] MAC Address minor textual issue
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: Thu, 18 May 2017 15:27:50 -0000

>> I do not agree with the statement that "there are strong privacy concerns". I suggest changing "concerns" to "requirements".
>> 
>> I think stating that there are strong concerns conveys a sense of this being a big unsolved problem. For the DSRC/ITS-G5 community this is not the case. Privacy protection, including careful avoidance of PII in messages, pseudonymous certificates, and frequent identifier randomization, has been designed into DSRC/ITS-G5 from day 1.  
> 
> Well, I for one am still mystified by how the solution maps to IP.  DSRC can do all of this work, but if my IP addressing doesn’t change in synchrony, it seems like it all doesn’t help. And if the IP addresses do change in synchrony, you abort upper layer TCP connections.
> 
> So I’m still concerned.

I agree that the IPv6 address needs to change whenever the MAC address changes.  This is not a problem for UDP traffic, but it can be a problem for TCP.  In my view, there is no privacy benefit to changing the MAC/IPv6 address while the vehicle is stationary, like in a garage overnight.  In fact, this is the time when long-lived TCP connections are extremely likely for actives like software update.  Is this a place we can add value with crisp recommendations?

Russ