Last Call Review of draft-ietf-bmwg-sdn-controller-benchmark-term-07

Request Review of draft-ietf-bmwg-sdn-controller-benchmark-term
Requested rev. no specific revision (document currently at 10)
Type Last Call Review
Team Routing Area Directorate (rtgdir)
Deadline 2018-02-02
Requested 2018-01-19
Requested by Alvaro Retana
Authors Bhuvaneswaran Vengainathan, Anton Basil, Mark Tassinari, Vishwas Manral, Sarah Banks
Draft last updated 2018-02-02
Completed reviews Rtgdir Last Call review of -07 by Ines Robles (diff)
Opsdir Last Call review of -07 by Ron Bonica (diff)
Genart Last Call review of -07 by Stewart Bryant (diff)
Secdir Last Call review of -07 by Paul Hoffman (diff)
Opsdir Telechat review of -09 by Ron Bonica (diff)
Genart Telechat review of -09 by Stewart Bryant (diff)
Assignment Reviewer Ines Robles
State Completed
Review review-ietf-bmwg-sdn-controller-benchmark-term-07-rtgdir-lc-robles-2018-02-02
Reviewed rev. 07 (document currently at 10)
Review result Has Nits
Review completed: 2018-02-02



I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related drafts as they pass through IETF last call and IESG review,
and sometimes on special request. The purpose of the review is to provide assistance to the Routing ADs.
For more information about the Routing Directorate, please see ‚Äč

Although these comments are primarily for the use of the Routing ADs, it would be helpful if you could consider them along with any other IETF Last Call comments
 that you receive, and strive to resolve them through discussion or by updating the draft.

Document: draft-ietf-bmwg-sdn-controller-benchmark-term-07
Reviewer: Ines Robles
Review Date: 02-02-2018
Intended status: Informational

I have some minor concerns about this document that I think should be resolved before publication.


I believe the draft is technically good. This document is well written and clear to understand. The figures are clear and helpful.

Major Issues:

No major issues found.

Minor Issues:

-There is a definition of Northbound Interface (NI) in section 2.1.2, but there is no a definition for Southbound Interface(SI).
A definition for SI, was available in the version 00 of this document [1], but deleted in further versions.
There is a reason for that?
I think it would be nice to have a definition for SI, or a pointer to one such as for NI.

- In section 2.1.2 in the Discussion, where it states: "...and orchestration systems to program...",
I think it would be nice to add an example, "...and orchestration systems such as [add example here] to program..."

- In section 2.1.8 you mention Cluster/Redundancy Mode.
  Does it include a "Distributed Controller" mode/function, like e.g. mentioned in [2]?

- Section in the Definition paragraph: "...(number of nodes, links and hosts)..." it seems to me like the hosts are not considered nodes in here?.
Is that correct?


Section 2.1.2: is same Service... => is same as the Service...
Section in the Definition paragraph: "at it Southbound..." => "at its Southbound..."
Section in the Definition paragraph: "at it Southbound..." => "at its Southbound..."
Section 4: The test coverage table
  -In the column 1, file 1: there is an empty space, maybe it would be nice to add a description for that column like "Stage" or something like that. What do you think?
  -In the Speed column, in the Setup stage: 1- Network Topology Discovery => Network Topology Discovery time.
  -In the Reliability column, in the Operational stage: 2- Exception Handling Detection Time => Exception Handling

Thanks for this document,

Best Regards,