Re: [ipwave] MAC Address minor textual issue

Jérôme Härri <jerome.haerri@eurecom.fr> Thu, 18 May 2017 14:03 UTC

Return-Path: <jerome.haerri@eurecom.fr>
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 9A4BC129BB7 for <its@ietfa.amsl.com>; Thu, 18 May 2017 07:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 NugkjaeRkkf3 for <its@ietfa.amsl.com>; Thu, 18 May 2017 07:03:24 -0700 (PDT)
Received: from smtp2.eurecom.fr (smtp2.eurecom.fr [193.55.113.211]) by ietfa.amsl.com (Postfix) with ESMTP id DD8CE129BAF for <its@ietf.org>; Thu, 18 May 2017 06:57:25 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.38,359,1491256800"; d="scan'208,217";a="6273233"
Received: from monza.eurecom.fr ([192.168.106.15]) by drago2i.eurecom.fr with ESMTP; 18 May 2017 15:57:24 +0200
Received: from xerus29 (xerus29.eurecom.fr [172.17.31.38]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by monza.eurecom.fr (Postfix) with ESMTPSA id 8E96515FD; Thu, 18 May 2017 15:57:24 +0200 (CEST)
From: Jérôme Härri <jerome.haerri@eurecom.fr>
To: 'Russ Housley' <housley@vigilsec.com>, 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
Cc: its@ietf.org
References: <b7d0f246-da90-ac56-db69-40e9e929900d@gmail.com> <13CE99A5-4B32-472A-B793-3ADC2E530409@vigilsec.com>
In-Reply-To: <13CE99A5-4B32-472A-B793-3ADC2E530409@vigilsec.com>
Date: Thu, 18 May 2017 15:57:24 +0200
Organization: EURECOM
Message-ID: <009601d2cfde$ad5abce0$081036a0$@eurecom.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0097_01D2CFEF.70E38CE0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQLaRBK88xykj8VYhlOq8uhoK7bq9wHFxqHEn90FTvA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/ISKkP1b4zbRmQV4763_otGQO9pw>
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:03:27 -0000

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