- ipv6-wg - mailman.ripe.net

[training] RIPE NCC Courses in Sofia, Bulgaria 16-17 April 2014
by Training Services 14 Mar '14

14 Mar '14

Dear Colleagues, The RIPE NCC Training Services Department invites you to register for our upcoming Training Courses in Sofia, Bulgaria: Course type: RIPE Database Training Course Date: Wednesday, 16 April 2014 Time: 09:00-17:30 Course type: IPv6 for LIRs Training Course Date: Thursday, 17 April 2014 Time: 09:00-17:30 How to register: ---------------- You can register up to two people from your LIR for each course by using the LIR Portal at: https://lirportal.ripe.net/training/courses Registration will close when maximum capacity is reached, so please register soon to ensure your attendance. The course is free of charge. We provide lunch and printed training materials. We do not cover any of your travel expenses or accommodation. We give all of our training courses in English. RIPE Database Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region. You can find more information about the course at: https://www.ripe.net/lir-services/training/courses/rdb IPv6 for LIRs Training Course: ------------------------------ You should attend this training course if you are part of the staff of a Local Internet Registry (LIR) in the RIPE NCC Service Region and if you: * Are thinking about deploying IPv6 in your organisation * Have been told you need to deploy IPv6 * Need to convince your manager that IPv6 needs to be deployed * Looked at an IPv6 address and thought it was too complicated to deploy in your network You can find more information about the course at: http://www.ripe.net/lir-services/training/courses/ipv6 If you have any questions, send an e-mail to <training(a)ripe.net>. Kind regards, RIPE NCC Training Services

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 11 Mar '14

11 Mar '14

Dear colleagues, We are pleased to announce the launch of new dates 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

Call for topics/ideas for RIPE 68 (Warsaw)
by Marco Hogewoning 06 Mar '14

06 Mar '14

Dear colleagues, It is that time of the year again that we need to start thinking about the agenda for our meeting. The 68th RIPE Meeting will be held in Warsaw from 12 to 16 May. The draft meeting plan has the IPv6 Working Group scheduled for 2 sessions on the morning of Thursday 15 May. Please let us know asap if you which to present something, discuss something or have any other things you would like to see included on the agenda. We especially would like to encourage people with operational experience in running IPv6 towards customers to consider sharing their experience and knowledge for the benefit of those operators who are still facing the challenges of IPv6 deployment. Submissions can be made to ipv6-wg-chair [at] ripe [dot] net Thank you and hope to meet you all in Warsaw, Marco, David and Shane The co-Chairs of the IPv6 Working Group

1 0

Fwd: [address-policy-wg] IPv6 PA/PI - restarting discussion after failed 2013-06 proposal
by Elvis Velea 04 Mar '14

04 Mar '14

Hi everyone, I am forwarding this message to the IPv6-WG as well as it involves changes that I/we may propose to make to the IPv6 Policy. Please join the discussion and comment; however, I would like to kindly ask you to send your replies to the AP-WG for the ease of collecting the feedback. cheers, elvis -------- Original Message -------- Subject: [address-policy-wg] IPv6 PA/PI - restarting discussion after failed 2013-06 proposal Date: Tue, 04 Mar 2014 02:50:52 +0100 From: Elvis Daniel Velea <elvis(a)v4escrow.net> Organization: V4Escrow, LLC To: Address Policy Working Group <address-policy-wg(a)ripe.net> Hi everyone, 2013-06 has failed to become policy and we all understand that it presented such big changes that it became too complex. I would like to restart that discussion and see what are the problems/failures of the IPv6 policies (both PI and PA) and come up with a proposal to fix these problems. I'd like to start with the first 4 problems that I have noticed: #1. In IPv4 a PI user can connect a customer to it's network or allow a customer to use a dedicated server using one IP address. This limitation had been extended to up to a /29 (in case redundant connections were offered - ie:VRRP) but most of the cases I have encountered were using either a /32 or a /30. Currently, the IPv6 policy states that the minimum a customer should use is a /64. And because the minimum per customer is a /64, when someone would actually use IPv6 PI for a customer, it would make an assignment of a subnet and violate the policy. I've heard of people using /128s for the servers of their customers and sharing the same vlan amongst multiple customers in the same /64. Others are just requesting a/48 PI and expect never to come back for more (therefore, could not care less about policies). Others just know that the RIPE NCC has no way to see if they sub-assign parts of the /48 PI, so they just request a /48 PI, promise never to sub-assign and later on, forget about the promise. Therefore, I propose that the first change we make to the IPv6 PI policy is that where a /64 could be used per customer (regardless of the service offered to that customer) only if it is registered properly in the RIPE Database. The change would allow PI users to sub-assign in IPv6, but only small (?) amounts of space and only if they actually register the assignment. #2. Second problem I've noticed is the fact that LIRs can receive /32s (and up to /29s) only by asking. On the other hand, if you do not want to become a RIPE NCC member or just can not, you are forced to use IPv6 - a /48. Additionally, this IPv6 PI can only be used for your own infrastructure and not to provide any service (other than SaaS) to your customers without violating the policy (see problem statement #1). One could request more than a /48 but it would need to demonstrate that it has two or more sites that have different routing policies or demonstrate that it has a need for more than 65K subnets. I would like to introduce the IPv6 PI ALLOCATION. This time, the PI allocation could be made to the PI user and the user could actually make assignments from it. The PI allocation would be just as large as the PA Allocation and the price for it would be no less than 50% of the membership fee (Off course, the fees can only be voted upon at the GM and the example is just purely theoretical). This would introduce that 'additional registry' which we never knew how to name during the discussions of 2013-06 and would allow PI users to request/receive a /29 from which they could make assignments. Everyone will say that /32 or /29 will become the new /48. Well, that may be true, on the other hand, it may be the price that could keep the number of large PI Allocations low. Additionally, we could add an arbitrary limit. For example, say that you can request an IPv6 PI Allocation only if you already have x hundred customers that will receive an assignment from you immediately. #3. Minimum assignment size The policy says that the minimum assignment size is a /64. However, the RIPE Database does not enforce this rule and I have seen /128s registered. for example: inet6num: 2001:b70:f000::/112 inet6num: 2001:820:0:1:1::1000/116 inet6num: 2a01:2f0f:ffff:ffff:100:1000::1/128 There are over 700 inet6num objects registered which are below a /64. If we take the policy literally, all these assignments currently violate the policy. Therefore, I think we should either change/remove the minimum assignment size or have the RIPE Database block the creation of any IPv6 assignment smaller than a /64. #4. fix utilisation and hd-ratio vs assignment size While the HD-ratio is being calculated in terms of /56s, the policy says (at point 5.4.1.) that the minimum assignment that can be made is a /64. Furthermore, as you can see above, /128s can be registered in the RIPE Database as well. If we will continue allowing the registration of less than /56 assignments, it will be difficult to almost impossible to the IPRAs to actually calculate what is the HD-ratio of an IPv6 allocation. While now it is too early to see additional IPv6 allocation requests, if we keep doing things as we've been doing for the past years, we will end up in a few years with a huge mess in the registry and the impossibility to calculate the HD-ratio without applying random procedures. A very simple and quick fix would be to say that if any prefix is registered, the whole /56 that includes the prefix is in use. But then, we may see people registering/using /128s from different /56s just to reach the HD-ratio for an additional allocation. Would that still be considered an efficient usage? An other option would be to change the HD-ratio calculation to the actual number of IP addresses used and consider all the IP addresses from an assignment used if correctly registered in the RIPE Database. Once we have worked out whether these 4 issues are indeed flaws in the policy or not and whether we want them fixed or not, I would like to hear your opinion in what else should be modified in the IPv6 policies. I will then collect all the feedback, probably present it at the next RIPE Meeting, and start to discuss an other approach/policy proposal to achieve what 2013-06 failed to achieve. cheers, elvis -- <http://v4escrow.net> Elvis Daniel Velea Chief Business Analyst Email: elvis(a)V4Escrow.net <mailto:elvis@v4escrow.net> US Phone: +1 (702) 475 5914 EU Phone: +3 (161) 458 1914 Recognised IPv4 Broker/Facilitator in: This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received this email in error, please notify the sender immediately and delete the original.Any other use of this email is strictly prohibited.

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 25 Feb '14

25 Feb '14

Dear colleagues, We are pleased to announce the launch of new dates 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

[training] RIPE NCC Training Courses April-June 2014
by Training Services 18 Feb '14

18 Feb '14

Dear Colleagues, Our training team travels the RIPE NCC service region to deliver training courses to our members without any additional cost. Over the next few months, we'll be in St. Julian's, Zagreb, Sofia, Brussels, Edinburgh, Tehran, Helsinki, Moscow, Kiel, Almaty, Reykjavik, Geneva. Visit the following page to register and to check which training courses we are giving in your area: https://lirportal.ripe.net/training/courses The RIPE NCC delivers the following training courses: - LIR Training Course - Database Training Course - IPv6 for LIRs Training Course - Routing Security Training Course - 3 day Deploying IPv6 Training Course (New) - DNSSec Training Course (New) For more information visit: https://www.ripe.net/lir-services/training/courses With kind regards, Rumy Spratley-Kanis Training Services Manager

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 11 Feb '14

11 Feb '14

Dear colleagues, We are pleased to announce the launch of new dates 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

Fwd: RACI @ RIPE 68 - Opportunity for Students and Researchers
by Marco Hogewoning 23 Jan '14

23 Jan '14

If you are or know somebody doing research that is somewhat Internet related (doesn’t have to be IPv6 :). RIPE NCC has again put a call out for applicants to the RACI programme. And I am sure that I can speak for my fellow chair that we are happy to consider any IPv6 related material for inclusion in our work group. MarcoH (in his role as co-chair of this working group) > Dear colleagues, > > The RIPE Academic Cooperation Initiative (RACI) is providing a number of > students and researchers the opportunity to participate at RIPE 68 in > Warsaw from 12-16 May. We are offering packages that include meeting > registration and paid travel and accommodation, and we are currently > seeking applications from across the RIPE NCC service region. > > We would like to ask for your assistance to raise awareness of the RACI > program. Many in the RIPE community have strong connections with > academic institutions, and we are keen to make those institutions and > their students aware of this great opportunity. > > RACI gives students and researchers the opportunity to present their > work in front of some the leading technical figures in the Internet > world, receive feedback on their research from experts and have their > work published on the RIPE Labs website for community feedback. The RACI > program also benefits the RIPE community by introducing newer members to > the community who can give interesting presentations at RIPE Meetings > that might not otherwise be seen. > > The initiative is coordinated with the RIPE Programme Committee to allow > the RACI participants to present their research, either during > plenary/working group sessions, or in lightning talks at other > designated sessions. > > Students and researchers may wish to present on any topic relevant to > the RIPE community, including (but not limited to): > > - Network measurement and analysis > - IPv6 deployment > - BGP routing > - Network security > - Internet governance > > Students and researchers who are interested in RACI sponsorship can fill > out the application form on the RIPE 68 webpages: > https://ripe68.ripe.net/programme/raci/application/ > > All applications must be received by Friday, 25 April 2014. Applicants > will be informed about the status of their application by Friday, 2 May > 2014. Any applications received after 25 April 2014 will be considered > for RACI at RIPE 69, to be held in London from 3-7 November 2014. > > More information on RACI is available at: > https://ripe68.ripe.net/programme/raci/ > > Best regards, > > The RACI Coordination Team > RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 20 Jan '14

20 Jan '14

Dear colleagues, We are pleased to announce the launch of new dates 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

RIPE 554 Errata Page
by Wilhelm Boeddinghaus 17 Jan '14

17 Jan '14

Dear colleagues, as shortly discussed in Dublin I suggest to set up an errata page for the RIPE 554 document. Errors have been found, and we cannot change anything in the document without getting a new RIPE document number. But having to many different versions of the document confuses our audience. A errata page would make it possible to document minor but important changes of the content of the document. If the group says "yes" we could ask RIPE to help with a page like this. It should be easily reachable from the download page of RIPE554. Kind regards, Wilhelm Boeddinghaus

15 33