1 / 5

Reason Header for Preemption in SIP

This draft proposes a Reason Header to inform UA and SIP elements of a purposeful premature end to a session, defining conditions and syntax for preemptive actions.

hnguyen
Download Presentation

Reason Header for Preemption in SIP

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reason Header for Preemption draft-polk-sipping-reason-header-for-preemption-00 James M. Polk 11 Nov 03

  2. What this is for • Informing remote the UA and SIP elements of a purposeful premature end to a session • Two conditions defined here: • At the UA • Within the network • Appropriate mechanism is using a Reason Header contained within a BYE request

  3. Proposed Syntax • IANA section of 3326 allows a SIP, Q.850 or token value for cause • This ID proposed 2 tokens: • Preempted_UA • Preempted_Network For example: Reason : preempted_UA

  4. Issues and suggestions Suggestion: • Don’t use token, but use a new namespace “preemption” • Suggested syntax becomes: Reason: preemption ;cause=1 ;text="Network Preemption" Reason: preemption ;cause=2 ;text="UA Preemption“ Issue: not sure this is currently allowed by RFC 3326

  5. Next Steps • Ask to be reviewed by SIP WG to become WG item • As a logical follow-on effort to the Resource-Priority Header

More Related