Linda, I am not following your answer to Scott's question. Further in line.
On 2/26/14, 9:38 AM, Linda Dunbar wrote:
Questions inserted below: *From:*Scott Brim [mailto:[email protected]] *Sent:* Wednesday, February 26, 2014 4:17 AM *To:* Linda Dunbar *Cc:* [email protected]; [email protected]; [email protected] *Subject:* Re: [i2rs] Comments to draft-ietf-i2rs-architecture-02.txt On Feb 25, 2014 7:56 PM, "Linda Dunbar" <[email protected] <mailto:[email protected]>> wrote: > - Section 6.2.1 (I2RS Agent Failure) > > o Unexpected failure: it is very likely under the “unexpected failure” that the I2RS agent loses its records of clients. A more reasonable way is for I2RS agent to broadcast its status (e.g. restart), to let the Clients to re-subscribe if they need to. The problem is: who should an agent broadcast its failure to? How does it know where the active clients are for particular services? There are some security concerns here. If non-volatile memory is not good enough, then a policy server could be used as a knowledgeable intermediary (many of your comments imply capabilities in policy servers), but that just pushes the problem around, it doesn't make it go away. [Linda] How does the client initially found the I2RS agent and establish the connection? Is it by management intervention? Clients can use the same approach. If it is by management intervention, the I2RS agent can simply report the “restart status” to the “system” that associates clients with I2RS agents.
I2RS clients do not find I2RS Agents. I2RS Agents are contacted by I2RS Clients. The closest they come to "finding" is if the I2RS Agent registers for notifications, then the I2RS Client will later send that I2RS Agent notifications. But that is dynamic information created by the I2RS Agent.
So the I2RS Agent has no means to broadcast the restart to all I2RS Clients. Unless of course it has persistent storage of I2RS state. In which case it would not need to broadcast the information.
Yours, Joel
Scott _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
