search

cdh4u / draft-sessiontimer-race

Other
0 stars 0 forks source link

turned-off #9

Open okumura-shinji opened 5 years ago

okumura-shinji commented 5 years ago

7.2. Processing a 2xx Response If the 2xx response did not contain a Session-Expires header field, there is no session expiration. In this case, no refreshes need to be sent. A 2xx without a Session-Expires can come for both initial and subsequent session refresh requests. This means that the session timer can be 'turned-off' in mid dialog by receiving a response without a Session-Expires header field.

Nevertheless, proxy can insert a S-E header into the request without S-E, and it can also insert a S-E header into the response without S-E. That is, session timer can not be stopped without proxy 's consent, and UA has no means to ask consent for proxy.

cdh4u commented 5 years ago

The proxy is only allowed to insert S-E in the response if the UAC indicated support in the request. So, if the UAC wants to turn off the session timer, it sends an UPDATE without indicating support for session timer.

Or, did I misunderstand your issue?

ietf-shinji commented 5 years ago

If "without indicating support for session timer" means that the Supported header does not include "timer", It seems something odd to me that the protocol is controlled by turning on / off the Supported header as appropriate. Instead of using a Supported header, we may be able to define new se-params that explicitly means "turned-off". It will be not easy but simple, and it is one solution.