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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 06 June 2017 01:23 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 DB48112EB72 for <ipv6@ietfa.amsl.com>; Mon, 5 Jun 2017 18:23:01 -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 NvZd30-U4aM9 for <ipv6@ietfa.amsl.com>; Mon, 5 Jun 2017 18:23:00 -0700 (PDT)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (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 7A29412EB6C for <ipv6@ietf.org>; Mon, 5 Jun 2017 18:23:00 -0700 (PDT)
Received: by mail-pf0-x22b.google.com with SMTP id 83so33101072pfr.0 for <ipv6@ietf.org>; Mon, 05 Jun 2017 18:23:00 -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=4llVZZUlkv3X95CQearIFbqjuHEcV/5MBVOq4qetp8Y=; b=lp4/9dR5IF/1mm9w4mBl9ec+/c2cVP5swx7Wg0PfGN/P9HzfEc4p8R5Oxcvd3tIn9r UGXJkOq5cl0n1xKfa5EPGWd045ZgRi3EXcqHpww0Jx2if9SkcYdHE7X4/Cn3fHIOKXAi /6AJ7/EGiwrZUV4b52PvwwZXHFtdzYFAAqzll7bvOoN3+NeCOQLPXJgQ1QaIPTYL0Nq9 p+36VD/q3trGk//p0ViXXAMhbY0YnekPmQW5atWEtgshwWk1xLtk9L6qb0yL13oyHAO4 mKDULP7OKApv+8dsJqg+21acI++ewY8HNa/VkCt5rAAnXao9V/mEfXLJmgo1QVQSyhNC oHMg==
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=4llVZZUlkv3X95CQearIFbqjuHEcV/5MBVOq4qetp8Y=; b=GS4sAIPInmrFkiIh9s4EEoEIYua7YsurJa874YIfZHSgQVVVFlGMifZybSs+3sV6Cy XRkdbaCcVX1IVjj7RaHbroA+JRuKzaaNXlX6LAmhrwPscpllkPH4dJIFueiulS/ErKY8 GCw/MdalLYUMXFz8L8qbKYc75hE/XhazBbaYp2e3rfWeBjlq+3pUfi72sG7OOCSZdqW6 QEIkRHSFk/A581jiiScoT3jhRAaqCmv7e20KpPu4IqHfbfgE283SS8Y/nzSAStYhTd7X 0zAl+duiJOQ6Sa7k4oki+Bm2F1Ulgcva811CTNx6S/yDyMT7a+2qwRDCuBkIfJP2nROC 9B+w==
X-Gm-Message-State: AODbwcC5/OTVLQ5MnI0cexLQJ1eLgYmRNvQGKpnbfFbKeuUzRmRyhFx+ 36Pqw1mPiD/tAPZl
X-Received: by 10.99.174.77 with SMTP id e13mr23997040pgp.145.1496712179906; Mon, 05 Jun 2017 18:22:59 -0700 (PDT)
Received: from ?IPv6:2406:e001:5517:1:28cc:dc4c:9703:6781? ([2406:e001:5517:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 67sm60506982pfn.84.2017.06.05.18.22.58 for <ipv6@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Jun 2017 18:22:59 -0700 (PDT)
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: ipv6@ietf.org
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> <3bca0f2c-78be-4554-33a3-53240864fa63@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <18bc765d-8900-c986-2757-870822a0a9f7@gmail.com>
Date: Tue, 06 Jun 2017 13:22:58 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <3bca0f2c-78be-4554-33a3-53240864fa63@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9CN8KMsiCMv4dKgPjHWpn6nhrvQ>
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: Tue, 06 Jun 2017 01:23:02 -0000

On 05/06/2017 21:53, Alexandre Petrescu wrote:
> Le 04/06/2017 à 13:05, Philip Homburg a écrit :
> [...]
>> 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.
> 
> Similar worries were expressed.
> 
> However, as I read this draft it does not propose to substitute new hard 
> limit for old hard limit.  The proposal is leave it at 'n', i.e. a variable.
> 
> The optimistic evolution of this could be that in some IP-over-foo this 
> variable could be exceptionally /96 and largely over-ridden by a 
> backward compatible /64.
> 
> Maybe something could be written down that clarifies this is not a
> proposal to substitute new hard limit for old hard limit.

Alexandre,

I think that is what the draft says. Most of the discussion here has not
been about what the draft says, but about what operators who don't read
RFCs anyway might or might not do because they don't understand that IPv6
isn't IPv4+. That's an interesting discussion, but I wish people would
give it a relevant subject like "IPv6 isn't IPv4+".

  Brian