Context Navigation

Changes between Initial Version and Version 1 of Ticket #1079

Ticket #1079
- Property Summary changed from ICE session should be kept alive even when media is marked as inactive to Media transport should be kept alive during double-hold scenario

-                      initial
+                      v1
 In double hold situation, media will be marked as a=inactive. When the media is reactivated again (the call is resumed), it looks like we unnecessarily restart ICE negotiation, which will fail if remote still has the ICE session intact.
+In double hold situation, media will be marked as a=inactive, and currently the media will be closed. This would cause the media transport to be reinitialized when the stream is resumed.
 More over, isn't it that we should keep sending keep-alive packets and maybe even RTCP packets even when the media is marked as inactive? This would be the argument to keep ICE session alive when media is inactive.
+There are two known possible failures with this behavior, with ICE and SRTP. With ICE, we unnecessarily restart ICE negotiation, which will fail if remote still has the ICE session intact. And similarly this will cause inconsistent states between local and remote SRTP endpoints if only one side restarts the session.
+More over, we should keep sending keep-alive packets even when the media is marked as inactive. This would be the argument to keep ICE session alive when media is inactive.