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

Colm MacCárthaigh <colm@allcosts.net> Thu, 28 January 2010 21:16 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 A5D7428C113; Thu, 28 Jan 2010 13:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.677
X-Spam-Level:
X-Spam-Status: No, score=-105.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 h3fyMw6etomf; Thu, 28 Jan 2010 13:16:19 -0800 (PST)
Received: from psg.com (psg.com [147.28.0.62]) by core3.amsl.com (Postfix) with ESMTP id BF48C28C10C; Thu, 28 Jan 2010 13:16:19 -0800 (PST)
Received: from majordom by psg.com with local (Exim 4.71 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1Nabe7-0002NT-1g for namedroppers-data0@psg.com; Thu, 28 Jan 2010 21:11:23 +0000
Received: from [209.85.216.204] (helo=mail-px0-f204.google.com) by psg.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <colm@allcosts.net>) id 1Nabe5-0002N1-7b for namedroppers@ops.ietf.org; Thu, 28 Jan 2010 21:11:21 +0000
Received: by pxi42 with SMTP id 42so1643393pxi.5 for <namedroppers@ops.ietf.org>; Thu, 28 Jan 2010 13:11:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.141.2.9 with SMTP id e9mr5247959rvi.239.1264713080279; Thu, 28 Jan 2010 13:11:20 -0800 (PST)
In-Reply-To: <58729.1264707908@nsa.vix.com>
References: <7c31c8cc1001271556w4918093er6e94e07cb92c4dc4@mail.gmail.com> <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>
Date: Thu, 28 Jan 2010 21:11:20 +0000
Message-ID: <6f5b6fe71001281311g6e1fdd05o84ba64837813a6fd@mail.gmail.com>
Subject: Re: [dnsext] Re: I-D ACTION:draft-vandergaast-edns-client-ip-00.txt
From: Colm MacCárthaigh <colm@allcosts.net>
To: Paul Vixie <vixie@isc.org>
Cc: namedroppers@ops.ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
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/>

On Thu, Jan 28, 2010 at 7:45 PM, Paul Vixie <vixie@isc.org> wrote:>
> i love how somebody else (CDN providers) violate all existing assumptions
> (by creating requestor-specific DNS replies) which then makes the Internet
> work "less well" for lots of people... who are then constrained from doing
> what were previously reasonable things (like using distant recursive servers).

Can you expand upon the "less well" ?

>> Do you want third-party DNS providers to not suck for youtube, akamai,
>> Google, and a good fraction of the net people use every day?  If so, you
>> need this.
>
> if youtube and akamai and google want to suck, let them suck.  they weren't
> the first movers and they won't be the last and redrawing the protocol to
> support their flawed technical model is not in the global system's interest.

Surely a large point of extension mechanisms is to cater for unusual
and ad-hoc circumstances in an interoperable way?

> this incoherency should be dealt with more harshly, perhaps by minimizing
> TTL to 5 minutes, and sharing a single DNS cache across global providers.

Why?

> any CDN who relies on what i call "stupid DNS tricks" to deliver their
> advantage should upgrade to something at the WWW layer, and leave DNS alone.
>
> especially with DNSSEC coming.

This I-D seems interoperable with DNSSEC, even NSEC3, on my reading.

-- 
Colm