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. Scott
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
