Re: Extending a /64

Tony Whyman <tony.whyman@mccallumwhyman.com> Mon, 16 November 2020 14:38 UTC

Return-Path: <tony.whyman@mccallumwhyman.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 ACB5A3A10E5 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 06:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 CeBqNUZxto-i for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 06:38:55 -0800 (PST)
Received: from mail2.mwassocs.co.uk (mail2.mwassocs.co.uk [IPv6:2a00:da00:1800:8030::1]) (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 084C33A10E4 for <ipv6@ietf.org>; Mon, 16 Nov 2020 06:38:54 -0800 (PST)
Received: from olympus.mwassocs.co.uk ([IPv6:2a02:390:813f:1:fa32:e4ff:fe9d:20df]) (authenticated bits=0) by mail2.mwassocs.co.uk (8.15.2/8.15.2/Debian-3) with ESMTPSA id 0AGEcprf059638 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ipv6@ietf.org>; Mon, 16 Nov 2020 14:38:52 GMT
Received: from [172.16.1.16] ([172.16.1.16]) by olympus.mwassocs.co.uk (8.15.2/8.15.2/Debian-10) with ESMTP id 0AGEcjEK010017 for <ipv6@ietf.org>; Mon, 16 Nov 2020 14:38:46 GMT
Subject: Re: Extending a /64
To: ipv6@ietf.org
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> <m1kePdR-0000I6C@stereo.hq.phicoh.net> <b022d11f-b55d-07ef-307d-949ff57cd562@foobar.org> <m1keS7i-0000E0C@stereo.hq.phicoh.net> <f06db586-15ed-6dd3-d09f-06a4e3759275@mccallumwhyman.com> <m1kecJm-0000EOC@stereo.hq.phicoh.net> <5101F72E-4197-4E58-8DEF-9EB9D5541482@thehobsons.co.uk> <m1kefWI-0000ETC@stereo.hq.phicoh.net>
From: Tony Whyman <tony.whyman@mccallumwhyman.com>
Message-ID: <845e43f9-4534-a125-3105-9d345b85029f@mccallumwhyman.com>
Date: Mon, 16 Nov 2020 14:38:40 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <m1kefWI-0000ETC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/rEtfw-vrMtoRmJH2PSbQC1vp9ME>
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: Mon, 16 Nov 2020 14:38:57 -0000

This discussion seems to have gone off in the wrong direction. There are 
no ICAO applications that foresee aircraft to aircraft communication 
using datalink. The underlying set of applications is:

1. Controller to Pilot Datalink Communication (CPDLC) - the name says it all

2. Automatic Dependent Surveillance (ADS) - allows an ATS Provider to 
monitor an aircraft's position and intent.

3. Flight Information Services (FIS) - allows a pilot to pull 
information (e.g. on runway conditions).

TCAS also exists as a collision avoidance system and this does use 
air-to-air communication. However, this is a rider on the Mode S 
surveillance radar and is not IP based.

On 16/11/2020 14:30, Philip Homburg wrote:
> However, this seems to be a case of doing things at the wrong level. If aircaft
> use IPv6 to communicate then obvious they need unique IPv6 addresses. However,
> each plane only needs to know its own address. Any time a plane communicates
> with an unknown plane, they can exchange higher level identities.