[rfc-dist] RFC 3841 on Caller Preferences for the Session Initiation Protocol (SIP)

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Tue Aug 31 08:43:03 PDT 2004

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

        RFC 3841

        Title:      Caller Preferences for the Session Initiation
                    Protocol (SIP)
        Author(s):  J. Rosenberg, H. Schulzrinne, P. Kyzivat
        Status:     Standards Track
        Date:       August 2004
        Mailbox:    jdrosen at dynamicsoft.com,
                    schulzrinne at cs.columbia.edu, pkyzivat at cisco.com
        Pages:      26
        Characters: 61382
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-sip-callerprefs-10.txt

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

This document describes a set of extensions to the Session Initiation
Protocol (SIP) which allow a caller to express preferences about
request handling in servers.  These preferences include the ability to
select which Uniform Resource Identifiers (URI) a request gets routed
to, and to specify certain request handling directives in proxies and
redirect servers.  It does so by defining three new request header
fields, Accept-Contact, Reject-Contact, and Request-Disposition,
which specify the caller's preferences.

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 at 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 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