About IPBCOP

When creating documentation for IT infrastructure it’s tough enough trying to figure out your current environment. Pre-existing documentation and templates can make this process much simpler.

The IP Best Current Operational Practice (IPBCOP) project will collect the best practices known within the operations community and capture those practices in a series of documents. These “living documents” are peer reviewed by technology experts who actually deploy and manage these environments. We believe the best documentation is when it is based on real-world implementations.

This is a community project and is open to all to participate and get involved. We welcome your participation and look forward to working together to build better documentation for the entire community.

Get Involved

There are three primary ways to get involved with the IP BCOP effort:

1. Join the mailing list where the discussion occurs.

2. Review the existing drafts.

3. Use the BCOP template to create a new draft to submit to the community.

We would, of course, also welcome you to follow us on Twitter, Facebook or Google+ and engage in the conversation there.

Ratified BCOPs

At the February 6, 2012, IPBCOP meeting at NANOG 54, the following documents were ratified as official Best Current Operational Practices:

Other documents exist in draft status and may be ratified in future meetings.

Drafts

At the current time, the following documents are in draft form and under discussion within the project:

We welcome any feedback you have on the drafts. Please join our mailing list to join the discussion.

October 23

New Version 0.6 of IPv6 Peering and Transit BCOP Draft

Chris Grundemann recently completed a new version 0.6 of the BCOP Draft on “IPv6 Peering and Transit.”  This draft was discussed at NANOG 56 in Dallas this week.  It is available for download in both Word and PDF and comments can be sent to the IPBCOP mailing list.

Permanent link to this article: #

May 14

Final ratified version of IPv6 Subnetting Best Current Operational Practice now posted

At the IPBCOP meeting at NANOG 54 on February 6, 2012, three of the draft BCOP documents were ratified.

One of those, the IPv6 Subnetting BCOP, has now been posted in its final ratified form.  The goal of this document is:

This BCOP aims to provide general IPv6 subnetting guidelines that can be followed by any network operator when planning and implementing an IPv6 network deployment. The primary focus is on understanding IPv6 subnets and addressing plans, creating operational clarity and future proofing.

The other two documents, both listed on the Ratified BCOPs page, were approved without further modifications from the published drafts. Once the documents receive some minor editorial cleanup they will then be posted.

Permanent link to this article: #

February 07

New BCOP Draft Posted – IPv6 Peering and Transit

We’ve now added a new BCOP draft to the site on “IPv6 Peering and Transit.”  Chris Grundemann presented the draft yesterday at NANOG 54 and at this point is looking for any and all feedback on the document.  He is looking for co-authors, contributors, expert reviewers and any other comments and suggestions about the draft.  It is available for download in both Word and PDF and comments can be sent to the IPBCOP mailing list.

Permanent link to this article: #

February 03

BCOP Presentation at NANOG 54

NANOG logoIf you will be attending NANOG 54 next week in San Diego, California, Aaron Hughes will be presenting about this IP BCOP effort.  The presentation will be on Monday, February 6, from 4:30-6:00pm in the California Ballroom. Aaron will be discussing:

  • Introduction to BCOP
  • Current Drafts & Ratification
  • New Drafts
  • New Website
  • SBIR (Michael Sinatra)
  • BCP ARP/ND (Linda Dunbar)
  • BCOP ORG review
  • Proposals for new content or topic requests

Aaron’s background is:

Aaron brings more than 15 years of experience in the telecommunications industry. Aaron Hughes is President and CTO at 6connect, Inc specializing in Internet Engineering automation solutions, cooling technologies and distributed managed services with a focus on IPv6. He is also the Chief Network Architect at UnitedLayer bringing more than 15 years of experience in the telecommunications industry and is responsible for network topology planning, design and operations. Aaron has also held network and system architecture and Sr. level management roles at Lockheed Martin, Cariden Technologies, Terremark, Certainty Solutions, Quest Technologies, RCN, UltraNet and Channel(1) Communications.

Permanent link to this article: #