Peering Policy - Revision history

Garlicky: /* Peering Information */

2023-10-04T15:38:57Z

Peering Information

← Older revision		Revision as of 09:38, 4 October 2023
Line 33:		Line 33:
	'''Suggested IPv4 Max Prefix:''' 75		'''Suggested IPv4 Max Prefix:''' 75

	'''Suggested IPv6 Max Prefix:''' 5		'''Suggested IPv6 Max Prefix:''' 15

	'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]		'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]

Pashdown: /* Peering Information */

2023-01-24T18:50:03Z

Peering Information

← Older revision		Revision as of 12:50, 24 January 2023
Line 31:		Line 31:
	'''[http://www.peeringdb.com/view.php?asn=6315 PeeringDB]'''		'''[http://www.peeringdb.com/view.php?asn=6315 PeeringDB]'''

	'''Suggested IPv4 Max Prefix:''' 50		'''Suggested IPv4 Max Prefix:''' 75

	'''Suggested IPv6 Max Prefix:''' 5		'''Suggested IPv6 Max Prefix:''' 5

Jab at 18:05, 28 January 2014

2014-01-28T18:05:23Z

← Older revision		Revision as of 12:05, 28 January 2014
Line 36:		Line 36:

	'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]		'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]


			[[Category:FAQ]][[Category:About]]

Pashdown: adjust max prefix

2013-05-29T17:35:04Z

adjust max prefix

← Older revision		Revision as of 11:35, 29 May 2013
Line 31:		Line 31:
	'''[http://www.peeringdb.com/view.php?asn=6315 PeeringDB]'''		'''[http://www.peeringdb.com/view.php?asn=6315 PeeringDB]'''

	'''Suggested Max Prefix:''' 50		'''Suggested IPv4 Max Prefix:''' 50

			'''Suggested IPv6 Max Prefix:''' 5

	'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]		'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]

Pashdown: md5 and ipv4 /24

2013-05-29T17:01:05Z

md5 and ipv4 /24

← Older revision		Revision as of 11:01, 29 May 2013
Line 13:		Line 13:
	#Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP. Neither party shall alter, sell, or give next-hops to a third party. These activities are considered theft of service, and will be prosecuted to the fullest extent of the law.		#Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP. Neither party shall alter, sell, or give next-hops to a third party. These activities are considered theft of service, and will be prosecuted to the fullest extent of the law.
	#Neither party shall announce to the other the more specific routes of prefixes learned via a third party transit customer.		#Neither party shall announce to the other the more specific routes of prefixes learned via a third party transit customer.
			#BGP MD5 authentication is preferred, but not required.
			#Peers are expected to aggregate their routes. Anything smaller than a IPv4 /24 will be dropped.

	== General Policy ==		== General Policy ==

Pashdown: initial

2013-05-29T00:15:56Z

initial

New page

== Operational Requirements ==
#Both parties provide an escalation path for resolving network issues in a timely fashion. Issues of a non-emergency technical nature should be responded to within 48 hours.
#Both parties shall be responsive to unsolicited bulk email, hacking, Denial of Service, and other network security and abuse issues. A good faith effort should be made to provide a qualified network engineer to trace ongoing network attacks within a reasonable amount of time.
#Both parties shall provide access to a route server, looking glass, or similar service for the purposes of routing audits, diagnostics, and troubleshooting.
#Both parties shall work quickly and diligently to establish additional capacity to accommodate traffic growth.

== Technical Requirements ==
#Both parties shall announce consistent routes across all interconnection points.
#Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering. Both parties shall make good faith efforts to keep this information up to date.
#Both parties shall make every reasonable effort to restrict the transmission of Denial of Service attacks and packets with forged source addresses from their network.
#Both parties shall announce only their own routes and the routes of their transit customers to the other party. No other routes are permitted, and may be filtered if detected.
#Neither party shall establish a static route, a route of last resort, or otherwise send traffic to the other party for a route not announced via BGP. Neither party shall alter, sell, or give next-hops to a third party. These activities are considered theft of service, and will be prosecuted to the fullest extent of the law.
#Neither party shall announce to the other the more specific routes of prefixes learned via a third party transit customer.

== General Policy ==
#XMission reserves the right to change this policy at any time.
#In the event of a severe or quality-of-service impacting violation of these policies, the interconnection may be temporarily suspended without notice.
#Any interconnection may be terminated for any reason, with 30 days notice.
#All requirements must be met at the time the request for Peering is made, and must continue to be met for the duration of the interconnection.
#XMission reserves the right to accept or decline any interconnection request for any reason.

== Peering Information ==

'''ASN:''' 6315

'''[http://www.radb.net/query/ IRR AS-SET]:''' AS-XMISSION

'''[http://www.peeringdb.com/view.php?asn=6315 PeeringDB]'''

'''Suggested Max Prefix:''' 50

'''Contact:''' [mailto:peering@xmission.com peering@xmission.com]