September 2015 - dns-wg - mailman.ripe.net

Advance notice - H-root address change on December 1, 2015
by Kash, Howard M CIV USARMY RDECOM ARL (US) 16 Nov '15

16 Nov '15

This is advance notice that there is a scheduled change to the IP addresses for one of the authorities listed for the DNS root zone and the .ARPA TLD. The change is to H.ROOT-SERVERS.NET, which is administered by the U.S. Army Research Laboratory. The new IPv4 address for this authority is 198.97.190.53. The new IPv6 address for the authority is 2001:500:1::53. This change is anticipated to be implemented in the root zone on 1 December 2015, however the new addresses are operational now. They will replace the previous IP addresses of 128.63.2.53 and 2001:500:1::803f:235 (also previously known as AOS.BRL.MIL and AOS.ARL.ARMY.MIL). We encourage operators of DNS infrastructure to update any references to the old IP addresses and replace them with the new addresses. In particular, many DNS resolvers have a DNS root "hints" file. This should be updated with the new IP addresses. New hints files will be available at the following URLs once the change has been formally executed on December 1: http://www.internic.net/domain/named.root http://www.internic.net/domain/named.cache The old IPv4 address will continue to work for six months after the transition (until 1 June 2016), at which point it will be retired from service. The address will remain under the control of the Army Research Laboratory, never to be used again for DNS service. The old IPv6 address will continue to work indefinitely, but may ultimately be retired from service. Simultaneous to the retirement of the old address on June 1, 2016, the ASN for H-root will change from 13 to 1508. You can monitor the transition of queries to the new addresses at the following URL: http://h.root-servers.org/old_vs_new.html -- Howard Kash U.S. Army Research Laboratory

1 1

Last Call for presentations and Draft programme for RIPE 71
by Benno Overeinder 27 Sep '15

27 Sep '15

Colleagues, A list of currently accepted RIPE 71 presentations is now published at: https://ripe71.ripe.net/programme/ There are still few slots remaining for a final RIPE 71 programme and RIPE Programme Committee will accept new proposals until 11 October 2015. This is our last call for you to submit your proposals. You can find the CFP for RIPE 71 below, or at https://ripe71.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc ---------------------------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 71 will take place from 16-20 November 2015 in Bucharest, Romania. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 71. See the full descriptions of the different presentation formats, https://ripe71.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 11 October 2015. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe71.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe71.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

3 2

RIPE NCC domain registrations
by Romeo Zwart 17 Sep '15

17 Sep '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, We have completed the release of some currently unused domains. We informed you of these plans in June: <https://www.ripe.net/ripe/mail/archives/dns-wg/2015-June/003097.html> The deleted domains are: ripe-ncc.org ripe-ncc.com ripe-ncc.net ripencc.com ripencc.net ripencc.org ripelabs.net ripen.cc ripe.int ipv6roadshow.com ipv6roadshow.net ipv6roadshow.org We welcome any and all feedback from the community. Kind regards, Romeo Zwart -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJV+nYZAAoJEKnY9vIUvfudRnoQAJRUVW3f/OEyVQ0rTcQ7Xaj7 PReR2pDSDHdCYxdsOhYvLL99bhz/YAubCRNlSKPPggiYIVSEE7o16Mg0QljmLr9s S5Sclw7IaDlADesHr+hw9NG4Y4MRIq6QwFDGV7zrmm6AfRFnIkWsqIjrsMC15p1T 0Vtp+RWQT229EQsigywsjwy4gbJozex5aHfASYINya3Qzs50NFOExRv42B1aPYSm 9Nv/oY50HpZ7bIbLYXEQEZfLMs0ek8nbIkbpymqgAD642F32R54u4FUgU3eZIRpS HHLwGuNopoaX2m6wrRUSvn2CREEOwnuseWRF2fBQ/v0TaJRRRsU/igvrIJjV3kYr vJrT563uInSHImm3Zdv+cJU+XsUYO2WefoY+hBSrH68FQTT9CbnBQcbTfK1+9RAE UZezZ/P1kKI6Zs1UzaVIas1+dmjW1Z8cnLasilSEPGkSAb8iSjj3/+hBx74arNIz Y5uvpMs3pOJENE7JHcmGaRSN6jEZGc6pk30LLiE9+PGIJ4lxtAPkf4F3WHxU0+H7 fkUvzL+cMqdv68MLsfHJrUr/wu3yQswIb4bpknbpJRXXv+J7IpARQi8Srcx4hZSz esjuA79AoR3Tn1slsxY3sNXZCp5q6Cfu5V4H8PZi4YPIFtdr+d5ucwuSE3SlxKLH m9v2no6AXHYdMxqPFLmp =goAX -----END PGP SIGNATURE-----

2 1

New zones added to DNSMON (.is, .nu, .om, .ua)
by Vesna Manojlovic 04 Sep '15

04 Sep '15

Dear colleagues, We continue to receive requests to add new zones to the DNSMON service, and are currently waiting for guidelines regarding an official process for this from the DNS Working Group. In the meantime, we have decided to accept only those requests from ccTLDs from the RIPE NCC service region or from RIPE NCC members, and only if requested by the zone operator. Out of the 12 requests we’ve received so far, four zones met these criteria. These four zones have now been added to DNSMON: https://atlas.ripe.net/dnsmon/group/is https://atlas.ripe.net/dnsmon/group/nu https://atlas.ripe.net/dnsmon/group/om https://atlas.ripe.net/dnsmon/group/ua If you have any suggestion about the process, please join the discussion on this mailing list. For other questions, please contact us at atlas(a)ripe.net Kind regards, Vesna Manojlovic Manager of Measurements Community Building RIPE NCC

1 0

2nd Call for presentations RIPE 71
by Benno Overeinder 02 Sep '15

02 Sep '15

Colleagues, Please note the approaching deadline of 13 September 2015 for RIPE 71 plenary programme submissions. You can find the CFP for RIPE 71 below, or at https://ripe71.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc ---------------------------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 71 will take place from 16-20 November 2015 in Bucharest, Romania. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 71. See the full descriptions of the different presentation formats, https://ripe71.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 13 September 2015. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe71.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe71.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0