Initial Key Agreement: Protocol IKA1 Sample Clauses

Initial Key Agreement: Protocol IKA1. − łG { } ∈ / 1. Each Ui picks a random ri [1, N ] and computes zi = gri mod N . Ui = Uc then signs Ui zi to obtain signature σi and sends mi = Ui zi σi to the controller Uc. zrc mod N . After receiving all the n − 1 messages, Uc computes Y as Y = Qi∈[1,n]\{c} yi 2. Upon receiving each message mi, Uc verifies the correctness of mi and computes yi = modN if n is even, and as Y = i∈[1,n] yi mod N if n is odd. Uc also computes the set T = {Ti | i ∈ [1, n] \ {c}} where Ti = Y · yi−1 mod N . Let Z = {zi | i ∈ [1, n]}. Then, Uc signs łG Z T to obtain signature σc and broadcasts mc = łG Z T σc to the entire group. 3. Upon receiving the broadcast message mc, each Ui Uc verifies the correctness of mc and computes Y = zri · Ti mod N . All users in łG compute their session key as K = H(T Y ), and store their random exponent ri and the set Z for future use. To take a simplified example as an illustration, consider a multicast group łG = {U1, U2,
AutoNDA by SimpleDocs

Related to Initial Key Agreement: Protocol IKA1

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

  • Quality Agreement Concurrently with execution of this Agreement, the Parties will enter into an agreement that details the quality assurance obligations of each Party with respect to the Manufacture and supply of Supplied Products under this Agreement (the “Quality Agreement”). Each Party shall perform its obligations under the Quality Agreement in accordance with the terms and conditions thereof. In the event of a conflict between the terms of the Quality Agreement and the terms of this Agreement, the provisions of the Quality Agreement shall govern.

  • Vendor Logo (Supplemental Vendor Information Only) No response Optional. If Vendor desires that their logo be displayed on their public TIPS profile for TIPS and TIPS Member viewing, Vendor may upload that logo at this location. These supplemental documents shall not be considered part of the TIPS Contract. Rather, they are Vendor Supplemental Information for marketing and informational purposes only. Some participating public entities are required to seek Disadvantaged/Minority/Women Business & Federal HUBZone ("D/M/WBE/Federal HUBZone") vendors. Does Vendor certify that their entity is a D/M/WBE/Federal HUBZone vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. NO Some participating public entities are required to seek Historically Underutilized Business (HUB) vendors as defined by the Texas Comptroller of Public Accounts Statewide HUB Program. Does Vendor certify that their entity is a HUB vendor? If you respond "Yes," you must upload current certification proof in the appropriate "Response Attachments" location. No Can the Vendor provide its proposed goods and services to all 50 US States? Yes

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • COMMENCEMENT OF WORK UNDER A SOW AGREEMENT Commencement of work as a result of the SOW-RFP process shall be initiated only upon issuance of a fully executed SOW Agreement and Purchase Order.

  • Pharmacovigilance Agreement Subject to the terms of this Agreement, and at a date to be determined by the JDC, Facet and Trubion shall define and finalize the actions the Parties shall employ to protect patients and promote their well-being in a written agreement (hereinafter referred to as the “Pharmacovigilance Agreement”). These responsibilities shall include mutually acceptable guidelines and procedures for the receipt, investigation, recordation, communication, and exchange (as between the Parties) of adverse event reports, pregnancy reports, and any other information concerning the safety of any Collaboration Product. Such guidelines and procedures shall be in accordance with, and enable the Parties to fulfill, local and national regulatory reporting obligations to Governmental Authorities. Furthermore, such agreed procedures shall be consistent with relevant ICH guidelines, except where said guidelines may conflict with existing local regulatory safety reporting requirements, in which case local reporting requirements shall prevail. The Pharmacovigilance Agreement will provide for a worldwide safety database to be maintained by the Party appointed by the JDC. Each Party hereby agrees to comply with its respective obligations under such Pharmacovigilance Agreement (as the Parties may agree to modify it from time to time) and to cause its Affiliates and permitted sublicensees to comply with such obligations.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Student Agreement It is important that I work to the best of my ability. Therefore, I shall strive to do the following:

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