Yeah, I remember that statement. Unfortunately, it only states there that the Session-Expires header is only allowed in those methods. It does not state that a Session Refresh is limited to those methods. I agree that it should be obvious, but as you said, they should have used more normative statements.
Joel Gerber Network Operations Specialist - Telephone Telephone Eastlink joel.ger...@corp.eastlink.ca T: 519.786.1241 -----Original Message----- From: Brett Tate [mailto:br...@broadsoft.com] Sent: March-27-15 10:03 AM To: Joel Gerber; sip-implementors Subject: RE: [Sip-implementors] Sessions Expires with Info > I do wish that RFC 6086 was a bit more specific. It only states INVITE or > UPDATE in-dialog transactions as refreshers, but, nowhere does it > state that > they are the only ones allowed for refreshing. A little bit of wording change > would have saved a lot of headaches. I agree that RFC 4028 potentially could have used more normative text; however it does indicate the following. Section 4: "The Session-Expires header field conveys the session interval for a SIP session. It is placed only in INVITE or UPDATE requests, as well as in any 2xx response to an INVITE or UPDATE." _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
