draft-ietf-cdni-logging-03.txt   draft-ietf-cdni-logging-04.txt 
Internet Engineering Task Force G. Bertrand, Ed. Internet Engineering Task Force G. Bertrand, Ed.
Internet-Draft I. Oprescu, Ed. Internet-Draft I. Oprescu, Ed.
Intended status: Informational France Telecom - Orange Intended status: Informational France Telecom - Orange
Expires: December 02, 2013 F. Le Faucheur, Ed. Expires: December 27, 2013 F. Le Faucheur, Ed.
Cisco Systems Cisco Systems
R. Peterkofsky R. Peterkofsky
Skytide, Inc. Skytide, Inc.
May 31, 2013 June 25, 2013
CDNI Logging Interface CDNI Logging Interface
draft-ietf-cdni-logging-03 draft-ietf-cdni-logging-04
Abstract Abstract
This memo specifies the Logging interface between a downstream CDN This memo specifies the Logging interface between a downstream CDN
(dCDN) and an upstream CDN (uCDN) that are interconnected as per the (dCDN) and an upstream CDN (uCDN) that are interconnected as per the
CDN Interconnection (CDNI) framework. First, it describes a CDN Interconnection (CDNI) framework. First, it describes a
reference model for CDNI logging. Then, it specifies the CDNI reference model for CDNI logging. Then, it specifies the CDNI
Logging File format and the actual protocol for exchange of CDNI Logging File format and the actual protocol for exchange of CDNI
Logging Files. Logging Files.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 02, 2013. This Internet-Draft will expire on December 27, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2013 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 33 skipping to change at page 2, line 33
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. CDNI Logging Reference Model . . . . . . . . . . . . . . . . 5 2. CDNI Logging Reference Model . . . . . . . . . . . . . . . . 5
2.1. CDNI Logging interactions . . . . . . . . . . . . . . . . 5 2.1. CDNI Logging interactions . . . . . . . . . . . . . . . . 5
2.2. Overall Logging Chain . . . . . . . . . . . . . . . . . . 8 2.2. Overall Logging Chain . . . . . . . . . . . . . . . . . . 8
2.2.1. Logging Generation and During-Generation Aggregation 9 2.2.1. Logging Generation and During-Generation Aggregation 9
2.2.2. Logging Collection . . . . . . . . . . . . . . . . . 10 2.2.2. Logging Collection . . . . . . . . . . . . . . . . . 10
2.2.3. Logging Filtering . . . . . . . . . . . . . . . . . . 10 2.2.3. Logging Filtering . . . . . . . . . . . . . . . . . . 10
2.2.4. Logging Rectification and Post-Generation Aggregation 11 2.2.4. Logging Rectification and Post-Generation Aggregation 11
2.2.5. Log-Consuming Applications . . . . . . . . . . . . . 12 2.2.5. Log-Consuming Applications . . . . . . . . . . . . . 11
2.2.5.1. Maintenance/Debugging . . . . . . . . . . . . . . 12 2.2.5.1. Maintenance/Debugging . . . . . . . . . . . . . . 11
2.2.5.2. Accounting . . . . . . . . . . . . . . . . . . . 12 2.2.5.2. Accounting . . . . . . . . . . . . . . . . . . . 12
2.2.5.3. Analytics and Reporting . . . . . . . . . . . . . 13 2.2.5.3. Analytics and Reporting . . . . . . . . . . . . . 12
2.2.5.4. Security . . . . . . . . . . . . . . . . . . . . 13 2.2.5.4. Security . . . . . . . . . . . . . . . . . . . . 12
2.2.5.5. Legal Logging Duties . . . . . . . . . . . . . . 13 2.2.5.5. Legal Logging Duties . . . . . . . . . . . . . . 13
2.2.5.6. Notions common to multiple Log Consuming 2.2.5.6. Notions common to multiple Log Consuming
Applications . . . . . . . . . . . . . . . . . . 13 Applications . . . . . . . . . . . . . . . . . . 13
3. CDNI Logging File Format . . . . . . . . . . . . . . . . . . 15 3. CDNI Logging File . . . . . . . . . . . . . . . . . . . . . . 15
3.1. CDNI Logging File Directives . . . . . . . . . . . . . . 16 3.1. Rules . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2. Logging Records . . . . . . . . . . . . . . . . . . . . . 20 3.2. CDNI Logging File Structure . . . . . . . . . . . . . . . 16
3.2.1. HTTP Request Logging Record . . . . . . . . . . . . . 21 3.3. CDNI Logging File Directives . . . . . . . . . . . . . . 18
3.2.2. CDNI Logging File Example . . . . . . . . . . . . . . 27 3.4. CDNI Logging Records . . . . . . . . . . . . . . . . . . 21
3.3. Fields and Directives Formats . . . . . . . . . . . . . . 28 3.4.1. HTTP Request Logging Record . . . . . . . . . . . . . 22
4. CDNI Logging File Exchange Protocol . . . . . . . . . . . . . 28 3.5. CDNI Logging File Example . . . . . . . . . . . . . . . . 29
4.1. CDNI Logging Feed . . . . . . . . . . . . . . . . . . . . 29 4. CDNI Logging File Exchange Protocol . . . . . . . . . . . . . 30
4.2. CDNI Logging File Pull . . . . . . . . . . . . . . . . . 29 4.1. CDNI Logging Feed . . . . . . . . . . . . . . . . . . . . 31
5. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 30 4.2. CDNI Logging File Pull . . . . . . . . . . . . . . . . . 31
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 31 5. Open Issues . . . . . . . . . . . . . . . . . . . . . . . . . 32
7. Security Considerations . . . . . . . . . . . . . . . . . . . 31 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 33
7.1. Authentication, Confidentiality, Integrity Protection . . 31 6.1. CDNI Logging Directive Names Registry . . . . . . . . . . 33
7.2. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 32 6.2. CDNI Logging Record-Type Registry . . . . . . . . . . . . 34
7.3. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 32 6.3. CDNI Logging Field Name Registry . . . . . . . . . . . . 34
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33 7. Security Considerations . . . . . . . . . . . . . . . . . . . 35
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 7.1. Authentication, Confidentiality, Integrity Protection . . 35
9.1. Normative References . . . . . . . . . . . . . . . . . . 33 7.2. Non Repudiation . . . . . . . . . . . . . . . . . . . . . 36
9.2. Informative References . . . . . . . . . . . . . . . . . 34 7.3. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 36
Appendix A. Requirements . . . . . . . . . . . . . . . . . . . . 34 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 36
A.1. Compliance with cdni-requirements . . . . . . . . . . . . 34 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
A.2. Additional Requirements . . . . . . . . . . . . . . . . . 35 9.1. Normative References . . . . . . . . . . . . . . . . . . 37
A.2.1. Timeliness . . . . . . . . . . . . . . . . . . . . . 35 9.2. Informative References . . . . . . . . . . . . . . . . . 37
A.2.2. Reliability . . . . . . . . . . . . . . . . . . . . . 35 Appendix A. Requirements . . . . . . . . . . . . . . . . . . . . 38
A.2.3. Security . . . . . . . . . . . . . . . . . . . . . . 35 A.1. Compliance with cdni-requirements . . . . . . . . . . . . 38
A.2.4. Scalability . . . . . . . . . . . . . . . . . . . . . 35 A.2. Additional Requirements . . . . . . . . . . . . . . . . . 39
A.2.5. Consistency between CDNI Logging and CDN Logging . . 36 A.2.1. Timeliness . . . . . . . . . . . . . . . . . . . . . 39
A.2.6. Dispatching/Filtering . . . . . . . . . . . . . . . . 36 A.2.2. Reliability . . . . . . . . . . . . . . . . . . . . . 39
A.2.3. Security . . . . . . . . . . . . . . . . . . . . . . 39
A.2.4. Scalability . . . . . . . . . . . . . . . . . . . . . 39
A.2.5. Consistency between CDNI Logging and CDN Logging . . 40
A.2.6. Dispatching/Filtering . . . . . . . . . . . . . . . . 40
Appendix B. Analysis of candidate protocols for Logging Appendix B. Analysis of candidate protocols for Logging
Transport . . . . . . . . . . . . . . . . . . . . . 36 Transport . . . . . . . . . . . . . . . . . . . . . 40
B.1. Syslog . . . . . . . . . . . . . . . . . . . . . . . . . 36 B.1. Syslog . . . . . . . . . . . . . . . . . . . . . . . . . 40
B.2. XMPP . . . . . . . . . . . . . . . . . . . . . . . . . . 36 B.2. XMPP . . . . . . . . . . . . . . . . . . . . . . . . . . 40
B.3. SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . 37 B.3. SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 40
1. Introduction 1. Introduction
This memo specifies the Logging interface between a downstream CDN This memo specifies the Logging interface between a downstream CDN
(dCDN) and an upstream CDN (uCDN). First, it describes a reference (dCDN) and an upstream CDN (uCDN). First, it describes a reference
model for CDNI logging. Then, it specifies the CDNI Logging File model for CDNI logging. Then, it specifies the CDNI Logging File
format and the actual protocol for exchange of CDNI Logging Files. format and the actual protocol for exchange of CDNI Logging Files.
The reader should be familiar with the following documents: The reader should be familiar with the following documents:
skipping to change at page 5, line 21 skipping to change at page 5, line 26
monitoring data can be used to generate alarms. monitoring data can be used to generate alarms.
2. CDNI Logging Reference Model 2. CDNI Logging Reference Model
2.1. CDNI Logging interactions 2.1. CDNI Logging interactions
The CDNI logging reference model between a given uCDN and a given The CDNI logging reference model between a given uCDN and a given
dCDN involves the following interactions: dCDN involves the following interactions:
o customization by the uCDN of the CDNI logging information to be o customization by the uCDN of the CDNI logging information to be
provided by the dCDN to the uCDN (e.g. control of which logging provided by the dCDN to the uCDN (e.g. control of which logging
fields are to be communicated to the uCDN for a given task fields are to be communicated to the uCDN for a given task
performed by the dCDN, control of which types of events are to be performed by the dCDN, control of which types of events are to be
logged). The dCDN takes into account this CDNI logging logged). The dCDN takes into account this CDNI logging
customization information to determine what logging information to customization information to determine what logging information to
provide to the uCDN, but it may, or may not, take into account provide to the uCDN, but it may, or may not, take into account
this CDNI logging customization information to influence what CDN this CDNI logging customization information to influence what CDN
logging information is to be generated and collected within the logging information is to be generated and collected within the
dCDN (e.g. even if the uCDN requests a restricted subset of the dCDN (e.g. even if the uCDN requests a restricted subset of the
logging information, the dCDN may elect to generate a broader set logging information, the dCDN may elect to generate a broader set
of logging information). The mechanism to support the of logging information). The mechanism to support the
customisation by the uCDN of CDNI Logging information is outside customisation by the uCDN of CDNI Logging information is outside
the scope of this document and left for further study. We note the scope of this document and left for further study. We note
that the CDNI Control interface or the CDNI Metadata interface that the CDNI Control interface or the CDNI Metadata interface
appear as candidate interfaces on which to potentially build such appear as candidate interfaces on which to potentially build such
a customisation mechanism in the future. Before such a mechanism a customisation mechanism in the future. Before such a mechanism
is available, the uCDN and dCDN are expected to agree off-line on is available, the uCDN and dCDN are expected to agree off-line on
what CDNI logging information is to be provide by dCDN to UCDN and what CDNI logging information is to be provide by dCDN to UCDN and
rely on management plane actions to configure the CDNI Logging rely on management plane actions to configure the CDNI Logging
skipping to change at page 6, line 48 skipping to change at page 7, line 7
o to analyze the performance of the delivery operated by the dCDNs o to analyze the performance of the delivery operated by the dCDNs
and to adjust its operations (e.g., request routing) as and to adjust its operations (e.g., request routing) as
appropriate, appropriate,
o to provide reporting (non real-time) and monitoring (real-time) o to provide reporting (non real-time) and monitoring (real-time)
information to CSP. information to CSP.
For instance, uCDN merges Logging data, extracts relevant KPIs, and For instance, uCDN merges Logging data, extracts relevant KPIs, and
presents a formatted report to the CSP, in addition to a bill for the presents a formatted report to the CSP, in addition to a bill for the
content delivered by uCDN itself or by its dCDNs on his behalf. uCDN content delivered by uCDN itself or by its dCDNs on his behalf. uCDN
may also provide Logging data as raw log files to the CSP, so that may also provide Logging data as raw log files to the CSP, so that
the CSP can use its own logging analysis tools. the CSP can use its own logging analysis tools.
+-----+ +-----+
| CSP | | CSP |
+-----+ +-----+
^ Reporting and monitoring data ^ Reporting and monitoring data
* Billing * Billing
,--*--. ,--*--.
Logging ,-' `-. Logging ,-' `-.
skipping to change at page 15, line 34 skipping to change at page 15, line 7
related to Surrogates' performance, caching information to evaluate related to Surrogates' performance, caching information to evaluate
the cache-hit ratio, information about the delivered file size to the cache-hit ratio, information about the delivered file size to
compute the volume of content delivered during peak hour, etc. compute the volume of content delivered during peak hour, etc.
Some of the KPIs, for instance those providing an instantaneous Some of the KPIs, for instance those providing an instantaneous
vision of the active sessions for a given CSP's content, are useful vision of the active sessions for a given CSP's content, are useful
essentially if they are provided in real-time. By contrast, some essentially if they are provided in real-time. By contrast, some
other KPIs, such as the one averaged on a long period of time, can be other KPIs, such as the one averaged on a long period of time, can be
provided in non-real time. provided in non-real time.
3. CDNI Logging File Format 3. CDNI Logging File
3.1. Rules
This specification uses the Augmented Backus-Naur Form (ABNF)
notation and core rules of [RFC5234]. In particular, the present
document uses the following rules from [RFC5234]:
CR = %x0D ; carriage return
DIGIT = %x30-39 ; 0-9
DQUOTE = %x22 ; " (Double Quote)
CRLF = CR LF ; Internet standard newline
HEXDIG = DIGIT / "A" / "B" / "C" / "D" / "E" / "F"
HTAB = %x09 ; horizontal tab
LF = %x0A ; linefeed
OCTET = %x00-FF ; 8 bits of data
The present document also uses the following rules from [RFC3986]:
host = as specified in section 3.2.2 of [RFC3986].
IPv4address = as specified in section 3.2.2 of [RFC3986].
IPv6address = as specified in section 3.2.2 of [RFC3986].
The present document also defines the folowing additional rules:
ADDRESS = IPv4address / IPv6address
DATE = 4DIGIT "-" 2DIGIT "-" 2DIGIT
Dates are recorded in the format YYYY-MM-DD where YYYY, MM and
DD stand for the numeric year, month and day respectively. All
dates are specified in Universal Time Coordinated (UTC).
DEC = 1*DIGIT ["." *DIGIT]
QSTRING = DQUOTE *NDQUOTE DQUOTE ; where
NDQUOTE = <any OCTET excluding DQUOTE> / 2DQUOTE ; whereby a
DQUOTE is conveyed inside a QSTRING unambiguously by repeating
it.
NHTABSTRING = *NHTAB ; where
NHTAB = <any OCTET excluding HTAB>
TIME = 2DIGIT ":" 2DIGIT ":" 2DIGIT ["." *DIGIT]
Times are recorded in the form HH:MM:SS or HH:MM:SS.S where HH
is the hour in 24 hour format, MM is minutes and SS is seconds.
All times are specified in Universal Time Coordinated (UTC).
3.2. CDNI Logging File Structure
As defined in Section 1.1 a CDNI logging field is as an atomic As defined in Section 1.1 a CDNI logging field is as an atomic
logging information element and a CDNI Logging Record is a collection logging information element and a CDNI Logging Record is a collection
of CDNI Logging Fields containing all logging information of CDNI Logging Fields containing all logging information
corresponding to a single logging event. This document defines a corresponding to a single logging event. This document defines a
third level of structure, the CDNI Logging File, that is a collection third level of structure, the CDNI Logging File, that is a collection
of CDNI Logging Records. This structure is illustrated in Figure 3. of CDNI Logging Records. This structure is illustrated in Figure 3.
The CDNI Logging File structure and encoding is specified in the
present section.
+------------------------------------------------------+ +----------------------------------------------------------+
|CDNI Logging File | |CDNI Logging File |
| | | |
| +--------------------------------------------------+ | | #Directive 1 |
| |CDNI Logging Record | | | #Directive 2 |
| | +-------------+ +-------------+ +-------------+ | | | ... |
| | |CDNI Logging | |CDNI Logging | |CDNI Logging | | | | #Directive P |
| | | Field | | Field | | Field | | | | |
| | +-------------+ +-------------+ +-------------+ | | | +------------------------------------------------------+ |
| +--------------------------------------------------+ | | |CDNI Logging Record 1 | |
| | | | +-------------+ +-------------+ +-------------+ | |
| +--------------------------------------------------+ | | | |CDNI Logging | |CDNI Logging | ... |CDNI Logging | | |
| |CDNI Logging Record | | | | | Field 1 | | Field 2 | | Field N | | |
| | +-------------+ +-------------+ +-------------+ | | | | +-------------+ +-------------+ +-------------+ | |
| | |CDNI Logging | |CDNI Logging | |CDNI Logging | | | | +------------------------------------------------------+ |
| | | Field | | Field | | Field | | | | |
| | +-------------+ +-------------+ +-------------+ | | | +------------------------------------------------------+ |
| +--------------------------------------------------+ | | |CDNI Logging Record 2 | |
| | | | +-------------+ +-------------+ +-------------+ | |
| +--------------------------------------------------+ | | | |CDNI Logging | |CDNI Logging | ... |CDNI Logging | | |
| |CDNI Logging Record | | | | | Field 1 | | Field 2 | | Field N | | |
| | +-------------+ +-------------+ +-------------+ | | | | +-------------+ +-------------+ +-------------+ | |
| | |CDNI Logging | |CDNI Logging | |CDNI Logging | | | | +------------------------------------------------------+ |
| | | Field | | Field | | Field | | | | |
| | +-------------+ +-------------+ +-------------+ | | | ... |
| +--------------------------------------------------+ | | |
+------------------------------------------------------+ | #Directive P+1 |
| |
| ... |
| |
| +------------------------------------------------------+ |
| |CDNI Logging Record M | |
| | +-------------+ +-------------+ +-------------+ | |
| | |CDNI Logging | |CDNI Logging | ... |CDNI Logging | | |
| | | Field 1 | | Field 2 | | Field N | | |
| | +-------------+ +-------------+ +-------------+ | |
| +------------------------------------------------------+ |
| |
| |
| #Directive P+Q |
+----------------------------------------------------------+
Figure 3: Structure of Logging Files Figure 3: Structure of Logging Files
The CDNI Logging File format is inspired from the W3C Extended Log The CDNI Logging File format is inspired from the W3C Extended Log
File Format [ELF]. However, it is fully specified by the present File Format [ELF]. However, it is fully specified by the present
document. Where the present document differs from the W3C Extended document. Where the present document differs from the W3C Extended
Log File Format, an implementation of CDNI Logging MUST comply with Log File Format, an implementation of CDNI Logging MUST comply with
the present document. the present document.
A CDNI Logging File MUST contain a sequence of lines containing US- A CDNI Logging File MUST contain a sequence of lines containing US-
ASCII characters [CHAR_SET] terminated by either the sequence LF or ASCII characters [CHAR_SET] terminated by CRLF.
CRLF. A CDNI Logging implementation consuming CDNI Logging Files
MUST accept lines terminated by either LF or CRLF.
Each line of a CDNI Logging File MUST contain either a directive or a Each line of a CDNI Logging File MUST contain either a directive or a
CDNI Logging Record. CDNI Logging Record.
Directives record information about the CDNI Logging process itself. Directives record information about the CDNI Logging process itself.
Lines containing directives MUST begin with the "#" character. Lines containing directives MUST begin with the "#" character.
Directives are specified in Section 3.1. Directives are specified in Section 3.3.
Logging Records provide actual details of the logged event. Logging Logging Records provide actual details of the logged event. Logging
Records are specified in Section 3.2. Records are specified in Section 3.4.
The CDNI File structure is defined by the following rules:
DIRLINE = "#" directive CRLF
DIRGROUP = 1*DIRLINE
RECLINE = <CDNI Logging Record> CRLF
RECGROUP = *RECLINE
<CDNI Logging File> = 1*<DIRGROUP RECGROUP>
3.3. CDNI Logging File Directives
The CDNI Logging File directives are defined by the following rules:
directive = DIRNAME ":" HTAB DIRVAL
DIRNAME = <directive name> = "Version" / "UUID" / "Claimed-Origin"
/ "Verified-Origin" / "Record-Type" / "Fields" / "Integrity-Hash"
/ "Non-Repudiation-Signature"
DIRVAL = <directive value as specified below for each directive
name>
3.1. CDNI Logging File Directives
An implementation of the CDNI Logging interface MUST support the An implementation of the CDNI Logging interface MUST support the
following directives (formats specified in the form <...> are following directives, listed below by their directive name:
specified in Section 3.3):
o Version: o Version:
* format: <digit>.<digit> * format: "CDNI" "/" 1*DIGIT "." 1*DIGIT
* semantic: indicates the version of the CDNI Logging File * directive value: indicates the version of the CDNI Logging File
format. The value MUST be "1.0" for the version specified in format. The value MUST be "CDNI/1.0" for the version specified
the present document. in the present document.
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
directive. It MUST be the first line of the CDNI Logging file. directive. It MUST be the first line of the CDNI Logging file.
o UUID: o UUID:
* format: <string> * format: QSTRING
* semantic: this is Universally Unique IDentifier for the CDNI * directive value: this is Universally Unique IDentifier for the
Logging File as specified in [RFC4122]. CDNI Logging File as specified in [RFC4122]. [Editor's note:
check RFC4122 format to see if QSTRING is the right format]
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
directive. directive.
o Claimed-Origin: o Claimed-Origin:
* format: <host> * format: host
* directive value: this contains the claimed identification of
* semantic: this contains the claimed identification of the the entity transmitting the CDNI Logging File (e.g. the host in
entity transmitting the CDNI Logging File (e.g. the host in a a dCDN supporting the CDNI Logging interface) or the entity
dCDN supporting the CDNI Logging interface) or the entity responsible for transmitting the CDNI Logging File (e.g. the
responsible for transmitting the CDNI Logging File (e.g. the
dCDN). dCDN).
* occurrence: there MUST be zero or one instance of this * occurrence: there MUST be zero or one instance of this
directive. This directive MAY be included by the dCDN. It directive. This directive MAY be included by the dCDN. It
MUST NOT be included or modified by the uCDN. MUST NOT be included or modified by the uCDN.
o Verified-Origin: o Verified-Origin:
* format: <host> * format: host
* semantic: this contains the identification, as established by
the entity receiving the CDNI Logging file, of the entity * directive value: this contains the identification, as
transmitting the CDNI Logging File (e.g. the host in a dCDN established by the entity receiving the CDNI Logging file, of
supporting the CDNI Logging interface) or the entity the entity transmitting the CDNI Logging File (e.g. the host in
responsible for transmitting the CDNI Logging File (e.g. the a dCDN supporting the CDNI Logging interface) or the entity
responsible for transmitting the CDNI Logging File (e.g. the
dCDN). dCDN).
* occurrence: there MUST be zero or one instance of this * occurrence: there MUST be zero or one instance of this
directive. This directive MAY be added by the uCDN. It MUST directive. This directive MAY be added by the uCDN. It MUST
NOT be included by the dCDN. The mechanisms used by the uCDN NOT be included by the dCDN. The mechanisms used by the uCDN
to establih and validate the entity respondible for the CDNI to establih and validate the entity respondible for the CDNI
Logging File is outside the scope of the present document. We Logging File is outside the scope of the present document. We
observe that, in particular, this may be achieved through observe that, in particular, this may be achieved through
authentication mechanisms that are part of the CDNI Logging authentication mechanisms that are part of the CDNI Logging
File pull mechanism (Section 4.2). File pull mechanism (Section 4.2).
o Record-Type: o Record-Type:
* format: <string> * format: NHTABSTRING
* semantic: indicates the type of the CDNI Logging Records that * directive value: indicates the type of the CDNI Logging Records
follow this directive, until another Record-Type directive (or that follow this directive, until another Record-Type directive
the end of the CDNI Logging File). "cdni_http_request_v1" MUST (or the end of the CDNI Logging File). "cdni_http_request_v1"
be indicated in the Record-Type directive for CDNI Logging MUST be indicated as the Record-Type directive value for CDNI
records corresponding to HTTP request (e.g. a HTTP delivery Logging records corresponding to HTTP request (e.g. a HTTP
request) as specified in Section 3.2.1. delivery request) as specified in Section 3.4.1.
* occurrence: there MUST be at least one instance of this * occurrence: there MUST be at least one instance of this
directive. The first instance of this directive MUST precede a directive. The first instance of this directive MUST precede a
Fields directive and precede any CDNI Logging Record. Fields directive and precede any CDNI Logging Record.
o Fields: o Fields:
* format: <field-name>[ <field-name>], where the allowed list of * format: FIENAME *<HTAB FIENAME> ; where FIENAME is specified in
<field-name> are specified for each Record-Type in Section 3.2. Section 3.4.
* semantic: this lists the names of all the fields for which a * directive value: this lists the names of all the fields for
value is to appear in the CDNI Logging Records that are after which a value is to appear in the CDNI Logging Records that are
this directive. The names of the fields, as well as their after this directive. The names of the fields, as well as
possible occurrences, are specified for each type of CDNI their possible occurrences, are specified for each type of CDNI
Logging Records in Section 3.2. The field names listed in this Logging Records in Section 3.4.
directive MUST be separated by the "horizontal tabulation
(TAB)" character.
* occurrence: there MUST be at least one instance of this * occurrence: there MUST be at least one instance of this
directive per Record-Type directive. The first instance of directive per Record-Type directive. The first instance of
this directive for a given Record-Type MUST precede any CDNI this directive for a given Record-Type MUST precede any CDNI
Logging Record for this Record-Type. Logging Record for this Record-Type.
o Integrity-Hash: o Integrity-Hash:
* format: <string> * format: 32HEXDIG
* semantic: This directive permits the detection of a corrupted * directive value: This directive permits the detection of a
CDNI Logging File. This can be useful, for instance, if a corrupted CDNI Logging File. This can be useful, for instance,
problem occurs on the filesystem of the dCDN Logging system and if a problem occurs on the filesystem of the dCDN Logging
leads to a truncation of a logging file. The Integrity-Hash system and leads to a truncation of a logging file. The
value is computed, and included in this directive by the entity Integrity-Hash value is computed, and included in this
that transmits the CDNI Logging File. It is computed by directive by the entity that transmits the CDNI Logging File.
applying the MD5 ([RFC1321]) cryptographic hash function on the It is computed by applying the MD5 ([RFC1321]) cryptographic
CDNI Logging File, including all the directives and logging hash function on the CDNI Logging File, including all the
records, up to the Intergrity-Hash directive itself, excluding directives and logging records, up to the Intergrity-Hash
the Integrity-Hash directive itself and, when present, also directive itself, excluding the Integrity-Hash directive itself
excluding the Non-Repudiation-Hash directive. The Integrity- and, when present, also excluding the Non-Repudiation-Hash
Hash value is represented as a US-ASCII encoded hexadecimal directive. The Integrity-Hash value is represented as a US-
number, 32 digits long (representing a 128 bit hash value). ASCII encoded hexadecimal number, 32 digits long (representing
The entity receiving the CDNI Logging File also computes in a a 128 bit hash value). The entity receiving the CDNI Logging
similar way the MD5 hash on the received CDNI Logging File and File also computes in a similar way the MD5 hash on the
compares this hash to the value of the Integrity-Hash received CDNI Logging File and compares this hash to the value
directive. If the two values are equal, then the received CDNI of the Integrity-Hash directive. If the two values are equal,
Logging File MUST be considered non-corrupted. If the two then the received CDNI Logging File MUST be considered non-
values are different, the received CDNI Logging File MUST be corrupted. If the two values are different, the received CDNI
considered corrupted. The behavior of the entity that received Logging File MUST be considered corrupted. The behavior of the
a corrupted CDNI Logging File is outside the scope of this entity that received a corrupted CDNI Logging File is outside
specification; we note that the entity MAY attempt to pull the scope of this specification; we note that the entity MAY
again the same CDNI Logging file from the transmitting entity. attempt to pull again the same CDNI Logging file from the
If the entity receiving the CDNI Logging File adds a Verified- transmitting entity. If the entity receiving the CDNI Logging
Origin directive, it MUST recompute and update the Integrity- File adds a Verified-Origin directive, it MUST recompute and
Hash directive so it also protects the added Verified-Origin update the Integrity-Hash directive so it also protects the
directive. added Verified-Origin directive.
* occurrence: there MUST be zero or one instance of this * occurrence: there MUST be zero or one instance of this
directive. There SHOULD be one instance of this directive. directive. There SHOULD be one instance of this directive.
One situation where that directive could be omitted is where One situation where that directive could be omitted is where
integrity protection is already provided via another mechanism integrity protection is already provided via another mechanism
(for example if an integrity hash is associated to the CDNI (for example if an integrity hash is associated to the CDNI
Logging file out of band through the CDNI Logging Logging Feed Logging file out of band through the CDNI Logging Logging Feed
Section 4.1 leveraging ATOM extensions such as those proposed Section 4.1 leveraging ATOM extensions such as those proposed
in [I-D.snell-atompub-link-extensions]. When present, this in [I-D.snell-atompub-link-extensions]. When present, this
field MUST be the last line of the CDNI Logging File when the field MUST be the last line of the CDNI Logging File when the
Non-Repudiation-Hash is absent, and MUST be the one before last Non-Repudiation-Hash is absent, and MUST be the one before last
line of the CDNI Logging File when the Non-Repudiation-Hash is line of the CDNI Logging File when the Non-Repudiation-Hash is
present. present.
skipping to change at page 19, line 52 skipping to change at page 21, line 18
Logging file out of band through the CDNI Logging Logging Feed Logging file out of band through the CDNI Logging Logging Feed
Section 4.1 leveraging ATOM extensions such as those proposed Section 4.1 leveraging ATOM extensions such as those proposed
in [I-D.snell-atompub-link-extensions]. When present, this in [I-D.snell-atompub-link-extensions]. When present, this
field MUST be the last line of the CDNI Logging File when the field MUST be the last line of the CDNI Logging File when the
Non-Repudiation-Hash is absent, and MUST be the one before last Non-Repudiation-Hash is absent, and MUST be the one before last
line of the CDNI Logging File when the Non-Repudiation-Hash is line of the CDNI Logging File when the Non-Repudiation-Hash is
present. present.
o Non-Repudiation-Signature: o Non-Repudiation-Signature:
* format: <string> * format: QSTRING [Editor's Note: revisit format once this field
* semantic: This field contains a signature that supports the is specified]
non-repudiation of the CDNI Logging File by the entity that
* directive value: This field contains a signature that supports
the non-repudiation of the CDNI Logging File by the entity that
transmitted the CDNI Logging File. [Editor's Note: Detailed transmitted the CDNI Logging File. [Editor's Note: Detailed
description To Be Added. David Mandelberg has the lead for description To Be Added. David Mandelberg has the lead for
drafting text.The text needs to indicate that the Claimed- drafting text.The text needs to indicate that the Claimed-
Origin directive MUST be covered and the Verified-Origin Origin directive MUST be covered and the Verified-Origin
directive MUST NOT be covered by the signature. We may want to directive MUST NOT be covered by the signature. We may want to
refer to RFC4949 for terminology around Non-Redudiation] refer to RFC4949 for terminology around Non-Redudiation]
* occurrence: there MAY be one and only one instance of this * occurrence: there MAY be one and only one instance of this
directive. When present, this directive MUST be the last line directive. When present, this directive MUST be the last line
of the CDNI Logging File. of the CDNI Logging File.
3.2. Logging Records 3.4. CDNI Logging Records
A CDNI Logging Record consists of a sequence of CDNI Logging Fields A CDNI Logging Record consists of a sequence of CDNI Logging Fields
relating to that single CDNI Logging Record. relating to that single CDNI Logging Record.
CDNI Logging Fields MUST be separated by the "horizontal tabulation CDNI Logging Fields MUST be separated by the "horizontal tabulation
(TAB)" character. (HTAB)" character.
Some CDNI Logging field names use a prefix scheme similar to the one To facilitate readability, a prefix scheme is used for CDNI Logging
used in W3C Extended Log File Format [ELF] to facilitate readability. field names in a similar way to the one used in W3C Extended Log File
The semantics of the prefix in the present document is: Format [ELF] . The semantics of the prefix in the present document
is:
o c: refers to the User Agent that issues the request (corresponds o c: refers to the User Agent that issues the request (corresponds
to the "client" of W3C Extended Log Format) to the "client" of W3C Extended Log Format)
o d: refers to the dCDN (relative to a given CDN acting as a uCDN) o d: refers to the dCDN (relative to a given CDN acting as a uCDN)
o s: refers to the dCDN Surrogate that serves the request o s: refers to the dCDN Surrogate that serves the request
(corresponds to the "server" of W3C Extended Log Format) (corresponds to the "server" of W3C Extended Log Format)
o u: refers to the uCDN (relative to a given CDN acting as a dCDN) o u: refers to the uCDN (relative to a given CDN acting as a dCDN)
o x: refers to extensions for vendor-specific logging fields
o cs: refers to communication from the dCDN Surrogate towards the o cs: refers to communication from the dCDN Surrogate towards the
User-Agent User-Agent
o sc: refers to communication from the User-Agent towards the dCDN o sc: refers to communication from the User-Agent towards the dCDN
Surrogate Surrogate
An implementation of the CDNI Logging interface as per the present An implementation of the CDNI Logging interface as per the present
specification MUST support the CDNI HTTP Delivery Records as specification MUST support the CDNI HTTP Delivery Records as
specified in Section 3.2.1. [Editor's Note": other types of delivery specified in Section 3.4.1. [Editor's Note": other types of delivery
records will be listed here if we specify other types for this records will be listed here if we specify other types for this
version eg Request Routing]. version eg Request Routing].
The formats listed in this section in the form <...> are specified in A CDNI Logging Record is defined by the following rules:
Section 3.3).
3.2.1. HTTP Request Logging Record FIEVAL = <CDNI Logging Field value>
The HTTP Request Logging Record contains the following CDNI Logging <CDNI Logging Record> = FIEVAL *<HTAB FIEVAL> ; where FIEVAL
contains the CDNI Logging field values corresponding to the CDNI
Logging field names (FIENAME) listed is the last Fields directive
predecing the present CDNI Logging Record.
FIENAME = "date" / "time" / "time-taken" / "c-ip" / "c-ip-
anonimizing" / "c-port" / "s-ip" / "s-hostname" / "s-port" / "cs-
method" / "cs-uri" / "u-uri" / "protocol" / "sc-status" / "sc-
total-bytes" / "sc-entity-bytes" / "cs(" <HTTP-header> ")" / "sc("
<HTTP-header> ")" / "s-ccid" / "s-sid" / "s-cached" / "s-uri-
signing" / "x-" <vendor-ID> "-" <vendor-specific-cdni-logging-
field-name>
3.4.1. HTTP Request Logging Record
The HTTP Request Logging Record is a CDNI Logging Record of Record-
Type "cdni_http_request_v1". It contains the following CDNI Logging
Fields, listed by their field name: Fields, listed by their field name:
o date: o date:
* format: <date> * format: DATE
* semantic: the date at which the processing of request completed * field value: the date at which the processing of request
on the Surrogate. completed on the Surrogate.
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
field. field.
o time: o time:
* format: <time> * format: TIME
* semantic: the time at which the processing of request completed * field value: the time at which the processing of request
on the Surrogate. completed on the Surrogate.
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
field. field.
o time-taken: o time-taken:
* format: <fixed> * format: DEC
* semantic: duration, in seconds, between the start of the * field value: decimal value of the duration, in seconds, between
processing of the request and the completion of the delivery by the start of the processing of the request and the completion
the Surrogate. of the request processing (e.g. completion of delivery) by the
Surrogate.
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
field. field.
o c-ip: o c-ip:
* format: <address> * format: ADDRESS
* semantic: the source IPv4 or IPv6 address (i.e. the "client" * field value: the source IPv4 or IPv6 address (i.e. the "client"
address) in the request received by the Surrogate. address) in the request received by the Surrogate.
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
field. field.
o c-ip-anonimizing: o c-ip-anonimizing:
* format: <integer> * format: 1*DIGIT
* semantic: the number of bits of the address in the c-ip field * field value: the number of rightmost bits of the address in the
that are zeroed-out in order to anonymize the logging record. c-ip field that are zeroed-out in order to anonymize the
The mechanism by which the two ends of teh CDNI Logging logging record. The mechanism by which the two ends of the
nterafce agree on whether anonimization is to be supported and CDNI Logging interface agree on whether anonimization is to be
the number of bits that need to be zeroed-out for this purpose supported and the number of bits that need to be zeroed-out for
are outside the scope of the present document. this purpose are outside the scope of the present document.
* occurrence: there MUST be zero or one instance of this field. * occurrence: there MUST be zero or one instance of this field.
o c-port: o c-port:
* format: <integer> * format: 1*DIGIT
* semantic: the source TCP port (i.e. the "client" port) in the * field value: the source TCP port (i.e. the "client" port) in
request received by the Surrogate. the request received by the Surrogate.
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o s-ip: o s-ip:
* format: <address> * format: ADDRESS
* semantic: the IPv4 or IPv6 address of the Surrogate that served * field value: the IPv4 or IPv6 address of the Surrogate that
the request (i.e. the "server" address). served the request (i.e. the "server" address).
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o s-hostname: o s-hostname:
* format: <host> * format: host
* semantic: the hostname of the Surrogate that served the request * field value: the hostname of the Surrogate that served the
(i.e. the "server" hostname). request (i.e. the "server" hostname).
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o s-port: o s-port:
* format: <integer> * format: 1*DIGIT
* semantic: the destination TCP port (i.e. the "server" port) in
the request received by the Surrogate. * field value: the destination TCP port (i.e. the "server" port)
in the request received by the Surrogate.
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o cs-method: o cs-method:
* format: <string> * format: NHTABSTRING
* semantic: this is the HTTP method of the HTTP request received * field value: this is the HTTP method of the HTTP request
by the Surrogate. received by the Surrogate.
* occurrence: There MUST be one and only one instance of this * occurrence: There MUST be one and only one instance of this
field. field.
o cs-uri: o cs-uri:
* format: <uri> * format: NHTABSTRING
* semantic: this is the complete http_URL (as specified in * field value: this is the complete URL of the request received
[RFC2616]) of the request received by the Surrogate. by the Surrogate. It is exactly in the format of a http_URL
specified in [RFC2616]) or, when the request was a HTTPS
request ([RFC2818]), it is in the format of a http_URL but with
the scheme part set to "https" instead of "http".
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o u-uri: o u-uri:
* format: <uri> * format: NHTABSTRING
* semantic: this is a complete http_URL (as specified in * field value: this is a complete URL, derived from the complete
[RFC2616]) derived from the complete URI of the request URI of the request received by the Surrogate (i.e. the cs-uri)
received by the Surrogate but transformed by the entity but transformed by the entity generating or transmitting the
generating or transmitting the CDNI Logging Record, in a way CDNI Logging Record, in a way that is agreed upon between the
that is agreed upon between the two ends of the CDNI Logging two ends of the CDNI Logging interface, so the transformed URI
interface, so the transformed URI is meaningful to the uCDN. is meaningful to the uCDN. For example, the two ends of the
For example, the two ends of the CDNI Logging interface could CDNI Logging interface could agree that the u-uri is
agree that the u-uri is constructed from the cs-uri by removing constructed from the cs-uri by removing the part of the
the part of the hostname that exposes which individual hostname that exposes which individual Surrogate actually
Surrogate actually performed the delivery. The details of performed the delivery. The details of modification performed
modification performed to generate the u-uri, as well as the to generate the u-uri, as well as the mechanism to agree on
mechanism to agree on these modifications between the two sides these modifications between the two sides of the CDNI Logging
of the CDNI Logging interface are outside the scope of the interface are outside the scope of the present document.
present document.
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
field. field.
o protocol: o protocol:
* format: <string> * format: NHTABSTRING
* semantic: this is value of the HTTP-Version field as specified * field value: this is value of the HTTP-Version field as
in [RFC2616] of the Request-Line of the request received by the specified in [RFC2616] of the Request-Line of the request
Surrogate (e.g. "HTTP/1.1"). received by the Surrogate (e.g. "HTTP/1.1").
* occurrence: there MUST be one and only one instance of this * occurrence: there MUST be one and only one instance of this
field. field.
o sc-status: o sc-status:
* format: <digit><digit><digit> * format: 3DIGIT
* semantic: this is the HTTP Status-Code in the HTTP response * field value: this is the HTTP Status-Code in the HTTP response
from the Surrogate. from the Surrogate.
* occurrence: There MUST be one and only one instance of this * occurrence: There MUST be one and only one instance of this
field. field.
o sc-total-bytes: o sc-total-bytes:
* format: <integer> * format: 1*DIGIT
* semantic: this is the total number of bytes of the HTTP * field value: this is the total number of bytes of the HTTP
response sent by the Surrogate in response to the request. response sent by the Surrogate in response to the request.
This includes the bytes of the Status-Line (including HTTP This includes the bytes of the Status-Line (including HTTP
headers) and of the message-body. headers) and of the message-body.
* occurrence: There MUST be one and only one instance of this * occurrence: There MUST be one and only one instance of this
field. field.
o sc-entity-bytes: o sc-entity-bytes:
* format: <integer> * format: 1*DIGIT
* semantic: this is the number of bytes of the message-body in * field value: this is the number of bytes of the message-body in
the HTTP response sent by the Surrogate in response to the the HTTP response sent by the Surrogate in response to the
request. This does not include the bytes of the Status-Line request. This does not include the bytes of the Status-Line
(and therefore does not include the bytes of the HTTP headers). (and therefore does not include the bytes of the HTTP headers).
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o cs(<HTTP-header>): o cs(<HTTP-header-name>):
* format: <string> * format: QSTRING
* semantic: the value of the HTTP header identified in the field
name as it appears in the request processed by the Surrogate. * field value: the value of the HTTP header (identified by the
<HTTP-header-name> in the CDNI Logging field name) as it
appears in the request processed by the Surrogate. For
example, when the CDNI Logging field name (FIENAME) listed in
the prededing Fields directive is "cs(User-Agent"), this CDNI
Logging field value contains the value of the User-Agent HTTP
header as received by the Surrogate in the request it
processed.
* occurrence: there MUST be zero, one or any number of instance * occurrence: there MUST be zero, one or any number of instance
of this field. of this field.
o sc(<HTTP-header>): o sc(<HTTP-header-name>):
* format: <string> * format: QSTRING
* semantic: the value of the HTTP header identified in the field * field value: the value of the HTTP header (identified by the
name as it appears in the response issued by the Surrogate to <HTTP-header-name> in the CDNI Logging field name) as it
serve the request. appears in the response issued by the Surrogate to serve the
request.
* occurrence: there MUST be zero, one or any number of instance * occurrence: there MUST be zero, one or any number of instance
of this field. of this field.
o s-ccid: o s-ccid:
* format: [Editor's Note: to be based on cdni-metadata or * format: QSTRING
relevant companion I-D]
* semantic: this contains the value of the Content Collection * field value: this contains the value of the Content Collection
IDentifier specified in [I-D.ietf-cdni-metadata] and associated IDentifier associated by the uCDN to the content served by the
to the content served by the Surrogate through the CDNI Surrogate via the CDNI Metadata interface
Metadata interface. ([I-D.ietf-cdni-metadata]).
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o s-sid: o s-sid:
* format: [Editor's Note: add reference to the I-D defining the * format: QSTRING
format of Session ID>?]
* semantic: this contains the value of the Session IDentifier * field value: this contains the value of a Session IDentifier
specified in ??? and associated to the served request by the generated by the dCDN for a specific HTTP Adaptive Streaming
Surrogate. (HAS) session and whose value is included in the Logging record
for every content chunk delivery of that session in view of
facilitating the later correlation of all the per content chunk
log records of a given HAS session. See section 3.4.2.2. of
[I-D.brandenburg-cdni-has] for more discussion on the concept
of Session IDentifier.
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o s-cached: [Editor's Note: W3C uses "cached" . is "s-cached" o s-cached:
better?]
* format: <string> * format: 1DIGIT
* semantic: this characterises whether the Surrogate could serve * field value: this characterises whether the Surrogate could
the request using content already stored on its local cache. serve the request using content already stored on its local
The allowed values are "0" (for miss) and "1" for hit). "1" cache. The allowed values are "0" (for miss) and "1" for hit).
MUST be used when the Surrogate could serve the request using "1" MUST be used when the Surrogate could serve the request
exclusively content already stored on its local cache. "0" using exclusively content already stored on its local cache.
MUST be used otherwise (including cases where the Surrogate "0" MUST be used otherwise (including cases where the Surrogate
served the request using some, but not all, content already served the request using some, but not all, content already
stored on its local cache). Note that a "0" only means a cache stored on its local cache). Note that a "0" only means a cache
miss in the Surrogate and does not provide any information on miss in the Surrogate and does not provide any information on
whether the content was already stored, or not, in another whether the content was already stored, or not, in another
device of the dCDN i.e. whether this was a "dCDN hit" or "dCDN device of the dCDN i.e. whether this was a "dCDN hit" or "dCDN
miss". miss".
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o s-uri-signing: o s-uri-signing:
* format: <string> * format: 1DIGIT
* semantic: this characterises the uri signing validation * field value: this characterises the uri signing validation
performed by the Surrogate on the request. The allowed values performed by the Surrogate on the request. The allowed values
are: are:
* *
+ "0" : no uri signature validation performed + "0" : no uri signature validation performed
+ "1" : uri signature validation performed and validated + "1" : uri signature validation performed and validated
+ "2" : uri signature validation performed and rejected + "2" : uri signature validation performed and rejected
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field.
o x-"vendor-ID"-"vendor-specific-cdni-logging-field-name":
* format: specified by the vendor for the actual vendor-specific
logging field. This format is outside the scope of the present
document.
* field value: this contains a vendor specific logging field.
The "vendor-ID" identifies the vendor and the "vendor-specific-
cdni-logging-field-name" identifies the actual vendor-specific
logging field. For example, a vendor specific field name would
look like "x-vendor1-important_info1".
* occurrence: there MUST be zero, one or any number of instance
of this field
The "Fields" directive corresponding to a HTTP Request Logging Record The "Fields" directive corresponding to a HTTP Request Logging Record
MUST list all the fields whose occurrence is specified above as MUST list all the fields name whose occurrence is specified above as
"There MUST be one and only one instance of this field". These "There MUST be one and only one instance of this field". The
fields MUST be present in every HTTP Request Logging Record. corresponding fields value MUST be present in every HTTP Request
Logging Record.
The "Fields" directive corresponding to a HTTP Request Logging Record The "Fields" directive corresponding to a HTTP Request Logging Record
MAY list all the fields whose occurrence is specified above as "there MAY list all the fields value whose occurrence is specified above as
MUST be zero or exactly one instance of this field" or "there MUST be "there MUST be zero or exactly one instance of this field" or "there
zero, one or any number of instance of this field". The set of such MUST be zero, one or any number of instance of this field". The set
fields actually listed in the "Fields" directive is selected by the of such fields name actually listed in the "Fields" directive is
implementation generating the CDNI Logging File based on agreements selected by the implementation generating the CDNI Logging File based
between the interconnected CDNs established through mechanisms on agreements between the interconnected CDNs established through
outside the scope of this specification (e.g. contractual mechanisms outside the scope of this specification (e.g. contractual
agreements) . When such a field is not listed in the "Fields" agreements) . When such a field name is not listed in the "Fields"
directive, it MUST NOT be included in the Logging Record. When such directive, the corresponding field value MUST NOT be included in the
a field is listed in the "Fields" directive, it MUST be included in Logging Record. When such a field name is listed in the "Fields"
the Logging Record; in that case, if the value for the field is not directive, the corresponding field value MUST be included in the
Logging Record; in that case, if the value for the field is not
available, this MUST be conveyed via a dash character ("-"). available, this MUST be conveyed via a dash character ("-").
The fields listed in the "Fields" directive can be listed in the The fields name listed in the "Fields" directive MAY be listed in the
order in which they are listed in Section 3.2.1 or in any other order in which they are listed in Section 3.4.1 or MAY be listed in
order. any other order.
[Editor's Note: discuss private fields ]
3.2.2. CDNI Logging File Example
#Version:1.0<CRLF> 3.5. CDNI Logging File Example
#UUID: urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6???<CRLF> #Version:<HTAB>CDNI/1.0<CRLF>
#Claimed-Origin: cdni-logging-entity.dcdn.example.com<CRLF> #UUID:<HTAB>"urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6"<CRLF>
#Record-Type: cdni_http_request_v1<CRLF> #Claimed-Origin:<HTAB>cdni-logging-entity.dcdn.example.com<CRLF>
#Fields:<TAB>date<TAB>time<TAB>time-taken<TAB>c-ip<TAB>cs- #Record-Type:<HTAB>cdni_http_request_v1<CRLF>
method<TAB>u-uri<TAB>protocol<TAB>sc-status<TAB>sc-total-bytes<TAB>cs
(User-Agent)<TAB>cs(Referer)<TAB>s-cached<CRLF>
2013-05-17<TAB>00:38:06.825<TAB>88.958<TAB>10.5.7.1<TAB>GET<TAB>http #Fields:<HTAB>date<HTAB>time<TAB>time-taken<HTAB>c-ip<HTAB>cs-
://cdni-ucdn.dcdn.example.com/video/movie100.mp4<TAB>HTTP/ method<HTAB>u-uri<HTAB>protocol<HTAB>sc-status<HTAB>sc-total-
1.1<TAB>200<TAB>672989<TAB>Mozilla/5.0 (Windows; U; Windows NT 6.0; bytes<HTAB>cs(User-Agent)<HTAB>cs(Referer)<HTAB>s-cached<CRLF>
en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127
Safari /533.4<TAB>host1.example.com <TAB>1<CRLF>
2013-05-17<TAB>00:39:09.145<TAB>169.790<TAB>10.5.10.5<TAB>GET<TAB>htt 2013-05-17<HTAB>00:38:06.825<HTAB>88.958<HTAB>10.5.7.1<HTAB>GET<HTAB>
p://cdni-ucdn.dcdn.example.com/video/movie118.mp4<TAB>HTTP/ http://cdni-ucdn.dcdn.example.com/video/movie100.mp4<HTAB>HTTP/
1.1<TAB>200<TAB>1579920<TAB>Mozilla/5.0 (Windows; U; Windows NT 6.0; 1.1<HTAB>200<HTAB>672989<HTAB>"Mozilla/5.0 (Windows; U; Windows NT
en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127
Safari /533.4<TAB>host1.example.com<TAB>1<CRLF> Safari /533.4"<HTAB>"host1.example.com"<HTAB>1<CRLF>
2013-05-17<HTAB>00:39:09.145<HTAB>169.790<HTAB>10.5.10.5<HTAB>GET<HTA
B>http://cdni-ucdn.dcdn.example.com/video/movie118.mp4<HTAB>HTTP/
1.1<HTAB>200<HTAB>1579920<HTAB>"Mozilla/5.0 (Windows; U; Windows NT
6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127
Safari /533.4"<HTAB>"host1.example.com"<HTAB>1<CRLF>
2013-05-17<TAB>00:42:53.437<TAB>2.879<TAB>10.5.10.5<TAB>GET<TAB>http 2013-05-17<HTAB>00:42:53.437<HTAB>2.879<HTAB>10.5.10.5<HTAB>GET<HTAB>
://cdni-ucdn.dcdn.example.com/video/picture11.mp4<TAB>HTTP/ http://cdni-ucdn.dcdn.example.com/video/picture11.mp4<HTAB>HTTP/
1.0<TAB>200<TAB>17724<TAB>Mozilla/5.0 (Windows; U; Windows NT 6.0; 1.0<HTAB>200<HTAB>17724<HTAB>"Mozilla/5.0 (Windows; U; Windows NT
en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 6.0; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127
Safari /533.4<TAB>host5.example.com<TAB>0<CRLF> Safari /533.4"<HTAB>"host5.example.com"<HTAB>0<CRLF>
#Integrity-Hash: 9e107d9d372bb6826bd81d3542a419d6 [Editor's Note: #Integrity-Hash: 9e107d9d372bb6826bd81d3542a419d6 [Editor's Note:
include the correct MD5-hash value for the actual example]<CRLF> include the correct MD5-hash value for the actual example]<CRLF>
3.3. Fields and Directives Formats
[Editor's Note: still needs work to minimise the number of types
defined across this section and specific types defined inside the
field definitions themselves]
o <digit> = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" |
"9"
o <integer> = 1*<digit>
o <address> = <integer> [ "." *<integer> ] [ ":" <integer> ]
o <host> = as specified in [RFC3986].
o <date> = 4<digit> "-" 2<digit> "-" 2<digit>
* Dates are recorded in the format YYYY-MM-DD where YYYY, MM and
DD stand for the numeric year, month and day respectively. All
dates are specified in Universal Time Coordinated (UTC).
o <time> = 2<digit> ":" 2<digit> ":" 2<digit> ["." *<digit>]
* Times are recorded in the form HH:MM:SS or HH:MM:SS.S where HH
is the hour in 24 hour format, MM is minutes and SS is seconds.
All times are specified in Universal Time Coordinated (UTC).
o <uri> = <string> containing a http_URL as specified in [RFC2616].
o <fixed> = Fixed Format Float = 1*<digit> [. *<digit>]
o <HTTP-header> = <string> containing a HTTP header field name (e.g.
"User-Agent", "Referer") as specified in [RFC2616].
4. CDNI Logging File Exchange Protocol 4. CDNI Logging File Exchange Protocol
This document specifies a protocol for the exchange of CDNI Logging This document specifies a protocol for the exchange of CDNI Logging
Files as specified in Section 3. Files as specified in Section 3.
This protocol comprises: This protocol comprises:
o a CDNI Logging feed, allowing the dCDN to notify the uCDN about o a CDNI Logging feed, allowing the dCDN to notify the uCDN about
the CDNI Logging files that can be retrieved by that uCDN from the the CDNI Logging files that can be retrieved by that uCDN from the
dCDN, as well as all the information necessary for retrieving each dCDN, as well as all the information necessary for retrieving each
of these CDNI Logging File. The CDNI Logging feed is specified in of these CDNI Logging File. The CDNI Logging feed is specified in
Section 4.1. Section 4.1.
o a CDNI Logging File pull mechanism, allowing the uCDN to obtain o a CDNI Logging File pull mechanism, allowing the uCDN to obtain
from the dCDN a given CDNI Logging File at the uCDN convenience. from the dCDN a given CDNI Logging File at the uCDN convenience.
The CDNI Logging File pull mechanisms is specified in Section 4.2. The CDNI Logging File pull mechanisms is specified in Section 4.2.
An implementation of the CDNI Logging interface as per the present An implementation of the CDNI Logging interface as per the present
document generating CDNI Logging file (i.e. on the dCDN side) MUST document generating CDNI Logging file (i.e. on the dCDN side) MUST
support the server side of the CDNI Logging feed and the server side support the server side of the CDNI Logging feed and the server side
of the CDNI Logging pull mechanism. of the CDNI Logging pull mechanism.
An implementation of the CDNI Logging interface as per the present An implementation of the CDNI Logging interface as per the present
document consuming CDNI Logging file (i.e. on the uCDN side) MUST document consuming CDNI Logging file (i.e. on the uCDN side) MUST
support the client side of the CDNI Logging feed and the client side support the client side of the CDNI Logging feed and the client side
of the CDNI Logging pull mechanism. of the CDNI Logging pull mechanism.
[Editor's note: verify that the client side and server side are well [Editor's note: verify that the client side and server side are well
defined in the respective sections] defined in the respective sections]
We note that implementations of the CDNI Logging interface MAY also We note that implementations of the CDNI Logging interface MAY also
support other mechanisms to exchange CDNI Logging Files, for example support other mechanisms to exchange CDNI Logging Files, for example
in view of exchanging logging information with minimum time-lag (e.g. in view of exchanging logging information with minimum time-lag (e.g.
sub-minute or sub-second) between when the event occurred in the dCDN sub-minute or sub-second) between when the event occurred in the dCDN
and when the corresponding Logging Record is made available to the and when the corresponding Logging Record is made available to the
uCDN (e.g. for log-consuming applications requiring extremely fresh uCDN (e.g. for log-consuming applications requiring extremely fresh
logging information such as near-real-time content delivery logging information such as near-real-time content delivery
monitoring). Such mechanism might be defined in future version of monitoring). Such mechanism might be defined in future version of
the present document. the present document.
4.1. CDNI Logging Feed 4.1. CDNI Logging Feed
[Editor's Note: text to be added. Feed is based on ATOM and contains [Editor's Note: text to be added. Feed is based on ATOM and contains
a UUID + URI for each CDNI Logging File in "window" - if appropriate a UUID + URI for each CDNI Logging File in "window" - if appropriate
the text should refer to the side generating the CDNI Logging Feed the text should refer to the side generating the CDNI Logging Feed
"as server-side", and the side consuming the Feed as the client- "as server-side", and the side consuming the Feed as the client-
side]. side].
4.2. CDNI Logging File Pull 4.2. CDNI Logging File Pull
A client-side implementation of the CDNI Logging interface MAY pull A client-side implementation of the CDNI Logging interface MAY pull
at its convenience any CDNI Logging File that is advertised by the at its convenience any CDNI Logging File that is advertised by the
server-side in the CDNI Logging Feed. To do so, the client-side: server-side in the CDNI Logging Feed. To do so, the client-side:
o MUST use HTTP v1.1 o MUST use HTTP v1.1
o SHOULD use TLS (i.e. use what is loosely referred to as "HTTPS") o SHOULD use TLS (i.e. use what is loosely referred to as "HTTPS")
o MUST use the URI associated to the CDNI Logging File in the CDNI o MUST use the URI associated to the CDNI Logging File in the CDNI
Logging Feed Logging Feed
o SHOULD indicate the compression schemes it supports o SHOULD indicate the compression schemes it supports
Note that a client-side implementation of the CDNI Logging interface Note that a client-side implementation of the CDNI Logging interface
MAY pull a CDNI Logging File that it has already pulled, as long as MAY pull a CDNI Logging File that it has already pulled, as long as
the file is still advertised by the server-side in the CDNI Logging the file is still advertised by the server-side in the CDNI Logging
Feed. Feed.
skipping to change at page 30, line 36 skipping to change at page 32, line 14
o when the client-side request indicates client-supported o when the client-side request indicates client-supported
compression schemes, SHOULD use a compression scheme that it compression schemes, SHOULD use a compression scheme that it
supports and is supported by the client-side supports and is supported by the client-side
[Editor's Note: discuss Non-Repudiation : it is a nice to have and [Editor's Note: discuss Non-Repudiation : it is a nice to have and
how it could be supported, via a different digest than the one for how it could be supported, via a different digest than the one for
integrity] integrity]
5. Open Issues 5. Open Issues
o What separator should be used between a directive name and a
directive value e.g. "#Version:1.0" or "#Version: 1.0" or
"#Version:<TAB>1.0"?
o Compression: <Ben>When we say the server MUST support gzip & o Compression: <Ben>When we say the server MUST support gzip &
deflate we probably need to think through whether we mean content- deflate we probably need to think through whether we mean content-
encoding, transfer-encoding or both. The semantics get a little encoding, transfer-encoding or both. The semantics get a little
confusing so we probably just need to think them through to ensure confusing so we probably just need to think them through to ensure
we allow a server to store compressed logs as transmit them we allow a server to store compressed logs as transmit them
compressed. compressed.
o Handling of Event logs and notifications: There are two aspects of o Handling of Event logs and notifications: There are two aspects of
that question: that question:
* non-real-time exchange of event logs from dCDN to uCDN for * non-real-time exchange of event logs from dCDN to uCDN for
audit purposes. This could be added to current spec presumably audit purposes. This could be added to current spec presumably
in the form of additional Record-Types and without requiring a in the form of additional Record-Types and without requiring a
significant change to the current CDNI LOgging file exchange significant change to the current CDNI LOgging file exchange
approach. It is proposed that this be handled as a [MED] approach. It is proposed that this be handled as a [MED]
requirement. e.g. try first specify what events and what requirement. e.g. try first specify what events and what
information needs to be exchanged; and depending on progress, information needs to be exchanged; and depending on progress,
decide to include in initial logging spec or not decide to include in initial logging spec or not
* real-time exchange of event notification from dCDN to uCDN for * real-time exchange of event notification from dCDN to uCDN for
immediate operational action (eg on notification by dCDN that immediate operational action (eg on notification by dCDN that
dCDN request routing is down, uCDN stops redirecting to this dCDN request routing is down, uCDN stops redirecting to this
dCDN). This would presumably require definition/extension of dCDN). This would presumably require definition/extension of
another CDNI interface or significant change/extension to the another CDNI interface or significant change/extension to the
current CDNI logging spec. It is proposed that thisbe kept out current CDNI logging spec. It is proposed that thisbe kept out
of the scope of the current cdni-logging spec . of the scope of the current cdni-logging spec .
Another question is what set of events should be logged/notified. Another question is what set of events should be logged/notified.
The first type of events realtes to "service-level" events i.e. The first type of events realtes to "service-level" events i.e.
high level events that affect the service that the dCDN is high level events that affect the service that the dCDN is
providing to the uCDN (e.g.dCDN request routing is down, dCDN is providing to the uCDN (e.g.dCDN request routing is down, dCDN is
overloaded). There is general agreements that it is desirable to overloaded). There is general agreements that it is desirable to
be able to log/notify such service-level events. The second type be able to log/notify such service-level events. The second type
of events is "atomic-level" events i.e. low level events that may of events is "atomic-level" events i.e. low level events that may
be useful to identify or track a component issue or a delivery be useful to identify or track a component issue or a delivery
issue. logging/notifying about such events may be useful in some issue. logging/notifying about such events may be useful in some
situations (eg uCDN and dCDN have a particular relationship situations (eg uCDN and dCDN have a particular relationship
allowing them to share detailed operational information) and may allowing them to share detailed operational information) and may
not be useful in some situations (because the dCDN does not want not be useful in some situations (because the dCDN does not want
to expose details of its CDN operation). Ideal approach is to to expose details of its CDN operation). Ideal approach is to
define both types of events and have the first type as MUST and define both types of events and have the first type as MUST and
the second type as MAY. Fall back approach woudl be to only the second type as MAY. Fall back approach woudl be to only
define the first type initially. define the first type initially.
o Add precise definition of what must be supported by transmitting o Add precise definition of what must be supported by transmitting
implementation and what must be implemented by receiving implementation and what must be implemented by receiving
application (regardless of what may actually be used in a given application (regardless of what may actually be used in a given
deployment). For example, it may be reasonable to mandate that a deployment). For example, it may be reasonable to mandate that a
receiving implementaton but be able to receive all the directives receiving implementaton but be able to receive all the directives
specified in the doc and all fields. specified in the doc and all fields.
6. IANA Considerations 6. IANA Considerations
TBD 6.1. CDNI Logging Directive Names Registry
The IANA is requested to create a new registry, CDNI Logging
Directive Names.
The initial contents of the CDNI Logging File Directives registry
comprise the names of the directives specified in Section 3.3 of the
present document, and are as follows:
+------------------------------+-----------+
+ Directive name + Reference |
+------------------------------+-----------+
+ Version + RFC xxxx |
+ UUID + RFC xxxx |
+ Claimed-Origin + RFC xxxx |
+ Verified-Origin + RFC xxxx |
+ Record-Type + RFC xxxx |
+ Fields + RFC xxxx |
+ Integrity-Hash + RFC xxxx |
+ Non-Repudiation-Signature + RFC xxxx |
+------------------------------+-----------+
Figure 4
[Instructions to IANA: Replace "RFC xxxx" by the RFC number of the
present document]
Additions to that registry are permitted by Standards Action, as
defined by [RFC5226].
[Editor's Note: reserve a range of names -e.g."x-" for vendor-
specific extensions]
6.2. CDNI Logging Record-Type Registry
The IANA is requested to create a new registry, CDNI Logging Record-
Types.
The initial contents of the CDNI Logging Record-Types registry
comprise the names of the CDNI Logging Record types specified in
Section 3.4 of the present document, and are as follows:
+------------------------------+-----------+
+ Directive name + Reference |
+------------------------------+-----------+
+ cdni_http_request_v1 + RFC xxxx |
+------------------------------+-----------+
Figure 5
[Instructions to IANA: Replace "RFC xxxx" by the RFC number of the
present document]
Additions to that registry are permitted by Standards Action, as
defined by [RFC5226].
[Editor's Note: reserve a range of names -e.g."x-" for vendor-
specific extensions]
6.3. CDNI Logging Field Name Registry
The IANA is requested to create a new registry, CDNI Logging Field
Names.
The initial contents of the CDNI Logging Fiels Names registry
comprise the names of the CDNI Logging fields specified in
Section 3.4 of the present document, and are as follows:
+---------------------------------------------+-----------+
+ Field name + Reference |
+---------------------------------------------+-----------+
+ date + RFC xxxx |
+ time + RFC xxxx |
+ time-taken + RFC xxxx |
+ c-ip + RFC xxxx |
+ c-ip- anonimizing + RFC xxxx |
+ c-port + RFC xxxx |
+ s-ip + RFC xxxx |
+ s-hostname + RFC xxxx |
+ s-port + RFC xxxx |
+ cs- method + RFC xxxx |
+ cs-uri + RFC xxxx |
+ u-uri + RFC xxxx |
+ protocol + RFC xxxx |
+ sc-status + RFC xxxx |
+ sc- total-bytes + RFC xxxx |
+ sc-entity-bytes + RFC xxxx |
+ cs(<HTTP-header>) + RFC xxxx |
+ sc(<HTTP-header>) + RFC xxxx |
+ s-ccid + RFC xxxx |
+ s-sid + RFC xxxx |
+ s-cached + RFC xxxx |
+ s-uri- signing + RFC xxxx |
+ x-<vendor-ID> + |
+ -<vendor-specific-cdni-logging-field-name> + RFC xxxx |
+---------------------------------------------+-----------+
Figure 6
[Instructions to IANA: Replace "RFC xxxx" by the RFC number of the
present document]
Additions to that registry are permitted by Standards Action, as
defined by [RFC5226].
[Editor's Note: tweak text for the range of names -e.g."x-" for
vendor-specific extensions]
7. Security Considerations 7. Security Considerations
7.1. Authentication, Confidentiality, Integrity Protection 7.1. Authentication, Confidentiality, Integrity Protection
The use of TLS for transport of the CDNI Logging feed mechanism The use of TLS for transport of the CDNI Logging feed mechanism
(Section 4.1) and CDNI Logging File pull mechanism (Section 4.2) (Section 4.1) and CDNI Logging File pull mechanism (Section 4.2)
allows: allows:
o the dCDN and uCDN to authenticate each other (to ensure they are o the dCDN and uCDN to authenticate each other (to ensure they are
transmitting/receiving CDNI Logging File from an authenticated transmitting/receiving CDNI Logging File from an authenticated
CDN) CDN)
o the CDNI Logging information to be transmitted with o the CDNI Logging information to be transmitted with
confidentiality confidentiality
skipping to change at page 32, line 24 skipping to change at page 36, line 7
o the integrity of the CDNI Logging information to be protected o the integrity of the CDNI Logging information to be protected
during the exchange. during the exchange.
The Integrity-Hash directive inside the CDNI Logging File provides The Integrity-Hash directive inside the CDNI Logging File provides
additional integrity protection, this time targeting potential additional integrity protection, this time targeting potential
corruption of the CDNI logging information during the CDNI Logging corruption of the CDNI logging information during the CDNI Logging
File generation. This mechanism does not allow restoration of the File generation. This mechanism does not allow restoration of the
corrupted CDNI Logging information, but it allows detection of such corrupted CDNI Logging information, but it allows detection of such
corruption and therefore triggering of appropraite correcting actions corruption and therefore triggering of appropraite correcting actions
(e.g. discard of corrupted information, attempt to re-obtain the (e.g. discard of corrupted information, attempt to re-obtain the CDNI
CDNI Logging information). Logging information).
7.2. Non Repudiation 7.2. Non Repudiation
The Non-Repudiation-Signature directive in the CDNI Logging File The Non-Repudiation-Signature directive in the CDNI Logging File
allows support of non-repudiation of the CDNI Logging File by the allows support of non-repudiation of the CDNI Logging File by the
dCDN. The optional Non-Repudiation-Hash can be used on the CDNI dCDN. The optional Non-Repudiation-Hash can be used on the CDNI
Logging interface where needed. Logging interface where needed.
7.3. Privacy 7.3. Privacy
skipping to change at page 33, line 5 skipping to change at page 36, line 36
CDNI Logging interface, the uCDN has visibility on significant CDNI Logging interface, the uCDN has visibility on significant
information such as the IP address of the End-User request and the information such as the IP address of the End-User request and the
URL of the request. Nonetheless, if the dCDN and uCDN agree that URL of the request. Nonetheless, if the dCDN and uCDN agree that
anonymization is required to avoid making some detailed information anonymization is required to avoid making some detailed information
available to the uCDN (such as how much bytes of the content has been available to the uCDN (such as how much bytes of the content has been
watched by an enduser and/or at what time) or is required to meet watched by an enduser and/or at what time) or is required to meet
some legal obligations, then the uCDN and dCDN can agree to exchange some legal obligations, then the uCDN and dCDN can agree to exchange
anonymized End-User IP addresses in CDNI Logging files and the c-ip- anonymized End-User IP addresses in CDNI Logging files and the c-ip-
anonymization field can be used to convey the number of bits that anonymization field can be used to convey the number of bits that
have been anonymized so that the meaningful information can still be have been anonymized so that the meaningful information can still be
easily extracted from the anonymized addressses (e.g. for easily extracted from the anonymized addressses (e.g. for geolocation
geolocation aware analytics). aware analytics).
8. Acknowledgments 8. Acknowledgments
This document borrows from the W3C Extended Log Format [ELF]. This document borrows from the W3C Extended Log Format [ELF].
The authors would like to thank Sebastien Cubaud, Pawel Grochocki, The authors would like to thank Sebastien Cubaud, Pawel Grochocki,
Christian Jacquenet, Yannick Le Louedec, Anne Marrec and Emile Christian Jacquenet, Yannick Le Louedec, Anne Marrec and Emile
Stephan for their contributions on early versions of this document. Stephan for their contributions on early versions of this document.
The authors would like also to thank Rob Murray, Fabio Costa, Sara The authors would like also to thank Rob Murray, Fabio Costa, Sara
skipping to change at page 33, line 46 skipping to change at page 37, line 31
[RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321,
April 1992. April 1992.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., [RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999. Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, RFC Resource Identifier (URI): Generic Syntax", STD 66, RFC
3986, January 2005. 3986, January 2005.
[RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally [RFC4122] Leach, P., Mealling, M., and R. Salz, "A Universally
Unique IDentifier (UUID) URN Namespace", RFC 4122, July Unique IDentifier (UUID) URN Namespace", RFC 4122, July
2005. 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009. [RFC5424] Gerhards, R., "The Syslog Protocol", RFC 5424, March 2009.
9.2. Informative References 9.2. Informative References
[CHAR_SET] [CHAR_SET]
, "IANA Character Sets registry", , <http://www.iana.org/ , "IANA Character Sets registry", , <http://www.iana.org/
assignments/character-sets/character-sets.xml>. assignments/character-sets/character-sets.xml>.
[ELF] Phillip M. Hallam-Baker, and Brian Behlendorf, "Extended [ELF] Phillip M. Hallam-Baker, . and . Brian Behlendorf,
Log File Format, W3C (work in progress), WD- "Extended Log File Format, W3C (work in progress), WD-
logfile-960323", , <http://www.w3.org/TR/WD-logfile.html>. logfile-960323", , <http://www.w3.org/TR/WD-logfile.html>.
[I-D.brandenburg-cdni-has] [I-D.brandenburg-cdni-has]
Brandenburg, R., Deventer, O., Faucheur, F., and K. Leung, Brandenburg, R., Deventer, O., Faucheur, F., and K. Leung,
"Models for adaptive-streaming-aware CDN Interconnection", "Models for adaptive-streaming-aware CDN Interconnection",
draft-brandenburg-cdni-has-05 (work in progress), April draft-brandenburg-cdni-has-05 (work in progress), April
2013. 2013.
[I-D.brandenburg-cdni-has]
Brandenburg, R., Deventer, O., Faucheur, F., and K. Leung,
"Models for adaptive-streaming-aware CDN Interconnection",
draft-brandenburg-cdni-has-05 (work in progress), April
2013.
[I-D.ietf-cdni-framework] [I-D.ietf-cdni-framework]
Peterson, L. and B. Davie, "Framework for CDN Peterson, L. and B. Davie, "Framework for CDN
Interconnection", draft-ietf-cdni-framework-03 (work in Interconnection", draft-ietf-cdni-framework-03 (work in
progress), February 2013. progress), February 2013.
[I-D.ietf-cdni-requirements] [I-D.ietf-cdni-requirements]
Leung, K. and Y. Lee, "Content Distribution Network Leung, K. and Y. Lee, "Content Distribution Network
Interconnection (CDNI) Requirements", draft-ietf-cdni- Interconnection (CDNI) Requirements", draft-ietf-cdni-
requirements-06 (work in progress), April 2013. requirements-07 (work in progress), May 2013.
[RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content [RFC6707] Niven-Jenkins, B., Le Faucheur, F., and N. Bitar, "Content
Distribution Network Interconnection (CDNI) Problem Distribution Network Interconnection (CDNI) Problem
Statement", RFC 6707, September 2012. Statement", RFC 6707, September 2012.
[RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma, [RFC6770] Bertrand, G., Stephan, E., Burbridge, T., Eardley, P., Ma,
K., and G. Watson, "Use Cases for Content Delivery Network K., and G. Watson, "Use Cases for Content Delivery Network
Interconnection", RFC 6770, November 2012. Interconnection", RFC 6770, November 2012.
Appendix A. Requirements Appendix A. Requirements
skipping to change at page 35, line 12 skipping to change at page 39, line 10
Section 7 of [I-D.ietf-cdni-requirements] are fulfilled by this Section 7 of [I-D.ietf-cdni-requirements] are fulfilled by this
document. document.
[Editor's node: to be written later] [Editor's node: to be written later]
A.2. Additional Requirements A.2. Additional Requirements
This section identies additional requirements that must also be met. This section identies additional requirements that must also be met.
[Editor's node: How do we incorporate this info into the I-D: in [Editor's node: How do we incorporate this info into the I-D: in
appendix? in main body? does it remain after publication or is appendix? in main body? does it remain after publication or is
temporary?] temporary?]
A.2.1. Timeliness A.2.1. Timeliness
Some applications consuming CDNI Logging information, such as Some applications consuming CDNI Logging information, such as
accounting or trend analytics, only require logging information to be accounting or trend analytics, only require logging information to be
available with a timeliness of the order of a day or the hour. This available with a timeliness of the order of a day or the hour. This
document focuses on addressing this requirement. document focuses on addressing this requirement.
Some applications consuming CDNI Logging information, such as real- Some applications consuming CDNI Logging information, such as real-
time analytics, require logging information to be available in real- time analytics, require logging information to be available in real-
time (i.e. of the order of a second after the corresponding event). time (i.e. of the order of a second after the corresponding event).
This document leaves this requirement out of scope. This document leaves this requirement out of scope.
A.2.2. Reliability A.2.2. Reliability
CDNI logging information must be transmitted reliably. The transport CDNI logging information must be transmitted reliably. The transport
protocol should contain an anti-replay mechanism. protocol should contain an anti-replay mechanism.
A.2.3. Security A.2.3. Security
CDNI logging information exchange must allow authentication, CDNI logging information exchange must allow authentication,
skipping to change at page 36, line 47 skipping to change at page 40, line 37
possibly facilitate, such a dispatching. possibly facilitate, such a dispatching.
Appendix B. Analysis of candidate protocols for Logging Transport Appendix B. Analysis of candidate protocols for Logging Transport
This section will be expanded later with an analysis of alternative This section will be expanded later with an analysis of alternative
candidate protocols for transport of CDNI Logging in non-real-time as candidate protocols for transport of CDNI Logging in non-real-time as
well as real-time. well as real-time.
B.1. Syslog B.1. Syslog
[Ed. node: to be written later] [Ed. node: to be written later]
B.2. XMPP B.2. XMPP
[Ed. node: to be written later] [Ed. node: to be written later]
B.3. SNMP B.3. SNMP
Authors' Addresses Authors' Addresses
Gilles Bertrand (editor) Gilles Bertrand (editor)
France Telecom - Orange France Telecom - Orange
38-40 rue du General Leclerc 38-40 rue du General Leclerc
Issy les Moulineaux 92130 Issy les Moulineaux 92130
FR FR
Phone: +33 1 45 29 89 46 Phone: +33 1 45 29 89 46
Email: gilles.bertrand@orange.com Email: gilles.bertrand@orange.com
Iuniana Oprescu (editor) Iuniana Oprescu (editor)
 End of changes. 122 change blocks. 
353 lines changed or deleted 579 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/