IETF Logo Mail Archive

[mif] DNS server selection revision under works..

<teemu.savolainen@nokia.com> Fri, 12 November 2010 00:52 UTC

Return-Path: <teemu.savolainen@nokia.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 C2F773A67EC for <mif@core3.amsl.com>; Thu, 11 Nov 2010 16:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.586
X-Spam-Level:
X-Spam-Status: No, score=-6.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 o678j1aGoobJ for <mif@core3.amsl.com>; Thu, 11 Nov 2010 16:52:58 -0800 (PST)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id D83563A67F0 for <mif@ietf.org>; Thu, 11 Nov 2010 16:52:57 -0800 (PST)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id oAC0rQmh010824 for <mif@ietf.org>; Thu, 11 Nov 2010 18:53:28 -0600
Received: from vaebh102.NOE.Nokia.com ([10.160.244.23]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 12 Nov 2010 02:53:25 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.8]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 12 Nov 2010 02:53:21 +0200
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-04.mgdnok.nokia.com ([65.54.30.8]) with mapi; Fri, 12 Nov 2010 01:53:20 +0100
From: teemu.savolainen@nokia.com
To: mif@ietf.org
Date: Fri, 12 Nov 2010 01:53:17 +0100
Thread-Topic: DNS server selection revision under works..
Thread-Index: AcuBj39WQNNfY2VzS2OrfycmHKBpxAAAVRXgAByn8DA=
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D6F039@NOK-EUMSG-01.mgdnok.nokia.com>
References: <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D02AEE@NOK-EUMSG-01.mgdnok.nokia.com> <29F4CEED-DB30-4A4B-8CDF-AB43B576DE01@nominum.com> <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D02AF6@NOK-EUMSG-01.mgdnok.nokia.com> <5390F566-8150-450B-BD5A-C2636EABE128@nominum.com> <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D6EA16@NOK-EUMSG-01.mgdnok.nokia.com> <99962D6D-2626-4B66-B996-DE6FA05B9BF8@nominum.com> <4F099E7F-800E-4F5E-96E5-9BD7FBF23BF2@nishidaya.org> <B21EAB17-ADA5-40FF-AA14-24D636B795F3@nominum.com> <FAEB3290-FF11-499C-AB9B-C3919B95E47B@nishidaya.org> <842EACF2-ADE7-434E-8F64-A5F65AA9893C@nominum.com> <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D6EC7B@NOK-EUMSG-01.mgdnok.nokia.com> <41FC18BB-A0E7-4895-98BE-0DB31F1A10C8@nominum.com> <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D6ED0D@NOK-EUMSG-01.mgdnok.nokia.com> <9A0B59CC-71D1-40B3-BBDA-C348F17E9D01@nominum.com> <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D6ED22@NOK-EUMSG-01.mgdnok.nokia.com>
In-Reply-To: <18034D4D7FE9AE48BF19AB1B0EF2729F5F05D6ED22@NOK-EUMSG-01.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 12 Nov 2010 00:53:21.0808 (UTC) FILETIME=[00FA6100:01CB8204]
X-Nokia-AV: Clean
Subject: [mif] DNS server selection revision under works..
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: Fri, 12 Nov 2010 00:52:58 -0000

FYI I'm working offline with Ted to come up with a revision of draft that hopefully addresses the concern, will let you know when something is available.

Meanwhile, any comments on these questions I had on the presentation:

1) Instead of multiple option instances change to use suboptions similar to DHCPv6 IA_RT

I think this is needed, but comments welcome if that is good idea or not (I personally couldn't get ISC DHCPv6 client work with multiple DHCPv6 option instances).

2) Install specific route for each DNS server address to ensure the DNS queries go out of right interface

This would increase reliability and I included it in -05. But comments welcome.

3) Should the DNS suffix list be compressed, like defined in RFC1035 section 4.1.4 or at draft-ietf-mip4-nemo-haaro-02 section 4.2 (dictionary based)? Savings would probably be quite small, but some still.

Do you think slightly added complexity is worthwhile to compress the suffix list a bit? Essentially repeating labels (.com, .www, etc) would be compressed.

Best regards,

Teemu

> -----Original Message-----
> From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On Behalf Of
> Savolainen Teemu (Nokia-MS/Tampere)
> Sent: 11. marraskuuta 2010 19:11
> To: Ted.Lemon@nominum.com
> Cc: mif@ietf.org
> Subject: Re: [mif] New revision of DNS server selection
> 
> > > We are chartered to work on DHCP. We might be able to do this
> feature
> > with things like ANDSF, 3GPP PCO IE, cablelabs, and so on, but is it
> > really worthwhile to define same thing all over again in those
> places?
> > Why not implement in DHCPv6 instead and then implement the DHCPv6 RFC
> > on those devices where it applies.
> >
> > I've already explained to you at length why I think we should not do
> > this.   I think at this point we're just repeating the same
> arguments.
> 
> Agree.
> 
> We need other opinions to find consensus for way forward.
> 
> 	Teemu
> _______________________________________________
> mif mailing list
> mif@ietf.org
> https://www.ietf.org/mailman/listinfo/mif

v2.23.0 | Report a Bug | By Email