Re: [sipcore] Session Timers (RFC 4028) for REFER, PUBLISH, MESSAGE not defined

[Samir Srivastava <[e-mail]>]

In-line prefixed with SS>>
ThanksSamir Srivastavahttp://samirsrivastava.typepad.com
On 5/13/2020 at 3:15 AM, "Paul Kyzivat"  wrote:On 5/12/20 5:30 PM,
Roman Shpount wrote:
> Samir,
> 
> Most likely Min-SE and Session-Expires headers in  REFER, PUBLISH, 
> MESSAGE would be out of scope for 4028bis. So far there was an
agreement 
> to limit the scope of 4028bis to fixing handling of multiple 
> transactions which modify Session-Expiration at the same time and 
> associated race conditions.
> 
> Any other changes would need to go into another RFC.
> 
> P.S. Why would you put Min-SE and Session-Expires into REFER,
PUBLISH, 
> MESSAGE? These header fields are only defined for INVITE/UPDATE
messages 
> and not applicable for any other messages.

Putting them in *these* messages would be nonsensical because they are

neither dialog establishing nor dialog refreshing. OTOH, it would make

perfect sense to use them in SUBSCRIBE/NOTIFY because they *are*. 
Session Timer is about maintaining the dialog. I would think it would
be 
equally applicable to these kinds of dialog usages. But that is
probably 
deserving of discussion.

SS>>  There are other messages in the table for which these headers
are not applicable. On the same line mention these headers are not
applicable for REFER, PUBLISH, MESSAGE methods. Messages apart from
(re)Inv and UPD are only mentioned in the table in 4028bis and RFC
4028. 4028bis mentions in the table that these headers are not
applicable for SUBSCRIBE / NOTIFY also.  

 Thanks,
 Paul