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

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 17 November 2020 22:48 UTC

Return-Path: <Fred.L.Templin@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 5751D3A0EB7 for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 14:48:34 -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 EcBG2qr8r7NA for <ipv6@ietfa.amsl.com>; Tue, 17 Nov 2020 14:48:32 -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 F02AD3A0E55 for <ipv6@ietf.org>; Tue, 17 Nov 2020 14:48:24 -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 0AHMmBvX027585; Tue, 17 Nov 2020 17:48:23 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605653303; bh=4/1SEmr+i4+96sRN6naF8BkbDkrV3F6SkkBNl3UH5Ok=; h=From:To:Subject:Date:References:In-Reply-To:From; b=M/B1SZLBslb0HF2WDyJSoEkCGXQARpoFkK3OLvohbJ2w77ziXPbJsleu76cHRXwC7 KzFFykkZ464fD1S5NCq8PM/EfDPyCmfKhmZkxaVUsuPDP9Xwdk84cdwbP4et/4Sb+9 z173gHfA9cXzdnILkPu/p9cfyGopbSOlHjUBijNei5t6o0Usx3EEpb16tBn4b1PVgW nhL051e/ghDsDD01TCawRDqNsr2I4lTWrmD/ycPqG2fiL/o1ywB80/KhGHgQ16nVXe k0tXpARJZ194nPlbb89Jj6/8qHNmA680bqeSqQCib7g/xEpWt+zL1sYUSMFihT/TRE S+ZQtopQhbbJw==
Received: from XCH16-01-10.nos.boeing.com (xch16-01-10.nos.boeing.com [144.115.66.5]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0AHMlGj5026585 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <ipv6@ietf.org>; Tue, 17 Nov 2020 17:47:16 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-01-10.nos.boeing.com (144.115.66.5) 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:47:15 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Tue, 17 Nov 2020 14:47:15 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: "Manfredi (US), Albert E" <albert.e.manfredi@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: Ada9K5ZwsZCWyCeZQpmVScf8+sAtLQARIIcAABCa9uD//4ObgIAAgthA
Date: Tue, 17 Nov 2020 22:47:15 +0000
Message-ID: <255a5c37a1724b22a5aeac937d8a3bc3@boeing.com>
References: <6728075c39884f40b49836e5e0061c76@boeing.com> <47e33c69-8ad9-b03e-872e-80b132af4906@gmail.com> <3ba4ac13fa304d09b7c3c6a1f0f50a9c@boeing.com> <79b67dece97044df9a15223154d15545@boeing.com>
In-Reply-To: <79b67dece97044df9a15223154d15545@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 5C4DC7F7D5D58624FE46C0EA9C35202BFB09D908D77F3038E09B24FE45F14C982000: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/tKOi18VHvlxcQW7tRn45q5wK2SA>
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:48:41 -0000

Bert, I appreciate the perspectives but we will want to use robust IID generation
capabilities such as RFC4941(bis) and RFC7217 without having to set the 24-bit ID
in each host's address. Plus, the aircraft ID is the moral equivalent of a VIN; it is
not a MAC address, nor an OUI, nor any other layer 2 addressing information
that would typically go into an IID. The aircraft ID is an identity, pure and simple.
And, if the aircraft can self-generate an MNP knowing only its ID, then it does
not have to ask the network to generate one for it.

Thanks - Fred

> -----Original Message-----
> From: Manfredi (US), Albert E
> Sent: Tuesday, November 17, 2020 2:31 PM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>; ipv6@ietf.org
> Subject: RE: [EXTERNAL] Re: Extending a /64 (ATN/IPS worked example)
> 
> -----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