[rtcweb] Consent freshness - interaction with SDP direction attributes

["Muthu Arul Mozhi Perumal (mperumal)" <[e-mail]>]

I was thinking what the interaction between the SDP direction attributes
and the generation of consent freshness (described in
draft-muthu-behave-consent-freshness-00) should be, in response to some
questions posted by Harald. My thought is that the direction attributes
in SDP should have no impact on the generation of consent freshness. As
far as the media connection address and port are valid, the browser
should continue to generate consent freshness requests, irrespective of
whether the stream is sendonly, recvonly, sendrecv or inactive,
analogous to RTCP.

 

This would:

- Eliminate the need for the browser to depend on the (untrusted) JS to
tell it when to stop/start generating consent requests.

- Keep the NAT bindings always alive.

 

Comments?

 

Muthu