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

        RFC 3311

        Title:      The Session Initiation Protocol (SIP)
                    UPDATE Method
        Author(s):  J. Rosenberg
        Status:     Standards Track
        Date:       October 2002
        Mailbox:    jdrosen@dynamicsoft.com
        Pages:      13
        Characters: 28125
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-update-02.txt

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

This specification defines the new UPDATE method for the Session
Initiation Protocol (SIP).  UPDATE allows a client to update
parameters of a session (such as the set of media streams and their
codecs) but has no impact on the state of a dialog.  In that sense,
it is like a re-INVITE, but unlike re-INVITE, it can be sent before
the initial INVITE has been completed.  This makes it very useful for
updating session parameters within early dialogs.

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.