IETF Logo Mail Archive

Re: [DNSOP] Do we need new draft that recommends number limits ?

Paul Vixie <paul@redbarn.org> Tue, 12 March 2024 14:50 UTC

Return-Path: <paul@redbarn.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 ADC86C15108C for <dnsop@ietfa.amsl.com>; Tue, 12 Mar 2024 07:50:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=redbarn.org
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 Hs4IWev5ne5z for <dnsop@ietfa.amsl.com>; Tue, 12 Mar 2024 07:50:01 -0700 (PDT)
Received: from util.redbarn.org (util.redbarn.org [IPv6:2001:559:8000:cd::222]) (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 D2F22C14F60E for <dnsop@ietf.org>; Tue, 12 Mar 2024 07:50:01 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "*.redbarn.org", Issuer "RapidSSL TLS RSA CA G1" (not verified)) by util.redbarn.org (Postfix) with ESMTPS id 1ECD919CCAE for <dnsop@ietf.org>; Tue, 12 Mar 2024 14:50:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1710255001; bh=zqDBpPy6Xq1AxR8znqodp5zPK8qSUl5S/23ouJaXlQY=; h=Date:Subject:In-Reply-To:References:From:To; b=nAEv4zW2MajzYxwWHR9du4GWU+WjbYVFPbO41xDsT0WvR9SjG5RiwZtkmf9MBXJYI do1EydelSPVM/s3kbyum3YZr3dR+0kl3e4U6DT0xegGwcLQgjdh3ruE6puIwGfR9ro iZhsAsnxpV1s35hto7Cih6KoJen5fUAcJsRfdvzs=
Received: from [24.104.150.152] (dhcp-152.access.rits.tisf.net [24.104.150.152]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id D6C4EC3F1F for <dnsop@ietf.org>; Tue, 12 Mar 2024 14:50:00 +0000 (UTC)
Date: Tue, 12 Mar 2024 07:49:59 -0700
Message-ID: <90fed16b-a136-4c81-919d-7a4d4ba068bc@redbarn.org>
In-Reply-To: <20240312.171904.558689864486146903.fujiwara@jprs.co.jp>
References: <20240312.171904.558689864486146903.fujiwara@jprs.co.jp>
From: Paul Vixie <paul@redbarn.org>
To: dnsop@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.boxer.email_6276430179366688"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/4TbDcWvqxziMb1cGWapVu7bA81o>
Subject: Re: [DNSOP] Do we need new draft that recommends number limits ?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.39
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, 12 Mar 2024 14:50:05 -0000

<<Rather than writing a draft for each limitation,

I think it would be better to compile them all into one draft.>>


+1.


p vixie

v2.23.0 | Report a Bug | By Email