Hi, it is interesting to see these comments but they are really out of scope for this document. This document discusses the interdomain routing between different autonomous systems, and clearly states that intradomain considerations are out of scope.
Thanks - Fred From: Abdussalam Baryun [mailto:[email protected]] Sent: Sunday, January 13, 2019 11:57 PM To: Fred Baker <[email protected]> Cc: Templin (US), Fred L <[email protected]>; [email protected]; [email protected]; [email protected] Subject: Re: [ipwave] I-D Action: draft-ietf-rtgwg-atn-bgp-01.txt Hi Fred Baker, I usually discuss deployment when the ietf-draft or ietf-RFC is a standard, but this draft is informational and it's including the planning for future technologies of Aeronautical Mobile Routing. More reply below, On Sat, Jan 12, 2019 at 10:00 PM Fred Baker <[email protected]<mailto:[email protected]>> wrote: Having now is read the draft, which doesn’t mention common Enterprise Routing protons such as IS-IS (which might be expected from history) or OSPF but is instead all about a very specific scope regarding IPv6 and BGP, I wouldn’t expect Fred to update the draft per your suggestion without a very strong operational argument. I think that new draft authors are expected to inform community about mobile routing protocols standard by IETF as working with the author's suggested mobile routing. I included standards like DLEP and OLSRv2, the draft does not mention at all, why? So I expect that Fred (the author) can discuss on the list the mobile routing options/not-options when the draft's title is about simple mobile routing (usually I expect updates can happen while WG discuss). Can you point to deployments in which mobile ad-hoc Routing protocols are envisaged or in use in aeronautics? We don't forget that the draft is suggested as informational not standard, so deployment is not the issue, IETF do publish things that will be in future implemented. Furthermore, IETF has standardised mobile routings so we cannot ignore them when we write a new draft specially when it is informational. Best Regards, AB Sent using a machine that autocorrects in interesting ways... On Jan 12, 2019, at 2:31 AM, Abdussalam Baryun <[email protected]<mailto:[email protected]>> wrote: Hi Fred, Thanks for this work which is very interesting. IMHO, the draft should consider using the DLEP, OLSRv2, AODVv2, multitopology protocols for IPv6, as RFC8175, RFC6130, RFC7181, draft-perkins-manet-aodvv2-02, and RFC7722. If not considering then I think it should mention why. Best regards AB On Sat, Jan 12, 2019 at 12:10 AM Templin (US), Fred L <[email protected]<mailto:[email protected]>> wrote: Hi, we have updated the draft based on questions and comments received. Mostly points for clarification, but there is also an important new Section on "Stub AS Mobile Routing Services". Please check the diffs and post comments to [email protected]<mailto:[email protected]>. Also cross-posting to ipwave and dmm due to interest there. Thanks - Fred > -----Original Message----- > From: rtgwg [mailto:[email protected]<mailto:[email protected]>] On > Behalf Of [email protected]<mailto:[email protected]> > Sent: Friday, January 11, 2019 1:51 PM > To: [email protected]<mailto:[email protected]> > Cc: [email protected]<mailto:[email protected]> > Subject: I-D Action: draft-ietf-rtgwg-atn-bgp-01.txt > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Routing Area Working Group WG of the IETF. > > Title : A Simple BGP-based Mobile Routing System for the > Aeronautical Telecommunications Network > Authors : Fred L. Templin > Greg Saccone > Gaurav Dawra > Acee Lindem > Victor Moreno > Filename : draft-ietf-rtgwg-atn-bgp-01.txt > Pages : 18 > Date : 2019-01-11 > > Abstract: > The International Civil Aviation Organization (ICAO) is investigating > mobile routing solutions for a worldwide Aeronautical > Telecommunications Network with Internet Protocol Services (ATN/IPS). > The ATN/IPS will eventually replace existing communication services > with an IPv6-based service supporting pervasive Air Traffic > Management (ATM) for Air Traffic Controllers (ATC), Airline > Operations Controllers (AOC), and all commercial aircraft worldwide. > This informational document describes a simple and extensible mobile > routing service based on industry-standard BGP to address the ATN/IPS > requirements. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-rtgwg-atn-bgp/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-rtgwg-atn-bgp-01 > https://datatracker.ietf.org/doc/html/draft-ietf-rtgwg-atn-bgp-01 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-rtgwg-atn-bgp-01 > > > 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<http://tools.ietf.org>. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > rtgwg mailing list > [email protected]<mailto:[email protected]> > https://www.ietf.org/mailman/listinfo/rtgwg _______________________________________________ its mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/its _______________________________________________ rtgwg mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/rtgwg
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
