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

[Ori Finkelman <[e-mail]>]

Hi Kevin,
I will try to pull more people from the SVA OCWG into CDNI so we can get
better perception of how content providers and CDNs will be using these
interfaces.
Please see comments below:

On Thu, Nov 16, 2017 at 8:27 PM, Kevin Ma <[e-mail]> wrote:

> 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.
>
[OF] >> Agree, will updated.

>
>   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.
>
[OF] >> I will change to content.playlists

>
>   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.
>
[OF] >> Sanjay, maybe we can pull in to this discussion relevant people
from commercial CDNs so they can explain how they see logging from their
perspectives ?

>
>   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.
>
[OF] >> As far as I understand, some relation to CORS is a must when
delegating between CDNs, otherwise the dCDN will not be sending the proper
CORS response headers and the client will not receive the content.
I agree tough, that this is a general caching issue, so technically that
could go into the generic caching specifications rather than CDNI. Do you
think there is an option to define it in a different working group ?
See what Fastly has to say about this
https://www.fastly.com/blog/caching-cors/
Basically they say you either have to use Vary, in which case you will get
different copies for different origins, or you can use logic to filter on
allows origins and set them properly in the ACAO response header, Fastly
use VCL for that, but that is an implementation detail.


>
> thanx.
>
> --  Kevin J. Ma
>
>
> On Thu, Nov 16, 2017 at 6:57 AM, Kevin Ma <[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]> 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
>>> Status:         https://datatracker.ietf.org/
>>> doc/draft-finkelman-cdni-sva-extensions/
>>> Htmlized:       https://tools.ietf.org/html/d
>>> raft-finkelman-cdni-sva-extensions-00
>>> Htmlized:       https://datatracker.ietf.org/
>>> doc/html/draft-finkelman-cdni-sva-extensions-00
>>>
>>>
>>> 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.
>>>
>>> The IETF Secretariat
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Ori Finkelman*Qwilt | Work: [phone] <072-222-1647> | Mobile:
>>> [phone] <052-383-2189> | [e-mail]
>>>
>>> _______________________________________________
>>> CDNi mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/cdni
>>>
>>>
>>
>


-- 

*Ori Finkelman*Qwilt | Work: [phone] <072-222-1647> | Mobile:
[phone] <052-383-2189> | [e-mail]