[bfcpbis] AD evaluation: draft-ietf-bfcpbis-sdp-ws-uri-06

[Alissa Cooper <[e-mail]>]

I have reviewed this document in preparation for IETF last call. I have a couple of comments to discuss before issuing the last call. I’ve also included some nits below that should be resolved together this IETF LC comments.

Substantive comments:

= Section 1 =

"In most cases it is not viable for certificates signed by well known
   authorities."

I don't understand what this sentence means.

= Section 5 =

"If there are
   multiple records returned for the connection URI in the "a=wss-uri"
   or "a=ws-uri" then the clients MAY use procedures in Section 4 of
   [RFC6555] to attempt the connection towards the server."

I'm confused about this. Why would there be multiple URIs? This isn't explained anywhere in the document. (Furthermore, I don't understand the comment from Dan Wing that was the origin of this text, I think. I thought the point of all of this work is to take advantage of the underlying WebSocket to send BFCP messages, so wouldn't DNS resolution be handled by the HTTP stack on the client?)

= Section 6 =

"Consequently, it is strongly
RECOMMENDED that integrity protection be applied to the SDP session
descriptions. For session descriptions carried in SIP [RFC3261], S/
MIME is the natural choice to provide such end-to-end integrity
protection."

Is this just suggesting S/MIME to have nice words in the text, or do you expect to see implementations using S/MIME to protect their SDP bodies?


Nits:

= Section 1 =

OLD
As defined in Section 3 of [RFC2818], when using Secure WebSockets
   the Canonical Name (CNAME) of the Secure Sockets Layer (SSL)
   [RFC6101] certificate MUST match the WebSocket connection URI host.

NEW
When using Secure WebSockets
   the Canonical Name (CNAME) of the Secure Sockets Layer (SSL)
   [RFC6101] certificate MUST match the WebSocket connection URI host (see Section 3 of [RFC2818]).
   
= Section 5 =

s/on Internet/on the Internet/   

s/ports (80 or 443)/port (80 or 443)/

= Section 6 =

s/it is strongly RECOMMENDED/it is RECOMMENDED/