[Diffserv] Re: Behavior Aggregates - where next?

Brian E Carpenter <brian@hursley.ibm.com> Tue, 16 May 2000 21:14 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 RAA12670 for <diffserv-archive@odin.ietf.org>; Tue, 16 May 2000 17:14:11 -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 QAA26995; Tue, 16 May 2000 16:44:13 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26964 for <diffserv@ns.ietf.org>; Tue, 16 May 2000 16:44:09 -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 QAA12281 for <diffserv@ietf.org>; Tue, 16 May 2000 16:44:06 -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 VAA71606 for <diffserv@ietf.org>; Tue, 16 May 2000 21:43:34 +0100
Received: from hursley.ibm.com (gsine04.us.sine.ibm.com [9.14.6.44]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id VAA29176 for <diffserv@ietf.org>; Tue, 16 May 2000 21:43:33 +0100 (BST)
Message-ID: <3921B2CF.301592B0@hursley.ibm.com>
Date: Tue, 16 May 2000 15:42:55 -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>
References: <38EA58D8.1093335D@hursley.ibm.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Diffserv] Re: 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

Obviously, now we've decided to use the phrase Per-Domain Behavior
instead of BA (across domains), the attached is slightly out of date-
the definition of BA in RFC 2475 does not need to be updated.
The rest is still valid if you replace BA by PDB.

  Brian

Brian E Carpenter wrote:
> 
> 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

-- 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Brian E Carpenter 
Program Director, Internet Standards & Technology, IBM 
On assignment for IBM at http://www.iCAIR.org 
Attend INET 2000: http://www.isoc.org/inet2000
Non-IBM email: brian@icair.org

_______________________________________________
diffserv mailing list
diffserv@ietf.org
http://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www-nrg.ee.lbl.gov/diff-serv-arch/