IETF Logo Mail Archive

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

Francois Le Faucheur <flefauch@gmail.com> Fri, 14 October 2016 12:05 UTC

Return-Path: <flefauch@gmail.com>
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 A2B3D129732 for <cdni@ietfa.amsl.com>; Fri, 14 Oct 2016 05:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 NmP4SIAmXeXT for <cdni@ietfa.amsl.com>; Fri, 14 Oct 2016 05:05:17 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 906C81297FD for <cdni@ietf.org>; Fri, 14 Oct 2016 05:04:28 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id b75so192040939lfg.3 for <cdni@ietf.org>; Fri, 14 Oct 2016 05:04:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8UsZk72wvk+eZ0pAArljf8dzdmQPiOMvkqZL8Ly5zlc=; b=RUwFZUs24m1M6Ov47s12GOThphd65HM0mYMfKR4rXSi0j+PZieDCd6JcgvW+STsg2R mKF/yrfFtjHZQmqw2Yp9rQNZgywLEco/fiIQlF+xtjkC3yhZE5SS6NS7FCuuqnHdn/6V V4lU5CcqoEspulyMItYWJc8iG3TDJCcvIT8rhAjpcCiTLYXMIXliZIIjw1ChoS5j6/DW ouLWPSA1L2GcRSgKjgVYvpCOHlFttkrlOJX7FNjvYqUOJa4YAxhUyBEpTyU8yScBwkPX Ey3yVTqlZlzNoDPGgWrvUw3dg1JVWM7WRaxlm9AFmLiLdg9ZSAtEZs7OcmmXNpwgynJ7 lIOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8UsZk72wvk+eZ0pAArljf8dzdmQPiOMvkqZL8Ly5zlc=; b=RyoCQ1fkgD8AJYhUq8Z3Jh2qNehGugDdkMpQhYmSDMmZCWWN/Cvv4egm/EczQD71qN MjzUMv2/5AZByNgy5udpeh98RNSOUwg/tpbaG8+UBjwXsUFKNZkMRgV9tgiW12CtZxSd 2/PRX/DENl2j2vxOc5jgy/r5dteO44PXvuq/eYtqXV8H5OoZfqAKjOJbW4gTWLrw/j+n ytlEPud5OTkHk7fYfv89CE+4H3zLUhw4qZhGIEvC09oRmgGTPAy7KW8YgMJKr1XPgHt3 FnuaToPIyBOUgWX/BO4T8Z/A9Csoch/SW/Ca+YHpFxPQ/cWpj5uCGaaPZTRsRbVMewQ3 DNXw==
X-Gm-Message-State: AA6/9RnGhX4loBkq9zrZcxD5gD6QQivcG51c4PEuEKUxAIl5WhUw3QDKGqyqr3o8QHLfyw==
X-Received: by 10.25.198.9 with SMTP id w9mr3414447lff.164.1476446665929; Fri, 14 Oct 2016 05:04:25 -0700 (PDT)
Received: from [192.168.1.21] (125.216.113.78.rev.sfr.net. [78.113.216.125]) by smtp.gmail.com with ESMTPSA id c77sm5058159lfg.13.2016.10.14.05.04.24 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 14 Oct 2016 05:04:24 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Francois Le Faucheur <flefauch@gmail.com>
In-Reply-To: <20161014035332.BE0CEB81B6E@rfc-editor.org>
Date: Fri, 14 Oct 2016 14:04:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CD4FD69-3F34-4CB6-9A1D-0130DA61E2A3@gmail.com>
References: <20161014035332.BE0CEB81B6E@rfc-editor.org>
To: "Niven - Jenkins, Ben (Nokia - GB)" <ben.niven-jenkins@nokia.com>, "Brandenburg, R. (Ray) van" <ray.vanbrandenburg@tno.nl>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/eLesemLgQjNvJPIblXfpKpZbiFU>
Cc: "<cdni@ietf.org>" <cdni@ietf.org>
Subject: Re: [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 12:05:23 -0000

Hi,
Congratulations to the editors and contributors of this document !
Francois

> On 14 Oct 2016, at 05:53, rfc-editor@rfc-editor.org wrote:
> 
> 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
> 
> 
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni

v2.23.0 | Report a Bug | By Email