Subject: Re: [dispatch] dispatch Digest, Vol 11, Issue 40

From: zhipeng zhou <[email-masked]>
Date: Wed, 24 Feb 2010 10:09:18 +0800

Hi Sal,
Thanks for your response.
While my question is what the difference for the far end device on whether
it hold single or muliple sessions with the other devices.
I mean, if the far end device hold several seperate sessions with the
household devices, for the user it is also available to get the integrated
experience by the support of the client.
For the communication itself, what profit can be got your proposal. The far
end device can maitain several sessions simultaneously.
Thanks.
Zhipeng

////////////////////////////////////////////////////////////////////////////
//////////////////////////////
Message: 4
Date: Tue, 23 Feb 2010 16:18:14 +0200
From: Salvatore Loreto <[email-masked]>
Subject: Re: [dispatch] A question	on
	"draft-loreto-dispatch-disaggregated-media-01"
To: [email-masked]
Message-ID: <[email-masked]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

Hi Zhipeng,

thanks for the question.

The advantage of the proposed solution is that the user does not need a 
device that is able to act as a controller:

indeed the proposed solution give the possibility for a user to create a 
multimedia session combining different media streams,
coming from different devices under his/her control (where none of those 
devices can act as a controller
for the other devices in the call), so that they are treated by the far 
end of the session as a single media session.

cheers
/Sal

On 02/21/2010 04:44 AM, zhipeng zhou wrote:
> Hi Salvatore and Gonzalo:
> After reading your newly uploaded 
> "draft-loreto-dispatch-disaggregated-media-01", esp. your section 4,
> I have a question as following :
> Since Bob's device will communicate with Alice's three devices, three 
> channels or sessions will be available to implement this scenario.
> While the sentece in this document "Since this type of scenario is not 
> covered by existing mechanisms, we
>    propose to initiate work on SIP extensions to support it." shows 
> that you like to implement this scenario through a new way.
> So, may you pls give a rough diagram and  indicate the advantage of 
> your proposed new solution.
> Thanks.
> Zhipeng
>
> -----------------------------------------------------
>
> Huawei Software Technologies Co.,Ltd.
>
> Floor 2, Building A, NO.48,Ning Nan AV., Nanjing , P.R.of China
> Zipcode:210012
> E-Mail: [email-masked] <mailto:[email-masked]>
> Phone:(+86) 25-82276771
> Fax:(+86) 25-82276760
>
> Mobile:(+86) 13404162849
> -----------------------------------------------------
>
>
****************************************************************************
***********************************
> ??????????????????,??????????????????????????????????
>
> (?????????????????????)????????
>
> ?????????,????????????? ???????!
>
****************************************************************************
***********************************
****************************************************************************
***********************************
> This e-mail and its attachments contain confidential information from 
> HUAWEI, which is intended only for the
>
> person or entity whose address is listed above. Any use of the 
> information contained herein in any way(including,
>
> but not limited to, total or partial disclosure, reproduction, or 
> dissemination) by persons other than the intended
>
> recipient(s) is prohibited.
>
> If you receive this e-mail in error, please notify the sender by phone 
> or email immediately and delete it!
>
****************************************************************************
***********************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.ietf.org/mail-archive/web/dispatch/attachments/20100223/2f8a06ce
/attachment.htm>

------------------------------

_______________________________________________
dispatch mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/dispatch

End of dispatch Digest, Vol 11, Issue 40
****************************************