Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Current IXF member list import rules #237
Default setting just decides if networks have to opt in or opt out.
only IP addresses within the IX prefix sets are added
All changes made by the importer are logged to the control panel, available to the AC, and able to be rolled back with a single click.
full documentation was provided to the AC 2017-11-01
referenced this issue
Nov 14, 2017
Is "state = active" in the JSON connection_list being required? I'm pondering how participants that are on hiatus are handled.
Is it expected that they will lose their PeeringDB listing in the IXP list when on hiatus, if marked "state = inactive". And then when they return to active state, they will either need allow_ix_update set to yes for an automatic update, or they will need to do a manual update?
Note: If a state is not set at all, it will be seen as active by default. If state is set the importer accepts either "active" or "connected" to qualify the entry for import.
From what I see almost 100% of incorrect entries came from networks who went out of business. Mailing them would not be very useful
@arnoldnipper since the ip addresses are what is being used to identify netixlans from ixf data, if one is found the other one can usually be corrected to the correct value, which seemed the reasonable approach to this during implementation, but maybe just dropping it makes more sense?