Re: [DNSOP] Benjamin Kaduk's No Objection on draft-ietf-dnsop-multi-provider-dnssec-04: (with COMMENT)

Shumon Huque <shuque@gmail.com> Thu, 09 April 2020 20:34 UTC

Return-Path: <shuque@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 D68883A0DDF; Thu, 9 Apr 2020 13:34:33 -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 nWZR6tjZYAox; Thu, 9 Apr 2020 13:34:32 -0700 (PDT)
Received: from mail-oi1-x22c.google.com (mail-oi1-x22c.google.com [IPv6:2607:f8b0:4864:20::22c]) (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 D00DB3A0DDE; Thu, 9 Apr 2020 13:34:31 -0700 (PDT)
Received: by mail-oi1-x22c.google.com with SMTP id m14so1080352oic.0; Thu, 09 Apr 2020 13:34:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uWAb6qb8U/oSkfjYZ2/qWd5EVvZoH/jXHYjP3UrRXsg=; b=ME4aH3NNl1yWUZskvIU0VLZyYhDHkhGpSH2T3FAV2fQPVgC7SXC3ajBMUxEoaIbJcW HDLGZV6iAXu9b34iA4N2AiREO+I7JcrrxukGmBrEHT31rVIa4RTlUs3k7kBsBR4LOg1D lIRrtgsvgeOAiR6VLFESiNTFCDOKhvVkcvu/eN0cW19Od7jcjT6iaePur1Ku0oz/4P8H cIDAyk/GU1qpRv2CcMPPpTrHwp25pM4fqbzHnXVn9oac9ixbLMfsYDMG/F1yBMbDY1jL JTFybZDBZBO5VmTu/WAQd/eh4NzRIOtN9FWBxVp3yXNciRnwfuMXqYmPKAW6tY8IAwC5 HZmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uWAb6qb8U/oSkfjYZ2/qWd5EVvZoH/jXHYjP3UrRXsg=; b=RQVj22WviO8vEzHE0v95TQFnD0PKu/tvIwOr2tGCQrSYlBWCsePOZAvsiwJrZpWRJ6 rAbXoGs8fIaiE6mW9htLP3m/oy14iHfXmHDg7EQD0IpoD30qep0YOCKbCtdLNI14Bk9W JpqwHp8nfgtzGkmmvgevk0L+9vdLTGcunl4+c7OtR7WFPVExtZglOj6CwX0XNONkCWl0 5of8fUJcoRN+kA17pukT8YOcrxs8Q92FJGEw/TczN1Mvt2O+/BLDWnoc5hTNs+bp6BHF Iwsn4WgvEfuegvF/b6qR7b16Ux6I6fEwZFRoIBs6B2U5iolhMF/QFEUSQDvAEKAbFu57 lUnw==
X-Gm-Message-State: AGi0PuZx+3a7zzZKC5Dsb/0EJ+DJF1TqS4TZS/5vEEguLvA/TBiAfbJE XV0T+AUFHeUVdekHRffn1Vw3sG/xQjA+CYuG0Rc=
X-Google-Smtp-Source: APiQypL4RjfLsBnz99rlgFcnUeevnc8GUXpCeTtLfN1z7JQNPZER3aYBr0dP2FUDvRiWyifkg9Vq4xCH5sqmWrJNwDs=
X-Received: by 2002:a05:6808:207:: with SMTP id l7mr979456oie.171.1586464471108; Thu, 09 Apr 2020 13:34:31 -0700 (PDT)
MIME-Version: 1.0
References: <158640898724.3293.17093328253615706681@ietfa.amsl.com> <CAH1iCiqT6bdhKq2uUSH1AU7jf9zOQ1OEQNpwHWZn=h4A2w2AOw@mail.gmail.com>
In-Reply-To: <CAH1iCiqT6bdhKq2uUSH1AU7jf9zOQ1OEQNpwHWZn=h4A2w2AOw@mail.gmail.com>
From: Shumon Huque <shuque@gmail.com>
Date: Thu, 09 Apr 2020 16:34:19 -0400
Message-ID: <CAHPuVdVJQiZxs52PnVbNfzbK+Vm-ODvFj-nNzZyHatCrTFR2LA@mail.gmail.com>
To: Brian Dickson <brian.peter.dickson@gmail.com>
Cc: Benjamin Kaduk <kaduk@mit.edu>, The IESG <iesg@ietf.org>, draft-ietf-dnsop-multi-provider-dnssec@ietf.org, "dnsop@ietf.org WG" <dnsop@ietf.org>, DNSOP chairs <dnsop-chairs@ietf.org>, Benno Overeinder <benno@nlnetlabs.nl>
Content-Type: multipart/alternative; boundary="0000000000003fd2bf05a2e18b6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/3UCXhpY19bD13B7l-_Z4ZrIBB_U>
Subject: Re: [DNSOP] Benjamin Kaduk's No Objection on draft-ietf-dnsop-multi-provider-dnssec-04: (with 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: Thu, 09 Apr 2020 20:34:34 -0000

On Thu, Apr 9, 2020 at 3:48 PM Brian Dickson <brian.peter.dickson@gmail.com>
wrote:

>
> On Wed, Apr 8, 2020 at 10:10 PM Benjamin Kaduk via Datatracker <
> noreply@ietf.org> wrote:
>
>>
>> Section 6.1, 6.2
>>
>> Should we say anything about when it's safe for a new ZSK to be used to
>> sign responses?
>>
>
> I think, technically speaking, it is always safe to use a new ZSK, and the
> only concern is when it's safe to remove and/or revoke the old ZSK (i.e.
> that it is safe to use ONLY the new ZSK.)
>

Hi Brian,

Your statement is true for double signature ZSK rolls (which are less
common).

In the pre-publish ZSK rollover scheme (much more common), the new ZSK
starts signing new or modified data in the zone _exclusively_, and the
corresponding old ZSK signatures are yanked out, after "propagation time +
DNSKEY TTL time" has transpired. So if you do this too early, data in your
zone could become unvalidatable.

This is described in RFC6781, although the description is a quite dated --
since it talks about monolithic re-signing of zone data, and does not
contemplate incremental signing, which is becoming far more common these
days.

Shumon.