Support encrypted RTP extensions (RFC 6904)

webrtc/api/peerconnectioninterface.h

Index: webrtc/api/peerconnectioninterface.h
diff --git a/webrtc/api/peerconnectioninterface.h b/webrtc/api/peerconnectioninterface.h
index b346783bb37048699b95e256026b8bf1a92bb08e..b2fdc1375b9c684a99064bb9da4b0358bc8b3147 100644
--- a/webrtc/api/peerconnectioninterface.h
+++ b/webrtc/api/peerconnectioninterface.h
@@ -871,6 +871,10 @@ class PeerConnectionFactoryInterface : public rtc::RefCountInterface {
 
     // Sets crypto related options, e.g. enabled cipher suites.
     rtc::CryptoOptions crypto_options;
+
+    // If set to true, encrypted RTP header extensions as defined in RFC 6904
+    // will be negotiated. They will be only used if both peers support ihem.

[pthatcher1, 2017/03/21 07:07:06]

ihem => them

[joachim, 2017/03/23 00:04:32]

Done.

+    bool enable_rtp_header_encryption = false;

[pthatcher1, 2017/03/21 07:07:06]

I think enable_encrypted_rtp_header_extensions would be slightly better.

[Taylor Brandstetter, 2017/03/22 18:00:10]

Is there a reason this is added here, and not in RTCConfiguration? I think
that's what we prefer by default.

[joachim, 2017/03/23 00:04:32]

Done.

[joachim, 2017/03/23 00:04:32]

I assumed that it would more be a general option like "ssl_max_version" or
"crypto_options" which will not be different per PeerConnection.

   };
 
   virtual void SetOptions(const Options& options) = 0;