On 11/28/19 5:15 PM, John R Levine wrote:
On Thu, 28 Nov 2019, Doug Barton wrote:
I don't see how relying on ISO's advice is poaching. They say:
You, like Ted, are ignoring the fact that ISO can choose to change
those rules.
The user assigned codes are part of the published ISO 3166 standard. If
that's not stable enough, neither is any ccTLD. What if they decided to
swap .US and .SU? Jaap assured us they're not going to change, and he
should know.
I don't doubt Jaap. What I doubt is that any organization as political
as ISO (or ICANN) will hold preferences stable in the absence of a
controlling policy.
Ok, so if you think there is a risk here, then it should be mitigated
by working together with ICANN ...
The politics about this at ICANN are hopeless. There are still six
applications for corp, home, and mail who would object loudly if ICANN
said they were permanently unavailable and who torpedoed Lyman Chapin's
proposal to add them to the 6761 list. Fighting that is not a good use
of anyone's time.
Given the time that's passed this landscape may have changed. But if it
has not for CORP, HOME, and MAIL; why not open the discussion about
whatever strings we decide are useful instead?
Doug
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
