From rjsparks@nostrum.com Tue May 8 09:10:53 2012 Return-Path: X-Original-To: rai@ietfa.amsl.com Delivered-To: rai@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B503E21F85C3 for ; Tue, 8 May 2012 09:10:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.654 X-Spam-Level: X-Spam-Status: No, score=-102.654 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t7Gymk6hYSZZ for ; Tue, 8 May 2012 09:10:53 -0700 (PDT) Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BC56621F85C0 for ; Tue, 8 May 2012 09:10:52 -0700 (PDT) Received: from unexplicable.local (pool-71-244-61-199.dllstx.fios.verizon.net [71.244.61.199]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q48GAnY0012695 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 8 May 2012 11:10:50 -0500 (CDT) (envelope-from rjsparks@nostrum.com) Message-ID: <4FA94589.3010207@nostrum.com> Date: Tue, 08 May 2012 11:10:49 -0500 From: Robert Sparks User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: rai@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Received-SPF: pass (nostrum.com: 71.244.61.199 is authenticated by a trusted mechanism) Subject: [RAI] Please review X-BeenThere: rai@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Real-time Applications and Infrastructure \(RAI\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2012 16:10:53 -0000 Folks - There was a BoF in Paris about enabling remote participation at IETF meetings. The tools that are being discussed are by their nature Real-Time oriented. Please review the draft below, and send feedback to the vmeet@ietf.org list RjS > From: Paul Hoffman > Date: May 7, 2012 11:02:25 PM EDT > To:vmeet@ietf.org > Subject: [vmeet] Requirements document -04 > > First off, my apologies for taking so long to get this out after Paris. There was much wider disagreement on goals, audiences, and intended requirements than I expected (and I was already skeptical...). I thrashed through the contributions from the BoF, the many hallway conversations, and threads that were opened after Paris. The result of trying to find rough consensus from all of that is draft -04, available at. The diff from -03 is mostly gibberish because of me moving a huge amount of background text to an appendix. > > Please comment on major topics in separate threads (or at least don't be offended if I split your comments into appropriately-named threads...). > > --Paul Hoffman From fluffy@iii.ca Fri May 25 09:07:52 2012 Return-Path: X-Original-To: rai@ietfa.amsl.com Delivered-To: rai@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8D321F8674 for ; Fri, 25 May 2012 09:07:52 -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=[AWL=-0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_SUB_RAND_LETTRS4=0.799] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xp9FTDPCF6c4 for ; Fri, 25 May 2012 09:07:50 -0700 (PDT) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 52ED921F8483 for ; Fri, 25 May 2012 09:07:50 -0700 (PDT) Received: from [192.168.4.100] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D34C122E259 for ; Fri, 25 May 2012 12:07:48 -0400 (EDT) From: Cullen Jennings Content-Type: multipart/alternative; boundary=Apple-Mail-8-1025097836 Date: Fri, 25 May 2012 10:07:46 -0600 References: <4AAE17A6-0E0A-492C-96D0-C7D0DBF5C78F@netapp.com> To: rai@ietf.org Message-Id: <31175B29-7E5B-42D5-9850-7F5AF4457C87@iii.ca> Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [RAI] Call for Papers: IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication, July 28, 2012 Vancouver, Canada X-BeenThere: rai@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: "Real-time Applications and Infrastructure \(RAI\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2012 16:07:52 -0000 --Apple-Mail-8-1025097836 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii >=20 >=20 > IAB / IRTF Workshop on > Congestion Control for Interactive > Real-Time Communication > July 28, 2012 > Vancouver, Canada > =20 > The IAB and IRTF will hold a workshop on Congestion Control for = Interactive Real-Time Communication" in Vancouver, Canada on Saturday, = July 28th, 2012 prior to the IETF-84 meeting (see = http://www.ietf.org/meeting/84/index.html). Participation at the = workshop is free of charge. There is no requirement to either register = with or attend the IETF-84 meeting that follows the workshop. > =20 > The workshop organizers would like to foster a discussion on: > What are appropriate congestion signals to use for interactive media = and data? > What existing congestion control algorithms are appropriate for = interactive media and data? What properties would be desirable in new = congestion control algorithms? > Measurement and/or simulations of new congestion signals (e.g., = delay-based) and their interaction with existing congestion control = mechanisms. > What are good available techniques for adjusting sending rates for = interactive media and data? What are the limits of those techniques? = What properties would be desirable in new techniques? > What application-specific considerations have to be taken into = account? > How can we ensure that real-time communications are well-behaved with = respect to other Internet applications while still providing good = quality? > What should the IETF and/or IRTF do? > The organizers seek position papers on any or all of these topics, as = well as other topics related to congestion control for interactive = realtime media. > =20 > Every prospective workshop participant must submit a position paper = containing a name and an email address. Authors of accepted papers will = be invited to the workshop. Papers up to 3 pages, formatted in HTML, = PDF, or plain text (for example, as a submitted Internet-Draft) are = ideal. Accepted position papers will be published. Additional details = about the meeting venue will be provided to authors of accepted papers. > Important Dates >=20 > Position paper submission deadline: June 23, 2012 > Notification to paper authors: June 30, 2012 > Workshop date: July 28, = 2012 > Additional Details >=20 > Additional details on the workshop as well as the submission process = is available at http://www.iab.org/cc-workshop/ > Contact >=20 > To sponsors: If you are interested to help us working towards better = interactive media congestion control mechanisms on the Internet (such as = by making a contribution towards catering costs and room rental), please = contact us! >=20 > In case of questions please send email to mary.ietf.barnes at = gmail.com. > =20 --Apple-Mail-8-1025097836 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii


IAB / IRTF Workshop on
Congestion Control for = Interactive
Real-Time Communication

July 28, = 2012
Vancouver, Canada

 
The IAB and IRTF = will hold a workshop on Congestion Control for Interactive Real-Time = Communication" in Vancouver, Canada on Saturday, July 28th, 2012 prior = to the IETF-84 meeting (see ).  Participation at the workshop is free of charge. There = is no requirement to either register with or attend the IETF-84 meeting = that follows the workshop.
  1. What are = appropriate congestion signals to use for interactive media and = data?
  2. What existing congestion control = algorithms are appropriate for interactive media and data? What = properties would be desirable in new congestion control = algorithms?
  3. What are = good available techniques for adjusting sending rates for interactive = media and data? What are the limits of those techniques? What properties = would be desirable in new techniques?
  4. What = application-specific considerations have to be taken into = account?
  5. How can we = ensure that real-time communications are well-behaved with respect to = other Internet applications while still providing good = quality?
  6. What = should the IETF and/or IRTF do?

Important = Dates

Additional Details