inline.

Hisham Khartabil wrote:

This came up at sipit 16.

draft-ietf-sip-session-timer-15.txt says in section 7.1:

"The UAC MAY include the refresher parameter with value 'uac' if it
   wishes to perform the refreshes.  However, it is RECOMMENDED that the
   parameter be omitted, so that it can be selected by the negotiation
   mechanisms described below."

I came across an implantation that sets the refresher parameter to 'uas' when initiating the INVITE. The claim was that the draft does not explicitly forbid that.

It doesnt forbid lots of things. However, it is not supposed to do that, and this is not a good idea.



The problem with that is: what if the UAS does not support session timer. The spec says in section 8.2 (proxy processing responses)


"If, however, the proxy remembers that the UAC did
   support session timer, additional processing is needed.

   Because there is no Session-Expires or Require header field in the
   response, the proxy knows it is the first session-timer-aware proxy
   to receive the response.  This proxy MUST insert a Session-Expires
   header field into the response with the value it remembered from the
   forwarded request."

Some proxies may interpret that to mean the whole value, including the refresher parameter that contained 'uas' which will cause all sorts of funny things to happen.

Right. It would have been OK to insert the whole thing had the UAC not done the wrong thing.



Now, the draft does go on to say

"  It (the proxy) MUST set the value of the 'refresher'
   parameter to 'uac'."

so the problem my fix itself, but i think we need to clarify this: either say that the UAC MUST NOT set the refresh parameter to 'uas' (which is what I prefer) or add some text clarifying the scenario and behaviour for proxies.

Its too late to clarify this, unfortunately, since the spec is about to issue as an RFC. However, Please tell those folks that this is not a correct implementation.


-Jonathan R.


-- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Director, Service Provider VoIP Architecture Parsippany, NJ 07054-2711 Cisco Systems [EMAIL PROTECTED] FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.cisco.com _______________________________________________ Sip-implementors mailing list [email protected] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to