Re: [CDNi] I-D Action: draft-ietf-cdni-redirection-12.txt

Phil Sorber <sorber@apache.org> Wed, 07 October 2015 22:15 UTC

Return-Path: <sorber@apache.org>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B4F81B29DD for <cdni@ietfa.amsl.com>; Wed, 7 Oct 2015 15:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.287
X-Spam-Level:
X-Spam-Status: No, score=-6.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 kk40u3XeL-Do for <cdni@ietfa.amsl.com>; Wed, 7 Oct 2015 15:15:34 -0700 (PDT)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by ietfa.amsl.com (Postfix) with SMTP id BF5391B29D8 for <cdni@ietf.org>; Wed, 7 Oct 2015 15:15:34 -0700 (PDT)
Received: (qmail 37869 invoked by uid 99); 7 Oct 2015 22:15:34 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2015 22:15:34 +0000
Received: from mail-io0-f170.google.com (mail-io0-f170.google.com [209.85.223.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id D01AB1A003F for <cdni@ietf.org>; Wed, 7 Oct 2015 22:15:33 +0000 (UTC)
Received: by ioii196 with SMTP id i196so38395681ioi.3 for <cdni@ietf.org>; Wed, 07 Oct 2015 15:15:32 -0700 (PDT)
X-Received: by 10.107.34.193 with SMTP id i184mr4783669ioi.92.1444256132788; Wed, 07 Oct 2015 15:15:32 -0700 (PDT)
MIME-Version: 1.0
References: <20151007085216.27764.67262.idtracker@ietfa.amsl.com>
In-Reply-To: <20151007085216.27764.67262.idtracker@ietfa.amsl.com>
From: Phil Sorber <sorber@apache.org>
Date: Wed, 07 Oct 2015 22:15:23 +0000
Message-ID: <CABF6JR381wpadvC9yREv0LQxWkWSJN_oqp9G9Dakn6mzCwg2Ag@mail.gmail.com>
To: "cdni@ietf.org" <cdni@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140e786c27de005218b15a1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/cdni/IgyyId89mipmomnHuZPPVRBOLC8>
Subject: Re: [CDNi] I-D Action: draft-ietf-cdni-redirection-12.txt
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 07 Oct 2015 22:15:36 -0000

There is a sentence in section 2 about HTTP redirection:

> Examples of an application level redirection are HTTP 302 Redirection and
RTMP 302 Redirection.

and then various other references to 302 redirection throughout the
document. My question is, what is the expectation for a multi-asset
exchange like segmented video where a UA is sent to a manifest and then
expected to download a series of video segments. Should the UA continually
go back to the redirector, or should it "stick" to the host it was
redirected to?

Perhaps this is out of the scope of this document?

On Wed, Oct 7, 2015 at 2:52 AM <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the Content Delivery Networks
> Interconnection Working Group of the IETF.
>
>         Title           : Request Routing Redirection Interface for CDN
> Interconnection
>         Authors         : Ben Niven-Jenkins
>                           Ray van Brandenburg
>         Filename        : draft-ietf-cdni-redirection-12.txt
>         Pages           : 30
>         Date            : 2015-10-07
>
> Abstract:
>    The Request Routing Interface comprises of (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.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-cdni-redirection/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-cdni-redirection-12
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-redirection-12
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni
>