1 / 5

REFER Clarifications

REFER Clarifications. d raft-sparks-sipcore-refer-clarifications-00 SIPCORE – IETF90. Change for next (final?) revision. Leave room for extension OLD

kitra
Download Presentation

REFER Clarifications

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. REFER Clarifications draft-sparks-sipcore-refer-clarifications-00 SIPCORE – IETF90

  2. Change for next (final?) revision • Leave room for extension • OLD • As a direct consequence of requiring the use of GRUU, and the requirements in section 4.5.2 of RFC6665, sending a REFER within any existing dialog is prohibited. • NEW • As a direct consequence of requiring the use of GRUU, and the requirements in section 4.5.2 of RFC6665, sending a REFER that might result in an additional dialog usage within any existing dialog is prohibited.

  3. Point to Add about INVITE Dialogs • Proposed Text • A UA that supports receiving REFER needs to include a GRUU as a Contact in INVITE requests to ensure out-of-dialog REFER requests related to this dialog arrive at this UA. • This is consistent with RFC 3261 section 8.1.1.8, RFC 5589, and RFC 6665 section 4.5.1

  4. Next Steps for this document • Revise addressing the points discussed so far • Adjustment to leave room for future extension • Add sentence calling out need to use GRUU in original INVITE dialog • Propose to submit this as WG -00 and start LC

  5. Other potential work • Should Adam submit a short update to RFC 6665 adding clarification to section 4.5.1 • OLD: • Notifiers MUST implement the Globally Routable User Agent URI (GRUU) extension defined in [RFC5627], and MUST use a GRUU as their local target. • NEW: • Notifiers MUST implement the Globally Routable User Agent URI (GRUU) extension defined in [RFC5627], and MUST use a GRUU as their local target in any SIP message (including INVITE requests and responses) that might result in the creation of a dialog.

More Related