It appears that Independent Submissions Editor (Eliot Lear) 
<rfc-...@rfc-editor.org> said:
>  On the one hand, we need to find a 
>way for people to explore alternative namespaces that look a bit like 
>domain names.  On the other hand, we don't want to create problems with 
>user expectations.

It is fine for people to look at other ways to do naming on the
Internet, but that does not mean they get to squat on the DNS
namespace.

Look at the handle system or I guess DONA now. It has its own
namespace or numberspace, and it has its own way to look stuff up.
Some of their registry-like-things have made their own arrangements to
do DNS gatewaying, like https://dx.doi.org/10.2345/blah, which is fine
and neither our problem nor ICANN's.

GNS is welcome to set up their own name space and provide their own
resolution system. If they want to do a GNS->DNS gateway, that's fine.
But the DNS is the DNS, and things that aren't the DNS don't go there.

R's,
John

PS: Yeah, I know about .onion, but one unfortunate decision does not a policy 
make.

_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to