Agreed, although much of the work is to make this so. I think the testnet testing will be crucial, if it is relatively bug free then the SLA should be 100%. There are issues we consider such as worldwide electricity outage and how the network recovers from that (not simple) as all close groups are a huge distance apart and the reconfiguration is very very fast as nodes come back on.
It should be a critical measure of the network though, to test from a fully working system, trigger a power off in an instant and then random power ups to check the assumptions are correct. Nodes initially should be responsible for huge data range, but with little data, as nodes connect they bring more data, but a closer range between them (so less responsibility). Huge data movements will occur though.
Another aspect is huge segmentation, for safecoin for instance the spending on the small side should stop as the large side will carry the weight of consensus on rejoin, there are some cool parts there though as the holder of any coin will be on one half of the segment though, except when he gets a plane or changes provider of course (and edge case). (NB bitcoin has this also, but no answer I know of yet)
This is only one aspect though, there is also the upgrade aspects which are more tricky. We cannot repeat the skype outage where all win servers updated and rebooted with a fault bringing the network down in a flood of data (avalanche failure). So upgrades handle randomly, but hit means we have to watch API breaking changes and occasionally have nodes be able to act as old nodes on old data and messages etc.
There are a few other areas like this, quite a lot to consider. The testnets will be crucial to find such flaws, especially as they will be small and therefore weak networks.
Soon everyone will have the mushy head syndrome of a maidsafe developer we occasionally walk into door frames missing the opening completely and some of these things are why