Loading Profile...
Shaping and Policing of Spotify Network Streams
Spotify utilizes P2P implementations to deal with content distribution. A result of this is a potentially high utilization of upstream bandwith; even with an idle client. This isn't a problem for most users, but may cause serious headache for network admins in campus- and corporate networks, where bandwidth is a limited resource.
There are many half-measures to deal with this problem, but sadly, the easiest one is to simply block the service.
I, like many other network engineers and netadmins, would like the ability to classify Spotify data streams, allowing policing and/or shaping of the service. The easiest ways to implement this would be;
* Known TCP/UDP Ports for all traffic.
* Ability to set DSCP/IP Precedence value in the software.
* NBAR - Network Based Application Recongnition (Cisco) template.
Are there any current plans to enhance the networking support of Spotify?
There are many half-measures to deal with this problem, but sadly, the easiest one is to simply block the service.
I, like many other network engineers and netadmins, would like the ability to classify Spotify data streams, allowing policing and/or shaping of the service. The easiest ways to implement this would be;
* Known TCP/UDP Ports for all traffic.
* Ability to set DSCP/IP Precedence value in the software.
* NBAR - Network Based Application Recongnition (Cisco) template.
Are there any current plans to enhance the networking support of Spotify?
I’m concerned.
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
