1 / 5

199 Status update draft-ietf-sip-199-00

199 Status update draft-ietf-sip-199-00. Christer Holmberg. OPEN ISSUE #1: Sending 199 reliably. Should it be allowed to send 199 reliably? Claim against: it would require resources to be kept in order to handle the associated PRACK

dawn-bryan
Télécharger la présentation

199 Status update draft-ietf-sip-199-00

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. 199Status updatedraft-ietf-sip-199-00 Christer Holmberg

  2. OPEN ISSUE #1:Sending 199 reliably • Should it be allowed to send 199 reliably? • Claim against: it would require resources to be kept in order to handle the associated PRACK • Claim against: proxy which triggers 199 would have to terminate the associated PRACK • Claim for: if we in future want to use 199 to solve HERFP, it shall be allowed to send 199 reliably • PROPOSAL: Allow sending of 199 reliably, but add text saying that it may also be sent unreliably even if 100rel has been required

  3. OPEN ISSUE #2:UAS sending 199 • Should an UAS be allowed to send 199? • May not be useful for a UA to send 199, but could be useful for B2BUA/AS type-of entities • PROPOSAL: Allow UAS to send 199

  4. OPEN ISSUE #3:SIP information in 199 • Should the 199 response contain information (SIP headers, final response code etc) from the final response which triggered the 199? • May be useful if we at some point use 199 to solve the HERFP • PROPOSAL: If the initial request indicates support of sipfrag, it is recommended to include sipfrag message body in 199

  5. OPEN ISSUE #4:199 option-tag • Do we need an option-tag to indicate support of 199, so that it is not sent to UACs not supporting it? • Intermediates may also have interest in receiving 199, which means they would have to be allowed to insert the option-tag (if not present in the request) • PROPOSAL: We don’t specify an option-tag

More Related