Request Routing Redirection Interface for CDN Interconnection
draft-ietf-cdni-redirection-06
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (cdni WG)
|
|
Last updated |
|
2014-12-12
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
Daryl Malas
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Daryl Malas" <d.malas@cablelabs.com>
|
Network Working Group B. Niven-Jenkins, Ed.
Internet-Draft Velocix (Alcatel-Lucent)
Intended status: Standards Track R. van Brandenburg, Ed.
Expires: June 13, 2015 TNO
December 10, 2014
Request Routing Redirection Interface for CDN Interconnection
draft-ietf-cdni-redirection-06
Abstract
The Request Routing Interface comprises of (1) the asynchronous
advertisement of footprint and capabilities by a downstream CDN that
allows an upstream CDN to decide whether to redirect particular user
requests to that downstream CDN; and (2) the synchronous operation of
an upstream CDN requesting whether a downstream CDN is prepared to
accept a user request and of a downstream CDN responding with how to
actually redirect the user request. This document describes an
interface for the latter part, i.e. the CDNI Request Routing
Redirection interface.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 13, 2015.
Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Niven-Jenkins & van BrandeExpires June 13, 2015 [Page 1]
Internet-Draft Request Routing Redirection December 2014
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Interface function and operation overview . . . . . . . . . . 4
4. HTTP based interface for the Redirection Interface . . . . . 5
4.1. Information passed in RI requests & responses . . . . . . 7
4.2. JSON encoding of RI requests & responses . . . . . . . . 8
4.3. MIME Media Types used by the RI interface . . . . . . . . 10
4.4. DNS redirection . . . . . . . . . . . . . . . . . . . . . 10
4.4.1. DNS Redirection requests . . . . . . . . . . . . . . 11
4.4.2. DNS Redirection responses . . . . . . . . . . . . . . 12
4.5. HTTP Redirection . . . . . . . . . . . . . . . . . . . . 14
4.5.1. HTTP Redirection requests . . . . . . . . . . . . . . 14
4.5.2. HTTP Redirection responses . . . . . . . . . . . . . 16
4.6. Cacheability and scope of responses . . . . . . . . . . . 18
4.7. Error responses . . . . . . . . . . . . . . . . . . . . . 20
4.8. Loop detection & prevention . . . . . . . . . . . . . . . 24
5. Security Considerations . . . . . . . . . . . . . . . . . . . 25
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 26
6.1. Media type registrations . . . . . . . . . . . . . . . . 26
6.1.1. CDNI RI requests . . . . . . . . . . . . . . . . . . 26
6.1.2. CDNI RI responses . . . . . . . . . . . . . . . . . . 27
6.2. RI Error response registry . . . . . . . . . . . . . . . 28
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 29
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
9.1. Normative References . . . . . . . . . . . . . . . . . . 29
9.2. Informative References . . . . . . . . . . . . . . . . . 30
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 30
1. Introduction
A Content Delivery Network (CDN) is a system built on an existing IP
network which is used for large scale content delivery, via
prefetching or dynamically caching content on its distributed
surrogates (caching servers). [RFC6707] describes the problem area
Show full document text