IETF Logo Mail Archive

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

Peter Thomassen <peter@desec.io> Wed, 25 May 2022 11:13 UTC

Return-Path: <peter@desec.io>
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 7E746C18353A for <dnsop@ietfa.amsl.com>; Wed, 25 May 2022 04:13:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.753
X-Spam-Level:
X-Spam-Status: No, score=-8.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-1.857, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=a4a.de
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 xbmm30id_uyy for <dnsop@ietfa.amsl.com>; Wed, 25 May 2022 04:13:43 -0700 (PDT)
Received: from mail.a4a.de (mail.a4a.de [IPv6:2a01:4f8:10a:1d5c:8000::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7938BC183533 for <dnsop@ietf.org>; Wed, 25 May 2022 04:13:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=a4a.de; s=20170825; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:Cc:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=cx53tOKLfEArpj4tykj+4YzgJcm9frSwMyr6A9J3w+o=; b=MF+U7IFwllQN4zO9ylaqk4a7qK Nkqky3jv3yZQAIds9xy+b1BWuS2kB7ZJkZW5E7E3hsVPufszAzLTdyjphv8KeUtj9QfQF7fVW2Trr 1+Dizvmbp+VSy/8ySxAc6acKvo0JA4x8C5COGh3jE73ft7HxKugWr0GEksfm6Nq+BmmoXUI2QkQtl JTVGMU7UTNVxXWeqnSrHBx4J8P1m2d3lrjZtG1DLU6lh43hX2cUWM6gesoExoJF0VvDve2AiX4w6+ gCnSNsN+Yf5/Ixn0AakPwcpnzkArv/iO67oGKAsPxurQvVxdveW953Owu7RvBs/4Z2ygcTw22Znbh lgzQB6Rg==;
Received: from [91.65.95.29] (helo=[192.168.178.70]) by mail.a4a.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from <peter@desec.io>) id 1ntoxG-0005pM-Gq; Wed, 25 May 2022 13:13:30 +0200
Message-ID: <ee0317bd-837d-08ed-4c21-b80618040ab0@desec.io>
Date: Wed, 25 May 2022 13:13:29 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
Content-Language: en-US
To: Wes Hardaker <wjhns1@hardakers.net>, Paul Hoffman <paul.hoffman@icann.org>
Cc: "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> <yblo7zn2apx.fsf@wd.hardakers.net>
From: Peter Thomassen <peter@desec.io>
In-Reply-To: <yblo7zn2apx.fsf@wd.hardakers.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/fM6aFukRcNG1oy7iGHUmBmOk9nk>
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: Wed, 25 May 2022 11:13:47 -0000

On 5/24/22 17:48, Wes Hardaker wrote:
>>> 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>
This seems to refer to https://mailarchive.ietf.org/arch/msg/ietf/zy2l7gWR8yGRIIt5mYY5WSorqGY/ (which I had not heard about before).

I'm not sure, Wes, if your comment is just a humorous reference or whether something from that discussion applies here?

In any case, the thread is rather long. Would somebody be able to summarize (or point to) the results of the discussion in a sentence or two?

Thanks,
Peter

-- 
https://desec.io/

v2.23.0 | Report a Bug | By Email