1 / 22

Story about RIPE-501 and RIPE-554

Story about RIPE-501 and RIPE-554. jan@go6.si. 1. About me (in a glance). CEO of Slovenian Go6 Institute IPv6 advocate IPv6 consultant for many Slovenian operators and enterprises In network and Internet operations for 22 years 13 years of experience with IPv6

rmclane
Télécharger la présentation

Story about RIPE-501 and RIPE-554

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. Story about RIPE-501 and RIPE-554 jan@go6.si 1

  2. About me (in a glance) • CEO of Slovenian Go6 Institute • IPv6 advocate • IPv6 consultant for many Slovenian operators and enterprises • In network and Internet operations for 22 years • 13 years of experience with IPv6 • Active and contributing member of RIPE and IETF community • Primary co-author of RIPE-501/554 IPv6 procurement doc • Co-author of RFC 6346 (A+P approach to IPv4 depletion) • Frequent IPv6 Flyer (Google IPv6 implementors conference, OECD meeting, RIPE, different government meetings, etc…) 2

  3. RIPE-501/554 - Why and how? • Started in Slovenia by asking our government why they don’t require IPv6 when buying equipment • Continued through Go6 up to RIPE IPv6 community and towards very successful globally recognized IPv6 procurement document • Translated in many languages

  4. RIPE-501/554 – Consensus building process • 1,5 year to get consensus on RIPE-501 • Another 1,5 years to get consensus on RIPE-554 • Many people from community and industry involved in this process

  5. RIPE-501/554 Why and how? • Removes a first speedbump in IPv6 deployment process • Governments and enterprises are actually using it • “You must require IPv6 and here is recommendation how”

  6. RIPE-501 – official RIPE-NCC BCP

  7. RIPE-554 – TOC

  8. RIPE-554 – hosts mandatory req.

  9. RIPE-554 – hosts optional req

  10. RIPE-501 position paper from a Vendor  VendorX position paper: After careful analysis of the RIPE-501 profile, Ci*co is expressing its support for the following reasons: The set of features listed is deployment oriented and takes into account architectures that have been validated by experience. The profile does not restrict itself to a small set of core IPv6 features. The document lists a coherent set of IPv6 features that are likely to help the industry deploy IPv6 at a faster pace. http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6553/brief_c80-674464.html

  11. Improvements in RIPE-554 It now covers: Hosts Consumer-grade Layer 2 switches Enterprise/service provider Layer 2 switches Firewalls, intrusion detection systems Routers and L3 switches CPE and Load Balancer spec Mobile nodes spec Requirements for system integrator

  12. Improvements in RIPE-554 More text, descriptions and explanations:

  13. Improvements in RIPE-554 Only one way to comply: Mix of IPv6 Ready Logo certification and/or the long list of RFCs

  14. RIPE-554 Intended to use as an initial template for European Commission to develop “Generic EU IPv6 profile” 21

  15. Co-authors of RIPE-554 – Q&A time  • Sander Steffann Jan Žorž Merike Käo sander@steffann.nljan@go6.sikaeo@merike.com 22

More Related