IETF Logo Mail Archive

Re: [DNSOP] [dns-privacy] FW: New Version Notification for draft-pan-dnsop-edns-isp-location-00

Ask Bjørn Hansen <ask@develooper.com> Tue, 21 March 2017 08:11 UTC

Return-Path: <ask@develooper.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 E894C12965B for <dnsop@ietfa.amsl.com>; Tue, 21 Mar 2017 01:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level:
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 3fa2JWiyVNHG for <dnsop@ietfa.amsl.com>; Tue, 21 Mar 2017 01:11:17 -0700 (PDT)
Received: from mbox1.develooper.com (mbox1.develooper.com [207.171.7.178]) by ietfa.amsl.com (Postfix) with ESMTP id B0CA1129671 for <dnsop@ietf.org>; Tue, 21 Mar 2017 01:11:15 -0700 (PDT)
Received: from mbox1.develooper.com (mbox1.develooper.com [127.0.0.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mbox1.develooper.com (Postfix) with ESMTPS id 2F01C175F03 for <dnsop@ietf.org>; Tue, 21 Mar 2017 01:11:14 -0700 (PDT)
Received: (qmail 31120 invoked from network); 21 Mar 2017 08:11:13 -0000
Received: from c-67-188-112-34.hsd1.ca.comcast.net (HELO ?10.0.200.101?) (ask@mail.dev@67.188.112.34) by smtp.develooper.com with ESMTPA; 21 Mar 2017 08:11:13 -0000
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Ask Bjørn Hansen <ask@develooper.com>
In-Reply-To: <CANLjSvUJfU1cafGXHyg=DuCnhm09mBm5z4ve2_g6j2ONgt2tRQ@mail.gmail.com>
Date: Tue, 21 Mar 2017 01:11:04 -0700
Cc: Barry Raveendran Greene <bgreene@senki.org>, dns-privacy@ietf.org, dnsop <dnsop@ietf.org>, "fuyu@cnnic.cn" <fuyu@cnnic.cn>
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBCEC002-D8D9-498E-8567-507181F9215E@develooper.com>
References: <000f01d29dfe$50b6b190$f22414b0$@cn> <CANLjSvXGO3rSpqb7hzwmV=vfm=UTHnQYqfBmt=uD9Mi8cL59Jg@mail.gmail.com> <16B293AD-27A2-4A6D-8A96-7CD847B59708@senki.org> <CANLjSvUJfU1cafGXHyg=DuCnhm09mBm5z4ve2_g6j2ONgt2tRQ@mail.gmail.com>
To: Lanlan Pan <abbypan@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SXroPQSHtD7fh9GWGIONZhQ2WFY>
Subject: Re: [DNSOP] [dns-privacy] FW: New Version Notification for draft-pan-dnsop-edns-isp-location-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Mar 2017 08:11:19 -0000

> On Mar 20, 2017, at 0:49, Lanlan Pan <abbypan@gmail.com> wrote:
> 
> Everyone has known that physical location and the topology of content delivery DO NOT MATCH.
> As last mail reply to Warren, my proposal can offer the SAME critical information for authoritative server to make tailored response decision as ECS's client subnet.
> Because in database such as maxmind,  ECS (client subnet) can be map into <AS number,  country, province, ISP>, which also guide network topology.
> Therefore, if ECS has ANY value for optimizing content delivery on the Internet, then EIL has.
> 
> For example，If ECS is tell AUTH :  the query is from 114.240.0.0/24. The AUTH knows that ECS(114.240.0.0/24) is indicated (CHINA, BEIJING, UNICOM), which is not only geolocation, but also contains network topology information. Then AUTH can return satisfied ip address according to the topology of content delivery.

Except for very small networks, the network topology isn’t just the name of the provider. I suspect that if you took away all the geoip type lookups the larger content delivery systems would work fine; but if you did the opposite (what you are proposing with EIL) they would not.

I believe Netflix has public information about how their OpenConnect system uses BGP and network topology information.


Ask (speaking only for myself)

v2.23.0 | Report a Bug | By Email