IETF Logo Mail Archive

Re: [mif] DNS selection with HE-MIF

Ted Lemon <Ted.Lemon@nominum.com> Sun, 03 February 2013 16:35 UTC

Return-Path: <Ted.Lemon@nominum.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 749E121F86C1 for <mif@ietfa.amsl.com>; Sun, 3 Feb 2013 08:35:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level:
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 7fQzZ9+6To0n for <mif@ietfa.amsl.com>; Sun, 3 Feb 2013 08:35:20 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id E5D5C21F8464 for <mif@ietf.org>; Sun, 3 Feb 2013 08:35:19 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUQ6Rx5TY2+pNGxxPhUrWBBkaOl3cnEkF@postini.com; Sun, 03 Feb 2013 08:35:19 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 936961080A2 for <mif@ietf.org>; Sun, 3 Feb 2013 08:35:19 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8AB46190043; Sun, 3 Feb 2013 08:35:19 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 3 Feb 2013 08:35:13 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [mif] DNS selection with HE-MIF
Thread-Index: AQHOAhiC0CZRnojC20SeBNCskG9mTphowXmAgAALy4CAAAyyAIAAANUA
Date: Sun, 03 Feb 2013 16:35:12 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63074747BDF8@mbx-01.win.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>
In-Reply-To: <510E910E.6090806@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C20F1F214A5C0A4EB7CBB6E88D2933A5@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mif@ietf.org>" <mif@ietf.org>, Keith Moore <moore@network-heretics.com>
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:35:20 -0000

On Feb 3, 2013, at 11:32 AM, Brian E Carpenter <brian.e.carpenter@gmail.com>
 wrote:
> 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.

Right, this is why this working group exists (IMHO).

v2.23.0 | Report a Bug | By Email