Subject: [Sipping] Ad-Hoc URI lists

From: Gonzalo Camarillo <[email-masked]>
Date: Sat, 27 Mar 2004 20:04:41 +0200

Folks,

during the IETF meeting, we received a lot of feedback on the exploders 
drafts. We have been working with several people to address their 
concerns. These three drafts include all the feedback we have received 
so far. Until they appear in the archives, they can be fetched from:

http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-uri-list-02.txt
http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-adhoc-conferencing-00.txt
http://standards.ericsson.net/gonzalo/papers/draft-camarillo-sipping-adhoc-simple-00.txt

The first draft specifies how to carry a URI list in a SIP message. The 
other two drafts describe what it means to have a URI list in an INVITE 
(a conference) and in a subscribe (a resource list). These two drafts 
reference the existing conference framework and resource list documents, 
so, they do not define any normative behavior besides providing the 
server with the list. Once the server gets the list, everything looks 
and feels like a regular conference or like a regular subscription to a 
resource list.

Comments are welcome.

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 [email-masked] for questions on current sip
Use [email-masked] for new developments of core SIP