Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices

Dave Thaler <dthaler@microsoft.com> Fri, 14 November 2014 22:00 UTC

Return-Path: <dthaler@microsoft.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51ED81ACECF for <dnssd@ietfa.amsl.com>; Fri, 14 Nov 2014 14:00:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level:
X-Spam-Status: No, score=-101.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6E7EQdIZYVL for <dnssd@ietfa.amsl.com>; Fri, 14 Nov 2014 14:00:07 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0711.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::1:711]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D0E1ACECE for <dnssd@ietf.org>; Fri, 14 Nov 2014 14:00:07 -0800 (PST)
Received: from BY2PR03MB412.namprd03.prod.outlook.com (10.141.141.25) by BY2PR03MB410.namprd03.prod.outlook.com (10.141.141.16) with Microsoft SMTP Server (TLS) id 15.1.11.14; Fri, 14 Nov 2014 21:59:44 +0000
Received: from BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) by BY2PR03MB412.namprd03.prod.outlook.com ([10.141.141.25]) with mapi id 15.01.0011.000; Fri, 14 Nov 2014 21:59:44 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>, Ted Lemon <Ted.Lemon@nominum.com>
Thread-Topic: [dnssd] DNS Name Autoconfiguration for Home Network Devices
Thread-Index: AQHP//BdbIlYWo1W40+HoQ6kr/OanJxghaCAgAAf7YCAAAG9AA==
Date: Fri, 14 Nov 2014 21:59:44 +0000
Message-ID: <cc9f90afaa7a48bdaf7a8906546571b5@BY2PR03MB412.namprd03.prod.outlook.com>
References: <CAPK2DeyuABqSbH5dtdtScYWnE-vkmGO642xFb6FZehu-5MTaAA@mail.gmail.com> <436692B4-978D-4E62-868E-78FA8AF3F26F@nominum.com> <CAPK2Deys6VU83R0hfv_8svNKuaSBEfu_dGqnGkoN_pQ9zE_6HQ@mail.gmail.com>
In-Reply-To: <CAPK2Deys6VU83R0hfv_8svNKuaSBEfu_dGqnGkoN_pQ9zE_6HQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [31.133.166.252]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:BY2PR03MB410;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:BY2PR03MB410;
x-forefront-prvs: 03950F25EC
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(189002)(51884002)(24454002)(33646002)(76576001)(99396003)(2656002)(74316001)(20776003)(64706001)(97736003)(122556002)(21056001)(40100003)(101416001)(87936001)(66066001)(120916001)(4396001)(107046002)(76176999)(54356999)(50986999)(86362001)(99286002)(105586002)(62966003)(31966008)(86612001)(95666004)(108616004)(106356001)(92566001)(106116001)(77156002)(46102003)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR03MB410; H:BY2PR03MB412.namprd03.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/wBMlnrm7HQvLIokGQ1iXm9N6Gb4
Cc: "dnssd@ietf.org" <dnssd@ietf.org>, Myung-Ki Shin <mkshin@etri.re.kr>, Brian Haberman <brian@innovationslab.net>, Jung-Soo Park <pjs@etri.re.kr>
Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Nov 2014 22:00:09 -0000

Paul wrote:
> For the regeneration and verification of a unique DNS name under DNS name conflict,
> the solution in RFC 6762 recommends to use an incremental digit (such as 2, 3, 4, etc.)
> by trial and error. In an IoT scenario where there will be many IoT devices of the same
> type, such as light bulb in home or hotel here, this incremental numbering approach
> will be costly and slow to let each IoT device have a unique DNS name, ...

My reading is that RFC 6762 does not _require_ an incremental digit.  You can put in
a random ID or MAC-derived ID or something else highly unlikely to collide.
As such, it should not be "costly and slow".  Indeed RFC 6762 does not specify what
you have to do.   Would it be possible to recast your draft as
"how to choose a unique ID and use RFC 6762" ? 

-Dave