The comments below are from me as an individual contributor. I have read the latest revision of this document. I still do not have a clear idea of what it is solving, TBH. It doesn’t define a new protocol, yet it makes claims about an architecture that implies a protocol between devices, a controller, and applications (see the figure in section 2). In Section 3.2, iFIT is referenced as having an ability to cache or send accumulated data. I don’t see how a framework can do this. Nor do I see how a framework can dynamically load new data probes as mentioned in Section 3.3. If this were a controller with an application architecture and specifications for component interoperability, perhaps, but I do not see that in this document.
In Section4, the document mentions a closed-loop for iFIT applications whereby applications can manage iFIT closed loops on top of a controller. But again, I don’t see how. Do the applications make API calls? What calls do they make? What makes it an “iFIT closed loop”? Ultimately, the summary says that iFIT combines algorithmic and architectural schemes into the framework, but I don’t see where that is done in a specific, implementable way (e.g., in Section 3.1.2 you begin to describe how you can adaptively sample packets, but you talk about abstract signals to/from the controller). Nor do I see how one would implement iFIT. When I read the iFIT draft, I feel like I’m missing a normative chunk that explains how the various pieces of this framework are to interact in a well-specified manner. It seems to me that perhaps a more useful document is one that focus on the implementation of PBT and/or IOAM, operational experiences, best practices, etc. Joe On Oct 21, 2019, at 14:34, Haoyu Song <[email protected]<mailto:[email protected]>> wrote: Dear OPSAWG chairs, The following draft has been extensively discussed and gone through six revisions. Network operators confirmed it is useful. We believe the draft is mature enough to be adopted by the WG therefore we request the chairs to initiate the adoption call for this draft. Thank you very much for the consideration! https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/ Best regards, Haoyu
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
