Re: [sipcore] About RFC3911(Join header)'s potential error:

I'd like to emphasize that I also think there should be no 
conference/mixing resources for the showed use case, as I said in the 
previous mail.

But I think what we said was not defined clearly in the RFC3911. And I 
also think it is hardly to do any deduction to get the rules we discussed.

So, it is not a question like "how should it be?", but a question like 
"where is it defined".

Thanks,

Gao

===================================
 Zip    : 210012
 Tel    : 87211
 Tel2   :(+86)-025-52877211
 e_mail : gao.yang2@zte.com.cn
===================================

"Worley, Dale R (Dale)" <dworley@avaya.com> 
发件人:  sipcore-bounces@ietf.org
2010-10-01 04:23

收件人
Paul Kyzivat <pkyzivat@cisco.com>, "gao.yang2@zte.com.cn" 
<gao.yang2@zte.com.cn>
抄送
"sipcore@ietf.org" <sipcore@ietf.org>
主题
Re: [sipcore] About RFC3911(Join header)'s potential error:

________________________________________
From: sipcore-bounces@ietf.org [sipcore-bounces@ietf.org] On Behalf Of 
Paul Kyzivat [pkyzivat@cisco.com]

I think the works you are concerned about already are consistent with
the scenario you raise. Specifically,

> and assign any mixing or conferencing resources necessary to complete 
the join

includes the case where no mixing or conferencing resources are necessary.
_______________________________________________

I think that Paul is correct here.  If two dialogs go to a server and are 
joined at the server, and both dialogs are sendonly at the server, then 
"mixing" is very simple: the one source (generated by the server) is 
duplicated as RTP to each dialog's remote end.

In practice, one might say that this "does not allocate mixing resources". 
 OTOH, for some implementations, this duplication of the media stream may 
require the allocation of a mixing resource, if no other component of the 
server can perform the duplication.

I do not see this as a problem that needs to be solved.

Dale
_______________________________________________
sipcore mailing list
sipcore@ietf.org
https://www.ietf.org/mailman/listinfo/sipcore

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.