1. CLUE Framework IETF 84 July 30 – Aug 3, 2012 Mark Duckworth Allyn Romanow Brian Baldino Andy Pepperell

2. Agenda Overall status of framework document Document changes from version 05 to 06 Current issues and proposals – Ticket #5 – describing composed captures – Ticket #9 – axis of capture – Ticket #8 – differentiate between capture scenes – Ticket #10 – is there sufficient info for receiver? 2

3. Overall Status Framework has been fairly stable since last IETF meeting, just a few minor changes There are 4 open issues being tracked, maybe some can be closed soon Extensibility is key, but we plan to address that in the protocol design rather than in the framework itself 3

4. Changes in version 06 Description attribute (for capture scene) can be in many languages, not just one Add new Axis of Capture Point attribute (Ticket #9) Remove appendices A.1 through A.6. Clarify that the provider must use the same coordinate system with same scale and origin for all coordinates within the same capture scene. 4

5. Ticket #5 describing composed captures Several people suggest the current boolean composed attribute is sufficient for CLUE version 1 Other protocols may be more appropriate for describing different aspects of composed captures CLUE may be extended in future, if necessary, to provide more information or integrate with other protocols Proposal – close Ticket #5 with no changes to framework 5

6. Ticket #9 – axis of capture New Axis of Capture Point attribute addresses this There was some discussion of changing the details of the text, but no conclusion yet – What should be assumed if some points are not specified? – should axis point be restricted, e.g. not behind capture point? – specific text proposed by Christian Proposal – close Ticket #9 with these clarifying changes as discussed on the list 6

7. Ticket #8 – differentiate between capture scenes Description attribute for a capture scene addresses this, at least in part Proposal – add an optional description attribute to media captures, as a few people have suggested already Proposal – close Ticket #8, unless people have specific proposals for additional information to include in the framework 7

8. Ticket #10 – is there sufficient info for receiver? draft-romanow-clue-audio-rendering-tag (on hold) suggestions for new audio attributes – from same room? live or recorder? draft-kyzivat-clue-extended-use-cases (in email) long email discussion with no conclusion Again, extensibility is key Proposal – keep framework as is for now, consider new items for future extensions 8