- dns-wg - mailman.ripe.net

reminder about the WG Chair appointment process
by Jim Reid 27 Nov '14

27 Nov '14

Colleagues, there's been very little response or discussion about the procedure which was proposed at the beginning of October. I think it's now time to start a "Last Call" on this. If anyone has any tweaks to he proposed text or counter proposals, please speak up now! It would be helpful if any changes are accompanied by suggested replacement text and an explanation. Simply saying "I don't like Clause Foo" is not helpful or productive: please say why you don't like that clause and provide replacement text. Since the PDP uses 4 weeks for its Last Call phase, let's do the same here. So if there are no changes or comments on the suggested text by the end of the year, it will be considered to be the agreed, final version of the procedure. [Well, until we revisit this in the future...] Assuming there is agreement on the final text by the end of the year, I will ask the WG for statements of support for that final text so that we can hopefully declare consensus early in the new year. The plan would then be for the procedure to start in good time for RIPE70. In case anyone cares, here's that proposed text again. # # $Id: appointment,v 1.6 2014/10/06 11:46:56 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. A co-chair cannot serve more than 2 consecutive terms. [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. [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 who is the subject of that consensus judgement. [7] Any appeal over a consensus decision will be heard by the RIPE Chair (or their deputy) whose decision shall be final.

4 8

New on RIPE Labs: The Resolvers We Use (by Geoff Huston)
by Mirjam Kuehne 26 Nov '14

26 Nov '14

Dear colleagues, For those who missed the plenary talk Geoff Huston gave on Monday during RIPE 69 ("The Resolvers We Use"), it is now published as an article on RIPE Labs: https://labs.ripe.net/Members/gih/the-resolvers-we-use Kind regards, Mirjam Kuehne RIPE NCC

1 0

Re: [dns-wg] RIPE NCC DNSSEC trust anchors
by Romeo Zwart 18 Nov '14

18 Nov '14

Dear Collegues, Our message from last Thursday (see https://www.ripe.net/ripe/mail/archives/dns-wg/2014-November/002981.html) has stirred a significant amount of discussion. Trying to summarize the responses on the mailing list, I came to the below list of topics: /1 Why does any zone under 62.in-addr.arpa have to be in the DLV? Since 62/8 is under RIPE NCC control, it can be properly signed. /2 Why does RIPE NCC still submit key material to the DLV? RIPE NCC should no longer endorse out-of-band mechanisms for key publication. /3 Discussion around the current use of ripe.int. /4 Discussion around the current use of ripen.cc. I will try to answer each of these point separately. 1/ While the RIPE NCC controls 62/8, the delegations under it are not necessarily under our control. Specifically the /24 mentioned in the original post is part of 62.76/16, which is delegated to the Russian Institute for Public Networks (RIPN). RIPN does not sign its zones, therefore we have been using an out of band mechanism. 2/ The RIPE NCC has been publishing this key material out of band for historical reasons. If there is a consensus in the WG that this is no longer needed, or even undesirable, we are happy to phase out the use of the DLV. 3/ RIPE NCC has been assigned ripe.int in the early 2000's. We are currently not using ripe.int, other than by redirecting to ripe.net. If the community advises the RIPE NCC to request IANA to sign .int, we can spend some effort on this, but we'd like to follow up on this separately. 4/ Ripen.cc is a historical artifact. RIPE NCC is not currently using it and we are not planning any future use. Releasing the domain is an operational decision that we may take in the future. Kind regards, Romeo Zwart RIPE NCC

18 34

RIPE NCC DNSSEC trust anchors
by Anand Buddhdev 14 Nov '14

14 Nov '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear colleagues, Most of the zones that the RIPE NCC signs with DNSSEC have trust anchors in their parent zones, with the exception of these three zones: 151.76.62.in-addr.arpa ripe.int ripen.cc We have been publishing trust anchors for these three zones on our website, as well as in the ISC DLV trust anchor repository (TAR): https://dlv.isc.org On Tuesday, 11 November 2014, we rolled our DNSSEC Key Signing Keys and added the new trust anchors for these three zones to the ISC DLV TAR. Because we believe manual configuration of trust anchors is very rare these days, we are taking this opportunity to stop publishing trust anchors for these three zones on our website. The trust anchors remain available via the ISC DLV TAR. Of course, as soon as we are able to publish DS records for these zones in their parents, we will do so and withdraw them from the ISC DLV TAR, as we have done for all our other zones. If you have any questions or concerns, please send email to dns(a)ripe.net. Regards, Anand Buddhdev Senior Engineer RIPE NCC -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlRkxj4ACgkQi+U8Q0SwlCvWtQCgiCxJt53Ala7tTYXzzXW6787w GPcAn0a/u+aRB8BlpTT5cp5QomFo/LSB =ZAsP -----END PGP SIGNATURE-----

14 25

Experiment proposal to improve K-root
by Romeo Zwart 29 Oct '14

29 Oct '14

Dear colleagues, We used RIPE Atlas to measure latency to K-root, and we believe we can improve average latency by adding new nodes to K-root in strategic locations. In a new RIPE Labs article, we propose performing an experiment that would let us measure this potential improvement. You can find the details, including the full measurement results, here: https://labs.ripe.net/Members/suzanne_taylor_muzzin/experiment-proposal-to-… As we define the experiment, we will publish more specific details about how many nodes we will add, in which locations, and what kind of improvement we might expect. If you have any feedback about these plans, please share your feedback on this list. Kind regards, Romeo Zwart Global Information Infrastructure Manager RIPE NCC

1 0

DNS-WG Draft agenda
by Jaap Akkerhuis 22 Oct '14

22 Oct '14

Apologies for the delay, but ICANN ate my homework and a disk crash didn't help either. Anyway, here is the draft agenda for the DNS-WG. jaap

1 0

time slot for RIPE NCC update
by Romeo Zwart 20 Oct '14

20 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 dear Chairs, As usual, we would like to have a time slot for a quick update from the RIPE NCC. Some 15 minutes would be sufficient. Anand will, as usual, present this. Also, are there any updates on the outstanding issues we have discussed on the list previously (the 'policy-statement' around ccTLD secondary; adding new zones to DNSMON and visualisation delay for DNSMON)? Discussion on these topics seems to have dried up a long time ago. It would be great if we can achieve formal closure on these during the coming meeting. Would it be useful to specifically schedule an agenda item to have the WG formalise their decisions? Kind regards, Romeo -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlRE5icACgkQGRL9suBV+er0zQCfdDZfzV7DCkAGXqYp+uC1nabY qD8AoIGmwV9pHuexvyLztjtr/vMsHKvn =v1VY -----END PGP SIGNATURE-----

1 0

heads-up on dec.com domain
by Nick Hilliard 11 Oct '14

11 Oct '14

folks, for those not already aware, control of the dec.com domain was transferred to an unknown third party a couple of weeks ago and is no longer owned by HP Inc, Hewlett-Packard Enterprise or anyone with prior responsibility to the remains of Digital Equipment Corporation. This means that the address records for the uucp-gw-{1,2}.pa.dec.com nameservers are controlled by an unknown third party. Most organisations migrated away from these host names many moons ago (including all but one cctld), but there are still some second-level domains out there who use these hosts for NS records. If any ccTLDs recognise this these host names in their zone files, the old farts still using them might appreciate a heads up on what's happened and what they need to do. Nick

5 4

proposal for appointment/removal of WG co-chairs
by Jim Reid 09 Oct '14

09 Oct '14

Colleagues, you may be aware that all RIPE Working Groups have been asked to devise and document a procedure for the selection of its Chairs. Some WGs have started to do that. Each WG is expected to come up with its own mechanism and decide on that themselves. My personal view is WGs are too different and the community is too diffuse for consensus to emerge on a "one size fits all" approach any time soon. Perhaps WGs will converge on a common approach in a few years in light of experience with whatever mechanisms get adopted in the coming months. However, that should not delay each WG deciding on a procedure and using it. And documenting it of course! With that in mind, here's a proposal for you to consider. The objective here is to have something simple and lightweight with the minimum of "rules" and "process". Feel free to disagree if you prefer something more elaborate. The key points in the draft are (a) the WG decides for itself how the WG gets run; (b) we work by consensus; (c) decisions are taken on the list; (d) there is an element of rotation. As well as the expected list discussion, there will be some time in the WG agenda for RIPE69 to discuss matters. The hope is the WG can reach consensus on an appointment/removal mechanism by the end of the year (ish) and the first run of the WG Chair beauty contest (swimsuit round optional) by RIPE70(ish) in 2015. Comments welcome. # # $Id: appointment,v 1.6 2014/10/06 11:46:56 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. A co-chair cannot serve more than 2 consecutive terms. [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. [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 who is the subject of that consensus judgement. [7] Any appeal over a consensus decision will be heard by the RIPE Chair (or their deputy) whose decision shall be final.

3 4

Call For Presentations RIPE 69, deadline 31 August 2014
by Benno Overeinder 25 Sep '14

25 Sep '14

Dear colleagues, Please find the CFP for RIPE 69 in London below. The deadline for submissions is 31 August 2014. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, RIPE PC http://www.ripe.net/ripe/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 69 will take place from 3-7 November 2014 in London, UK. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary session presentations, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 69. 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. The RIPE PC accepts proposals for different presentation formats, including plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. See the full descriptions of these formats at https://ripe69.ripe.net/submit-topic/presentation-formats/ Presenters who are proposing a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. In addition to presentations selected in advance for the plenary, the RIPE PC also offers several time slots for "lightning talks", which are selected immediately before or during the conference. The following general requirements apply: - Proposals for plenary session presentations, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 31 August 2014, using the meeting submission system at https://ripe69.ripe.net/submit-topic/guidelines/. Proposals submitted after this date will be considered on a space-available basis. - Lightning talks should also be submitted using the meeting submission system (https://ripe69.ripe.net/submit-topic/submission-form/) and can be submitted just days before the RIPE Meeting starts or even during the meeting week. The allocation of lightning talk slots will be announced in short notice – in some cases on the same day but often one day prior to the relevant session. - Presenters should indicate how much time they will require. See more information on time slot allocations per presentation format at https://ripe69.ripe.net/submit-topic/presentation-formats/. - Proposals for talks 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, it is expected that most, if not all, presenters/panellists will 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/

2 2