[Tsvwg] Re: terminology issues in draft-floyd-tsvwg-besteffort - simple pair-wise relationships
Bob Briscoe <rbriscoe@jungle.bt.co.uk> Thu, 26 July 2007 12:53 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 1IE2pz-0000DZ-WB; Thu, 26 Jul 2007 08:53:04 -0400
Received: from tsvwg by megatron.ietf.org with local (Exim 4.43) id 1IE2py-0000DS-U3 for tsvwg-confirm+ok@megatron.ietf.org; Thu, 26 Jul 2007 08:53:02 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IE2py-0000DK-JC for tsvwg@ietf.org; Thu, 26 Jul 2007 08:53:02 -0400
Received: from smtp3.smtp.bt.com ([217.32.164.138]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IE2py-00033X-0l for tsvwg@ietf.org; Thu, 26 Jul 2007 08:53:02 -0400
Received: from i2kc08-ukbr.domain1.systemhost.net ([193.113.197.71]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:53:00 +0100
Received: from cbibipnt08.iuser.iroot.adidom.com ([147.149.100.81]) by i2kc08-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Jul 2007 13:53:00 +0100
Received: From bagheera.jungle.bt.co.uk ([132.146.168.158]) by cbibipnt08.iuser.iroot.adidom.com (WebShield SMTP v4.5 MR1a P0803.399); id 1185454379720; Thu, 26 Jul 2007 13:52:59 +0100
Received: from mut.jungle.bt.co.uk ([10.86.5.78]) by bagheera.jungle.bt.co.uk (8.13.5/8.12.8) with ESMTP id l6QCqrf5013224; Thu, 26 Jul 2007 13:52:57 +0100
Message-Id: <5.2.1.1.2.20070726134851.04e7f740@pop3.jungle.bt.co.uk>
X-Sender: rbriscoe@pop3.jungle.bt.co.uk
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Thu, 26 Jul 2007 13:53:08 +0100
To: Sally Floyd <sallyfloyd@mac.com>
From: Bob Briscoe <rbriscoe@jungle.bt.co.uk>
In-Reply-To: <9359d93f7aa2aa2768b04107fa12d5ef@mac.com>
References: <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk> <5.2.1.1.2.20070721102131.051439c0@pop3.jungle.bt.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: -1.36 () ALL_TRUSTED
X-Scanned-By: MIMEDefang 2.56 on 132.146.168.158
X-OriginalArrivalTime: 26 Jul 2007 12:53:00.0798 (UTC) FILETIME=[E5E4A1E0:01C7CF83]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
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
Sally, At 18:43 24/07/2007, Sally Floyd wrote: >>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". Good - that's v precise - thanks. re-ECN is a proposal to solely add an additional metric to IP. You are correct that all the possible economic structures that might be built over it are just what I predict might happen. And in that sense, it _can_ support a structure of simple pairwise relationships that could also give precise incentives for everyone to limit the congestion they cause. >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.) Understood. Cheers bob >- Sally >http://www.icir.org/floyd/ ____________________________________________________________________________ Bob Briscoe, <bob.briscoe@bt.com> Networks Research Centre, BT Research B54/77 Adastral Park,Martlesham Heath,Ipswich,IP5 3RE,UK. +44 1473 645196
- [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