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

"Michael Hammer \(mhammer\)" <mhammer@cisco.com> Wed, 08 November 2006 16:43 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhqWs-0001H1-CD; Wed, 08 Nov 2006 11:43:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GhqW7-0000Sr-08 for sipping@ietf.org; Wed, 08 Nov 2006 11:43:11 -0500
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GhqUW-00065D-5X for sipping@ietf.org; Wed, 08 Nov 2006 11:41:33 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 08 Nov 2006 11:41:32 -0500
X-IronPort-AV: i="4.09,401,1157342400"; d="scan'208"; a="109135434:sNHT52268392"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA8GfVoo015712; Wed, 8 Nov 2006 11:41:31 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kA8GfRYT013497; Wed, 8 Nov 2006 11:41:31 -0500 (EST)
Received: from xmb-rtp-20b.amer.cisco.com ([64.102.31.53]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 8 Nov 2006 11:41:29 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sipping] comments on draft-roach-sipping-callcomp-bfcp-00
Date: Wed, 08 Nov 2006 11:41:28 -0500
Message-ID: <072C5B76F7CEAB488172C6F64B30B5E3022DAC14@xmb-rtp-20b.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] comments on draft-roach-sipping-callcomp-bfcp-00
Thread-Index: AccDPKo2+hdVmg1URUC//iEzqVqcHwAGAWTQ
From: "Michael Hammer (mhammer)" <mhammer@cisco.com>
To: Thomas.Froment@alcatel.fr, Jeroen van Bemmel <jbemmel@zonnet.nl>
X-OriginalArrivalTime: 08 Nov 2006 16:41:29.0991 (UTC) FILETIME=[BDCE7970:01C70354]
DKIM-Signature: a=rsa-sha1; q=dns; l=1446; t=1163004091; x=1163868091; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mhammer@cisco.com; z=From:=22Michael=20Hammer=20\(mhammer\)=22=20<mhammer@cisco.com> |Subject:RE=3A=20[Sipping]=20comments=20on=20draft-roach-sipping-callcomp-bfcp-00 |To:<Thomas.Froment@alcatel.fr>, =20=22Jeroen=20van=20Bemmel=22=20<jbemmel@zo nnet.nl>; X=v=3Dcisco.com=3B=20h=3DxesuDYUS5hhP5YgFmay3D64vSwM=3D; b=lgBMoByTUB23rk8gfJQv59zNxbE7MIauT1JfJEuNlGXhF17OYXbfJP6r3PmuPJfExa67FO7o SdcLTliEIXFSbUJCFWLnbfC5LgiBX0L+iVNbpnMMyURLuDcc/lGAPeq/;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=mhammer@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: IETF Sipping List <sipping@ietf.org>, Adam Roach <adam@nostrum.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

This does not sound like a valid poll.

Mike
 

> -----Original Message-----
> From: Thomas.Froment@alcatel.fr [mailto:Thomas.Froment@alcatel.fr] 
> Sent: Wednesday, November 08, 2006 8:49 AM
> To: Jeroen van Bemmel
> Cc: GARCIN Sebastien RD-CORE-ISS; Michael Hammer (mhammer); 
> Adam Roach; Jonathan Rosenberg (jdrosen); IETF Sipping List
> Subject: Re: [Sipping] comments on 
> draft-roach-sipping-callcomp-bfcp-00
> 
> 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