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

Davey Song <songlinjian@gmail.com> Fri, 28 November 2014 08:22 UTC

Return-Path: <songlinjian@gmail.com>
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 407C61A1AA2 for <dnsop@ietfa.amsl.com>; Fri, 28 Nov 2014 00:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 n3Sz1EDEwHLM for <dnsop@ietfa.amsl.com>; Fri, 28 Nov 2014 00:22:04 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04DB61A1AA0 for <dnsop@ietf.org>; Fri, 28 Nov 2014 00:22:04 -0800 (PST)
Received: by mail-qg0-f48.google.com with SMTP id q107so4466113qgd.35 for <dnsop@ietf.org>; Fri, 28 Nov 2014 00:22:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3+gHnQPIxVZWka4vX2cgjHKz/HkE5YO55Me6SHXYxFA=; b=ZWz0fGw0rBo/DZEeQk7biaxKpUsCrhBKS0D5bbewFeA3E0KtA2k9LvZbvrfnxHIXP7 umBbYrP1LzQiwx84n+pEU3nGC8Qiz1etMTLlaLI9nbqjKiORvKuSJf/zw4MbcdHgkwMi SC9ITpvp4KdN2ODmV8rlFRLbj6oy1v5Jda5PK4kqhPVKEI9RGn6XdXc+MstwW9EzY8q6 ZAOe5btFFtU7x677sHVCRbzAm+L0ZLn+s1cU1WaQtxO/FafLMw2MTja9GagP1IDSGfaK NctG169edPxaY9Gw7Wr0p48mNWipj7sU9gtCWFnEr7fmUuCKdkAW+ODyL9aAkBt3GpQG O/nQ==
MIME-Version: 1.0
X-Received: by 10.229.248.132 with SMTP id mg4mr60057615qcb.29.1417162923225; Fri, 28 Nov 2014 00:22:03 -0800 (PST)
Received: by 10.140.91.202 with HTTP; Fri, 28 Nov 2014 00:22:03 -0800 (PST)
In-Reply-To: <54782272.4080903@redbarn.org>
References: <20141126190228.2644.32272.idtracker@ietfa.amsl.com> <CAAObRXJM1Ucu3RtJCZPaw2ss0+ZBXxnDyyUvshuAnqEQYEi2XA@mail.gmail.com> <54768F63.9070509@redbarn.org> <CAAObRXLhG0Wfj2eC=+Xb+jnO0fLbiSAvVJti5VtpGANRyHC22g@mail.gmail.com> <54782272.4080903@redbarn.org>
Date: Fri, 28 Nov 2014 16:22:03 +0800
Message-ID: <CAAObRXJoXe4ER6nivN-4dJhb8+Q2vfAtbcz9FBEdf4XHPRnQDw@mail.gmail.com>
From: Davey Song <songlinjian@gmail.com>
To: Paul Vixie <paul@redbarn.org>
Content-Type: multipart/alternative; boundary="001a11360328a0b9300508e6f43e"
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/Salcpf3r_XeE3czrJTHDeaK8ls4
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] Fwd: 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: Fri, 28 Nov 2014 08:22:06 -0000

On Fri, Nov 28, 2014 at 3:21 PM, Paul Vixie <paul@redbarn.org> wrote:

>
> for example, if 13 is good, would 130 (10X) or 1300 (100X) be better?
> even with 1300 root name servers, the fallback to TCP after TC=1 in a
> priming query (even with EDNS) would only add one extra round trip over
> the three that are required to run a TCP query. since priming queries
> are uncommon, i still don't see why that first round trip is worth
> avoiding.
>
> At least we can try Fast Open TCP on it to save more round for performance
purpose .

Priming exchange is special because this exchange lead the people to the
unique name space of Internet. If we share the same dream of "One World One
Internet" , any extra effort is deserved to protect its resiliency in IPv6
network(section 2.1), integrity with fully signed(section 2.2) and more NS
server to enable more participation of  CDOs. (section 2.3)

>
> however, the systemic complexity of all those RDNS servers performing
> all those measurements seems like cause for concern. with 1300 root name
> servers, it would take 1300 referrals for any given RDNS server to learn
> which root name server was closest to it. unless all 1300 of those
> servers are widely anycast, then many of those initial 1300 referrals
> would have suboptimal round trip times. also with that many servers,
> error theory predicts that some number of them will be unreachable,
> causing retries that add to the total number of referral events required
> to locate the closest (by RTT) root server.
>
>
The difficulty of comparing 1300 referrals triggers me to think of
introducing special measures to Priming Exchange, such as the mechanism
like CDN/smart DNS to return a set of address (maybe less than 5) best suit
for the resolver.  Well, if that possible, that requirement makes Priming
Exchange more special because it break the  atomic principle of DNS.


>
> i share these research questions for four reasons.
>
> first, ZDNS and BII are ideally suited to investigate this matter in
> your test bed.
>

> Thanks Paul. our discussion broadens and enrich our thinking on section
2.3 issue. We  will continue working on that to explore the space for
the question and answer .

As to the draft,  be aware the proposal  is not particularly for the root
 NS number issue.   Actually I realized in advance that if section 2.3 is
too controversial I will think of remove or amend it.

Davey

> --
> Paul Vixie
>