After the authors broke the ‘Last Call’ in the RIPE IPv6 Working Group, the final consensus on the replacement of RIPE-501 with a new proposal was not reached. Since then we have done some work on revisions and changes which have been proposed meantime. Finally, the new version of the document draft is crafted and published here as first…
\n<\/p>\n
At November RIPE63 meeting in Vienna we were almost at the end of “WG Last Call”, but as twe received some important comments and suggestions from Jari Arkko (IETF Internet Area Director), Jouni Korhonen (DMM IETF WG Chair) and Eric Vyncke (Cisco , IPv6 security guru), we decided to ask IPv6 WG chairs to break the last call in order we could address all this very useful comments and suggestions and make new version even better.<\/p>\n
What have we changed? Jouni has made some technical corrections in the “Mobile Nodes” section, which is now called “Mobile Devices” – especially the Mandatory and optional requirements, some of the new RFC documents, and some new 3GPP specifications.<\/p>\n
Most of the debate in the community was on IPsec support. A new RFC on IPv6 requirements is that IPsec is now “optional” and not “Mandatory” (RFC 6434). RIPE IPv6 WG consensus was to follow this paper, bu we also added the following instruction about this matter to those who initiate the tenders:<\/p>\n
———– In the original IPv6 Node Requirements (RFC 4294) IPsec was listed as a ‘MUST’ implement to be standards compliant. The updated RFC (RFC 6434) changed IPsec to a ‘SHOULD’ implement. Reasons for the change are stated in this new RFC.<\/em><\/p>\n The RIPE IPv6 Working Group has extensively discussed whether to make IPsec support mandatory or optional. The most vocal constituents showed support for moving IPsec to the optional sections which is what is reflected in this document.<\/em><\/p>\n Organisations that use IPsec or expect to use it in the future should include the following in the mandatory section when initiating the tender:<\/em> The IPsec specification is now “optional”, but if the OSPF-v3 is demanded in router equipment, this becomes Mandatory, as required by RFC4552 – our specification requires clearly says: “If OSPF-v3 is Requested, the equipment Must comply with” Authentication \/ Confidentiality for OSPF-v3 [RFC4552]”<\/p>\n New, 7th version of the proposal replacement for RIPE-501is online<\/a>, see also http:\/\/go6.si\/ripe501bis\/<\/a><\/p>\n Jan \u017dor\u017e, Go6<\/p>","protected":false},"excerpt":{"rendered":" After the authors broke the ‘Last Call’ in the RIPE IPv6 Working Group, the final consensus on the replacement of RIPE-501 with a new proposal was not reached. Since then we have done some work on revisions and changes which have been proposed meantime. Finally, the new version of the document draft is crafted and […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_newsletter_tier_id":0,"jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[2459],"tags":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/ptA56-1mm","jetpack-related-posts":[{"id":4775,"url":"https:\/\/go6.si\/en\/2011\/10\/naslednja-verzija-ripe501-dokumenta-zadnji-fazi\/","url_meta":{"origin":5230,"position":0},"title":"(Slovensko) Naslednja verzija RIPE-501 dokumenta v zadnji fazi…","author":"JanZorz","date":"Wednesday October 12th, 2011","format":false,"excerpt":"Zadnja, popravljena verzija RIPE-501 dokumenta je sedaj tik pred \"Last Call\" v RIPE IPv6 Working Grupi. Sprememb je veliko, predvsem smo dokument poenostavili in ponudili samo eno opcijo (ali IPv6 Ready Logo certifikat ali pa spisek RFC-jev), dodali smo tudi specifikacijo za CPE, mobilne naprave in Load Balancerje. Za konec\u2026","rel":"","context":"In "RIPE-501"","block_context":{"text":"RIPE-501","link":"https:\/\/go6.si\/en\/category\/ripe-501\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4567,"url":"https:\/\/go6.si\/en\/2011\/07\/ripe501-meeting-veroni\/","url_meta":{"origin":5230,"position":1},"title":"(Slovensko) RIPE-501 meeting v Veroni","author":"JanZorz","date":"Monday July 4th, 2011","format":false,"excerpt":"Go6 gre v Verono, kjer se bomo dobili s Sander Steffannom, soavtorjem RIPE-501 na delovnem sestanku glede naslednje veryije RIPE-501 dokumenta... Nova verzija dokumenta bo dodala nekaj novosti, pustili smo samo eno opcijo namesto treh - sedaj je priporo\u010dilo zahtevati IPv6 Ready Logo certifikat, \u010de pa oprema ni bila podvr\u017eena\u2026","rel":"","context":"In "RIPE-501"","block_context":{"text":"RIPE-501","link":"https:\/\/go6.si\/en\/category\/ripe-501\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":5034,"url":"https:\/\/go6.si\/en\/2011\/12\/taiwan-gradi-svoj-nacionalni-ipv6-profil-na-osnovi-ripe501\/","url_meta":{"origin":5230,"position":2},"title":"(Slovensko) Taiwan gradi svoj nacionalni IPv6 profil na osnovi RIPE-501","author":"JanZorz","date":"Thursday December 22nd, 2011","format":false,"excerpt":"Nekaj dni nazaj smo avtorji RIPE-501 dobili iz Taiwana nekaj vpra\u0161anj oziroma komentarjev na novo verzijo RIPE-501 dokumenta, ki je sedaj v draft fazi in bo (upamo) kmalu v finalni fazi za sprejetje kot \"replacement\" za RIPE-501 dokument. Po nekaj iteracijah smo izvedeli, da so Tajvanci vzeli na\u0161e delo kot\u2026","rel":"","context":"In "ego trips"","block_context":{"text":"ego trips","link":"https:\/\/go6.si\/en\/category\/ego-trips\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4595,"url":"https:\/\/go6.si\/en\/2011\/07\/predlog-v2-dokumenta-ki-naj-bi-nasledil-ripe501-je-narejen\/","url_meta":{"origin":5230,"position":3},"title":"(Slovensko) Predlog v.2 dokumenta, ki naj bi nasledil RIPE-501 je narejen…","author":"JanZorz","date":"Thursday July 21st, 2011","format":false,"excerpt":"RIPE-501 je do\u017eivel velik uspeh tako doma kot tudi v tujini in uporabljajo ga v kar nekaj dr\u017eavah kot osnovne smernice in \"template\", kako zahtevati IPv6 ko nakupujejo opremo. Zaradi tega uspeha je veliko povpra\u0161evanje po naslednji verziji, ki naj bi dokument \u0161e poenostavila ter dodala specifikacije, ki manjkajo... Kot\u2026","rel":"","context":"In "RIPE-501"","block_context":{"text":"RIPE-501","link":"https:\/\/go6.si\/en\/category\/ripe-501\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4533,"url":"https:\/\/go6.si\/en\/2011\/06\/cisco-je-javnost-dal-ripe501-position-paper\/","url_meta":{"origin":5230,"position":4},"title":"(Slovensko) Cisco je v javnost dal “RIPE-501 position paper”","author":"JanZorz","date":"Friday June 17th, 2011","format":false,"excerpt":"Cisco je na svojih spletnih straneh objavil dokument, v katerem se je opredelil do na\u0161ega \"procurement\" dokumenta, ki nosi ime RIPE-501 in je uradni \"best current practice\" v RIPE regiji kako specificirati zahteve za IPv6 podporo ko kupujemo opremo za na\u0161e podjetje... V svojem sporo\u010dilu podjetje Cisco izra\u017ea popolno podporo\u2026","rel":"","context":"In "RIPE-501"","block_context":{"text":"RIPE-501","link":"https:\/\/go6.si\/en\/category\/ripe-501\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3757,"url":"https:\/\/go6.si\/en\/2010\/11\/ripe-501\/","url_meta":{"origin":5230,"position":5},"title":"(Slovensko) Na\u0161 dokument s spiskom IPv6 zahtev v IKT opremi postal uradno RIPE priporo\u010dilo.","author":"JanZorz","date":"Monday November 29th, 2010","format":false,"excerpt":"Malce pozno, a vendar - na\u0161 predlog dokumenta, ki definira IPv6 zahteve pri nabavi IKT opreme na razpisih (in tudi druga\u010de) je dobil mednarodni epilog - RIPE je prepoznal konsenz znotraj tehni\u010dne in operaterske internetne skupnosti in na\u0161 predlog objavil kot uradno priporo\u010dilo s \u0161tevilko RIPE-501... Zgodovina tega dokumenta je\u2026","rel":"","context":"In "IPv6 cooperation"","block_context":{"text":"IPv6 cooperation","link":"https:\/\/go6.si\/en\/category\/ipv6-cooperation\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/posts\/5230"}],"collection":[{"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/comments?post=5230"}],"version-history":[{"count":0,"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/posts\/5230\/revisions"}],"wp:attachment":[{"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/media?parent=5230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/categories?post=5230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/go6.si\/en\/wp-json\/wp\/v2\/tags?post=5230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nIPsec: Mandatory or Optional<\/strong><\/em><\/p>\n
\n \u2022 IPsec-v3 [RFC4301, RFC4303, RFC4302] *<\/em>
\n \u2022 IKE version 2 (IKEv2) [RFC5996 (obsoletes RFC4306), RFC4718] *<\/em>
\n \u2022 ISAKMP [RFC2407, RFC2408, RFC2409]<\/em>
\n—————<\/p>\n