1 / 4

REFER and Referred-By

This document discusses the confusion around the use of SIP-REFER and SIP-ReferredBy in the SIP Events framework. It introduces a new mechanism for signaling whether a subscription is created and proposes mandatory subscriptions as a lightweight way to terminate subscriptions. The document also addresses security concerns using the S/MIME mechanism. The draft has been submitted for review and minimal discussion has taken place thus far.

sheffer
Download Presentation

REFER and Referred-By

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 and Referred-By Robert Sparks dynamicsoft

  2. REFER • Late discussion demonstrated confusion about use of sip-events • draft-sparks-sip-refer-3265disc.txt adds clarifying discussion, defined new mechanism to signal whether subscription is created • BUT – no implementations of optional subscriptions, so that mechanism isn’t needed

  3. REFER Will submit refer-06 this week reflecting 3265disc without the Require/Supported mechanism Mandatory subscriptions lightweight way to terminate subscription

  4. Referred-Bydraft-ietf-sip-referredby-00 • Draft submitted after interim meeting • Uses S/MIME mechanism described in draft-peterson-sip-identity-00 to address security issues • Very little discussion on list since draft was submitted

More Related