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.
View SourceView Similar (4)
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.
View Source

Related to Application Specific Behavior

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By February 1, 2017, the Division will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the Division to provide equally effective alternative access. The Plan for New Content will require the Division, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternatives are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the Division online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the Division will officially adopt and fully implement the amended policies and procedures.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.

  • 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.

  • Core Profession Specific Provide nationally consistent legal advice and management to support effective and lawful registration, notifications and compliance procedures, and hearing panels processes Profession-specific services, as listed in the National Board’s regulatory plan and annual budget.