Re: [homegate] HOMENET working group proposal

ken carlberg <> Tue, 12 July 2011 14:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 395E921F8700 for <>; Tue, 12 Jul 2011 07:33:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.158
X-Spam-Status: No, score=-2.158 tagged_above=-999 required=5 tests=[AWL=0.441, BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id cUAIjMNVfiWR for <>; Tue, 12 Jul 2011 07:33:08 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 4926821F86FB for <>; Tue, 12 Jul 2011 07:33:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default;; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-Source:X-Source-Args:X-Source-Dir; b=mRHr4N1mRmCdUJiZrtZDyNU6vUNwbM9xPZeUSvBSSgduRmwnIqKMhe5eWzsSaMchB3JSl1RdDfkrhbJ6y2dbRWpUQoUW7FGRHYNSb4GXq8XxRWCZ2nEjLATe+B9QLJD9;
Received: from ([]:61305 helo=[]) by with esmtpa (Exim 4.69) (envelope-from <>) id 1Qge1C-00014M-JP; Tue, 12 Jul 2011 14:32:58 +0000
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: ken carlberg <>
In-Reply-To: <>
Date: Tue, 12 Jul 2011 10:33:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Fred Baker <>
X-Mailer: Apple Mail (2.1084)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
Subject: Re: [homegate] HOMENET working group proposal
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Broadband Home Gateway Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 12 Jul 2011 14:33:09 -0000


> 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.

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.