From iesg-secretary@ietf.org Tue Jan 21 06:21:08 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 747CD1A00A7; Tue, 21 Jan 2014 06:21:08 -0800 (PST) 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 w0CuUjuYolTj; Tue, 21 Jan 2014 06:21:07 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E96E1A010D; Tue, 21 Jan 2014 06:21:03 -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: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140121142103.25736.36009.idtracker@ietfa.amsl.com> Date: Tue, 21 Jan 2014 06:21:03 -0800 Cc: avtext mailing list , avtext chair , RFC Editor Subject: [avtext] Protocol Action: 'Support for Multiple Clock Rates in an RTP Session' to Proposed Standard (draft-ietf-avtext-multiple-clock-rates-11.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: Tue, 21 Jan 2014 14:21:08 -0000 The IESG has approved the following document: - 'Support for Multiple Clock Rates in an RTP Session' (draft-ietf-avtext-multiple-clock-rates-11.txt) as Proposed Standard This document is the product of the Audio/Video Transport Extensions Working Group. The IESG contact persons are Gonzalo Camarillo and Richard Barnes. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-avtext-multiple-clock-rates/ Technical Summary This document clarifies the RTP specification when different clock rates are used in an RTP session. It also provides guidance on how to interoperate with legacy RTP implementations that use multiple clock rates. It updates RFC 3550. Working Group Summary The document went through a working group last call. There were comments and the document was updated to resolve all comments. The work began in the context of the AVT working group, following a mailing list discussion in which several problems in RFC 3550 became clear. The work became a work item of the AVTEXT working group following the split of AVT. Document Quality The document got good reviews from AVText members. Several existing implementations implement the behavior recommended by the draft. In order to ensure the correctness of the document's recommendations about interoperability with legacy implementations, a review of existing RTP stack behavior was performed at SIPit 26. Personnel The Document Shepherd is Jonathan Lennox. The Responsible Area Director is Gonzalo Camarillo. From iesg-secretary@ietf.org Tue Jan 21 11:15:49 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 C3E521A018E; Tue, 21 Jan 2014 11:15:49 -0800 (PST) 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 9kv4KVVK2Ky7; Tue, 21 Jan 2014 11:15:48 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E101A019F; Tue, 21 Jan 2014 11:15:48 -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: 4.90.p2 Auto-Submitted: auto-generated Precedence: bulk Sender: Message-ID: <20140121191547.6904.47817.idtracker@ietfa.amsl.com> Date: Tue, 21 Jan 2014 11:15:47 -0800 Cc: avtext@ietf.org Subject: [avtext] Last Call: (Duplicating RTP Streams) to Proposed Standard X-BeenThere: avtext@ietf.org X-Mailman-Version: 2.1.15 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: Tue, 21 Jan 2014 19:15:50 -0000 The IESG has received a request from the Audio/Video Transport Extensions WG (avtext) to consider the following document: - 'Duplicating RTP Streams' 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 2014-02-04. 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 Packet loss is undesirable for real-time multimedia sessions, but can occur due to congestion, or other unplanned network outages. This is especially true for IP multicast networks, where packet loss patterns can vary greatly between receivers. One technique that can be used to recover from packet loss without incurring unbounded delay for all the receivers is to duplicate the packets and send them in separate redundant streams. This document explains how Real-time Transport Protocol (RTP) streams can be duplicated without breaking RTP or RTP Control Protocol (RTCP) rules. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-duplication/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-duplication/ballot/ The following IPR Declarations may be related to this I-D: http://datatracker.ietf.org/ipr/1656/ From keith.drage@alcatel-lucent.com Wed Jan 29 16:36:46 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 1CFB41A03F8 for ; Wed, 29 Jan 2014 16:36:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.9 X-Spam-Level: X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] 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 9-yte_eRMQhb for ; Wed, 29 Jan 2014 16:36:44 -0800 (PST) Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id F2C3D1A041C for ; Wed, 29 Jan 2014 16:36:43 -0800 (PST) Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0U0adMJ013648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 29 Jan 2014 18:36:40 -0600 (CST) Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0U0acC6005685 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Thu, 30 Jan 2014 01:36:38 +0100 Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Thu, 30 Jan 2014 01:36:38 +0100 From: "DRAGE, Keith (Keith)" To: "avtext@ietf.org" Thread-Topic: draft-ietf-avtext-rtp-grouping-taxonomy-00 Thread-Index: Ac8dU1Voeb6dcTfdT9S2qN1Oa7Qzaw== Date: Thu, 30 Jan 2014 00:36:37 +0000 Message-ID: <949EF20990823C4C85C18D59AA11AD8B12572E@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.239.27.38] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [avtext] draft-ietf-avtext-rtp-grouping-taxonomy-00 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: Thu, 30 Jan 2014 00:36:46 -0000 We could do with a few people reading the above draft and identifying omiss= ions, open issues, or corrections, so the editors can get a new version out= prior to the AVTEXT meeting in London. https://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-grouping-taxonomy/ In particular, those of you who have drafts that might use some of this ter= minology. Regards Keith= From alex@vidyo.com Thu Jan 30 11:53:53 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 EA7191A04B3 for ; Thu, 30 Jan 2014 11:53:53 -0800 (PST) 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 HCmabXMZl8sg for ; Thu, 30 Jan 2014 11:53:49 -0800 (PST) Received: from server209.appriver.com (server209e.appriver.com [8.31.233.120]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6611A0489 for ; Thu, 30 Jan 2014 11:53:48 -0800 (PST) X-Note-AR-ScanTimeLocal: 1/30/2014 2:53:44 PM 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-32/SG:2 1/30/2014 2:53:19 PM X-GBUdb-Analysis: 0, 162.209.16.214, Ugly c=0.878908 p=-0.964815 Source White X-Signature-Violations: 0-0-0-7588-c X-Note-419: 31.201 ms. Fail:0 Chk:1347 of 1347 total X-Note: SCH-CT/SI:0-1347/SG:1 1/30/2014 2:53:39 PM X-Note: Spam Tests Failed: X-Country-Path: ->UNITED STATES->LOCAL 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: G327 G328 G329 G330 G334 G335 G445 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.2) with ESMTPS id 93850330 for avtext@ietf.org; Thu, 30 Jan 2014 14:53:44 -0500 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; Thu, 30 Jan 2014 13:53:43 -0600 From: Alex Eleftheriadis To: "avtext@ietf.org" Thread-Topic: [AVTCORE] draft-ietf-avtext-rtp-grouping-taxonomy-00 Thread-Index: AQHPHfT6eb6dcTfdT9S2qN1Oa7Qzaw== Date: Thu, 30 Jan 2014 19:53:42 +0000 Message-ID: References: <949EF20990823C4C85C18D59AA11AD8B125741@FR712WXCHMBA11.zeu.alcatel-lucent.com> In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B125741@FR712WXCHMBA11.zeu.alcatel-lucent.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [135.11.8.183] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [avtext] [AVTCORE] draft-ietf-avtext-rtp-grouping-taxonomy-00 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: Thu, 30 Jan 2014 19:53:54 -0000 On Jan 29, 2014, at 7:41 PM, "DRAGE, Keith (Keith)" wrote: > To all potential users of the taxonomy document in other working groups. >=20 > We could do with a few people reading the above draft and identifying omi= ssions, open issues, or corrections, so the editors can get a new version o= ut prior to the AVTEXT meeting in London. >=20 > https://datatracker.ietf.org/doc/draft-ietf-avtext-rtp-grouping-taxonomy/ >=20 > In particular, those of you who have drafts that might use some of this t= erminology. >=20 > Please respond to the avtext list. [snip] I did a quick read-through. Comments below; hope they are useful. --- 2.1 Media Chain I would take the first sentence of 2.1, Media Chain, and use it to define m= edia: "a sequence of physical world stimulus represented in digital form" It is not evident from the text, but it should be recognized that it is pos= sible to have a a Media Source without a Physical Stimulus and associated M= edia Capture. Computer-generated content would fall under this category. 2.1.1 Physical Stimulus The definition does not need to use the receiver. Also, the word "capture" = is ambiguous. You probably mean measured using an appropriate sensor/transd= ucer and converted in digital form. 2.1.2 Media Capture Should not use "captured" in the definition itself (circular definition). I= would use: "The process of transforming the Physical Stimulus into digital= form using an appropriate sensor/transducer." 2.1.6 Media Encoder In addition to hierarchical encoding, such as the one used in H.264 SVC, it= is also possible to have what is called multiple description coding. In th= is case you have two independently encoded streams, each one complementing = the other. One simple example would be taken the even and odd samples of an= audio stream, and forming two independently encoded audio streams (each at= half the sampling rate). If you receive either you can decode; if you rece= ive both you can decode at full quality.=20 The section should also mention that for completeness. I am not aware of an= y commercially available encoder that uses MDC today.=20 2.1.9 Media Packetizer The terms SST and MST were defined as Single Session Transmission and Multi= -Session Transmission, respectively, in RFC 6190. I understand the argument= s for switching session with stream, but I think re-defining them now only = creates confusion (plus the new terms do not appear to be drop-in replaceme= nts for RFC 6190 anyway, since Multi-Session in Single-Stream was not antic= ipated in RFC 6190). =20 2.1.20 Media Decoder The way the system is presented, with 2.1.18 Media Depacketizer as an indep= endent component, you do not foresee that the media decoder may perform con= cealment. There may be much tighter coupling between the components that su= ggested here (ILP concepts etc.).=20 4. Topologies and Communication Entities I think here you should cite the new topologies update (http://tools.ietf.o= rg/html/draft-ietf-avtcore-rtp-topologies-update-01), and mention that ther= e are topologies that are not included in this brief summary. Otherwise it = appears that the section tries to be exhaustive - and it clearly is not. --Alex From georgehanes@hushmail.com Thu Jan 30 14:04:49 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 527D01A0489 for ; Thu, 30 Jan 2014 14:04:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.323 X-Spam-Level: X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RP_MATCHES_RCVD=-0.535, SPF_HELO_NEUTRAL=0.112, 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 7WJCTJf8Jid4 for ; Thu, 30 Jan 2014 14:04:47 -0800 (PST) Received: from smtp3.hushmail.com (smtp3a.hushmail.com [65.39.178.201]) by ietfa.amsl.com (Postfix) with ESMTP id C4DBF1A04B2 for ; Thu, 30 Jan 2014 14:04:47 -0800 (PST) Received: from smtp3.hushmail.com (smtp3a.hushmail.com [65.39.178.201]) by smtp3.hushmail.com (Postfix) with SMTP id 8B64EE02CC for ; Thu, 30 Jan 2014 22:04:44 +0000 (UTC) Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52]) by smtp3.hushmail.com (Postfix) with ESMTP for ; Thu, 30 Jan 2014 22:04:44 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 22C916018A; Thu, 30 Jan 2014 22:04:44 +0000 (UTC) MIME-Version: 1.0 Date: Thu, 30 Jan 2014 17:04:43 -0500 To: avtext@ietf.org From: georgehanes@hushmail.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20140130220444.22C916018A@smtp.hushmail.com> Subject: [avtext] Be cautious of this computer science conference 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: Thu, 30 Jan 2014 22:11:31 -0000 Be cautious of this computer science conference If you have any thought of attending the world’s biggest f-a-k-e conference in computer science http://www.world-academy-of-science.org you should visit any websites below https://sites.google.com/site/worlddump1 or https://sites.google.com/site/dumpconf https://sites.google.com/site/moneycomp1 https://sites.google.com/site/worlddump4 The organizer of this conference is H-amid A-rabnia http://www.cs.uga.edu/~hra a professor from University of Georgia, Athens, US. He already earned millions of dollars from the registration fee. He recently started a new conference CSCI due to his hunger for money http://www.americancse.org He did not reveal the reviews and reviewers' information for all the papers he received, despite repeated requests and challenges. The reason for his failure is there are no reviews and reviewers and he just cheated the research community for more than a decade by announcing that each draft paper is reviewed by two experts. We challenge him to publish these details at the conference website. Where are your experts? Where are your reviews? Soon he comes up with a story announcing that he lost all the information having reviews and reviewers because of computer crash or theft. DBLP stopped indexing these conferences since 2011 and displayed an explicit message; "The DBLP Advisory Board decided to discontinue indexing of this conference series". Visit http://www.informatik.uni-trier.de/~ley/db/conf/biocomp/index.html as a sample. He was forced to remove his name, the university of Georgia name, and university of Georgia email address from the conference’s contact page because the University has banned him from doing that. Do not spoil your resume by publishing in this conference. Apologies for posting to multiple mailing lists. Spreading the news is the only way to stop this conference from harming innocent researchers. Respectfully, Many researchers cheated by these conferences