The only substantial problem that I found in my previous review of -02 revision of this draft, namely the top-level container being mandatory, has been addressed. Therefore, from the YANG point of view the ietf-flexe module is ready to be published. **** General comments Not being a native speaker, I usually leave English language issues to the RFC Editor. However, some formulations in this I-D make the document difficult to read and comprehend. Several cases are pointed out below but I would strongly recommend a language and stylistic review of the entire document. **** Specific comments ***** Section 1 - The sentence starting with “It supports …” makes no sense to me. ***** Section 1.2 - In the first sentence, “can be” should be replaced with “is” (as it actually was in revision -02). - The explanation of tree diagram conventions should be removed, the reference to RFC 8340 suffices. ***** Section 4 - /flexe/flexe-clients/flexe-client: What is the difference between client-num and client-index? This could be explained in the descriptions. - /flexe/flexe-groups/flexe-group/port-name: I suspect that the interface this leafref refers to has to exist for the configuration to be valid, so the type should probably be restricted with require-instance true; - /flexe/flexe-clients/flexe-client/group-index /flexe/flexe-clients/flexe-client/timeslot-lists/timeslot-list/port-name The “flexe:” prefixes in path expressions are unnecessary, so I'd suggest to remove them in order to make the paths shorter and easier to follow.