Your SlideShare is downloading. ×
Jan zorz procurement-ripe-501
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Jan zorz procurement-ripe-501


Published on

Published in: Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Procurement
    • RIPE-501 and next version draft
    • Jan Žorž, Go6 Institute Slovenia
    Stavanger, Norway (2011)
  • 2. 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
    Stavanger, Norway (2011)
  • 3. 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”
    • Intended input for generic EU IPv6 profile through EC project GEN6
    Stavanger, Norway (2011)
  • 4. RIPE-501 – official RIPE-NCC BCP Stavanger, Norway (2011)
  • 5. RIPE-501
    • 3 options: RFC lists, IPv6 Ready Logo cert and mix of first and second option.
    • Hosts
    • Consumer-grade Layer 2 switches
    • Enterprise/service provider Layer 2 switches
    • Firewalls, intrusion detection systems
    • Requirements for system integrator
    Stavanger, Norway (2011)
  • 6. 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.
    Stavanger, Norway (2011)
  • 7. Improvements in RIPE-501 replacement
    • It now covers:
      • Hosts
      • Consumer-grade Layer 2 switches
      • Enterprise/service provider Layer 2 switches
      • Firewalls, intrusion detection systems
      • CPE and Load Balancer spec
      • Mobile nodes spec
      • Requirements for system integrator
    Stavanger, Norway (2011)
  • 8. Improvements in RIPE-501 replacement
    • Only one way to comply:
      • Mix of IPv6 Ready Logo certification and the long list of RFCs
    Stavanger, Norway (2011)
  • 9. State of the RIPE-501 replacement
    • Merike Käo as new co-author
    • Finished the editing phase
    • Published on RIPE IPv6 WG mailing list for discussion, currently under Last Call
    • See new versions at
    Stavanger, Norway (2011)
  • 10. State of the RIPE-501 replacement
    • Lots of input and on-list and offlist discussion
    • Some very late, but still useful comments
    • Many people and organizations are waiting for this update or replacement getting official (two of them being EU/EC and also German government…)
    • Probably we’ll look into new and updated version at some point in time…
    Stavanger, Norway (2011)
  • 11. URLs, files, info…
    • RIPE-501: http :// 501
    • Draft of replacement document: equipment
    • Intermediate versions: /
    Stavanger, Norway (2011)
  • 12. Q&A
    • We are looking for consensus on next version of RIPE-501 at least for November RIPE meeting.
    • We have fully functional mailboxes, send us suggestions and comments 
    • [email_address]
    • [email_address]
    • [email_address]
    Stavanger, Norway (2011)