idnits 2.17.1 draft-ietf-sip-privacy-general-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3323 5 Title: A Privacy Mechanism for the Session Initiation 6 Protocol (SIP) 7 Author(s): J. Peterson 8 Status: Standards Track 9 Date: November 2002 10 Mailbox: jon.peterson@neustar.biz 11 Pages: 22 12 Characters: 54116 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-ietf-sip-privacy-general-01.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3323.txt 19 This document defines new mechanisms for the Session Initiation 20 Protocol (SIP) in support of privacy. Specifically, guidelines are 21 provided for the creation of messages that do not divulge personal 22 identity information. A new "privacy service" logical role for 23 intermediaries is defined to answer some privacy requirements that 24 user agents cannot satisfy themselves. Finally, means are presented 25 by which a user can request particular functions from a privacy 26 service. 28 This document is a product of the Session Initiation Proposal 29 Investigation Working Group of the IETF. 31 This is now a Proposed Standard Protocol. 33 This document specifies an Internet standards track protocol for 34 the Internet community, and requests discussion and suggestions 35 for improvements. Please refer to the current edition of the 36 "Internet Official Protocol Standards" (STD 1) for the 37 standardization state and status of this protocol. Distribution 38 of this memo is unlimited. 40 This announcement is sent to the IETF list and the RFC-DIST list. 41 Requests to be added to or deleted from the IETF distribution list 42 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 43 added to or deleted from the RFC-DIST distribution list should 44 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 46 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 47 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 48 help: ways_to_get_rfcs. For example: 50 To: rfc-info@RFC-EDITOR.ORG 51 Subject: getting rfcs 53 help: ways_to_get_rfcs 55 Requests for special distribution should be addressed to either the 56 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 57 specifically noted otherwise on the RFC itself, all RFCs are for 58 unlimited distribution.echo 59 Submissions for Requests for Comments should be sent to 60 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 61 Authors, for further information.