Hello, I read through the draft sip-subnot-etags-00 and I found several issues that needs to be clarified.
1. typo in introduction In sentence "Typically, a SUBSCRIBE request is issued whenever a subscription is installed, periodically refreshed or terminated." shall be probably "NOTIFY". 2. some kind of misleading in text when talking about SIP PUBLISH message as an example of entity tags usage. When talking about PUBLISH I think, there is slightly different usage scenario. In response to initial PUBLISH message, server generates entity tag. Client is mandated to use this entity tag if she wants to change state of that particular presence source. If this entity tag is not used, PUBLISH message installs new presence source and not overwrites the former state. For purposes of presence notifications, these publications are then composed. This usage is a bit different that supposed for SUBSCRIBE messages, The text evokes feeling of something different. 3. What is exactly meant with "Meta-information-check"? What is this meta information. 4. Besides RLS subscriptions there is one more problem, the subscriptions to changes in documents. So extend the problem also on notification about changes in multiple documents. 5. In my mind, there popped up an idea to move the SIP-Etag into the response to SUBSCRIBE message. This way client can be informed about the entity tag also without sending the NOTIFY message at all. Have you considered this possibility? 6. What about situation when e.g. presentity has no presence document installed and some body subscribes her. The the notifier sends empty document, wouldn't be there some special handling? E.g. no entity tag. br, Martin +-------------------------------------+ Martin Hynar Software Specialist TietoEnator Czech Software Center Phone: +420 597 459 713 Mobile: +420 724 432 817 E-mail: [EMAIL PROTECTED] Vystavni 292/13 CZ-709 16 Ostrava www.tietoenator.com Please note: The information contained in this message may be legally privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized use, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank You.
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
