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

Dave Lawrence <tale@dd.org> Fri, 24 February 2012 15:10 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 2B7F521F86B1; Fri, 24 Feb 2012 07:10:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1330096250; bh=uPZv+xhC6/6UhJTRO8L/5HxZEwy0LKM8fFORcjm+pK8=; h=MIME-Version:Message-ID:Date:From:To:In-Reply-To:References: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=L+FBYNozqWpI+64o+KsNaFjdhwz0sCyYwneGnsUx09DMMo7r2Pq7hHU4Tr1ggf54O CglLg5iLsZSD4judcjazX+37LmcNeemTR6N+AJ8eoto72DhQvptoXCK42mozA21AN2 0ooTXSiCLsoXt5M2s9HTK1R0BGms6J+ivB7wwyus=
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 442D621F87E9 for <dnsext@ietfa.amsl.com>; Fri, 24 Feb 2012 07:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vQkIRDEsC8GH for <dnsext@ietfa.amsl.com>; Fri, 24 Feb 2012 07:10:46 -0800 (PST)
Received: from gro.dd.org (gro.dd.org [209.198.103.200]) by ietfa.amsl.com (Postfix) with ESMTP id 42C2321F8770 for <dnsext@ietf.org>; Fri, 24 Feb 2012 07:10:44 -0800 (PST)
Received: by gro.dd.org (Postfix, from userid 102) id 2A6D23F465; Fri, 24 Feb 2012 10:10:43 -0500 (EST)
MIME-Version: 1.0
Message-ID: <20295.43122.988885.227069@gro.dd.org>
Date: Fri, 24 Feb 2012 10:10:42 -0500
From: Dave Lawrence <tale@dd.org>
To: dnsext@ietf.org
In-Reply-To: <4F390A8E.5050200@nlnetlabs.nl>
References: <20120207130116.22821.43383.idtracker@ietfa.amsl.com> <4F344AD0.9040607@ogud.com> <4F390A8E.5050200@nlnetlabs.nl>
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

W.C.A. Wijngaards writes:
> Could the authors put text in 6.1.1:
> The OPT record is normally placed near the end of the additional section.
>
> Because then there is guidance for the 'normal case'.

Given the interest in trying to have an EDNS-capable server include
the OPT whenever possible, I'd recommend that the guidance be for the
record to be first.

I'd actually thought that was what earlier drafts said, but going back
to them I see they didn't do it explicitly and I only inferred it
because the simplest algorithm for building the reply would be "add
the OPT if it fits, then add any other records until you run out of
room."  There are, of course, other ways of doing it, but providing
guidance that it be first emphasizes the idea that the OPT is the one
Additional RR that we really want to be present if at all possible.
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext