Subject: Re: [CDNi] Charter adjustement: milestones related to the Request Routing Interface

From: Francois Le Faucheur <[email-masked]>
Date: Fri, 4 May 2012 13:53:19 +0200

Hello,

Just to keep everyone posted, the adjustment discussed below has now been incorporated in the charter (http://tools.ietf.org/wg/cdni/charters).

Cheers

Francois

On 18 Apr 2012, at 14:27, Francois Le Faucheur wrote:

> Folks,
> 
> As you know, what we had initially identified as one CDNI interface (the Request Routing Interface) actually comprises two different components, with different requirements, that will likely be realized by leveraging different base protocols (e.g. web-services/HTTP/DNS for one, e.g. BGP/ALTO for the other) and that will be progressed at different pace. These two components are:
> 	* "Request Routing Interface/Redirection": to support the synchronous operation of actually redirecting a user request.
> 	* "Request Routing Interface/Footprint &  Capabilities Advertisement": to support the asynchronous advertisement of footprint and capabilities by a dCDN that allows a uCDN to decide whether to redirect particular user requests to that dCDN.
> 
> The working-group chairs and ADs propose to bring the charter in alignment with that, and specifically to adjust the list of milestones of the CDN charter. 
> 
> The proposed change is:
> OLD:
> "
>  Dec 2012 - Submit specification of the CDNI Request Routing interface to IESG as Proposed Standard
> "
> NEW:
> "
>  Dec 2012 - Submit specification of the CDNI Request Routing/Redirection interface to IESG as Proposed Standard
>  Jun 2013 - Submit specification of the CDNI Request Routing/Footprint & Capabilities Advertisement interface to IESG as Proposed Standard
> "
> 
> Please let us know if you have any objections, concerns or comments on this proposed charter adjustment.
> 
> Thank you
> 
> Francois & Rich
> 
> ==============================================================================
> 
> A little more optional background, just in case:
> 
> Here is some text straight from the CDNI framework document about the two components of the Request Routing Interface:
> "
> We may think of the request routing interface as comprising two parts:
> 1.the asynchronous advertisement of footprint and capabilities by a dCDN that allows a uCDN to decide whether to redirect particular user requests to that dCDN; and
> 2. the synchronous operation of actually redirecting a user request.
>   (These are somewhat analogous to the operations of routing and forwarding in IP.)     ”
> "
> 
> Here is the definition of the Request Routing Interface as per current charter. I believe that definition still stands as is and need not be modified since it is broad enough to encompass the two components:
> "
> 	* A specification of the "CDNI request-routing interface". This
>    interface will allow an upstream CDN request routing system to obtain
>    from the downstream CDN the information necessary to perform request
>    redirection.
> "
> 
> 
> _______________________________________________
> CDNi mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/cdni