[rfc-dist] RFC 3960 on Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP)

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


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


        RFC 3960

        Title:      Early Media and Ringing Tone Generation
                    in the Session Initiation Protocol (SIP)
        Author(s):  G. Camarillo, H. Schulzrinne
        Status:     Informational
        Date:       December 2004
        Mailbox:    Gonzalo.Camarillo at ericsson.com,
                    schulzrinne at cs.columbia.edu
        Pages:      13
        Characters: 31692
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sipping-early-media-02.txt

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


This document describes how to manage early media in the Session
Initiation Protocol (SIP) using two models: the gateway model and the
application server model.  It also describes the inputs one needs to
consider in defining local policies for ringing tone generation.

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

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  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