Agreement Protocol Sample Clauses

Agreement Protocol. First we describe how PBFT achieves agreement on a unique order of requests within a single view. Figure 25.9 shows how the nodes come to an agreement on a sequence number for a client request. Informally, the protocol has these five steps: 1. The nodes receive a request and relay it to the primary. 2. The primary sends a pre-prepare-message to all backups, informing them that it wants to execute that request with the sequence number specified in the message. 3. Backups send prepare-messages to all nodes, informing them that they agree with that suggestion. 4. All nodes send commit-messages to all nodes, informing everyone that they have committed to execute the request with that sequence number. 5. They execute the request and inform the client.
Sample 1Sample 2See All (4)
Agreement Protocol. The fact that the message history can be modified does not mean that both participants agree on anything. It just allows them to revise earlier statements, which is not sufficient to coordinate actions between agents. In order to coordi- nate, it is required to come to a shared understanding about facts, which requires that the agents state the facts and that they signal each other that they agree on them. In the Semantic Web, the core of such an agreement naturally is a set of triples. Consequently, the agreement protocol allows the participants to select a set of triples as agreed-upon.
Sample 1Sample 2Sample 3
Agreement Protocol. The fact that the message history can be modified does not mean that both participants agree on anything. It just allows them to revise earlier statements, which is not sufficient to coordinate actions between agents. In order to coordi- nate, it is required to come to a shared understanding about facts, which requires that the agents state the facts and that they signal each other that they agree on them. In the Semantic Web, the core of such an agreement naturally is a set of triples. Consequently, the agreement protocol allows the participants to select a set of triples as agreed-upon. C → D The result is formally defined as the agreement function Fagr : , yielding a dataset in which each graph corresponds to one agreement in the conversation C and the associated graph name is an IRI that identifies the agreement.5 In the following, we define Fagr. 5 Note that Fagr, in contrast to Smod and Sack, does not simply select named graphs from a dataset. Rather, it selects them and recombines their triples, hence we do not refer to it as a selection.
Sample 1
Agreement Protocol. First we describe how PBFT achieves agreement on a unique order of requests within a view. request pre-prepare prepare commit reply (r, c)c (v, s, r, n0 )n0 (v, s, r, ni)ni (v, s, ni)ni (r, ni)ni client c primary p backup n1 backup n2 backup n3
Sample 1
Agreement Protocol. First we describe how PBFT achieves agreement on a unique order of requests within a single view. Figure 26.9 shows how the nodes come to an agreement on a sequence number for a client request. Informally, the protocol has these five steps: 1. The nodes receive a request and relay it to the primary. 2. The primary sends a pre-prepare-message to all backups, informing them that it wants to execute that request with the sequence number specified in the message. 3. Backups send prepare-messages to all nodes, informing them that they agree with that suggestion. 4. All nodes send commit-messages to all nodes, informing everyone that they have committed to execute the request with that sequence number. 5. They execute the request and inform the client. request pre-prepare prepare commit reply (r, c)c (v, s, r, p)p (v, s, r, ni)ni (v, s, ni)ni (r, ni)ni client c primary p backup n1 backup n2 backup n3
Sample 1
Agreement Protocol. Each receiver chooses a secret key, S. ;;; The receiver publishes a public key, which gives a, p, and ;;; P=a^S(mod p). The receiver also supplies a procedure that the ;;; sender can call with the ciphertext. Given a message, m, the ;;; sender chooses his own secret, T, and composes a ciphertext that ;;; has two components, x=a^T(mod p) and y=m*P^T(mod p). The ;;; Xxxxxx-Xxxxxxx shared secret is x^S(mod p)=P^T(mod p). So the ;;; receiver decrypts the message by computing m=(y/x^S)(mod p). (define (eg-receiver dh-system) ;ElGamal receiver (let ((k (dh-system-size dh-system)) (p (dh-system-prime dh-system))) (let ((my-secret (random-k-digit-number k)) (mod-expt (exptmod p)) (mod-* (modular p *)) (mod-inv (inversemod p))) (let ((advertised-number (mod-expt (dh-system-primitive-root dh-system) my-secret))) (let ((public-key (eg-make-public-key dh-system advertised-number)) (decryption-procedure (lambda (ciphertext) (let ((x (eg-ciphertext-x ciphertext)) (y (eg-ciphertext-y ciphertext))) (let ((m (mod-* y (mod-inv (mod-expt x my-secret))))) (integer->string m)))))) (eg-make-receiver public-key decryption-procedure)))))) (define (eg-send-message message receiver) YOUR CODE HERE) ;;; Data abstractions supporting the ElGamal system (define (public-dh-system k) (list k (random-k-digit-prime k) 2)) (define (dh-system-size system) (car system)) (define (dh-system-prime system) (cadr system)) (define (dh-system-primitive-root system) (caddr system)) (define (eg-make-ciphertext x y) (cons x y)) (define (eg-ciphertext-x c) (car c)) (define (eg-ciphertext-y c) (cdr c)) (define (eg-make-public-key dh-system advertised-number) (cons dh-system advertised-number)) (define (eg-public-key-system key) (car key)) (define (eg-public-key-number key) (cdr key)) (define (eg-make-receiver public-key decryption-procedure) (cons public-key decryption-procedure)) (define (eg-receiver-public-key receiver) (car receiver)) (define (eg-receiver-decryption-procedure receiver) (cdr receiver)) #|
Sample 1

Related to Agreement Protocol

  • Protocol No action to coerce or censor or penalize any negotiation participant shall be made or implied by any other member as a result of participation in the negotiation process.

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

  • MUTUAL AGREEMENT PROCEDURE 1. Where difficulties or doubts arise between the Contracting Parties regarding the implementation or interpretation of this Agreement, the respective competent authorities shall endeavour to resolve the matter by mutual agreement. 2. In addition to the agreements referred to in paragraph 1, the competent authorities of the Contracting Parties may mutually agree on the procedures to be used under Articles 5 and 6. 3. The competent authorities of the Contracting Parties may communicate with each other directly for purposes of reaching agreement under this Article.

  • Amendment Procedures Amendments to this Agreement may be proposed only by the General Partner. To the fullest extent permitted by law, the General Partner shall have no duty or obligation to propose or approve any amendment to this Agreement and may decline to do so free of any duty or obligation whatsoever to the Partnership, any Limited Partner or any other Person bound by this Agreement, and, in declining to propose or approve an amendment to this Agreement, to the fullest extent permitted by law shall not be required to act in good faith or pursuant to any other standard imposed by this Agreement, any Group Member Agreement, any other agreement contemplated hereby or under the Delaware Act or any other law, rule or regulation or at equity, and the General Partner in determining whether to propose or approve any amendment to this Agreement shall be permitted to do so in its sole and absolute discretion. An amendment to this Agreement shall be effective upon its approval by the General Partner and, except as otherwise provided by Section 13.1 or Section 13.3, the holders of a Unit Majority, unless a greater or different percentage of Outstanding Units is required under this Agreement. Each proposed amendment that requires the approval of the holders of a specified percentage of Outstanding Units shall be set forth in a writing that contains the text of the proposed amendment. If such an amendment is proposed, the General Partner shall seek the written approval of the requisite percentage of Outstanding Units or call a meeting of the Unitholders to consider and vote on such proposed amendment. The General Partner shall notify all Record Holders upon final adoption of any amendments. The General Partner shall be deemed to have notified all Record Holders as required by this Section 13.2 if it has posted or made accessible such amendment through the Partnership’s or the Commission’s website.

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

  • Amendment Procedure (a) Except as provided in subsection (b) of this Section 11.3, this Declaration may be amended, after a majority of the Trustees have approved a resolution therefor, by the affirmative vote required by Section 10.4 of this Declaration. The Trustees also may amend this Declaration without any vote of Shareholders of any class or series to divide the Shares of the Trust into one or more classes or additional classes, or one or more series of any such class or classes, to determine the rights, powers, preferences, limitations and restrictions of any class or series of Shares, to change the name of the Trust or any class or series of Shares, to make any change that does not adversely affect the relative rights or preferences of any Shareholder, as they may deem necessary, or to conform this Declaration to the requirements of the 1940 Act or any other applicable federal laws or regulations including pursuant to Section 6.2 or the requirements of the regulated investment company provisions of the Code, but the Trustees shall not be liable for failing to do so. (b) No amendment may be made to Section 2.1, Section 2.2, Section 2.3, Section 3.9, Section 5.1, Section 5.2, Section 11.2(a), this Section 11.3, Section 11.4, Section 11.6 or Section 11.7 of this Declaration and no amendment may be made to this Declaration which would change any rights with respect to any Shares of the Trust by reducing the amount payable thereon upon liquidation of the Trust or by diminishing or eliminating any voting rights pertaining thereto (except that this provision shall not limit the ability of the Trustees to authorize, and to cause the Trust to issue, other securities pursuant to Section 6.2), except after a majority of the Trustees have approved a resolution therefor, by the affirmative vote of the holders of not less than seventy-five percent (75%) of the Shares of each affected class or series outstanding, voting as separate classes or series, unless such amendment has been approved by eighty percent (80%) of the Trustees, in which case approval by a Majority Shareholder Vote shall be required. Nothing contained in this Declaration shall permit the amendment of this Declaration to impair the exemption from personal liability of the Shareholders, Trustees, officers, employees and agents of the Trust or to permit assessments upon Shareholders. (c) An amendment duly adopted by the requisite vote of the Board of Trustees and, if required, the Shareholders as aforesaid, shall become effective at the time of such adoption or at such other time as may be designated by the Board of Trustees or Shareholders, as the case may be. A certification in recordable form signed by a majority of the Trustees setting forth an amendment and reciting that it was duly adopted by the Trustees and, if required, the Shareholders as aforesaid, or a copy of the Declaration, as amended, in recordable form, and executed by a majority of the Trustees, shall be conclusive evidence of such amendment when lodged among the records of the Trust or at such other time designated by the Board. Notwithstanding any other provision hereof, until such time as a Registration Statement under the Securities Act of 1933, as amended, covering the first public offering of Shares of the Trust shall have become effective, this Declaration may be terminated or amended in any respect by the affirmative vote of a majority of the Trustees or by an instrument signed by a majority of the Trustees.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • Agreement Scope The scope of this Agreement is as prescribed in section 46 of the Act, setting out: • the health services to be provided to the State by the HSP, • the TTR in support of the health services to be provided, • the funding to be provided to the HSP for the provision of the health services, including the way in which the funding is to be provided, • the performance measures and operational targets for the provision of the health services by the HSP, • how the evaluation and review of results in relation to the performance measures and operational targets is to be carried out, • the performance data and other data to be provided by the HSP to the Department CEO, including how, and how often, the data is to be provided, and • any other matter the Department CEO considers relevant to the provision of the health services by the HSP. Where appropriate, reference will be made in this Agreement to Policy Frameworks issued by the Department CEO pursuant to Part 3, Division 2 of the Act.

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

  • Procurement Procedures 11.1 The Recipient must secure the best value for money and shall act in a fair, open and non-discriminatory manner in all purchases of goods and services.