Re: [mif] I-D Action:draft-ietf-mif-dns-server-selection-02.txt
<teemu.savolainen@nokia.com> Tue, 12 April 2011 12:06 UTC
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: mif@ietfc.amsl.com
Delivered-To: mif@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 93EB5E0771 for <mif@ietfc.amsl.com>; Tue, 12 Apr 2011 05:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.557
X-Spam-Level:
X-Spam-Status: No, score=-4.557 tagged_above=-999 required=5 tests=[AWL=-1.958, BAYES_00=-2.599]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJTPLKbuqtCV for <mif@ietfc.amsl.com>; Tue, 12 Apr 2011 05:05:59 -0700 (PDT)
Received: from mgw-da02.nokia.com (smtp.nokia.com [147.243.128.26]) by ietfc.amsl.com (Postfix) with ESMTP id CB2D0E0737 for <mif@ietf.org>; Tue, 12 Apr 2011 05:05:59 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-da02.nokia.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id p3CC4vxM004733 for <mif@ietf.org>; Tue, 12 Apr 2011 15:05:58 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Apr 2011 15:05:50 +0300
Received: from 008-AM1MMR1-006.mgdnok.nokia.com (65.54.30.61) by NOK-AM1MHUB-04.mgdnok.nokia.com (65.54.30.8) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 12 Apr 2011 14:05:50 +0200
Received: from 008-AM1MPN1-036.mgdnok.nokia.com ([169.254.6.195]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.01.0270.002; Tue, 12 Apr 2011 14:05:49 +0200
From: teemu.savolainen@nokia.com
To: mif@ietf.org
Thread-Topic: [mif] I-D Action:draft-ietf-mif-dns-server-selection-02.txt
Thread-Index: AQHL+QDMQDWiERuQJkqfuREMi7NQ0JRaIH/Q
Date: Tue, 12 Apr 2011 12:05:49 +0000
Message-ID: <916CE6CF87173740BC8A2CE4430969620215C4@008-AM1MPN1-036.mgdnok.nokia.com>
References: <20110412110001.1999.60971.idtracker@ietfc.amsl.com>
In-Reply-To: <20110412110001.1999.60971.idtracker@ietfc.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.162.157.91]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Apr 2011 12:05:50.0360 (UTC) FILETIME=[F6F71180:01CBF909]
X-Nokia-AV: Clean
Subject: Re: [mif] I-D Action:draft-ietf-mif-dns-server-selection-02.txt
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: Tue, 12 Apr 2011 12:06:00 -0000
Hi, This version includes following main updates (also some lesser): - 3.1 comment that updated hosts can talk directly to correct DNS servers. This relates to comment: "what if in new option only suffixes were communicated to hosts, not IP addresses of DNS servers". Plain suffixes would essentially mandate DNS proxy on the gateway that would then forward the questions to correct places. Better not mandate such proxy, I think. - 4.3. Limitations of use section, quite significant - Appendix B: Use of different trust anchors for choosing between different validated answers is now here DHCPv4 is not described as I don't see yet WG consensus for having, or not having, it. Teemu > -----Original Message----- > From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of > ext Internet-Drafts@ietf.org > Sent: 12. huhtikuuta 2011 14:00 > To: i-d-announce@ietf.org > Cc: mif@ietf.org > Subject: [mif] I-D Action:draft-ietf-mif-dns-server-selection-02.txt > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Multiple Interfaces Working Group of > the IETF. > > > Title : Improved DNS Server Selection for Multi-Homed > Nodes > Author(s) : T. Savolainen, et al. > Filename : draft-ietf-mif-dns-server-selection-02.txt > Pages : 21 > Date : 2011-04-12 > > A multi-homed node can be connected to multiple networks that may > utilize different DNS namespaces. The node commonly receives DNS > server configuration information from all connected networks. Some of > the DNS servers may have information about namespaces other servers do > not have. When the multi-homed node needs to utilize DNS, it has to > choose which of the servers to contact to. This document describes a > policy based method for helping on selection of DNS server, for both > forward and reverse DNS lookup procedures, with help of DNS suffix and > IPv6 prefix information received via DHCPv6. > > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-ietf-mif-dns-server- > selection-02.txt > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > Below is the data which will enable a MIME compliant mail reader > implementation to automatically retrieve the ASCII version of the > Internet-Draft.
- [mif] I-D Action:draft-ietf-mif-dns-server-select… Internet-Drafts
- Re: [mif] I-D Action:draft-ietf-mif-dns-server-se… teemu.savolainen