1 / 7

BCOP Taskforce Administrative Matters

BCOP Taskforce Administrative Matters. RIPE 68 Monday 12 May 2014. Agenda. Administrative matters (5-10 mins ) IPv6 Troubleshooting for Helpdesks (15 mins ) 
Sander Steffann et al. BGP Configuration BCOP (15 mins )
Francois Contat et al.

kimn
Télécharger la présentation

BCOP Taskforce Administrative Matters

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 TaskforceAdministrative Matters RIPE 68 Monday 12 May 2014

  2. Agenda • Administrative matters (5-10 mins) • IPv6 Troubleshooting for Helpdesks (15 mins)
Sander Steffannet al. • BGP Configuration BCOP (15 mins)
Francois Contatet al. • DNSSEC Operational Practices for Authoritative Name Servers (15 mins)
MatthijsMekking • Update on the “Code of Conduct” Initiative (10 mins)
Andrei Robachevsky • Closing(5-10 mins)

  3. Administrative Matters • BCOP TF charter • Update from NANOG BCOP - Chris Grundemann • Update from JANOG BCOP – Seiichi Kawamura and/or MatsuzakiYoshinobu

  4. BCOP TF Proposed Charter: Goals • Identify and discuss operational issues among the operators and to produce document series that capture the best practices for operationalising Internet technologies. • Provide a way to make good operational practices reference documents easily available, e.g., via RIPE Documents series. • Documents should be produced by experienced operators. • Provide a place for operators to identify, discuss, and communicate their operational needs, and if there are no standards for this problem, channel these to the standards process.

  5. BCOP TF Proposed Charter: Activities • Presentations from operators that lay out their issues using existing technology, protocols, standards, and implementations. • Shepherd document that capture good current operational practice: • Find two (or more) operators to work on a document. • Collect community input by presenting document in appropriate WG, making sure that document is technically sound (this can imply that different iterations of the document are discussed in WG). • Coordinate with other BCOP activities in other RIR regions (e.g. at NANOG), for overlap or conflicting documents, etc. • Publish document in RIPE series with attribute to WG. • Open discussion of what operators need to ease the deployment of new technologies—features and mechanisms needed in the real world.

  6. BCOP TF Closing

  7. BCOP TF Activities Follow Up • Join activity/initiative to produce a BCOP document • collaborative effort with operators involved • BCOP TF ignites, but most work is within WGs • Join the mailing list: https://www.ripe.net/mailman/listinfo/bcop • BCOP TF page: http://www.ripe.net/ripe/groups/tf/bcop

More Related