[Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - per flow or per user

Sally Floyd <sallyfloyd@mac.com> Tue, 24 July 2007 17:29 UTC

Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDOCD-0004je-O7; Tue, 24 Jul 2007 13:29:17 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1IDOCC-0004jW-9T for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:29:16 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDOCB-0004jO-Uo for tsvwg@ietf.org; Tue, 24 Jul 2007 13:29:15 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDOCB-0001cf-GV for tsvwg@ietf.org; Tue, 24 Jul 2007 13:29:15 -0400
Received: (qmail 14758 invoked by uid 0); 24 Jul 2007 17:21:39 -0000
Received: by simscan 1.2.0 ppid: 14751, pid: 14754, t: 0.7281s scanners: clamav: 0.90.2/m: spam: 3.1.8
X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on hiltonsmtp.worldspice.net
X-Spam-Level: ****
X-Spam-Status: No, score=4.2 required=6.5 tests=ALL_TRUSTED,BAYES_99 autolearn=disabled version=3.2.1
Received: from unknown (HELO ?172.28.169.190?) (sallyfloyd@67.97.210.2) by hiltonsmtp.worldspice.net with ESMTPA; 24 Jul 2007 17:21:38 -0000
In-Reply-To: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <80cbbf6f29fe311e534c72629df8b466@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:29:11 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - per flow or per user
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Bob -

> 4/ User policing: Bulk per-customer (in our simplest effective 
> proposal).
>
> Please don't imply that we're advocating per-flow policing. Admittedly 
> we have always shown how you could do either per-flow or per-user. 
> Before Oct-06 when I wrote that I-D on dismantling flow rate fairness, 
> the community wanted to be able to police flow rates, so we wanted to 
> show we could. But we neither require it nor recommend it. Our 
> per-user policing makes per-flow policing redundant (but it's still 
> there if an IPS wants it).
>
> For the avoidance of doubt, "Bulk per-customer" policing means 
> policing all traffic crossing the customer's sending access interface 
> using a bulk token bucket to regulate the bit rate of congestion 
> marked packets to all destinations together.

If you let me know where the draft implied that you were
advocating per-flow policing, I would be happy to correct it.
(I looked, but I didn't see it.)

The draft is not intended to be about any specific proposed mechanism.
It is simply in support of "simple best-effort traffic", and in support 
of
flow-based fairness for simple best-effort traffic.

- Sally
http://www.icir.org/floyd/