idnits 2.17.1 draft-ietf-sip-asserted-identity-02.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 3325 5 Title: Private Extensions to the Session Initiation 6 Protocol (SIP) for Asserted Identity within 7 Trusted Networks 8 Author(s): C. Jennings, J. Peterson, M. Watson 9 Status: Informational 10 Date: November 2002 11 Mailbox: fluffy@cisco.com, Jon.Peterson@NeuStar.biz, 12 mwatson@nortelnetworks.com 13 Pages: 18 14 Characters: 36170 15 Updates/Obsoletes/SeeAlso: None 17 I-D Tag: draft-ietf-sip-asserted-identity-02.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3325.txt 21 This document describes private extensions to the Session Initiation 22 Protocol (SIP) that enable a network of trusted SIP servers to assert 23 the identity of authenticated users, and the application of existing 24 privacy mechanisms to the identity problem. The use of these 25 extensions is only applicable inside an administrative domain with 26 previously agreed-upon policies for generation, transport and usage of 27 such information. This document does NOT offer a general privacy or 28 identity model suitable for use between different trust domains, or 29 use in the Internet at large. 31 This document is a product of the Session Initiation Protocol Working 32 Group and the Session Initiation Proposal Investigation Working Groups 33 of the IETF. 35 This memo provides information for the Internet community. It does 36 not specify an Internet standard of any kind. Distribution of this 37 memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.