2:16 p.m.
On the call today the question was raised as to where one should
publish, and correspondingly where one can find, route policy
information for a given network. I believe it was Warrick that
mentioned the (historical) utility of traceroute.org as an example.
At least for commercial peers here in the US, the use of peeringdb.com
is probably the default interface used today for peering coordination.
I would claim that it would be of significant utility to R&E networks
for coordination as well.
From there one can find relevant information such as:
- URL to a Peering Policy web page w/ additional details
- URL links to looking glasses (if applicable)
- additional details in the notes field
For the more specific case of bgp community support, at present this is
still free-form text that has to go somewhere, but it's not always clear
where to look.
To pick on my friend Warrick, you can find a good example at:
https://www.peeringdb.com/net/393
Though perhaps in the notes field Warrick could say, "You can find
supported bgp communities near the bottom of our magnificent 1,174
line aut-num record in RADB"
Or for us at https://www.peeringdb.com/net/940
Perhaps we should add something to the tune of, "You can find our
supported traffic engineering bgp communities at /dev/null, best of luck!
But note for LHCONE VRF peers, we do support the mandatory knobs at
https://twiki.cern.ch/twiki/bin/view/LHCONE/LhcOneVRF#BGP_communities"
Dale