Last Call Review of draft-ietf-hybi-permessage-compression-22
review-ietf-hybi-permessage-compression-22-opsdir-lc-kumari-2015-06-23-00

Request Review of draft-ietf-hybi-permessage-compression
Requested rev. no specific revision (document currently at 28)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2015-06-24
Requested 2015-06-11
Other Reviews Genart Last Call review of -22 by Dan Romascanu (diff)
Genart Telechat review of -24 by Dan Romascanu (diff)
Secdir Last Call review of -21 by Robert Sparks (diff)
Review State Completed
Reviewer Warren Kumari
Review review-ietf-hybi-permessage-compression-22-opsdir-lc-kumari-2015-06-23
Posted at http://www.ietf.org/mail-archive/web/ops-dir/current/msg01156.html
Reviewed rev. 22 (document currently at 28)
Review result Ready
Draft last updated 2015-06-23
Review completed: 2015-06-23

Review
review-ietf-hybi-permessage-compression-22-opsdir-lc-kumari-2015-06-23

Be ye not afraid.

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.

Document reviewed:  draft-ietf-hybi-permessage-compression-22

Summary: Ready, no nits, no comments.


Details:
Well, this is a first -- I have never before performed a review
without finding at least some nits (typos, grammar, etc).

Because I feel bad about not having *any* comments I'll scrape the
bottom of the barrel -- I find the use of underscores jarring in e.g:
'This document references the procedure to _Fail the WebSocket
Connection_. ' and think these could be replaced with quotes instead.
I'll fully admit this is bikeshedding.

Oh, the title on Section 8 also looks a little odd, was the 'p'
intended to be uppercase? Could go either way...

There are no operational impacts that I can see, other than less
traffic on the wire, and more code in network devices if any of them
are websocket servers or clients (e.g for management).


W


-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf