Wednesday, 16 May

Day three of RIPE 76 saw 686 attendees checked in for the first day of RIPE Working Group (WG) sessions.

Wednesday’s Programme Highlights

Address Policy WG

• Erik Bais was confirmed as the new Co-chair of the Address Policy WG
• An update on the ongoing consultation on the future of the ASO within ICANN
• A recap of how the Global Policy Development Process (GPDP) works
• An overview of open policy proposals in the five RIR service regions

DNS WG

• A presentation on NSEC Aggressive Caching Measurements covering DNSSEC security and performance with an explanation of aggressive cache versus random subdomain attacks
• A presentation on Measuring ATR (Additional Truncated Response), which is a hybrid response to problems around the handling of large UDP packets and IP fragmentation
• The importance of DNSSEC Key Rollovers when using DNSSEC and managing the complexity of DNSSEC operations

Connect WG

• MANRS for IXPs: an initiative to improve routing security
• Updates about the PeeringDB and IXPDB
• Will van Gulik was appointed as third Co-chair of the Connect WG

Address Policy WG II

• Feedback from the RIPE NCC’s Registration Services Department:
  • Should a waiting list be used after full IPv4 exhaustion?
  • What should be done with the very small final pieces of IPv4?
  • Is there enough IPv4 address space reserved for IXPs?

• Three policy proposal discussions:
  • 2018-01 Organisation-LIR Clarification in IPv6 Policy
  • 2018-02 Assignment Clarification in IPv6 Policy
  • 2018-03 Fixing Outdated Information in the IPv4 Policy
• In the Open Policy Hour, a discussion about removing IPv6 PI

DNS WG II

• DNS status report from the RIPE NCC: four new K-root instances online since RIPE 76. Dushabe K-root is online and was funded by the RIPE NCC Community Projects Fund
  • The RIPE NCC Executive Board has approved the proposal for a new 100G site
• Results from a survey on DNS privacy that showed 68% of respondents considered privacy important to their business and saw this as a positive marketing point
  • Biggest obstacle to enabling encryption is that products are not available, 70% skeptical about using hosted DNS privacy services

Database WG

• Update on the Registry Data Access Protocol (RDAP),  used to enable secure access to information such as that in the RIPE Database
  • Today this is used by the five FIRs and also by Domain Name Registries including .com and .net, and many ccTLDs
• Main concepts of the General Data Protection Regulation (GDPR) and how the RIPE NCC is implementing this for the RIPE Database
• A new approach that makes it easier to access information in the RIPE Database by not requiring specific skills and allowing common-language written queries.
  • A service is available for testing and feedback is being sought

RIPE NCC Services WG

• An update on the RIPE NCC Community Projects Fund
• An update on the RIPE NCC’s GDPR implementation
• The RIPE NCC’s Arbitration Procedure and an examination of the likely consequences if it is formalised
• An update from the IANA Review Committee on the services the RIRs are receiving from IANA/PTI

Favourite Tweets