[mif] New rev of MIF DNS server selection document

<teemu.savolainen@nokia.com> Wed, 26 October 2011 07:01 UTC

Return-Path: <teemu.savolainen@nokia.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 E694621F84AF; Wed, 26 Oct 2011 00:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.482
X-Spam-Level:
X-Spam-Status: No, score=-0.482 tagged_above=-999 required=5 tests=[AWL=-2.087, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4zdeipHsh++P; Wed, 26 Oct 2011 00:01:26 -0700 (PDT)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2003521F8484; Wed, 26 Oct 2011 00:01:19 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-sa02.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id p9Q71CPd024271; Wed, 26 Oct 2011 10:01:18 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 26 Oct 2011 10:00:51 +0300
Received: from 008-AM1MMR1-007.mgdnok.nokia.com (65.54.30.23) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 26 Oct 2011 09:00:47 +0200
Received: from 008-AM1MPN1-037.mgdnok.nokia.com ([169.254.7.8]) by 008-AM1MMR1-007.mgdnok.nokia.com ([65.54.30.23]) with mapi id 14.01.0339.002; Wed, 26 Oct 2011 09:00:46 +0200
From: <teemu.savolainen@nokia.com>
To: <mif@ietf.org>, <dnsext@ietf.org>, <dnsop@ietf.org>, <dhcwg@ietf.org>
Thread-Topic: New rev of MIF DNS server selection document
Thread-Index: AcyTq3sQ9JbsYFTkR5yAi3kg51bouw==
Date: Wed, 26 Oct 2011 07:00:46 +0000
Message-ID: <916CE6CF87173740BC8A2CE44309696203787DCE@008-AM1MPN1-037.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tituslabs-classifications-30: TLPropertyRoot=Nokia; Confidentiality=Company Confidential; Project=None;
x-titus-version: 3.3.8.1
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: 0Ywc1/TmJmZP14okFmB8GOGuG+9CndY/chBUg2sNqfclVQc560ay4nTVu+Pyk2IAuFttQ0hJIgNZv0C/nLXvVl6FFyrPFpbSBOJjV37tYwuNoeTkhogx7FiT8UlHtNh3raK/yv2tgY3MgXDEMDyjWF7v2fpwqE5b1AYchEkJFQCkQUWl7EB+ZbJkdpe0Azkr2V/cOFBVnD04GNJZ4cF4iaQZsj+MbhDweV76wYxTT/s6Sm6Cel+NQRlCDM/kxxA4
x-originating-ip: [10.162.56.71]
Content-Type: multipart/alternative; boundary="_000_916CE6CF87173740BC8A2CE44309696203787DCE008AM1MPN1037mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 26 Oct 2011 07:00:51.0909 (UTC) FILETIME=[FF9DC750:01CC93AC]
X-Nokia-AV: Clean
Subject: [mif] New rev of MIF DNS server selection document
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: Wed, 26 Oct 2011 07:01:28 -0000

Hi all,



Thank you for all the discussions.



I have submitted -07 version with the following changes:

-          Complete removal of section 4.6 about DNS search list option handling. This topic clearly is something that is too big for this draft to cover and also seems to be mostly out of the scope of this draft. If there some day will be a new draft that addresses various issues with DNS search lists, it might also discuss the issues related to MIF

-          Security additions, namely the following two additions:

o   “In some occasions an interface may be considered trusted only if explicitly configured to be trusted.”

o   “An implementation may not be able to determine trust levels without explicit configuration provided by user or administrator.  Therefore, for example, an implementation may not by default trust configuration received even over VPN interfaces.”

-          DHCPv4 option structure clarification:

o   Possibility to have multiple options that are concatenated as described in RFC3396

o   Removal of “payload len” field



I now think that after these improvements this is even more ready to go towards IESGJ



I-D itself: http://www.ietf.org/id/draft-ietf-mif-dns-server-selection-07.txt



Diff to -06:  http://tools.ietf.org/rfcdiff?url2=draft-ietf-mif-dns-server-selection-07



Best regards,



                Teemu



From: dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] On Behalf Of Savolainen Teemu (Nokia-CTO/Tampere)
Sent: 19. lokakuuta 2011 09:43
To: denghui02@hotmail.com; mif@ietf.org; dnsext@ietf.org; dnsop@ietf.org; dhcwg@ietf.org
Cc: sa.morris7@googlemail.com; pk@isoc.de
Subject: Re: [dhcwg] [mif] 2nd Last Call for MIF DNS server selection document



Hi all,



This second WGLC resulted in very few comments. In the DHC WG we discussed about DHCPv4 option structure and in MIF there was a comment about document-internal reference bug.



I have now uploaded a version six that contains:

-          Fixes to the DHCPv4 option structure

-          Highlighting stricter length limitation in case of DHCPv4 option

-          Fix to the reference bug

-          Small fixes to missing DHCPv4 considerations in sections 4.5 and 4.6.



Please see diff: http://tools.ietf.org/rfcdiff?url2=draft-ietf-mif-dns-server-selection-06



If no further comments, I think this document is ready to go to the IESG.



Thank you,



                Teemu





From: mif-bounces@ietf.org<mailto:mif-bounces@ietf.org> [mailto:mif-bounces@ietf.org]<mailto:[mailto:mif-bounces@ietf.org]> On Behalf Of ext Hui Deng
Sent: 30. syyskuuta 2011 18:29
To: mif@ietf.org<mailto:mif@ietf.org>; dnsext@ietf.org<mailto:dnsext@ietf.org>; dnsop@ietf.org<mailto:dnsop@ietf.org>; dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Cc: pk@isoc.de<mailto:pk@isoc.de>; john_brzozowski@cable.comcast.com<mailto:john_brzozowski@cable.comcast.com>; sa.morris7@googlemail.com<mailto:sa.morris7@googlemail.com>
Subject: [mif] 2nd Last Call for MIF DNS server selection document



Dear all

Based on 1st round WG LC, the authors have received significant advice about revision and submited a new version accordingly:
http://www.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-05.txt

And we plan to issue a second round WG LC, and cc to DHCWG, DNSEXT, DNSOP related working groups, please DNSEXT/DNSOP chairs help to forward to the MLs since I may not subscribe to them.

This is a 2 weeks with little extension LC, it will finish on October 17,
Please send substantive review and editorial comments to mif@ietf.org<mailto:mif@ietf.org>

Thanks a lot for youre view
Best regards,

Margaret and Hui



Below are Teemu's writeup about the revision:

I uploaded -05 update so that next comments would take into account changes
I already did based on discussions with Murray (as was copied to this list).
The biggest clarifications related to how DNS queries are sent to different
servers and when all servers are waited for answers (if reply is not
validated) and when not. I.e. this text:
--
  A node SHALL send requests to DNS servers in the order defined by the
  priority list until an acceptable reply is received, all replies are
  received, or a time out occurs.  In the case of a requested name
  matching to a specific domain or network rule accepted from any
  interface, a DNSSEC-aware resolver MUST NOT proceed with a reply that
  cannot be validated using DNSSEC until all DNS servers on the
  priority list have been contacted or timed out.  This protects
  against possible redirection attacks.  In the case of the requested
  name not matching to any specific domain or network, first received
  response from any DNS server MAY be considered acceptable.  A DNSSEC-
  aware node MAY always contact all DNS server in an attempt to receive
  a response that can be validated, but contacting all DNS servers is
  not mandated for the default case as in some deployments that would
  consume excess resources.
--
       Teemu
> -----Original Message-----
> From: mif-bounces@ietf.org<mailto:mif-bounces@ietf.org> [mailto:mif-bounces@ietf.org]<mailto:[mailto:mif-bounces@ietf.org]> On Behalf Of
> ext internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
> Sent: 20. syyskuuta 2011 22:10
> To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
> Cc: mif@ietf.org<mailto:mif@ietf.org>
> Subject: [mif] I-D Action: draft-ietf-mif-dns-server-selection-05.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-Interfaced
> Nodes
>       Author(s)       : Teemu Savolainen
>                           Jun-ya Kato
>                           Ted Lemon
>       Filename        : draft-ietf-mif-dns-server-selection-0 5.txt
>       Pages           : 26
>       Date            : 2011-09-20
>
>    A multi-interfaced node is connected to multiple networks, some of
>    which may be utilizing private DNS namespaces.  A 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 a multi-interfaced node
>    needs to utilize DNS, the node has to choose which of the servers to
>    contact to.  This document describes DHCPv4 and DHCPv6 option that
>    can be used to configure nodes with inform ation required to perform
>    informed DNS server selection decisions.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mif-dns-server-selection-05.txt