Skip to main content

Session Initiation Protocol (SIP) Extension for Instant Messaging

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3428.
Authors Henning Schulzrinne , Jonathan Rosenberg , Ben Campbell , David M. Gurle , Christian Huitema
Last updated 2015-10-14 (Latest revision 2002-09-16)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3428 (Proposed Standard)
Action Holders
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Allison J. Mankin
IESG note
Send notices to <>
A new Request for Comments is now available in online RFC libraries.

        RFC 3428
        Title:      Session Initiation Protocol (SIP) Extension for
                    Instant Messaging
        Author(s):  B. Campbell, Ed., J. Rosenberg, H. Schulzrinne,
                    C. Huitema, D. Gurle
        Status:     Standards Track
        Date:       December 2002
        Pages:      18
        Characters: 41475
        Updates/Obsoletes:SeeAlso:    None
        I-D Tag:    draft-ietf-sip-message-07.txt


Instant Messaging (IM) refers to the transfer of messages between
users in near real-time.  These messages are usually, but not
required to be, short.  IMs are often used in a conversational mode,
that is, the transfer of messages back and forth is fast enough for
participants to maintain an interactive conversation.

This document proposes the MESSAGE method, an extension to the
Session Initiation Protocol (SIP) that allows the transfer of Instant
Messages.  Since the MESSAGE request is an extension to SIP, it
inherits all the request routing and security features of that
protocol.  MESSAGE requests carry the content in the form of MIME
body parts.  MESSAGE requests do not themselves initiate a SIP
dialog; under normal usage each Instant Message stands alone, much
like pager messages.  MESSAGE requests may be sent in the context of
a dialog initiated by some other SIP request.

This document is a product of the Session Initiation Protocol Working
Group of the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements.  Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.