[CRISP-TEAM] Draft Notes CRISP 7th Teleconference

[Nurani Nimpuno]

Dear Laureana,

Thank you so much for your prompt and detailed notes.

If I may, just two minor amendments:


> NN: I generally agree with MA. I perceived a slight differentiation with what CN was saying. Leave the wording to the legal team, but the community defines which issues are to be included. At RIPE NCC we think that it’s basically up to us and not to ICANN to set the terms for this. We want to avoid specific requirements for termination. Those things need to be written so that we (the community) get to decide whether the contract is terminated or not.


Replace with:

NN: I generally agree with MA. I perceived a slight differentiation with what CN was saying. Leave the wording to the legal team, but the community defines which issues are to be included. In the RIPE community, there have been strong voices expressing that it needs to be up to us to set the terms. We want to avoid having  requirements that makes it difficult for us to terminate for example. They need to be written so that we (the community) get to decide whether the contract is terminated or not.


> NN: I think it’s a great idea to ask for more input in different ways. I have 2 concerns with the suggestion. 1) We’ve tried to be very clear about the process through which we gather community input. By adding a new thing we might create confusion. 2) How does this fit into the input we’ve received earlier as we’ve been clear that we wanted input on the IANA XFER list? My concern is the timing – we have a very short timeline. After the second draft is published we don’t have a lot of time. How do we as CRISP team manage that input? Do we take that back to the global mailing list? I have concerns about the process and concerns about the timing


Replace with:

NN: I think it’s a great idea to ask for more input in different ways. However, I have 2 concerns with the suggestion. 1) We’ve tried to be very clear about the process through which we gather community input. By adding a new thing we might create confusion as to how and where to provide input. How does this fit into the input we’ve received earlier, as we’ve been clear that we wanted input on the IANA XFER list? If there is conflicting input after the second draft, how do we foresee that process? I am also unclear about what input a teleconference in the final days would bring, that people have not brought to their communities or the ianaxfer list so far. 2) My second concern is simply the timing - we have a very short timeline. After the second draft is published, there are only a couple of days before the final wrap-up. How do we as CRISP team manage that input? Do we take that back to the global mailing list? And what is the timing of that? So, I have concerns about the process and concerns about the timing.


> NN: I just wanted to say that my interpretation of the comments (HPH on the ML) – I think he was reasoning that you could give it to the NRO NC but that it would also make sense to give it to a separate body.

Replace with:
NN: I just wanted to say that my interpretation of the comments (HPH on the ML) – I think he was reasoning that you could give it to the NRO NC as that exists and is functioning, but that it would also make sense to give it to a separate body as it would then not lead to mission creep for the NRO NC.

Thanks.
Kind regards,

Nurani


----------------------------------------------------------
Nurani Nimpuno, Head of Outreach & Communications, Netnod       
<nurani at netnod.se>                   http://www.netnod.se



On 4 jan 2015, at 18:14, Laureana Pavon <laureana at lacnic.net> wrote:

> Dear CRISP Team,
> 
> I'm attaching the draft notes of the 7th CRISP teleconference held on January 2nd for your perusal.
> 
> Please let me know if you have any comments or suggestions.
> 
> Laureana Pavon
> (on behalf of the NRO Secretariat)
> <ASO AC January 2nd meeting-DRAFT NOTES-v01.docx>_______________________________________________
> CRISP mailing list
> CRISP at nro.net
> https://www.nro.net/mailman/listinfo/crisp