RE: [EXTERNAL] Re: Extending a /64

"Manfredi (US), Albert E" <albert.e.manfredi@boeing.com> Thu, 19 November 2020 22:41 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 C58573A1327 for <ipv6@ietfa.amsl.com>; Thu, 19 Nov 2020 14:41:12 -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 sjCD6Qqk58IA for <ipv6@ietfa.amsl.com>; Thu, 19 Nov 2020 14:41:11 -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 2CCAA3A1326 for <ipv6@ietf.org>; Thu, 19 Nov 2020 14:41:10 -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 0AJMf7mp014932; Thu, 19 Nov 2020 17:41:08 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605825668; bh=79LKZiJAX5GSprhXciIsVb6nam9Vikzj9/KCMChbpuM=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=tH4zUuxe/13HT6CelHdV5DZMonalQIpKFrpfJVF30JSHRAL92AbnhpAO69NghKZ1H I95A/sX26nqZ34M3GNpm+mhpz45jYT5/qC7UCdYSTBedXNwYefFtfbGhDz6PHnhF5p y6dmx1e4uDOvcv9QNlRsk+C8fDm9ImKtQwTzuCeoGdfEDONmw4V9S4RTy0spZDUqb5 hNxvVALxno1pkyW9SPIbDwOQ71asiqqRr1T87x0R+dp14zQ8qv+yEqdsFZPDU6BeeU HMb91wzAmMZI9WIbvHODHdys5AZvT9kgP22uhNQgid9nUH/OR3HMkicfY54z/iDRVG Xga7YxORg5LCg==
Received: from XCH16-01-11.nos.boeing.com (xch16-01-11.nos.boeing.com [144.115.66.39]) by clt-mbsout-01.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0AJMf27e014879 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 19 Nov 2020 17:41:02 -0500
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; Thu, 19 Nov 2020 14:41:01 -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; Thu, 19 Nov 2020 14:41:01 -0800
From: "Manfredi (US), Albert E" <albert.e.manfredi@boeing.com>
To: Nick Hilliard <nick@foobar.org>, Mark Smith <markzzzsmith@gmail.com>
CC: 6man WG <ipv6@ietf.org>
Subject: RE: [EXTERNAL] Re: Extending a /64
Thread-Topic: [EXTERNAL] Re: Extending a /64
Thread-Index: AQHWver5ofghX1o7kESQM9kw6okchanPclsAgABmvACAAC+cAIAAXb0AgAAqEQD//3qVQA==
Date: Thu, 19 Nov 2020 22:41:01 +0000
Message-ID: <c13b8a28cd514e519b6d7b2e962704df@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> <5f505585-1328-d942-2ec2-a2d96b7b4779@foobar.org> <CAO42Z2yk5pEKGFEYk3MDDDybVDZt6GiE1Pw932n4gLaqSxGH7A@mail.gmail.com> <23487.1605731956@localhost> <CAO42Z2yesLcdRw0HrNBsUAm-x=T9OneCjPMLmq8oZ4_ZH99Tsw@mail.gmail.com> <8f6bab4b-4171-66ba-cff4-742adc10ceea@foobar.org> <01cd5a82-be72-54b8-0171-3720f25cae0d@mccallumwhyman.com> <CAO42Z2xYAut_dfQtGrwkm7VWw9NPhsa5xaE9NqjCaK9L8RoMQA@mail.gmail.com> <7c500d2b-bc44-d00e-9cc2-96046c6ec5d6@foobar.org>
In-Reply-To: <7c500d2b-bc44-d00e-9cc2-96046c6ec5d6@foobar.org>
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: F2F6695AF36027EDEEEBD327D0C7850E1C23210FF0AD12BDA76550D78E54CAF62000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9TWQ44MYZgK_PKIZ_An-z5XWYFw>
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: Thu, 19 Nov 2020 22:41:13 -0000

-----Original Message-----
From: ipv6 <ipv6-bounces@ietf.org> On Behalf Of Nick Hilliard

> Thing is, if an organisation feels that their needs for ip address 
allocation are sufficiently different from everyone else's in the world 
that they need to bypass the RIRs and apply for a direct IANA 
reservation - whether that be in GUA space or not - then the 
organisation needs to make a case which justifies this ask.

I agree with the sentiment. It's not at all obvious why the airplane ID must, of absolute necessity, belong in the prefix of an IPv6 address. This seems to have been an assumption based on previous ideas, on how one might use NSAPAs. If I got that history right. So, if that's what we expected in NSAPAs, we'll do the same thing with IPv6. Why?

Also, it seems immaterial whether these networks will ultimately be reachable from "the Internet," or not. That's an orthogonal discussion, getting into safety matters and other such. The goal of reaching mobile platforms seems to be feasible, and scalable, with plain vanilla mobile IP, as far as I've understood the problem. But for that, the IPv6 address architecture has to be used.

When cars, buses, trains, etc., also want IPv6 mobility, I would not expect them to be requesting such extraordinary accommodations?

> Obviously there's no problem discussing ideas on 6man to get the lay of 
the land, but bypassing the RIRs for addressing requirements seems to be 
an extraordinary ask, and an extraordinary request will need 
extraordinary justification.

Yes.

Bert