From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, codel@lists.bufferbloat.net
Subject: Re: [Codel] [multipathtcp] Fwd: IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication, July 28, 2012 Vancouver, Canada
Date: Fri, 25 May 2012 20:34:40 +0100 [thread overview]
Message-ID: <CAA93jw7S3U50vr7a71MhEF7YWvThLBi09LDN+r8Zsij3KYmWpg@mail.gmail.com> (raw)
In-Reply-To: <AB4A214E-2735-4AD4-AC50-903596B6C63D@townsley.net>
This seems interesting. I'm too tired to think about it right now. Anyone?
Paper submission deadline is june 23
> 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 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.
>
> 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.
>
> 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
>
> Position paper submission deadline: June 23, 2012
> Notification to paper authors: June 30, 2012
> Workshop date: July 28, 2012
>
> Additional Details
>
> Additional details on the workshop as well as the submission process is
> available at http://www.iab.org/cc-workshop/
>
> Contact
>
> 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!
>
> In case of questions please send email to mary.ietf.barnes at gmail.com.
>
>
>
>
> _______________________________________________
> multipathtcp mailing list
> multipathtcp@ietf.org
> https://www.ietf.org/mailman/listinfo/multipathtcp
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
parent reply other threads:[~2012-05-25 19:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AB4A214E-2735-4AD4-AC50-903596B6C63D@townsley.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7S3U50vr7a71MhEF7YWvThLBi09LDN+r8Zsij3KYmWpg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox