Original text:
4.5. <del> In contrast to segmented delivery, several applications use UDP or unreliable SCTP to deliver RTP or raw TS-formatted video. </del>  Under congestion and loss, this approach generally experiences more video artifacts with fewer delay or head-of-line blocking effects. applications like videoconferencing, or for other live-action video with interactive components, such as some sporting events. <del> Congestion avoidance strategies for this kind of deployment vary widely in practice, ranging from some streams that are entirely unresponsive to using feedback signaling to change encoder settings (as in RFC5762), or to use fewer enhancement layers (as in RFC6190), to proprietary methods for detecting quality of experience issues and cutting off video. </del>  5. <del> **Note to Reviewers^^ - this section includes some material that may be tutorial for some readers.  We can decide how to say that, if the tutorial material is worth keeping.  Spencer thought it was worth including, because it provides a contrast to the material on QUIC, which is significantly less tutorial, unless you participated in the QUIC working group. </del>  Because networking resources are shared between users, a good place to start our discussion is how contention between users, and

Reviewer comments:
Also clarified relationship with UDP Behaviors section
I think this is ready to merge. Opinions?
I was more concerned about overlap when I opened , but what's in the section on Unreliable Transport and what's in the section on UDP behaviors seems to read pretty well to me. Opinions?
SRT, TS-Multicast over UDP, etc.
I THINK this is requesting a change in the "Unreliable Transport" section.
I think this one is also ready to close. Opinions?

Revised text:
4.5.  <ins> In contrast to segmented delivery, several applications use unreliable UDP or SCTP with its "partial reliability" extension RFC3758 to deliver Media encapsulated in RTP RFC3550 or raw MPEG Transport Stream ("MPEG-TS")-formatted video MPEG-TS, when the media is being delivered in situations such as broadcast and live streaming, that better tolerate occasional packet loss without retransmission. </ins> Under congestion and loss, this approach generally experiences more video artifacts with fewer delay or head-of-line blocking effects. applications like videoconferencing, or for other live-action video with interactive components, such as some sporting events.  <ins> The Secure Reliable Transport protocol SRT also uses UDP in an effort to achieve lower latency for streaming media, although it adds reliability at the application layer. Congestion avoidance strategies for deployments using unreliable transport protocols vary widely in practice, ranging from being entirely unresponsive to congestion, to using feedback signaling to change encoder settings (as in RFC5762), to using fewer enhancement layers (as in RFC6190), to using proprietary methods to detect "quality of experience" issues and turn off video in order to allow less bandwidth-intensive media such as audio to be delivered. More details about congestion avoidance strategies used with unreliable transport protocols are included in udp-behavior. </ins> 5.  <ins> *Note to Reviewers* This section includes some material on UDP and TCP that may be tutorial for some readers.  We can decide how to explain that, if the working group feels that this tutorial material is worth keeping. Spencer thought it was worth including, because it provides a contrast to the material on QUIC, which is significantly less tutorial, unless the reader participated in the QUIC working group. </ins> Because networking resources are shared between users, a good place to start our discussion is how contention between users, and