Re: Extending a /64

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 16 November 2020 14:55 UTC

Return-Path: <alexandre.petrescu@gmail.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 5A3F43A1119 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 06:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 Z1f3qB42WYA5 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 06:55:12 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 A434B3A1118 for <ipv6@ietf.org>; Mon, 16 Nov 2020 06:55:11 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AGEt8XJ004872 for <ipv6@ietf.org>; Mon, 16 Nov 2020 15:55:08 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 17AFB205F1E for <ipv6@ietf.org>; Mon, 16 Nov 2020 15:55:08 +0100 (CET)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0D20C203190 for <ipv6@ietf.org>; Mon, 16 Nov 2020 15:55:08 +0100 (CET)
Received: from [10.11.243.87] ([10.11.243.87]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AGEt7Un014330 for <ipv6@ietf.org>; Mon, 16 Nov 2020 15:55:07 +0100
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> <845e43f9-4534-a125-3105-9d345b85029f@mccallumwhyman.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <7ace052b-1d15-5892-f032-5565aaf64bbd@gmail.com>
Date: Mon, 16 Nov 2020 15:55:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3
MIME-Version: 1.0
In-Reply-To: <845e43f9-4534-a125-3105-9d345b85029f@mccallumwhyman.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/M5rGwfOHE9NuRV9K2gjzrtfUYL0>
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:55:13 -0000


Le 16/11/2020 à 15:38, Tony Whyman a écrit :
> This discussion seems to have gone off in the wrong direction. There are 
> no ICAO applications that foresee aircraft to aircraft communication 
> using datalink.

Eh?  Maybe with LDACS? draft-ietf-raw-ldacs-05 "5.2.2.  Air-to-Air 
Extension for LDACS"

Alex

  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://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------