RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Tue, 17 November 2020 22:30 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 3A6B33A0E11 for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 14:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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_DNSWL_MED=-2.3, 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 ZZu0O_LigXEX for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 14:30:50 -0800 (PST)
Received: from clt-mbsout-01.mbs.boeing.net (clt-mbsout-01.mbs.boeing.net [130.76.144.162]) (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 B94293A0DFA for <ipv6@ietf.org>; Tue, 17 Nov 2020 14:30:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 0AHMUeTF012032; Tue, 17 Nov 2020 17:30:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605652242; bh=gq0OaapfzFohK6EOL80M3ZZ6coYPm1VKv4bKe4W5rSw=; h=From:To:Subject:Date:References:In-Reply-To:From; b=Kiq9uLF6bb0XVUNqOJM5932nOoIrpq8pAfITmdP8S4KwwfO3zQ+vPEr4eoIPvHPu/ na1TETPuR+3TcnKefFRBG54MbfkWoSbv0/QBnQg2yGVPSVXATCEdwyEuH3TyCwtJg1 3GazjJUt58Wtq0JkMq1iOxKwhEjg18Pu8vdHl9gE9AP3J9M6YI1Mkeglc3PJI8g+74 PNrBjnLzMMM24fWTbbPWOmLLWl8lxxhFbfJy8TIROWqXAhJ5CCrGHKv0zBDnT6W2hH IinVHyNNQSgc+ydFtxTLCseLtbhzxku0+TaRXQB90Gdmuy+MnlwiU8MvqU6z/2YfiR HmBkt/KVASf1A==
Received: from XCH16-07-08.nos.boeing.com (xch16-07-08.nos.boeing.com [144.115.66.110]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0AHMUbMO011978 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <ipv6@ietf.org>; Tue, 17 Nov 2020 17:30:37 -0500
Received: from XCH16-01-11.nos.boeing.com (144.115.66.39) by XCH16-07-08.nos.boeing.com (144.115.66.110) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Tue, 17 Nov 2020 14:30:36 -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; Tue, 17 Nov 2020 14:30:36 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)
Thread-Topic: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)
Thread-Index: Ada9K5ZwWz4mPAGrS4OXbJJSrwUMPQARIIcAAAA+lgAAEFIHMA==
Date: Tue, 17 Nov 2020 22:30:35 +0000
Message-ID: <79b67dece97044df9a15223154d15545@boeing.com>
References: <6728075c39884f40b49836e5e0061c76@boeing.com> <47e33c69-8ad9-b03e-872e-80b132af4906@gmail.com> <3ba4ac13fa304d09b7c3c6a1f0f50a9c@boeing.com>
In-Reply-To: <3ba4ac13fa304d09b7c3c6a1f0f50a9c@boeing.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: 40133F1A2C6EEFBCF7AC11CDF11FE574DE8173759011EE799CB454B7F90BE2622000: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/QbDeh2Jb8P5D_4RpCLhDdxoD0yg>
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 22:30:56 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Templin (US), Fred L

> From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com]
>>
>> I can see the value of having it in the address, assuming you have some kind of authentication of the address. Why does it specifically need to be in the prefix?
>
> It needs to be in the upper 60 bits, because the lower 68 bits are used for on-board
subnetting and assigning interface identifiers to on-board network nodes.

IMO, it's always going to be difficult to assume so many changes to existing practice and existing conventions, all at once.

Doing this is a more conventional way, you could request a /48 or a /56 (at least) for each airplane, as their home address. That prefix could belong to the country home base of the airline, for example, exactly as one would expect. Without taking away prefix bits to identify an airplane.

Use the 16 or 8 bits for on board subnetting. Use up, say, 24 or 39 bits of the IID in each subnet for whatever airplane identifier. Now you have only one fight on your hands: an IID that is not purely random.

I'm with Brian. The natural location of non-topological bits is in the IID. No surprise, as they were originally thought to incorporate the MAC address. Which is non-topological, and incorporates 24 bits of OUI.

Bert