jan zorz procurement-ripe-501

12
Jan Žorž <[email protected]> Procurement RIPE-501 and next version draft Jan Žorž, Go6 Institute Slovenia Stavanger, Norway (2011)

Upload: ipv6no

Post on 30-May-2015

416 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

Procurement

RIPE-501 and next version draft

Jan Žorž, Go6 Institute Slovenia

Stavanger, Norway (2011)

Page 2: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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)

Page 3: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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)

Page 4: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

RIPE-501 – official RIPE-NCC BCP

Stavanger, Norway (2011)

Page 5: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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)

Page 6: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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

Stavanger, Norway (2011)

Page 7: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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)

Page 8: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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)

Page 9: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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 http://go6.si/RIPE501bis/

Stavanger, Norway (2011)

Page 10: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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)

Page 11: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

URLs, files, info…

• RIPE-501:http://www.ripe.net/ripe/docs/ripe-501

• Draft of replacement document: http://www.ripe.net/ripe/docs/other-documents/requirements-for-ipv6-in-ict-equipment

• Intermediate versions: http://go6.si/ripe501bis/

Stavanger, Norway (2011)

Page 12: Jan zorz procurement-ripe-501

Jan Žorž <[email protected]>

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 protected]@steffann.nl

[email protected], Norway (2011)