January 2015 - ipv6-wg - mailman.ripe.net

[training] RIPE NCC Webinars
by Training Services 26 Jan '15

26 Jan '15

Dear colleagues, The RIPE NCC Training Services Department invites you to register for our Webinars. The RIPE NCC Webinars are live and take only one hour. You can interact with our trainers without leaving your desk. We focus on the topics and issues most important for LIRs. Register now at https://www.ripe.net/lir-services/training/e-learning/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Services

1 0

Last Call: "IPv6 Troubleshooting for Residential ISP Helpdesks"
by Jen Linkova 21 Jan '15

21 Jan '15

Hello, At IPv6 WG session in London, we discussed the most recent version of the "IPv6 Troubleshooting for Residential ISP Helpdesks" document. The proposed plan of action was to reach the consensus on the technical details of the document and then publish it (as combined IPv6 WG and BCOP TF effort). This email announces the working group last call for the "IPv6 Troubleshooting for Residential ISP Helpdesks" document. Please read the most recent version of it: https://www.ripe.net/ripe/groups/tf/bcop/ipv6-troubleshooting-for-residenti… and provide your comments to the list *until 23:59 Fri Dec 19th 2014*. Thanks! -- SY, Jen Linkova aka Furry

3 3

New on RIPE Labs: IPv4 and IPv6 Tweets on a Map
by Mirjam Kuehne 21 Jan '15

21 Jan '15

Dear colleagues, We looked at tweets mentioning IPv4 and IPv6 and how they appear on a map over time. It's great to see that IPv6-related tweets are more popular. Find more information on RIPE Labs: https://labs.ripe.net/Members/emileaben/visualising-ipv4-ipv6-tweets If you have any questions or suggestions, please let us know. Kind regards, Mirjam Kuehne RIPE NCC

3 2

Call for Presentations
by Benedikt Stockebrand 18 Jan '15

18 Jan '15

Hi folks, since the call for presentations for the plenary sessions of RIPE 70 on May 18--22 in Amsterdam (https://ripe69.ripe.net) is already out (see https://ripe70.ripe.net/submit-topic/submission-form/) we'd like to ask anyone interested in doing "anything" (presentation or whatever else, I'll just write "presentation" from here on) during the working group session to send us your proposal. A couple of notes about the procedure: - There is no formal submission mechanism as with the plenary/program committee. Just drop a mail to ipv6-wg-chairs(a)ripe.net and if we have any questions we'll contact you. - We're interested in pretty much anything related to IPv6, including deployment, operation, further development and whatever you think might be of interest to the working group. - If you're unsure about proposing your presentation to the plenary or the IPv6 working group, I suggest you submit it to the plenary through the link mentioned above and send us an e-mail in parallel; that way we have a better chance to make sure that topics too esoteric for the plenary may actually find their niche in the working group, rather than being lost forever. - What we do need are: - Your name and (at least) e-mail address - The (preliminary) title of your presentation - A (preliminary) abstract (a paragraph or two) - A short bio of yours - The time you roughly expect to need <=== IMPORTANT:-) - Whatever questions you have - We need to have an idea how much time we need for the working group session, so we can request an additional time slot from the NCC if needed. So please, send us at least a preliminary draft as soon as possible; you can always polish your proposal up afterwards. - And, as Filiz pointed out in the call for presentations for the plenary: "Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings." Cheers, Benedikt (with blessings from Jen and Dave) -- Benedikt Stockebrand, Stepladder IT Training+Consulting Dipl.-Inform. http://www.stepladder-it.com/ Business Grade IPv6 --- Consulting, Training, Projects BIVBlog---Benedikt's IT Video Blog: http://www.stepladder-it.com/bivblog/

1 0

IPv6 survey (JANOG 35 IPv6 session)
by MAWATARI Masataka 09 Jan '15

09 Jan '15

Hi all, JANOG will have a session "Why don't we want to deploy IPv6?" in JANOG 35 meeting next month. It will focus on IPv6 deployment of the contents providers in Japan. To help us make this session better, we carry out a questionnaire survey to the service providers. It would be great if you could fill out the following form: https://www.janog.gr.jp/meeting/janog35/program/ipv6/ipv6_form_en/ Your co-operation will be appreciated. We will make a good use out of the survey information in order to improve this session. We'll update you with more details about JANOG 35 meeting through the following page. http://www.janog.gr.jp/en/index.php?JANOG35_Meeting Happy Holidays! -- Japan Internet Exchange MAWATARI Masataka <mawatari(a)jpix.ad.jp>

1 2

We suggest that RIPE-554bis CPE equipment requires RFC 7084 and CE-Router Logo. Thank you!
by 邱萬德 09 Jan '15

09 Jan '15

Hello Sir: We suggest that RIPE-554bis CPE equipment requires RFC 7084 and CE-Router Logo. (https://www.ipv6ready.org/?page=documents&tag=phase-2-cpe ) CE-Router Logo are developed by US UNH-IOL, CableLab and Taiwan CHT-TL. CE-Router Logo Conformance Test Software is developed by CHT-TL IPv6 Testing Lab. The URL is as follows: http://interop.ipv6.org.tw/CERouter/ Thank you very much! Best Regards, Wan-Der Chiou@CHT-TL IPv6 Testing Lab. http://interop.ipv6.org.tw/English/index.php Requirements for CPE equipment Mandatory support: · RFC6204 (Basic Requirements for IPv6 Customer Edge Routers) * => RFC7084 and requires CE-Router Logo [../images/IPv6_CE_Router1.png] Please be advised that this email message (including any attachments) contains confidential information and may be legally privileged. If you are not the intended recipient, please destroy this message and all attachments from your system and do not further collect, process, or use them. Chunghwa Telecom and all its subsidiaries and associated companies shall not be liable for the improper or incomplete transmission of the information contained in this email nor for any delay in its receipt or damage to your system. If you are the intended recipient, please protect the confidential and/or personal information contained in this email with due care. Any unauthorized use, disclosure or distribution of this message in whole or in part is strictly prohibited. Also, please self-inspect attachments and hyperlinks contained in this email to ensure the information security and to protect personal information.

7 10