11:59 a.m.
Hi,
At REANNZ we maintain an AS-SET with all our customers. We use this for commodity peering,
transit, etc and this is recorded in peeringdb.
However, it doesn't include NREN transit/backup. I don't really want to add NREN
transit to that AS-SET as I have no intention of announcing those prefixes to my commodity
peers and not including them provides some protection against making a mistake and leaking
them.
What I would like to do is maintain a second AS-SET that points to my regular AS-SET as
well as the list of NREN AS or AS-SETs I might provide transit to. The problem I see is
where to record this? Peeringdb doesn't have a suitable field other than notes.
Whilst we (Janet, AS786) are largely a leaf network off GEANT for these purposes (though
with some exceptions related to DDoS protection and islands connected off islands), we do
have a few AS-SETs that we use to cope with these differences.
AS-JANETUS (named from when we had a PoP in New York many moons ago) is used for our
transit providers.
AS-JANETPLUS is used for our commercial peers.
AS-JANETEURO is used for GEANT/R&E.
We put AS-JANETPLUS in PeeringDB on the basis that is largely used by potential peers,
and our AS786 aut-num object describes the routing policy with transit and GEANT.
Cheers,
Rob