Re: [Hls-interest] [E] Survey: signaling HLS client capability

Trevor Hunsaker <trevor.hunsaker@verizonmedia.com> Thu, 20 May 2021 20:29 UTC

Return-Path: <trevor.hunsaker@verizondigitalmedia.com>
X-Original-To: hls-interest@ietfa.amsl.com
Delivered-To: hls-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8AFF3A24D0 for <hls-interest@ietfa.amsl.com>; Thu, 20 May 2021 13:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verizonmedia.com
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 Hlz2CePIksF1 for <hls-interest@ietfa.amsl.com>; Thu, 20 May 2021 13:29:27 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69D083A24CC for <hls-interest@ietf.org>; Thu, 20 May 2021 13:29:27 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id w1so13245261ybt.1 for <hls-interest@ietf.org>; Thu, 20 May 2021 13:29:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verizonmedia.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cKQXUW+G4FhDm5Ui72nhckiizuEGfWa/HeIVNAweFp4=; b=IWqq29LxIgpVhL8lSZ+xc0hQaGldzVoSzh7TvtgH0NsD2pqMd+lBOOU7giWXipgVCn x9QbWYAJ86fMfNV9Kjqoll8ZghZKcRH92Mt96AAvk7k5eEI9FjYKs5svuOEGtuxxTNsQ SlDN8uzJ/QNK//HdCAB/YfocCIbo6g3vn3oOX11gHz7rithrWUcxMsRyE9nwvbFXc+HC Y57Py9NZffB0zL549msG0WnoX+WL4gMKF/G+3ZP6BDto3+D5Oe7Q/LJDdbUcZKObQosO mHap4/ea8LH/tCpAiDonIU3pf9g1ZImAyblsBDf7MecCfUyE9uyCM4wW0v34mHmSWPsT W83g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cKQXUW+G4FhDm5Ui72nhckiizuEGfWa/HeIVNAweFp4=; b=UpJU0ttElTU4yyuWiDAJx/xIqms+9ovy7n9EzvWZSYYh2yuW/nftdhzPx0k8DO1JuP m2F7qyJOahZ6UmFtCb6uSl0LdISZfnDzMR++Gi7MTPvq/d+olL5G2+Vte/iC1XhCq/TH /bQK++n8xqiOYBdwM4cSnl1EaiY1DOpIKiATJudT0RKUhPExdoLdSh54cXiip8Zjhpva aPqbQFLmuwDHCDQXvu9PCql0v/+8FgO9azW0sIX+JbtD2WCfga9d09ecaCUWEaNQrgsI BKBJ2I1ILFr5DJ8i9sSvJBRLDs7n3q2pzuvWxMKslto+BkBWD0XtFWVHdGWmCYCp0H0a qMdQ==
X-Gm-Message-State: AOAM532bysKie08R5jz/R9BRcO/8Gx0SFCDHiI6EdgVPjWk/GVco/dJO ra9baXQ/IC3BtU6dYUy7BcKNv7oE6lc3tax1dsKIQb1EmG6/vQ==
X-Google-Smtp-Source: ABdhPJzdjkTZlYUH/JoRf1XXe02ikKs/i6EnUB6E78h5SLRhlzQ3Fyp1d/TNvpxb/AOkXNk/84H217OPHyCMpENPF+0=
X-Received: by 2002:a25:2844:: with SMTP id o65mr9713231ybo.356.1621542565542; Thu, 20 May 2021 13:29:25 -0700 (PDT)
MIME-Version: 1.0
References: <8FE883FB-29BD-402B-BB50-E199036281EE@apple.com>
In-Reply-To: <8FE883FB-29BD-402B-BB50-E199036281EE@apple.com>
From: Trevor Hunsaker <trevor.hunsaker@verizonmedia.com>
Date: Thu, 20 May 2021 14:28:59 -0600
Message-ID: <CAH11nzC+yxnVE+-C=xLq-WRhKaswgVUUPharg5D46aOsy0HyRw@mail.gmail.com>
To: Roger Pantos <rpantos=40apple.com@dmarc.ietf.org>
Cc: hls-interest@ietf.org
Content-Type: multipart/alternative; boundary="0000000000009ba67b05c2c8ccc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/hls-interest/_RAtOFvkA8YbXg9Rtq2E4YLTjrk>
Subject: Re: [Hls-interest] [E] Survey: signaling HLS client capability
X-BeenThere: hls-interest@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussions about HTTP Live Streaming \(HLS\)." <hls-interest.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hls-interest>, <mailto:hls-interest-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/hls-interest/>
List-Post: <mailto:hls-interest@ietf.org>
List-Help: <mailto:hls-interest-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hls-interest>, <mailto:hls-interest-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 May 2021 20:31:18 -0000

As a "people already doing something along these lines... what requirement
is driving that":

For us At Verizon Media, the requirement is often to omit some feature that
is causing an issue in a player over which our customers have little or no
control. For example, we semi-recently discovered that some
AirPlay2-enabled smart TVs are incapable of handling full-segment-encrypted
.aac alternate audio tracks, and crash when presented with them (submitted
bug FB8948360 about this). Our encoding pipeline takes longer to adapt than
our manifest generation system, so we added support for a URL parameter as
a means of instructing our manifest server to omit such tracks from the
manifest. We have a small handful or two of such URL params floating in our
system, as workarounds for all kinds of players in the ecosystem.

We've also used the User-Agent to help us decide which HLS version a device
is capable of supporting, and try to be compliant about which features we
include for a given HLS version.




On Thu, May 20, 2021 at 10:00 AM Roger Pantos <rpantos=
40apple.com@dmarc.ietf.org> wrote:

> With the increasing number of optional features in HLS (such as low
> latency, content steering, interstitial support, different codecs, etc.),
> there is a desire in some quarters to present different streams to
> different devices, beyond the regular variant stream selection performed on
> the client.
>
> We're considering some kind of signal of client capability, such as a
> query parameter on the Master Playlist URL, to support this kind of server
> decision. But before we go too far I'd like to understand if it would
> actually be of practical benefit, and what universe of use cases it makes
> sense to support. So:
>
> - Do you think you would use this kind of thing? For what?
>
> - If you are already doing something along these lines, perhaps driven by
> the User-Agent string or something else, what requirement is driving that?
>
> (Alternately, if you think that this would only make things worse, let us
> know why!)
>
> Feel free to respond here, or to send your response privately to
> http-live-streaming-review@group.apple.com.
>
>
> thanks,
>
> Roger Pantos
> Apple Inc.
> --
> Hls-interest mailing list
> Hls-interest@ietf.org
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_hls-2Dinterest&d=DwICAg&c=sWW_bEwW_mLyN3Kx2v57Q8e-CRbmiT9yOhqES_g_wVY&r=XOy1sMJB-v4-pT8o8aTMSGXStN19eHAo6D_AaKvUJso&m=gG3_laqdYt1I2B9tqBUeHVl36ZLo-643YDPapqmGjm4&s=6cLzncMjPm1DCxoql2i_D9waQJFNTn4k3tF3J-qw-Eo&e=
>