Alissa Cooper's Discuss on draft-ietf-bmwg-vswitch-opnfv-03: (with DISCUSS and COMMENT)
Alissa Cooper <[email protected]>
| Newsgroups | gmane.ietf.bmwg |
|---|---|
| Message-ID | <[email protected]> |
Alissa Cooper has entered the following ballot position for draft-ietf-bmwg-vswitch-opnfv-03: Discuss 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-bmwg-vswitch-opnfv/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Picking up on the thread that started with the Gen-ART review, I'm not clear on the position of this document when it comes to repeatability. If all of the parameters listed in Section 3.3 (assuming they apply) are configured and documented, is it assumed that the benchmarks will be repeatable and comparable with hardware implementation benchmarks? Or is the position of the document that the benchmarks are not likely to be repeatable/comparable in some (many?) cases, given the increase in complexity? Or that more work needs to be done (outside the specification process) to achieve repeatability? I think this needs to be more clear in the document. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I understand the debate about the publication of this document as an IETF consensus RFC. To me it seems valuable to publish and that this item is within the WG's charter. I think adding the updates necessary to make the document up-to-date with the Danube 3.0 release as suggested in the thread with Alvaro would be valuable.