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

I agree that the /64 boundary is beneficial for many reasons when delegating
an IPv6 prefix to a site. What the site does with the prefix internally (including
sub-delegating into longer prefixes) is entirely up to the site.

Thanks - Fred

From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Lorenzo Colitti
Sent: Friday, June 02, 2017 7:34 AM
To: Peter Hessler <phessler@theapt.org>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00

Do not support. A few reasons:

  *   The /64 boundary is beneficial for many reasons. See RFC 7421 and RFC 7934.
  *   The document lists no compelling use cases of what you can do with less than 2^64 addresses per link than you can't do with a 2^64 addresses per link.
  *   The only technical motivation in this draft seems to be "classful addressing was a bad idea in IPv4". That's not a valid argument in IPv6 because the address space is completely different. A /64 is *four billion times* bigger than the IPv4 internet. That's 10,000 times more than the difference between a grain of sand and the whole planet we live on. Such a huge scaling difference pretty much invalidates any argument that solutions that worked well in IPv4 will work well in IPv6.
  *   Routing on any prefix length is already required by the standards - see BCP 198.
Please stop trying to make IPv6 be the same as IPv4. That will take away our ability to make the Internet better once IPv4 is gone.

On Fri, Jun 2, 2017 at 11:12 PM, Peter Hessler <phessler@theapt.org<mailto:phessler@theapt.org>> wrote:
Support

On 2017 Jun 02 (Fri) at 16:11:12 +0200 (+0200), Job Snijders wrote:
:Hi Working Group,
:
:Please review the below.
:
:Kind regards,
:
:Job
:
:----- Forwarded message from internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> -----
:
:Date: Mon, 22 May 2017 04:25:28 -0700
:From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
:To: Job Snijders <job@ntt.net<mailto:job@ntt.net>>, Randy Bush <randy@psg.com<mailto:randy@psg.com>>, Christopher Morrow <morrowc@google.com<mailto:morrowc@google.com>>,
:       Fernando Gont <fgont@si6networks.com<mailto:fgont@si6networks.com>>, Nick Hilliard <nick@inex.ie<mailto:nick@inex.ie>>, Geoff Huston
:       <gih@apnic.net<mailto:gih@apnic.net>>, Brian Carpenter <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>>, Chris Morrow
:       <morrowc@google.com<mailto:morrowc@google.com>>
:Subject: New Version Notification for draft-bourbaki-6man-classless-ipv6-00.txt
:
:
:A new version of I-D, draft-bourbaki-6man-classless-ipv6-00.txt
:has been successfully submitted by Randy Bush and posted to the
:IETF repository.
:
:Name:          draft-bourbaki-6man-classless-ipv6
:Revision:      00
:Title:         IPv6 is Classless
:Document date: 2017-05-22
:Group:         Individual Submission
:Pages:         7
:URL:            https://www.ietf.org/internet-drafts/draft-bourbaki-6man-classless-ipv6-00.txt
:Status:         https://datatracker.ietf.org/doc/draft-bourbaki-6man-classless-ipv6/
:Htmlized:       https://tools.ietf.org/html/draft-bourbaki-6man-classless-ipv6-00
:Htmlized:       https://datatracker.ietf.org/doc/html/draft-bourbaki-6man-classless-ipv6-00
:
:
:Abstract:
:   Over the history of IPv6, various classful address models have been
:   proposed, none of which has withstood the test of time.  The last
:   remnant of IPv6 classful addressing is a rigid network interface
:   identifier boundary at /64.  This document removes the fixed position
:   of that boundary for interface addressing.
:
:
:
:
:Please note that it may take a couple of minutes from the time of submission
:until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.
:
:The IETF Secretariat
:
:
:----- End forwarded message -----
:
:--------------------------------------------------------------------
:IETF IPv6 working group mailing list
:ipv6@ietf.org<mailto:ipv6@ietf.org>
:Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
:--------------------------------------------------------------------
--
If Reagan is the answer, it must have been a VERY silly question.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org<mailto:ipv6@ietf.org>
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------