Message-Id: <6.2.3.4.2.20050905132653.042e1450@mail.jefsey.com>
Date: Mon, 05 Sep 2005 13:36:17 +0200
To: Pekka Savola <pekkas@netcore.fi>,
	Christian Huitema <huitema@windows.microsoft.com>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <Pine.LNX.4.61.0509051212010.14797@netcore.fi>
References: <DAC3FCB50E31C54987CD10797DA511BA10A5A1E2@WIN-MSG-10.wingroup.windeploy.ntdev.microsoft.com>
	<Pine.LNX.4.61.0509051212010.14797@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
Subject: RE: Last Call: 'Linklocal Multicast Name Resolution (LLMNR)'
 toProposed Standard
Precedence: list
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

At 11:29 05/09/2005, Pekka Savola wrote:
>On Mon, 5 Sep 2005, Christian Huitema wrote:
>>LLMNR does not create additional DNS queries.
>However, as folks have pointed out, having a lookup mechanism which 
>can also use real FQDN's has benefits compared to just restricting 
>to .local.  The more difficult problem is being able to separate 
>"really owned FQDN" from "invented, bogus FQDN"... while not making 
>the problem worse by creating even more DNS traffic.

This mechanism would work on a list of TLDs to compare with. May be 
the proper place to introduce a full TLD service where a istld(tld) 
function would return a null string if it did not exist and the 
proper tld to use otherwise. This would enforce a strict TLD aliasing 
able to support an internationalised version of the existing TLDs for 
full ML.ML names.

That function could be extended to isdn(dn.tld) where the dn could be 
nullified if it did use only characters from the TLD associated 
charset. This would address the homograph problem, since TLD Managers 
can decide of their TLD charsets, but cannot impose them beyond their 
own registration level.

jfc



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf