Protocol Operation Sample Clauses

Protocol Operation. The protocol will take effect from the date it is agreed by all parties, or on 01/01/09, whichever is later in time. The protocol will remain in operation unless terminated by the Community Services and Disability Ministers’ Advisory Council. Prepared by: The Privacy and Information Access Section Legal Services and Procurement Branch Centrelink PO Box 7788 Canberra ACT 2610 1 Formulation of the Appendix 2 Centrelink’s privacy framework and other legislative obligations 3 Disclosure of information under the threat to life, health or welfare provision 4 How to request information from Centrelink 5 What Centrelink generally can and can not assist with 6 Response timeframes from Centrelink 7 General step by step processes for Public Interest requests 8 Normal operating hours and after business hours support by Centrelink 9 Senior Centrelink Officer details for reconsideration of decision and dispute resolution 10 Centrelink Contact Officer details 11 Child Protection Contact Officer details 12 Use of the In-Touch Program 13 Protecting your password 14 Informal review
View SourceView Similar (4)
Protocol Operation. This section deals with the protocol details involved in the negotiation between a SIP entity and its next-hop SIP entity. Throughout the text the next-hop SIP entity is referred to as the first-hop proxy or outbound proxy. However, the reader should bear in mind that a user agent server can also be the next-hop for a proxy or, in absence of proxies, for a user agent client. Note as well that a proxy can also have an outbound proxy.
View SourceView Similar (2)
Protocol Operation. This section deals with the protocol details involved in the negotiation between a SIP entity and its next-hop SIP entity. Throughout the text the next-hop SIP entity is referred to as the first-hop proxy or outbound proxy. However, the reader should bear in mind that a user agent server can also be the next-hop for a proxy or, in absence of proxies, for a user agent client. Note as well that a proxy can also have an outbound proxy. 3.4.1 Client Initiated A client wishing to establish some type of security with its first- hop proxy MUST add a Security-Client header field to a request addressed to this proxy (i.e., the destination of the request is the first-hop proxy). This header field contains a list of all the security mechanisms that the client supports. The client SHOULD NOT add preference parameters to this list. The client MUST add both a Require and Proxy-Require header field with the value "sec-agree" to its request. The Security-Client header field is used by the server to include any necessary information in its response. For example, if digest- integrity is the chosen mechanism, the server includes an HTTP authentication challenge in the response. If S/MIME is chosen, the appropriate certificate is included. If the security mechanisms supported by the client do not need any further information to be established (e.g., TLS) the client MAY choose not to include the Security-Client header field in its request. ▇▇▇▇▇ et al [Page 7] A server receiving an unprotected request that contains a Require or Proxy-Require header field with the value "sec-agree" MUST challenge the client with a 494 (Security Agreement Required) response. The server MUST add a Security-Server header field to this response listing the security mechanisms that the server supports. The server MUST add its list to the response even if there are no common security mechanisms in the client's and server's lists. The servers list MUST NOT depend on the contents of the client's list. The server MUST compare the list received in the Security-Client header field with the list to be sent in the Security-Server header field. When the client receives this response, it will choose the common security mechanism with the highest "q" value. Therefore, the server MUST add the necessary information so that the client can initiate that mechanism (e.g., a WWW-Authenticate header field for digest-integrity). When the client receives a response with a Security-Server header field, it SHOULD choose t...
View Source
Protocol Operation. 7 3.4.1 Client Initiated. 7
View Source

Related to Protocol Operation

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including RTU for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG shall immediately after each synchronization/tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Commercial Operation (i) On or before December 31, 2021, Interconnection Customer must demonstrate commercial operation of all generating units. Demonstrating commercial operation includes achieving Initial Operation in accordance with Section 1.4 of Appendix 2 to this ISA and making commercial sales or use of energy, as well as, if applicable, obtaining capacity qualification in accordance with the requirements of the Reliability Assurance Agreement Among Load Serving Entities in the PJM Region.

  • Project Management Plan Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and

  • PROFESSIONAL DEVELOPMENT AND EDUCATIONAL IMPROVEMENT A. Both the Board and the Association encourage teachers to seek professional improvement. In order to assist teachers in extending and improving their skills the following plan will be implemented. B. All Teachers will be encouraged to earn a Masters degree or coursework toward additional certification that is in the field of education and within a teacher's discipline, or in an area that is beneficial to the school. C. The Board will pay teacher's expenses for undergraduate and/or graduate credits, specialty and additional endorsements under the following conditions. 1. In allocating budgeted funds priority will be given to the teachers in a “masters” program and those teachers who need to complete coursework for certification. 2. All courses must be approved, in advance, by the Superintendent. Courses for recertification purposes must be approved in advance by the certification committee and the superintendent. The teacher shall receive a written reply from the Superintendent within ten (10) days of application for course approval (See Appendix D). 3. Each teacher will be eligible for up to six (6) semester hours of credit or, if enrolled in a matriculated, organized program, 12 semester hours of credit for undergraduate will be paid if part of a graduate program or graduate courses per contract year. The Superintendent reserves the right to request intent to take courses prior to final budget preparation. Failure to communicate such intent at the time of the Superintendent’s request may jeopardize course reimbursement due to a lack of funding. 4. The administration will pay in advance the cost of the course. Presentation of evidence of satisfactory completion of the course (A grade of B or better) is the responsibility of the teacher. In the event the course is not completed or not completed satisfactorily, the teacher will refund the payment received in advance and in accordance with Appendix D – attached. 5. Teachers who resign shall not be eligible for reimbursement after the date of resignation Teachers who have been reimbursed for any course work toward securing a masters within the last two (2) years of employment shall be required to continue their service to RSU # 78 for an additional two (2) years (twenty-four months) or will be required to reimburse the district the cost associated with Masters courses taken prior to departing, Such reimbursement to the district shall be remitted via payroll deductions as arranged between the District and employee, unless the failure to continue employment is due to illness, disability, death, or reduction of position. 6. Reimbursement will only be for tuition and fees. It will not include reimbursement for mileage, books and other expenses unless the teacher is required to take the course by the administration.

  • Co-operation Each Party acknowledges that this ESA must be approved by the Department and agree that they shall use Commercially Reasonable efforts to cooperate in seeking to secure such approval.