peeringdb: [beta] run through all poc when notifying about a conflict
Currently, only technical poc are considered for notifying about a conflict. However, there are networks which don’t have technical poc but provide other poc (abuse, sales, marketing). So instead of only considering technical poc we should consider all poc.
Please add to the ordered check-list these pocs in this order
- Maintenance (if not yet considered)
- Abuse
- Sales
- Public Relations
In case there is still no poc left, immediately open a DeskPRO ticket asking the exchange for more information. Please note that all exchanges meanwhile have at least tech_email or policy_email set.
curl -sG https://peeringdb.com/api/ix | jq '[.data[] | select((.tech_email == "") and (.policy_email == ""))] | length'
0
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 24 (17 by maintainers)
@peterhelmenstine I meant adding the admin contact(s) as a target for the mails including the technical POCs first, before bothering sales and marketing pocs.