IETF Logo Mail Archive

RE: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Fri, 13 December 2019 15:45 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 AB373120180 for <ipv6@ietfa.amsl.com>; Fri, 13 Dec 2019 07:45:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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 nytKKWaUdAXQ for <ipv6@ietfa.amsl.com>; Fri, 13 Dec 2019 07:45:28 -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 1282412011D for <ipv6@ietf.org>; Fri, 13 Dec 2019 07:45:27 -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 xBDFjODO004276; Fri, 13 Dec 2019 10:45:24 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1576251924; bh=HF2vfU8q1I0sBcxHmcEdhfIEKhrRMlLktTfDXnhx8YU=; h=From:To:Subject:Date:References:In-Reply-To:From; b=aX0Eb/JV9H/0DTwPXYtdE0tw1ZTZLAroh2Htbx3GcW9cdvu6rcm3Te0bL72MVnbxW Kw8rYywqrSNwNQZqkCfKod1S2e+JeSMYPybKa0UZnDDrKg/vsbNaEyzvLoCDqnglJH zHyjAf4AYKgDTV0jSucTn4DnLkc0eEPy7Ym17lQKWjGRXL1Z1EBNv7dYjQ5qijmZAL rtD4spqYkqvfvjwDCHb8Muz+vWKnF3ajlc5dHPvmCxFXsFSNKt6dbSBz7jfKp9uVaW et2kOGeUq1cyfo1trujbdFSjPgJz8QJq04nwHHpxFvR/heymHbecp6KEMcSJtbIVUM PvFmuvqmZsgWg==
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/UPSTREAM_MBSOUT) with ESMTPS id xBDFjA65001738 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Fri, 13 Dec 2019 10:45:10 -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.1779.2; Fri, 13 Dec 2019 07:45:08 -0800
Received: from XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8]) by XCH16-07-10.nos.boeing.com ([fe80::e065:4e77:ac47:d9a8%2]) with mapi id 15.01.1779.002; Fri, 13 Dec 2019 07:45:08 -0800
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Subject: RE: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
Thread-Topic: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
Thread-Index: AdWvfvQ/Qahqc9q1R/Cq9Ga4F3JaywBo+XfHAAVCUkAAM3GXgAAOgGBw
Date: Fri, 13 Dec 2019 15:45:08 +0000
Message-ID: <c69c52c0c75146b4aadc7bde13f4320b@boeing.com>
References: <43a015b6161243ecb67e840f488947b2@boeing.com> <3f5f7214-6af6-3d6b-d183-cc96cc4b4462@gmail.com> <DBDB43BD-783F-42C4-A407-EE24CCC078B4@thehobsons.co.uk> <cdec1ad459584a588cfa85d3ee5c306a@boeing.com> <b2f826c7-87b7-4111-f88f-c5e2f3f6c8ae@gmail.com>
In-Reply-To: <b2f826c7-87b7-4111-f88f-c5e2f3f6c8ae@gmail.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: 841F18CFE775E31DC4763881F5BED82B92EA256F0B1EBA2A583EEE48235382522000:8
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gDi-Xc4AOUr43JpgfGk4PO9t48g>
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: Fri, 13 Dec 2019 15:45:31 -0000

Alex, we have indeed seen the RFC1149 example showing IP over even very low-end
transmission media. Anything that can transit an IP packet is an (IP) "link", so you are
of course correct. But, speaking for practical purposes, ICAO does have a notion of
"IP links" and "non-IP links".

Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> Sent: Friday, December 13, 2019 6:36 AM
> To: ipv6@ietf.org
> Subject: Re: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
> 
> I think non-IP data links are so until one writes an IP-over-data-link
> document and implementation.
> 
> I think TCAS can carry IP packets, like serial links do.
> 
> Alex
> 
> 
> Le 12/12/2019 à 23:06, Templin (US), Fred L a écrit :
> > Simon, interesting point but TCAS is a non-IP data link whereas this spec considers
> > only IP links. We could probably make more clear in the spec that only IP data links
> > are in-scope, and not any of the aircraft's non-IP links (e.g., TCAS, ADS-B, etc.).
> >
> > Thanks - Fred
> >
> >> -----Original Message-----
> >> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Simon Hobson
> >> Sent: Thursday, December 12, 2019 11:32 AM
> >> To: 6man WG <ipv6@ietf.org>
> >> Subject: Re: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
> >>
> >> Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
> >>>
> >>
> >>> I would like to ask whether ICAO AT/IPS effort considers that an
> >>> aircraft signals its presence by way of RA emitted by aero interface or
> >>> by a message generated by Transponder?
> >>
> >> In this application area, there is significant scope for confusion.
> >>
> >> One specific example that comes to mind is between RA (Router Advertisement) in the networking arena, and RA (resolution
> >> Advisory) in the TCAS system. https://en.wikipedia.org/wiki/Traffic_collision_avoidance_system
> >>
> >> Just something to keep in mind - that the use of "common" acronyms across different fields has the scope for more confusion than
> >> normal.
> >>
> >> Simon
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------
> >
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email