Re: [ipwave] 118

"Joel M. Halpern" <jmh@joelhalpern.com> Wed, 17 April 2019 16:03 UTC

Return-Path: <jmh@joelhalpern.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 B44BA12044D; Wed, 17 Apr 2019 09:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 HJCh-lSOZgRF; Wed, 17 Apr 2019 09:03:07 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C396120458; Wed, 17 Apr 2019 09:03:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 44kn8C0Lz9z17LRf; Wed, 17 Apr 2019 09:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1555516987; bh=7WMidn8FLMwkqZj4sSeL/MVRc2UqEpBKJ8m+DZfP6lk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=NawOkbrADsAqqrS1FwQHnnwdZCpgRUK3i28ih4+nfaIgUdYC6rfD4SUz7jZcxLOM8 x2R8QdM/HCJ0O6LsGBHTa3rv/4iG99OO3mLLXpGvYiaACDMbPd0VIwr9oj5orLSabS iS+Z971xRci0iB6i4DORGaTw2zwr7NaYUn1yx1mI=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 44kn894mLPzFppL; Wed, 17 Apr 2019 09:03:05 -0700 (PDT)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Eric Gray <eric.gray@ericsson.com>
Cc: "<int-dir@ietf.org>" <int-dir@ietf.org>, IETF Discussion <ietf@ietf.org>, "its@ietf.org" <its@ietf.org>, "draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org" <draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org>
References: <155169869045.5118.3508360720339540639@ietfa.amsl.com> <bcb6d12d-5b21-1f10-1afe-221321f8e7a6@gmail.com> <CAJE_bqd5t77B5ij3ot-F-ucx5+3A7LATC-VTBx3w2_kCDD8fNA@mail.gmail.com> <96574d8b-c5f4-c641-4a79-47974a18d87e@gmail.com> <b2459889-f8d6-43c0-acc2-2ffe00fb1985@gmail.com> <26900f46-88da-cf3e-9ae0-b23e056ee840@gmail.com> <ad32743d-981a-0ae7-a6ca-f7a4e9841831@gmail.com> <ece445c6-d599-152c-80aa-670495cbb64d@gmail.com> <CAJE_bqdVqPT761+59TOPHXnr5RqtjNk6WAA81_jZAogGqpJX2A@mail.gmail.com> <350c5cf2-b338-047d-e99b-db6d6a4f6574@gmail.com> <4b717f2c-e8b3-8a47-96d4-67901a98c15f@gmail.com> <f3f722c3-ace5-2e9a-7aaa-30cdc6b5980c@joelhalpern.com> <BN8PR15MB26443D676D275E0BBD30919897250@BN8PR15MB2644.namprd15.prod.outlook.com> <efbfa9be-9b54-ff12-f88e-435959f9b36e@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <beb9cbe3-fcd1-86ea-3ec3-36e4ecb9ae93@joelhalpern.com>
Date: Wed, 17 Apr 2019 12:03:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <efbfa9be-9b54-ff12-f88e-435959f9b36e@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/its/hwj5SifeB5Wp0-i29Rl91iKWqkA>
Subject: Re: [ipwave] 118
X-BeenThere: its@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Apr 2019 16:03:09 -0000

Your earlier text included the line:

"A MAC address SHOULD be of length 48 decimal."

Even if the SHOULD were not capitalized, that would look like an effort 
in this document to specify the length of a MAC address.  With the 
capitalization, it appears even more strongly to be such an effort.

One of your suggestions removed that text, which would be a good way to 
resolve this problem.  Eric's question is based on the text you sent, 
which is taken directly from the document.

Yours,
Joel

On 4/17/19 10:29 AM, Alexandre Petrescu wrote:
> 
> 
> Le 17/04/2019 à 16:24, Eric Gray a écrit :
>> Adding to what Joel said, why are we attempting to define how long a 
>> MAC address SHOULD be?
> 
> We are attempting to define how long a better privacy Interface ID (not 
> MAC) should be.
> 
> There is a difference between an Interface ID and a MAC address.
> 
> An Interface ID is what to put near a prefix to make an address.  For 
> example, 3 in 192.168.1.3 is an Interface ID.
> 
> The longer IID the better privacy, intuitively speaking.
> 
> Why do you think we try to define how long a MAC address should be?
> 
> Alex
> 
>>
>> -----Original Message-----
>> From: ietf <ietf-bounces@ietf.org> On Behalf Of Joel M. Halpern
>> Sent: Wednesday, April 17, 2019 9:39 AM
>> To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
>> Cc: <int-dir@ietf.org> <int-dir@ietf.org>; IETF Discussion 
>> <ietf@ietf.org>; its@ietf.org; 
>> draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org
>> Subject: Re: 118
>>
>> Trimmed.
>>
>> On 4/17/19 3:46 AM, Alexandre Petrescu wrote:
>> ....
>>>
>>> I propose the following:
>>> OLD:
>>>>        A randomized Interface ID has the same characteristics of a
>>>>        randomized MAC address, except the length in bits.  A MAC
>>>>        address SHOULD be of length 48 decimal.  An Interface ID
>>>>        SHOULD be of length 64 decimal for all types of IPv6
>>>>        addresses.  In the particular case of IPv6 link-local
>>>>        addresses, the length of the Interface ID MAY be 118
>>>>        decimal.
>>>
>>> NEW:
>>>>        A randomized Interface ID has the same characteristics of a
>>>>        randomized MAC address, except the length in bits.  A MAC
>>>>        address SHOULD be of length 48 decimal.  An Interface ID
>>>>        SHOULD be of length specified in other documents.
>>>
>>> Do you disagree?
>>
>> "SHOULD be of a length specified in other documents" wihtout any 
>> reference to what the other documents are or how to find them seems 
>> like a recipe for implementor error.  Can we be somewhat more specific?
>>
>> Thank you,
>> Joel
>>
>