Re: [DNSOP] I-D Action: draft-song-dnsop-tcp-primingexchange-00.txt

Paul Hoffman <paul.hoffman@vpnc.org> Thu, 27 November 2014 16:05 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212961A00BF for <dnsop@ietfa.amsl.com>; Thu, 27 Nov 2014 08:05:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.647
X-Spam-Level:
X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3E8GxpbkKmu0 for <dnsop@ietfa.amsl.com>; Thu, 27 Nov 2014 08:05:04 -0800 (PST)
Received: from proper.com (Hoffman.Proper.COM [207.182.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB42D1A009E for <dnsop@ietf.org>; Thu, 27 Nov 2014 08:05:03 -0800 (PST)
Received: from [10.20.30.90] (142-254-17-143.dsl.dynamic.fusionbroadband.com [142.254.17.143]) (authenticated bits=0) by proper.com (8.14.9/8.14.7) with ESMTP id sARG50k2094760 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Nov 2014 09:05:02 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 142-254-17-143.dsl.dynamic.fusionbroadband.com [142.254.17.143] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAAObRXJM1Ucu3RtJCZPaw2ss0+ZBXxnDyyUvshuAnqEQYEi2XA@mail.gmail.com>
Date: Thu, 27 Nov 2014 08:05:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FFAC9976-D502-4AAE-AB7D-8A869CB140AB@vpnc.org>
References: <20141126190228.2644.32272.idtracker@ietfa.amsl.com> <CAAObRXJM1Ucu3RtJCZPaw2ss0+ZBXxnDyyUvshuAnqEQYEi2XA@mail.gmail.com>
To: Davey Song <songlinjian@gmail.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/dE2WUO2NIBAYh4LfzEl5MyMDEP0
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] I-D Action: draft-song-dnsop-tcp-primingexchange-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 27 Nov 2014 16:05:10 -0000

On Nov 26, 2014, at 11:18 AM, Davey Song <songlinjian@gmail.com> wrote:
> Hi folks, I just post a draft on Priming Exchange over TCP. Comments are welcome!

The proposed solution is not needed as long as the resolver that using the priming exchange can fall back to TCP. A different approach to the document would be:

   Motivation: The root zone is longer than 512 octets,
   so responses to priming queries are truncated.

   Requirement: All resolvers that perform priming
   queries MUST be able to use TCP as specified in
   RFC 1035 when performing the priming query.

That should be an RFC of less than two pages, and would not involve making priming queries special enough to require a protocol change for them.

--Paul Hoffman