I agree with Tom. This work does not seem to applicable to I2RS WG.
At best, it is related to L2VPN WG, now, PALS and BESS.
And in addition, there are other SDOs that are working on this as well.
It would be difficult to unwind the overlap.
/himanshu
-Original Message-
From: i2rs
1:30 PM
To: Russ White
Cc: Joel M. Halpern; i2rs@ietf.org; Shah, Himanshu
Subject: Re: [i2rs] question on I2RS architecture
This is an aspect of the unexpected interactions problem. There's text in the
architecture saying that these can happen. This was offered for discussion on
the list
, then your point stands, but
that is not what I was discussing.
/himanshu
-Original Message-
From: sriganeshk...@gmail.com [mailto:sriganeshk...@gmail.com] On Behalf Of
Sriganesh Kini
Sent: Wednesday, November 06, 2013 3:43 PM
To: Shah, Himanshu
Cc: Alia Atlas; Russ White; i2rs@ietf.org; Joel
At the IETF I2RS interim meeting, I raised the concern about conflicting set
operations by I2RS clients to different I2RS agents,
Which may end up causing micro-loop or far-side loop.
Is this addressed in the architecture?
May be this is responsibility of network orchestrator.
If it is not
