Re: [DNSOP] [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt

Davey Song <songlinjian@gmail.com> Tue, 25 September 2018 09:09 UTC

Return-Path: <songlinjian@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB16713114A; Tue, 25 Sep 2018 02:09:26 -0700 (PDT)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QWRMvV6XOhCU; Tue, 25 Sep 2018 02:09:24 -0700 (PDT)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65F2D130F24; Tue, 25 Sep 2018 02:09:24 -0700 (PDT)
Received: by mail-qt1-x82e.google.com with SMTP id l16-v6so12026838qtq.10; Tue, 25 Sep 2018 02:09:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lASZSwvDTek2PBdiKxvcOvFKp1r/UdQ7Jsn1sijf2SQ=; b=hmRG/VvGVYFafdHO98vpLNiKoFP5Kkt1DBpJsNwWXaXEU3qCTloRHcv3vEXZC80HJJ OsMklCadW9HJ0JWfrAIXYuk6LWUWliCnV/s4fr3YsG+NS3H9pZ9pF+cCMPhDDIy6F3dQ rwn3zvy8O71Ho7QmkL7i//locmhuf2OdTdNLRT3WJWl4BJJjopAPG/ia49TMYXLoWgAW l0rWg+tq8YRywFeILaiXpWArZTLm+Rnx3N8LJ7Ya+yFDYseGjOj2OQm9htUQexRrnouf W8d+zzUW6FJBBNWSoZI+VOvbGewrDm8YnyXDNcN91ekGV3Olpa1SBrtqe5zjqDuvZjA5 JLUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lASZSwvDTek2PBdiKxvcOvFKp1r/UdQ7Jsn1sijf2SQ=; b=fkDOVy3x9kNxR/b6XX9vvt3PoRuu6ptaSaUXW+ux4N8SxKk0s1ZucD6kGad1K1c+QJ DCSWuKUsOHK8ug4arGRUBQlWvetcUZrejzhcjHvWLJ7sm5FoS/GAIRABrJzqHCcEsZ0U Wi0huQlKAvsqIn6Ms0rwTWKleTveEUX0wzXXVp2w6lK0Kj+x1Tl9IkXSHbPGrz460xkX vL3kxJMZmysmYyaehfP05ilZDsArdSKUIdc3k2Ljiw3qQmFBldmCrWxgr6yKEVq6u41+ rwT72Sb+8OrZ+hD6D7DppOZYzZ3j7jC1GSlnjakRA1qFEf+W5ir0ZPSBzKj+b7ruM8GZ whag==
X-Gm-Message-State: ABuFfoiR6b3DsXid8iw2upvpEQ3E6HbaCdwj7HnTsNCUxrsRd2irUO8i 9Kfv68S1OoKtjjnfxakvD88LRv6v+4uwet2b3Lw=
X-Google-Smtp-Source: ACcGV63OwysZDGkwbeukmolAyKoFOLR+B4qjsCaQE+4peJ8vmwKarE353qaY89YUFvND0W3mXnh/ne4lNzEePMEELBs=
X-Received: by 2002:ac8:3414:: with SMTP id u20-v6mr17402qtb.237.1537866563454; Tue, 25 Sep 2018 02:09:23 -0700 (PDT)
MIME-Version: 1.0
References: <153751052820.5339.10049404273601155140.idtracker@ietfa.amsl.com> <CAAObRXLWpXVbPyyxuzJH8osi+R1rdV8N8=Woqvq3UR9nk8kDaA@mail.gmail.com> <CAJE_bqd4jjeZy9Stp-v6O0VOyvEJiE9vW1BLuy-wzqPGvDagoQ@mail.gmail.com> <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
In-Reply-To: <CAAObRX+6ktcD8i_aToKbX7UJoSPT0NMPV0xKqT8-k+7_d0R5Nw@mail.gmail.com>
From: Davey Song <songlinjian@gmail.com>
Date: Tue, 25 Sep 2018 17:09:13 +0800
Message-ID: <CAAObRXKVVu3qkBGAdRzXaX1=qr498__Fg8hhqWPg3uEDFxm2Ow@mail.gmail.com>
To: 神明達哉 <jinmei@wide.ad.jp>
Cc: v6ops@ietf.org, dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003a0b390576ae7666"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DAyzuIHIn_ZVl6VmvdMWr03DIQU>
Subject: Re: [DNSOP] [v6ops] Fwd: New Version Notification for draft-v6ops-xie-network-happyeyeballs-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 25 Sep 2018 09:09:27 -0000

To get to know the current status of HE , I did a simple test on my handy
devices visit top 20 website or open existing apps (currently only DNS). I
captured AAAA&A DNS query pairs (intervel less than 10s) and count HE query
pairs whoes interval less than 100ms. There is a prelimiary result:

1) My laptop with web browsers (Chrome, firfox, Sogou, QQ, 360). All
browers support HE in DNS in which  more than 90% AAAA&A query pairs are HE
query pairs.
2) My Andriod phone(V7.1.1).  262 AAAA&A query pairs out of  802 pairs . It
means only 32.6% DNS queries supported by HE. Not 32.6% Apps on my phone,
because some Apps may sent more DNS queries than others. I made a
statisitcs on interval of all AAAA& A pairs (statistics if no HE pairs
included), the average interval is 409ms (534ms), the median delay is
198ms(324ms), and the maximum is 7,135ms. If hostname resolution is not
support HE, the connection attampt will also be delayed accrodingly.
3) My ipad (V11.4.1).  1208 AAAA& A query pairs out of 1216 pairs. It means
more than 99% DNS queries supported by HE. It is true that IOS asynchronous
DNS API. But it is unkonwn on how many apps make connection asynchronously.
It will be investigated later.

In conlusion, HE is not widely supported at least in Android  platform.
Large companies can invest and implement it for their users. But it is not
fair for small Apps providers to endure such competitive disadvantage due
to IPv6 deployment.

- In general, I wouldn't be excited about placing such complicated
>>   functionality in the network rather than end hosts.  Sometimes it
>>   may be justified as a least evil option, but the current description
>>   of the draft didn't fully convince me
>>
>
> Before I put down this draft, I talked with some CPs (content/app
> providers) and ISPs, they have motivations and requirement on this.  One
> example is Tencent, they are planning to deploy a complicated measurement
> network to info their Apps (with a SDK ) which address family they should
> try first (their apps use dns over http).  I'm told that Tencent think HE
> implemented on each client is too complicated (they have comlicated apps)
> and resource consuming. ISP's motivation is easy to understood, they always
> try to improve their network connenctivity on both IPv4 and IPv6. I have no
> more comment on your saying of evil option:) Any technology can be used as
> evil purpose I think.
>


Davey