Introduction to PeeringDB by Arnold Nipper
0 likes419 views
The document provides information about PeeringDB and its recent updates. It discusses why networks should list themselves in PeeringDB, as it helps facilitate new peering arrangements and allows networks to find peering contact and connection information of other networks. It also summarizes PeeringDB's governance structure and committees, highlights recent developments like new translations and a product manager hire, and outlines upcoming focus areas around fixing issues and discussing data ownership policies.
![• List all networks: curl -sG https://peeringdb.com/api/net
• Specific: https://peeringdb.com/api/net/20?pretty&depth=0&fields=id,org_id,name,asn,created,updated
Peering Asia 3.0, Kuala Lumpur, 2019-11-07
Quick Example Output in JSON
8
{
"meta": {},
"data": [
{
"id": 20,
"org_id": 10356,
"name": "20C",
"asn": 63311,
"created": "2014-11-17T14:59:34Z",
"updated": "2019-02-23T00:12:20Z"
}
]
}](https://image.slidesharecdn.com/day2-2peeringasia3-arnold-nipper-v2-191210091231/85/Introduction-to-PeeringDB-by-Arnold-Nipper-8-320.jpg)
Introduction to PeeringDB by Arnold Nipper
- 2. • Why should my facility, IXP or network be listed in PeeringDB? • Helps establish new peering more efficiently, with all information easy to find in one place • Maintain all of your contact and connection info • Find other network's peering contact and connection info • Find interconnection facility and IXP info • A PeeringDB record is required by many networks to peer • Can be used for automation to generate router configurations • Initial configuration to setup peering quickly • Update configuration if maximum prefixes change Peering Asia 3.0, Kuala Lumpur, 2019-11-07 2 What is PeeringDB?
- 3. APIX Region from PeeringDB‘s Point of View Peering Asia 3.0, Kuala Lumpur, 2019-11-07 3 Country IX Facilities Networks at IXes Networks in Facilities Networks total Networks in PeeringDB Networks in RIR AU 25 100 414 376 512 461 2545 IN 23 104 458 363 535 672 2551 JP 15 43 398 256 471 289 1119 ID 13 35 132 66 152 223 1654 CN 13 18 44 7 49 106 1663 NZ 8 36 119 112 148 142 626 HK 7 38 343 334 455 167 933 TH 7 18 50 47 71 69 566 SG 5 34 355 349 460 104 534 PH 5 4 31 20 43 58 436 TW 4 13 71 75 98 59 359 KR 3 8 63 33 72 60 1031 GU 3 4 5 7 8 6 10 VN 3 4 3 2 5 22 367 KH 3 2 18 1 18 35 121
- 4. APIX Region from PeeringDB‘s Point of View Peering Asia 3.0, Kuala Lumpur, 2019-11-07 4 Country IX Facilities Networks at IXes Networks in Facilities Networks total Networks in PeeringDB Networks in RIR MY 2 22 101 84 123 87 265 BD 2 10 21 8 25 176 864 NP 2 4 20 3 21 34 105 MN 2 0 6 0 6 20 50 MM 1 3 13 1 14 28 86 BT 1 3 8 1 8 13 19 PG 1 1 9 0 9 9 23 VU 1 1 3 1 4 3 13 AF 1 0 15 0 15 19 56 PK 0 2 0 3 3 40 182 MP 0 2 0 2 2 0 1 MO 0 1 0 0 0 4 12 BN 0 1 0 0 0 3 15 LK 0 0 0 0 0 7 25 NC 0 0 0 0 0 6 14 MV 0 0 0 0 0 6 13 FJ 0 0 0 0 0 5 14 LA 0 0 0 0 0 3 31
- 5. APIX Region from PeeringDB‘s Point of View Peering Asia 3.0, Kuala Lumpur, 2019-11-07 5 Country IX Facilities Networks at IXes Networks in Facilities Networks total Networks in PeeringDB Networks in RIR TL 0 0 0 0 0 3 8 TO 0 0 0 0 0 2 4 SB 0 0 0 0 0 1 8 WS 0 0 0 0 0 1 8 NR 0 0 0 0 0 1 3 FM 0 0 0 0 0 0 4 AS 0 0 0 0 0 0 3 KI 0 0 0 0 0 0 3 PW 0 0 0 0 0 0 3 CK 0 0 0 0 0 0 1 KP 0 0 0 0 0 0 1 MH 0 0 0 0 0 0 1 NU 0 0 0 0 0 0 1 TV 0 0 0 0 0 0 1 PN 0 0 0 0 0 0 0
- 6. The GUI // org view Peering Asia 3.0, Kuala Lumpur, 2019-11-07 Facilities are Shown Here NIXI has 1 Facility Networks are Shown Here NIXI has 1 Network Record Exchanges are Shown Here NIXI has 7 Exchange Records 6
- 7. RESTful API Designed for Automation • All operations are supported and are designed to be automated • Read • Create • Update • Delete • Each object type has an associated tag • Basic types: org, net, ix, fac, poc • Derived types: ixfac, ixlan, ixpfx, netfac, netixlan • List of objects: https://peeringdb.com/apidocs/ • API documentation: http://docs.peeringdb.com/api_specs/ Peering Asia 3.0, Kuala Lumpur, 2019-11-07 7
- 8. • List all networks: curl -sG https://peeringdb.com/api/net • Specific: https://peeringdb.com/api/net/20?pretty&depth=0&fields=id,org_id,name,asn,created,updated Peering Asia 3.0, Kuala Lumpur, 2019-11-07 Quick Example Output in JSON 8 { "meta": {}, "data": [ { "id": 20, "org_id": 10356, "name": "20C", "asn": 63311, "created": "2014-11-17T14:59:34Z", "updated": "2019-02-23T00:12:20Z" } ] }
- 9. Governance and Membership • PeeringDB is a United States 501(c)(6) volunteer organization that is 100% funded by sponsorships • Healthy organization, building financial reserves and executing the long term strategic plan • Membership rules • A corporation, limited liability company, partnership or other legal business entity may be a Member of the Corporation • Membership is determined by having both an active PeeringDB.com account and an individual representative or role subscription to the PeeringDB Governance mailing list • 344 addresses subscribed to the Governance mailing list (as of April 16, 2019) • Governance list is at http://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-gov • More information available at http://gov.peeringdb.com/ Peering Asia 3.0, Kuala Lumpur, 2019-11-07 9
- 10. Admin Committee Operations Committee Outreach Committee Product Committee • Manage administration of user accounts and PeeringDB records • Answer support tickets • Cleansing and completion of PeeringDB records Leads: Stefan Funke (Chair) Contact:admincom@ lists.peeringdb.com • Manage PeeringDB infrastructure Leads: Job Snijders (Chair) and Aaron Hughes (Vice Chair) Contact: pdb-ops@ lists.peeringdb.com • Manage marketing and social media • Develop and maintain presentations, workshops and webinars • Coordinate presentations and attendance at events Leads: Greg Hankins (Chair) and Bijal Sanghani (Vice Chair) Contact: outreachcom@ lists.peeringdb.com • Manage roadmap and development priorities • Ask for input from the community on desired features • Write SoWs to solicit bids to complete requested features Leads: Stephen McManus (Chair) and Matt Griswold (Vice Chair) Product Manager: Filiz Yilmaz Contact: productcom@ lists.peeringdb.com Committees Peering Asia 3.0, Kuala Lumpur, 2019-11-07 10
- 11. • Admin Committee volunteers are based around the world in a variety of time zones with diverse language skills • Goal is to resolve support tickets within 24 hours Peering Asia 3.0, Kuala Lumpur, 2019-11-07 11 Support Ticket Statistics 3,81 6,26 8,36 7,75 8,76 21,39 27,68 27,93 28,12 1,00 1,06 1,27 4,39 0,53 0,59 0,55 0,24 0,22 0,00 5,00 10,00 15,00 20,00 25,00 30,00 2012 2013 2014 2015 2016 (1.0) 2016 (2.0) 2017 2018 2019 Tickets/Day Resolution Time (d) 300% Increase! 1389 2284 3050 2828 648 9966 9915 8323 6225 1837 6873 10160 0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000 11000 2012 2013 2014 2015 2016 2017 2018 2019 Total Tickets/Year PeeringDB 1.0 PeeringDB 2.0
- 12. Contact sponsorship@peeringdb.com for sponsorship info! • Diamond Sponsorship - $25,000 / year • Limited to 2 sponsors • Very large logo on top line of Sponsors page with URL • Diamond Sponsor badge display on all records • Social media promotion • Platinum Sponsorship - $10,000 / year • Large logo on second line of Sponsors page with URL • Platinum Sponsor badge display on all records • Social media promotion • Gold Sponsorship - $5,000 / year • Medium logo on third line of Sponsors page • Gold Sponsor badge display on all records • Social media promotion • Silver Sponsorship - $2,500 / year • Small logo on fourth line of Sponsors page • Silver Sponsor badge display on all records • Social media promotion Become a PeeringDB Sponsor! Peering Asia 3.0, Kuala Lumpur, 2019-11-07 12
- 13. Thank you to our sponsors! 10/27/2019 EVENT, CITY, COUNTRY 13 Diamond Sponsor Platinum Sponsors Gold Sponsors Silver Sponsors
- 14. New Product Manager • Filiz Yilmaz joined as our Product Manager on 2019-04-01 • Responsibilities • Facilitate the creation of an ongoing roadmap for PeeringDB and provide this as input to the Outreach Committee • Shepherd the discussions of issues on GitHub and ensure resolution of issues that require decisions • Manage implementation and rollout of new features • Maintain the PeeringDB software release schedule • Keep Product Committee related documents on docs.peeringdb.com up to date • Contact: filiz@peeringdb.com Peering Asia 3.0, Kuala Lumpur, 2019-11-07 14 Filiz Yilmaz
- 15. Recent Developments - Highlights • Product Committee Decision Making process • Reworkeded process to act faster on issues • Product Committee Members to shepherd discussions • Logging decisions on Github for info dissemination and transparency purposes • Translations • Process documented internally to streamline the release of translated strings • Languages will be released at 80% maturity level • Newly added languages are always on https://beta.peeringdb.com from day 1 • Vendor selection Process • Policy document currently in the making • Increase vendor diversity 1 5 EPF 2019, Talinn, Estonia18/09/2019 Peering Asia 3.0, Kuala Lumpur, 2019-11-07
- 16. Internationalization Support – New in 2.9.1 1. Go to Your Profile 2. Choose Your Language and click “Set language preference” 3. Text Now Appears in the Selected Language! Translations Wanted! Get in Touch With productcom@lists.peeringdb.com if You are Interested in Translating. Peering Asia 3.0, Kuala Lumpur, 2019-11-07 16
- 17. Translations 1 7 18/09/2019 Peering Asia 3.0, Kuala Lumpur, 2019-11-07
- 18. Product Update - Next release and Discussions • Focus still on the Backlog issues, bug fixes and translations • Discussions on • IX-F importer • Data deletion and how to retain deleted data for R&D purposes • Data ownership • Discussion on who has final say on data when more than one party is involved (e.g. netixlan, ixfac, netfac, ) • Established a Task Force to work on a policy document 1 8 EPF 2019, Talinn, Estonia18/09/2019 Peering Asia 3.0, Kuala Lumpur, 2019-11-07
- 19. Putting it all together and what next? 1 9 PeeringDB 2.0 Process/New Features Bug fixes Outreach Surveys Translations API 2018 Django IX-F JSON 2017 Process improvements • Vendor Selection process • TF for Data ownership Backlog clean-up & Bug fixes Add More Languages • Turkish, Arabic, Romanian are recent additions Improve Translation tools to help translators Collect of user stories Identify new features/changes Ex: Interconnection requests sent using PeeringDB UI, helping business processes of networks?? 2019-2020 2016 Peering Asia 3.0, Kuala Lumpur, 2019-11-07
- 20. • Announce list: http://lists.peeringdb.com/cgi- bin/mailman/listinfo/pdb-announce • Governance list: http://lists.peeringdb.com/cgi- bin/mailman/listinfo/pdb-gov • Technical list: http://lists.peeringdb.com/cgi- bin/mailman/listinfo/pdb-tech • User Discuss list: http://lists.peeringdb.com/cgi- bin/mailman/listinfo/user-discuss • Docs, presentations, guides, tools: http://docs.peeringdb.com/ • Board and Officers: stewards@lists.peeringdb.com • Admins: support@peeringdb.com • Presentation requests: outreachcom@lists.peeringdb.com • Uptime status: http://status.peeringdb.com/ • Bugs and feature requests: https://github.com/peeringdb/peeringdb/ • Social media: • https://www.facebook.com/peeringdb/ • https://www.linkedin.com/company/peeringdb • @PeeringDB Information and Resources Peering Asia 3.0, Kuala Lumpur, 2019-11-07 20
- 21. Questions?