<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.6000.16735" name=GENERATOR></HEAD>
<BODY id=role_body style="FONT-SIZE: 10pt; COLOR: #000000; FONT-FAMILY: Arial"
bottomMargin=7 leftMargin=7 topMargin=7 rightMargin=7><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>In einer eMail vom 17.11.2008 17:08:38 Westeuropäische Normalzeit schreibt
bill@herrin.us:</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000 size=2>On Sat,
Nov 15, 2008 at 3:49 PM, Iljitsch van Beijnum<BR><iljitsch@muada.com>
wrote:<BR>> Depends on the topology restrictions you're willing to live
with. I don't<BR>> think we need to support the situation where a
multihomer connects to ISPs<BR>> in South Africa and Hawaii.<BR><BR>What
about the one where he connects via a low earth orbit
satellite<BR>constellation which has redundant ground stations in Hawaii, New
York,<BR>Germany and India? Or any 4 points that actually fit on an orbit?
The<BR>cool thing about LEO is that it starts around 100 miles up, so
you<BR>don't have long speed of light delays or large
transmit-power<BR>requirements. But you do have a huge geographic
spread.<BR><BR>In a developing country, it would be doubly-handy if a customer
could<BR>use a terrestrial radio network when the signal is good and fall
back<BR>on a more expensive LEO satellite when the terrestrial radio
network<BR>has problems, all without disturbing the ongoing
end-to-end<BR>connections.</FONT></BLOCKQUOTE>
<DIV>Yes. This is precisely where the routing challenges start to get
exciting.</DIV>
<DIV> </DIV>
<DIV>Heiner</DIV>
<DIV> </DIV></FONT></BODY></HTML>