[bfcpbis] Spencer Dawkins' Yes on draft-ietf-bfcpbis-bfcp-websocket-13: (with COMMENT)

["Spencer Dawkins" <[e-mail]>]

Spencer Dawkins has entered the following ballot position for
draft-ietf-bfcpbis-bfcp-websocket-13: Yes

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-bfcpbis-bfcp-websocket/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I have a couple of questions on authentication in this draft.

Does this text,

      Since the WebSocket API does not distinguish between certificate
      errors and other kinds of failure to establish a connection, it
is
      expected that browser vendors will warn end users directly of any
      kind of problem with the server certificate.

apply to any WebSocket-based application?

In this text,

   A floor control server that receives a message over TCP/WS can
   request the use of TCP/WSS by generating an Error message, as
   described in Section 13.8 of [I-D.ietf-bfcpbis-rfc4582bis], with an
   Error code with a value of 9 (use TLS).

is "request" the right word? Or is "require" more accurate, if the server
isn't going to establish a TCP/WS connection?