draft-ietf-cdni-logging-09.txt   draft-ietf-cdni-logging-10.txt 
Internet Engineering Task Force F. Le Faucheur, Ed. Internet Engineering Task Force F. Le Faucheur, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track G. Bertrand, Ed. Intended status: Standards Track G. Bertrand, Ed.
Expires: August 17, 2014 I. Oprescu, Ed. Expires: September 4, 2014 I. Oprescu, Ed.
Orange Orange
R. Peterkofsky R. Peterkofsky
Skytide, Inc. Skytide, Inc.
February 13, 2014 March 3, 2014
CDNI Logging Interface CDNI Logging Interface
draft-ietf-cdni-logging-09 draft-ietf-cdni-logging-10
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 August 17, 2014. This Internet-Draft will expire on September 4, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 5, line 15 skipping to change at page 5, line 15
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 CDNI provided by the dCDN to the uCDN (e.g., control of which CDNI
Logging Fields are to be communicated to the uCDN for a given task Logging 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 or control of which types of events are to
logged). The dCDN takes into account this CDNI Logging be 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 customization 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. Until such
that the CDNI Control interface or the CDNI Metadata interface a mechanism is available, the uCDN and dCDN are expected to agree
appear as candidate interfaces on which to potentially build such off-line on what exact set of CDNI Logging information is to be
a customisation mechanism in the future. Before such a mechanism provided by the dCDN to the uCDN, and to rely on management plane
is available, the uCDN and dCDN are expected to agree off-line on actions to configure the CDNI Logging functions in the dCDN to
what CDNI Logging information is to be provided by the dCDN to the generate this information set and in the uCDN to expect this
UCDN and rely on management plane actions to configure the CDNI information set.
Logging functions to generate (respectively, expect) in dCDN
(respectively, in uCDN).
o generation and collection by the dCDN of the intra-CDN Logging o generation and collection by the dCDN of the intra-CDN Logging
information related to the completion of any task performed by the information related to the completion of any task performed by the
dCDN on behalf of the uCDN (e.g., delivery of the content to an dCDN on behalf of the uCDN (e.g., delivery of the content to an
End User) or related to events happening in the dCDN that are End User) or related to events happening in the dCDN that are
relevant to the uCDN (e.g., failures or unavailability in dCDN). relevant to the uCDN (e.g., failures or unavailability in dCDN).
This takes place within the dCDN and does not directly involve This takes place within the dCDN and does not directly involve
CDNI interfaces. CDNI interfaces.
o communication by the dCDN to the uCDN of the Logging information o communication by the dCDN to the uCDN of the Logging information
skipping to change at page 6, line 14 skipping to change at page 6, line 12
the present document and left for further study. This document the present document and left for further study. This document
exclusively specifies exchange of Logging information related to exclusively specifies exchange of Logging information related to
content delivery. Exchange of Logging information related to content delivery. Exchange of Logging information related to
operational events (e.g., dCDN request routing function operational events (e.g., dCDN request routing function
unavailable, content acquisition failure by dCDN) for audit or unavailable, content acquisition failure by dCDN) for audit or
operational reactive adjustments by uCDN is outside the scope of operational reactive adjustments by uCDN is outside the scope of
the present document and left for further study. the present document and left for further study.
o customization by the dCDN of the CDNI Logging information to be o customization by the dCDN of the CDNI Logging information to be
provided by the uCDN on behalf of the dCDN. The mechanism to provided by the uCDN on behalf of the dCDN. The mechanism to
support the customisation by the dCDN of CDNI Logging information support the customization by the dCDN of CDNI Logging information
is outside the scope of this document and left for further study. is outside the scope of this document and left for further study.
o generation and collection by the uCDN of Intra-CDN Logging o generation and collection by the uCDN of Intra-CDN Logging
information related to the completion of any task performed by the information related to the completion of any task performed by the
uCDN on behalf of the dCDN (e.g., serving of content by uCDN to uCDN on behalf of the dCDN (e.g., serving of content by uCDN to
dCDN for acquisition purposes by dCDN) or related to events dCDN for acquisition purposes by dCDN) or related to events
happening in the uCDN that are relevant to the dCDN. This takes happening in the uCDN that are relevant to the dCDN. This takes
place within the uCDN and does not directly involve CDNI place within the uCDN and does not directly involve CDNI
interfaces. interfaces.
skipping to change at page 15, line 23 skipping to change at page 15, line 23
The KPIs used depend strongly on the considered log-consuming The KPIs used depend strongly on the considered log-consuming
application -- the CDN operator may be interested in different application -- the CDN operator may be interested in different
metrics than the CSP is. In particular, CDN operators are often metrics than the CSP is. In particular, CDN operators are often
interested in delivery and acquisition performance KPIs, information interested in delivery and acquisition performance KPIs, information
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 a timely manner. By contrast,
other KPIs, such as the one averaged on a long period of time, can be some other KPIs, such as those averaged on a long period of time, can
provided in non-real- time. be provided in non-real-time.
3. CDNI Logging File 3. CDNI Logging File
3.1. Rules 3.1. Rules
This specification uses the Augmented Backus-Naur Form (ABNF) This specification uses the Augmented Backus-Naur Form (ABNF)
notation and core rules of [RFC5234]. In particular, the present notation and core rules of [RFC5234]. In particular, the present
document uses the following rules from [RFC5234]: document uses the following rules from [RFC5234]:
CR = %x0D ; carriage return CR = %x0D ; carriage return
skipping to change at page 16, line 37 skipping to change at page 16, line 37
NAMEFORMAT = ALPHANUM *(ALPHANUM / "_" / "-") NAMEFORMAT = ALPHANUM *(ALPHANUM / "_" / "-")
QSTRING = DQUOTE *NDQUOTE DQUOTE ; where QSTRING = DQUOTE *NDQUOTE DQUOTE ; where
NDQUOTE = <any OCTET excluding DQUOTE> / 2DQUOTE ; whereby a NDQUOTE = <any OCTET excluding DQUOTE> / 2DQUOTE ; whereby a
DQUOTE is conveyed inside a QSTRING unambiguously by repeating DQUOTE is conveyed inside a QSTRING unambiguously by repeating
it. it.
NHTABSTRING = *NHTAB ; where NHTABSTRING = *NHTAB ; where
NHTAB = <any OCTET excluding HTAB and CRLF> NHTAB = <any OCTET excluding HTAB, CR and LF>
TIME = 2DIGIT ":" 2DIGIT ":" 2DIGIT ["." *DIGIT] TIME = 2DIGIT ":" 2DIGIT ":" 2DIGIT ["." *DIGIT]
Times are recorded in the form HH:MM:SS or HH:MM:SS.S where HH 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. is the hour in 24 hour format, MM is minutes and SS is seconds.
All times are specified in Universal Time Coordinated (UTC). All times are specified in Universal Time Coordinated (UTC).
3.2. CDNI Logging File Structure 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
skipping to change at page 28, line 30 skipping to change at page 28, line 30
<HTTP-header-name> in the CDNI Logging field name) as it <HTTP-header-name> in the CDNI Logging field name) as it
appears in the response issued by the Surrogate to serve the appears in the response issued by the Surrogate to serve the
request, but prepended by a DQUOTE and appended by a DQUOTE. request, but prepended by a DQUOTE and appended by a DQUOTE.
If the HTTP header as it appeared in the request processed by If the HTTP header as it appeared in the request processed by
the Surrogate contains one or more DQUOTE, each DQUOTE MUST be the Surrogate contains one or more DQUOTE, each DQUOTE MUST be
escaped by an additional DQUOTE. For example, if the HTTP escaped by an additional DQUOTE. For example, if the HTTP
header contains My_Header"value", then the field value of the header contains My_Header"value", then the field value of the
cs(<HTTP-header-name>) is "My_Header""value""". cs(<HTTP-header-name>) is "My_Header""value""".
* occurrence: there MAY be zero, one or any number of instances * occurrence: there MAY be zero, one or any number of instances
of this field. of this field. For a given <HTTP-header-name>, there MUST be
zero or exactly one instance of this field.
o s-ccid: o s-ccid:
* format: QSTRING * format: QSTRING
* field value: this contains the value of the Content Collection * field value: this contains the value of the Content Collection
IDentifier (CCID) associated by the uCDN to the content served IDentifier (CCID) associated by the uCDN to the content served
by the Surrogate via the CDNI Metadata interface by the Surrogate via the CDNI Metadata interface
([I-D.ietf-cdni-metadata]), prepended by a DQUOTE and appended ([I-D.ietf-cdni-metadata]), prepended by a DQUOTE and appended
by a DQUOTE. If the CCID conveyed in the CDNI Metadata by a DQUOTE. If the CCID conveyed in the CDNI Metadata
interface contains one or more DQUOTE, each DQUOTE MUST be interface contains one or more DQUOTE, each DQUOTE MUST be
escaped by an additional DQUOTE. For example, if the CCID escaped by an additional DQUOTE. For example, if the CCID
conveyed in the CDNI Metadata interface is My_CCIDD"value", conveyed in the CDNI Metadata interface is My_CCIDD"value",
then the field value of the s-ccid is "My_CCID""value""". then the field value of the s-ccid is "My_CCID""value""".
* occurrence: there MUST be zero or exactly one instance of this * occurrence: there MUST be zero or exactly one instance of this
field. field. For a given <HTTP-header-name>, there MUST be zero or
exactly one instance of this field.
o s-sid: o s-sid:
* format: QSTRING * format: QSTRING
* field value: this contains the value of a Session IDentifier * field value: this contains the value of a Session IDentifier
(SID) generated by the dCDN for a specific HTTP session, (SID) generated by the dCDN for a specific HTTP session,
prepended by a DQUOTE and appended by a DQUOTE. In particular, prepended by a DQUOTE and appended by a DQUOTE. In particular,
for HTTP Adaptive Streaming (HAS) session, the Session for HTTP Adaptive Streaming (HAS) session, the Session
IDentifier value is included in the Logging record for every IDentifier value is included in the Logging record for every
content chunk delivery of that session in view of facilitating content chunk delivery of that session in view of facilitating
the later correlation of all the per content chunk log records the later correlation of all the per content chunk log records
of a given HAS session. See section 3.4.2.2. of [RFC6983] for of a given HAS session. See section 3.4.2.2. of [RFC6983] for
more discussion on the concept of Session IDentifier in the more discussion on the concept of Session IDentifier in the
context of HAS. If the SID conveyed contains one or more context of HAS. If the SID conveyed contains one or more
skipping to change at page 36, line 20 skipping to change at page 36, line 20
an archive document). To do so, the client-side: an archive document). To do so, the client-side:
o MUST use HTTP v1.1 [RFC2616]; o MUST use HTTP v1.1 [RFC2616];
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")
as per [RFC2818] whenever protection of the CDNI Logging as per [RFC2818] whenever protection of the CDNI Logging
information is required (see Section 6.1); information is required (see Section 6.1);
o MUST use the URI that was associated to the CDNI Logging File o MUST use the URI that was associated to the CDNI Logging File
(within the "src" attribute of the corresponding atom:content (within the "src" attribute of the corresponding atom:content
element) in the CDNI Logging Feed element) in the CDNI Logging Feed;
o MUST support exchange of CDNI Logging Files with no content o MUST support exchange of CDNI Logging Files with no content
encoding applied to the representation; encoding applied to the representation;
o SHOULD support exchange of CDNI Logging Files with "gzip" content o SHOULD support exchange of CDNI Logging Files with "gzip" content
encoding (as defined in [RFC2616]) applied to the representation. encoding (as defined in [RFC2616]) applied to the representation.
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. MAY pull a CDNI Logging File that it has already pulled.
skipping to change at page 37, line 21 skipping to change at page 37, line 21
Logging File. Logging File.
The potential retention limits (e.g., sliding time window, maximum The potential retention limits (e.g., sliding time window, maximum
aggregate file storage quotas) within which the dCDN is to retain and aggregate file storage quotas) within which the dCDN is to retain and
be ready to serve a CDNI Logging File previously advertised in the be ready to serve a CDNI Logging File previously advertised in the
CDNI Logging Feed is outside the scope of the present document and is CDNI Logging Feed is outside the scope of the present document and is
expected to be agreed upon by uCDN and dCDN via other means (e.g., expected to be agreed upon by uCDN and dCDN via other means (e.g.,
human agreement). The server-side implementation MUST retain, and be human agreement). The server-side implementation MUST retain, and be
ready to serve, any CDNI Logging File within the agreed retention ready to serve, any CDNI Logging File within the agreed retention
limits. Outside these agreed limits, the server-side implementation limits. Outside these agreed limits, the server-side implementation
MAY indicate its unability to serve (e.g., with HTTP status code 404) MAY indicate its inability to serve (e.g., with HTTP status code 404)
a CDNI Logging File or MAY refuse to serve it (e.g., with HTTP status a CDNI Logging File or MAY refuse to serve it (e.g., with HTTP status
code 403 or 410). code 403 or 410).
5. IANA Considerations 5. IANA Considerations
5.1. CDNI Logging Directive Names Registry 5.1. CDNI Logging Directive Names Registry
The IANA is requested to create a new registry, CDNI Logging The IANA is requested to create a new registry, CDNI Logging
Directive Names. Directive Names.
skipping to change at page 38, line 6 skipping to change at page 38, line 6
| Fields + RFC xxxx | | Fields + RFC xxxx |
| Integrity-Hash + RFC xxxx | | Integrity-Hash + RFC xxxx |
+------------------------------+-----------+ +------------------------------+-----------+
Figure 5 Figure 5
[Instructions to IANA: Replace "RFC xxxx" above by the RFC number of [Instructions to IANA: Replace "RFC xxxx" above by the RFC number of
the present document] the present document]
Within the registry, names are to be allocated by IANA according to Within the registry, names are to be allocated by IANA according to
the "Specification Required" policy specified in [RFC5226]. the "Specification Required" policy specified in [RFC5226].
Directive names MUST be allocated by IANA with a format of NAMEFORMAT Directive names are to be allocated by IANA with a format of
(see Section 3.1). NAMEFORMAT (see Section 3.1).
Each specification that defines a new CDNI Logging directive MUST Each specification that defines a new CDNI Logging directive needs to
contain a description for the new directive with the same set of contain a description for the new directive with the same set of
information as provided in Section 3.3 (i.e., format, directive value information as provided in Section 3.3 (i.e., format, directive value
and occurrence). and occurrence).
5.2. CDNI Logging Record-Types Registry 5.2. CDNI Logging Record-Types Registry
The IANA is requested to create a new registry, CDNI Logging Record- The IANA is requested to create a new registry, CDNI Logging Record-
Types. Types.
The initial contents of the CDNI Logging Record-Types registry The initial contents of the CDNI Logging Record-Types registry
skipping to change at page 38, line 36 skipping to change at page 38, line 36
| cdni_http_request_v1 + RFC xxxx | | cdni_http_request_v1 + RFC xxxx |
+------------------------------+-----------+ +------------------------------+-----------+
Figure 6 Figure 6
[Instructions to IANA: Replace "RFC xxxx" above by the RFC number of [Instructions to IANA: Replace "RFC xxxx" above by the RFC number of
the present document] the present document]
Within the registry, Record-Types are to be allocated by IANA Within the registry, Record-Types are to be allocated by IANA
according to the "Specification Required" policy specified in according to the "Specification Required" policy specified in
[RFC5226]. Record-Types MUST be allocated by IANA with a format of [RFC5226]. Record-Types are to be allocated by IANA with a format of
NAMEFORMAT (see Section 3.1). NAMEFORMAT (see Section 3.1).
Each specification that defines a new Record-Type MUST contain a Each specification that defines a new Record-Type needs to contain a
description for the new Record-Type with the same set of information description for the new Record-Type with the same set of information
as provided in Section 3.4.1. This includes: as provided in Section 3.4.1. This includes:
o a list of all the CDNI Logging Fields that can appear in a CDNI o a list of all the CDNI Logging Fields that can appear in a CDNI
Logging Record of the new Record-Type Logging Record of the new Record-Type
o for all these Fields: a specification of the occurrence for each o for all these Fields: a specification of the occurrence for each
Field in the new Record-Type Field in the new Record-Type
o for every newly defined Field i.e., for every Field that results o for every newly defined Field, i.e., for every Field that results
in a registration in the CDNI Logging Field Names Registry in a registration in the CDNI Logging Field Names Registry
(Section 5.3): a specification of the field name, format and field (Section 5.3): a specification of the field name, format and field
value. value.
5.3. CDNI Logging Field Names Registry 5.3. CDNI Logging Field Names Registry
The IANA is requested to create a new registry, CDNI Logging Field The IANA is requested to create a new registry, CDNI Logging Field
Names. Names.
The initial contents of the CDNI Logging Fields Names registry The initial contents of the CDNI Logging Fields Names registry
skipping to change at page 39, line 49 skipping to change at page 39, line 49
| s-cached + RFC xxxx | | s-cached + RFC xxxx |
+---------------------------------------------+-----------+ +---------------------------------------------+-----------+
Figure 7 Figure 7
[Instructions to IANA: Replace "RFC xxxx" above by the RFC number of [Instructions to IANA: Replace "RFC xxxx" above by the RFC number of
the present document] the present document]
Within the registry, names are to be allocated by IANA according to Within the registry, names are to be allocated by IANA according to
the "Specification Required" policy specified in [RFC5226]. Field the "Specification Required" policy specified in [RFC5226]. Field
names MUST be allocated by IANA with a format of NHTABSTRING (see names are to be allocated by IANA with a format of NHTABSTRING (see
Section 3.1). Section 3.1).
The above registry is intended to be shared across the currently The above registry is intended to be shared across the currently
defined Record-Type (i.e., cdni_http_request_v1) as well as potential defined Record-Type (i.e., cdni_http_request_v1) as well as potential
other CDNI Logging Record-Types that may be defined in separate other CDNI Logging Record-Types that may be defined in separate
specifications. When a Field from this registry is used by another specifications. When a Field from this registry is used by another
CDNI Logging Record-Type, it MUST be used with the exact semantics CDNI Logging Record-Type, it is to be used with the exact semantics
and format specified in the document that registered this field and and format specified in the document that registered this field and
that is identified in the Reference column of the registry. If that is identified in the Reference column of the registry. If
another CDNI Logging Record-Type requires a Field with a semantics another CDNI Logging Record-Type requires a Field with semantics that
that is not strictly identical, or a format that is not strictly are not strictly identical, or a format that is not strictly
identical then this new Field MUST be registered in the registry with identical then this new Field is to be registered in the registry
a different Field name. When a Field from this registry is used by with a different Field name. When a Field from this registry is used
another CDNI Logging Record-Type, it MAY be used with different by another CDNI Logging Record-Type, it can be used with different
occurence rules. occurence rules.
5.4. CDNI Logging MIME Media Type 5.4. CDNI Logging MIME Media Type
The IANA is requested to allocate the "application/cdni.LoggingFile" The IANA is requested to allocate the "application/cdni.LoggingFile"
MIME Media Type (whose use is specified in Section 4.1.1 of the MIME Media Type (whose use is specified in Section 4.1.1 of the
present document) in the MIME Media Types registry. present document) in the MIME Media Types registry.
6. Security Considerations 6. Security Considerations
skipping to change at page 41, line 12 skipping to change at page 41, line 12
Alternate methods MAY be used for ensuring the confidentiality of the Alternate methods MAY be used for ensuring the confidentiality of the
information in the logging files such as setting up an IPsec tunnel information in the logging files such as setting up an IPsec tunnel
between the two CDNs or using a physically secured internal network between the two CDNs or using a physically secured internal network
between two CDNs that are owned by the same corporate entity. between two CDNs that are owned by the same corporate entity.
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 appropriate 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 Logging information). CDNI Logging information).
6.2. Denial of Service 6.2. Denial of Service
This document does not define specific mechanism to protect against This document does not define specific mechanism to protect against
Denial of Service (DoS) attacks on the Logging Interface. However, Denial of Service (DoS) attacks on the Logging Interface. However,
the CDNI Logging feed and CDNI Logging pull endpoints can be the CDNI Logging feed and CDNI Logging pull endpoints can be
protected against DoS attacks through the use of TLS transport and/or protected against DoS attacks through the use of TLS transport and/or
via mechanisms outside the scope of the CDNI Logging interface such via mechanisms outside the scope of the CDNI Logging interface such
skipping to change at page 43, line 34 skipping to change at page 43, line 34
[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, "Extended
Log File Format, W3C (work in progress), WD- 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.ietf-cdni-framework] [I-D.ietf-cdni-framework]
Peterson, L., Davie, B., and R. Brandenburg, "Framework Peterson, L., Davie, B., and R. Brandenburg, "Framework
for CDN Interconnection", draft-ietf-cdni-framework-09 for CDN Interconnection", draft-ietf-cdni-framework-10
(work in progress), January 2014. (work in progress), March 2014.
[I-D.ietf-cdni-metadata] [I-D.ietf-cdni-metadata]
Niven-Jenkins, B., Murray, R., Watson, G., Caulfield, M., Niven-Jenkins, B., Murray, R., Watson, G., Caulfield, M.,
Leung, K., and K. Ma, "CDN Interconnect Metadata", draft- Leung, K., and K. Ma, "CDN Interconnect Metadata", draft-
ietf-cdni-metadata-04 (work in progress), December 2013. ietf-cdni-metadata-06 (work in progress), February 2014.
[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-17 (work in progress), January 2014. requirements-17 (work in progress), January 2014.
[I-D.snell-atompub-link-extensions] [I-D.snell-atompub-link-extensions]
Snell, J., "Atom Link Extensions", draft-snell-atompub- Snell, J., "Atom Link Extensions", draft-snell-atompub-
link-extensions-09 (work in progress), June 2012. link-extensions-09 (work in progress), June 2012.
 End of changes. 25 change blocks. 
42 lines changed or deleted 43 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/