Barry Leiba has entered the following ballot position for draft-ietf-bess-nsh-bgp-control-plane-13: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-bess-nsh-bgp-control-plane/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- — Section 1.2 — o Service Function Overlay Network. The logical network comprised of Classifiers, SFFs, and SFIs that are connected by paths or tunnels through underlay transport networks. You use “comprises” correctly four other times in the document, but this one is incorrect: “comprised of” should instead be either “comprising” or “composed of”. I only bother mentioning it because it’s right the four other times. — Section 3.1 — The Service Function Type identifies the functions/features of service function can offer, e.g., classifier, firewall, load balancer, etc. Should this be “a service function”, rather than “of service function”? And a nit: you don’t need both “e.g.” and “etc.” together: either one will do on its own. — Section 3.2.1 — o The errors listed above are treated as follows: 1., 2., 6., 7.: The attribute MUST be treated as malformed and the "treat-as-withdraw" approach used as per [RFC7606]. 3.: Unknown TLVs SHOULD be ignored, and message processing SHOULD continue. 4.: Treated as a malformed message and the "treat-as-withdraw" approach used as per [RFC7606] Why is 4 not included in the 1,2,6,7 group? It seems odd to separate it and not to make it “MUST”, like the others. — Section 9 — Service Function Chaining provides a significant attack opportunity: packets can be diverted from their normal paths through the network, can be made to execute unexpected functions, and the functions that are instantiated in software can be subverted. The second item in the list appears to lack a subject: <what?> can be made to execute unexpected functions. _______________________________________________ BESS mailing list [email protected] https://www.ietf.org/mailman/listinfo/bess
