Re: [DNSOP] Additional EDE codes for resource limits
Wes Hardaker <wjhns1@hardakers.net> Wed, 02 December 2020 18:32 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 BBB0C3A18BA for <dnsop@ietfa.amsl.com>; Wed, 2 Dec 2020 10:32:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level:
X-Spam-Status: No, score=-0.499 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 2YNju280hmiB for <dnsop@ietfa.amsl.com>; Wed, 2 Dec 2020 10:32:13 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.192.181]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08DDF3A17DE for <dnsop@ietf.org>; Wed, 2 Dec 2020 10:31:01 -0800 (PST)
Received: from localhost (unknown [10.0.0.3]) by mail.hardakers.net (Postfix) with ESMTPA id B3BF5268F6; Wed, 2 Dec 2020 10:30:59 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: "libor.peltan" <libor.peltan@nic.cz>
Cc: dnsop@ietf.org
References: <19129a4c-7aab-1c81-2a6e-e382479851c1@nic.cz>
Date: Wed, 02 Dec 2020 10:30:59 -0800
In-Reply-To: <19129a4c-7aab-1c81-2a6e-e382479851c1@nic.cz> (libor peltan's message of "Tue, 1 Dec 2020 10:32:24 +0100")
Message-ID: <yblsg8o5acc.fsf@w7.hardakers.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/anknNh0IEd_dAXktS3dtZUPVlVk>
Subject: Re: [DNSOP] Additional EDE codes for resource limits
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, 02 Dec 2020 18:32:22 -0000
"libor.peltan" <libor.peltan@nic.cz> writes: I'm trying to think about when these would be included and what would be in the rest of the response. > 1) it lacks resources So, with this one it would return something like REFUSED quickly without doing the search for data and just say "I'm overwhelmed, try again later" essentially? > 2) rate-limiting was applied So this would be used in the common RRL case, where information would be left out and the TC bit was set? IE, the EDE code would indicate that RRL had been hit; that makes some sense. -- Wes Hardaker USC/ISI
- [DNSOP] Additional EDE codes for resource limits libor.peltan
- Re: [DNSOP] Additional EDE codes for resource lim… Wes Hardaker
- Re: [DNSOP] Additional EDE codes for resource lim… Eric Orth