Re: [CDNi] CDNI Metadata Interface

[Francois Le Faucheur <[e-mail]>]

Hi,

On 18 Oct 2011, at 02:44, HeXiaoyan wrote:

> Hi Francois,
> >     * the concept of "hostnames" should be made more flexible so it matches not just on hostnames but on pattern match over hostname/path. Let's call this "resource sets".
>        * "resource sets" should be dependent on "Agents". So perhaps it shoudl be folded inside your "Metadata" so it can be defined on a per "dCDN" basis.
>  
> Are you proposing remove the “hostname” object or keep it and adding “resource sets” to “Metadata”?

I was proposing that we have a single object but just make it more flexible. In some cases, it will be identifying hostnames, but it some case it may identify some more granular set of resources (eg. a hostname + part of the URI path).

> I think the “hostname” object should be kept as sometimes the customer would possibly deploy a enforcement policy associated to a hostname , e.g. for hostname associated with  a set of web pages, CP may prefer DNS routing as HTTP redirection will cause cookie issues among others. Keeping hostname level can provide cp with this flexibility.  

I agree we want to be able to do that in certain situations.

Cheers

Francois

>  
> Best Regards
> Xiaoyan(Susan) He
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Francois Le Faucheur
> Sent: Tuesday, October 18, 2011 3:43 AM
> To: Kevin J Ma
> Cc: [e-mail]
> Subject: Re: [CDNi] CDNI Metadata Interface
>  
> Hello Kevin,
>  
> [with Individual hat on]
>  
> A first set of high level questions:
>  
> * directionality of metadata creation/retrieval/removal/update mechanism:
> Could you clarify which of the above operation you see possibly happening in which direction?
> For example, regarding update/removal, do you see:
>        *a)  the POST possibly being issued towards the uCDN to update/remove some metadata in the uCDN repository?
>        *b) the POST possibly being issued by the uCDN towards the dCDN to update/remove some metadata in the dCDN repository (after some out-of-date metadata had been retrieved by dCDN from uCDN).
> For example, regarding retrieval, clearly we want the dCDN to issue a GET towards the uCDN to acquire metadata. Now do you see that the GET could possibly be also issued by the uCDN to check metadata stored by the dCDN?
>  
> * in your CDNI metadata model, a "domain" is directly associated with a set of "hostnames". So this assumes that the same set of unmodified hostnames is used unmodified everywhere in all the potential dCDNs. That can be the case in some deployment, but that may not always be the case. For example, when HTTP redirection is used across CDNs, an upstream CDN may want to modify (possibly hide) the actual content provider hostnames (and possibly part of the URI path) when redirecting to a dCDN (I believe this is mentioned in the framework). 
> Would you consider modifying your proposed CDNI model to allow for the fact that a domain may be "referenced" differently by some dCDNs than by the uCDN?
> I think it means:
>        * the concept of "hostnames" should be made more flexible so it matches not just on hostnames but on pattern match over hostname/path. Let's call this "resource sets".
>        * "resource sets" should be dependent on "Agents". So perhaps it shoudl be folded inside your "Metadata" so it can be defined on a per "dCDN" basis.
> Would that work for you?
>  
> * in section 3.3.3, you have a couple of examples showing "/CDNI/MI/domain". Should those not say "/CDNI/MI/metadata"?
>  
>  
> Cheers
>  
> Francois
>  
>       
>  
>  
> On 6 Oct 2011, at 22:21, Kevin J Ma wrote:
> 
> 
> Hi all,
> 
>  Just uploaded a new I-D with a proposed metadata model and API:
> 
>    http://www.ietf.org/internet-drafts/draft-ma-cdni-metadata-00.txt
> 
>  The model takes a rather generic approach to metadata representation
>  to support opaque metadata and addresses some of the security issues
>  associated with metadata retrieval.  Comments welcome.
> 
> thanx.
> 
> --  Kevin J. Ma
> 
> _______________________________________________
> CDNi mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/cdni
>  
>  



Francois Le Faucheur
Distinguished Engineer
Corporate Development
[e-mail]
Phone: [phone]
Mobile: [phone]



Cisco Systems France
Greenside
400 Ave de Roumanille
06410 Sophia Antipolis
France
Cisco.com


 


 Think before you print.

This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

Cisco Systems France, Société à responsabiité limitée, Rue Camille Desmoulins – Imm Atlantis Zac Forum Seine Ilot 7 92130 Issy les Moulineaux, Au capital de 91.470 €, 349 166 561 RCS Nanterre, Directeur de la publication: Jean-Luc Michel Givone.

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html