RGnet/PSGnet Peering Policy
For all trouble and problems with established peers email@example.com. Only
for very serious emergencies call +1 206 780 0431 x1.
Organization : RGnet/PSGnet
Seattle SIX : AS3130 184.108.40.206 2001:504:16::c3a/64 AS-RGNET
Equinix Dallas : AS4128 220.127.116.11 2001:504:0:5::4128:1 AS-RG-DFW
Contact Email : firstname.lastname@example.org
IRR Database : RGNET (whois.rg.net), mirrored by radb, ripe, and verio
General policy for peering
- RGnet/PSGnet consists of disjoint ASs, each being a research
rack. There are no users/customers behind the routers.
- RGnet/PSGnet peers on the SIX only with routers that are in
the Westin Building.
- RGnet/PSGnet prefers all BGP sessions have MD5 signature
- RGnet/PSGnet requires that peers permit LSR, loose source
routing, at least at the routers bordering the peering.
- Peers must agree to actively cooperate chasing security
violations, denial of service attacks, and similar incidents.
- Peers must agree to actively respond to all technical issues
within 48 hours. Non-response may result in depeering and other
- Peers must not abuse the peering relationship by doing any of
the following non exhaustive list: pointing default, resetting next
hop, selling or giving next hop to others, etc.
- RGnet/PSGnet reserves the right to not peer with anyone as
RGnet/PSGnet sees fit and to terminate any peering at any time with
30 days notice.
- RGnet/PSGnet reserves the right to change this peering policy
with 30 days notice.
If you agree to the above and wish to peer, please send the
following information to our contact address, <email@example.com>.
Peering Point :
IP Address :
Contact Email :
AS Macro :
IRR Database :
And please DO NOT configure the BGP session until we have agreed
and set a time to do so.