Subject: [Mops] Draft ROUTE
From: Waqar Zia <[email-masked]>
To: Kyle Rose <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Wed, 22 Jul 2020 19:17:59 +0000
List-Id: Media OPerationS <mops.ietf.org>

Dear all,

Related to the following discussions and an earlier thread on DVB ABR spec, we have submitted this I-D on ROUTE here: https://tools.ietf.org/html/draft-zia-route-00 . It is one of the low-latency enabled multicast protocols supported by DVB ABR spec. A summary on ROUTE is in the following:

The Real-time Transport Object delivery over Unidirectional Transport protocol (ROUTE Protocol) is optimized for robust delivery of application objects, including application objects with real-time delivery constraints, to receivers over a unidirectional transport. Application objects consist of data that has meaning to applications that use the ROUTE Protocol for delivery of data to receivers, for example, a file, or a DASH or HLS segment, a WAV audio clip, etc. The ROUTE Protocol also supports low-latency streaming applications and is geared for faster channel acquisition, while at the same time its optimized in terms of signaling overhead.

ROUTE is aligned with FLUTE as defined in RFC 6726 as well as the extensions defined in 3GPP MBMS, but also makes use of some principles of FCAST as defined in RFC 6968; for example, object metadata and the object content may be sent together in a compound object.

Profiles of ROUTE Protocol have already been specified in ATSC 3.0 and DVB Adaptive Media Streaming over IP Multicast. Hence in the context of this I-D, the aforementioned ATSC 3.0 and DVB systems are the applications using ROUTE. This I-D will serve as a direct reference for such applications in the future and allows for deriving specific profiles based on the protocol specified in this I-D.

I imagine it is a bit late to have any detailed discussions on this for the 108th virtual meeting, also considering the very small time slot for MOPS, but I would be happy to present this in future. Your comments and feedback on the draft are most welcome!

Best regards,
Waqar.

Dr. Waqar Zia
Qualcomm CDMA Technologies
O: +49 89 614 694 0031
------------------------------------------------------------------------
Qualcomm CDMA Technologies GmbH
Anzinger Str. 13, 81671 Muenchen
Amtsgericht München, HRB 133031
Geschäftsführer: Daniel Philip Welch

This message may contain information which is confidential or privileged.
If you are not the intended recipient, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy. Thank you.

Qualcomm CDMA Technologies GmbH has taken every reasonable precautions to ensure that any attachments to this e-mail has been swept for viruses.
However, we cannot accept liability for any damage sustained as a result of software viruses and would advise that you carry out your own virus checks before opening any attachment.

From: Mops <[email-masked]> On Behalf Of Kyle Rose
Sent: 25 June 2020 00:38
To: Leslie Daigle <[email-masked]>
Cc: Alexandre GOUAILLARD <[email-masked]>; [email-masked]; Maxim Sharabayko <[email-masked]>; Deen, Glenn <[email-masked]>
Subject: Re: [Mops] Low latency protocol comparision

CAUTION: This email originated from outside of the organization.
On Wed, Jun 24, 2020 at 6:16 PM Leslie Daigle <[email-masked]<mailto:[email-masked]>> wrote:

Hi,

Speaking as only one of the chairs of this group, I have to say I like how this is shaping up.

My only question is whether there is work to be done even at the IETF 108 hackathon, in order to establish the test cases and test suite?

Happy to hear from the other co-chair of this group :^) and any other group participants.

Heh...  As the other co-chair, Leslie and I are in alignment on this. If there's prep work to be done at the 108 hackathon, great! If not, BKK (or, likely, the virtual replacement for it) sounds like a plan. Even if we don't do anything at the 108 hackathon, there's probably a bit of prep we'll want to do prior to the 109 hackathon, including coordinating with Charles on any special network setup we might need should the meeting be held in person.

Kyle