Re: [Moq] Flow to join 15 seconds before live

Cullen Jennings <fluffy@iii.ca> Fri, 29 March 2024 14:41 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAM4esxSV5v31kxU0bxeyTfHbncowjF5hskZ28L-EBtOkWXWVvg@mail.gmail.com>
Date: Fri, 29 Mar 2024 08:41:29 -0600
Cc: nathan.burr@paramount.com, "Law, Will" <wilaw=40akamai.com@dmarc.ietf.org>, Alan Frindell <afrind=40meta.com@dmarc.ietf.org>, Suhas Nandakumar <suhasietf@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, MOQ Mailing List <moq@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <400D195B-5060-4671-A07F-558CA2D594A3@iii.ca>
References: <B1E13534-1440-42B7-A820-3EFC405AD558@iii.ca> <CAHVo=ZmUsVvnJ43-_HMjk51OcRJaYJ1iiO94Hfx9askqaMcZTA@mail.gmail.com> <1B369D1B-7B1F-46FE-B2F1-48B453F8DBFA@akamai.com> <CA+9kkMBXWaJuHrrqer6cQcL0MUQ-LURO-FCTpZ=NpTASTfY97w@mail.gmail.com> <CAMRcRGS+k9Y5FgG=jEo9KV4K9N3jM6Uzmdvcmi+w3yXxPUEt0A@mail.gmail.com> <1345E124-ECB0-409E-83F2-4DF485067C2D@fb.com> <BCDC64CD-FECB-46F9-9517-1739F7B1E41D@akamai.com> <CANG3SPxrcyjWL6OgiYPNgLhB5SOTAk8wdppkbNBBMjoo+1W66A@mail.gmail.com> <CAM4esxSV5v31kxU0bxeyTfHbncowjF5hskZ28L-EBtOkWXWVvg@mail.gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/moq/HWZ9IY2hXJ5J4IUyu_Cvzj3klpY>
Subject: Re: [Moq] Flow to join 15 seconds before live
Precedence: list

> On Mar 27, 2024, at 3:24 PM, Martin Duke <martin.h.duke@gmail.com> wrote:
> 
> As an individual, what I don't like about the freeze flag is that it muddies the distinction between SUBSCRIBE (just forward what comes from the publisher) and FETCH (if it's not cached, go get it from the publisher). A frozen SUBSCRIBE is a FETCH for future groups, which to me defeats the whole point of separating FETCH and SUBSCRIBE.

I agree it should not be that. I viewed it as simply a way to tell the relay to pre warm the cache and set up the flow as it the client was subscribed not bother to send the objects to the client.  Using it as way to get the live edge may be the wrong thing todo and it make be that something with semantics more like I suspect Will was imaging with trackinfo would also be needed.

[Moq] Flow to join 15 seconds before live Cullen Jennings
Re: [Moq] Flow to join 15 seconds before live Luke Curley
Re: [Moq] Flow to join 15 seconds before live Ted Hardie
Re: [Moq] Flow to join 15 seconds before live Law, Will
Re: [Moq] Flow to join 15 seconds before live Luke Curley
Re: [Moq] Flow to join 15 seconds before live Suhas Nandakumar
Re: [Moq] Flow to join 15 seconds before live Alan Frindell
Re: [Moq] Flow to join 15 seconds before live Cullen Jennings
Re: [Moq] Flow to join 15 seconds before live Nathan Burr
Re: [Moq] Flow to join 15 seconds before live Martin Duke
Re: [Moq] Flow to join 15 seconds before live Cullen Jennings
Re: [Moq] Flow to join 15 seconds before live Law, Will
Re: [Moq] Flow to join 15 seconds before live Alex Giladi
Re: [Moq] Flow to join 15 seconds before live Luke Curley
Re: [Moq] Flow to join 15 seconds before live Martin Duke
Re: [Moq] Flow to join 15 seconds before live Cullen Jennings
Re: [Moq] Flow to join 15 seconds before live Cullen Jennings