From drc at virtualized.org Wed Sep 3 03:11:36 2014 From: drc at virtualized.org (David Conrad) Date: Tue, 2 Sep 2014 18:11:36 -0700 Subject: [dns-wg] 127.0.53.53 in logs? Message-ID: Hi, I was wondering if any resolver operators were seeing 127.0.53.53 in log files. For anyone who isn?t aware, seeing that address would suggest a ?name collision? (see https://www.icann.org/resources/pages/name-collision-2013-12-06-en if you don?t know what that is). As currently over 300 new generic TLDs have been delegated and there was much ... ?discussion? about the risk associated with the delegation of those TLDs, I?d be interested in hearing about anything anyone is seeing related to ?name collision". Thanks, -drc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 496 bytes Desc: Message signed with OpenPGP using GPGMail URL: From bortzmeyer at nic.fr Wed Sep 3 09:36:00 2014 From: bortzmeyer at nic.fr (Stephane Bortzmeyer) Date: Wed, 3 Sep 2014 09:36:00 +0200 Subject: [dns-wg] 127.0.53.53 in logs? In-Reply-To: References: Message-ID: <20140903073600.GA13093@nic.fr> On Tue, Sep 02, 2014 at 06:11:36PM -0700, David Conrad wrote a message of 43 lines which said: > I was wondering if any resolver operators were seeing 127.0.53.53 in > log files. Most of it will probably be created by OARC members (or other researchers) testing the ICANN system with dig, drill or delv... > For anyone who isn?t aware, seeing that address would suggest a > ?name collision? No (see above). > there was much ... ?discussion? about the risk associated with the > delegation of those TLDs, No, not really, it's just FUD created by people who wanted to delay the new gTLDs, plus ICANN always eager to add new rules. From woody at pch.net Mon Sep 8 15:17:19 2014 From: woody at pch.net (Bill Woodcock) Date: Mon, 8 Sep 2014 06:17:19 -0700 Subject: [dns-wg] [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available In-Reply-To: <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> <532842DB.7000306@ripe.net> <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> Message-ID: <7240528F-AFA4-40F1-A7D9-FD7CA0BB5B0A@pch.net> Anything that can be done about the bad AS48294 probe, that doesn?t actually have IPv6 connectivity? Can you have it stop reporting its lack of IPv6 connectivity, or exclude it from results, or something? It makes it hard to see what?s going on in overview results, if it?s constantly adding to the floor of measurements it contributes to. Obviously, I?d prefer a generalized solution that applied to all such non-functional probes. Thanks. -Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: PastedGraphic-2.png Type: image/png Size: 1023088 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From robert at ripe.net Tue Sep 9 11:22:14 2014 From: robert at ripe.net (Robert Kisteleki) Date: Tue, 09 Sep 2014 11:22:14 +0200 Subject: [dns-wg] [ncc-services-wg] [dnsmon-user] The Beta Version of the New DNSMON is Now Available In-Reply-To: <7240528F-AFA4-40F1-A7D9-FD7CA0BB5B0A@pch.net> References: <77BC1167-29D6-45C1-B380-7C67A8B49621@ripe.net> <532842DB.7000306@ripe.net> <201403191049.s2JAnv8p001190@bela.nlnetlabs.nl> <7240528F-AFA4-40F1-A7D9-FD7CA0BB5B0A@pch.net> Message-ID: <540EC6C6.9000406@ripe.net> On 2014.09.08. 15:17, Bill Woodcock wrote: > > Anything that can be done about the bad AS48294 probe, that doesn?t actually > have IPv6 connectivity? Can you have it stop reporting its lack of IPv6 > connectivity, or exclude it from results, or something? It makes it hard to > see what?s going on in overview results, if it?s constantly adding to the > floor of measurements it contributes to. Obviously, I?d prefer a > generalized solution that applied to all such non-functional probes. > > Thanks. > > > -Bill Hello, (keeping only the DNS-WG in the address list) Even though we ask for stable IPv4+IPv6 connectivity from all Anchor hosts, reality is that some are more flaky than others. At the moment we don't have a clear policy on whether to remove these from DNSMON measurements, and if so, when. (Is an hour of non-working a good trigger? A day, a week, a month, a year? Should it be put back if it behaves again? Should the historic results be changed for the affected period by this removal?) In virtually all such cases we're in contact with the host to resolve the issue. As you can imagine, sometimes it takes time. What you can do now is exclude particular anchor from the visualisation (press shift in the server view). This only affects that view in the UI, and does not exclude that probe from the aggregate results. Regards, Robert From jim at rfc1035.com Fri Sep 12 12:21:08 2014 From: jim at rfc1035.com (Jim Reid) Date: Fri, 12 Sep 2014 11:21:08 +0100 Subject: [dns-wg] draft minutes from RIPE68 Message-ID: <79F9CFAE-EE3F-46D9-A781-DBF2D17B4053@rfc1035.com> Colleagues, here are the draft minutes from the last WG meeting. Please let me know of any errors or omissions. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: ripe68minutes Type: application/octet-stream Size: 16588 bytes Desc: not available URL: -------------- next part -------------- From jabley at hopcount.ca Tue Sep 16 17:09:33 2014 From: jabley at hopcount.ca (Joe Abley) Date: Tue, 16 Sep 2014 11:09:33 -0400 Subject: [dns-wg] Root Zone KSK Rollover Operations Workshop (save the date) Message-ID: Hi all, ICANN will facilitate an open, technical workshop to discuss operational plans for a future root zone KSK rollover, during the upcoming ICANN 51 meeting to be held in Los Angeles in October 2014. The workshop is intended for participants who have a technical, operational perspective and is an opportunity to explore potential options, operational considerations, and other aspects of rolling the root zone KSK. The workshop will be held on Thursday October 16, 2014 at the ICANN meeting venue in Los Angeles. This will be an open event, and remote participation will be available. More details including a tentative agenda, will be made available soon. If you are able to participate, please join the ksk-rollover mailing list at which will be used to coordinate this workshop, and to function as a venue for technical discussion as this work proceeds in the future. Regards, Joe & Roy & Jakob & Duane & Dan ad-hoc workshop coordinators From jaap at NLnetLabs.nl Wed Sep 24 00:05:21 2014 From: jaap at NLnetLabs.nl (Jaap Akkerhuis) Date: Wed, 24 Sep 2014 00:05:21 +0200 Subject: [dns-wg] RIPE 69 is coming! Send in your agenda items Message-ID: <201409232205.s8NM5Ldc003571@bela.nlnetlabs.nl> The subject is the Exec Summary. Yes, it is this time of the year again. Ripe is coming to town. We have a single slot reserved at on Thursday the 6th of November and like to see that filled with your contributions. There has been quite some turmoil in DNS land lately, from the policy stuff (iana transition) via gTLD outroll and various options to accomodate CDNs (ALIAS, ANAME etc in the apex) to root zone KSK rollover so I expect that there will be a lot to talk about. Therefore, send you proposals ASAP. jaap From benno at NLnetLabs.nl Wed Sep 24 23:34:46 2014 From: benno at NLnetLabs.nl (Benno Overeinder) Date: Wed, 24 Sep 2014 23:34:46 +0200 Subject: [dns-wg] Final Call For Presentations RIPE 69, deadline 1 October 2014 In-Reply-To: <53FDC1E9.7070104@NLnetLabs.nl> References: <53FDC1E9.7070104@NLnetLabs.nl> Message-ID: <542338F6.3020205@NLnetLabs.nl> Dear colleagues, Following the past submission deadline, there is a Draft RIPE Plenary programme published at: https://ripe69.ripe.net/programme/meeting-plan/plenary/ There are still slots remaining for the final RIPE 69 programme and RIPE Programme Committee will accept new proposals until 1 October 2014. This is a last call deadline if you wish to submit a proposal. Kind regards, Benno Overeinder for RIPE programme committee On 27/08/14 13:32, Benno Overeinder wrote: > 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/ From daniel.karrenberg at ripe.net Thu Sep 25 10:23:38 2014 From: daniel.karrenberg at ripe.net (Daniel Karrenberg) Date: Thu, 25 Sep 2014 10:23:38 +0200 Subject: [dns-wg] Final Call For Presentations RIPE 69, deadline 1 October 2014 In-Reply-To: <542338F6.3020205@NLnetLabs.nl> References: <53FDC1E9.7070104@NLnetLabs.nl> <542338F6.3020205@NLnetLabs.nl> Message-ID: <5423D10A.5000604@ripe.net> The correct link for the draft program is: https://ripe69.ripe.net/programme/meeting-plan/draft-programme/