What is a Peering Coordinator?

Transcription

1 What is a Peering Coordinator? May 25, 2009 Copyright 2009 Limelight Networks. All rights reserved.

2 A change of presenters Guy Tal Martin Levy

3 Presentation agenda What is a Peering Coordinator? Why do I need one? What is a Peering Policy? Do I need one? What is in play at a peering discussion? What is a successful peering agreement? Homework before starting a peering discussion. Peering db, what it is and how to use it. Meetings to attend. 3

4 What is a peering coordinator? 4

5 What is a Peering Coordinator? More than almost anyone at your company, a peering coordinator is responsible for the performance of the network. Peering coordinators ensure that their customers traffic gets to and from its destination in the best possible manner. Public face to your company. 5

6 What a Peering Coordinator is not Salesman Product manager BGP expert Network architect 6

7 Why do I need a Peering Coordinator? A good peering coordinator not only brings on new peering, he/she makes your existing peering more robust. While a network engineer or a NOC can handle turning up new peers, these people have other job responsibilities that are their primary focus. You need someone devoted to your peering strategy. Having a single point of contact for people to communicate with simplifies the peering process. 7

8 What is peering? 8

9 What is peering? Peering involves two networks coming together to exchange traffic with each other freely, and for mutual benefit. This 'mutual benefit' is most often the motivation behind peering, which is often described solely by "reduced costs for transit services". Other less tangible motivations can include: Increased capacity for extremely large amounts of traffic (distributing traffic across many networks). Increased control over your traffic (reducing dependence on one or more transit providers). 9

10 What is peering? (continued) Improved performance (attempting to bypass potential bottlenecks with a "direct" path). Improved perception of your network (being able to claim a "higher tier"). Government regulations, or the desire to avoid the appearance of being a monopoly. Increased billable customer traffic. Another common way to look at peering is, Would either side be more hurt if the peering does not exist? 10

11 Peering policies 11

12 Peering policies A peering policy is designed to help both your organization and external organizations understand what the minimum requirements are for connecting to your network Peering policies should be shaped by a company s engineering, sales and product management departments 12

13 Types of peering policies Open Network will generally peer with anyone Selective Network will peer if certain requirements are met Restrictive Network will generally not peer with anyone 13

14 Open peering policies Networks that have traffic profiles that are very imbalanced (either inbound or outbound) Networks that do not have an overwhelming market share or have lower traffic volumes Networks that are more concerned with performance than top line revenue 14

15 Selective peering policies Carrier networks that have traffic profiles that are imbalanced (either inbound or outbound) Networks that do not have an overwhelming market share but with higher traffic volumes Networks that are most concerned with bottom line revenue 15

16 Restrictive peering policies Carrier networks that have traffic profiles that are very balanced Networks that have close to monopolistic market share Networks that are more concerned with top line revenue than performance 16

17 Sample peering policies 17

18 Sample peering policy Network must have backbone circuits of X size The network considering the peering wants to know that there is sufficient network between each of your POPs to handle both day-to-day operations as well as be able to route during failure/maintenance conditions. Also shows that your network is large enough to be considered a peer. Network must interconnect in X locations The network considering the peering is not interested in carrying all the traffic to or from you. With multiple interconnection points, there will be some hot-potatoing of traffic that will be in their best interest. Also shows that your network is large enough to be considered a peer. 18

19 Sample peering policy Network must exchange X amount of traffic Peering can get expensive for larger networks, in capital expenditure (capex), operational expenditure (opex) as well as overhead (oh). Another metric designed to show that your network is large enough to be considered a peer. Network may not be a customer simultaneously If your company is already paying the network you are applying for peering with to exchange traffic, what is their motivation to make it free? Even if you are not sending them any traffic to their customers, it s still a threat to their revenue. 19

20 Sample peering policy Network must have 24/7 NOC The network considering the peering wants to know that you take your IP platform as serious as they do. There is also usually a stipulation that complaints be looked at withing X hours. Also shows that your network is large enough to be considered a peer. Network must maintain abuse desk Similar to a 24/7 NOC, an abuse desk is vital for IP operations. Directly connecting to a network creates some additional security risk for a network. Both sides should have a way to handle those risks. 20

21 Sample peering policy Network may only announce customer routes The definition of Settlement Free Interconnect (SFI) is that each network only announces their customer routes to each other, but there are networks that would announce other routes to influence peering metrics. Network may not point default route to other network Needing to point default route at another network is a clear sign that there is an imbalance in networks. Networks that have been discovered to point default are immediately depeered and publicly shamed. 21

22 Sample peering policy Network must filter their customers announcements For many networks, maintaining a prefix-list access-list or even an as-path access-list does not scale. There is a certain degree of trust among peers when they exchange Network Layer Reachability Information (NLRI). Network must announce routes consistently By selectively announcing or withdrawing routes from particular peering points, a network can force their peering partner to carry more traffic than they should. Consistent announcements allows both sides to handle their own TE. 22

23 Sample peering policy Network must maintain X ratio of traffic For some networks, there is a belief that the ratio of traffic exchanged indicates whether another network is a peer or a customer. An imbalance in either direction can indicate that the network will have to carry more of the burden of traffic delivery than the other network. There is a long standing debate whether ratios should be a peering metric or not, and it s an emotional subject for many. With increase of peer to peer traffic, many ISPs have much more balanced traffic than before! e.g. You send 200Mb, You get 100Mb: 2:1 ratio 23

24 Lesser used peering policy items Network must transit X amount of ASNs To some networks, this is an indication that your network is large enough to peer with. Network must maintain single global ASN Like the requirement about consistent announcements, a peering manager wants to make sure that they would get all routes in all locations with identical route characteristics. Network must aggregate their routes Similar to global ASN and consistent announcements, this requirement ensures that the network applying for peering carries its fair share of traffic. 24

25 Lesser used peering policy items Network must register routes with routing registry Most network won t actually filter based on routes registered in a route registry, but if everyone did, the internet would be a lot more secure. This shows that the applying network is at least attempting to filter its customers. Network must interconnect with interfaces of at least X size Ensures that traffic will not be bottle-necked based on the physical interconnections themselves. Also shows that your network is large enough to be considered a peer. 25

26 Lesser used peering policy items Network must peer with each other in all locations that they operate (including home market) This is assumed by most peering policies as it seems almost obvious, but there are networks that refuse to peer in their home markets, and if they do, they will not qualify for peering with networks that either have this stipulation in writing or implication. Network must have peering.db entry It is difficult to keep contact information up to date for many network operators, so having a central database of network and contact information is critical for many networks. 26

27 Peering physical interconnections 27

28 Peering physical interconnections Public Interconnections Internet exchanges or Network Access Points (IXs or NAPs) are often times a very economical method of exchanging traffic, assuming the peering policy is at least selective. Generally done by multiple networks connecting to an Ethernet switch or fabric. Private Interconnections Often referred to as Private Network Interconnections (PNIs). Can be either be Ethernet or rarely SONET/SDH based, but the key is that it s a Point To Point (PTP) circuit or crossconnect. 28

29 Multilateral vs Bilateral IXPs Bilateral BGP sessions Peering coordinators can pick and choose which networks to peer with. Some IXs with hundreds of networks make this difficult for operations departments to keep up with network status (i.e. flapping peers, maintenances, etc.) Mandatory Multilateral Peering Agreements (MLPA) An option at many IXs around the world (but for some reason mandatory at many LATAM IXs). Discourages networks from connecting if they have selective or restrictive peering policies. Beneficial if government mandates that local ISPs must interconnect at the IX. Low administrative overhead. 29

30 Notable IXPs for South America FAPESP/NapDoBrasil - established 1998 PTT Brasil - established 2004 CABASE Buenos Aires - established 1998 NOTA Miami - established 2001 NAP Chile - established 1997 NAP Peru - established 2000 NAP Colombia - established 1998 NAP Ecuador - established

31 Sample peering fabric (KleyReX or AMSIX) 31

32 What is peering.db? 32

33 Peering.db A peering database that everyone should have an entry in and keep maintained. Created by and for peering coordinators. A chance to publish information to let other companies know about your network and how to contact you. A reference of Internet exchange (IX) points and colocation facilities. 33

34 Peering.db homepage 34

35 Getting started with peering.db Navigate to and register a user account. Use your work address. You will then be prompted to attach your user record to a network record. If one already exists for your company, you will need to be verified by the creator of the account. If one doesn t exist, you can create your company record. Putting more information into your company record will ensure more people will know about you and contact you! 35

36 Peering.db networks view 36

37 Peering.db facilities view 37

38 Peering.db exchange point view 38

39 Meetings to attend 39

40 Conferences to attend LACNIC Best concentration of Latin American network operators and peering coordinators. But you already know that, you re here GPF (Global Peering Forum) Good mix of North American, European, Asian, and Latin American peering coordinators. ITW (International Telecoms Week) Executive level meetings with global carriers. NANOG Mostly North American operators and peering coordinators. 40

41 Tips for successful conferences Know who is attending Check the attendee list and make a list of people that work at networks that you work or want to work with. Ask the meeting coordinators to help with introductions if necessary. Schedule meetings before you arrive The best way to ensure you speak to everyone you want to is to them and fill up your appointment calendar. Send out-going, friendly, English speaking people A lot can get done at the actual meetings, but a good company representative can make the initial contacts and pass along contact information as well. 41

42 Peering negotiations 42

43 First and foremost, know your network Who are your marquee customers? Your customers make you interesting. It s OK if you don t have transit customers, traffic sourced or destined to your network can many times be interesting enough. Singly-homed traffic gives you power. There is only one place to get that traffic from, YOU! What markets and networks does your traffic come from? Where is it going? Does your network architecture/hardware allow you to expand into many or few sites? Have facts and figures of your network profile. 43

44 I know who am I, who are you? How do you know where your traffic is coming from/going to? You may have a gut feeling, but is your company going to spend millions of dollars on a feeling? Use flow-based tools to find out for sure, you may be surprised. Create a list of top networks that you exchange traffic with that you are not currently peering with, and rank them by amount of traffic. 44

45 Know your target peer s network Now you know who you want to peer with, what next? Before you contact them, find out where they have network POPs. Check company website for network maps. Check peering.db for a list of facilities and IXs. If possible, find out what size the network is You may only be exchanging 1Gbps of traffic, but that may be 10% of their traffic. Most networks would welcome peering off that percentage of traffic. What type of peering strategy do they have? 45

46 The actual negotiation (part 1) Most networks have open peering policies, so if you re both connected to an IX, peering can begin within hours or days of initial contact. What if someone has a selective policy? Chances are if you have an interesting enough network or if they don t sell transit in your home market, you ll be able to peer. Many selective networks have peering policies that they expect you to meet. 46

47 The actual negotiation (part 2) The most difficult network to get peering from is the restrictive network. Timing is everything. Some restrictive networks are forced to maintain a certain number of peered networks due to merger regulations. In these cases, smaller traffic flows are in your favor. Depending on who your upstream is, there may be congestion or ratio issues with their peering partner, so to help alleviate those concerns, you may qualify for peering. You can t get what you don t ask for. To the bold goes the spoils! 47

48 Network expansion? 48

49 Expanding your network for peering Theoretically, you now know that if you expand into a new POP, you could pick up X amount of peering, time to start making introductions. But who do you talk to? Contact the colocation provider and IXP operators in the target city. They usually have contacts at all the networks they provide services to. Plus, more peering for you means more business for them, so they have business reasons to want you to join and exchange traffic. Many networks use generic mailing lists for common tasks, such as peering@ or noc@ 49

50 Expanding your network for peering either the contacts you gather or as a worst case scenario, the peering@ list alias. Include a description of your network is and why they should want to peer with you. This is your opportunity to brag about your network. Create a list of favorable responses and how much traffic that represents. Now the important part, find out whether it makes sense for you to expand your network in order to peer! 50

51 Building a business case Get quotes from colocation providers and transport providers and compute how much it s going to cost to build a new POP. Divide that cost by how much traffic you believe you will be able to peer. If that cost is lower than how much you pay for transit, you have a good case to expand your network. Transit may cost less. It s not always cheaper to peer. Consider other factors like performance, redundancy, ability to meet previously unattainable peering policies. 51

52 In summary 52

53 Summary Devote one person to peering at your company, it s a full time job! Design your network so that you are flexible enough to achieve your traffic engineering goals. Create a viable peering strategy that fits your network. The more visible you are, the more successful your peering will be. This includes using industry standard mailing list aliases and joining peering.db! Know as much about your target network as you can. Send the right people to the right meetings. Remember that in the end, it s all dollars and sense. 53

54 Questions? Guy Tal Director of Strategic Relations Martin Levy Director, IPv6 Strategy Copyright 2009 Limelight Networks. All rights reserved.