ua driven privacy mechanism for sip
play

UA-Driven Privacy Mechanism for SIP draft-ietf-sip-ua-privacy-02 - PowerPoint PPT Presentation

IETF72 SIP - Jul. 31, 2008 UA-Driven Privacy Mechanism for SIP draft-ietf-sip-ua-privacy-02 Mayumi Munakata Shida Schubert Takumi Ohba UA-Driven Privacy (draft-ietf-sip-ua-privacy-02) Mayumi M. Changes from 01


  1. IETF72 SIP - Jul. 31, 2008 UA-Driven Privacy Mechanism for SIP draft-ietf-sip-ua-privacy-02 Mayumi Munakata Shida Schubert Takumi Ohba

  2. UA-Driven Privacy (draft-ietf-sip-ua-privacy-02) Mayumi M. Changes from 01 (1/3) • Incorporated the result of last meeting (Anonymous From header) From header must be "anonymous@anonymous.invalid" unless RFC4474 is provided/is to be used, in which case it must be "anonymous@{user's domain name}". • Deleted the Requirement section All the requirements seemed too obvious. (UA MUST anonymize a SIP message by itself, and the backward compatibility MUST be secured.) • Organized the text in Sec 4 (Treatment of Privacy-Sensitive Information)

  3. UA-Driven Privacy (draft-ietf-sip-ua-privacy-02) Mayumi M. Changes from 01 (2/3) • Added instructions to treat each SIP headers Such as Contact, From, and Via, as well as SDP and host name. • Deleted the citations from RFC3323 The draft does not obsolete RFC3323 , but defines UA-driven anonymization that is independent. The draft now focuses on providing a guideline for UA to conceal the privacy-sensitive information utilizing GRUU and TURN .

  4. UA-Driven Privacy (draft-ietf-sip-ua-privacy-02) Mayumi M. Changes from 01 (3/3) 1. Deleted the text on the need of the indication of UA-driven privacy The purposes of indication were: 1. To request intermediaries not to add any extra privacy-sensitive information 2. To request intermediaries not to anonymize the already-anonymized message For the first purpose; P-Asserted-Identity is the only privacy sensitive information that can be considered critical which is added by the network entity. As the privacy on P-Asserted-Identity can be addressed by setting "id" in the Privacy header, no additional indication is necessary. For the second purpose; We understand that the redundancy of anonymization is not a problem. (Intermediaries could anonymize the message that is already anonymized.)

  5. UA-Driven Privacy (draft-ietf-sip-ua-privacy-01) Mayumi M. Next Step  Intended status Informational or BCP?  What to do next - Update the draft to incorporate comments on SIP-ML - WGLC?

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend