Re: [MMUSIC] [avtext] framemarking: add frame size info

"Mo Zanaty (mzanaty)" <> Mon, 27 March 2017 15:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DF870129739; Mon, 27 Mar 2017 08:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id UKSKk0FVCwQM; Mon, 27 Mar 2017 08:10:45 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 52E4B129452; Mon, 27 Mar 2017 08:10:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=35008; q=dns/txt; s=iport; t=1490627445; x=1491837045; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=yokPB9x+mOsNyzalEbA86NnY5E47reCOnpbrmu7jk2A=; b=GSfZWNJ1tzUVAMiyEBrlXELO2zkYWggDqKhLwYLLpP8XiRNCSYib//LH fR3R0n9HLwMhQ2dk1d3Jj2bLzX82vrq7R7zZljd3ofz14zlIV2t15lIKe rYukzOErucTn5vRxvAGTiS5jTJ4fbIsS4CQ1BZPgYiwr94ZgR3Utj9Pzf Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DJAQAvKtlY/51dJa1SCgEYAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGCbjsrYYELB4NbY4kskU2IF400gg4fAQyCQIJsSgIagns/GAE?= =?us-ascii?q?CAQEBAQEBAWsohRUBAQEBAwEBITIZCwwEAgEIEQMBAQEhBwMCAgIfBgsUCQgCB?= =?us-ascii?q?AENBQkSiVQDFQ6rX4Imhy8NgwMBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhk6DZoE?= =?us-ascii?q?JglGBWyQUBwkegkiCXwWJHgeMZ4YVOgGGeocbhDaBfFSBC4cihjSKbQIkhCyEJ?= =?us-ascii?q?QEfOIEEWRVBhB85HYFjdQEBiCaBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.36,232,1486425600"; d="scan'208,217";a="214964986"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Mar 2017 15:10:43 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v2RFAhlD016944 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 27 Mar 2017 15:10:44 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 27 Mar 2017 10:10:43 -0500
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Mon, 27 Mar 2017 10:10:42 -0500
From: "Mo Zanaty (mzanaty)" <>
To: =?utf-8?B?TWlndWVsIFBhcsOtcyBEw61heg==?= <>, "Jonathan Lennox" <>
CC: "" <>, mmusic <>
Thread-Topic: [MMUSIC] [avtext] framemarking: add frame size info
Thread-Index: AQHSpwxN7LteRg2zYk6+J0YoGnCPzQ==
Date: Mon, 27 Mar 2017 15:10:42 +0000
Message-ID: <>
References: <> <em8de2860d-9b70-44ce-87e5-3c6ecb1fb1ee@sydney> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D4FEA22D6B914mzanatyciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [MMUSIC] [avtext] framemarking: add frame size info
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 27 Mar 2017 15:10:49 -0000

Hi Miguel,

This was discussed in IETF 97 during the AVTEXT session on Frame Marking.
See the slides and minutes.

The recommended and agreed solution was to use RID rather than add frame size
in the Frame Marking header extension.


From: mmusic <<>> on behalf of Miguel París Díaz <<>>
Date: Monday, March 27, 2017 at 3:43 AM
To: Jonathan Lennox <<>>
Cc: "<>" <<>>, "<>" <<>>
Subject: Re: [MMUSIC] [avtext] framemarking: add frame size info

Hello again,
is there anybody considering this proposal, or nobody see the benefits?

Kind regards!!

2016-11-10 15:18 GMT+01:00 Miguel París Díaz <<>>:
in the new draft of sdp-simulcast an "RTP Aspect" section [1] has been added, which explains how the media is handled on RTP level.

Specifically, In the Media-Switching Mixer section [2] the same thoughts I exposed are said:

   This section discusses the behavior in cases where the RTP middlebox
   behaves like the Media-Switching Mixer (Section 3.6.2<>) in RTP
   Topologies [RFC7667<>]7>].  The fundamental aspect here is that the media
   sources delivered from the middlebox will be the mixer's conceptual
   or functional ones.  For example, one media source may be the main
   speaker in high resolution video, while a number of other media
   sources are thumbnails of each participant.

   The above results in that the RTP stream produced by the mixer is one
   that switches between a number of received incoming RTP streams for
   different media sources and in different simulcast versions.  The
   mixer selects the media source to be sent as one of the RTP streams,
   and then selects among the available simulcast streams for the most
   appropriate one.  The selection criteria include available bandwidth
   on the mixer to receiver path and restrictions based on the
   functional usage of the RTP stream delivered to the receiver.  An
   example of the latter, is that it is unnecessary to forward a full HD
   video to a receiver if the display area is just a thumbnail.  Thus,
   restrictions may exist to not allow some simulcast streams to be
   forwarded for some of the mixer's media sources.

In our case to provide this feature, currently we have to depay the RTP packets, and apply different types of parses (depending on the codec) to read the frame size, which reduces the scalability of the system and hinder the implementation a lot.
Because of that, I think that having frame size (width and height) info in the Frame Marking RTP header extension is quite interesting to implement this kind of use cases in a easy and efficient way (the same that an audio-level extension header is provided to avoid analysing it in the middlebox side).

I am adding MMUSIC group in the thread, because I think that this also should be discussed in the context of the simulcast case.



2016-08-30 12:37 GMT+02:00 Miguel París Díaz <<>>:
I assume that the media distributor has the information from the SDP (it performs the SDP negotiation which each "client"), but the point is that encoders may change the video size depending on the available bandwidth, the complexivity of the video source, etc., unless the sender forces the encoders' configuration with a fix frame size...

2016-08-26 19:07 GMT+02:00 Jonathan Lennox <<>>:
(As an individual.)

In the latest version of simulcast the media distributor would need the RID values, not the PT values, but the idea is the same — it needs the SDP.

Note that if the media distributor doesn’t have information from the SDP it can’t reliably identify the frame marking header extension at all, since header extension IDs are negotiated. So I’m not sure how much benefit there is to putting the size in the header extension.

That said, if we envision a scenario where encoders might be frequently changing their video size (in response to available network bandwidth, or the like), it might be useful for encoders to be able to indicate the current size they’re encoding without needing to send updated SDP all the time.

On Aug 26, 2016, at 12:52 PM, Paul E. Jones <<>> wrote:


You make the assumption that the media distributor will not see the SDP, I suppose.  While certainly a valid model, I'll admit that I had personally assumed any media forwarding function would see the SDP (or at least be told the PT values and any relevant flow information similar to what RFC 6236 provides) and would thus know which PT values correspond to what video resolutions if simulcast is employed.


------ Original Message ------
From: "Miguel París Díaz" <<>>
Sent: 8/25/2016 10:12:48 AM
Subject: [avtext] framemarking: add frame size info

it would be great having frame size (width and height) info in the Frame Marking RTP header extension [1].

For example, in the case of using simulcast in an SFU, selecting the stream by the size would ease the application development and improve the experience of the users.
Application developers don't usually have deep knowledge about media like bitrate, etc., but they know which video size has to be rendered in the GUI, which may depend on the client where the app is running: a mobile, a PC with a 13"· screen, a PC with 27" screen, etc.

In this way and taking a videoconference app as example, if a participant select another participant to be rendered as main video, the app could ask the SFU to select the video quality that better matches to 800x600 size.

What do you think about this idea?

Thanks and best regards!!


Miguel París Díaz
Computer/Software engineer.
Researcher and architect in<>
avtext mailing list<>

Miguel París Díaz
Computer/Software engineer.
Researcher and architect in

Miguel París Díaz
Computer/Software engineer.
Researcher and architect in

Miguel París Díaz
Computer/Software engineer.
Researcher and architect in