RE: [EXTERNAL] Re: Extending a /64

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Sun, 15 November 2020 23:12 UTC

Return-Path: <albert.e.manfredi@boeing.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 43BEB3A1064 for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 15:12:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, RCVD_IN_MSPIKE_H2=-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=boeing.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 95JYNXQwRjtB for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 15:12:34 -0800 (PST)
Received: from ewa-mbsout-01.mbs.boeing.net (ewa-mbsout-01.mbs.boeing.net [130.76.20.194]) (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 F2FD33A105E for <ipv6@ietf.org>; Sun, 15 Nov 2020 15:12:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 0AFNCUST055697; Sun, 15 Nov 2020 15:12:31 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605481951; bh=27T2yfpYwM9pMGO7kEsd4OSCCEDv3olHqcEP9Z7KCsk=; h=From:To:Subject:Date:References:In-Reply-To:From; b=QzbqhjuBfVl5g7FnHIB/H/SezZMRNzU4jTOK2SxBL1Fp2uA7AfrXAs888EHXYPNfX Q+LA7sM8RiE5cI1bG53fvwIS2T1wo9Zfw2Aj1bW9q4s0jMmy7000AIHBrUz8WB38nJ pPhSGh9Sn9yrkx191iYYMDY1M95nC+IbDzj3lvlNz3jgmE+woUeoTrI8QO1aBVXCwC 1wtSlEb20KwWiGQFMG6en9G8KV3wSwTwpAMQuqdWf/bAjBMIehhOCihxN6c//ANBAY H3JTRrlQKcmKAJqA7BBfo96dD27EruXz0U0jFivb+MwCTNAhkzPoSqzcaVxN340Hi5 RBKEco4jzIcTQ==
Received: from XCH16-01-11.nos.boeing.com (xch16-01-11.nos.boeing.com [144.115.66.39]) by ewa-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0AFNCJ3t055551 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Sun, 15 Nov 2020 15:12:19 -0800
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-01-11.nos.boeing.com (144.115.66.39) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Sun, 15 Nov 2020 15:12:18 -0800
Received: from XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b]) by XCH16-01-11.nos.boeing.com ([fe80::c57c:39bc:4c0a:384b%4]) with mapi id 15.01.2044.004; Sun, 15 Nov 2020 15:12:18 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: Extending a /64
Thread-Topic: [EXTERNAL] Re: Extending a /64
Thread-Index: AQHWu18TSAPYQn9dKU+Kr3IaOFR/aKnKGBIAgAAIXQD//4H0LIAAkFcAgAAS5ID//4F3fIAAicoA//99xkA=
Date: Sun, 15 Nov 2020 23:12:17 +0000
Message-ID: <9f6aa80bf79748a49e389d32c33eed2f@boeing.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> <29299.1605477799@localhost> <m1keQWu-0000LoC@stereo.hq.phicoh.net> <bf703645-6d9d-9592-61b1-ff4d00d43aa4@gmail.com>
In-Reply-To: <bf703645-6d9d-9592-61b1-ff4d00d43aa4@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [144.115.204.6]
x-tm-snts-smtp: 62AB06E1F19E03070AF11E63121B05C2B8B906B112933A8878A7CFB7D2A065172000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mIsdKVIHRL5JF9jnJJ627qgYJ_M>
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: Sun, 15 Nov 2020 23:12:35 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Brian E Carpenter

> On 16-Nov-20 11:29, Philip Homburg wrote:
>>
>> Assuming 16 billion people in the year 2100, then a 39 bit number for planes
has space for 34 planes for each person alive.

That's a little bit apples and oranges. You expect many, many more addressable devices, not to mention routers and subnets, on any large platform, than you would on a "person." I don't think it's logical to associate address space with number of people. Not directly, anyway. (Maybe eventually, when we all have hundreds on embedded medical sensors in our bodies, people and platforms will be more similar?)
 
>> Maybe that is overdoing it a bit. Or if we have that number of planes, maybe
a single prefix is a bit silly.

Amen.

> It's more than that. It's just wrong and doesn't match how Internet WAN routing works.
>
> We might as well admit that 3GPP/5G gets worldwide mobile connectivity right and the Internet doesn't.

Amen to that too. Although it doesn't go far enough, right? We're hauling along intranets now, not just one /64.

Also, I work with ships rather than planes. I can guarantee that a single ship would not be happy with one /60, if we are to assume that IIDs are 64 bits wide. Not even close, and this has next to nothing to do with how many souls are on board.

It's also not clear why a single platform should be fed off a single prefix. In fact, different onboard nets are administered by different organizations, so that the normal case would be, each organization assigns its own prefixen.

In practice, I'd say, we should not assume that excomm and interior communications would be managed the same way. In fact, they are not.

Bert