Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-kskroll-sentinel

Joe Abley <> Fri, 06 April 2018 14:00 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BD0F81201FA for <>; Fri, 6 Apr 2018 07:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Uyg3em-5elw0 for <>; Fri, 6 Apr 2018 07:00:33 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4010:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 574C51200FC for <>; Fri, 6 Apr 2018 07:00:33 -0700 (PDT)
Received: by with SMTP id z143-v6so700410lff.3 for <>; Fri, 06 Apr 2018 07:00:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=from:mime-version:references:in-reply-to:date:message-id:subject:to :cc; bh=kyHGktlCnAp70UTmV+4a+R+ZTze37c4Y+NN/3RZv2E4=; b=jVsGPYZfF6FsVjwmK7YKOJO7EaT8qPJxhh04rGKjp/PFTa9EMRhGZGPQfPZIAb6RsY fQ7oZhXXbEETKwYhql7eJfEjuMovZFvPQ1IDgLqt6UkdsPS6J3+F7Dd4Chstxx7EnF0G HISItfHiWSGUSILr4b3XEd9OBbJMFIwzZiL9s=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:from:mime-version:references:in-reply-to:date :message-id:subject:to:cc; bh=kyHGktlCnAp70UTmV+4a+R+ZTze37c4Y+NN/3RZv2E4=; b=bA0wi1iKDPp50GazUfWz+SEjJLFJyhtkXqKdG6Rtz9tRIXZcV29EJhZDqTMIHsXsll 6+12JYyQJzK9M/r8GSo9v1BCHzxXlfbV2fdt9eb1lVc37yfD/pkm1FA0QrgsQQZWNxYJ bj4Py/OShwK2GXrzhg9dZwt3HgSMTM198IvsIzR0YKmqJkYzEcblgyDViYY2TwFrwRtw FBMLElAn/yqn6Ry+RdX98Otuti9HRlQ2hp0FAixVKVPiOLel3Po0Es9ZFgSE+2cBSdah P6oNbZX5LENVXHFj5/eBAow/zXxEYZM4p3N+exeGN7wKIruhiQZ40f7tvVuYM+AiWQiR ZWqw==
X-Gm-Message-State: ALQs6tAroLxRAM4xPCsxJaoL1s25IyrLWR+EDO2uilGgWLKZ4zxEWus0 emLDjhC4wxN5bxNbqhIKyI9d24K6wDEqCskxO7yVGw==
X-Google-Smtp-Source: AIpwx48kHDNtl3WXs/GdETDGapfpcRp/asDoJYE6I9FRqZhPOFtExIQtuzbyitrc6C3cRGu8oDfDIeVk6Ci4qOhu0O4=
X-Received: by with SMTP id m21mr16511331ljj.31.1523023231510; Fri, 06 Apr 2018 07:00:31 -0700 (PDT)
Received: from unknown named unknown by with HTTPREST; Fri, 6 Apr 2018 07:00:30 -0700
From: Joe Abley <>
Mime-Version: 1.0 (1.0)
References: <> <> <> <>
In-Reply-To: <>
Date: Fri, 6 Apr 2018 07:00:30 -0700
Message-ID: <>
To: Job Snijders <>
Cc: Warren Kumari <>, tjw ietf <>, dnsop <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [DNSOP] Working Group Last Call for: draft-ietf-dnsop-kskroll-sentinel
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 06 Apr 2018 14:00:36 -0000

On Apr 6, 2018, at 09:45, Job Snijders <> wrote:

> While you are right that it is useful to define what is required for
> what sort of document, but I'd like to observe that at this moment, we
> are looking at a draft with 0 (zero, null, nada) implementations*, and
> also no implementation report draft which stipulates what should be
> tested. So your specific question is perhaps somewhat moot. Whatever the
> answer is, it will be larger than zero.

I feel that I'm a reasonably pragmatic person and I am not generally
in favour of boiling the ocean when all we were asked for was an
ISO-standard cup of tea.

However, I think it's worth reflecting on what happens when we don't
have a firm grip on protocol compliance in related implementations --
we get the kind of confusion that resulted from RFC8145. Although that
confusion has numerous root causes, we know for a fact that
variability in implementation has contributed to the madness.

The purpose of this particular draft is to facilitate useful
measurements that will yield a clear signal. I don't imagine the
authors of the draft are any more eager to see a noisy signal than the
rest of us.

If we can make it easier for implementations to behave reliably and
predictably e.g. by specifying what compliance means, I regardless of
the formal requirements of the working group, perhaps we should.