Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below

[Spencer Dawkins at IETF <[e-mail]>]

Hi, Justin,

On Tue, Feb 18, 2020 at 10:01 PM Justin Uberti <[e-mail]> wrote:

>
>
> On Tue, Feb 18, 2020 at 2:47 PM Spencer Dawkins at IETF <
> [e-mail]> wrote:
>
>> I am also hoping for clarity here, or at least clue.
>>
>> On Tue, Feb 18, 2020 at 2:02 PM Ross Finlayson <[e-mail]>
>> wrote:
>>
>>>
>>> > On Feb 19, 2020, at 5:12 AM, Jonathan Rosenberg <[e-mail]>
>>> wrote:
>>> >
>>> > Also to be clear - whilst I agree that RTP on QUIC is interesting - it
>>> is not in scope because httpbis is our target, not quic. We want to allow
>>> voice signaling and media to run over web infrastructure services, so http
>>> is our 'waist of the hourglass' not quic.
>>>
>>> So just to clarify here:  Is your goal (for this protocol) that media be
>>> transferred only over streams (TCP or (reliable) QUIC), not datagrams?
>>> Consequently, how important is end-to-end latency for audio/video calls
>>> that would use this protocol?
>>>
>>> And are peer-to-peer audio/video calls (that would not involve a web
>>> server at all, except perhaps for initial end-user lookup/discovery) out of
>>> scope for this protocol?
>>>
>>> If that's the case, then you’re not really ‘replacing’ RTP, but rather
>>> defining a new media transport protocol to be used in this one (restricted,
>>> but important) environment: Transport using reliable protocols via web
>>> server(s).  And if that’s the case, then I’m concerned that your SIP
>>> replacement (i.e., replacement of the one thing that’s truly broken, and
>>> needs replacing) might end up being too restrictive for more general media
>>> transport (datagrams and/or peer-to-peer).
>>>
>>
>> I think I arrived at the same place as Ross, coming from the opposite
>> direction. ("Thunk!")
>>
>> ISTM that the proposal floating through here for a new media transport
>> protocol, if it is successful, would be useful for non-RIPT applications as
>> well, and ISTM that other proposals for RTP over QUIC (or whatever we're
>> all muttering about privately), if one of them is successful, might be
>> useful for RIPT applications as well.
>>
>> So, the first suggestion I'd make at the BOF, if work on media transport
>> of whatever flavor is still part of the proposed RIPT charter, is to split
>> it off into a separate proposal, which I'd love to see go forward on its
>> own, unless there are really strong reasons why RIPT signaling
>> specification work and RIPT media transport work need to be coupled, need
>> to fate-share, and need to compete for attention in the same working group.
>>
>> I can say more about that at a mike in Vancouver, but let me start with
>> this, on a mailing list ...
>>
>
> Spencer -
>

This time, I AM Spencer :-)


> I agree that the signaling and media transport aspects are separable, but
> ultimately many applications will deploy them together, and perhaps
> multiplex them over the same HTTP transport. As such, there's definitely
> value in having a WG that considers the overall problem space and the
> various interactions between the layers (I think there are actually 3
> layers - signaling, session descriptions, and media transport).
>

"Consider" is the key word, and I think that's an invitation to good
systems engineering. No objection to that.

My suggestion is that the BOF proponents be really clear about what they
expect to happen after the considering, and especially asking whether work
on media relies on the same expertise as signaling, and (speaking as past
AD for QUIC) whether you really need everyone in the same room at the same
time, with no opportunity for parallel processing of separable topics.

At a minimum, I'd suggest adding AVTCORE, MMUSIC, and ICE to the list of
working groups to coordinate with.

But do the right thing, of course :-)

Best,

Spencer


> Certainly worth discussing further though.
>
>
>> Best,
>>
>> Spencer
>>
>>
>>> Ross Finlayson
>>> Live Networks, Inc.
>>> http://www.live555.com/
>>>
>>> --
>> V3 mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/v3
>>
>