1 / 17

CLUE protocol

CLUE protocol. CLUE design team meeting 28/10/2014. Outline. News in version 2 State machines READV ADV diff mechanism Open issues. Diff with version 1. Main changes : Major review of state machines Diff mechanism for the ADV READV and READV RESPONSE messages removed

mckenzie-hardin
Download Presentation

CLUE protocol

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 protocol CLUE design team meeting 28/10/2014

  2. Outline • News in version 2 • State machines • READV • ADV diffmechanism • Open issues

  3. Diffwithversion 1 • Mainchanges: • Major review of state machines • Diff mechanism for the ADV • READV and READV RESPONSE messages removed • Minor changes: • Schema and examples updated according to the changes in the data model document • IANA section • References updated and split into Informative references and Normative references as in framework v17. • Terminology: many definitions added. • Response codes updated

  4. CLUE Participant’s state machine

  5. MP’s state machine

  6. MC’s state machine

  7. READV • Conceivedtoallow a MC torequest a new ADV from the MP, but… • Case 1 • When the MP issuesan ADV, itgoesto the WAIT FOR ACK state; • If no ACK arrives, itmoves back to the ADV state and issues a new ADV • .. For a limitednumberoftimes; afterthat, the MP goesto TERMINATED

  8. READV • Case 2: • When the MC is in the ADV PROCESSING state and somethinggoes wrong with the received ADV, the MC sends a NACK message and goes back towaitfor a new ADV • The MP, on the basisof the response code of the ACK, • Understandsthat a new copy of the ADV isneeded • Goes back to the ADV state and sends a new ADV to the MC

  9. READV • Case 3: • In case ofchannelerrors or end ofsessionevents, the state machineof the CLUE Participantgoesto the TERMINATED state • All the resourcesallocatedfor the sub-state machines are released • A newchannelsetupphaseisneeded • Wheneverythingis up again, the MC goes in the WAIT FOR ADV state and the MP in the ADV state, so sooner or later a new (full) ADV willarriveto the MC

  10. Diffmechanismfor the ADV • New schema for the ADV message

  11. Diffmechanismexample: full ADV <advertisement xmlns="urn:ietf:params:xml:ns:clue-message"... protocol="CLUE" v="0.2"> <clueId>Ciccio</clueId> <sequenceNr>11</sequenceNr> <mediaCaptures> <ns2:mediaCapture ...xsi:type="ns2:audioCaptureType" captureID="AC0" mediaType="audio"> ... <ns2:description lang="en">main audio from the room</ns2:description> ... <ns2:capturedPeople> <ns2:personIDREF>ciccio</ns2:personIDREF> </ns2:capturedPeople> </ns2:mediaCapture> <ns2:mediaCapture ... xsi:type="ns2:videoCaptureType" captureID="VC0" mediaType="video"> ... <ns2:description lang="en">left camera video capture</ns2:description> ... <ns2:capturedPeople> <ns2:personIDREF>ciccio</ns2:personIDREF> </ns2:capturedPeople> </ns2:mediaCapture> ... <people> <ns2:person personID="ciccio"> <ns2:personInfo> <ns3:fn> <ns3:text>Ciccio Esposito</ns3:text> </ns3:fn> </ns2:personInfo> <ns2:personType>chairman</ns2:personType> <ns2:personType>timekeeper</ns2:personType> </ns2:person> </people> </advertisement>

  12. Diffmechanismexample: partial ADV <advertisement xmlns="urn:ietf:params:xml:ns:clue-message" ... protocol="CLUE" v="0.2"> <clueId>Ciccio</clueId> <sequenceNr>12</sequenceNr> <add sel="/advertisement/people"> <ns2:person personID="alice_ID"> <ns2:personInfo> <ns3:fn> <ns3:text>Alice Romano</ns3:text> </ns3:fn> </ns2:personInfo> <ns2:personType>attendee</ns2:personType> </ns2:person> </add> <add sel="/advertisement/mediaCaptures/mediaCapture/capturedPeople"> <ns2:personIDREF>alice_ID</ns2:personIDREF> </add> </advertisement>

  13. Open issues • Reviewof the state machines (and responsecodes) by the community • Diffmechanism: mandatory or not • IANA sectiontobecompleted • Security sectiontobeadded

  14. Partial ADV MP MC Adv # 12 nack Adv # 13 ack PartialAdv # 14 (ref #13) nack PartialAdv # 15 (ref #13) ack PartialAdv # 16 (ref #15) ack

  15. Call flow example MP MC ADV Adv # 12 adv sent advrecvd WAIT FOR ACK PROCESSING ADV CONF+ACK sent Conf + ack (ref ADV#12) Changetpsettings ADV WAIT FOR CONF RESP Adv # 13 advrecvd WAIT FOR ACK PROCESSING ADV Ignored, Out of date CONF+ACK sent Conf + ack (ref ADV#13) WAIT FOR CONF RESP Conf+ackreceived CONF RESPONSE Successfulconfresponse sent Confresponse #14 Successful Confresponse recvd SDP O/A SDP O/A

  16. CLUE data model: tickets • #48 - Linking participant Information with Participant Type • #54 – Data model: Security Considerations • #62 – Data model: Audio captures • #63 - Action: Data model - Remove audio channel format • #59 - Action: Change "Capture Scene Entry (CSE)" to “Capture Scene View (CSV)” • #60 - Action: Change "Global CSE List" to “Global View List” • #61 - Action: Proposal for describing the coordinate system • ToDo • #55 – Data model: IANA considerations • ToDo • #35 - Ensure Framework and Data model terminology is consistent • Framework v 18

  17. Updatestoappear • <mccContent> insteadof <content>, <mccConfiguredContent> insteadof <configuredContent> • <captureView> insteadof <view> • IANA registrationforvaluesofenumeratedtypes • Ongoingdiscussion • Extensions

More Related