<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I second/third Daniels suggestions that we stop crying about the horse that bolted the stable long ago, its just a waste of time and bandwidth, yes we really could do with having some mechanism to stop the “scammers” from just setting up as many LIR’s as they can but i can’t help but think that no matter what avenue you take its going to hurt the genuine person needing space and not solve the problem of the grey/black market of IP trading, so why fix a broken system with yet another broken system when the answer is very clear...<div class=""><br class=""></div><div class="">IPv6 take up and deployment to the consumer is quite frankly poor, especially when we have known about this problem for 20+ years now i certainly think RIPE’s budget for IPv6 training, evangelism etc needs to be far higher. we need to be doing whatever we can to encourage and push for wider adoption of IPv6 - including lobbying the CPE vendors and core networking vendors to make sure there kit is A grade standard for IPv6 support, yes the core networking kit side is generally fine these days but CPE support can be quite shockingly poor and the vendors need to be taken to task on it.</div><div class=""><br class=""></div><div class="">i do second the idea of RIPE run or RIPE supported tunnel end points for transitional purposes and other initiatives that will encourage IPv6 adoption</div><div class=""><br class=""></div><div class=""><br class=""><div class=""> <div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><p class=""><span style="font-family: arial, helvetica, sans-serif; color: rgb(51, 51, 51);" class="">Anthony Somerset,<br class="">Technical Director,</span></p><p class=""><img src="http://cloudunboxed.net/img/email-logo.png" alt="Cloud Unboxed Limited" border="0" width="220" class=""></p><p class=""><span style="font-family: arial, helvetica, sans-serif; color: rgb(51, 51, 51);" class=""><strong class=""><span style="color: rgb(0, 0, 0);" class="">w:</span></strong><span class="Apple-converted-space"> </span><span style="color: rgb(51, 102, 255);" class=""><a title="www.cloudunboxed.net" href="http://www.cloudunboxed.net" class=""><span style="color: rgb(51, 102, 255);" class="">cloudunboxed.net</span></a></span><span class="Apple-converted-space"> </span>|<span class="Apple-converted-space"> </span><strong class=""><span style="color: rgb(0, 0, 0);" class="">e: </span></strong> </span><a href="mailto:anthony.somerset@cloudunboxed.net" class=""><span style="color: rgb(51, 102, 255);" class="">anthony.somerset@cloudunboxed.net</span></a><span style="font-family: arial, helvetica, sans-serif; color: rgb(51, 51, 51);" class=""> |<span class="Apple-converted-space"> </span><strong class=""><span style="color: rgb(0, 0, 0);" class="">t:</span></strong><span class="Apple-converted-space"> </span>+44 (0)33 0088 2444</span></p><p class=""><span style="font-family: arial, helvetica, sans-serif; color: rgb(0, 128, 0);" class="">Please consider the environment before printing this e-mail.</span></p><p class=""><em class=""><span style="font-family: arial, helvetica, sans-serif; color: rgb(128, 128, 128);" class="">This e-mail and any attachments are confidential and intended for the addressed individual or entity only. If you have received this e-mail in error, please notify the sender immediately and then discard this e-mail. Unauthorized copying, sharing and distributing of this e-mail is prohibited. The content in this e-mail does not necessarily represent the views of the company. The addressee should check all attachments for malware; the company makes no representation as regards the absence of<span class="Apple-converted-space"> </span> malware in attachments to this e-mail.</span></em></p></div> </div> <br class=""><div><blockquote type="cite" class=""><div class="">On 22 Sep,2016, at 20:16, Daniel Pearson <<a href="mailto:daniel@privatesystems.net" class="">daniel@privatesystems.net</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Nigel,<br class=""><br class="">Thanks for the information. I've read a lot of the plan and have a couple of questions if you feel inclined to provide some more insight.<br class=""><br class="">According to what I can see, the budget is split into several parts for training. A general 'overall' training budget and then a much smaller budget for IPv6 Support. Based on this document in particular, it's hard to say exactly how much of the larger training budget is spent specifically on IPv6, but it does show that the dedicated "IPv6 Support" budget is quite small, roughly 171,000 EUR.<br class=""><br class="">It seems primarily tied to MENOG sponsored IPv6 Roadshows. The rest seems split into the ENOG region, mostly with past efforts being to cross train folks with the idea that they will help present more road shows.<br class=""><br class="">The final split in the budget is the online resources for IPv6.<br class=""><br class="">Can you say how much of the training budget applies to IPv6 in general?<br class=""><br class="">Any plans to expand the IPv6 roadshows outside of ENOG and MENOG?<br class=""><br class="">My personal opinion is the budget of 171,000 EUR for IPv6 Support, for the size of RIPE, is quite small. I would be interested to see that increased quite a bit to allow for more online resources, training, webinars and potentially even access to professionals that, while not providing support per say, could help guide folks unfamiliar with some of the IPv6 pitfalls in the right direction.<br class=""><br class="">Daniel~<br class=""><br class="">On 09/22/2016 12:47 PM, Nigel Titley wrote:<br class=""><blockquote type="cite" class="">Daniel (and others)<br class=""><br class="">On 22/09/16 18:32, Daniel Pearson wrote:<br class=""><blockquote type="cite" class="">Tim,<br class=""><br class="">I would say you get a gold star for recommending something feasible and<br class="">realistic. RIPE already had a budget excess of over 5 Mil EUR last year.<br class="">I would not be opposed if RIPE was tasked with creating a department to<br class="">help with IPv6 education through programs like that.<br class=""></blockquote>Could I respectfully suggest that you take a look at the RIPE NCC<br class="">activity plan which tells you exactly on what and how much the RIPE NCC<br class="">is planning to spend next year. It already spends a lot on outreach and<br class="">it continues to spend a lot on IPv6 education. It's been doing this for<br class="">many, many years. Start by looking at last year's plan, this year's will<br class="">be out very soon.<br class=""><br class="">Have a look and comment on it.<br class=""><br class="">All the best<br class=""><br class="">Nigel<br class="">Chairman RIPE NCC Board<br class=""><br class="">----<br class="">If you don't want to receive emails from the RIPE NCC members-discuss<br class="">mailing list, please log in to your LIR Portal account and go to the general page:<br class=""><a href="https://lirportal.ripe.net/general/" class="">https://lirportal.ripe.net/general/</a><br class=""><br class="">Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.<br class=""></blockquote><br class=""><br class=""><br class="">----<br class="">If you don't want to receive emails from the RIPE NCC members-discuss<br class="">mailing list, please log in to your LIR Portal account and go to the general page:<br class=""><a href="https://lirportal.ripe.net/general/" class="">https://lirportal.ripe.net/general/</a><br class=""><br class="">Click on "Edit my LIR details", under "Subscribed Mailing Lists". From here, you can add or remove addresses.<br class=""></div></div></blockquote></div><br class=""></div></body></html>