[rfc-dist] RFC 3959 on The Early Session Disposition Type for the Session Initiation Protocol (SIP)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Tue Dec 21 15:20:16 PST 2004


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


        RFC 3959

        Title:      The Early Session Disposition Type for
                    the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo
        Status:     Standards Track
        Date:       December 2004
        Mailbox:    Gonzalo.Camarillo at ericsson.com
        Pages:      11
        Characters: 22160
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-early-disposition-03.txt

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


This document defines a new disposition type (early-session) for the
Content-Disposition header field in the Session Initiation Protocol
(SIP).  The treatment of "early-session" bodies is similar to the
treatment of "session" bodies.  That is, they follow the offer/answer
model.  Their only difference is that session descriptions whose
disposition type is "early-session" are used to establish early media
sessions within early dialogs, as opposed to regular sessions within
regular dialogs.

This document is a product of the Session Initiation Proposal
Investigation 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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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

        To: rfc-info at 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 at 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 at 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.
-------------- next part --------------
Skipped content of type multipart/alternative


More information about the rfc-dist mailing list