idnits 2.17.1 draft-ietf-sip-sec-agree-05.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 3329 5 Title: Security Mechanism Agreement for the Session 6 Initiation Protocol (SIP) 7 Author(s): J. Arkko, V. Torvinen, G. Camarillo, A. Niemi, 8 T. Haukka 9 Status: Standards Track 10 Date: January 2003 11 Mailbox: jari.arkko@ericsson.com, 12 vesa.torvinen@ericsson.fi, 13 Gonzalo.Camarillo@ericsson.com, 14 aki.niemi@nokia.com, tao.haukka@nokia.com 15 Pages: 24 16 Characters: 51503 17 Updates/Obsoletes/See Also: None 19 I-D Tag: draft-ietf-sip-sec-agree-05.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3329.txt 23 This document defines new functionality for negotiating the security 24 mechanisms used between a Session Initiation Protocol (SIP) user 25 agent and its next-hop SIP entity. This new functionality 26 supplements the existing methods of choosing security mechanisms 27 between SIP entities. 29 This document is a product of the Session Initiation Protocol Working 30 Group of the IETF. 32 This is now a Proposed Standard Protocol. 34 This document specifies an Internet standards track protocol for 35 the Internet community, and requests discussion and suggestions 36 for improvements. Please refer to the current edition of the 37 "Internet Official Protocol Standards" (STD 1) for the 38 standardization state and status of this protocol. Distribution 39 of this memo is unlimited. 41 This announcement is sent to the IETF list and the RFC-DIST list. 42 Requests to be added to or deleted from the IETF distribution list 43 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 44 added to or deleted from the RFC-DIST distribution list should 45 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 47 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 48 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 49 help: ways_to_get_rfcs. For example: 51 To: rfc-info@RFC-EDITOR.ORG 52 Subject: getting rfcs 54 help: ways_to_get_rfcs 56 Requests for special distribution should be addressed to either the 57 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 58 specifically noted otherwise on the RFC itself, all RFCs are for 59 unlimited distribution.echo 60 Submissions for Requests for Comments should be sent to 61 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 62 Authors, for further information.