IETF Logo Mail Archive

Re: RFC4941bis: consequences of many addresses for the network

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 24 January 2020 17:22 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 2AA8E120B64 for <ipv6@ietfa.amsl.com>; Fri, 24 Jan 2020 09:22:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 JBhxjDFHdY1W for <ipv6@ietfa.amsl.com>; Fri, 24 Jan 2020 09:22:38 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99008120B66 for <ipv6@ietf.org>; Fri, 24 Jan 2020 09:22:37 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C57063897F; Fri, 24 Jan 2020 12:22:02 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DCECA60A; Fri, 24 Jan 2020 12:22:36 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
cc: ipv6@ietf.org
Subject: Re: RFC4941bis: consequences of many addresses for the network
In-Reply-To: <m1iuwJV-0000MAC@stereo.hq.phicoh.net>
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <e936078e-01f9-0254-a8d0-4095455154ac@si6networks.com> <D85412DF-4B03-4790-9E39-968D50ECF86B@employees.org> <m1iuwJV-0000MAC@stereo.hq.phicoh.net>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 24 Jan 2020 12:22:36 -0500
Message-ID: <31399.1579886556@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/AC45le-XmvZlJeB8nPPjUozyDrY>
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: Fri, 24 Jan 2020 17:22:40 -0000

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> wrote:
    > However, given the desire to fit everything in SLAAC, what is missing at
    > the moment is a way for the network to express intent.

    > The most basic way would be for a flag that disables temporary addresses.

    > A more adavanced option would be specify limits on the number of temporary
    > addresses and possibly ways to register/deregister an address. For example,
    > nodes can keep addresses alive be periodically generating a NA for the address.

I would love to see an RA option with a byte in it that said how many slots
per mac address the router supported.

A value of 0 would force temporary addresses off.

Probably "0" would imply that there were actually two slots available per MAC
(LL and one ULA).

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email