From bliss-bounces@ietf.org Sat Dec 01 20:34:46 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IydjB-0001fS-7S; Sat, 01 Dec 2007 20:34:37 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Iydj9-0001ew-73
	for bliss@ietf.org; Sat, 01 Dec 2007 20:34:35 -0500
Received: from agnada.com ([69.36.182.244])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Iydj8-00038y-Q7
	for bliss@ietf.org; Sat, 01 Dec 2007 20:34:35 -0500
Received: from [192.168.1.4] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lB21YX2a012642
	for <bliss@ietf.org>; Sat, 1 Dec 2007 18:34:34 -0700
Message-ID: <47520BA7.1090100@ntt-at.com>
Date: Sat, 01 Dec 2007 17:34:31 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Subject: [BLISS] [Fwd: SFSIW-1 Call for Participation]
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

FYI
----------------------

The First SIP Forum SIP Interoperability Workshop will be held Monday,
December 3, from 11:30am - 1pm in Salon B at the Westin Bayshore Hotel
in Vancouver, British Columbia, Canada.

Note the session is open to the community.  However, making
presentations and lunch are only available to those individuals who, per
the Call for Papers and Participation, submitted a position paper.

The submitted position papers for the First SIP Interoperability

Workshop can be found here:

<http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,42/Itemid,75>
Some mailers may break the above line.  Remember to reassemble it.
Otherwise, here is a TinyURL link to the same page.
http://tinyurl.com/2mq5cz







_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



From bliss-bounces@ietf.org Thu Dec 06 11:00:07 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J0J8u-0002Rc-7x; Thu, 06 Dec 2007 11:00:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J0J8s-0002RT-DR
	for bliss@ietf.org; Thu, 06 Dec 2007 11:00:02 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J0J8r-0007Jh-Tk
	for bliss@ietf.org; Thu, 06 Dec 2007 11:00:02 -0500
Received: from sj-dkim-4.cisco.com ([171.71.179.196])
	by sj-iport-2.cisco.com with ESMTP; 06 Dec 2007 08:00:01 -0800
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id lB6G01cs005714
	for <bliss@ietf.org>; Thu, 6 Dec 2007 08:00:01 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id lB6G01nb006494
	for <bliss@ietf.org>; Thu, 6 Dec 2007 16:00:01 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 6 Dec 2007 08:00:01 -0800
Received: from [10.21.119.199] ([10.21.119.199]) by xfe-sjc-211.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 6 Dec 2007 08:00:01 -0800
Message-ID: <47581CA7.2000705@cisco.com>
Date: Thu, 06 Dec 2007 11:00:39 -0500
From: Jonathan Rosenberg <jdrosen@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 06 Dec 2007 16:00:01.0180 (UTC)
	FILETIME=[0EB3CDC0:01C83821]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2789; t=1196956801;
	x=1197820801; c=relaxed/simple; s=sjdkim4002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jdrosen@cisco.com;
	z=From:=20Jonathan=20Rosenberg=20<jdrosen@cisco.com>
	|Subject:=20comments=20on=20draft-poetzl-bliss-call-completion
	|Sender:=20; bh=J2/62X28kyD3DYX/su0Z5QgwrfqZxd94LMUM+LjfpCo=;
	b=XYP4VI4mXGkDDTXRXp3xkxwMlfNKQCAy19mdiMgOJiluVxJr0MscabEIEF258E+0wklpCy+O
	1i4kROBzjJxB20JV7OvfUbG7sZ3JWuN6ft4bf4GY5qSdOa7Q5uvsgKqq;
Authentication-Results: sj-dkim-4; header.From=jdrosen@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim4002 verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Subject: [BLISS] comments on draft-poetzl-bliss-call-completion
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

Section 6.1:

I think this completely understates the problem; if the caller is using 
dialog and the callee is using http polling it completely fails. 
Similarly in section 6.3. Just because a UA supports the dialog event 
package, doesn't mean it would know to subscribe for call completion 
using it.

> Conclusion 
>      
>     As seen on the analysis above, when dialog event package is used, 
>     it's only the server that needs to support call-completion, and 
>     with the wide implementations of the dialog event package, high 
>     level of interoperability can be anticipated if this approach is 
>     used. 

I don't understand this. The caller needs to clearly support call 
completion since there needs to be a UI for the user to invoke it, and 
the UA has to know to utilize dialog event package. Call completion is 
clearly a double-ended service in that both sides need to support some 
functionality beyond existing specs for it to work.

General comments:

The document says there is no role for state agents. But what about a 
user that has multiple devices. Is the assumption that there is a 
stateful b2bua type of element that is aware of the state of all of 
them, and the subscribe terminates there? That would be a state agent. 
Or does the SUBSCRIBE fork to all devices? This is important since we'll 
need to make recommendations on which elements implement the event agent 
side of this - phones or 'servers' in the network. I'll note this 
question is addressed in draft-worley-call-completion. That draft raises 
several issues which need to be addressed, in particular:

1. handling multiple UAs at caller side
2. handling multiple UAs at callee side
3. correlating the call completion call with the queue request
4. figuring out how to determine the availability states of user/UA

So I believe we will need to combine these two drafts for a complete 
solution.




Nits:

> this, until either the callee receives a HTTP response that 
> 
>  Poetzl                    Expires May, 2008                    Page 4 
>   
>  Internet-Draft             Call Completion              November 2007 
>   
> 
>     contains information about caller's readiness for receiving a call 
>     or it gives up. 

s/caller's/callee's


>  it MUST include "application/call-completion". This 
>     "application/call-completion" data format is described in chapter 
>     8. 

you mean Section 10


Thanks,
Jonathan R.
-- 
Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
Cisco Fellow                                   Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen@cisco.com
http://www.jdrosen.net                         PHONE: (408) 902-3084
http://www.cisco.com

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



From bliss-bounces@ietf.org Fri Dec 07 02:58:10 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J0Y63-0005c5-85; Fri, 07 Dec 2007 02:58:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J0Y61-0005X4-Ak
	for bliss@ietf.org; Fri, 07 Dec 2007 02:58:05 -0500
Received: from agnada.com ([69.36.182.244])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J0Y60-0007Cl-Um
	for bliss@ietf.org; Fri, 07 Dec 2007 02:58:05 -0500
Received: from [192.168.1.4] (S0106001839eceb7a.vc.shawcable.net
	[24.80.240.54]) (authenticated bits=0)
	by agnada.com (8.12.11.20060308/8.12.11) with ESMTP id lB77vuN6019710
	for <bliss@ietf.org>; Fri, 7 Dec 2007 00:58:03 -0700
Message-ID: <4758FCFE.600@ntt-at.com>
Date: Thu, 06 Dec 2007 23:57:50 -0800
From: Shida Schubert <shida@ntt-at.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: bliss@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [BLISS] Meeting minutes posted
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org


The link below points to the minutes from the meeting today. Any 
corrections and comments are
appreciated.

 http://www3.ietf.org/proceedings/07dec/minutes/bliss.html

 Regards
  Shida

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



From bliss-bounces@ietf.org Fri Dec 07 09:51:33 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J0eY9-0006Fw-0u; Fri, 07 Dec 2007 09:51:33 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J0eY7-0006Fm-St
	for bliss@ietf.org; Fri, 07 Dec 2007 09:51:31 -0500
Received: from tcmail23.telekom.de ([217.6.95.237])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J0eY5-00008j-RX
	for bliss@ietf.org; Fri, 07 Dec 2007 09:51:31 -0500
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de
	[10.125.177.105]) by tcmail21.telekom.de with ESMTP;
	Fri, 7 Dec 2007 15:51:28 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Fri, 7 Dec 2007 15:51:27 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: [BLISS] comments on draft-poetzl-bliss-call-completion
Date: Fri, 7 Dec 2007 15:51:27 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C1873222029F53D3@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <47581CA7.2000705@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [BLISS] comments on draft-poetzl-bliss-call-completion
Thread-Index: Acg4IRQpmht+ww9BRM2Xk9ETPYZnGQAujKlg
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <jdrosen@cisco.com>,
    <bliss@ietf.org>
X-OriginalArrivalTime: 07 Dec 2007 14:51:27.0998 (UTC)
	FILETIME=[A577C9E0:01C838E0]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Cc: xaled@web.de
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

Hi Jonathan,

some answers inline.

BR, Martin


> -----Urspr=FCngliche Nachricht-----
> Von: Jonathan Rosenberg [mailto:jdrosen@cisco.com]=20
> Gesendet: Donnerstag, 6. Dezember 2007 17:01
> An: bliss@ietf.org
> Betreff: [BLISS] comments on draft-poetzl-bliss-call-completion
>=20
>=20
> Section 6.1:
>=20
> I think this completely understates the problem; if the=20
> caller is using=20
> dialog and the callee is using http polling it completely fails.=20
> Similarly in section 6.3. Just because a UA supports the dialog event=20
> package, doesn't mean it would know to subscribe for call completion=20
> using it.
>
Yes, that's one of the issues of using the dialog event package. It's =
not dedicated to call completion.

=20
> > Conclusion=20
> >     =20
> >     As seen on the analysis above, when dialog event=20
> package is used,=20
> >     it's only the server that needs to support call-completion, and=20
> >     with the wide implementations of the dialog event package, high=20
> >     level of interoperability can be anticipated if this=20
> approach is=20
> >     used.=20
>=20
> I don't understand this. The caller needs to clearly support call=20
> completion since there needs to be a UI for the user to=20
> invoke it, and=20
> the UA has to know to utilize dialog event package. Call=20
> completion is=20
> clearly a double-ended service in that both sides need to=20
> support some=20
> functionality beyond existing specs for it to work.
There is definitely a missing semantics in the dialog event package, =
that would indicate to the UA that it's going to be queued and notified =
only when it's at the top of the queue. We have added this because we =
heard from others that this kind of implementation based on dialog-event =
package really exists in the wild.
>From our understandings, the server with this kind of dialog-event =
implementation,  selectively sends NOTIFY with "dialog terminated" to =
the subscriber that was on the top of the queue. When this solution is =
used, a UA never knows that it is in queue, it thinks it's simply =
subscribing to a dialog-event package. The overall result of this is =
that the UAs are getting the notification with callee's availability in =
order, similar to when call-completion package is used, except for the =
UA being=20
aware of the fact that it's actually being queued. But anyway also when =
the caller does not support call completion, with the fallback to the =
dialog event package the callee has the possibility to receive the =
(redial) calls in order.



>=20
> General comments:
>=20
> The document says there is no role for state agents. But what about a=20
> user that has multiple devices. Is the assumption that there is a=20
> stateful b2bua type of element that is aware of the state of all of=20
> them, and the subscribe terminates there? That would be a=20
> state agent.=20
> Or does the SUBSCRIBE fork to all devices? This is important=20
> since we'll=20
> need to make recommendations on which elements implement the=20
> event agent=20
> side of this - phones or 'servers' in the network. I'll note this=20
> question is addressed in draft-worley-call-completion. That=20
> draft raises=20
> several issues which need to be addressed, in particular:
>=20
> 1. handling multiple UAs at caller side
> 2. handling multiple UAs at callee side
> 3. correlating the call completion call with the queue request
> 4. figuring out how to determine the availability states of user/UA
>=20
> So I believe we will need to combine these two drafts for a complete=20
> solution.
Yes, that is the plan once the work on Dale's document is finished. For =
the time we work on call completion it's easier to be able to update the =
two different documents.


>=20
>=20
>=20
>=20
> Nits:
>=20
> > this, until either the callee receives a HTTP response that=20
> >=20
> >  Poetzl                    Expires May, 2008               =20
>     Page 4=20
> >  =20
> > =0C>  Internet-Draft             Call Completion             =20
> November 2007=20
> >  =20
> >=20
> >     contains information about caller's readiness for=20
> receiving a call=20
> >     or it gives up.=20
>=20
> s/caller's/callee's
>=20
>=20
> >  it MUST include "application/call-completion". This=20
> >     "application/call-completion" data format is described=20
> in chapter=20
> >     8.=20
>=20
> you mean Section 10
Oh, of course, thank you.

>=20
>=20
> Thanks,
> Jonathan R.
> --=20
> Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
> Cisco Fellow                                   Edison, NJ 08837
> Cisco, Voice Technology Group
> jdrosen@cisco.com
> http://www.jdrosen.net                         PHONE: (408) 902-3084
> http://www.cisco.com
>=20
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
>=20

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



From bliss-bounces@ietf.org Fri Dec 07 13:13:39 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J0hhe-0006nM-3l; Fri, 07 Dec 2007 13:13:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J0hhd-0006my-0K
	for bliss@ietf.org; Fri, 07 Dec 2007 13:13:33 -0500
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J0hhc-0007KP-1e
	for bliss@ietf.org; Fri, 07 Dec 2007 13:13:32 -0500
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 07 Dec 2007 10:13:31 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254])
	by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id lB7IDVRl013568; 
	Fri, 7 Dec 2007 10:13:31 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id lB7IDLxl027923;
	Fri, 7 Dec 2007 18:13:31 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 7 Dec 2007 10:13:29 -0800
Received: from [10.21.65.194] ([10.21.65.194]) by xfe-sjc-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 7 Dec 2007 10:13:29 -0800
Message-ID: <47598D48.3020305@cisco.com>
Date: Fri, 07 Dec 2007 13:13:28 -0500
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
Subject: Re: AW: [BLISS] comments on draft-poetzl-bliss-call-completion
References: <CCA850DCD3FBE2479D5076C5C1873222029F53D3@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <CCA850DCD3FBE2479D5076C5C1873222029F53D3@S4DE9JSAAHW.ost.t-com.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 07 Dec 2007 18:13:29.0140 (UTC)
	FILETIME=[DE3B4740:01C838FC]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5437; t=1197051211;
	x=1197915211; c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=pkyzivat@cisco.com;
	z=From:=20Paul=20Kyzivat=20<pkyzivat@cisco.com>
	|Subject:=20Re=3A=20AW=3A=20[BLISS]=20comments=20on=20draft-poetzl-bliss-
	call-completion |Sender:=20;
	bh=AWffqfPjupzUl6M4lwW30Jy5/FAwMUTM4QVmijzFj7c=;
	b=FK/ARNtaexUmGsa6D3nsAwwQUj9kEvUrXjHmvND6hz6eyP9j5EZWSDiqwg91ihcmwZY46m3d
	ek7cPWFnwFl4A2YUtDa1Vrx4mEcd9Sq4VVsWqjO6+nlxwJcZgKj6HoRZ;
Authentication-Results: sj-dkim-2; header.From=pkyzivat@cisco.com; dkim=pass (
	sig from cisco.com/sjdkim2002 verified; ); 
X-Spam-Score: -4.0 (----)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: bliss@ietf.org, xaled@web.de
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

Martin,

I have no problem with using the dialog event package as a fallback for 
this feature. But only if it is a *vanilla* implementation of the dialog 
event package. If queuing is added to the dialog event package then it 
is no longer the same package. Adding the queuing semantics breaks its 
value for other purposes, and is entirely unacceptable.

	Paul

Huelsemann, Martin wrote:
> Hi Jonathan,
> 
> some answers inline.
> 
> BR, Martin
> 
> 
>> -----Ursprüngliche Nachricht-----
>> Von: Jonathan Rosenberg [mailto:jdrosen@cisco.com] 
>> Gesendet: Donnerstag, 6. Dezember 2007 17:01
>> An: bliss@ietf.org
>> Betreff: [BLISS] comments on draft-poetzl-bliss-call-completion
>>
>>
>> Section 6.1:
>>
>> I think this completely understates the problem; if the 
>> caller is using 
>> dialog and the callee is using http polling it completely fails. 
>> Similarly in section 6.3. Just because a UA supports the dialog event 
>> package, doesn't mean it would know to subscribe for call completion 
>> using it.
>>
> Yes, that's one of the issues of using the dialog event package. It's not dedicated to call completion.
> 
>  
>>> Conclusion 
>>>      
>>>     As seen on the analysis above, when dialog event 
>> package is used, 
>>>     it's only the server that needs to support call-completion, and 
>>>     with the wide implementations of the dialog event package, high 
>>>     level of interoperability can be anticipated if this 
>> approach is 
>>>     used. 
>> I don't understand this. The caller needs to clearly support call 
>> completion since there needs to be a UI for the user to 
>> invoke it, and 
>> the UA has to know to utilize dialog event package. Call 
>> completion is 
>> clearly a double-ended service in that both sides need to 
>> support some 
>> functionality beyond existing specs for it to work.
> There is definitely a missing semantics in the dialog event package, that would indicate to the UA that it's going to be queued and notified only when it's at the top of the queue. We have added this because we heard from others that this kind of implementation based on dialog-event package really exists in the wild.
>>From our understandings, the server with this kind of dialog-event implementation,  selectively sends NOTIFY with "dialog terminated" to the subscriber that was on the top of the queue. When this solution is used, a UA never knows that it is in queue, it thinks it's simply subscribing to a dialog-event package. The overall result of this is that the UAs are getting the notification with callee's availability in order, similar to when call-completion package is used, except for the UA being 
> aware of the fact that it's actually being queued. But anyway also when the caller does not support call completion, with the fallback to the dialog event package the callee has the possibility to receive the (redial) calls in order.
> 
> 
> 
>> General comments:
>>
>> The document says there is no role for state agents. But what about a 
>> user that has multiple devices. Is the assumption that there is a 
>> stateful b2bua type of element that is aware of the state of all of 
>> them, and the subscribe terminates there? That would be a 
>> state agent. 
>> Or does the SUBSCRIBE fork to all devices? This is important 
>> since we'll 
>> need to make recommendations on which elements implement the 
>> event agent 
>> side of this - phones or 'servers' in the network. I'll note this 
>> question is addressed in draft-worley-call-completion. That 
>> draft raises 
>> several issues which need to be addressed, in particular:
>>
>> 1. handling multiple UAs at caller side
>> 2. handling multiple UAs at callee side
>> 3. correlating the call completion call with the queue request
>> 4. figuring out how to determine the availability states of user/UA
>>
>> So I believe we will need to combine these two drafts for a complete 
>> solution.
> Yes, that is the plan once the work on Dale's document is finished. For the time we work on call completion it's easier to be able to update the two different documents.
> 
> 
>>
>>
>>
>> Nits:
>>
>>> this, until either the callee receives a HTTP response that 
>>>
>>>  Poetzl                    Expires May, 2008                
>>     Page 4 
>>>   
>>> >  Internet-Draft             Call Completion              
>> November 2007 
>>>   
>>>
>>>     contains information about caller's readiness for 
>> receiving a call 
>>>     or it gives up. 
>> s/caller's/callee's
>>
>>
>>>  it MUST include "application/call-completion". This 
>>>     "application/call-completion" data format is described 
>> in chapter 
>>>     8. 
>> you mean Section 10
> Oh, of course, thank you.
> 
>>
>> Thanks,
>> Jonathan R.
>> -- 
>> Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
>> Cisco Fellow                                   Edison, NJ 08837
>> Cisco, Voice Technology Group
>> jdrosen@cisco.com
>> http://www.jdrosen.net                         PHONE: (408) 902-3084
>> http://www.cisco.com
>>
>> _______________________________________________
>> BLISS mailing list
>> BLISS@ietf.org
>> https://www1.ietf.org/mailman/listinfo/bliss
>>
> 
> _______________________________________________
> BLISS mailing list
> BLISS@ietf.org
> https://www1.ietf.org/mailman/listinfo/bliss
> 

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



From bliss-bounces@ietf.org Wed Dec 12 12:05:45 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J2V1h-0002t4-H2; Wed, 12 Dec 2007 12:05:41 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J2V1g-0002so-1K
	for bliss@ietf.org; Wed, 12 Dec 2007 12:05:40 -0500
Received: from tcmail23.telekom.de ([217.6.95.237])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J2V1f-0002fB-4G
	for bliss@ietf.org; Wed, 12 Dec 2007 12:05:39 -0500
Received: from S4DE9JSAANO.ost.t-com.de (S4DE9JSAANO.ost.t-com.de
	[10.125.177.105]) by tcmail21.telekom.de with ESMTP;
	Wed, 12 Dec 2007 18:05:37 +0100
Received: from S4DE9JSAAHW.ost.t-com.de ([10.125.177.160]) by
	S4DE9JSAANO.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); 
	Wed, 12 Dec 2007 18:05:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: AW: AW: [BLISS] comments on draft-poetzl-bliss-call-completion
Date: Wed, 12 Dec 2007 18:05:36 +0100
Message-Id: <CCA850DCD3FBE2479D5076C5C1873222029F53E0@S4DE9JSAAHW.ost.t-com.de>
In-Reply-To: <47598D48.3020305@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: AW: [BLISS] comments on draft-poetzl-bliss-call-completion
Thread-Index: Acg4/OF38H28yZweTLSLB2VAMhyfbgD2KSgA
From: "Huelsemann, Martin" <Martin.Huelsemann@t-com.net>
To: <pkyzivat@cisco.com>
X-OriginalArrivalTime: 12 Dec 2007 17:05:37.0123 (UTC)
	FILETIME=[372F8B30:01C83CE1]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 86f85b2f88b0d50615aed44a7f9e33c7
Cc: bliss@ietf.org, "Alexeitsev, D" <D.Alexeitsev@t-com.net>
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

Hi Paul,

in my understanding this would be a fallback to an unchanged dialog =
event package, basing on the procedures in the services examples draft =
for an automatic redial, only with the notifications send in order.


BR, Martin




> -----Urspr=FCngliche Nachricht-----
> Von: Paul Kyzivat [mailto:pkyzivat@cisco.com]=20
> Gesendet: Freitag, 7. Dezember 2007 19:13
> An: H=FClsemann, Martin
> Cc: jdrosen@cisco.com; bliss@ietf.org; xaled@web.de
> Betreff: Re: AW: [BLISS] comments on=20
> draft-poetzl-bliss-call-completion
>=20
>=20
> Martin,
>=20
> I have no problem with using the dialog event package as a=20
> fallback for=20
> this feature. But only if it is a *vanilla* implementation of=20
> the dialog=20
> event package. If queuing is added to the dialog event=20
> package then it=20
> is no longer the same package. Adding the queuing semantics=20
> breaks its=20
> value for other purposes, and is entirely unacceptable.
>=20
> 	Paul
>=20
> Huelsemann, Martin wrote:
> > Hi Jonathan,
> >=20
> > some answers inline.
> >=20
> > BR, Martin
> >=20
> >=20
> >> -----Urspr=FCngliche Nachricht-----
> >> Von: Jonathan Rosenberg [mailto:jdrosen@cisco.com]=20
> >> Gesendet: Donnerstag, 6. Dezember 2007 17:01
> >> An: bliss@ietf.org
> >> Betreff: [BLISS] comments on draft-poetzl-bliss-call-completion
> >>
> >>
> >> Section 6.1:
> >>
> >> I think this completely understates the problem; if the=20
> >> caller is using=20
> >> dialog and the callee is using http polling it completely fails.=20
> >> Similarly in section 6.3. Just because a UA supports the=20
> dialog event=20
> >> package, doesn't mean it would know to subscribe for call=20
> completion=20
> >> using it.
> >>
> > Yes, that's one of the issues of using the dialog event=20
> package. It's not dedicated to call completion.
> >=20
> > =20
> >>> Conclusion=20
> >>>     =20
> >>>     As seen on the analysis above, when dialog event=20
> >> package is used,=20
> >>>     it's only the server that needs to support=20
> call-completion, and=20
> >>>     with the wide implementations of the dialog event=20
> package, high=20
> >>>     level of interoperability can be anticipated if this=20
> >> approach is=20
> >>>     used.=20
> >> I don't understand this. The caller needs to clearly support call=20
> >> completion since there needs to be a UI for the user to=20
> >> invoke it, and=20
> >> the UA has to know to utilize dialog event package. Call=20
> >> completion is=20
> >> clearly a double-ended service in that both sides need to=20
> >> support some=20
> >> functionality beyond existing specs for it to work.
> > There is definitely a missing semantics in the dialog event=20
> package, that would indicate to the UA that it's going to be=20
> queued and notified only when it's at the top of the queue.=20
> We have added this because we heard from others that this=20
> kind of implementation based on dialog-event package really=20
> exists in the wild.
> >>From our understandings, the server with this kind of=20
> dialog-event implementation,  selectively sends NOTIFY with=20
> "dialog terminated" to the subscriber that was on the top of=20
> the queue. When this solution is used, a UA never knows that=20
> it is in queue, it thinks it's simply subscribing to a=20
> dialog-event package. The overall result of this is that the=20
> UAs are getting the notification with callee's availability=20
> in order, similar to when call-completion package is used,=20
> except for the UA being=20
> > aware of the fact that it's actually being queued. But=20
> anyway also when the caller does not support call completion,=20
> with the fallback to the dialog event package the callee has=20
> the possibility to receive the (redial) calls in order.
> >=20
> >=20
> >=20
> >> General comments:
> >>
> >> The document says there is no role for state agents. But=20
> what about a=20
> >> user that has multiple devices. Is the assumption that there is a=20
> >> stateful b2bua type of element that is aware of the state=20
> of all of=20
> >> them, and the subscribe terminates there? That would be a=20
> >> state agent.=20
> >> Or does the SUBSCRIBE fork to all devices? This is important=20
> >> since we'll=20
> >> need to make recommendations on which elements implement the=20
> >> event agent=20
> >> side of this - phones or 'servers' in the network. I'll note this=20
> >> question is addressed in draft-worley-call-completion. That=20
> >> draft raises=20
> >> several issues which need to be addressed, in particular:
> >>
> >> 1. handling multiple UAs at caller side
> >> 2. handling multiple UAs at callee side
> >> 3. correlating the call completion call with the queue request
> >> 4. figuring out how to determine the availability states of user/UA
> >>
> >> So I believe we will need to combine these two drafts for=20
> a complete=20
> >> solution.
> > Yes, that is the plan once the work on Dale's document is=20
> finished. For the time we work on call completion it's easier=20
> to be able to update the two different documents.
> >=20
> >=20
> >>
> >>
> >>
> >> Nits:
> >>
> >>> this, until either the callee receives a HTTP response that=20
> >>>
> >>>  Poetzl                    Expires May, 2008               =20
> >>     Page 4=20
> >>>  =20
> >>> =0C> >  Internet-Draft             Call Completion             =20
> >> November 2007=20
> >>>  =20
> >>>
> >>>     contains information about caller's readiness for=20
> >> receiving a call=20
> >>>     or it gives up.=20
> >> s/caller's/callee's
> >>
> >>
> >>>  it MUST include "application/call-completion". This=20
> >>>     "application/call-completion" data format is described=20
> >> in chapter=20
> >>>     8.=20
> >> you mean Section 10
> > Oh, of course, thank you.
> >=20
> >>
> >> Thanks,
> >> Jonathan R.
> >> --=20
> >> Jonathan D. Rosenberg, Ph.D.                   499 Thornall St.
> >> Cisco Fellow                                   Edison, NJ 08837
> >> Cisco, Voice Technology Group
> >> jdrosen@cisco.com
> >> http://www.jdrosen.net                         PHONE:=20
> (408) 902-3084
> >> http://www.cisco.com
> >>
> >> _______________________________________________
> >> BLISS mailing list
> >> BLISS@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/bliss
> >>
> >=20
> > _______________________________________________
> > BLISS mailing list
> > BLISS@ietf.org
> > https://www1.ietf.org/mailman/listinfo/bliss
> >=20
>=20

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



From bliss-bounces@ietf.org Wed Dec 19 17:40:19 2007
Return-path: <bliss-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1J57aK-0006w9-9J; Wed, 19 Dec 2007 17:40:16 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1J57aJ-0006w2-Q0
	for bliss@ietf.org; Wed, 19 Dec 2007 17:40:15 -0500
Received: from py-out-1112.google.com ([64.233.166.177])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J57aH-0001pJ-M4
	for bliss@ietf.org; Wed, 19 Dec 2007 17:40:15 -0500
Received: by py-out-1112.google.com with SMTP id d32so13830010pye.12
	for <bliss@ietf.org>; Wed, 19 Dec 2007 14:40:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	bh=C0qnFWFlmcbI9J05VoiEnWeRBvMsAYRHuZE3UHUVTEk=;
	b=ZS0xZT2rO8NHlnk8UCDoWcOrJijNrPNUV1Yy7crvBAOKEyUtHIEdoupYShdyL2L+Nl4heR50y8r35jYAnxGCbxhK7C/C2U4igmqnUBstH6XlceCUioI024GdIqan8FR6xr/JO32W+K/6/WUwg16lAQHQwaBy2oaNdj4WocecaTo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=iSmw4xvzzrNv0saqjnvLcTCWqxlW6H5lu1SwLWTGu/Sj0VCR4DmPLeyIkbWN564POFXPg1fIw4Vs5jAsOAPcod38OSeG2LMYjWrIILZrQjgT1DpVc52VXgWUNapcUboyvxGUfk43WtdW+4Kg1TO5VRVuAPvUZOMPk6gIZembkws=
Received: by 10.141.43.5 with SMTP id v5mr3618730rvj.49.1198104010400;
	Wed, 19 Dec 2007 14:40:10 -0800 (PST)
Received: by 10.141.178.2 with HTTP; Wed, 19 Dec 2007 14:40:10 -0800 (PST)
Message-ID: <c164605b0712191440j7efc7b1dt6b4eb7d9cbd7244c@mail.gmail.com>
Date: Wed, 19 Dec 2007 14:40:10 -0800
From: "Jason Fischl" <jason@counterpath.com>
To: bliss@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: c3272db32e9f367a
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: 
Subject: [BLISS] Formation of design teams for Automated Handling,
	Call Queuing, Call Parking, Line Sharing
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF"
	<bliss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bliss>,
	<mailto:bliss-request@ietf.org?subject=subscribe>
Errors-To: bliss-bounces@ietf.org

At the IETF 70 meeting in Vancouver, we decided to form design teams
to help focus the working group on meeting our deliverables.  The
design teams will be meeting biweekly on an audio conference. We
expect to start the conference calls the week of January 8th, 2008.

There will initially be four design teams focused on each of our milestones.

Automated Handling: Goal is to submit a BCP in April, 2008.
Call Queing: Goal is to submit a BCP in August, 2008.
Call Parking: Goal is to submit a BCP in August, 2008.
Line Sharing: Goal is to submit a BCP in October, 2008.

Anyone that would like to contribute to any of these efforts is
invited to join the relevant design team.

Please send an email to the BLISS working group chairs if you intend
to contribute and would like to be part of the design team. Also,
please indicate your timezone and the design team(s) that you are
interested in participating in.

Regards

Jason Fischl
Shida Schubert

_______________________________________________
BLISS mailing list
BLISS@ietf.org
https://www1.ietf.org/mailman/listinfo/bliss



