Joost Application Behavior:
----------------------------------
1. First, the peer initiates the secure HTTPS to www.theveniceproject.com (89.251.2.86 ) 85 
    and then it sends three more https encrypted sessions to the following servers

Ø	tolbiac.ops.theveniceproject.com (89.251.4.175) /*backend servers*/
Ø	adengine.ops.theveniceproject.com (89.251.4.175)
Ø	tracker.ops.theveniceproject.com (89.251.4.175)

2. Then, the peer checks the version of the software through sending a HTTP GET 
    request to version.ops.theveniceproject.com.

3. Finally, it connects to the super node (lid.ops.theveniceproject.com) to establish 
    connections with other peers and accessing video content.

Notes:
--------
1. Joost has got official UDP and TCP ports 4166 assigned by the IANA 
    on April 23, 2007. But older versions (Joost 0.9.2 or before) uses different ports 
    UDP 33333 and TCP 5223. Some other older versions might be using   
    UDP ports: 1643-1651 and 44616  

2. Joost distributes licensed content. Thus all new contents are introduced through its own   
    servers. Some of the server addresses are as follows:
Ø	212.8.163.0/24 (Belgium)
Ø	89.251.0.0/23 (Netherlands)
Ø	213.207.101.128/25 (Netherlands)
Ø	212.187.185.0.24 (United Kingdom)
Ø	4.71.105.0/24 (Los Angles, California)

2. Ordinary Joost nodes receives the video content from Joost-operated servers which 
    operates on port 33333. Thus, traffic from Joost oriented servers can be blocked but it   
    will not block traffic from other ordinary Joost nodes. (Majority of the traffic comes 
    from the Joost owned servers only.

3. Packets under 200 bytes are considered control packets, and data packets are 1000 
    bytes or more.