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

Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com> Sun, 04 June 2017 14:26 UTC

Return-Path: <pch-b7900FA3D@u-1.phicoh.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 97A7F129B33 for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 07:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level:
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 PUST0axOPcte for <ipv6@ietfa.amsl.com>; Sun, 4 Jun 2017 07:26:27 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id B2DA1128B4E for <ipv6@ietf.org>; Sun, 4 Jun 2017 07:26:26 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dHWU5-0000HLC; Sun, 4 Jun 2017 16:26:25 +0200
Message-Id: <m1dHWU5-0000HLC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
From: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>
Sender: pch-b7900FA3D@u-1.phicoh.com
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <CALx6S34y1ZS95dD6Qv5A90RnKwh2NqC=VDaZ2vSq+zpo5+NpUg@mail.gmail.com> <5932DA16.9040008@foobar.org> <CAKD1Yr3HkiAweix3fhxT2+9moj7eP2AGRtf7hESpOKihKMCUOg@mail.gmail.com> <CALx6S36b_8z2_vi4T8ZNKs72v5rKAR9YpBWz+r+xb-J-yO4sfQ@mail.gmail.com> <CAKD1Yr0s9TN3dYayhzKqX58yMC39vhGxcVi8+c3b2_VPNiyxwQ@mail.gmail.com> <20170604124829.GI30896@gir.theapt.org> <CAD6AjGR-Bgu2-JdrouiNWtVhj8fkkuH-gJQo9UkG5jWMx4sJ_Q@mail.gmail.com> <CALx6S37=DgrZeUbm7N5afEHmo-sGCUb3gYsmsXrcjehR8RZyXw@mail.gmail.com>
In-reply-to: Your message of "Sun, 4 Jun 2017 07:13:21 -0700 ." <CALx6S37=DgrZeUbm7N5afEHmo-sGCUb3gYsmsXrcjehR8RZyXw@mail.gmail.com>
Date: Sun, 04 Jun 2017 16:26:24 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/5ZiCRQDNEdjR58a1a-3v-lAj860>
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 14:26:29 -0000

In your letter dated Sun, 4 Jun 2017 07:13:21 -0700 you wrote:
>That is not what we are proposing (in ILA at least). This is not
>intended to work over the Internet. Mobility would be implemented
>within a carrier network, external to that network it is transparent.
>Logically, this provides the same functionality as encapsulation does
>with the benefit of not incurring the overhead of encapsulation.

The current IPv6 address architecture is basically a relatively densely
allocated /64 prefix plus an extremely sparse 64-bit IID.

With DHCPv6 you can today have dense IIDs that allow space for experiments.

However, without a clear consensus that embedding identifiers in IPv6
addresses is good idea, it strikes me as bad to use that as an argument
to change how SLAAC works.

At least for me, messing up the IPv6 address architecure just to save the
overhead of encapsulation is not worth it.