IETF Logo Mail Archive

Re: [DNSOP] IETF meeting prep and what

Joe Abley <jabley@hopcount.ca> Fri, 18 June 2021 19:05 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF9BE3A1EAA for <dnsop@ietfa.amsl.com>; Fri, 18 Jun 2021 12:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C4SVSKBrDkfW for <dnsop@ietfa.amsl.com>; Fri, 18 Jun 2021 12:05:25 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB84A3A1EA9 for <dnsop@ietf.org>; Fri, 18 Jun 2021 12:05:24 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id l2so5582387qtq.10 for <dnsop@ietf.org>; Fri, 18 Jun 2021 12:05:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0+bJpLdnu9AB5ui8k3XHwe/SkTZiPLul55QFlD2Lq4U=; b=LcDe1xZXL9oVjvBmwgOiwsXx2HaMOxbfH+ioQhtAeRZvYEzvrofWQzeaXGwqMaX7nv lbHTST9GCZDtRQCR9y5xjKjSYLn1l05E+DBsSoqVCTh2iwf6GLiXvO894QQsPli/IlBS MtRijfd23PxXKByf5u1VTLv0boA8Bo3jwRhNo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0+bJpLdnu9AB5ui8k3XHwe/SkTZiPLul55QFlD2Lq4U=; b=oTT9E9ZdKcMs0/BNkPWLKzTQWBI9EScjNTVm7BypWOdqhn17jx3t8B9QMo3P/CpQKU JCESg39blLYjLrQvRVSUiZcbXi0kRLNFKr3AlSOaJAS8SGmeLG9tsJFYbyJQJrvyoPHN sQGGi2hQp+x/CD4ptU8jAU+oPZdmulaoiKrGOQXWIzSqVJQDq+NyylomcZEqSpyNt/FV V3eTS3n98uO/+6X5nmrx8Od2DHWWyWp/EflbmR6E/o12xj+GJhhcSbq3PfHL3TjUverD PiLhGc6ZISisjgeJtHQQw2dcy+1Se78dPGQyH8vCQ+4WgHIi1wWASp7eBvh+IpB9oH/T 6RzA==
X-Gm-Message-State: AOAM531bKxhtSgAaOUUpsWvB43RCCsTyka8ltfOxi0P9VNpZtk1FCNj/ jG8Od5Je+O1G1N9f0q8oHQDFwg==
X-Google-Smtp-Source: ABdhPJxyx9i2Enp4fig3l472ERjkuYtU7LhEmTCak/TxV5gc8JLTJiPGqTxs49NKIBGS4wLbYeFlVw==
X-Received: by 2002:a05:622a:14cc:: with SMTP id u12mr2495533qtx.214.1624043122965; Fri, 18 Jun 2021 12:05:22 -0700 (PDT)
Received: from smtpclient.apple ([2607:f2c0:e784:c7:256e:9e53:2b8:640e]) by smtp.gmail.com with ESMTPSA id q16sm4559551qkq.121.2021.06.18.12.05.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Jun 2021 12:05:22 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <A7A0319B-2DB5-49F7-9E8C-A0065157D14A@nohats.ca>
Date: Fri, 18 Jun 2021 15:05:21 -0400
Cc: Peter van Dijk <peter.van.dijk@powerdns.com>, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CB2EC32-E53D-4D08-8431-F7B6AD68D004@hopcount.ca>
References: <5a9b35c5806e36b0802be493d87beb8ef2fef18d.camel@powerdns.com> <A7A0319B-2DB5-49F7-9E8C-A0065157D14A@nohats.ca>
To: Paul Wouters <paul@nohats.ca>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Zu6vvG7wUpsHdLqKIEvTRjBw0Ek>
Subject: Re: [DNSOP] IETF meeting prep and what
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jun 2021 19:05:30 -0000

On 18 Jun 2021, at 14:45, Paul Wouters <paul@nohats.ca> wrote:

> On Jun 18, 2021, at 13:41, Peter van Dijk <peter.van.dijk@powerdns.com> wrote:
> 
>> I propose replacing rfc5011-security-considerations with a short document deprecating 5011 in its entirety.
> 
> Eh? 5011 is baked into various software. Why would replace 5011 ?
> 
> Did I miss something?

There were some conversations adjacent to the last great root zone KSK roll excitement about how a more measurable and reliable mechanism might be useful. My memory is that there might be value in specifying a new mechanism that could be used as an alternative to or in conjunction with 5011, though, not that 5011 was fundamentally unsound and deserved to be deprecated.

I agree that, in the end, 5011 seems to have done a reasonable job -- it was just hard to predict with any degree of comfort or certainty.


Joe

v2.14.0 | Report a Bug | By Email