Re: [DNSOP] [dnsext] Re: Computerworld apparently has changed DNS protocol

David Conrad <drc@virtualized.org> Thu, 05 November 2009 01:09 UTC

Return-Path: <drc@virtualized.org>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0752A3A6A4B for <dnsop@core3.amsl.com>; Wed, 4 Nov 2009 17:09:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level:
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 y4U+0rmm96-g for <dnsop@core3.amsl.com>; Wed, 4 Nov 2009 17:09:18 -0800 (PST)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id 4A9C23A679F for <dnsop@ietf.org>; Wed, 4 Nov 2009 17:09:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by virtualized.org (Postfix) with ESMTP id D7E308E00DB; Wed, 4 Nov 2009 17:09:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at virtualized.org
Received: from virtualized.org ([127.0.0.1]) by localhost (trantor.virtualized.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0+c5UZdrEXlr; Wed, 4 Nov 2009 17:08:25 -0800 (PST)
Received: from [192.168.1.2] (c-24-130-210-17.hsd1.ca.comcast.net [24.130.210.17]) by virtualized.org (Postfix) with ESMTP id F0E1A8E00AD; Wed, 4 Nov 2009 17:08:24 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: text/plain; charset="us-ascii"
From: David Conrad <drc@virtualized.org>
In-Reply-To: <d791b8790911041345u378d9525i1cfc48251fe2d132@mail.gmail.com>
Date: Wed, 04 Nov 2009 17:08:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6C16EFB-9E48-4C85-BF76-B16247B21B5F@virtualized.org>
References: <200911041858.TAA24009@TR-Sys.de> <FD44BF39-5B62-4689-AC6D-8DFFAF340EA1@icsi.berkeley.edu> <20091104192634.GA31981@vacation.karoshi.com.> <d791b8790911041141k71066fa9nede54d5dff9394fa@mail.gmail.com> <8643905B-B73B-4D87-A1CE-F218E4BA9FD4@virtualized.org> <d791b8790911041345u378d9525i1cfc48251fe2d132@mail.gmail.com>
To: Matthew Dempsky <matthew@dempsky.org>
X-Mailer: Apple Mail (2.1077)
Cc: dnsop WG <dnsop@ietf.org>
Subject: Re: [DNSOP] [dnsext] Re: Computerworld apparently has changed DNS protocol
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Nov 2009 01:09:19 -0000

Matthew,

On Nov 4, 2009, at 1:45 PM, Matthew Dempsky wrote:
> On Wed, Nov 4, 2009 at 12:04 PM, David Conrad <drc@virtualized.org> wrote:
>> On Nov 4, 2009, at 11:41 AM, Matthew Dempsky wrote:
>>> On Wed, Nov 4, 2009 at 11:26 AM,  <bmanning@vacation.karoshi.com> wrote:
>>>>       The current deployment plan is to stage things to push out large responses
>>>>       early - prior to having any actual DNSSEC usable data ... ostensibly to
>>>>       flush out DNSmtu problems.
>>> 
>>> Is this plan to push out large responses indiscriminately, or only in
>>> response to queries with DO=1?
>> 
>> We're not planning on breaking the DNS protocol.  DNSSEC responses will only be provided if DO=1 (currently about 70% of the queries hitting the root have DO=1).
> 
> I'd appreciate if someone could clarify what the "large responses"
> that will preexist "actual DNSSEC usable data" that Bill Manning is
> referring to are.

They are signed responses, but signed with a 'deliberately unvalidatable root key'.

> It's unclear to me whether it's still technically
> DNSSEC data and hence would require a client to send DO=1,

Yes, it is DNSSEC data and will only be returned if DO=1.  Clients that do not set DO=1 will not receive the DNSSEC responses.

> or if it
> will be something like large additional section TXT records or just
> trailing bytes.

No.

Regards,
-drc