ipv6-wg

Download

ipv6-wg@ripe.net

April 2017

8 participants
2 discussions

New on RIPE Labs: IPv6 RIPEness Through the Years
by Mirjam Kuehne 13 Apr '17

13 Apr '17

Dear colleagues, In 2010, we introduced IPv6 RIPEness to recognise Local Internet Registries in the RIPE NCC service region that had begun deploying IPv6. Seven years later, we looked at how the IPv6 RIPEness level of the RIPE NCC membership evolved over time. Please find some interesting results on RIPE Labs: https://labs.ripe.net/Members/wilhelm/ipv6-ripeness-through-the-years Kind regards, Mirjam Kuhne RIPE NCC

1 0

IPv6 prefix delegation BCOP document available for comments and suggestions
by Jan Zorz - Go6 12 Apr '17

12 Apr '17

Dear RIPE IPv6 WG, As promised at last RIPE meeting in Madrid, we produced a first draft of "Best Current Operational Practice for operators: IPv6 prefix assignment for end-users - static (stable) or dynamic (non-stable) and what size to choose." The aim of this document is to document the best current operational practice on what size of IPv6 prefix ISPs should assign/delegate to their customers and should they delegate it in a stable, static way or should it change over time. Please find the PDF attached and also accessible at: https://www.sinog.si/docs/draft-IPv6pd-BCOP-v1.pdf We are submitting this document to RIPE IPv6 WG (here) to check the technical validity of the document and also get consensus on it. We are also submitting it to RIPE BCOP TF to check if this is a real best operational practice and get consensus on it there. Please, read the document and send back comments to this mailing list. All feedback is more than welcome. On behalf of co-authors, Jan Žorž P.S: This document is not intended to document what practices may be in future and what they might look like, but to reflect the best methods of implementing IPv6 at the time of publication. Updates to this document will be published to reflect changes in best current practices where there are developments in standards and implementations.

13 30