[1341] in linux-net channel archive
route propagation across administrative domains
daemon@ATHENA.MIT.EDU (Raul Miller)
Tue Nov 7 02:36:44 1995
Date: Mon, 6 Nov 95 19:35 EST
From: Raul Miller <rdm@tad.micro.umn.edu>
To: linux-net@vger.rutgers.edu
I know this isn't "the" right place for this question, but it's as
close as I know to the right place...
It's a "well known problem" in internet routing that routes across
administrative domains are hard to manage. This has suddenly become
important to me, because I'm watching the route between my machine and
my maildrop oscillate back and forth across the country. [The
interface between Sprintlink and ANS will be in Washington DC for a
minute or so, then in San Fransisco for a minute or so -- with
intermittent failures for a minute or two sprinkled in for variety.]
This brings to mind the obvious question: why aren't routes "anchored"
in place for five-tenminutes (or whatever) after they're initially
established, to damp out this kind of thing? At least for where they
affect admin domain route points...
I presume that eventually this thing will die out. Perhaps even
there's a good reason for not going with this kind of solution.
Mostly, I'd like someone to point me at the relevant body of
information that talks about this -- since it's personally relevant
I'm curious.
Thanks,
--
Raul
