Re: [Ianaplan] A draft for your review

[JFC Morfin <[e-mail]>]

Suzanne,

IANAL but I know that contracts are protocols between 
people/organizations. Asking engineers to discuss contracts seems as 
sure as asking lawyers to write a technical standard RFC.

At 16:51 01/11/2014, Suzanne Woolf wrote:
>On the first-- as already pointed out, we've got existing IETF 
>authority (the MoU) and process (RFC 6761, with all the accompanying 
>machinery of writing drafts and making the case for a change in the 
>relevant registry under its rules). We've also got the machinery to 
>change that process if it's inadequate: normal IETF process for 
>updating or obsoleting an RFC, a WG whose charter includes such 
>namespace issues (DNSOP), and an IAB liaison statement sent to ICANN 
>specifically on this topic, also under IETF process and an existing 
>liaison relationship (https://datatracker.ietf.org/liaison/1351/). I 
>can speak as DNSOP co-chair that we're interested in input, because 
>applying RFC 6761 has already proven problematic and people keep 
>writing drafts that attempt it. And I can't speak for the IAB, but 
>response to the liaison statement would probably be welcome too.
>
>If people feel coordination on a specific  "technical use names" 
>issue is needed, there are mechanisms in place today to do it. If 
>people feel better coordination process is needed (such as might 
>follow from a clearer definition of "technical use names"), there 
>are mechanisms in place today to create them too, and even recent 
>suggestions (the DNSOP re-charter, the IAB liaison statement) that 
>people might want to consider invoking them.

I am afraid I do not see in which manner having mechanisms to achieve 
something makes it so that all of this will be achieved. RFC 2860 is 
clear about this: in case of a standing disagreement, RFC 2860 
Section 4.3, Note: "In the event ICANN adopts a policy that prevents 
it from complying with the provisions of this Section 4 with respect 
to the assignments described in (a) - (c) above, ICANN will notify 
the IETF, which may then exercise its ability to cancel this MOU 
under Section 2 above."

This language does not permit ICANN to be accountable concerning the 
NTIA's demand:  "Maintain the security, stability, and resiliency of 
the Internet DNS". The IETF has the ultimate capacity of decision 
and, therefore, responsibility (actually ISOC has it through the 
appeal process).


>At 17:52 01/11/2014, Andrew Sullivan wrote:
>But that didn't happen, which suggests to me that the division of 
>labour, again, is working.

IMHO, to make the past the guarantee of your future is to ensure that 
you will be fooled.


>At 18:53 01/11/2014, David Conrad wrote:
>Given the IETF has delegated administration via RFC 2860, I would 
>have thought it useful to formally include the delegatee in 
>discussions related to the resource (either domain names or IP 
>addresses) being discussed, not just have the decision be solely 
>dependent on the IESG's opinion.

David, is this truly the "status quo" :-)?

If I understand you, what ICANN wants is to control things through RFC 2960bis.

I have 255 classes that I can use and IETF has a few thousand that it 
can freely affect. Perhaps it is time to contract that the ICANN/NTIA 
"IN" Class is the undisputed ICANN one.

If there are too many or buggy TLDs in the root of that class, users 
will know about it and competition will play its role.

jfc