[Diffserv] Admission Control In DiffServ
"Ashkenazi, Liat (Liat)" <lashkena@avaya.com> Thu, 27 June 2002 11:46 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 HAA12387 for <diffserv-archive@odin.ietf.org>; Thu, 27 Jun 2002 07:46:04 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA26267 for diffserv-archive@odin.ietf.org; Thu, 27 Jun 2002 07:46:48 -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 HAA25752; Thu, 27 Jun 2002 07:41:42 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id GAA19375 for <diffserv@optimus.ietf.org>; Thu, 27 Jun 2002 06:31:51 -0400 (EDT)
Received: from ierw.net.avaya.com (ierw.net.avaya.com [198.152.13.101]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08620 for <diffserv@ietf.org>; Thu, 27 Jun 2002 06:31:07 -0400 (EDT)
Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA23828 for <diffserv@ietf.org>; Thu, 27 Jun 2002 06:30:01 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id GAA23806 for <diffserv@ietf.org>; Thu, 27 Jun 2002 06:30:00 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C21DC5.D666A2C1"
Date: Thu, 27 Jun 2002 13:31:46 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F15C045@IS0004AVEXU1.global.avaya.com>
Thread-Topic: Admission Control In DiffServ
Thread-Index: AcIdxbT39VWrgk/OTGmzguPy9Fk61A==
From: "Ashkenazi, Liat (Liat)" <lashkena@avaya.com>
To: diffserv@ietf.org
Subject: [Diffserv] Admission Control In DiffServ
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
Hello! I'm investigating the DiffServ Issue. I don’t understand how we can do admission control in DiffServ? How the administrator can know the condition of the network (is it loaded or available to get another “call”)? In ATM for example we know that the administrator check for each “call” if there is enough bandwidth and decide by advance the end to end path. How it works in DiffServ? Is there relation between the admission control and the routing algorithm? Thank You, Liat Ashkenazi. lashkena@avaya.com
- [Diffserv] Admission Control In DiffServ Ashkenazi, Liat (Liat)
- Re: [Diffserv] Admission Control In DiffServ Brian E Carpenter
- Re: [Diffserv] Admission Control In DiffServ iokumus
- Re: [Diffserv] Admission Control In DiffServ Brian E Carpenter