100 likes | 314 Views
Extending the Session Initiation Protocol (SIP) Reason Header for Applications draft-mohali-sipcore-reason-extension-application-00. Marianne Mohali ( marianne.mohali@orange-ftgroup.com ) Bruno Chatras (bruno.chatras@orange-ftgroup.com). Problem statement. As per RFC 3326:
E N D
Extending the Session Initiation Protocol (SIP) Reason Header for Applicationsdraft-mohali-sipcore-reason-extension-application-00 Marianne Mohali (marianne.mohali@orange-ftgroup.com) Bruno Chatras (bruno.chatras@orange-ftgroup.com)
Problem statement • As per RFC 3326: • Reason header field may be present to indicate why a SIP request was issued. Problem: • Applications may initiate rejection or cancellation of SIP request • but cannot include an application-specific reason in the CANCEL/BYE request.
Problem statement (contd.) • As per RFC 4244: • Reason header field may be present in the History-Info header to indicate why a SIP request was retargeted. Problem: • Existing protocol-cause values do not permit sending application-specific reasons
Proposed solution • Allow the use of Reason header field in application-initiated SIP requests • Extension similar to RFC4411 (preemption) • By creating: • a new protocol value: "application" • a new set of associated cause values: protocol protocol-cause reason-text -------------- ------------------ ----------------- application cause=x text="xxxx" Example:Reason:application;cause=2;text="Freephone"
Use case Freephone Server Agent Alice INVITE Call is retargeted INVITE History-Info: [Reason:application;cause=2;text="Freephone"]
Early Comments/feedbacks Issue 1: Add a cause value for forking needs? => Reason in CANCEL sent on the legs to release
Early Comments/feedbacks Issue 2: Add more readability in IANA section => done in the next version
Early Comments/feedbacks Issue 3: Improve cause values description => done in the next version
Next Steps • Need more reviewers • WG item? • Intended status: standards track
Questions? Thank you !