This patchset mainly add NACK, RTX, DTLS active support, fix some issues and 
optimize the ICE and DTLS code

This version fix issue:
1. fix https://ffmpeg.org/pipermail/ffmpeg-devel/2025-July/346906.html
2. fix build error when openssl is 1.1.0, log:
libavformat/tls_openssl.c: In function ‘tls_write’:
libavformat/tls_openssl.c:1022:28: error: implicit declaration of function 
‘DTLS_get_data_mtu’; did you mean ‘DTLS_set_link_mtu’? 
[-Werror=implicit-function-declaration]
 1022 |         size = FFMIN(size, DTLS_get_data_mtu(c->ssl));
      |                            ^~~~~~~~~~~~~~~~~
3. clean up dtls code
4. add doc for whip and dtls

Jack Lau (14):
  avformat/whip: add whip_flags ignore_ipv6 to skip IPv6 ICE candidates
  avformat/whip: fix typos
  avformat/whip: fix H264 profile_iop bit map for SDP
  avformat/whip: implement NACK and RTX suppport
  avformat/whip: reindent whip options
  avformat/whip: add support for active dtls role
  avformat/whip: remove DTLSState enum
  avformat/whip: check the peer whether is ice lite
  avformat/whip: remove WHIP_STATE_DTLS_CONNECTING
  avformat/whip: simplify and modularize the ICE and DTLS
  avformat/tls_openssl: directly use mtu in TLSShared
  avformat/tls: add new option use_srtp to control whether enable it
  avformat/tls_openssl: cleanup the pointer name of TLSContext and
    TLSShared
  doc: add doc for dtls and whip

winlin (1):
  WHIP: X509 cert serial number should be positive.

 doc/muxers.texi            |  29 ++-
 doc/protocols.texi         |  78 ++++++
 libavformat/tls.h          |  17 +-
 libavformat/tls_openssl.c  | 264 ++++++++++----------
 libavformat/tls_schannel.c |   7 -
 libavformat/whip.c         | 486 ++++++++++++++++++++++++-------------
 6 files changed, 556 insertions(+), 325 deletions(-)

-- 
2.49.0

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".

Reply via email to