[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Simple] comments on draft-ietf-simple-view-sharing-00
inline:
Robert Sparks wrote:
On Jul 8, 2008, at 10:10 PM, Jonathan Rosenberg wrote:
I am sorry it took so long to respond here. Thanks for your comments.
Responses below:
Michael Froman wrote:
Hello,
I have a few comments about draft-ietf-simple-view-sharing-00. I
haven't seen any of this on-list (maybe I've missed it) so please
excuse me if you've already discussed this.
--- #1 concern ---
Sec. 4.2 What if (like in RLS using xcap) the information used to
construct the ACL is not nearby? There appears to be no mode of
responding with "I'm working on it and I'll let you know." The
phrase that specifically concerns me is "Furthermore, the initial
state sent by the presence agent MUST include an ACL document."
This is a current problem in 4662 when used with xcap, and it would
be nice to avoid creating a similar problem in this spec.
I don't understand the problem. The presence server would just wait to
send the NOTIFY until it had the state.
3265 immediate notifies.
What do you send when its really time to kick that immediate NOTIFY out
and the information you need for that ACL isn't there yet?
Is this a real problem? "Immediate" NOTIFY doesn't have a requirement
around a specific time; it seems reasonable to wait for whatever backend
DB operations are required before you send a NOTIFY. You need to do that
anyway to figure out what presence document to send them.
Would it be OK just to send an empty NOTIFY and then push this stuff
out, as you say, when the presence server gets the state?
I do think its OK; but I still don't understand the problem.
-Jonathan R.
--
Jonathan D. Rosenberg, Ph.D. 499 Thornall St.
Cisco Fellow Edison, NJ 08837
Cisco, Voice Technology Group
jdrosen at cisco.com
http://www.jdrosen.net PHONE: (408) 902-3084
http://www.cisco.com
_______________________________________________
Simple mailing list
Simple at ietf.org
https://www.ietf.org/mailman/listinfo/simple