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

> -----Original Message-----
> From: Alexandre Petrescu [mailto:alexandre.petrescu@gmail.com]
> Sent: Thursday, December 12, 2019 12:01 AM
> To: Templin (US), Fred L <Fred.L.Templin@boeing.com>; ipv6@ietf.org
> Subject: Re: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
> 
> 
> 
> Le 11/12/2019 à 16:35, Templin (US), Fred L a écrit :
> > Alex,
> >
> >>> As for the text in the draft, I think there is an issue with the term
> >>> 'ARO' Aero Registration Option which might be taken for the existing
> >>> 'ARO' Address Registration Option.
> >>
> >> Thanks for pointing this out; we will come up with something different.
> >
> > Here's a thought: why don't we just call it the "ICAO option"?
> 
> It is a good suggestion that I do not oppose.

Someone else suggested to call it the "AERO" option (Aeronautical Endpoint
Registration Option) - would that be better?

> But I would like to learn whether ICAO ATN/IPS considers also UAM
> vehicles like VTOL air taxi flying cars (VoloCopter, Geely, Lilium,
> Kitty Hawk, Ehang, Link&Fly)?

ICAO ATN/IPS concerns air traffic management services for civil aviation only.
That is for aircraft that take off from and land at airports, and that maintain an
ongoing dialogue with air traffic control en route. However, the proposed
option may have broader applicability to use cases such as the one you are
describing here.

Thanks - Fred

> It might be that these kinds of vehicles inherit more from the
> automotive industry, like for example carrying an IP-OBU, rather than a
> transponder, which is highly likely to use IPv6 Router Advertisements,
> or BSM messages.  Which brings 'SAE', 'IEEE' and probably new traffic
> management organisations in the picture, at a same level as ICAO.
> 
> At that point, it might be that 'ICAO' option in RA might be questionable.
> 
> Or maybe ICAO option would be only for aircraft above 200m (meters)
> above ground.
> 
> Alex
> 
> > BTW, I am here in the 6man working group seeking document progression at the
> > request of ICAO Communications Panel Working Group I - they have asked me to
> > take this work forward to publication. I have also discussed possible approaches
> > with our IETF area director, and I am acting on the guidance received. So, this
> > work represents a coming-together of the two communities, where I would
> > hope there would be a spirit of mutual cooperation.
> >
> > Thanks - Fred
> >
> >> -----Original Message-----
> >> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin (US), Fred L
> >> Sent: Wednesday, December 11, 2019 6:56 AM
> >> To: Alexandre Petrescu <alexandre.petrescu@gmail.com>; ipv6@ietf.org
> >> Subject: RE: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
> >>
> >> Hi Alex,
> >>
> >>> -----Original Message-----
> >>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandre Petrescu
> >>> Sent: Wednesday, December 11, 2019 12:27 AM
> >>> To: ipv6@ietf.org
> >>> Subject: Re: Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
> >>>
> >>>
> >>>
> >>>
> >>> Le 10/12/2019 à 18:30, Templin (US), Fred L a écrit :
> >>>> The International Civil Aviation Organization (ICAO) is building an Aeronautical Telecommunications
> >>>> Network with Internet Protocol Services (ATN/IPS). ICAO sees a use case for an IPv6 Air/Ground
> >>>> (A/G) interface to support aircraft communications with ATN/IPS ground domain correspondents.
> >>>> This document presents a candidate (A/G) interface solution. Please post any solution-oriented
> >>>> comments for this document on ipv6@ietf.org.
> >>>
> >>> 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?
> >>
> >> The purpose of the RS/RA messaging is to register each of the aircraft's individual IP data
> >> links with the ground-domain mobility service. Any transponder messaging is orthogonal
> >> to the data communications service offered by the ATN/IPS, i.e., they are complimentary
> >> independent functions.
> >>
> >>> As for the text in the draft, I think there is an issue with the term
> >>> 'ARO' Aero Registration Option which might be taken for the existing
> >>> 'ARO' Address Registration Option.
> >>
> >> Thanks for pointing this out; we will come up with something different.
> >>
> >> Fred
> >> fred.l.templin@boeing.com
> >>
> >>> Alex
> >>>
> >>>>
> >>>> -----Original Message-----
> >>>> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> >>>> Sent: Tuesday, December 10, 2019 9:12 AM
> >>>> To: i-d-announce@ietf.org
> >>>> Subject: I-D Action: draft-templin-atn-aero-interface-08.txt
> >>>>
> >>>>
> >>>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> >>>>
> >>>>
> >>>>           Title           : Transmission of IPv6 Packets over Aeronautical ("aero") Interfaces
> >>>>           Authors         : Fred L. Templin
> >>>>                             Tony Whyman
> >>>> 	Filename        : draft-templin-atn-aero-interface-08.txt
> >>>> 	Pages           : 25
> >>>> 	Date            : 2019-12-10
> >>>>
> >>>> Abstract:
> >>>>      Aeronautical mobile nodes (e.g., aircraft of various configurations)
> >>>>      communicate with networked correspondents over multiple access
> >>>>      network data links and configure mobile routers to connect their on-
> >>>>      board networks.  An Air-to-Ground (A/G) interface specification is
> >>>>      therefore needed for coordination with the ground domain network.
> >>>>      This document specifies the transmission of IPv6 packets over
> >>>>      aeronautical ("aero") interfaces.
> >>>>
> >>>>
> >>>> The IETF datatracker status page for this draft is:
> >>>> https://datatracker.ietf.org/doc/draft-templin-atn-aero-interface/
> >>>>
> >>>> There are also htmlized versions available at:
> >>>> https://tools.ietf.org/html/draft-templin-atn-aero-interface-08
> >>>> https://datatracker.ietf.org/doc/html/draft-templin-atn-aero-interface-08
> >>>>
> >>>> A diff from the previous version is available at:
> >>>> https://www.ietf.org/rfcdiff?url2=draft-templin-atn-aero-interface-08
> >>>>
> >>>>
> >>>> Please note that it may take a couple of minutes from the time of submission
> >>>> until the htmlized version and diff are available at tools.ietf.org.
> >>>>
> >>>> Internet-Drafts are also available by anonymous FTP at:
> >>>> ftp://ftp.ietf.org/internet-drafts/
> >>>>
> >>>> _______________________________________________
> >>>> I-D-Announce mailing list
> >>>> I-D-Announce@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>>> Internet-Draft directories: http://www.ietf.org/shadow.html
> >>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> 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
> >> --------------------------------------------------------------------