Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial version 4/25/2008 0.2 Minor Updated the technical content. 6/27/2008 1.0 Major Updated and revised the technical content. 8/15/2008 1.01 Minor Revised and edited the technical content. 12/12/2008 2.0 Major Updated and revised the technical content. 2/13/2009 2.01 Minor Revised and edited the technical content. 3/13/2009 2.02 Revised and edited the technical content. 7/13/2009 2.03 Major Revised and edited the technical content 8/28/2009 2.04 Editorial Revised and edited the technical content 11/6/2009 2.05 Editorial Revised and edited the technical content 2/19/2010 2.06 Editorial Revised and edited the technical content 3/31/2010 2.07 Major Updated and revised the
technical content 4/30/2010 2.08 Editorial Revised and edited the technical content 6/7/2010 2.09 Editorial Revised and edited the technical content 6/29/2010 2.10 Editorial Changed language and formatting in the technical content. 7/23/2010 2.10 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 3.0 Major Significantly changed the technical content. 11/15/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 3.0 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 3.0 None No changes to the meaning, language, or
formatting of the technical content. 6/10/2011 3.0 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 4.0 Major Significantly changed the technical content. 4/11/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 4.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 4.1 Minor Clarified the meaning of the technical content. 2/11/2013 4.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 4.1 None No changes to the meaning, language, or
formatting of the technical content. 11/18/2013 4.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 4.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 5.0 Significantly changed the technical content. 7/31/2014 5.1 Minor Clarified the meaning of the technical content. 10/30/2014 5.1 None No changes to the meaning, language, or formatting of the technical content. 3/30/2015 6.0 Major Significantly changed the technical content. 6/30/2015 6.0 None No changes to the meaning, language, or formatting of the technical content.
If the received data is from a peer that has been identified as the active peer through a Set Active Destination request, it MUST be formed as specified in section . Receiving Non-TURN Data from the Client Once the protocol client has set a peer as the active destination, it can send non-TURN framed data to the . This data is relayed through the TURN server to the active peer. When the TURN server receives this data, it MUST follow the procedure specified in section 7.6, with the exception that the data MUST be formed as specified in section . Receiving Multiplexed TURN Encapsulated Data from the Client If a Multiplexed TURN Session ID (section ) has been allocated for the session, once the has set a peer as the active destination, it can send encapsulated data to the . This data is relayed through the TURN server to the active peer. When the TURN server receives this data, it MUST follow the procedure specified in section 7.6, with the exception that the data MUST be formed as specified in section and in section .<38> Events Lifetime Expiration: When the lifetime timer fires, the processes it as specified in section 7.7. Local Events None.
38 37 37 38 47 47 37 46 46 Messages 20 26 27 29 27 24 25 27 Mapped Address ( 22, 34) 23 33 MS-Service Quality ( 11, 34) 31 29 29 28 25 22 30 19 35 16 Pseudo-TLS over TCP ( 16, 18, 19) 19 19 35 N 9 O Other local events client ( 37, 43) server ( 37, 47) 11 P 52 14 14 53 R 9 10 9 14 S Security 52 52 Sequencing rules 37 41 40 43 43 42 42 37 44 47 47 47 46 46 Server abstract data model ( 37, 38, 43) triggered events ( 37, 44) initialization ( 37, 44) 37 44 47 38 37 37 38 47 47 37 46 46 other local events ( 37, 47) 37 44 47 47 47 46 46 timer events ( 37, 47) timers ( 37, 43) 15 T Timer events client ( 37, 43) server ( 37, 47) Timers client ( 37, 38) server ( 37, 43) 57 16 Pseudo-TLS over TCP ( 16, 18, 19) 19 19 Triggered events - higher-layer 37 39 40 40 39