Re: [homegate] HOMENET working group proposal

Randy Turner <rturner@amalfisystems.com> Wed, 13 July 2011 12:58 UTC

Return-Path: <rturner@amalfisystems.com>
X-Original-To: homegate@ietfa.amsl.com
Delivered-To: homegate@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1783221F853A for <homegate@ietfa.amsl.com>; Wed, 13 Jul 2011 05:58:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level:
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2JCWt5kOq971 for <homegate@ietfa.amsl.com>; Wed, 13 Jul 2011 05:58:05 -0700 (PDT)
Received: from omr3.networksolutionsemail.com (omr3.networksolutionsemail.com [205.178.146.53]) by ietfa.amsl.com (Postfix) with ESMTP id 848C321F856F for <homegate@ietf.org>; Wed, 13 Jul 2011 05:58:05 -0700 (PDT)
Received: from cm-omr2 (mail.networksolutionsemail.com [205.178.146.50]) by omr3.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id p6DCw4lV010052 for <homegate@ietf.org>; Wed, 13 Jul 2011 08:58:04 -0400
X-Authenticated-IP: 174.254.69.245
Received: from [174.254.69.245] ([174.254.69.245:58283] helo=[10.247.147.234]) by cm-omr2 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id 56/DC-04012-C569D1E4; Wed, 13 Jul 2011 08:58:04 -0400
References: <4E0AE696.4020603@piuha.net> <7FC8F60B-469E-4635-B5C0-4FD6B9AC30F8@g11.org.uk> <3C0C6442-E0A9-4B44-80AB-2BCDFA029D6B@cisco.com> <4D8BC195-1251-4E9E-A7A5-46EB64A1678E@g11.org.uk> <DB7C38AB-F2C0-4C03-A8AC-BD1A49FCE93D@townsley.net>
In-Reply-To: <DB7C38AB-F2C0-4C03-A8AC-BD1A49FCE93D@townsley.net>
Mime-Version: 1.0 (iPhone Mail 8E401)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <8191C026-8791-4320-ABDA-A9EFB9B8458E@amalfisystems.com>
X-Mailer: iPhone Mail (8E401)
From: Randy Turner <rturner@amalfisystems.com>
Date: Wed, 13 Jul 2011 05:58:02 -0700
To: Mark Townsley <mark@townsley.net>
Cc: "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] HOMENET working group proposal
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homegate>, <mailto:homegate-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homegate>
List-Post: <mailto:homegate@ietf.org>
List-Help: <mailto:homegate-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homegate>, <mailto:homegate-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 12:58:06 -0000

+1 on the self-configuring of parameters

Randy

On Jul 13, 2011, at 5:07 AM, Mark Townsley <mark@townsley.net>; wrote:

> 
> On Jul 12, 2011, at 4:33 PM, ken carlberg wrote:
> 
>> Fred,
>> 
>>> I think that the need is felt in home, SOHO, and hotel (eg, broadband last mile) networks, and suggestions I have made along such lines have focused on them. However, the topic is closer to the charter of tsvwg IMHO, except in the ways that it manifests in broadband interfaces (the fact of the router, modem, CMTS/DSLAM, and upstream router being separate entities with separate buffers). The problem is in essence that ECN/AQM is generally not implemented in such networks, in part because there is a sense on the carrier side that loss is a bad thing, and in part because tuning the algorithms can be a pain. What the Georgia Tech folks have worked out, as much as anything, is an acceptable configuration driven by user perceptions rather than research optimizations (eg, for them it's not about finding the absolute knee of the curve and making the combined queue be as thin as possible, but finding a pragmatic solution that is predictable and acceptable to the typical user).
>> 
>> given that a lot of these boxes are linux-based, is it a case of not being implemented, or simply not being turned on in the shipped image?  And if the latter, then perhaps Homegate/Homenet offers us a means of configuring ECN/AQM.
> 
> Certainly, a primary homenet requirement would be that the parameters configure themselves so that a user does not have to. 
> 
> - Mark
> 
>> 
>> And I agree, the algorithms would be something that is advanced in TSVWG.  And we're also in agreement that the home/SOHO/hotel segment is just one part of where bufferbloat can manifest itself.
>> 
>> -ken
>> 
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
> 
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate
>