- ipv6-wg - mailman.ripe.net

Version 6 of IPv6 prefix delegations BCOP is out
by Jan Zorz - Go6 15 Aug '17

15 Aug '17

Dear RIPE IPv6 WG, We received offline some good and valuable comments from MarcoH, addressed them and issued the version 6 of the document draft. https://sinog.si/docs/draft-IPv6pd-BCOP-v6.pdf Please, read and comment, if you think that we need to carry on with editing this document. If not, I would like to see if we can reach a consensus to move forward and ask RIPE staff to do the language check and publish this document as RIPE BCP. Any comments? Suggestions? For v6_pd_BCOP co-authors team, Jan Žorž

4 6

RIPE75 DCTM requirements ( small changes )
by Jetten Raymond 15 Aug '17

15 Aug '17

Hello IPv6 Working group! > ** NOTE FOR SPEAKERS[1] ** > > After Dubai had already been chosen as the location for the upcoming RIPE meeting, the authorities there (DTCM) have started to enforce some rules for conferences and speakers. All speakers (including remote speakers) will need to email the following information to meeting(a)ripe.net<mailto:meeting@ripe.net> before 15 September 2017): > > - Full name, title > - A colour copy of their passport > - A copy of their Emirates ID (if a UAE resident) > - Profile/bio for the speaker (at least 200 characters) > - Mobile number > - Email address > > This information will then be forwarded to the DTCM by the RIPE NCC. > > We realise that these requirements go beyond what was expected at previous meetings and that they may be a cause for concern for some people - especially the sharing of colour copies of passports. Unfortunately there is nothing we can do about this - we have to comply with local laws. If you do not wish to comply with these requirements then you will not be allowed to present on stage. You will still be able to join the discussions from the floor. > > [1] "Speakers" includes anyone who is presenting on stage - presenters, WG Chairs, and community members who are chairing or moderating sessions. This also includes policy proposers who are planning to present their policy. Attendees speaking at the microphones during the Q&A are explicitly not considered as speakers. The RIPE NCC has negotiated with the authorities in Dubai, and has some good news for us. It is now confirmed that a photocopy of speakers' passports is *not* required. Residents of the UAE are still required to upload a copy of their Emirates ID (in jpeg format). The information on https://ripe75.ripe.net/attend/dtcm-requirements/ has been updated. All attendees, and especially speakers, should take a look at that page to avoid surprises. Speakers will be asked to upload the above data via a secure webform provided by the RIPE NCC, who will then pass it on to the DTCM. The data will be permanently deleted from the RIPE NCC infrastructure one week after the RIPE 75 Meeting. Rgds, Ray, IPv6 working group Co-Chair

1 0

Same procedure as every year: Chair (Re-)election
by Benedikt Stockebrand 15 Aug '17

15 Aug '17

Hi IPv6 working group, looks like it's time we did a bit of paperwork... According to the "IPv6 WG Chair Selection Process"[1] it is time for one of us chairs to step down and possibly stand again for re-election. Jen and I fought it out (and what you'd expect, I lost:-) and it was decided that I'll step down---to stand for re-election---effective the next WG meeting in Dubai. With the way things have worked out, I'd be more than happy to serve another term as a WG chair. Cheers, Benedikt [1] https://www.ripe.net/participate/ripe/wg/ipv6/ipv6-wg-chair-selection-proce… -- 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/

3 2

IPv6 Prefix delegation BCOP version 3 is out...
by Jan Zorz - Go6 28 Jul '17

28 Jul '17

Dear RIPE IPv6 WG, After presentation at RIPE74 BCOP TF and IPv6 WG sessions we got some feedback from community over mailing list and while on stage and we addressed those comments as far as we could, resulting in version 3 of the IPv6 prefix delegations draft. To avoid sending around emails with attachment I'm providing the link where you can access the PDF file: https://www.sinog.si/docs/draft-IPv6pd-BCOP-v3.pdf I have a feeling that after all this cycles and comments from the community - we are reaching the point when we'll have to consider calling a consensus if possible, make it a stable RIPE BCOP document and give it a number. Please, read the latest version and see if you can agree with the current text and express your support (if agree) on this mailing list, so chairs can judge if there is enough consensus on the text to maybe go into a WG last call (or maybe even skip that if clear consensus, this is not PDP process ;) ) Cheers and thnx, Jan (on behalf of the co-authors of the document)

11 24

IMPORTANT: RIPE75 is SPECIAL (call for presentations)
by Jen Linkova 24 Jul '17

24 Jul '17

Dear IPv6 Enthusiasts, We are building the agenda for the next meeting, so if you'd like to present at IPv6 WG sessions at RIPE75 or have some ideas/suggestions for the agenda - please contact ipv6-wg-chairs(a)ripe.net. IMPORTANT: There is smth unusual about RIPE75 you should be aware of, especially if you are planning to present. Dubai's Department of Tourism and Commerce Marketing (DCTM) have special requirements for events. The more detailed information could be found below in the text format (and the .docx is attached for your reference), but the short summary is: 1) a final list of all speakers at RIPE 75 must be provided to the DCTM one month before the start of the meeting; 2) all speakers (including remote presenters) need to provide a colour copy of their passport and a short bio (min 2000 chars). What does it means for us? Obviously we need to finalize the agenda much earlier than usual. Also those requirements make it very hard (almost impossible) to add new talks at the very last moment or deal with speakers change. Therefore if you are considering to present but still hesitating it's better to let us (chairs) know and submit a talk tentatively. Sorry about hassle and we hope to see as many amazing talks submitted as usual, despite all those irritating inconvenience! ;) Additional info: ---- Department of Commerce and Tourism Marketing (DTCM) Permit General information The application of a UAE law applies to all events held in Dubai including the RIPE 75 meeting. Following this local law, all speakers and attendees must provide additional personal information to the DTCM in advance of the meeting. While the impact will be minimal for attendees, the requirement to have speakers’ passports and other information weeks ahead of the meeting will require the RIPE Meeting agenda to be finalised much earlier than usual, and with less room for last-minute agenda changes. What are the requirements of the law? 1. All RIPE 75 attendees (including RIPE NCC staff) will need to provide the following information: Full name Country of residence Date of birth Nationality Telephone number (mobile or landline) Email address This information will be collected through our usual registration form and will be passed to the event agency that acts on behalf of the government. The event agency will use attendees’ information to produce barcodes for each attendee. The meeting badge will include the barcode and barcode number. 2. All speakers (including remote speakers) will need to email the following information to meeting(a)ripe.net one month before the start of the meeting. We will forward this information to the DTCM: Full name, title A colour copy of their passport A copy of their Emirates ID (if a UAE resident) Profile/bio for the speaker (at least 200 characters) Mobile number Email According to the law, a speaker will be rejected if any false information is submitted and a new application must be submitted. What does this mean for the WG Chairs and PC? The agendas for all WG sessions should be finalised one month before RIPE 75 begins, so that all presenters have time to submit their information/passports. The WG Chairs will need to make people aware of this deadline in their calls for presentations and when soliciting presentations for the meeting. We suggest that panels be avoided as much as possible, as it might be challenging logistically to ensure that speakers send in their information in time. Another option (“loophole”) would be to have the panel participants contribute as “audience members” from the floor. Who counts as a speaker? Essentially, this includes anyone who is presenting on stage - plenary and WG presenters, panel participants, WG Chairs and PC members and community members who are chairing or moderating sessions. Not included in this definition is attendees who are speaking at the microphones during Q&A sessions. Why does the government require this information? How will the data be handled? The stated reason is to facilitate greater efficiency for event organisers and government entities that are responsible for granting permits. The data is used to conduct analysis, market research and examine industry trends. The data is not shared with other event organisers or ticket resellers/registration companies. We have also been told that the real reason is for security (to avoid anti-government or anti-religious speakers). The information on attendees is also used to get an accurate sense of how many attendees were at the meeting. We do not know how long they will keep the information supplied or how it will be handled. Telephone numbers/email addresses will not be checked. What are the penalties for non-compliance? A fee is paid to the government for each individual case of incorrect data submitted. The attendee is liable for this, not the RIPE NCC. However, the DTCM has said if we show good faith, they will be understanding. Regarding the speakers, the fine is 5-15,000 AUD in the case of non-compliance. The RIPE NCC would be liable for this. Are any people exempted from these requirements? There are some options for a limited number of people to be exempted, but this is intended for high-level government attendees only. -- SY, Jen Linkova aka Furry on behalf of RIPE IPv6 WG Chairs.

11 12

New on RIPE Labs: Local Packet Filtering with IPv6
by Mirjam Kuehne 13 Jul '17

13 Jul '17

Dear colleagues, Please read this new article by Enno Rey on RIPE Labs where he discusses local packet filtering of IPv6, which might depend on the address configuration strategy chosen for your respective systems: https://labs.ripe.net/Members/enno_rey/local-packet-filtering-with-ipv6 Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: Simplifying IPv6 Addressing for Customers - Part 1
by Mirjam Kuehne 11 Jul '17

11 Jul '17

Dear colleagues, One of the main issues when an ISP is planning to deliver IPv6 services is to decide how to address the customers. In this first of two articles Jordi Palet Martinez looks into one of the issues related to IPv6 addressing for customers: the value of “persistence”. https://labs.ripe.net/Members/jordipaletm/simplifying-ipv6-addressing-of-cu… Kind regards, Mirjam Kühne RIPE NCC

2 2

IPv6 operations discussions
by Lee Howard 16 Jun '17

16 Jun '17

The IETF v6ops working group is chartered to improve the operation of IPv6. We have several active documents right now that would benefit from broader operator feedback. For instance, there is current active discussion on: Requirements for IPv6 Routers <https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs> This document provides a list of requirements for operators’ routers. Is it clear and exhaustive? Basic Requirements for IPv6 Customer Edge Routers <https://tools.ietf.org/html/draft-ietf-v6ops-rfc7084-bis> What transition technologies should all CPE vendors put in their devices? The current version proposes all of: 464xlat, DS-Lite, lw4o6, MAP-E, MAP-T, 6in4, and 6rd, as well as IPv4 multicast over IPv6. There are related documents that split out some requirements for further discussion. Happy Eyeballs Version 2: Better Connectivity Using Concurrency <https://tools.ietf.org/html/draft-ietf-v6ops-rfc6555bis> Is this a useful update to the existing Happy Eyeballs specification (rfc6555)? Should we update Happy Eyeballs? Considerations For Using Unique Local Addresses <https://tools.ietf.org/html/draft-ietf-v6ops-ula-usage-considerations> Are ULAs useful, or are they a natural and risky predecessor to IPv6 NAT? It would help future IPv6 operations if current operators would read these documents and comment on them on the mailing list: https://www.ietf.org/mailman/listinfo/v6ops Note Well that comments become part of the IETF record, and thank you for them. Lee v6ops co-chair

1 0

New on RIPE Labs: Finding Open DNS Resolvers on IPv6
by Mirjam Kuehne 16 Jun '17

16 Jun '17

Dear colleagues, Please read this new article by Luuk Hendriks on how to find open DNS resolvers on IPv6: https://labs.ripe.net/Members/luuk_hendriks/finding-open-dns-resolvers-on-i… Kind regards, Mirjam Kühne RIPE NCC

1 0

New on RIPE Labs: What Stops IPv6 Traffic in a Dual-stack ISP?
by Mirjam Kuehne 14 Jun '17

14 Jun '17

Dear colleagues, Enric Pujol, network data analyst, is looking at barriers for dual-stack ISPs to carry IPv6 traffic: https://labs.ripe.net/Members/mirjam/what-stops-ipv6-traffic-in-a-dual-stac… Kind regards, Mirjam Kühne RIPE NCC

1 0