meaning, language, or formatting of the technical content. 2/11/2011 0.3.2 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 0.3.2 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 0.3.2 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 0.4 Clarified the meaning of the technical content. 9/23/2011 0.4 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 1.0 Major Updated and revised the technical content. 3/30/2012 2.0 Major Updated and revised
the technical content. 7/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.1 Minor Clarified the meaning of the technical content. 1/31/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Updated and revised the technical content. 11/14/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 4.0 Updated and revised the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content.
When SessionState (section 3.1.1.1) is set to DataState, the server sends the data payload provided by the WDS Multicast Application Protocol to the clients, as specified in . When the server stops receiving replies from the Master Client, the server changes the SessionState (section 3.1.1.1) to QCCState to force the choice of a new client as the master client. The server MUST accept and process packets received from clients on (section 3.1.1.1) during the lifetime of the multicast session. For each packet received from a client, the server MUST validate the packet as specified in section and MUST ignore all packets that are not properly constructed. Whenever a packet is received from a client, the server MUST reset the Inactivity Timer (section ) and set its timeout value back to the value specified in section 3.1.2. The WDS Multicast Transport Protocol causes lower-layered triggered events to the WDS Multicast Application Protocol ([MS-WDSMA]) as the following specifies: Trigger Description POLLACK Trigger Section Status Trigger Section Data Empty Trigger Section Terminate Trigger Section The server MUST process the packet based on the OpCode (section ) as specified below. OpCode Description WDSMCTP_OP_JOIN 0x02 Section 3.1.5.2 WDSMCTP_OP_QCR 0x05 Section 3.1.5.8 WDSMCTP_OP_LEAVE 0x0B Section WDSMCTP_OP_POLLACK 0x0C Section 3.1.5.5 WDSMCTP_OP_ACK 0x08 Section WDSMCTP_OP_NACK 0x09 Section When the Inactivity Timer (section 3.1.2) expires (which happens when the server does not receive packets from any clients for the time specified in section 3.1.2), the server MUST terminate the multicast session. Packet Validation
Index A Abstract data model 46 47 46 46 47 30 31 32 31 30 33 34 57 24 24 9 C 9 64 Client 46 47 46 46 47 51 50 60 message processing 60 55 52 53 57 52 59 54 59 60 58 54 54 59 56 59 57 56 60 46 sequencing 60 55 52 53 57 52 59 54 59 60 58 54 54 59 56 59 57 56 60 50 22 D Data configuration - client Missing ODATA List 50 48 49 49 49 47 Data model - abstract 46 47 46 46 47 30 31 32 31 30 33 34 DataState - processing 40 40 40 41 41 processing NACK packet 43 42 43 40 43 59 23 Demote Trigger - processing 44 44 23 E 13 13
F 9 G 7 H triggered events 51 34 I 62 17 17 62 8 Initialization 50 34 7 J JOIN packet - processing 36 36 37 37 14 14 54 15 15 Joining multicast session 53 53 52 K 59 22 KICK Trigger - processing 38 38 22 L 37 21 21 Leaving 53 53 54 Local events 60 46 LossReport - updating 57 56 56 M Message processing client 60 55 52 53 57 52 59 54 59 60 58 54 54 59 56 59 57 56 server 35 40 44 36 38 37 37 38 38 39 Messages 24 23 13 14 15 22 21 27 28 25 10 20 20 16 16 26 10 12 24 syntax 12 10 11 12 15 10
Multicast session - joining 53 53 52 N NACK management 57 57 58 27 27 28 60 28 28 28 7 O 58 25 25 Other local events 60 46 8 P 10 10 Packet processing 35 36 52 62 POLL packet - processing 54 54 20 37 20 38 20 20 9 9 63 Q QCC packet - processing 54 55 16 55 16 QCCState - processing 39 39 38 39 16 39 16 18 59 R 59 26 26 7 8 7 8 S Security 62 62 10 10 Sequencing rules client 60 55 52 53 57 52 59 54 59 60 58 54 54 59 56 59 57 56 server 35 40 44 36 38 37 37 38 38 39 Server 30 31 32 31 30 33 34 34 34 46