David Conrad <[email protected]> writes: > whether the IETF “reserving” a TLD is intruding on ICANN’s territory. > > After WG LC, I propose that the WG chairs, ADs, IAB, and ICANN liaison > discuss this. My current expectation is that we probably will send ICANN > a > liaison to politely let them know what we are doing, so that they have the > opportunity to comment, and we would consider any feedback that they give, > returning the document back to the WG, if needed. > > I guess that’s marginally better than what the IETF did with RFC 6762 (i.e., > publish the RFC ‘reserving’ a TLD then, a year and a half later, issue the > liaison statement to invite discussion). The reluctance to ask the question > still > seems silly to me, particularly if one wishes to maintain good relations, but > this is clearly deep into the political sphere so I won’t bother arguing > further.
Hi David, <WITH my IAB hat on, but WITHOUT my ICANN board hat on> The IAB discussed a while back about "when" to send a statement to the ICANN board about this issue. The decision was that if the WG didn't have consensus yet (we have a bit more of one now than then), it sure seem appropriate to send ICANN a note with a "maybe we might if we can ever come to internal agreement". In other words, it's just wasting their time if we haven't even decided something is a good idea. So, the decision made at the time was: once the WG has concluded that something is a good idea (a draft passes WG last call), *then* it seems like the right time to send a message to ICANN about our plans. That being said, the IAB is also aware of this issue and will be further discussing it in the next few weeks. If you wish to make arguments about why the previous decision about whether the question should be asked immediately, and what the nature of that question should be: I'm all ears and will pass it on (at least in aggregated consensus form) during future IAB discussions. -- Wes Hardaker USC/ISI _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
