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

Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com> Fri, 16 June 2017 23:33 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 50C8112969E for <ipv6@ietfa.amsl.com>; Fri, 16 Jun 2017 16:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 TCUj0NjxnXIF for <ipv6@ietfa.amsl.com>; Fri, 16 Jun 2017 16:33:17 -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 2BC1412956C for <ipv6@ietf.org>; Fri, 16 Jun 2017 16:33:15 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1dM0jp-0000EwC; Sat, 17 Jun 2017 01:33:13 +0200
Message-Id: <m1dM0jp-0000EwC@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: <391c730c-fa75-7596-bb6b-383ea6583131@gmail.com> <0b57c999-b5df-8a44-e3fd-55cee628f3f3@si6networks.com> <20170614092327.GB30896@gir.theapt.org> <E61AFFF1-0354-41EE-8E11-50433B26BAF7@employees.org> <20170614094034.GC30896@gir.theapt.org> <A7502902-245B-499B-916B-28630CD5A824@employees.org> <20170614095910.GE30896@gir.theapt.org> <CAKD1Yr2C74Nd+NSe5MfTpaQ0z1HSotVXCohK9uDYc0sqR3rMLg@mail.gmail.com> <edbf9bf8-cd15-c0e6-f0f8-19f96f6333b2@gmail.com> <CAKD1Yr1X12T10qsUtFau2neUnA0yVnOkMsAk5UOB-KjS7qxNTw@mail.gmail.com> <20170616050718.wbpb2oqhfrvsk6fv@hanna.meerval.net> <m1dLqbv-0000GBC@stereo.hq.phicoh.net> <16648f96a35a4f41a20526fa04395996@XCH15-06-11.nw.nos.boeing.com> <557643ff-8dd8-6b21-5cc8-7ad0f4f12ced@gmail.com>
In-reply-to: Your message of "Sat, 17 Jun 2017 10:15:00 +1200 ." <557643ff-8dd8-6b21-5cc8-7ad0f4f12ced@gmail.com>
Date: Sat, 17 Jun 2017 01:33:11 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mdSqhNsz8ZcC1m-Ntqx5rkn4QnA>
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: Fri, 16 Jun 2017 23:33:20 -0000

>>> The most contentious point in draft-bourbaki-6man-classless-ipv6-00
>>> is that it tries to change the IID length used for SLAAC.
>
>I find this allegation hard to reconcile with the following sentence
>in the Recommendations section of the draft:
>
>"But operationally we recommend,
>barring strong considerations to the contrary, using 64-bits for
>SLAAC..."

The way I understand the draft, it tries to make the IID length purely
a decision of the operator.

Operators are adviced to use 64 bits, but the draft tries to give operators
the freedom to advertise a /120 and have the host use an 8 bit IID.

For obvious reasons, Lorenzo is not happy with that. I'm not happy with
that either.

But what I find curious, is that as far as I know Job has no operational
need for SLAAC. Mostly likely, Randy doesn't have an operational need for
SLAAC either.

So why is this mixed in a single draft?

What prefix related issues are encoutered by people who operate core routers?
That's a discussion that should be easy to solve.

On the other hand, there seems to be very little consensus on how to
move forward with SLAAC.