Re: [CDNi] I-D Action: draft-ietf-cdni-metadata-19.txt

Hi All,

  At the working group session, we went over the two questions from my previous email:

  1. I removed the Auth Type registry.

     There was no objection to this in the room.  If anyone has concerns, please speak up.

  2. I think we could either make links mandatory for structural metadata, or require that all structural metadata always be versioned together.

     I proposed the latter, i.e., add text that if structural metadata ever needed to change (which we hope it wouldn't), that all structural metadata objects should be updated at the same time and new ptypes allocated.  There was no objection to this in the room.  If anyone has concerns, please speak up.

  I plan to upload a final update to the metadata draft next week and hand it back over to Alexey.

thanx!

--  Kevin J. Ma

> -----Original Message-----
> From: Kevin Ma J
> Sent: Friday, July 08, 2016 4:41 PM
> To: cdni@ietf.org
> Cc: Benoit Claise; Sheng Jiang; ops-dir@ietf.org; ops-ads@tools.ietf.org;
> 'joel jaeggli'; Gunter Van De Velde; 'Alissa Cooper'; 'Stephen Farrell';
> 'Ben Campbell'; The IESG; 'Kathleen Moriarty'; 'Meral Shirazipour'; gen-
> art@ietf.org; 'Zhang Dacheng'; secdir@ietf.org; 'Mirja Kuehlewind'
> Subject: RE: [CDNi] I-D Action: draft-ietf-cdni-metadata-19.txt
> 
> Hi All,
> 
>   (As and author) I am still working through the last of the IESG
> comments, but I wanted to post an update before the draft deadline.
> 
>   This update should address all of the opsdir, secdir, and genart
> comments, as well as all of the DISCUSSes and most of the non-DISCUSS
> comments.
> 
>   Still todo are:
>   - Address the general cleanup comments from Stephen Farrell and Ben
> Campbell, including link loop prevention
>   - Close on comments from Alissa Cooper
> 
>   Two changes in the updated version for which I think we need to feedback
> from the WG:
>     1. I removed the Auth Type registry.  After thinking about it some
> more, my rationale is this: we changed all metadata objects to have a
> ptype, and the Auth object is a metadata object, so it has to have a
> ptype, and since there's already a registry for ptypes, the Auth Type
> registry is just a duplicate registry where we say that the already
> registered metadata object is an Auth object.  This seems really redundant
> since the spec will be the same in both registries.  (Note: This was not
> the case before we switched to the ptype registry.)  So, I think removing
> the Auth Type registry is simpler and cleaner, unless anyone disagrees?
>     2. I was cleaning up the "versioning" text and realized that the ptype
> of structural metadata is not necessarily explicitly listed in the json
> responses, unless they are linked.  The example in 6.10 uses links, but
> embedding would also be valid?  I think we could either make links
> mandatory for structural metadata, or require that all structural metadata
> always be versioned together, though I'm open to other thoughts on this.
> 
> thanx!
> 
> --  Kevin J. Ma
> 
> > -----Original Message-----
> > From: CDNi [mailto:cdni-bounces@ietf.org] On Behalf Of internet-
> > drafts@ietf.org
> > Sent: Friday, July 08, 2016 4:32 PM
> > To: i-d-announce@ietf.org
> > Cc: cdni@ietf.org
> > Subject: [CDNi] I-D Action: draft-ietf-cdni-metadata-19.txt
> >
> >
> > 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
> > of the IETF.
> >
> >         Title           : CDN Interconnection Metadata
> >         Authors         : Ben Niven-Jenkins
> >                           Rob Murray
> >                           Matt Caulfield
> >                           Kevin J. Ma
> > 	Filename        : draft-ietf-cdni-metadata-19.txt
> > 	Pages           : 63
> > 	Date            : 2016-07-08
> >
> > Abstract:
> >    The Content Delivery Networks Interconnection (CDNI) metadata
> >    interface enables interconnected Content Delivery Networks (CDNs) to
> >    exchange content distribution metadata in order to enable content
> >    acquisition and delivery.  The CDNI metadata associated with a piece
> >    of content provides a downstream CDN with sufficient information for
> >    the downstream CDN to service content requests on behalf of an
> >    upstream CDN.  This document describes both a base set of CDNI
> >    metadata and the protocol for exchanging that metadata.
> >
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-cdni-metadata/
> >
> > There's also a htmlized version available at:
> > https://tools.ietf.org/html/draft-ietf-cdni-metadata-19
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-cdni-metadata-19
> >
> >
> > 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