1 / 8

CLUE Framework

CLUE Framework. IETF 86, Orlando March 11-15, 2013 Mark Duckworth. Recent Changes. Re-write introduction and overview add basic call flow sequence diagram Remove Consumer Capability Message Simultaneous Transmission Sets are optional Many clarifications, based on email list discussions

zan
Download Presentation

CLUE Framework

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 Framework IETF 86, Orlando March 11-15, 2013 Mark Duckworth

  2. Recent Changes • Re-write introduction and overview • add basic call flow sequence diagram • Remove Consumer Capability Message • Simultaneous Transmission Sets are optional • Many clarifications, based on email list discussions • Propose moving some details to other documents

  3. Conform to SDP Offer/Answer • CLUE is not advocating doing anything contrary to negotiated SDP • Propose to make this explicit in the framework • use RFC4566 SDP and RFC3264 Offer/Answer with SDP

  4. Simultaneous Transmission Sets • Could be for any reason, not just physical constraints • Propose to allow expressing STS in terms of Capture Sets, Capture Set Entries, and Media Captures • Keep it as simple list of sets • do not add logical operations or other ways of expressing it

  5. All Media Types in CSE and STS • Should a Capture Scene Entry and Simultaneous Transmission Set include media of all types, or just a single type? • Currently they include just a single type

  6. Attribute Issues • Area of Scene proposal • keep it as area, not volume. Should be equal or greater than extents of individual capture areas • scene-switch-policy • should it be on Capture Set rather than CSE? Want each media type to be consistent. • draft-groves-clue-capture-attr • proposal to accept these changes in framework (and data model)

  7. Refactoring – where to draw the line • Framework-09 proposes to move some detail to other document, probably the data model • Some say the proposal goes too far, and some of that information should stay in the framework • Proposal • syntax details should go in the data model. • Concepts should be explained in the framework. • Use consistent terms. • Keep some of the detail in framework

  8. Update Examples • Should keep current examples in framework • Editors’ task to update them for consistency with other changes, and with data model terminology • Editors encourage others to contribute additional examples

More Related