 |
 |
The folks on NWAX are using IXPManager (https://github.com/inex/IXP-Manager), as well as others. AFAIK, this automates lots of this process (DNS, route-servers, etc) and pulls things from PeeringDB. Might be worth a look. -- Andrew Hoyos [log in to unmask] > On Oct 25, 2016, at 2:00 PM, Jason Hanke <[log in to unmask]> wrote: > > There is also a peeringDB API. > > It might be time for a database driven documentation. Then we could > export/import to dns or switch configs. > > An online request form might be a good start. > > On Tue, Oct 25, 2016 at 1:56 PM, Richard Laager <[log in to unmask]> wrote: >> The exchange only cares about the max prefix value if it's larger than >> our default route server limit of 1000. That's a big network, and I >> think we've only hit that once. I'm not sure we need to bother getting >> an explicit number from every network on turn-up. >> >> On the PeeringDB thing... I've thought about that before too. Is >> *requiring* an entry going too far? I'm on the fence about that. >> >> I see that SIX links the AS number in the participants list to PeeringDB >> rather than bgp.he.net. I like the bgp.he.net links, but I should see if >> I can find some place on the list to put a PeeringDB link. >> >> -- >> Richard > > > > -- > Jay Hanke > CTO > Neutral Path Communications > 3 Civic Center Plaza, Suite 204 > Mankato, MN 56001 > (507) 327-2398 mobile > [log in to unmask] > www.neutralpath.net