[DNSOP] Can an RRSET remain valid past the expiration timestamp on its signing RRSIG?
Nick Johnson <nick@ethereum.org> Wed, 24 July 2019 05:50 UTC
Return-Path: <nick@ethereum.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 D142E120276 for <dnsop@ietfa.amsl.com>; Tue, 23 Jul 2019 22:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ethereum.org
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 H3hY52ewsfBa for <dnsop@ietfa.amsl.com>; Tue, 23 Jul 2019 22:50:18 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 54FD812003F for <dnsop@ietf.org>; Tue, 23 Jul 2019 22:50:18 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id n5so46667508otk.1 for <dnsop@ietf.org>; Tue, 23 Jul 2019 22:50:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ethereum.org; s=google; h=mime-version:from:date:message-id:subject:to; bh=FX8isUz8OW7wVjd2t3pSO1OZZcSv360FrU1S5X8Yu8M=; b=dhYbK2IbibBx0ajf5VMW6YUw5OkUNOrhUeVCywrCU79eiTtdwxiGWSGqhkfEQnjAlv Ok/6galngDfO5feY3NfC4pcisCMm2XmO4P1qHMS7R31KzdcJ8FBRNElhmcQn78VByvxy YYKo0UWhI92lyPKM9jLYwvEPO/khgru2DyQn4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FX8isUz8OW7wVjd2t3pSO1OZZcSv360FrU1S5X8Yu8M=; b=RUVBo6jgUYZG1Xrp+kgBLbxjw0I+EKPjf0QvCHm167vw8wwJBe8b3WwW1WvxMOVLkF tZj4yR8vjNlCaRFpvh6lYbQn1DtliO+hmGqAr6/QUCnh72MkyyqodRsE4J/T2tYalbGs 1919ax92tGDvBsxElIsRTQxuNvqxrfiYspT68ajfz4FIGAgTD1WDqs34Bbnc2fbqtRLh nqSAeXPV2hbRPzJ82GwHbiGUCixlG08rnM2tL5YEZZzwkycrRIFDNmZTkZyiK5hjpE80 czLXfhyw6aD0UbnYKRyDiFvnD98ysErc5X20HwQrC8eMPAnpW0lJ3OsLqo5+d+I+nh7I H9Zw==
X-Gm-Message-State: APjAAAVyQMFi5gPkRw4QwElLYy/2M9o2t1BebobQKsfYU5qTAGagUVK1 CgS7L+vj6cWKN7ZQuN6Pa/9VhiXCW8uW4TFnEOE1Ke0mReakDQ==
X-Google-Smtp-Source: APXvYqwHRktrlaJYUskZRWuLACgyOelgH17u98qNVpp7ptPsKoerHQEfSV4TNrQ2Sjl3swtNs4/aL33N8DyBHK7EXMY=
X-Received: by 2002:a9d:5c11:: with SMTP id o17mr33643245otk.107.1563947417451; Tue, 23 Jul 2019 22:50:17 -0700 (PDT)
MIME-Version: 1.0
From: Nick Johnson <nick@ethereum.org>
Date: Wed, 24 Jul 2019 17:50:04 +1200
Message-ID: <CAFz7pMutjXgW4m-rpBUFqy3E+HQtQsO4f-s-TxxYxtyKaJBhxg@mail.gmail.com>
To: dnsop WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000043d198058e66e2af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/hGBVwhHtgAOmq64maBJ6wMVJvQk>
Subject: [DNSOP] Can an RRSET remain valid past the expiration timestamp on its signing RRSIG?
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, 24 Jul 2019 05:50:20 -0000
Suppose I receive a response containing an RRSET with records with ttl=3600, signed with an RRSIG that has an expiration timestamp 60 seconds from now. After validating the signature, can I cache the RRSET for 3600 seconds, or only for 60 seconds? If the former, and the RRSET is a DNSKEY, can I rely on it to validate other RRSIGs for the entire 3600 seconds? -Nick Johnson
- [DNSOP] Can an RRSET remain valid past the expira… Nick Johnson
- Re: [DNSOP] Can an RRSET remain valid past the ex… Matthijs Mekking
- Re: [DNSOP] Can an RRSET remain valid past the ex… Nick Johnson