[CRISP-TEAM] Factors for implementaion which affects the timelines

[Andrei Robachevsky]

Thank you Izumi,

Izumi Okutani wrote on 09/06/15 16:40:
> Hi Andrei,
> 
> 
>> Could you please elaborate what you mean by "fallback mechanism"?
> 
> Sure, the idea is in case the RIRs have to switch the IANA Function Operator.
> Basically it is the point Vint Cerf has raised on the ianaxfer list.
> 

Understood.

Looking at this from a formal point of view isn't this what is in
Article 11 of the SLA "Continuity of operations"? Or do you think this
work will lead to changes in this article, prescribing specific fallback
mechanisms?

Andrei

> I can think of be two situation:
> 
>  1. When RIRs need to switch the IFO as emergency due to serious failure in service level
>     - Need to switch in a short period of time and there is no gurantee the existing IFO will be able to provide the data needed, within the timeframe needed for the switch
>     - Steps need to be defined on how to do this as well as identifying the need for data escrow for non-public data
> 
>  2. When RIRs switch the IFO with advanced notice
>     - Likely to have time for preparation but need to define steps
>     - If we are making open RFP, setting the criteria may be another factor in preparing implementation
> 
> 
> Izumi
> 
> On 2015/06/09 23:29, Andrei Robachevsky wrote:
>> Hi Izumi,
>>
>> Could you please elaborate what you mean by "fallback mechanism"?
>>
>> Thanks,
>>
>> Andrei
>>
>> Izumi Okutani wrote on 05/06/15 21:18:
>>>  d. Fallback mechanism
>>>    - Identify elements which needs fallback mechanism
>>>    - Define process
>>>    - Analyse possible impact
>>>    - Identify the need of RFP and if needed draft one
>