[DNSOP] [Errata Verified] RFC6781 (4844)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 29 March 2017 17:19 UTC
Return-Path: <wwwrun@rfc-editor.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 91D8D1292C5; Wed, 29 Mar 2017 10:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 L0ROFPAId9hn; Wed, 29 Mar 2017 10:19:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05E781289C3; Wed, 29 Mar 2017 10:19:04 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3C7D2B8011A; Wed, 29 Mar 2017 10:18:53 -0700 (PDT)
To: sanz@denic.de, olaf@nlnetlabs.nl, matthijs@nlnetlabs.nl, miek.gieben@sidn.nl
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: joelja@bogus.com, iesg@ietf.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20170329171853.3C7D2B8011A@rfc-editor.org>
Date: Wed, 29 Mar 2017 10:18:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Z25ZjjUZ_ZfvasBsLa0n85P7c9A>
Subject: [DNSOP] [Errata Verified] RFC6781 (4844)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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 Mar 2017 17:19:06 -0000
The following errata report has been verified for RFC6781, "DNSSEC Operational Practices, Version 2". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=6781&eid=4844 -------------------------------------- Status: Verified Type: Technical Reported by: Marcos Sanz <sanz@denic.de> Date Reported: 2016-10-26 Verified by: Joel Jaeggli (IESG) Section: 4.1.2 Original Text ------------- initial: Initial version of the zone. The parental DS points to DNSKEY_K_1. Before the rollover starts, the child will have to verify what the TTL is of the DS RR that points to DNSKEY_K_1 -- it is needed during the rollover, and we refer to the value as TTL_DS. new DNSKEY: During the "new DNSKEY" phase, the zone administrator generates a second KSK, DNSKEY_K_2. The key is provided to the parent, and the child will have to wait until a new DS RR has been generated that points to DNSKEY_K_2. After that DS RR has been published on all servers authoritative for the parent's zone, the zone administrator has to wait at least TTL_DS to make sure that the old DS RR has expired from caches. DS change: The parent replaces DS_K_1 with DS_K_2. Corrected Text -------------- initial: Initial version of the zone. The parental DS points to DNSKEY_K_1. Before the rollover starts, the child will have to verify what the TTL is of the DS RR that points to DNSKEY_K_1 -- it is needed during the rollover, and we refer to the value as TTL_DS. Also, we refer to the TTL value of the DNSKEY_K_1 RR as TTL_DNSKEY. new DNSKEY: During the "new DNSKEY" phase, the zone administrator generates a second KSK, DNSKEY_K_2. The new DNSKEY RRSet that includes DNSKEY_K_2 is published at the child. After waiting at least TTL_DNSKEY, DNSKEY_K_2 (or the DS RR generated from it, that is DS_K_2) is provided to the parent. DS change: The parent replaces DS_K_1 with DS_K_2. After that DS RR has been published on all servers authoritative for the parent's zone, the zone administrator has to wait at least TTL_DS to make sure that the old DS RR has expired from caches. Notes ----- I just corrected what is fundamentally flawed. RFC 7583 section 3.3.1 provides a much detailed explanation of the process. -------------------------------------- RFC6781 (draft-ietf-dnsop-rfc4641bis-13) -------------------------------------- Title : DNSSEC Operational Practices, Version 2 Publication Date : December 2012 Author(s) : O. Kolkman, W. Mekking, R. Gieben Category : INFORMATIONAL Source : Domain Name System Operations Area : Operations and Management Stream : IETF Verifying Party : IESG
- [DNSOP] [Errata Verified] RFC6781 (4844) RFC Errata System