1. Summary The document shepherd is Evangelos Haleplidis The responsible Area Director is Alia Atlas The document describes extending the ForCES LFB topology across FEs i.e inter-FE connectivity without needing any changes to the ForCES specification by defining the Inter-FE LFB. The Inter-FE LFB provides ability to pass data, metadata and exceptions across FEs. The document describes a generic way to transport the mentioned details but focuses on ethernet transport. 2. Review and Consensus The document is straightforward, and there was no difficulty in coming to consensus on all points described. There were discussion between a couple of members of the working group, but all issues have been addressed prior to this document being accepted as a working group document. At least one implementation has validated the features described in the document. There were no issues reported during the last call and therefore we believe the working group is solidly behind this document. 3. Intellectual Property The authors have confirmed conformance with BCP 78/79. There are no IPR disclosures on the document. 4. Other Points a) There is a error nit from idnits: ** Downref: Normative reference to an Informational RFC: RFC 3746 b) There a number of spelling errors. Please use https://tools.ietf.org/tools/idspell/webservice to fix. For example: 1. "focusses" -> "focuses" 2. "ethernet" -> "Ethernet" 3. "metadatum" -> "Metadatum" 4. "learnt" -> "learned" 5. "Higig" -> "HiGig" c) There are a couple of editorial issues: 1. End of Page 3: "Details on how a graph of LFB class instances can be created can be derived by the..." Please fix the: can be created can be derived" 2. Page 6: "as well egress ports." -> "as well as egress ports." (same issue in page 9) 3. Page 7: "Each Network function." -> "Each Network Function." 4. Page 8: "The setup in Figure 3 can be split out across 3 FEs instead as demonstrated in Figure 4" -> "instead of" 5. Page 11: "This includes what of the of the original metadata" double "of the" 6. Page 24 - Last sentence "control. this" -> "control. This" d) Would it make sense to use the newer version of the model (1.1)? e) You need to change the IANA metadata ID request from "0x00000010" to "0x00000011". 0x00000010 has already been registered by RFC 7409. f) In the XML, you have set the LFB class ID to 6612, but in the IANA request, you have requested the reservation of class ID 6112. Please select one.