From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "alln-iport.cisco.com", Issuer "Cisco SSCA2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 9041C21F1A7 for ; Sun, 15 Dec 2013 23:34:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1709; q=dns/txt; s=iport; t=1387179294; x=1388388894; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Z7VTGsCGHQcKC8N1A5grkk3pobGv6SG4Mo2slZ45C90=; b=ZEDvI+3ZQCTBYcjLqZXh2JVndk5oJCKjJmOsFTIW7X8xbB7U106gDXC4 /1keQJASd/hs2Bmcc8zoELZ+D4cZHc3smxKxtzwcSFdwSa+8SE5JNN3R9 H5Kuijua8aH8/DB3eCQsbUTZCH0cAnqIE7AUpOU3wE+GPo4HOF4VnueGw 8=; X-Files: signature.asc : 195 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgMFAKWsrlKtJV2Y/2dsb2JhbABZgwqBDbhlgR4WdIIlAQEBAwF5BQsCAQhGMiUCBA4FDoduCMdLF48ZB4MjgRMEkDOBMYYykhSDKoIq X-IronPort-AV: E=Sophos;i="4.95,493,1384300800"; d="asc'?scan'208";a="7003326" Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-5.cisco.com with ESMTP; 16 Dec 2013 07:34:53 +0000 Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id rBG7Yr7v028088 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Dec 2013 07:34:53 GMT Received: from xmb-rcd-x09.cisco.com ([169.254.9.86]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Mon, 16 Dec 2013 01:34:52 -0600 From: "Fred Baker (fred)" To: Bob Briscoe Thread-Topic: [e2e] [aqm] What is a good burst? -- AQM evaluation guidelines Thread-Index: AQHO+jFOK/WIn67e5kiRmezjT1upVA== Date: Mon, 16 Dec 2013 07:34:52 +0000 Message-ID: <80CEFF86-8687-4266-B87C-8FB5B894D4DF@cisco.com> References: <9660C545-473C-4039-AB42-A12B7C761FC8@cisco.com> <201312152257.rBFMveZO022075@bagheera.jungle.bt.co.uk> In-Reply-To: <201312152257.rBFMveZO022075@bagheera.jungle.bt.co.uk> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: x-originating-ip: [10.19.64.114] Content-Type: multipart/signed; boundary="Apple-Mail=_74E31F59-A6A4-49D5-A8B3-725BF1044FF5"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 Cc: bloat , "aqm@ietf.org" , "" Subject: Re: [Bloat] [e2e] [aqm] What is a good burst? -- AQM evaluation guidelines X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 07:34:54 -0000 --Apple-Mail=_74E31F59-A6A4-49D5-A8B3-725BF1044FF5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Dec 15, 2013, at 2:57 PM, Bob Briscoe wrote: > Fred, >=20 > Jonathan Morton, Michael Scharf & I took Naeem's question to mean = "What should an AQM assume the size of a good burst is?" whereas I think = you and David C-B took the question to mean "What should an end-system = take the size of a good burst to be?". I can't comment on what he means. I took the question as "what should a = system that is in receipt of what it might consider a 'burst', and more = especially a 'good burst', to be?" I don't know that a sending transport (which is to be distinguished from = the queueing arrangement in that same system) or a receiving system = *has* a definition of a "good" or "bad" burst. The one is sending data, = which in the context of y two examples might be a good or bad idea, and = the other is receiving it. =46rom the receiver's perspective, the data = either arrived or it didn't; if it arrived, there is no real argument = for not delivering it to its application... --Apple-Mail=_74E31F59-A6A4-49D5-A8B3-725BF1044FF5 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="signature.asc" Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iD8DBQFSrq0abjEdbHIsm0MRAgMIAJ4lLmSETxkaMAigHrXGpPxbHp0fzACgn/ep I0xrsI7E7+2EKohbKjOvMCs= =IglE -----END PGP SIGNATURE----- --Apple-Mail=_74E31F59-A6A4-49D5-A8B3-725BF1044FF5--