Re: [DNSOP] Informal meeting about root KSK futures at IETF 103

Steve Crocker <> Mon, 29 October 2018 22:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 8D25B131002 for <>; Mon, 29 Oct 2018 15:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QC_u9B6xv7Xa for <>; Mon, 29 Oct 2018 15:46:31 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::b2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 77DE01277CC for <>; Mon, 29 Oct 2018 15:46:31 -0700 (PDT)
Received: by with SMTP id v92-v6so4197717ybi.5 for <>; Mon, 29 Oct 2018 15:46:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=ZyjxZqgYHSV6h7+/1QLFQ9HsNcGVpqVdDPe0TVgNvmc=; b=WUbT+pmUz1GK6ugZuBWxmBvGtdPfic6X9AKr0BogTx7OB7RrToNe3h4CHLYYP53h9y HCdXE3VzUS9NZzrDwFpRu1UMb/VWNcoCBanLv5wHQlVSxD2PF8txKeNVWvKEAWJU3/mq vTADN3XeXx1681Ak+avvbJWbw82WzkRikRFy6HxBnAQc9PnxvwlN6Vl+vqJOdw6EBeif 5XXlrkT/R55wfxUNn/m/pbMeoUquuI2jy0Ul6K8/q+caI5GHBi/wNo+BwT1Z7MVHm7S0 9Zn3wfPdOuSQswGV5gT6Qn1K38/HYsFYvTuW24CC5mMLrWJMIGy2FnLbdhXOCwguaswp SCYA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=ZyjxZqgYHSV6h7+/1QLFQ9HsNcGVpqVdDPe0TVgNvmc=; b=AMMCZ+SgM4zLv8XUqwxHdPL6KWJ03NKckGMyIVXgHwxVHOBHvLFds85baFQjx5gcXu f7EEafXHhSoSJD8+wjBXnWzyPhDnD1zJUcRsMEbuRscwsQtIIJlTsrIscfIgxAMFYkqO cFcDz1Uo+vBFSK9oT4aP9f1m6hKqgY2d/UmwoaOlKJM9rKOtKZdyUTmrbcfwDGYOLRRx OP1t1VwVSlUBGoB6zZBAs2UX5O+8VqYh2O5CXTJvdU8xs2I0N+9Taa26wWoo6QWnfKjT OsQttThRJQTgdSfn6YiIorttDq0aba9tB1fPjjRczm/8fybBvzxXv81TKAruflGNCqsy +2LA==
X-Gm-Message-State: AGRZ1gI8OsUFsuE349Pq8hwUNRFQJs4b7080T+XwzqM+O7vc/RBT5LZB HjPBoFLJbGfn88ok5hBX/M+ijR4dqerXs0Yf+ICxhwu4
X-Google-Smtp-Source: AJdET5cMqywNmw7e7qfiYH5h0VkMiVP0EuGzJIS7K0DW1AqRIIji8s3Oumh9YmF5zDX+P0SFFFH9fbf11YNZ1xBXGNk=
X-Received: by 2002:a25:2d60:: with SMTP id s32-v6mr16350748ybe.471.1540853190187; Mon, 29 Oct 2018 15:46:30 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <>
In-Reply-To: <>
From: Steve Crocker <>
Date: Mon, 29 Oct 2018 18:46:19 -0400
Message-ID: <>
To: dnsop <>
Content-Type: multipart/alternative; boundary="0000000000000d8baa057965d77a"
Archived-At: <>
Subject: Re: [DNSOP] Informal meeting about root KSK futures at IETF 103
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 29 Oct 2018 22:46:35 -0000

I won't be in Bangkok, so I won't be able to participate.  In my view,
there were two specific problems that dominated the rollover problem.  The
first was the inability to determine the configuration of querying
resolver.  The second was the in ability to notify resolver operators if it
was evident their software was misconfigured.

Although these two problems became evident and important during the
rollover, they also apply more generally, so if the IETF is going to work
on improvements, it would be helpful if the improvements would be useful in
the event of other configuration or operational issues.  Ideally, every
resolver that issues a query would provide configuration information,
perhaps in a controlled fashion, and there should also be a way to notify
the resolver operator of operational problems.

We will need to do more rollovers in the future, driven at least in part by
the need to change algorithms.  I would hope we can work toward making
these relatively straightforward.



On Mon, Oct 29, 2018 at 12:36 PM Dave Lawrence <> wrote:

> Dave Lawrence writes:
> > Count me as another, for that very reason.  When I first saw Paul's
> > message I thought, "oh that's a shame" but figured it to be fairly
> > set.  If there's flexibility for making the meeting happen earlier in
> > the week, I'd be interested.
> Following up to my own message, since this was further down in my box
> on another list...
> ------- start of forwarded message (RFC 934 encapsulation) -------
> From: Paul Hoffman <>
> Subject: Re: [ksk-rollover] Informal meeting at IETF 103
> To: "" <>
> Based on some requests from folks who are leaving the IETF meeting
> early, I have also reserved a meeting room for 1600-1700 Wednesday
> afternoon (local time), Pagoda Room on the 4th floor.
> And just to emphasize: the purpose of this week's informal gatherings is
> to let folks in the IETF community chat about their ideas in front of
> other IETFers. This is similar to the KSK-related mic lines at the
> DNS-OARC and RIPE meetings a few weeks ago. These IETF side-meetings
> really are just slightly-better-organized hallway discussions. Given the
> wide range of proposals we have already heard, it is good to get a bit
> of face-to-face sharing going early.
> We won't start formal planning about the KSK futures until after the
> rollover process is complete*. When we do, we'll do it in discussion
> environments that are much more inclusive than these informal IETF
> side-meetings or the mic lines at other technical meetings.
> [...]
> ------- end -------
> _______________________________________________
> DNSOP mailing list