RFC 3903 on Session Initiation Protocol (SIP) Extension for Event State Publication

A new Request for Comments is now available in online RFC libraries.

        RFC 3903

        Title:      Session Initiation Protocol (SIP) Extension
                    for Event State Publication
        Author(s):  A. Niemi, Ed.
        Status:     Standards Track
        Date:       October 2004
        Mailbox:    aki.niemi@nokia.com
        Pages:      32
        Characters: 72062
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-publish-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3903.txt

This document describes an extension to the Session Initiation
Protocol (SIP) for publishing event state used within the SIP Events
framework.  The first application of this extension is for the
publication of presence information.

The mechanism described in this document can be extended to support
publication of any event state for which there exists an appropriate
event package.  It is not intended to be a general-purpose mechanism
for transport of arbitrary data, as there are better-suited
mechanisms for this purpose.

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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.

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.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.