Bundle Link Integrity Procedure Sample Clauses

Bundle Link Integrity Procedure. These procedures test bundle link integrity during normal operation. A bundle link endpoint shall transmit the HELLO message following expiration of timer T_HELLO. Timer T_ACK shall be started. A bundle link endpoint receiving a valid HELLO message while in the up state shall respond with a HELLO_ACK message. All HELLO messages received when the bundle link is not in the up state must be ignored. A bundle link endpoint receiving a valid HELLO_ACK message shall:
AutoNDA by SimpleDocs

Related to Bundle Link Integrity Procedure

  • Security Procedure The Client acknowledges that the Security Procedure it has designated on the Selection Form was selected by the Client from Security Procedures offered by State Street. The Client agrees that the Security Procedures are reasonable and adequate for its wire transfer transactions and agrees to be bound by any payment orders, amendments and cancellations, whether or not authorized, issued in its name and accepted by State Street after being confirmed by any of the selected Security Procedures. The Client also agrees to be bound by any other valid and authorized payment order accepted by State Street. The Client shall restrict access to confidential information relating to the Security Procedure to authorized persons as communicated in writing to State Street. The Client must notify State Street immediately if it has reason to believe unauthorized persons may have obtained access to such information or of any change in the Client’s authorized personnel. State Street shall verify the authenticity of all instructions according to the Security Procedure.

  • Security Procedures The Fund shall comply with data access operating standards and procedures and with user identification or other password control requirements and other security procedures as may be issued from time to time by State Street for use of the System on a remote basis and to access the Data Access Services. The Fund shall have access only to the Fund Data and authorized transactions agreed upon from time to time by State Street and, upon notice from State Street, the Fund shall discontinue remote use of the System and access to Data Access Services for any security reasons cited by State Street; provided, that, in such event, State Street shall, for a period not less than 180 days (or such other shorter period specified by the Fund) after such discontinuance, assume responsibility to provide accounting services under the terms of the Custodian Agreement.

  • SECURITY PROCESSES If requested by an Authorized User as part the Request for Quote process, Contractor shall complete a Consensus Assessment Initiative Questionnaire (CAIQ) including on an annual basis thereafter, if requested by the Authorized User. The CAIQ is available at Cloud Security Alliance (xxxxx://xxxxxxxxxxxxxxxxxxxxx.xxx/). The CAIQ may be used to assist the Authorized User in building the necessary assessment processes when engaging with Contractors. In addition to a request for a CAIQ, Contractor shall cooperate with all reasonable Authorized User requests for a Written description of Contractor’s physical/virtual security and/or internal control processes. The Authorized User shall have the right to reject any Contractor’s RFQ response or terminate an Authorized User Agreement when such a request has been denied. For example, Federal, State and local regulations and/or laws may require that Contractors operate within the Authorized User’s regulatory environment. In order to ensure that security is adequate and free of gaps in control coverage, the Authorized User may require information from the Contractor’s Service Organization Controls (SOC) audit report.

  • WARRANTY PROCEDURES You need proof of purchase for warranty service.

  • CONTRACTOR INTEGRITY PROVISIONS It is essential that those who seek to contract with the Commonwealth of Pennsylvania (“Commonwealth”) observe high standards of honesty and integrity. They must conduct themselves in a manner that fosters public confidence in the integrity of the Commonwealth contracting and procurement process.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant-assisted project in accordance with Section 287.057, Florida Statutes.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

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

  • Change Management Process If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.

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