draft-ietf-sipping-3pcc-01.txt   draft-ietf-sipping-3pcc-02.txt 
Internet Engineering Task Force SIPPING WG Internet Engineering Task Force SIPPING WG
Internet Draft J. Rosenberg Internet Draft J. Rosenberg
dynamicsoft dynamicsoft
J. Peterson J. Peterson
Neustar Neustar
H. Schulzrinne H. Schulzrinne
Columbia U. Columbia U.
G. Camarillo G. Camarillo
Ericsson Ericsson
draft-ietf-sipping-3pcc-01.txt draft-ietf-sipping-3pcc-02.txt
May 29, 2002 June 5, 2002
Expires: November 2002 Expires: December 2002
Best Current Practices for Third Party Call Control Best Current Practices for Third Party Call Control in the Session Initiation Protocol
in the Session Initiation Protocol
STATUS OF THIS MEMO STATUS OF THIS MEMO
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 5 skipping to change at page 1, line 49
Abstract Abstract
Third party call control refers to the ability of one entity to Third party call control refers to the ability of one entity to
create a call in which communications is actually between other create a call in which communications is actually between other
parties. Third party call control is possible using the mechanisms parties. Third party call control is possible using the mechanisms
specified within the Session Initiation Protocol (SIP). However, specified within the Session Initiation Protocol (SIP). However,
there are several possible approaches, each with different benefits there are several possible approaches, each with different benefits
and drawbacks. This document discusses best current practices for the and drawbacks. This document discusses best current practices for the
usage of the SIP for third party call control. usage of the SIP for third party call control.
Table of Contents
1 Introduction ........................................ 3
2 Terminology ......................................... 3
3 Definitions ......................................... 4
4 3pcc Call Establishment ............................. 4
4.1 Flow I .............................................. 4
4.2 Flow II ............................................. 5
4.3 Flow III ............................................ 7
4.4 Flow IV ............................................. 8
4.5 Recommendations ..................................... 10
5 Error Handling ...................................... 10
6 Continued Processing ................................ 11
7 3pcc and Early Media ................................ 12
8 Third Party Call Control and SDP Preconditions ...... 16
8.1 Controller Initiates ................................ 16
8.2 Party A Initiates ................................... 17
9 Example Call Flows .................................. 20
9.1 Click to Dial ....................................... 20
9.2 Mid-Call Announcement Capability .................... 22
10 Implementation Recommendations ...................... 24
11 Security Considerations ............................. 24
11.1 Identity ............................................ 24
11.2 End-to-End Encryption and Integrity ................. 25
12 IANA Considerations ................................. 25
13 Acknowledgements .................................... 25
14 Authors Addresses ................................... 25
15 Normative References ................................ 26
16 Informative References .............................. 27
1 Introduction 1 Introduction
(Note to RFC Editor - please replace all instances of RFC BBBB with (Note to RFC Editor - please replace all instances of RFC BBBB with
RFC 3261 when draft-ietf-sip-rfc2543bis is published as an RFC. RFC 3261 when draft-ietf-sip-rfc2543bis is published as an RFC.
Please replace all instances of RFC MMMM with the RFC number of Please replace all instances of RFC MMMM with the RFC number of
draft-ietf-sip-manyfolks-resource when it issues as an RFC.) draft-ietf-sip-manyfolks-resource when it issues as an RFC.)
In the traditional telephony context, third party call control allows In the traditional telephony context, third party call control allows
one entity (which we call the controller) to set up and manage a one entity (which we call the controller) to set up and manage a
communications relationship between two or more other parties. Third communications relationship between two or more other parties. Third
skipping to change at page 19, line 17 skipping to change at page 1, line 805
|<---------------------| | |<---------------------| |
|(2) 183 answer1 | | |(2) 183 answer1 | |
|no media | | |no media | |
|--------------------->| | |--------------------->| |
|(3) PRACK | | |(3) PRACK | |
|<---------------------| | |<---------------------| |
|(4) 200 OK | | |(4) 200 OK | |
|--------------------->| | |--------------------->| |
| |(5) INVITE no SDP | | |(5) INVITE no SDP |
| |--------------------->| | |--------------------->|
| |(6) 183 OK offer2 | | |(6) 183 offer2 |
| |des=sendrecv | | |des=sendrecv |
| |conf=recv | | |conf=recv |
| |cur=none | | |cur=none |
| |<---------------------| | |<---------------------|
|(7) UPDATE offer2' | | |(7) UPDATE offer2' | |
|des=sendrecv | | |des=sendrecv | |
|conf=recv | | |conf=recv | |
|cur=none | | |cur=none | |
|<---------------------| | |<---------------------| |
|(8) 200 UPDATE | | |(8) 200 UPDATE | |
skipping to change at line 1290 skipping to change at page 1, line 1260
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
1 Introduction ........................................ 3
2 Terminology ......................................... 3
3 Definitions ......................................... 4
4 3pcc Call Establishment ............................. 4
4.1 Flow I .............................................. 4
4.2 Flow II ............................................. 5
4.3 Flow III ............................................ 7
4.4 Flow IV ............................................. 8
4.5 Recommendations ..................................... 10
5 Error Handling ...................................... 10
6 Continued Processing ................................ 11
7 3pcc and Early Media ................................ 12
8 Third Party Call Control and SDP Preconditions ...... 16
8.1 Controller Initiates ................................ 16
8.2 Party A Initiates ................................... 17
9 Example Call Flows .................................. 20
9.1 Click to Dial ....................................... 20
9.2 Mid-Call Announcement Capability .................... 22
10 Implementation Recommendations ...................... 24
11 Security Considerations ............................. 24
11.1 Identity ............................................ 24
11.2 End-to-End Encryption and Integrity ................. 25
12 IANA Considerations ................................. 25
13 Acknowledgements .................................... 25
14 Authors Addresses ................................... 25
15 Normative References ................................ 26
16 Informative References .............................. 27
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/