Peering with Symantec
Symantec is moving toward a model of operating with three regionalised autonomous systems. Currently you may see traffic from a number of different autonomous systems, but an effort is underway to merge all of our commercial networks behind
AS21345 in Europe, AS26282 in North America and AS7583 in Asia Pacific & Japan.
For more information about Symantec please visit our corporate website.
While Symantec does not require a signed peering agreement with its peers it expects peers to be in line with the following policy:
The total traffic exchange between Symantec and any applicant should exceed 5Mbps. Symantec may advertise a subset of routes toward public exchange route-servers for peers which do not meet this criteria.
Symantec does not currently require applicants to maintain any specific traffic ratio.
Applicants who are downstream of existing peers should demonstrate significant mutual benefit from the establishment of a direct peering relationship.
Each interconnection between the applicant and Symantec is required to have no less than 1000Mbit/s capacity.
Multiple interconnects between peering networks are preferred.
All cabling costs shall be distributed between the applicant and Symantec, interface costs are solely those of the respective parties.
The applicant must maintain sufficient backbone capacity to exchange traffic without congestion.
The applicant must be willing to peer in all markets, including their home market.
The applicant must operate a 24x7x365 NOC which can be contacted via email or telephone.
The applicant must be able and willing to quickly trace and mitigate ongoing denial of service attacks, and malicious network activities.
The applicant must not establish a static route, default route (route of last resort), utilise any other means to send traffic over the interconnection for a route that is not advertised over BGP or otherwise abuse the peering relationship.
Neither party shall restrict, or otherwise tamper with traffic legitimately bound to the other party.
Applicant must not sell or give next-hop to any non-customer 3rd party (i.e. peer must not re-advertise Symantec routes to any peer)
Both parties shall register route, route6 and other related objects in an IRR database. These objects shall be maintained in order to ensure they are current for the purpose of filtering.
Symantec reserves the right to temporarily suspend any or all interconnections with a peer without prior notice in the event that the peer network is causing operational, or material damage to Symantec. Any interconnect suspended in this manner will be restored as soon as both parties are confident that
the operational issues are cured and cleared.
Symantec reserves the right to terminate any peering at any time with 60 days notice.
Symantec reserves the right to refuse peering to an applicant if it deems fit based upon commercial or operation concerns.
Symantec requests that all peers maintain up to date records in the PeeringDB (www.peeringdb.com)
We are available on a number of public exchanges today, with more coming. We are also happy to consider 1G and 10G PNI connections where this makes engineering sense.
The best place to request peering is by emailing Peering. We also maintain our PeeringDB.com records. You should too!