IETF Logo Mail Archive

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

Barry Raveendran Greene <bgreene@senki.org> Thu, 23 March 2017 18:06 UTC

Return-Path: <bgreene@senki.org>
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 3ECB8129B49 for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 11:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level:
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=unavailable 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 shefEPX11-YH for <dnsop@ietfa.amsl.com>; Thu, 23 Mar 2017 11:06:39 -0700 (PDT)
Received: from smtp85.ord1c.emailsrvr.com (smtp85.ord1c.emailsrvr.com [108.166.43.85]) (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 C5F55129B15 for <dnsop@ietf.org>; Thu, 23 Mar 2017 11:06:39 -0700 (PDT)
Received: from smtp3.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id B5E17A0457; Thu, 23 Mar 2017 14:06:36 -0400 (EDT)
X-Auth-ID: bgreene@senki.org
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: bgreene-AT-senki.org) with ESMTPSA id 47D98A0443; Thu, 23 Mar 2017 14:06:36 -0400 (EDT)
X-Sender-Id: bgreene@senki.org
Received: from [172.16.1.5] (c-73-92-124-43.hsd1.ca.comcast.net [73.92.124.43]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Thu, 23 Mar 2017 14:06:36 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Barry Raveendran Greene <bgreene@senki.org>
In-Reply-To: <CANLjSvWMYt1khfETApcW4Wt3aourPmhY-7Kz3Jrxjv4x89=3HA@mail.gmail.com>
Date: Thu, 23 Mar 2017 11:06:35 -0700
Cc: Ask Bjørn Hansen <ask@develooper.com>, "fuyu@cnnic.cn" <fuyu@cnnic.cn>, dns-privacy@ietf.org, dnsop <dnsop@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3CD9E11E-F2C5-4871-8D6F-019317C8D983@senki.org>
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> <BBCEC002-D8D9-498E-8567-507181F9215E@develooper.com> <CANLjSvXA03qGN9TZ2oON7bJfygU7Uzor6H3ku83E_NhA3FBa7A@mail.gmail.com> <3C0E763C-4C7F-4A63-A178-58F2AD77D3AC@develooper.com> <CANLjSvWMYt1khfETApcW4Wt3aourPmhY-7Kz3Jrxjv4x89=3HA@mail.gmail.com>
To: Lanlan Pan <abbypan@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/KPxO_dB9mxpKBkRktbNyi3KWTks>
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: Thu, 23 Mar 2017 18:06:42 -0000

> On Mar 21, 2017, at 11:38 PM, Lanlan Pan <abbypan@gmail.com> wrote:
> 
> However, if you know about the geolocation <COUNTRY, PROVINCE, ISP>,  you can make a better response, most of time, is the best response too.

Your statement is not matching the operational realities I live in. I understand how mapping is done in my current environment. I understand how it is done in many of my peer CDNs. I also understand the tools I would need to measure better path calculations. Everything is in IP, RIPs, FIBs, AS Patch, system load, content availability, etc. Knowing that it is in Palo Alto California is not something useful.

What is needed is the allocated IP block to start the mapping determination. Then every CDN does their “secret sauce” to delver the best customer experience. Geographic location is just not one of those factors. ECS delivers this now.

v2.23.0 | Report a Bug | By Email