IETF Logo Mail Archive

[CDNi] Triggers playlist: draft-finkelman-cdni-sva-extensions-00.txt

Ben Niven-Jenkins <ben@niven-jenkins.co.uk> Tue, 28 November 2017 12:28 UTC

Return-Path: <ben@niven-jenkins.co.uk>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6BEF1275C5 for <cdni@ietfa.amsl.com>; Tue, 28 Nov 2017 04:28:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level:
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PN04LHnZocHK for <cdni@ietfa.amsl.com>; Tue, 28 Nov 2017 04:28:20 -0800 (PST)
Received: from mailex.mailcore.me (mailex.mailcore.me [94.136.40.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81460126B71 for <cdni@ietf.org>; Tue, 28 Nov 2017 04:28:20 -0800 (PST)
Received: from cpc93788-hari17-2-0-cust3332.20-2.cable.virginm.net ([82.39.109.5] helo=[192.168.0.13]) by smtp04.mailcore.me with esmtpa (Exim 4.89) (envelope-from <ben@niven-jenkins.co.uk>) id 1eJezq-0006OJ-Q3; Tue, 28 Nov 2017 12:28:19 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>
In-Reply-To: <CAMrHYE1zMjUbmV-h4QOxfckW9vaU0k2QjKCUdA5dPSrpnKNmKw@mail.gmail.com>
Date: Tue, 28 Nov 2017 12:28:15 +0000
Cc: Ori Finkelman <orif@qwilt.com>, cdni@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8214AF4-9CDA-4BE3-A5E2-F2B1BD06FE1D@niven-jenkins.co.uk>
References: <150937917932.7823.7624674920223255542.idtracker@ietfa.amsl.com> <CAMb9nTv8RPoi9-z9kPTrrMmT3L-0-iUD6bVj=n_EdsG8q5t+ow@mail.gmail.com> <CAMrHYE2i48Gf7+3LZ_D651nTZwAQc=rLHGnoP6_oS8avjJjqEg@mail.gmail.com> <CAMrHYE1zMjUbmV-h4QOxfckW9vaU0k2QjKCUdA5dPSrpnKNmKw@mail.gmail.com>
To: Kevin Ma <kevin.j.ma.ietf@gmail.com>
X-Mailer: Apple Mail (2.2098)
X-Mailcore-Auth: 9600544
X-Mailcore-Domain: 172912
X-KLMS-Rule-ID: 1
X-KLMS-Message-Action: clean
X-KLMS-AntiSpam-Status: not scanned, license restriction
X-KLMS-AntiPhishing: not scanned, license restriction
X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.721, bases: 2017/11/28 07:07:00 #11127478
X-KLMS-AntiVirus-Status: Clean, skipped
Archived-At: <https://mailarchive.ietf.org/arch/msg/cdni/a7UgmJ_oyyRlfYavSBK_sArcLu0>
Subject: [CDNi] Triggers playlist: draft-finkelman-cdni-sva-extensions-00.txt
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Nov 2017 12:28:22 -0000

Ori, Colleagues,

I just read draft-finkelman-cdni-sva-extensions-00 and have some comments I will send in separate emails to keep each conversation to a single topic.


> On 16 Nov 2017, at 12:27, Kevin Ma <kevin.j.ma.ietf@gmail.com> wrote:
> 
>   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.

Support for multiple optional playlist formats places a burden on the dCDN to support the multiple playlist formats. Multiple optional playlist formats places a burden on the uCDN, e.g. it needs to be able to handle a dCDN that does not support a particular playlist e.g. by transforming the playlist to a dCDN supported format or by falling back to a list of URLs carried in the triggers request.

Support for multiple optional playlist formats therefore (IMO) works against interoperability. What is the use case for requiring multiple optional playlist formats?

What is the envisioned model if a dCDN does not support playlists in trigger requests? Is the uCDN expected to fallback to producing a trigger request with the URLs from the playlist enumerated as *.urls/*.patterns?
 
Thanks
Ben

v2.23.0 | Report a Bug | By Email