- dns-wg - mailman.ripe.net

RIPE NCC domain registrations
by Romeo Zwart 01 Jul '15

01 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, The RIPE NCC holds a number of domains besides ripe.net. Some of these domains were only registered as a "protection" mechanism, which was considered good practice at the time. We now plan to release the following domains, which are not being actively used by the RIPE NCC: 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 Depending on the registration expiration date of each of these domains, we will either let the domain expire or take steps to actively delete it. The following domains held by the RIPE NCC are still in use. We have no immediate plans to release any of these domains: ripe.net enumdata.org enog.org nro.net nro.org ipv6eyechart.net ipv6actnow.org ipv6actnow.com ipv6actnow.net Please let us know within two weeks if you have any comments or feedback about this process. Kind regards, Romeo Zwart -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVkovvAAoJEKnY9vIUvfudPR8P/0PEnpvz435gKM941vSf7j3U rqYcnBD54MQBiw8MaUA4Q+UTjw/DsHsFw/EISXt1EFITp2ACrLBesQbMWWtr/V3Q ylz1DRDiRI8JKWuKvoAbCKcdwpbeH6C3JhNl4wlSvmNUq47EFF7la24XvpiuyrBo 1vf8K9q0I9HfBixXbbqfipd0VGlvw9RKejpTRhUwJ90kR5VytvJMcR+COJlBr/83 q9EHrXmk8fZn8rp/pakygITSxny+psvaaJY9HxffQJM23iClSPz11kwGmFFvhYFf JIxDvzbVtYPZHpZCKK20UWisXcrQsu7XdVNV4zechKzf+H7kHR5O+ODGsKE6w91A G1bWOlqqC9jLDIaq8pTKLV1kwtyM/1Ng2ZA8yG9Xk1RHnKkDCVBLZiShyjbd/MWs xwdqs9JKXVwKjaIBJq5p64pR3i94rHdn9qepfNgXQ8bbtEy+xHtlBpLce0jMoHKA y87Z7a82NyZymose6xfPIdF+Jz6FqDKyOxk3MwjC9b3XeEGbh9WpvzvSCn1b7ZIx gD3fcFC7xgQxTqo898CiZjDrxSwE7MXG0rSfZ3jDH9prrPyK6L4MpMalISqW5vvK Vu6m/vQQSIb4qamc1BaGBtLCroEQJP94Cs3OvwEg4mAKpmysfn9ZMyxnjdsDHSsw YnZLUwD60vPiurov+Am0 =4MS6 -----END PGP SIGNATURE-----

9 12

Call for Presentations - DNS-OARC Fall Workshop, Oct 2015
by Sean Stuart 18 Jun '15

18 Jun '15

The next DNS-OARC Fall Workshop will take place in Montreal on Oct 3rd and 4th, the weekend before NANOG65. DNS-OARC is requesting proposals for presentations, with a preference for DNSSEC work. We are looking for the whole spectrum, from measurement work using passive and active techniques, to applications and potential new uses of DNSSEC. This workshop intends to build from previous strong DNS-OARC workshops, where operational content and research is welcome. Presentations from DNS operators are particularly welcome, as well as from DNS researchers. All DNS-related subjects are accepted, introduction to new tools, visualizations, data analysis, DNSSEC and novel uses of the DNS. If you are an DNS-OARC member, and have a sensitive topic you would like to present for members-only, we will accommodate those talks too. Time will be available for lighting talks to fit short presentations (5 to 10 minutes). Workshop Milestones 17 June 2015, Call for Presentations posted 17 June 2015, Open for submissions 30 July 2015, Deadline for submission 20 August 2015, Final Program published 1 October 2015, Final deadline for slideset submission Details for abstract submission will be published here: https://indico.dns-oarc.net/event/24/call-for-abstracts/ The workshop will be organized on different tracks, depending on the topics and the timing of each presentation. If you are interested in a lightning talk, let us know at the time of submission. You can contact the Programme Committee: https://www.dns-oarc.net/oarc/programme via <submissions(a)dns-oarc.net> if you have questions or concerns. Sean Stuart, for the DNS-OARC Programme Committee DNS-OARC is also seeking sponsorship for this workshop, please contact <sponsor(a)dns-oarc.net> if your organization is interested in becoming a sponsor. (Please note that DNS-OARC is run on a non-profit basis, and is not in a position to reimburse expenses or time for speakers at its meetings.) -- Sean Stuart Engineer, Resolution Operations sstuart(a)verisign.com m: +1-571-265-2148 t: +1-703-948-4204 12061 Bluemont Way, Reston, VA, 20190 VerisignInc.com <http://www.verisigninc.com/>

1 0

Improvements to the RIPE NCC DNS provisioning infrastructure
by Anand Buddhdev 02 Jun '15

02 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear colleagues, The RIPE NCC is improving the resiliency of our DNS infrastructure by introducing multiple provisioning and distribution servers. One of the services we provide is secondary DNS for large reverse DNS zones. LIRs request this by adding "ns.ripe.net" to the "nserver:" attribute of their domain objects. Our provisioning system then automatically configures the server ns.ripe.net as a secondary for the reverse zone in that domain object. However, ns.ripe.net is not a single physical server. It provides DNS service from several servers using BGP anycast. For this reason, we have separate hidden distribution servers. If you are using this service, you will need to update your configuration. You will need to change your DNS server access control lists, notify settings and firewall settings. Please allow the following two new name servers to transfer your reverse DNS zone(s): 193.0.19.190 / 2001:67c:2e8:11::c100:13be 93.175.159.250 / 2001:67c:2d7c:66::53 Additionally, if you would like ns.ripe.net to update promptly, then please send notify messages to the above four addresses. Note that any notify messages sent directly to the addresses of ns.ripe.net will not be seen. Also, we do NOT support any non-standard configurations (such as port numbers other than 53, TSIG keys and so on). Please update your configuration by 31 July 2015. This is the date when we’ll retire the old server. If you have any questions, please send an email to <dns(a)ripe.net> Regards, Anand Buddhdev RIPE NCC -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVbaqyAAoJEBXgoyUMySoFkcwP/iFoS32eGZYdmTkyGoKvFZgS 6bdIVZcUNZzE3KEbLj9mtLG4pZIdDrCtAkEgg+ZRGwElCjzzrxTXybQxziAOz/JJ Xy+FUpXyf2HpgQ0b6Zbu+Dx8lYbt++hVHD6NYSUrZgKZDVw4/nNE1b32XW63WUK3 Du4nou3JF8m5bOBG4qkLU4jPoQDuSr4pduOZ6LX7/Vilxfj4r12wgTED2hTCgaD/ +8vBmHVcxQPkYy+r8/ZG63raHIpTn8glEjb/ecAZJ9XGAgHGgS3nZkARKy0V80Yg HtBmEx6U3BksBYKq2iFiNZK1jYwD4yO9Jq66wgSpbH3Oqw9ocgiI4Q8VfqrevZC+ 98smPv60sKJAGj22yziscSWJESk3jWYYOrY1J+vVtqi777JbXw6vgIQUgki9+Udi V6qHNV0nRfjrPgyE9F9xdufZjrWMiNmiKffPa+LOSc15nTGFeY5A5FFW4fo+Up37 7qMvOpMML6tBJTbKVkG0uOPkQ/hzEoRgLnvvGiSvwG4uRie13MVk1nEVlnad1SKs c1UwsdhkVZ1qf4b7jlquB0rBkRn3KIZkuCE6TLSSI9BKZg4krX2A2CuvaC7cm+jn XIm/Kh4nyVg5wpqRP9eLkwneDD7aPmWKUDZ79GEdcRejg32Cmii22bGgcxa3gw1W JmMzYQFsa/UuDQI8nbJT =btiT -----END PGP SIGNATURE-----

1 0

K-root hosted nodes
by Romeo Zwart 13 May '15

13 May '15

Dear colleagues, Starting today, the RIPE NCC will accept requests from organisations interested in hosting a K-root node in their own networks. If your organisation is interested in hosting a node, you can find more information, including the technical requirements and details about the request process, online: http://k.root-servers.org/hosting More background information about these plans can be found in several RIPE Labs articles: https://labs.ripe.net/Members/kranjbar/future-of-ripe-ncc-technical-services https://labs.ripe.net/Members/romeo_zwart/k-root-expansion-plan https://labs.ripe.net/Members/romeo_zwart/new-architecture-for-k-root-local… As always, we welcome your feedback on these plans. Best regards, Romeo Zwart RIPE NCC

1 0

final DNS WG agenda for Wed & Thu
by Peter Koch 12 May '15

12 May '15

Dear WG, after some careful shifting and resizing, here's now the final agenda for our two DNS WG sessions on Wednesday and Thursday: ----------------------------------------------------------------------------- RIPE 70 DNS WG Wed 13 May 2015 09:00 - 10:30 ----------------------------------------------------------------------------- A Administrivia WG chairs B RIPE NCC report Anand Buddhdev, RIPE NCC C IETF report D Knot DNS 2.0 - status update - a new major version introducing updated DNSSEC Jan V#elák, CZ.NIC E Test cases for validating a DNS delegation - a step towards a best practice Sandoche Balakrichenan, Mats Dufberg F DNSSEC ECDSA algorithm use and acceptance Olafur Gudmundsson, Cloudflare G DLV sunset Jim Martin, ISC ----------------------------------------------------------------------------- RIPE 70 DNS WG Thu 14 May 2015 09:00 - 10:30 ----------------------------------------------------------------------------- H Knot Resolver - more thorough introduction Marek Vavru#a, CZ.NIC I Network-Tuning for DNS zone transfers in (lossy) Long Fat Networks Marco Prause, DENIC J Root Zone KSK Rollover Ed Lewis, ICANN K An enlightening talk N.N. Z Wrapup Chairs ----------------------------------------------------------------------------- -Peter

1 0

a final(?) co-chair selection process
by Jim Reid 09 May '15

09 May '15

Colleagues, here is what I hope could be a co-chair selection process that the WG can adopt. It's been tweaked to take account of recent feedback and should now be free of ambiguities. The most significant change is a new Clause 7: how to handle things whenever an unforseen situation arises. ie The WG will decide how best to handle these situations as and when they arise. This should hopefully avoid further rat-holing on hypothetical corner cases. Please remember this process is not etched in stone. It's not Holy Writ. It's supposed to be a "good enough" starting point. If later experience tells us that assessment is wrong or if a better mechanism happens to come along, the WG can of course apply its usual consensus based decision-making to change or replace whatever process is currently in use. Traffic on the list about this topic has been rather light and this has made it difficult to make an assessment on whether consensus has been reached or not. The WG needs to make a decision about this by RIPE70 - ie next week. With that in mind, your co-chairs have decided that silence implies consent. So unless there are substantive comments to the proposed text -- meaningful objections supported by an justification/explanation and replacement text -- the intention will be to adopt the proposed text at the WG meeting next week. Similarly, if anyone objects to this silence-implies-consent-approach or feels more time is needed, please speak up. Assuming the WG adopts this process, it will be invoked for the first time later this year, probably at or around RIPE71. # # $Id: appointment,v 1.9 2015/05/05 12:53:39 jim Exp $ # [1] The DNS WG will have N co-chairs. N will normally be 2 or 3, as determined by the WG. [2] A co-chair will serve a term of N years, where N is the number of co-chairs. Terms will be staggered so that one term expires every year. [3] The WG will be given adequate notice that a co-chair's term is ending and to invite applications for that position. Anyone can volunteer for appointment except that at the end of a second consecutive term, the outgoing co-chair may not do so. [4] At the end of a co-chair's term, the WG will decide by consensus who is appointed to the available co-chair position. In the event of a tie, the consensus tied candidates will draw lots. [5] The WG may decide by consensus to remove a WG co-chair at any time. [6] Consensus will be determined on the DNS WG mailing list. The consensus judgement will be made by the serving WG co-chair(s) and will exclude the co-chair(s) who is the subject of that consensus judgement. [7] Any issues relating to the selection or replacement of a co-chair which are not covered by the above will be decided by WG consensus. When the WG is unable to reach consensus, the matter will be referred to the RIPE Chair (or their deputy) whose decision shall be final. [8] Any appeal over a consensus decision will be heard by the RIPE Chair (or their deputy) whose decision shall be final.

3 3

RIPE Labs article: K-root expansion plans
by Romeo Zwart 23 Apr '15

23 Apr '15

Dear colleagues, The RIPE NCC is getting ready to expand the K-root network. We'd like to share more details about our expansion plans at this stage and look forward to hearing your feedback: https://labs.ripe.net/Members/romeo_zwart/k-root-expansion-plan We will start accepting requests for new K-root hosted nodes in mid-May. There will be a separate announcement about this during RIPE 70, which will have all details about the process for becoming a host. Best regards, Romeo Zwart RIPE NCC

1 0

Draft Agenda for DNS WG meeting at RIPE 70, Amsterdam
by Peter Koch 20 Mar '15

20 Mar '15

Dear DNS WG, the next RIPE meeting, RIPE 70 in Amsterdam, is eight weeks away. The DNS WG has a single slot on Thursday morning this time. Please find below the first draft agenda for our meeting. We are pretty much filling our assigned time already, but please do not hesitate to comment here or directly to your co-chairs at <dns-wg-chairs(a)ripe.net>. ----------------------------------------------------------------------------- RIPE 70 DNS WG 14 May 2015 09:00 - 10:30 ----------------------------------------------------------------------------- A Administrivia WG chairs B RIPE NCC report Anand Buddhdev, RIPE NCC C Reports from abroad (IETF, ICANN, OARC, ...) N.N. D Knot DNS 2.0 - status update - a new major version introducing updated DNSSEC Jan Vcelák, CZ.NIC E Knot Resolver - more thorough introduction Marek Vavrusa, CZ.NIC F Network-Tuning for DNS zone transfers in (lossy) Long Fat Networks Marco Prause, DENIC G DLV sunset Vicky Risk, ISC ----------------------------------------------------------------------------- Best regards, Peter

1 1

RIPE 70 draft programme and CFP 2nd deadline 12 april 2015
by Benno Overeinder 17 Mar '15

17 Mar '15

Dear colleagues, Following the past submission deadline, a Draft Programme for RIPE 70 is now published at: https://ripe70.ripe.net/programme/meeting-plan/draft-programme/ We will accept new proposals until 12 April 2015 for the remaining few slots. You can find the Call for Presentations and guidelines for submissions at: https://ripe70.ripe.net/submit-topic/cpf/ https://ripe70.ripe.net/submit-topic/guidelines/ Kind regards, Benno Overeinder RIPE PC -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

New on RIPE Labs: New Architecture Model for K-root Local Instances
by Mirjam Kuehne 13 Mar '15

13 Mar '15

Dear colleagues, We have redesigned the K-root architecture for our hosted nodes, formerly known as K-root local instances. System architecture and network setup have been simplified a lot. This will reduce our management effort for K-root and reduce costs for K-root hosts. More details on RIPE Labs: https://labs.ripe.net/Members/romeo_zwart/new-architecture-for-k-root-local… Kind regards, Mirjam Kuehne RIPE NCC

4 4