From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 191CC21F1D6 for ; Tue, 4 Jun 2013 10:55:01 -0700 (PDT) Received: by mail-qa0-f44.google.com with SMTP id j8so393268qah.17 for ; Tue, 04 Jun 2013 10:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4O/hiaD550oZIt0HI6vuOgc8kspNLZNd8izbv6Em2uo=; b=dW78p9rAqU189QtKPLSd0D+TeC6onMY+AHMia8kDgndnfmUcX2N5bn0s67Aphq590I 4ELUEZLRUCBPpQCwmnxyqNxQnnyCwqp21LdCcg6p4NliS25hpHhQKi9QZUBr3vlM2oN1 7NacvgOld+Kc0tLn+9bE0M94q+moPskEVcVu3hO41x4JV7Io9bXbsN2T7jcJPHyL8Yt9 9YOS6QCLLuEgoRp4XdqClLcJArACJAyxkd4buBqXCB08d1U6IUKwsplVH74nvgV1Jaqe 4pSoy9q9TxjgMRQOThaVFdTUZHwP6QebQzRizQ0HI6tuEYNo4deO+rBSRkvydQfHJSMd um6Q== MIME-Version: 1.0 X-Received: by 10.224.137.73 with SMTP id v9mr24449133qat.59.1370368499928; Tue, 04 Jun 2013 10:54:59 -0700 (PDT) Sender: gettysjim@gmail.com Received: by 10.49.2.67 with HTTP; Tue, 4 Jun 2013 10:54:59 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 Jun 2013 13:54:59 -0400 X-Google-Sender-Auth: U-CXPj_oAg6pkjrxSKKi6Vu1DU8 Message-ID: From: Jim Gettys To: Dave Taht Content-Type: multipart/alternative; boundary=001a11c2dcc6a66f5f04de57c725 Cc: bloat Subject: Re: [Bloat] CFP: Workshop on Reducing Internet Latency X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jun 2013 17:55:01 -0000 --001a11c2dcc6a66f5f04de57c725 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 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" wrote: > >> This workshop may be of interest to folks here. >> >> Regards, >> Mat >> >> Workshop on Reducing Internet Latency >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> 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 worksh= op >> aims to galvanise action to fix that. All layers of the stack are in >> scope. >> >> Latency is an increasingly important topic for networking researchers an= d >> 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 kin= d, >> latency is a critical factor in determining end-user satisfaction and th= e >> 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 reductio= n >> 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=B9t controlling me, I=B9m controlling it. Ultimate= ly >> 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 submi= t >> short (up to 2 pages) position papers outlining their views on a specifi= c >> aspect of the overall scope. The emphasis here is on relevance and brevi= ty >> - 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 identifyi= ng >> 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 bein= g >> 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 > > --001a11c2dcc6a66f5f04de57c725 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
As = Dave says, it's really unfortunate to schedule this on top of LPC: that= basically prevents anyone =A0serious working on Linux networking attending= . I argue, that Linux is the most important OS right now to deal with, give= n that Android, most internet servers, and home routers are all Linux based= ). =A0Linux is also by far furthest along in dealing with the problem, and = moves fastest.

Location is suboptimal, but su= ch is life...
<= br>
I expect the dates w= ill cause heartburn for Andrew McGregor too, who we hope/expect will be inv= olved in fixing the Linux WiFi stack.

At a minim= um rescheduling might get a few people who actually influence code that is = shipping there.... =A0Increasing interactions between these communities wou= ld be really, really wise as Dave says.

For future reference, there ar= e 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, a= lways in Late January/early February in Austrailia or New Zealand). =A0Indi= vidual teams may have other meetings as well, but those are the big ones.
=A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0- Jim
=A0


On Wed, May 29, 2013 at 10:56 PM, Dave Taht <dave.taht@gmail.com&g= t; 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 p= referably 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
=A0 =A0 =A0 =A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 17-18 September 2013
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 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<= br> 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 an= y 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=B9t controlling me, I=B9m controlling it. Ultimately<= br> 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.&q= uot;

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:
- =A0 =A0 =A0 surveys of latency across all layers
- =A0 =A0 =A0 analyses of sources of latency and severity/variability
- =A0 =A0 =A0 the cost of latency problems to society and the economy, or t= he value of
fixing it
- =A0 =A0 =A0 principles for latency reduction across the stack
- =A0 =A0 =A0 solutions to reduce latency, including cross-layer
- =A0 =A0 =A0 deployment considerations for latency reducing technology
- =A0 =A0 =A0 benchmarking, accreditation, measurement and market compariso= n 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<= br> - 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<= br> 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@list= s.bufferbloat.net
= https://lists.bufferbloat.net/listinfo/bloat


_______________________________________________
Bloat mailing list
Bloat@lists.bufferbloat.net<= /a>
= https://lists.bufferbloat.net/listinfo/bloat


--001a11c2dcc6a66f5f04de57c725--