General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] CFP: Workshop on Reducing Internet Latency
Date: Tue, 4 Jun 2013 13:54:59 -0400	[thread overview]
Message-ID: <CAGhGL2BNJv+qu_ucUWa=hU=zTuweDohGdzwZRyKbJw_rPRoZ9g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4CR_vaC-PXPCEkNtohaXhHKEb=EBVc7Mhn4ONSGGAEQA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 6326 bytes --]

As Dave says, it's really unfortunate to schedule this on top of LPC: that
basically prevents anyone  serious working on Linux networking attending. I
argue, that Linux is the most important OS right now to deal with, given
that Android, most internet servers, and home routers are all Linux based).
 Linux is also by far furthest along in dealing with the problem, and moves
fastest.

Location is suboptimal, but such is life...

I expect the dates will cause heartburn for Andrew McGregor too, who we
hope/expect will be involved in fixing the Linux WiFi stack.

At a minimum rescheduling might get a few people who actually influence
code that is shipping there....  Increasing interactions between these
communities would be really, really wise as Dave says.

For future reference, there are three or so meetings a year that Linux
folks care about in general: LPC, the Kernel summit (if you're invited),
and LCA (linux Conf Australia, always in Late January/early February in
Austrailia or New Zealand).  Individual teams may have other meetings as
well, but those are the big ones.
                                     - Jim



On Wed, May 29, 2013 at 10:56 PM, Dave Taht <dave.taht@gmail.com> wrote:

> The proposed date for this event conflicts with linuxcon and the plumbers
> conference.
>
> http://events.linuxfoundation.org/events/linuxcon-north-america
>
> If it were held concurrently or sequentially with that and preferably in
> the same country... It would help.
> On May 29, 2013 7:13 AM, "Mat Ford" <ford@isoc.org> wrote:
>
>> This workshop may be of interest to folks here.
>>
>> Regards,
>> Mat
>>
>> Workshop on Reducing Internet Latency
>>         =====================================
>>                 17-18 September 2013
>>                 London, England
>>
>> Introduction and Scope
>> ----------------------
>> Latency tends to have been sacrificed in favour of headline bandwidth in
>> the way the Internet has been built. This two-day invitation-only workshop
>> aims to galvanise action to fix that. All layers of the stack are in
>> scope.
>>
>> Latency is an increasingly important topic for networking researchers and
>> Internet practitioners alike. Data from Google, Microsoft, Amazon and
>> others indicate that latency increases for interactive Web applications
>> result in less usage and less revenue from sales or advertising income.
>> Whether trying to provide platforms for Web applications, high-frequency
>> stock trading, multi-player online gaming or 'cloud' services of any kind,
>> latency is a critical factor in determining end-user satisfaction and the
>> success of products in the marketplace. Consequently, latency and
>> variation in latency are key performance metrics for services these days.
>>
>> But latency reduction is not just about increasing revenues for big
>> business. Matt Mullenweg of WordPress motivates work on latency reduction
>> well when he says, "My theory here is when an interface is faster, you
>> feel good. And ultimately what that comes down to is you feel in control.
>> The [application] isn¹t controlling me, I¹m controlling it. Ultimately
>> that feeling of control translates to happiness in everyone. In order to
>> increase the happiness in the world, we all have to keep working on this."
>>
>> Invitations to attend the workshop will depend on receipt of a position
>> paper. In a spirit of co-ordination across the industry, submissions are
>> encouraged from developers and network operators as well as the research
>> and standards communities.
>>
>> A wide range of latency related topics are in scope including, but not
>> limited to:
>> -       surveys of latency across all layers
>> -       analyses of sources of latency and severity/variability
>> -       the cost of latency problems to society and the economy, or the
>> value of
>> fixing it
>> -       principles for latency reduction across the stack
>> -       solutions to reduce latency, including cross-layer
>> -       deployment considerations for latency reducing technology
>> -       benchmarking, accreditation, measurement and market comparison
>> practices
>>
>> Submissions
>> -----------
>> This is an invitation-only workshop. Prospective participants must submit
>> short (up to 2 pages) position papers outlining their views on a specific
>> aspect of the overall scope. The emphasis here is on relevance and brevity
>> - you do not need to write a lot of text, just demonstrate that you have
>> thought about the problem space and have something interesting to say on
>> the topic.
>>
>> Please send position papers in PDF format to: latency@isoc.org
>>
>> Participant numbers will be limited to focus on discussion and identifying
>> actions rather than slideware.
>>
>> Accepted position papers will be made public. A report on the workshop
>> will be published after participants have agreed the content. Therefore,
>> it will be possible to state views during the workshop without them being
>> publicly attributed.
>>
>> Important Dates
>> ---------------
>> Position paper submission deadline: 23 June 2013
>> Paper acceptance notification: 28 June 2013
>> Workshop dates: 9am, Tuesday 17th to 5pm, Wednesday 18th September 2013
>> (subject to change)
>>
>> Program committee
>> -----------------
>> Mat Ford, Internet Society, co-chair
>> Bob Briscoe, BT, co-chair
>> Gorry Fairhurst, University of Aberdeen
>> Arvind Jain, Google
>> Jason Livingood, Comcast
>> Andrew McGregor, Google
>>
>> Workshop venue and other details
>> --------------------------------
>> Venue: London (exact location to be confirmed)
>> Registration fee: nil
>> Recommended accommodation: To be confirmed
>> The workshop is sponsored by the Internet Society, the RITE project,
>> Simula Research Labs and the TimeIn project. The Internet Society will
>> host a workshop dinner on the Tuesday evening.
>>
>>
>> _______________________________________________
>> Bloat mailing list
>> Bloat@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/bloat
>>
>>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>

[-- Attachment #2: Type: text/html, Size: 8127 bytes --]

  reply	other threads:[~2013-06-04 17:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29  9:54 Mat Ford
2013-05-30  2:56 ` Dave Taht
2013-06-04 17:54   ` Jim Gettys [this message]
2013-06-11 10:51 ` Matthew Ford
2013-12-09 12:49 ` Matthew Ford
2013-12-10  6:48   ` Mikael Abrahamsson
2013-12-10  7:54     ` Neil Davies
2013-12-10  8:04       ` [Bloat] ADSL2+ interleaving (Re: CFP: Workshop on Reducing Internet Latency) Mikael Abrahamsson
2013-12-10  8:07         ` Neil Davies
2013-12-10  8:48     ` [Bloat] CFP: Workshop on Reducing Internet Latency MUSCARIELLO Luca IMT/OLN
2013-12-10  9:36       ` Mikael Abrahamsson
2013-12-10  9:40         ` MUSCARIELLO Luca IMT/OLN

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGhGL2BNJv+qu_ucUWa=hU=zTuweDohGdzwZRyKbJw_rPRoZ9g@mail.gmail.com' \
    --to=jg@freedesktop.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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