Design Goals Sample Clauses

Design Goals. We seek a protocol with the following characteristics: — Security: No one other than the participants may have access to the generated key. — PFS: It must approach Perfect Forward Secrecy. — Privacy: It must preserve the privacy of the initiator and/or responder, insofar as possible. — Memory-DoS: It must resist memory exhaustion attacks. — Computation-DoS: It must resist CPU exhaustion attacks on the responder. — Availability: It must protect against easy to mount protocol-specific DoS at- tacks, for example, in a wireless environment where an attacker can observe everyone’s transmissions but cannot interfere with the transmitted packets themselves. — Efficiency: It must be efficient with respect to computation, bandwidth, and number of rounds. — Non-negotiated: It must avoid complex negotiations over capabilities. — Simplicity: The resulting protocol must be as simple as possible, within the constraints of the requirements. The Security requirement is obvious enough (we use the security model of Xxxxxxx and Xxxxxxxx [2001; 2002a]). The rest, however, require some discussion. The PFS property is perhaps the most controversial. (PFS is an attribute of encrypted communications allowing for a long-term key to be compromised without affecting the security of past session keys.) Rather than assert that “we must have PFS at all costs,” we treat the amount of forward secrecy as an engineering parameter that can be traded off against other necessary functions, such as efficiency or resistance to DoS attacks. In fact, this corresponds quite nicely to the reality of today’s Internet systems, where a compromise during the existence of a security association (SA) will reveal the plaintext of any ongoing transmissions. Our protocol has a forward secrecy interval; SAs are protected against compromises that occur outside of that interval. Specifically, we allow a party to reuse the same secret Diffie–Xxxxxxx (DH) exponents for multiple exchanges within a given time period; this may save a large number of costly modular exponentiations. The Privacy property means that the protocol must not reveal the identity of a participant to any unauthorized party, including an active attacker that attempts to act as the peer. Clearly, it is not possible for a protocol to pro- tect both the initator and the responder against an active attacker; one of the participants must always “go first.” In general, we believe that the most ap- propriate choice is to protect the initator, since t...
Sample 1
AutoNDA by SimpleDocs
Design Goals. Our two main design goals in this study were:
Sample 1
Design Goals. 2.1 The building shall create an icon for New York City and have a memorable presence on the skyline.
Sample 1
Design Goals. Based on existing literatures, a secure protocol should satisfy the following security requirements and functions: •
Sample 1
Design Goals. The goal for the design review process will be for there to be two distinct facilities, with separately identifiable spaces, and functions. The Parties may wish to create common areas that can be jointly managed and/or made available to others as needed.
Sample 1
Design Goals. The Task Assistance Framework provides a simple, flexible, and configurable layer that demonstrates the following characteristics: • The Task Assistance Framework uses the Script as a model to provide visual assistance and navigation control to the User that is performing the Script. • The Script model is used as a structure on which many different types of Task Assistance can be built. Thus a new Task Assistance Framework can be added without affecting the Script model. • The Script description can be persisted in a number of forms (for example, flat file, relational database table, class with an instance variable holding onto a collection of Activities). It can be changed without changing the Task Assistance Framework that utilizes it. • The Task Assistance Framework implements a clear separation of responsibilities between the visual representation of the Script model and the Task Assistance services. This allows transparent additions of new forms of Task Assistance (visual "task lists," CueCards, "wizards"). • The Task Assistance Framework is an optional extension to the User Interface Control Framework.
Sample 1
Design Goals. To design an AKA protocol, we need to consider three aspects at the same time, which are the network environment, security goals and privacy goals. This subsection will consider them one by one. IoT offers numerous advantages and services to the users. An important aspect of pervasive IoT devices is its constrained resources. So, various energy efficient lightweight mechanisms should be designed to store, process and transfer the data as per application requirements and with an optimized resource management. AKA-Goal 1: Lightweight property: Given the constraints of IoT environment, it is desirable that the AKA protocol should be lightweight in computation and communication. AKA protocol primitives should consume fewer resources without compromising the required level of security and privacy.
Sample 1
AutoNDA by SimpleDocs

Related to Design Goals

  • Goals Goals define availability, performance and other objectives of Service provisioning and delivery. Goals do not include remedies and failure to meet any Service Goal does not entitle Customer to a Service credit.

  • Acceptance Criteria 6.7.2.1. During the test there shall be no evidence of:

  • Performance Objectives 4.1 The Performance Plan (Annexure A) sets out-

  • Performance Goals A. The Trust and State Street have developed mutually acceptable performance goals dated March 1, 2011 , and as may be amended from time to time, regarding the manner in which they expect to deliver and receive the services under this Agreement (hereinafter referred to as “Service Level Agreement”). The parties agree that such Service Level Agreement reflects performance goals and any failure to perform in accordance with the provisions thereof shall not be considered a breach of contract that gives rise to contractual or other remedies. It is the intention of the parties that the sole remedy for failure to perform in accordance with the provisions of the Service Level Agreement, or any dispute relating to performance goals set forth in the Service Level Agreement, will be a meeting of the parties to resolve the failure pursuant to the consultation procedure described in Sections V. B. and V.C. below. Notwithstanding the foregoing, the parties hereby acknowledge that any party’s failure (or lack thereof) to meet the provisions of the Service Level Agreement, while not in and of itself a breach of contract giving rise to contractual or other remedies, may factor into the Trust’s reasonably determined belief regarding the standard of care exercised by State Street hereunder.

  • Performance Measure The specific representation of a process or outcome that is relevant to the assessment of performance; it is quantifiable and can be documented

  • Approved Working Drawings The Final Working Drawings shall be approved by Landlord (the “Approved Working Drawings”) prior to the commencement of construction of the Premises by Tenant. After approval by Landlord of the Final Working Drawings, Tenant may submit the same to the appropriate municipal authorities for all applicable building permits. Tenant hereby agrees that neither Landlord nor Landlord’s consultants shall be responsible for obtaining any building permit or certificate of occupancy for the Premises and that obtaining the same shall be Tenant’s responsibility; provided, however, that Landlord shall cooperate with Tenant in executing permit applications and performing other ministerial acts reasonably necessary to enable Tenant to obtain any such permit or certificate of occupancy. No changes, modifications or alterations in the Approved Working Drawings may be made without the prior written consent of Landlord, which consent may not be unreasonably withheld.

  • Performance Targets Threshold, target and maximum performance levels for each performance measure of the performance period are contained in Appendix B.

  • Milestones Subject to the provisions of the SGIP, the Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement. A Party’s obligations under this provision may be extended by agreement. If a Party anticipates that it will be unable to meet a milestone for any reason other than a Force Majeure event, it shall immediately notify the other Parties of the reason(s) for not meeting the milestone and (1) propose the earliest reasonable alternate date by which it can attain this and future milestones, and (2) requesting appropriate amendments to Attachment 4. The Party affected by the failure to meet a milestone shall not unreasonably withhold agreement to such an amendment unless it will suffer significant uncompensated economic or operational harm from the delay, (1) attainment of the same milestone has previously been delayed, or (2) it has reason to believe that the delay in meeting the milestone is intentional or unwarranted notwithstanding the circumstances explained by the Party proposing the amendment.

  • Objectives The objectives of this Agreement are to:

  • Performance Criteria The Performance Criteria are set forth in Exhibit A to this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.