IETF Logo Mail Archive

[Sipping] Comments on draft-roach-sipping-callcomp-bfcp-00.txt

Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com> Tue, 31 October 2006 19:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GezLq-0003Fr-Ce; Tue, 31 Oct 2006 14:32:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GezLn-0003Fh-4j for sipping@ietf.org; Tue, 31 Oct 2006 14:32:43 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GezLf-0002VB-Hx for sipping@ietf.org; Tue, 31 Oct 2006 14:32:43 -0500
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 0633D3B9; Tue, 31 Oct 2006 20:32:35 +0100 (CET)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 20:32:33 +0100
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 31 Oct 2006 20:32:33 +0100
Received: from [131.160.126.98] (rvi2-126-98.lmf.ericsson.se [131.160.126.98]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 57D772370; Tue, 31 Oct 2006 21:32:33 +0200 (EET)
Message-ID: <4547A4D0.2060704@ericsson.com>
Date: Tue, 31 Oct 2006 21:32:32 +0200
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: sipping <sipping@ietf.org>, Adam Roach <adam@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 31 Oct 2006 19:32:33.0876 (UTC) FILETIME=[50410940:01C6FD23]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc:
Subject: [Sipping] Comments on draft-roach-sipping-callcomp-bfcp-00.txt
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Errors-To: sipping-bounces@ietf.org

Hi,

a few comments on draft-roach-sipping-callcomp-bfcp-00.txt.

The draft proposes to to establish a SIP session for the BFCP
connection. Once the floor is grated, the callee establishes another SIP
session for the actual call.

The draft should explain how the callee correlates both SIP sessions.
That is, how does the callee know that the user calling is the same one
as got the floor. The draft should deal with such correlations for
anonymous callers as well, where the caller's identity will not be
available for the correlation.

Two possible solutions for this correlation are to use RFC 4538 or to
use the same session for BFCP and for the actual call (e.g., sending a
re-INVITE). RFC 4538 would work with the mechanism as specified in the
current draft.


A question: the draft talks about the establishment of one or more BFCP
sessions. What do you have in mind? In which cases would UAs establish
more than one BFCP session?


Cheers,

Gonzalo


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sip@ietf.org for new developments of core SIP

v2.23.0 | Report a Bug | By Email