[avtext] framemarking: add frame size info
Miguel París Díaz <mparisdiaz@gmail.com> Thu, 25 August 2016 14:12 UTC
Return-Path: <mparisdiaz@gmail.com>
X-Original-To: avtext@ietfa.amsl.com
Delivered-To: avtext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F66E12D0F1 for <avtext@ietfa.amsl.com>; Thu, 25 Aug 2016 07:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhRv_foDj7zH for <avtext@ietfa.amsl.com>; Thu, 25 Aug 2016 07:12:53 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E4B12B02E for <avtext@ietf.org>; Thu, 25 Aug 2016 07:12:51 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id i5so74196392wmg.0 for <avtext@ietf.org>; Thu, 25 Aug 2016 07:12:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=HaS0azw07pVNoyfw85fFzNO4hM68RBn2CeR8oYODIqQ=; b=KIVCDNVTuegyZqE6d3k6gjjvxpYe5TDeeaidk7k9x9djnJ0BtzJkFlDGJ8So3F6oMZ XkDP67/cIemn1VUimiOwPyPJuqeNvwgtRsiRL6JeqDaujA64qThZ1fPVtlTf1VswTcX7 yWQlFiHwsDXX1vXOoYiWo9uWvA/7PbrhFiOaG5w149de0wQulbj0LhxMsmuAqbO7V2fD HN1hr+xFV91wGNzUt0QUhlQF0ixH/bYAAdNUuf+EEYP8gzbXj5Cd1lR7L/Hs5WW7Pa1f ldxAu4O5Xb9cyRstBCMAB0sEQeXG4q0B+YYRJXDQvreEsS7q7s1S69y4hm8yLsdzO6Fv mfRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HaS0azw07pVNoyfw85fFzNO4hM68RBn2CeR8oYODIqQ=; b=NOKCdXMyD8em+AHEM9DHQbsoTsRiWc4EsGAHFsKeJuktOc83t+E+de2GYTQnTfKtS4 OOrvm0aHxW7Y4CSOfaNdh0XazAqh6oBc0FoC0nJcfniXjBgDcGvBgX1gKqp/dWHbpleZ v+3e8WN5H8mXSY34mTEKGqI2AtnDz60JzlT6EuUUu0b3wOpSHD7XAa0rY25p40ZlndcL yQXZ3oGr70Q+nm5Nl3HQ9mUh5QlQCLjDRiVOgUnz7lCl7QPHbJWoUqgxvdL4hjkLjF5J P97khyw56kbBI9i1HG1paJBi/U/1ym+lIJyMuMLQ2+6jPyqWHX3JT+ppVblMnLjVSfO5 vz2g==
X-Gm-Message-State: AEkoouv6wgltODyJ/5oHYAubh3vcZ5bWuJkiwuqkXyMfrwEkn8B02UZbUmlBWJ9CDNAREs26BdJVCwtXhLAYJg==
X-Received: by 10.194.148.202 with SMTP id tu10mr8235440wjb.56.1472134369285; Thu, 25 Aug 2016 07:12:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.57.208 with HTTP; Thu, 25 Aug 2016 07:12:48 -0700 (PDT)
From: Miguel París Díaz <mparisdiaz@gmail.com>
Date: Thu, 25 Aug 2016 16:12:48 +0200
Message-ID: <CAEn+E3h-b=8VEkhZ56Z9Ww+mTCA2H1B93UAkgbfmySyi2CnvnA@mail.gmail.com>
To: avtext@ietf.org
Content-Type: multipart/alternative; boundary="089e0122825e249df2053ae5feae"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avtext/CcmDkCGQ3ORO77u-ADBPFSgEmY8>
Subject: [avtext] framemarking: add frame size info
X-BeenThere: avtext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Audio/Video Transport Extensions working group discussion list <avtext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avtext>, <mailto:avtext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avtext/>
List-Post: <mailto:avtext@ietf.org>
List-Help: <mailto:avtext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avtext>, <mailto:avtext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2016 14:12:57 -0000
Hello, it would be great having frame size (width and height) info in the Frame Marking RTP header extension [1]. Why? 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!! Refs [1] https://tools.ietf.org/html/draft-ietf-avtext-framemarking-02 -- Miguel París Díaz ------------------------------------------------------------------------ Computer/Software engineer. Researcher and architect in http://www.kurento.org http://twitter.com/mparisdiaz ------------------------------------------------------------------------
- [avtext] framemarking: add frame size info Miguel París Díaz
- Re: [avtext] framemarking: add frame size info Paul E. Jones
- Re: [avtext] framemarking: add frame size info Jonathan Lennox
- Re: [avtext] framemarking: add frame size info Miguel París Díaz
- Re: [avtext] framemarking: add frame size info Miguel París Díaz
- Re: [avtext] framemarking: add frame size info Miguel París Díaz
- Re: [avtext] [MMUSIC] framemarking: add frame siz… Mo Zanaty (mzanaty)
- Re: [avtext] [MMUSIC] framemarking: add frame siz… Miguel París Díaz