…on the rate at which they will create new bindings. Discussions in the IETF ICE WG during the work on this specification concluded that once every 5 ms is well supported. This is why Ta has a lower bound of 5 ms. Furthermore, transmission of these packets on the network makes use…
…on the rate at which they will create new bindings. Discussions in the IETF ICE WG during the work on this specification concluded that once every 5 ms is well supported. This is why Ta has a lower bound of 5 ms. Furthermore, transmission of these packets on the network makes use…
…ho, in the context of the work on RFC 1995bis, recently has provided the DNSEXT WG access to a privately archived DNSIND mailing list thread on RFC 1995, in which such issues have been discussed in November 1999. For the record, the technical issues in RFC 1995 that can be addres…
…ho, in the context of the work on RFC 1995bis, recently has provided the DNSEXT WG access to a privately archived DNSIND mailing list thread on RFC 1995, in which such issues have been discussed in November 1999. For the record, the technical issues in RFC 1995 that can be addres…
… in other affected protocols and in new protocols being designed. In the MMUSIC WG there is work on a replacement of SDP called SDP-NG. It is recommended that the problems outlined in this document be considered when designing solutions for specifying bandwidth in the SDP-NG [ 17…
…Binding Indications which are one-way and therefore not sufficient. The current WG consensus is to use ICE Binding Requests for continuing consent freshness. ICE already requires that implementations respond to such requests, so this approach is maximally compatible. A separate d…
…ection discusses the main use cases for RTP stream pause and resume. The RTCWEB WG's use case and requirements document [ RFC7478 ] defines the following API requirements in Appendix A , which is also used by the W3C WebRTC WG: A8 The web API must provide means for the web applic…