Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard

Henning Schulzrinne <hgs@cs.columbia.edu> Thu, 01 September 2005 12:20 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAo3g-0006nu-Az; Thu, 01 Sep 2005 08:20:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EAo3d-0006kp-Re for ietf@megatron.ietf.org; Thu, 01 Sep 2005 08:20:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00373 for <ietf@ietf.org>; Thu, 1 Sep 2005 08:20:38 -0400 (EDT)
Received: from brinza.cc.columbia.edu ([128.59.29.8] ident=cu41754) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EAo5Y-0004Lv-N6 for ietf@ietf.org; Thu, 01 Sep 2005 08:22:43 -0400
Received: from [192.168.0.31] (pool-141-153-174-94.mad.east.verizon.net [141.153.174.94]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.13.0/8.13.0) with ESMTP id j81CKSKa016466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 1 Sep 2005 08:20:28 -0400 (EDT)
Message-ID: <4316F20E.9080706@cs.columbia.edu>
Date: Thu, 01 Sep 2005 08:20:30 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
Organization: Columbia University
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Keith Moore <moore@cs.utk.edu>
References: <DAC3FCB50E31C54987CD10797DA511BA1096B57F@WIN-MSG-10.wingroup.windeploy.n tdev.microsoft.com> <p06230956bf3bd9a4992d@[17.202.35.52]> <431676B7.5040302@cs.utk.edu>
In-Reply-To: <431676B7.5040302@cs.utk.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.48 on 128.59.29.8
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)' to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Maybe something like a Service Location Protocol, so that one could 
query by a combination of properties, not just name?

Keith Moore wrote:
> Dave Singer wrote:
> 
>> The whole idea that 'real DNS' can arbitrarily pre-empt local name 
>> resolution seems, well, wrong, and needs serious study for security 
>> implications for the services using those names, no?
> 
> 
> The whole idea that local names should look like DNS names and be 
> queried through the same APIs and user interfaces seems, well, wrong (or 
> dubious at best), and needs serious study for the implications of 
> applications using those APIs and the impact of such names on DNS, no?
> 
> IMO, local names and a lookup service for local names would be extremely 
> useful, but neither the names nor the query interface should look much 
> like DNS - the names should look different because otherwise there's too 
> much potential for confusion with DNS names, and the query service 
> should look different because local name lookup service probably can't 
> make the same kinds of consistency or stability assurances that DNS does.
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf