Jan zorz procurement-ripe-501


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Jan zorz procurement-ripe-501

  1. 1. Procurement <ul><li>RIPE-501 and next version draft </li></ul><ul><li>Jan Žorž, Go6 Institute Slovenia </li></ul>Stavanger, Norway (2011)
  2. 2. Why and how? <ul><li>Started in Slovenia by asking our government why they don’t require IPv6 when buying equipment </li></ul><ul><li>Continued through Go6 up to RIPE IPv6 community and towards very successful globally recognized IPv6 procurement document </li></ul><ul><li>Translated in many languages </li></ul>Stavanger, Norway (2011)
  3. 3. Why and how? <ul><li>Removes a first speedbump in IPv6 deployment process </li></ul><ul><li>Governments and enterprises are actually using it </li></ul><ul><li>“ You must require IPv6 and here is recommendation how” </li></ul><ul><li>Intended input for generic EU IPv6 profile through EC project GEN6 </li></ul>Stavanger, Norway (2011)
  4. 4. RIPE-501 – official RIPE-NCC BCP Stavanger, Norway (2011)
  5. 5. RIPE-501 <ul><li>3 options: RFC lists, IPv6 Ready Logo cert and mix of first and second option. </li></ul><ul><li>Hosts </li></ul><ul><li>Consumer-grade Layer 2 switches </li></ul><ul><li>Enterprise/service provider Layer 2 switches </li></ul><ul><li>Firewalls, intrusion detection systems </li></ul><ul><li>Requirements for system integrator </li></ul>Stavanger, Norway (2011)
  6. 6. RIPE-501 position paper from a Vendor  <ul><li>VendorX position paper: </li></ul><ul><li>After careful analysis of the RIPE-501 profile, Ci*co is expressing its support for the following reasons: </li></ul><ul><li>The set of features listed is deployment oriented and takes into account architectures that have been validated by experience. </li></ul><ul><li>The profile does not restrict itself to a small set of core IPv6 features. </li></ul><ul><li>The document lists a coherent set of IPv6 features that are likely to help the industry deploy IPv6 at a faster pace. </li></ul><ul><li>http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6553/brief_c80-674464.html </li></ul>Stavanger, Norway (2011)
  7. 7. Improvements in RIPE-501 replacement <ul><li>It now covers: </li></ul><ul><ul><li>Hosts </li></ul></ul><ul><ul><li>Consumer-grade Layer 2 switches </li></ul></ul><ul><ul><li>Enterprise/service provider Layer 2 switches </li></ul></ul><ul><ul><li>Firewalls, intrusion detection systems </li></ul></ul><ul><ul><li>CPE and Load Balancer spec </li></ul></ul><ul><ul><li>Mobile nodes spec </li></ul></ul><ul><ul><li>Requirements for system integrator </li></ul></ul>Stavanger, Norway (2011)
  8. 8. Improvements in RIPE-501 replacement <ul><li>Only one way to comply: </li></ul><ul><ul><li>Mix of IPv6 Ready Logo certification and the long list of RFCs </li></ul></ul>Stavanger, Norway (2011)
  9. 9. State of the RIPE-501 replacement <ul><li>Merike Käo as new co-author </li></ul><ul><li>Finished the editing phase </li></ul><ul><li>Published on RIPE IPv6 WG mailing list for discussion, currently under Last Call </li></ul><ul><li>See new versions at http://go6.si/RIPE501bis/ </li></ul>Stavanger, Norway (2011)
  10. 10. State of the RIPE-501 replacement <ul><li>Lots of input and on-list and offlist discussion </li></ul><ul><li>Some very late, but still useful comments </li></ul><ul><li>Many people and organizations are waiting for this update or replacement getting official (two of them being EU/EC and also German government…) </li></ul><ul><li>Probably we’ll look into new and updated version at some point in time… </li></ul>Stavanger, Norway (2011)
  11. 11. URLs, files, info… <ul><li>RIPE-501: http ://www.ripe.net/ripe/docs/ripe- 501 </li></ul><ul><li>Draft of replacement document: http://www.ripe.net/ripe/docs/other-documents/requirements-for-ipv6-in-ict- equipment </li></ul><ul><li>Intermediate versions: http://go6.si/ripe501bis / </li></ul>Stavanger, Norway (2011)
  12. 12. Q&A <ul><li>We are looking for consensus on next version of RIPE-501 at least for November RIPE meeting. </li></ul><ul><li>We have fully functional mailboxes, send us suggestions and comments  </li></ul><ul><li>[email_address] </li></ul><ul><li>[email_address] </li></ul><ul><li>[email_address] </li></ul>Stavanger, Norway (2011)