On 4 Jul 2015, at 1:56, manning wrote:
So I -think- we are on the same page here, although I would replace your use
of the phrase, “name space” with domain. We have empirical evidence of
multiple domains using the same name space.
(Fred Baker persuaded me that there is a single name space,
I guess my question here is, what would prevent House Finch Feathers OY from
applying
for the DNS(IN) string ONION from ICANN because they want that as a TLD in the
IN
class?
At the moment, nothing.
Remember, we also have a draft about .HOME and .CORP and .MAIL. ICANN
says they're not
On 4 Jul 2015, at 8:31, John Levine wrote:
I guess my question here is, what would prevent House Finch Feathers OY from
applying
for the DNS(IN) string ONION from ICANN because they want that as a TLD in
the IN
class?
At the moment, nothing.
Remember, we also have a draft about .HOME
See the end for something provocative.
ICANN do say what strings in the name space should be TLDs.
IETF do say what strings in the name space should NOT be TLDs.
The rest are just strings waiting to end up in one of the two groups.
Patrik
Perfectly stated. There is really just one
All
I'm hoping to see some discussion on the mailing list on this, or we'll
bring it up in Prague.
This draft has been languishing that was resolved with some discussion,
and it's time to either move it along or shut it down.
tim
On 7/3/15 10:26 AM, Ray Bellis wrote:
This update to the
I'll have extensive comments, mostly positive, after the weekend.
On July 4, 2015 4:06:31 PM GMT+01:00, Tim Wicinski tjw.i...@gmail.com wrote:
All
I'm hoping to see some discussion on the mailing list on this, or we'll
bring it up in Prague.
This draft has been languishing that was resolved
(no hats)
On Jul 4, 2015, at 3:12 AM, Patrik Fältström p...@frobbit.se wrote:
Once again:
ICANN do say what strings in the name space should be TLDs.
IETF do say what strings in the name space should NOT be TLDs.
In the interests of precision in our discussion: I’m not convinced that’s
On 4 Jul 2015, at 18:29, Suzanne Woolf wrote:
It seems to me, from long experience of both organizations, that ICANN says
what names should and shouldn’t be in the DNS root zone—
Well, I have never seen ICANN saying definite no to any string. ICANN only
say no, this string is not to be ok in
On Fri, Jul 03, 2015 at 06:43:13AM -0700, manning wrote:
Actually, there IS an escape method already defined. We just don’t use it
much these days.
It’s called “class”
Classes don't work in the general case, because CNAME (and following
it, DNAME) is class-independent. This is arguably a
Avoiding collisions between DNS and non-DNS use of domain names is
probably important to us (to some degree that’s what we’re trying to
decide). But I have thought, and continue to think, that we make a
serious mistake if we regard it as our purpose to “say what strings in
the name space
10 matches
Mail list logo
