Re: [V3] Gateway new to old

It may be a reasonable goal to aim to re-use RTP payload formats as the media packetisation within the new transport. That is, different headers and transport, but format the media content the same way.

Since payload format packetisation already all have registered media types this would make the media content easy to identify, and save a lot of work in re-defining packetisation schemes.

Colin

> On 27 Mar 2020, at 20:22, Justin Uberti <juberti=40google.com@dmarc.ietf.org> wrote:
> 
> It's hard to imagine that we can avoid this if we are in fact going to use H3 as a substrate. 
> 
> I do think it would be useful to ensure the RIPT->RTP gateway can be stateless and transparent (i.e., you can transform a RIPT frame into a RTP packet with reasonable fidelity), so that said gateway is all you need in order for existing services to participate in the RIPT ecosystem.
> 
> On Fri, Mar 27, 2020 at 9:32 AM Cullen Jennings <fluffy@iii.ca <mailto:fluffy@iii.ca>> wrote:
> 
> 
>> On Mar 27, 2020, at 8:23 AM, Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org <mailto:magnus.westerlund=40ericsson.com@dmarc.ietf.org>> wrote:
>> 
>> The next media transport issue that was barely discussed in the BOF is the
>> legacy (RTP) interoperate question. This is going to come back in the scope
>> discussion and do needs at least a direction. 
> 
> In WebRTC, we decided to be able to gateway SIP to WebRTC without processing media. That turned out to be a major limitation to how WebRTC worked. That is good and we have WebRTC but for this, I am storngly of the view we should not have that design constraint. 
> 
> I think it is fine to require a media gateway to go from RIPT to RTP. Sure that should be pretty easy - one of the major use cases for this work will likely involve building SBCs that talk RIPT on one side and SIP on the other. Pretty sure that a bunch of other people are thinking about the same. 
> 
> That sound right to you are or are you arguing for something else ?
> 
> 
> -- 
> V3 mailing list
> V3@ietf.org <mailto:V3@ietf.org>
> https://www.ietf.org/mailman/listinfo/v3 <https://www.ietf.org/mailman/listinfo/v3>
> -- 
> V3 mailing list
> V3@ietf.org
> https://www.ietf.org/mailman/listinfo/v3