> On May 14, 2015, at 11:21 AM, David Conrad <d...@virtualized.org> wrote: > > However, as I said, how it is labeled is somewhat irrelevant. What matters to > me is figuring out the objective criteria by which we can determine whether > and/or how a particular label is being used so much that its delegation in > the DNS would damage the Internet's security/stability. So far, all the > criteria I've seen to date boils down to Justice Stewart's "I know it when I > see it" which makes me uncomfortable.
I think the idea that there could be any such criterion is aptly refuted by the existence of an adjudication process in ICANN, as well as the difficulty ICANN has had in actually selling TLDs. Despite our wishes to the contrary, processes of this sort are not like protocols, and typically can't run themselves. That is why the human element is so heavily relied on. IETF process in particular absolutely cannot work without this human element, which is baked in and referred to as "rough consensus." >> But in the case of .onion, .corp and .home, we _do_ have such a reason. > > Great! What is that reason so it can be encoded into an RFC, can be > measured, and there can be an objective evaluation as to whether a > prospective name can be placed into the Special Use Names registry? The technical argument is different in each case. In the case of .onion, I refer you to the ToR documentation as well as the two drafts that are being discussed. In the case of .corp and .home, the organizations that started using these names had reasons for using them. If these reasons were documented in drafts and presented to the working group, I would expect the working group to consider them, and either reach consensus to publish, or not. I would expect that consensus to be arrived at on the technical merits of the proposal, not on the basis of various participants' various opinions about fairness or amount of traffic at the root. Until that happens, the IETF's position on both .corp and .home is nonexistent, and they should not be put in the special use names registry. Irrespective of the technical merits of .corp and .home, of course, the DNSOP working group might well publish a document talking about the operational implications of .corp and .home with respect to the root, but I personally see very little value in doing so, since the leaks of these names are likely coming from devices operated by people who would never read such a document.
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
