idnits 2.17.1 draft-ietf-sip-message-07.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 3428 5 Title: Session Initiation Protocol (SIP) Extension for 6 Instant Messaging 7 Author(s): B. Campbell, Ed., J. Rosenberg, H. Schulzrinne, 8 C. Huitema, D. Gurle 9 Status: Standards Track 10 Date: December 2002 11 Mailbox: bcampbell@dynamicsoft.com, 12 jdrosen@dynamicsoft.com, 13 schulzrinne@cs.columbia.edu, 14 huitema@microsoft.com, dgurle@microsoft.com 15 Pages: 18 16 Characters: 41475 17 Updates/Obsoletes:SeeAlso: None 19 I-D Tag: draft-ietf-sip-message-07.txt 21 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3428.txt 23 Instant Messaging (IM) refers to the transfer of messages between 24 users in near real-time. These messages are usually, but not 25 required to be, short. IMs are often used in a conversational mode, 26 that is, the transfer of messages back and forth is fast enough for 27 participants to maintain an interactive conversation. 29 This document proposes the MESSAGE method, an extension to the 30 Session Initiation Protocol (SIP) that allows the transfer of Instant 31 Messages. Since the MESSAGE request is an extension to SIP, it 32 inherits all the request routing and security features of that 33 protocol. MESSAGE requests carry the content in the form of MIME 34 body parts. MESSAGE requests do not themselves initiate a SIP 35 dialog; under normal usage each Instant Message stands alone, much 36 like pager messages. MESSAGE requests may be sent in the context of 37 a dialog initiated by some other SIP request. 39 This document is a product of the Session Initiation Protocol Working 40 Group of the IETF. 42 This is now a Proposed Standard Protocol. 44 This document specifies an Internet standards track protocol for the 45 Internet community, and requests discussion and suggestions for 46 improvements. Please refer to the current edition of the "Internet 47 Official Protocol Standards" (STD 1) for the standardization state 48 and status of this protocol. Distribution of this memo is unlimited. 50 This announcement is sent to the IETF list and the RFC-DIST list. 51 Requests to be added to or deleted from the IETF distribution list 52 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 53 added to or deleted from the RFC-DIST distribution list should 54 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 56 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 57 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 58 help: ways_to_get_rfcs. For example: 60 To: rfc-info@RFC-EDITOR.ORG 61 Subject: getting rfcs 63 help: ways_to_get_rfcs 65 Requests for special distribution should be addressed to either the 66 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 67 specifically noted otherwise on the RFC itself, all RFCs are for 68 unlimited distribution.echo 69 Submissions for Requests for Comments should be sent to 70 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 71 Authors, for further information.