Re: [ipwave] MAC Address minor textual issue
François Simon <fygsimon@gmail.com> Thu, 18 May 2017 14:52 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 0DF0612EB5F for <its@ietfa.amsl.com>; Thu, 18 May 2017 07:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.201
X-Spam-Level:
X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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_LOW=-0.7, 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 IwdXN4sqPeXW for <its@ietfa.amsl.com>; Thu, 18 May 2017 07:52:54 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 43AC912EB28 for <its@ietf.org>; Thu, 18 May 2017 07:47:22 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id u75so37614636qka.3 for <its@ietf.org>; Thu, 18 May 2017 07:47:22 -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=U4HIrnxQsg4FwC0Vzu0NQq1YkYrQTvzjVR7pAsgwuJk=; b=HercALtiUiuvWYZJVMTUW1eQ5TXTdsbvFeMywN3qIL//4kocTwBtP+wmKMNFsDBtfT TQGnSX3WnpglCV5hFcTVdHw+4zQwSNHla1SZ8TLIErETlp8hKB80BysOy709cZeB93hU lPd2ezAmFgJs1aikOpxPE4N+YWWfvvcM5ckjiwzqATMYaTl0nFN4BTZfJAhCIljxtRmj +YRtiWV4dymEdpV980K7/qwsZRV5ccs+un8hE1Daij7RCLFbbbRAT20b5e98RZ/d+57v 9IBvwXPEVmD4g2TFZFPlBQtQ3LIDm2O0K5oprNIQ4I0JRQkVFJkrM1GCaCbUvSe6MMiY K6mA==
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=U4HIrnxQsg4FwC0Vzu0NQq1YkYrQTvzjVR7pAsgwuJk=; b=mNKbvMzN6Xil6B5m9pHP1bP7XUBRkx24sEZSang5a1rW9VSQkU2IMB2lPEoSUVFSfX f+KoYn6DcQNJ/AtmjKdKRA6SXMGuvTQaZNHUuvC3ZJu96kTAAMqcZIO/0e9UUigvop71 vZxYiCpTjtBRsuokk6O7SaZ2drAOM7ZYeUvk88kLXqOUk30f+o6aHq44yaOTAII0edWz 2TsLPn67uYXV9Me/rkwxOA0Poli45cbhRqtPyhLUaiYPkIPKi5RcsKgd7fPRnM/cncAi OlAG0vD7NpfRZvH+RuauPVNpKKXWgYipC6ufpZgstEYs3pBH/6stzZDnu355CZSHdRi5 7IMg==
X-Gm-Message-State: AODbwcDRqVbmUibrdVo+Ad+30aSnHKe+QZja4kmro+06c7+ZDNPbt7uy XfE9ODshqMWQLw==
X-Received: by 10.55.138.193 with SMTP id m184mr3917370qkd.192.1495118841496; Thu, 18 May 2017 07:47:21 -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 75sm1858061qkw.63.2017.05.18.07.47.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 May 2017 07:47:20 -0700 (PDT)
From: François Simon <fygsimon@gmail.com>
To: 'Russ Housley' <housley@vigilsec.com>, 'Alexandre Petrescu' <alexandre.petrescu@gmail.com>
Cc: its@ietf.org, fygsimon@gmail.com
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 10:47:19 -0400
Message-ID: <008601d2cfe5$a6cc8f50$f465adf0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0087_01D2CFC4.1FBD6050"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLaRBK88xykj8VYhlOq8uhoK7bq9wHFxqHEn90GxPA=
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/1RGOQMwrMZDeOJT4KwKDM-1bbD8>
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:52:56 -0000
Mr. Housley; See comments in the text. Fygs From: its [mailto:its-bounces@ietf.org] On Behalf Of Russ Housley Sent: Thursday, May 18, 2017 9:44 AM To: Alexandre Petrescu <alexandre.petrescu@gmail.com> 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 <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 [Fygs: if we are talking about privacy, I believed the statement is correct. Other methods are used in IEEE 802.11 Security to support privacy. This function would not be expected to be in the MAC sub-layer]. 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. [Fygs: This is correct. IEEE 1609 recognize this fact and such does not mandate the implementations to secure privacy whatever privacy services are provided, there may be a legal right for appropriately authorized parties to reverse that privacy for law enforcement or to ensure the correct operation of the system. ]. 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? [Fygs: I do not think there is an imposition implied here. IEEE 1609.0: IEEE 1609 standards provide primitives to change local WAVE MAC addresses to protect the privacy of the device operator. The process by which a decision is made to change the WAVE MAC address is not addressed in the IEEE 1609 standards. See 5.13.10 for further discussion.]
- [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