Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt

Martin Barry <marty@supine.com> Fri, 29 January 2010 09:12 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBED53A69FA; Fri, 29 Jan 2010 01:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghpWG9172xDz; Fri, 29 Jan 2010 01:12:27 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id 7D5AE28C132; Fri, 29 Jan 2010 01:12:27 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1NamnT-000Ffh-C3 for namedroppers-data0@psg.com; Fri, 29 Jan 2010 09:05:47 +0000
Received: from [64.71.152.85] (helo=tigger.mamista.net) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from <marty@supine.com>) id 1NamnP-000Ff1-Tw for namedroppers@ops.ietf.org; Fri, 29 Jan 2010 09:05:43 +0000
Received: by tigger.mamista.net (Postfix, from userid 1001) id AFB1C110783; Fri, 29 Jan 2010 20:05:42 +1100 (EST)
Date: Fri, 29 Jan 2010 20:05:42 +1100
From: Martin Barry <marty@supine.com>
To: namedroppers@ops.ietf.org
Subject: Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt
Message-ID: <20100129090542.GB8361@tigger.mamista.net>
References: <6184.1264657589@nsa.vix.com> <4966825a1001280807i768a33ccs98f809366bce33d8@mail.gmail.com> <48894.1264695230@nsa.vix.com> <50A91B20-5AC1-4819-91ED-E5141F068D48@wiggum.com> <52065.1264699087@nsa.vix.com> <FDD5D1103B8EA4D13C4A2C4C@Ximines.local> <EEAAE4BF-BBA9-4141-BECC-A8440715597F@icsi.berkeley.edu> <58729.1264707908@nsa.vix.com> <6f5b6fe71001281311g6e1fdd05o84ba64837813a6fd@mail.gmail.com> <64415.1264714867@nsa.vix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <64415.1264714867@nsa.vix.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

Just a small comment on "dns-tricks" versus "routing-tricks".

$quoted_author = "Paul Vixie" ;
> 
> because i like caching, and because i don't think the dns q-tuple should be
> expanded to include more elements.  because dns is a phat target for folks
> whose business models require cost-shifting from their edge to our middle.
> oh hell, i said all this in the acm queue article:
> 
> http://queue.acm.org/detail.cfm?id=1647302

"Anycast TCP is also in use by a few CDNs and works at least as well as any
DNS-layer solution. Anycast is stable for minutes or hours at a time, so
it's rare for two TCP packets to the same destination to reach different
anycast contributors."

Anycast usually implies a /24 used for a single service or group of
services. This limits "routing-tricks" to those that have a spare /24, speak
BGP in multiple locations and can justify polluting the global routing table
with another /24.

Conversely "dns-tricks" can be, and are, used by those who don't meet the
above criteria. The only limitations are having authorative servers capable
of applying the "tricks".

Both imply some burden shifting in order to provide "better" service to the
end user.

cheers
Marty