On Thu, 2010-03-25 at 11:21 +0100, Fabian Greffrath wrote: > reopen 575209 > reassign 575209 eglibc > found 575209 2.10.2-6 > found 575209 2.11-0exp6 > severity 575209 important > retitle 575209 Please resolv domain names with hyphens as border chars > tags 575209 + patch > thanks > > Hi Holger et al (please drop -devel out of the list of CCs if you feel > this is getting off-topic), > > sorry, but I find it unacceptable to close this bug referring to a > single paragraph in a (random) RFC . However, there is a multitude > of other reasons why I think this bug *is* an issue: That 'random' RFC happens to be an Internet standard (STD 13) and still largely valid today. > - Sites with domain names like <ker-.deviantart.com> do already exist! > Do you think they should be accessible by any other proprietary > operating system, but not Debian? Not really! So if Windows accepts it then it must be OK? I don't think we have to follow that rule. Otherwise you should be demanding support for NMB and WINS in glibc. > - There is already an inconsistency among the different > implementations in Debian (or Linux as a whole), as e.g. ping and any > other program using gethostbyname() fail to resolv, whereas nslookup > and host succeed. This is what happens when you ignore Internet standards. > - The advice in the cited RFC is already ignored. Domain names that > start with a digit, e.g. 12345.foo.bar, can be resolved, whereas the > RFC tells us "They [labels] must start with a letter, end with a > letter or digit [...]". [...] It is not ignored; the standard was updated by RFC 1123 (STD 3). Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Description: This is a digitally signed message part