RE: [Sipping] comments on draft-roach-sipping-callcomp-bfcp-00
"Elwell, John" <john.elwell@siemens.com> Wed, 08 November 2006 21:39 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghv8x-0001nd-5t; Wed, 08 Nov 2006 16:39:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ghv8w-0001nV-1G for sipping@ietf.org; Wed, 08 Nov 2006 16:39:34 -0500
Received: from mailgate.siemenscomms.co.uk ([195.171.110.225] helo=bemg01.siemenscomms.co.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ghv8q-0000j5-Mo for sipping@ietf.org; Wed, 08 Nov 2006 16:39:32 -0500
Received: from ntht207e.uksgcs.siemenscomms.co.uk ([137.223.247.82]) by siemenscomms.co.uk (PMDF V6.0-24 #40642) with ESMTP id <0J8F00B7NLHKP3@siemenscomms.co.uk> for sipping@ietf.org; Wed, 08 Nov 2006 21:39:20 +0000 (GMT)
Received: by ntht207e.uksgcs.siemenscomms.co.uk with Internet Mail Service (5.5.2657.72) id <49LG0G8Q>; Wed, 08 Nov 2006 21:39:09 +0000
Content-return: allowed
Date: Wed, 08 Nov 2006 21:39:07 +0000
From: "Elwell, John" <john.elwell@siemens.com>
Subject: RE: [Sipping] comments on draft-roach-sipping-callcomp-bfcp-00
To: Thomas.Froment@alcatel.fr, Jeroen van Bemmel <jbemmel@zonnet.nl>
Message-id: <50B1CBA96870A34799A506B2313F26670A5023AE@ntht201e.siemenscomms.co.uk>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-type: text/plain
Content-transfer-encoding: 7bit
X-Spam-Score: 1.1 (+)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc: Adam Roach <adam@nostrum.com>, IETF Sipping List <sipping@ietf.org>, "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
As I stated at the mic yesterday and also in an earlier email, I do not think the BFCP approach is a sensible way of solving the call completion problem. Setting aside alternative solutions that might be more appropriate in a pure SIP environment, if the main driver is to provide a solution that can interwork with PSTN CCBS/CCNR, we should try to satisfy this requirement in the simplest way possible. IMO, BFCP is not the simplest approach and introduces unwanted complexity, particularly at a gateway. I think the Poetzle draft is a far better starting point, especially if we could try to align it better with the principles of RFC 3265, for example following some of the suggestions of Jeroen. John > -----Original Message----- > From: Thomas.Froment@alcatel.fr [mailto:Thomas.Froment@alcatel.fr] > Sent: 08 November 2006 13:49 > To: Jeroen van Bemmel > Cc: IETF Sipping List; Adam Roach; Michael Hammer (mhammer) > 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 > _______________________________________________ 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
- [Sipping] comments on draft-roach-sipping-callcom… Jonathan Rosenberg
- AW: [Sipping] comments on draft-roach-sipping-cal… Huelsemann, Martin
- Re: [Sipping] comments on draft-roach-sipping-cal… Adam Roach
- AW: [Sipping] comments on draft-roach-sipping-cal… Huelsemann, Martin
- RE: [Sipping] comments on draft-roach-sipping-cal… Elwell, John
- AW: [Sipping] comments on draft-roach-sipping-cal… Huelsemann, Martin
- RE: [Sipping] comments on draft-roach-sipping-cal… GARCIN Sebastien RD-CORE-ISS
- Re: AW: [Sipping] comments on draft-roach-sipping… Jonathan Rosenberg
- Re: AW: [Sipping] comments on draft-roach-sipping… Paul Kyzivat
- RE: [Sipping] comments on draft-roach-sipping-cal… Michael Hammer (mhammer)
- RE: [Sipping] comments on draft-roach-sipping-cal… GARCIN Sebastien RD-CORE-ISS
- Re: [Sipping] comments on draft-roach-sipping-cal… Jeroen van Bemmel
- RE: [Sipping] comments on draft-roach-sipping-cal… GARCIN Sebastien RD-CORE-ISS
- Re: [Sipping] comments on draft-roach-sipping-cal… Thomas.Froment
- Re: [Sipping] comments on draft-roach-sipping-cal… Jeroen van Bemmel
- RE: [Sipping] comments on draft-roach-sipping-cal… Michael Hammer (mhammer)
- RE: [Sipping] comments on draft-roach-sipping-cal… Elwell, John
- RE: [Sipping] comments on draft-roach-sipping-cal… Francois Audet