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

Hi Phil,

> On 7 Oct 2015, at 23:15, Phil Sorber <sorber@apache.org> wrote:
> 
> 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?

It depends on the type of reference. Sections 4 & 5 of RFC3986 cover this.  

> Perhaps this is out of the scope of this document?

Yes it is IMO.

Ben

> 
> On Wed, Oct 7, 2015 at 2:52 AM <internet-drafts@ietf.org <mailto: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/ <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 <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 <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 <http://tools.ietf.org/>.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/ <ftp://ftp.ietf.org/internet-drafts/>
> 
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org <mailto:CDNi@ietf.org>
> https://www.ietf.org/mailman/listinfo/cdni <https://www.ietf.org/mailman/listinfo/cdni>
> _______________________________________________
> CDNi mailing list
> CDNi@ietf.org
> https://www.ietf.org/mailman/listinfo/cdni