Re: [Int-dir] 118

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 18 April 2019 11:57 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: int-dir@ietfa.amsl.com
Delivered-To: int-dir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBCB1200A0; Thu, 18 Apr 2019 04:57:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] 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 ERZYJkk0jC-u; Thu, 18 Apr 2019 04:57:37 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 09C51120052; Thu, 18 Apr 2019 04:57:36 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3IBvX0S039654; Thu, 18 Apr 2019 13:57:34 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5A6202064F1; Thu, 18 Apr 2019 13:57:34 +0200 (CEST)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 425E82063BB; Thu, 18 Apr 2019 13:57:34 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x3IBvX1Y026560; Thu, 18 Apr 2019 13:57:34 +0200
To: "Joel M. Halpern" <jmh@joelhalpern.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> <beb9cbe3-fcd1-86ea-3ec3-36e4ecb9ae93@joelhalpern.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6a0a77d1-1f7f-12a8-24a9-6a53d456de83@gmail.com>
Date: Thu, 18 Apr 2019 13:57:33 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <beb9cbe3-fcd1-86ea-3ec3-36e4ecb9ae93@joelhalpern.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-dir/gLEehJEpmHj-YR3b_PRKfw5QYH4>
Subject: Re: [Int-dir] 118
X-BeenThere: int-dir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This list is for discussion between the members of the Internet Area directorate." <int-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-dir>, <mailto:int-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-dir/>
List-Post: <mailto:int-dir@ietf.org>
List-Help: <mailto:int-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-dir>, <mailto:int-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2019 11:57:40 -0000


Le 17/04/2019 à 18:03, Joel M. Halpern a écrit :
> 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.

Understood. I will remove the phrase telling MAC SHOULD be 48.

(one remark though.  Some Windows people call a MAC address something 
else than what IEEE defines to be a MAC address.  For example, they 
create a MAC identifier that has nothing to do with an interface; that 
is unique across all Microsoft machines; it is useful for new devices 
like my new tablet having no RJ45 but tracked by my IT dept by a MAC 
address and disallowed to use WiFi; I forgot the name of that MAC 
address; it is called 'MAC something address'; it may be visible in 
BIOS; it is 48bit length).

Alex

> 
> 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
>>>
>>
>