IETF Logo Mail Archive

Re: 64bit MAC addresses and SLAAC

otroan@employees.org Mon, 22 June 2020 10:14 UTC

Return-Path: <otroan@employees.org>
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 6DBD03A0A6D for <ipv6@ietfa.amsl.com>; Mon, 22 Jun 2020 03:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=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 Fu6U4XXue12T for <ipv6@ietfa.amsl.com>; Mon, 22 Jun 2020 03:14:16 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [198.137.202.74]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 407EB3A0A6C for <ipv6@ietf.org>; Mon, 22 Jun 2020 03:14:16 -0700 (PDT)
Received: from astfgl.hanazo.no (unknown [IPv6:2a02:20c8:5921:100:551e:6386:f36c:89fb]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 102814E11A4F; Mon, 22 Jun 2020 10:14:15 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by astfgl.hanazo.no (Postfix) with ESMTP id 1ACCB37402E8; Mon, 22 Jun 2020 12:14:10 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: 64bit MAC addresses and SLAAC
From: otroan@employees.org
In-Reply-To: <m1jnIY2-0000NqC@stereo.hq.phicoh.net>
Date: Mon, 22 Jun 2020 12:14:09 +0200
Cc: 6man WG <ipv6@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FB6873C-95AE-445C-9820-09AF78AAB669@employees.org>
References: <e716dc36b56f4806b4c4dbfbf1ab852a@boeing.com> <04B8995F-7BF9-4DB0-826C-9E4BF95FD169@employees.org> <43ce64f0-3373-ca9a-f83d-40c44c4d5920@gmail.com> <m1jlwVZ-0000RgC@stereo.hq.phicoh.net> <MN2PR11MB356561378679A6AD1CA895B4D8980@MN2PR11MB3565.namprd11.prod.outlook.com> <m1jmHAN-0000OcC@stereo.hq.phicoh.net> <MN2PR11MB35652DAAA66B512ECB644A8FD8980@MN2PR11MB3565.namprd11.prod.outlook.com> <m1jmI0D-0000N6C@stereo.hq.phicoh.net> <MN2PR11MB35659E7213F585108CFDA514D8980@MN2PR11MB3565.namprd11.prod.outlook.com> <m1jnIY2-0000NqC@stereo.hq.phicoh.net>
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/psSmlIHQRfomABxtSzxHP8cIou4>
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: Mon, 22 Jun 2020 10:14:17 -0000

Philip,

>> - the router still needs the resolution. There's stuff in
>> draft-ietf-6man-grand and/or RFC 8505 for that.  - handling mobility
>> vs. anycast. There's stuff in draft-ietf-rift-rift-12#section-4.3.3.3
>> for that.  - all NBMAs are not hub and spoke so there's a routing
>> game to trigger. There's stuff in draft-ietf-roll-unaware-leaves
>> for that.  - still need to feed the mapping server for the overlay.
>> There's stuff in draft-thubert-6man-unicast-lookup for that.  -
>> zerotrust / SAVI is also missing and SEND did not cut it. There's
>> stuff in draft-ietf-6lo-ap-nd for that.
>> 
>> For more detaiuls, there's draft-thubert-6man-ipv6-over-wireless,
>> just let you go over it and comment if you really care.
> 
> Link address resolution can be solved to colocating a DHPCv6 relay with the
> router. The relay can maintain IPv6 address to link layer address mappings
> and inject those into the router's neighbor cache.
> 
> It seems to me that letting a host generate an address using SLAAC and then
> forcing the host to register the address somewhere is just all of the work that
> DHCPv6 does with none of the benefits.

Indeed.

> Of course, if DHCPv6 would be allowed to have a default router option, then the
> use of multicast could be reduced even further.

If there is interest I suppose I could ask for adoption of:
https://datatracker.ietf.org/doc/draft-troan-6man-universal-ra-option/

Cheers,
Ole

v2.23.0 | Report a Bug | By Email