Revision Summary Date Revision History Revision Class Comments 6/4/2010 0.1 Major First Release. 7/16/2010 0.1 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 0.1 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 0.2 Minor Clarified the meaning of the technical content. 11/19/2010 0.2 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 0.2 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 0.2 None No changes to the meaning, language, or formatting of the technical content.
3/25/2011 0.2 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 0.2.1 Editorial Changed language and formatting in the technical content. 6/17/2011 0.3 Clarified the meaning of the technical content. 9/23/2011 0.3 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.1 Clarified the meaning of the technical content. 10/25/2012 3.0 Major Updated and revised the technical content. 1/31/2013 3.0 None No changes to the meaning, language,
or formatting of the technical content. 8/8/2013 4.0 Major Updated and revised the technical content. 11/14/2013 5.0 Major Updated and revised the technical content. 2/13/2014 6.0 Major Updated and revised the technical content. 5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 7.0 Major Significantly changed the technical content. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content.
Messages Transport The Manifest Request and Fragment Request messages MUST be represented as HTTP request messages, as specified by the Request rule of , subject to the following constraints: The method MUST be "GET". For the Manifest Request message, the RequestURI MUST adhere to the syntax of the ManifestRequest field, specified in section . For the Fragment Request message, the RequestURI MUST adhere to the syntax of the FragmentRequest field, specified in section . The HTTP-Version SHOULD be HTTP/1.1. The Manifest Response and Fragment Response messages MUST be represented as HTTP response messages, as specified by the Response rule of [RFC2616], subject to the following constraints: The Status-Code SHOULD be 200. For the Manifest Response message, the message body MUST adhere to the syntax of the ManifestResponse field, specified in section . For the Fragment Response message, the message body MUST adhere to the syntax to the FragmentResponse field, specified in section . The HTTP-Version SHOULD be HTTP/1.1. The Live Ingest Request MUST be represented as an HTTP request message, as specified by the Request rule of [RFC2616], subject to the following constraints: The Method MUST be "POST". The "Transfer-Encoding: Chunked" header SHOULD replace the "Content-Length" header. The RequestURI MUST adhere to the syntax of the LiveIngestRequest field, specified in section . The HTTP-Version SHOULD be HTTP/1.1. Message Syntax The Smooth Streaming Transport Protocol defines five of messages: Manifest Request (section ) Manifest Response (section ) Fragment Request (section ) Fragment Response (section ) Live Ingest Request (section ) The following fields are commonly used across the message set. The syntax of each field is specified in Augmented Backus–Naur Form (ABNF) . TRUE: A case-insensitive string value for true, for use in XML attributes.
Index A 52 41 50 9 C 10 60 Client 41 event processing 49 49 47 47 46 44 45 46 45 45 45 45 50 50 41 41 sequencing rules 49 49 47 47 46 50 45 D Data - abstract 41 50 E Event processing client 49 49 47 47 46 51 Examples 55 56 56 55 55 57 56 F 10 44 35 25 33 26 25 26 G 5 H triggered events 45 46 45 45 45 51 53 54 I 58 58 7 53 45 51 5 L 35 35 Local events 50 52 M 13 14 13 14 32 Messages 35 25 26 33 25 26 35
35 13 14 13 14 32 27 26 16 40 40 14 34 34 16 23 11 30 29 28 19 27 11 31 19 27 26 N 6 O Other local events 50 52 7 P 58 9 9 41 54 59 16 R 6 7 6 9 S Security 58 58 Sequencing rules client 49 49 47 47 46 51 Server 50 51 51 51 52 52 50 51 52 51 40 40 14 34 34 10 16 23 36 11 T 30 29 28 Timer events 50 52 Timers 45 51 19 60 27 11 Triggered events client 46 45 45 45 51 Triggered events - higher-layer 45 51 31 U 19 V 10 10