IETF Logo Mail Archive

Re: [mif] Comments on draft-ietf-mif-dns-server-selection-01

Ted Lemon <Ted.Lemon@nominum.com> Tue, 29 March 2011 07:57 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@core3.amsl.com
Delivered-To: mif@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67F9A3A6A83 for <mif@core3.amsl.com>; Tue, 29 Mar 2011 00:57:06 -0700 (PDT)
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.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l8AHiQ-o-Ttw for <mif@core3.amsl.com>; Tue, 29 Mar 2011 00:57:05 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by core3.amsl.com (Postfix) with ESMTP id 6DA523A69FC for <mif@ietf.org>; Tue, 29 Mar 2011 00:57:05 -0700 (PDT)
Received: from source ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKTZGRMhjTyLisOoPPX8zvXE6EuLwvPNJO@postini.com; Tue, 29 Mar 2011 00:58:43 PDT
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 46593F80A5 for <mif@ietf.org>; Tue, 29 Mar 2011 00:58:42 -0700 (PDT)
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 3A62719006C; Tue, 29 Mar 2011 00:58:42 -0700 (PDT) (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.01.0255.000; Tue, 29 Mar 2011 00:58:42 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com>
Thread-Topic: [mif] Comments on draft-ietf-mif-dns-server-selection-01
Thread-Index: AQHL7T2TZudS6uSp00WtSjuDIkpv2ZRDyiSAgAAVv0yAAIYIAP//jdfK
Date: Tue, 29 Mar 2011 07:58:42 +0000
Message-ID: <B66B2C01-A514-4731-B3AB-B03EAB5B00DB@nominum.com>
References: <20110328114453.GD85777@crankycanuck.ca>, <916CE6CF87173740BC8A2CE44309696201647D@008-AM1MPN1-036.mgdnok.nokia.com> <EA8E2993-CEB7-45E9-B573-4140F5560A55@nominum.com>, <916CE6CF87173740BC8A2CE443096962016624@008-AM1MPN1-036.mgdnok.nokia.com>
In-Reply-To: <916CE6CF87173740BC8A2CE443096962016624@008-AM1MPN1-036.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mif@ietf.org" <mif@ietf.org>
Subject: Re: [mif] Comments on draft-ietf-mif-dns-server-selection-01
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 29 Mar 2011 07:57:06 -0000

On Mar 29, 2011, at 9:47 AM, "teemu.savolainen@nokia.com" <teemu.savolainen@nokia.com> wrote:
> Where the case 4 could happen? When the trusted DNS server address is configured via some secure channel (e.g. administratively)?

Yes, that's the case I had in mind.   It's probably worth defining the terms more clearly if there is agreement on the set of four requirements that I suggested, but I'm curious to know if Andrew and Peter think they make sense.

v2.23.0 | Report a Bug | By Email