[CRISP-TEAM] Suggested Text - III.A.3 (consultation with the community)

Nurani Nimpuno nurani at netnod.se
Tue Jan 13 12:39:50 CET 2015


On 13 jan 2015, at 12:04, Paul Rendek <rendek at ripe.net> wrote:

> Hello All,
> 
> Yes, that it Andrei, this new text you propose looks great to me.

+1
Nurani

> 
> I support it.
> 
> Paul
> 
> 
> On 1/13/15 10:58 AM, Andrei Robachevsky wrote:
>> Izumi Okutani wrote on 13/01/15 10:34:
>>> Thank you Andrei for drafing the suggested text which refers to opne
>>> consultation of the SLA.
>>> 
>>> Your suggested text looks good to me, and perhaps it would strengthen
>>> our rationale on why RIR staff will draft, if we could add something like:
>>> 
>>> It is expected that RIR staff will draft the specific language of this
>>> agreement *as the direct stakeholder of the number resources component
>>> of the IANA function*,
>>> 
>> Thank you Izumi, this addition makes sense to me. Perhaps (also changing
>> "the RIR staff" to "the RIRs" for consistency with other principles):
>> 
>> It is expected that the RIRs, as the contractual party of this
>> agreement, will draft the specific language of this agreement,...
>> 
>> So the new version will read:
>> 
>> NEW:
>> 
>> It is expected that the RIRs, as the contractual party of this
>> agreement, will draft the specific language of this agreement. During
>> the drafting process the RIRs are expected to consult the RIR
>> communities.  The drafting process will be guided by the principles
>> listed below. References to relevant sections of the current NTIA
>> agreement are also noted, as it is expected the new agreement will share
>> many of the same contractual goals and mechanisms.
>> 
>> 
>> Thanks,
>> 
>> Andrei
>> 
>> 
>>> (the part marked in * suggested to be added)
>>> 
>>> It doesn't have to be worded in the way I suggested but was wondering if
>>> it's worth explaining why RIRs are responsible, which seems like the
>>> source of confusion for some.
>>> 
>>> What are your thoughts?
>>> 
>>> Izumi
>>> 
>>> On 2015/01/13 18:18, Andrei Robachevsky wrote:
>>>> Hi,
>>>> 
>>>> Here is a suggested addition to the text in order to reflect the
>>>> expectation of the community that the RIRs will consult the community
>>>> when developing the SLAs. We believe that the concerns raised by people
>>>> on the ianaxfer related to some specific details of dispute resolution
>>>> and applicable law come from the fear that this is the last opportunity
>>>> for the community to voice their opinion. The additional statement is
>>>> aimed to assure this is not the case.
>>>> 
>>>> OLD:
>>>> 
>>>> It is expected that RIR staff will draft the specific language of this
>>>> agreement, and that the drafting process will be guided by the
>>>> principles listed below. References to relevant sections of the current
>>>> NTIA agreement are also noted, as it is expected the new agreement will
>>>> share many of the same contractual goals and mechanisms.
>>>> 
>>>> NEW:
>>>> 
>>>> It is expected that RIR staff will draft the specific language of this
>>>> agreement. During the drafting process RIR staff is expected to consult
>>>> the RIR communities.  The drafting process will be guided by the
>>>> principles listed below. References to relevant sections of the current
>>>> NTIA agreement are also noted, as it is expected the new agreement will
>>>> share many of the same contractual goals and mechanisms.
>>>> 
>>>> 
>>>> Your feedback is welcome,
>>>> 
>>>> Regards,
>>>> 
>>>> Andrei
>>>> 
>>>> _______________________________________________
>>>> CRISP mailing list
>>>> CRISP at nro.net
>>>> https://www.nro.net/mailman/listinfo/crisp
>>>> 
>>> 
>>> _______________________________________________
>>> CRISP mailing list
>>> CRISP at nro.net
>>> https://www.nro.net/mailman/listinfo/crisp
>>> 
>> _______________________________________________
>> CRISP mailing list
>> CRISP at nro.net
>> https://www.nro.net/mailman/listinfo/crisp
>> 
> 
> 
> _______________________________________________
> CRISP mailing list
> CRISP at nro.net
> https://www.nro.net/mailman/listinfo/crisp





More information about the CRISP mailing list