Re: IPv6 address usage

Fernando Gont <fgont@si6networks.com> Tue, 28 January 2020 01:37 UTC

Return-Path: <fgont@si6networks.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 1BDCF3A086B for <ipv6@ietfa.amsl.com>; Mon, 27 Jan 2020 17:37:25 -0800 (PST)
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 hwU8lh60iDFZ for <ipv6@ietfa.amsl.com>; Mon, 27 Jan 2020 17:37:23 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 336893A084A for <ipv6@ietf.org>; Mon, 27 Jan 2020 17:37:22 -0800 (PST)
Received: from [192.168.100.103] (unknown [186.183.48.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 84B8C86BA5; Tue, 28 Jan 2020 02:37:14 +0100 (CET)
Subject: Re: IPv6 address usage
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: IPv6 List <ipv6@ietf.org>, "Pascal Thubert (pthubert)" <pthubert@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <2044DC74-3529-45BF-9886-56030B5EA515@gmail.com> <059D9CB7-9677-4CD2-BCDC-2393FA072BD7@cisco.com> <240550a2-803b-b108-5261-564c22a1eae0@si6networks.com> <30845.1579886425@localhost> <70bc3e67-796e-983c-c418-8d5e189f820c@si6networks.com> <14350.1579897423@localhost>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <02cb44e7-d679-ca82-0e0d-0ab1d7170def@si6networks.com>
Date: Mon, 27 Jan 2020 21:03:29 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <14350.1579897423@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/34H6LtO6lLBFmDmR19d8zVhfb-s>
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: Tue, 28 Jan 2020 01:37:29 -0000

On 24/1/20 17:23, Michael Richardson wrote:
> 
> Fernando Gont <fgont@si6networks.com> wrote:
>      >> I think that it is reasonable to establish an upper limit (8? 16?) of number
>      >> of entries per MAC address in a border router in those environments.
> 
>      > HOw would that go along with RFC7834/BCP204?
> 
> 1) Number of Neighbor Cache Entries, not necessarily addresses...
> 2) there is a different between avoiding the limit of "1" address and
>     suppporting NCE 2^8 per host.  A /64 delegation occupies 1 NCE, or
>     more accurately, 1 TCAM entry. It's likely that routing and NCE
>     occupy the same TCAM.
> 3) a problem with PD per-host is that the upper bits are now unique for host,
>     which makes 4941 somewhat useless, because you can't really hide in a
>     crowd of one.

Well, in that case, that would imply your adversary knows you're 
connected to a one-prefix-per-host network.



>      >> This is exactly the place where temporary addresses make the most sense.
>      >> The only reason it isn't a problem now is because (a) lack of IPv6,
>      >> (b) most coffee-shop visits are shorter than lifetime.
> 
>      > Where, specificallt, would you expect temporary addresses to be causing
>      > trouble?
> 
> On a network like the IETF's, where supporting 1500 laptops winds up
> requiring 64K NCE entries in every router, and we have only 8K.

Questions:

Does the network really hit 64K as a result of temporary addresses?

(that would also assume that clients employ multiple long-live 
connections issued during the week. Otherwise, while a client might have 
multiple valid addresses, you wouldn't hear from them).

Any clues whether folks would use DHCPv6 if they could? (for all 
practical purposes)



> On a campus network I can see there being 30,000 student-devices.
> If we allow for 8-16 per device, that's probably manageable, but 200 per
> device is not.

The underlying problem is that we slaac, you don't get to allow or 
disallow. But rather advertise and hope for the best.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492