[Diffserv] Behavior Aggregates - where next?
Brian E Carpenter <brian@hursley.ibm.com> Tue, 04 April 2000 21:32 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17180 for <diffserv-archive@ietf.org>; Tue, 4 Apr 2000 17:32:03 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA01846; Tue, 4 Apr 2000 17:02:31 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id RAA01815 for <diffserv@ns.ietf.org>; Tue, 4 Apr 2000 17:02:26 -0400 (EDT)
Received: from mail-gw.hursley.ibm.com (mail-gw.hursley.ibm.com [194.196.110.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16363 for <diffserv@ietf.org>; Tue, 4 Apr 2000 17:04:47 -0400 (EDT)
Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id WAA59032; Tue, 4 Apr 2000 22:04:14 +0100
Received: from hursley.ibm.com (gsine03.us.sine.ibm.com [9.14.6.43]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id WAA30144; Tue, 4 Apr 2000 22:04:13 +0100 (BST)
Message-ID: <38EA58D8.1093335D@hursley.ibm.com>
Date: Tue, 04 Apr 2000 16:04:24 -0500
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.61 [en] (Win98; I)
X-Accept-Language: en,fr
MIME-Version: 1.0
To: Diff Serv <diffserv@ietf.org>
CC: Kathleen Nichols <kmn@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Diffserv] Behavior Aggregates - where next?
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Diffserv Discussion List <diffserv.ietf.org>
X-BeenThere: diffserv@ietf.org
Content-Transfer-Encoding: 7bit
Following the diffserv discussion in Adelaide, we would like to clarify the motivation and direction for the work on BAs. Firstly, to clear out a terminology issue, the formal definition of a BA in RFC 2475 is slightly too restrictive and will require updating. Secondly, the plan is to continue the bottom-up approach adopted from the start of the diffserv work. Having defined a set of PHBs, the next step is to identify and quantify the characteristics that packets belonging to a behavior aggregate will experience as they cross a DS domain. This can result in an edge-to-edge quality of service definition. Enterprise network managers, and many ISPs, need a range of such definitions with numeric parameters, as an aid to deploying diffserv in a useful way. The diffserv WG charter was recently updated in response to this need. Thirdly, the intention now is to clarify draft-ietf-diffserv-ba-def-01.txt in view of the discussion. Also draft-ietf-diffserv-ba-vw-00.txt is a first draft of a "worked example" of a BA and it will undergo more revision. Finally, other BA drafts related to the various standard PHBs, including the Class Selectors, are solicited. Brian and Kathie diffserv co-chairs _______________________________________________ diffserv mailing list diffserv@ietf.org http://www.ietf.org/mailman/listinfo/diffserv Archive: http://www-nrg.ee.lbl.gov/diff-serv-arch/
- [Diffserv] Behavior Aggregates - where next? Brian E Carpenter
- [Diffserv] Re: Behavior Aggregates - where next? Brian E Carpenter