Telechat Review of draft-ietf-bmwg-sdn-controller-benchmark-meth-08
review-ietf-bmwg-sdn-controller-benchmark-meth-08-genart-telechat-bryant-2018-04-16-00
| Request | Review of | draft-ietf-bmwg-sdn-controller-benchmark-meth |
|---|---|---|
| Requested revision | No specific revision (document currently at 09) | |
| Type | Telechat Review | |
| Team | General Area Review Team (Gen-ART) (genart) | |
| Deadline | 2018-04-17 | |
| Requested | 2018-02-27 | |
| Authors | Bhuvaneswaran Vengainathan , Anton Basil , Mark Tassinari , Vishwas Manral , Sarah Banks | |
| Draft last updated | 2018-04-16 | |
| Completed reviews |
Rtgdir Last Call review of -07
by
Henning Rogge
(diff)
Opsdir Last Call review of -07 by Scott O. Bradner (diff) Genart Last Call review of -07 by Stewart Bryant (diff) Secdir Last Call review of -07 by Russ Housley (diff) Genart Telechat review of -08 by Stewart Bryant (diff) |
|
| Assignment | Reviewer | Stewart Bryant |
| State | Completed | |
| Review |
review-ietf-bmwg-sdn-controller-benchmark-meth-08-genart-telechat-bryant-2018-04-16
|
|
| Reviewed revision | 08 (document currently at 09) | |
| Result | Ready with Nits | |
| Completed | 2018-04-16 |
review-ietf-bmwg-sdn-controller-benchmark-meth-08-genart-telechat-bryant-2018-04-16-00
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team (Gen-ART) reviews all IETF documents being processed by the IESG for the IETF Chair. Please wait for direction from your document shepherd or AD before posting a new version of the draft. For more information, please see the FAQ at <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. Document: draft-ietf-bmwg-sdn-controller-benchmark-meth-08 Reviewer: Stewart Bryant Review Date: 2018-04-16 IETF LC End Date: 2018-02-02 IESG Telechat date: 2018-04-19 Summary: This is a well written comprehensive test set for SDN controllers. Two minor points remain from my previous review that I would draft to the attention of the responsible AD. Major issues: None Minor issues: I found the large amount of text on Openflow that appears out of the blue in the appendix somewhat strange since the test suit is controller protocol agnostic. I understand that this is included by way of illustrative example. It might be useful to the reader to make a statement to this effect. Nits/editorial comments: The test traffic generators TP1 and TP2 SHOULD be connected to the first and the last leaf Network Device. SB> I am sure I know what does first and last mean, but the meaning should be called out.