IETF Logo Mail Archive

Re: 64bit MAC addresses and SLAAC

Ole Troan <otroan@employees.org> Thu, 18 June 2020 06:37 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 E5EBB3A0E9D for <ipv6@ietfa.amsl.com>; Wed, 17 Jun 2020 23:37:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 gHER2y4AVOzc for <ipv6@ietfa.amsl.com>; Wed, 17 Jun 2020 23:37:33 -0700 (PDT)
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::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 C98553A0B01 for <ipv6@ietf.org>; Wed, 17 Jun 2020 23:37:33 -0700 (PDT)
Received: from [IPv6:2a01:79d:53aa:d30:2ce7:3dc4:856e:e846] (unknown [IPv6:2a01:79d:53aa:d30:2ce7:3dc4:856e:e846]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id DA8A34E11A6D; Thu, 18 Jun 2020 06:37:31 +0000 (UTC)
Content-Type: multipart/alternative; boundary="Apple-Mail-A2C269ED-8D83-44CD-B301-668082BE59DE"
Content-Transfer-Encoding: 7bit
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Subject: Re: 64bit MAC addresses and SLAAC
Date: Thu, 18 Jun 2020 08:37:28 +0200
Message-Id: <7D15A1D2-A745-4CD6-8603-33D9EDCEB1BE@employees.org>
References: <CABNhwV20QRsS6eROFVVCi8eJ9r+3Wa0DYVo5czXF190JhqQZ+g@mail.gmail.com>
Cc: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
In-Reply-To: <CABNhwV20QRsS6eROFVVCi8eJ9r+3Wa0DYVo5czXF190JhqQZ+g@mail.gmail.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
X-Mailer: iPhone Mail (17F80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/nJGHsxkMrfDcN8q1CSBpifFS-Tg>
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: Thu, 18 Jun 2020 06:37:35 -0000


> On 18 Jun 2020, at 02:04, Gyan Mishra <hayabusagsm@gmail.com> wrote:
> 
>> Why is DHCPv6 not possible? Of course there is the Android problem.
>> But I doubt that a low power IoT device would share a wifi-link with an
>> Android device.
> 
>    I used use cases where the individual or unmanaged networks in those cases may not have the expertise to setup dhcpv6 

There’s nothing intrinsic in the dhcpv6 protocol that prohibits it from being automatically set up and configured. I believe homenet did this. On the first-hop router you could eg run a dhcp server instance  per link. It’s only if you want a centralized dhcp service with relays it becomes more complicated.  

Cheers 
Ole

v2.23.0 | Report a Bug | By Email