Re: [mif] DNS selection with HE-MIF
Keith Moore <moore@network-heretics.com> Sun, 03 February 2013 17:12 UTC
Return-Path: <moore@network-heretics.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF6E21F8889 for <mif@ietfa.amsl.com>; Sun, 3 Feb 2013 09:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.367
X-Spam-Level:
X-Spam-Status: No, score=-3.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-Zw5qH26MHg for <mif@ietfa.amsl.com>; Sun, 3 Feb 2013 09:12:58 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id B3CE721F867B for <mif@ietf.org>; Sun, 3 Feb 2013 09:12:58 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C986220722; Sun, 3 Feb 2013 12:12:57 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Sun, 03 Feb 2013 12:12:57 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=EBP69b667f1BvghjlU4ceG 6CbMI=; b=ImrU6wHuMGNDQjJAs1uPZNtZO67suJEPvo146ITOqRU/h0FMPAIQlu 7OSckpNq1AAfcA3z5E2pnDiPqdoDiyfMbuZyEwsjdffxhTzqtoCaEk/NqqwVdRsM KoThG3FGUHDTY7m3+B4WyhbrSsrHO23tXkYtiP32nV9VcFSNDSl9E=
X-Sasl-enc: aGmt5HhCxDd9TI1d3IN9n3X4UlfZcEG/u/H8Q1VTwsPD 1359911577
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id D4B954827D7; Sun, 3 Feb 2013 12:12:56 -0500 (EST)
Message-ID: <510E9A8C.6030103@network-heretics.com>
Date: Sun, 03 Feb 2013 12:12:44 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
References: <CAM+vMERak2vAoYFeSLRep2xjpm480qPjutyv4-tV=KtU0XO=fw@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B630747479BA9@mbx-01.win.nominum.com> <CAM+vMETvE==qUZO2_rhyUB+=ChUR4a9CoTCF+q=gBL2cRA+0UA@mail.gmail.com> <8D23D4052ABE7A4490E77B1A012B63074747BB1E@mbx-01.win.nominum.com> <510E8667.3020608@network-heretics.com> <510E910E.6090806@gmail.com> <8D23D4052ABE7A4490E77B1A012B63074747BDF8@mbx-01.win.nominum.com> <510E9246.1070502@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63074747BEED@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63074747BEED@mbx-01.win.nominum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "<mif@ietf.org>" <mif@ietf.org>
Subject: Re: [mif] DNS selection with HE-MIF
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 17:12:59 -0000
On 02/03/2013 11:48 AM, Ted Lemon wrote: > On Feb 3, 2013, at 11:37 AM, Keith Moore <moore@network-heretics.com> wrote: >> And IMO, it's far beyond a reasonable scope for this, or any, WG that is limited to a single area. And perhaps a traditional IETF WG isn't the right structure for tackling this kind of problem. > This seems like a fairly nonsensical statement. The IETF has areas, and working groups. It is frequently the case that work being done in a working group affects more than one area. The IETF has not burst into an explosion of pure energy as a result of the streams being crossed thus far. I suspect we are safe in the future as well. My view is that the Internet (with IETF's help) has been painting itself into increasingly smaller corners for at least 15 years now, maybe longer. NATs, DNS hacks, interception proxies, various kinds of packet filters, all basically make the Internet less predictable for applications, and thus increase development, operation, and support costs for everybody. Trying to work around them all just makes the Internet more complex without making it more functional. The IETF needs to get out of the habit of treating every problem as something that can be solved by spinning up a narrowly-focused working group, that functions just like every other working group because "that's the way we do things". I realize, of course, that MIF can't change IETF's habits. But if you're looking for a sane way forward, it's essential to realize that IETF's habits are a huge part of the problem. Otherwise you keep trying to use the same working habits to address problems that they fundamentally cannot address. > If you have some concrete proposal to make, I think it would be worth hearing it, but if you are just going to take pot shots, there's not much the rest of us can do except to try to continue getting work done while ducking your occasional volley. My proposal is to document the problems as best you can, and make concrete suggestions for areas in which the Internet architecture might be tweaked, but don't try to resolve the conflicts within MIF. Instead, ask IAB to look at the matter and provide IESG with advice as to how to proceed. Keith
- [mif] DNS selection with HE-MIF GangChen
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF GangChen
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF Keith Moore
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF Brian E Carpenter
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF Keith Moore
- Re: [mif] DNS selection with HE-MIF Keith Moore
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF Keith Moore
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF Michael Richardson
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF Brian E Carpenter
- Re: [mif] DNS selection with HE-MIF GangChen
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF GangChen
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF GangChen
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF GangChen
- Re: [mif] DNS selection with HE-MIF Ted Lemon
- Re: [mif] DNS selection with HE-MIF GangChen