Re: [Diffserv] SLA & admission control

Brian E Carpenter <brian@hursley.ibm.com> Wed, 27 November 2002 16:36 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17983 for <diffserv-archive@odin.ietf.org>; Wed, 27 Nov 2002 11:36:43 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gARGd0806813 for diffserv-archive@odin.ietf.org; Wed, 27 Nov 2002 11:39:00 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGR6v05116; Wed, 27 Nov 2002 11:27:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gARGIkv04811 for <diffserv@optimus.ietf.org>; Wed, 27 Nov 2002 11:18:46 -0500
Received: from d06lmsgate-5.uk.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16953 for <diffserv@ietf.org>; Wed, 27 Nov 2002 11:15:58 -0500 (EST)
Received: from d06relay01.portsmouth.uk.ibm.com (d06relay01.portsmouth.uk.ibm.com [9.166.84.147]) by d06lmsgate-5.uk.ibm.com (1.0.0) with ESMTP id QAA46778; Wed, 27 Nov 2002 16:17:49 GMT
Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d06relay01.portsmouth.uk.ibm.com (8.12.3/NCO/VER6.4) with SMTP id gARGIMZt038032; Wed, 27 Nov 2002 16:18:22 GMT
Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA35068 from <brian@hursley.ibm.com>; Wed, 27 Nov 2002 17:18:19 +0100
Message-Id: <3DE4F035.B8F91CA@hursley.ibm.com>
Date: Wed, 27 Nov 2002 17:17:57 +0100
From: Brian E Carpenter <brian@hursley.ibm.com>
Organization: IBM
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en,fr,de
Mime-Version: 1.0
To: Geunhyung Kim <geunkim@postech.ac.kr>
Cc: diffserv <diffserv@ietf.org>
Subject: Re: [Diffserv] SLA & admission control
References: <BOEGLMDCEOOEELFHJBGCGEHNDFAA.geunkim@postech.ac.kr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: diffserv-admin@ietf.org
Errors-To: diffserv-admin@ietf.org
X-BeenThere: diffserv@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=unsubscribe>
List-Id: Diffserv Discussion List <diffserv.ietf.org>
List-Post: <mailto:diffserv@ietf.org>
List-Help: <mailto:diffserv-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/diffserv>, <mailto:diffserv-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

It depends on the PDB in use. If it has a bandwidth limit,
then ingress policing will be used to discard excess traffic.
In this case, it may be desirable to apply admission control,
rather than let the policing throw traffic away. Actually,
that is something that the SLA should specify.

     Brian

Geunhyung Kim wrote:
> 
> Hello, All,
> 
> I have some confusion about the SLA and admission control.
> When the provider contracts the SLA with the customer
>  - the provide check if the network can support the SLA and the provider make the contract when the SLA can be supported.
> 
> As far as I know, when the SLA mechanism is used in the DiffServ domain, the admission control mechanism is not required, I thought.
> Is my thought correct ?
> If not, please let me know why the admission control is required after SLA is entered into agreement.
> 
> Thanks in advance,
> 
> Geunhyung Kim
> 
> None of us is as smart as all of us
> ==========================================
> Geunhyung Kim
> 
> E-mail: geunkim@postech.edu
> 
> Tel: +82-54-279-5655
> Fax: +82-54-279-5699
> 
> Networking & Distributed Systems Lab.
> CSE
> POSTECH
_______________________________________________
diffserv mailing list
diffserv@ietf.org
https://www1.ietf.org/mailman/listinfo/diffserv
Archive: http://www.ietf.org/mail-archive/working-groups/diffserv/current/maillist.html