Good Peering Practices
-
Upload
bangladesh-network-operators-group -
Category
Internet
-
view
495 -
download
0
Transcript of Good Peering Practices
Good Peering PracticesbdNOG - May 2014
Google Confidential and Proprietary
Google Confidential and Proprietary
Google Confidential and Proprietary
Topics
● Why and where to peer● Types of peering● Business and technical steps● [stats]● Common reasons for delays● Managing your peering● Top Tips
Google Confidential and Proprietary
Why peer?
CC photos by: Open Source, Dave Cross, San Jose Library
qualityeconomics control
Google Confidential and Proprietary
Where to peer?
No “single source of truth” - lots of resources
● peeringDB.com● IXP Maps● provider maps / data● ask your NOG!
Google Confidential and Proprietary
as15169.peeringdb.com
Google Confidential and Proprietary
www.internetexchangemap.com
Google Confidential and Proprietary
another map / large network or content provider
www.cloudflare.com/network-map
Google Confidential and Proprietary
http://goo.gl/3VnNZn
Google Confidential and Proprietary
SANOG23 Virtualisation Group (src: unknown)
Google Confidential and Proprietary
control (quality)
r-serverIXP switch
ISP A
ISP B
Route-Server peering
cost, resources
ISP A
ISP B
Direct peering (PNI)ISP A
ISP B
Public peering (bilateral)
IXP switch
BGP
Physical
Google Confidential and Proprietary
Business and technical steps: public / bilateral
“A survey of 142,000 peering agreements conducted for this report shows that … 99.5% of interconnection agreements are concluded without a written contract” DOI :10.1787/20716826
Agree settlement and contract basis
Turnup BGP
Traffic flows!
Google Confidential and Proprietary
Business and technical steps: PNI
● who orders xcnt usually provides IPs● non-ordering party provides demarc and LoA
Agree settlement and contract basis
Agree xcnt orderer
Install, test xcnt
Turnup BGP
...
Google Confidential and Proprietary
[comparison of PNI turnup times]
- total PNI turnup time avg [days] - ideally a range with median, max, min- broken down by region, eg NA, SA, APAC, EMEA
Google Confidential and Proprietary
[comparison of time steps]
Ideally for S Asian peers, [india, SL, Bd, pk, bt, np]
- broken down time on mains steps - ideally.
Google Confidential and Proprietary
Common reasons for delays
Issue Mitigation to reduce delays
Peer not ready to provide demarc (circuit, router not in place)
- Clearly signal expected readiness- Double check own resources before commitment
Cross-connect troubleshooting (fibers wrong-way, dirty, ports not free)
- Have direct contact details of xcnt provider- Support ‘live’ troubleshooting
Misunderstandings on process, roles and responsibilities
- Attend industry fora, ask for advice- Clear agreement on bus/tech steps at the start
Google infrastructure constraints [!] - Ask if Google has any constraints (we should tell you!)
Google Confidential and Proprietary
Managing your peering
Peering is up and traffic is flowing! All done?
NO!!
You need to now:1. monitor (up/down, traffic levels) - most do this OK2. plan for augments - most could do this much better3. plan for resilience - most could do this much better
Google Confidential and Proprietary
Google Confidential and Proprietary
Google Confidential and Proprietary
Closing: top tips
DON’T
★ assume peering relationships are ‘provider-customer’
★ forget to plan for capacity and resilience
★ [xxx]
DO
★ plan carefully why you want to peer - and where
★ develop a specific peering coordinator role
★ keep PeeringDB.com up-to-date
★ maintain multiple paths