1. Issues with MONET Prasad

2. Latency Overhead Every single HTTP request has to go through Waypoint Selection This could add a substantial amount of user perceived latency, and after a long wait, user might be reported of a permanent failure! If peers are used, overhead of authentication introduces more delays!

3. Scalability issues Not End-to-End Network is made substantially complex Resilient Overlay Network is known to have severe scalability issues. This carries the same issues with it

4. Failure issues It cannot guarantee one to two nines availability if the server itself has failed It cannot guarantee one to two nines availability if the local proxy itself has failed It cannot guarantee one to two nines availability if there is a link common to all the alternate paths and that has failed! As this cannot guarantee the paths do not share links, how does it really guarantee one to two nines availability in case of common links failures? The paper itself acknowledges it cannot handle software failures!

5. History Usage issues Usage of history hinders accuracy because of transient nature of the network

6. Access Control Issues The paper acknowledges the issue with access control Suggested solution is cumbersome to say the least

7. Vagueness in specification The paper does not give any details about how MONET uses multi-homed sites to achieve its goal, although they have a paragraph for this topic! There is no indication of how the waypoint starts its operation

8. Security Issues Proxy pollution problem is exacerbated If peers are not authenticated, DOS possibility exists

9. Efficiency Issues Lot of effort is wasted (if 4 SYNs are sent, 3 are wasted!) Peers end up doing good amount of work for nothing RTTVAR-based scheme is noticeably inferior to k-means clustering At best, this is just tries to make a good guess work rather inefficiently!

10. Congestion Issues If the only available path is severely congested, waypoint could declare unavailability and report error back to the client – this brings in the correctness issue!

11. Finally… MONET tries to solve the problem of availability by: Introducing lot of complexity Introducing substantial latency Introducing scalability problems Introducing security problems And, it doesn’t fully solve the problem of availability!