Talk:Peering

message: ICAIS description relies on implicit conclusions and inferences drawn by an educated reader. Even then, the thing is presented from an almost theoretical, save the terminology, and politically based  view, which gives no detail and makes it difficult to form an opinion. After reading it several times over, I concluded that: International Charging Agreements for Internet Service is viewed from an economic perspective. Adoption would decrease costs for those least able to pay and would arbitrarily place economic burden on those who bear no moral or legal responsibility to remedy fabricated injustice. AwesomeMachine 17:47, 31 May 2011 (UTC)
replies: text: Someone has since done this. -- Beland 23:56, 16 May 2006 (UTC)
thread_title: Clarification

message: Some of the general guidelines to successfully engaging in peering include:
* Do: Respond promptly to NOC emails/calls.
* Do: Have administrative, technical and NOC contact information ready on any peering request.
* Do: Maintain a database of traffic to existing peers to assist with peering upgrades as traffic increases. Regularly examine how much traffic you do to your peers at a set interval so you can prevent any capacity issues.
* Do: When approaching a network to peer, have traffic statistics ready.
* Do: Treat your peering sessions like any other production circuit. Just because it is free does not mean you can shut it down at any time. 
* Do: Maintain a peering "web site" which includes your locations, IP addresses, ASNs, contact information (administrative, technical, NOC) and policies.
* Do: Use www.peeringdb.com to share your peering information with other networks.
If you have to reduce/increase your prefix count, please let your peers know when, how long, and if possible, why.
* Do not: Leak prefixes to your peers.
* Do not: Point non-advertised routes or default routes to peering nexthops.
* Do not: Sell specific peer routes to customers (known as selling nexthop).
* Do not: E-mail bomb existing peers, or peers who do not respond to you.
* Do not: Advertise inconsistent prefixes at multiple peering locations.
* Do not: Expect the other peer to honor your MEDs
* Do not: Lie about your network size, network capacity, or traffic to a potential or existing peer.
* Do not: Setup eBGP sessions via public peering to networks that have not agreed to peer with you.
* Do not: Attempt to modify BGP origin codes to force cold-potato routing.
----
I removed the above because it is normative, which is not NPOV. -- Beland 23:55, 16 May 2006 (UTC)
replies: text: I disagree. Those are an accurate description of accepted best practice in the industry. That is, a description of what is, not what should be. Though their description is not the best, shouldn't be do and don't lists but practices generally considered helpful and unhelpful. Perhaps that distinction is why they appeared to be recommendations rather than actual accepted practice. Jamesday 19:20, 5 September 2006 (UTC)
thread_title:  Peering dos and don'ts 

message: With the following line:
Peer directly with that network, or with a network who sells transit service to that network, or
If A pays B, B pays C and C has a peering with D, does it mean that D can send traffic to A through B and C?
Thanks 89.180.64.93 05:54, 10 May 2007 (UTC)
thread_title:  Clarification 

message: Hello fellow Wikipedians,
I have just added archive links to  on Peering. Please take a moment to review my edit. If necessary, add  after the link to keep me from modifying it. Alternatively, you can add  to keep me off the page altogether. I made the following changes:
*Added archive https://web.archive.org/20070927183732/http://www.information-age.com/article/2001/june/psinet-c_and_w_dispute_causes_internet_blackout to http://www.information-age.com/article/2001/june/psinet-c_and_w_dispute_causes_internet_blackout
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
Cheers. —cyberbot IITalk to my owner:Online 06:43, 28 August 2015 (UTC)
thread_title:  External links modified