IETF Logo Mail Archive

Re: [dnsext] WGLC: draft-eastlake-dnsext-xnamercode-03.txt

Alex Bligh <alex@alex.org.uk> Tue, 26 April 2011 09:24 UTC

Return-Path: <alex@alex.org.uk>
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 17D00E06A1 for <dnsext@ietfa.amsl.com>; Tue, 26 Apr 2011 02:24:31 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vgzLeeRdHWGT for <dnsext@ietfa.amsl.com>; Tue, 26 Apr 2011 02:24:30 -0700 (PDT)
Received: from mail.avalus.com (mail.avalus.com [89.16.176.221]) by ietfa.amsl.com (Postfix) with ESMTP id 889B6E069A for <dnsext@ietf.org>; Tue, 26 Apr 2011 02:24:30 -0700 (PDT)
Received: from [192.168.100.15] (87-194-71-186.bethere.co.uk [87.194.71.186]) by mail.avalus.com (Postfix) with ESMTPSA id 356E0C560C7; Tue, 26 Apr 2011 10:24:27 +0100 (BST)
Date: Tue, 26 Apr 2011 10:24:27 +0100
From: Alex Bligh <alex@alex.org.uk>
To: Tony Finch <dot@dotat.at>, George Barwood <george.barwood@blueyonder.co.uk>
Message-ID: <A9DDE2FB59163318F771DBD4@Ximines.local>
In-Reply-To: <alpine.LSU.2.00.1104261021300.18882@hermes-2.csi.cam.ac.uk>
References: <20110413151032.GK24471@shinkuro.com> <20110425190533.GE1943@shinkuro.com> <6995342773AA4DDC9ED528F8F9D4260F@local> <alpine.LSU.2.00.1104261021300.18882@hermes-2.csi.cam.ac.uk>
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: dnsext@ietf.org
Subject: Re: [dnsext] WGLC: draft-eastlake-dnsext-xnamercode-03.txt
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Alex Bligh <alex@alex.org.uk>
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, 26 Apr 2011 09:24:31 -0000

--On 26 April 2011 10:22:07 +0100 Tony Finch <dot@dotat.at> wrote:

>> where the meaning of the last sentence is not entirely clear.
>
> I guess the "or" means "which is expected to be"

If nothing else, that demonstrates that the word "unambiguously" in
the draft text below is overstating the case:

"[RFC1035] unambiguously states that the AA bit is to be set based on
   whether the server providing the answer with the first owner name in
   the answer section is authoritative."


-- 
Alex Bligh

v2.23.0 | Report a Bug | By Email