[Sipping] Conferencing for UAs

[Gonzalo Camarillo <[e-mail]>]

Hello,

some comments on the following draft:
http://www.ietf.org/internet-drafts/draft-ietf-sipping-cc-conferencing-03.txt

The focus of a conference returns the conference URI in the contact 
header field of the 200 OK for the INVITE. The UAC uses this URI to 
SUBSCRIBE to the conf package (using a new dialog)...

Why are we forcing the focus to use the same URI for receiving the 
INVITEs from all the users and for receiving the SUBSCRIBEs? I believe 
the solution would be cleaner if we defined a new header field (e.g., 
Associated-Conf-State) that carried a globally routable URI. The 200 OK 
for the initial INVITE (or the INVITE in a dial-out case) would carry 
this header field. This would keep separate the URI used for joining the 
conference and the URI used for subscribing to the state of the conference.

This is actually the approach that the draft below follows:
http://www.ietf.org/internet-drafts/draft-camarillo-sipping-transac-package-00.txt

We define the Associated-Transactions-State to be returned, for example, 
in the 200 OK of a MESSAGE sent to an exploder. Note that we had to 
create this new header because MESSAGE does not carry a Contact 
header... following the same approach in both, the conferencing work and 
the exploders work would be good, in my opinion.

Comments?

Thanks,

Gonzalo


This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP