proprietary (i.e. not standard- ized) services and applications over the public Internet (e.g. Skype, Viber, WhatsApp, BitTorrent), video streaming services over the public Internet (e.g. YouTube, Netflix, 6.6 QoS for Internet Access Service and Over-the-Top Data Services and many video sharing websites), social networking over the public Internet (e.g. Face- book, Twitter), cloud computing services over the public Internet (e.g. Google Docs, Amazon cloud services), and every existing and future service/application which will be provided over the public Internet. One may define OTT (i.e. data services) by specifying what they are not. OTT services are all IP-based services which are not provided over managed IP networks in the broadband access part (either fixed or mobile access). Although served in a best-effort manner, OTT services also have QoS requirements, but they are indirectly specified. How? All OTT services which are used by a given user are multiplexed with all other IP traffic from other instances of the same OTT service or other OTT services from the same or from other users who use the same Internet access (e.g. the same fixed broadband access or the same cell/base station in mobile broadband access network). The QoS and QoE directly are dependent upon the bitrates provided via fixed or mobile broadband and ultra-broadband access, SO the aggregate bitrate should be sustained. Therefore it is required for provided bitrates to be included in the SLA by the telecom operator (i.e. ISP), which is further monitored by a national regulator. For this purpose Internet traffic needs to be managed as well and all links that carry Internet traffic should be dimensioned to carry the aggregated IP traffic over given access, core, or transport IP network. So, traffic management, network planning, and dimensioning are well required for OTT services, i.e. for the Internet traffic to/from end-users. Are there any issues regarding the traffic management on one side and network neu- trality on the other? Well, network 