A new Request for Comments is now available in online RFC libraries.
BCP0119
RFC 4579
Title: Session Initiation Protocol (SIP) Call
Control - Conferencing for User Agents
Author: A. Johnston, O. Levin
Status: Best Current Practice
Date: August 2006
Mailbox: alan@sipstation.com,
oritl@microsoft.com
Pages: 43
Characters: 96506
Updates:
See-Also: BCP0119
I-D Tag: draft-ietf-sipping-cc-conferencing-07.txt
URL: http://www.rfc-editor.org/rfc/rfc4579.txt
This specification defines conferencing call control features for the
Session Initiation Protocol (SIP). This document builds on the
Conferencing Requirements and Framework documents to define how a
tightly coupled SIP conference works. The approach is explored from
the perspective of different user agent (UA) types:
conference-unaware, conference-aware, and focus UAs. The use of
Uniform Resource Identifiers (URIs) in conferencing, OPTIONS for
capabilities discovery, and call control using REFER are covered in
detail with example call flow diagrams. The usage of the isfocus
feature tag is defined. This document specifies an Internet Best Current
Practices for the Internet Community, and requests discussion and
suggestions for improvements.
This document is a product of the Session Initiation Proposal
Investigation Working Group of the IETF.
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. 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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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.
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.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
