Requirements
Urbanwave uses PeeringDB as a single authoritative source of truth. This means peering partners must have an up-to-date PeeringDB entry before a bilateral peering session can be established.
Urbanwave will use industry standards to secure the peering sessions. This includes industry standard practices and best common practices, including but not limited to BCP-38 and route filtering. Both parties should have a well set-up route-set or AS-SET as well as up-to date prefix maximums defined in PeeringDB. Urbanwave will use this data to filter routes received from the network’s BGP sessions.
Both parties must have an up-to-date NOC contact email, which is responsive to raised issues and concerns.
More details on PeeringDB at https://www.peeringdb.com/net/25280
