Network Working Group Danhua. Wang, Ed.
Internet-Draft Huawei Technologies
Intended status: Standards Track B. Niven-Jenkins, Ed.
Expires: October 02, 2013 Velocix (Alcatel-Lucent)
Xiaoyan. He
Huawei
Chen. Ge
China Telecom
Wei. Ni
China Mobile
March 31, 2013
Request Routing Redirection Interface for CDN Interconnection
draft-he-cdni-routing-request-redirection-05
Abstract
The Request Routing Interface comprises of (1) the asynchronous
advertisement of footprint and capabilities by a downstream CDN that
allows a 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 October 02, 2013.
Copyright Notice
Wang, et al. Expires October 02, 2013 [Page 1]
Internet-Draft Routing Request Redirection March 2013
Copyright (c) 2013 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
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 RESTful interface for the Redirection Interface . 5
4.1. Information passed in RI requests & responses . . . . . . 7
4.2. JSON encoding of RI requests & responses . . . . . . . . 9
4.3. DNS redirection . . . . . . . . . . . . . . . . . . . . . 10
4.3.1. DNS Redirection requests . . . . . . . . . . . . . . 10
4.3.2. DNS Redirection responses . . . . . . . . . . . . . . 12
4.4. HTTP Redirection . . . . . . . . . . . . . . . . . . . . 13
4.4.1. HTTP Redirection requests . . . . . . . . . . . . . . 13
4.4.2. HTTP Redirection responses . . . . . . . . . . . . . 14
4.5. Indicating the cacheability and scope of responses . . . 15
4.6. Error responses . . . . . . . . . . . . . . . . . . . . . 17
4.7. Loop detection & prevention . . . . . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . . . 19
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
8. Outstanding considerations . . . . . . . . . . . . . . . . . 20
9. Contributing Authors . . . . . . . . . . . . . . . . . . . . 20
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative References . . . . . . . . . . . . . . . . . . 20
10.2. Informative References . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21
datatracker.ietf.org