Re: draft-bourbaki-6man-classless-ipv6-00

Lorenzo Colitti <lorenzo@google.com> Sun, 04 June 2017 13:10 UTC

Return-Path: <lorenzo@google.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 5C1B9129B1E for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 06:10:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 iQ1XjKWzVHKU for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 06:10:32 -0700 (PDT)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8BE6129B1A for <ipv6@ietf.org>; Sun, 4 Jun 2017 06:10:31 -0700 (PDT)
Received: by mail-ua0-x229.google.com with SMTP id u10so64384148uaf.1 for <ipv6@ietf.org>; Sun, 04 Jun 2017 06:10:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NadkxXP0qPHopjBHX49cH4RZ+QahJhD7aDipQ3Ky3jI=; b=XZ8V0EBoP4HsjgdDyAWfE1ld3ssC1k8foSiPml9d26RWvt2ImHxKBLOjSdVsJ4peXS Da2Gnt0mP8mmxgNP1cQHDKBxFdmzv+p6f8RmSUvmruZwaf0Gg4AvvgU9t5AVG53dMVGL 6oYn29IBtWuhLNBZcP/Tn7KZdj4JxDIa49Om12DFvTrv/qotkWLrf13jlyixQPnzXmd/ k+oxIzhz2ecMFWlG8/btjAsLg7XCqZsIlRzksui3gG7ur8aQT42hDAuibqpoZNjE3q3D eKKUs1o7uHBZ5duTzYXQ5wqAxRHLaUn/v34A9S7q1qCBybHW2Kz7VyZev30989jdHtL2 BUSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NadkxXP0qPHopjBHX49cH4RZ+QahJhD7aDipQ3Ky3jI=; b=U9FUI0xvx5rTrUKw/wG+J0pN96rz/uTnfFFbGGXnbqwNp97jYE7rJ2VdvtwjI+KkwX WOxNscUn8YKa7Oo/U6Egx9xdLsmDqNaA20KyawCOWWTVuXEOBx3NGrY/sxWr5CWwJKJy WYqIonGTO/p3yly3cVYCUyEPmeBGFgbNYEPtC6O5Fy+jMGex2t3gMVtbeXlkPCOpFB+5 fmmLlV2xVQhEJkpwtNdAJs/AXO/9Df5B28OZoXJJKedV8fRr4InYw8eKe3xl1asZYXUe CPuvgy8H5p5PynA5MoGYYI44St8Cz3FjN50dUvGs4PrfxtekvA34SSzPNTtKNdzawJNA BpOA==
X-Gm-Message-State: AODbwcB1co751q2z91NIgq/y5WIzNjHdlhSH26JqTSzu+7ocbGNqkxvA SopEmMCG5HozRCZofKbKcT8v+zbR98jTp6SAkA==
X-Received: by 10.176.17.228 with SMTP id q36mr6802799uac.20.1496581830901; Sun, 04 Jun 2017 06:10:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.168.138 with HTTP; Sun, 4 Jun 2017 06:10:09 -0700 (PDT)
In-Reply-To: <m1dHTLx-0000DcC@stereo.hq.phicoh.net>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <20170602141259.GD30896@gir.theapt.org> <CAKD1Yr0DtQYvCYLQexhXe_nhb5rjeyhnB4bCveqyO5Xbuwdg1A@mail.gmail.com> <CAKFn1SEdjhsQ3tKPZdbdfF4ArDzw-FZfjQT68gV55Fc-5vzBvw@mail.gmail.com> <CAKD1Yr3ppM0UF8HoN8PgS7F0iEmK26ebiuJK=tkAdZnuLWpkZg@mail.gmail.com> <CAKFn1SHASt34ihJmGN0iRFQQzLTMspZfxXHgBjBatXXcRYF4cw@mail.gmail.com> <20170604093119.nt733rb3ymmjssww@Vurt.local> <m1dHTLx-0000DcC@stereo.hq.phicoh.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Sun, 04 Jun 2017 22:10:09 +0900
Message-ID: <CAKD1Yr0ZZwRar6D-2bkXBKPYehqqW99+BMtDOjyovR8WDXKzxw@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="f403045e75fc68e5480551221cba"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/RKiEW-PcvbtSaeAmPf8M4RUgohY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 04 Jun 2017 13:10:33 -0000

On Sun, Jun 4, 2017 at 8:05 PM, Philip Homburg <
pch-ipv6-ietf-4@u-1.phicoh.com> wrote:

> Moving on to a network architecture point of view, when using pseudo random
> IIDs there will be a longest prefix that can be supported. Lets say for the
> sake of argument we can support of /96.
>
> Then the effect will be that if in the future hosts support SLAAC upto /96
> then we are back at the same hard limit. We have just moved be boundary by
> 32 bits.
>

That's *exactly* right.


> There is no reason to expect this to change if we make longer prefixes
> possible.
> It is just that end users will then end up with a /96 and find that they
> can't subdivide it any further.
>

Right. So then someone will say, "we need to extend the network at the
edges!". And we move the boundary again, to /112. And then to 120, and then
to /124, until we get to one /128 per device. But long before that, a)
SLAAC is dead because there's not enough space in the prefix to form a
random IID, b) the hosts start doing NAT because they don't want to waste
their time. We now have 128-bit IPv4. Except that at least in IPv4, address
shortage was real. In IPv6 it isn't.

Or, if we remove the boundaries altogether, we end up with /128 straight
away, because operational consistency. We now have 128-but IPv4 again.