Philip Smith's Internet Development Site

User Tools

Site Tools

Trace: • hardware • hints • the_internet_routing_registry • why-peer • peering_policies
peering-toolbox:the_peering_database

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
peering-toolbox:the_peering_database [2022/05/06 05:17] – [The Peering Database] philippeering-toolbox:the_peering_database [2023/04/30 05:45] (current) – [Background] philip
Line 1: Line 1:
-===== The Peering Database =====+====== The Peering Database ======
  
 The [[https://www.peeringdb.com/|Peering Database]] is a freely available, user-maintained database of networks which take part in the global Internet. It is considered the authoritative source of all information relating to network operators who participate in peering around the world.  The [[https://www.peeringdb.com/|Peering Database]] is a freely available, user-maintained database of networks which take part in the global Internet. It is considered the authoritative source of all information relating to network operators who participate in peering around the world. 
Line 5: Line 5:
 The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centres, and other interconnection facilities, and is the first stop in making interconnection decisions.  The database facilitates the global interconnection of networks at Internet Exchange Points (IXPs), data centres, and other interconnection facilities, and is the first stop in making interconnection decisions. 
  
-==== Background ====+  * [[the_peering_database#background|Background]] 
 +  * [[the_peering_database#what_is_the_peering_db|What is the PeeringDB]] 
 +  * [[the_peering_database#creating_a_peeringdb_entry|Creating a PeeringDB entry]] 
 +  * [[the_peering_database#why_a_peeringdb_entry|Why a PeeringDB entry is needed]] 
 +===== Background =====
  
 In the early Internet (of the 1990s) there were few network operators and interconnect points around the world that interconnections were relatively straightforward to seek out and implement (in the author's experience anyway). In March 1999 there were 4640 ASNs in the Internet with only 800 providing transit. This compares with today's total exceeding 73000 ASNs and over 10000 ASNs providing transit, never mind that almost every country in the world now has at least one Internet Exchange Point if not a datacentre facilitating commercial interconnects. In the early Internet (of the 1990s) there were few network operators and interconnect points around the world that interconnections were relatively straightforward to seek out and implement (in the author's experience anyway). In March 1999 there were 4640 ASNs in the Internet with only 800 providing transit. This compares with today's total exceeding 73000 ASNs and over 10000 ASNs providing transit, never mind that almost every country in the world now has at least one Internet Exchange Point if not a datacentre facilitating commercial interconnects.
  
-In the 1990s establishing new interconnects by attending in major Internet operations meetings (NANOG, RIPE, AfNOG, APRICOT and so on), with network information passed on by word of mouth or email or even by letter!+In the 1990s, establishing new interconnects was achieved by attending major Internet operations meetings (NANOG, RIPE, AfNOG, APRICOT and so on), with network information passed on by word of mouth or email or even by letter!
  
 With the rapid growth of the Internet in the late 1990s and early 2000s, there needed to be a more scalable way for a Network Operator to get their "peering information" out to the global Internet operations community. And hence the PeeringDB was born. With the rapid growth of the Internet in the late 1990s and early 2000s, there needed to be a more scalable way for a Network Operator to get their "peering information" out to the global Internet operations community. And hence the PeeringDB was born.
  
-==== What is the Peering DB ====+===== What is the Peering DB =====
  
 The Peering DB is a repository of the important information that network operators need to determine whether an interconnection is feasible, makes commercial sense, makes technical sense, and is even technically feasible. While the Peering DB website has much more detailed information, the Peering Toolbox is highlighting the key points. The Peering DB is a repository of the important information that network operators need to determine whether an interconnection is feasible, makes commercial sense, makes technical sense, and is even technically feasible. While the Peering DB website has much more detailed information, the Peering Toolbox is highlighting the key points.
Line 29: Line 33:
 This one shows the Public peering and Private peering facilities AWS is present at. So a potential peer can check which locations they share with AWS, and then contact them about peering. The page for AWS contains data about number of prefixes, traffic ratios, etc, plus the IP addressing used at the various public Internet connect points. All this is designed to make it easier for prospective peers to assess and reach out to AWS for peering. This one shows the Public peering and Private peering facilities AWS is present at. So a potential peer can check which locations they share with AWS, and then contact them about peering. The page for AWS contains data about number of prefixes, traffic ratios, etc, plus the IP addressing used at the various public Internet connect points. All this is designed to make it easier for prospective peers to assess and reach out to AWS for peering.
  
-And the final example shows Aerelion (formerly Telia Carrier), the operator of AS1299, one of the international transit carriers serving the global Internet:+And the final example shows Arelion, the operator of AS1299, one of the international transit carriers serving the global Internet:
  
 {{:peering-toolbox:peeringdb-arelion.png?500|}} {{:peering-toolbox:peeringdb-arelion.png?500|}}
Line 35: Line 39:
 again showing the type of data that are published in the PeeringDB. again showing the type of data that are published in the PeeringDB.
  
-==== Creating a PeeringDB Entry ====+===== Creating a PeeringDB Entry =====
  
 The Peering Toolbox recommends (strongly) that any entity with their own AS Number and address space should create an entry in the Peering DB. There is no cost to doing so. The Peering Toolbox recommends (strongly) that any entity with their own AS Number and address space should create an entry in the Peering DB. There is no cost to doing so.
Line 46: Line 50:
   * Organisation website   * Organisation website
   * ASN   * ASN
-  * IRR as-set (you created one earlier)+  * IRR AS-set
   * Network Type   * Network Type
   * Number of IPv4 prefixes   * Number of IPv4 prefixes
   * Number of IPv6 prefixes   * Number of IPv6 prefixes
   * Traffic Levels   * Traffic Levels
-  * Traffic Ratios (inbound to your network, or out from your network) +  * Traffic Ratios (inbound to the network, or out from the network) 
-  * Geographic Scope (ie what locations do you serve)+  * Geographic Scope (ie what locations are served)
   * Protocols supported (IPv4 and IPv6 are common)   * Protocols supported (IPv4 and IPv6 are common)
   * Peering Policy (Open, Selective, Restricted)   * Peering Policy (Open, Selective, Restricted)
Line 61: Line 65:
  
  
-==== Why a PeeringDB entry ====+===== Why a PeeringDB entry =====
  
 Today very few network operators will considering peering with an entity that has no PeeringDB entry. In fact, many will make it a requirement before they will even respond to a peering request. Indeed, some operators will go as far as using information in the PeeringDB for configuring peering sessions with their peers, making it essential that the entries are kept up to date. Today very few network operators will considering peering with an entity that has no PeeringDB entry. In fact, many will make it a requirement before they will even respond to a peering request. Indeed, some operators will go as far as using information in the PeeringDB for configuring peering sessions with their peers, making it essential that the entries are kept up to date.
Line 68: Line 72:
  
  
-[[:peering-toolbox/how-to-peer| Back to "What I need to Peer" page]]+[[:peering-toolbox/how-to-peer| Back to "What is required for Peering" page]]
peering-toolbox/the_peering_database.1651814239.txt.gz · Last modified: by philip