[At-Large] Cruz' revenge

[svg at milathan.ltd]

+1 

Stéphane Van Gelder



> Le 3 oct. 2016 à 20:12, Alberto Soto <asoto at ibero-americano.org> a écrit :
> 
> Hello. 
>  
> It is the first time that happened since the creation of ICANN. A quick risk analysis would say: <>
> - That custody during transport is not for ICANN
> - That duplication is not necessary
> - There was a very quick response
> - ICANN is working with transparency and accountability in solving critical problems, with costs adjusted as necessary to maintain the operation.
>  
> Kind regards
>  
> Alberto
> De: at-large-bounces at atlarge-lists.icann.org <mailto:at-large-bounces at atlarge-lists.icann.org> [mailto:at-large-bounces at atlarge-lists.icann.org <mailto:at-large-bounces at atlarge-lists.icann.org>] En nombre de Seun Ojedeji
> Enviado el: lunes, 03 de octubre de 2016 03:00 p.m.
> Para: Roberto Gaetano <roberto_gaetano at hotmail.com <mailto:roberto_gaetano at hotmail.com>>
> CC: At-Large Worldwide <at-large at atlarge-lists.icann.org <mailto:at-large at atlarge-lists.icann.org>>
> Asunto: Re: [At-Large] Cruz' revenge
>  
> Hello Roberto,
> 
> Please tell me the first question is "pun intended" ;-) As to the second; well I understand it's prudent to have backup of network services/data but what does having a backup of over 100 tons of hardware mean? I think it definitely will mean a lot of redundancy resulting to a waste of resources as well.
> 
> As I note from the announcement[1], looks like a number of the devices has been replaced. The remote hubs will be the major hit. I can imagine the ICANN tech are working around the logistics.
> 
> Regards
> 1. https://www.icann.org/news/blog/fire-on-cargo-ship-affects-it-equipment-bound-for-icann57-hyderabad <https://www.icann.org/news/blog/fire-on-cargo-ship-affects-it-equipment-bound-for-icann57-hyderabad>
> Sent from my LG G4
> Kindly excuse brevity and typos
> 
>  
> On 3 Oct 2016 18:21, "Roberto Gaetano" <roberto_gaetano at hotmail.com <mailto:roberto_gaetano at hotmail.com>> wrote:
>> http://domainincite.com/21067-ship-explosion-takes-icann-gear-out-of-action <http://domainincite.com/21067-ship-explosion-takes-icann-gear-out-of-action>
>>  
>> Two questions:
>> ·         We always talk about disaster recovery, duplication of resources, etc. Why did we not put in place these measures? The question will now be “if those folks cannot secure their own equipment, how can they be trusted to take care of the Internet?”
>> 
>> ·         What will be the real impact for the meeting? I cannot believe that we do not have backup solutions, as Murphy implies.
>> 
>> We live in interesting times indeed. Brings me back to 1998, when CORE servers were stolen.
>> Cheers,
>> R
>>  
>> 
>> _______________________________________________
>> At-Large mailing list
>> At-Large at atlarge-lists.icann.org <mailto:At-Large at atlarge-lists.icann.org>
>> https://atlarge-lists.icann.org/mailman/listinfo/at-large <https://atlarge-lists.icann.org/mailman/listinfo/at-large>
>> 
>> At-Large Official Site: http://atlarge.icann.org <http://atlarge.icann.org/>
> 
>  <https://www.avast.com/antivirus>	
> El software de antivirus Avast ha analizado este correo electrónico en busca de virus. 
> www.avast.com <https://www.avast.com/antivirus>
> _______________________________________________
> At-Large mailing list
> At-Large at atlarge-lists.icann.org <mailto:At-Large at atlarge-lists.icann.org>
> https://atlarge-lists.icann.org/mailman/listinfo/at-large <https://atlarge-lists.icann.org/mailman/listinfo/at-large>
> 
> At-Large Official Site: http://atlarge.icann.org <http://atlarge.icann.org/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://atlarge-lists.icann.org/pipermail/at-large/attachments/20161004/f2cfde6c/attachment.html>