Last Call Review of draft-ietf-tsvwg-ieee-802-11-09
review-ietf-tsvwg-ieee-802-11-09-opsdir-lc-banks-2017-10-10-00

Request Review of draft-ietf-tsvwg-ieee-802-11
Requested rev. no specific revision
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2017-10-09
Requested 2017-09-25
Other Reviews Genart Last Call review of -09 by Roni Even
Review State Completed
Reviewer Sarah Banks
Review review-ietf-tsvwg-ieee-802-11-09-opsdir-lc-banks-2017-10-10
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/gF2fEP0ei8AZ2Ks7BH1ddZKXQFA
Reviewed rev. 09
Review result Ready
Draft last updated 2017-10-10
Review closed: 2017-10-10

Review
review-ietf-tsvwg-ieee-802-11-09-opsdir-lc-banks-2017-10-10

I have reviewed this document as part of the Operational directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments.

Status: Ready

Overall, this is a well written document, explaining the problem, discussing the concerns, and makes proposals. As a reader, I appreciated the discussion around the IEEE/IETF issues, for lack of a better term, and the discussion around the existing RFCs, leading to a clear explanation of the task at hand, even though it's pretty lengthy. Kudos to the authors (or WG?) for considering an applicability statement. Extra kudos to the authors for Section 1.4 (I might have to steal this idea too). Overall, I thought it was clear, reads well, and is ready to go.

A small note; nits is not clean, and I'd like to see us get into a habit of sending clean nits drafts into the queue. Please resolve your open nits issues.

Thanks
Sarah