1 / 6

CLUE Signalling

CLUE Signalling. IETF 89 Robert Hansen. Signalling -07 revision. Changes not as substantial as diff to -06 would suggest Moved protocols/data channel text to appendix Relevant to draft- holmberg -clue- datachannel and draft- presta -clue-protocol Removed most discussion of pros/cons

jennis
Download Presentation

CLUE Signalling

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. CLUE Signalling IETF 89 Robert Hansen

  2. Signalling -07 revision • Changes not as substantial as diff to -06 would suggest • Moved protocols/data channel text to appendix • Relevant to draft-holmberg-clue-datachannel and draft-presta-clue-protocol • Removed most discussion of pros/cons • Added normative text for establishing calls with/without CLUE

  3. CLUE-controlled m-lines • Makes use of the grouping framework, with new “CLUE” semantic • MIDs of CLUE-controlled m-lines included in the same group as CLUE channel • CLUE m-lines also include a label attribute, used to reference them in CLUE protocol messages • Media must not be sent from these m-lines until negotiated via CLUE

  4. Establishing CLUE • Recommends that initially no CLUE m-lines except data-channel • Implementations in CLUE-only environments may choose to disregard this • Once data channel negotiated can add CLUE-controlled m-lines via new offers • CLUE protocol used to negotiate what captures to send

  5. Non-CLUE data channels • Recommend that any non-CLUE m-lines that share a media type with a CLUE-controlled m-line are disabled via SDP O/A once CLUE media starts • Not mandatory, as there may later be uses for mixed CLUE/non-CLUE media

  6. Changing CLUE status mid-call • Ongoing call goes from non-CLUE to CLUE if mid-call O/A means both sides negotiate CLUE data channel support • If in a CLUE call either side removes support for the data channel in their SDP the call is no longer CLUE enabled, media on all CLUE-controlled m-lines must stop • This is distinct from signalling failure of the data channel, where the call remains CLUE-enabled

More Related