[Insipid] Conference INSIPID backwards-compat call flows
Hadriel Kaplan <hadriel.kaplan@oracle.com> Sat, 17 August 2013 14:09 UTC
Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0CF11E8125 for <insipid@ietfa.amsl.com>; Sat, 17 Aug 2013 07:09:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.432
X-Spam-Level:
X-Spam-Status: No, score=-6.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGYHE0kcuLqu for <insipid@ietfa.amsl.com>; Sat, 17 Aug 2013 07:09:22 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id AB18A11E8122 for <insipid@ietf.org>; Sat, 17 Aug 2013 07:09:22 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r7HE9Fk3011690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <insipid@ietf.org>; Sat, 17 Aug 2013 14:09:17 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7HE9F1D011199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <insipid@ietf.org>; Sat, 17 Aug 2013 14:09:15 GMT
Received: from abhmt118.oracle.com (abhmt118.oracle.com [141.146.116.70]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r7HE9E2g012582 for <insipid@ietf.org>; Sat, 17 Aug 2013 14:09:14 GMT
Received: from [192.168.1.108] (/66.31.4.117) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 17 Aug 2013 07:09:14 -0700
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <5EE2A3AF-4AA0-44A5-BFC2-642F24367AFB@oracle.com>
Date: Sat, 17 Aug 2013 10:09:14 -0400
To: "insipid@ietf.org" <insipid@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Subject: [Insipid] Conference INSIPID backwards-compat call flows
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2013 14:09:31 -0000
This email is about the conferencing cases. Note that as far as I'm aware, the INSIPID requirements document does NOT consider these call flows in-scope, in the sense that it says they're actually separate, distinct communication sessions. See section 3.2 in the requirements draft: http://tools.ietf.org/html/draft-ietf-insipid-session-id-reqts-08#page-4 Regardless, below are the call flows... --------------------------------------------------------------------------- 9.4. Single Focus Conferencing Multiple users call into a conference server (say, an MCU) to attend one of many conferences hosted on or managed by that server. Each user has to identify which conference they want to join, but this information is not necessarily in the SIP messaging. It might be done by having a dedicated address for the conference or via an IVR, as assumed in this example. Each user in this example goes through a two-step process of signaling to gain entry onto their conference call. Session ID Conference --- Alice Focus Bob Carol | | | | | | | | {A} |----INVITE----->| | | {A;M1} |<---200 OK------| | | {A;M1} |-----ACK------->| | | |<====RTP=======>| | | {A;M'} |<---reINVITE----| (to change the | | {A;M'} |-----200 OK---->| UUID to M') | | {A;M'} |<-----ACK-------| | | | | | | | | | | {B} | |<----INVITE-----| | {B;M2} | |-----200 OK---->| | {B;M2} | |<-----ACK-------| | | |<=====RTP======>| | {B;M'} | (to change the |----reINVITE--->| | {B;M'} | UUID to M') |<----200 OK-----| | {B;M'} | |------ACK------>| | | | | | | | | | {C} | |<--------------------INVITE-----| {C;M3} | |---------------------200 OK---->| {C;M3} | |<---------------------ACK-------| | |<=====================RTP======>| {C;M'} | (to change the |--------------------reINVITE--->| {C;M'} | UUID to M') |<--------------------200 OK-----| {C;M'} | |----------------------ACK------>| Figure 4 - Single Focus Conference Bridge --------------------------------------------------------------------------- 9.5. Single Focus Conferencing using WebEx Alice, Bob and Carol call into same Webex conference. Session ID Conference --- Alice Focus Bob Carol | | | | |<** HTTPS *****>| | | | Transaction | | | | | | | {M} |<----INVITE-----| | | {M;A} |-----200 OK---->| | | {M;A} |<-----ACK-------| | | |<=====RTP======>| | | | | | | | |<** HTTPS *****>| | | | Transaction | | | | | | {M} | |-----INVITE---->| | {M;B} | |<----200 OK-----| | {M;B} | |------ACK------>| | | |<=====RTP======>| | | | | | | |<****************** HTTPS *****>| | | Transaction | | | | | {M} | |--------------------INVITE----->| {M;C} | |<-------------------200 OK------| {M;C} | |---------------------ACK------->| | |<====================RTP=======>| Figure 5 - Single Focus Webex Conference --------------------------------------------------------------------------- 9.6. Cascading Conference Bridge Support for the Session ID To expand conferencing capabilities requires cascading conference bridges. A conference bridge, or MCU, needs a way to identify itself when contacting another MCU. RFC 4579 [RFC4579] defines the 'isfocus' Contact: header parameter just for this purpose. Session ID --- MCU-1 MCU-2 MCU-3 MCU-4 | | | | {M'} |----INVITE----->| | | {M';J} |<---200 OK------| | | {M';J} |-----ACK------->| | | Figure 6 - MCUs Communicating Session ID UUID for Bridge Session ID --- MCU-1 MCU-2 MCU-3 MCU-4 | | | | {M'} |----INVITE----->| | | {M';J} |<---200 OK------| | | {M';J} |-----ACK------->| | | | | | | {M'} |---------------------INVITE----->| | {M';K} |<--------------------200 OK------| | {M';K} |----------------------ACK------->| | | | | | {M'} |-------------------------------------INVITE----->| {M';L} |<------------------------------------200 OK------| {M';L} |--------------------------------------ACK------->| Figure 7 - MCU Communicating Session ID UUID to More than One -hadriel
- [Insipid] Conference INSIPID backwards-compat cal… Hadriel Kaplan