SIP隐私机制：保护个人身份信息

需积分: 10 25 浏览量更新于2024-07-22 收藏 33KB PDF 举报

RFC 3323 - A Privacy Mechanism for the Session Initiation Protocol (SIP) RFC 3323 是一个关于 Session Initiation Protocol (SIP) 的隐私机制的规范文档，该文档定义了新的机制来支持 SIP 隐私。下面是该文档中提到的知识点： 1. 隐私机制：该文档定义了新的机制来支持 SIP 隐私，旨在保护用户的个人身份信息不被泄露。 2. 隐私服务：文档中定义了一个新的逻辑角色-"隐私服务"，用于满足用户代理无法满足的隐私要求。该角色将扮演着中间人的角色，帮助用户保护其隐私。 3. 消息创建指南：文档提供了创建不泄露个人身份信息的消息的指南，旨在保护用户的隐私。 4. 用户请求：文档中还提供了用户请求特定功能的方法，从而可以从隐私服务中获取所需的隐私保护功能。 5. SIP 隐私机制架构：该文档定义了一个基于 SIP 的隐私机制架构，旨在保护用户的隐私。 6. 隐私服务的逻辑角色：文档中定义了隐私服务的逻辑角色，该角色扮演着中间人的角色，帮助用户保护其隐私。 7. SIP 消息隐私保护：文档提供了保护 SIP 消息隐私的机制，旨在保护用户的隐私。 8. 用户隐私保护：文档中定义了用户隐私保护的机制，旨在保护用户的隐私。 9. 隐私服务请求：文档提供了用户请求隐私服务的方法，旨在获取所需的隐私保护功能。 10. SIP 隐私机制的实现：文档提供了实现 SIP 隐私机制的指南，旨在保护用户的隐私。 11. 隐私机制的安全性：文档中讨论了隐私机制的安全性问题，旨在保护用户的隐私。 12. SIP 隐私机制的优点：文档中讨论了 SIP 隐私机制的优点，旨在保护用户的隐私。 13. 隐私服务的实现：文档提供了实现隐私服务的指南，旨在保护用户的隐私。 14. 用户隐私保护机制：文档中定义了用户隐私保护机制，旨在保护用户的隐私。 15. SIP 隐私机制的应用：文档中讨论了 SIP 隐私机制的应用，旨在保护用户的隐私。 RFC 3323 提供了一个基于 SIP 的隐私机制，旨在保护用户的隐私。该文档定义了隐私机制的架构、隐私服务的逻辑角色、消息创建指南、用户请求机制等，旨在保护用户的隐私。

RFC 3323 Privacy Mechanism for SIP November 2002

3.1 When is Privacy Necessary?

Users may wish for identity information to be withheld from a given

party for any number of reasons, for example:

Users might want to contact a particular party without revealing

their identity in order to impart information with which they

would not like to be associated

Users might fear that the exposure of their identity or personal

information to some networks or destinations will make them a

target for unsolicited advertising, legal censure or other

undesirable consequences

Users might want to withhold from participants in a session the

identity by which they are known to network intermediaries for the

purposes of billing and accounting

When a user agent decides to send a request through a proxy server,

it may be difficult for the originator to anticipate the final

destination of that message. For that reason, users are advised not

to base their estimation of their privacy needs on where they expect

a message will go. For example, if a user sends a request to

telephone number, they may believe that the final destination of the

request will be a station in the public switched telephone network

(PSTN) that is unable to inspect, say, SIP Contact headers, and

therefore assume that it is safe to leave such headers in the clear;

however, such a request might very well end up being retargeted by

the network to a native SIP endpoint to which Contact headers are

quite legible.

This document describes three degrees of privacy - one level of

user-provided privacy, and two levels of network-provided privacy

(header privacy and session privacy). How much privacy does a user

need for any given session? Generally, if a user is seeking privacy,

they’re going to need as much of it as they can get. However, if a

user knows of no privacy service, they must be content with user-

provided privacy alone. Similarly, if a user knows of an

anonymization service that can provide session privacy, but is unable

to secure session traffic to prevent the anonymizer from possibly

eavesdropping on the session, they might judge the loss of session

privacy to be the lesser evil. The user might also be aware of

exceptional conditions about the architecture in which the user agent

is deployed that may obviate one or more privacy concerns.

Peterson Standards Track [Page 5]

剩余21页未读，继续阅读

zsu_leo

粉丝: 4
资源: 9

SIP隐私机制：保护个人身份信息

rfc3262.txt.zip_rfc3261_rfc3261.txt_rfc3262_sip 3261

rfc3262.rar_RFC 3262 .P_rfc32_rfc3262

SIP.rar_rfc2543.pdf_sip

rfc1661.txt.rar_PPP RFC1661.txt_RFC16_memo_ppp_rfc1661

SIP协议.RFC3621中文版.zip_RFC 3621_RFC3621_sip_sip rfc3621_sip协议

RFC4244.An_Extension_to_SIP_for_Request_History_Information

rfc3016.rar_3016. com_RFC3016_RFC3016中文版_rfc 3016 pudn

SIP-RFC3261.rar_rfc3261_sip

rfc5366.Conference_Establishment_in_SIP

RFC868.ZIP_rfc868s.zip_windows2003 RFC 868

最新资源