Linda, (think you for trimming.)
On 2/26/14, 11:17 AM, Linda Dunbar wrote:
Joel,
--- Joel Halpern wrote ---
> 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.
[Linda] I meant to ask "at the very beginning, where does the I2RS
clients get the information on which I2RS agent to register for
notification"? Is it by some management entity? If yes, then when the
I2RS agent restarts, the I2RS agent should send a notification to
this "management entity", instead depending on the I2RS agent's
non-volatile DB. It is possible during the time that this I2RS agent
is down, the client is reassigned to a different agent.
I2RS Clients locate I2RS agents by many means. We are not mandating
them. For example, an I2RS agent may start by using local means to find
its local router. It can then use I2RS mechanisms to get the topology.
Based on that, and the service it wants to provide, it can then select
which I2RS agents to register with and what events to register for. But
that is only one example. It may be that some other entity (a PCE for
example) provides the needed topology information. Or any number of
other deployment models. The I2RS Agent failure notification mechanism
ought not be dependent upon the I2RS client deployment and management
strategy.
Yours,
Joel
Linda
_______________________________________________
i2rs mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/i2rs
