From shalunov@bittorrent.com  Fri Aug  7 12:00:11 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E4EF3A6FB9; Fri,  7 Aug 2009 12:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJ7LzAL3ELtd; Fri,  7 Aug 2009 12:00:10 -0700 (PDT)
Received: from mail-fx0-f226.google.com (mail-fx0-f226.google.com [209.85.220.226]) by core3.amsl.com (Postfix) with ESMTP id C4FA23A6F58; Fri,  7 Aug 2009 11:59:51 -0700 (PDT)
Received: by fxm26 with SMTP id 26so1551444fxm.42 for <multiple recipients>; Fri, 07 Aug 2009 11:59:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.115.138 with SMTP id i10mr381743faq.82.1249671590093; Fri,  07 Aug 2009 11:59:50 -0700 (PDT)
In-Reply-To: <B00AFD87-145C-477D-982F-B66140E34B51@apple.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <B00AFD87-145C-477D-982F-B66140E34B51@apple.com>
Date: Fri, 7 Aug 2009 11:59:50 -0700
Message-ID: <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: james woodyatt <jhw@apple.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Fri, 07 Aug 2009 12:03:52 -0700
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] Amount of packet buffering in home gateways
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 07 Aug 2009 19:00:11 -0000

The manufacturers would benefit from specific guidance -- if we could
say that the right value were 10 packets or 10kB or 100ms worth of
serialization delay, rounded up to an integer number of packets or
some such, they could implement it.

Trouble is, we don't know any such right value.

What we do know are things like:

* Even a single TCP flow on a very slow link will need a few packets
worth of buffer so that it can keep something in flight and so that
fast retransmit works.  Different values have been argued to be right
from this perspective, from 6 packets to 10.

* Multiple TCP flows likely need more buffer, but probably not much
more, because it becomes increasingly acceptable for fast retransmit
to fail and timeout to fire when there are more connections -- they're
probably going to keep the link busy anyway.

* Any of that is way too much from the POV of delay experienced by
interactive apps (interactive =3D user waiting, so includes web).

The conjunction implies a lack of right value.  In absence of such,
best we could hope for is giving negative guidance.  We do know that a
64-kB buffer on a 128-kb/s link serves no purpose and could write it
up and explain why.  We'll end up with excessively conservative
recommendations this way, but maybe it's OK.

If we can't agree on specific guidance that people can use to size the
buffers and instead can only agree on general considerations like ones
I listed above, we might be better off not issuing any guidance at all
in the spirit of doing no harm.  After all, if we can't translate that
into bytes (which a manufacturer ultimately must), why should we
expect others to do so?




On Wed, Jul 29, 2009 at 1:59 AM, james woodyatt<jhw@apple.com> wrote:
> On Jul 29, 2009, at 10:34, Iljitsch van Beijnum wrote:
>>
>> The question is, what do we want to tell home gateway builders?
>
> We should tell them that forwarding IP flows from higher bandwidth links
> into much lower bandwidth links generally produces better results when
> queues are only large enough to handle common burst sizes without loss an=
d
> no larger. =A0Unnecessarily large transmission queues may introduce
> persistently and perversely high path latency on fully loaded low-bandwid=
th
> links, producing severe negative effects on application throughput.
>
> Beyond that, I don't know what else we should say. =A0Maybe it would help=
 to
> give some guidance for various common sub-IP links.
>
>
> --
> james woodyatt <jhw@apple.com>
> member of technical staff, communications engineering
>
>
>



--=20
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com

From lars.eggert@nokia.com  Sat Aug  8 00:29:40 2009
Return-Path: <lars.eggert@nokia.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2DD0C3A6A4F; Sat,  8 Aug 2009 00:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50-4TTXlRRTF; Sat,  8 Aug 2009 00:29:39 -0700 (PDT)
Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id 8BFE63A6BC1; Sat,  8 Aug 2009 00:29:21 -0700 (PDT)
Received: from [10.0.1.5] (cs95024.pp.htv.fi [212.90.95.24]) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n787T7j9052536 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 8 Aug 2009 10:29:07 +0300 (EEST) (envelope-from lars.eggert@nokia.com)
Message-Id: <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
From: Lars Eggert <lars.eggert@nokia.com>
To: Stanislav Shalunov <shalunov@bittorrent.com>
In-Reply-To: <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com>
Content-Type: multipart/signed; boundary=Apple-Mail-29-826407615; micalg=sha1; protocol="application/pkcs7-signature"
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sat, 8 Aug 2009 10:29:07 +0300
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <B00AFD87-145C-477D-982F-B66140E34B51@apple.com> <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com>
X-Mailer: Apple Mail (2.936)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (mail.fit.nokia.com [195.148.124.194]); Sat, 08 Aug 2009 10:29:07 +0300 (EEST)
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] [tsv-area] Amount of packet buffering in home gateways
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 08 Aug 2009 07:29:40 -0000

--Apple-Mail-29-826407615
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi,

these are all good points. I wanted to repeat something I said at the  
mike in Stockholm which I think is essential:

We cannot make a recommendation for a certain buffer size without also  
saying which queuing scheme we recommend for that buffer.

If we assume that FIFO queuing will be used, yes, the buffer size has  
a large, direct impact on the observable behavior. Not so for various  
AQM schemes (RED, etc.). Since my personal preference would be to  
recommend something smarter than FIFO, I don't see buffer size as very  
critical then. (Now, how to correctly parameterize an AQM scheme for a  
given link, *that* would be critical...)

Lars

On 2009-8-7, at 21:59, Stanislav Shalunov wrote:

> The manufacturers would benefit from specific guidance -- if we could
> say that the right value were 10 packets or 10kB or 100ms worth of
> serialization delay, rounded up to an integer number of packets or
> some such, they could implement it.
>
> Trouble is, we don't know any such right value.
>
> What we do know are things like:
>
> * Even a single TCP flow on a very slow link will need a few packets
> worth of buffer so that it can keep something in flight and so that
> fast retransmit works.  Different values have been argued to be right
> from this perspective, from 6 packets to 10.
>
> * Multiple TCP flows likely need more buffer, but probably not much
> more, because it becomes increasingly acceptable for fast retransmit
> to fail and timeout to fire when there are more connections -- they're
> probably going to keep the link busy anyway.
>
> * Any of that is way too much from the POV of delay experienced by
> interactive apps (interactive = user waiting, so includes web).
>
> The conjunction implies a lack of right value.  In absence of such,
> best we could hope for is giving negative guidance.  We do know that a
> 64-kB buffer on a 128-kb/s link serves no purpose and could write it
> up and explain why.  We'll end up with excessively conservative
> recommendations this way, but maybe it's OK.
>
> If we can't agree on specific guidance that people can use to size the
> buffers and instead can only agree on general considerations like ones
> I listed above, we might be better off not issuing any guidance at all
> in the spirit of doing no harm.  After all, if we can't translate that
> into bytes (which a manufacturer ultimately must), why should we
> expect others to do so?
>
>
>
>
> On Wed, Jul 29, 2009 at 1:59 AM, james woodyatt<jhw@apple.com> wrote:
>> On Jul 29, 2009, at 10:34, Iljitsch van Beijnum wrote:
>>>
>>> The question is, what do we want to tell home gateway builders?
>>
>> We should tell them that forwarding IP flows from higher bandwidth  
>> links
>> into much lower bandwidth links generally produces better results  
>> when
>> queues are only large enough to handle common burst sizes without  
>> loss and
>> no larger.  Unnecessarily large transmission queues may introduce
>> persistently and perversely high path latency on fully loaded low- 
>> bandwidth
>> links, producing severe negative effects on application throughput.
>>
>> Beyond that, I don't know what else we should say.  Maybe it would  
>> help to
>> give some guidance for various common sub-IP links.
>>
>>
>> --
>> james woodyatt <jhw@apple.com>
>> member of technical staff, communications engineering
>>
>>
>>
>
>
>
> -- 
> Stanislav Shalunov
> BitTorrent Inc
> shalunov@bittorrent.com
>
> personal: http://shlang.com


--Apple-Mail-29-826407615
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQDCCAvkw
ggJioAMCAQICEEi7WbMMKa2GLKFpQDaOBQEwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MDgyMzE3NDMzOVoXDTA5MDgyMzE3NDMz
OVowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy
dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF
AAOCAQ8AMIIBCgKCAQEAlwQVktJZCY89iU6jcW1XnZQN+aMgF2utCUT3H3ZKB5Jbet1SDWt0md/W
571bHjxtn9CfEJdochNL3l9f1WiJNdVbJ182557Ltx9SojqthpqtA0jKEqo2gqrf+raUj1demmo0
6ocsLqv046CrwidOp6k0RAfvkKPLhD4PD9Nk3oaZuxqBz1wY4u8Q83iWMArDeXiQxfNZnOBz5cDs
VvVjTjitm3VANkbD02tNkwl5AHw7htde4yH8hIwlfzqsAtHBEah3HyOvs9b+gHg2pFz9eS+HuotY
ZKycCweRs8NKXoCg+zAkVYi3zvZEH2VOuPlpMQMrB9+fLWg2UBsTeZ864wIDAQABozIwMDAgBgNV
HREEGTAXgRVsYXJzLmVnZ2VydEBub2tpYS5jb20wDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQUF
AAOBgQBMdV2U+ryV5t3nuBFH19XKflodN6Bc60GBYHHY/Z0+Cl08Q75qzTt02IILBg+/YVh/fygb
6pFrOm1sFtLN7fENBfbO2VtpFjP2lGUgbXTVT5xGM6+MtqZiBI6LqexAeY6gsd/taoUfy9fZG42d
ciBA9gSGlQjjWQyG8mb5HR8L9jCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJ
BgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgG
A1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMg
RGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3
DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3
MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5
KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzAN
BgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9
fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+
uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMB
Af8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3
dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgG
A1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcP
f6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH
2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8x
ggMQMIIDDAIBATB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAo
UHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQ
SLtZswwprYYsoWlANo4FATAJBgUrDgMCGgUAoIIBbzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcB
MBwGCSqGSIb3DQEJBTEPFw0wOTA4MDgwNzI5MDdaMCMGCSqGSIb3DQEJBDEWBBTx6q8Mvv/d12BI
hytPoJPWaTTQOjCBhQYJKwYBBAGCNxAEMXgwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEwgYcGCyqGSIb3DQEJEAILMXigdjBiMQsw
CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UE
AxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECEEi7WbMMKa2GLKFpQDaOBQEw
DQYJKoZIhvcNAQEBBQAEggEAOpIrV2S19oxRcwRYjuWLSvI/HPfK3NvOxGDt3Xl0jtGBzHtFSlbw
voQJdDk4JApuv4gnaQR4HK0EjVHHssIhb3yg0vZSe6D3jTwg5/eFfPsn0q1JBMSJlI1oPP8GLs9E
VujINr2fB7DwH3DzDF3Pb+ZEtEd6juWdKUPnCXoo7tAis7ui5k1WuTqU6ZZv8pvVw6QYNbWBOPaL
dnZHLuSb5ejUbLsRJgGPm8kiszzK9nK8ybp8EedMvOmiIKR8D9woJ+10m3hVA0Ye3fuODPlezLoa
WKhLL5z+DxW8Vts7Hy/M7gOOKlvHgUVwfVwjCczFgbgj+TUU/rmE/y2S1grnJwAAAAAAAA==

--Apple-Mail-29-826407615--

From swmike@swm.pp.se  Sat Aug  8 00:54:36 2009
Return-Path: <swmike@swm.pp.se>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82FE13A6964; Sat,  8 Aug 2009 00:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.347
X-Spam-Level: 
X-Spam-Status: No, score=-2.347 tagged_above=-999 required=5 tests=[AWL=0.252,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udaCOfLHXbQk; Sat,  8 Aug 2009 00:54:35 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by core3.amsl.com (Postfix) with ESMTP id 508343A68DA; Sat,  8 Aug 2009 00:54:34 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 05BF99C; Sat,  8 Aug 2009 09:54:36 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 04C099A; Sat,  8 Aug 2009 09:54:36 +0200 (CEST)
Date: Sat, 8 Aug 2009 09:54:36 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "homegate@ietf.org" <homegate@ietf.org>
In-Reply-To: <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
Message-ID: <alpine.DEB.1.10.0908080938270.5006@uplift.swm.pp.se>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <B00AFD87-145C-477D-982F-B66140E34B51@apple.com> <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com> <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: TSV Area <tsv-area@ietf.org>
Subject: Re: [homegate] [tsv-area] Amount of packet buffering in home gateways
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 08 Aug 2009 07:54:36 -0000

On Sat, 8 Aug 2009, Lars Eggert wrote:

> If we assume that FIFO queuing will be used, yes, the buffer size has a 
> large, direct impact on the observable behavior. Not so for various AQM 
> schemes (RED, etc.). Since my personal preference would be to recommend 
> something smarter than FIFO, I don't see buffer size as very critical 
> then. (Now, how to correctly parameterize an AQM scheme for a given 
> link, *that* would be critical...)

Hi, in some discussion that came up during the IETF I talked about my home 
scheme, so just to give an example of a heuristic that I personally have 
found to work well in Cisco MQC (not proposing something concrete, just 
giving an example):

class-map match-all small-packets
  match packet length max 200
class-map match-all prio-data
  match access-group name outgoing-prio-data

policy-map out-child
  class prio-data
     bandwidth 300
  class small-packets
     bandwidth 300
  class class-default
     fair-queue 1024
      random-detect
      random-detect ecn
policy-map out-parent
  class class-default
     shape average 700000
   service-policy out-child

ip access-list extended outgoing-prio-data
  permit tcp any any eq 22
  permit udp any any eq domain
  permit icmp any any
  permit ospf any any
  permit tcp any any eq telnet
  permit tcp any any eq www
  permit 41 any any

So basically, I have 1 meg upstream on my cable modem and since I have no 
influence on the buffering there (and the shaping I'm doing is on a ipip 
tunnel), I make sure I use way less than my bw and then I assure a minimum 
bw to outgoing packets to a few services/ports on the Internet 
(ssh/dns/telnet/http), then I also assure a certain amount of bw to 
smaller packets (to catch the typical ACKs and smaller packets typically 
seen in interactive applications such as VOIP and others), then everything 
else is going into fair-queue with WRED and ECN (yes, I actually use ECN 
because I wanted to test it :P)).

This queuing scheme is actually very helpful even on faster links, because 
if you have a T3 link (45 meg) and do FIFO on it with good TCP windows on 
the end hosts, a single TCP flow can make this jump to 100+ ms buffer 
easily, thus you want fair-queue to make it do something intelligent with 
the different flows to avoid your SSH traffic sitting behind this 100ms of 
file transfer. Thus I think any proposal should recommend/inform about 
this even for 100 meg uplinks and higher, as soon as you have big buffers 
you want to do something intelligent queuing where the higher speeds you 
have and lesser buffers, the less intelligence is needed.

I tried replicating this using "tc" in Linux a few years back but gave up 
after a few hours because I just couldn't make it work, so anyone being a 
master at that, I'd be very helpful translating this into "tc" conf :)

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

From touch@ISI.EDU  Sat Aug  8 23:15:25 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82D2F3A684E; Sat,  8 Aug 2009 23:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.749
X-Spam-Level: 
X-Spam-Status: No, score=-2.749 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBLm1iT5JMJg; Sat,  8 Aug 2009 23:15:24 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id A4FEF3A6878; Sat,  8 Aug 2009 23:15:24 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n796F1md029515; Sat, 8 Aug 2009 23:15:03 -0700 (PDT)
Message-ID: <4A7E4674.8050500@isi.edu>
Date: Sat, 08 Aug 2009 20:45:56 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>
In-Reply-To: <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 06:15:25 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, all,

Has anyone raised the potential need for fair-sharing in home gateways?
I.e., to prevent a single home user from swamping out another home user?

(we saw this in a gateway Lars, Yu-shun Wang, and I developed, FWIW,
when we used it to support demos at workshops).

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp+RnQACgkQE5f5cImnZrs18gCg9OGS9559T494JHZbxFnuTj+n
9kwAoNKVBt30NYxAt/6w4w+wJ428HHUa
=AJQg
-----END PGP SIGNATURE-----


From oran@cisco.com  Sun Aug  9 08:36:01 2009
Return-Path: <oran@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 12F2D3A6A58; Sun,  9 Aug 2009 08:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.545
X-Spam-Level: 
X-Spam-Status: No, score=-6.545 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A9tnvP8VMEjs; Sun,  9 Aug 2009 08:36:00 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 053213A6B4C; Sun,  9 Aug 2009 08:36:00 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAL+JfkqrR7PE/2dsb2JhbAC1D4grjksFhBiBUYhC
X-IronPort-AV: E=Sophos;i="4.43,349,1246838400"; d="scan'208";a="225508689"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-1.cisco.com with ESMTP; 09 Aug 2009 15:36:03 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n79Fa3Ln024860;  Sun, 9 Aug 2009 08:36:03 -0700
Received: from stealth-10-32-245-150.cisco.com (stealth-10-32-245-150.cisco.com [10.32.245.150]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n79Fa2V0019692; Sun, 9 Aug 2009 15:36:03 GMT
Message-Id: <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>
From: David R Oran <oran@cisco.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A7E4674.8050500@isi.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sun, 9 Aug 2009 11:36:01 -0400
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu>
X-Mailer: Apple Mail (2.936)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1662; t=1249832163; x=1250696163; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=oran@cisco.com; z=From:=20David=20R=20Oran=20<oran@cisco.com> |Subject:=20Re=3A=20[homegate]=20support=20for=20fair-shari ng=20in=20home=20gateways? |Sender:=20; bh=vE4fJOLyGR8LQ8ZL/QuBIPZusiaCA+8913esIcoLcBQ=; b=thqW2hVJoD0/QJ2yA+NDMge4HtL2+ginhcqq+xUibx6jGrFy1y39AGmWfn z3FsutIHQN8ZJpgegTuSwnkcFa5uZCVFY8Ep+oc5a6GYGYa4HhyWrE5xVRqu M7nB22AECT;
Authentication-Results: sj-dkim-4; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 15:36:01 -0000

On Aug 8, 2009, at 11:45 PM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, all,
>
> Has anyone raised the potential need for fair-sharing in home  
> gateways?
> I.e., to prevent a single home user from swamping out another home  
> user?
>
If one can define "user" in a technically useful way, then it may or  
may not be feasible. If one can't define "user" then I don't know  
where to start.

If user==host, then there may be a way to cover the simple cases - but  
even that's a bit tricky without some kind of signaling protocol.

I think I know how to do this with MPLS :-)

Also a challenge with IPv6 is the ease with which host addresses an be  
manufactured.

Alternatively, if one posits in-home VLANS (like I have in my house),  
then I can pretty easily carve things up. But I suspect we don't want  
to got there either :-)

I'm all ears if somebody has a proposal to make.

Note also, that we have so many easy problems to tackle, if this one  
turns out to be difficult I'd be loathe to make it in scope.

DaveO.

> (we saw this in a gateway Lars, Yu-shun Wang, and I developed, FWIW,
> when we used it to support demos at workshops).
>
> Joe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkp+RnQACgkQE5f5cImnZrs18gCg9OGS9559T494JHZbxFnuTj+n
> 9kwAoNKVBt30NYxAt/6w4w+wJ428HHUa
> =AJQg
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From touch@ISI.EDU  Sun Aug  9 08:55:56 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A2CB3A6A7B; Sun,  9 Aug 2009 08:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYUXZM5E3HPL; Sun,  9 Aug 2009 08:55:55 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 9221F3A6A01; Sun,  9 Aug 2009 08:55:55 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n79Fti3D016409; Sun, 9 Aug 2009 08:55:46 -0700 (PDT)
Message-ID: <4A7EF180.1030109@isi.edu>
Date: Sun, 09 Aug 2009 08:55:44 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: David R Oran <oran@cisco.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>
In-Reply-To: <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 15:55:56 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



David R Oran wrote:
> 
> On Aug 8, 2009, at 11:45 PM, Joe Touch wrote:
> 
> Hi, all,
> 
> Has anyone raised the potential need for fair-sharing in home gateways?
> I.e., to prevent a single home user from swamping out another home user?
> 
>> If one can define "user" in a technically useful way, then it may or may
>> not be feasible. If one can't define "user" then I don't know where to
>> start.
> 
>> If user==host, then there may be a way to cover the simple cases - but
>> even that's a bit tricky without some kind of signaling protocol.

User = IP address (i.e., just to keep it simple). And that's already
supported in FreeBSD, so I doubt it's that tricky.

>> Alternatively, if one posits in-home VLANS (like I have in my house),
>> then I can pretty easily carve things up. But I suspect we don't want to
>> got there either :-)

Even fair corresponding to NAT'd address is useful. It doesn't have to
be perfectly fair, it just prevents one user from crowding everyone else
out due to non-reacting flows.

>> Note also, that we have so many easy problems to tackle, if this one
>> turns out to be difficult I'd be loathe to make it in scope.

It's not difficult; it just needs to be spec'd, and the spec doesn't
need to be precise. The goal is to do something that is per address at
least, and prevents crowding out, and that's already supportable in at
least one existing OS.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp+8X8ACgkQE5f5cImnZruD5ACeMcrCu29qT4wh3krGQFyYxBSs
UscAn2aRxBmLCozWlICPe/cLBpiOR66F
=cBxF
-----END PGP SIGNATURE-----

From shalunov@bittorrent.com  Sun Aug  9 13:40:44 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE61E3A6B14; Sun,  9 Aug 2009 13:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.134
X-Spam-Level: 
X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XC69rwDDpXD6; Sun,  9 Aug 2009 13:40:43 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by core3.amsl.com (Postfix) with ESMTP id AA2283A67FD; Sun,  9 Aug 2009 13:40:43 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 28so934681wff.31 for <multiple recipients>; Sun, 09 Aug 2009 13:40:45 -0700 (PDT)
Received: by 10.142.214.5 with SMTP id m5mr33304wfg.341.1249850443892; Sun, 09 Aug 2009 13:40:43 -0700 (PDT)
Received: from ?192.168.1.106? (c-67-188-254-19.hsd1.ca.comcast.net [67.188.254.19]) by mx.google.com with ESMTPS id 22sm8987629wfi.32.2009.08.09.13.40.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 09 Aug 2009 13:40:43 -0700 (PDT)
Message-Id: <8AACF67B-A6D9-4E1D-9848-31A9B7313DED@bittorrent.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 13:40:43 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <B00AFD87-145C-477D-982F-B66140E34B51@apple.com> <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com> <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
X-Mailer: Apple Mail (2.935.3)
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] [tsv-area] Amount of packet buffering in home gateways
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 20:40:45 -0000

Lars,

Right.  Two separate points here:

1. With AQM, one needs to replace "buffer" in my statements below with  
"occupied buffer".  This will presumably be controlled by AQM  
parameters (a drop low watermark or whatnot).  The statements still  
stand: no amount of AQM is going to make TCP dynamics better with a  
single-packet window, for example.  The core problem of having to have  
a few packets in flight per flow and that translating to a large  
serialization delay stands.  If anything, it's ECN that could help  
here, not AQM.

2. I didn't mention AQM because I don't believe we should recommend  
one.  We should not do RED, because it's clear by now that it's  
suboptimal.  We should not do something other than RED, because  
homegate isn't the place.

Thanks,  -- Stas

-- 
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com

On Aug 8, 2009, at 12:29 AM, Lars Eggert wrote:

> Hi,
>
> these are all good points. I wanted to repeat something I said at  
> the mike in Stockholm which I think is essential:
>
> We cannot make a recommendation for a certain buffer size without  
> also saying which queuing scheme we recommend for that buffer.
>
> If we assume that FIFO queuing will be used, yes, the buffer size  
> has a large, direct impact on the observable behavior. Not so for  
> various AQM schemes (RED, etc.). Since my personal preference would  
> be to recommend something smarter than FIFO, I don't see buffer size  
> as very critical then. (Now, how to correctly parameterize an AQM  
> scheme for a given link, *that* would be critical...)
>
> Lars
>
> On 2009-8-7, at 21:59, Stanislav Shalunov wrote:
>
>> The manufacturers would benefit from specific guidance -- if we could
>> say that the right value were 10 packets or 10kB or 100ms worth of
>> serialization delay, rounded up to an integer number of packets or
>> some such, they could implement it.
>>
>> Trouble is, we don't know any such right value.
>>
>> What we do know are things like:
>>
>> * Even a single TCP flow on a very slow link will need a few packets
>> worth of buffer so that it can keep something in flight and so that
>> fast retransmit works.  Different values have been argued to be right
>> from this perspective, from 6 packets to 10.
>>
>> * Multiple TCP flows likely need more buffer, but probably not much
>> more, because it becomes increasingly acceptable for fast retransmit
>> to fail and timeout to fire when there are more connections --  
>> they're
>> probably going to keep the link busy anyway.
>>
>> * Any of that is way too much from the POV of delay experienced by
>> interactive apps (interactive = user waiting, so includes web).
>>
>> The conjunction implies a lack of right value.  In absence of such,
>> best we could hope for is giving negative guidance.  We do know  
>> that a
>> 64-kB buffer on a 128-kb/s link serves no purpose and could write it
>> up and explain why.  We'll end up with excessively conservative
>> recommendations this way, but maybe it's OK.
>>
>> If we can't agree on specific guidance that people can use to size  
>> the
>> buffers and instead can only agree on general considerations like  
>> ones
>> I listed above, we might be better off not issuing any guidance at  
>> all
>> in the spirit of doing no harm.  After all, if we can't translate  
>> that
>> into bytes (which a manufacturer ultimately must), why should we
>> expect others to do so?
>>
>>
>>
>>
>> On Wed, Jul 29, 2009 at 1:59 AM, james woodyatt<jhw@apple.com> wrote:
>>> On Jul 29, 2009, at 10:34, Iljitsch van Beijnum wrote:
>>>>
>>>> The question is, what do we want to tell home gateway builders?
>>>
>>> We should tell them that forwarding IP flows from higher bandwidth  
>>> links
>>> into much lower bandwidth links generally produces better results  
>>> when
>>> queues are only large enough to handle common burst sizes without  
>>> loss and
>>> no larger.  Unnecessarily large transmission queues may introduce
>>> persistently and perversely high path latency on fully loaded low- 
>>> bandwidth
>>> links, producing severe negative effects on application throughput.
>>>
>>> Beyond that, I don't know what else we should say.  Maybe it would  
>>> help to
>>> give some guidance for various common sub-IP links.
>>>
>>>
>>> --
>>> james woodyatt <jhw@apple.com>
>>> member of technical staff, communications engineering
>>>
>>>
>>>
>>
>>
>>
>> -- 
>> Stanislav Shalunov
>> BitTorrent Inc
>> shalunov@bittorrent.com
>>
>> personal: http://shlang.com
>


From shalunov@bittorrent.com  Sun Aug  9 13:46:57 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 635333A6D69; Sun,  9 Aug 2009 13:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gzIOOhDRrWnt; Sun,  9 Aug 2009 13:46:56 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by core3.amsl.com (Postfix) with ESMTP id 7DA5C3A68CC; Sun,  9 Aug 2009 13:46:56 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 28so935073wff.31 for <multiple recipients>; Sun, 09 Aug 2009 13:46:42 -0700 (PDT)
Received: by 10.142.141.19 with SMTP id o19mr67260wfd.328.1249850802359; Sun, 09 Aug 2009 13:46:42 -0700 (PDT)
Received: from ?192.168.1.106? (c-67-188-254-19.hsd1.ca.comcast.net [67.188.254.19]) by mx.google.com with ESMTPS id 28sm10106291wfd.4.2009.08.09.13.46.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 09 Aug 2009 13:46:41 -0700 (PDT)
Message-Id: <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A7EF180.1030109@isi.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 13:46:36 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu>
X-Mailer: Apple Mail (2.935.3)
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 20:46:57 -0000

On Aug 9, 2009, at 8:55 AM, Joe Touch wrote:

> User = IP address (i.e., just to keep it simple).

In a typical home deployment, there's just one IP address visible to  
the home gateway (e.g., cable/DSL modem): the address that the home  
router has acquired.  The actual machines, phones, game consoles,  
etc., are behind a NAT.

-- 
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com

From oran@cisco.com  Sun Aug  9 15:32:23 2009
Return-Path: <oran@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D04753A6A5A; Sun,  9 Aug 2009 15:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.547
X-Spam-Level: 
X-Spam-Status: No, score=-6.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PrGEhs0f30SA; Sun,  9 Aug 2009 15:32:23 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id E521A3A6BE1; Sun,  9 Aug 2009 15:32:22 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAA7rfkqrR7O6/2dsb2JhbAC1H4grjiIFhBg
X-IronPort-AV: E=Sophos;i="4.43,349,1246838400"; d="scan'208";a="225550003"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 09 Aug 2009 22:32:26 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n79MWQR9021428;  Sun, 9 Aug 2009 15:32:26 -0700
Received: from stealth-10-32-245-150.cisco.com (stealth-10-32-245-150.cisco.com [10.32.245.150]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n79MWPcm022763; Sun, 9 Aug 2009 22:32:26 GMT
Message-Id: <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>
From: David R Oran <oran@cisco.com>
To: Stanislav Shalunov <shalunov@bittorrent.com>
In-Reply-To: <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Sun, 9 Aug 2009 18:32:24 -0400
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>
X-Mailer: Apple Mail (2.936)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=808; t=1249857146; x=1250721146; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=oran@cisco.com; z=From:=20David=20R=20Oran=20<oran@cisco.com> |Subject:=20Re=3A=20[homegate]=20[tsv-area]=20support=20for =20fair-sharing=20in=20home=20gateways? |Sender:=20; bh=DQM1YSyCZpoNWQEMQjNwtm0sQpVLX0WvGc9GmJozVCQ=; b=s9ipVKBlM2XC+JxQ5IX86zRQn0RUQT3oG8v4i9Dw3JyL1SCwTh8+FZylnC w51U44rU+ejeD776ZKv6EBwaSjir07v6Uhn3lJ09ZLKIOoDYj1xDBqlWYp0F MWLardPOyL;
Authentication-Results: sj-dkim-2; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org, Joe Touch <touch@ISI.EDU>
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 22:32:23 -0000

On Aug 9, 2009, at 4:46 PM, Stanislav Shalunov wrote:

> On Aug 9, 2009, at 8:55 AM, Joe Touch wrote:
>
>> User = IP address (i.e., just to keep it simple).
>
> In a typical home deployment, there's just one IP address visible to  
> the home gateway (e.g., cable/DSL modem): the address that the home  
> router has acquired.  The actual machines, phones, game consoles,  
> etc., are behind a NAT.
>
But those ARE visible to the outbound queueing machinery of the HG,  
and hence the queues facing the uplink could have finer policy.

> -- 
> Stanislav Shalunov
> BitTorrent Inc
> shalunov@bittorrent.com
>
> personal: http://shlang.com
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From shalunov@bittorrent.com  Sun Aug  9 15:40:37 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AD5CC3A6CA8; Sun,  9 Aug 2009 15:40:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQBzBYRZaVaw; Sun,  9 Aug 2009 15:40:36 -0700 (PDT)
Received: from mail-pz0-f178.google.com (mail-pz0-f178.google.com [209.85.222.178]) by core3.amsl.com (Postfix) with ESMTP id B6AD73A6CB3; Sun,  9 Aug 2009 15:40:36 -0700 (PDT)
Received: by pzk8 with SMTP id 8so2689196pzk.31 for <multiple recipients>; Sun, 09 Aug 2009 15:40:38 -0700 (PDT)
Received: by 10.142.213.21 with SMTP id l21mr88269wfg.116.1249857638202; Sun, 09 Aug 2009 15:40:38 -0700 (PDT)
Received: from ?192.168.1.106? (c-67-188-254-19.hsd1.ca.comcast.net [67.188.254.19]) by mx.google.com with ESMTPS id 22sm9198769wfi.32.2009.08.09.15.40.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 09 Aug 2009 15:40:37 -0700 (PDT)
Message-Id: <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: David R Oran <oran@cisco.com>
In-Reply-To: <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 15:40:31 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>
X-Mailer: Apple Mail (2.935.3)
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org, Joe Touch <touch@ISI.EDU>
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 09 Aug 2009 22:40:37 -0000

Perhaps a picture will help clarify:

home devices <-- ~25Mb/s (wifi) --> router <-- 100Mb/s --> homegate  
<-- 0.4 Mb/s --> Internet

The router is the NAT.  The homegate is the headend of the congested  
link.

In a typical home situation, the router is a Linksys base station/NAT  
box and the homegate is something like a Motorola cable modem.

-- 
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com

On Aug 9, 2009, at 3:32 PM, David R Oran wrote:

>
> On Aug 9, 2009, at 4:46 PM, Stanislav Shalunov wrote:
>
>> On Aug 9, 2009, at 8:55 AM, Joe Touch wrote:
>>
>>> User = IP address (i.e., just to keep it simple).
>>
>> In a typical home deployment, there's just one IP address visible  
>> to the home gateway (e.g., cable/DSL modem): the address that the  
>> home router has acquired.  The actual machines, phones, game  
>> consoles, etc., are behind a NAT.
>>
> But those ARE visible to the outbound queueing machinery of the HG,  
> and hence the queues facing the uplink could have finer policy.
>
>> -- 
>> Stanislav Shalunov
>> BitTorrent Inc
>> shalunov@bittorrent.com
>>
>> personal: http://shlang.com
>> _______________________________________________
>> homegate mailing list
>> homegate@ietf.org
>> https://www.ietf.org/mailman/listinfo/homegate
>


From touch@ISI.EDU  Sun Aug  9 17:25:22 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D635C3A6C3B; Sun,  9 Aug 2009 17:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level: 
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRP9fvnUvM8Y; Sun,  9 Aug 2009 17:25:22 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 165143A67F3; Sun,  9 Aug 2009 17:25:22 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7A0PEtA011848; Sun, 9 Aug 2009 17:25:16 -0700 (PDT)
Message-ID: <4A7F68EA.1030205@isi.edu>
Date: Sun, 09 Aug 2009 17:25:14 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Stanislav Shalunov <shalunov@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>
In-Reply-To: <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 00:25:22 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Stanislav Shalunov wrote:
> On Aug 9, 2009, at 8:55 AM, Joe Touch wrote:
> 
>> User = IP address (i.e., just to keep it simple).
> 
> In a typical home deployment, there's just one IP address visible to the
> home gateway (e.g., cable/DSL modem): the address that the home router
> has acquired.  The actual machines, phones, game consoles, etc., are
> behind a NAT.

The addresses that I'm thinking of keeping track of would be those on
the home side, for all the machines behind the device. NATd or not,
doesn't matter - it's the same problem.

Think of it this way. You have a home gateway, and your Tivo goes
berzerk with UDP packets to the Internet; you don't want that starving
out your laptop's email, or anything else.

This is less about being truly 'fair', since any fairness scheme can be
gamed. It's about preventing starvation...

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp/aOoACgkQE5f5cImnZrsEMgCg3mKYY8Ddy9Cc27hPNOB5Ij0f
/3sAoOJ4IJRmwnJ0VVi7JjUeg4/jIoY6
=OQnt
-----END PGP SIGNATURE-----

From touch@ISI.EDU  Sun Aug  9 17:27:33 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E6343A6D3A; Sun,  9 Aug 2009 17:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level: 
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id om7y5j4WW74I; Sun,  9 Aug 2009 17:27:32 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id E48533A6C3B; Sun,  9 Aug 2009 17:27:32 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7A0RHoV012083; Sun, 9 Aug 2009 17:27:19 -0700 (PDT)
Message-ID: <4A7F6964.3020701@isi.edu>
Date: Sun, 09 Aug 2009 17:27:16 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Stanislav Shalunov <shalunov@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com> <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com>
In-Reply-To: <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 00:27:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Stanislav Shalunov wrote:
> Perhaps a picture will help clarify:
> 
> home devices <-- ~25Mb/s (wifi) --> router <-- 100Mb/s --> homegate <--
> 0.4 Mb/s --> Internet
> 
> The router is the NAT.  The homegate is the headend of the congested link.
> 
> In a typical home situation, the router is a Linksys base station/NAT
> box and the homegate is something like a Motorola cable modem.

In the typical home situation, I expect the wifi, router, and homegate
all in one box (they are for everyone I know).

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkp/aWQACgkQE5f5cImnZrslLQCbBTyHL8THpjCYnfplIDtvVdA9
BLsAoLI9sOv2k0NQEEMwZkSapVdO72W7
=9gTY
-----END PGP SIGNATURE-----

From shalunov@bittorrent.com  Sun Aug  9 18:02:03 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32D773A6D6B; Sun,  9 Aug 2009 18:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xSGPdhe5JKw; Sun,  9 Aug 2009 18:02:02 -0700 (PDT)
Received: from mail-pz0-f192.google.com (mail-pz0-f192.google.com [209.85.222.192]) by core3.amsl.com (Postfix) with ESMTP id 4E0DF3A6B1B; Sun,  9 Aug 2009 18:02:02 -0700 (PDT)
Received: by pzk30 with SMTP id 30so2542726pzk.5 for <multiple recipients>; Sun, 09 Aug 2009 18:02:03 -0700 (PDT)
Received: by 10.142.161.11 with SMTP id j11mr641329wfe.52.1249866123595; Sun, 09 Aug 2009 18:02:03 -0700 (PDT)
Received: from ?192.168.1.106? (c-67-188-254-19.hsd1.ca.comcast.net [67.188.254.19]) by mx.google.com with ESMTPS id 32sm10381557wfc.34.2009.08.09.18.01.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 09 Aug 2009 18:02:02 -0700 (PDT)
Message-Id: <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A7F6964.3020701@isi.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 18:01:49 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com> <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu>
X-Mailer: Apple Mail (2.935.3)
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 01:02:03 -0000

On Aug 9, 2009, at 5:27 PM, Joe Touch wrote:
> In the typical home situation, I expect the wifi, router, and homegate
> all in one box (they are for everyone I know).

Most home users with better-than-dialup are connected with cable or DSL.

The vast majority of them use wifi and NAT.

The cable/DSL modems provide neither wifi nor NAT services.

This makes for a typical situation with two boxes.

The only technology that would enable home connectivity with one box  
would be something supported by the common home routers.  Which only  
support Ethernet on the uplink.  Ethernet is not commonly used to  
deliver home Internet service in the United States.

The node that you might be thinking of is the router/NAT/wifi box.   
This box is not at a head end of a congested bottleneck.

-- 
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com


From richard@bennett.com  Sun Aug  9 18:06:35 2009
Return-Path: <richard@bennett.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 009413A6B9D for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 18:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.103
X-Spam-Level: 
X-Spam-Status: No, score=-1.103 tagged_above=-999 required=5 tests=[AWL=-0.296, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id reTDOsKkg9io for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 18:06:34 -0700 (PDT)
Received: from outbound-mail-311.bluehost.com (outbound-mail-311.bluehost.com [67.222.54.4]) by core3.amsl.com (Postfix) with SMTP id 061D63A698F for <homegate@ietf.org>; Sun,  9 Aug 2009 18:06:33 -0700 (PDT)
Received: (qmail 14892 invoked by uid 0); 10 Aug 2009 01:06:37 -0000
Received: from unknown (HELO host308.hostmonster.com) (74.220.215.108) by outboundproxy6.bluehost.com with SMTP; 10 Aug 2009 01:06:37 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bennett.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=FCVge1KWfWAMpqBlz/oZ0VDL5d3EXOzDjWhHPmvcPCxBIWfZ6rMwT7F9zHkCNEgfyau8WJSxKuWcvYN50CLRQQxvm1V3s45syQfHadZcysouuzD44QvMjqlpImqyX0Fz;
Received: from c-24-5-230-26.hsd1.ca.comcast.net ([24.5.230.26] helo=[192.168.1.101]) by host308.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <richard@bennett.com>) id 1MaJLR-0005HE-H6; Sun, 09 Aug 2009 19:06:37 -0600
Message-ID: <4A7F729A.7040800@bennett.com>
Date: Sun, 09 Aug 2009 18:06:34 -0700
From: Richard Bennett <richard@bennett.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Joe Touch <touch@ISI.EDU>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com>	<68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>	<4A7E4674.8050500@isi.edu>	<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>	<4A7EF180.1030109@isi.edu>	<7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>	<439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>	<E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu>
In-Reply-To: <4A7F6964.3020701@isi.edu>
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {5842:host308.hostmonster.com:bennett1:bennett.com} {sentby:smtp auth 24.5.230.26 authed with richard+bennett.com}
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org, Stanislav Shalunov <shalunov@bittorrent.com>
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 01:06:35 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I agree with Joe, nobody considers a standalone DSL "modem" or DOCSIS
modem to be the home gateway, the NAT/Etherswitch/Wi-Fi AP is the home
gateway. Let's be clear about basic terminology. Many home gateways
have the DSL modem built-in these days, and in fact nobody is
developing new DSL modems that aren't integrated with a NAT. Some NATs
do have DOCSIS built-in, but this is less common because DOCSIS is
expensive to develop and test.<br>
<br>
Many home gateways do in fact use VLANs on both the upstream and
downstream side, especially the CPE gateways that are part of a
triple-play system with VOD to STBs inside the home. Some that I've
seen use VLANs to carry packets from one of the Virtual BSS's on the
Wi-Fi AP to a carrier NAT outside the home as well. VLANs are an
excellent way to prioritize and de-prioritize packets.<br>
<br>
Similarly, Wi-Fi has a system of frame prioritization called WMM that
uses a subset of the 802.11e standard. It's widely supported in home
gateways these days, along with systems for shallow packet inspection
that allow users to boost the priority of Skype and lower the priority
of P2P, for example. Many P2P systems are not well domesticated.<br>
<br>
RB<br>
<br>
Joe Touch wrote:
<blockquote cite="mid:4A7F6964.3020701@isi.edu" type="cite">
  <pre wrap="">-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Stanislav Shalunov wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Perhaps a picture will help clarify:

home devices &lt;-- ~25Mb/s (wifi) --&gt; router &lt;-- 100Mb/s --&gt; homegate &lt;--
0.4 Mb/s --&gt; Internet

The router is the NAT.  The homegate is the headend of the congested link.

In a typical home situation, the router is a Linksys base station/NAT
box and the homegate is something like a Motorola cable modem.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
In the typical home situation, I expect the wifi, router, and homegate
all in one box (they are for everyone I know).

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a>

iEYEARECAAYFAkp/aWQACgkQE5f5cImnZrslLQCbBTyHL8THpjCYnfplIDtvVdA9
BLsAoLI9sOv2k0NQEEMwZkSapVdO72W7
=9gTY
-----END PGP SIGNATURE-----
_______________________________________________
homegate mailing list
<a class="moz-txt-link-abbreviated" href="mailto:homegate@ietf.org">homegate@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/homegate">https://www.ietf.org/mailman/listinfo/homegate</a>
  </pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-- 
Richard Bennett
Research Fellow
Information Technology and Innovation Foundation
Washington, DC</pre>
</body>
</html>

From richard@bennett.com  Sun Aug  9 18:08:16 2009
Return-Path: <richard@bennett.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 070743A6B9D for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 18:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.758
X-Spam-Level: 
X-Spam-Status: No, score=-1.758 tagged_above=-999 required=5 tests=[AWL=0.507,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jWI7UtFPX78w for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 18:08:15 -0700 (PDT)
Received: from outbound-mail-131.bluehost.com (outbound-mail-131.bluehost.com [67.222.39.21]) by core3.amsl.com (Postfix) with SMTP id 4BA083A6B00 for <homegate@ietf.org>; Sun,  9 Aug 2009 18:08:15 -0700 (PDT)
Received: (qmail 9971 invoked by uid 0); 10 Aug 2009 01:08:18 -0000
Received: from unknown (HELO host308.hostmonster.com) (74.220.215.108) by outboundproxy4.bluehost.com with SMTP; 10 Aug 2009 01:08:18 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bennett.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=ZcNrdBM8xZnM0QwE3VXiPR/DLgl9gZ+O9SO+Ypi3fxcAk7/rGAvXQlXNmw1nEWpLvUZZKAPGbyjtlLO2M3qWmg4HTpmkoP1+/ybImJ4FRM11h+NdRs1I1bQkbFB+3iOv;
Received: from c-24-5-230-26.hsd1.ca.comcast.net ([24.5.230.26] helo=[192.168.1.101]) by host308.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <richard@bennett.com>) id 1MaJN4-0007ku-Lk; Sun, 09 Aug 2009 19:08:18 -0600
Message-ID: <4A7F7300.3060709@bennett.com>
Date: Sun, 09 Aug 2009 18:08:16 -0700
From: Richard Bennett <richard@bennett.com>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Stanislav Shalunov <shalunov@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com>	<68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>	<4A7E4674.8050500@isi.edu>	<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>	<4A7EF180.1030109@isi.edu>	<7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>	<439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>	<E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com>	<4A7F6964.3020701@isi.edu> <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
In-Reply-To: <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Identified-User: {5842:host308.hostmonster.com:bennett1:bennett.com} {sentby:smtp auth 24.5.230.26 authed with richard+bennett.com}
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org, Joe Touch <touch@ISI.EDU>
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 01:08:16 -0000

Some DSL systems use PPPoE, FWIW, and FiOS has an Ethernet interface 
between the ONT and the NAT, alongside a MoCA interface, pick one.

Stanislav Shalunov wrote:
> On Aug 9, 2009, at 5:27 PM, Joe Touch wrote:
>> In the typical home situation, I expect the wifi, router, and homegate
>> all in one box (they are for everyone I know).
>
> Most home users with better-than-dialup are connected with cable or DSL.
>
> The vast majority of them use wifi and NAT.
>
> The cable/DSL modems provide neither wifi nor NAT services.
>
> This makes for a typical situation with two boxes.
>
> The only technology that would enable home connectivity with one box 
> would be something supported by the common home routers.  Which only 
> support Ethernet on the uplink.  Ethernet is not commonly used to 
> deliver home Internet service in the United States.
>
> The node that you might be thinking of is the router/NAT/wifi box.  
> This box is not at a head end of a congested bottleneck.
>

-- 
Richard Bennett
Research Fellow
Information Technology and Innovation Foundation
Washington, DC


From paul.hoffman@vpnc.org  Sun Aug  9 18:15:43 2009
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6D2783A683A for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 18:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.24
X-Spam-Level: 
X-Spam-Status: No, score=-2.24 tagged_above=-999 required=5 tests=[AWL=0.359,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JXrSTeJJIyl8 for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 18:15:42 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 67DDA3A6B1B for <homegate@ietf.org>; Sun,  9 Aug 2009 18:15:42 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n7A1Ffx8054357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 9 Aug 2009 18:15:42 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p062408a7c6a524837708@[10.20.30.158]>
In-Reply-To: <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com> <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu> <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
Date: Sun, 9 Aug 2009 18:15:43 -0700
To: Stanislav Shalunov <shalunov@bittorrent.com>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Cc: homegate@ietf.org
Subject: [homegate] Home gateway systems
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 01:15:43 -0000

At 6:01 PM -0700 8/9/09, Stanislav Shalunov wrote:
>On Aug 9, 2009, at 5:27 PM, Joe Touch wrote:
>>In the typical home situation, I expect the wifi, router, and homegate
>>all in one box (they are for everyone I know).
>
>Most home users with better-than-dialup are connected with cable or DSL.
>
>The vast majority of them use wifi and NAT.
>
>The cable/DSL modems provide neither wifi nor NAT services.
>
>This makes for a typical situation with two boxes.

Is there any published research to back up these assertions? They go against what I am familiar with in the home DSL world, namely DSL modem/gateway combos.

--Paul Hoffman, Director
--VPN Consortium

From shalunov@bittorrent.com  Sun Aug  9 18:43:22 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CF5583A6A8F; Sun,  9 Aug 2009 18:43:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level: 
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xCJanLoveTof; Sun,  9 Aug 2009 18:43:22 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 0D69C3A6B59; Sun,  9 Aug 2009 18:43:21 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 28so962622wff.31 for <multiple recipients>; Sun, 09 Aug 2009 18:43:23 -0700 (PDT)
Received: by 10.142.127.7 with SMTP id z7mr349418wfc.113.1249868603756; Sun, 09 Aug 2009 18:43:23 -0700 (PDT)
Received: from ?192.168.1.106? (c-67-188-254-19.hsd1.ca.comcast.net [67.188.254.19]) by mx.google.com with ESMTPS id 22sm10583441wfd.8.2009.08.09.18.43.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 09 Aug 2009 18:43:23 -0700 (PDT)
Message-Id: <C01286C4-B52A-49DA-9768-DB90F5D74B90@bittorrent.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: Richard Bennett <richard@bennett.com>
In-Reply-To: <4A7F729A.7040800@bennett.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 18:43:07 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com>	<68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>	<4A7E4674.8050500@isi.edu>	<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>	<4A7EF180.1030109@isi.edu>	<7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>	<439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>	<E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu> <4A7F729A.7040800@bennett.com>
X-Mailer: Apple Mail (2.935.3)
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 01:43:22 -0000

On Aug 9, 2009, at 6:06 PM, Richard Bennett wrote:

> I agree with Joe, nobody considers a standalone DSL "modem" or  
> DOCSIS modem to be the home gateway, the NAT/Etherswitch/Wi-Fi AP is  
> the home gateway

The standalone modems are the head ends of the congested bottleneck  
leading up from the home.  They are the devices where buffer size  
matters.

> [...]
>
> Similarly, Wi-Fi has a system of frame prioritization called WMM  
> that uses a subset of the 802.11e standard. It's widely supported in  
> home gateways these days, along with systems for shallow packet  
> inspection that allow users to boost the priority of Skype and lower  
> the priority of P2P, for example. Many P2P systems are not well  
> domesticated.

I think you'll find Skype is P2P.

-- 
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com


From dwhite@olp.net  Sun Aug  9 19:06:32 2009
Return-Path: <dwhite@olp.net>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C6363A6D20 for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 19:06:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, IP_NOT_FRIENDLY=0.334, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id taMC3mIQ1RFH for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 19:06:31 -0700 (PDT)
Received: from olp.net (olp-67-217-144-185.olp.net [67.217.144.185]) by core3.amsl.com (Postfix) with ESMTP id 513753A6929 for <homegate@ietf.org>; Sun,  9 Aug 2009 19:06:31 -0700 (PDT)
Received: by dan.olp.net (Postfix, from userid 1000) id 00F0F459EB5; Sun,  9 Aug 2009 20:31:07 -0500 (CDT)
Date: Sun, 9 Aug 2009 20:31:07 -0500
From: Dan White <dwhite@olp.net>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20090810013107.GG4328@dan.olp.net>
References: <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com> <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu> <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com> <p062408a7c6a524837708@[10.20.30.158]>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="p7qwJlK53pWzbayA"
Content-Disposition: inline
In-Reply-To: <p062408a7c6a524837708@[10.20.30.158]>
X-OS: Linux zek 2.6.26-2-xen-amd64 x86_64
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: homegate@ietf.org, Stanislav Shalunov <shalunov@bittorrent.com>
Subject: Re: [homegate] Home gateway systems
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 02:06:32 -0000

--p7qwJlK53pWzbayA
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 09/08/09=A018:15=A0-0700, Paul Hoffman wrote:
>At 6:01 PM -0700 8/9/09, Stanislav Shalunov wrote:
>>On Aug 9, 2009, at 5:27 PM, Joe Touch wrote:
>>>In the typical home situation, I expect the wifi, router, and homegate
>>>all in one box (they are for everyone I know).
>>
>>Most home users with better-than-dialup are connected with cable or DSL.
>>
>>The vast majority of them use wifi and NAT.
>>
>>The cable/DSL modems provide neither wifi nor NAT services.
>>
>>This makes for a typical situation with two boxes.
>
>Is there any published research to back up these assertions? They go again=
st what I am familiar with in the home DSL world, namely DSL modem/gateway =
combos.
>
>--Paul Hoffman, Director
>--VPN Consortium

Me too.

For the last 5 years we've only deployed ADSL 2+ modems that are wireless
(and NAT) capable.

Now we've got a bad taste in our mouths from all the support tickets we've
had to volley.

All modem vendors we've spoken to in the last several months have
integrated wireless into most of their models, and seem to scratch their
heads when we ask for non-wireless capable modems. Finding VDSL2 or ADSL
bonded modems without built-in wireless is actually pretty dificult.

--=20
Dan White
BTC Broadband

--p7qwJlK53pWzbayA
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkp/eFsACgkQjEHNWladFEX7NgCgoRVy9GfD8isXxXjMSvhRn42D
o+MAoI+UzSpjcasLhsb6txu5NeEeOpLH
=oBjX
-----END PGP SIGNATURE-----

--p7qwJlK53pWzbayA--

From shalunov@bittorrent.com  Sun Aug  9 19:57:18 2009
Return-Path: <shalunov@bittorrent.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E5783A6B9A for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 19:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.309
X-Spam-Level: 
X-Spam-Status: No, score=-2.309 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RQFS8r5ug1R for <homegate@core3.amsl.com>; Sun,  9 Aug 2009 19:57:16 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by core3.amsl.com (Postfix) with ESMTP id 7E74A3A6C55 for <homegate@ietf.org>; Sun,  9 Aug 2009 19:57:15 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 28so973451wff.31 for <homegate@ietf.org>; Sun, 09 Aug 2009 19:57:18 -0700 (PDT)
Received: by 10.142.13.21 with SMTP id 21mr390819wfm.236.1249873037681; Sun, 09 Aug 2009 19:57:17 -0700 (PDT)
Received: from ?192.168.1.106? (c-67-188-254-19.hsd1.ca.comcast.net [67.188.254.19]) by mx.google.com with ESMTPS id 22sm10591965wfi.12.2009.08.09.19.57.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 09 Aug 2009 19:57:16 -0700 (PDT)
Message-Id: <451394FB-E239-4886-A05A-0A075B6C3F87@bittorrent.com>
From: Stanislav Shalunov <shalunov@bittorrent.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <p062408a7c6a524837708@[10.20.30.158]>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 19:57:14 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com> <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu> <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com> <p062408a7c6a524837708@[10.20.30.158]>
X-Mailer: Apple Mail (2.935.3)
Cc: homegate@ietf.org
Subject: Re: [homegate] Home gateway systems
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 02:57:18 -0000

On Aug 9, 2009, at 6:15 PM, Paul Hoffman wrote:

> At 6:01 PM -0700 8/9/09, Stanislav Shalunov wrote:
>> On Aug 9, 2009, at 5:27 PM, Joe Touch wrote:
>>> In the typical home situation, I expect the wifi, router, and  
>>> homegate
>>> all in one box (they are for everyone I know).
>>
>> Most home users with better-than-dialup are connected with cable or  
>> DSL.
>>
>> The vast majority of them use wifi and NAT.
>>
>> The cable/DSL modems provide neither wifi nor NAT services.
>>
>> This makes for a typical situation with two boxes.
>
> Is there any published research to back up these assertions? They go  
> against what I am familiar with in the home DSL world, namely DSL  
> modem/gateway combos.


Of the unscientific sample of DSL lines ordered within last year that  
I could quickly query, 12 installs came without wifi or NAT -- and 0  
came with.  This only covered two local telcos though, so it's  
possible that others put different boxes in.

No cable modems came sporting antennas either.

Since you're in the home DSL world, which local telcos install modems  
with wifi and NAT and what is the fraction of the installed base?

However, this is only an upper bound on the right metric.  If the  
modem boxes ship with wifi/NAT, but then a user puts in a Linksys/D- 
Link/Netgear box between that and the home devices, the unconfigured  
presence of wifi/NAT in the modem is not relevant.

So, going from the other end, let's look at how many boxes, say,  
Linksys sells.  Those are all second boxes that go on top of the  
simple "modems".  I can't seem to find if Cisco breaks out Linksys  
sales, but last year before acquisition (according to http://www.techedgeezine.com/cisco_buys_linksys_1.htm) 
  Linksys had annual sales of $429M with 22% market share.  This  
suggests that tens of millions of second boxes were sold then annually  
(~20M boxes at $100/box, the real price is lower, but some revenue  
must have been from other products, so this should be a wash).  With  
an MTBF of 5 years, that puts most broadband households behind a  
second box.

(Our friends from Cisco might be able to point out the more recent  
sales figures of something like WRT54 series and similar and market  
share for Linksys if that stuff is public, but this is enough for the  
back of the envelope.)

D-Link and Netgear don't break out home networking, but overall  
revenues with guesstimates of share of revenue and market share seem  
to jibe.  I'm not going to put that in this message, already too long.

http://www.corpasia.net/taiwan/2332/annual/2007/EN/AR2007-1.pdf
http://investor.netgear.com/secfiling.cfm?filingID=950134-07-4560

But we're digressing.  Long story short:

	The buffer size that matters is at the head end of the congested  
bottleneck.

	The Amazon top-selling "modem" (http://www.amazon.com/Motorola-Surfboard-SB5101-Cable-Modem/dp/B000JV9LUK/ 
) is at the head end of a congested bottleneck.

	The Amazon top-selling home "router" (http://www.amazon.com/Linksys-WRT54G2-Wireless-G-Broadband-Router/dp/B0014J07R2/ 
) is not usually at the head of a congested bottleneck.

	HOMEGATE should care about the former device and should not care  
about the latter.

-- 
Stanislav Shalunov
BitTorrent Inc
shalunov@bittorrent.com

personal: http://shlang.com

From mbaugher@cisco.com  Sun Aug  9 21:49:55 2009
Return-Path: <mbaugher@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A75F23A6AA5; Sun,  9 Aug 2009 21:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.491
X-Spam-Level: 
X-Spam-Status: No, score=-5.491 tagged_above=-999 required=5 tests=[AWL=1.108,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nksbfZWMqve9; Sun,  9 Aug 2009 21:49:54 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id C20A43A6A2B; Sun,  9 Aug 2009 21:49:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAHFDf0qrR7MV/2dsb2JhbAC2HIgrjgEFhBiBUYhC
X-IronPort-AV: E=Sophos;i="4.43,351,1246838400"; d="scan'208";a="364002925"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 10 Aug 2009 04:49:57 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n7A4nwXr010718;  Sun, 9 Aug 2009 21:49:58 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n7A4nwK4016755; Mon, 10 Aug 2009 04:49:58 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Sun, 9 Aug 2009 21:49:58 -0700
Received: from [10.0.1.5] ([10.21.114.193]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 9 Aug 2009 21:49:58 -0700
Message-Id: <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com>
From: Mark Baugher <mbaugher@cisco.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A7E4674.8050500@isi.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 9 Aug 2009 21:48:41 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 10 Aug 2009 04:49:58.0110 (UTC) FILETIME=[0306E7E0:01CA1976]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1230; t=1249879798; x=1250743798; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbaugher@cisco.com; z=From:=20Mark=20Baugher=20<mbaugher@cisco.com> |Subject:=20Re=3A=20[homegate]=20support=20for=20fair-shari ng=20in=20home=20gateways? |Sender:=20; bh=DXK67v6E6S3pL8/zWfAEeVlxQo00Bj5pjO+p18GDoaU=; b=T5SV5hpwIeTXRQYTuoTVZtQRGVnheR5ndq7KsZjFWr6sazSmGJEampjzxA cCMFOd1vVZE8Nn5f2/+rhNw0F1dmuprJ0i9/qOcI04fv/SeSVojzbtETwhiX pDhWnhJDZ3euewxs5clH9tmY6XjL3v+uk82a7m3bFohIYckgqsdS4=;
Authentication-Results: sj-dkim-1; header.From=mbaugher@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 04:49:55 -0000

On Aug 8, 2009, at 8:45 PM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, all,
>
> Has anyone raised the potential need for fair-sharing in home  
> gateways?
> I.e., to prevent a single home user from swamping out another home  
> user?

Non-technological solutions are often more useful in the home.  If one  
user
is mom and the other user is Johnny, then mom will tell Johnny to shut  
down
the bittorrent so she can do her work.  We saw that in an ethnographic  
study
of home users last year.  We can rely on social controls for home  
networking
and should consider how to make use of them.

Mark
>
>
> (we saw this in a gateway Lars, Yu-shun Wang, and I developed, FWIW,
> when we used it to support demos at workshops).
>
> Joe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkp+RnQACgkQE5f5cImnZrs18gCg9OGS9559T494JHZbxFnuTj+n
> 9kwAoNKVBt30NYxAt/6w4w+wJ428HHUa
> =AJQg
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From Ray.Bellis@nominet.org.uk  Mon Aug 10 00:16:05 2009
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCD443A6AAB; Mon, 10 Aug 2009 00:16:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p1ZLs5nHpidg; Mon, 10 Aug 2009 00:16:04 -0700 (PDT)
Received: from mx3.nominet.org.uk (mx3.nominet.org.uk [213.248.199.23]) by core3.amsl.com (Postfix) with ESMTP id 01CC83A6A68; Mon, 10 Aug 2009 00:16:03 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:In-Reply-To:References:To:Cc: Subject:MIME-Version:X-Mailer:Message-ID:From:Date: X-MIMETrack:Content-Type; b=Gjwg9l+kank9YIy3Z+gwA1s430ycYG+T6FFC1Ux/1iVuBBt0Xt3ObyAm LpS9XB23Ri2E6bnrkmWMLq4/25ovSdJ7D4MKBUalEFpDLUBj9gMoYYChB MX9+hnNaWuTLyIO;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1249888568; x=1281424568; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray.Bellis@nominet.org.uk|Subject:=20Re:=20[home gate]=20Home=20gateway=20systems|Date:=20Mon,=2010=20Aug =202009=2008:15:57=20+0100|Message-ID:=20<OFE72378BB.9894 687D-ON8025760E.0026E54B-8025760E.0027E9A3@nominet.org.uk >|To:=20Stanislav=20Shalunov=20<shalunov@bittorrent.com> |Cc:=20homegate@ietf.org,=0D=0A=09homegate-bounces@ietf.o rg,=0D=0A=09Paul=20Hoffman=20<paul.hoffman@vpnc.org> |MIME-Version:=201.0|In-Reply-To:=20<451394FB-E239-4886-A 05A-0A075B6C3F87@bittorrent.com>|References:=20<CD75E101- E956-4682-A3CF-454986AC0C37@muada.com>=09<68A1E2ED-774A-4 0B2-B0A5-8A2F7EF59753@nokia.com>=0D=0A=09<4A7E4674.805050 0@isi.edu>=09<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco. com>=0D=0A=09<4A7EF180.1030109@isi.edu>=09<7132B313-6C17- 45C0-914E-EF5BDBF037C8@bittorrent.com>=0D=0A=09<439A249E- 196C-41B1-B175-10C55415B2AD@cisco.com>=09<E416433A-148F-4 BD3-AB47-99E83D7BCAFD@bittorrent.com>=0D=0A=09<4A7F6964.3 020701@isi.edu>=09<81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@b ittorrent.com>=0D=0A=09<p062408a7c6a524837708@[10.20.30.1 58]>=20<451394FB-E239-4886-A05A-0A075B6C3F87@bittorrent.c om>; bh=mUpgFMRBP94ARJSxY17WMoN+qoHEHNFvAXCW/UILotk=; b=4ytemc1LX6RmMUg3gnTzh97qK12X4RF2EiBCnOJvGvHY1FDhGT1h+3TW 9CF6tnRlHXe4bn+XxGHaDEZ1PRN2R1QmrfpEtzHU+TrYfpFrp9IoFXmDn LEsqbv1EuGgvOiF;
X-IronPort-AV: E=Sophos;i="4.43,352,1246834800"; d="scan'208";a="16568876"
Received: from notes1.nominet.org.uk ([213.248.197.128]) by mx3.nominet.org.uk with ESMTP; 10 Aug 2009 08:16:01 +0100
In-Reply-To: <451394FB-E239-4886-A05A-0A075B6C3F87@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com>	<68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu>	<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu>	<7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>	<E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu>	<81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com> <p062408a7c6a524837708@[10.20.30.158]> <451394FB-E239-4886-A05A-0A075B6C3F87@bittorrent.com>
To: Stanislav Shalunov <shalunov@bittorrent.com>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 8.5 December 05, 2008
Message-ID: <OFE72378BB.9894687D-ON8025760E.0026E54B-8025760E.0027E9A3@nominet.org.uk>
From: Ray.Bellis@nominet.org.uk
Date: Mon, 10 Aug 2009 08:15:57 +0100
X-MIMETrack: Serialize by Router on notes1/Nominet(Release 7.0.1FP1 | May 25, 2006) at 10/08/2009 08:16:05 AM, Serialize complete at 10/08/2009 08:16:05 AM
Content-Type: multipart/alternative; boundary="=_alternative 0027E9A18025760E_="
Cc: homegate-bounces@ietf.org, homegate@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [homegate] Home gateway systems
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 07:16:05 -0000

This is a multipart message in MIME format.
--=_alternative 0027E9A18025760E_=
Content-Type: text/plain; charset="US-ASCII"

>    The Amazon top-selling "modem" (http://www.amazon.com/Motorola-
> Surfboard-SB5101-Cable-Modem/dp/B000JV9LUK/ 
> ) is at the head end of a congested bottleneck.
> 
>    The Amazon top-selling home "router" (http://www.amazon.com/
> Linksys-WRT54G2-Wireless-G-Broadband-Router/dp/B0014J07R2/ 
> ) is not usually at the head of a congested bottleneck.
> 
>    HOMEGATE should care about the former device and should not care 
> about the latter.

IMHO, you've got this completely the wrong way around.

HomeGate is about making sure that the unit that provides the IP gateway 
function (be that a router or a NAT) works properly.  The focus is on the 
"router", and not on the "modem".

HomeGate is _not_ only about congestion management and queueing, if 
anything that's a very small part of the remit.  Where it is relevant is 
in making sure that the relatively smart router doesn't throw packets out 
of its WAN port faster than the dumb modem can handle.  That should 
provide far better queueing than the modem could manage by itself, but in 
effect does make the router "at the head end" of the bottleneck.

FWIW, the European market is completely dominated by combined devices with 
integrated DSL modems.  In the US there's many more standalone gateway 
devices (with ethernet on both sides) although AIUI the increasing 
provision of DSL services is changing this.  This is why when writing 
SAC035 I worked with the former and my US co-author worked with the 
latter.

kind regards,

Ray

-- 
Ray Bellis, MA(Oxon) MIET
Senior Researcher in Advanced Projects, Nominet
e: ray@nominet.org.uk, t: +44 1865 332211



--=_alternative 0027E9A18025760E_=
Content-Type: text/html; charset="US-ASCII"

<tt><font size=2><br>
&gt; &nbsp; &nbsp;The Amazon top-selling &quot;modem&quot; (</font></tt><a href="http://www.amazon.com/Motorola-"><tt><font size=2>http://www.amazon.com/Motorola-</font></tt></a><tt><font size=2><br>
&gt; Surfboard-SB5101-Cable-Modem/dp/B000JV9LUK/ <br>
&gt; ) is at the head end of a congested bottleneck.<br>
&gt; <br>
&gt; &nbsp; &nbsp;The Amazon top-selling home &quot;router&quot; (</font></tt><a href=http://www.amazon.com/><tt><font size=2>http://www.amazon.com/</font></tt></a><tt><font size=2><br>
&gt; Linksys-WRT54G2-Wireless-G-Broadband-Router/dp/B0014J07R2/ <br>
&gt; ) is not usually at the head of a congested bottleneck.<br>
&gt; <br>
&gt; &nbsp; &nbsp;HOMEGATE should care about the former device and should
not care &nbsp;<br>
&gt; about the latter.<br>
</font></tt>
<br><tt><font size=2>IMHO, you've got this completely the wrong way around.</font></tt>
<br>
<br><tt><font size=2>HomeGate is about making sure that the unit that provides
the IP gateway function (be that a router or a NAT) works properly. &nbsp;The
focus is on the &quot;router&quot;, and not on the &quot;modem&quot;.</font></tt>
<br>
<br><tt><font size=2>HomeGate is _not_ only about congestion management
and queueing, if anything that's a very small part of the remit. &nbsp;Where
it is relevant is in making sure that the relatively smart router doesn't
throw packets out of its WAN port faster than the dumb modem can handle.
&nbsp;That should provide far better queueing than the modem could manage
by itself, but in effect does make the router &quot;at the head end&quot;
of the bottleneck.</font></tt>
<br>
<br><tt><font size=2>FWIW, the European market is completely dominated
by combined devices with integrated DSL modems. &nbsp;In the US there's
many more standalone gateway devices (with ethernet on both sides) although
AIUI the increasing provision of DSL services is changing this. &nbsp;This
is why when writing SAC035 I worked with the former and my US co-author
worked with the latter.</font></tt>
<br>
<br><tt><font size=2>kind regards,</font></tt>
<br>
<br><tt><font size=2>Ray</font></tt>
<br>
<br><tt><font size=2>-- <br>
Ray Bellis, MA(Oxon) MIET<br>
Senior Researcher in Advanced Projects, Nominet<br>
e: ray@nominet.org.uk, t: +44 1865 332211<br>
<br>
<br>
</font></tt>
--=_alternative 0027E9A18025760E_=--

From henk@ripe.net  Mon Aug 10 00:54:58 2009
Return-Path: <henk@ripe.net>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 90C7A3A6C7B for <homegate@core3.amsl.com>; Mon, 10 Aug 2009 00:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.422
X-Spam-Level: 
X-Spam-Status: No, score=-4.422 tagged_above=-999 required=5 tests=[AWL=-2.138, BAYES_00=-2.599, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qEcV8ep5BxIF for <homegate@core3.amsl.com>; Mon, 10 Aug 2009 00:54:57 -0700 (PDT)
Received: from postlady.ripe.net (postlady.ripe.net [193.0.19.65]) by core3.amsl.com (Postfix) with ESMTP id 64E4C3A6A63 for <homegate@ietf.org>; Mon, 10 Aug 2009 00:54:57 -0700 (PDT)
Received: from herring.ripe.net ([193.0.1.203]) by postlady.ripe.net with esmtp (Exim 4.63) (envelope-from <henk@ripe.net>) id 1MaPiO-0005HG-SY; Mon, 10 Aug 2009 09:54:50 +0200
Received: from geir-3.local (henk.vpn.ripe.net [193.0.21.33]) by herring.ripe.net (Postfix) with ESMTP id CFD042F583; Mon, 10 Aug 2009 09:54:44 +0200 (CEST)
Message-ID: <4A7FD244.6050207@ripe.net>
Date: Mon, 10 Aug 2009 09:54:44 +0200
From: Henk Uijterwaal <henk@ripe.net>
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: Stanislav Shalunov <shalunov@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com>	<68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>	<4A7E4674.8050500@isi.edu>	<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>	<4A7EF180.1030109@isi.edu>	<7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>	<439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>	<E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com>	<4A7F6964.3020701@isi.edu>	<81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>	<p062408a7c6a524837708@[10.20.30.158]> <451394FB-E239-4886-A05A-0A075B6C3F87@bittorrent.com>
In-Reply-To: <451394FB-E239-4886-A05A-0A075B6C3F87@bittorrent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: ----
X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d5386f050773aba187b9d0ade5013dcbf9
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, homegate@ietf.org
Subject: Re: [homegate] Home gateway systems
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 07:54:58 -0000

Stanislav Shalunov wrote:

> Of the unscientific sample of DSL lines ordered within last year that I 
> could quickly query, 12 installs came without wifi or NAT -- and 0 came 
> with.  This only covered two local telcos though, so it's possible that 
> others put different boxes in.

A quick check of the biggest consumer-market ISP's here shows that their
current default offering is a modem that does NAT, WiFi and quite often
VoIP.  One usually gets such a modem for free.


> So, going from the other end, let's look at how many boxes, say, Linksys 
> sells.  Those are all second boxes that go on top of the simple 
> "modems".  I can't seem to find if Cisco breaks out Linksys sales, but 
> last year before acquisition (according to 
> http://www.techedgeezine.com/cisco_buys_linksys_1.htm) Linksys had 
> annual sales of $429M with 22% market share.  This suggests that tens of 
> millions of second boxes were sold then annually (~20M boxes at 
> $100/box, the real price is lower, but some revenue must have been from 
> other products, so this should be a wash).  With an MTBF of 5 years, 
> that puts most broadband households behind a second box.

I'd think that a fair number of those 20M boxes are being used in offices
and such.

Henk







-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.xs4all.nl/~henku
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

Belgium: an unsolvable problem, discussed in endless meetings, with no
          hope for a solution, where everybody still lives happily.

From cabo@tzi.org  Mon Aug 10 03:57:00 2009
Return-Path: <cabo@tzi.org>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3ACF83A6ACC; Mon, 10 Aug 2009 03:57:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.845
X-Spam-Level: 
X-Spam-Status: No, score=-5.845 tagged_above=-999 required=5 tests=[AWL=0.404,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4QQBWclCUXl; Mon, 10 Aug 2009 03:56:59 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9:209:3dff:fe00:7136]) by core3.amsl.com (Postfix) with ESMTP id 23D853A6B3E; Mon, 10 Aug 2009 03:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id n7AAupLT023338; Mon, 10 Aug 2009 12:56:52 +0200 (CEST)
Received: from [192.168.217.101] (p5489E329.dip.t-dialin.net [84.137.227.41]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTP id 4CD9BBFF8;  Mon, 10 Aug 2009 12:56:51 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
To: Stanislav Shalunov <shalunov@bittorrent.com>
In-Reply-To: <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com> <4A7EF180.1030109@isi.edu> <7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com> <439A249E-196C-41B1-B175-10C55415B2AD@cisco.com> <E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com> <4A7F6964.3020701@isi.edu> <81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com>
Message-Id: <058CFE71-DB10-4104-B3E4-83B5AF17B30B@tzi.org>
Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 10 Aug 2009 12:56:50 +0200
X-Mailer: Apple Mail (2.935.3)
X-Mailman-Approved-At: Mon, 10 Aug 2009 04:16:49 -0700
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 10:57:00 -0000

On Aug 10, 2009, at 03:01, Stanislav Shalunov wrote:

> The cable/DSL modems provide neither wifi nor NAT services.

A very common (the most common? at least in my perception...) =20
configuration in Europe is a single box that combines DSL modem, NAT, =20=

WiFi AP and, if part of a phone line replacement offering, some SIP/=20
RTP to legacy telephony gateway (POTS, ISDN sockets).  Just to give =20
one (popular) example of such a box: Speedport W503V, =80 2 when ordered =
=20
with a new DSL line.

That's what most people here are likely to have in mind when they hear =20=

the term "home gateway".
(I think that term simply is unsalvageable.)

Gruesse, Carsten


From sblake@extremenetworks.com  Sun Aug  9 20:53:00 2009
Return-Path: <sblake@extremenetworks.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1F1C3A6A58; Sun,  9 Aug 2009 20:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.283
X-Spam-Level: 
X-Spam-Status: No, score=-0.283 tagged_above=-999 required=5 tests=[AWL=2.317,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IR8X9Wb33tHI; Sun,  9 Aug 2009 20:53:00 -0700 (PDT)
Received: from ussc-casht-p1.extremenetworks.com (ussc-casht-p1.extremenetworks.com [207.179.9.62]) by core3.amsl.com (Postfix) with ESMTP id 045DF3A68D0; Sun,  9 Aug 2009 20:52:59 -0700 (PDT)
Received: from [10.35.16.1] (10.35.16.1) by ussc-casht-p1.corp.extremenetworks.com (10.0.4.73) with Microsoft SMTP Server id 8.1.358.0; Sun, 9 Aug 2009 20:53:03 -0700
From: Steven Blake <sblake@extremenetworks.com>
To: Lars Eggert <lars.eggert@nokia.com>
In-Reply-To: <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <B00AFD87-145C-477D-982F-B66140E34B51@apple.com> <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com> <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com>
Content-Type: text/plain
Organization: Extreme Networks
Date: Sun, 9 Aug 2009 23:53:00 -0400
Message-ID: <1249876380.30947.33.camel@tachyon>
MIME-Version: 1.0
X-Mailer: Evolution 2.24.5 (2.24.5-2.fc10) 
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 10 Aug 2009 04:17:09 -0700
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] [tsv-area] Amount of packet buffering in home gateways
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 03:53:01 -0000

On Sat, 2009-08-08 at 00:29 -0700, Lars Eggert wrote:

> Hi,
> 
> these are all good points. I wanted to repeat something I said at the  
> mike in Stockholm which I think is essential:
> 
> We cannot make a recommendation for a certain buffer size without also  
> saying which queuing scheme we recommend for that buffer.
> 
> If we assume that FIFO queuing will be used, yes, the buffer size has  
> a large, direct impact on the observable behavior. Not so for various  
> AQM schemes (RED, etc.). Since my personal preference would be to  
> recommend something smarter than FIFO, I don't see buffer size as very  
> critical then. (Now, how to correctly parameterize an AQM scheme for a  
> given link, *that* would be critical...)

802.1Qbb (http://www.ieee802.org/1/pages/802.1bb.html) priority PAUSE
has the right semantics to push the queues back into the hosts where
they can react intelligently.  Unfortunately, this would require
more-or-less universal adoption in modems, gateways, switches, hosts,
and WiFi APs.


Regards,

/////////////////////////////////////////////
Steven Blake       sblake@extremenetworks.com
Extreme Networks              +1 919-884-3211


From oran@cisco.com  Mon Aug 10 04:54:42 2009
Return-Path: <oran@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 343193A6CDD; Mon, 10 Aug 2009 04:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Ef24kr9aOiE; Mon, 10 Aug 2009 04:54:40 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 8ADCB3A6E68; Mon, 10 Aug 2009 04:54:22 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEALmnf0qrR7MV/2dsb2JhbAC2fIgrNQmODAWCS4FNgVE
X-IronPort-AV: E=Sophos;i="4.43,353,1246838400"; d="scan'208";a="225747269"
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-1.cisco.com with ESMTP; 10 Aug 2009 11:54:26 +0000
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n7ABsQVc001570;  Mon, 10 Aug 2009 04:54:26 -0700
Received: from stealth-10-32-245-150.cisco.com (stealth-10-32-245-150.cisco.com [10.32.245.150]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id n7ABsPXS022374; Mon, 10 Aug 2009 11:54:25 GMT
Message-Id: <18A8FA1E-AE46-4460-86F9-AAD0C6B43EBD@cisco.com>
From: David R Oran <oran@cisco.com>
To: Steven Blake <sblake@extremenetworks.com>
In-Reply-To: <1249876380.30947.33.camel@tachyon>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 10 Aug 2009 07:54:24 -0400
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <B00AFD87-145C-477D-982F-B66140E34B51@apple.com> <6c82d1360908071159n42410a1as669e82783fea2ccb@mail.gmail.com> <CE602311-015A-46B0-9867-5ADCC4A518A4@nokia.com> <1249876380.30947.33.camel@tachyon>
X-Mailer: Apple Mail (2.936)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2017; t=1249905266; x=1250769266; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=oran@cisco.com; z=From:=20David=20R=20Oran=20<oran@cisco.com> |Subject:=20Re=3A=20[homegate]=20[tsv-area]=20Amount=20of=2 0packet=20buffering=20in=20home=20gateways |Sender:=20; bh=1iyTaA9giWAA+0wgrayznX6bpSfNUMU07XEkd2gD7Sk=; b=eQg/WqczsEVHRy1dB11FR37rBxLNVtGoCEGNVQgb+3LB0J+E9L53DNWr74 G7z3/B3ONXdMgqND9CZo4SjS4gKZ5F3PEWD91d8ksgAlQREGc6pZwPc/35C7 S9UuYAwpsfy3lu6g1KEkkdkaUt2j7iRmK/nPWLAlDRfY9WSrqTZFY=;
Authentication-Results: sj-dkim-1; header.From=oran@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; ); 
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] [tsv-area] Amount of packet buffering in home gateways
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 11:54:42 -0000

On Aug 9, 2009, at 11:53 PM, Steven Blake wrote:

> On Sat, 2009-08-08 at 00:29 -0700, Lars Eggert wrote:
>
>> Hi,
>>
>> these are all good points. I wanted to repeat something I said at the
>> mike in Stockholm which I think is essential:
>>
>> We cannot make a recommendation for a certain buffer size without  
>> also
>> saying which queuing scheme we recommend for that buffer.
>>
>> If we assume that FIFO queuing will be used, yes, the buffer size has
>> a large, direct impact on the observable behavior. Not so for various
>> AQM schemes (RED, etc.). Since my personal preference would be to
>> recommend something smarter than FIFO, I don't see buffer size as  
>> very
>> critical then. (Now, how to correctly parameterize an AQM scheme  
>> for a
>> given link, *that* would be critical...)
>
> 802.1Qbb (http://www.ieee802.org/1/pages/802.1bb.html) priority PAUSE
> has the right semantics to push the queues back into the hosts where
> they can react intelligently.  Unfortunately, this would require
> more-or-less universal adoption in modems, gateways, switches, hosts,
> and WiFi APs.
>
Well, if you can put the algorithms into the home gateway to know when  
to send PAUSE, you can by definition manage the queues intelligently  
in the home gateway itself. I don't see how this changes anything -  
unlike in localized L2 networks, in an IP network bottlenecks can be  
anywhere on the path. There's nothing special about the second hop  
that pushing the congestion notification one hop upstream solves  
anything.

Take this to the extreme (no pun intended) and you wind up with X.25  
backward congestion notification.

Cheers, DaveO.

>
> Regards,
>
> /////////////////////////////////////////////
> Steven Blake       sblake@extremenetworks.com
> Extreme Networks              +1 919-884-3211
>
> _______________________________________________
> homegate mailing list
> homegate@ietf.org
> https://www.ietf.org/mailman/listinfo/homegate


From touch@ISI.EDU  Mon Aug 10 07:14:40 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ED22628C100; Mon, 10 Aug 2009 07:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.659
X-Spam-Level: 
X-Spam-Status: No, score=-2.659 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hr-J47JsU9Rg; Mon, 10 Aug 2009 07:14:40 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 0E2003A6BCB; Mon, 10 Aug 2009 07:14:24 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7AEEJwx025886; Mon, 10 Aug 2009 07:14:21 -0700 (PDT)
Message-ID: <4A802B3B.8000002@isi.edu>
Date: Mon, 10 Aug 2009 07:14:19 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com>
In-Reply-To: <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 14:14:41 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Mark Baugher wrote:
> 
> On Aug 8, 2009, at 8:45 PM, Joe Touch wrote:
> 
> Hi, all,
> 
> Has anyone raised the potential need for fair-sharing in home gateways?
> I.e., to prevent a single home user from swamping out another home user?
> 
>> Non-technological solutions are often more useful in the home.  If one user
>> is mom and the other user is Johnny, then mom will tell Johnny to shut down
>> the bittorrent so she can do her work.  We saw that in an ethnographic
>> study
>> of home users last year.  We can rely on social controls for home
>> networking
>> and should consider how to make use of them.

That works only when Mom knows Johnny is doing something like that.

Further, I don't see why social controls are useful when a trivial
mechanism is sufficient.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqAKzoACgkQE5f5cImnZruDrgCeKhwSE1AEUyKh55Dc/CCaU8gr
0moAoNMagcrG8dRvPuUXZQl7hqZJi0r8
=7HuG
-----END PGP SIGNATURE-----

From touch@ISI.EDU  Mon Aug 10 07:26:33 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 40D273A68AF; Mon, 10 Aug 2009 07:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.654
X-Spam-Level: 
X-Spam-Status: No, score=-2.654 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u27BB2+J6YIO; Mon, 10 Aug 2009 07:26:32 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 4A88228C13F; Mon, 10 Aug 2009 07:26:32 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7AEQDuG028539; Mon, 10 Aug 2009 07:26:15 -0700 (PDT)
Message-ID: <4A802E05.2010402@isi.edu>
Date: Mon, 10 Aug 2009 07:26:13 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com>	<68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com>	<4A7E4674.8050500@isi.edu>	<ED8B25E3-C3AD-4007-8CE5-3CF408749C63@cisco.com>	<4A7EF180.1030109@isi.edu>	<7132B313-6C17-45C0-914E-EF5BDBF037C8@bittorrent.com>	<439A249E-196C-41B1-B175-10C55415B2AD@cisco.com>	<E416433A-148F-4BD3-AB47-99E83D7BCAFD@bittorrent.com>	<4A7F6964.3020701@isi.edu>	<81FAA1B1-98A0-415B-805F-DDB0F1FC00A1@bittorrent.com> <058CFE71-DB10-4104-B3E4-83B5AF17B30B@tzi.org>
In-Reply-To: <058CFE71-DB10-4104-B3E4-83B5AF17B30B@tzi.org>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, homegate@ietf.org, Stanislav Shalunov <shalunov@bittorrent.com>
Subject: Re: [homegate] [tsv-area] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 14:26:33 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Carsten Bormann wrote:
> On Aug 10, 2009, at 03:01, Stanislav Shalunov wrote:
> 
>> The cable/DSL modems provide neither wifi nor NAT services.
> 
> A very common (the most common? at least in my perception...)
> configuration in Europe is a single box that combines DSL modem, NAT,
> WiFi AP and, if part of a phone line replacement offering, some SIP/RTP
> to legacy telephony gateway (POTS, ISDN sockets).  Just to give one
> (popular) example of such a box: Speedport W503V, € 2 when ordered with
> a new DSL line.

I have a Westell VersaLink model 327W, which I've used for several
years, as have many Verizon customers. Like modems I've had since before
2000, it includes a NAT. Like modems I've had since 2003, it has
integrated wifi.

Most people I know are not techies - they get one box from the telco /
cableco and just use it. FWIW, most telcos and cablecos will even help
you setup a few laptops/desktops as part of the install.

That's typical for DSL and cable modem installations in the US, and has
been for many years now.

FWIW, people don't buy these things from Amazon or anywhere else
directly in the US - they come free with 1-2 yrs of service.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqALgUACgkQE5f5cImnZrt9ZgCgxlQVLHn983ZzOmYuqbtnL8F2
P1UAniVFaK/6HgjeSUvv0OwumknYkzYE
=G6jY
-----END PGP SIGNATURE-----

From mbaugher@cisco.com  Mon Aug 10 09:55:07 2009
Return-Path: <mbaugher@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CCCD3A6CBF; Mon, 10 Aug 2009 09:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.614
X-Spam-Level: 
X-Spam-Status: No, score=-5.614 tagged_above=-999 required=5 tests=[AWL=0.985,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VmvX54LsHHAX; Mon, 10 Aug 2009 09:55:06 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 355A73A6A99; Mon, 10 Aug 2009 09:55:06 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAEvtf0qrR7O6/2dsb2JhbAC5bIgrjmoFhBiBUYhC
X-IronPort-AV: E=Sophos;i="4.43,354,1246838400"; d="scan'208";a="364329445"
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-6.cisco.com with ESMTP; 10 Aug 2009 16:55:10 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n7AGtA7h032409;  Mon, 10 Aug 2009 09:55:10 -0700
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n7AGtANv002981; Mon, 10 Aug 2009 16:55:10 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 10 Aug 2009 09:55:09 -0700
Received: from sjc-mbaugher-8713.cisco.com ([10.19.93.36]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 10 Aug 2009 09:55:09 -0700
Message-Id: <3B861838-20EC-451E-A095-0E528706E0A2@cisco.com>
From: Mark Baugher <mbaugher@cisco.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A802B3B.8000002@isi.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 10 Aug 2009 09:55:08 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com> <4A802B3B.8000002@isi.edu>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 10 Aug 2009 16:55:09.0374 (UTC) FILETIME=[51C2E5E0:01CA19DB]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1489; t=1249923310; x=1250787310; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbaugher@cisco.com; z=From:=20Mark=20Baugher=20<mbaugher@cisco.com> |Subject:=20Re=3A=20[homegate]=20support=20for=20fair-shari ng=20in=20home=20gateways? |Sender:=20; bh=eM6JQ3DMkr4Swb65rmY4m5bieglpqhIenWNvhKPQ6kQ=; b=FoOuByTfik2tY/Y/dPkNpxfNeKeaEPQ0R8L9oOGlCIQy7pslc9LER9m3VK tPAriJDw7NRuLPsTWFSIp5SP7XkMREWIcLLpIeL6W+e8TSsY0nceMzC88Ef0 YbGK3Rbpq/;
Authentication-Results: sj-dkim-2; header.From=mbaugher@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); 
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 16:55:07 -0000

On 10/08/2009, at 7:14 AM, Joe Touch wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Mark Baugher wrote:
>>
>> On Aug 8, 2009, at 8:45 PM, Joe Touch wrote:
>>
>> Hi, all,
>>
>> Has anyone raised the potential need for fair-sharing in home  
>> gateways?
>> I.e., to prevent a single home user from swamping out another home  
>> user?
>>
>>> Non-technological solutions are often more useful in the home.  If  
>>> one user
>>> is mom and the other user is Johnny, then mom will tell Johnny to  
>>> shut down
>>> the bittorrent so she can do her work.  We saw that in an  
>>> ethnographic
>>> study
>>> of home users last year.  We can rely on social controls for home
>>> networking
>>> and should consider how to make use of them.
>
> That works only when Mom knows Johnny is doing something like that.
>
> Further, I don't see why social controls are useful when a trivial
> mechanism is sufficient.

I expect that you will need policy for any such mechanism - if for
no other reason to allow the user to shut it off when desired.  That's
what is non-trivial on an unmanaged network.  There's not much that's
simply on a home network in my experience.

Mark

>
>
> Joe
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqAKzoACgkQE5f5cImnZruDrgCeKhwSE1AEUyKh55Dc/CCaU8gr
> 0moAoNMagcrG8dRvPuUXZQl7hqZJi0r8
> =7HuG
> -----END PGP SIGNATURE-----


From touch@ISI.EDU  Mon Aug 10 10:33:37 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9549C28C1A9; Mon, 10 Aug 2009 10:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mZCJ7WNQ6tzs; Mon, 10 Aug 2009 10:33:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id BE5D228C1BA; Mon, 10 Aug 2009 10:33:36 -0700 (PDT)
Received: from [75.212.197.1] (1.sub-75-212-197.myvzw.com [75.212.197.1]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7AHXMqf013186; Mon, 10 Aug 2009 10:33:25 -0700 (PDT)
Message-ID: <4A8059E2.9010308@isi.edu>
Date: Mon, 10 Aug 2009 10:33:22 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com> <4A802B3B.8000002@isi.edu> <3B861838-20EC-451E-A095-0E528706E0A2@cisco.com>
In-Reply-To: <3B861838-20EC-451E-A095-0E528706E0A2@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 17:33:37 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Mark Baugher wrote:
...
> Mark Baugher wrote:
>>>>
>>>> On Aug 8, 2009, at 8:45 PM, Joe Touch wrote:
>>>>
>>>> Hi, all,
>>>>
>>>> Has anyone raised the potential need for fair-sharing in home gateways?
>>>> I.e., to prevent a single home user from swamping out another home user?
>>>>
>>>>> Non-technological solutions are often more useful in the home.  If
>>>>> one user
>>>>> is mom and the other user is Johnny, then mom will tell Johnny to
>>>>> shut down
>>>>> the bittorrent so she can do her work.  We saw that in an ethnographic
>>>>> study
>>>>> of home users last year.  We can rely on social controls for home
>>>>> networking
>>>>> and should consider how to make use of them.
> 
> That works only when Mom knows Johnny is doing something like that.
> 
> Further, I don't see why social controls are useful when a trivial
> mechanism is sufficient.
> 
>> I expect that you will need policy for any such mechanism - if for
>> no other reason to allow the user to shut it off when desired.  That's
>> what is non-trivial on an unmanaged network.  There's not much that's
>> simply on a home network in my experience.

Users already have many similar things - DHCP, NAT, SSID default to
announce, etc. - "on" by default, and they allow the user to shut it off
or alter the configuration.

This is no different. It's really not a huge leap. It just needs to be
included in the requirements, and defaulted to "ON" like most of these
other things.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqAWeIACgkQE5f5cImnZrvyVgCZAaWql8Ga6wG8yETB4exXyuV1
k1IAn0gNf8pgw5qEH0otJ8WhMxNyh5Ft
=Mxmt
-----END PGP SIGNATURE-----

From mbaugher@cisco.com  Mon Aug 10 12:03:12 2009
Return-Path: <mbaugher@cisco.com>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE15628C1F4; Mon, 10 Aug 2009 12:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.712
X-Spam-Level: 
X-Spam-Status: No, score=-5.712 tagged_above=-999 required=5 tests=[AWL=0.886,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkCUi5o7eniO; Mon, 10 Aug 2009 12:03:11 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id E70C128C1E8; Mon, 10 Aug 2009 12:03:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAMgLgEqrR7PE/2dsb2JhbACCJi+4DogrjnsFhBiKEw
X-IronPort-AV: E=Sophos;i="4.43,355,1246838400";  d="scan'208,217";a="364419985"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-6.cisco.com with ESMTP; 10 Aug 2009 19:03:15 +0000
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n7AJ3FaW024562;  Mon, 10 Aug 2009 12:03:15 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n7AJ3Ffo021253; Mon, 10 Aug 2009 19:03:15 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 10 Aug 2009 12:03:15 -0700
Received: from sjc-mbaugher-8713.cisco.com ([10.19.93.36]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 10 Aug 2009 12:03:14 -0700
Message-Id: <AAEC3E48-8CE8-4098-8F9F-18D9CEAA9841@cisco.com>
From: Mark Baugher <mbaugher@cisco.com>
To: Joe Touch <touch@ISI.EDU>
In-Reply-To: <4A8059E2.9010308@isi.edu>
Content-Type: multipart/alternative; boundary=Apple-Mail-43-1040854696
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 10 Aug 2009 12:03:14 -0700
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com> <4A802B3B.8000002@isi.edu> <3B861838-20EC-451E-A095-0E528706E0A2@cisco.com> <4A8059E2.9010308@isi.edu>
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 10 Aug 2009 19:03:15.0189 (UTC) FILETIME=[36DD3250:01CA19ED]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=4228; t=1249930995; x=1250794995; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mbaugher@cisco.com; z=From:=20Mark=20Baugher=20<mbaugher@cisco.com> |Subject:=20Re=3A=20[homegate]=20support=20for=20fair-shari ng=20in=20home=20gateways? |Sender:=20; bh=5QB2d1MJYhrDVdOF+J4jGV+MiB+vbQVZhGOR99kjjjQ=; b=Y1tXatL04g7+JksQyKVFkMw+ZG6S95iCDYjCTJE1GVR/BX6CNZ+aqHl9Yh pgPIPO1RKnGSVfDZlI4OMWc0hXFtY6IbDBiaJE2KdofZB1m6yHDFtwQ8BCWm Bhcp7pzi3Q;
Authentication-Results: sj-dkim-4; header.From=mbaugher@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; ); 
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 19:03:12 -0000

--Apple-Mail-43-1040854696
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On 10/08/2009, at 10:33 AM, Joe Touch wrote:

> Users already have many similar things - DHCP, NAT, SSID default to
> announce, etc. - "on" by default, and they allow the user to shut it  
> off
> or alter the configuration.

Duplicate DHCP servers and double-NATs are a huge problem for vendors of
home networking equipment when the unskilled user needs to shut it off.
The user may need to shut it "off" when upgrading to a new 802.11N AP
and attaching it to an existing home gateway/router/NAT, for example.
Experience has shown that a majority of home users cannot do that
without making a service call to the vendor's 800 number or hiring
GeekSquad or some other service to reconfigure the network.  The call to
the vendor typically costs the vendor tens of dollars, often for a  
device
that sells for under $50.  GeekSquad, Firedog, etc. costs the non-
professional user about $150 or so.

It should make us more sensitive to HCI in the home when considering new
features that get exposed to users.  Some HCI folks are very hot on  
social
controls and other innovations for this very reason.

That's the point I am trying to make.  Not that there is anything that  
is
particularly complicated in your proposal.  Practically every config  
knob
on the home network has a cost associated with it, often a large cost.

Mark



--Apple-Mail-43-1040854696
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On 10/08/2009, at =
10:33 AM, Joe Touch wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: -webkit-monospace; font-size: 14px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0; ">Users already have many similar =
things - DHCP, NAT, SSID default to<br>announce, etc. - "on" by default, =
and they allow the user to shut it off<br>or alter the =
configuration.</span></blockquote><div><br></div><div>Duplicate DHCP =
servers and double-NATs are a huge problem for vendors of</div><div>home =
networking equipment when the unskilled user needs to shut it off. =
&nbsp;</div><div>The user&nbsp;may need to shut it "off" when upgrading =
to a new 802.11N AP</div><div>and attaching it to an existing home =
gateway/router/NAT, for example. &nbsp;</div><div>Experience =
has&nbsp;shown&nbsp;that a&nbsp;majority of home users cannot do =
that&nbsp;</div><div>without making a service&nbsp;call&nbsp;to the =
vendor's 800 number or hiring&nbsp;</div><div>GeekSquad or some other =
service to&nbsp;reconfigure the network. &nbsp;The call =
to&nbsp;</div><div>the vendor typically costs the vendor tens =
of&nbsp;dollars,&nbsp;often for a device</div><div>that sells for under =
$50. &nbsp;GeekSquad, Firedog,&nbsp;etc. costs the =
non-</div><div>professional user about $150 or =
so.</div><div><br></div><div>It should make us more sensitive to HCI in =
the home when considering new</div><div>features that get exposed to =
users. &nbsp;Some HCI folks are very hot on social</div><div>controls =
and other innovations for this very =
reason.</div><div><br></div><div>That's the point I am trying to make. =
&nbsp;Not that there is anything that is</div><div>particularly =
complicated in your proposal. &nbsp;Practically every config =
knob&nbsp;</div><div>on the home network has a cost&nbsp;associated with =
it, often a large =
cost.</div><div><br></div><div>Mark</div><div><br></div></div><div><br></d=
iv></body></html>=

--Apple-Mail-43-1040854696--

From touch@ISI.EDU  Mon Aug 10 12:16:51 2009
Return-Path: <touch@ISI.EDU>
X-Original-To: homegate@core3.amsl.com
Delivered-To: homegate@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 65BF028C1C2; Mon, 10 Aug 2009 12:16:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6vqc1SuqyJg; Mon, 10 Aug 2009 12:16:49 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id C24B33A68AF; Mon, 10 Aug 2009 12:16:49 -0700 (PDT)
Received: from [75.212.197.1] (1.sub-75-212-197.myvzw.com [75.212.197.1]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7AJGUE0008061; Mon, 10 Aug 2009 12:16:32 -0700 (PDT)
Message-ID: <4A80720C.6020605@isi.edu>
Date: Mon, 10 Aug 2009 12:16:28 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
References: <CD75E101-E956-4682-A3CF-454986AC0C37@muada.com> <68A1E2ED-774A-40B2-B0A5-8A2F7EF59753@nokia.com> <4A7E4674.8050500@isi.edu> <69F7F1D9-3692-4CD1-98AC-4713196AB86D@cisco.com> <4A802B3B.8000002@isi.edu> <3B861838-20EC-451E-A095-0E528706E0A2@cisco.com> <4A8059E2.9010308@isi.edu> <AAEC3E48-8CE8-4098-8F9F-18D9CEAA9841@cisco.com>
In-Reply-To: <AAEC3E48-8CE8-4098-8F9F-18D9CEAA9841@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: TSV Area <tsv-area@ietf.org>, "homegate@ietf.org" <homegate@ietf.org>
Subject: Re: [homegate] support for fair-sharing in home gateways?
X-BeenThere: homegate@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Broadband Home Gateway Discussion <homegate.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 10 Aug 2009 19:16:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Mark,

Mark Baugher wrote:
> 
> On 10/08/2009, at 10:33 AM, Joe Touch wrote:
> 
>> Users already have many similar things - DHCP, NAT, SSID default to
>> announce, etc. - "on" by default, and they allow the user to shut it off
>> or alter the configuration.
> 
> Duplicate DHCP servers and double-NATs are a huge problem for vendors of
> home networking equipment when the unskilled user needs to shut it off.  
> The user may need to shut it "off" when upgrading to a new 802.11N AP
> and attaching it to an existing home gateway/router/NAT, for example.  

I've seen this sort of thing done lots of places and it works fine.

For any default service, the user *may* need to shut it off, but frankly
fair-sharing is far less intrusive than services that are already
defaulted-on, e.g., NAT, SSID-announce, wifi channel selection, etc.

...
> That's the point I am trying to make.  Not that there is anything that is
> particularly complicated in your proposal.  Practically every config knob 
> on the home network has a cost associated with it, often a large cost.

The cost of what I'm suggesting needs to be compared to the context of
other costs. "fair sharing" does cost CPU and buffer memory, but the
benefit -- esp. to naiive users -- is large. As a configuration
addition, it's in the decimal points compared to most home gateway
capabilities.

- ---

My concern is that home gateways often get used in ways that aren't what
most people think is typical. Kids show up with devices that just
connect. Devices exchange large files without explicit user invocation.
Large groups of devices come and go frequently.

Current home gateways fail on two main points right now:
	1) a single user can swamp the pipe
	(e.g., updating their facebook page, or doing
	a bittorrent xfer without knowing it)

	2) flux in the set of users, or large sets of users,
	can bring DHCP to its knees

We saw this when we deployed Tethernet (www.isi.edu/tethernet), a
home-gateway style device that has additional features. Even when it
operated as a regular home gateway - even with a ethernet uplink - we
found that having fair sharing ON and having a reasonably robust DHCP
server was useful. We used it to support conferences (Infocom, Sigcomm),
groups of several dozen demos (DARPA PI meetings, DISCEX conference, NSF
meetings), and various other large meetings at hotels and in homes.

None if this is hard, but existing home gateways fall flat on these
points, and it's worth (a) noting and (b) avoiding.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqAcgwACgkQE5f5cImnZrsnXACgnDA+FrzpjlNu2Fq2FogNgdpR
apEAmwUZ0yvCAJEjnYPUXmYftpNVuKCw
=8ktG
-----END PGP SIGNATURE-----