Re: Extending a /64 (ATN/IPS worked example)

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 17 November 2020 20: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 F30603A09EB for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 12:00:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 nrvWhfLgRY3F for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 12:00:14 -0800 (PST)
Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) (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 418623A03AA for <ipv6@ietf.org>; Tue, 17 Nov 2020 12:00:03 -0800 (PST)
Received: by mail-pl1-x630.google.com with SMTP id s2so10842881plr.9 for <ipv6@ietf.org>; Tue, 17 Nov 2020 12:00:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=+gM3nMfyOA27soiK0J9hVwstXb4IMliVai+vr7XiLuc=; b=ooTuCAuM9+zNyvzvsI50VBt4OcUpBpDLKn73NictMNkHKbZlL5wdqIEgmcVvJdehDs W6NSgTV+ywWwC7aT8A8ofwpe8CjwUaS5KCElFHljEhrc9/abEKqRkw34J/YnHbJ/9MCq Mw1lMS1ZwmdacO3+Q6wZkYK4Y1baH1okj4Dxtxdzaf0hM87Br6pWoxxpaz6Eu95bp/Co fvHajTFIXME60JDsauMRQQN4rIEz0Zvi+ri40/JmyYyDljqRQUoqlTbGCFPDAJLN9awe JhpDkkJsN/PenuawCeK6ZP0kHZ+mpSMKiLiRPih66fOZMRv/vld8F+5yLWya0XFOyykO hKKA==
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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=+gM3nMfyOA27soiK0J9hVwstXb4IMliVai+vr7XiLuc=; b=WDzzygLyHREddtHd9DWNh/rEh+Ml/1Vgy4Pwa0KdmK59yDhQ+fpKGE5WL58n3NzUWA tJiwr3ISM671q4USJbPyTbtsxsIZrjs4SNVOZkBYgeR9kyev/HSU1UU8/wWPzF6zysQ9 cKB7fIex0pGajuH3xH+DPwPLNoGGf4eAcWaX2Q0/BgiPoo3or3LOr7y1akGacptAH/8n reKqUxxS2hmHkcTf1e9h0wALEiuY1A+NDGxOYzFmMYTH03rt9+oBWkrAfoDa7dqstOG4 tQZJYqNHpmuihN1R3zQsKViQPqAJj+wMJidvhhXjdcM+cWiEPVoRDct4IVIstZJF/glk z9ow==
X-Gm-Message-State: AOAM531BI0Hep9G2obwS2c6lBN0legsVpQKvcsVc5hNhWcXHzX+CVvxU 23pOSPsKziTBs3RtnkTHowihmygvDNaMeA==
X-Google-Smtp-Source: ABdhPJx2QjRs9B7pezep0SPYzNSxe/mEC6z0YasBP3G0ZcnP96rMwpyUNgridOmVC3LDQWqExOKx6A==
X-Received: by 2002:a17:90a:1f0b:: with SMTP id u11mr657795pja.105.1605643202064; Tue, 17 Nov 2020 12:00:02 -0800 (PST)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id s6sm23530955pfh.9.2020.11.17.11.59.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Nov 2020 12:00:01 -0800 (PST)
Subject: Re: Extending a /64 (ATN/IPS worked example)
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
References: <202011151920.0AFJKN9U003337@mail2.mwassocs.co.uk> <3d26bffe-b6c9-4ed7-6135-a515f9902fd7@gmail.com> <m1keOTi-0000EGC@stereo.hq.phicoh.net> <CAO42Z2wZkXryhw1u5WAFdtCvXHyyz1zeM22FP_gRxjurjsG-Jw@mail.gmail.com> <CAN-Dau2XTRJpR9S=ZXOXOD6PkxLTD7KAzN-CwoGhMUmSQTp0Zg@mail.gmail.com> <91d4b7d4-5477-50c0-fb34-5e7bbfdfb253@gmail.com> <ad5ee6e1-c402-f9d4-80a2-f9f0fd5c3da5@mccallumwhyman.com> <m1kezKE-0000FAC@stereo.hq.phicoh.net> <b52e6eb4-142e-2442-2c6a-9997df91b2f6@mccallumwhyman.com> <m1kf3Jt-0000LAC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <38503680-a3f6-4375-e1da-2b7be7253ca4@gmail.com>
Date: Wed, 18 Nov 2020 08:59:56 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <m1kf3Jt-0000LAC@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/gMJeoiKDVePQjJgvgdyBl7MHe0E>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Nov 2020 20:00:22 -0000

On 18-Nov-20 04:55, Philip Homburg wrote:
> In your letter dated Tue, 17 Nov 2020 15:02:40 +0000 you wrote:
>>> This a clear example of a bad addressing plan. If you have 5000 airlines and
>>> the biggest has 1300 aircraft then you don't give all tiny airlines the
>>> same amount of space you need for the biggest.
>>>
>> It's only a "bad addressing plan" if your sole success criteria is dense 
>> allocation. IPv6 should have liberated us from such a narrow success 
>> criteria. The success criteria that I am invoking include cost of 
>> administration and legacy support.
> 
> 'should have' is an interesting concept. We can't really go back in time.

To be clear, the IPv6 *fixed length* address model changes the parameters
of allocation practice because of moving from (say) 24 to (say) 64 bits
of routeable prefix, but in no way changes the philosophy of allocation
practice. IPv6 has ~64 topology bits instead of ~24; the actual numbers
in the H-ratio calculation change; the potential lifetime of the address
space expands enormously; the economic value of address space collapse
enormously. But all of that breaks if you start assigning address bits
non-topologically. That's why IPv6 and IPv4 share CIDR as the basis
for both prefix allocation and wide-area routing.

To get away from that, we'd indeed have to jump into our time machines,
go back to a meeting that happened just outside O'Hare airport in early
1994, and agree on a variable length addressing scheme.

> Technically we can just do a complete overhaul of the IPv6 addressing 
> architecture. But I doubt that people who now have existing IPv6 networks and
> products would be interested in that. Changing a widely adopted
> architecture also has a huge cost.
> 
>> I also do not see the point in having a different (shorter) prefix 
>> length for aircraft in smaller airlines compared with those in larger 
>> airlines.
> 
> Well, ISPs with few customers have a longer prefix than those with many
> customers. I guess you propose that we should have taken the shortest
> prefix needed for the largest ISP in the world, and then give the same
> prefix to every last tiny ISP as well?

Exactly. An operator of any kind should get a prefix that matches their
current and projected requirements. That's what CIDR-based allocation
is all about. Airlines are no different.

   Brian

> 
>> If you are arguing for dense allocation as a general rule then this 
>> should apply to the whole /64 prefix. I assume that you are demanding 
>> that ISPs allocate a /64 to all their users unless they can make the 
>> case for multiple subnets and, even then, are parsimonious in their 
>> attitude and push back hard against any user that wants more than a /60, 
>> demanding proof that they have more than 256 subnets.
> 
> You can make that argument, but is not part of the design of IPv6. The
> design of IPv6 is the endusers should always have enough space to number
> their networks.
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>