IETF Logo Mail Archive

Re: [DNSOP] [Ext] More input for draft-ietf-dnsop-dnssec-bcp?

Wes Hardaker <wjhns1@hardakers.net> Tue, 24 May 2022 15:48 UTC

Return-Path: <wjhns1@hardakers.net>
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 D3A9AC18D83B for <dnsop@ietfa.amsl.com>; Tue, 24 May 2022 08:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 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] 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 XDbrIcvy7ctv for <dnsop@ietfa.amsl.com>; Tue, 24 May 2022 08:48:12 -0700 (PDT)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (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 2BCCDC18D837 for <dnsop@ietf.org>; Tue, 24 May 2022 08:48:12 -0700 (PDT)
Received: from localhost (unknown [10.0.0.9]) by mail.hardakers.net (Postfix) with ESMTPA id 8943220686; Tue, 24 May 2022 08:48:10 -0700 (PDT)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Paul Hoffman <paul.hoffman@icann.org>
Cc: Peter Thomassen <peter@desec.io>, "dnsop@ietf.org" <dnsop@ietf.org>
References: <02759DA4-45AF-4021-BBD1-B8733CD85CE1@icann.org> <d82ca1ff-db2f-773c-dee2-345d85cc059d@desec.io> <5BF5157A-2C96-464A-B670-A8C923774234@icann.org>
Date: Tue, 24 May 2022 08:48:10 -0700
In-Reply-To: <5BF5157A-2C96-464A-B670-A8C923774234@icann.org> (Paul Hoffman's message of "Tue, 26 Apr 2022 23:28:58 +0000")
Message-ID: <yblo7zn2apx.fsf@wd.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Pww0skEUm2J6cQF1ehcB4LCJ9UQ>
Subject: Re: [DNSOP] [Ext] More input for draft-ietf-dnsop-dnssec-bcp?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 24 May 2022 15:48:12 -0000

Paul Hoffman <paul.hoffman@icann.org> writes:

> > However, I noticed that three of the RFCs listed in the draft are
> > from 202x, and likely more will have to be added in the future. That
> > made me wonder:
> > 
> > How do we update this collection?
> 
> That's an excellent question! The likely, not-excellent answer is "we
> don't". That is, if you look at similar documents for other protocol
> sets like SIP and IPsec, they were never updated.

<WarrenHat>
  Living documents
</WarrenHat>

-- 
Wes Hardaker
USC/ISI

v2.23.0 | Report a Bug | By Email