Re: Extending a /64

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Mon, 16 November 2020 16:03 UTC

Return-Path: <Fred.L.Templin@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 06B453A1218 for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:03:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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 iWzjn1egxaDt for <ipv6@ietfa.amsl.com>; Mon, 16 Nov 2020 08:03:24 -0800 (PST)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (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 AED763A1234 for <ipv6@ietf.org>; Mon, 16 Nov 2020 08:02:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 0AGG2pn6028876; Mon, 16 Nov 2020 11:02:52 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1605542572; bh=0ZgNIlZ34vqJkVi+dURCp+CqLQxEIEKfhv2s3FClKj8=; h=From:To:Subject:Date:From; b=qgnx43MwELOUQ6Ovbs/ViSyXDQX9tqzXJqkHqHnXb5fe/oMYoMDhZx94TaIgYfcf/ I6UgCcUxmDeiGGD4ZaEOcOxlZW6WAUAHlJ0tbj2NrUbrxU6CI+Zdsg/6c3TsXf8tU+ EF2U+cm/wV0JauLc0xbilFw2LkLDzjcz285bxFmPD4TH205sNbNktQYbUZC8i3H/LH LxuWPNbF/80XO+Wo30PkZS/B+Ga4178C5v62oBnthiYJ+r06Ss/MKOTbnS5NBECAtt 2JopFGWeJC0oVgrO8MW/nas8SDnKF2hoQ08a9dy8eDFihfLmf2+9W15NUwE7wyIkJ9 WoefKvIsuccwA==
Received: from XCH16-07-12.nos.boeing.com (xch16-07-12.nos.boeing.com [144.115.66.114]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 0AGG2dUr028609 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 16 Nov 2020 11:02:39 -0500
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-12.nos.boeing.com (144.115.66.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Mon, 16 Nov 2020 08:02:37 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Mon, 16 Nov 2020 08:02:37 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Tony Whyman <tony.whyman@mccallumwhyman.com>, "Da Silva, Saulo" <Sdasilva@icao.int>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: Extending a /64
Thread-Topic: Extending a /64
Thread-Index: Ada8MeZ33Ixvy736SBq0Kmqz8GxheQ==
Date: Mon, 16 Nov 2020 16:02:37 +0000
Message-ID: <7ac7915465b24428a2224b9b4b68f092@boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 66B6DD063E3B679FBF350A16ED17214D898F02FF52896E664D4C0A933AE85B912000:8
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/FTi8ubmzveyKGc7bcBNp7LHSZVU>
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:03:26 -0000

The AERO/OMNI technologies are air-air capable, and not just air-ground. That is
one big reason why they are also being considered for ground transportation and
urban air mobility where "vehicle-to-vehicle" (V2) is important.

Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Tony Whyman
> Sent: Monday, November 16, 2020 7:55 AM
> To: Da Silva, Saulo <Sdasilva@icao.int>; ipv6@ietf.org
> Subject: [EXTERNAL] 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-
> yRRw1bRFNxq3xFe0rvxo57JW3EORgd4Y26YVF1A3xJsGZYRey0b4EIYy8ftofcyCu7BKkGwioWSLWoCYbTzIMknfOy-
> InoUgJYGfaqD7b1PlyjfOs8ZkaaScuic6BjfH5hTsbJpBV2VmzoNDG6f7CoPZtjQqwXQ19FQu3evxWz0PTffaVTwtvvzpf9p9kkX8LX_mM4wx3
> g_jmYCK195bx7bKPQ0K0yoQzrihSnUSf7IQpTyfWp1zyNnknt4KbOeHobj8oxycxJAY6QC3ckVxhuUM85Vly6EtrO37uaUL/https%3A%2F%
> 2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fipv6
> > --------------------------------------------------------------------
> >
> >
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------