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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 17 June 2017 00:00 UTC

Return-Path: <brian.e.carpenter@gmail.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 6A22A129540 for <ipv6@ietfa.amsl.com>; Fri, 16 Jun 2017 17:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 C96du4Bx3qmI for <ipv6@ietfa.amsl.com>; Fri, 16 Jun 2017 17:00:32 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 6D5C7128B51 for <ipv6@ietf.org>; Fri, 16 Jun 2017 17:00:32 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id s66so28849438pfs.1 for <ipv6@ietf.org>; Fri, 16 Jun 2017 17:00:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=kYS+4eb6mpdY5MNjP+psjOKQ/4Muv0CA/j0acPbMQ/s=; b=I3kr4t88ZJuNys5Z/MoU8pWv40XFSgCkGIcBz0/jVjf6YFFA6IFepMOzcnIZdugs9u Jej6cJFWzrHz0k2bcA7nE0fRm5WQ3RgOcLSIwrBw4dycckuq23nriXhnHiJ2B4WaFooI 2rDXke0cOuifhAstYcS86ZiUw7UPAYQmMKIA+2bKFQe5ZHCUnXr5W5VXue6xaD8ydDVH nVJUVaQP+VDCMAHg8zjP6RgtqyYcBnWd2kLvotkk/vCE51bhCY5dyYQDSIMvd5alAYty YEiQs/Qzf+SOED+RzHVhki4XsqXHGKBV89ichrYZPG39Q8UMwD3WsHJpXH5+2g2Ii11p lM3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=kYS+4eb6mpdY5MNjP+psjOKQ/4Muv0CA/j0acPbMQ/s=; b=FaxWZIV0UbXAwJXLAejnre4IRmipsgqx3O1m+fpOD7+AqDI7pAVVDbXK4XB4sZmHWO 7v0t5VG+GRJcK9qLgSViO/z/H0rtp1qQvo00f3vpKHQ3yzB4aEzbgNnorLz69wIQbAWw v3aF7tpaKVjRZTFnIAgK895UmKB4Vah0rgRSDHkNM7U+tCG843TO7sjYsLQup6vraGQ/ nuhhaou585VTuq3CaLHRs0wVjxIdbTm5d2E4xLUtOde2PLbMzM4cktnLc20ZoFmSeaef pEOMg8BWvNfKK2cl/GUhY+Go8ltqo3QKMrYT7mVgcJ9Ne6iPzywVfgJLgV7DVqDPbxrf 3MsA==
X-Gm-Message-State: AKS2vOye1Y07XU4NSmnT3Bw2HLMX5iC2qu29TUYJZHAN5gs1aBhOqm1c jnkqQhfyIajUeNVN
X-Received: by 10.98.23.73 with SMTP id 70mr13504387pfx.76.1497657631682; Fri, 16 Jun 2017 17:00:31 -0700 (PDT)
Received: from ?IPv6:2406:e007:53e7:1:28cc:dc4c:9703:6781? ([2406:e007:53e7:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id b3sm6448333pfg.47.2017.06.16.17.00.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Jun 2017 17:00:31 -0700 (PDT)
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Philip Homburg <pch-ipv6-ietf-4@u-1.phicoh.com>, ipv6@ietf.org
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> <m1dM0jp-0000EwC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d21d2b7c-7e04-08a8-3f48-ed944d6368b8@gmail.com>
Date: Sat, 17 Jun 2017 12:00:39 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <m1dM0jp-0000EwC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/XguvtHM0VSAm2aAaK8HHfXHw89c>
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: Sat, 17 Jun 2017 00:00:34 -0000

On 17/06/2017 11:33, Philip Homburg wrote:
>>>> 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?

Because, I think, the word 'prefix' has three distinct aspects in
IPv6: a prefix used by a routing protocol, a prefix used by a
node to determine if another node is connected to the same link,
and a prefix used to construct the complete address of a node.
We have generally been a bit careless in distinguishing these
three aspects.

   Brian

> 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.
> 
> 
>