1 / 6

draft-elwell-sipping-redirection-reason-01

draft-elwell-sipping-redirection-reason-01. Motivation. Address 302 ambiguity issue Additional information for UAC and UAS Improved interworking with legacy. Issues discussed on list. What is “normal rerouting”? Probably need to remove this codepoint

cleo-french
Download Presentation

draft-elwell-sipping-redirection-reason-01

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. draft-elwell-sipping-redirection-reason-01

  2. Motivation • Address 302 ambiguity issue • Additional information for UAC and UAS • Improved interworking with legacy

  3. Issues discussed on list • What is “normal rerouting”? • Probably need to remove this codepoint • Simply omit the Reason header if nothing particular to say about reason for redirection • How a Reason header in request or response relates to that request or response • More clarification needed

  4. Issues discussed on list (continued) • How it relates to History-Info • Was clarified on list • How to define values • Whether this is a sufficient list of values • Whether apps can do anything useful with the additional info • Not just for apps – also for display at UAS and UAC • Also for legacy interworking

  5. Issues discussed on list (continued) • Could Q.732 be used instead of inventing new namespace? • Use of Reason header in a response – is it allowed in RFC 3326? • Current text: “The Reason header field MAY appear in any request within a dialog, in any CANCEL request and in any response whose status code explicitly allows the presence of this header field.”

  6. Way forward • Three choices: • Do nothing • Define new extensible namespace along lines proposed in this draft • Define new namespace for Q.732 codepoints • In last two cases, define responses in which Reason header can be used in this way (e.g., 1xx, 2xx, 3xx) • In any case, may wish to permit existing Reason header in 3xx responses to solve only the 302 ambiguity problem

More Related