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

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 18 November 2020 03:44 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 8CEB63A1387 for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 19:44:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 PCfvqS5ZY0Bu for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 19:43:55 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B23283A1383 for <ipv6@ietf.org>; Tue, 17 Nov 2020 19:43:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 7BA14389BF for <ipv6@ietf.org>; Tue, 17 Nov 2020 22:44:48 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id eQyGzPY4aPeb for <ipv6@ietf.org>; Tue, 17 Nov 2020 22:44:47 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id C6E54389BE for <ipv6@ietf.org>; Tue, 17 Nov 2020 22:44:47 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 8B45D6A7 for <ipv6@ietf.org>; Tue, 17 Nov 2020 22:43:53 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ipv6@ietf.org
Subject: Re: Extending a /64 (ATN/IPS worked example)
In-Reply-To: <b52e6eb4-142e-2442-2c6a-9997df91b2f6@mccallumwhyman.com>
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>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 17 Nov 2020 22:43:53 -0500
Message-ID: <17871.1605671033@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/meLlzdT2WV-ZjStcVEPd4ZrC-iU>
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: Wed, 18 Nov 2020 03:44:01 -0000

Tony Whyman <tony.whyman@mccallumwhyman.com> wrote:
    >>> Each aircraft operator could individually register (e.g.) a /32
    >>> with an RIR for their Home Network Prefix. However, there are more
    >>> than 5,000 airlines and if you want to have firewall rules that
    >>> refer to "all uplink packets", an un-coordinated registration of
    >>> Home Network Prefixes would lead to a big configuration maintenance
    >>> problem for every firewall in the ATN/IPS. The
    >>>
    >>> I believe that American Airlines currently has the largest fleet
    >>> with about 1,300 aircraft. You would need a minimum of 11 bits for
    >>> this fleet - rounded up to 12 for a nibble boundary.

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

You are both right.

Picking a median size and then allowing for multiple allocations to the
larger entities probably is a better plan.
Small airlines grow and bigger airlines fail, or merge, etc.

If tweaking the number of bits here could move us from 39 bits
(which I don't yet understand the math on), to say, 32 bits, then it might
work out better.

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

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

This.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide