1. CLUE protocol CLUE design team meeting 07/10/2014 15/10/2013

2. Open tickets #56: Security Considerations #58: IANA Considerations #13: What data needs to be in CLUE specific signaling? #20: Rejecting configure #45: Backwards compatibility #44: Remove contradiction wrt responding to ADV with CONF #25: ADV: all or delta #22: out of date ADVs 15/10/2013

3. #56: Security considerations Using RFC6503 – Centralized Conferencing Manipulation Protocol as a template – User Authentication and Authorization – Security and Privacy of Identity – Mitigating DoS Attacks 15/10/2013

4. #58 – IANA Considerations Using RFC6503 – Centralized Conferencing Manipulation Protocol as a template URN Registration – urn:ietf:params:xml:ns:clue-protocol DNS Registrations – Application service tag CLUE – Application protocol tag CLUE XML Schema Registration CLUE Protocol Registry – CLUE message types – CLUE response codes 15/10/2013

5. #13 - What data needs to be in CLUE specific signaling? CLUE messages have been defined in the protocol document Signaling is covered by draft-ietf-clue-signaling No text is attached to the ticket The ticket should be closed 15/10/2013

6. #20 – Rejecting configure CONF can be rejected by the MP – Response codes & reason strings: ADV Expired Bad Syntax Invalid value … “Does the prior configure remain in effect?” – Yes The ticket should be closed 15/10/2013

7. #45 – Backward compatibility Minor versions are backward compatible – If I know 1.5, I must be able to know 1.2 Minor versions “define further features and functionality besides those defined in the previous versions, in an incremental way, without impacting the basic rules defined in the previous version of the schema” Downgrade mechanism needs to be specified – E.g., to turn from 1.5 to 1.2 15/10/2013

8. #45 – Backward compatibility The downgrade is up to the CLUE Participant with the highest minor version number The schemas associated with new versions must be publicly available Downgrading from v1.5 to v1.2 means making the diff between schema v1.5 and schema v1.2 and considering only the common part – The rest being the incremental update made from v1.2 to v1.5 15/10/2013

9. #44 - Remove contradiction wrt responding to ADV with CONF Ways to respond to ADV – ACK, followed by a CONF – NACK only (ACK with an error response code) – CONF + ACK true line in the CONF message The ticket should be closed 15/10/2013

10. #25 - ADV: all or delta CLUE Partial Updates, draft-groves-clue- partial-update-00 – The mechanism will be included in the protocol To appear in version 8 – Updates are needed to the XML definition of the ADV When a previous ADV has been ACK-ed, the MP MAY use the diff mechanism to create the new ADV 15/10/2013

11. Open issues CLUE Participant definition needs approval – Both in protocol and in data model documents – “An entity able to use the CLUE protocol within a telepresence session. It can be an endpoint or a MCU” 15/10/2013