Re: [DNSOP] Some distinctions and a request - Have some class?

P Vixie <paul@redbarn.org> Sun, 05 July 2015 12:11 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30F3C1A1B88 for <dnsop@ietfa.amsl.com>; Sun, 5 Jul 2015 05:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 DsBWTWL7OYMm for <dnsop@ietfa.amsl.com>; Sun, 5 Jul 2015 05:11:39 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B20C81A1B7C for <dnsop@ietf.org>; Sun, 5 Jul 2015 05:11:39 -0700 (PDT)
Received: from [192.168.2.172] (unknown [195.11.186.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 7B768184D7; Sun, 5 Jul 2015 12:11:38 +0000 (UTC)
User-Agent: K-9 Mail for Android
In-Reply-To: <20150705115107.GA27268@sources.org>
References: <20150704063120.2380.qmail@ary.lan> <017CF015-8A06-40D5-9ECF-B7B7E208C7AF@frobbit.se> <6F830DF3-9FD6-43A1-8E9A-5854958BA848@shinkuro.com> <20150705115107.GA27268@sources.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----CPHCEGLYB8M09FN9SZA6R76S8SSETV"
Content-Transfer-Encoding: 8bit
From: P Vixie <paul@redbarn.org>
Date: Sun, 05 Jul 2015 13:11:31 +0100
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Steve Crocker <steve@shinkuro.com>
Message-ID: <F8D42EF3-CF9A-4836-A798-1AD18CDB5260@redbarn.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/6ioE7Bk1Se_fH2HpeceWTyBkqMg>
Cc: "dnsop@ietf.org" <dnsop@ietf.org>
Subject: Re: [DNSOP] Some distinctions and a request - Have some class?
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 05 Jul 2015 12:11:41 -0000

Delay is expensive for responders since it requires state. Steve's goal of making some tld strings flaky so as to encourage developers to avoid DNS for those names could be met statelessly. For example delegate them to localhost.

On July 5, 2015 12:51:08 PM GMT+01:00, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
>On Sat, Jul 04, 2015 at 09:16:17AM -0700,
> Steve Crocker <steve@shinkuro.com> wrote 
> a message of 21 lines which said:
>
>> except for the additional load it places on the root servers,
>
>RFC 7535 could be a solution.
>
>> I propose augmenting the DNS to include entries in the root that
>> serve the purpose of giving slow NXDOMAIN responses instead of quick
>> responses for those strings that the IETF has identified as not
>> TLDs.
>
>If it is a serious proposal, I object. Delaying answers require
>keeping state in the authoritative name server and opens a nice DoS
>boulevard.
>
>_______________________________________________
>DNSOP mailing list
>DNSOP@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsop

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.