From nobody Tue Nov 1 06:44:01 2016 Return-Path: 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 8020412955D; Tue, 1 Nov 2016 06:43:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.221 X-Spam-Level: X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 WVUao8U7nvF9; Tue, 1 Nov 2016 06:43:49 -0700 (PDT) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02B231294EA; Tue, 1 Nov 2016 06:43:47 -0700 (PDT) X-AuditID: c1b4fb3a-d9bff700000078c6-a0-58189c11bfcf Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.183.84]) by (Symantec Mail Security) with SMTP id 70.19.30918.11C98185; Tue, 1 Nov 2016 14:43:46 +0100 (CET) Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.3.319.2; Tue, 1 Nov 2016 14:43:45 +0100 To: IETF AVTCore WG , "avtext@ietf.org" , ART ADs From: Magnus Westerlund Message-ID: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> Date: Tue, 1 Nov 2016 14:43:43 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 8bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42KZGbE9RFdojkSEwaZJUhYbn05msXjZs5Ld 4uO9G6wOzB5LlvxkCmCM4rJJSc3JLEst0rdL4MpY/W0zc8E8roonT+cwNTDO5Ohi5OSQEDCR +HXmC1MXIxeHkMA6RokJK24yQjjLGCXmTTrN3sXIwSEikCrRMMkZpIFNwELi5o9GNhBbWMBU Yt/yBWA2r4C9xMbXbUwgNouAisTt7h4wW1QgRuL6s0dQNYISJ2c+YQEZyQxU/2BrGUiYWUBe onnrbGYQW0hAW6KhqYN1AiPvLCQdsxA6ZiHpWMDIvIpRtDi1uDg33chIL7UoM7m4OD9PLy+1 ZBMjMJQObvlttYPx4HPHQ4wCHIxKPLwFMeIRQqyJZcWVuYcYJTiYlUR4lWdLRAjxpiRWVqUW 5ccXleakFh9ilOZgURLnNVt5P1xIID2xJDU7NbUgtQgmy8TBKdXA2NUaoVrtW6+WWaLZtT0y a1JXwKLak7cP2DCW/NJlzg4SbPYsnFvF2HQ2L/Hhkbu5lkqhrd59bEsWnXsaGPTYLvKZ7pRp 2uxPSsITNvcw94qknBSq4GO7X/SrmOV32drFp5Y8k/7KvSxeYfFUxRezXqxdc+OOfNmxWVvu 1VbELTqc+FdF5nqqEktxRqKhFnNRcSIAzbXvWSECAAA= Archived-At: Subject: [avtext] Merging AVTCORE and AVTEXT into a single WG? X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 13:43:56 -0000 AVTCORE, and AVTEXT, The WG chairs and ADs have had some discussion about if AVTCORE and AVTEXT should be merged. The main reason is that the participant overlap is large, and the amount of work currently in the two WGs are low enough that a single WG would still not have a heavy load. Benefits of a merge would be that fewer WG chairs would be needed, a single meeting slot when we meet (which we anyway have been doing lately). We have not discussed any changes to the scope of the charters. So what do you as participant think about this proposal? Please provide your views and feedback. We have also scheduled time for discussing this at the end of the AVTEXT followed by AVTCORE meeting slot in Seoul. This is to provide input to the ADs which is the ones that in the end make the decision. Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 Färögatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- From nobody Tue Nov 1 07:17:57 2016 Return-Path: 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 4880212954E; Tue, 1 Nov 2016 07:17:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.221 X-Spam-Level: X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 LTdmqeGX6oiz; Tue, 1 Nov 2016 07:17:51 -0700 (PDT) Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AE3A1296FF; Tue, 1 Nov 2016 07:17:46 -0700 (PDT) X-AuditID: c1b4fb2d-5b107980000009f7-3f-5818a4080f7f Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by (Symantec Mail Security) with SMTP id 87.60.02551.804A8185; Tue, 1 Nov 2016 15:17:44 +0100 (CET) Received: from ESESSMB209.ericsson.se ([169.254.9.177]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.03.0319.002; Tue, 1 Nov 2016 15:17:43 +0100 From: Christer Holmberg To: Magnus Westerlund , IETF AVTCore WG , "avtext@ietf.org" , ART ADs Thread-Topic: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? Thread-Index: AQHSNEYARfamcArD50eUs1TtG0ljh6DELvqA Date: Tue, 1 Nov 2016 14:17:42 +0000 Message-ID: References: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> In-Reply-To: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.9.160926 x-originating-ip: [153.88.183.20] Content-Type: text/plain; charset="iso-8859-1" Content-ID: <53CBFBC6CF4182459FB12670569167D0@ericsson.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMIsWRmVeSWpSXmKPExsUyM2K7oi7HEokIg3U/dSw2Pp3MYvGyZyW7 xcd7N1gdmD2WLPnJFMAYxWWTkpqTWZZapG+XwJXxffpn5oI+3oqfLd0sDYx3uboYOTkkBEwk tk/4yNzFyMUhJLCOUWLKnIeMEM5iRolbbR+AMhwcbAIWEt3/tEHiIgKzGSV6705kBukWFnCW 2L35CBOILSLgIrHx91ZWCNtIoufQM3YQm0VARWLX+wVgcV4Ba4mGZVPAeoUE7CWuN19iBJnP KeAg8eiPKEiYUUBM4vupNWAjmQXEJW49mc8EcaiAxJI955khbFGJl4//sYK0igroSay5HwYR VpS4On05VKuexI2pU9ggbGuJR9Oes0DY2hLLFr5mhrhGUOLkzCcsExjFZiHZNgtJ+ywk7bOQ tM9C0r6AkXUVo2hxanFxbrqRsV5qUWZycXF+nl5easkmRmBUHdzyW3cH4+rXjocYBTgYlXh4 C2LEI4RYE8uKK3MPMUpwMCuJ8MoslogQ4k1JrKxKLcqPLyrNSS0+xCjNwaIkzmu28n64kEB6 YklqdmpqQWoRTJaJg1OqgZH1E8dmIRsbDpvawtD1f4rWz3K1Vl6z6ftt1buaOa4qdzb8urew QFeR5eCaJ0/PJ/okuuRGXfvAbtul9bng4N31ey5MDYibxHGGW/nfvO+Z3f8zY7cwlpi8erkx R/ha+QUrd52kJV/s139Zcqt9qtnRR1Yb/2ZyLP9jK6V+3/Bj6a1fAmt/LpJWYinOSDTUYi4q TgQAJPs2JaYCAAA= Archived-At: Subject: Re: [avtext] [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2016 14:17:53 -0000 Hi, I support the merger. Regards, Christer On 01/11/16 15:43, "avt on behalf of Magnus Westerlund" wrote: >AVTCORE, and AVTEXT, > >The WG chairs and ADs have had some discussion about if AVTCORE and >AVTEXT should be merged. The main reason is that the participant overlap >is large, and the amount of work currently in the two WGs are low enough >that a single WG would still not have a heavy load. Benefits of a merge >would be that fewer WG chairs would be needed, a single meeting slot >when we meet (which we anyway have been doing lately). We have not >discussed any changes to the scope of the charters. > >So what do you as participant think about this proposal? Please provide >your views and feedback. > >We have also scheduled time for discussing this at the end of the AVTEXT >followed by AVTCORE meeting slot in Seoul. > >This is to provide input to the ADs which is the ones that in the end >make the decision. > >Magnus Westerlund > >---------------------------------------------------------------------- >Services, Media and Network features, Ericsson Research EAB/TXM >---------------------------------------------------------------------- >Ericsson AB | Phone +46 10 7148287 >F=E4r=F6gatan 6 | Mobile +46 73 0949079 >SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com >---------------------------------------------------------------------- > >_______________________________________________ >Audio/Video Transport Core Maintenance >avt@ietf.org >https://www.ietf.org/mailman/listinfo/avt From nobody Wed Nov 2 01:47:11 2016 Return-Path: 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 F20401294BE; Wed, 2 Nov 2016 01:47:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.22 X-Spam-Level: X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.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 uUgqJ5X6WJWV; Wed, 2 Nov 2016 01:47:08 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D596A126D74; Wed, 2 Nov 2016 01:47:07 -0700 (PDT) X-AuditID: c1b4fb25-93fff70000001e3e-1d-5819a80946e8 Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.183.39]) by (Symantec Mail Security) with SMTP id 5D.6F.07742.908A9185; Wed, 2 Nov 2016 09:47:06 +0100 (CET) Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.39) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 2 Nov 2016 09:47:05 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=IyixpZw0TPLrTtZUMWkULi4D1P1Yu3UtcSTHP+7Gp6s=; b=FgPRsJTRJklayKvhDCjigit/XN3kIW/wgx0nB2VUveX/68hR34mC06RNq41qS6YzqcgOzMLgVMd/Ioef31RrfgIetSyxKXO4iR+SznqEnqm2RDXBQJvNW47SZnAMshMVJ7IAwLUPKdVsdZVZLxwTEoIk2pGdOinHsPPUfBJae70= Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com (10.173.92.21) by AM5PR0701MB2579.eurprd07.prod.outlook.com (10.173.92.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.707.1; Wed, 2 Nov 2016 08:47:04 +0000 Received: from AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) by AM5PR0701MB2577.eurprd07.prod.outlook.com ([10.173.92.21]) with mapi id 15.01.0707.004; Wed, 2 Nov 2016 08:47:04 +0000 From: Bo Burman To: Christer Holmberg , Magnus Westerlund , IETF AVTCore WG , "avtext@ietf.org" , ART ADs Thread-Topic: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? Thread-Index: AQHSNEYM6Gt7yYBE6UKRinujtyNQQaDELN4AgAE19XQ= Date: Wed, 2 Nov 2016 08:47:04 +0000 Message-ID: References: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=bo.burman@ericsson.com; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [95.204.70.62] x-ld-processed: 92e84ceb-fbfd-47ab-be52-080c6b87953f,ExtAddr x-ms-office365-filtering-correlation-id: 5043aed7-e06b-491f-8dac-08d402fcd24b x-microsoft-exchange-diagnostics: 1; AM5PR0701MB2579; 7:HP1eFSAkltWh6ebnsZsV1MQJsckB3/RU062OYMWQO0MZUwywwraTMqZXKHRfyafQih5CQR9M7o0u0mVbDCPU49kYJzZGvaSxNVt2yeiMOonQ4ksDV0YaHCqzIOpqlaXYjrlVmU8gyIxKNP6+mIzl99UdiDvvLVoQjAMLRykLqWqKQddlro1GQ7OC2usbt/gBLkkyXGzBfEJ4UKu6smzbOj+5TnS2X+cTX80J2y8xx92+KZVm+nMCpIaOo7kGTMsyFhL3j6KeGDtA0klr2++5KHU2aLxdCsj2NdMudeLzXA83njx33j3vw9abmb1idX8+HRoKykq19GbU40h4IDdF1iwM4kao/58yr0CnTrLhnBw= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2579; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(37575265505322)(158342451672863); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001); SRVR:AM5PR0701MB2579; BCL:0; PCL:0; RULEID:; SRVR:AM5PR0701MB2579; x-forefront-prvs: 0114FF88F6 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(189002)(199003)(377424004)(24454002)(5660300001)(92566002)(3280700002)(76176999)(3660700001)(95246002)(54356999)(561944003)(66066001)(50986999)(19580395003)(3846002)(19580405001)(86362001)(122556002)(586003)(2906002)(102836003)(16236675004)(6116002)(9686002)(19625215002)(101416001)(2950100002)(8936002)(2501003)(15975445007)(5002640100001)(77096005)(68736007)(7736002)(7846002)(450100001)(7906003)(8676002)(81156014)(81166006)(10400500002)(97736004)(5001770100001)(2900100001)(63666004)(106356001)(106116001)(107886002)(11100500001)(33646002)(189998001)(87936001)(105586002)(19617315012)(229853001)(51650200001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM5PR0701MB2579; H:AM5PR0701MB2577.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_p1px1ish5nl1046j6qqna8js1478076423072emailandroidcom_" MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Nov 2016 08:47:04.7992 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2579 X-OriginatorOrg: ericsson.com X-Brightmail-Tracker: H4sIAAAAAAAAA02Se0iTYRTGef0u+xyt3tbMownF6KbltMyQXKYkaokQpHih28oPNafTbUqG gYEieSlrmZesqc1S85JhJWWZsxATk5DKdDOqZaw0zIwQxfLbt8L/fu/zPIf3nMNhCHEd5cok pWpZdapCKaWFZEXMg02ewnqXGO/Bd6Rf22cd6WctahD4/RgbpgKJMINh1uEAihPK41llUiar 9go4Jkws/zpEp732OjXTFJmDzroXIIYBvANaa08WIEdGjFsQzLRoC5BwkXsRGCqvUtyDxMUE fDFWO/CpKw4wWk7+Tz2/MC7gDBpvBn2HGXGGBA8i6PvTjDhjFd4L50pqbCzBwdA2d4/ivpbg XVBcFsbJJF4P+vp+mmMRDoHzQz9tETFWwfxEHCc7YjlYrcUkxwivht8vmmz9ENgZRix6GwPG YOgcJHh2AuunBYrPx4Lu4oCA17fCwFsL4nkdTLZN23U5lBeW2WsjYLq2juZGAVxLQG3npL0g DCYt+fbQYm8DEzS/xXDoGJPx+U4E7aY6ks+4wcvGJwRvNNFQ1WVG/BZZuNWch0qQR+WSIXhW QmtJEV1p28VK6KuwkLwug+HSyzTPW+BmzTeCZ08oXzCSS/VqJGhEThpWczwlYbuPjFUnndBo VKmyVFZ7Fy0eT3f73IYONDQRZESYQdJloqlmiBFTikxNVooRAUNIJSLiukuMWBSvyDrNqlVH 1RlKVmNEaxhS6iza2fA+WowTFFo2mWXTWPU/14FxdM1BIXSeYEVrpmnjjD4xNq76lSmihziz PCNavydAfn/2KaWGfn+zmy73UUOewVs3fjA4299nsPRhYMrMvG/6hOmadCoyav4NPrLvdmhj RXeQOQr1hF/KP+T8kWIK0S9fZeizhSoZeyN7d0v32u+qgpDHI6O57qPTvfsPJ3d90KXfkZKa RMU2D0KtUfwFt2XB7zgDAAA= Archived-At: Subject: Re: [avtext] [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 08:47:10 -0000 --_000_p1px1ish5nl1046j6qqna8js1478076423072emailandroidcom_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable +1 I think this makes sense. Cheers, Bo -------- Originalmeddelande -------- Fr=E5n: Christer Holmberg Datum: 2016-11-01 15:18 (GMT+01:00) Till: Magnus Westerlund , IETF AVTCore WG <= avt@ietf.org>, avtext@ietf.org, ART ADs Rubrik: Re: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? Hi, I support the merger. Regards, Christer On 01/11/16 15:43, "avt on behalf of Magnus Westerlund" wrote: >AVTCORE, and AVTEXT, > >The WG chairs and ADs have had some discussion about if AVTCORE and >AVTEXT should be merged. The main reason is that the participant overlap >is large, and the amount of work currently in the two WGs are low enough >that a single WG would still not have a heavy load. Benefits of a merge >would be that fewer WG chairs would be needed, a single meeting slot >when we meet (which we anyway have been doing lately). We have not >discussed any changes to the scope of the charters. > >So what do you as participant think about this proposal? Please provide >your views and feedback. > >We have also scheduled time for discussing this at the end of the AVTEXT >followed by AVTCORE meeting slot in Seoul. > >This is to provide input to the ADs which is the ones that in the end >make the decision. > >Magnus Westerlund > >---------------------------------------------------------------------- >Services, Media and Network features, Ericsson Research EAB/TXM >---------------------------------------------------------------------- >Ericsson AB | Phone +46 10 7148287 >F=E4r=F6gatan 6 | Mobile +46 73 0949079 >SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com >---------------------------------------------------------------------- > >_______________________________________________ >Audio/Video Transport Core Maintenance >avt@ietf.org >https://www.ietf.org/mailman/listinfo/avt _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt --_000_p1px1ish5nl1046j6qqna8js1478076423072emailandroidcom_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
+1
I think this makes sense.
Cheers,
Bo


-------- Originalmeddelande --------
Fr=E5n: Christer Holmberg <christer.holmberg@ericsson.com>
Datum: 2016-11-01 15:18 (GMT+01:00)
Till: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF A= VTCore WG <avt@ietf.org>, avtext@ietf.org, ART ADs <art-ads@ietf.o= rg>
Rubrik: Re: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG?

Hi,

I support the merger.

Regards,

Christer


On 01/11/16 15:43, "avt on behalf of Magnus Westerlund"
<avt-bounces@ietf.org on behalf of magnus.westerlund@ericsson.com> wr= ote:

>AVTCORE, and AVTEXT,
>
>The WG chairs and ADs have had some discussion about if AVTCORE and
>AVTEXT should be merged. The main reason is that the participant overla= p
>is large, and the amount of work currently in the two WGs are low enoug= h
>that a single WG would still not have a heavy load. Benefits of a merge=
>would be that fewer WG chairs would be needed, a single meeting slot >when we meet (which we anyway have been doing lately). We have not
>discussed any changes to the scope of the charters.
>
>So what do you as participant think about this proposal? Please provide=
>your views and feedback.
>
>We have also scheduled time for discussing this at the end of the AVTEX= T
>followed by AVTCORE meeting slot in Seoul.
>
>This is to provide input to the ADs which is the ones that in the end >make the decision.
>
>Magnus Westerlund
>
>----------------------------------------------------------------------<= br> >Services, Media and Network features, Ericsson Research EAB/TXM
>----------------------------------------------------------------------<= br> >Ericsson AB          =        | Phone  +46 10 7148287
>F=E4r=F6gatan 6         &n= bsp;       | Mobile +46 73 0949079
>SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com >----------------------------------------------------------------------<= br> >
>_______________________________________________
>Audio/Video Transport Core Maintenance
>avt@ietf.org
>https://www.ietf.= org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/= mailman/listinfo/avt
 --_000_p1px1ish5nl1046j6qqna8js1478076423072emailandroidcom_-- From nobody Wed Nov 2 10:33:38 2016 Return-Path: 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 6F93B1296FC; Wed, 2 Nov 2016 10:33:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, 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 61dUn8S7SYOD; Wed, 2 Nov 2016 10:33:30 -0700 (PDT) Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::22e]) (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 5B5C21296FD; Wed, 2 Nov 2016 10:33:30 -0700 (PDT) Received: by mail-ua0-x22e.google.com with SMTP id 20so18768222uak.0; Wed, 02 Nov 2016 10:33:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eVd5njnRkkUm6ZQST3exHrJXNJVlVZg4L2nl21PdDQY=; b=jh8DL6Z86prsJ631vMwRa/U+FA++25Mkclr81OK4Wh/+Wp72aPphISs7rzQ4HaK+ee 97yjpIeebNb7Hda4TKmu1aJXb/DtHOYTIsMD0y/RAl7/WdAHo3oip3quA2PXw5qqBdnr iVo97Ozqvd8CfgSKDZOcJLvAAtbtp6vLD3IJQNuWWhvyRg//tV2YL440QqBcRHwfj60j g4WUH0VY89wYWzWvRuLVegV7/j/sXOCG8E4b7XQ44N+M3BTTC+521AQ8GhiiPPTcraUL hWow/pFawSHgxAwKBP9OvUP8hJ99uGLT/mXYdB8bLtKPITJKlfHulBWjYas7VyiUWp7P QwqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eVd5njnRkkUm6ZQST3exHrJXNJVlVZg4L2nl21PdDQY=; b=P8Xh3ENC+KwwjwzLFV8kI7wkP0xQpDeNiv9RHyJukM1YMcIBZGZJ0pb+l1d8fmc84J bveoJWW008sQKtUm7kwfk2j3HDaC6jVng1yxvSrvi6Hhz4ciJ7dONbMW/y34xKQT+ypH j42W85oOjXu5vAyXL+jabczN8aBiE+qFwOisZ+vXUjRag6sSZjKIq5yWN3XSyBfiCGv8 tyrFsw/7r0lZtOKZs0Gxsy7HwQ7MCwVBWIRdE7+/tBis5AiP7kTYfYmxzb/TT9YFcSwU 3p2NgauZ/hyIMSjkSVEph5PSaD2cY3Sz20NLA63z5DKpWFpskKY2YCZiILx9W+yU20lE CZvQ== X-Gm-Message-State: ABUngvdEvK08bWNM5FoEt7cB5eEsWct+3ZmZ89o+ZD8dYbG5P5aEUhsuV/sgPjP+6Z6wRubMiajEnsbe3bqSdg== X-Received: by 10.159.33.69 with SMTP id 63mr3393483uab.2.1478108009290; Wed, 02 Nov 2016 10:33:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.16.10 with HTTP; Wed, 2 Nov 2016 10:33:08 -0700 (PDT) In-Reply-To: References: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> From: Bernard Aboba Date: Wed, 2 Nov 2016 10:33:08 -0700 Message-ID: To: Bo Burman Content-Type: multipart/alternative; boundary=94eb2c0b70fed5617f054054d6f6 Archived-At: Cc: ART ADs , "avtext@ietf.org" , IETF AVTCore WG , Christer Holmberg Subject: Re: [avtext] [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2016 17:33:32 -0000 --94eb2c0b70fed5617f054054d6f6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I also think it makes sense. On Wed, Nov 2, 2016 at 1:47 AM, Bo Burman wrote: > +1 > I think this makes sense. > Cheers, > Bo > > > -------- Originalmeddelande -------- > Fr=C3=A5n: Christer Holmberg > Datum: 2016-11-01 15:18 (GMT+01:00) > Till: Magnus Westerlund , IETF AVTCore WG > , avtext@ietf.org, ART ADs > Rubrik: Re: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? > > Hi, > > I support the merger. > > Regards, > > Christer > > > On 01/11/16 15:43, "avt on behalf of Magnus Westerlund" > wrote: > > >AVTCORE, and AVTEXT, > > > >The WG chairs and ADs have had some discussion about if AVTCORE and > >AVTEXT should be merged. The main reason is that the participant overlap > >is large, and the amount of work currently in the two WGs are low enough > >that a single WG would still not have a heavy load. Benefits of a merge > >would be that fewer WG chairs would be needed, a single meeting slot > >when we meet (which we anyway have been doing lately). We have not > >discussed any changes to the scope of the charters. > > > >So what do you as participant think about this proposal? Please provide > >your views and feedback. > > > >We have also scheduled time for discussing this at the end of the AVTEXT > >followed by AVTCORE meeting slot in Seoul. > > > >This is to provide input to the ADs which is the ones that in the end > >make the decision. > > > >Magnus Westerlund > > > >---------------------------------------------------------------------- > >Services, Media and Network features, Ericsson Research EAB/TXM > >---------------------------------------------------------------------- > >Ericsson AB | Phone +46 10 7148287 > >F=C3=A4r=C3=B6gatan 6 | Mobile +46 73 0949079 > >SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > >---------------------------------------------------------------------- > > > >_______________________________________________ > >Audio/Video Transport Core Maintenance > >avt@ietf.org > >https://www.ietf.org/mailman/listinfo/avt > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext > > --94eb2c0b70fed5617f054054d6f6 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I also think it makes sense.=C2=A0

On Wed, Nov 2, 2016 at 1:47 AM, Bo = Burman <bo.burman@ericsson.com> wrote:
+1
I think this makes sense.
Cheers,
Bo


-------- Originalmeddelande --------
Fr=C3=A5n: Christer Holmberg <christer.holmberg@ericsson.com> =
Datum: 2016-11-01 15:18 (GMT+01:00)
Till: Magnus Westerlund <magnus.westerlund@ericsson.com>, IETF= AVTCore WG <avt@ietf.= org>, avtext@ie= tf.org, ART ADs <art-ads@ietf.org>
Rubrik: Re: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG?

Hi,

I support the merger.

Regards,

Christer


On 01/11/16 15:43, "avt on behalf of Magnus Westerlund"
<avt-bounces@i= etf.org on behalf of magnus.westerlund@ericsson.com> wrote:

>AVTCORE, and AVTEXT,
>
>The WG chairs and ADs have had some discussion about if AVTCORE and
>AVTEXT should be merged. The main reason is that the participant overla= p
>is large, and the amount of work currently in the two WGs are low enoug= h
>that a single WG would still not have a heavy load. Benefits of a merge=
>would be that fewer WG chairs would be needed, a single meeting slot >when we meet (which we anyway have been doing lately). We have not
>discussed any changes to the scope of the charters.
>
>So what do you as participant think about this proposal? Please provide=
>your views and feedback.
>
>We have also scheduled time for discussing this at the end of the AVTEX= T
>followed by AVTCORE meeting slot in Seoul.
>
>This is to provide input to the ADs which is the ones that in the end >make the decision.
>
>Magnus Westerlund
>
>-------------------------------------------------------------= ---------
>Services, Media and Network features, Ericsson Research EAB/TXM
>-------------------------------------------------------------= ---------
>Ericsson AB=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | Phone=C2=A0 +46 10 7148287 >F=C3=A4r=C3=B6gatan 6=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | Mobile +46 73 0949079=
>SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>-------------------------------------------------------------= ---------
>
>_______________________________________________
>Audio/Video Transport Core Maintenance
>avt@ietf.org
>https://www.ietf.org/mailman/listinfo/avt

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
htt= ps://www.ietf.org/mailman/listinfo/avt

_______________________________________________
avtext mailing list
avtext@ietf.org
https://www.ietf.org/mailman/listinfo/avtext

--94eb2c0b70fed5617f054054d6f6-- From nobody Thu Nov 3 05:58:27 2016 Return-Path: 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 EE3B5129531; Thu, 3 Nov 2016 05:58:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.018 X-Spam-Level: X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 LAnt91NInDBH; Thu, 3 Nov 2016 05:58:24 -0700 (PDT) Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 857151294E9; Thu, 3 Nov 2016 05:58:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1817; q=dns/txt; s=iport; t=1478177904; x=1479387504; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=KKNO/aZhZAhQhWuK9LgoeXiPuanoZ2m/6gouCef/620=; b=am4EMZVXA8c/cQoDd5OF07Mkbuqd9zc/B+jZsfsJC0fevDwFNGLAO6fj 1FIFQ7tqfApwHwvwaUk+nNzrm6EmgOkH6A/TGrTWCO6zJPXNXzED4qZEt 2/MTnj3HHsig0ev+HQwJ0GwgHkXs3ispqzMGC5c6g8Jr6iWhOFEEMde2p c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DQAgCyMxtY/4QNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzABAQEBAR9YfAekL5RHgggdC4V6AoIlQRIBAgEBAQEBAQFiKIR?= =?us-ascii?q?hAQEBBAEBAQl5AgICAQgRAwECKAcbDAsUCQgCBAESiFYOuncBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBGQUFhjqEVYonBYhJhkOFNoVeAZA8gW6Eb4ktjR2EAwElDSNrhR9?= =?us-ascii?q?yhm6BDAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,438,1473120000"; d="scan'208";a="342923486" Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Nov 2016 12:58:23 +0000 Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id uA3CwNnZ000390 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 3 Nov 2016 12:58:23 GMT Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 3 Nov 2016 07:58:22 -0500 Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1210.000; Thu, 3 Nov 2016 07:58:22 -0500 From: "Mo Zanaty (mzanaty)" To: Magnus Westerlund , IETF AVTCore WG , "avtext@ietf.org" , ART ADs Thread-Topic: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? Thread-Index: AQHSNdH1w8vLuzaQlEOicz2/MdKkCw== Date: Thu, 3 Nov 2016 12:58:22 +0000 Message-ID: References: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> In-Reply-To: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.9.160926 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.179.122] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Subject: Re: [avtext] [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 12:58:26 -0000 I support this. Mo -----Original Message----- From: avt on behalf of 'Magnus Westerlund' Date: Tuesday, November 1, 2016 at 9:43 AM To: "avt@ietf.org" , "avtext@ietf.org" , ART ADs Subject: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? AVTCORE, and AVTEXT, The WG chairs and ADs have had some discussion about if AVTCORE and AVTEXT should be merged. The main reason is that the participant overlap is large, and the amount of work currently in the two WGs are low enough that a single WG would still not have a heavy load. Benefits of a merge would be that fewer WG chairs would be needed, a single meeting slot when we meet (which we anyway have been doing lately). We have not discussed any changes to the scope of the charters. So what do you as participant think about this proposal? Please provide your views and feedback. We have also scheduled time for discussing this at the end of the AVTEXT followed by AVTCORE meeting slot in Seoul. This is to provide input to the ADs which is the ones that in the end make the decision. Magnus Westerlund ---------------------------------------------------------------------- Services, Media and Network features, Ericsson Research EAB/TXM ---------------------------------------------------------------------- Ericsson AB | Phone +46 10 7148287 F=E4r=F6gatan 6 | Mobile +46 73 0949079 SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com ---------------------------------------------------------------------- _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt From nobody Thu Nov 3 06:41:28 2016 Return-Path: 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 4A2DC1299E4; Thu, 3 Nov 2016 06:41:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -16.018 X-Spam-Level: X-Spam-Status: No, score=-16.018 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Oh_D5A8LqwwG; Thu, 3 Nov 2016 06:41:22 -0700 (PDT) Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC3E3129A06; Thu, 3 Nov 2016 06:40:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2984; q=dns/txt; s=iport; t=1478180416; x=1479390016; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ckWQMI4QBdw6QE1LS3LRFyG4o7VinVLS+H1KzVN5C68=; b=hEFm+Os507yGBPLq2lwKz0IkgGDCoqR+9VA2IELOeoY5K4rf7tvpTsH2 HxpJ6KNmxh3vv7iMof/qEY05F7qznRIo1vdSWp/lPuKUZUrC9Dz54t2zY OqoJZS/MJjHuFKIatnRFtHHmrJeeY4hvCCBGwDLGbR/YUF2eKOQuDCZDc A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAQCiPRtY/4wNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzABAQEBAR9YfAeNMJcAlEeCCB0LhTBKAoImPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRhAQEBBAEBATc0CwwEAgEIEQMBAh8QJwsdCAIEAQ0FiFYOun4BAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEchj+EVYE8iGsFiEGHTYoSAYYzigmBbk6EIYkthyeFdoQ?= =?us-ascii?q?DAR43a4MzgWxyhm6BDAEBAQ?= X-IronPort-AV: E=Sophos;i="5.31,438,1473120000"; d="scan'208";a="343798338" Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Nov 2016 13:40:16 +0000 Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id uA3DeFN7030253 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 3 Nov 2016 13:40:16 GMT Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 3 Nov 2016 08:40:15 -0500 Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1210.000; Thu, 3 Nov 2016 08:40:15 -0500 From: "Mo Zanaty (mzanaty)" To: "internet-drafts@ietf.org" , "i-d-announce@ietf.org" Thread-Topic: [avtext] I-D Action: draft-ietf-avtext-framemarking-03.txt Thread-Index: AQHSNdfO9qqEUGY9EEWRj2ERUJbHxw== Date: Thu, 3 Nov 2016 13:40:15 +0000 Message-ID: References: <147795046651.23193.2070361815432103504.idtracker@ietfa.amsl.com> In-Reply-To: <147795046651.23193.2070361815432103504.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.9.160926 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.82.179.122] Content-Type: text/plain; charset="us-ascii" Content-ID: <44E0AAA140983A43802720411BA705B8@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: "avtext@ietf.org" Subject: Re: [avtext] I-D Action: draft-ietf-avtext-framemarking-03.txt X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 13:41:26 -0000 This update incorporates feedback and decisions from Berlin, along with editorial changes. 1. A shorter variant of the extension is defined for non-scalable streams which omits all fields that only apply to scalable streams. 2. References to the relevant codec payload formats were added to the Layer ID Mapping sections. 3. References to drafts were updated to RFCs. Except draft-aboba-avtcore-sfu-rtp which expired. We need to decide whether to remove this reference, keep it and progress that draft, or merge relevant content from that draft into this document. I would like to hear from Bernard and others on this. Note Well: An IPR declaration (ID#2876) was recently submitted on this WG document. The authors see no issues continuing to progress this draft given the permissive licensing terms, but the WG needs to weigh in. https://datatracker.ietf.org/ipr/2876/ Thanks, Mo -----Original Message----- From: avtext on behalf of "internet-drafts@ietf.org" Date: Monday, October 31, 2016 at 5:47 PM To: "i-d-announce@ietf.org" Cc: "avtext@ietf.org" Subject: [avtext] I-D Action: draft-ietf-avtext-framemarking-03.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Extensions of the IETF. Title : Frame Marking RTP Header Extension Authors : Espen Berger Suhas Nandakumar Mo Zanaty Filename : draft-ietf-avtext-framemarking-03.txt Pages : 10 Date : 2016-10-31 Abstract: This document describes a Frame Marking RTP header extension used to convey information about video frames that is critical for error recovery and packet forwarding in RTP middleboxes or network nodes. It is most useful when media is encrypted, and essential when the middlebox or node has no access to the media encryption keys. It is also useful for codec-agnostic processing of encrypted or unencrypted media, while it also supports extensions for codec-specific information. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtext-framemarking/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-avtext-framemarking-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtext-framemarking-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ avtext mailing list avtext@ietf.org https://www.ietf.org/mailman/listinfo/avtext From nobody Thu Nov 3 07:10:31 2016 Return-Path: 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 8BE251299E6 for ; Thu, 3 Nov 2016 07:10:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=networked-media.20150623.gappssmtp.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 TPccNbxHesKm for ; Thu, 3 Nov 2016 07:10:27 -0700 (PDT) Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (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 9AB9D129A2B for ; Thu, 3 Nov 2016 07:10:24 -0700 (PDT) Received: by mail-lf0-x22e.google.com with SMTP id t196so39494020lff.3 for ; Thu, 03 Nov 2016 07:10:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networked-media.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TQDZDn3WpJC4r5klhe2ghvTUasR19C0A0DG5jQY3Y64=; b=emcoQL2UqEPpweUI/Uc4cj1r9sOg/UDzdt3W3wHqFpkzTJ6KmrO23/kov0dLoNQFua hRYffh59zwjXb4qP66MA45fUUYcqN1bAdcA6G+v5KKHzv1w0l4iDcIO+Lcw/kKD4KIpM X5BtjrmlhoFNN9Zcr+bR6ZdAOyT4Oxq0wsgHZ4ohVv3jHj0PnvvUH/qAB2ECmqMQbDez 4LLEFsr5/onCoIKBtlnZecs0NCTo6DYHolb6U+xSgyVPOpZ/3D7toN+dJ8wa0Py2NoO3 bCNeGlWOMZohS35XLOJ2KZ22X5pasNghWoT93RsLdQCWo48n4aTx/JUTr6e4DCL0RRhs 5i1w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TQDZDn3WpJC4r5klhe2ghvTUasR19C0A0DG5jQY3Y64=; b=HaBzC9zr6yu/ZZO9sNDjmKeJVbTAiUNZuGTw83SP7yJmYtJnfItIZXvjHLJnttgvja M5n8O7gLZGYXqIvZ5LapqsSwgIoIUAqXcvMP3s2wwqQxbdMw8qMZj/jsh0P2o6boK/QZ YB8fyE12sOHIAcqbmYBPygScTsy/D48LN1mnvIXYwNrkOkuLPes7xbAt1RN/CH6fOgzn E7TbVzxgaXAcb2hCqHuvdVNi/Z7XWfhW86nSR4mBsCQ5tk7mKTgEtBhZzTZYI6bg/byj 3cRVwuRnKYy0oI5SnJzSjwGtaw/B5JbrV5tn9241g9e9ajWIOJ9rxJWRMk0b6EaSTaHh 5hzA== X-Gm-Message-State: ABUngveu344w0xHB/bMxLVfIsG5lwE4FSiBcUIH9lAJE/SV3Q4S6UWe/tdYHFmNnbSJ7Y3N47uwLtNMRvfXTRQ== X-Received: by 10.25.23.228 with SMTP id 97mr4766860lfx.167.1478182222675; Thu, 03 Nov 2016 07:10:22 -0700 (PDT) MIME-Version: 1.0 Received: by 10.114.1.198 with HTTP; Thu, 3 Nov 2016 07:10:22 -0700 (PDT) In-Reply-To: References: <99fb874c-cae7-e194-cf96-05f588a5c255@ericsson.com> From: "Ali C. Begen" Date: Thu, 3 Nov 2016 17:10:22 +0300 Message-ID: To: "Mo Zanaty (mzanaty)" Content-Type: multipart/alternative; boundary=001a114101704bd4c20540661e51 Archived-At: Cc: ART ADs , "avtext@ietf.org" , IETF AVTCore WG Subject: Re: [avtext] [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2016 14:10:29 -0000 --001a114101704bd4c20540661e51 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1. On Thu, Nov 3, 2016 at 3:58 PM, Mo Zanaty (mzanaty) wrote: > I support this. > > Mo > > -----Original Message----- > From: avt on behalf of 'Magnus Westerlund' > > Date: Tuesday, November 1, 2016 at 9:43 AM > To: "avt@ietf.org" , "avtext@ietf.org" , > ART ADs > Subject: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG? > > AVTCORE, and AVTEXT, > > The WG chairs and ADs have had some discussion about if AVTCORE and > AVTEXT should be merged. The main reason is that the participant overlap > is large, and the amount of work currently in the two WGs are low enough > that a single WG would still not have a heavy load. Benefits of a merge > would be that fewer WG chairs would be needed, a single meeting slot > when we meet (which we anyway have been doing lately). We have not > discussed any changes to the scope of the charters. > > So what do you as participant think about this proposal? Please provide > your views and feedback. > > We have also scheduled time for discussing this at the end of the AVTEXT > followed by AVTCORE meeting slot in Seoul. > > This is to provide input to the ADs which is the ones that in the end > make the decision. > > Magnus Westerlund > > ---------------------------------------------------------------------- > Services, Media and Network features, Ericsson Research EAB/TXM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > F=C3=A4r=C3=B6gatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > > _______________________________________________ > Audio/Video Transport Core Maintenance > avt@ietf.org > https://www.ietf.org/mailman/listinfo/avt > > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext > --001a114101704bd4c20540661e51 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
+1.

On Thu, Nov 3, 2016 at 3:58 PM, Mo Zanaty (mzanaty) <mzanaty@cisc= o.com> wrote:
I support thi= s.

Mo

-----Original Message-----
From: avt <avt-bounces@ietf.org<= /a>> on behalf of 'Magnus Westerlund'
<magnus.westerlund@eri= csson.com>
Date: Tuesday, November 1, 2016 at 9:43 AM
To: "avt@ietf.org" <avt@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>,
ART ADs <art-ads@ietf.org> Subject: [AVTCORE] Merging AVTCORE and AVTEXT into a single WG?

AVTCORE, and AVTEXT,

The WG chairs and ADs have had some discussion about if AVTCORE and
AVTEXT should be merged. The main reason is that the participant overlap is large, and the amount of work currently in the two WGs are low enough that a single WG would still not have a heavy load. Benefits of a merge
would be that fewer WG chairs would be needed, a single meeting slot
when we meet (which we anyway have been doing lately). We have not
discussed any changes to the scope of the charters.

So what do you as participant think about this proposal? Please provide
your views and feedback.

We have also scheduled time for discussing this at the end of the AVTEXT followed by AVTCORE meeting slot in Seoul.

This is to provide input to the ADs which is the ones that in the end
make the decision.

Magnus Westerlund

-----------------------------------------------------------------= -----
Services, Media and Network features, Ericsson Research EAB/TXM
-----------------------------------------------------------------= -----
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| = Phone=C2=A0 +46= 10 7148287
F=C3=A4r=C3=B6gatan 6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0| Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
-----------------------------------------------------------------= -----

_______________________________________________
Audio/Video Transport Core Maintenance
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

_______________________= ________________________
avtext mailing list
avtext@ietf.org
https://www.ietf.org/mailman/listinfo/avtext

--001a114101704bd4c20540661e51-- From nobody Thu Nov 10 06:18:59 2016 Return-Path: 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 088B812950C; Thu, 10 Nov 2016 06:18:58 -0800 (PST) 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 Fth8xCk4_jbo; Thu, 10 Nov 2016 06:18:55 -0800 (PST) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 62E121296AC; Thu, 10 Nov 2016 06:18:52 -0800 (PST) Received: by mail-wm0-x236.google.com with SMTP id c184so52992021wmd.0; Thu, 10 Nov 2016 06:18:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5rWsDzhyfhf2rwSxRC4O3TYyC0whgcNH5xQ3fsfxeCs=; b=jWoO0P+U0OcwDpARENCjSBLAl7khRzdt2WLur15f+pUp8T5VDjxKY59tw6lEUUQZDm 7x/r6lJnWSdizUoWcC4PtD7PLbnp0hgqYn7YeF/4QgMM9762Nmb86tZafZT9M7vIV0zK YnBGZT365wW2LTOw4KtaF6QU03LtfC4mhwgt1DK6L58NUyoXP481QGVw/Uhm98vudKzI S4Cs+6OPJqJUqjmsyMdn+W+gvvFED3Z6wwT/tVTJy8fJK52E9RywAW22VLlH8ZytfJpS 4NO/vlk7fCcsJUDJCQR2vGHPY2sWPGlK5XxlN28okU/idNEYxM24Ywl7XjH1h6LgZNqz I2xw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5rWsDzhyfhf2rwSxRC4O3TYyC0whgcNH5xQ3fsfxeCs=; b=FZOA8gZKsHQgg08GgcX8EE2D/RXBle9WrfOL84Xj3qWbDkn+edWC6wTxbd7Aljie4d d4os32tQolWU2RC5h/9nlbkS1uZBbE+fY8AodOi+9TLBBqgsFxw1SaNsbviOZI6c7UzU +0aBIaO/JQTHKD5Jj7bA9Lho0mz0Hd6byDVkBDBatBM0A6ROeyEBia0J0vyB6FXTIiDE FsHOaRmxMIIHF7jrfWqvz+2AGmT50Rcuju0HkWPPf8rQeTgs1vaDuzF/BpZ2G0kxt2SG 8wG7C55SSunzEn5DO8Qp27fwIiTqrLTsnPbBytE7hl+AcvX1fsJPjOCGb+wCQUynSdM4 wZ3g== X-Gm-Message-State: ABUngvcBB5mF+xeZm8rsAGOmu2rsYqsgsEymN+CtwVC15/L6fA/OMwYpFBWcfnNfyyPNr6aXiELUoQmiACREvQ== X-Received: by 10.28.134.74 with SMTP id i71mr25468496wmd.100.1478787530850; Thu, 10 Nov 2016 06:18:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.194.175.198 with HTTP; Thu, 10 Nov 2016 06:18:50 -0800 (PST) In-Reply-To: References: From: =?UTF-8?Q?Miguel_Par=C3=ADs_D=C3=ADaz?= Date: Thu, 10 Nov 2016 15:18:50 +0100 Message-ID: To: Jonathan Lennox Content-Type: multipart/alternative; boundary=001a11442c02798e3b0540f30dcd Archived-At: Cc: "avtext@ietf.org" , mmusic Subject: Re: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2016 14:18:58 -0000 --001a11442c02798e3b0540f30dcd Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, 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 ]. 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. Best!! Refs [1] https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-06#section-7.2 [2] https://tools.ietf.org/html/draft-ietf-mmusic-sdp-simulcast-06#section-7.2.= 1 2016-08-30 12:37 GMT+02:00 Miguel Par=C3=ADs D=C3=ADaz : > 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 =E2=80=94 it nee= ds the SDP. >> >> Note that if the media distributor doesn=E2=80=99t have information from= the SDP >> it can=E2=80=99t reliably identify the frame marking header extension at= all, since >> header extension IDs are negotiated. So I=E2=80=99m not sure how much be= nefit 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, o= r >> the like), it might be useful for encoders to be able to indicate the >> current size they=E2=80=99re encoding without needing to send updated SD= P all the >> time. >> >> On Aug 26, 2016, at 12:52 PM, Paul E. Jones >> wrote: >> >> Miguel, >> >> 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 persona= lly >> 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 vi= deo >> resolutions if simulcast is employed. >> >> Paul >> >> ------ Original Message ------ >> From: "Miguel Par=C3=ADs D=C3=ADaz" >> To: avtext@ietf.org >> Sent: 8/25/2016 10:12:48 AM >> Subject: [avtext] framemarking: add frame size info >> >> 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 th= e >> experience of the users. >> Application developers don't usually have deep knowledge about media lik= e >> 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"=C2=B7 screen, a PC with 27" screen, etc. >> >> In this way and taking a videoconference app as example, if a participan= t >> select another participant to be rendered as main video, the app could a= sk >> 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=C3=ADs D=C3=ADaz >> ------------------------------------------------------------------------ >> Computer/Software engineer. >> Researcher and architect in http://www.kurento.org >> http://twitter.com/mparisdiaz >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> avtext mailing list >> avtext@ietf.org >> https://www.ietf.org/mailman/listinfo/avtext >> >> >> > > > -- > Miguel Par=C3=ADs D=C3=ADaz > ------------------------------------------------------------------------ > Computer/Software engineer. > Researcher and architect in http://www.kurento.org > http://twitter.com/mparisdiaz > ------------------------------------------------------------------------ > --=20 Miguel Par=C3=ADs D=C3=ADaz ------------------------------------------------------------------------ Computer/Software engineer. Researcher and architect in http://www.kurento.org http://twitter.com/mparisdiaz ------------------------------------------------------------------------ --001a11442c02798e3b0540f30dcd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hello,
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.

Specif= ically, In the Media-Switching Mixer section [2] the same thoughts I expose= d are said:
   This section discusses the b=
ehavior in cases where the RTP middlebox
   behaves like the Media-Switching Mixer (Section 3.6.2)=
 in RTP
   Topologies [RFC7667].  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 de= pay 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=20 Frame Marking RTP header extension is quite interesting to implement=20 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 s= ide).

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

Best!!


2016-08-30 12:37 GM= T+02:00 Miguel Par=C3=ADs D=C3=ADaz <mparisdiaz@gmail.com>:
I assume that the med= ia distributor has the information from the SDP (it performs the SDP negoti= ation which each "client"), but the point is that encoders may ch= ange the video size depending on the available bandwidth, the complexivity = of the video source, etc., unless the sender forces the encoders' confi= guration with a fix frame size...


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

In the latest version of simulcast the media distributor would need th= e RID values, not the PT values, but the idea is the same =E2=80=94 it need= s the SDP.

Note that if the media distributor doesn=E2=80=99t have information fr= om the SDP it can=E2=80=99t reliably identify the frame marking header exte= nsion at all, since header extension IDs are negotiated. So I=E2=80=99m 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 frequentl= y 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 curr= ent size they=E2=80=99re encoding without needing to send updated SDP all the time.

On Aug 26, 2016, at 12:52 PM, Paul E. Jones <paulej@packetizer.com> wrote:
Miguel,

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

Paul

------ Original Message ------
From: "Miguel Par=C3=ADs D=C3=ADaz" <mparisdiaz@gmail.com>
Sent: 8/25/2016 10:12:48 AM
Subject: [avtext] framemarking: add frame size info

Hello,
it would be great having frame size (width and height) info in the Fra= me Marking RTP header extension [1].

Why?
For example, in the case of using simulcast in an SFU, selecting the s= tream by the size would ease the application development and improve the ex= perience of the users.
Application developers don't usually have deep knowledge about med= ia 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"=C2=B7 screen, a PC with 27" screen, etc.

In this way and taking a videoconference app as example, if a particip= ant 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]=C2=A0https://tools.ietf.org/html/dra= ft-ietf-avtext-framemarking-02

--=C2=A0
Miguel Par=C3=ADs D=C3=ADaz
-----------------------------------------------------------------= -------
Computer/Software engineer.
Researcher and architect in=C2=A0http://www.kurento.org
http://twitter.= com/mparisdiaz
-----------------------------------------------------------------= -------
_______________________________________________<= /span>
avtext mailing list
avtext@ietf.org
https://www.ietf.org/mailman/listinfo/avtext




--
Miguel Par=C3=ADs D=C3=ADaz
------------------------------= ------------------------------------------
Computer/Software engine= er.
Researcher and architect in http://www.kurento.org
http://twitter.com/mparisdiaz
----------= --------------------------------------------------------------



--
Mi= guel Par=C3=ADs D=C3=ADaz
----------------------------------------------= --------------------------
Computer/Software engineer.
Researcher and= architect in http://w= ww.kurento.org
http://twitter.com/mparisdiaz
-------------------------------= -----------------------------------------
--001a11442c02798e3b0540f30dcd-- From nobody Wed Nov 16 16:41:13 2016 Return-Path: X-Original-To: avtext@ietf.org Delivered-To: avtext@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1890C12960D; Wed, 16 Nov 2016 16:40:58 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.37.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147934325809.14856.2781524455193348767.idtracker@ietfa.amsl.com> Date: Wed, 16 Nov 2016 16:40:58 -0800 Archived-At: Cc: avtext@ietf.org Subject: [avtext] I-D Action: draft-ietf-avtext-avpf-ccm-layered-03.txt X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 00:40:58 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Extensions of the IETF. Title : Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs Authors : Stephan Wenger Jonathan Lennox Bo Burman Magnus Westerlund Filename : draft-ietf-avtext-avpf-ccm-layered-03.txt Pages : 11 Date : 2016-11-16 Abstract: This document updates RFC5104 by fixing a shortcoming in the specification language of the Codec Control Message Full Intra Request (FIR) as defined in RFC5104 when using it with layered codecs. In particular, a Decoder Refresh Point needs to be sent by a media sender when a FIR is received on any layer of the layered bitstream, regardless on whether those layers are being sent in a single or in multiple RTP flows. The other payload-specific feedback messages defined in RFC 5104 and RFC 4585 as updated by RFC 5506 have also been analyzed, and no corresponding shortcomings have been found. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtext-avpf-ccm-layered/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-avtext-avpf-ccm-layered-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-avtext-avpf-ccm-layered-03 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Wed Nov 16 16:44:24 2016 Return-Path: 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 74E43129417 for ; Wed, 16 Nov 2016 16:44:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.903 X-Spam-Level: X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steweorg.onmicrosoft.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 JtJ7Tl-Fitk5 for ; Wed, 16 Nov 2016 16:44:20 -0800 (PST) Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0110.outbound.protection.outlook.com [104.47.33.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F52612951B for ; Wed, 16 Nov 2016 16:44:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=steweorg.onmicrosoft.com; s=selector1-stewe-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=a6oZ0NUsHA4BllOrSDyewwo2+Tjgtse97H1jswXLv7o=; b=FpliwQ9jn7/cnmRKngMkAf5dAvlUbXkHfvYz8O4D1S40KEjUy5y3Yib9IbUQ7QI/JW47nddXkvsjFwiooo8fT1tNq5Ij/P/h8gnf+MHga579LWVnRAMPgcw3txWmzIobbfT3tjMnOp0Ij/9RIx/0np14w/fXoUe70pb4feDgvMY= Received: from BL2PR17MB0771.namprd17.prod.outlook.com (10.167.118.143) by BL2PR17MB0772.namprd17.prod.outlook.com (10.167.118.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.721.10; Thu, 17 Nov 2016 00:44:16 +0000 Received: from BL2PR17MB0771.namprd17.prod.outlook.com ([10.167.118.143]) by BL2PR17MB0771.namprd17.prod.outlook.com ([10.167.118.143]) with mapi id 15.01.0721.015; Thu, 17 Nov 2016 00:44:16 +0000 From: Stephan Wenger To: "avtext@ietf.org" Thread-Topic: New Version Notification for draft-ietf-avtext-avpf-ccm-layered-03.txt Thread-Index: AQHSQGtF5EBEqNe+UECTg6z5Hro2L6Db0H6A Date: Thu, 17 Nov 2016 00:44:15 +0000 Message-ID: <3EB24DA6-C7C6-417F-8E81-1E8C90B9751B@stewe.org> References: <147934325832.14856.11026143836940953545.idtracker@ietfa.amsl.com> In-Reply-To: <147934325832.14856.11026143836940953545.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=stewe@stewe.org; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [31.133.142.127] x-microsoft-exchange-diagnostics: 1; BL2PR17MB0772; 7:trFu6UrMXd1fJ47KFnDxQr4qS8SRiiZP5N/tlEMr+FICMpfvDoBGafF1glQHA9iIr2LoOCAx9H6fCm49AYPNo8VPtqzd96hE/96bnDwyrMmbM6gl/VBH5F1fmA9Ez+TvnR2Ezu5S0lxI1+cvavNFL+m1/MNUF9e76LfTveIPIP9ozcRouZy0zQrNjeJRA/BgQt3rmfmpI9hRmXZ9XShgvbZulebpUgSjqRn2+PoAXwlB3CE/51VAT1yEirCiT5QoYHkradi8lAIfDyEQGgNw3tQtuG8vDwSUqJNdihloThLrSeuCulVWVYrZW/FhP2K/7AkhWA9lEXhNX5012Iarq/9VwkYVWO9/zUm3r2/IOe8= x-ms-office365-filtering-correlation-id: 956d205a-3779-47b7-050c-08d40e82dbeb x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:BL2PR17MB0772; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(120809045254105); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6060326)(6040281)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041223)(6061324)(6043046); SRVR:BL2PR17MB0772; BCL:0; PCL:0; RULEID:; SRVR:BL2PR17MB0772; x-forefront-prvs: 01294F875B x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(7916002)(2473002)(24454002)(199003)(377424004)(189002)(83716003)(3846002)(5660300001)(106356001)(8936002)(230783001)(229853002)(102836003)(86362001)(450100001)(81166006)(6116002)(97736004)(87936001)(122556002)(92566002)(77096005)(7846002)(305945005)(7736002)(82746002)(33656002)(2501003)(3280700002)(2900100001)(76176999)(36756003)(54356999)(6916009)(2950100002)(66066001)(50986999)(4001150100001)(110136003)(8676002)(3660700001)(1730700003)(81156014)(68736007)(101416001)(5640700001)(6506003)(107886002)(189998001)(6512003)(99286002)(2906002)(15650500001)(106116001)(2351001)(105586002)(104396002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BL2PR17MB0772; H:BL2PR17MB0771.namprd17.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; received-spf: None (protection.outlook.com: stewe.org does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <8DF29674C9D7D24D9A5B581A63A32AB7@namprd17.prod.outlook.com> Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-OriginatorOrg: stewe.org X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Nov 2016 00:44:15.9778 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 865fc51c-5fae-4322-98ef-0121a85df0b6 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL2PR17MB0772 Archived-At: Subject: [avtext] FW: New Version Notification for draft-ietf-avtext-avpf-ccm-layered-03.txt X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 00:44:22 -0000 QXMgYW5ub3VuY2VkIGluIFNlb3VsLCB0aGUgMDMgdmVyc2lvbiBpcyBub3cgcG9zdGVkLCBhZGRy ZXNzaW5nIEJlbuKAmXMgcmV2aWV3Lg0KU3RlcGhhbg0KDQoNCg0KT24gMTEvMTcvMTYsIDA5OjQw LCAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiA8aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPiB3 cm90ZToNCg0KPg0KPkEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1pZXRmLWF2dGV4dC1hdnBm LWNjbS1sYXllcmVkLTAzLnR4dA0KPmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkg U3RlcGhhbiBXZW5nZXIgYW5kIHBvc3RlZCB0byB0aGUNCj5JRVRGIHJlcG9zaXRvcnkuDQo+DQo+ TmFtZToJCWRyYWZ0LWlldGYtYXZ0ZXh0LWF2cGYtY2NtLWxheWVyZWQNCj5SZXZpc2lvbjoJMDMN Cj5UaXRsZToJCVVzaW5nIENvZGVjIENvbnRyb2wgTWVzc2FnZXMgaW4gdGhlIFJUUCBBdWRpby1W aXN1YWwgUHJvZmlsZSB3aXRoIEZlZWRiYWNrIHdpdGggTGF5ZXJlZCBDb2RlY3MNCj5Eb2N1bWVu dCBkYXRlOgkyMDE2LTExLTE3DQo+R3JvdXA6CQlhdnRleHQNCj5QYWdlczoJCTExDQo+VVJMOiAg ICAgICAgICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRm LWF2dGV4dC1hdnBmLWNjbS1sYXllcmVkLTAzLnR4dA0KPlN0YXR1czogICAgICAgICBodHRwczov L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWF2dGV4dC1hdnBmLWNjbS1sYXll cmVkLw0KPkh0bWxpemVkOiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt aWV0Zi1hdnRleHQtYXZwZi1jY20tbGF5ZXJlZC0wMw0KPkRpZmY6ICAgICAgICAgICBodHRwczov L3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaWV0Zi1hdnRleHQtYXZwZi1jY20tbGF5 ZXJlZC0wMw0KPg0KPkFic3RyYWN0Og0KPiAgIFRoaXMgZG9jdW1lbnQgdXBkYXRlcyBSRkM1MTA0 IGJ5IGZpeGluZyBhIHNob3J0Y29taW5nIGluIHRoZQ0KPiAgIHNwZWNpZmljYXRpb24gbGFuZ3Vh Z2Ugb2YgdGhlIENvZGVjIENvbnRyb2wgTWVzc2FnZSBGdWxsIEludHJhDQo+ICAgUmVxdWVzdCAo RklSKSBhcyBkZWZpbmVkIGluIFJGQzUxMDQgd2hlbiB1c2luZyBpdCB3aXRoIGxheWVyZWQNCj4g ICBjb2RlY3MuICBJbiBwYXJ0aWN1bGFyLCBhIERlY29kZXIgUmVmcmVzaCBQb2ludCBuZWVkcyB0 byBiZSBzZW50IGJ5IGENCj4gICBtZWRpYSBzZW5kZXIgd2hlbiBhIEZJUiBpcyByZWNlaXZlZCBv biBhbnkgbGF5ZXIgb2YgdGhlIGxheWVyZWQNCj4gICBiaXRzdHJlYW0sIHJlZ2FyZGxlc3Mgb24g d2hldGhlciB0aG9zZSBsYXllcnMgYXJlIGJlaW5nIHNlbnQgaW4gYQ0KPiAgIHNpbmdsZSBvciBp biBtdWx0aXBsZSBSVFAgZmxvd3MuICBUaGUgb3RoZXIgcGF5bG9hZC1zcGVjaWZpYyBmZWVkYmFj aw0KPiAgIG1lc3NhZ2VzIGRlZmluZWQgaW4gUkZDIDUxMDQgYW5kIFJGQyA0NTg1IGFzIHVwZGF0 ZWQgYnkgUkZDIDU1MDYgaGF2ZQ0KPiAgIGFsc28gYmVlbiBhbmFseXplZCwgYW5kIG5vIGNvcnJl c3BvbmRpbmcgc2hvcnRjb21pbmdzIGhhdmUgYmVlbg0KPiAgIGZvdW5kLg0KPg0KPiAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICANCj4NCj4NCj5QbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEg Y291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQo+dW50aWwgdGhl IGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9y Zy4NCj4NCj5UaGUgSUVURiBTZWNyZXRhcmlhdA0KPg0K From nobody Thu Nov 17 18:17:24 2016 Return-Path: X-Original-To: avtext@ietf.org Delivered-To: avtext@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 63D17128E18; Thu, 17 Nov 2016 18:17:22 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.38.1 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <147943544237.1655.15908068998757310618.idtracker@ietfa.amsl.com> Date: Thu, 17 Nov 2016 18:17:22 -0800 Archived-At: Cc: draft-ietf-avtext-avpf-ccm-layered@ietf.org, avtext@ietf.org, avtext-chairs@ietf.org Subject: [avtext] Last Call: (Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs) to Proposed Standard X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Reply-To: ietf@ietf.org List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 02:17:22 -0000 The IESG has received a request from the Audio/Video Transport Extensions WG (avtext) to consider the following document: - 'Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs' as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2016-12-14. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document updates RFC5104 by fixing a shortcoming in the specification language of the Codec Control Message Full Intra Request (FIR) as defined in RFC5104 when using it with layered codecs. In particular, a Decoder Refresh Point needs to be sent by a media sender when a FIR is received on any layer of the layered bitstream, regardless on whether those layers are being sent in a single or in multiple RTP flows. The other payload-specific feedback messages defined in RFC 5104 and RFC 4585 as updated by RFC 5506 have also been analyzed, and no corresponding shortcomings have been found. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-avtext-avpf-ccm-layered/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-avtext-avpf-ccm-layered/ballot/ No IPR declarations have been submitted directly on this I-D. From nobody Fri Nov 18 18:27:31 2016 Return-Path: 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 B2572129601 for ; Fri, 18 Nov 2016 18:27:29 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.717 X-Spam-Level: X-Spam-Status: No, score=-5.717 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 aNq4AB5S2DbZ for ; Fri, 18 Nov 2016 18:27:28 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD93012951B for ; Fri, 18 Nov 2016 18:27:27 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CVN50573; Sat, 19 Nov 2016 02:27:25 +0000 (GMT) Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml702-cah.china.huawei.com (10.201.5.99) with Microsoft SMTP Server (TLS) id 14.3.235.1; Sat, 19 Nov 2016 02:27:24 +0000 Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.151]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Sat, 19 Nov 2016 10:27:17 +0800 From: "Huangyihong (Rachel)" To: "avtext@ietf.org" Thread-Topic: [avtext] IPR disclosure related to draft-ietf-avtext-framemarking Thread-Index: AdJCDHFimXrGw53ZR0+h73P/EvYPPA== Date: Sat, 19 Nov 2016 02:27:16 +0000 Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB8705F4A5@nkgeml513-mbx.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.45.1.223] Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4A5nkgeml513mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090205.582FB88D.0078, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.151, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 2f0e13a772c265cd65a71c5f331d3645 Archived-At: Subject: [avtext] IPR disclosure related to draft-ietf-avtext-framemarking X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2016 02:27:29 -0000 --_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4A5nkgeml513mbxchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, An IPR disclosure that pertains to draft-ietf-avtext-framemarking was submi= tted. https://datatracker.ietf.org/ipr/2876/. In Seoul meeting, we discussed it and didn't see any objection in the room = to progress this work with IPR. We'd like to confirm it in the mailing list. Do any other WG participants h= ave objections to proceed with this work after this IPR disclosure? Please = state it on the mail list until Friday December 2, 2016. BR, Rachel --_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4A5nkgeml513mbxchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

An = IPR disclosure that pertains to draft-ietf-avtext-framemarking was submitte= d. https://datatrack= er.ietf.org/ipr/2876/.

In Seoul meeting, we discuss= ed it and didn’t see any objection in the = room to progress this work with IPR.

 

We’d like to confirm it in the mailing list. Do any other WG participants have objections to= proceed with this work after this IPR disclosure? Please state it on the m= ail list until Friday December 2, 2016.

 

BR,

Rachel

--_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4A5nkgeml513mbxchi_-- From nobody Fri Nov 18 18:39:31 2016 Return-Path: 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 3A88C12951B for ; Fri, 18 Nov 2016 18:39:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.717 X-Spam-Level: X-Spam-Status: No, score=-5.717 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no 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 NoqwVwe1omDV for ; Fri, 18 Nov 2016 18:39:28 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0FC2129439 for ; Fri, 18 Nov 2016 18:39:27 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAX61133; Sat, 19 Nov 2016 02:39:25 +0000 (GMT) Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Sat, 19 Nov 2016 02:39:24 +0000 Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.151]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Sat, 19 Nov 2016 10:39:17 +0800 From: "Huangyihong (Rachel)" To: "avtext@ietf.org" Thread-Topic: [avtext] draft minutes for IETF 97 Thread-Index: AdJCDh6zyTfWmpzzQU+pIIfi5Efdlg== Date: Sat, 19 Nov 2016 02:39:16 +0000 Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB8705F4E3@nkgeml513-mbx.china.huawei.com> Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.45.1.223] Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4E3nkgeml513mbxchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A0B0204.582FBB5E.0057, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.151, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 69f97945d0ec96d84cc2426245c038d8 Archived-At: Subject: [avtext] draft minutes for IETF 97 X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Audio/Video Transport Extensions working group discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Nov 2016 02:39:30 -0000 --_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4E3nkgeml513mbxchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, The rough minutes of AVTEXT session in IETF 97 is available now. https://www.ietf.org/proceedings/97/minutes/minutes-97-avtext-00.txt Thanks to Roni Even and Stephan Wenger to be the notetakers. If you see any corrections or clarifications, please send it to the mailing= list. BR, Rachel --_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4E3nkgeml513mbxchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

The rough minutes of AVTEXT ses= sion in IETF 97 is available now.

https://www.ietf.org/proc= eedings/97/minutes/minutes-97-avtext-00.txt

 

Thanks to Roni Even and Stephan= Wenger to be the notetakers.

 

If you see any corrections or c= larifications, please send it to the mailing list.

 

BR,

Rachel

--_000_51E6A56BD6A85142B9D172C87FC3ABBB8705F4E3nkgeml513mbxchi_--