Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expand on desire for special-use names to be human-readable #36

Closed
rdroms opened this issue Feb 3, 2017 · 7 comments
Closed

Expand on desire for special-use names to be human-readable #36

rdroms opened this issue Feb 3, 2017 · 7 comments

Comments

@rdroms
Copy link
Collaborator

rdroms commented Feb 3, 2017

From Suzanne Woolf
https://www.ietf.org/mail-archive/web/dnsop/current/msg19170.html

Problems associated with Special-Use Domain Names

  1. The text “It is generally assumed that protocols that need a special-use name need a human-readable special-use name. This assumption may not be warranted in all cases.” doesn’t go far enough. People assume both that they need a human-readable name, and that they need a single label name (“TLD”). Both assumptions, especially together, create a perception that there’s a limited number of useful domain names in the world, with corresponding tendencies to treat the underlying resource as scarce. Domain names aren’t scarce; domain names that meet some of the implicit assumptions people make about them might well be.
@rdroms
Copy link
Collaborator Author

rdroms commented Feb 13, 2017

OLD:

o It is generally assumed that protocols that need a special-use
name need a human-readable special-use name. This assumption may
not be warranted in all cases.

NEW:

o It is generally assumed that protocols that need a special-use
name need a mnemonic, single-label, human-readable special-use
name. This assumption may not be warranted in all cases.

@wkumari
Copy link
Collaborator

wkumari commented Feb 15, 2017

Perhaps we should add in something about why some people want many of them to be human readable / typable?

Also, there are 2.8e+12 possible 8 letter TLDs, so even if people make the assumptions we still have, er, lots...

@rdroms
Copy link
Collaborator Author

rdroms commented Feb 15, 2017

And, I suppose, why the assumption may not be warranted.

@rdroms
Copy link
Collaborator Author

rdroms commented Feb 20, 2017

Updated suggested fix:

OLD:

o It is generally assumed that protocols that need a special-use
name need a human-readable special-use name. This assumption may
not be warranted in all cases.

NEW:

o It is generally assumed that protocols that need a special-use
name need a mnemonic, single-label, human-readable special-use
name, for use in user interfaces such as command lines or URL
entry fields. This assumption may not be warranted in all cases;
for example, in applications where the DNS name is never visible
to a user.

@Abhayakara
Copy link
Owner

How about "while this assumption is likely correct in some cases, it is likely not correct in all cases, ..."

@Abhayakara
Copy link
Owner

we have consensus

@rdroms
Copy link
Collaborator Author

rdroms commented Mar 3, 2017

Edits completed

@rdroms rdroms closed this as completed Mar 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants