idnits 2.17.1 draft-ietf-cdni-logging-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 10, 2013) is 3845 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2616 (Obsoleted by RFC 7230, RFC 7231, RFC 7232, RFC 7233, RFC 7234, RFC 7235) ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) == Outdated reference: A later version (-14) exists of draft-ietf-cdni-framework-05 == Outdated reference: A later version (-21) exists of draft-ietf-cdni-metadata-02 == Outdated reference: A later version (-17) exists of draft-ietf-cdni-requirements-10 -- Obsolete informational reference (is this intentional?): RFC 2818 (Obsoleted by RFC 9110) Summary: 2 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force F. Le Faucheur, Ed. 3 Internet-Draft Cisco Systems 4 Intended status: Standards Track G. Bertrand, Ed. 5 Expires: April 13, 2014 I. Oprescu, Ed. 6 Orange 7 R. Peterkofsky 8 Skytide, Inc. 9 October 10, 2013 11 CDNI Logging Interface 12 draft-ietf-cdni-logging-07 14 Abstract 16 This memo specifies the Logging interface between a downstream CDN 17 (dCDN) and an upstream CDN (uCDN) that are interconnected as per the 18 CDN Interconnection (CDNI) framework. First, it describes a 19 reference model for CDNI logging. Then, it specifies the CDNI 20 Logging File format and the actual protocol for exchange of CDNI 21 Logging Files. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on April 13, 2014. 40 Copyright Notice 42 Copyright (c) 2013 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 59 1.2. Requirements Language . . . . . . . . . . . . . . . . . . 4 60 2. CDNI Logging Reference Model . . . . . . . . . . . . . . . . 5 61 2.1. CDNI Logging interactions . . . . . . . . . . . . . . . . 5 62 2.2. Overall Logging Chain . . . . . . . . . . . . . . . . . . 8 63 2.2.1. Logging Generation and During-Generation Aggregation 9 64 2.2.2. Logging Collection . . . . . . . . . . . . . . . . . 10 65 2.2.3. Logging Filtering . . . . . . . . . . . . . . . . . . 10 66 2.2.4. Logging Rectification and Post-Generation Aggregation 11 67 2.2.5. Log-Consuming Applications . . . . . . . . . . . . . 11 68 2.2.5.1. Maintenance/Debugging . . . . . . . . . . . . . . 11 69 2.2.5.2. Accounting . . . . . . . . . . . . . . . . . . . 12 70 2.2.5.3. Analytics and Reporting . . . . . . . . . . . . . 12 71 2.2.5.4. Security . . . . . . . . . . . . . . . . . . . . 12 72 2.2.5.5. Legal Logging Duties . . . . . . . . . . . . . . 12 73 2.2.5.6. Notions common to multiple Log Consuming 74 Applications . . . . . . . . . . . . . . . . . . 13 75 3. CDNI Logging File . . . . . . . . . . . . . . . . . . . . . . 15 76 3.1. Rules . . . . . . . . . . . . . . . . . . . . . . . . . . 15 77 3.2. CDNI Logging File Structure . . . . . . . . . . . . . . . 16 78 3.3. CDNI Logging File Directives . . . . . . . . . . . . . . 18 79 3.4. CDNI Logging Records . . . . . . . . . . . . . . . . . . 21 80 3.4.1. HTTP Request Logging Record . . . . . . . . . . . . . 22 81 3.5. CDNI Logging File Example . . . . . . . . . . . . . . . . 29 82 4. CDNI Logging File Exchange Protocol . . . . . . . . . . . . . 30 83 4.1. CDNI Logging Feed . . . . . . . . . . . . . . . . . . . . 30 84 4.1.1. Atom Formatting . . . . . . . . . . . . . . . . . . . 31 85 4.1.2. Updates to Log Files and the Feed . . . . . . . . . . 31 86 4.1.3. Redundant Feeds . . . . . . . . . . . . . . . . . . . 32 87 4.1.4. Example CDNI Logging Feed . . . . . . . . . . . . . . 32 88 4.2. CDNI Logging File Pull . . . . . . . . . . . . . . . . . 33 89 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 90 5.1. CDNI Logging Directive Names Registry . . . . . . . . . . 34 91 5.2. CDNI Logging Record-Types Registry . . . . . . . . . . . 35 92 5.3. CDNI Logging Field Names Registry . . . . . . . . . . . . 35 93 5.4. CDNI Logging MIME Media Type . . . . . . . . . . . . . . 36 94 6. Security Considerations . . . . . . . . . . . . . . . . . . . 36 95 6.1. Authentication, Confidentiality, Integrity Protection . . 36 96 6.2. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 37 98 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 38 99 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 38 100 8.1. Normative References . . . . . . . . . . . . . . . . . . 38 101 8.2. Informative References . . . . . . . . . . . . . . . . . 39 102 Appendix A. Compliance with CDNI Requirements . . . . . . . . . 40 103 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 44 105 1. Introduction 107 This memo specifies the CDNI Logging interface between a downstream 108 CDN (dCDN) and an upstream CDN (uCDN). First, it describes a 109 reference model for CDNI logging. Then, it specifies the CDNI 110 Logging File format and the actual protocol for exchange of CDNI 111 Logging Files. 113 The reader should be familiar with the following documents: 115 o CDNI problem statement [RFC6707] and framework 116 [I-D.ietf-cdni-framework] identify a Logging interface, 118 o Section 8 of [I-D.ietf-cdni-requirements] specifies a set of 119 requirements for Logging, 121 o [RFC6770] outlines real world use-cases for interconnecting CDNs. 122 These use cases require the exchange of Logging information 123 between the dCDN and the uCDN. 125 As stated in [RFC6707], "the CDNI Logging interface enables details 126 of logs or events to be exchanged between interconnected CDNs". 128 The present document describes: 130 o The CDNI Logging reference model (Section 2), 132 o The CDNI Logging File format (Section 3), 134 o The CDNI Logging File Exchange protocol (Section 4). 136 1.1. Terminology 138 In this document, the first letter of each CDNI-specific term is 139 capitalized. We adopt the terminology described in [RFC6707] and 140 [I-D.ietf-cdni-framework], and extend it with the additional terms 141 defined below. 143 For clarity, we use the word "Log" only for referring to internal CDN 144 logs and we use the word "Logging" for any inter-CDN information 145 exchange and processing operations related to CDNI Logging interface. 146 Log and Logging formats may be different. 148 CDN Logging information: logging information generated and collected 149 within a CDN 151 CDNI Logging information: logging information exchanged across CDNs 152 using the CDNI Logging Interface 154 Logging information: logging information generated and collected 155 within a CDN or obtained from another CDN using the CDNI Logging 156 Interface 158 CDNI Logging Field: an atomic element of information that can be 159 included in a CDNI Logging Record. The time an event/task started, 160 the IP address of an End user to whom content was delivered, and the 161 URI of the content delivered are examples of CDNI Logging Fields. 163 CDNI Logging Record: an information record providing information 164 about a specific event. This comprises a collection of CDNI Logging 165 Fields. 167 CDNI Logging File: a file containing CDNI Logging Records, as well as 168 additional information facilitating the processing of the CDNI 169 Logging Records. 171 CDN Reporting: the process of providing the relevant information that 172 will be used to create a formatted content delivery report provided 173 to the CSP in deferred time. Such information typically includes 174 aggregated data that can cover a large period of time (e.g., from 175 hours to several months). Uses of Reporting include the collection 176 of charging data related to CDN services and the computation of Key 177 Performance Indicators (KPIs). 179 CDN Monitoring: the process of providing content delivery information 180 in real-time. Monitoring typically includes data in real time to 181 provide visibility of the deliveries in progress, for service 182 operation purposes. It presents a view of the global health of the 183 services as well as information on usage and performance, for network 184 services supervision and operation management. In particular, 185 monitoring data can be used to generate alarms. 187 1.2. Requirements Language 188 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 189 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 190 document are to be interpreted as described in RFC 2119 [RFC2119]. 192 2. CDNI Logging Reference Model 194 2.1. CDNI Logging interactions 196 The CDNI logging reference model between a given uCDN and a given 197 dCDN involves the following interactions: 199 o customization by the uCDN of the CDNI logging information to be 200 provided by the dCDN to the uCDN (e.g. control of which logging 201 fields are to be communicated to the uCDN for a given task 202 performed by the dCDN, control of which types of events are to be 203 logged). The dCDN takes into account this CDNI logging 204 customization information to determine what logging information to 205 provide to the uCDN, but it may, or may not, take into account 206 this CDNI logging customization information to influence what CDN 207 logging information is to be generated and collected within the 208 dCDN (e.g. even if the uCDN requests a restricted subset of the 209 logging information, the dCDN may elect to generate a broader set 210 of logging information). The mechanism to support the 211 customisation by the uCDN of CDNI Logging information is outside 212 the scope of this document and left for further study. We note 213 that the CDNI Control interface or the CDNI Metadata interface 214 appear as candidate interfaces on which to potentially build such 215 a customisation mechanism in the future. Before such a mechanism 216 is available, the uCDN and dCDN are expected to agree off-line on 217 what CDNI logging information is to be provide by dCDN to UCDN and 218 rely on management plane actions to configure the CDNI Logging 219 functions to generate (respectively, expect) in dCDN 220 (respectively, in uCDN). 222 o generation and collection by the dCDN of logging information 223 related to the completion of any task performed by the dCDN on 224 behalf of the uCDN (e.g., delivery of the content to an end user) 225 or related to events happening in the dCDN that are relevant to 226 the uCDN (e.g., failures or unavailability in dCDN). This takes 227 place within the dCDN and does not directly involve CDNI 228 interfaces. 230 o communication by the dCDN to the uCDN of the logging information 231 collected by the dCDN relevant to the uCDN. This is supported by 232 the CDNI Logging interface and in the scope of the present 233 document. For example, the uCDN may use this logging information 234 to charge the CSP, to perform analytics and monitoring for 235 operational reasons, to provide analytics and monitoring views on 236 its content delivery to the CSP or to perform trouble-shooting. 237 This document exclusively specifies non-real-time exchange of 238 logging information. Closer to real-time exchange of logging 239 information (say sub-minute or sub-second) is outside the scope of 240 the present document and left for further study. This document 241 exclusively specifies exchange of logging information related to 242 content delivery. Exchange of logging information related to 243 operational events (e.g. dCDN request routing function 244 unavailable, content acquisition failure by dCDN) for audit or 245 operational reactive adjustments by uCDN is outside the scope of 246 the present document and left for further study. 248 o customization by the dCDN of the logging to be performed by the 249 uCDN on behalf of the dCDN. The mechanism to support the 250 customisation by the dCDN of CDNI Logging information is outside 251 the scope of this document and left for further study. 253 o generation and collection by the uCDN of logging information 254 related to the completion of any task performed by the uCDN on 255 behalf of the dCDN (e.g., serving of content by uCDN to dCDN for 256 acquisition purposes by dCDN) or related to events happening in 257 the uCDN that are relevant to the dCDN. This takes place within 258 the uCDN and does not directly involve CDNI interfaces. 260 o communication by the uCDN to the dCDN of the logging information 261 collected by the uCDN relevant to the dCDN. For example, the dCDN 262 might potentially benefit from this information for security 263 auditing or content acquisition troubleshooting. This is outside 264 the scope of this document and left for further study. 266 Figure 1 provides an example of CDNI Logging interactions (focusing 267 only on the interactions that are in the scope of this document) in a 268 particular scenario where 4 CDNs are involved in the delivery of 269 content from a given CSP: the uCDN has a CDNI interconnection with 270 dCDN-1 and dCDN-2. In turn, dCDN2 has a CDNI interconnection with 271 dCDN3. In this example, uCDN, dCDN-1, dCDN-2 and dCDN-3 all 272 participate in the delivery of content for the CSP. In this example, 273 the CDNI Logging interface enables the uCDN to obtain logging 274 information from all the dCDNs involved in the delivery. In the 275 example, uCDN uses the Logging data: 277 o to analyze the performance of the delivery operated by the dCDNs 278 and to adjust its operations after the fact (e.g., request 279 routing) as appropriate, 281 o to provide (non real-time) reporting and monitoring information to 282 CSP. 284 For instance, uCDN merges Logging data, extracts relevant KPIs, and 285 presents a formatted report to the CSP, in addition to a bill for the 286 content delivered by uCDN itself or by its dCDNs on his behalf. uCDN 287 may also provide Logging data as raw log files to the CSP, so that 288 the CSP can use its own logging analysis tools. 290 +-----+ 291 | CSP | 292 +-----+ 293 ^ Reporting and monitoring data 294 * Billing 295 ,--*--. 296 Logging ,-' `-. 297 Data =>( uCDN )<= Logging 298 // `-. _,-' \\ Data 299 || `-'-'-' || 300 ,-----. ,-----. 301 ,-' `-. ,-' `-. 302 ( dCDN-1 ) ( dCDN-2 )<== Logging 303 `-. ,-' `-. _,-' \\ Data 304 `--'--' `--'-' || 305 ,-----. 306 ,' `-. 307 ( dCDN-3 ) 308 `. ,-' 309 `--'--' 311 ===> CDNI Logging Interface 312 ***> outside the scope of CDNI 314 Figure 1: Interactions in CDNI Logging Reference Model 316 A dCDN (e.g., dCDN-2) integrates the relevant logging information 317 obtained from its dCDNs (e.g., dCDN-3) in the logging information 318 that it provides to the uCDN, so that the uCDN ultimately obtains all 319 logging information relevant to a CSP for which it acts as the 320 authoritative CDN. 322 Note that the format of Logging information that a CDN provides over 323 the CDNI interface might be different from the one that the CDN uses 324 internally. In this case, the CDN needs to reformat the Logging 325 information before it provides this information to the other CDN over 326 the CDNI Logging interface. Similarly, a CDN might reformat the 327 Logging data that it receives over the CDNI Logging interface before 328 injecting it into its log-consuming applications or before providing 329 some of this logging information to the CSP. Such reformatting 330 operations introduce latency in the logging distribution chain and 331 introduce a processing burden. Therefore, there are benefits in 332 specifying CDNI Logging format that are suitable for use inside CDNs 333 and also are close to the CDN Log formats commonly used in CDNs 334 today. 336 2.2. Overall Logging Chain 338 This section discusses the overall logging chain within and across 339 CDNs to clarify how CDN Logging information is expected to fit in 340 this overall chain. Figure 2 illustrates the overall logging chain 341 within the dCDN, across CDNs using the CDNI Logging interface and 342 within the uCDN. Note that the logging chain illustrated in the 343 Figure is obviously only an example and varies depending on the 344 specific environments. For example, there may be more or less 345 instantiations of each entity (i.e., there may be 4 Log consuming 346 applications in a given CDN). As another example, there may be one 347 instance of Rectification process per Log Consuming Application 348 instead of a shared one. 350 Log Consuming Log Consuming 351 App App 352 /\ /\ 353 | | 354 Rectification-------- 355 /\ 356 | 357 Filtering 358 /\ 359 | 360 Collection uCDN 361 /\ /\ 362 | | 363 | Generation 364 | 365 CDNI Logging --------------------------------------------- 366 exchange 367 /\ Log Consuming Log Consuming 368 | App App 369 | /\ /\ 370 | | | 371 Rectification Rectification--------- 372 /\ /\ 373 | | 374 Filtering 375 /\ 376 | 377 Collection dCDN 378 /\ /\ 379 | | 380 Generation Generation 382 Figure 2: CDNI Logging in the overall Logging Chain 384 The following subsections describe each of the processes potentially 385 involved in the logging chain of Figure 2. 387 2.2.1. Logging Generation and During-Generation Aggregation 389 CDNs typically generate logging information for all significant task 390 completions, events, and failures. Logs are typically generated by 391 many devices in the CDN including the surrogates, the request routing 392 system, and the control system. 394 The amount of Logging information generated can be huge. Therefore, 395 during contract negotiations, interconnected CDNs often agree on a 396 Logging retention duration, and optionally, on a maximum size of the 397 Logging data that the dCDN must keep. If this size is exceeded, the 398 dCDN must alert the uCDN but may not keep more Logs for the 399 considered time period. In addition, CDNs may aggregate logs and 400 transmit only summaries for some categories of operations instead of 401 the full Logging data. Note that such aggregation leads to an 402 information loss, which may be problematic for some usages of Logging 403 (e.g., debugging). 405 [RFC6983] discusses logging for HTTP Adaptive Streaming (HAS). In 406 accordance with the recommendations articulated there, it is expected 407 that a surrogate will generate separate logging information for 408 delivery of each chunk of HAS content. This ensures that separate 409 logging information can then be provided to interconnected CDNs over 410 the CDNI Logging interface. Still in line with the recommendations 411 of [RFC6983], the logging information for per-chunck delivery may 412 include some information (a Content Collection IDentifier and a 413 Session IDentifier) intended to facilitate subsequent post-generation 414 aggregation of per-chunk logs into per-session logs. Note that a CDN 415 may also elect to generate aggregate per-session logs when performing 416 HAS delivery, but this needs to be in addition to, and not instead 417 of, the per-chunk delivery logs. We note that this may be revisited 418 in future versions of this document. 420 Note that in the case of non real-time logging, the trigger of the 421 transmission or generation of the logging file appears to be a 422 synchronous process from a protocol standpoint. The implementation 423 algorithm can choose to enforce a maximum size for the logging file 424 beyond which the transmission is automatically triggered (and thus 425 allow for an asynchronous transmission process). 427 2.2.2. Logging Collection 429 This is the process that continuously collects logs generated by the 430 log-generating entities within a CDN. 432 In a CDNI environment, in addition to collecting logging information 433 from log-generating entities within the local CDN, the Collection 434 process also collects logging information provided by another CDN, or 435 other CDNs, through the CDNI Logging interface. This is illustrated 436 in Figure 2 where we see that the Collection process of the uCDN 437 collects logging information from log-generating entities within the 438 uCDN as well as logging information coming through CDNI Logging 439 exchange with the dCDN through the CDNI Logging interface. 441 2.2.3. Logging Filtering 443 A CDN may require to only present different subset of the whole 444 logging information collected to various log-consuming applications. 445 This is achieved by the Filtering process. 447 In particular, the Filtering process can also filter the right subset 448 of information that needs to be provided to a given interconnected 449 CDN. For example, the filtering process in the dCDN can be used to 450 ensure that only the logging information related to tasks performed 451 on behalf of a given uCDN are made available to that uCDN (thereby 452 filtering all the logging information related to deliveries by the 453 dCDN of content for its own CSPs). Similarly, the Filtering process 454 may filter or partially mask some fields, for example, to protect End 455 Users' privacy when communicating CDNI Logging information to another 456 CDN. Filtering of logging information prior to communication of this 457 information to other CDNs via the CDNI Logging interface requires 458 that the downstream CDN can recognize the set of log records that 459 relate to each interconnected CDN. 461 The CDN will also filter some internal scope information such as 462 information related to its internal alarms (security, failures, load, 463 etc). 465 In some use cases described in [RFC6770], the interconnected CDNs do 466 not want to disclose details on their internal topology. The 467 filtering process can then also filter confidential data on the 468 dCDNs' topology (number of servers, location, etc.). In particular, 469 information about the requests served by every Surrogate may be 470 confidential. Therefore, the Logging information must be protected 471 so that data such as Surrogates' hostnames is not disclosed to the 472 uCDN. In the "Inter-Affiliates Interconnection" use case, this 473 information may be disclosed to the uCDN because both the dCDN and 474 the uCDN are operated by entities of the same group. 476 2.2.4. Logging Rectification and Post-Generation Aggregation 478 If Logging is generated periodically, it is important that the 479 sessions that start in one Logging period and end in another are 480 correctly reported. If they are reported in the starting period, 481 then the Logging of this period will be available only after the end 482 of the session, which delays the Logging generation. 484 A Logging rectification/update mechanism could be useful to reach a 485 good trade-off between the Logging generation delay and the Logging 486 accuracy. Depending on the selected Logging protocol(s), such 487 mechanism may be invaluable for real time Logging, which must be 488 provided rapidly and cannot wait for the end of operations in 489 progress. 491 In the presence of HAS, some log-consuming applications can benefit 492 from aggregate per-session logs. For example, for analytics, per- 493 session logs allow display of session-related trends which are much 494 more meaningful for some types of analysis than chunk-related trends. 495 In the case where the log-generating entities have generated during- 496 generation aggregate logs, those can be used by the applications. In 497 the case where aggregate logs have not been generated, the 498 Rectification process can be extended with a Post-Generation 499 Aggregation process that generates per-session logs from the per- 500 chunk logs, possibly leveraging the information included in the per- 501 chunk logs for that purpose (Content Collection IDentifier and a 502 Session IDentifier). However, in accordance with [RFC6983], this 503 document does not define exchange of such aggregate logs on the CDNI 504 Logging interface. We note that this may be revisited in future 505 versions of this document. 507 2.2.5. Log-Consuming Applications 509 2.2.5.1. Maintenance/Debugging 511 Logging is useful to permit the detection (and limit the risk) of 512 content delivery failures. In particular, Logging facilitates the 513 detection of configuration issues. 515 To detect faults, Logging must enable the reporting of any CDN 516 delivery operation success and failure. The uCDN can summarize such 517 information into KPIs. For instance, Logging needs to allow the 518 computation of the number of times, during a given time period, that 519 content delivery related to a specific service succeeds/fails. 521 Logging enables the CDN providers to identify and troubleshoot 522 performance degradations. In particular, Logging enables the 523 communication of traffic data (e.g., the amount of traffic that has 524 been forwarded by a dCDN on behalf of an uCDN over a given period of 525 time), which is particularly useful for CDN and network planning 526 operations. 528 2.2.5.2. Accounting 530 Logging is essential for accounting, to permit inter-CDN billing and 531 CSP billing by uCDNs. For instance, Logging information provided by 532 dCDNs enables the uCDN to compute the total amount of traffic 533 delivered by every dCDN for a particular Content Provider, as well 534 as, the associated bandwidth usage (e.g., peak, 95th percentile), and 535 the maximum number of simultaneous sessions over a given period of 536 time. 538 2.2.5.3. Analytics and Reporting 540 The goal of analytics is to gather any relevant information to track 541 audience, analyze user behavior, and monitor the performance and 542 quality of content delivery. For instance, Logging enables the CDN 543 providers to report on content consumption (e.g., delivered sessions 544 per content) in a specific geographic area. 546 The goal of reporting is to gather any relevant information to 547 monitor the performance and quality of content delivery and allow 548 detection of delivery issues. For instance, reporting could track 549 the average delivery throughput experienced by End-Users in a given 550 region for a specific CSP or content set over a period of time. 552 2.2.5.4. Security 554 The goal of security is to prevent and monitor unauthorized access, 555 misuse, modification, and denial of access of a service. A set of 556 information is logged for security purposes. In particular, a record 557 of access to content is usually collected to permit the CSP to detect 558 infringements of content delivery policies and other abnormal End 559 User behaviors. 561 2.2.5.5. Legal Logging Duties 562 Depending on the country considered, the CDNs may have to retain 563 specific Logging information during a legal retention period, to 564 comply with judicial requisitions. 566 2.2.5.6. Notions common to multiple Log Consuming Applications 568 2.2.5.6.1. Logging Information Views 570 Within a given log-consuming application, different views may be 571 provided to different users depending on privacy, business, and 572 scalability constraints. 574 For example, an analytics tool run by the uCDN can provide one view 575 to an uCDN operator that exploits all the logging information 576 available to the uCDN, while the tool may provide a different view to 577 each CSP exploiting only the logging information related to the 578 content of the given CSP. 580 As another example, maintenance and debugging tools may provide 581 different views to different CDN operators, based on their 582 operational role. 584 2.2.5.6.2. Key Performance Indicators (KPIs) 586 This section presents, for explanatory purposes, a non-exhaustive 587 list of Key Performance Indicators (KPIs) that can be extracted/ 588 produced from logs. 590 Multiple log-consuming applications, such as analytics, monitoring, 591 and maintenance applications, often compute and track such KPIs. 593 In a CDNI environment, depending on the situation, these KPIs may be 594 computed by the uCDN or by the dCDN. But it is usually the uCDN that 595 computes KPIs, because uCDN and dCDN may have different definitions 596 of the KPIs and the computation of some KPIs requires a vision of all 597 the deliveries performed by the uCDN and all its dCDNs. 599 Here is a list of important examples of KPIs: 601 o Number of delivery requests received from End-Users in a given 602 region for each piece of content, during a given period of time 603 (e.g., hour/day/week/month) 605 o Percentage of delivery successes/failures among the aforementioned 606 requests 608 o Number of failures listed by failure type (e.g., HTTP error code) 609 for requests received from End Users in a given region and for 610 each piece of content, during a given period of time (e.g., hour/ 611 day/week/month) 613 o Number and cause of premature delivery termination for End Users 614 in a given region and for each piece of content, during a given 615 period of time (e.g., hour/day/week/month) 617 o Maximum and mean number of simultaneous sessions established by 618 End Users in a given region, for a given Content Provider, and 619 during a given period of time (e.g., hour/day/week/month) 621 o Volume of traffic delivered for sessions established by End Users 622 in a given region, for a given Content Provider, and during a 623 given period of time (e.g., hour/day/week/month) 625 o Maximum, mean, and minimum delivery throughput for sessions 626 established by End Users in a given region, for a given Content 627 Provider, and during a given period of time (e.g., hour/day/week/ 628 month) 630 o Cache-hit and byte-hit ratios for requests received from End Users 631 in a given region for each piece of content, during a given period 632 of time (e.g., hour/day/week/month) 634 o Top 10 of the most popularly requested content (during a given day 635 /week/month), 637 o Terminal type (mobile, PC, STB, if this information can be 638 acquired from the browser type header, for example). 640 Additional KPIs can be computed from other sources of information 641 than the Logging, for instance, data collected by a content portal or 642 by specific client-side application programming interfaces. Such 643 KPIs are out of scope for the present memo. 645 The KPIs used depend strongly on the considered log-consuming 646 application -- the CDN operator may be interested in different 647 metrics than the CSP is. In particular, CDN operators are often 648 interested in delivery and acquisition performance KPIs, information 649 related to Surrogates' performance, caching information to evaluate 650 the cache-hit ratio, information about the delivered file size to 651 compute the volume of content delivered during peak hour, etc. 653 Some of the KPIs, for instance those providing an instantaneous 654 vision of the active sessions for a given CSP's content, are useful 655 essentially if they are provided in real-time. By contrast, some 656 other KPIs, such as the one averaged on a long period of time, can be 657 provided in non-real time. 659 3. CDNI Logging File 661 3.1. Rules 663 This specification uses the Augmented Backus-Naur Form (ABNF) 664 notation and core rules of [RFC5234]. In particular, the present 665 document uses the following rules from [RFC5234]: 667 CR = %x0D ; carriage return 669 DIGIT = %x30-39 ; 0-9 671 DQUOTE = %x22 ; " (Double Quote) 673 CRLF = CR LF ; Internet standard newline 675 HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F" 677 HTAB = %x09 ; horizontal tab 679 LF = %x0A ; linefeed 681 OCTET = %x00-FF ; 8 bits of data 683 The present document also uses the following rules from [RFC3986]: 685 host = as specified in section 3.2.2 of [RFC3986]. 687 IPv4address = as specified in section 3.2.2 of [RFC3986]. 689 IPv6address = as specified in section 3.2.2 of [RFC3986]. 691 The present document also defines the folowing additional rules: 693 ADDRESS = IPv4address / IPv6address 695 DATE = 4DIGIT "-" 2DIGIT "-" 2DIGIT 697 Dates are recorded in the format YYYY-MM-DD where YYYY, MM and 698 DD stand for the numeric year, month and day respectively. All 699 dates are specified in Universal Time Coordinated (UTC). 701 DEC = 1*DIGIT ["." *DIGIT] 703 QSTRING = DQUOTE *NDQUOTE DQUOTE ; where 704 NDQUOTE = / 2DQUOTE ; whereby a 705 DQUOTE is conveyed inside a QSTRING unambiguously by repeating 706 it. 708 NHTABSTRING = *NHTAB ; where 710 NHTAB = 712 TIME = 2DIGIT ":" 2DIGIT ":" 2DIGIT ["." *DIGIT] 714 Times are recorded in the form HH:MM:SS or HH:MM:SS.S where HH 715 is the hour in 24 hour format, MM is minutes and SS is seconds. 716 All times are specified in Universal Time Coordinated (UTC). 718 3.2. CDNI Logging File Structure 720 As defined in Section 1.1 a CDNI logging field is as an atomic 721 logging information element and a CDNI Logging Record is a collection 722 of CDNI Logging Fields containing all logging information 723 corresponding to a single logging event. This document defines a 724 third level of structure, the CDNI Logging File, that is a collection 725 of CDNI Logging Records. This structure is illustrated in Figure 3. 726 The use of a file structure for transfer of CDNI Logging information 727 is selected since this is the most common practise today for exchange 728 of logging information within and across CDNs. 730 +----------------------------------------------------------+ 731 |CDNI Logging File | 732 | | 733 | #Directive 1 | 734 | #Directive 2 | 735 | ... | 736 | #Directive P | 737 | | 738 | +------------------------------------------------------+ | 739 | |CDNI Logging Record 1 | | 740 | | +-------------+ +-------------+ +-------------+ | | 741 | | |CDNI Logging | |CDNI Logging | ... |CDNI Logging | | | 742 | | | Field 1 | | Field 2 | | Field N | | | 743 | | +-------------+ +-------------+ +-------------+ | | 744 | +------------------------------------------------------+ | 745 | | 746 | +------------------------------------------------------+ | 747 | |CDNI Logging Record 2 | | 748 | | +-------------+ +-------------+ +-------------+ | | 749 | | |CDNI Logging | |CDNI Logging | ... |CDNI Logging | | | 750 | | | Field 1 | | Field 2 | | Field N | | | 751 | | +-------------+ +-------------+ +-------------+ | | 752 | +------------------------------------------------------+ | 753 | | 754 | ... | 755 | | 756 | #Directive P+1 | 757 | | 758 | ... | 759 | | 760 | +------------------------------------------------------+ | 761 | |CDNI Logging Record M | | 762 | | +-------------+ +-------------+ +-------------+ | | 763 | | |CDNI Logging | |CDNI Logging | ... |CDNI Logging | | | 764 | | | Field 1 | | Field 2 | | Field N | | | 765 | | +-------------+ +-------------+ +-------------+ | | 766 | +------------------------------------------------------+ | 767 | | 768 | | 769 | #Directive P+Q | 770 +----------------------------------------------------------+ 772 Figure 3: Structure of Logging Files 774 The CDNI Logging File format is inspired from the W3C Extended Log 775 File Format [ELF]. However, it is fully specified by the present 776 document. Where the present document differs from the W3C Extended 777 Log File Format, an implementation of CDNI Logging MUST comply with 778 the present document. 780 Using a format that resembles the W3C Extended Log File Format is 781 intended to keep CDNI logging format close to intra-CDN logging 782 format commonly used in CDNs today, thereby minimizing systematic 783 translation at CDN/CDNI boundary. 785 A CDNI Logging File MUST contain a sequence of lines containing US- 786 ASCII characters [CHAR_SET] terminated by CRLF. 788 Each line of a CDNI Logging File MUST contain either a directive or a 789 CDNI Logging Record. 791 Directives record information about the CDNI Logging process itself. 792 Lines containing directives MUST begin with the "#" character. 793 Directives are specified in Section 3.3. 795 Logging Records provide actual details of the logged event. Logging 796 Records are specified in Section 3.4. 798 The CDNI File structure is defined by the following rules: 800 DIRLINE = "#" directive CRLF 802 DIRGROUP = 1*DIRLINE 804 RECLINE = CRLF 806 RECGROUP = *RECLINE 808 = 1* 810 3.3. CDNI Logging File Directives 812 The CDNI Logging File directives are defined by the following rules: 814 directive = DIRNAME ":" HTAB DIRVAL 816 DIRNAME = any CDNI Logging Directive name registered in the CDNI 817 Logging Directive Names registry (Section 5.1). 819 DIRVAL = 822 An implementation of the CDNI Logging interface MUST support all of 823 the following directives, listed below by their directive name: 825 o Version: 827 * format: "CDNI" "/" 1*DIGIT "." 1*DIGIT 829 * directive value: indicates the version of the CDNI Logging File 830 format. The value MUST be "CDNI/1.0" for the version specified 831 in the present document. 833 * occurrence: there MUST be one and only one instance of this 834 directive per CDNI Logging File. It MUST be the first line of 835 the CDNI Logging file. 837 o UUID: 839 * format: NHTABSTRING 841 * directive value: this a Universally Unique IDentifier (UUID) 842 from the UUID Uniform Resource Name (URN) namespace specified 843 in [RFC4122]) for the CDNI Logging File . 845 * occurrence: there MUST be one and only one instance of this 846 directive per CDNI Logging File. 848 o Claimed-Origin: 850 * format: host 852 * directive value: this contains the claimed identification of 853 the entity transmitting the CDNI Logging File (e.g. the host in 854 a dCDN supporting the CDNI Logging interface) or the entity 855 responsible for transmitting the CDNI Logging File (e.g. the 856 dCDN). 858 * occurrence: there MUST be zero or one instance of this 859 directive per CDNI Logging File. This directive MAY be 860 included by the dCDN. It MUST NOT be included or modified by 861 the uCDN. 863 o Verified-Origin: 865 * format: host 867 * directive value: this contains the identification, as 868 established by the entity receiving the CDNI Logging file, of 869 the entity transmitting the CDNI Logging File (e.g. the host in 870 a dCDN supporting the CDNI Logging interface) or the entity 871 responsible for transmitting the CDNI Logging File (e.g. the 872 dCDN). 874 * occurrence: there MUST be zero or one instance of this 875 directive per CDNI Logging File. This directive MAY be added 876 by the uCDN (e.g. before storing the CDNI Logging File). It 877 MUST NOT be included by the dCDN. The mechanisms used by the 878 uCDN to establish and validate the entity responsible for the 879 CDNI Logging File is outside the scope of the present document. 880 We observe that, in particular, this may be achieved through 881 authentication mechanisms that are part of the CDNI Logging 882 File pull mechanism (Section 4.2). 884 o Record-Type: 886 * format: NHTABSTRING 888 * directive value: indicates the type of the CDNI Logging Records 889 that follow this directive, until another Record-Type directive 890 (or the end of the CDNI Logging File). This can be any CDNI 891 Logging Record type registered in the CDNI Logging Record-types 892 registry (Section 5.2). "cdni_http_request_v1" MUST be 893 indicated as the Record-Type directive value for CDNI Logging 894 records corresponding to HTTP request (e.g. a HTTP delivery 895 request) as specified in Section 3.4.1. 897 * occurrence: there MUST be at least one instance of this 898 directive per CDNI Logging File. The first instance of this 899 directive MUST precede a Fields directive and precede any CDNI 900 Logging Record. 902 o Fields: 904 * format: FIENAME * ; where FIENAME can take any 905 CDNI Logging field name registered in the CDNI Logging Field 906 Names registry (Section 5.3). 908 * directive value: this lists the names of all the fields for 909 which a value is to appear in the CDNI Logging Records that 910 follow the instance of this directive (until another instance 911 of this directive). The names of the fields, as well as their 912 possible occurrences, are specified for each type of CDNI 913 Logging Records in Section 3.4. 915 * occurrence: there MUST be at least one instance of this 916 directive per Record-Type directive. The first instance of 917 this directive for a given Record-Type MUST appear before any 918 CDNI Logging Record for this Record-Type. 920 o Integrity-Hash: 922 * format: 32HEXDIG 924 * directive value: This directive permits the detection of a 925 corrupted CDNI Logging File. This can be useful, for instance, 926 if a problem occurs on the filesystem of the dCDN Logging 927 system and leads to a truncation of a logging file. The valid 928 Integrity-Hash value is included in this directive by the 929 entity that transmits the CDNI Logging File. It is computed by 930 applying the MD5 ([RFC1321]) cryptographic hash function on the 931 CDNI Logging File, including all the directives and logging 932 records, up to the Intergrity-Hash directive itself, excluding 933 the Integrity-Hash directive itself. The Integrity-Hash value 934 is represented as a US-ASCII encoded hexadecimal number, 32 935 digits long (representing a 128 bit hash value). The entity 936 receiving the CDNI Logging File also computes in a similar way 937 the MD5 hash on the received CDNI Logging File and compares 938 this hash to the value of the Integrity-Hash directive. If the 939 two values are equal, then the received CDNI Logging File MUST 940 be considered non-corrupted. If the two values are different, 941 the received CDNI Logging File MUST be considered corrupted. 942 The behavior of the entity that received a corrupted CDNI 943 Logging File is outside the scope of this specification; we 944 note that the entity MAY attempt to pull again the same CDNI 945 Logging file from the transmitting entity. If the entity 946 receiving the CDNI Logging File adds a Verified-Origin 947 directive, it MUST recompute and update the Integrity-Hash 948 directive so it also protects the added Verified-Origin 949 directive. 951 * occurrence: there MUST be zero or one instance of this 952 directive. There SHOULD be one instance of this directive. 953 One situation where that directive could be omitted is where 954 integrity protection is already provided via another mechanism 955 (for example if an integrity hash is associated to the CDNI 956 Logging file out of band through the CDNI Logging Logging Feed 957 Section 4.1 leveraging ATOM extensions such as those proposed 958 in [I-D.snell-atompub-link-extensions]. When present, this 959 field MUST be the last line of the CDNI Logging File. 961 3.4. CDNI Logging Records 963 A CDNI Logging Record consists of a sequence of CDNI Logging Fields 964 relating to that single CDNI Logging Record. 966 CDNI Logging Fields MUST be separated by the "horizontal tabulation 967 (HTAB)" character. 969 To facilitate readability, a prefix scheme is used for CDNI Logging 970 field names in a similar way to the one used in W3C Extended Log File 971 Format [ELF] . The semantics of the prefix in the present document 972 is: 974 o c: refers to the User Agent that issues the request (corresponds 975 to the "client" of W3C Extended Log Format) 977 o d: refers to the dCDN (relative to a given CDN acting as a uCDN) 979 o s: refers to the dCDN Surrogate that serves the request 980 (corresponds to the "server" of W3C Extended Log Format) 982 o u: refers to the uCDN (relative to a given CDN acting as a dCDN) 984 o cs: refers to communication from the User-Agent towards the dCDN 985 Surrogate 987 o sc: refers to communication from the dCDN Surrogate towards the 988 User-Agent 990 An implementation of the CDNI Logging interface as per the present 991 specification MUST support the CDNI HTTP Delivery Records as 992 specified in Section 3.4.1. 994 A CDNI Logging Record is defined by the following rules: 996 FIEVAL = 998 = FIEVAL * ; where FIEVAL 999 contains the CDNI Logging field values corresponding to the CDNI 1000 Logging field names (FIENAME) listed is the last Fields directive 1001 predecing the present CDNI Logging Record. 1003 3.4.1. HTTP Request Logging Record 1005 The HTTP Request Logging Record is a CDNI Logging Record of Record- 1006 Type "cdni_http_request_v1". It contains the following CDNI Logging 1007 Fields, listed by their field name: 1009 o date: 1011 * format: DATE 1013 * field value: the date at which the processing of request 1014 completed on the Surrogate. 1016 * occurrence: there MUST be one and only one instance of this 1017 field. 1019 o time: 1021 * format: TIME 1023 * field value: the time at which the processing of request 1024 completed on the Surrogate. 1026 * occurrence: there MUST be one and only one instance of this 1027 field. 1029 o time-taken: 1031 * format: DEC 1033 * field value: decimal value of the duration, in seconds, between 1034 the start of the processing of the request and the completion 1035 of the request processing (e.g. completion of delivery) by the 1036 Surrogate. 1038 * occurrence: there MUST be one and only one instance of this 1039 field. 1041 o c-ip: 1043 * format: ADDRESS 1045 * field value: the source IPv4 or IPv6 address (i.e. the "client" 1046 address) in the request received by the Surrogate. 1048 * occurrence: there MUST be one and only one instance of this 1049 field. 1051 o c-ip-anonimizing: 1053 * format: 1*DIGIT 1055 * field value: the number of rightmost bits of the address in the 1056 c-ip field that are zeroed-out in order to anonymize the 1057 logging record. The mechanism by which the two ends of the 1058 CDNI Logging interface agree on whether anonimization is to be 1059 supported and the number of bits that need to be zeroed-out for 1060 this purpose are outside the scope of the present document. 1062 * occurrence: there MUST be zero or one instance of this field. 1064 o c-port: 1066 * format: 1*DIGIT 1068 * field value: the source TCP port (i.e. the "client" port) in 1069 the request received by the Surrogate. 1071 * occurrence: there MUST be zero or exactly one instance of this 1072 field. 1074 o s-ip: 1076 * format: ADDRESS 1078 * field value: the IPv4 or IPv6 address of the Surrogate that 1079 served the request (i.e. the "server" address). 1081 * occurrence: there MUST be zero or exactly one instance of this 1082 field. 1084 o s-hostname: 1086 * format: host 1088 * field value: the hostname of the Surrogate that served the 1089 request (i.e. the "server" hostname). 1091 * occurrence: there MUST be zero or exactly one instance of this 1092 field. 1094 o s-port: 1096 * format: 1*DIGIT 1098 * field value: the destination TCP port (i.e. the "server" port) 1099 in the request received by the Surrogate. 1101 * occurrence: there MUST be zero or exactly one instance of this 1102 field. 1104 o cs-method: 1106 * format: NHTABSTRING 1108 * field value: this is the HTTP method of the HTTP request 1109 received by the Surrogate. 1111 * occurrence: There MUST be one and only one instance of this 1112 field. 1114 o cs-uri: 1116 * format: NHTABSTRING 1118 * field value: this is the complete URL of the request received 1119 by the Surrogate. It is exactly in the format of a http_URL 1120 specified in [RFC2616]) or, when the request was a HTTPS 1121 request ([RFC2818]), it is in the format of a http_URL but with 1122 the scheme part set to "https" instead of "http". 1124 * occurrence: there MUST be zero or exactly one instance of this 1125 field. 1127 o u-uri: 1129 * format: NHTABSTRING 1131 * field value: this is a complete URL, derived from the complete 1132 URI of the request received by the Surrogate (i.e. the cs-uri) 1133 but transformed by the entity generating or transmitting the 1134 CDNI Logging Record, in a way that is agreed upon between the 1135 two ends of the CDNI Logging interface, so the transformed URI 1136 is meaningful to the uCDN. For example, the two ends of the 1137 CDNI Logging interface could agree that the u-uri is 1138 constructed from the cs-uri by removing the part of the 1139 hostname that exposes which individual Surrogate actually 1140 performed the delivery. The details of modification performed 1141 to generate the u-uri, as well as the mechanism to agree on 1142 these modifications between the two sides of the CDNI Logging 1143 interface are outside the scope of the present document. 1145 * occurrence: there MUST be one and only one instance of this 1146 field. 1148 o protocol: 1150 * format: NHTABSTRING 1152 * field value: this is value of the HTTP-Version field as 1153 specified in [RFC2616] of the Request-Line of the request 1154 received by the Surrogate (e.g. "HTTP/1.1"). 1156 * occurrence: there MUST be one and only one instance of this 1157 field. 1159 o sc-status: 1161 * format: 3DIGIT 1163 * field value: this is the HTTP Status-Code in the HTTP response 1164 from the Surrogate. 1166 * occurrence: There MUST be one and only one instance of this 1167 field. 1169 o sc-total-bytes: 1171 * format: 1*DIGIT 1173 * field value: this is the total number of bytes of the HTTP 1174 response sent by the Surrogate in response to the request. 1175 This includes the bytes of the Status-Line (including HTTP 1176 headers) and of the message-body. 1178 * occurrence: There MUST be one and only one instance of this 1179 field. 1181 o sc-entity-bytes: 1183 * format: 1*DIGIT 1185 * field value: this is the number of bytes of the message-body in 1186 the HTTP response sent by the Surrogate in response to the 1187 request. This does not include the bytes of the Status-Line 1188 (and therefore does not include the bytes of the HTTP headers). 1190 * occurrence: there MUST be zero or exactly one instance of this 1191 field. 1193 o cs(): 1195 * format: QSTRING 1197 * field value: the value of the HTTP header (identified by the 1198 in the CDNI Logging field name) as it 1199 appears in the request processed by the Surrogate. For 1200 example, when the CDNI Logging field name (FIENAME) listed in 1201 the prededing Fields directive is "cs(User-Agent"), this CDNI 1202 Logging field value contains the value of the User-Agent HTTP 1203 header as received by the Surrogate in the request it 1204 processed. 1206 * occurrence: there MUST be zero, one or any number of instance 1207 of this field. 1209 o sc(): 1211 * format: QSTRING 1213 * field value: the value of the HTTP header (identified by the 1214 in the CDNI Logging field name) as it 1215 appears in the response issued by the Surrogate to serve the 1216 request. 1218 * occurrence: there MUST be zero, one or any number of instance 1219 of this field. 1221 o s-ccid: 1223 * format: QSTRING 1225 * field value: this contains the value of the Content Collection 1226 IDentifier associated by the uCDN to the content served by the 1227 Surrogate via the CDNI Metadata interface 1228 ([I-D.ietf-cdni-metadata]). 1230 * occurrence: there MUST be zero or exactly one instance of this 1231 field. 1233 o s-sid: 1235 * format: QSTRING 1237 * field value: this contains the value of a Session IDentifier 1238 generated by the dCDN for a specific HTTP Adaptive Streaming 1239 (HAS) session and whose value is included in the Logging record 1240 for every content chunk delivery of that session in view of 1241 facilitating the later correlation of all the per content chunk 1242 log records of a given HAS session. See section 3.4.2.2. of 1243 [RFC6983] for more discussion on the concept of Session 1244 IDentifier. 1246 * occurrence: there MUST be zero or exactly one instance of this 1247 field. 1249 o s-cached: 1251 * format: 1DIGIT 1253 * field value: this characterises whether the Surrogate served 1254 the request using content already stored on its local cache or 1255 not. The allowed values are "0" (for miss) and "1" (for hit). 1256 "1" MUST be used when the Surrogate did serve the request using 1257 exclusively content already stored on its local cache. "0" MUST 1258 be used otherwise (including cases where the Surrogate served 1259 the request using some, but not all, content already stored on 1260 its local cache). Note that a "0" only means a cache miss in 1261 the Surrogate and does not provide any information on whether 1262 the content was already stored, or not, in another device of 1263 the dCDN i.e. whether this was a "dCDN hit" or "dCDN miss". 1265 * occurrence: there MUST be zero or exactly one instance of this 1266 field. 1268 The "Fields" directive corresponding to a HTTP Request Logging Record 1269 MUST list all the fields name whose occurrence is specified above as 1270 "There MUST be one and only one instance of this field". The 1271 corresponding fields value MUST be present in every HTTP Request 1272 Logging Record. 1274 The "Fields" directive corresponding to a HTTP Request Logging Record 1275 MAY list all the fields value whose occurrence is specified above as 1276 "there MUST be zero or exactly one instance of this field" or "there 1277 MUST be zero, one or any number of instance of this field". The set 1278 of such fields name actually listed in the "Fields" directive is 1279 selected by the implementation generating the CDNI Logging File based 1280 on agreements between the interconnected CDNs established through 1281 mechanisms outside the scope of this specification (e.g. contractual 1282 agreements). When such a field name is not listed in the "Fields" 1283 directive, the corresponding field value MUST NOT be included in the 1284 Logging Record. When such a field name is listed in the "Fields" 1285 directive, the corresponding field value MUST be included in the 1286 Logging Record; in that case, if the value for the field is not 1287 available, this MUST be conveyed via a dash character ("-"). 1289 The fields name listed in the "Fields" directive MAY be listed in the 1290 order in which they are listed in Section 3.4.1 or MAY be listed in 1291 any other order. 1293 A dCDN-side implementation of the CDNI Logging interface MUST support 1294 the ability to include valid values for the following Logging Fields 1295 in a CDNI Logging Record of Record-Type "cdni_http_request_v1": 1297 o date 1299 o time 1301 o time-taken 1303 o c-ip 1305 o c-port 1307 o s-ip 1309 o s-hostname 1311 o s-port 1313 o cs- method 1315 o cs-uri 1317 o u-uri 1319 o protocol 1321 o sc-status 1323 o sc- total-bytes 1325 o sc-entity-bytes 1327 o cs() 1329 o sc() 1330 o s-cached 1332 A dCDN-side implementation of the CDNI Logging interface MAY support 1333 the ability to include valid values for the following Logging Fields 1334 in a CDNI Logging Record of Record-Type "cdni_http_request_v1": 1336 o c-ip-anonimizing 1338 o s-ccid 1340 o s-sid 1342 An uCDN-side implementation of the CDNI Logging interface MUST be 1343 able to accept CDNI Logging Files with CDNI Logging Records of 1344 Record-Type "cdni_http_request_v1" containing any CDNI Logging Field 1345 defined in Section 3.4.1 as long as the CDNI Logging Record and the 1346 CDNI Logging File are compliant with the present document. 1348 3.5. CDNI Logging File Example 1350 #Version:CDNI/1.0 1352 #UUID:"urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6" 1354 #Claimed-Origin:cdni-logging-entity.dcdn.example.com 1356 #Record-Type:cdni_http_request_v1 1358 #Fields:datetimetime-takenc-ipcs- 1359 methodu-uriprotocolsc-statussc-total- 1360 bytescs(User-Agent)cs(Referer)s-cached 1362 2013-05-1700:38:06.8259.05810.5.7.1GETh 1363 ttp://cdni-ucdn.dcdn.example.com/video/movie100.mp4HTTP/ 1364 1.12006729891"Mozilla/5.0 (Windows; U; Windows NT 1365 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 1366 Safari /533.4""host1.example.com"1 1368 2013-05-1700:39:09.14515.3210.5.10.5GET 1369 http://cdni-ucdn.dcdn.example.com/video/movie118.mp4HTTP/ 1370 1.120015799210"Mozilla/5.0 (Windows; U; Windows NT 1371 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 1372 Safari /533.4""host1.example.com"1 1373 2013-05-1700:42:53.43752.87910.5.10.5GEThttp://cdni-ucdn.dcdn.example.com/video/picture11.mp4HTTP/ 1375 1.020097234724"Mozilla/5.0 (Windows; U; Windows NT 1376 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 1377 Safari /533.4""host5.example.com"0 1379 #Integrity-Hash: 9e107d9d372bb6826bd81d3542a419d6 [Editor's Note: 1380 include the correct MD5-hash value for the actual example] 1382 4. CDNI Logging File Exchange Protocol 1384 This document specifies a protocol for the exchange of CDNI Logging 1385 Files as specified in Section 3. 1387 This protocol comprises: 1389 o a CDNI Logging feed, allowing the dCDN to notify the uCDN about 1390 the CDNI Logging files that can be retrieved by that uCDN from the 1391 dCDN, as well as all the information necessary for retrieving each 1392 of these CDNI Logging File. The CDNI Logging feed is specified in 1393 Section 4.1. 1395 o a CDNI Logging File pull mechanism, allowing the uCDN to obtain 1396 from the dCDN a given CDNI Logging File at the uCDN convenience. 1397 The CDNI Logging File pull mechanisms is specified in Section 4.2. 1399 An implementation of the CDNI Logging interface as per the present 1400 document generating CDNI Logging file (i.e. on the dCDN side) MUST 1401 support the server side of the CDNI Logging feed and the server side 1402 of the CDNI Logging pull mechanism. 1404 An implementation of the CDNI Logging interface as per the present 1405 document consuming CDNI Logging file (i.e. on the uCDN side) MUST 1406 support the client side of the CDNI Logging feed and the client side 1407 of the CDNI Logging pull mechanism. 1409 We note that implementations of the CDNI Logging interface MAY also 1410 support other mechanisms to exchange CDNI Logging Files, for example 1411 in view of exchanging logging information with minimum time-lag (e.g. 1412 sub-minute or sub-second) between when the event occurred in the dCDN 1413 and when the corresponding Logging Record is made available to the 1414 uCDN (e.g. for log-consuming applications requiring extremely fresh 1415 logging information such as near-real-time content delivery 1416 monitoring). Such mechanisms are outside the scope of the present 1417 document but might be defined in future version of this document . 1419 4.1. CDNI Logging Feed 1420 The server-side implementation of the CDNI Logging feed MUST produce 1421 an Atom feed [RFC4287]. This feed is used to advertise log files 1422 that are available for the client-side to retrieve using the CDNI 1423 Logging pull mechanism. 1425 4.1.1. Atom Formatting 1427 A CDNI Logging feed MUST be structured as an Archived feed, as 1428 defined in [RFC5005], and MUST be formatted in Atom [RFC4287]. This 1429 means it consists of a subscription document that is regularly 1430 updated as new CDNI logging files become available, and information 1431 about older CDNI Logging files is moved into archive documents. Once 1432 created, archive documents are never modified. 1434 Each CDNI Logging file listed in an Atom feed MUST be described in an 1435 atom:entry container element. 1437 The atom:entry MUST contain an atom:content element whose "src" 1438 attribute is a link to the CDNI Logging file and whose "type" 1439 attribute is the MIME Media Type indicating that the entry is a CDNI 1440 Logging File. We define this MIME Media Type as "application/ 1441 cdni.LoggingFile" (See Section 5.4). 1443 For compatibility with some Atom feed readers the atom:entry MAY also 1444 contain an atom:link entry whose "href" attribute is a link to the 1445 CDNI Logging file and whose "type" attribute is the MIME Media Type 1446 indicating that the entry is a CDNI Logging File using the 1447 "application/cdni.LoggingFile" MIME Media Type (See Section 5.4). 1449 The IRI used in the atom:id of the atom:entry MUST contain the UUID 1450 of the CDNI Logging file. 1452 The atom:updated in the atom:entry MUST indicate the time at which 1453 the CDNI Logging file was last updated. 1455 4.1.2. Updates to Log Files and the Feed 1457 CDNI Logging files MUST NOT be modified by the dCDN once published in 1458 the CDNI Logging feed. 1460 The frequency with which the subscription feed is updated, the period 1461 of time covered by each CDNI Logging file or each archive document, 1462 and timeliness of publishing of CDNI Logging files is outside the 1463 scope of the present document and is expected to be agreed upon by 1464 uCDN and dCDN via other means (e.g. human agreement). 1466 The server-side implementation MUST retain, and be ready to serve, 1467 any CDNI Logging File currently published by the server-side in the 1468 subscription document of the CDNI Logging Feed. 1470 The server-side implementation SHOULD use HTTP cache control headers 1471 on the subscription feed to indicate the frequency at which the 1472 client-side is to poll for updates. 1474 4.1.3. Redundant Feeds 1476 The server-side implementation MAY present more than one CDNI Logging 1477 feed and for redundancy, CDNI Logging files MAY be published in more 1478 than one feed. 1480 A client-side implementation MAY support such redundant CDNI Logging 1481 feeds. If it supports redundant CDNI Logging feed, the client-side 1482 SHOULD use the UUID of the CDNI Logging file, presented in the 1483 atom:id element of the Atom feed, to avoid uncessarily pulling and 1484 storing each CDNI Logging file more than once. 1486 4.1.4. Example CDNI Logging Feed 1488 Figure 4 illustrates an example of the subscription document of a 1489 CDNI Logging feed. 1491 1492 > 1494 CDNI Logging Feed 1495 2013-03-23T16:21:11Z 1496 urn:uuid:663ae677-40fb-e99a-049d-c5642916b8ce 1497 1499 1501 1503 CDNI Log Feed 1504 Generator 1505 dcdn.example 1506 1507 CDNI Logging File for uCDN at 1508 2013-03-23 14:55:00 1509 urn:uuid:12345678-1234-abcd-00aa-01234567abcd 1510 2013-03-23T14:55:00Z 1511 1515 CDNI Logging File for uCDN at 1516 2013-03-23 14:55:00 1517 1518 1519 CDNI Logging File for uCDN at 1520 2013-03-23 15:55:00 1521 urn:uuid:87654321-4321-dcba-aa00-dcba7654321 1522 2013-03-23T15:55:00Z 1523 1526 CDNI Logging File for uCDN at 1527 2013-03-23 15:55:00 1528 1529 ... 1530 1531 ... 1532 1533 1535 Figure 4: Example subscription document of a CDNI Logging Feed 1537 4.2. CDNI Logging File Pull 1539 A client-side implementation of the CDNI Logging interface MUST pull, 1540 at its convenience, a CDNI Logging File that is published by the 1541 server-side in the CDNI Logging Feed. To do so, the client-side: 1543 o MUST use HTTP v1.1 ( [RFC2616]); 1545 o SHOULD use TLS (i.e. use what is loosely referred to as "HTTPS") 1546 as per [RFC2818] whenever protection of the CDNI Logging 1547 information is required (see Section 6.1); 1549 o MUST use the URI that was associated to the CDNI Logging File 1550 (within the "src" attribute of the corresponding atom:content 1551 element) in the CDNI Logging Feed 1553 o MUST support exchange of CDNI Logging Files with no content 1554 encoding applied to the representation; 1556 o SHOULD support exchange of CDNI Logging Files with "gzip" content 1557 encoding (as defined in [RFC2616]) applied to the representation. 1559 Note that a client-side implementation of the CDNI Logging interface 1560 MAY pull a CDNI Logging File that it has already pulled, as long as 1561 the file is still published by the server-side in the subscription 1562 document of CDNI Logging Feed. 1564 The server-side implementation MUST respond to any valid pull request 1565 by a client-side implementation for a CDNI Logging File published by 1566 the server-side in the subscription document of the CDNI Logging 1567 Feed. The server-side implementation: 1569 o MUST handle the client-side request as per HTTP v1.1; 1571 o MUST include the CDNI Logging File identified by the request URI 1572 inside the body of the HTTP response; 1574 o MUST support exchange of CDNI Logging Files with no content 1575 encoding applied to the representation; 1577 o SHOULD support exchange of CDNI Logging Files with "gzip" content 1578 encoding (as defined in [RFC2616]) applied to the representation. 1580 Content negotiation approaches defined in [RFC2616] (e.g. using 1581 Accept-Encoding request-header field or Content-Encoding entity- 1582 header field) MAY be used by the client-side and server-side 1583 implementations to establish the content-coding to be used for a 1584 particular exchange of a CDNI Logging File. 1586 Applying compression content encoding (such as "gzip") is expected to 1587 mitigate the impact of exchanging the large volumes of logging 1588 information expected across CDNs. This is expected to be 1589 particularly useful in the presence of HTTP Adaptive Streaming (HAS) 1590 which, as per the present version of the document, will result in a 1591 separate CDNI Log Record for each HAS segment delivery in the CDNI 1592 Logging File. 1594 5. IANA Considerations 1596 5.1. CDNI Logging Directive Names Registry 1598 The IANA is requested to create a new registry, CDNI Logging 1599 Directive Names. 1601 The initial contents of the CDNI Logging File Directives registry 1602 comprise the names of the directives specified in Section 3.3 of the 1603 present document, and are as follows: 1605 +------------------------------+-----------+ 1606 | Directive Name + Reference | 1607 +------------------------------+-----------+ 1608 | Version + RFC xxxx | 1609 | UUID + RFC xxxx | 1610 | Claimed-Origin + RFC xxxx | 1611 | Verified-Origin + RFC xxxx | 1612 | Record-Type + RFC xxxx | 1613 | Fields + RFC xxxx | 1614 | Integrity-Hash + RFC xxxx | 1615 +------------------------------+-----------+ 1617 Figure 5 1619 [Instructions to IANA: Replace "RFC xxxx" above by the RFC number of 1620 the present document] 1622 Within the registry, names are to be allocated by IANA according to 1623 the "Specification Required" policy specified in [RFC5226]. 1625 5.2. CDNI Logging Record-Types Registry 1627 The IANA is requested to create a new registry, CDNI Logging Record- 1628 Types. 1630 The initial contents of the CDNI Logging Record-Types registry 1631 comprise the names of the CDNI Logging Record types specified in 1632 Section 3.4 of the present document, and are as follows: 1634 +------------------------------+-----------+ 1635 | Record-Types + Reference | 1636 +------------------------------+-----------+ 1637 | cdni_http_request_v1 + RFC xxxx | 1638 +------------------------------+-----------+ 1640 Figure 6 1642 [Instructions to IANA: Replace "RFC xxxx" above by the RFC number of 1643 the present document] 1645 Within the registry, Record-Types are to be allocated by IANA 1646 according to the "Specification Required" policy specified in 1647 [RFC5226]. 1649 5.3. CDNI Logging Field Names Registry 1651 The IANA is requested to create a new registry, CDNI Logging Field 1652 Names. 1654 The initial contents of the CDNI Logging Fields Names registry 1655 comprise the names of the CDNI Logging fields specified in 1656 Section 3.4 of the present document, and are as follows: 1658 +---------------------------------------------+-----------+ 1659 | Field Name + Reference | 1660 +---------------------------------------------+-----------+ 1661 | date + RFC xxxx | 1662 | time + RFC xxxx | 1663 | time-taken + RFC xxxx | 1664 | c-ip + RFC xxxx | 1665 | c-ip-anonimizing + RFC xxxx | 1666 | c-port + RFC xxxx | 1667 | s-ip + RFC xxxx | 1668 | s-hostname + RFC xxxx | 1669 | s-port + RFC xxxx | 1670 | cs- method + RFC xxxx | 1671 | cs-uri + RFC xxxx | 1672 | u-uri + RFC xxxx | 1673 | protocol + RFC xxxx | 1674 | sc-status + RFC xxxx | 1675 | sc- total-bytes + RFC xxxx | 1676 | sc-entity-bytes + RFC xxxx | 1677 | cs() + RFC xxxx | 1678 | sc() + RFC xxxx | 1679 | s-ccid + RFC xxxx | 1680 | s-sid + RFC xxxx | 1681 | s-cached + RFC xxxx | 1682 +---------------------------------------------+-----------+ 1684 Figure 7 1686 [Instructions to IANA: Replace "RFC xxxx" above by the RFC number of 1687 the present document] 1689 Within the registry, names are to be allocated by IANA according to 1690 the "Specification Required" policy specified in [RFC5226]. 1692 5.4. CDNI Logging MIME Media Type 1694 The IANA is requested to allocate the "application/cdni.LoggingFile" 1695 MIME Media Type (whose use is specified in Section 4.1.1 of the 1696 present document) in the MIME Media Types registry. 1698 6. Security Considerations 1700 6.1. Authentication, Confidentiality, Integrity Protection 1701 The use of TLS as per [RFC2818] for transport of the CDNI Logging 1702 feed mechanism (Section 4.1) and CDNI Logging File pull mechanism 1703 (Section 4.2) allows: 1705 o the dCDN and uCDN to authenticate each other (to ensure they are 1706 transmitting/receiving CDNI Logging File from an authenticated 1707 CDN) 1709 o the CDNI Logging information to be transmitted with 1710 confidentiality 1712 o the integrity of the CDNI Logging information to be protected 1713 during the exchange 1715 In an environment where any such protection is required, TLS SHOULD 1716 be used for transport of the CDNI Logging feed and the CDNI Logging 1717 File pull. 1719 A CDNI Logging implementation MUST support TLS transport of the CDNI 1720 Logging feed and the CDNI Logging File pull. 1722 The Integrity-Hash directive inside the CDNI Logging File provides 1723 additional integrity protection, this time targeting potential 1724 corruption of the CDNI logging information during the CDNI Logging 1725 File generation. This mechanism does not allow restoration of the 1726 corrupted CDNI Logging information, but it allows detection of such 1727 corruption and therefore triggering of appropraite correcting actions 1728 (e.g. discard of corrupted information, attempt to re-obtain the CDNI 1729 Logging information). 1731 6.2. Privacy 1733 CDNs have the opportunity to collect detailed information about the 1734 downloads performed by End-Users. The provision of this information 1735 to another CDN introduces potential End-Users privacy protection 1736 concerns. We observe that when CDNI interconnection is realised as 1737 per [I-D.ietf-cdni-framework], the uCDN handles the initial End-User 1738 requests (before it is redirected to the dCDN) so, regardless of 1739 which information is, or is not, communicated to the uCDN through the 1740 CDNI Logging interface, the uCDN has visibility on significant 1741 information such as the IP address of the End-User request and the 1742 URL of the request. Nonetheless, if the dCDN and uCDN agree that 1743 anonymization is required to avoid making some detailed information 1744 available to the uCDN (such as how much bytes of the content has been 1745 watched by an enduser and/or at what time) or is required to meet 1746 some legal obligations, then the uCDN and dCDN can agree to exchange 1747 anonymized End-User IP addresses in CDNI Logging files and the c-ip- 1748 anonymization field can be used to convey the number of bits that 1749 have been anonymized so that the meaningful information can still be 1750 easily extracted from the anonymized addressses (e.g. for geolocation 1751 aware analytics). 1753 7. Acknowledgments 1755 This document borrows from the W3C Extended Log Format [ELF]. 1757 Rob Murray significantly contributed into the text of Section 4.1 . 1759 The authors would like to thank Sebastien Cubaud, Pawel Grochocki, 1760 Christian Jacquenet, Yannick Le Louedec, Anne Marrec and Emile 1761 Stephan for their contributions on early versions of this document. 1762 The authors would like also to thank Fabio Costa, Sara Oueslati, Yvan 1763 Massot, Renaud Edel, and Joel Favier for their input and comments. 1764 Finally, they thank the contributors of the EU FP7 OCEAN project for 1765 valuable inputs. 1767 8. References 1769 8.1. Normative References 1771 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1772 Requirement Levels", BCP 14, RFC 2119, March 1997. 1774 [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., 1775 Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext 1776 Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. 1778 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 1779 Resource Identifier (URI): Generic Syntax", STD 66, RFC 1780 3986, January 2005. 1782 [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally 1783 Unique IDentifier (UUID) URN Namespace", RFC 4122, July 1784 2005. 1786 [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom 1787 Syndication Format", RFC 4287, December 2005. 1789 [RFC5005] Nottingham, M., "Feed Paging and Archiving", RFC 5005, 1790 September 2007. 1792 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 1793 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 1794 May 2008. 1796 [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax 1797 Specifications: ABNF", STD 68, RFC 5234, January 2008. 1799 8.2. Informative References 1801 [CHAR_SET] 1802 , "IANA Character Sets registry", , . 1805 [ELF] Phillip M. Hallam-Baker, . and . Brian Behlendorf, 1806 "Extended Log File Format, W3C (work in progress), WD- 1807 logfile-960323", , . 1809 [I-D.ietf-cdni-framework] 1810 Peterson, L. and B. Davie, "Framework for CDN 1811 Interconnection", draft-ietf-cdni-framework-05 (work in 1812 progress), September 2013. 1814 [I-D.ietf-cdni-metadata] 1815 Niven-Jenkins, B., Murray, R., Watson, G., Caulfield, M., 1816 Leung, K., and K. Ma, "CDN Interconnect Metadata", draft- 1817 ietf-cdni-metadata-02 (work in progress), July 2013. 1819 [I-D.ietf-cdni-requirements] 1820 Leung, K. and Y. Lee, "Content Distribution Network 1821 Interconnection (CDNI) Requirements", draft-ietf-cdni- 1822 requirements-10 (work in progress), September 2013. 1824 [I-D.snell-atompub-link-extensions] 1825 Snell, J., "Atom Link Extensions", draft-snell-atompub- 1826 link-extensions-09 (work in progress), June 2012. 1828 [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, 1829 April 1992. 1831 [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000. 1833 [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content 1834 Distribution Network Interconnection (CDNI) Problem 1835 Statement", RFC 6707, September 2012. 1837 [RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma, 1838 K., and G. Watson, "Use Cases for Content Delivery Network 1839 Interconnection", RFC 6770, November 2012. 1841 [RFC6983] van Brandenburg, R., van Deventer, O., Le Faucheur, F., 1842 and K. Leung, "Models for HTTP-Adaptive-Streaming-Aware 1843 Content Distribution Network Interconnection (CDNI)", RFC 1844 6983, July 2013. 1846 Appendix A. Compliance with CDNI Requirements 1848 [Editor's Note: this section may need a small update if ietf-cdni- 1849 requirements introduces an additional requirement for Privacy/ 1850 Anonimization as recently discussed on the list, and if LI14 & LI-15 1851 are modified] 1853 The three tables below review compliance against, respectively, the 1854 Generic CDNI requirements, the CDNI Logging interafce requirements 1855 and the CDNI security requirements of [I-D.ietf-cdni-requirements]. 1856 The first two columns of the tables indicate the requirement number, 1857 and the requirement priority as defined in 1858 [I-D.ietf-cdni-requirements]. The third column of the table 1859 indicates the level of compliance of the CDNI Logging interface 1860 specified in the present document against the given requirement, and 1861 the fourth column provides additional comment and explanation on how 1862 or why the compliance is achieved or not achieved. 1864 +-------+-------+-----------+---------------------------------------+ 1865 | Re- | Prior-| Compli- | Comment | 1866 | quire-| ity | ance | | 1867 | ment | | | | 1868 +-------+-------+-----------+---------------------------------------+ 1869 | GEN-1 | MED | Full | Leverages existing protocols incl | 1870 | | | | including HTTP, TLS and ATOM | 1871 +-------+-------+-----------+---------------------------------------+ 1872 | GEN-2 | HIGH | Full | Does not require any change or upgrade| 1873 | | | | to the user agent | 1874 +-------+-------+-----------+---------------------------------------+ 1875 | GEN-3 | HIGH | Full | Does not require any change or upgrade| 1876 | | | | to the Content Service Provider | 1877 +-------+-------+-----------+---------------------------------------+ 1878 | GEN-4 | HIGH | Full | Does not depend on intra-CDN info | 1879 +-------+-------+-----------+---------------------------------------+ 1880 | GEN-5 | HIGH | Full | Supports logging of HTTP delivery | 1881 +-------+-------+-----------+---------------------------------------+ 1882 | GEN-6 | HIGH | N/A | | 1883 +-------+-------+-----------+---------------------------------------+ 1884 | GEN-7 | LOW | Not | Only supports logging for HTTP | 1885 | | | Compliant | delivery, but easily extensible to | 1886 | | | | add support for other delivery protos | 1887 +-------+-------+-----------+---------------------------------------+ 1888 | GEN-8 | LOW | N/A | | 1889 +-------+-------+-----------+---------------------------------------+ 1890 | GEN-9 | MED | Full | Supports logging across cascaded CDNs | 1891 +-------+-------+-----------+---------------------------------------+ 1892 | GEN-10| MED | Full | Supports any toplogy of interconnected| 1893 | | | | CDNs | 1894 +-------+-------+-----------+---------------------------------------+ 1895 | GEN-11| HIGH | Parial | No explicit mechanism for loop | 1896 | | | | avoidance is defined; the exchange of | 1897 | | | | logs is usually done in a point to | 1898 | | | | point manner between two well identi- | 1899 | | | | fied entities situated in the uCDN and| 1900 | | | | dCDN. Loop avoidance is expected to be| 1901 | | | | handled by implementations based on | 1902 | | | | inferring the CDN path from the URI | 1903 | | | | structure in the HTTP redirection case| 1904 | | | | and/or administrative information | 1905 | | | | (topology restrictions in case of DNS | 1906 | | | | redirection method also handled admi- | 1907 | | | | nistratively) | 1908 +-------+-------+-----------+---------------------------------------+ 1909 | GEN-12| HIGH | N/A | | 1910 +-------+-------+-----------+---------------------------------------+ 1911 | GEN-13| HIGH | Full | Supports Logging for HTTP Adaptive | 1912 | | | | Streaming (HSAS) content, with one | 1913 | | | | Logging Record per HAS segment. | 1914 | | | | Supports a few optional logging fields| 1915 | | | | specific to HAS. Does not support | 1916 | | | | summarized Logging Records for HAS, | 1917 | | | | but extensible to add that. | 1918 +-------+-------+-----------+---------------------------------------+ 1920 Figure 8: Compliance to Generic CDNI Requirements 1922 +-------+-------+-----------+---------------------------------------+ 1923 | Re- | Prior-| Compli- | Comment | 1924 | quire-| ity | ance | | 1925 | ment | | | | 1926 +-------+-------+-----------+---------------------------------------+ 1927 | LI-1 | HIGH | Full | Reliable transfer is achieved by the | 1928 | | | | transport protocol: the logging data | 1929 | | | | is transmitted over HTTP over TCP. | 1930 | | | | Also, supports optional redundancy of | 1931 | | | | the Logging feed. | 1932 +-------+-------+-----------+---------------------------------------+ 1933 | LI-2 | HIGH | Full | Supports | 1934 | | | | logs for all content deliveries both | 1935 | | | | complete and incomplete performed by | 1936 | | | | the dCDN on behalf of the uCDN | 1937 +-------+-------+-----------+---------------------------------------+ 1938 | LI-3 | MED | Full | The CDNI Logging Interface does not | 1939 | | | | impose any restrictions related to the| 1940 | | | | transmission of logs generated by | 1941 | | | | intermediary CDNs; the dCDN formats | 1942 | | | | internally all the final logging files| 1943 | | | | including those received from interme-| 1944 | | | | diary CDNs and the locally generated | 1945 +-------+-------+-----------+---------------------------------------+ 1946 | LI-4 | HIGH | Full | The ATOM feed allows the uCDN to trig-| 1947 | | | | ger the download of logging files | 1948 | | | | whenever needed | 1949 +-------+-------+-----------+---------------------------------------+ 1950 | LI-5 | MED | Partial | The uCDN can pull logging files from | 1951 | | | | the dCDN whenever a new file is | 1952 | | | | available. The timing constraints for | 1953 | | | | the generation of the logging files | 1954 | | | | are to be defined offline, and can be | 1955 | | | | defined to an arbitrary period. This | 1956 | | | | is expected to be compatible with | 1957 | | | | applications that have low timing | 1958 | | | | constraints (e.g. 24 hours) such as | 1959 | | | | billing. This is expected to be | 1960 | | | | compatible with applications that | 1961 | | | | have high timing constraints (e.g. 5 | 1962 | | | | minutes) such as monitoring or | 1963 | | | | analytics. This is not expected to be | 1964 | | | | compatible with applications that have| 1965 | | | | very high timing constraints (e.g. | 1966 | | | | a few seconds or below) | 1967 +-------+-------+-----------+---------------------------------------+ 1968 | LI-6 | HIGH | Full | Section 3.4 describes the CDNI Logging| 1969 | | | | Records and the possible fields that | 1970 | | | | can be included in a record. | 1971 | | | | Supports a single type of CDNI event | 1972 | | | | i.e. HTTP delivery | 1973 +-------+-------+-----------+---------------------------------------+ 1974 | LI-7 | HIGH | Full | Defines an ATOM based feed and HTTP | 1975 | | | | or HTTPS transport | 1976 +-------+-------+-----------+---------------------------------------+ 1977 | LI-8 | MED | Partial | Allows as uCDN to pull current CDNI | 1978 | | | | Logging files to access current | 1979 | | | | Logging records. Does not allow uCDN | 1980 | | | | to request Log Records before next | 1981 | | | | Logging file is made available. | 1982 +-------+-------+-----------+---------------------------------------+ 1983 | LI-9 | LOW | Not | The current version of the document | 1984 | | | Compliant | does not specify any mechanisms for | 1985 | | | | producing aggregate / summarized logs,| 1986 | | | | but exchanged logging files provide | 1987 | | | | all the information that is necessary | 1988 | | | | to the uCDN in order to produce aggre-| 1989 | | | | gated logs. Extensible to add such | 1990 | | | | mechanisms in the future | 1991 +-------+-------+-----------+---------------------------------------+ 1992 | LI-10 | LOW | Not | Future versions might define such a | 1993 | | | compliant | mechanism for logging performance | 1994 | | | | data. Allows uCDN to derive some perf | 1995 | | | | indicators from delivery Records | 1996 +-------+-------+-----------+---------------------------------------+ 1997 | LI-11 | MED | Not | Future versions might define such a | 1998 | | | compliant | mechanism for logging data about | 1999 | | | | resources consumed by the dCDN | 2000 +-------+-------+-----------+---------------------------------------+ 2001 | LI-12 | MED | Not | Future versions might define such a | 2002 | | | compliant | mechanism for logging data about | 2003 | | | | resources consumed by cascaded CDNs | 2004 +-------+-------+-----------+---------------------------------------+ 2005 | LI-13 | HIGH | Not | Not supported by CDNI Logging | 2006 | | | compliant | interface. However, it is expected | 2007 | | | | that teh CDNI Control interface will | 2008 | | | | allow tracing of delete request | 2009 | | | | results (e.g. success, failure). | 2010 +-------+-------+-----------+---------------------------------------+ 2011 | LI-14 | HIGH | Full | Details about extensibility mechanisms| 2012 | | | | in Section 6. | 2013 +-------+-------+-----------+---------------------------------------+ 2014 | LI-15 | HIGH | Full | Details about proprietary fields in | 2015 | | | | Section 6. | 2016 +-------+-------+-----------+---------------------------------------+ 2017 | LI-16 | HIGH | Full | The CDNI Logging feed indicates which | 2018 | | | | Logging file is (or was) available | 2019 +-------+-------+-----------+---------------------------------------+ 2020 | LI-17 | MED | Full | Content Collection ID and Session ID | 2021 | | | | are supported for logging records re- | 2022 | | | | lated to HTTP Adaptive Streaming | 2023 +-------+-------+-----------+---------------------------------------+ 2025 Figure 9: Compliance to CDNI Logging interface Requirements 2027 +-------+-------+-----------+---------------------------------------+ 2028 | Re- | Prior-| Compli- | Comment | 2029 | quire-| ity | ance | | 2030 | ment | | | | 2031 +-------+-------+-----------+---------------------------------------+ 2032 | SEC-1 | HIGH | Full | TLS can be used for transport of any | 2033 | | | | CDNI logging related information which| 2034 | | | | provides authentication, confidentia- | 2035 | | | | lity, integrity protection as well as | 2036 | | | | protection agasint spoofing and replay| 2037 +-------+-------+-----------+---------------------------------------+ 2038 | SEC-2 | HIGH | Full | No specific mechanism against Denial | 2039 | | | | of Service attacks is defined on the | 2040 | | | | Logging Interface. Spoofed requests | 2041 | | | | can be avoided by using TLS. | 2042 | | | | Protection against spoofed delivery | 2043 | | | | requests are outside the scope of CDNI| 2044 | | | | Logging | 2045 +-------+-------+-----------+---------------------------------------+ 2046 | SEC-3 | MED | N/A | Establishing CDN path with non- | 2047 | | | | repudiation is outside the scope of | 2048 | | | | CDNI Logging. Does not prevent use of | 2049 | | | | such mechanism (e.g. including info | 2050 | | | | in content URI). | 2051 +-------+-------+-----------+---------------------------------------+ 2052 | SEC-4 | MED | Not | A non-repudiation mechanism for CDNI | 2053 | | | compliant | logging might be defined in a separate| 2054 | | | | document | 2055 +-------+-------+-----------+---------------------------------------+ 2056 | SEC-5 | LOW | N/A | | 2057 +-------+-------+-----------+---------------------------------------+ 2059 Figure 10: Compliance to CDNI Security Requirements 2061 Authors' Addresses 2063 Francois Le Faucheur (editor) 2064 Cisco Systems 2065 E.Space Park - Batiment D 2066 6254 Allee des Ormes - BP 1200 2067 Mougins cedex 06254 2068 FR 2070 Phone: +33 4 97 23 26 19 2071 Email: flefauch@cisco.com 2072 Gilles Bertrand (editor) 2073 Orange 2074 38-40 rue du General Leclerc 2075 Issy les Moulineaux 92130 2076 FR 2078 Phone: +33 1 45 29 89 46 2079 Email: gilles.bertrand@orange.com 2081 Iuniana Oprescu (editor) 2082 Orange 2083 38-40 rue du General Leclerc 2084 Issy les Moulineaux 92130 2085 FR 2087 Phone: +33 6 89 06 92 72 2088 Email: iuniana.oprescu@orange.com 2090 Roy Peterkofsky 2091 Skytide, Inc. 2092 One Kaiser Plaza, Suite 785 2093 Oakland CA 94612 2094 USA 2096 Phone: +01 510 250 4284 2097 Email: roy@skytide.com