Robert, On Mon, Jun 09, 2014 at 05:19:48PM +0200, Robert Raszuk wrote: > Hi Jeff, > > Late but still few comments on the draft-ietf-i2rs-architecture-03:
Thanks for the review! > 1. > > This I2RS architecture recognizes that the routing > > system and a router???s OS provide useful mechanisms > > that applications could harness to accomplish > > application-level goals. > > What happens if multiple applications have mutually exclusive needs ? > It is not really an error as applications and clients by design are > independent. Where is the arbitration to take place ? In I2RS Client, > in I2RS Agent or in global router's RIB ? You should find this addressed in section 7.8. > 2. > Fundamental question ... > > Is the I2RS protocol communication to take place in-band, out-of-band > or both of the data plane ? If we are including in-band I presume > there is serious risk that the information carried within the protocol > may cause in-band channels to stop working hence the device becomes > unreachable (at least for the I2RS system). > > It may be good for architecture document to be able to comment on it. This seemed like one of those sort of things that were too obvious to state, but perhaps it's worth stating it. Authors, would you consider a few sentences in section 7 to cover this point? > 3. > > Anticipated I2RS Services > > Is OEM hidden within the "Dynamic Data & Statistics" or is it just > plain missing ? ;) The usual derivation of: Architecture -> Models + Protocol -> XXX -> Profit! is left as an exercise to the implementor. -- Jeff _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
