2 Structures
Section 2.1 defines fields that can appear in a logging message. Not all fields appear in all logging messages, however. Section 2.2 defines the syntax of World Wide Web Consortium (W3C)-based logging messages, and section 2.4 defines the syntax of XML-based logging messages.
Section 2.5 defines the legacy logging message type. Section 2.6 defines the Streaming Log message type. Section 2.7 defines the Rendering Log message type. Section 2.8 defines the Connection Log message type.
Note These sections can also contain variants that supersede the definitions in 2.1.
The information contained in a logging message is always specific to a particular session. The extent of a session is defined by the streaming protocol used by the server. A Rendering Log message (as specified in section 2.7) can be sent without streaming from a server, and, in that case, a session starts when the playback of the playlist starts and stops when the playback of the playlist stops.
Following are some common Augmented Backus-Naur Form (ABNF) constructions, as specified in [RFC4234], that are used throughout this specification. Any ABNF syntax rules that are not defined in [RFC4234] or in this specification are defined in [RFC1945] or [RFC2616].
-
date-year = 4DIGIT ; "19xx" and "20xx" typical date-month = 2DIGIT ; 01 through 12 date-day = 2DIGIT ; 01 through 31 time-hour = 2DIGIT ; 00 through 24 time-min = 2DIGIT ; 00 through 59 time-sec = 2DIGIT ; 00 through 59, 60 if leap second ip_addr = IPv4address | IPv6address ; Defined in Appendix A of RFC3986 ver_major = 1*2DIGIT ver_minor = 1*2DIGIT ["." 1*4DIGIT "." 1*4DIGIT]