From nobody Wed Jun 11 01:53:03 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3931A0160 for ; Wed, 11 Jun 2014 01:52:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 24d_oVk9EKhp for ; Wed, 11 Jun 2014 01:52:38 -0700 (PDT) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 946751B2835 for ; Wed, 11 Jun 2014 01:52:37 -0700 (PDT) X-AuditID: c1b4fb3a-f79746d000006fe2-6c-539818d3c50b Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 41.10.28642.3D818935; Wed, 11 Jun 2014 10:52:35 +0200 (CEST) Received: from ESESSMB105.ericsson.se ([169.254.5.253]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0174.001; Wed, 11 Jun 2014 10:52:34 +0200 From: Bo Burman To: "avtext@ietf.org" Thread-Topic: Proposed RTP Taxonomy updates Thread-Index: Ac+FRq0SgfJnszleRS+PT7rslqpngw== Date: Wed, 11 Jun 2014 08:52:33 +0000 Message-ID: Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.20] Content-Type: multipart/alternative; boundary="_000_BBE9739C2C302046BD34B42713A1E2A22E2151FDESESSMB105erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+Jvje5liRnBBkeeGVh8vHeD1YHRY8mS n0wBjFFcNimpOZllqUX6dglcGV3nG9gKzlZW7Duyiq2B8VRWFyMnh4SAicTS+4vZIGwxiQv3 1oPZQgJHGSXmr+LrYuQCspcwSkzoucEIkmAT0JCYv+MumC0ioC5xZ/oFsAZhATWJI2sXsUPE tSVubX3JAmHrSby5/hOshkVAVWLV1ttgNq+Ar8SHtfPA5jAKyErc/34PrJ5ZQFzi1pP5TBAH CUgs2XOeGcIWlXj5+B8rhK0ocXX6ciaI+nyJ/RfeMUPMFJQ4OfMJywRGoVlIRs1CUjYLSRlE XEdiwe5PbBC2tsSyha+ZYewzBx4zIYsvYGRfxShanFpcnJtuZKSXWpSZXFycn6eXl1qyiREY Ewe3/LbawXjwueMhRgEORiUe3gXu04OFWBPLiitzDzFKc7AoifNe1KgOFhJITyxJzU5NLUgt ii8qzUktPsTIxMEp1cBYGDtzgp3hv0cPDplpdp19k7eKpeSEbk2hwdVT63N33Vb6/GSO4qPd e7rO8XcwClqf7fBP7vfx777/+17rN7/ZBxMWWM/SusXTK7Pi+aYjf+tVj04q+tyxSbTkZUeF WVGSR0nfulmZ0zhXhDe4zozhfL7Fc+GnNjPVBwkLlqlp2Z3NUDbeMvm8EktxRqKhFnNRcSIA wj+1c2oCAAA= Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/L6UZBCD_qvsqix31PUmAjyLqPs0 Subject: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 11 Jun 2014 08:52:42 -0000 --_000_BBE9739C2C302046BD34B42713A1E2A22E2151FDESESSMB105erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, Based on my interpretation of the mailing list discussions, these are the e= dits that are planned for the next version: * Re-structure the entire document such that alternate usages, desc= ribing existing terms using Taxonomy wording, are separated out into their = own (alphabetically sorted) sub-sections, making it possible to find them t= hrough the table of contents * Remove any sub-section level 4 numbering possibly remaining after= the above change * Change the term "Packet Stream" to "RTP Stream" throughout the do= cument, since "Packet Stream" is too unspecific * Remove all topologies discussion in section 4 to avoid any confli= ct or multiple description of topologies, even if informational. * In the above, keep one informational figure that depicts one exam= ple of the terms Communication Session, Multimedia Session, RTP Session, an= d End Point, and move that figure, as an example, to the Concepts sub-secti= on on Communication Entities. * Clarify in Synchronization Context section that CNAME is not an E= nd Point identifier * In that same section, point out that although RTP uses NTP-format= timestamps, they don't need to be NTP synchronized to be useful. Also refe= rence draft-ietf-avtcore-clksrc. * Add a new relation section with an explicit explanation of RTP du= plication as of RFC 7198, preferably with a figure. * Remove the statement that a CLUE Media Capture is identified via = indexed notation, since it is incorrect. * Make it clear in the characteristics of RTP Stream that the SSRC = identifier of a single RTP Stream can change, but only as a result of SSRC = collision or a clock rate change (referring RFC 7160) * Clarify that multiple 6190 packet streams from a single Media Sou= rce can be present in a single RTP Session, despite what is said in 6190 se= ction 1.2.2 * Remove the current discussion on and definition of MST-SS/MS and = SST-SS/MS * Mention that an "End Point" is typically a single "host" Unless there are objections, I plan to submit an updated draft including th= e above changes during next week. Comments and questions are welcome! Cheers, Bo --_000_BBE9739C2C302046BD34B42713A1E2A22E2151FDESESSMB105erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear all,

 

Based on my interpretation of the mailing list discu= ssions, these are the edits that are planned for the next version:

·         Re-structure the entire document such that a= lternate usages, describing existing terms using Taxonomy wording, are sepa= rated out into their own (alphabetically sorted) sub-sections, making it po= ssible to find them through the table of contents

·         Remove any sub-section level 4 numbering pos= sibly remaining after the above change

·         Change the term “Packet Stream” = to “RTP Stream” throughout the document, since “Packet St= ream” is too unspecific

·         Remove all topologies discussion in section = 4 to avoid any conflict or multiple description of topologies, even if info= rmational.

·         In the above, keep one informational figure = that depicts one example of the terms Communication Session, Multimedia Ses= sion, RTP Session, and End Point, and move that figure, as an example, to t= he Concepts sub-section on Communication Entities.

·         Clarify in Synchronization Context section t= hat CNAME is not an End Point identifier

·         In that same section, point out that althoug= h RTP uses NTP-format timestamps, they don’t need to be NTP synchroni= zed to be useful. Also reference draft-ietf-avtcore-clksrc.

·         Add a new relation section with an explicit = explanation of RTP duplication as of RFC 7198, preferably with a figure.

·         Remove the statement that a CLUE Media Captu= re is identified via indexed notation, since it is incorrect.

·         Make it clear in the characteristics of RTP = Stream that the SSRC identifier of a single RTP Stream can change, but only= as a result of SSRC collision or a clock rate change (referring RFC 7160)<= o:p>

·         Clarify that multiple 6190 packet streams fr= om a single Media Source can be present in a single RTP Session, despite wh= at is said in 6190 section 1.2.2

·         Remove the current discussion on and definit= ion of MST-SS/MS and SST-SS/MS

·         Mention that an “End Point” is t= ypically a single “host”

 

Unless there are objections, I plan to submit an upd= ated draft including the above changes during next week.

 

Comments and questions are welcome!

 

Cheers,

Bo

 

--_000_BBE9739C2C302046BD34B42713A1E2A22E2151FDESESSMB105erics_-- From nobody Wed Jun 11 11:25:50 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79C731A023D for ; Wed, 11 Jun 2014 11:25:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.696 X-Spam-Level: X-Spam-Status: No, score=0.696 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 saAE3slAHWV5 for ; Wed, 11 Jun 2014 11:25:48 -0700 (PDT) Received: from BLU004-OMC1S18.hotmail.com (blu004-omc1s18.hotmail.com [65.55.116.29]) by ietfa.amsl.com (Postfix) with ESMTP id BE7751A00D4 for ; Wed, 11 Jun 2014 11:25:47 -0700 (PDT) Received: from BLU181-W71 ([65.55.116.7]) by BLU004-OMC1S18.hotmail.com with Microsoft SMTPSVC(7.5.7601.22701); Wed, 11 Jun 2014 11:25:47 -0700 X-TMN: [HxlDIdmkXKCZZP/kVuDbF4DMHLZCAo9k] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_1e612e94-7311-447f-b8c8-469457a60f5b_" From: Bernard Aboba To: Bo Burman , "avtext@ietf.org" Date: Wed, 11 Jun 2014 11:25:46 -0700 Importance: Normal In-Reply-To: References: MIME-Version: 1.0 X-OriginalArrivalTime: 11 Jun 2014 18:25:47.0395 (UTC) FILETIME=[90958D30:01CF85A2] Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/dh8v0gDYRzDaCGGF43wwDQ4P2Cg Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 11 Jun 2014 18:25:48 -0000 --_1e612e94-7311-447f-b8c8-469457a60f5b_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable =0A= Bo said:=20 =B7 =0A= Remove the current discussion on and definition of MST-SS/MS and SST-SS/MS Why is this being removed? Personally=2C I thought it was useful. =0A= =0A= =0A= = --_1e612e94-7311-447f-b8c8-469457a60f5b_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
=0A=

Bo said: =3B

<= br>

=B7 =3B =3B =3B =3B=  =3B =3B =3B =3B=0A= Remove the current discussion on and definition of MST= -SS/MS and SST-SS/MS


Why is this being removed?  =3BPersonally=2C I thought it= was useful. =3B

=0A=


= =0A=

 =3B

=0A=


= --_1e612e94-7311-447f-b8c8-469457a60f5b_-- From nobody Wed Jun 11 11:33:18 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB561B2817 for ; Wed, 11 Jun 2014 11:33:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.601 X-Spam-Level: X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 e_hiuNvg987c for ; Wed, 11 Jun 2014 11:33:15 -0700 (PDT) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BFE51B2816 for ; Wed, 11 Jun 2014 11:33:15 -0700 (PDT) Received: by mail-wg0-f44.google.com with SMTP id x13so142998wgg.3 for ; Wed, 11 Jun 2014 11:33:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=6BMp8gJ7Wq2xRNekUDYkSES/dYKxFx/Mbll5d1TVVXY=; b=k66T7kEeTt1tsSW+5IZgaHPqTLC5FWF7PW0GbxZdeDty+tHzz60pxQnt4bAtb1LQwS 4wa1JLKk8HM5/TqkbIHeFTLNmfqKpLStKCfwbB8bY3TKAZQj9GZhfsisc5kPjwLgxplY MY3dP0YogyNhYW2kHc7tsd6vIoNUCJ3siXhS/+y6YsNvCshQYwRFaQ0vesBoK4JkNpXr tb2gyXhh5qOzsu+VUi2PhmAawAvw3GQ4J+ekMCEulW5huCW2vpi7feGGsXzrhtZQ1Mrv LiSgH9eOou4PUO6gL9RIE4iDx39+zKuoxeIV7/tuug4bqCIBvs5UY/2KXtbES7iKRsy8 qNgw== X-Gm-Message-State: ALoCoQkVg55IskzB8r16vk/dyb/W5aYpi4uZbjTkks0E82Sjm0Xe7Zbe0CTylZdpMCu75DyGpkPe X-Received: by 10.180.81.1 with SMTP id v1mr12779405wix.10.1402511593862; Wed, 11 Jun 2014 11:33:13 -0700 (PDT) Received: from camionet.local ([80.96.26.125]) by mx.google.com with ESMTPSA id en6sm28716826wib.11.2014.06.11.11.33.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Jun 2014 11:33:12 -0700 (PDT) Message-ID: <5398A0E7.1070808@jitsi.org> Date: Wed, 11 Jun 2014 21:33:11 +0300 From: Emil Ivov User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Bernard Aboba , Bo Burman , "avtext@ietf.org" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/ECAjzvOu2hb_vx0VjTFT26ajcDY Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 11 Jun 2014 18:33:17 -0000 On 11.06.14, 21:25, Bernard Aboba wrote: > Bo said: > > > ĚRemove the current discussion on and definition of MST-SS/MS and SST-SS/MS > > > Why is this being removed? Personally, I thought it was useful. +1 -- https://jitsi.org From nobody Wed Jun 11 11:47:31 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D15911A0259 for ; Wed, 11 Jun 2014 11:47:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham 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 gvqZhs5dqP5S for ; Wed, 11 Jun 2014 11:47:27 -0700 (PDT) Received: from server209.appriver.com (server209c.appriver.com [8.31.233.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C56A1A00D4 for ; Wed, 11 Jun 2014 11:47:26 -0700 (PDT) X-Note-AR-ScanTimeLocal: 6/11/2014 2:47:23 PM X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Primary: alex@vidyo.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note-SnifferID: 0 X-Note: TCH-CT/SI:0-62/SG:2 6/11/2014 2:47:11 PM X-GBUdb-Analysis: 0, 162.209.16.214, Ugly c=0.783533 p=-0.978055 Source White X-Signature-Violations: 0-0-0-2316-c X-Note-419: 0 ms. Fail:0 Chk:1340 of 1340 total X-Note: SCH-CT/SI:0-1340/SG:1 6/11/2014 2:47:22 PM X-Note: Spam Tests Failed: X-Country-Path: ->UNITED STATES-> X-Note-Sending-IP: 162.209.16.214 X-Note-Reverse-DNS: X-Note-Return-Path: alex@vidyo.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G330 G331 G332 G333 G337 G338 G448 X-Note: Encrypt Rule Hits: X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [162.209.16.214] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 104311176; Wed, 11 Jun 2014 14:47:23 -0400 Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0146.000; Wed, 11 Jun 2014 13:47:22 -0500 From: Alex Eleftheriadis To: Emil Ivov Thread-Topic: [avtext] Proposed RTP Taxonomy updates Thread-Index: Ac+FRq0SgfJnszleRS+PT7rslqpngwAhcuEAAABCT4AAAH6pgA== Date: Wed, 11 Jun 2014 18:47:21 +0000 Message-ID: <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> References: <5398A0E7.1070808@jitsi.org> In-Reply-To: <5398A0E7.1070808@jitsi.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [85.72.239.80] Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/W2CnAUwQZCLEIWHYKwt_MLpkdZ4 Cc: "avtext@ietf.org" Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 11 Jun 2014 18:47:28 -0000 +1 On Jun 11, 2014, at 9:33 PM, Emil Ivov wrote: >=20 >=20 > On 11.06.14, 21:25, Bernard Aboba wrote: >> Bo said: >>=20 >>=20 >> =B7Remove the current discussion on and definition of MST-SS/MS and SST-= SS/MS >>=20 >>=20 >> Why is this being removed? Personally, I thought it was useful. >=20 > +1 >=20 >=20 >=20 > --=20 > https://jitsi.org >=20 > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext From nobody Tue Jun 17 01:53:35 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22FF1A0327 for ; Tue, 17 Jun 2014 01:53:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 jw_vlebTgQqL for ; Tue, 17 Jun 2014 01:53:32 -0700 (PDT) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D4251A02C2 for ; Tue, 17 Jun 2014 01:53:31 -0700 (PDT) X-AuditID: c1b4fb30-f79a56d000006536-d4-53a00209a9d1 Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 5B.DA.25910.90200A35; Tue, 17 Jun 2014 10:53:30 +0200 (CEST) Received: from ESESSMB105.ericsson.se ([169.254.5.228]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.03.0174.001; Tue, 17 Jun 2014 10:53:29 +0200 From: Bo Burman To: Alex Eleftheriadis , Emil Ivov Thread-Topic: [avtext] Proposed RTP Taxonomy updates Thread-Index: Ac+FRq0SgfJnszleRS+PT7rslqpngwASx8kAAABCT4AAAH6pgAEdJpVg Date: Tue, 17 Jun 2014 08:53:28 +0000 Message-ID: References: <5398A0E7.1070808@jitsi.org> <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> In-Reply-To: <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.20] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpkkeLIzCtJLcpLzFFi42KZGfG3RpeLaUGwwdelvBbXd65lsfh47war xf4ll5kt1uycwOLA4vG45wybx5IlP5k8/r8J9Gh7doc9gCWKyyYlNSezLLVI3y6BK2PqvGfs BRPYK55+PsPewHiGtYuRk0NCwETixsZdLBC2mMSFe+vZuhi5OIQEjjJKbF2+ghHCWcIo8fHU W0aQKjYBDYn5O+6C2SICLhLfPncBdXNwMAuESLRNVQIJCwsYS+w8vI8VosRE4u/GycwQtpvE qkPT2UBsFgFViZ8TX4LFeQV8JRY/WckOsesso8T6aW1gF3EK2Eq83XuFCcRmFJCVuP/9Hlic WUBc4taT+UwQVwtILNlznhnCFpV4+fgf1GeKElenL2eCqNeRWLD7ExuErS2xbOFrqMWCEidn PmGZwCg2C8nYWUhaZiFpmYWkZQEjyypG0eLU4qTcdCMjvdSizOTi4vw8vbzUkk2MwDg7uOW3 wQ7Gl88dDzEKcDAq8fAuMJgfLMSaWFZcmXuIUZqDRUmcd+G5ecFCAumJJanZqakFqUXxRaU5 qcWHGJk4OKUaGPVUNzF+Sli5h8PydVrYXlv72st1/GsZ3aU+Kqd3b518mFW5T8ewmYX9QOmv mI9rZkQKfjpwxCD4VJaW7O+ft3Y58Hm8vznjQPy3uMLEKcETF9q9Fl3wlf/FOb+in/IGJ5fW OoVpnKg8M6/mzGMh957fcgstJOvvnZyW9O9hzclr2qmnCtksS5RYijMSDbWYi4oTAQkS+VqU AgAA Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/5R9s1vuan2PxRXhHHuFO1nsuva8 Cc: "avtext@ietf.org" Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 17 Jun 2014 08:53:34 -0000 My misunderstanding from previous discussions in that case; I will definite= ly not remove it if it is felt useful! > -----Original Message----- > From: Alex Eleftheriadis [mailto:alex@vidyo.com] > Sent: den 11 juni 2014 20:47 > To: Emil Ivov > Cc: Bernard Aboba; Bo Burman; avtext@ietf.org > Subject: Re: [avtext] Proposed RTP Taxonomy updates >=20 > +1 >=20 > On Jun 11, 2014, at 9:33 PM, Emil Ivov wrote: >=20 > > > > > > On 11.06.14, 21:25, Bernard Aboba wrote: > >> Bo said: > >> > >> > >> *Remove the current discussion on and definition of MST-SS/MS and SST-= SS/MS > >> > >> > >> Why is this being removed? Personally, I thought it was useful. > > > > +1 > > > > > > > > -- > > https://jitsi.org > > > > _______________________________________________ > > avtext mailing list > > avtext@ietf.org > > https://www.ietf.org/mailman/listinfo/avtext From nobody Tue Jun 17 07:14:28 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615251A002F for ; Tue, 17 Jun 2014 07:14:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.131 X-Spam-Level: X-Spam-Status: No, score=-1.131 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=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 jJ0xySCUf0Sz for ; Tue, 17 Jun 2014 07:14:22 -0700 (PDT) Received: from server209.appriver.com (server209f.appriver.com [8.31.233.121]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E98BD1A015A for ; Tue, 17 Jun 2014 07:14:21 -0700 (PDT) X-Note-AR-ScanTimeLocal: 6/17/2014 10:14:20 AM X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Primary: jonathan@vidyo.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note-SnifferID: 0 X-Note: TCH-CT/SI:0-114/SG:2 6/17/2014 10:14:13 AM X-GBUdb-Analysis: 0, 162.209.16.214, Ugly c=0.802449 p=-0.965961 Source White X-Signature-Violations: 0-0-0-5968-c X-Note-419: 15.6004 ms. Fail:0 Chk:1339 of 1339 total X-Note: SCH-CT/SI:0-1339/SG:1 6/17/2014 10:14:15 AM X-Note: Spam Tests Failed: X-Country-Path: ->UNITED STATES-> X-Note-Sending-IP: 162.209.16.214 X-Note-Reverse-DNS: X-Note-Return-Path: jonathan@vidyo.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G330 G331 G332 G333 G337 G338 G448 X-Note: Encrypt Rule Hits: X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [162.209.16.214] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 105603614; Tue, 17 Jun 2014 10:14:20 -0400 Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0146.000; Tue, 17 Jun 2014 09:14:18 -0500 From: Jonathan Lennox To: Bo Burman Thread-Topic: [avtext] Proposed RTP Taxonomy updates Thread-Index: Ac+FRq0SgfJnszleRS+PT7rslqpngwASx8kAAABCT4AAAH6pgAEdJpVgABW64AA= Date: Tue, 17 Jun 2014 14:14:18 +0000 Message-ID: <643E675C-9520-4122-99FF-EE8BB0A42549@vidyo.com> References: <5398A0E7.1070808@jitsi.org> <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [160.79.219.114] Content-Type: text/plain; charset="Windows-1252" Content-ID: <302A99B344B44B43868B0DAF12787146@vidyo.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/SLKh8fUsVE7JOWju-fiU_PfHKaM Cc: "avtext@ietf.org" Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 17 Jun 2014 14:14:26 -0000 (Speaking as an individual.) My argument =97 which may be what you were remembering =97 was that this di= stinction was useful, but secondary. In my view, the primary distinction is between single-stream encoding and m= ulti-stream encoding (whatever term we end up using for this) =97 i.e., whe= ther scalable media is encoded as one RTP packet stream, or several. Following up to that is the decision about how these RTP packet streams are= allocated to RTP sessions, if you're using a multi-stream encoding, and ho= w correlation is done to indicate the association between the streams. And= this is definitely an important discussion to have, and we need good termi= nology for it. That said, I think the term =93MST-SS=94 =97 if that=92s meant to expand to= =93Multi-Session Transmission - Single Stream=94 =97 doesn=92t make any se= nse, because a single RTP packet stream can only be in a single RTP session= . I think the distinction people are trying to make with this term is whet= her streams in multiple sessions are correlated by giving them the same SSR= C, or whether they have some other correlation mechanism? But if so, we ne= ed a better term for this. On Jun 17, 2014, at 4:53 AM, Bo Burman wrote: > My misunderstanding from previous discussions in that case; I will defini= tely not remove it if it is felt useful! >=20 >> -----Original Message----- >> From: Alex Eleftheriadis [mailto:alex@vidyo.com] >> Sent: den 11 juni 2014 20:47 >> To: Emil Ivov >> Cc: Bernard Aboba; Bo Burman; avtext@ietf.org >> Subject: Re: [avtext] Proposed RTP Taxonomy updates >>=20 >> +1 >>=20 >> On Jun 11, 2014, at 9:33 PM, Emil Ivov wrote: >>=20 >>>=20 >>>=20 >>> On 11.06.14, 21:25, Bernard Aboba wrote: >>>> Bo said: >>>>=20 >>>>=20 >>>> *Remove the current discussion on and definition of MST-SS/MS and SST-= SS/MS >>>>=20 >>>>=20 >>>> Why is this being removed? Personally, I thought it was useful. >>>=20 >>> +1 >>>=20 >>>=20 >>>=20 >>> -- >>> https://jitsi.org >>>=20 >>> _______________________________________________ >>> avtext mailing list >>> avtext@ietf.org >>> https://www.ietf.org/mailman/listinfo/avtext >=20 > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext >=20 From nobody Tue Jun 17 07:43:13 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB44D1A005B for ; Tue, 17 Jun 2014 07:43:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.551 X-Spam-Level: X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham 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 L5bzoY66aKdB for ; Tue, 17 Jun 2014 07:43:07 -0700 (PDT) Received: from BLU004-OMC1S18.hotmail.com (blu004-omc1s18.hotmail.com [65.55.116.29]) (using TLSv1.2 with cipher AES128-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 895601A0025 for ; Tue, 17 Jun 2014 07:43:07 -0700 (PDT) Received: from BLU406-EAS58 ([65.55.116.7]) by BLU004-OMC1S18.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712); Tue, 17 Jun 2014 07:43:06 -0700 X-TMN: [wJokvXM6/0vsYMuK1BQU3HvyIGn8ZKv1] X-Originating-Email: [bernard_aboba@hotmail.com] Message-ID: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 References: <5398A0E7.1070808@jitsi.org> <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> <643E675C-9520-4122-99FF-EE8BB0A42549@vidyo.com> From: Bernard Aboba MIME-Version: 1.0 (1.0) In-Reply-To: <643E675C-9520-4122-99FF-EE8BB0A42549@vidyo.com> Date: Tue, 17 Jun 2014 10:43:05 -0400 To: Jonathan Lennox X-OriginalArrivalTime: 17 Jun 2014 14:43:06.0372 (UTC) FILETIME=[7345BC40:01CF8A3A] Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/JGSzlhl_1rS032YKmdVs2X1eJ8E Cc: "avtext@ietf.org" Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 17 Jun 2014 14:43:13 -0000 SSBoYWQgdGhlIHNhbWUgcXVlc3Rpb24gYWJvdXQgTVNULVNTLiBCdXQgYXMgSSB1bmRlcnN0YW5k IGl0LCB0aGlzIGlzIHRvIG1lYW4gYSBzaW5nbGUgc3RyZWFtIHBlciBzZXNzaW9uLCBub3QgdGhl IHNhbWUgU1NSQyBmb3IgZXZlcnkgc2Vzc2lvbi4gDQoNCj4gT24gSnVuIDE3LCAyMDE0LCBhdCAx MDoxNCBBTSwgIkpvbmF0aGFuIExlbm5veCIgPGpvbmF0aGFuQHZpZHlvLmNvbT4gd3JvdGU6DQo+ IA0KPiAoU3BlYWtpbmcgYXMgYW4gaW5kaXZpZHVhbC4pDQo+IA0KPiBNeSBhcmd1bWVudCDigJQg d2hpY2ggbWF5IGJlIHdoYXQgeW91IHdlcmUgcmVtZW1iZXJpbmcg4oCUIHdhcyB0aGF0IHRoaXMg ZGlzdGluY3Rpb24gd2FzIHVzZWZ1bCwgYnV0IHNlY29uZGFyeS4NCj4gDQo+IEluIG15IHZpZXcs IHRoZSBwcmltYXJ5IGRpc3RpbmN0aW9uIGlzIGJldHdlZW4gc2luZ2xlLXN0cmVhbSBlbmNvZGlu ZyBhbmQgbXVsdGktc3RyZWFtIGVuY29kaW5nICh3aGF0ZXZlciB0ZXJtIHdlIGVuZCB1cCB1c2lu ZyBmb3IgdGhpcykg4oCUIGkuZS4sIHdoZXRoZXIgc2NhbGFibGUgbWVkaWEgaXMgZW5jb2RlZCBh cyBvbmUgUlRQIHBhY2tldCBzdHJlYW0sIG9yIHNldmVyYWwuDQo+IA0KPiBGb2xsb3dpbmcgdXAg dG8gdGhhdCBpcyB0aGUgZGVjaXNpb24gYWJvdXQgaG93IHRoZXNlIFJUUCBwYWNrZXQgc3RyZWFt cyBhcmUgYWxsb2NhdGVkIHRvIFJUUCBzZXNzaW9ucywgaWYgeW91J3JlIHVzaW5nIGEgbXVsdGkt c3RyZWFtIGVuY29kaW5nLCBhbmQgaG93IGNvcnJlbGF0aW9uIGlzIGRvbmUgdG8gaW5kaWNhdGUg dGhlIGFzc29jaWF0aW9uIGJldHdlZW4gdGhlIHN0cmVhbXMuICBBbmQgdGhpcyBpcyBkZWZpbml0 ZWx5IGFuIGltcG9ydGFudCBkaXNjdXNzaW9uIHRvIGhhdmUsIGFuZCB3ZSBuZWVkIGdvb2QgdGVy bWlub2xvZ3kgZm9yIGl0Lg0KPiANCj4gVGhhdCBzYWlkLCBJIHRoaW5rIHRoZSB0ZXJtIOKAnE1T VC1TU+KAnSDigJQgaWYgdGhhdOKAmXMgbWVhbnQgdG8gZXhwYW5kIHRvIOKAnE11bHRpLVNlc3Np b24gVHJhbnNtaXNzaW9uIC0gU2luZ2xlIFN0cmVhbeKAnSDigJQgZG9lc27igJl0IG1ha2UgYW55 IHNlbnNlLCBiZWNhdXNlIGEgc2luZ2xlIFJUUCBwYWNrZXQgc3RyZWFtIGNhbiBvbmx5IGJlIGlu IGEgc2luZ2xlIFJUUCBzZXNzaW9uLiAgSSB0aGluayB0aGUgZGlzdGluY3Rpb24gcGVvcGxlIGFy ZSB0cnlpbmcgdG8gbWFrZSB3aXRoIHRoaXMgdGVybSBpcyB3aGV0aGVyIHN0cmVhbXMgaW4gbXVs dGlwbGUgc2Vzc2lvbnMgYXJlIGNvcnJlbGF0ZWQgYnkgZ2l2aW5nIHRoZW0gdGhlIHNhbWUgU1NS Qywgb3Igd2hldGhlciB0aGV5IGhhdmUgc29tZSBvdGhlciBjb3JyZWxhdGlvbiBtZWNoYW5pc20/ ICBCdXQgaWYgc28sIHdlIG5lZWQgYSBiZXR0ZXIgdGVybSBmb3IgdGhpcy4NCj4gDQo+PiBPbiBK dW4gMTcsIDIwMTQsIGF0IDQ6NTMgQU0sIEJvIEJ1cm1hbiA8Ym8uYnVybWFuQGVyaWNzc29uLmNv bT4gd3JvdGU6DQo+PiANCj4+IE15IG1pc3VuZGVyc3RhbmRpbmcgZnJvbSBwcmV2aW91cyBkaXNj dXNzaW9ucyBpbiB0aGF0IGNhc2U7IEkgd2lsbCBkZWZpbml0ZWx5IG5vdCByZW1vdmUgaXQgaWYg aXQgaXMgZmVsdCB1c2VmdWwhDQo+PiANCj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K Pj4+IEZyb206IEFsZXggRWxlZnRoZXJpYWRpcyBbbWFpbHRvOmFsZXhAdmlkeW8uY29tXQ0KPj4+ IFNlbnQ6IGRlbiAxMSBqdW5pIDIwMTQgMjA6NDcNCj4+PiBUbzogRW1pbCBJdm92DQo+Pj4gQ2M6 IEJlcm5hcmQgQWJvYmE7IEJvIEJ1cm1hbjsgYXZ0ZXh0QGlldGYub3JnDQo+Pj4gU3ViamVjdDog UmU6IFthdnRleHRdIFByb3Bvc2VkIFJUUCBUYXhvbm9teSB1cGRhdGVzDQo+Pj4gDQo+Pj4gKzEN Cj4+PiANCj4+Pj4gT24gSnVuIDExLCAyMDE0LCBhdCA5OjMzIFBNLCBFbWlsIEl2b3YgPGVtY2hv QGppdHNpLm9yZz4gd3JvdGU6DQo+Pj4+IA0KPj4+PiANCj4+Pj4gDQo+Pj4+PiBPbiAxMS4wNi4x NCwgMjE6MjUsIEJlcm5hcmQgQWJvYmEgd3JvdGU6DQo+Pj4+PiBCbyBzYWlkOg0KPj4+Pj4gDQo+ Pj4+PiANCj4+Pj4+ICpSZW1vdmUgdGhlIGN1cnJlbnQgZGlzY3Vzc2lvbiBvbiBhbmQgZGVmaW5p dGlvbiBvZiBNU1QtU1MvTVMgYW5kIFNTVC1TUy9NUw0KPj4+Pj4gDQo+Pj4+PiANCj4+Pj4+IFdo eSBpcyB0aGlzIGJlaW5nIHJlbW92ZWQ/ICBQZXJzb25hbGx5LCBJIHRob3VnaHQgaXQgd2FzIHVz ZWZ1bC4NCj4+Pj4gDQo+Pj4+ICsxDQo+Pj4+IA0KPj4+PiANCj4+Pj4gDQo+Pj4+IC0tDQo+Pj4+ IGh0dHBzOi8vaml0c2kub3JnDQo+Pj4+IA0KPj4+PiBfX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fXw0KPj4+PiBhdnRleHQgbWFpbGluZyBsaXN0DQo+Pj4+IGF2 dGV4dEBpZXRmLm9yZw0KPj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L2F2dGV4dA0KPj4gDQo+PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fXw0KPj4gYXZ0ZXh0IG1haWxpbmcgbGlzdA0KPj4gYXZ0ZXh0QGlldGYub3JnDQo+PiBo dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dGV4dA0KPiANCj4gX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gYXZ0ZXh0IG1haWxp bmcgbGlzdA0KPiBhdnRleHRAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h bi9saXN0aW5mby9hdnRleHQNCg== From nobody Tue Jun 17 07:46:59 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7819C1A005B for ; Tue, 17 Jun 2014 07:46:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.131 X-Spam-Level: X-Spam-Status: No, score=-1.131 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77, SPF_PASS=-0.001] autolearn=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 nFpw2VA3uine for ; Tue, 17 Jun 2014 07:46:54 -0700 (PDT) Received: from server209.appriver.com (server209c.appriver.com [8.31.233.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB7A81A0024 for ; Tue, 17 Jun 2014 07:46:53 -0700 (PDT) X-Note-AR-ScanTimeLocal: 6/17/2014 10:46:52 AM X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Policy: GLOBAL - vidyo.com X-Primary: jonathan@vidyo.com X-Note: This Email was scanned by AppRiver SecureTide X-Virus-Scan: V- X-Note-SnifferID: 0 X-Note: TCH-CT/SI:0-90/SG:2 6/17/2014 10:46:13 AM X-GBUdb-Analysis: 0, 162.209.16.214, Ugly c=0.805443 p=-0.962903 Source White X-Signature-Violations: 0-0-0-7859-c X-Note-419: 15.6004 ms. Fail:0 Chk:1338 of 1338 total X-Note: SCH-CT/SI:0-1338/SG:1 6/17/2014 10:46:38 AM X-Note: Spam Tests Failed: X-Country-Path: ->UNITED STATES-> X-Note-Sending-IP: 162.209.16.214 X-Note-Reverse-DNS: X-Note-Return-Path: jonathan@vidyo.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G330 G331 G332 G333 G337 G338 G448 X-Note: Encrypt Rule Hits: X-Note: Mail Class: VALID X-Note: Headers Injected Received: from [162.209.16.214] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 105620782; Tue, 17 Jun 2014 10:46:52 -0400 Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0146.000; Tue, 17 Jun 2014 09:46:50 -0500 From: Jonathan Lennox To: Bernard Aboba Thread-Topic: [avtext] Proposed RTP Taxonomy updates Thread-Index: Ac+FRq0SgfJnszleRS+PT7rslqpngwASx8kAAABCT4AAAH6pgAEdJpVgABW64AAAAQFYgAAAIYcA Date: Tue, 17 Jun 2014 14:46:50 +0000 Message-ID: <463F2553-BAC7-463B-BEF1-7A3B19A3F6EF@vidyo.com> References: <5398A0E7.1070808@jitsi.org> <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> <643E675C-9520-4122-99FF-EE8BB0A42549@vidyo.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [160.79.219.114] Content-Type: text/plain; charset="Windows-1252" Content-ID: <8D0C8FA194E71B4991FBF532D4E373CA@vidyo.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/tzi2ZQmmwyuMYoIXRfMDj8Isg4I Cc: "avtext@ietf.org" Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 17 Jun 2014 14:46:58 -0000 Oh, I see =97 MST-SS means multiple packet streams, and multiple sessions, = but a 1:1 mapping between streams and sessions (as opposed to having more p= acket streams than sessions, and mapping multiple streams into each session= ). I guess that=92s a useful distinction, though it=92s getting a bit into the= weeds. I don=92t think MST-SS is a good name for this, though. On Jun 17, 2014, at 10:43 AM, Bernard Aboba wro= te: > I had the same question about MST-SS. But as I understand it, this is to = mean a single stream per session, not the same SSRC for every session.=20 >=20 >> On Jun 17, 2014, at 10:14 AM, "Jonathan Lennox" wro= te: >>=20 >> (Speaking as an individual.) >>=20 >> My argument =97 which may be what you were remembering =97 was that this= distinction was useful, but secondary. >>=20 >> In my view, the primary distinction is between single-stream encoding an= d multi-stream encoding (whatever term we end up using for this) =97 i.e., = whether scalable media is encoded as one RTP packet stream, or several. >>=20 >> Following up to that is the decision about how these RTP packet streams = are allocated to RTP sessions, if you're using a multi-stream encoding, and= how correlation is done to indicate the association between the streams. = And this is definitely an important discussion to have, and we need good te= rminology for it. >>=20 >> That said, I think the term =93MST-SS=94 =97 if that=92s meant to expand= to =93Multi-Session Transmission - Single Stream=94 =97 doesn=92t make any= sense, because a single RTP packet stream can only be in a single RTP sess= ion. I think the distinction people are trying to make with this term is w= hether streams in multiple sessions are correlated by giving them the same = SSRC, or whether they have some other correlation mechanism? But if so, we= need a better term for this. >>=20 >>> On Jun 17, 2014, at 4:53 AM, Bo Burman wrote: >>>=20 >>> My misunderstanding from previous discussions in that case; I will defi= nitely not remove it if it is felt useful! >>>=20 >>>> -----Original Message----- >>>> From: Alex Eleftheriadis [mailto:alex@vidyo.com] >>>> Sent: den 11 juni 2014 20:47 >>>> To: Emil Ivov >>>> Cc: Bernard Aboba; Bo Burman; avtext@ietf.org >>>> Subject: Re: [avtext] Proposed RTP Taxonomy updates >>>>=20 >>>> +1 >>>>=20 >>>>> On Jun 11, 2014, at 9:33 PM, Emil Ivov wrote: >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> On 11.06.14, 21:25, Bernard Aboba wrote: >>>>>> Bo said: >>>>>>=20 >>>>>>=20 >>>>>> *Remove the current discussion on and definition of MST-SS/MS and SS= T-SS/MS >>>>>>=20 >>>>>>=20 >>>>>> Why is this being removed? Personally, I thought it was useful. >>>>>=20 >>>>> +1 >>>>>=20 >>>>>=20 >>>>>=20 >>>>> -- >>>>> https://jitsi.org >>>>>=20 >>>>> _______________________________________________ >>>>> avtext mailing list >>>>> avtext@ietf.org >>>>> https://www.ietf.org/mailman/listinfo/avtext >>>=20 >>> _______________________________________________ >>> avtext mailing list >>> avtext@ietf.org >>> https://www.ietf.org/mailman/listinfo/avtext >>=20 >> _______________________________________________ >> avtext mailing list >> avtext@ietf.org >> https://www.ietf.org/mailman/listinfo/avtext From nobody Tue Jun 17 07:48:28 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D847D1A0049 for ; Tue, 17 Jun 2014 07:48:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham 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 eZPVtCSNAQE2 for ; Tue, 17 Jun 2014 07:48:22 -0700 (PDT) Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8420E1A0008 for ; Tue, 17 Jun 2014 07:48:21 -0700 (PDT) X-AuditID: c1b4fb3a-f79746d000006fe2-f2-53a055334798 Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id DA.84.28642.33550A35; Tue, 17 Jun 2014 16:48:19 +0200 (CEST) Received: from ESESSMB105.ericsson.se ([169.254.5.228]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.03.0174.001; Tue, 17 Jun 2014 16:48:18 +0200 From: Bo Burman To: Jonathan Lennox , Bernard Aboba Thread-Topic: [avtext] Proposed RTP Taxonomy updates Thread-Index: Ac+FRq0SgfJnszleRS+PT7rslqpngwASx8kAAABCT4AAAH6pgAEdJpVgABW64AD//5KygIAAAQwA///eOoA= Date: Tue, 17 Jun 2014 14:48:18 +0000 Message-ID: References: <5398A0E7.1070808@jitsi.org> <30F68C17-0A0A-415A-B14E-6EDDBEDF4733@vidyo.com> <643E675C-9520-4122-99FF-EE8BB0A42549@vidyo.com> <463F2553-BAC7-463B-BEF1-7A3B19A3F6EF@vidyo.com> In-Reply-To: <463F2553-BAC7-463B-BEF1-7A3B19A3F6EF@vidyo.com> Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.147] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyM+Jvja5x6IJgg9vN6hYf791gtdi/5DKz xf7F55kdmD0e95xh81iy5CeTR9uzO+wBzFFcNimpOZllqUX6dglcGaeOnWUsuKRZsen0VKYG xp2KXYycHBICJhJ3V3ayQthiEhfurWfrYuTiEBI4yigx5fcqFghnCaPEzvmvwKrYBDQk5u+4 ywhiiwiESmxoWc0MYjMLqEsc3rcELC4sYCyx8/A+VogaE4m/GyczQ9hJEvMnbmcCsVkEVCWO LjrPBmLzCvhK7FvXxQSxbCWzRNfzH2DNnAK2EoefHQazGQVkJe5/v8cCsUxc4taT+UwQZwtI LNlznhnCFpV4+fgfUD0HkK0kMW1rGkS5jsSC3Z/YIGxtiWULXzND7BWUODnzCcsERrFZSKbO QtIyC0nLLCQtCxhZVjGKFqcWF+emGxnppRZlJhcX5+fp5aWWbGIERtXBLb+tdjAefO54iFGA g1GJh3eBwfxgIdbEsuLK3EOM0hwsSuK8C8/NCxYSSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXA mLHK9Wvu5d/Lrr/n3fpwV5sX/+neuY9lsgu9F1yy6QmuaU8+/Doifo9SwOV785gVQkLis519 nlSq72yo+M2dfdElMWfDxuBJouxLVzw68mRq+EP1NdeORR3futrmvWSQFGNHcEdmzKKfi6rn +qWE5mhw+Lpc1bs/JTFdbqfiOo58npnrnUxuKrEUZyQaajEXFScCABpS7yyLAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/cCjH3KjvDDAzjtPWOi1lbBB0urQ Cc: "avtext@ietf.org" Subject: Re: [avtext] Proposed RTP Taxonomy updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 17 Jun 2014 14:48:27 -0000 Yes, you are right Bernard. That is my preferred interpretation. I would like to interpret MST-SS to mean multiple RTP streams, spread acros= s multiple RTP Sessions, with the restriction that there can only be a sing= le RTP Stream _per RTP Session_. In that case, you can potentially use the = RTP Session identifier (whatever that is, up to some RTP-external signaling= ) to distinguish the different RTP Streams in the MST and could even possib= ly ignore what SSRC they use. So, I'd like to think of -SS/MS to be _scoped_ by the preceding SST/MST, in= terms of semantics. That way, all four alternatives make sense to me. Regarding identification and relation: SST-SS: Trivial, a single RTP Stream from a single Media Source. SST-MS: Multiple RTP Streams in a single RTP Session are distinguished by t= heir SSRCs, and (I guess?) each such SST-stream would correspond to a singl= e-stream encoding of a single Media Source. MST-SS: A single RTP Stream in each of multiple RTP Sessions, where each su= ch single RTP Stream could be from any one of potentially multiple Media So= urces, and the method to relate which RTP Streams belong to a common Media = Source is (currently) unknown. If there is only a single Media Source, ther= e is no problem to relate the RTP Streams because they all belong to the sa= me Media Source.=20 MST-MS: Multiple (one or more) RTP Streams in each of multiple RTP Sessions= , where each RTP Stream could be from any one of potentially multiple Media= Sources, and the method to relate which RTP Streams belong to a common Med= ia Source is (currently) unknown. Cheers, Bo > -----Original Message----- > From: Jonathan Lennox [mailto:jonathan@vidyo.com] > Sent: den 17 juni 2014 16:47 > To: Bernard Aboba > Cc: Bo Burman; avtext@ietf.org > Subject: Re: [avtext] Proposed RTP Taxonomy updates >=20 > Oh, I see - MST-SS means multiple packet streams, and multiple sessions, = but a 1:1 mapping between streams and > sessions (as opposed to having more packet streams than sessions, and map= ping multiple streams into each session). >=20 > I guess that's a useful distinction, though it's getting a bit into the w= eeds. I don't think MST-SS is a good name for this, > though. >=20 > On Jun 17, 2014, at 10:43 AM, Bernard Aboba w= rote: >=20 > > I had the same question about MST-SS. But as I understand it, this is t= o mean a single stream per session, not the same > SSRC for every session. > > > >> On Jun 17, 2014, at 10:14 AM, "Jonathan Lennox" w= rote: > >> > >> (Speaking as an individual.) > >> > >> My argument - which may be what you were remembering - was that this d= istinction was useful, but secondary. > >> > >> In my view, the primary distinction is between single-stream encoding = and multi-stream encoding (whatever term we > end up using for this) - i.e., whether scalable media is encoded as one R= TP packet stream, or several. > >> > >> Following up to that is the decision about how these RTP packet stream= s are allocated to RTP sessions, if you're using a > multi-stream encoding, and how correlation is done to indicate the associ= ation between the streams. And this is > definitely an important discussion to have, and we need good terminology = for it. > >> > >> That said, I think the term "MST-SS" - if that's meant to expand to "M= ulti-Session Transmission - Single Stream" - > doesn't make any sense, because a single RTP packet stream can only be in= a single RTP session. I think the distinction > people are trying to make with this term is whether streams in multiple s= essions are correlated by giving them the same > SSRC, or whether they have some other correlation mechanism? But if so, = we need a better term for this. > >> > >>> On Jun 17, 2014, at 4:53 AM, Bo Burman wrote= : > >>> > >>> My misunderstanding from previous discussions in that case; I will de= finitely not remove it if it is felt useful! > >>> > >>>> -----Original Message----- > >>>> From: Alex Eleftheriadis [mailto:alex@vidyo.com] > >>>> Sent: den 11 juni 2014 20:47 > >>>> To: Emil Ivov > >>>> Cc: Bernard Aboba; Bo Burman; avtext@ietf.org > >>>> Subject: Re: [avtext] Proposed RTP Taxonomy updates > >>>> > >>>> +1 > >>>> > >>>>> On Jun 11, 2014, at 9:33 PM, Emil Ivov wrote: > >>>>> > >>>>> > >>>>> > >>>>>> On 11.06.14, 21:25, Bernard Aboba wrote: > >>>>>> Bo said: > >>>>>> > >>>>>> > >>>>>> *Remove the current discussion on and definition of MST-SS/MS and = SST-SS/MS > >>>>>> > >>>>>> > >>>>>> Why is this being removed? Personally, I thought it was useful. > >>>>> > >>>>> +1 > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> https://jitsi.org > >>>>> > >>>>> _______________________________________________ > >>>>> avtext mailing list > >>>>> avtext@ietf.org > >>>>> https://www.ietf.org/mailman/listinfo/avtext > >>> > >>> _______________________________________________ > >>> avtext mailing list > >>> avtext@ietf.org > >>> https://www.ietf.org/mailman/listinfo/avtext > >> > >> _______________________________________________ > >> avtext mailing list > >> avtext@ietf.org > >> https://www.ietf.org/mailman/listinfo/avtext From nobody Mon Jun 23 05:32:04 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B83DF1B2992 for ; Mon, 23 Jun 2014 05:32:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.301 X-Spam-Level: X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 aIjbG8aS6nhR for ; Mon, 23 Jun 2014 05:31:58 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09EC51B2AA3 for ; Mon, 23 Jun 2014 05:31:56 -0700 (PDT) X-AuditID: c1b4fb25-f79226d000004024-aa-53a81e3a38d8 Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E8.D2.16420.A3E18A35; Mon, 23 Jun 2014 14:31:54 +0200 (CEST) Received: from ESESSMB105.ericsson.se ([169.254.5.228]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0174.001; Mon, 23 Jun 2014 14:31:54 +0200 From: Bo Burman To: "avtext@ietf.org" Thread-Topic: PAUSE/RESUME draft updates Thread-Index: Ac+OwIFuBzkbNTqhREmBCTnE8XQ3+w== Date: Mon, 23 Jun 2014 12:31:53 +0000 Message-ID: Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.20] Content-Type: multipart/alternative; boundary="_000_BBE9739C2C302046BD34B42713A1E2A22E24B133ESESSMB105erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+Jvja6V3Ipgg0UTTC0+3rvB6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujLa/c1gKbupV/F34gqWB8ZBGFyMnh4SAiUTLkZ3sELaYxIV7 69m6GLk4hASOMkrcfrqLCcJZwiix+ewsJpAqNgENifk77jKC2CIC6hJ3pl9gA7GFBZQlOo9/ YoGIa0jsan/K3MXIAWTrSSy+WQkSZhFQlfja+h6snFfAV+JLw31WEJtRQFbi/vd7YK3MAuIS t57MZ4I4SEBiyZ7zzBC2qMTLx/9YIWxFiavTlzNB1OdLbDjcygwxU1Di5MwnLBMYhWYhGTUL SdksJGUQcR2JBbs/sUHY2hLLFr5mhrHPHHjMhCy+gJF9FaNocWpxUm66kbFealFmcnFxfp5e XmrJJkZgTBzc8lt1B+PlN46HGAU4GJV4eBW6lgcLsSaWFVfmHmKU5mBREuddeG5esJBAemJJ anZqakFqUXxRaU5q8SFGJg5OqQZGC9Ym59nfDj9m/1VS5iZ5vjPz0afzm1o2mFwstcy//7Xo w8qOT+Uy8qz/Hga2FRbPfhHAYryt9Uk706G8vLS9eyue/Lg1eSH7b50vSy49/pBv/f7WjrzH wRqHDJtvaLxTum0em3jt8oGD7u/fZ50w+VSf8fTzcu2kxhVZwq7tnDc3fJsgs1PfXYmlOCPR UIu5qDgRAFhyjXRqAgAA Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/Ki3hTlbjby5wyqfvlifh7TrwCKg Subject: [avtext] PAUSE/RESUME draft updates X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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: Mon, 23 Jun 2014 12:32:01 -0000 --_000_BBE9739C2C302046BD34B42713A1E2A22E24B133ESESSMB105erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I would like to learn the WG's opinion on removing text from section 5.1 "S= ignaling Technology Performance Comparison" of https://datatracker.ietf.org= /doc/draft-ietf-avtext-rtp-stream-pause/. Today that section is a fairly verbose performance comparison between SIP- = and RTCP-based signaling, which is part of the argumentation and conclusion= to use RTCP for RTP PAUSE/RESUME signaling purposes. That section could po= tentially be replaced by a much more compact summary, maybe a table, given = that the WG already decided to go for RTCP-based signaling. On the other ha= nd, the current text may be seen as containing useful information that shou= ld be kept for future reference. Should section 5.1 be kept as-is, or should it be replaced by a shorter tex= t (and possibly a table)? I've also found a mistake in section 6.5: TMMBN >0: Corresponds to a REFUSE indication when a media stream is requested to be paused with TMMBR 0. This statement is not correct, since the TMMBR 0 must unconditionally be fo= llowed according to CCM [RFC 5104]. It is thus not possible to refuse a PAU= SE when using TMMBR/TMMBN. I suggest to change this paragraph accordingly. = I also suggest to insert an explicit note in section 6.4 (REFUSE) that TMMB= N>0 cannot be used as REFUSE to a PAUSE that is sent using TMMBR 0. Cheers, Bo --_000_BBE9739C2C302046BD34B42713A1E2A22E24B133ESESSMB105erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable --_000_BBE9739C2C302046BD34B42713A1E2A22E24B133ESESSMB105erics_-- From nobody Tue Jun 24 05:25:00 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97FE31B28B3 for ; Tue, 24 Jun 2014 05:24:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 7MgCMSVSqiWN for ; Tue, 24 Jun 2014 05:24:55 -0700 (PDT) Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E01781B2896 for ; Tue, 24 Jun 2014 05:24:54 -0700 (PDT) X-AuditID: c1b4fb25-f79226d000004024-0e-53a96e148445 Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id E0.74.16420.41E69A35; Tue, 24 Jun 2014 14:24:53 +0200 (CEST) Received: from ESESSMB105.ericsson.se ([169.254.5.228]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0174.001; Tue, 24 Jun 2014 14:24:52 +0200 From: Bo Burman To: "avtext@ietf.org" Thread-Topic: Summary of proposed updates to RTP Taxonomy regarding CLUE terms Thread-Index: Ac+Pou08miJYxkr/T8OUGNOfhupvuQ== Date: Tue, 24 Jun 2014 12:24:51 +0000 Message-ID: Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.147] Content-Type: multipart/alternative; boundary="_000_BBE9739C2C302046BD34B42713A1E2A22E24B826ESESSMB105erics_" MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOLMWRmVeSWpSXmKPExsUyM+Jvja5o3spgg1vnWS0+3rvB6sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujMWTzjIWbPeomLP1AGMD40e7LkZODgkBE4nJ/bNYIGwxiQv3 1rN1MXJxCAkcZZS4+/ghlLOEUeLg7J1MIFVsAhoS83fcZQSxRQTUJe5Mv8AGYgsLeEqsnHeK BSIeIPHn1WRmCFtP4sj1FWBxFgFViZvHX4DN4RXwlfh59A5YnFFAVuL+93tgNrOAuMStJ/OZ IC4SkFiy5zwzhC0q8fLxP9YuRg4gW0li2tY0iPJ8iVez+lggRgpKnJz5hGUCo9AsJJNmISmb haQMIq4jsWD3JzYIW1ti2cLXzDD2mQOPmZDFFzCyr2IULU4tTspNNzLWSy3KTC4uzs/Ty0st 2cQIjImDW36r7mC8/MbxEKMAB6MSD69C9opgIdbEsuLK3EOM0hwsSuK8C8/NCxYSSE8sSc1O TS1ILYovKs1JLT7EyMTBKdXAWPraaEbyWVOR7qWnFJdfSS14XTnNLNftya0zpQHWorJFP3fc uLW/+N+PXb/eGQlfdLsZazjnsEP29qjDhWYbaiwuLc8JOWl/8XXoBpX9TWmPwmo2CT5pmSxx a3nX/0cTJRh1pV9e+yhjzzR/UeeM5sPa9x25yr889fzz+U8b38pZb+ZKcOf/N1ZiKc5INNRi LipOBACwQfzAagIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/S9UHoonCc-brGUCEuoaqGD-XL8k Subject: [avtext] Summary of proposed updates to RTP Taxonomy regarding CLUE terms X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 24 Jun 2014 12:24:58 -0000 --_000_BBE9739C2C302046BD34B42713A1E2A22E24B826ESESSMB105erics_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Apologies for the cross-post of information, but there has currently been a= discussion on the CLUE mailing list regarding text in the Taxonomy that re= fers to CLUE terms, which now seems to have concluded. This is a summary of= the proposed CLUE-related changes to be included in the next version of Ta= xonomy (soon to be sent out): 1. Media Capture is the CLUE term used for either a Taxonomy Media Ca= pture or a Media Source, depending on in which context the term is used. 2. Individual Encoding is the CLUE term used for the configuration in= formation needed to perform a Taxonomy Media Encoder transformation. 3. Capture Encoding is the CLUE term used for a Taxonomy Encoded Stre= am related to CLUE specific semantic information. 4. A CLUE Endpoint describes exactly one Taxonomy Participant and one= or more related End Points. 5. It should be clarified that a Taxonomy Participant can be associat= ed with several End Points, but an End Point can be associated to only one = Participant at any single point in time. 6. It should be clarified that a single synchronization context can b= e shared among several End Points associated with the same Participant, but= that a single End Point can handle several synchronization contexts. 7. Taxonomy should contain some text on Multipoint Control Unit (MCU)= , but not specifically for CLUE. It could for example say that it is the ce= ntral node in any type of star topology conference (likely with a reference= to topologies-update), and that it describes a Participant (conference foc= us) and one or more related End Points (sometimes one per conference Partic= ipant). Cheers, Bo --_000_BBE9739C2C302046BD34B42713A1E2A22E24B826ESESSMB105erics_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Apologies for the cross-post of information, but the= re has currently been a discussion on the CLUE mailing list regarding text = in the Taxonomy that refers to CLUE terms, which now seems to have conclude= d. This is a summary of the proposed CLUE-related changes to be included in the next version of Taxonomy (soon = to be sent out):

 

1.     &= nbsp; Media Capture is the CLUE term used for either a Ta= xonomy Media Capture or a Media Source, depending on in which context the t= erm is used.

2.     &= nbsp; Individual Encoding is the CLUE term used for the c= onfiguration information needed to perform a Taxonomy Media Encoder transfo= rmation.

3.     &= nbsp; Capture Encoding is the CLUE term used for a Taxono= my Encoded Stream related to CLUE specific semantic information.=

4.     &= nbsp; A CLUE Endpoint describes exactly one Taxonomy Part= icipant and one or more related End Points.

5.     &= nbsp; It should be clarified that a Taxonomy Participant = can be associated with several End Points, but an End Point can be associat= ed to only one Participant at any single point in time.

6.     &= nbsp; It should be clarified that a single synchronizatio= n context can be shared among several End Points associated with the same P= articipant, but that a single End Point can handle several synchronization = contexts.

7.     &= nbsp; Taxonomy should contain some text on Multipoint Con= trol Unit (MCU), but not specifically for CLUE. It could for example say th= at it is the central node in any type of star topology conference (likely w= ith a reference to topologies-update), and that it describes a Participant (conference focus) and one or more rel= ated End Points (sometimes one per conference Participant).

 

Cheers,

Bo

 

--_000_BBE9739C2C302046BD34B42713A1E2A22E24B826ESESSMB105erics_-- From nobody Fri Jun 27 00:33:58 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B18F11B3175; Fri, 27 Jun 2014 00:33:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham 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 npRgHomYA1oJ; Fri, 27 Jun 2014 00:33:55 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 62DB71B278A; Fri, 27 Jun 2014 00:33:55 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 5.5.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140627073355.19139.57207.idtracker@ietfa.amsl.com> Date: Fri, 27 Jun 2014 00:33:55 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/_YFGJylztHTw390NVcfbbrY73cA Cc: avtext@ietf.org Subject: [avtext] I-D Action: draft-ietf-avtext-rtp-grouping-taxonomy-02.txt X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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, 27 Jun 2014 07:33:56 -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 Working Group of the IETF. Title : A Taxonomy of Grouping Semantics and Mechanisms for Real-Time Transport Protocol (RTP) Sources Authors : Jonathan Lennox Kevin Gross Suhas Nandakumar Gonzalo Salgueiro Bo Burman Filename : draft-ietf-avtext-rtp-grouping-taxonomy-02.txt Pages : 41 Date : 2014-06-27 Abstract: The terminology about, and associations among, Real-Time Transport Protocol (RTP) sources can be complex and somewhat opaque. This document describes a number of existing and proposed relationships among RTP sources, and attempts to define common terminology for discussing protocol entities and their relationships. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-grouping-taxonomy/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-avtext-rtp-grouping-taxonomy-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-avtext-rtp-grouping-taxonomy-02 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 Fri Jun 27 00:49:09 2014 Return-Path: X-Original-To: avtext@ietfa.amsl.com Delivered-To: avtext@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B23061B2F2A for ; Fri, 27 Jun 2014 00:49:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham 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 b90obCh8ni6g for ; Fri, 27 Jun 2014 00:49:06 -0700 (PDT) Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 896481B3129 for ; Fri, 27 Jun 2014 00:49:05 -0700 (PDT) X-AuditID: c1b4fb30-f79da6d000006b80-a3-53ad21ef4993 Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id BD.54.27520.FE12DA35; Fri, 27 Jun 2014 09:49:03 +0200 (CEST) Received: from ESESSMB105.ericsson.se ([169.254.5.228]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.03.0174.001; Fri, 27 Jun 2014 09:49:03 +0200 From: Bo Burman To: "avtext@ietf.org" Thread-Topic: [avtext] I-D Action: draft-ietf-avtext-rtp-grouping-taxonomy-02.txt Thread-Index: AQHPkdoqBylV2jp1UUSeJtDcqtEA1puEkyIQ Date: Fri, 27 Jun 2014 07:49:03 +0000 Message-ID: References: <20140627073355.19139.57207.idtracker@ietfa.amsl.com> In-Reply-To: <20140627073355.19139.57207.idtracker@ietfa.amsl.com> Accept-Language: sv-SE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [153.88.183.19] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+Jvje57xbXBBvf3aVt8vHeD1YHRY8mS n0wBjFFcNimpOZllqUX6dglcGXv/fGQqOC5SsXvaG6YGxgaBLkZODgkBE4n/D6ayQ9hiEhfu rWfrYuTiEBI4yigxrXEJC4SzhFFi+4c5TCBVbAIaEvN33GUEsUUE1CXuTL8A1MHBISwQJPGo QRXEFBEIljg2Jx/CNJKYty0LpJhFQFXi5frfYKt4BXwltk98wgZiCwk4Slw+fBUszingJDH9 4kIWEJtRQFbi/vd7YDazgLjErSfzmSDOFJBYsuc8M4QtKvHy8T9WCFtRov1pAyNEvY7Egt2f 2CBsbYllC18zQ+wVlDg58wnLBEbRWUjGzkLSMgtJyywkLQsYWVYxihanFiflphsZ6aUWZSYX F+fn6eWllmxiBMbDwS2/DXYwvnzueIhRgINRiYd3QfyaYCHWxLLiytxDjNIcLErivAvPzQsW EkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwLhMPlXyYfYcvq8st9u5np0v+pa8akLjlQ6LOLVF 8uuK3xUeDTn8b83fDg35i6d4fyk7NR8Sy+SUfyXwr2XLFqGXp3rMGorO/jzb++vZytsCCwrO XRD5qWnjxb2hOUH7iVq0d+np7VfFbzIw63cv6LSOqhFczb9yx5dsRi6Lt8z1Z57uuG88Q1iJ pTgj0VCLuag4EQBvJ85QaAIAAA== Archived-At: http://mailarchive.ietf.org/arch/msg/avtext/2RL5dJJOS6YKyX2LrFV3VcDMyJ4 Subject: Re: [avtext] I-D Action: draft-ietf-avtext-rtp-grouping-taxonomy-02.txt X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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: Fri, 27 Jun 2014 07:49:07 -0000 This version is significantly re-worked according to suggestions in London = and discussions on the list, and the changes are summarized in the document= appendix. Worth noting are the re-naming of "Packet Stream" to the more specific "RTP= Stream" (impacting many other names as well), removing the topology sectio= n to avoid any conflict with topologies-update, and the addition of a new s= ection describing existing terms in taxonomy wording. /Bo > -----Original Message----- > From: avtext [mailto:avtext-bounces@ietf.org] On Behalf Of internet-draft= s@ietf.org > Sent: den 27 juni 2014 09:34 > To: i-d-announce@ietf.org > Cc: avtext@ietf.org > Subject: [avtext] I-D Action: draft-ietf-avtext-rtp-grouping-taxonomy-02.= txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts direct= ories. > This draft is a work item of the Audio/Video Transport Extensions Workin= g Group of the IETF. >=20 > Title : A Taxonomy of Grouping Semantics and Mechanisms= for Real-Time Transport Protocol (RTP) Sources > Authors : Jonathan Lennox > Kevin Gross > Suhas Nandakumar > Gonzalo Salgueiro > Bo Burman > Filename : draft-ietf-avtext-rtp-grouping-taxonomy-02.txt > Pages : 41 > Date : 2014-06-27 >=20 > Abstract: > The terminology about, and associations among, Real-Time Transport > Protocol (RTP) sources can be complex and somewhat opaque. This > document describes a number of existing and proposed relationships > among RTP sources, and attempts to define common terminology for > discussing protocol entities and their relationships. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-grouping-taxonomy/ >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-avtext-rtp-grouping-taxonomy-02 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-avtext-rtp-grouping-taxonom= y-02 >=20 >=20 > Please note that it may take a couple of minutes from the time of submiss= ion until the htmlized version and diff are > available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > avtext mailing list > avtext@ietf.org > https://www.ietf.org/mailman/listinfo/avtext