draft-ietf-cdni-metadata-11.txt   draft-ietf-cdni-metadata-12.txt 
Network Working Group B. Niven-Jenkins Network Working Group B. Niven-Jenkins
Internet-Draft R. Murray Internet-Draft R. Murray
Intended status: Standards Track Velocix (Alcatel-Lucent) Intended status: Standards Track Velocix (Alcatel-Lucent)
Expires: January 28, 2016 M. Caulfield Expires: April 21, 2016 M. Caulfield
Cisco Systems Cisco Systems
K. Ma K. Ma
Ericsson Ericsson
July 27, 2015 October 19, 2015
CDN Interconnection Metadata CDN Interconnection Metadata
draft-ietf-cdni-metadata-11 draft-ietf-cdni-metadata-12
Abstract Abstract
The Content Delivery Networks Interconnection (CDNI) metadata The Content Delivery Networks Interconnection (CDNI) metadata
interface enables interconnected Content Delivery Networks (CDNs) to interface enables interconnected Content Delivery Networks (CDNs) to
exchange content distribution metadata in order to enable content exchange content distribution metadata in order to enable content
acquisition and delivery. The CDNI metadata associated with a piece acquisition and delivery. The CDNI metadata associated with a piece
of content provides a downstream CDN with sufficient information for of content provides a downstream CDN with sufficient information for
the downstream CDN to service content requests on behalf of an the downstream CDN to service content requests on behalf of an
upstream CDN. This document describes both a base set of CDNI upstream CDN. This document describes both a base set of CDNI
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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 January 28, 2016. This Internet-Draft will expire on April 21, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 5
1.2. Supported Metadata Capabilities . . . . . . . . . . . . . 5 1.2. Supported Metadata Capabilities . . . . . . . . . . . . . 5
2. Design Principles . . . . . . . . . . . . . . . . . . . . . . 6 2. Design Principles . . . . . . . . . . . . . . . . . . . . . . 6
3. CDNI Metadata object model . . . . . . . . . . . . . . . . . 6 3. CDNI Metadata object model . . . . . . . . . . . . . . . . . 7
3.1. HostIndex, HostMatch, HostMetadata, PathMatch, 3.1. HostIndex, HostMatch, HostMetadata, PathMatch,
PatternMatch and PathMetadata objects . . . . . . . . . . 8 PatternMatch and PathMetadata objects . . . . . . . . . . 8
3.2. Generic CDNI Metadata Objects . . . . . . . . . . . . . . 10 3.2. Generic CDNI Metadata Objects . . . . . . . . . . . . . . 11
3.3. Metadata Inheritance and Override . . . . . . . . . . . . 13 3.3. Metadata Inheritance and Override . . . . . . . . . . . . 14
4. CDNI Metadata objects . . . . . . . . . . . . . . . . . . . . 14 4. CDNI Metadata objects . . . . . . . . . . . . . . . . . . . . 15
4.1. Definitions of the CDNI structural metadata objects . . . 15 4.1. Definitions of the CDNI structural metadata objects . . . 16
4.1.1. HostIndex . . . . . . . . . . . . . . . . . . . . . . 15 4.1.1. HostIndex . . . . . . . . . . . . . . . . . . . . . . 16
4.1.2. HostMatch . . . . . . . . . . . . . . . . . . . . . . 16 4.1.2. HostMatch . . . . . . . . . . . . . . . . . . . . . . 17
4.1.3. HostMetadata . . . . . . . . . . . . . . . . . . . . 17 4.1.3. HostMetadata . . . . . . . . . . . . . . . . . . . . 18
4.1.4. PathMatch . . . . . . . . . . . . . . . . . . . . . . 18 4.1.4. PathMatch . . . . . . . . . . . . . . . . . . . . . . 19
4.1.5. PatternMatch . . . . . . . . . . . . . . . . . . . . 19 4.1.5. PatternMatch . . . . . . . . . . . . . . . . . . . . 20
4.1.6. PathMetadata . . . . . . . . . . . . . . . . . . . . 20 4.1.6. PathMetadata . . . . . . . . . . . . . . . . . . . . 21
4.1.7. GenericMetadata . . . . . . . . . . . . . . . . . . . 21 4.1.7. GenericMetadata . . . . . . . . . . . . . . . . . . . 22
4.2. Definitions of the initial set of CDNI Generic Metadata 4.2. Definitions of the initial set of CDNI Generic Metadata
objects . . . . . . . . . . . . . . . . . . . . . . . . . 23 objects . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2.1. SourceMetadata . . . . . . . . . . . . . . . . . . . 23 4.2.1. SourceMetadata . . . . . . . . . . . . . . . . . . . 24
4.2.1.1. Source . . . . . . . . . . . . . . . . . . . . . 24 4.2.1.1. Source . . . . . . . . . . . . . . . . . . . . . 25
4.2.2. LocationACL Metadata . . . . . . . . . . . . . . . . 25 4.2.2. LocationACL Metadata . . . . . . . . . . . . . . . . 26
4.2.2.1. LocationRule . . . . . . . . . . . . . . . . . . 27 4.2.2.1. LocationRule . . . . . . . . . . . . . . . . . . 28
4.2.2.2. Footprint . . . . . . . . . . . . . . . . . . . . 28 4.2.2.2. Footprint . . . . . . . . . . . . . . . . . . . . 28
4.2.3. TimeWindowACL . . . . . . . . . . . . . . . . . . . . 29 4.2.3. TimeWindowACL . . . . . . . . . . . . . . . . . . . . 29
4.2.3.1. TimeWindowRule . . . . . . . . . . . . . . . . . 31 4.2.3.1. TimeWindowRule . . . . . . . . . . . . . . . . . 30
4.2.3.2. TimeWindow . . . . . . . . . . . . . . . . . . . 32 4.2.3.2. TimeWindow . . . . . . . . . . . . . . . . . . . 31
4.2.4. ProtocolACL Metadata . . . . . . . . . . . . . . . . 32 4.2.4. ProtocolACL Metadata . . . . . . . . . . . . . . . . 32
4.2.4.1. ProtocolRule . . . . . . . . . . . . . . . . . . 33 4.2.4.1. ProtocolRule . . . . . . . . . . . . . . . . . . 33
4.2.5. DeliveryAuthorization Metadata . . . . . . . . . . . 34 4.2.5. DeliveryAuthorization Metadata . . . . . . . . . . . 34
4.2.6. Cache . . . . . . . . . . . . . . . . . . . . . . . . 34 4.2.6. Cache . . . . . . . . . . . . . . . . . . . . . . . . 34
4.2.7. Auth . . . . . . . . . . . . . . . . . . . . . . . . 35 4.2.7. Auth . . . . . . . . . . . . . . . . . . . . . . . . 35
4.2.7.1. BasicAuth . . . . . . . . . . . . . . . . . . . . 36 4.2.8. Grouping . . . . . . . . . . . . . . . . . . . . . . 36
4.2.8. Grouping . . . . . . . . . . . . . . . . . . . . . . 37 4.3. CDNI Metadata Simple Data Type Descriptions . . . . . . . 37
4.3. CDNI Metadata Simple Data Type Descriptions . . . . . . . 38 4.3.1. Link . . . . . . . . . . . . . . . . . . . . . . . . 37
4.3.1. Link . . . . . . . . . . . . . . . . . . . . . . . . 38 4.3.2. Protocol . . . . . . . . . . . . . . . . . . . . . . 38
4.3.2. Protocol . . . . . . . . . . . . . . . . . . . . . . 39 4.3.3. Endpoint . . . . . . . . . . . . . . . . . . . . . . 38
4.3.3. Endpoint . . . . . . . . . . . . . . . . . . . . . . 39 4.3.4. Time . . . . . . . . . . . . . . . . . . . . . . . . 38
4.3.4. Time . . . . . . . . . . . . . . . . . . . . . . . . 40 4.3.5. IPv4CIDR . . . . . . . . . . . . . . . . . . . . . . 39
4.3.5. IPv4CIDR . . . . . . . . . . . . . . . . . . . . . . 40 4.3.6. IPv6CIDR . . . . . . . . . . . . . . . . . . . . . . 39
4.3.6. IPv6CIDR . . . . . . . . . . . . . . . . . . . . . . 40 4.3.7. ASN . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.3.7. ASN . . . . . . . . . . . . . . . . . . . . . . . . . 40 4.3.8. CountryCode . . . . . . . . . . . . . . . . . . . . . 39
4.3.8. CountryCode . . . . . . . . . . . . . . . . . . . . . 41 5. CDNI Metadata Capabilities . . . . . . . . . . . . . . . . . 40
5. CDNI Metadata Capabilities . . . . . . . . . . . . . . . . . 41 6. CDNI Metadata interface . . . . . . . . . . . . . . . . . . . 40
6. CDNI Metadata interface . . . . . . . . . . . . . . . . . . . 41 6.1. Transport . . . . . . . . . . . . . . . . . . . . . . . . 41
6.1. Transport . . . . . . . . . . . . . . . . . . . . . . . . 42 6.2. Retrieval of CDNI Metadata resources . . . . . . . . . . 42
6.2. Retrieval of CDNI Metadata resources . . . . . . . . . . 43 6.3. Bootstrapping . . . . . . . . . . . . . . . . . . . . . . 43
6.3. Bootstrapping . . . . . . . . . . . . . . . . . . . . . . 44 6.4. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4. Encoding . . . . . . . . . . . . . . . . . . . . . . . . 44 6.5. Extensibility . . . . . . . . . . . . . . . . . . . . . . 44
6.5. Extensibility . . . . . . . . . . . . . . . . . . . . . . 45 6.6. Metadata Enforcement . . . . . . . . . . . . . . . . . . 44
6.6. Metadata Enforcement . . . . . . . . . . . . . . . . . . 46 6.7. Metadata Conflicts . . . . . . . . . . . . . . . . . . . 45
6.7. Metadata Conflicts . . . . . . . . . . . . . . . . . . . 46 6.8. Versioning . . . . . . . . . . . . . . . . . . . . . . . 45
6.8. Versioning . . . . . . . . . . . . . . . . . . . . . . . 47 6.9. Media Types . . . . . . . . . . . . . . . . . . . . . . . 46
6.9. Media Types . . . . . . . . . . . . . . . . . . . . . . . 47 6.10. Complete CDNI Metadata Example . . . . . . . . . . . . . 47
6.10. Complete CDNI Metadata Example . . . . . . . . . . . . . 48 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 7.1. CDNI Payload Types . . . . . . . . . . . . . . . . . . . 50
7.1. CDNI Metadata Footprint Types Registry . . . . . . . . . 53 7.1.1. CDNI MI HostIndex Payload Type . . . . . . . . . . . 51
7.2. CDNI Metadata Protocol Types Registry . . . . . . . . . . 54 7.1.2. CDNI MI HostMatch Payload Type . . . . . . . . . . . 51
7.3. CDNI Metadata Auth Types Registry . . . . . . . . . . . . 54 7.1.3. CDNI MI HostMetadata Payload Type . . . . . . . . . . 52
8. Security Considerations . . . . . . . . . . . . . . . . . . . 54 7.1.4. CDNI MI PathMatch Payload Type . . . . . . . . . . . 52
8.1. Authentication . . . . . . . . . . . . . . . . . . . . . 55 7.1.5. CDNI MI PatternMatch Payload Type . . . . . . . . . . 52
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 55 7.1.6. CDNI MI PathMetadata Payload Type . . . . . . . . . . 52
8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 55 7.1.7. CDNI MI SourceMetadata Payload Type . . . . . . . . . 52
8.4. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 56 7.1.8. CDNI MI Source Payload Type . . . . . . . . . . . . . 53
8.5. Securing the CDNI Metadata interface . . . . . . . . . . 56 7.1.9. CDNI MI LocationACL Payload Type . . . . . . . . . . 53
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 57 7.1.10. CDNI MI LocationRule Payload Type . . . . . . . . . . 53
10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 57 7.1.11. CDNI MI Footprint Payload Type . . . . . . . . . . . 53
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 57 7.1.12. CDNI MI TimeWindowACL Payload Type . . . . . . . . . 53
11.1. Normative References . . . . . . . . . . . . . . . . . . 57 7.1.13. CDNI MI TimeWindowRule Payload Type . . . . . . . . . 54
11.2. Informative References . . . . . . . . . . . . . . . . . 58 7.1.14. CDNI MI TimeWindow Payload Type . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 59 7.1.15. CDNI MI ProtocolACL Payload Type . . . . . . . . . . 54
7.1.16. CDNI MI ProtocolRule Payload Type . . . . . . . . . . 54
7.1.17. CDNI MI DeliveryAuthorization Payload Type . . . . . 54
7.1.18. CDNI MI Cache Payload Type . . . . . . . . . . . . . 55
7.1.19. CDNI MI Auth Payload Type . . . . . . . . . . . . . . 55
7.1.20. CDNI MI Grouping Payload Type . . . . . . . . . . . . 55
7.2. CDNI Metadata Footprint Types Registry . . . . . . . . . 55
7.3. CDNI Metadata Protocol Types Registry . . . . . . . . . . 56
7.4. CDNI Metadata Auth Types Registry . . . . . . . . . . . . 56
8. Security Considerations . . . . . . . . . . . . . . . . . . . 57
8.1. Authentication . . . . . . . . . . . . . . . . . . . . . 57
8.2. Confidentiality . . . . . . . . . . . . . . . . . . . . . 57
8.3. Integrity . . . . . . . . . . . . . . . . . . . . . . . . 58
8.4. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 58
8.5. Securing the CDNI Metadata interface . . . . . . . . . . 58
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 59
10. Contributing Authors . . . . . . . . . . . . . . . . . . . . 59
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 59
11.1. Normative References . . . . . . . . . . . . . . . . . . 59
11.2. Informative References . . . . . . . . . . . . . . . . . 60
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 61
1. Introduction 1. Introduction
Content Delivery Networks Interconnection (CDNI) [RFC6707] enables a Content Delivery Networks Interconnection (CDNI) [RFC6707] enables a
downstream Content Delivery Network (dCDN) to service content downstream Content Delivery Network (dCDN) to service content
requests on behalf of an upstream CDN (uCDN). requests on behalf of an upstream CDN (uCDN).
The CDNI metadata interface is discussed in [RFC7336] along with four The CDNI metadata interface is discussed in [RFC7336] along with four
other interfaces that may be used to compose a CDNI solution (CDNI other interfaces that may be used to compose a CDNI solution (CDNI
Control interface, CDNI Request Routing Redirection interface, CDNI Control interface, CDNI Request Routing Redirection interface, CDNI
skipping to change at page 15, line 45 skipping to change at page 16, line 45
Example HostIndex object containing two HostMatch objects, where the Example HostIndex object containing two HostMatch objects, where the
first HostMatch object is embedded and the second HostMatch object is first HostMatch object is embedded and the second HostMatch object is
referenced: referenced:
{ {
"hosts": [ "hosts": [
{ {
<Properties of embedded HostMatch object> <Properties of embedded HostMatch object>
}, },
{ {
"type": "application/cdni.HostMatch.v1+json", "type": "MI.HostMatch.v1",
"href": "http://metadata.ucdn.example/hostmatch1234" "href": "http://metadata.ucdn.example/hostmatch1234"
} }
] ]
} }
4.1.2. HostMatch 4.1.2. HostMatch
The HostMatch object contains a Hostname or IP address to match The HostMatch object contains a Hostname or IP address to match
against content requests. The HostMatch object also contains a against content requests. The HostMatch object also contains a
HostMetadata object to apply if a match is found. HostMetadata object to apply if a match is found.
skipping to change at page 17, line 8 skipping to change at page 18, line 8
<Properties of embedded HostMetadata object> <Properties of embedded HostMetadata object>
} }
} }
Example HostMatch object referencing (via a Link object, see Example HostMatch object referencing (via a Link object, see
Section 4.3.1) a HostMetadata object: Section 4.3.1) a HostMetadata object:
{ {
"host": "video.example.com", "host": "video.example.com",
"host-metadata" : { "host-metadata" : {
"type": "application/cdni.HostMetadata.v1+json", "type": "MI.HostMetadata.v1",
"href": "http://metadata.ucdn.example/host1234" "href": "http://metadata.ucdn.example/host1234"
} }
} }
4.1.3. HostMetadata 4.1.3. HostMetadata
A HostMetadata object contains the CDNI metadata properties for A HostMetadata object contains the CDNI metadata properties for
content served for a particular host (defined in the HostMatch content served for a particular host (defined in the HostMatch
object) and possibly child PathMatch objects. object) and possibly child PathMatch objects.
skipping to change at page 19, line 15 skipping to change at page 20, line 15
Example PathMatch object referencing the PathMetadata object to use Example PathMatch object referencing the PathMetadata object to use
for URIs that match the case-sensitive URI path pattern "/movies/*" for URIs that match the case-sensitive URI path pattern "/movies/*"
(contained within an embedded PatternMatch object): (contained within an embedded PatternMatch object):
{ {
"path-pattern": { "path-pattern": {
"pattern": "/movies/*", "pattern": "/movies/*",
"case-sensitive": true "case-sensitive": true
}, },
"path-metadata": { "path-metadata": {
"type": "application/cdni.PathMetadata.v1+json", "type": "MI.PathMetadata.v1",
"href": "http://metadata.ucdn.example/host1234/pathDCE" "href": "http://metadata.ucdn.example/host1234/pathDCE"
} }
} }
4.1.5. PatternMatch 4.1.5. PatternMatch
A PatternMatch object contains the pattern string and flags that A PatternMatch object contains the pattern string and flags that
describe the PathMatch expression. describe the PathMatch expression.
Property: pattern Property: pattern
skipping to change at page 21, line 47 skipping to change at page 22, line 47
4.1.7. GenericMetadata 4.1.7. GenericMetadata
A GenericMetadata object is a wrapper for managing individual CDNI A GenericMetadata object is a wrapper for managing individual CDNI
metadata properties in an opaque manner. metadata properties in an opaque manner.
Property: generic-metadata-type Property: generic-metadata-type
Description: Case-insensitive CDNI metadata object type. Description: Case-insensitive CDNI metadata object type.
Type: String containing the Media Type of the object contained Type: String containing the CDNI Payload Type of the object
in the generic-metadata-value property. contained in the generic-metadata-value property.
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Property: generic-metadata-value Property: generic-metadata-value
Description: CDNI metadata object. Description: CDNI metadata object.
Type: Format/Type is defined by the value of generic-metadata- Type: Format/Type is defined by the value of generic-metadata-
type property above. type property above.
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
skipping to change at page 23, line 5 skipping to change at page 24, line 5
Type: Boolean Type: Boolean
Mandatory-to-Specify: No. Default is comprehensible (i.e., a Mandatory-to-Specify: No. Default is comprehensible (i.e., a
value of False). value of False).
Example GenericMetadata object containing a metadata object that Example GenericMetadata object containing a metadata object that
applies to the applicable URI path and/or host (within a parent applies to the applicable URI path and/or host (within a parent
PathMetadata and/or HostMetadata object): PathMetadata and/or HostMetadata object):
{ {
"mandatory-to-enforce": true, "mandatory-to-enforce": true,
"generic-metadata-type": <Media Type of this metadata object>, "safe-to-redistribute": true,
"generic-metadata-value": "incomprehensible": false,
{ "generic-metadata-type": <CDNI Payload Type of this metadata object>,
<Properties of this metadata object> "generic-metadata-value":
} {
} <Properties of this metadata object>
}
}
4.2. Definitions of the initial set of CDNI Generic Metadata objects 4.2. Definitions of the initial set of CDNI Generic Metadata objects
The objects defined below are intended to be used in the The objects defined below are intended to be used in the
GenericMetadata object generic-metadata-value field as defined in GenericMetadata object generic-metadata-value field as defined in
Section 4.1.7 and their generic-metadata-type property MUST be set to Section 4.1.7 and their generic-metadata-type property MUST be set to
the appropriate Media Type as defined in Table 4. the appropriate CDNI Payload Type as defined in Table 4.
4.2.1. SourceMetadata 4.2.1. SourceMetadata
Source metadata provides the dCDN with information about content Source metadata provides the dCDN with information about content
acquisition, i.e., how to contact an uCDN Surrogate or an Origin acquisition, i.e., how to contact an uCDN Surrogate or an Origin
Server to obtain the content to be served. The sources are not Server to obtain the content to be served. The sources are not
necessarily the actual Origin Servers operated by the CSP but might necessarily the actual Origin Servers operated by the CSP but might
be a set of Surrogates in the uCDN. be a set of Surrogates in the uCDN.
Property: sources Property: sources
skipping to change at page 24, line 6 skipping to change at page 25, line 6
Type: List of Source objects (see Section 4.2.1.1) Type: List of Source objects (see Section 4.2.1.1)
Mandatory-to-Specify: No. Default is to use static Mandatory-to-Specify: No. Default is to use static
configuration, out-of-band from the metadata interface. configuration, out-of-band from the metadata interface.
Example SourceMetadata object (which contains two Source objects) Example SourceMetadata object (which contains two Source objects)
that describes which servers the dCDN should use for acquiring that describes which servers the dCDN should use for acquiring
content for the applicable URI path and/or host: content for the applicable URI path and/or host:
{ {
"mandatory-to-enforce": true, "generic-metadata-type": "MI.SourceMetadata.v1"
"generic-metadata-type": "application/cdni.SourceMetadata.v1+json"
"generic-metadata-value": "generic-metadata-value":
{ {
"sources": [ "sources": [
{ {
"generic-metadata-type": "endpoints": [
"application/cdni.Source.v1+json" "a.service123.ucdn.example",
"generic-metadata-value": "b.service123.ucdn.example"
{ ],
"endpoints": [ "protocol": "http1.1"
"a.service123.ucdn.example",
"b.service123.ucdn.example"
],
"protocol": "http1.1"
}
}, },
{ {
"generic-metadata-type": "endpoints": ["origin.service123.example"],
"application/cdni.Source.v1+json" "protocol": "http1.1"
"generic-metadata-value":
{
"endpoints": ["origin.service123.example"],
"protocol": "http1.1"
}
} }
] ]
} }
} }
4.2.1.1. Source 4.2.1.1. Source
A Source object describes the source to be used by the dCDN for A Source object describes the source to be used by the dCDN for
content acquisition, e.g., a Surrogate within the uCDN or an content acquisition, e.g., a Surrogate within the uCDN or an
alternate Origin Server, the protocol to be used and any alternate Origin Server, the protocol to be used and any
skipping to change at page 25, line 35 skipping to change at page 26, line 25
Type: Protocol (see Section 4.3.2) Type: Protocol (see Section 4.3.2)
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Example Source object that describes a pair of endpoints (servers) Example Source object that describes a pair of endpoints (servers)
the dCDN can use for acquiring content for the applicable host and/or the dCDN can use for acquiring content for the applicable host and/or
URI path: URI path:
{ {
"generic-metadata-type": "application/cdni.Source.v1+json" "endpoints": [
"generic-metadata-value": "a.service123.ucdn.example",
{ "b.service123.ucdn.example"
"endpoints": [ ],
"a.service123.ucdn.example", "protocol": "http1.1"
"b.service123.ucdn.example"
],
"protocol": "http1.1"
}
} }
4.2.2. LocationACL Metadata 4.2.2. LocationACL Metadata
LocationACL metadata defines which locations a User Agent needs to be LocationACL metadata defines which locations a User Agent needs to be
in, in order to be able to receive the associated content. in, in order to be able to receive the associated content.
A LocationACL which does not include a locations property results in A LocationACL which does not include a locations property results in
an action of allow, meaning that delivery can be performed regardless an action of allow, meaning that delivery can be performed regardless
of the User Agent's location. The action from the first footprint to of the User Agent's location. The action from the first footprint to
skipping to change at page 26, line 33 skipping to change at page 27, line 20
(blocks) delivery based on the User Agent's location. (blocks) delivery based on the User Agent's location.
Type: List of LocationRule objects (see Section 4.2.2.1) Type: List of LocationRule objects (see Section 4.2.2.1)
Mandatory-to-Specify: No. Default is allow all locations. Mandatory-to-Specify: No. Default is allow all locations.
Example LocationACL object that allows the dCDN to deliver content to Example LocationACL object that allows the dCDN to deliver content to
any location/IP address: any location/IP address:
{ {
"mandatory-to-enforce": true, "generic-metadata-type": "MI.LocationACL.v1"
"generic-metadata-type": "application/cdni.LocationACL.v1+json"
"generic-metadata-value": "generic-metadata-value":
{ {
} }
} }
Example LocationACL object (which contains a LocationRule object Example LocationACL object (which contains a LocationRule object
which itself contains a Footprint object) that only allows the dCDN which itself contains a Footprint object) that only allows the dCDN
to deliver content to User Agents in the USA: to deliver content to User Agents in the USA:
{ {
"mandatory-to-enforce": true, "generic-metadata-type": "MI.LocationACL.v1"
"generic-metadata-type": "application/cdni.LocationACL.v1+json"
"generic-metadata-value": "generic-metadata-value":
{ {
"locations": [ "locations": [
{ {
"generic-metadata-type": "action": "allow",
"application/cdni.LocationRule.v1+json" "footprints": [
"generic-metadata-value":
{ {
"action": "allow", "footprint-type": "countrycode",
"footprints": [ "footprint-value": ["us"]
{
"generic-metadata-type":
"application/cdni.Footprint.v1+json"
"generic-metadata-value":
{
"footprint-type": "countrycode",
"footprint-value": ["us"]
}
}
]
} }
]
} }
] ]
} }
} }
4.2.2.1. LocationRule 4.2.2.1. LocationRule
A LocationRule contains or references a list of Footprint objects and A LocationRule contains or references a list of Footprint objects and
the corresponding action. the corresponding action.
skipping to change at page 28, line 4 skipping to change at page 28, line 24
Type: List of Footprint objects (see Section 4.2.2.2) Type: List of Footprint objects (see Section 4.2.2.2)
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Property: action Property: action
Description: Defines whether the rule specifies locations to Description: Defines whether the rule specifies locations to
allow or deny. allow or deny.
Type: Enumeration [allow|deny] encoded as a lowercase string Type: Enumeration [allow|deny] encoded as a lowercase string
Mandatory-to-Specify: No. Default is deny. Mandatory-to-Specify: No. Default is deny.
Example LocationRule object (which contains a Footprint object) that Example LocationRule object (which contains a Footprint object) that
allows the dCDN to deliver content to clients in the USA: allows the dCDN to deliver content to clients in the USA:
{ {
"generic-metadata-type": "action": "allow",
"application/cdni.LocationRule.v1+json" "footprints": [
"generic-metadata-value": {
{ "footprint-type": "countrycode",
"action": "allow", "footprint-value": ["us"]
"footprints": [ }
{ ]
"generic-metadata-type": }
"application/cdni.Footprint.v1+json"
"generic-metadata-value":
{
"footprint-type": "countrycode",
"footprint-value": ["us"]
}
}
]
}
} }
4.2.2.2. Footprint 4.2.2.2. Footprint
A Footprint object describes the footprint to which a LocationRule A Footprint object describes the footprint to which a LocationRule
may be applied to, e.g., an IPv4 address range or a geographic may be applied to, e.g., an IPv4 address range or a geographic
location. location.
Property: footprint-type Property: footprint-type
skipping to change at page 29, line 4 skipping to change at page 29, line 15
(Country Code, see Section 4.3.8). (Country Code, see Section 4.3.8).
Type: Lowercase String Type: Lowercase String
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Property: footprint-value Property: footprint-value
Description: List of footprint values conforming to the Description: List of footprint values conforming to the
specification associated with the registered footprint type. specification associated with the registered footprint type.
Footprint values may be simple strings (e.g., IPv4CIDR,
IPv5CIDR, ASN, and CountryCode), however, other Footprint
objects may be defined in the future, along with a more complex
encoding (e.g., GPS coordinate tuples).
Type: List of footprints Type: List of footprints
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Example Footprint object describing a footprint covering the USA: Example Footprint object describing a footprint covering the USA:
{ {
"generic-metadata-type": "footprint-type": "countrycode",
"application/cdni.Footprint.v1+json" "footprint-value": ["us"]
"generic-metadata-value":
{
"footprint-type": "countrycode",
"footprint-value": ["us"]
}
} }
Example Footprint object describing a footprint covering the IP Example Footprint object describing a footprint covering the IP
address ranges 192.0.2.0/24 and 198.51.100.0/24: address ranges 192.0.2.0/24 and 198.51.100.0/24:
{ {
"generic-metadata-type": "footprint-type": "ipv4cidr",
"application/cdni.Footprint.v1+json" "footprint-value": ["192.0.2.0/24", "198.51.100.0/24"]
"generic-metadata-value":
{
"footprint-type": "ipv4cidr",
"footprint-value": ["192.0.2.0/24", "198.51.100.0/24"]
}
} }
4.2.3. TimeWindowACL 4.2.3. TimeWindowACL
TimeWindowACL metadata defines time-based restrictions. TimeWindowACL metadata defines time-based restrictions.
A TimeWindowACL which does not include a times property results in an A TimeWindowACL which does not include a times property results in an
action of allow, meaning that delivery can be performed regardless of action of allow, meaning that delivery can be performed regardless of
the time of the User Agent's request. The action from the first the time of the User Agent's request. The action from the first
window to match against the current time is the action a CDN MUST window to match against the current time is the action a CDN MUST
skipping to change at page 30, line 22 skipping to change at page 30, line 28
Type: List of TimeWindowRule objects (see Section 4.2.3.1) Type: List of TimeWindowRule objects (see Section 4.2.3.1)
Mandatory-to-Specify: No. Default is allow all time windows. Mandatory-to-Specify: No. Default is allow all time windows.
Example TimeWIndowACL object (which contains a TimeWindowRule object Example TimeWIndowACL object (which contains a TimeWindowRule object
which itself contains a TimeWIndow object) that only allows the dCDN which itself contains a TimeWIndow object) that only allows the dCDN
to deliver content to clients between 09:00AM 01/01/2000 UTC and to deliver content to clients between 09:00AM 01/01/2000 UTC and
17:00AM 01/01/2000 UTC: 17:00AM 01/01/2000 UTC:
{ {
"mandatory-to-enforce": true, "generic-metadata-type": "MI.TimeWindowACL.v1"
"generic-metadata-type": "application/cdni.TimeWindowACL.v1+json"
"generic-metadata-value": "generic-metadata-value":
{ {
"times": [ "times": [
{ {
"generic-metadata-type": "action": "allow",
"application/cdni.TimeWindowRule.v1+json" "windows": [
"generic-metadata-value":
{ {
"action": "allow", "start": 946717200,
"windows": [ "end": 946746000
{
"generic-metadata-type":
"application/cdni.TimeWindow.v1+json"
"generic-metadata-value":
{
"start": 946717200,
"end": 946746000
}
}
]
} }
]
} }
] ]
} }
} }
4.2.3.1. TimeWindowRule 4.2.3.1. TimeWindowRule
A TimeWindowRule contains or references a list of TimeWindow objects A TimeWindowRule contains or references a list of TimeWindow objects
and the corresponding action. and the corresponding action.
skipping to change at page 31, line 32 skipping to change at page 31, line 23
Type: Enumeration [allow|deny] encoded as a lowercase string Type: Enumeration [allow|deny] encoded as a lowercase string
Mandatory-to-Specify: No. Default is deny. Mandatory-to-Specify: No. Default is deny.
Example TimeWIndowRule object (which contains a TimeWIndow object) Example TimeWIndowRule object (which contains a TimeWIndow object)
that only allows the dCDN to deliver content to clients between that only allows the dCDN to deliver content to clients between
09:00AM 01/01/2000 UTC and 17:00AM 01/01/2000 UTC: 09:00AM 01/01/2000 UTC and 17:00AM 01/01/2000 UTC:
{ {
"generic-metadata-type": "action": "allow",
"application/cdni.TimeWindowRule.v1+json" "windows": [
"generic-metadata-value":
{ {
"action": "allow", "start": 946717200,
"windows": [ "end": 946746000
{
"generic-metadata-type":
"application/cdni.TimeWindow.v1+json"
"generic-metadata-value":
{
"start": 946717200,
"end": 946746000
}
}
]
} }
]
} }
4.2.3.2. TimeWindow 4.2.3.2. TimeWindow
A TimeWindow object describes a time range which may be applied by an A TimeWindow object describes a time range which may be applied by an
TimeWindowACL, e.g., start 946717200 (i.e., 09:00AM 01/01/2000 UTC), TimeWindowACL, e.g., start 946717200 (i.e., 09:00AM 01/01/2000 UTC),
end: 946746000 (i.e., 17:00AM 01/01/2000 UTC). end: 946746000 (i.e., 17:00AM 01/01/2000 UTC).
Property: start Property: start
skipping to change at page 32, line 31 skipping to change at page 32, line 9
Description: The end time of the window. Description: The end time of the window.
Type: Time (see Section 4.3.4) Type: Time (see Section 4.3.4)
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Example TimeWIndow object that describes a time window from 09:00AM Example TimeWIndow object that describes a time window from 09:00AM
01/01/2000 UTC to 17:00AM 01/01/2000 UTC: 01/01/2000 UTC to 17:00AM 01/01/2000 UTC:
{ {
"generic-metadata-type": "start": 946717200,
"application/cdni.TimeWindow.v1+json" "end": 946746000
"generic-metadata-value":
{
"start": 946717200,
"end": 946746000
}
} }
4.2.4. ProtocolACL Metadata 4.2.4. ProtocolACL Metadata
ProtocolACL metadata defines delivery protocol restrictions. ProtocolACL metadata defines delivery protocol restrictions.
A ProtocolACL which does not include a protocol-acl property results A ProtocolACL which does not include a protocol-acl property results
in an action of allow, meaning that delivery can be performed in an action of allow, meaning that delivery can be performed
regardless of the protocol of the User Agent's request. The action regardless of the protocol of the User Agent's request. The action
from the first protocol to match against the request protocol is the from the first protocol to match against the request protocol is the
skipping to change at page 33, line 26 skipping to change at page 33, line 6
denies (blocks) delivery based on delivery protocol. denies (blocks) delivery based on delivery protocol.
Type: List of ProtocolRule objects (see Section 4.2.4.1) Type: List of ProtocolRule objects (see Section 4.2.4.1)
Mandatory-to-Specify: No. Default is allow all protocols. Mandatory-to-Specify: No. Default is allow all protocols.
Example ProtocolACL object (which contains a ProtocolRule object) Example ProtocolACL object (which contains a ProtocolRule object)
that only allows the dCDN to deliver content using HTTP/1.1: that only allows the dCDN to deliver content using HTTP/1.1:
{ {
"mandatory-to-enforce": true, "generic-metadata-type": "MI.ProtocolACL.v1"
"generic-metadata-type": "application/cdni.ProtocolACL.v1+json"
"generic-metadata-value": "generic-metadata-value":
{ {
"protocol-acl": [ "protocol-acl": [
{ {
"generic-metadata-type": "action": "allow",
"application/cdni.ProtocolRule.v1+json" "protocols": ["http1.1"]
"generic-metadata-value":
{
"action": "allow",
"protocols": ["http1.1"]
}
} }
] ]
} }
} }
4.2.4.1. ProtocolRule 4.2.4.1. ProtocolRule
A ProtocolRule contains or references a list of Protocol objects. A ProtocolRule contains or references a list of Protocol objects.
ProtocolRule objects are used to construct a ProtocolACL to apply ProtocolRule objects are used to construct a ProtocolACL to apply
restrictions to content acquisition or delivery. restrictions to content acquisition or delivery.
skipping to change at page 34, line 22 skipping to change at page 33, line 45
allow or deny. allow or deny.
Type: Enumeration [allow|deny] encoded as a lowercase string Type: Enumeration [allow|deny] encoded as a lowercase string
Mandatory-to-Specify: No. Default is deny. Mandatory-to-Specify: No. Default is deny.
Example ProtocolRule object (which contains a ProtocolRule object) Example ProtocolRule object (which contains a ProtocolRule object)
that includes the protocol HTTP/1.1: that includes the protocol HTTP/1.1:
{ {
"generic-metadata-type": "action": "allow",
"application/cdni.ProtocolRule.v1+json" "protocols": ["http1.1"]
"generic-metadata-value":
{
"action": "allow",
"protocols": ["http1.1"]
}
} }
4.2.5. DeliveryAuthorization Metadata 4.2.5. DeliveryAuthorization Metadata
Delivery Authorization defines authorization methods for the delivery Delivery Authorization defines authorization methods for the delivery
of content to User Agents. of content to User Agents.
Property: delivery-auth-methods Property: delivery-auth-methods
Description: Options for authorizing content requests. Description: Options for authorizing content requests.
Delivery for a content request is authorized if any of the Delivery for a content request is authorized if any of the
authorization methods in the list is satisfied for that authorization methods in the list is satisfied for that
request. request.
Type: List of Auth objects (see Section 4.2.7) Type: List of Auth objects (see Section 4.2.7)
Mandatory-to-Specify: No. Default is no authorization Mandatory-to-Specify: No. Default is no authorization
required. required.
Example DeliveryAuthorization object (which contains an Auth object):
{
"generic-metadata-type": "MI.DeliveryAuthorization.v1"
"generic-metadata-value":
{
"delivery-auth-methods": [
{
"auth-type": <CDNI Payload Type of this Auth object>,
"auth-value":
{
<Properties of this Auth object>
}
}
]
}
}
4.2.6. Cache 4.2.6. Cache
A Cache object describes the cache control parameters to be applied A Cache object describes the cache control parameters to be applied
to the content by intermediate caches. to the content by intermediate caches.
Property: ignore-query-string Property: ignore-query-string
Description: Allows a Surrogate to ignore URI query string Description: Allows a Surrogate to ignore URI query string
parameters when comparing the requested URI against the URIs in parameters when comparing the requested URI against the URIs in
its cache for equivalence. Matching against query parameters its cache for equivalence. Matching against query parameters
skipping to change at page 35, line 25 skipping to change at page 35, line 17
Type: List of String Type: List of String
Mandatory-to-Specify: No. Default is to consider query string Mandatory-to-Specify: No. Default is to consider query string
parameters when comparing URIs. parameters when comparing URIs.
Example Cache object that instructs the dCDN to ignore all query Example Cache object that instructs the dCDN to ignore all query
parameters: parameters:
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.Cache.v1+json" "MI.Cache.v1"
"generic-metadata-value": "generic-metadata-value":
{ {
"ignore-query-string": [] "ignore-query-string": []
} }
} }
Example Cache object that instructs the dCDN to ignore the (case- Example Cache object that instructs the dCDN to ignore the (case-
insensitive) query parameters named "sessionid" and "random": insensitive) query parameters named "sessionid" and "random":
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.Cache.v1+json" "MI.Cache.v1"
"generic-metadata-value": "generic-metadata-value":
{ {
"ignore-query-string": ["sessionid", "random"] "ignore-query-string": ["sessionid", "random"]
} }
} }
4.2.7. Auth 4.2.7. Auth
An Auth object defines authentication and authorization methods to be An Auth object defines authentication and authorization methods to be
used during content acquisition and content delivery, respectively. used during content acquisition and content delivery, respectively.
Property: auth-type Property: auth-type
Description: Registered Auth type (see Section 4.2.7.1 and Description: Registered Auth type (Section 7.4).
Section 7.3).
Type: String Type: String
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Property: auth-value Property: auth-value
Description: An object conforming to the specification Description: An object conforming to the specification
associated with the Registered Auth type. associated with the Registered Auth type.
Type: GenericMetadata Object Type: GenericMetadata Object
Mandatory-to-Specify: Yes. Mandatory-to-Specify: Yes.
Example Auth object (which contains a BasicAuth object, see Example Auth object:
Section 4.2.7.1):
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.Auth.v1+json" "MI.Auth.v1"
"generic-metadata-value": "generic-metadata-value":
{ {
"auth-type": "httpbasic", "auth-type": <CDNI Payload Type of this Auth object>,
"auth-value": "auth-value":
{ {
"generic-metadata-type": <Properties of this Auth object>
"application/cdni.BasicAuth.v1+json"
"generic-metadata-value":
{
"username": "user",
"password": "pass"
}
} }
} }
} }
4.2.7.1. BasicAuth
BasicAuth is a Registered Auth type defining an object for
encapsulating user credentials (i.e., username and password) for use
with HTTP Basic Authentication (see Section 7.3). The BasicAuth
object contains the following properties:
Property: username
Description: Identification of user.
Type: String
Mandatory-to-Specify: Yes.
Property: password
Description: Password for user identified by username property.
Type: String
Mandatory-to-Specify: Yes.
Example BasicAuth object containing the username "user" and password
"pass":
{
"generic-metadata-type":
"application/cdni.BasicAuth.v1+json"
"generic-metadata-value":
{
"username": "user",
"password": "pass"
}
}
4.2.8. Grouping 4.2.8. Grouping
A Grouping object identifies a large group of content to which a A Grouping object identifies a large group of content to which a
given asset belongs. given asset belongs.
Property: ccid Property: ccid
Description: Content Collection identifier for an application- Description: Content Collection identifier for an application-
specific purpose such as logging. specific purpose such as logging.
Type: String Type: String
Mandatory-to-Specify: No. Default is an empty string. Mandatory-to-Specify: No. Default is an empty string.
Property: sid
Description: Session identifier for an application-specific
purpose such as logging.
Type: String
Mandatory-to-Specify: No. Default is an empty string.
Example Grouping object that specifies a Content Collection Example Grouping object that specifies a Content Collection
Identifier and a Session identifier for the content associated with Identifier for the content associated with the Grouping object's
the Grouping object's parent HostMetdata or PathMetadata: parent HostMetdata or PathMetadata:
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.Grouping.v1+json" "MI.Grouping.v1"
"generic-metadata-value": "generic-metadata-value":
{ {
"ccid": "ABCD", "ccid": "ABCD",
"sid": "EFGH"
} }
} }
4.3. CDNI Metadata Simple Data Type Descriptions 4.3. CDNI Metadata Simple Data Type Descriptions
This section describes the simple data types that are used for This section describes the simple data types that are used for
properties of CDNI metadata objects. properties of CDNI metadata objects.
4.3.1. Link 4.3.1. Link
A Link object may be used in place of any of the objects or A Link object may be used in place of any of the objects or
properties described above. Link objects can be used to avoid properties described above. Link objects can be used to avoid
duplication if the same metadata information is repeated within the duplication if the same metadata information is repeated within the
metadata tree. When a Link object replaces another object, its href metadata tree. When a Link object replaces another object, its href
property is set to the URI of the resource and its type property is property is set to the URI of the resource and its type property is
set to the Media Type of the object it is replacing. set to the CDNI Payload Type of the object it is replacing.
dCDNs can detect the presence of a Link object instead of another dCDNs can detect the presence of a Link object instead of another
metadata object by detecting the presence of a property named "href" metadata object by detecting the presence of a property named "href"
within the object. This measn that GenericMetadata types MUST NOT within the object. This means that GenericMetadata types MUST NOT
contain a property named "href" because doing so would conflict with contain a property named "href" because doing so would conflict with
the ability for dCDNs to detect Link objects being used to reference the ability for dCDNs to detect Link objects being used to reference
a GenericMetadata object. a GenericMetadata object.
Property: href Property: href
Description: The URI of the addressable object being Description: The URI of the addressable object being
referenced. referenced.
Type: String Type: String
skipping to change at page 39, line 12 skipping to change at page 37, line 46
Description: The type of the object being referenced. Description: The type of the object being referenced.
Type: String Type: String
Mandatory-to-Specify: No Mandatory-to-Specify: No
Example Link object referencing a HostMetadata object: Example Link object referencing a HostMetadata object:
{ {
"type": "application/cdni.HostMetadata.v1+json", "type": "MI.HostMetadata.v1",
"href": "http://metadata.ucdn.example/host1234" "href": "http://metadata.ucdn.example/host1234"
} }
4.3.2. Protocol 4.3.2. Protocol
Protocol objects are used to specify registered protocols for content Protocol objects are used to specify registered protocols for content
acquisition or delivery (see Section 7.2). acquisition or delivery (see Section 7.3).
Type: String Type: String
Example: Example:
"http1.1" "http1.1"
4.3.3. Endpoint 4.3.3. Endpoint
A Hostname (with optional port) or an IP address (with optional A Hostname (with optional port) or an IP address (with optional
skipping to change at page 44, line 49 skipping to change at page 43, line 42
scope of this document. scope of this document.
6.4. Encoding 6.4. Encoding
CDNI metadata objects MUST be encoded as I-JSON objects [RFC7493] CDNI metadata objects MUST be encoded as I-JSON objects [RFC7493]
containing a dictionary of (key,value) pairs where the keys are the containing a dictionary of (key,value) pairs where the keys are the
property names and the values are the associated property values. property names and the values are the associated property values.
The keys of the dictionary are the names of the properties associated The keys of the dictionary are the names of the properties associated
with the object and are therefore dependent on the specific object with the object and are therefore dependent on the specific object
being encoded (i.e., dependent on the Media Type of the returned being encoded (i.e., dependent on the CDNI Payload Type of the
resource). Likewise, the values associated with each property returned resource). Likewise, the values associated with each
(dictionary key) are dependent on the specific object being encoded property (dictionary key) are dependent on the specific object being
(i.e., dependent on the Media Type of the returned resource). encoded (i.e., dependent on the CDNI Payload Type of the returned
resource).
Dictionary keys (properties) in I-JSON are case sensitive. By Dictionary keys (properties) in I-JSON are case sensitive. By
convention any dictionary key (property) defined by this document convention any dictionary key (property) defined by this document
(for example the names of CDNI metadata object properties) MUST be (for example the names of CDNI metadata object properties) MUST be
represented in lowercase. represented in lowercase.
6.5. Extensibility 6.5. Extensibility
The set of GenericMetadata objects may be extended with additional The set of GenericMetadata objects may be extended with additional
(standards based or vendor specific) metadata objects through the (standards based or vendor specific) metadata objects through the
skipping to change at page 45, line 27 skipping to change at page 44, line 20
object defined in Section 4.1.7 specifies a type field and a type- object defined in Section 4.1.7 specifies a type field and a type-
specific value field that allows any metadata to be included in specific value field that allows any metadata to be included in
either the HostMetadata or PathMetadata lists. either the HostMetadata or PathMetadata lists.
As with the initial GenericMetadata types defined in Section 4.2, As with the initial GenericMetadata types defined in Section 4.2,
future GenericMetadata types MUST specify the information necessary future GenericMetadata types MUST specify the information necessary
for constructing and decoding the GenericMetadata object. for constructing and decoding the GenericMetadata object.
Any document which defines a new GenericMetadata type SHOULD: Any document which defines a new GenericMetadata type SHOULD:
1. Specify the Media Type used to identify the new GenericMetadata 1. Specify the CDNI Payload Type used to identify the new
type being specified. GenericMetadata type being specified.
2. Define the set of properties associated with the new type 2. Define the set of properties associated with the new type
contained within the GenericMetadata object. GenericMetadata contained within the GenericMetadata object. GenericMetadata
types MUST NOT contain a property named "href" because doing so types MUST NOT contain a property named "href" because doing so
would conflict with the ability for dCDNs to detect Link objects would conflict with the ability for dCDNs to detect Link objects
being used to reference a GenericMetadata object. being used to reference a GenericMetadata object.
3. For each property, define a name, description, type, and whether 3. For each property, define a name, description, type, and whether
or not the property is mandatory-to-specify. or not the property is mandatory-to-specify.
skipping to change at page 46, line 36 skipping to change at page 45, line 23
associated with redirection requests and content requests and reject associated with redirection requests and content requests and reject
any requests where "mandatory-to-enforce" metadata associated with any requests where "mandatory-to-enforce" metadata associated with
the content cannot be enforced. the content cannot be enforced.
6.7. Metadata Conflicts 6.7. Metadata Conflicts
It is possible that new metadata definitions may obsolete or conflict It is possible that new metadata definitions may obsolete or conflict
with existing GenericMetadata (e.g., a future revision of the CDNI with existing GenericMetadata (e.g., a future revision of the CDNI
metadata interface may redefine the Auth GenericMetadata object or a metadata interface may redefine the Auth GenericMetadata object or a
custom vendor extension may implement an alternate Auth metadata custom vendor extension may implement an alternate Auth metadata
option). If multiple metadata (e.g., cdni.Auth.v2, vendor1.Auth, and option). If multiple metadata (e.g., MI.Auth.v2, vendor1.Auth, and
vendor2.Auth) all conflict with an existing GenericMetadata object vendor2.Auth) all conflict with an existing GenericMetadata object
(e.g., cdni.Auth) and all are marked as "mandatory-to-enforce", it (e.g., MI.Auth.v1) and all are marked as "mandatory-to-enforce", it
may be ambiguous which metadata should be applied, especially if the may be ambiguous which metadata should be applied, especially if the
functionality of the metadata overlap. functionality of the metadata overlap.
As described in Section 3.3, metadata override only applies to As described in Section 3.3, metadata override only applies to
metadata objects of the same exact type, found in HostMetadata and metadata objects of the same exact type, found in HostMetadata and
nested PathMetadata structures. The CDNI metadata interface does not nested PathMetadata structures. The CDNI metadata interface does not
support enforcement of dependencies between different metadata types. support enforcement of dependencies between different metadata types.
It is the responsibility of the CSP and the CDN operators to ensure It is the responsibility of the CSP and the CDN operators to ensure
that metadata assigned to a given content do not conflict. that metadata assigned to a given content do not conflict.
Note: Because metadata is inherently ordered in GenericMetadata Note: Because metadata is inherently ordered in GenericMetadata
lists, as well as in the PathMetadata hierarchy and PathMatch lists, lists, as well as in the PathMetadata hierarchy and PathMatch lists,
multiple conflicting metadata types MAY be used, however, metadata multiple conflicting metadata types MAY be used, however, metadata
hierarchies MUST ensure that independent PathMatch root objects are hierarchies MUST ensure that independent PathMatch root objects are
used to prevent ambiguous or conflicting metadata definitions. used to prevent ambiguous or conflicting metadata definitions.
6.8. Versioning 6.8. Versioning
The version of CDNI metadata objects is conveyed inside the Media The version of CDNI metadata objects is conveyed inside the CDNI
Type that is included in the HTTP Content-Type header. Upon Payload Type that is included in the HTTP Content-Type header. Upon
responding to a request for an object, a CDNI metadata server MUST responding to a request for an object, a CDNI metadata server MUST
include a Content-Type header with the Media Type containing the include a Content-Type header with the CDNI Payload Type containing
version number of the object. HTTP requests sent to a metadata the version number of the object. HTTP requests sent to a metadata
server SHOULD include an Accept header with the Media Type (which server SHOULD include an Accept header with the CDNI Payload Type
includes the version) of the expected object. Metadata clients can (which includes the version) of the expected object. Metadata
specify multiple Media Types in the Accept header, for example if a clients can specify multiple CDNI Payload Types in the Accept header,
metadata client is capable of processing two different versions of for example if a metadata client is capable of processing two
the same type of object (defined by different Media Types) it may different versions of the same type of object (defined by different
decide to include both in the Accept header. The version of each CDNI Payload Types) it may decide to include both in the Accept
object defined by this document is version 1. For example: "Content- header. The version of each object defined by this document is
Type: application/cdni.HostIndex.v1+json". version 1. For example: "Content-Type: application/cdni;
ptype=MI.HostIndex.v1".
GenericMetadata objects include a "type" property which specifies the GenericMetadata objects include a "type" property which specifies the
Media Type of the GenericMetadata value. This Media Type should also CDNI Payload Type of the GenericMetadata value. This CDNI Payload
include a version. Any document which defines a new GenericMetadata Type should also include a version. Any document which defines a new
type MUST specify the version number which it describes. For GenericMetadata type MUST specify the version number which it
example: "application/cdni.Location.v1+json". describes. For example: "MI.Location.v1".
6.9. Media Types 6.9. Media Types
All Media Types for CDNI metadata objects are prefixed with All CDNI metadata objects use the Media Type "application/cdni". The
"application/cdni.". The Media Type for each object then contains CDNI Payload Type for each object then contains the object name of
the object name of that object as defined by this document. The that object as defined by this document, prefixed with "MI.".
object type name is followed by ".v" and the version number of the Table 4 lists the CDNI Paylod Type for the metadata objects
object type (e.g., ".v1"). Finally, the encoding type "+json" is
appended. Table 4 lists the Media Type for the metadata objects
(resources) that are specified in this document. (resources) that are specified in this document.
+-----------------------+-------------------------------------------+ +-----------------------+-----------------------------+
| Data Object | MIME Media Type | | Data Object | CDNI Payload Type |
+-----------------------+-------------------------------------------+ +-----------------------+-----------------------------+
| HostIndex | application/cdni.HostIndex.v1+json | | HostIndex | MI.HostIndex.v1 |
| HostMatch | application/cdni.HostMatch.v1+json | | HostMatch | MI.HostMatch.v1 |
| HostMetadata | application/cdni.HostMetadata.v1+json | | HostMetadata | MI.HostMetadata.v1 |
| PathMatch | application/cdni.PathMatch.v1+json | | PathMatch | MI.PathMatch.v1 |
| PatternMatch | application/cdni.PatternMatch.v1+json | | PatternMatch | MI.PatternMatch.v1 |
| PathMetadata | application/cdni.PathMetadata.v1+json | | PathMetadata | MI.PathMetadata.v1 |
| GenericMetadata | application/cdni.GenericMetadata.v1+json | | GenericMetadata | MI.SourceMetadata.v1 |
| SourceMetadata | application/cdni.SourceMetadata.v1+json | | Source | MI.Source.v1 |
| Source | application/cdni.Source.v1+json | | LocationACL | MI.LocationACL.v1 |
| LocationACL | application/cdni.LocationACL.v1+json | | LocationRule | MI.LocationRule.v1 |
| LocationRule | application/cdni.LocationRule.v1+json | | Footprint | MI.Footprint.v1 |
| Footprint | application/cdni.Footprint.v1+json | | TimeWindowACL | MI.TimeWindowACL.v1 |
| TimeWindowACL | application/cdni.TimeWindowACL.v1+json | | TimeWindowRule | MI.TimeWindowRule.v1 |
| TimeWindowRule | application/cdni.TimeWindowRule.v1+json | | TimeWindow | MI.TineWindow.v1 |
| TimeWindow | application/cdni.TineWindow.v1+json | | ProtocolACL | MI.ProtocolACL.v1 |
| ProtocolACL | application/cdni.ProtocolACL.v1+json | | ProtocolRule | MI.ProtocolRule.v1 |
| ProtocolRule | application/cdni.ProtocolRule.v1+json | | DeliveryAuthorization | MI.DeliveryAuthorization.v1 |
| DeliveryAuthorization | application/ | | Cache | MI.Cache.v1 |
| | cdni.DeliveryAuthorization.v1+json | | Auth | MI.Auth.v1 |
| Cache | application/cdni.Cache.v1+json | | Grouping | MI.Grouping.v1 |
| Grouping | application/cdni.Grouping.v1+json | +-----------------------+-----------------------------+
| Auth | application/cdni.Auth.v1+json |
| BasicAuth | application/cdni.BasicAuth.v1+json |
+-----------------------+-------------------------------------------+
Table 4: MIME Media Types for CDNI Metadata objects Table 4: CDNI Payload Types for CDNI Metadata objects
6.10. Complete CDNI Metadata Example 6.10. Complete CDNI Metadata Example
A dCDN may request the HostIndex and receive the following object of A dCDN may request the HostIndex and receive the following object
type "application/cdni.HostIndex.v1+json": with a CDNI payload type of "MI.HostIndex.v1":
{ {
"hosts": [ "hosts": [
{ {
"host": "video.example.com", "host": "video.example.com",
"_links": { "host-metadata" : {
"host-metadata" : { "type": "MI.HostMetadata.v1",
"type": "application/cdni.HostMetadata.v1+json", "href": "http://metadata.ucdn.example/host1234"
"href": "http://metadata.ucdn.example/host1234"
}
} }
}, },
{ {
"host": "images.example.com", "host": "images.example.com",
"_links": { "host-metadata" : {
"host-metadata" : { "type": "MI.HostMetadata.v1",
"type": "application/cdni.HostMetadata.v1+json", "href": "http://metadata.ucdn.example/host5678"
"href": "http://metadata.ucdn.example/host5678"
}
} }
} }
] ]
} }
If the incoming request has a Host header with "video.example.com" If the incoming request has a Host header with "video.example.com"
then the dCDN would fetch the next metadata object from then the dCDN would fetch the next metadata object from
"http://metadata.ucdn.example/host1234" expecting a MIME media type "http://metadata.ucdn.example/host1234" expecting a CDNI payload type
of "application/cdni.HostMetadata.v1+json": of "MI.HostMetadata.v1":
{ {
"metadata": [ "metadata": [
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.SourceMetadata.v1+json", "MI.SourceMetadata.v1",
"generic-metadata-value": { "generic-metadata-value": {
"sources": [ "sources": [
{ {
"_links": {
"acquisition-auth": {
"auth-type": "application/cdni.Auth.v1+json",
"href": "http://metadata.ucdn.example/auth1234"
}
},
"endpoint": "acq1.ucdn.example", "endpoint": "acq1.ucdn.example",
"protocol": "http1.1" "protocol": "http1.1"
}, },
{ {
"_links": {
"acquisition-auth": {
"auth-type": "application/cdni.Auth.v1+json",
"href": "http://metadata.ucdn.example/auth1234"
}
},
"endpoint": "acq2.ucdn.example", "endpoint": "acq2.ucdn.example",
"protocol": "http1.1" "protocol": "http1.1"
} }
] ]
} }
}, },
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.LocationACL.v1+json", "MI.LocationACL.v1",
"generic-metadata-value": { "generic-metadata-value": {
"locations": [ "locations": [
{ {
"footprints": [ "footprints": [
{ {
"footprint-type": "IPv4CIDR", "footprint-type": "IPv4CIDR",
"footprint-value": "192.0.2.0/24" "footprint-value": "192.0.2.0/24"
} }
], ],
"action": "deny" "action": "deny"
} }
] ]
} }
}, },
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.ProtocolACL.v1+json", "MI.ProtocolACL.v1",
"generic-metadata-value": { "generic-metadata-value": {
"protocol-acl": [ "protocol-acl": [
{ {
"protocols": [ "protocols": [
"http1.1" "http1.1"
], ],
"action": "allow" "action": "allow"
} }
] ]
} }
} }
], ],
"paths": [ "paths": [
{ {
"path-pattern": { "path-pattern": {
"pattern": "/video/trailers/*" "pattern": "/video/trailers/*"
}, },
"_links": { "path-metadata": {
"path-metadata": { "type": "MI.PathMetadata.v1",
"type": "application/cdni.PathMetadata.v1+json", "href": "http://metadata.ucdn.example/host1234/pathABC"
"href": "http://metadata.ucdn.example/host1234/pathABC"
}
} }
}, },
{ {
"path-pattern": { "path-pattern": {
"pattern": "/video/movies/*" "pattern": "/video/movies/*"
}, },
"_links": { "path-metadata": {
"path-metadata": { "type": "MI.PathMetadata.v1",
"type": "application/cdni.PathMetadata.v1+json", "href": "http://metadata.ucdn.example/host1234/pathDCE"
"href": "http://metadata.ucdn.example/host1234/pathDCE"
}
} }
} }
] ]
} }
Suppose the path of the requested resource matches the "/video/ Suppose the path of the requested resource matches the "/video/
movies/*" pattern, the next metadata requested would be for movies/*" pattern, the next metadata requested would be for
"http://metadata.ucdn.example/host1234/movies" with an expected type "http://metadata.ucdn.example/host1234/movies" with an expected CDNI
of "application/cdni.PathMetadata.v1+json": payload type of "MI.PathMetadata.v1":
{ {
"metadata": [], "metadata": [],
"paths": [ "paths": [
{ {
"path-pattern": { "path-pattern": {
"pattern": "/videos/movies/hd/*" "pattern": "/videos/movies/hd/*"
}, },
"_links": { "path-metadata": {
"pathmetadata": { "type": "MI.PathMetadata.v1",
"type": "application/cdni.PathMetadata.v1+json", "href":
"href": "http://metadata.ucdn.example/host1234/pathABC/path123"
"http://metadata.ucdn.example/host1234/pathABC/path123"
}
} }
} }
] ]
} }
Finally, if the path of the requested resource also matches the Finally, if the path of the requested resource also matches the
"/videos/movies/hd/*" pattern, the dCDN would also fetch the "/videos/movies/hd/*" pattern, the dCDN would also fetch the
following object from "http://metadata.ucdn.example/host1234/movies/ following object from "http://metadata.ucdn.example/host1234/movies/
hd" with MIME media type "application/cdni.PathMetadata.v1+json": hd" with CDNI payload type "MI.PathMetadata.v1":
{ {
"metadata": [ "metadata": [
{ {
"generic-metadata-type": "generic-metadata-type":
"application/cdni.TimeWindowACL.v1+json", "MI.TimeWindowACL.v1",
"generic-metadata-value": { "generic-metadata-value": {
"times": [ "times": [
"windows": [ "windows": [
{ {
"start": "1213948800", "start": "1213948800",
"end": "1327393200" "end": "1327393200"
} }
], ],
"action": "allow" "action": "allow"
] ]
} }
} }
] ]
} }
7. IANA Considerations 7. IANA Considerations
This document requests the registration of the following MIME Media 7.1. CDNI Payload Types
Type under the IANA MIME Media Type registry
(http://www.iana.org/assignments/media-types/index.html).
application/cdni.HostIndex.v1+json This document requests the registration of the following CDNI Payload
Types under the IANA CDNI Payload Type registry:
application/cdni.HostMatch.v1+json +-----------------------------+---------------+
| Payload Type | Specification |
+-----------------------------+---------------+
| MI.HostIndex.v1 | RFCthis |
| MI.HostMatch.v1 | RFCthis |
| MI.HostMetadata.v1 | RFCthis |
| MI.PathMatch.v1 | RFCthis |
| MI.PatternMatch.v1 | RFCthis |
| MI.PathMetadata.v1 | RFCthis |
| MI.SourceMetadata.v1 | RFCthis |
| MI.Source.v1 | RFCthis |
| MI.LocationACL.v1 | RFCthis |
| MI.LocationRule.v1 | RFCthis |
| MI.Footprint.v1 | RFCthis |
| MI.TimeWindowACL.v1 | RFCthis |
| MI.TimeWindowRule.v1 | RFCthis |
| MI.TimeWindow.v1 | RFCthis |
| MI.ProtocolACL.v1 | RFCthis |
| MI.ProtocolRule.v1 | RFCthis |
| MI.DeliveryAuthorization.v1 | RFCthis |
| MI.Cache.v1 | RFCthis |
| MI.Auth.v1 | RFCthis |
| MI.Grouping.v1 | RFCthis |
+-----------------------------+---------------+
application/cdni.HostMetadata.v1+json [RFC Editor: Please replace RFCthis with the published RFC number for
this document.]
application/cdni.PathMatch.v1+json 7.1.1. CDNI MI HostIndex Payload Type
application/cdni.PatternMatch.v1+json Purpose: The purpose of this payload type is to distinguish HostIndex
MI objects (and any associated capabilitiy advertisement)
application/cdni.PathMetadata.v1+json Interface: MI/FCI
application/cdni.GenericMetadata.v1+json Encoding: see Section 4.1.1
application/cdni.SourceMetadata.v1+json 7.1.2. CDNI MI HostMatch Payload Type
application/cdni.Source.v1+json Purpose: The purpose of this payload type is to distinguish HostMatch
MI objects (and any associated capabilitiy advertisement)
application/cdni.LocationACL.v1+json Interface: MI/FCI
application/cdni.LocationRule.v1+json Encoding: see Section 4.1.2
application/cdni.Footprint.v1+json
application/cdni.TimeWindowACL.v1+json 7.1.3. CDNI MI HostMetadata Payload Type
application/cdni.TimeWindowRule.v1+json Purpose: The purpose of this payload type is to distinguish
HostMetadata MI objects (and any associated capabilitiy
advertisement)
application/cdni.TimeWindow.v1+json Interface: MI/FCI
application/cdni.ProtocolACL.v1+json Encoding: see Section 4.1.3
application/cdni.ProtocolRule.v1+json 7.1.4. CDNI MI PathMatch Payload Type
application/cdni.DeliveryAuthorization.v1+json Purpose: The purpose of this payload type is to distinguish PathMatch
MI objects (and any associated capabilitiy advertisement)
application/cdni.Cache.v1+json Interface: MI/FCI
application/cdni.Grouping.v1+json Encoding: see Section 4.1.4
application/cdni.Auth.v1+json 7.1.5. CDNI MI PatternMatch Payload Type
application/cdni.BasicAuth.v1+json Purpose: The purpose of this payload type is to distinguish
PatternMatch MI objects (and any associated capabilitiy
advertisement)
7.1. CDNI Metadata Footprint Types Registry Interface: MI/FCI
Encoding: see Section 4.1.5
7.1.6. CDNI MI PathMetadata Payload Type
Purpose: The purpose of this payload type is to distinguish
PathMetadata MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.1.6
7.1.7. CDNI MI SourceMetadata Payload Type
Purpose: The purpose of this payload type is to distinguish
SourceMetadata MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.1
7.1.8. CDNI MI Source Payload Type
Purpose: The purpose of this payload type is to distinguish Source MI
objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.1.1
7.1.9. CDNI MI LocationACL Payload Type
Purpose: The purpose of this payload type is to distinguish
LocationACL MI objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.2
7.1.10. CDNI MI LocationRule Payload Type
Purpose: The purpose of this payload type is to distinguish
LocationRule MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.2.1
7.1.11. CDNI MI Footprint Payload Type
Purpose: The purpose of this payload type is to distinguish Footprint
MI objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.2.2
7.1.12. CDNI MI TimeWindowACL Payload Type
Purpose: The purpose of this payload type is to distinguish
TimeWindowACL MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.3
7.1.13. CDNI MI TimeWindowRule Payload Type
Purpose: The purpose of this payload type is to distinguish
TimeWindowRule MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.3.1
7.1.14. CDNI MI TimeWindow Payload Type
Purpose: The purpose of this payload type is to distinguish
TimeWindow MI objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.3.2
7.1.15. CDNI MI ProtocolACL Payload Type
Purpose: The purpose of this payload type is to distinguish
ProtocolACL MI objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.4
7.1.16. CDNI MI ProtocolRule Payload Type
Purpose: The purpose of this payload type is to distinguish
ProtocolRule MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.4.1
7.1.17. CDNI MI DeliveryAuthorization Payload Type
Purpose: The purpose of this payload type is to distinguish
DeliveryAuthorization MI objects (and any associated capabilitiy
advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.5
7.1.18. CDNI MI Cache Payload Type
Purpose: The purpose of this payload type is to distinguish Cache MI
objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.6
7.1.19. CDNI MI Auth Payload Type
Purpose: The purpose of this payload type is to distinguish Auth MI
objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.7
7.1.20. CDNI MI Grouping Payload Type
Purpose: The purpose of this payload type is to distinguish Grouping
MI objects (and any associated capabilitiy advertisement)
Interface: MI/FCI
Encoding: see Section 4.2.8
7.2. CDNI Metadata Footprint Types Registry
The IANA is requested to create a new "CDNI Metadata Footprint Types" The IANA is requested to create a new "CDNI Metadata Footprint Types"
registry. The "CDNI Metadata Footprint Types" namespace defines the registry in the "Content Delivery Networks Interconnection (CDNI)
valid Footprint object type values used by the Footprint object in Parameters" category. The "CDNI Metadata Footprint Types" namespace
Section 4.2.2.2. Additions to the Footprint type namespace conform defines the valid Footprint object type values used by the Footprint
to the "Expert Review" policy as defined in [RFC5226]. The expert object in Section 4.2.2.2. Additions to the Footprint type namespace
reviewer should verify that new type definitions do not duplicate conform to the "Specification Required" policy as defined in
existing type definitions and prevent gratuitous additions to the [RFC5226]. The designated expert will verify that new type
namespace. definitions do not duplicate existing type definitions and prevent
gratuitous additions to the namespace.
The following table defines the initial Footprint Registry values: The following table defines the initial Footprint Registry values:
+----------------+-------------------------------+---------------+ +----------------+-------------------------------+---------------+
| Footprint Type | Description | Specification | | Footprint Type | Description | Specification |
+----------------+-------------------------------+---------------+ +----------------+-------------------------------+---------------+
| ipv4cidr | IPv4 CIDR address block | RFCthis | | ipv4cidr | IPv4 CIDR address block | RFCthis |
| ipv6cidr | IPv6 CIDR address block | RFCthis | | ipv6cidr | IPv6 CIDR address block | RFCthis |
| asn | Autonomous System (AS) Number | RFCthis | | asn | Autonomous System (AS) Number | RFCthis |
| countrycode | ISO 3166-1 alpha-2 code | RFCthis | | countrycode | ISO 3166-1 alpha-2 code | RFCthis |
+----------------+-------------------------------+---------------+ +----------------+-------------------------------+---------------+
7.2. CDNI Metadata Protocol Types Registry [RFC Editor: Please replace RFCthis with the published RFC number for
this document.]
7.3. CDNI Metadata Protocol Types Registry
The IANA is requested to create a new "CDNI Metadata Protocol Types" The IANA is requested to create a new "CDNI Metadata Protocol Types"
registry. The "CDNI Metadata Protocol Types" namespace defines the registry in the "Content Delivery Networks Interconnection (CDNI)
valid Protocol object values in Section 4.3.2, used by the Parameters" category. The "CDNI Metadata Protocol Types" namespace
SourceMetadata and ProtocolACL objects. Additions to the Protocol defines the valid Protocol object values in Section 4.3.2, used by
namespace conform to the "Expert Review" policy as defined in the SourceMetadata and ProtocolACL objects. Additions to the
[RFC5226]. The expert review should verify that new protocol Protocol namespace conform to the "Specification Required" policy as
definitions do not duplicate existing protocol definitions and defined in [RFC5226], where the specification defines the Protocol
prevent gratuitous additions to the namespace. Type and the protocol to which it is associated. The designated
expert will verify that new protocol definitions do not duplicate
existing protocol definitions and prevent gratuitous additions to the
namespace.
The following table defines the initial Protocol values: The following table defines the initial Protocol values corresponding
to the HTTP and HTTPS protocols:
+--------------+------------------------------------+---------------+ +----------+-----------------------+---------------+----------------+
| Protocol | Description | Specification | | Protocol | Description | Type | Protocol |
| Type | | | | Type | | Specification | Specification |
+--------------+------------------------------------+---------------+ +----------+-----------------------+---------------+----------------+
| http1.1 | Hypertext Transfer Protocol -- | RFC7230 | | http1.1 | Hypertext Transfer | RFCthis | RFC7230 |
| | HTTP/1.1 | | | | Protocol -- HTTP/1.1 | | |
| https1.1 | HTTP/1.1 Over TLS | RFC2818 | | https1.1 | HTTP/1.1 Over TLS | RFCthis | RFC2818 |
+--------------+------------------------------------+---------------+ +----------+-----------------------+---------------+----------------+
7.3. CDNI Metadata Auth Types Registry [RFC Editor: Please replace RFCthis with the published RFC number for
this document.]
7.4. CDNI Metadata Auth Types Registry
The IANA is requested to create a new "CDNI Metadata Auth Types" The IANA is requested to create a new "CDNI Metadata Auth Types"
registry. The "CDNI Metadata Auth Type" namespace defines the valid registry in the "Content Delivery Networks Interconnection (CDNI)
Auth object types used by the Auth object in Section 4.2.7. Parameters" category. The "CDNI Metadata Auth Type" namespace
Additions to the Auth Type namespace conform to the "Expert Review" defines the valid Auth object types used by the Auth object in
policy as defined in [RFC5226]. The expert review should verify that Section 4.2.7. Additions to the Auth Type namespace conform to the
new type definitions do not duplicate existing type definitions and "Specification Required" policy as defined in [RFC5226]. The
prevent gratuitous additions to the namespace. designated expert will verify that new type definitions do not
duplicate existing type definitions and prevent gratuitous additions
to the namespace.
The following table defines the initial Auth type values: The registry will initially be unpopulated:
+-----------+---------------------------------------+---------------+ +-----------+-------------+---------------+
| Auth Type | Description | Specification | | Auth Type | Description | Specification |
+-----------+---------------------------------------+---------------+ +-----------+-------------+---------------+
| httpbasic | Username and password authentication | RFCthis | +-----------+-------------+---------------+
| | for use with HTTP Basic | |
| | authentication. | |
+-----------+---------------------------------------+---------------+
8. Security Considerations 8. Security Considerations
8.1. Authentication 8.1. Authentication
Unauthorized access to metadata could result in denial of service. A Unauthorized access to metadata could result in denial of service. A
malicious metadata server, proxy server or an attacker performing a malicious metadata server, proxy server or an attacker performing a
"man in the middle" attack could provide malicious metadata to a dCDN "man in the middle" attack could provide malicious metadata to a dCDN
that either: that either:
o Denies service for one or more pieces of content to one or more o Denies service for one or more pieces of content to one or more
User Agents; or User Agents; or
skipping to change at page 58, line 30 skipping to change at page 60, line 44
"Recommendations for Secure Use of Transport Layer "Recommendations for Secure Use of Transport Layer
Security (TLS) and Datagram Transport Layer Security Security (TLS) and Datagram Transport Layer Security
(DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May (DTLS)", BCP 195, RFC 7525, DOI 10.17487/RFC7525, May
2015, <http://www.rfc-editor.org/info/rfc7525>. 2015, <http://www.rfc-editor.org/info/rfc7525>.
11.2. Informative References 11.2. Informative References
[I-D.ietf-cdni-redirection] [I-D.ietf-cdni-redirection]
Niven-Jenkins, B. and R. Brandenburg, "Request Routing Niven-Jenkins, B. and R. Brandenburg, "Request Routing
Redirection Interface for CDN Interconnection", draft- Redirection Interface for CDN Interconnection", draft-
ietf-cdni-redirection-11 (work in progress), July 2015. ietf-cdni-redirection-13 (work in progress), October 2015.
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, [RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818,
DOI 10.17487/RFC2818, May 2000, DOI 10.17487/RFC2818, May 2000,
<http://www.rfc-editor.org/info/rfc2818>. <http://www.rfc-editor.org/info/rfc2818>.
[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, Resource Identifier (URI): Generic Syntax", STD 66,
RFC 3986, DOI 10.17487/RFC3986, January 2005, RFC 3986, DOI 10.17487/RFC3986, January 2005,
<http://www.rfc-editor.org/info/rfc3986>. <http://www.rfc-editor.org/info/rfc3986>.
 End of changes. 118 change blocks. 
452 lines changed or deleted 522 lines changed or added

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