This document summarizes updates and status of Best Current Operational Practices (BCOP) from around the world. It discusses what a BCOP is, the problem it aims to address, and the BCOP solution. It then provides a global update on BCOP activity in various regions including Africa, Asia, Europe, Latin America, and North America. It outlines next steps such as continuing to develop new BCOP documents and considering global coordination. The presentation concludes by inviting attendees to get involved and provides relevant website links.
2. BCOP | February 2013
Agenda
• What is BCOP
• What is the problem?
• Global Update
• AfBCOP Update
• Other regions: LacNOG; NANOG; JANOG…
• Way Forward.
3. BCOP | February 2013
What’s a BCOP?
Best Current Operational Practice
•A living document describing the best operational
practices currently agreed on by subject matter
experts
•Vetted and periodically reviewed by the global network
engineering community (GNEC)
4. BCOP | February 2013
The Problem
• Operational knowledge tends to be “tribal”
• Presentations, hallway conversations, internal documents, in
someone’s head…
• Technology, tools, and practices change over time…
• There are hundreds of operational forums globally
• Archives stored in different formats, some searchable, rarely
have speech text or video, no vetting, and state unknown.
• How do I find up-to-date, relevant information
when I need it?
5. BCOP | February 2013
The BCOP Solution
Open, Transparent, Bottom-up, and Community
led
Community driven, community written, community
vetted Best Current Operational Practices from an
open forum, list, and publicly searchable site.
Community written and approved Development
Process for BCOPs
Everyone is welcome to participate
6. BCOP | February 2013
BCOP activity around the world:
http://www.internetsociety.org/deploy360/about/bcop/
•Africa region: AfBCOP group was started in May 2013, co-
chair: Douglas Onyango & Fiona Asonga.
•Asia: BCOP Task Force started at JANOG, co-chaired by Seiichi
Kawamura and Yoshinobu Matsuzaki, NZNOG BCOP starting up,
lead by Dean Pemberton
• No whole-region effort started yet
•Europe: RIPE BCOP Task Force created, co-chaired by Benno
Overeider and Jan Žorž
•Latin America: A BCOP Task Force was started under LACNOG,
lead by Luis Balbinot and Pedro R Torres Jr.
•North America: NANOG BCOP Committee established, lead by
Aaron Hughes and Chris Grundemann
7. BCOP | February 2013
AfBCOP Update
May 2013: First presentation made by Jan
Nov 2013: Presentation and BoF during the AFRINIC meeting
May 2014: Presentation and BoF during the AIS in Djibouti
Nov 2014: Presentation at the AFRINIC meeting in Mauritius
1. Co-Chair selected (Fiona Asonga)
2. Proposal: Common questions & best on IPv6 in Africa Proposal
(Alfred Arouna)
8. BCOP | February 2013
Potential Topics for Additional BCOPs
http://www.internetsociety.org/deploy360/about/bcop/topics/
•How to test your network performance
•How to check your visibility from global Internet
•De-Aggregation: strict filtering /48s out of /32
•How are operators using IRR?
•IPv6 enterprise network renumbering scenarios, considerations, and
methods
•DNS Policies
•Email Policies
•ICMP Filtering
•… (we need more suggestions)
9. BCOP | February 2013
Next Steps
•Continue to bootstrap new efforts as needed
•Develop new BCOP documents
• Lots of low-hanging fruit
•Review and update existing BCOP documents
•Start thinking & talking about Global
coordination
10. BCOP | February 2013
Get Involved Today!
•Join us at AIS 2016
•Contribute to an existing draft (discussion soon online)
•Offer ideas for new drafts
11. BCOP | February 2013
Websites
BCOP topics:
http://www.internetsociety.org/deploy360/about/bcop/topics/
What’s going on around the world:
http://www.internetsociety.org/deploy360/about/bcop/
12. BCOP | February 2013
News from RIPE region:
New ideas in the pipeline:
•How to simplify network operations
•DNS TTLs and best practices
•DDoS mitigation and best practices in cooperation and
reporting
•IPv6 deployment BCOP for enterprise/campus
environments
13. BCOP | February 2013
RIPE-631 BCOP document:
Title: “IPv6 troubleshooting for residential
helpdesks”
Contributors: Lee Howard, John Jason Brzozowski, David Freedman, Jason
Fesler, Tim Chown, Sander Steffann, Chris Grundemann, Jen Linkova, Chris
Tuska, Daniel Breuer, Jan Žorž
This document is intended to provide a starting point for
technical support staff at ISPs or enterprise IT helpdesks in
supporting IPv6. Problems with IPv6 are very rare, but fear
of the unknown has prevented or delayed many
organizations from rolling out IPv6 to their users, when all
technical problems have been solved. While this document
cannot encompass all possible problems, it should provide a
solid first step for front-line support personnel.
15. BCOP | February 2013
Table of content
1. What is a BCOP?
2. Summary
3. Background / History
4. Using This Document - Note for Helpdesk Managers
5. IPv6 Troubleshooting
5.1 Basic IPv6 Test
5.2 Test Connectivity
5.3 Test DNS
5.4 Check Home Router
5.5 Escalate
6. Explanation of Help Desk Codes on http://isp.test-
ipv6.com
112 - IPv4, plus Broken IPv6
4 - IPv4 only
4t - IPv4 plus Teredo
46 - IPv4 + IPv6
46t - Dual Stack, Possible Tunnel
624 - 6to4
64 - NAT64
16. BCOP | February 2013
Table of content
64t - NAT64, possible tunnel
“slow”
“mtu” - “Possible MTU issues” Warning
“Site(s) with failed connectivity” Warning
7. IPv6 training for helpdesk
8. Conclusion
9. Operator’s specifics
Appendix A: Acknowledgements
Appendix B. Basic troubleshooting flowchart
Appendix C. Collecting Data for Escalation
17. BCOP | February 2013
https://www.ripe.net/ripe/docs/ripe-631