Receiving ADD_LINK_REJ Messages Sample Clauses

Receiving ADD_LINK_REJ Messages. A bundle link endpoint receiving an ADD_LINK_REJ message shall examine the cause information. If the cause code is UNKNOWN_VENDOR_EXTENSION, the bundle link endpoint shall not include the rejected Vendor Extension Information Element in subsequent ADD_LINK messages. All implementations must be capable of operating without vendor extensions. Upon reception of all ADD_LINK_REJ messages, the originator of the ADD_LINK message shall: 1. remain in the add sent or add rx state; 2. transmit the corrected ADD_LINK message. If the ADD_LINK message cannot be corrected then the sending of the ADD_LINK should be delayed by the T_HELLO timer. Implementations of MFR that don’t support vendor extensions can safely assume that the ADD_LINK_REJ message is not correctable. 3. Stop timer T_ACK; start timer T_ACK T_HELLO; and 4. send a BL_DEACTIVATE indication to the bundle with the cause code and diagnostics, if diagnostics are present in the message. The bundle should issue a MB_ERROR indication to report the failure to layer management. Refer to Table 4 for a list of the cause values and the contents of the diagnostic element. Note: An example of where the ADD_LINK message probably cannot be corrected is when the cause code is INCONSISTENT_BUNDLE. An example of where the ADD_LINK message probably can be corrected is when the cause is UNKNOWN_VENDOR_EXTENSION. In the latter case, the corrected ADD_LINK message will not have the Vendor Extension Information Element.
AutoNDA by SimpleDocs
Receiving ADD_LINK_REJ Messages. A bundle link endpoint receiving an ADD_LINK_REJ message shall examine the cause information. If the cause code is UNKNOWN_VENDOR_EXTENSION, the bundle link endpoint shall not include the rejected Vendor Extension Information Field in subsequent ADD_LINK messages. All implementations must be capable of operating without vendor extensions. Upon reception of all ADD_LINK_REJ messages, the originator of the ADD_LINK message shall: 1. remain in the add sent or add rx state; 2. transmit the ADD_LINK message; 3. start timer T_ACK; and 4. send a BL_DEACTIVATE indication to the bundle with the cause code and diagnostics, if diagnostics are present in the message. The bundle should issue a MB_ERROR indication to report the failure to layer management. Refer to Table 4 for a list of the cause values and the contents of the diagnostic field.
Receiving ADD_LINK_REJ Messages. A bundle link endpoint receiving an ADD_LINK_REJ message shall examine the cause information. If the cause code is UNKNOWN_VENDOR_EXTENSION, the bundle link endpoint shall not include the rejected Vendor Extension Information Field in subsequent ADD_LINK messages. All implementations must be capable of operating without vendor extensions. Upon reception of all ADD_LINK_REJ messages, the originator of the ADD_LINK message shall:

Related to Receiving ADD_LINK_REJ Messages

  • TEXT MESSAGING WHILE DRIVING In accordance with Executive Order (EO) 13513, “Federal Leadership on Reducing Text Messaging While Driving,” any and all text messaging by Federal employees is banned: a) while driving a Government owned vehicle (GOV) or driving a privately owned vehicle (POV) while on official Government business; or b) using any electronic equipment supplied by the Government when driving any vehicle at any time. All cooperators, their employees, volunteers, and contractors are encouraged to adopt and enforce policies that ban text messaging when driving company owned, leased or rented vehicles, POVs or GOVs when driving while on official Government business or when performing any work for or on behalf of the Government.

  • Alerts via Text Message To stop Alerts via text message, text "STOP" to 99785 at anytime. Alerts sent to your primary email address will be unaffected by this action. To restore Alerts on your Mobile Device, just visit the Alerts tab in Online Banking and click the box next to your mobile number for the Alert(s) you would like to receive again. For help with SMS text alerts, text “HELP” to 99785. In case of questions, please contact Customer Care at 0-000-000-0000. Our participating carriers include (but are not limited to) AT&T® Wireless, T-Mobile®, U.S. Cellular®, Verizon Wireless.

  • Reducing Text Messaging While Driving Pursuant to Executive Order 13513, 74 FR 51225 (Oct. 6, 2009), Recipient should encourage its employees, subrecipients, and contractors to adopt and enforce policies that ban text messaging while driving, and Recipient should establish workplace safety policies to decrease accidents caused by distracted drivers.

  • Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Encrypt or Encryption As defined in the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Security Rule at 45 CFR 164.304, means the use of an algorithmic process to transform Personally Identifiable Information into an unusable, unreadable, or indecipherable form in which there is a low probability of assigning meaning without use of a confidential process or key.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Email You acknowledge that we are able to send electronic mail to you and receive electronic mail from you. You release us from any claim you may have as a result of any unauthorised copying, recording, reading or interference with that document or information after transmission, for any delay or non-delivery of any document or information and for any damage caused to your system or any files by a transfer.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

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