IETF Logo Mail Archive

RE: Extending a /64

"Da Silva, Saulo" <Sdasilva@icao.int> Mon, 16 November 2020 16:35 UTC

Return-Path: <Sdasilva@icao.int>
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 45C3C3A1192 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 H38cFSmbgcrN for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:35:18 -0800 (PST)
Received: from esa1.hc196-20.ca.iphmx.com (esa1.hc196-20.ca.iphmx.com [216.71.132.118]) (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 6FA0B3A126C for <ipv6@ietf.org>; Mon, 16 Nov 2020 08:35:18 -0800 (PST)
IronPort-SDR: S/3POehTB3tTPcCzEmaGw89mFTe3StEfnTZRQe4/n0rJ1zsZw8+IeNNSzHcFjr3oJuGCrVRG3F 1h34+oINLXIb1k6uqRHiR5C6n2kY4swoLhtCokp/M+t0d2l9hwaBOwVn3E8tjAEVoy/3kAX4W9 gEGNzFjdBo2syAelAbBkxyoiUl0/in3UHo3JaZ+4hQIalX3rTByiCpV6kmfmcTw9ccflAvTBjt vk24CEugEp9kKdw4ufdm1d1XL1Nlz18O9naM3hR74UYnIOeU8zsD1olgrtIyLOajmgrF2uyp6/ U+o=
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from smtp.icao.int ([192.206.28.75]) by esa1.hc196-20.ca.iphmx.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 16 Nov 2020 11:35:17 -0500
Received: from ExchMBX2.icaohq.icao.lan (10.1.4.159) by Exch1.icaohq.icao.lan (10.1.4.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Mon, 16 Nov 2020 11:35:17 -0500
Received: from ExchMBX1.icaohq.icao.lan (10.1.4.158) by ExchMBX2.icaohq.icao.lan (10.1.4.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Mon, 16 Nov 2020 11:35:17 -0500
Received: from ExchMBX1.icaohq.icao.lan ([fe80::190f:1f34:f603:5101]) by ExchMBX1.icaohq.icao.lan ([fe80::190f:1f34:f603:5101%2]) with mapi id 15.01.2044.004; Mon, 16 Nov 2020 11:35:17 -0500
From: "Da Silva, Saulo" <Sdasilva@icao.int>
To: Tony Whyman <tony.whyman@mccallumwhyman.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Extending a /64
Thread-Topic: Extending a /64
Thread-Index: AQHWtbmX60WFjQT7Vk6VPo+WsP5IQKm+hq8AgAsdG4CAAE1JAIAACF0A//+0TjGAAF38AIAABnGA//+xrv+AAHvMgP//r1BpAB8lloD//71WhYAAg6aA//+1q7WAAFXvAIAATaZA///HzoCAAEjokA==
Date: Mon, 16 Nov 2020 16:35:16 +0000
Message-ID: <f9b3be1f8f1c4a6ab90cfc5b7e6beb57@icao.int>
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> <845e43f9-4534-a125-3105-9d345b85029f@mccallumwhyman.com> <650a29ac79594955b622ee677fb77651@icao.int> <1fe4959a-d539-c13f-a183-b8f5dcce057f@mccallumwhyman.com>
In-Reply-To: <1fe4959a-d539-c13f-a183-b8f5dcce057f@mccallumwhyman.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.1.4.248]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/xFqy986xdFCv2LQplrtNOhZGUlA>
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 16:35:20 -0000

You are right.
This is not WG-I discussions. But it is under discussion in other groups of experts.

-----Original Message-----
From: Tony Whyman [mailto:tony.whyman@mccallumwhyman.com] 
Sent: 16-Nov-20 10:55 AM
To: Da Silva, Saulo <Sdasilva@icao.int>; ipv6@ietf.org
Subject: Re: Extending a /64

I take your point - but these considerations are not (to my knowledge) in the scope of the work being undertaken by Working Group I. You are looking here a future concepts and these should be all limited to line of sight.

Currently, any air-to-air routing is out of scope. If you want to bring air-to-air routing in scope then we need to discuss.

Tony

On 16/11/2020 15:05, Da Silva, Saulo wrote:
> Tony.
> The evolution of the aviation system towards increasing capacity and acess of what we call new entrants (drones, high level operations, supersonic acft, etc) through strategic and tactical self separation do need air-to-air comm. The concept of management by trajectory instead of isolated clearances do need air-to-air. The aviation industry is working towards that direction.
>
> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Tony Whyman
> Sent: 16-Nov-20 9:39 AM
> To: ipv6@ietf.org
> Subject: Re: Extending a /64
>
> 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.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: 
> https://secure-web.cisco.com/1Ttb6AZE6VAf8slZg6Up2Wbc-yRRw1bRFNxq3xFe0
> rvxo57JW3EORgd4Y26YVF1A3xJsGZYRey0b4EIYy8ftofcyCu7BKkGwioWSLWoCYbTzIMk
> nfOy-InoUgJYGfaqD7b1PlyjfOs8ZkaaScuic6BjfH5hTsbJpBV2VmzoNDG6f7CoPZtjQq
> wXQ19FQu3evxWz0PTffaVTwtvvzpf9p9kkX8LX_mM4wx3g_jmYCK195bx7bKPQ0K0yoQzr
> ihSnUSf7IQpTyfWp1zyNnknt4KbOeHobj8oxycxJAY6QC3ckVxhuUM85Vly6EtrO37uaUL
> /https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fipv6
> --------------------------------------------------------------------
>
>

v2.23.0 | Report a Bug | By Email