North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: inter-domain link recovery

  • From: Roland Dobbins
  • Date: Wed Aug 15 05:07:24 2007
  • Authentication-results: sj-dkim-2; [email protected]; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
  • Dkim-signature: v=0.5; a=rsa-sha256; q=dns/txt; l=721; t=1187165846; x=1188029846; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; [email protected]; z=From:=20Roland=20Dobbins=20<[email protected]> |Subject:=20Re=3A=20inter-domain=20link=20recovery |Sender:=20; bh=DpAFf0yeBvSsxgTUFwaFv6Q1uuQBwMgeEu5pb8K88mc=; b=SbRyaEm2mHDstUkUoqtTZbBGAW6pddy4RA54NE0iJCYGimG6fnigElZ11Re3GR1FEdIGqufl 7X585Y/QhyXiOLDnToH/FXGNEk6gJl85WD6rH6QsZLsXpoxxluOl1mD2;


On Aug 15, 2007, at 12:11 AM, Chengchen Hu wrote:

But when in these cases, how to recover it? The network operators just wait for physically reparing the link or they may manully configure an alternative path by paying another network for transit service or finding a peering network?

Or they've already sufficient diversity in terms of peering/transit relationships and physical interconnectivity to handle the situation in question - depending upon the situation, of course.

-----------------------------------------------------------------------
Roland Dobbins <[email protected]> // 408.527.6376 voice

Culture eats strategy for breakfast.

-- Ford Motor Company