1 / 16

BCOP Update

BCOP Update. Aaron Hughes. What is BCOP. Best Current Operational Practices Open repository of living BCOPs Bottoms up development process Operator consensus driven (80/20) Transparent Revision controlled Vetted via BCOP-DP (community written) and subject matter experts Local and Global.

gerald
Download Presentation

BCOP Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BCOP Update Aaron Hughes

  2. What is BCOP • Best Current Operational Practices • Open repository of living BCOPs • Bottoms up development process • Operator consensus driven (80/20) • Transparent • Revision controlled • Vetted via BCOP-DP (community written) and subject matter experts • Local and Global

  3. Problem Statement • I have an operational problem and would like to know the best current operational practice to solve it. • There are hundreds of operational forums globally • All stored in different formats, some searchable, rarely have speech text or video, no vetting, and state unknown.

  4. BCOP Timeline • 2010 • Lightning Talks in operator and RIR communities resulting in validating need • E-mail list –discuss launched • 2011 • Website launch • Deployment process evolution and launch as an unattached group • Draft BCOPs written

  5. BCOP Timeline cont. • 2012 • Renamed BCP to BCOP (IETF confusion) • BCOP-DP completed • BCOPs ratified • Request assistance from ISOC, ARIN, NANOG, RIPE, volunteers • 2013 • Single unattached group move to Multi-Regional & Global BCOP org.

  6. BCOP Structure 2012

  7. Restructure • Regional Operator driven • Some BCOPs stay local • Others become Global BCOPs when appropriate (Process in progress)

  8. Restructure cont.

  9. Restructure cont. • Move existing BCOP-PD, BCOPs, List, website, track to single local OG to use as template for other OG/OF • Identify neutral organization to host global BCOPs • Validate interest from parties and execute

  10. Regional • NANOG Board agreed with need and support • Moved list • Moving website • Track converted to regional • BCOP-PD changes in progress to use as template in other OG/OF

  11. Global • ISOC Deploy360 Programme identified as match for hosting global process, support, hosting, etc. • Strategic alignment / real-world deployment information for key Internet technologies such as IPv6, DNSSEC, Routing Resiliency/Security

  12. Snapshot today • Regional in place @NANOG • Focus shifted to content (BCOPs) • ISOC testing water / validating interest Globally / working with regional BCOPs to create global process and repository

  13. What’s done today? • BCOP-DP • BCOP_IPv6_Subnetting • BCOP_Public_Peering_Exchange • BCOP_IPv6_Peering_and_Transit • Input needed for v2

  14. What’s next • Prior to NANOG58 (June) • Website move • Updated doc management system in place • Revision controlled rich docs (challenge) • Several BCOP Drafts to list for discussion • Send us your ideas! (bcop@nanog.org)

  15. How to get involved • ARIN/NANOG Region • http://mailman.nanog.org/mailman/listinfo/bcop • Global involvement • Deploy360@isoc.org • General questions • Aaron Hughes aaron@6connect.com • Chris Grundemanncgrundemann@gmail.com

  16. Questions?

More Related