You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been asked by several members (and datacenters with automated processes) at last weeks NANOG meeting if any support for IX-API (ix-api.net) would be coming in the future.
I believe that this is critical especially where there are community IXPs, such as us, that are also in markets that are served by those IXPs that created the IX-API. Allowing the automation of certain functions such as reseller ports, updating member info and contacts, mac addresses and ASNs would be helpful. Although we don't offer anything other than a peering LAN and closed user groups, automating those functions via the IX-API would reduce our volunteer time and workflows. If implemented I think a check box to allow use per member, similar to allowing peeringdb authentication, would be the way to go.
Reading the IX-API specifications and glossary also reminded my that in the past we have been asked to add Implementation and Legal (and Abuse) contacts as well, which we have pushed to our CRM. Having the Contract Reference or PO number in IXP-Manager is also something we have had to push towards the CRM.
The text was updated successfully, but these errors were encountered:
We have been asked by several members (and datacenters with automated processes) at last weeks NANOG meeting if any support for IX-API (ix-api.net) would be coming in the future.
I believe that this is critical especially where there are community IXPs, such as us, that are also in markets that are served by those IXPs that created the IX-API. Allowing the automation of certain functions such as reseller ports, updating member info and contacts, mac addresses and ASNs would be helpful. Although we don't offer anything other than a peering LAN and closed user groups, automating those functions via the IX-API would reduce our volunteer time and workflows. If implemented I think a check box to allow use per member, similar to allowing peeringdb authentication, would be the way to go.
Reading the IX-API specifications and glossary also reminded my that in the past we have been asked to add Implementation and Legal (and Abuse) contacts as well, which we have pushed to our CRM. Having the Contract Reference or PO number in IXP-Manager is also something we have had to push towards the CRM.
The text was updated successfully, but these errors were encountered: