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