[DNSOP] RFC6781 Cooperating DNS provider signed zone migration

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 24 June 2022 21:05 UTC

Return-Path: <ietf-dane@dukhovni.org>
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 2DA18C15A725 for <dnsop@ietfa.amsl.com>; Fri, 24 Jun 2022 14:05:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xazeExwx-wqV for <dnsop@ietfa.amsl.com>; Fri, 24 Jun 2022 14:04:59 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6EFC159484 for <dnsop@ietf.org>; Fri, 24 Jun 2022 14:04:59 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 56027FED8C; Fri, 24 Jun 2022 17:04:57 -0400 (EDT)
Date: Fri, 24 Jun 2022 17:04:57 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: dnsop@ietf.org
Message-ID: <YrYm+ZH7vSie3L/5@straasha.imrryr.org>
Reply-To: dnsop@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/53DJBcNqNENGAThdLlxcQbUcQTQ>
Subject: [DNSOP] RFC6781 Cooperating DNS provider signed zone migration
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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, 24 Jun 2022 21:05:00 -0000

Is anyone aware of better descriptions of cooperating DNS operator DNS
provider migrations than are found in RFC 6781 section 4.3.5.1

    https://datatracker.ietf.org/doc/html/rfc6781#section-4.3.5.1

and Appendix D:

    https://datatracker.ietf.org/doc/html/rfc6781#appendix-D

Both descriptions could use more detailed prose (especially appendix D
that has none), and there are some mistakes in the diagrams.

Also which of the two processes do actual hosting operators support?
(To my mind, Appendix D is the more realistic model, but it is much more
sketchy than 4.3.5.1).

Would it make sense to write a BCP that updates 6781 in light of
operational best practices in the last decade?

-- 
    Viktor.