1 / 6

A Mechanism to Secure SIP Information inserted by Intermediaries

This draft proposes a mechanism to secure SIP information inserted by intermediaries, focusing on middle-to-middle and middle-to-end security. It addresses the relationship to end-to-end security and considers the transitive trust model between intermediaries.

valdezd
Download Presentation

A Mechanism to Secure SIP Information inserted by Intermediaries

An Image/Link below is provided (as is) to download presentation 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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIPPING WG Meeting IETF-58 A Mechanism to Secure SIP Information inserted by Intermediaries draft-barnes-sipping-sec-inserted-info-01.txt Mary Barnes (mary.barnes@nortelnetworks.com)

  2. Changes from -00 • Major re-write to focus on a more general middle-to-middle and middle-to-end security problem. • Current focus is requirements. • Addresses relationship to e2m security.

  3. H1’ H2 H1’ H2 H1 * * Example Scenario User 1 UA1 Proxy A Proxy #1 Proxy #2 UA2 H1: Header added initially by UA#1 which is protected by e2m security H1': Proxy#1 modifies H1 (after validating based on e2m security) H2 : Added by Proxy#1 (secured along with H1' using m2e security) *: Headers are forwarded in the Request, but are not manipulated.

  4. Relation to e2m security • Slightly different than e2m security requirements in that this problem is dealing with the information added by intermediaries and used by intermediaries or endpoints as the basis for a service. • m2m premised on a fundamental level of trust that intermediary has been “authorized” or is in some way trusted to provide services (through fundamental SIP service support) for the end user whose Request is being handled. • m2m/m2e builds a transitive trust model between intermediaries, not requiring endpoints to have certificates for all the entities/intermediaries.

  5. Relation to e2m security • e2m and m2m/m2e share some fundamental problems to be solved in SIP. • Additional mechanism for challenging Intermediaries. • Ability for intermediaries to add (and modify and remove) message bodies. • High level of overlap between solution options.

  6. Next Steps • Agree the basic requirements and problem domain. • Merge requirements with e2m? • Request additional feedback on the draft(s)/problem on the mailing list.

More Related