DUNDi peering

General Peering Information

Currently, the peering structure is as follows:

Tier 1 Peers - (Service Provider Level)

  • Primary Peers with a significant amount of bandwidth
  • Peers only with Tier 1 and Tier 2 providers. (Optimally all tier 1 providers willl be peers of each other.)

Tier 2 Peers - (ISP Provider Level)

  • Secondary Peers with at least 50% of their Tier 1 providers bandwidth
  • Peers with at least one Tier 1 provider, but mostly with Tier 2 and Tier 3 providers.

Tier 3 Peers

  • Tertiary Peers with at least 50% of their Tier 2 provider's bandwidth.
  • Peers with at least one Tier 2 provider, but mostly with Tier 3 providers and end users/customers.

Quote from Mark Spencer:
"The core tier 1 people will all be exchanging *most* call setups. The
challenge is to try to trim off as many branches as possible and to reduce
as much as possible the number of queries that have to go deep into the
tree. To this end, it is beneficial to have numbers which are similar
(e.g. all Netherlands numbers) behind a one or more tier 1 / tier 2 nodes.
Note that the protocol is designed to handle *any* graph and any
distribution of numbers, but certain orientations are more effective in
the value they bring to the cache and in their ability to block off large
chunks of the tree."

To reduce the total number of branches it is advisable to seek out peers with numbers that are similar.

Your search heirarchy should be as follows:
  • Country Code
  • Area/Locale Code

Ues the following links to contact providers:

See Also

General Peering Information

Currently, the peering structure is as follows:

Tier 1 Peers - (Service Provider Level)

  • Primary Peers with a significant amount of bandwidth
  • Peers only with Tier 1 and Tier 2 providers. (Optimally all tier 1 providers willl be peers of each other.)

Tier 2 Peers - (ISP Provider Level)

  • Secondary Peers with at least 50% of their Tier 1 providers bandwidth
  • Peers with at least one Tier 1 provider, but mostly with Tier 2 and Tier 3 providers.

Tier 3 Peers

  • Tertiary Peers with at least 50% of their Tier 2 provider's bandwidth.
  • Peers with at least one Tier 2 provider, but mostly with Tier 3 providers and end users/customers.

Quote from Mark Spencer:
"The core tier 1 people will all be exchanging *most* call setups. The
challenge is to try to trim off as many branches as possible and to reduce
as much as possible the number of queries that have to go deep into the
tree. To this end, it is beneficial to have numbers which are similar
(e.g. all Netherlands numbers) behind a one or more tier 1 / tier 2 nodes.
Note that the protocol is designed to handle *any* graph and any
distribution of numbers, but certain orientations are more effective in
the value they bring to the cache and in their ability to block off large
chunks of the tree."

To reduce the total number of branches it is advisable to seek out peers with numbers that are similar.

Your search heirarchy should be as follows:
  • Country Code
  • Area/Locale Code

Ues the following links to contact providers:

See Also

Created by: rwjblue, Last modification: Mon 15 of Jun, 2009 (17:10 UTC) by amessina
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+