- dns-wg - mailman.ripe.net

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

Call for input for the RIPE 70 DNS WG meeting
by Peter Koch 09 Feb '15

09 Feb '15

Dear WG, the meeting plan for RIPE 70 <https://ripe70.ripe.net/programme/meeting-plan/> in Amsterdam shows a 90 minute slot on Thursday (14 May) for the DNS WG. This is the usual call for input, presentations, suggestions for discussions. Please let me or us (== <dns-wg-chairs(a)ripe.net>) know what you'd like to present, share, or talk about. Our goal is to have a draft agenda ready by the end of February. Thanks, Peter

1 0

Call For Presentations RIPE 70, submission deadline 1 March 2015
by Benno Overeinder 13 Jan '15

13 Jan '15

Dear colleagues, Please find the CFP for RIPE 70 below. The deadline for submissions is 1 March 2015. 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 for the RIPE Programme Committee 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 70 will take place from 11-15 May 2015 in Amsterdam, The Netherlands. 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 70. 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://ripe70.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 1 March 2015, using the meeting submission system at https://ripe70.ripe.net/submit-topic/submission-form/. Proposals submitted after this date will be considered on a space-available basis. Important Dates regarding RIPE 70 can be found at: https://ripe70.ripe.net/programme/important-dates/ - Lightning talks should also be submitted using the meeting submission system (https://ripe70.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://ripe70.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/

1 0

yet another heave on the WG Chair selection procedure
by Jim Reid 11 Jan '15

11 Jan '15

Happy new year everyone. The list has been silent about the draft selection procedure. This means it's not possible to decide if there's a consensus or not so we can declare victory and move on. Sigh. Could I ask you all to review the proposal and comment on the list? One sticking point appears to be the "A co-chair cannot serve more than 2 consecutive terms." provision in [2]. Someone commented at the mike at RIPE69 that this was a good thing. One of your co-chairs says the opposite. Everyone else has not commented one way or the other. Result: stalemate. WGs are supposed to have adopted a selection process by now and have it up and running in good time for RIPE70. Our WG is lagging behind the others. So, could we please have some comments on the proposed procedure and try to get the WG to converge on a consensus? Thanks. It would be appreciated if people gave clear statements of support or objection. In the latter case, please explain why and suggest alternate text. Simply saying "I disagree" will not be constructive. Though it would of course help with the consensus determination. Here's the suggested process 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.

9 15

Solicitation for Statements of Interest regarding Root KSK Rollover
by KSK Rollover SOI 19 Dec '14

19 Dec '14

ICANN, as the IANA functions operator, in cooperation with Verisign as the Root Zone Maintainer and the National Telecommunications Information Administration (NTIA) as the Root Zone Administrator, together known as the Root Zone Management (RZM) partners, seek to develop a plan for rolling the DNS root zone key-signing key (KSK). The KSK is used to sign the root zone zone-signing key (ZSK), which in turn is used to DNSSEC-sign the Internet’s root zone. The Root Zone Partners are soliciting five to seven volunteers from the community to participate in a Design Team to develop the Root Zone KSK Rollover Plan (“The Plan”). These volunteers along with the RZM partners will form the Design Team to develop The Plan. Individuals interested in volunteering approximately 5 hours per week for the Design Team should consult the announcement: https://www.icann.org/en/system/files/files/ksk-soi-11dec14-en.pdf and submit their Statement of Interest to ksk-rollover-soi(a)icann.org no later than January 16, 2015.

4 6