IETF Logo Mail Archive

Re: [mif] DNS selection with HE-MIF

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 03 February 2013 16:32 UTC

Return-Path: <brian.e.carpenter@gmail.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 713F121F8447 for <mif@ietfa.amsl.com>; Sun, 3 Feb 2013 08:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.13
X-Spam-Level:
X-Spam-Status: No, score=-101.13 tagged_above=-999 required=5 tests=[AWL=0.561, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 uNNqeZhgtqUc for <mif@ietfa.amsl.com>; Sun, 3 Feb 2013 08:32:17 -0800 (PST)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id B9B9C21F843E for <mif@ietf.org>; Sun, 3 Feb 2013 08:32:16 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id ez12so2134650wid.6 for <mif@ietf.org>; Sun, 03 Feb 2013 08:32:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qstMXA9jN2Nv86y80/IJVYiNWYOcUCO3F84whA9HjFE=; b=EZhhLr/0hGBiHGJG1083njenbwKjRMxudvtcH0BprHtKWP+lnHPlDxozhHXHZI2/si qkhLv5QES7AZGwmTkmBm6xqN0PO9n9tBCKD+LY60H7v5xYqAogFFanHAf5dk74RQ8HV9 hjaAT/UaMIb1OdHNX7J5HKvzBccC1CDQ2+VQwM9phN2KZN1OtEFaPmMKZAuC674AZorK ywQbZvVCIUz8fxLwXgeIePwypN3ltGht9knL2WRWNaPMpgzzXocvuhDkEpmYYWzFzlhC hXLt3KDcjUnHGKTWBSsb4zXtt4zc+qQ2tyUgCfOsEyot9RnVkSh5POIm+7JGhpCBXyfR TfJg==
X-Received: by 10.194.119.5 with SMTP id kq5mr30621541wjb.48.1359909135962; Sun, 03 Feb 2013 08:32:15 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-151.as13285.net. [2.102.218.151]) by mx.google.com with ESMTPS id eo10sm16445129wib.9.2013.02.03.08.32.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 03 Feb 2013 08:32:15 -0800 (PST)
Message-ID: <510E910E.6090806@gmail.com>
Date: Sun, 03 Feb 2013 16:32:14 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.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>
In-Reply-To: <510E8667.3020608@network-heretics.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: 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 16:32:17 -0000

On 03/02/2013 15:46, Keith Moore wrote:
> On 02/03/2013 10:04 AM, Ted Lemon wrote:
>> This is why when I've discussed this issue in the past, I've always
>> argued that each provisioning domain needs to be treated separately.  
>> We should not look up names in one provisioning domain and use them in
>> another; if we want to try connecting across multiple provisioning
>> domains, we should do DNS lookups on each such provisioning domain,
>> and use the results we get only for connecting within that
>> provisioning domain.
> Problem is, this is bad for the Internet architecture, as it basically
> encourages using DNS as a routing protocol.

It also means that the resolver performing the lookup needs to
understand this concept of "provisioning domain" and to know which
such domain(s) matter for the lookup in question.

My big book of Internet magic doesn't seem to explain how the
resolver would know this, or how the RR would be tagged to
designate which domain(s) it applies to.

    Brian

v2.23.0 | Report a Bug | By Email