IETF Logo Mail Archive

RE: 64bit MAC addresses and SLAAC

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Wed, 17 June 2020 17:44 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96D823A096B for <ipv6@ietfa.amsl.com>; Wed, 17 Jun 2020 10:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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=boeing.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 Oil26RS-BU21 for <ipv6@ietfa.amsl.com>; Wed, 17 Jun 2020 10:44:56 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 C6AF63A0933 for <ipv6@ietf.org>; Wed, 17 Jun 2020 10:44:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 05HHipRO027562; Wed, 17 Jun 2020 13:44:53 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1592415893; bh=wtg07ejJtmuLAEERNAMa5H6fugfQxqogTCvZ6nQ1eKE=; h=From:To:CC:Subject:Date:From; b=kw6DLIU93R9oVjBYq/f04DW8nM0no4ybo7zfbAHwS53tmqlf40hFgJBVYjQCAAw4S DTCJGgIzMIPPsoWkrKpNNGvyH+sRkEPCC3iAmrnGoJ+gryBiq3FcP2gBdLhzRFdIe3 /cbIXTEswbzqJGUQ0FBoXaE/88Bb2MtdYz1royotjL9ClzXyngvifRsOElvoOxO3oO yzqoMjpZgvGGb8tzztj29dcujNhJ2V5FzfiJ4vew0MKN/P6SSgpAD933vHL+RGtqYg RnV9LoykaIDUtD5jE4tTR8pmiOh6MelUaWhjU60NZeGM6shwDyADQGqeEFwD7bnSuu ThysLjIxQEz3A==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 05HHifjs025764 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 17 Jun 2020 13:44:41 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1979.3; Wed, 17 Jun 2020 10:44:39 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1979.003; Wed, 17 Jun 2020 10:44:39 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: 64bit MAC addresses and SLAAC
Thread-Topic: 64bit MAC addresses and SLAAC
Thread-Index: AdZEzeuKPFYqBMu/T6aePNfVerw9Mg==
Date: Wed, 17 Jun 2020 17:44:39 +0000
Message-ID: <e716dc36b56f4806b4c4dbfbf1ab852a@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 3CBB6AA5C6BFBAE187D2F01D5AE849CEC19E37F6C4FC2BFC51F6C87AEBF07F782000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/BM7G9jyOLZPfDkDO7AiSzl0Dsg4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2020 17:44:58 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Wednesday, June 17, 2020 9:36 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> Cc: 6man WG <ipv6@ietf.org>
> Subject: Re: 64bit MAC addresses and SLAAC
> Fred,
> 
> > Fernando, I think an unspoken assumption in these past several messages is that
> > privacy is ALWAYS a required property. However, there are cases where address
> > privacy is not only not required, but it is also desirable and useful to be able to
> > track a node by a stable and unchanging IP address or prefix.
> >
> > This is not intended to challenge the non-use of MAC addresses in Interface
> > Identifiers per your documents, but just to say that in some environments the
> > randomization and constant changing of IP addresses may actual run counter to
> > operational objectives.
> 
> Implementations and operational deployments or other link-types are of course free to choose whatever recommendation (or none)
> for default IID generation.
> IID mechanisms are not protocol specifications. They are recommendations taking various parameters into account (stability, tracking
> etc).
> These are not required for interoperability.
> Configure IIDs manually if you like.

You seem to be acknowledging my point that privacy is not always a required property,
and that in some environments stability, tracking, etc. are desirable. And, for those types
of environments, placing a constant-value token somewhere in the address (whether it
came from a hardware code, administrative setting or algorithmic generation) should be
fine. Did I understand correctly?

Thanks - Fred

> Cheers,
> Ole=

v2.23.0 | Report a Bug | By Email