mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "John Levine" <johnl@iecc.com>
To: musl@lists.openwall.com
Subject: Re: Re: Would not love to see reconsideration for domain and search
Date: 26 Oct 2015 17:41:48 -0000	[thread overview]
Message-ID: <20151026174148.23543.qmail@ary.lan> (raw)
In-Reply-To: <20151026161639.GF8645@brightrain.aerifal.cx>

>Note that ndots=1 search is rather harmless as long as ICANN has a
>prohibition on top-level domains resolving to an address.

That horse left the barn over 15 years ago:

https://www.rfc-editor.org/info/rfc7085

ICANN currently has a rule against it for generic TLDs, but they have
no control over two-letter country codes, and as our RFC notes, a lot
of ccTLDs have had A and MX records.

I say currently because Google asked for an exception to put an A
record to make http://search/ work, and it took some discussion before
ICANN said no.  The no was as much about anti-competitive reasons, the
default would be to Google's search engine, as the technical issues.
If someeone else asked, they'd probably say no, but it's not cast in
stone.

In response to another question about search order, the default value
of ndots is 1, so any domain name with at least one dot, such as
frodo.cs, is looked up directly before it tries a search list.  You
can set ndots to anything you want, but I expect that your users would
not be happy if gmail.com and yahoo.com could be shadowed by local host
names.

R's,
John

PS: Just for the record, the world's shortest e-mail address is n@ai.
I'm j@jl.ly, but that's almost twice as long.



  reply	other threads:[~2015-10-26 17:41 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 21:24 Would " Tim Hockin
2015-10-22 21:56 ` Rich Felker
2015-10-22 22:36   ` Tim Hockin
2015-10-22 23:00     ` Josiah Worcester
2015-10-22 23:37       ` Tim Hockin
2015-10-23  4:27         ` Rich Felker
2015-10-23  5:13           ` Tim Hockin
2015-10-23  5:31             ` Rich Felker
2015-10-23  5:37               ` Tim Hockin
2015-10-23  6:00                 ` Rich Felker
2015-10-23  6:04                   ` Tim Hockin
2016-01-29  0:57                 ` Rich Felker
2015-10-27  0:30               ` Rich Felker
2015-10-27  0:37                 ` Tim Hockin
2015-10-27  0:45                   ` Rich Felker
2015-10-27  8:11                 ` u-uy74
2015-11-28 22:48                 ` Jan Broer
2015-11-28 23:20                   ` Rich Felker
2015-11-29  3:06                     ` Jan Broer
2016-01-29  0:58                   ` Rich Felker
2015-10-26  2:14           ` Re: Would not " John Levine
2015-10-26  5:14             ` Tim Hockin
2015-10-26 16:16               ` Rich Felker
2015-10-26 17:41                 ` John Levine [this message]
2015-10-26 18:08                   ` Rich Felker
2015-10-23  8:12       ` Re: Would " u-uy74
2015-10-23  9:35         ` Laurent Bercot
2015-10-23 12:23           ` Laurent Bercot
2015-10-23 15:57           ` Tim Hockin
2015-10-23  5:26 ` Kurt H Maier
2015-10-24 21:33   ` Tim Hockin
2015-10-24 21:57     ` Kurt H Maier
2015-10-24 23:31       ` Rich Felker
2015-10-24 22:02     ` Rich Felker
2015-10-24 22:32       ` Tim Hockin
2015-10-25  8:20       ` u-uy74
2015-10-25 13:06       ` Jan Broer
2015-10-25 13:19         ` u-uy74
2015-10-25 13:39           ` Jan Broer
2015-10-25 14:08             ` u-uy74
2015-10-25 19:08         ` Rich Felker
2015-10-26  1:26       ` Isaac Dunham
2015-10-26 15:35         ` Rich Felker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151026174148.23543.qmail@ary.lan \
    --to=johnl@iecc.com \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).