Re: [dnsext] BADVER/FORMERR

"Michael Sheldon" <msheldon@godaddy.com> Tue, 15 November 2011 22:31 UTC

Return-Path: <msheldon@godaddy.com>
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 3731011E80FD for <dnsext@ietfa.amsl.com>; Tue, 15 Nov 2011 14:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level:
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=0.930, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 TzaseSoA42fK for <dnsext@ietfa.amsl.com>; Tue, 15 Nov 2011 14:30:58 -0800 (PST)
Received: from smtpoutwbe06.prod.mesa1.secureserver.net (smtpoutwbe06.prod.mesa1.secureserver.net [208.109.78.208]) by ietfa.amsl.com (Postfix) with SMTP id E8CCE11E80F1 for <dnsext@ietf.org>; Tue, 15 Nov 2011 14:30:57 -0800 (PST)
Received: (qmail 2860 invoked from network); 15 Nov 2011 22:30:57 -0000
Received: from unknown (HELO gem-wbe32.prod.mesa1.secureserver.net) (64.202.189.144) by smtpoutwbe06.prod.mesa1.secureserver.net with SMTP; 15 Nov 2011 22:30:57 -0000
Received: (qmail 14575 invoked by uid 99); 15 Nov 2011 22:30:56 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 172.19.38.143
User-Agent: Web-Based Email 5.6.04
Message-Id: <20111115153055.205a61dff9fc1684c258b274662bb912.4a8b265d31.wbe@email00.secureserver.net>
From: Michael Sheldon <msheldon@godaddy.com>
To: dnsext <dnsext@ietf.org>
Date: Tue, 15 Nov 2011 15:30:55 -0700
Mime-Version: 1.0
Subject: Re: [dnsext] BADVER/FORMERR
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>
X-List-Received-Date: Tue, 15 Nov 2011 22:31:12 -0000

> -------- Original Message --------
> Subject: Re: [dnsext] BADVER/FORMERR
> From: Dick Franks <rwfranks@acm.org>
> Date: Tue, November 15, 2011 11:32 am
> To: Ray Bellis <Ray.Bellis@nominet.org.uk>
> Cc: dnsext <dnsext@ietf.org>
> 

> Part of Mark A's argument is that the semantics for QDCOUNT = 0 should
> be considered well defined because no standard query processing is
> involved if there is no question to process.

Really? Exactly what part of any RFC defines what should be returned on
a QUERY where QDCOUNT == 0? Unless you found something I haven't seen,
it's not only not well-defined, it's not defined at all. 

> Furthermore, he noted that an empty question section is (trivially)
> parsable, and cites three plausible scenarios where such a query might
> be useful.

He defines circumstances where he can learn things from the server by
deliberately sending invalid data, thus eliciting an error message. So
we've already defined that he's deliberately sending contextually bogus
data. The question is, if everything in the EDNS section is correct,
what would the response be to QDCOUNT=0? Unless you can convince me
there is a valid non-error response to this, I see nothing wrong with
returning a response based on the first error I find and discontinuing
parsing at that point. In my opinion, a query with no query is a format
error. Any further errors beyond that point are irrelevant.

My suggestion Mark, is to put some kind of question in the packet, the
size difference is frankly insignificant.


Michael Sheldon
Dev-DNS Services
GoDaddy.com