Hi Andy, >> Start small and grow up, don't start big and try to fill out the details >> --IMHO. > > This is an important point. > Do you want a framework that is filled in by vendors > (and possibly SDOs) that may be different on each platform, > or do you want a common API that provides basic functionality > that all vendors must implement? Or both?
FWIW it seems neither to me. If I2RS interface is to become significant in the industry it must support most common applications which are required by actual operators - both for WAN, MAN, LAN, access and DCs. If it will lack basic primitives which folks expect it to have I am afraid it's use will be limited to bits and pieces demos at various conferences and NOGs which I think is not what I2RG WG is aiming for. So the approach to go by use cases seems wise provided all interested parties will or can submit their use cases. Especially "can" is important here as number of operators are at the design or development phase of number of new services which are competitive and can not be shared in public. With that one could observe that OF does offer much lower level of interface to data plane and could be used or worked on without exposing your future services. That's why I have started this thread asking for RIB interface definition to be able to sense if what is currently on the table has potential of being useful for projects I am involved with or not. Best, R. _______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
