Philipp Hancke cfaba8fd2d Measure SDP munging
by storing
  [[LastCreatedOffer]] / [[LastCreatedAnswer]]
which are similar to the W3C equivalent but as
description objects instead of serialized SDP strings.

While rejecting all SDP munging is not feasible, this lets us
measure and reject certain modifications gradually.

Chromium metrics CL:
  https://chromium-review.googlesource.com/c/chromium/src/+/6089633

This is measured at three points during the lifetime of a peerconnection:
* for the first SLD call
* when the connection is first established
* when the connection was established and is being closed

Note that the "first" SDP munging detected is returned which may hide that something uses more than one modification.

BUG=chromium:40567530

Change-Id: I964e3ee6e75f73b777d90556fac8691a6f3dc27f
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/370680
Reviewed-by: Harald Alvestrand <hta@webrtc.org>
Reviewed-by: Henrik Boström <hbos@webrtc.org>
Reviewed-by: Johannes Kron <kron@webrtc.org>
Commit-Queue: Henrik Boström <hbos@webrtc.org>
Cr-Commit-Position: refs/heads/main@{#43741}
2025-01-15 07:38:45 -08:00
..
2025-01-15 07:38:45 -08:00
2025-01-08 11:55:45 -08:00
2024-12-09 17:34:59 +00:00
2024-07-23 17:23:45 +00:00
2025-01-08 11:55:45 -08:00
2024-12-03 15:00:21 +00:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-15 07:38:45 -08:00
2025-01-08 11:55:45 -08:00