RE: Multihop eBGP peering or VPN based eBGP peering

[John van Oppen <jvanoppen () spectrumnet us>]

Perhaps I am missing something from your advantage list, but why would you want to exchange routing information with a 
network to which you don't have a connection due to a local failure?    I think you are attempting to abstract routing 
from the underlying physical infrastructure a bit too much.   If the power is out in the carrier pop to which you are 
connected, they don't have a way to give you traffic so why would a multi-hop session help.     

BGP being down is rarely something that happens on its own, it is typically due to something far more physical (router 
failure, pop outage, circuit outage, etc).   

John 

-----Original Message-----
From: Michael McConnell [mailto:michael () winkstreaming com] 
Sent: Sunday, June 16, 2013 5:40 PM
To: nanog () nanog org
Subject: Multihop eBGP peering or VPN based eBGP peering

Hello all,

Any idea why more companies don't offer eBGP peering / multi hop peering? Its very common for providers to offer single 
or double hop peering, so why not 5 or 10 hops? In many cases people find it logical to perform single or double hop 
peering, why is peering any greater always frowned upon. I understand the logic that you can't control the path beyond 
a point, however I still see numerous advantages. 

One obvious advantages one is, imagine you east coast data centre and you had a eBGP peering session with a west coast 
router, you'd be able to control ingress via the west coast. (aka routing around an region outage that is effecting 
ingress) For example during the last hurricane around New Jersey, numerous tier 1's were down towards the atlantic and 
every peer for the atlantic was effected. One could have just made the ingress via the west coast the logical route. 

Thoughts?

Mike

--

Michael McConnell
WINK Streaming;
email: michael () winkstreaming com
phone: +1 312 281-5433 x 7400
cell: +506 8706-2389
skype: wink-michael
web: http://winkstreaming.com