IDNA 2008 Question Re: "Confusable" Characters in Domain Names
2010-11-03 17:14:55 GMT
_______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
_______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
On Wed, Nov 03, 2010 at 05:14:55PM +0000, john daw wrote:
> Dear List Members,I am a little unclear what impact the IDNA 2008
> policy will have ondomain name registrant's who have a domain that
> does not fall underthe policy's permissible code-points, particularly
> symbol-based domainnames.The IDNA 2008 protocol clearly explains what
> code point are permissible,but what (in practice) will it mean if
> someone types in e.g. €.com in theirbrowser under IDNA 2008?I do
> realise that an error message may be displayed, but will IDNA 2008
> allow the domain name registrant to satisfy the user's query by
> forwardingthem on to a different (legal) domain name?I will hope to
> hear any replies on this matter.Regards,John Daw
Is this a good translation of your question:
Are TLD registrars allowed to include CNAME RRs for domains
otherwise not allowed either by IDNA2008 or by the registrar?
?
Nico
--
--
_______________________________________________
Idna-update mailing list
Idna-update <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/idna-update
_______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
If your browser is operating under purely idna2008 rules the lookup should fail. But some implementations
may permit the lookup without verfying the legality of the characters in the lookup string. V
From: idna-update-bounces <at> alvestrand.no < idna-update-bounces <at> alvestrand.no>
To: idna-update <at> alvestrand.no < idna-update <at> alvestrand.no>
Sent: Wed Nov 03 13:14:55 2010
Subject: IDNA 2008 Question Re: "Confusable" Characters in Domain Names
Dear List Members,
I am a little unclear what impact the IDNA 2008 policy will have on
domain name registrant's who have a domain that does not fall under
the policy's permissible code-points, particularly symbol-based domain
names.
The IDNA 2008 protocol clearly explains what code point are permissible,
but what (in practice) will it mean if someone types in e.g. .com in their
browser under IDNA 2008?
I do realise that an error message may be displayed, but will IDNA 2008
allow the domain name registrant to satisfy the user's query by forwarding
them on to a different (legal) domain name?
I will hope to hear any replies on this matter.
Regards,
John Daw
_______________________________________________
Idna-update mailing list
Idna-update <at> alvestrand.no
http://www.alvestrand.no/mailman/listinfo/idna-update
_______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
On Wed, Nov 03, 2010 at 12:27:37PM -0500, Nicolas Williams wrote: > Are TLD registrars allowed to include CNAME RRs for domains > otherwise not allowed either by IDNA2008 or by the registrar? zone operators can, of course, do whatever they want in the zones they operate, subject to whatever agreements they have about delegation. But a CNAME wouldn't do much good, would it, since it will only redirect the name itself and not any names underneath. A -- -- Andrew Sullivan ajs <at> shinkuro.com Shinkuro, Inc.
On Thu, Nov 04, 2010 at 11:08:10AM -0400, Andrew Sullivan wrote: > On Wed, Nov 03, 2010 at 12:27:37PM -0500, Nicolas Williams wrote: > > Are TLD registrars allowed to include CNAME RRs for domains > > otherwise not allowed either by IDNA2008 or by the registrar? > > zone operators can, of course, do whatever they want in the zones they > operate, subject to whatever agreements they have about delegation. > But a CNAME wouldn't do much good, would it, since it will only > redirect the name itself and not any names underneath. Of course, but I was trying to understand if the OP was trying to ask that question, as I couldn't imagine how else "redirects" might work at the DNS level. The OP's question just makes no sense to me.
I’d like to throw in my 2 cents. Clearly a browser has no clue if the DNS layer is operating under IDNA2003 or IDNA2008 rules, nor even if the current browser supports post-IDNA2008 rules (like characters new to Unicode since IDNA2008). Particularly since different zones could operate under different rules. I think it’s likely that some browsers will have a relaxed set of rules, since strict adherence to any particular version would likely break names/zones, whether future or old. The existence of UTS#46 seems to support the idea that some flexibility is desired.
IMO it’s not the client’s responsibility to say whether DNS rules are being followed, but rather the DNS layer’s responsibility to correctly resolve names and provide the appropriate errors when the name isn’t valid.
-Shawn
From: idna-update-bounces <at> alvestrand.no [mailto:idna-update-bounces <at> alvestrand.no]
On Behalf Of Vint Cerf
Sent: Poʻakolu, Nowemapa 03, 2010 10:58 AM
To: taliskermoon <at> hotmail.co.uk; idna-update <at> alvestrand.no
Subject: Re: IDNA 2008 Question Re: "Confusable" Characters in Domain Names
If your browser is operating under purely idna2008 rules the lookup should fail. But some implementations may permit the lookup without verfying the legality of the characters in the lookup string. V
From:
idna-update-bounces <at> alvestrand.no <idna-update-bounces <at> alvestrand.no>
To: idna-update <at> alvestrand.no <idna-update <at> alvestrand.no>
Sent: Wed Nov 03 13:14:55 2010
Subject: IDNA 2008 Question Re: "Confusable" Characters in Domain Names
Dear List Members,
I am a little unclear what impact the IDNA 2008 policy will have on
domain name registrant's who have a domain that does not fall under
the policy's permissible code-points, particularly symbol-based domain
names.
The IDNA 2008 protocol clearly explains what code point are permissible,
but what (in practice) will it mean if someone types in e.g. €.com in their
browser under IDNA 2008?
I do realise that an error message may be displayed, but will IDNA 2008
allow the domain name registrant to satisfy the user's query by forwarding
them on to a different (legal) domain name?
I will hope to hear any replies on this matter.
Regards,
John Daw
_______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
At 21:40 04/11/2010, Shawn Steele wrote: >IMO itâs not the clientâs responsibility to say whether DNS >rules are being followed, but rather the DNS layerâs >responsibility to correctly resolve names and provide the >appropriate errors when the name isnât valid. Correct. All what is expected from the client is to be transparent to the user entry when its "IDNinA" support is not requested. Whatever the kind of DNS "IDNApplication" front-end used by the user, it must be able to receive the very entry the user has keyed. jfc
_______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
On Thu, Nov 04, 2010 at 08:40:47PM +0000, Shawn Steele wrote: > I’d like to throw in my 2 cents. Clearly a browser has no clue if > the DNS layer is operating under IDNA2003 or IDNA2008 rules I have no idea what this would me. The DNS layer is not operating under _either_ IDNA2003 or IDNA2008 rules. It's operating like it always did: it matches labels, one label at a time, and it matches them exactly, bit for bit. Moreover, under IDNA of any flavour, it does that under the constraint of the old-fashioned hostname rules (which means, roughly, letters, digits, hyphen or LDH). > IMO it’s not the client’s responsibility to say whether DNS rules > are being followed, but rather the DNS layer’s responsibility to > correctly resolve names and provide the appropriate errors when the > name isn’t valid. The rules _are not_ DNS rules, and if that isn't perfectly clear from reading IDNA2008, I have no idea how to make it more so. A -- -- Andrew Sullivan ajs <at> shinkuro.com Shinkuro, Inc. _______________________________________________ Idna-update mailing list Idna-update <at> alvestrand.no http://www.alvestrand.no/mailman/listinfo/idna-update
RSS Feed65 | |
|---|---|
4 | |
13 | |
10 | |
42 | |
27 | |
11 | |
125 | |
2 | |
28 | |
18 | |
12 | |
5 | |
1 | |
27 | |
34 | |
49 | |
45 | |
58 | |
29 | |
29 | |
126 | |
16 | |
9 | |
81 | |
1 | |
47 | |
70 | |
22 | |
553 | |
108 | |
202 | |
219 | |
250 | |
494 | |
47 | |
29 | |
294 | |
536 | |
228 | |
90 | |
282 | |
131 | |
270 | |
70 | |
93 | |
244 | |
74 | |
308 | |
226 | |
498 | |
168 | |
178 | |
102 | |
33 | |
1 | |
5 | |
112 | |
11 | |
17 | |
40 | |
78 | |
300 | |
96 | |
1 |