Re: [DNSOP] [Ext] Martin Duke's Discuss on draft-ietf-dnsop-dnssec-iana-cons-04: (with DISCUSS and COMMENT)

Martin Duke <martin.h.duke@gmail.com> Wed, 29 September 2021 16:16 UTC

Return-Path: <martin.h.duke@gmail.com>
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 506D93A00C8; Wed, 29 Sep 2021 09:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 qdcRHeJ5Bqjv; Wed, 29 Sep 2021 09:16:03 -0700 (PDT)
Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (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 10C2F3A00C1; Wed, 29 Sep 2021 09:16:03 -0700 (PDT)
Received: by mail-vk1-xa2e.google.com with SMTP id s137so1404777vke.11; Wed, 29 Sep 2021 09:16:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MxBMezknZQxjqIOdPvD9kOgzu7+9kfksHpI5hFKgrTU=; b=bP9+VOGH5c6pbmZyi80Nt7Z9JuG9cb71FSaOy3C0J9IDrV+sU8XYztg4uoW4bEOxp2 QpzdMpfAmWOTI/HFXVcAEXeXMc+s7MDyParttchTmMEJikoZrcnRtrACS7fSH8Lx8smo D0tJ1CwOfEmHFCtEZx2D7FyYUIGew/OWIGb/PGnycrSsN6YPW4CIeFn+joXZY/7wVjCz C8EQyRvucWyKJPudOim/r6DuhDcmZ8o+lgzWHi9OSP1xIVfAwrgBqW6PoAbUC9Una9Ig iS2M698gIKOj14rObF7epmQek7a0K4o1lPLjNDGr88ERfnAXLx2cpspI8TvNlondvYtH egmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MxBMezknZQxjqIOdPvD9kOgzu7+9kfksHpI5hFKgrTU=; b=yaG/M578Eeg8d0J6Kj4FV+b54s3A53WsUyn5UXZ69LupHnqEPhB26gNU7eDOkGB5/v 7l/eDBWTo8x9h/h+xnTwyiBcj2sH+qp5CwX0NgYMYjsdiem3eBs5WrRneMFD6Jb+UF9M QKxDomVT/P+ndL33mHccW+S7XV+U4jvJmZ72YTQGOQHqgtAn62xAbGXAdYo9Dhee4KKW RRTFURigaov30LB9ilXOkb/4wUBtpquAxydEgXyko+zNists8W3ABJ+go78RRfFLoHvA ri65EdTJXbiHqb1BsfV1Uq27ZjZVBGJmrQLjm7u2xGnD0PgEEPloktfeGFV1Bzc+ymyI 4Qcg==
X-Gm-Message-State: AOAM5334qETznUFcuhqcxPqDDZVjzoYKca1ndzAOTv5XT8sTAuko5LKk KUanvBjG3OYIU77F6my0RAhfXZjPLNM+4BBKfLTYTOVh
X-Google-Smtp-Source: ABdhPJxa3xPLFSfTsccW6nlHZ7L+FZoZPmq/BxucUfOw/EkCYgwNq8HLnD+bKUiEdGm5aUsfe3m731N5bcf0GxPkgok=
X-Received: by 2002:a1f:3a4b:: with SMTP id h72mr461052vka.19.1632932160047; Wed, 29 Sep 2021 09:16:00 -0700 (PDT)
MIME-Version: 1.0
References: <163285408723.29955.12780997671770548944@ietfa.amsl.com> <AE26C926-F618-4C16-88E6-5DD4AED2B178@icann.org>
In-Reply-To: <AE26C926-F618-4C16-88E6-5DD4AED2B178@icann.org>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 29 Sep 2021 09:15:49 -0700
Message-ID: <CAM4esxTC4QHvg+bihhMudO3jpyrpMu0G1YkCrSJH=PLSJkNZHw@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: The IESG <iesg@ietf.org>, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000579c9f05cd24a5c7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/xbNzSOfH5XvI77QTVejDv2zHoLA>
Subject: Re: [DNSOP] [Ext] Martin Duke's Discuss on draft-ietf-dnsop-dnssec-iana-cons-04: (with DISCUSS and COMMENT)
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: Wed, 29 Sep 2021 16:16:09 -0000

Thank you for clarifying. If 4033-4035 fully replaced 3658, then one of
them should have picked up the specification of the registry that 3658
established. Maybe this is something that could be addressed in this
document, or perhaps somewhere else; I'd like to have the discussion.

On Wed, Sep 29, 2021 at 8:49 AM Paul Hoffman <paul.hoffman@icann.org> wrote:

> On Sep 28, 2021, at 11:34 AM, Martin Duke via Datatracker <
> noreply@ietf.org> wrote:
> >
> > ----------------------------------------------------------------------
> > DISCUSS:
> > ----------------------------------------------------------------------
> >
> > Holding this point because we should discuss it; this might be a problem
> to be
> > solved by a different document, in which case I'll lift it.
> >
> > Section 8 of RFC8126 says that bis documents should update the reference
> in
> > IANA registries to replace obsolete documents with not-obsolete ones. It
> > appears that 3658 didn't have a "bis" document but clearly was replaced
> by
> > three others.
>
> It was obsoleted by RFCs 4033, 4034, and 4035. Those are not "bis"
> documents, they are full replacements.
>
> > I don't really understand how they fully obsolete 3658 if there
> > are still registries hanging out there.
>
> Please define "hanging out there". :-) The registry of interest is at <
> https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml#ds-rr-types-1>.
> The "Reference" section in that registry lists
> "[RFC3658][RFC4034][RFC4035]".
>
> Is your objection that the registry still lists RFC 3658? If so, this
> seems an IANA issue, not an issue with this draft.
>
> > Regardless, perhaps this draft is an
> > opportunity to update the reference to these registries?
>
> The draft refers to the correct registry.
>
> > Or is 3658 not
> > "really" obsolete?
>
> It is really obsolete, and has been for well over a decade.
>
> Is this explanation complete enough for you to lift your DISCUSS ballot?
>
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Nit: Please expand DS and NSEC3 on first use.
> >
>
> Good catch; I will add these to the -05 draft.
>
> --Paul Hoffman