End-to-middle Security in SIP draft-ietf-sipping-e2m-sec-reqs-04 draft-ono-sipping-end2middle-security-03. Kumiko Ono firstname.lastname@example.org. IETF61. Requirements. draft-ietf-sipping-e2m-sec-reqs-04. Changes since 03. Section 2.1: Examples of Scenarios
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
REQ-CONF-4: It MAY allow a UA to request that the recipient UA disclose information to the proxy server, which requesting UA is disclosing the information to. The request itself SHOULD be secure.
OptionA-1. A new SIP header
Option A-2. A new parameter in a SIP header
i.e.: "content-id" param in Route header
Option B-1. A new MIME header
Option B-2. A new parameter in a MIME header
i.e.: "required-entity" param in
Option A-1. A new SIP header
Proxy should have a way to notify a UA about e2m security utilization in addition to using UAC driven method, such as session policy package.
1) When a proxy server needs to view an encrypted data sent by UAC, it requires end-to-middle confidentiality.
2) When a proxy server needs to validate the data integrity of the message, it requires end-to-middle integrity.