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
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.
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...
Protocol Operation. 7 3.4.1 Client Initiated. 7