curity and network integrity management are also necessary, but again, this should not go beyond the actual requirements. Network neutrality means that all traffic is treated equally over the IAS. However, the ISP may apply traffic classes by using DPI then differentiating and classifying IP packets belonging to different types of applications or traffic types (e.g. audio, video, data) for their transfer over the core or transit networks (e.g. by using separate VPNs). In such cases certain Internet traffic classes will be prioritized over others (e.g. in core and transit networks), which may lead to degradations of OTT services that are classified into lower priority classes in this case, especially in time periods when there is high volume of high(er) priority traffic in the network. However, proper packet scheduling at network nodes (e.g. routers, gateways) as well as network dimensioning (regarding the capacity of links on all paths over the operator's IP networks) may prevent such degradations for OTT services provided over the IAS (i.e. through the public Internet network). Other degradation of both IAS and specific OTT services (provided over IAS) can be due to high volume of traffic of specialized (i.e. managed) services over the same IP networks. Both types of services, Internet-based and specialized (managed), can be pro- vided over the same broadband and ultra-broadband IP networks, with applied traffic engineering for sharing of the total bandwidth (e.g. dedicated bandwidth for IAS and for managed IP services, or shared bandwidth between IAS and managed IP services, with priority applied to managed IP services in the ISP's network) [5]. However, in peak hours congestion may occur for specialized services which may use certain bandwidth of the IAS and with that degrade the IAS and individual OTT services provided through the IAS. However, if the bandwidth for the IAS is strictly reserved, specialized services may have lower QoS than specified or contracted (e.g. more VoIP calls rejected or dropped in mo