Re: [dnsext] I-D Action: draft-ietf-dnsext-rfc2671bis-edns0-08.txt

Joao Damas <joao@bondis.org> Mon, 13 February 2012 23:16 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 941C521E8034; Mon, 13 Feb 2012 15:16:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1329174973; bh=Hjd+KL77aPZH7o3rEz4aI9tNKR+3J0FWPMV0vmwKBI8=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To:Cc: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=M5KfCHuDQucxXzBVS7QfeZWa6jUCpcmMIxyAUczoa+kEh4DxFqxEkbUYNQJdMFQKk yyG9+Mj08UGOOKo7T+Hk0P3oJBIWnxwkVRY2G2W/G6wRhL38qHAe4d9uWCKYHlXcpr VgeTCJx1gT7aFAk8TU8Ok4Sj/g2pYfoIk1EVk40Q=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88AD321E8020 for <dnsext@ietfa.amsl.com>; Mon, 13 Feb 2012 15:16:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.204
X-Spam-Level:
X-Spam-Status: No, score=-1.204 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3FCl79hD5Ov for <dnsext@ietfa.amsl.com>; Mon, 13 Feb 2012 15:16:11 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 0953C21E8037 for <dnsext@ietf.org>; Mon, 13 Feb 2012 15:16:10 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.pao1.isc.org (Postfix) with ESMTPS id 9A95EC9498; Mon, 13 Feb 2012 23:16:00 +0000 (UTC) (envelope-from joao@bondis.org)
Received: from [IPv6:2001:4f8:3:65:81dc:4d4:27cf:75ba] (unknown [IPv6:2001:4f8:3:65:81dc:4d4:27cf:75ba]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 7230D216C6D; Mon, 13 Feb 2012 23:16:00 +0000 (UTC) (envelope-from joao@bondis.org)
Mime-Version: 1.0 (Apple Message framework v1257)
From: Joao Damas <joao@bondis.org>
In-Reply-To: <a06240802cb5f053b3b1d@[192.168.128.21]>
Date: Mon, 13 Feb 2012 15:16:00 -0800
Message-Id: <C3625191-C9D2-464F-98CB-7B7F6582071C@bondis.org>
References: <20120207130116.22821.43383.idtracker@ietfa.amsl.com> <4F344AD0.9040607@ogud.com> <4F390A8E.5050200@nlnetlabs.nl> <a06240802cb5f053b3b1d@[192.168.128.21]>
To: Edward Lewis <Ed.Lewis@neustar.biz>
X-Mailer: Apple Mail (2.1257)
Cc: dnsext@ietf.org
Subject: Re: [dnsext] I-D Action: draft-ietf-dnsext-rfc2671bis-edns0-08.txt
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

That's exactly it.
It could be less but that would mean you would be *almost* better off without EDNS (you still would get the additional flag field). You would be adding overhead to the DNS packet while limiting the packet size to a smaller amount than plain DNS creating an increased potential for fallback to TCP

Joao

On 13 Feb 2012, at 10:27, Edward Lewis wrote:

> At 14:05 +0100 2/13/12, W.C.A. Wijngaards wrote:
> 
>> Why is: udpsize < 512 MUST be treated as 512 size?
> 
> My assumption:
> 
> 1) For ease of implementation
> 2) Because if the bufsize is too small, the header might not fit. ;)
> 
> There's a need to set a lower bound for bufsize large enough to allow for even a FORMERR response.  That's, what 12 bytes give or take, way less than 512, but the protocol is used to 512 as hard size limit.
> 
> Do you want/need to see 512 lowered?
> -- 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Edward Lewis
> NeuStar                    You can leave a voice message at +1-571-434-5468
> 
> 2012...time to reuse those 1984 calendars!
> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext

_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext