Le 08/06/2015 23:29, Templin, Fred L a écrit :
Hi,

I finally had a chance to sit back and think about the scaling
properties of AERO, and I think it is within reason for each AERO
link to service O(10^9) Clients. Here is what I wrote in the latest
AERO draft version:

"Scaling properties of the AERO routing system are therefore limited
by the number of BGP routes that can be carried by Relays.  Assuming
O(10^6) as a maximum number of BGP routes,

Deserves explanation of the O notation, and deserves expalining why you
assume 10^6 (and not 10^7).

Another maximum number of BGP routes can be found in the routers in the
Default-Free Zone: 535593 as of January 30th, 2015.

Do you want the AERO system to scale as much as the entire existing
Internet?  Or be part of it?

this means that at most O(10^6) Clients can be serviced by Relays
within a single BGP instance.

The O explanation would include the fact that several Clients behind a
Mobile Router keeps the same order of magnitude?

A means of increasing scaling would be to assign a different set of
Relays for each set of ASPs, and still have each Server peer with
each Relay but with a distinct BGP instance for each Relay set.
Another possibility would be for Servers to institute route filters
within a single BGP instance so that each set of Relays only
receives BGP updates for the ASPs they aggregate.

Assuming up to O(10^3) sets of Relays, scaling can then accommodate
O(10^9) Clients with no additional overhead for Servers and Relays.
In this way, each set of Relays services a specific set of ASPs that
they advertise to peers outside of the AERO link, and each Server
configures ASP-specific routes that list the correct set of Relays
as next hops."

https://datatracker.ietf.org/doc/draft-templin-aerolink/

I still have to understand this draft.

But when talking scaling of a routing system, I think it is worth
characterizing it with maybe a few more parameters.

The maximum number of IP hops in a shortest path between the BGP routers
which exchanged a route respective to a Moving Network.
The positive influence of the default routes on the reduction of route
update messages.
The influence of aggregating prefixes in the reduction of routes in the
routing tables (centralized and well-planned addressing architecture).

It is also worth making affirmative statements of the fact that BGP
worked to support mobility of a network the size of an airliner over two
continents, with an IP hop count of maximum 4(?) between the BGP routers
on the ground which injected the respective route.  This would hint at
the fact that a BGP system part of AERO is scalable to support mobility.

Alex



Comments?

Thanks - Fred [email protected]

_______________________________________________ dmm mailing list
[email protected] https://www.ietf.org/mailman/listinfo/dmm



_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm

Reply via email to