…t be able to send short latency unreliable datagram traffic to a peer browser [ RFC5405 ]. ---------------------------------------------------------------- A13, A14, A15, A16, A17, A18, A23 Holmberg, et al. Informational [Page 16] RFC 7478 WebRTC March 2015 2.4 . Browser - GW/Ser…
…st be able to send short latency unreliable datagram traffic to a peer browser [RFC5405]. ---------------------------------------------------------------- A13, A14, A15, A16, A17, A18, A23 Holmberg, et al. Informational [Page 16] RFC 7478 WebRTC March 2015 2.4. Browser - GW/Serve…
…t be able to send short latency unreliable datagram traffic to a peer browser [ RFC5405 ]. ---------------------------------------------------------------- A13, A14, A15, A16, A17, A18, A23 Holmberg, et al. Informational [Page 16] RFC 7478 WebRTC March 2015 2.4 . Browser - GW/Ser…
…t be able to send short latency unreliable datagram traffic to a peer browser [ RFC5405 ]. ---------------------------------------------------------------- A13, A14, A15, A16, A17, A18, A23 Holmberg, et al. Informational [Page 16] RFC 7478 WebRTC March 2015 2.4 . Browser - GW/Ser…
… application or protocol and explain their rationale for their design choice. [ RFC5405 ] was scoped to provide guidelines for unicast applications only, whereas this document also provides guidelines for UDP flows that use IP anycast, multicast, broadcast, and applications that …
…ular, a decrease of ACK_TIMEOUT below 1 second would violate the guidelines of [RFC5405]. ([RTO-CONSIDER] provides some additional background.) CoAP was designed to enable implementations that do not maintain round-trip-time (RTT) measurements. However, where it is desired to dec…