Re: Extending a /64

S Moonesamy <sm+ietf@elandsys.com> Sun, 15 November 2020 14:52 UTC

Return-Path: <sm@elandsys.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 280303A1316 for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 06:52:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 UgBBu84-JsGQ for <ipv6@ietfa.amsl.com>; Sun, 15 Nov 2020 06:52:50 -0800 (PST)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCBE3A1314 for <ipv6@ietf.org>; Sun, 15 Nov 2020 06:52:49 -0800 (PST)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.132.182]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 0AFEqZJa002888 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Nov 2020 06:52:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1605451967; x=1605538367; i=@elandsys.com; bh=j4btlVe1LQq3JtGqg9jwymyZtua4GKCAH/9woJYRojY=; h=Date:To:From:Subject:In-Reply-To:References; b=uwaCKsEd2ZIavU55FueBMQTMzJWb2QOqC7YhGeqA+/NSh2lGuDudmL5mEa0u7YrYw 1otEiBs7iX6wAAP6KuZGRPmZeaZ2JoUDjdrO4DAmpALntekwGo6D6NDyJ+djVj78M4 VJ7iTRVTWRb7wQYFP5jF4fFtZfQNyGP8MfSPma9s=
Message-Id: <6.2.5.6.2.20201115062248.0c7ff710@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 15 Nov 2020 06:43:41 -0800
To: Tony Whyman <tony.whyman@mccallumwhyman.com>, ipv6@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Extending a /64
In-Reply-To: <b468124f-f85b-7e20-a354-c6b7eaba3447@mccallumwhyman.com>
References: <005ECBB3-088B-4363-BB53-8D4AD25CA3D2@employees.org> <b468124f-f85b-7e20-a354-c6b7eaba3447@mccallumwhyman.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vD7jIKAdyCXd97jKouccz1xAOR0>
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 14:52:54 -0000

Hi Tony,

I'll disclose that I am affiliated with a RIR.

At 05:00 AM 08-11-2020, Tony Whyman wrote:
>The problem of the /64 limit came up in ICAO working groups earlier 
>this year when developing a global addressing plan for the ATN/IPS 
>and there would be strong support here for allowing subnet prefixes 
>to go beyond the /64 boundary.
>
>Our problem is that we wanted to define an addressing plan that uses 
>39 bits to identify each aircraft, allows for a minimum of 4 more 
>bits for subnetting and works within the existing standards. I'll 
>give some background below for those interested in why 39 bits, but 
>the problem is that if you are going to allocate a /64 (deriving 
>from a /60 MNP) to each subnet on an aircraft then you need a /21 as 
>your initial allocation - and this is before you start thinking 
>about other ATN/IPS users such as drones.
>
>In order to avoid a potential problem getting a sufficient address 
>allocation, we did look at extending into the "other 64 bits" of an 
>IPv6 address for subnet IDs, which was looking very "unused". After 
>all, you can only cram in a handful of systems into the

There were proposals to assign a /56 MNP for an aircraft.  That 
"drone" user looks like something different from an aircraft for 
address assignment purposes.

The procedure for global allocation registration is listed at 
http://r.elandsys.com/r/51238

Regards,
S. Moonesamy