Hi, After a number of private discussions here in Buenos Aires I feel the need to clarify something:
In keeping with the way I understood the IETF to work, no one who works at ICANN who has responded on this topic is speaking on behalf of ICANN (including me). Like everyone else at the IETF, ICANN staff participate as individuals. If ICANN (the company or the community) wants to make a statement, I believe there is a liaison from the IETF to ICANN through which that statement would go. As far as I know, ICANN (either the company or the community) does not have an opinion on RFC 6761 or the issues relating to special use names (not just TLDs) it creates. Traditionally, ICANN, as the IANA Function Operator, has been more than happy to rely on external entities to define lists, e.g., ISO-3166/MA who defines the ISO-3166 2 letter codes. If the IETF wishes to define a list of names that are not to be used in the DNS for (presumably) technical reasons (in keeping with RFC 2860 section 4.3(a) or (c)), I am fairly certain the ICANN community (not ICANN the company -- staff simply implements the policies defined by the community) will create a clause in the next Applicant's Guide Book that says "you can't request a name on this list defined by the IETF; if you have a problem with that, take it up with them." Of course, I personally believe that it would simply be crazy for the IETF to drive into that particular swamp yelling "me too!"[0] and take on the legal responsibilities and liabilities associated with maintaining such an exclusion list (the Applicant's Guide Book is 300+ pages for a reason). Based on past experiences, I suspect saying "but it is only used in a particular context" is unlikely to dissuade too many folks with more lawyers and money than brains who want "their" TLD, but perhaps I'm wrong. Regards, -drc (ICANN CTO but speaking only for myself) [0] with apologies to Dave Clark > On Apr 5, 2016, at 4:35 PM, Ted Lemon <[email protected]> wrote: > > I wrote about six pages of comments on the recently-submitted special-use TLD > problem statement document. However, ultimately I concluded that it would > be easier to just write what I thought the problem statement should look like > rather than try to suggest (and then no doubt discuss one by one) a large set > of changes that I think it needs. > > So this weekend I spent quite a bit of time talking to various people who I > knew would have insight into the question, and the result is the draft I just > submitted. Ralph Droms was instrumental in inspiring me to write the > document, and helped me out by doing an initial review. > > I've included the submission announcement below. I realize that this is a > woefully late submission for discussion at IETF 95, since I mostly wrote it > yesterday, _at_ IETF 95. However, I think it may serve as a better starting > point for the discussion than the current problem statement draft, so if you > have time to read it, I would genuinely appreciate it if you could give it a > look. > > Thanks! > ________________________________________ > From: [email protected] [[email protected]] > Sent: Tuesday, April 5, 2016 15:09 > To: Ralph Droms; Ted Lemon > Subject: New Version Notification for draft-tldr-sutld-ps-00.txt > > A new version of I-D, draft-tldr-sutld-ps-00.txt > has been successfully submitted by Ted Lemon and posted to the > IETF repository. > > Name: draft-tldr-sutld-ps > Revision: 00 > Title: Special Use TLD Problem Statement > Document date: 2016-04-05 > Group: Individual Submission > Pages: 15 > URL: > https://www.ietf.org/internet-drafts/draft-tldr-sutld-ps-00.txt > Status: https://datatracker.ietf.org/doc/draft-tldr-sutld-ps/ > Htmlized: https://tools.ietf.org/html/draft-tldr-sutld-ps-00 > > > Abstract: > The Special-Use Domain Names registration policy in RFC 6761 has been > shown through experience to present unanticipated challenges. This > memo explores current IETF and non-IETF publications relating on > special-use TLDs, describes the history of domain names, and > enumerates some problems that have come up in connection with the > Special-Use Domain Names allocation process specifically as it > related to top-level domains. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > _______________________________________________ > DNSOP mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnsop _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
