Archive:Skype protocol: Difference between revisions
Filled in 2 bare reference(s) with reFill () |
m →Peer-to-peer architecture: c/e |
||
| Line 16: | Line 16: | ||
Skype was the first [[peer-to-peer]] IP telephony network.<ref>Page 11 in {{cite arXiv |eprint=cs/0412017v1 |title= An analysis of the Skype peer-to-peer Internet telephony protocol |class= cs.NI |year= 2004 |version= |accessdate= |author1= Salman A. Baset |author2= Henning Schulzrinne }}</ref> The network contains three types of entities: ''[[Supernode (networking)|supernodes]]'', ordinary nodes, and the login server. Each client maintains a ''host cache'' with the [[IP address]] and port numbers of reachable supernodes. The Skype user directory is decentralized and distributed among the supernodes in the network. | Skype was the first [[peer-to-peer]] IP telephony network.<ref>Page 11 in {{cite arXiv |eprint=cs/0412017v1 |title= An analysis of the Skype peer-to-peer Internet telephony protocol |class= cs.NI |year= 2004 |version= |accessdate= |author1= Salman A. Baset |author2= Henning Schulzrinne }}</ref> The network contains three types of entities: ''[[Supernode (networking)|supernodes]]'', ordinary nodes, and the login server. Each client maintains a ''host cache'' with the [[IP address]] and port numbers of reachable supernodes. The Skype user directory is decentralized and distributed among the supernodes in the network. | ||
Previously any client with good bandwidth, no restrictions due to firewall or NAT, and adequate processing power could become a supernode. This placed an extra burden on those who connected to the Internet without | Previously any client with good bandwidth, no restrictions due to [[firewall (networking)|firewall]] or [[network address translation]] (NAT), and adequate processing power could become a supernode. This placed an extra burden on those who connected to the Internet without NAT, as Skype used their computers and Internet connections as third parties for [[UDP hole punching]] (to directly connect two clients both behind NAT) or to completely relay other users' calls. In 2012, Microsoft altered the design of the network, and brought all supernodes under their control as hosted servers in data centres.<ref>{{cite news|last=Branscombe|first=Mary|title=Forget the conspiracy theories: Skype's supernodes belong in the cloud|url=http://www.zdnet.com/forget-the-conspiracy-theories-skypes-supernodes-belong-in-the-cloud-7000001720/|accessdate=17 June 2013|newspaper=500 words into the future (ZDNet)|date=27 July 2012}}</ref> Microsoft at the time defended the move, saying they "believe this approach has immediate performance, scalability and availability benefits for the hundreds of millions of users that make up the Skype community."<ref>{{cite news|title=Skype replaces P2P supernodes with Linux boxes hosted by Microsoft (updated)|url=http://arstechnica.com/business/2012/05/skype-replaces-p2p-supernodes-with-linux-boxes-hosted-by-microsoft/|accessdate=17 June 2013|newspaper=Ars Technica|date=2 May 2012}}</ref> At the time there was some concern regarding the privacy implications of the change,<ref>{{cite news|last=Kosner|first=Anthony|title=Will Microsoft's Changes To The Architecture Of Skype Make It Easier To Snoop?|url=http://www.forbes.com/sites/anthonykosner/2012/07/18/did-microsoft-change-the-architecture-of-skype-to-make-it-easier-to-snoop/|accessdate=17 June 2013|newspaper=Forbes blog|date=18 July 2012}}</ref> which appear to have been proven true with the revelation of the [[PRISM (surveillance program)|PRISM]] surveillance program in June 2013.<ref>{{cite news|last=Gallagher|first=Ryan|title=Newly Revealed PRISM Snooping Makes Verizon Surveillance Look Like Kids' Stuff|url=http://www.slate.com/blogs/future_tense/2013/06/06/nsa_prism_surveillance_private_data_from_google_microsoft_skype_apple_yahoo.html|accessdate=17 June 2013|newspaper=Slate blog|date=6 June 2013}}</ref><ref>{{cite news|last=Greenwald|first=Glenn|title=NSA Prism program taps in to user data of Apple, Google and others|url=https://www.theguardian.com/world/2013/jun/06/us-tech-giants-nsa-data|accessdate=17 June 2013|newspaper=The Guardian|date=7 June 2013}}</ref> | ||
Skype does not support the use of the [[IPv6]] protocol,<ref>{{cite web|url=https://twitter.com/SkypeTalks/status/264057558262747136|title=Skype does not support IPv6.|publisher=Skype official Twitter account|date=1 Nov 2012|accessdate=4 Nov 2012}}</ref> which would greatly reduce the complexity associated with the aforementioned IPv4 communication structure. | Skype does not support the use of the [[IPv6]] protocol,<ref>{{cite web|url=https://twitter.com/SkypeTalks/status/264057558262747136|title=Skype does not support IPv6.|publisher=Skype official Twitter account|date=1 Nov 2012|accessdate=4 Nov 2012}}</ref> which would greatly reduce the complexity associated with the aforementioned IPv4 communication structure. | ||
Supernodes relay communications on behalf of two other clients, both of which are behind | Supernodes relay communications on behalf of two other clients, both of which are behind firewalls or "one-to-many" network address translation. | ||
Without relaying by the | Without relaying by the supernodes, two clients with firewall or NAT difficulties would be unable to make or receive calls from one another. Skype tries to get the two ends to negotiate the connection details directly, but sometimes the sum of problems at both ends can prevent direct conversation being established. | ||
The problems with firewalls and NAT can be: | The problems with firewalls and NAT can be: | ||
* The external port numbers or IP address are not derivable, because NAT rewrites them | * The external port numbers or IP address are not derivable, because NAT rewrites them | ||
* The firewall and NAT in use prevents the session being received | * The firewall and NAT in use prevents the session being received | ||
* UDP is not usable due to NAT issues, such as timeout | * UDP is not usable due to NAT issues, such as timeout | ||
* | * Firewalls block many ports | ||
* TCP through many-to-one NAT is always "outward only" by default | * TCP through many-to-one NAT is always "outward only" by default – adding port-forwarding settings to the NAT router can allow reception of TCP sessions | ||
Supernodes are grouped into ''slots'' (9–10 supernodes), and slots are grouped into ''blocks'' (8 slots). | Supernodes are grouped into ''slots'' (9–10 supernodes), and slots are grouped into ''blocks'' (8 slots). | ||