[CDNi] RFC 7975 on Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection

rfc-editor@rfc-editor.org Fri, 14 October 2016 03:53 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B3781295C8; Thu, 13 Oct 2016 20:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.598
X-Spam-Level:
X-Spam-Status: No, score=-105.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NppdSILJeT20; Thu, 13 Oct 2016 20:53:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8FB01295B0; Thu, 13 Oct 2016 20:53:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BE0CEB81B6E; Thu, 13 Oct 2016 20:53:32 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20161014035332.BE0CEB81B6E@rfc-editor.org>
Date: Thu, 13 Oct 2016 20:53:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/MufnZ2uU7iko1VNRVZHQQcDW4uk>
Cc: drafts-update-ref@iana.org, cdni@ietf.org, rfc-editor@rfc-editor.org
Subject: [CDNi] RFC 7975 on Request Routing Redirection Interface for Content Delivery Network (CDN) Interconnection
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2016 03:53:34 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7975

        Title:      Request Routing Redirection Interface for 
                    Content Delivery Network (CDN) Interconnection 
        Author:     B. Niven-Jenkins, Ed.,
                    R. van Brandenburg, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2016
        Mailbox:    ben.niven-jenkins@nokia.com, 
                    ray.vanbrandenburg@tno.nl
        Pages:      35
        Characters: 75830
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cdni-redirection-20.txt

        URL:        https://www.rfc-editor.org/info/rfc7975

        DOI:        http://dx.doi.org/10.17487/RFC7975

The Request Routing interface comprises (1) the asynchronous
advertisement of footprint and capabilities by a downstream Content
Delivery Network (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.

This document is a product of the Content Delivery Networks Interconnection Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC