There are different levels of peering.
The policies below describe tier 1/2 peering between the big guys. Most peering relationships are not at that level.
Many small businesses have peering with more than one service provider. It's quite common. The current startup I work for has a /24 that they announce to their colo provider in San Francisco, as well as the ISP that serves their HQ location further down the peninsula. (The colo and their HQ are tied together as one ASN).
Michael N6MEF
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Tim Pozar Sent: Friday, March 16, 2012 9:43 AM To: AMPRNet working group Subject: Re: [44net] directly routed subnets
(Please trim inclusions from previous messages) _______________________________________________ On Mar 16, 2012, at 8:20 AM, Brian Kantor wrote:
Perhaps I should start collecting AUPs from various sources rather than having to create one from scratch.
URLs to model AUPs would be appreciated.
In concern of BGP peering...
You can see some of the hoops that ARIN requires for an ASN at:
https://www.arin.net/policy/nrpm.html
See section 5 https://www.arin.net/policy/nrpm.html#five for ASN requirements.
Certainly there are policies for peering that other ASNs. Some of these policies are good to look at for requirements for announcing address space. Some of the requirements are a bit onerous and don't apply. Comcast has their set of requirements at:
http://www.comcast.com/peering/
Certainly things like "Applicant must operate a US-wide IP backbone whose links are primarily 10 Gbps or greater" should not be a requirement. But points like:
* Applicant must have a professionally managed 24x7 NOC and agree to repair or otherwise remedy any problems within a reasonable timeframe. Applicant must also agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems.
or
* Applicant must maintain responsive abuse contacts for reporting and dealing with UCE (Unsolicited Commercial Email), technical contact information for capacity planning and provisioning and administrative contacts for all legal notices.
may be a good idea. The latter one would be needed to help resolve poisoning of address space and getting listed on various RBLs.
Other sites that have peering requirements can be seen at:
ATT - http://www.corp.att.com/peering/ Verizon - http://www.verizonbusiness.com/terms/peering/ AOL - http://www.atdn.net/settlement_free_int.shtml MFN/Abovenet - http://www.above.net/peering/
If folks want can make a stab at a draft for requirements for someone announcing 44/8 space.
Tim
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net