Peering

Peering Agreement — the terms

Liberty Security Services, LLC — AS21990

AS21990 asks for a signed mutual agreement before a peering session is turned up. This page sets out what that agreement says, so you can decide whether it is worth your time before you write to us — rather than after a round trip and an emailed PDF.

What each side agrees to

Traffic

• Each side announces only its own routes and those of its customers.
• Neither side announces routes learned from a third-party peer or transit provider, and neither uses the other as transit.
• Neither side points a default route at the other.

Routing

• Both sides register their routes in an IRR. A side that announces routes for customers or downstream networks also maintains an AS-SET describing itself and them. AS21990 originates one prefix and carries no downstream routes, so its route objects are a complete answer for filter-building purposes.
• Both sides maintain valid ROAs and perform Route Origin Validation, dropping RPKI invalids.
• Both sides filter what they receive against the other’s registered IRR data.
• Both sides apply a max-prefix limit and give notice before exceeding a previously advised one. AS21990’s figure is 20, which matches our PeeringDB record.

Operations

• Seven days’ notice of planned maintenance affecting the interconnection, prompt notice of emergency work. That is the same commitment as our public maintenance policy, deliberately — a contract that promised something different from the website would be a trap for whichever of us read the wrong one.
• A NOC contact reachable at any hour for issues affecting the interconnection, a monitored abuse contact, and a current PeeringDB record. Our desk is staffed 07:00–21:00 Eastern and an on-call rotation covers the rest; the clause says reachable at any hour rather than 24-hour NOC because the second would imply a staffed desk around the clock and that is not what we have.
• Where traffic from one side is causing material harm, the other may filter it immediately and tell us afterwards. That runs both ways.

Money

• Settlement-free. Neither side invoices the other, and neither incurs any payment obligation under the agreement.
• Each side bears its own interconnection costs — cross-connect, optics, ports.

Term

• Runs from the date of last signature until terminated.
• Either side may terminate for convenience on 30 days’ written notice. No lock-in, and no exclusivity: peering with us does not restrict who else you peer with or buy transit from.
• Immediate suspension is available for material breach of the traffic, no-leak or abuse clauses, or where the law requires it.
• The interconnection is provided as-is. Neither side warrants availability, capacity or performance.
• The existence of the peering relationship is not confidential. Technical and commercial detail exchanged under it is.

Two clauses are not on this page

Limitation of liability and governing law are in the executable document and are with counsel. We are not going to publish a settled position on either while that is true, because a term stated publicly and then changed at signature is worse than one you were told to expect.

What we can say now: the liability clause excludes indirect and consequential loss both ways, and the governing-law clause currently names New York. If you are outside New York and that is a problem, say so early rather than at signature — it is a conversation we expect to have.

Getting the document

Email peering@as21990.net with your ASN and PeeringDB link and we will send the executable copy. It comes with a technical schedule to complete: AS numbers, prefixes announced, max-prefix, AS-SET where you have one, interconnection point, and NOC, abuse and peering contacts for each side.

The peering section of our main page covers the request process, what we filter on, and session parameters. Note that we have no presence in a carrier-neutral facility today, so private interconnect is the route rather than a cross-connect you can order.