Common use of Class of Service Clause in Contracts

Class of Service. The E-Line EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. IETF RFC 2474). The Verizon traffic priority classes are identified as:

Appears in 7 contracts

Sources: Service Level Agreement, Service Level Agreement, Service Level Agreement

Class of Service. The E-Line LAN EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. IETF RFC 2474). The Verizon traffic priority classes are identified as:: EF Real Time Data (RT) 5 and 6 AF4, AF41, AF42/43, AF3, AF31, AF32/33 Priority Data (PD) 4 AF2AF21, AF 22/23 Business Data (BD) 2 and 3 BE Basic Data (B) 0,1, and 7

Appears in 2 contracts

Sources: Service Level Agreement, Service Level Agreement

Class of Service. The E-Line EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. IETF RFC 2474). The Verizon traffic priority classes are identified as:: AF4, AF41, AF42/43, AF3, AF31, AF32/33 Priority Data (PD) 4

Appears in 1 contract

Sources: Service Level Agreement

Class of Service. The E-Line LAN EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. IETF RFC 2474). The Verizon traffic priority classes are identified as:: Diff-Serv Queue E-LAN EVC Class of ServiceCoS Naming 802.1q P-bits AF4, AF41, AF42/43, AF3, AF31, AF32/33 Priority Data (PD) 4

Appears in 1 contract

Sources: Service Level Agreement

Class of Service. The E-Line EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Diff-Serv”) model (i.e. IETF RFC 2474). The Verizon traffic priority classes are identified as:

Appears in 1 contract

Sources: Service Level Agreement

Class of Service. The E-Line LAN EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. IETF RFC 2474). The Verizon traffic priority classes are identified as:: AF4, AF41, AF42/43, AF3, AF31, AF32/33 Priority Data (PD) 4

Appears in 1 contract

Sources: Service Level Agreement

Class of Service. The E-Line EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. i.e.i.e., IETF RFC 2474). The Verizon traffic priority classes are identified as:: AF4, AF41, AF42/43, AF3, AF31, AF32/33 Priority Data (PD) 4

Appears in 1 contract

Sources: Service Level Agreement

Class of Service. The E-Line LAN EVC class of service (“CoS”) delivery methodology is based on 802.1q IEEE standards and follows the Internet Engineering Task Force (“IETF”) Differentiated Services (“Diff- Serv”) model (i.e. i.e.i.e., IETF RFC 2474). The Verizon traffic priority classes are identified as:: AF4, AF41, AF42/43, AF3, AF31, AF32/33 Priority Data (PD) 4

Appears in 1 contract

Sources: Service Level Agreement