1 / 3

UA-Driven Privacy Mechanism for SIP draft-ietf-sip-ua-privacy-01

IETF71 SIP - Mar. 13rd, 2008. UA-Driven Privacy Mechanism for SIP draft-ietf-sip-ua-privacy-01. Mayumi Munakata Shida Schubert Takumi Ohba. UA-Driven Privacy (draft-ietf-sip-ua-privacy-01) Mayumi M. Changes from 00 (and from draft-munakata-sip-privacy-new-01).

bunny
Download Presentation

UA-Driven Privacy Mechanism for SIP draft-ietf-sip-ua-privacy-01

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. IETF71 SIP - Mar. 13rd, 2008 UA-Driven Privacy Mechanism for SIPdraft-ietf-sip-ua-privacy-01 Mayumi Munakata Shida Schubert Takumi Ohba

  2. UA-Driven Privacy (draft-ietf-sip-ua-privacy-01) Mayumi M. Changes from 00(and from draft-munakata-sip-privacy-new-01) • Treatment of From headerIn the previous version, a temp-gruu was used as an anonymous URI in the Contact and From headers.In the current version, a temp-gruu is only for the Contact header, and the anonymous URI for the From header is FFS.The draft-ietf-sip-gruu-15 allows a temp-gruu to be set in the Contact header only, but does not allow it in the From header. • Editorial changes- Readable text.- Change the term of "user-privacy-related" to "privacy-sensitive".- Add the term of "privacy-sensitive information" into the Terminology section.

  3. UA-Driven Privacy (draft-ietf-sip-ua-privacy-01) Mayumi M. Open Issue • Anonymous URI for the From header RFC 3261 recommends "anonymous@anonymous.invalid" in the From header, which makes the SIP-Identity (RFC 4474) unavailable. RFC 4474 (Step 2 in Sec 5) recommends "anonymous@{user's domain name}". What should UA set in the From header of an anonymous message? 1. "anonymous@anonymous.invalid" 2. "anonymous@{user's domain name}" 3. A temporary GRUU Is it reasonable to extend the GRUU and use a temp-gruu as an authenticated anonymous From address? Any use cases? Our proposal:Suggest the use of "anonymous@{user's domain name}" and make a note that the SIP-Identity will not function when "anonymous@anonymous.invalid" is used.

More Related