-
Notifications
You must be signed in to change notification settings - Fork 1
/
related_work
60 lines (53 loc) · 2.92 KB
/
related_work
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Multicast discussion
---------
- [Diot 2000]
@article{diot2000deployment,
title={Deployment issues for the IP multicast service and architecture},
author={Diot, Christophe and Levine, Brian Neil and Lyles, Bryan and Kassem, Hassan and Balensiefen, Doug},
journal={IEEE network},
volume={14},
number={1},
pages={78--88},
year={2000},
publisher={IEEE}
}
- [Sharma 2003]
@article{sharma2003ip,
title={IP multicast operational network management: design, challenges, and experiences},
author={Sharma, Puneet and Perry, Edward and Malpani, Radhika},
journal={IEEE network},
volume={17},
number={2},
pages={49--55},
year={2003},
publisher={IEEE}
}
Examples of multicast being used
----------------------------------
- [Internet2 Multicast 2007]
- [BBC Multicast 2007]
https://support.bbc.co.uk/multicast/
- [ESM 2007]
@article{chu2002case,
title={A case for end system multicast},
author={Chu, Yang-hua and Rao, Sanjay G and Seshan, Srinivasan and Zhang, Hui},
journal={IEEE Journal on selected areas in communications},
volume={20},
number={8},
pages={1456--1471},
year={2002},
publisher={IEEE}
}
Netflix Open Connect Appliances
-------------------------------
https://openconnect.netflix.com/Open-Connect-Overview.pdf
Netflix uses its own content delivery network called Open Connect. It also partners with ISPs to host their Open Connect Appliances to bring content closer to customers. Seems to use TCP.
HTTP Persistent Connection
--------------------------
https://en.wikipedia.org/wiki/HTTP_persistent_connection
http initially was a connectionless TCP protocol. It would need to create a new TCP connection/request for each individual image and object within a webpage until the full page was loaded. To eliminate the overhead of multiple TCP connection setup and breakdown, newer versions of http implemented persistent connection, which set up one connection for a page and kept the connection open until all the requests of the page were completed.
http 2.0 allows for "server push", in which the server prematurely sends relevant site data to user even before the user has requested it to cut down latency. For instance, after the first request for the webpage layout, the server knows that the user will also ask for all the images in the webpage so it can send that immediately instead of waiting for the following requests. Need to look into this more. Does not seem to care about how hot records are, only if the webpage developer has explicitly identified what files/objects should be sent once the first request comes in.
BitTorrent
----------
http://www.bittorrent.org/beps/bep_0029.html
Originally, used TCP, but TCP gave equal priority to bittorrent as other urgent programs. So the uTorrent transfer protocol (uTP) was created which uses UDP and an application layer reliability implementation. uTP can throttle itself when the packet buffer is full with the goal of leaving non-background internet tasks unaffected by uTP.