Re: [CDNi] draft-ma-cdni-metadata-01.txt: mD objects extensibility

[<[e-mail]>]

Hi Kevin,


See below.

> -----Message d'origine-----
> De : Kevin J Ma [mailto:[e-mail]]
> Envoyé : mercredi 2 novembre 2011 23:31
> À : STEPHAN Emile RD-CORE-LAN; [e-mail]
> Cc : [e-mail]; [e-mail]; [e-mail]
> Objet : RE: [CDNi] draft-ma-cdni-metadata-01.txt: mD objects
> extensibility
> 
> Hi Emile,
> 
>   By extensible, I mean that uCDNs should be able to define their own
>   private metadata (if they want) to describe delivery functions that
>   they support and if a dCDN understands it then that's great, but if
>   not then the uCDN should be able to specify whether or not the dCDN
>   must decline to serve the content.
> 
>   In general, I favor a protocol which has opaque data encapsulation,
>   using a layered approach, but, there are certainly other ways to do
>   it, and the WG may choose to go a different route.  I don't know if
>   an 'extension' field is the best approach, but I hope that the CDNI
>   MI specification will ultimately support vendor defined metadata.

IMO, we don't need to lost time and energy on this point.
To go further we need to add the support of proprietary defined metadata in the req and framework documents.

Regards
Emile

> 
> thanx.
> 
> --  Kevin J. Ma
> 
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]]
> > Sent: Wednesday, November 02, 2011 10:20 AM
> > To: Kevin J Ma; [e-mail]
> > Cc: [e-mail]; [e-mail]; [e-mail]
> > Subject: [CDNi] draft-ma-cdni-metadata-01.txt: mD objects
> extensibility
> >
> > Hi Kevin,
> >
> > Following are my thoughts on v01.
> >
> > IMO, It is obvious that the framework of CDNi will include objects
> > extensibility and consequently support opaque metadata. The draft
> should
> > focus on the identification of the information elements required to
> > support the awareness and the restriction of the 7 interfaces listed
> in
> > the introduction rather than promoting the need of opaque metadata.
> >
> > So I propose that we add something like following in draft-davie-
> cdni-
> > framework:
> >
> > "5 Data modeling Framework
> > 5.1  Objects extensibility
> >
> >    CDNs interoperate to distribute content services that may require
> the
> > exchange of
> >    specific metadata.  Consequently each object is extensible and
> >    includes a field 'extension' for this purpose. This applies to all
> CDNi
> > interfaces.
> > "
> >
> > Regards
> > Emile
> >
> > > -----Message d'origine-----
> > > De : [e-mail] [mailto:[e-mail]] De la
> part de
> > > Kevin J Ma
> > > Envoyé : mardi 1 novembre 2011 00:37
> > > À : [e-mail]
> > > Objet : [CDNi] FW: New Version Notification fordraft-ma-cdni-
> metadata-
> > > 01.txt
> > >
> > > An updated version of draft-ma-cdni-metadata has been uploaded.
> > > It fixes some typos, incorporates some of the comments received
> > > from the list, and adds some core metadata definitions.
> > >
> > > comments welcome.
> > >
> > > thanx.
> > >
> > > --  Kevin J. Ma
> > >
> > >
> > > A new version of I-D, draft-ma-cdni-metadata-01.txt has been
> > > successfully submitted by Kevin Ma and posted to the IETF
> repository.
> > >
> > > Filename:	 draft-ma-cdni-metadata
> > > Revision:	 01
> > > Title:		 Content Distribution Network Interconnection (CDNI)
> > > Metadata Interface
> > > Creation date:	 2011-10-31
> > > WG ID:		 Individual Submission
> > > Number of pages: 33
> > >
> > >
> > > _______________________________________________
> > > CDNi mailing list
> > > [e-mail]
> > > https://www.ietf.org/mailman/listinfo/cdni