Re: [DNSOP] Fwd: New Version Notification for draft-pan-dnsop-edns-isp-location-02.txt

Robert Edmonds <edmonds@mycre.ws> Fri, 28 July 2017 17:17 UTC

Return-Path: <edmonds@mycre.ws>
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 A6C0D131F6F for <dnsop@ietfa.amsl.com>; Fri, 28 Jul 2017 10:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-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 l2BRiJ08tUG8 for <dnsop@ietfa.amsl.com>; Fri, 28 Jul 2017 10:17:24 -0700 (PDT)
Received: from mycre.ws (mycre.ws [45.33.102.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52DC7131D15 for <dnsop@ietf.org>; Fri, 28 Jul 2017 10:17:24 -0700 (PDT)
Received: by chase.mycre.ws (Postfix, from userid 1000) id AE51312C190B; Fri, 28 Jul 2017 13:17:23 -0400 (EDT)
Date: Fri, 28 Jul 2017 13:17:23 -0400
From: Robert Edmonds <edmonds@mycre.ws>
To: Dave Lawrence <tale@dd.org>
Cc: Lanlan Pan <abbypan@gmail.com>, dnsop <dnsop@ietf.org>
Message-ID: <20170728171723.6vyqrtm5enan4ttg@mycre.ws>
References: <150025655295.32691.13544492065984079858.idtracker@ietfa.amsl.com> <CANLjSvVFOVa77Pp=LgVqJ31mMZLL27FyvTnnrDXHUjuscOFUmQ@mail.gmail.com> <22892.32000.730535.635648@gro.dd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <22892.32000.730535.635648@gro.dd.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/Ifx9HGXlPw9Bj42fbLYmm_9pnc8>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-pan-dnsop-edns-isp-location-02.txt
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: Fri, 28 Jul 2017 17:17:26 -0000

Hi,

Dave Lawrence wrote:
> Have you had any feedback from authority server implementers who are
> interested in using this? 

As an authority server implementer at a CDN -- we have no interest in
using anything like this.

> I'm having a hard time picturing many CDNs wanting to switch, in no
> small part because geo is not the only goal of mapping.  The
> < COUNTRY, AREA, ISP > tuple that is defined is insufficient.

Yes, as has been made clear in previous discussion on this document.

Even if it were sufficient, using only a <COUNTRY, AREA, ISP> tuple to
direct traffic makes it incumbent on the resolver operator to accurately
geolocate the client IP and faithfully transmit the result to the
authoritative operator. If the resolver operator is an ISP, this
proposal would give the ISP an enormous amount of counter- traffic
engineering power by spoofing the COUNTRY/AREA fields.

-- 
Robert Edmonds