Re: [CDNi] [E] Re: Fwd: New Version Notification for draft-finkelman-cdni-sva-extensions-00.txt

[[e-mail]]

Kevin Ma wrote:
>For Logging, it would be unfortunate if the logging interface we specified had to be >completely bypassed.  If there is a need, then we should address it, but I would be interested in >hearing from vendors on this.
Primary motivators for specifying logging requirements in draft-finkelman-cdni-sva-extensions is largely because of CDNs already have and use Squid based logging and would rather not add a separate process to receive and process logging information sent by the dCDN (ISP’s open caching nodes). The other motivation was to add a negotiation capabilities between a dCDN and a uCDN on how to “transport” those logs across the two domains. The logging spec in “draft-finkleman…” allows this and again may leverage transport types (logstash, SFTP, Kafka etc).

Thanks
Sanjay

From: CDNi [mailto:[e-mail]] On Behalf Of Kevin Ma
Sent: Thursday, November 16, 2017 8:27 PM
To: Ori Finkelman <[e-mail]>
Cc: [e-mail]
Subject: [E] Re: [CDNi] Fwd: New Version Notification for draft-finkelman-cdni-sva-extensions-00.txt

Hi Ori,

  (As an individual) For request router address, I think you may want to consider a prioritized list of endpoints.  My initial thought is that this is something better suited for a Control/Bootstrap interface, but if the request router addresses change over time, then perhaps FCI is the right place for it.  Either way, I agree some discovery mechanism would be useful.

  For Fallback address, I don't see any issue with adding a new metadata object for this purpose.

  For Triggers regex, I think this falls into the same category as the URI Signing glob question Phil posed.  We have the simple pattern matching because we originally thought regex would be too heavy, but if folks like regex, conceptually I don't see a reason why we couldn't add it (or replace the pattern match with regex).

  For Triggers playlist, a long time ago we decided to not deal with HTTP adaptive streaming to simplify the initial scope, but I think video and HAS awareness is probably necessary and worthwhile for us to re-address.  I think I like content.playlists better than playlist.urls, but that's a detail.

  For Triggers geo-limit and scheduling, I think the concepts are useful.  The implementation probably needs to be hashed out more, per the discussions in the working group meeting.  I think it would be good to use these as a first implementation of trigger extensibility.  In general, I like the idea of having something like generic-metadata for triggers.  We didn't have a use case for it originally, but I think you have provided valid use cases therefor.

  For Relayed token auth, this one I have concerns about.  I'm not sure how the security folks will feel about this, but I think if you and Phil could iterate on this, perhaps there's a reasonable solution to be found.

  For Logging, it would be unfortunate if the logging interface we specified had to be completely bypassed.  If there is a need, then we should address it, but I would be interested in hearing from vendors on this.

  For CORS, I think this is an interesting topic and unfortunately we did not have time to talk about it in the WG session.  I will be interested to hear thoughts from the rest of the WG on the proposals.  It doesn't really have to be in CDNI, but it might be useful to have.

thanx.

--  Kevin J. Ma


On Thu, Nov 16, 2017 at 6:57 AM, Kevin Ma <[e-mail]<mailto:[e-mail]>> wrote:
Hi All,

  As we discussed in the CDNI Session today, the chairs have begun looking at WG rechartering and would like to gauge general WG interest in the Streaming Video Alliance Open Caching proposals presented by Ori and Sanjay.

  We encourage you to read the draft and send mail to the list if you have comments, questions, concerns, or just a thumbs up/down on any of the topics discussed.

thanx!

--  Kevin and Francois


On Mon, Oct 30, 2017 at 4:42 PM, Ori Finkelman <[e-mail]<mailto:[e-mail]>> wrote:
Dear CDNI working group,
I have just submitted a draft for extension proposals for CDNI,
These extensions are derived from the work done within the Open Caching working group of the Video Streaming Alliance (SVA).
Open Caching is a specific case of CDNI and therefore we are looking to standardized these extensions and proposed new functionalities under the CDNI wg.

Looking forward to get feedback from the cdni group.

Best regards,
Ori



A new version of I-D, draft-finkelman-cdni-sva-extensions-00.txt
has been successfully submitted by Ori Finkelman and posted to the
IETF repository.

Name:           draft-finkelman-cdni-sva-extensions
Revision:       00
Title:          CDNI SVA Extensions
Document date:  2017-10-30
Group:          Individual Submission
Pages:          25
URL:            https://www.ietf.org/internet-drafts/draft-finkelman-cdni-sva-extensions-00.txt<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_internet-2Ddrafts_draft-2Dfinkelman-2Dcdni-2Dsva-2Dextensions-2D00.txt&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=PMnY8KpuUopuFhL6K52t4itbaoUkReKaZaVaU8J_HZM&s=G57__ggdP8hJ3uZ3F0PGazlgq9ZfaQ4rT-jvMxEe9B8&e=>
Status:         https://datatracker.ietf.org/doc/draft-finkelman-cdni-sva-extensions/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dfinkelman-2Dcdni-2Dsva-2Dextensions_&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=PMnY8KpuUopuFhL6K52t4itbaoUkReKaZaVaU8J_HZM&s=z6r5V-t04fZvyCaT0Ou58tauQbLewrDJkt5arT18F9w&e=>
Htmlized:       https://tools.ietf.org/html/draft-finkelman-cdni-sva-extensions-00<https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_html_draft-2Dfinkelman-2Dcdni-2Dsva-2Dextensions-2D00&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=PMnY8KpuUopuFhL6K52t4itbaoUkReKaZaVaU8J_HZM&s=3PN14xFCX28RVLaeylVgnu5XLf5NrCl0T8mzo5TXX7o&e=>
Htmlized:       https://datatracker.ietf.org/doc/html/draft-finkelman-cdni-sva-extensions-00<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dfinkelman-2Dcdni-2Dsva-2Dextensions-2D00&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=PMnY8KpuUopuFhL6K52t4itbaoUkReKaZaVaU8J_HZM&s=sHMfBp_rcLT3h0eQVAwceqM7RJUo1jt7MQ6ACv3G4tY&e=>


Abstract:
   The Open Caching working group of the Streaming Video Alliance is
   focused on the delegation of video delivery request from commercial
   CDNs to a caching layer at the ISP.  In that aspect, Open Caching is
   a specific use case of CDNI, where the commercial CDN is the upstream
   CDN (uCDN) and the ISP caching layer is the downstream CDN (dCDN).





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<https://urldefense.proofpoint.com/v2/url?u=http-3A__tools.ietf.org&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=PMnY8KpuUopuFhL6K52t4itbaoUkReKaZaVaU8J_HZM&s=H_4GnM-WRyvcG6tLMcbS4npdeovndNO2oMsru5EInwM&e=>.

The IETF Secretariat



--
Ori Finkelman
Qwilt | Work: [phone]<tel:[phone]> | Mobile: [phone]<tel:[phone]> | [e-mail]<mailto:[e-mail]>

_______________________________________________
CDNi mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/cdni<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_cdni&d=DwMFaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=XniVbishGiO2Ao9hKqSc-hTVIWCi3T-x6GdHR4ZTgoM&m=PMnY8KpuUopuFhL6K52t4itbaoUkReKaZaVaU8J_HZM&s=6hmp7qo1TZSSiNlcW7bG_ucwl31519kZiI0tAEWTpLs&e=>