Application Specific Behavior Sample Clauses

Application Specific Behavior. BEK does not make use of any application-specific network management practices. BEK does not favor, modify, inhibit, rate control or block any specific protocols, protocol ports or fields, or any applications or classes of applications.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Application Specific Behavior. At our Internet edge, the TOS/DSCP bit on packets is cleared, and set to high priority on packets determined to be Voice over IP using the Cisco “auto qos voip” command. Within the core of our network, all packets are treated equally. At the customer edge of our network, packets with this higher priority TOS/DSCP value may given preferred treatment to improve traffic delivery over non-high priority traffic. Certain ports and protocols are blocked for the purpose of stopping the spread of viruses. Presently, TCP and UDP on ports 135-139 and port 445 are blocked. Protocol/port combinations may be added or removed from time to time as virus threats come and go.
Sample 1

Related to Application Specific Behavior

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

  • APPLICATION/SCOPE 1.1 Effective March 7, 2019, this Collective Agreement shall be applicable to every person who requires a teacher certificate as a condition of employment with the School Division excepting those positions agreed to be excluded in local bargaining between the School Division and the Association. Effective December 16, 2019, clause 1.1 above is repealed and replaced by the following clause:

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!