Security State Notification Sample Clauses

Security State Notification. Secure TIP devices MAY transmit a TIP NOTIFY message following the establishment of a secure TIP session to indicate that despite the use of SRTP, the TIP session MUST be considered as non- secure by the remote peer. Secure TIP devices MAY transmit a TIP NOTIFY message to revert an SRTP TIP session security state from non-secure and back to secure. Secure TIP devices MUST NOT transmit a TIP NOTIFY message over a non-secure TIP session. Secure TIP devices MUST be prepared to receive a TIP NOTIFY message and MUST inform the user of the security state indicated by the NOTIFY message. TIP devices receiving a TIP NOTIFY message over a non-secure TIP session MUST ignore those.
View Source
Security State Notification. Secure TIP devices MAY transmit a TIP NOTIFY message following the establishment of a secure TIP session to indicate that despite the use of SRTP, the TIP session MUST be considered as non- secure by the remote peer. Secure TIP devices MAY transmit a TIP NOTIFY message to revert an SRTP TIP session security state from non-secure and back to secure. Secure TIP devices MUST NOT transmit a TIP NOTIFY message over a non-secure TIP session. Secure TIP devices MUST be prepared to receive a TIP NOTIFY message and MUST inform the user of the security state indicated by the NOTIFY message. TIP devices receiving a TIP NOTIFY message over a non-secure TIP session MUST ignore those. Figure 7 shows a call setup between two secure TIP endpoints. The first INVITE transaction negotiates a single audio and video media line with H264 and AAC. The negotiated media line might have an AVP or an SAVP RTP profile. Once the initial call setup completes, each secure TIP device starts two DTLS-SRTP sessions for each media line irrespective of whether the AVP or the SAVP profile was negotiated for the media line. 1. The DTLS-SRTP session for which the TIP device acts as a client will be used by the device to generate its SRTP and SRTCP master keys used for encryption. The crypto algorithm negotiated in the session will also be used for transmitted packet authentication and encryption 2. The DTLS-SRTP session for which the TIP device acts as a server will be used by the device to generate the SRTP and SRTCP master keys used for decryption. The crypto algorithm negotiated in the session will also be used for received packets authentication and decryption Once both DTLS-SRTP sessions have completed successfully for a specific (S)RTP session, the TIP device starts its secure TIP negotiation. From now on the call flow should follow the same pattern as described in 4.1 except that SRTP and SRTCP packets are transmitted and received rather than RTP and RTCP packets.
View Source

Related to Security State Notification

  • Foreign Asset/Account Reporting Notification The Participant must report securities held (including Shares) or any bank or brokerage accounts opened and maintained outside Belgium on the Participant’s annual tax return. In a separate report, the Participant is required to report to the National Bank of Belgium the details of such accounts opened and maintained outside Belgium. This report, as well as additional information on how to complete it, can be found on the website of the National Bank of Belgium, ▇▇▇.▇▇▇.▇▇, under the Kredietcentrales / Centrales des crédits caption.

  • Reporting Notification A. Quarterly Reports In addition to any reports required pursuant to §19 or pursuant to any exhibit, for any contract having a term longer than 3 months, Local Agency shall submit, on a quarterly basis, a written report specifying progress made for each specified performance measure and standard in this Agreement. Such progress report shall be in accordance with the procedures developed and prescribed by the State. Progress reports shall be submitted to the State not later than five (5) Business Days following the end of each calendar quarter or at such time as otherwise specified by the State.

  • Obligor Notification Forms The Borrower shall furnish the Collateral Agent and the Administrative Agent with an appropriate power of attorney to send (at the Administrative Agent’s discretion on the Collateral Agent’s behalf, after the occurrence and during the continuance of an Event of Default or the Facility Maturity Date) Obligor notification forms to give notice to the Obligors of the Collateral Agent’s interest in the Collateral Portfolio and the obligation to make payments as directed by the Administrative Agent on the Collateral Agent’s behalf.

  • Customer Notification By executing this Agreement, the Advisor acknowledges that as required by the Advisers Act the Sub-Advisor has supplied to the Advisor and the Trust copies of the Sub-Advisor’s Form ADV with all exhibits and attachments (including the Sub-Advisor’s statement of financial condition) and will promptly supply to the Advisor copies of all amendments or restatements of such document. Otherwise, the Advisor’s rights under federal law allow termination of this contract without penalty within five business days after entering into this contract. U.S. law also requires the Sub-Advisor to obtain, verify, and record information that identifies each person or entity that opens an account. The Sub-Advisor will ask for the Trust’s legal name, principal place of business address, and Taxpayer Identification or other identification number, and may ask for other identifying information.

  • Union Notification The Union shall be notified of all appointments, hirings, layoffs, transfers, recalls and terminations of employment.