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

Embedded below. 

> -----Original Message-----
> From: Elwell, John [mailto:john.elwell@siemens.com] 
> Sent: Wednesday, November 08, 2006 13:39
> To: Thomas.Froment@alcatel.fr; Jeroen van Bemmel
> Cc: Adam Roach; IETF Sipping List; Michael Hammer (mhammer)
> Subject: RE: [Sipping] comments on 
> draft-roach-sipping-callcomp-bfcp-00
> 
> 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.

As I also said at the mike, I agree 100% with John. Using 
a separate protocol like BFCP for CCBS+CCNR does not seem to
be a sensible way of solving this 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.

I completely agree again. 

I would also like to start with a native SIP approach based on
something like the Poetzle draft. If we want to start with a really
simple approach we can also look at section 2.17 of 
http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples-
11.txt
as a starting point.

But yes, if a plain dialog-package approach is not sufficient, then 
defining a package like in
http://tools.ietf.org/wg/sipping/draft-poetzl-sipping-call-completion-01
.txt seems much more appealing than using BFCP.

_______________________________________________
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