Re: [ipwave] MAC Address minor textual issue
François Simon <fygsimon@gmail.com> Thu, 18 May 2017 15:11 UTC
Return-Path: <fygsimon@gmail.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 C4A98129AA0 for <its@ietfa.amsl.com>; Thu, 18 May 2017 08:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.998
X-Spam-Level:
X-Spam-Status: No, score=-0.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5mUcippkokQi for <its@ietfa.amsl.com>; Thu, 18 May 2017 08:11:52 -0700 (PDT)
Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26F0D129BF5 for <its@ietf.org>; Thu, 18 May 2017 08:05:24 -0700 (PDT)
Received: by mail-qt0-x242.google.com with SMTP id r58so6063285qtb.2 for <its@ietf.org>; Thu, 18 May 2017 08:05:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=6eL4AgTZCJiFkuKOTX9Cmgd4SSr+K0UJ1TSdg7+s5vI=; b=Y30ylR1D9MpI4XWwpJYi8dz9CMicaorBdiVWQY0ak4chEgx9r4900c0as6Wg9dl51z KUOStntTTzEvALrTmfukvc8qRvHfsF3/96CafrnyAdJ9c69i0HMTchR0xDSs0Diw9fug IXPOrOiCk8gad1271ywylnUOr5PIdjkIQfB/+JZwP7VU6USZuYWdOH+t1SyR1FvGZaQo Y8lHizztt2VT1NvV3oaA4hHjr+VE45IX3y6IwZOVZddcmQ8px9a+LaQQjjCofEWLyqKE Nb+rzwIBkxEt5YTor7r2zmRL2+R4cCrRqVWv+BhXHg1OVHZu5z9mzYVggEKWka6+RRiL Ovew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=6eL4AgTZCJiFkuKOTX9Cmgd4SSr+K0UJ1TSdg7+s5vI=; b=lqQtjv2g5E63amDBvC064uXyGJiCwXO6SbYCH9ywrnn3Gm4AtmKkIHWxLs3dP+ATNz WS+zWRc30Bj+s18La7QtisW434qxlB2pDI4mS0t8BbXi0zILoiJBDq+BsX/rJLkNoWMm 4WS23xVWTxWN+yQpNRnWBWkSRvurmwwk+2I2AGf2py8Ljp/ITIaHmrml2Y0Iqf8xqjj0 Ij4sifIiMA9/lfcTUaVqJqfBLzE5VBM5/4ddDH1OUOIaBxAZrkbURSAg6gfSp0qDR5MF +E+C6EmsfhegW4c3kaMcc+wprT11vhqn6zuDG3FbdLQwLREd7Cp+Zsser1Z2QpzRltXO JXkQ==
X-Gm-Message-State: AODbwcDo49JmwCsAUi/gNdcGieoyrcO3YwDVurF3AJ1AYEJQXRJ3G/s5 f29xmxG/B9TxXA==
X-Received: by 10.200.40.178 with SMTP id i47mr4597081qti.59.1495119923329; Thu, 18 May 2017 08:05:23 -0700 (PDT)
Received: from FrancoisPC (pool-108-48-182-247.washdc.fios.verizon.net. [108.48.182.247]) by smtp.gmail.com with ESMTPSA id c202sm2834881qke.65.2017.05.18.08.05.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 May 2017 08:05:22 -0700 (PDT)
From: François Simon <fygsimon@gmail.com>
To: 'John Kenney' <jkenney@us.toyota-itc.com>, 'Jérôme Härri' <jerome.haerri@eurecom.fr>
Cc: 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>, 'Russ Housley' <housley@vigilsec.com>, its@ietf.org, fygsimon@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>
In-Reply-To: <CAP6QOWQkSod0JxSdN9U+ztPwhLu0z35w-=O=WMQL1EOi_UzwpQ@mail.gmail.com>
Date: Thu, 18 May 2017 11:05:21 -0400
Message-ID: <00a301d2cfe8$2b95de10$82c19a30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00A4_01D2CFC6.A488F900"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLaRBK88xykj8VYhlOq8uhoK7bq9wHFxqHEAmd6r9ABFBL2jJ/BPGbg
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/k6mKdT4iWig6T0hWble6lvF1eBs>
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:11:55 -0000
Gentlemen; Regardless if we are talking about MAC address changes or any other methods related to privacy, this would not be a data-plane MAC sub-layer function. Fygs From: its [mailto:its-bounces@ietf.org] On Behalf Of John Kenney Sent: Thursday, May 18, 2017 10:51 AM To: Jérôme Härri <jerome.haerri@eurecom.fr> Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>; Russ Housley <housley@vigilsec.com>; its@ietf.org Subject: Re: [ipwave] MAC Address minor textual issue Hello All: 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. The requirements are cross-layer and systemic, but also not universal for OCB (e.g. RSUs are licensed for a site and do not need privacy protection), so 802.11 would not have been the best place to address them. Stating that they are not addressed in 802.11 sounds to me like it was an oversight or omission. It was not. I agree with noting that some standards already address privacy protection, but I don't think it helps to list standards (like 802.11) that do not. I hope these comments are helpful. Best Regards, John On Thu, May 18, 2017 at 6:57 AM, Jérôme Härri <jerome.haerri@eurecom.fr <mailto:jerome.haerri@eurecom.fr> > wrote: Dear Russ, Dear Alex, Indeed, and so does ETSI ITS. So, we can keep what is there, and maybe add something like: (…)While the 802.11-OCB standard does not specify anything particular with respect to MAC addresses, higher layer stack architecture, such as IEEE 1609 and ETSI ITS does impose MAC requirements. Accordingly, similar requirements might be expected or required when operating IPv6 over 802.11-OCB without these architectures (…) Do we need to define what we mean by ‘MAC requirements’? Best Regards, Jérôme From: its [mailto:its-bounces@ietf.org <mailto:its-bounces@ietf.org> ] On Behalf Of Russ Housley Sent: Thursday 18 May 2017 15:44 To: Alexandre Petrescu Cc: its@ietf.org <mailto:its@ietf.org> Subject: [ipwave] MAC Address minor textual issue On May 18, 2017, at 5:39 AM, Alexandre Petrescu <alexandre.petrescu@gmail.com <mailto: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 _______________________________________________ its mailing list its@ietf.org <mailto:its@ietf.org> https://www.ietf.org/mailman/listinfo/its -- John Kenney Director and Principal Researcher Toyota InfoTechnology Center, USA 465 Bernardo Avenue Mountain View, CA 94043 Tel: 650-694-4160. Mobile: 650-224-6644
- [ipwave] draft-ietf-ipwave-ipv6-over-80211ocb-02 … Alexandre Petrescu
- [ipwave] RSU minor textual issue Russ Housley
- [ipwave] 802.11p minor textual issue Russ Housley
- [ipwave] MAC Address minor textual issue Russ Housley
- Re: [ipwave] MAC Address minor textual issue Jérôme Härri
- Re: [ipwave] MAC Address minor textual issue François Simon
- Re: [ipwave] MAC Address minor textual issue John Kenney
- Re: [ipwave] MAC Address minor textual issue Tony Li
- Re: [ipwave] MAC Address minor textual issue François Simon
- Re: [ipwave] 802.11p minor textual issue John Kenney
- Re: [ipwave] 802.11p minor textual issue Russ Housley
- Re: [ipwave] MAC Address minor textual issue Russ Housley
- Re: [ipwave] MAC Address minor textual issue John Kenney
- Re: [ipwave] RSU minor textual issue François Simon
- Re: [ipwave] RSU minor textual issue Rex Buddenberg
- Re: [ipwave] RSU minor textual issue François Simon
- Re: [ipwave] RSU minor textual issue Alexandre Petrescu
- Re: [ipwave] RSU minor textual issue Alexandre Petrescu
- Re: [ipwave] RSU minor textual issue Alexandre Petrescu
- Re: [ipwave] RSU minor textual issue Alexandre Petrescu
- Re: [ipwave] MAC Address minor textual issue Alexandre Petrescu
- Re: [ipwave] RSU minor textual issue William Whyte
- Re: [ipwave] RSU minor textual issue Alexandre Petrescu
- Re: [ipwave] RSU minor textual issue François Simon