IETF Logo Mail Archive

[ipwave] MAC Address minor textual issue

Russ Housley <housley@vigilsec.com> Thu, 18 May 2017 13:49 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 35C901294F4 for <its@ietfa.amsl.com>; Thu, 18 May 2017 06:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 Wy6TVMhp7thJ for <its@ietfa.amsl.com>; Thu, 18 May 2017 06:49:14 -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 49CEE1294B2 for <its@ietf.org>; Thu, 18 May 2017 06:43:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id A9993300538 for <its@ietf.org>; Thu, 18 May 2017 09:43:50 -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 azmpsyb_dXOk for <its@ietf.org>; Thu, 18 May 2017 09:43:49 -0400 (EDT)
Received: from [5.5.33.141] (vpn.snozzages.com [204.42.252.17]) by mail.smeinc.net (Postfix) with ESMTPSA id 2093F300435; Thu, 18 May 2017 09:43:49 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <13CE99A5-4B32-472A-B793-3ADC2E530409@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F788A224-5C30-4CEC-94DA-71C9B5C90930"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 18 May 2017 09:43:50 -0400
In-Reply-To: <b7d0f246-da90-ac56-db69-40e9e929900d@gmail.com>
Cc: "its@ietf.org" <its@ietf.org>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <b7d0f246-da90-ac56-db69-40e9e929900d@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/m-DRzEMdZlwPX6-Gpjop6DnPcbU>
Subject: [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 13:49:16 -0000

> On May 18, 2017, at 5:39 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> 
> OLD:
>> In vehicular communications using 802.11-OCB links, there are strong
>> privacy concerns with respect to addressing. While the 802.11-OCB
>> standard does not specify anything in particular with respect to MAC
>> addresses
> 
> It has been suggested that there is something to think about here, which
> may affect the above statement: there is at least one country where the
> vehicle|driver information, be it physical or electronic, must be
> allowed access by law enforcement if so required.
> 
> This is noted.  I suggest we discuss this separately.
> 
> At this time I do not modify this text.
> 
> End issue.

IEEE 1609 does impose MAC address requirements.  Is this the right place to call that out?

Russ

v2.23.0 | Report a Bug | By Email