IETF Logo Mail Archive

[dnsext] RFC3596: A/AAAA records and additional section processing

Jehan Pagès <jehan.marmottard@gmail.com> Fri, 04 March 2011 06:34 UTC

Return-Path: <jehan.marmottard@gmail.com>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 04D973A6906 for <dnsext@core3.amsl.com>; Thu, 3 Mar 2011 22:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.999
X-Spam-Level:
X-Spam-Status: No, score=-2.999 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EF3sR3Wehk99 for <dnsext@core3.amsl.com>; Thu, 3 Mar 2011 22:34:19 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 408973A692D for <dnsext@ietf.org>; Thu, 3 Mar 2011 22:34:19 -0800 (PST)
Received: by wyb42 with SMTP id 42so1952734wyb.31 for <dnsext@ietf.org>; Thu, 03 Mar 2011 22:35:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=f7qRkp83geeZpwFg3I5tXG0l+GKAIDYmeEdtAaeGgOE=; b=vz/8W+uTrD1meP3bQ+nUxyy33fy226V7kvAdTfdffL260leTRYUCp73iZ5Au+123JR CTgVCtE41bdZ9r65qDAtmdwmMeQlwFXZP8MoP+GUTJ0JRIlLfZf6JuknuTBKgT1p4YhK ST6x3+5uGMOC8iBO6YLrb0BhsIX5WDKLeRABU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=lcbAtAfi6cJG/8Z84LghKgFeNyAK4+V2oUq9wVncDRCV7eMlsDbh1b2l6xpfXTt+qK oUniihFnjrS7MvS2EZt7geeZwbQkbSeZCqIZoSIG4oYDfDtj86vvJ/3axzsZzX9PG3xP e6/2r5rxe5eF0QrB1XpKqnr8loL6PGCaQitV8=
MIME-Version: 1.0
Received: by 10.216.230.152 with SMTP id j24mr223218weq.81.1299220527399; Thu, 03 Mar 2011 22:35:27 -0800 (PST)
Received: by 10.216.171.131 with HTTP; Thu, 3 Mar 2011 22:35:27 -0800 (PST)
Date: Fri, 04 Mar 2011 15:35:27 +0900
Message-ID: <AANLkTik6zTfBcq129pX_uQC-adruhVGnk=CjRn29=fpt@mail.gmail.com>
From: Jehan Pagès <jehan.marmottard@gmail.com>
To: dnsext@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [dnsext] RFC3596: A/AAAA records and additional section processing
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Mar 2011 06:34:21 -0000

Hi all,

I have a small question about the IPv6 resource records extension (RFC3596).
As section 2.3 states:
« A type AAAA query does not trigger additional section processing. ». Fine.

But I noticed that some DNS servers (like the one installed on my
server, a bind 9.7.2) would return the A records in additional section
on a AAAA query and AAAA records in additional on A queries.
And when I thought about this, I realized it was a pretty good logics.
Usually when people will try to contact a server, they will want both
A and AAAA records.
So the question is: why wouldn't this be standard?
Thanks.

Jehan

v2.23.0 | Report a Bug | By Email