[Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - flat monthly pricing
Sally Floyd <sallyfloyd@mac.com> Tue, 24 July 2007 17:16 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 1IDO0I-00010g-FF; Tue, 24 Jul 2007 13:16:58 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1IDO0G-0000xz-Ln for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:16:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDO0G-0000vU-59 for tsvwg@ietf.org; Tue, 24 Jul 2007 13:16:56 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDO0F-000120-PC for tsvwg@ietf.org; Tue, 24 Jul 2007 13:16:56 -0400
Received: (qmail 13974 invoked by uid 0); 24 Jul 2007 17:09:19 -0000
Received: by simscan 1.2.0 ppid: 13962, pid: 13970, t: 0.7565s 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:09:19 -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: <5a31970f1159b2e836c378b0e9c99e4c@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:16:51 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
Cc: tsvwg IETF list <tsvwg@ietf.org>, Mark Allman <mallman@icir.org>
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - flat monthly pricing
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
> 3/ User pricing: Flat monthly (in our simplest effective proposal). > > Please don't imply we're advocating user congestion pricing, given the > whole reason we brought re-ECN to the IETF back in 2005 was because we > found a way to limit congestion without constraining how operators > price their services to their customers. Specifically, re-ECN is > designed to work with flat monthly pricing. This draft is not about re-ECN. It is about the usefulness of "simple best-effort traffic", and the usefulness of flow-rate fairness for simple best-effort traffic. This draft is not about the presence or absence of flat monthly pricing for users. One could have flat monthly pricing with no other limitations, one could have flat monthly pricing with volume limits, or one could have flat monthly pricing with some form of "you get what you pay for". The first two forms don't result in "rich" users getting all of the bandwidth in times of high congestion (e.g., after the earthquake). The third form easily could. E.g., if all of the traffic was "you get what you pay for", even with flat monthly fees, then it could be really expensive to send packets in the time interval after the earthquake, or some other highly-congested period, and only the rich would be able to send packets. I would be opposed to setting such a "you get what you pay for" goal as the overriding goal for the global Internet, with or without flat monthly fees. - Sally http://www.icir.org/floyd/
- [Tsvwg] terminology issues in draft-floyd-tsvwg-b… Bob Briscoe
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Sally Floyd
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Sally Floyd
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Sally Floyd
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Sally Floyd
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Bob Briscoe
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Bob Briscoe
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Bob Briscoe
- [Tsvwg] Re: terminology issues in draft-floyd-tsv… Bob Briscoe