IETF Logo Mail Archive

Re: [Sipping] comments on draft-roach-sipping-callcomp-bfcp-00

Thomas.Froment@alcatel.fr Wed, 08 November 2006 14:04 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gho2x-0007OI-HK; Wed, 08 Nov 2006 09:04:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gho0y-0006q6-C3 for sipping@ietf.org; Wed, 08 Nov 2006 09:02:52 -0500
Received: from smail.alcatel.fr ([62.23.212.165]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ghnne-0006tD-2C for sipping@ietf.org; Wed, 08 Nov 2006 08:49:11 -0500
Received: from frmail28.netfr.alcatel.fr (frmail28.netfr.alcatel.fr [155.132.251.28]) by smail.alcatel.fr (8.13.4/8.13.4/ICT) with ESMTP id kA8Dn6xj020923; Wed, 8 Nov 2006 14:49:06 +0100
Received: from [127.0.0.1] ([155.132.188.76]) by frmail28.netfr.alcatel.fr (Lotus Domino Release 5.0.9a) with ESMTP id 2006110814490079:3047 ; Wed, 8 Nov 2006 14:49:00 +0100
Message-ID: <4551E041.8080901@alcatel.fr>
Date: Wed, 08 Nov 2006 14:48:49 +0100
From: Thomas.Froment@alcatel.fr
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Jeroen van Bemmel <jbemmel@zonnet.nl>
Subject: Re: [Sipping] comments on draft-roach-sipping-callcomp-bfcp-00
References: <49E7012A614B024B80A7D175CB9A64EC0C02FE1B@ftrdmel1.rd.francetelecom.fr>
In-Reply-To: <49E7012A614B024B80A7D175CB9A64EC0C02FE1B@ftrdmel1.rd.francetelecom.fr>
X-MIMETrack: Itemize by SMTP Server on FRMAIL28/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at 11/08/2006 14:49:01, Serialize by Router on FRMAIL28/FR/ALCATEL(Release 5.0.9a |January 7, 2002) at 11/08/2006 14:49:02, Serialize complete at 11/08/2006 14:49:02
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
X-Scanned-By: MIMEDefang 2.51 on 155.132.180.81
X-Spam-Score: 1.3 (+)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: IETF Sipping List <sipping@ietf.org>, Adam Roach <adam@nostrum.com>, "Michael Hammer (mhammer)" <mhammer@cisco.com>
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

About the usage of BFCP, chairs started a poll yesterday during the 
meeting, but decided to stop it after 5/10 people raised their hand to 
vote for "this is a good approach"...
Then, Rohan(I think) asked "who understand  / is interested by the 
problem"?, and since few people were responding, nobody got the chance 
to vote for "this is NOT a good approach"...

So, maybe we can start a new poll on mailing list with *interested* people?

Jeroen van Bemmel wrote:

> That being said, I believe what is triggering the "academic" objections is the underlying model of draft-poetzl-sipping-call-completion-01: multiple subscriptions to a single resource (the CCBS/CCNR queue) but a single notification to the "first, non-suspended subscriber". That goes against
> RFC3265 (in more than one ways)
>   
Can you clatify this statement? for me, this  is not completely clear why...



_______________________________________________
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