Re: [ipwave] MAC Address minor textual issue

John Kenney <jkenney@us.toyota-itc.com> Thu, 18 May 2017 14:56 UTC

Return-Path: <jkenney@us.toyota-itc.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 7D6C512700F for <its@ietfa.amsl.com>; Thu, 18 May 2017 07:56:36 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=us-toyota-itc-com.20150623.gappssmtp.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 rleNfsKxrF50 for <its@ietfa.amsl.com>; Thu, 18 May 2017 07:56:34 -0700 (PDT)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (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 BF44212751F for <its@ietf.org>; Thu, 18 May 2017 07:50:52 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id z52so36888500wrc.2 for <its@ietf.org>; Thu, 18 May 2017 07:50:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=us-toyota-itc-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zasJ888p0TOpmYR9coZFsz76nB3qdpqvUBIgLDSe4Zc=; b=ZbyHqu0JKRiiVuP0bvtV+gwiWBH4qYpgQ0IGfyaguULJV8TJs3GrMVlAaeTrHf3QBt cU+2VrsPh7TokmR/XCXXV2otFOarIPOhDEjWPmpOHufPbwHU50nqQS7ByPTwFjkm5w0s oJ5t4ioAShLROgZvwQq5wnUYNuDZQTUvtmNsIaMsnRkaHmAD8BotUVT6pjg/BTC6Adgn Q2hEl5eUImWWcB7fO7DsUWBm8+BXPrjgU/Vqxi3UvcKtcnzlwhQ2ZsDE6ClKIimEp3PO D/oenglXeMBk/DY4qitsgq6vKj6dw697G62rPuEWiJVwKEKDsLwPm0Dmap4So+BjgGpf EqYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zasJ888p0TOpmYR9coZFsz76nB3qdpqvUBIgLDSe4Zc=; b=ZPpVZJIhC9m5N3kIHTIfNUH0XNPmdTXR2nvExlQB6L0YL1e2r1WiU9hpBrGag3Katd KguszltoidVC8yXfd0xznal38WczaD0sfvLGZ8sBNaxp03Yt/BqQ0l6ivux9eUC0OOdn vPTKrHhd4eaxPlKbhyGiy/uXYMJ9goUR7DOqDJE6ISQBfJzt8nNidv1l89b8tnZ23J21 PR3R6jCUalgid/poSz2Vs7J3HWwHdcbZKuv7nMrnlo0xFHiu5hrTv/YtcI1LWyu/fHPF rQJg9x6C5qs3VfhsVlEibUMgG/dT9UL2oV+VBGQdvkU+c2EZhvaSNnFSsUtkC2ZZ00Gz 68tw==
X-Gm-Message-State: AODbwcDFTvDxfv12Co+o0hV3eA2yOXj0ad9B9NxlODJRMWjspSoWjq8+ lAaKylLoCQe3pw9Wljkz5LZaDne7jhRF
X-Received: by 10.223.163.21 with SMTP id c21mr3023961wrb.38.1495119051145; Thu, 18 May 2017 07:50:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.136 with HTTP; Thu, 18 May 2017 07:50:50 -0700 (PDT)
In-Reply-To: <009601d2cfde$ad5abce0$081036a0$@eurecom.fr>
References: <b7d0f246-da90-ac56-db69-40e9e929900d@gmail.com> <13CE99A5-4B32-472A-B793-3ADC2E530409@vigilsec.com> <009601d2cfde$ad5abce0$081036a0$@eurecom.fr>
From: John Kenney <jkenney@us.toyota-itc.com>
Date: Thu, 18 May 2017 07:50:50 -0700
Message-ID: <CAP6QOWQkSod0JxSdN9U+ztPwhLu0z35w-=O=WMQL1EOi_UzwpQ@mail.gmail.com>
To: Jérôme Härri <jerome.haerri@eurecom.fr>
Cc: Russ Housley <housley@vigilsec.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, "its@ietf.org" <its@ietf.org>
Content-Type: multipart/alternative; boundary="f403045f1a5cf0f105054fcd8734"
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/DNbQThR6LhHeN4gEC8no4duwicM>
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 14:56:36 -0000

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>
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] *On Behalf Of *Russ Housley
> *Sent:* Thursday 18 May 2017 15:44
> *To:* Alexandre Petrescu
> *Cc:* its@ietf.org
> *Subject:* [ipwave] MAC Address minor textual issue
>
>
>
>
>
> 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
>
>
>
> _______________________________________________
> its mailing list
> 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