[rfc-dist] RFC 4596 on Guidelines for Usage of the Session Initiation Protocol (SIP) Caller Preferences Extension
rfc-editor at rfc-editor.org
Tue Jul 25 15:23:38 PDT 2006
A new Request for Comments is now available in online RFC libraries.
Title: Guidelines for Usage of the
Session Initiation Protocol (SIP) Caller Preferences
Author: J. Rosenberg, P. Kyzivat
Date: July 2006
Mailbox: jdrosen at cisco.com,
pkyzivat at cisco.com
I-D Tag: draft-ietf-sipping-callerprefs-usecases-05.txt
This document contains guidelines for usage of the Caller Preferences
Extension to the Session Initiation Protocol (SIP). It demonstrates
the benefits of caller preferences with specific example
applications, provides use cases to show proper operation, provides
guidance on the applicability of the registered feature tags, and
describes a straightforward implementation of the preference and
capability matching algorithm specified in Section 7.2 of RFC 3841.
This memo provides information for the Internet community.
This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.
INFORMATIONAL: 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
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
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
IETF-Announce mailing list
IETF-Announce at ietf.org
More information about the rfc-dist