Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard

Job Snijders <job@ntt.net> Tue, 21 February 2017 20:28 UTC

Return-Path: <job@ntt.net>
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 6ECB71296EE; Tue, 21 Feb 2017 12:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 rWoz1hpdSNQ5; Tue, 21 Feb 2017 12:28:56 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CF0812944C; Tue, 21 Feb 2017 12:28:56 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgH3F-00095y-CC (job@us.ntt.net); Tue, 21 Feb 2017 20:28:55 +0000
Date: Tue, 21 Feb 2017 21:28:21 +0100
From: Job Snijders <job@ntt.net>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170221202821.GB32367@Vurt.local>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/kDajy710Z-N-X9jC-uRgye8GyrE>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 21 Feb 2017 20:28:57 -0000

On Wed, Feb 22, 2017 at 06:43:56AM +1100, Mark Smith wrote:
> On 22 February 2017 at 04:27, Job Snijders <job@ntt.net>; wrote:
> > On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
> >> On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net>; wrote:
> >> > ps. The "Write a draft" argument is weak at best, since we are
> >> > already are discussing a draft (called
> >> > 'draft-ietf-6man-rfc4291bis-07.txt'), which is in IETF Last call,
> >> > which means it is in a place to discuss the contents of that draft.
> >> > No reason to kick the can down the road.
> >>
> >> I'm sorry, but that's really how it is. The text you dislike has been
> >> the standard for almost 20 years, and is it inappropriate to change it
> >> in the context of reclassifying this document from draft standard to
> >> Internet standard.
> >
> > Or, perhaps it is inappropiate for the -bis document to target "Internet
> > Standard" classification at this moment? ¯\_(ツ)_/¯
> >
> > Especially when solidifying recommendations in an architecture Internet
> > Standard-to-be, the utmost care should be taken to verify whether the
> > paper reality (RFCs) and operational reality (what people do, for
> > $reasons) are aligned.
> >
> 
> Flexibility isn't cheaper, it is more operationally expensive, because
> it creates opportunity for complexity and errors.
> 
> A very simple example to demonstrate the additional cost of flexibility.
> 
> You showed the the distribution of prefix lengths in an AS. That may
> have taken say 5 minutes to assemble and calculate? If all your prefix
> lengths were /64s, you could have saved 5 minutes because you would
> know the single value.
> 
> Multiply that sort of example 5 minutes over the many times you deal
> with the complexity and errors that will occur when having a range of
> prefix lengths, and that will add up to a significant amount of time.
> It was an unavoidable cost in IPv4 because it was necessary to stretch
> the usable life of IPv4's 32 bits of address space. It is an avoidable
> cost in IPv6.
> 
> IPv4 too started out with a fixed or well known boundary between the
> network portion and the host portion.
> 
> RFC760:
> 
> "   Addresses are fixed length of four octets (32 bits).  An address
>     begins with a one octet network number, followed by a three octet
>     local address.  This three octet field is called the "rest" field."
> 
> I advocate for /48s for all customers over a mix of /56s and /48s for
> the same reason. The cost of managing the different prefix lengths and
> resolving errors when the incorrect size prefix is assigned to a
> customer are significant compared to the savings in RIR fees, and
> perhaps may eliminate all those savings. When there is a single value
> or size, there is no ambiguity and no opportunity for error.
> 
> I think many network engineers (and many technical people in general)
> consider flexibility to be a a desirable property because they think
> it means they'll be able to adapt to any future requirement without
> any significant constraints. It's an understandable view (which I used
> to have), however, I don't think they often consider the cost that
> flexibility creates. I've also haven't seen that flexibility pay off
> as much as it is supposed to.
> 
> > In those years sufficient data has been collected to conclude that
> > /64 is not the "be all and end all".
> 
> Alternatively, it could show that people are applying IPv4 practices
> they're familiar with to IPv6, even when it isn't necessary. They're
> missing out on operational savings from simplicity.

Have you read rfc1925 section 2.4?

You are grossly overstating these 'operational savings'. Also, for the
sake of this dialogue I'll apply Hanlon's razor and operate under the
assumption that you are not familiar with my work environment. 

I am amazed your reaction to my sharing of real-world data is the
equivalent of "well, i think you are doing it wrong". A lack of empathy
is exhibited in that you do not wonder _why_ things are what they are.

Kind regards,

Job