Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial version 4/25/2008 0.2 Minor Revised and edited technical content 6/27/2008 1.0 Revised and edited technical content 8/15/2008 1.01 Minor Revised and edited technical content 12/12/2008 2.0 Major Revised and edited technical content 2/13/2009 2.01 Minor Revised and edited technical content 3/13/2009 2.02 Minor Revised and edited 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
11/18/2013 4.2 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 4.2 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 4.3 Clarified the meaning of the technical content. 7/31/2014 4.3 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 4.4 Minor Clarified the meaning of the technical content. 3/30/2015 5.0 Significantly changed the technical content. 6/30/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/4/2015 6.0 Major Significantly changed the
technical content. 7/1/2016 7.0 Significantly changed the technical content. 9/14/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 9/29/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 8.0 Major Significantly changed the technical content. 12/12/2017 8.0 None No changes to the meaning, language, or formatting of the technical content. 4/27/2018 9.0 Major Significantly changed the technical content. 7/24/2018 10.0 Major Significantly changed the technical content.
L (1 bit): The last packet packet flag. This field MUST be set to 1 if the packet is the last packet train packet in the packet train. It MUST be set to 0 otherwise. Packet Idx (7 bits): The index of the packet train packet in the packet train. It starts from 0. R (1 bit): Reserved. The sender SHOULD set it to 0. The receiver MUST ignore it. Packet Count (7 bits): The total number of packet train packets in the packet train. Packet Byte Count (2 bytes): The accumulated number of bytes in the RTCP RR packets containing the packet train packet counting from the first packet train packet to this packet train packet. RTCP Profile Specific Extension for Peer Info Exchange The format of the profile specific extension for peer info exchange is as follows: <32> 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 Type Length SSRC Inbound Link Bandwidth Outbound Link Bandwidth NC Reserve1 Reserve2 Reserve3 Type (2 The extension type. Set to 0x000C (12). Length (2 bytes): The extension length in bytes, including this header. Set to 0x0014(20). SSRC (4 bytes): The from which the peer info exchange is sent. Inbound Link Bandwidth (4 bytes): The maximum inbound bandwidth supported by the host. Outbound Link Bandwidth (4 bytes): The maximum outbound bandwidth supported by the host. NC (1 bit): No flag. If NC is one, it indicates the inbound and outbound link bandwidth carried in the profile extension MUST NOT be cached and used beyond this session. Reserve1 (7 bits): Reserved field. The sender SHOULD set it to zero. The receiver MUST ignore it. Reserve2 (1 byte): Reserved field. The sender SHOULD set it to zero. The receiver MUST ignore it. Reserve3 (2 bytes): Reserved field. The sender SHOULD set it to zero. The receiver MUST ignore it. RTCP Profile Specific Extension for Network Congestion Notification The format of the profile-specific extension for Network Congestion Notification is as follows<33>: 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1 Type Length
A Abstract data model 41 35 13 healer metrics 53 23 B Bandwidth estimation 47 C 13 66 D Data model - abstract 41 35 Dominant speaker history notification extension 59 Dominant speaker notification 47 E Estimated bandwidth 47 20 46 53 47 59 47 60 57 51 58 52 54 56 46 53 51 59 F 14 G 7 H triggered events 42 37 61 61 10 Initialization 42 36 7 L Local events 44 38 M Message processing 43 37 Messages 17 28 17 RTCP Packet Pair Packet 17, 17) RTCP Packet Train ( 17, 18) RTCP Packet Train Packet ( 17, 18) 17 19 23 20 21 25 22 26 22 Receiver-side bandwidth limit ( 25, 28) 23 21 18 18 18 18 15 15 Modality send bandwidth limit 60 N Network congestion notification extension 57 10 O
11 P Packet loss notification 51 21 Packet Train Packet 25 Padding 22 61 Peer Info Exchange 26 Picture loss indication extension 58 Policy server bandwidth 52 22 Policy server bandwidth notification 52 13 13 62 R Receiver-side Bandwidth Limit ( 25, 28) 54 10 10 10 12 RTCP 41 42 42 44 43 38 43 44 42 17 28 17 RTCP Packet Pair Packet message ( 17, 17) RTCP Packet Train message ( 17, 18) RTCP Packet Train Packet message ( 17, 18) 17 19 23 20 21 25 22 26 22 Receiver-side bandwidth limit ( 25, 28) 23 21 18 18 18 18 RTP 35 37 36 38 37 35 37 38 36 15 S SDES private extension 56 18 Security 61 61 Sequencing rules 43 37 SSRC change throttling 46 14 Timer events 44 38 Timers 42 36 66 15 Triggered events 42 37 TURN server bandwidth 53 23 TURN server bandwidth notification 53 V 14 13 Video preference 51 21 Video source request extension 59