Re: [conex] Accounting of ConEx signals
"Scheffenegger, Richard" <rs@netapp.com> Fri, 07 October 2011 10:43 UTC
Return-Path: <rs@netapp.com>
X-Original-To: conex@ietfa.amsl.com
Delivered-To: conex@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4C5A21F877F for <conex@ietfa.amsl.com>; Fri, 7 Oct 2011 03:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.543
X-Spam-Level:
X-Spam-Status: No, score=-10.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PvtXF4ediyEF for <conex@ietfa.amsl.com>; Fri, 7 Oct 2011 03:43:21 -0700 (PDT)
Received: from mx3.netapp.com (mx3.netapp.com [217.70.210.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3CDC721F8B00 for <conex@ietf.org>; Fri, 7 Oct 2011 03:43:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.68,501,1312182000"; d="scan'208";a="269317598"
Received: from smtp3.europe.netapp.com ([10.64.2.67]) by mx3-out.netapp.com with ESMTP; 07 Oct 2011 03:46:32 -0700
Received: from amsrsexc1-prd.hq.netapp.com (amsrsexc1-prd.hq.netapp.com [10.64.251.107]) by smtp3.europe.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id p97AkT1Z021392; Fri, 7 Oct 2011 03:46:30 -0700 (PDT)
Received: from LDCMVEXC1-PRD.hq.netapp.com ([10.65.251.108]) by amsrsexc1-prd.hq.netapp.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 7 Oct 2011 12:46:30 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 07 Oct 2011 11:44:48 +0100
Message-ID: <5FDC413D5FA246468C200652D63E627A108AABB2@LDCMVEXC1-PRD.hq.netapp.com>
In-Reply-To: <20111007000031.GD2234@verdi>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [conex] Accounting of ConEx signals
Thread-Index: AcyEhCbmEuTvOWSgS0q/ennAiuCCHAAVzypA
References: <201110070115.27485.mkuehle@ikr.uni-stuttgart.de> <20111007000031.GD2234@verdi>
From: "Scheffenegger, Richard" <rs@netapp.com>
To: John Leslie <john@jlc.net>, Mirja K?hlewind <mirja.kuehlewind@ikr.uni-stuttgart.de>
X-OriginalArrivalTime: 07 Oct 2011 10:46:30.0221 (UTC) FILETIME=[5F3AFFD0:01CC84DE]
Cc: conex@ietf.org
Subject: Re: [conex] Accounting of ConEx signals
X-BeenThere: conex@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Congestion Exposure working group discussion list <conex.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/conex>, <mailto:conex-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/conex>
List-Post: <mailto:conex@ietf.org>
List-Help: <mailto:conex-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/conex>, <mailto:conex-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Oct 2011 10:43:21 -0000
Hi John, I tend to agree with you - on average, there will be little difference between counting packets, or counting bytes; However, if we don't agree on what is the "correct" approach beforehand and any box is free to account whatever, this may lead to exploits. On another example, if my ISP charges for the congestion volume, it is not irrelevant how this accounting is performed. And as soon as money is involved, this is a high incentive to cheat... IMHO, congestion volume (as defined) is measured in bytes, not packets; and as Conex is a IP-layer mechanism, the natural unit would be full IP packets (IP header + payload), which happens to be readily available by examining the header (although not as quick as simply accounting packets). For the sender transmitting variable sized packets, this may lead to a different number of conex marked packets (but more accurate byte-congestion volume), or vice versa. Richard Scheffenegger > > For most purposes, I think just counting the marks will suffice; > but clearly we shouldn't prohibit experiments counting something else. > > -- > John Leslie <john@jlc.net> > _______________________________________________ > conex mailing list > conex@ietf.org > https://www.ietf.org/mailman/listinfo/conex
- [conex] Accounting of ConEx signals Mirja Kühlewind
- Re: [conex] Accounting of ConEx signals John Leslie
- Re: [conex] Accounting of ConEx signals Scheffenegger, Richard
- Re: [conex] Accounting of ConEx signals John Leslie
- Re: [conex] Accounting of ConEx signals Christopher Morrow
- Re: [conex] Accounting of ConEx signals Mirja Kuehlewind
- Re: [conex] Accounting of ConEx signals Bob Briscoe
- Re: [conex] Accounting of ConEx signals Christopher Morrow
- Re: [conex] Accounting of ConEx signals John Leslie
- Re: [conex] Accounting of ConEx signals John Leslie
- Re: [conex] Accounting of ConEx signals Bob Briscoe
- Re: [conex] Accounting of ConEx signals Bob Briscoe
- Re: [conex] Accounting of ConEx signals John Leslie
- Re: [conex] Accounting of ConEx signals Bob Briscoe
- Re: [conex] Accounting of ConEx signals Mirja Kuehlewind
- Re: [conex] Accounting of ConEx signals Bob Briscoe
- Re: [conex] Accounting of ConEx signals Scheffenegger, Richard
- Re: [conex] Accounting of ConEx signals John Leslie
- Re: [conex] Accounting of ConEx signals Mirja Kuehlewind