Re: [mif] [dnsext] 2nd Last Call for MIF DNS server selection document

<teemu.savolainen@nokia.com> Thu, 20 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 1135121F85A1; Thu, 20 Oct 2011 00:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level:
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599]
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 4+0TEhUqtys6; Thu, 20 Oct 2011 00:01:36 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 3320621F8593; Thu, 20 Oct 2011 00:01:35 -0700 (PDT)
Received: from vaebh105.NOE.Nokia.com (vaebh105.europe.nokia.com [10.160.244.31]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p9K71K4Z007935; Thu, 20 Oct 2011 10:01:29 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh105.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 20 Oct 2011 10:01:20 +0300
Received: from 008-AM1MMR1-002.mgdnok.nokia.com (65.54.30.57) by NOK-am1MHUB-02.mgdnok.nokia.com (65.54.30.6) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 20 Oct 2011 09:01:18 +0200
Received: from 008-AM1MPN1-037.mgdnok.nokia.com ([169.254.7.8]) by 008-AM1MMR1-002.mgdnok.nokia.com ([65.54.30.57]) with mapi id 14.01.0339.002; Thu, 20 Oct 2011 09:01:18 +0200
From: <teemu.savolainen@nokia.com>
To: <Ray.Bellis@nominet.org.uk>
Thread-Topic: [dnsext] [mif] 2nd Last Call for MIF DNS server selection document
Thread-Index: AQHMjlOod32iNq3Hr0aVNz752afFi5WEy7FQ
Date: Thu, 20 Oct 2011 07:01:17 +0000
Message-ID: <916CE6CF87173740BC8A2CE44309696203783EE0@008-AM1MPN1-037.mgdnok.nokia.com>
References: <COL118-W55403198A984BAAE44BA47B1F70@phx.gbl> <916CE6CF87173740BC8A2CE44309696203782D75@008-AM1MPN1-037.mgdnok.nokia.com> <121DABD1-65E8-4275-8471-9FA38D25C434@nominet.org.uk>
In-Reply-To: <121DABD1-65E8-4275-8471-9FA38D25C434@nominet.org.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
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: VgNFIFU9Hx+/nZJb9Kg7IvQmQ0o/K2jquxqC2Uue5GHpzEuo3S9zNfeh3beuXC4d4U+9SoG2zegA7qMLdX6PTG17IL7pxR5S/KY/iCJNnn1c5UqLju8bmTWbhVRC5KYyRvx6Lux+omb+cjLr4ZT4xGr6EYlMoJAb4mKk7Ygo2IOCLEfvotq8eZrg90l9H1dML3IGXW5CR0VaroyKyJb6YmetiFAenF/tDgR293RVPdnMoKPAurwSeBTTqO8uNr6TcXVEvm613p4YTVwzPTjUYrSShwM2n81B2EdPx398YIM=
x-originating-ip: [10.162.69.25]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_000B_01CC8F0F.35163130"
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Oct 2011 07:01:20.0574 (UTC) FILETIME=[123935E0:01CC8EF6]
X-Nokia-AV: Clean
Cc: mif@ietf.org, dnsop@ietf.org, dnsext@ietf.org, pk@isoc.de, john_brzozowski@cable.comcast.com, dhcwg@ietf.org, denghui02@hotmail.com
Subject: Re: [mif] [dnsext] 2nd Last Call for 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: Thu, 20 Oct 2011 07:01:37 -0000

Hi Ray,

> -----Original Message-----
> From: ext Ray Bellis [mailto:Ray.Bellis@nominet.org.uk]
> Sent: 19. lokakuuta 2011 13:40
> To: Savolainen Teemu (Nokia-CTO/Tampere)
> Cc: <denghui02@hotmail.com>om>; <mif@ietf.org>rg>; <dnsext@ietf.org>rg>;
> <dnsop@ietf.org>rg>; <dhcwg@ietf.org>rg>; <pk@isoc.de>de>;
> <john_brzozowski@cable.comcast.com>
> Subject: Re: [dnsext] [mif] 2nd Last Call for MIF DNS server selection
> document
> 
> I have concerns about §4.6:
> 
> "A bare name (a name without any dots) MUST be first treated as a pre-
DNS
> hostname, and only after that the name SHALL be appended with  domain
> information and described DNS server selection logic be  utilized."
> 
> When new gTLDs are introduced it is likely for brand-name gTLDs that they
> will wish to use bare names in the DNS (i.e. a single label hostname) for
their
> primary web sites.
> 
> Hence bare names may become much more frequently used as DNS names,
> and §4.6 wouldn't permit those to work unless '.' is also in the suffix
list.
>
> I'd like to hear the authors' thoughts on these.  I'm not sure that this
draft
> necessarily needs any significant changes - it may only require changes to
> ensure that bare names are also considered as potential DNS names in their
> own right.

Okay, I understand there is no clear consensus yet how these single label
names should be handled by the resolvers at the first place? Should resolver
first treat them as pre-DNS hostnames, then as DNS hostnames, and then try
search list? The DNS server selection logic would be applied already when
resolving single label name, i.e. the network could provide a single label
domain "brand" in the domains list.

Maybe section 4.6 could be like this, perhaps (changes in second paragraph
and title)?
--
4.6.  Interactions with DNS search lists and single label hostnames

   A node may be configured with DNS search list by DHCPv6
   OPTION_DOMAIN_LIST [RFC3646] or DHCPv4 Domain Search Option
   [RFC3397].

   A bare name (a name without any dots) MUST be first treated as a pre-
   DNS hostname, after which resolution of the name SHALL be attempted
   with DNS, and as a last resort the name SHALL be appended with
   domain information. DNS server selection logic SHALL be 
   utilized for both of the latter two DNS using methods.

   Resolution for the name containing any dots SHOULD first be attempted
   with DNS servers of all interfaces.  Only if the resolution fails the
   node SHOULD append the name with search list domain(s) and then again
   utilize improved DNS server selection algorithm to decide which DNS
   server(s) to contact.
--

Best regards,

	Teemu