[Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - simple pair-wise relationships
Sally Floyd <sallyfloyd@mac.com> Tue, 24 July 2007 17:43 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 1IDOQA-00051h-Vv; Tue, 24 Jul 2007 13:43:42 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1IDOQ8-0004zQ-VA for tsvwg-confirm+ok@megatron.ietf.org; Tue, 24 Jul 2007 13:43:40 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IDOQ8-0004zD-In for tsvwg@ietf.org; Tue, 24 Jul 2007 13:43:40 -0400
Received: from hiltonsmtp.worldspice.net ([216.37.94.58]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IDOQ8-000203-3K for tsvwg@ietf.org; Tue, 24 Jul 2007 13:43:40 -0400
Received: (qmail 15493 invoked by uid 0); 24 Jul 2007 17:36:04 -0000
Received: by simscan 1.2.0 ppid: 15480, pid: 15489, t: 0.7673s 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:36:03 -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: <9359d93f7aa2aa2768b04107fa12d5ef@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Date: Tue, 24 Jul 2007 10:43:35 -0700
To: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
X-Mailer: Apple Mail (2.624)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: "FLOYD, Sally" <floyd@acm.org>, tsvwg IETF list <tsvwg@ietf.org>, mallman@icir.org
Subject: [Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - simple pair-wise relationships
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
> 5/ Economic infrastructure: Simple pair-wise relationships (in our > simplest proposal) > > Please don't imply we're making economic infrastructure more complex. > All network layer relationships would still be between directly > connected neighbours (pairwise). > > Currently many border contracts between privately connected ISPs or > between ISPs and a peering exchange include an element of usage > charging (as well as interface capacity pricing). Whether based on > volume, on some notion of peak demand, or on a hybrid. We propose > adding a metric (congestion volume) that is only slightly less simple > than monthly byte-volume. > > However, congestion volume is much more effective, as it can be used > to make networks precisely accountable for the costs they cause in > other networks (unlike a volume metric, which depresses usage even > when the capacity is there for it). > > So most of the inter-domain contracts that currently include an > element of usage might switch to using congestion volume. And those > that don't include any form of usage measurements in their contracts > might stick that way. That doesn't make any contracts any more > complex. Our draft says the following: "The difficulties of deployment for end-to-end intserv or diffserv mechanisms are well-known, having in part to do with the difficulties of deployment for the economic infrastructure that would be needed [B03]. It seems likely that cost-based pricing based on re-ECN could also have a difficult deployment path, involving the deployment of ECN-marking at routers, policers at both ends of a connection, and a complex set of economic relationships [B07]." I would be happy to clarify it that the set of economic relationships required for "cost-based pricing based on re-ECN" would be pairwise, with a metric for congestion volume. (Note that this sentence is not about all possible forms of re-ECN, but about "cost-based pricing based on re-ECN". Our draft is not about re-ECN - 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/
- [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