Thanks Ranjit. The word "MUST" seems to throw some vendors off. I saw at
least one device that behaves this way due to the word "MUST". Is there way to
get that reviewed and edited?
Thanks,
Hoil
From: Ranjit Avasarala
Sent: Friday, May 28, 2021 1:40 PM
To:
On 5/28/21 4:40 PM, Ranjit Avasarala wrote:
Hi Holi
The RFC says UAS should add a Require: timer in response when UAC is the
refresher to indicate to UAC that it is the refresher. But I think this is
redundant as UAC anyway knows it is the refresher and does not need a
reminder from UAS.
The
Hi Ranjit, thanks for taking a look.
However, I'm more interested in case where UAS is responding to UAC's request
with refresher as itself (uac). Consider this case -
UAC INVITE (Session-Expires: 1800;refresher=uac, Supported: timer) >
UAS
UAC < 200 OK (Session-Expires:
Hi Holi
The RFC says UAS should add a Require: timer in response when UAC is the
refresher to indicate to UAC that it is the refresher. But I think this is
redundant as UAC anyway knows it is the refresher and does not need a
reminder from UAS.
On Fri, May 28, 2021 at 3:18 PM Hoil Choi wrote:
Hi Holi
the presence of the "Require" header with value "timer" from UAS indicates
to UAC that it (UAC) is performing the refreshing operation. but if the UAS
is the refresher, then if Require header with value "timer" is present in
response from UAS, then UAC should send BYE if it does not
