[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    Re: [Sip-implementors] Errata ID: 4744 for RFC 4028: Session Expire timer value can be changed?
From:       OKUMURA Shinji <ietf.shinji () gmail ! com>
Date:       2020-12-07 5:58:28
Message-ID: eec49970-63f9-be63-2f13-8f57c45cd407 () gmail ! com
[Download RAW message or body]

Hi Aakash,

According to the current RFC, UAs can not start another negotiation of 
the session timer during the early dialog.

Regards,
Shinji

On 2020/12/05 1:03, akashdeep vishnoi wrote:
> Hi,
>
> I have a little confusion in this :
> --------------------------------
> Errata ID: 4744
> Status: Reported
> Type: Technical
> Publication Format(s) : TEXT
> Reported By: Chao Wang
> Date Reported: 2016-07-19
>
> Section 3 says:
>   A UAC starts by sending an INVITE. This includes a Supported header field
> with the option tag 'timer', indicating support for this extension
>
> It should say:
> A UAC starts by sending an INVITE. This includes a Supported header field
> with the option tag 'timer', indicating support for this extension.If UAC
> or UAS knows one negotiation of session timer is ongoing, it SHALL not
> start a new one.
>
>
> -------------------------------------------------------------------------------
> As per above explanation, I want to know if* Session Expire timer value can
> be changed by UAS/UAC by sending early UPDATE* before Call is established
> when INVITE request already has one timer value.
>
> Thanks,
> Aakash
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
[prev in list] [next in list] [prev in thread] [next in thread]