From mailnull@www1.ietf.org Fri Nov 8 02:58:49 2002 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 CAA09850 for ; Fri, 8 Nov 2002 02:58:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gA880xx03062 for diffserv-archive@odin.ietf.org; Fri, 8 Nov 2002 03:00:59 -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 gA87f2v01976; Fri, 8 Nov 2002 02:41:02 -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 gA7KZ2v15411 for ; Thu, 7 Nov 2002 15:35:02 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08965 for <1timer>; Thu, 7 Nov 2002 15:11:40 -0500 (EST) Message-Id: <200211072011.PAA08965@ietf.org> From: The IESG To: All IETF Working Groups: ; x-msg: NoteWell Date: Thu, 07 Nov 2002 15:11:40 -0500 Subject: [Diffserv] Note Well Statement 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , From time to time, especially just before a meeting, this statement is to be sent to each and every IETF working group mailing list. =========================================================================== NOTE WELL All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to - the IETF plenary session, - any IETF working group or portion thereof, - the IESG, or any member thereof on behalf of the IESG, - the IAB or any member thereof on behalf of the IAB, - any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, - the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. _______________________________________________ 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 From mailnull@www1.ietf.org Mon Nov 25 09:00:01 2002 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 JAA28223 for ; Mon, 25 Nov 2002 09:00:01 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAPE2Fi02150 for diffserv-archive@odin.ietf.org; Mon, 25 Nov 2002 09:02:15 -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 gAPDhAv01085; Mon, 25 Nov 2002 08:43:10 -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 gAPDLxv32266 for ; Mon, 25 Nov 2002 08:21:59 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26507; Mon, 25 Nov 2002 08:19:13 -0500 (EST) Message-Id: <200211251319.IAA26507@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: diffserv@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 25 Nov 2002 08:19:13 -0500 Subject: [Diffserv] I-D ACTION:draft-bless-diffserv-multicast-05.txt 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IP Multicast in Differentiated Services Networks Author(s) : R. Bless, K. Wehrle Filename : draft-bless-diffserv-multicast-05.txt Pages : 33 Date : 2002-11-22 This document identifies problems which will arise when IP Multicast is used in Differentiated Services (DS) networks. Although the basic DS forwarding mechanisms also work with IP Multicast, some facts have to be considered which are related to the provisioning of multicast resources. The presented problems mainly lead to situations in which other service users are affected adversely in their experienced quality. An adequate solution is described in this document. It provides the necessary resource decoupling for protecting reserved resources until admission control is performed. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-bless-diffserv-multicast-05.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-bless-diffserv-multicast-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-bless-diffserv-multicast-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-11-22112443.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-bless-diffserv-multicast-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-bless-diffserv-multicast-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-11-22112443.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ 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 From mailnull@www1.ietf.org Mon Nov 25 12:18:55 2002 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 MAA10734 for ; Mon, 25 Nov 2002 12:18:55 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAPHLBX16024 for diffserv-archive@odin.ietf.org; Mon, 25 Nov 2002 12:21:11 -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 gAPGuav13109; Mon, 25 Nov 2002 11:56:36 -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 gAPGh2v12634 for ; Mon, 25 Nov 2002 11:43:02 -0500 Received: from iramx2.ira.uni-karlsruhe.de (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07703 for ; Mon, 25 Nov 2002 11:40:14 -0500 (EST) Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5] helo=irams1.ira.uka.de) by iramx2.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian)) id 18GMK0-0002TM-00 for ; Mon, 25 Nov 2002 17:42:56 +0100 Received: from i72pc127.tm.uni-karlsruhe.de ([141.3.70.78] helo=tpce10.ipv6.tm.uka.de) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 (Debian)) id 18GMK1-0007Hv-00 for ; Mon, 25 Nov 2002 17:42:57 +0100 Received: from tpce10.ipv6.tm.uka.de (localhost [127.0.0.1]) by tpce10.ipv6.tm.uka.de (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id gAPGgQe08984 for ; Mon, 25 Nov 2002 17:42:26 +0100 Resent-Message-Id: <200211251642.gAPGgQe08984@tpce10.ipv6.tm.uka.de> Received: from localhost (localhost [127.0.0.1]) by tpce10.ipv6.tm.uka.de (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id gAPELAe08085 for ; Mon, 25 Nov 2002 15:21:10 +0100 Received: from irams1.ira.uni-karlsruhe.de [141.3.10.5] by localhost with POP3 (fetchmail-5.9.0) for bless@localhost (single-drop); Mon, 25 Nov 2002 15:21:10 +0100 (CET) Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80]) by irams1.ira.uka.de with esmtp (Exim 3.30 #7 (Debian)) id 18GK5T-0002Fh-00 for ; Mon, 25 Nov 2002 15:19:47 +0100 Received: from exim by iramx1.ira.uni-karlsruhe.de with spam-scanned (Exim 3.30 #10 (Debian)) id 18GK5K-0007lx-00 for ; Mon, 25 Nov 2002 15:19:45 +0100 Received: from loki.ietf.org ([132.151.1.177]) by iramx1.ira.uni-karlsruhe.de with esmtp (Exim 3.30 #10 (Debian)) id 18GK4s-0007k4-00; Mon, 25 Nov 2002 15:19:10 +0100 Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA05654 for ietf-123-outbound.06@ietf.org; Mon, 25 Nov 2002 08:45:00 -0500 (EST) Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id IAA05312 for ; Mon, 25 Nov 2002 08:20:06 -0500 (EST) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26063 for ; Mon, 25 Nov 2002 08:17:24 -0500 (EST) Message-Id: <200211251317.IAA26063@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Date: Mon, 25 Nov 2002 08:17:24 -0500 X-Spam-Status: No, hits=-95.1 required=5.0 tests=TO_MALFORMED,NO_REAL_NAME,DOUBLE_CAPSWORD,EXCUSE_6, USER_IN_WHITELIST version=2.31 Resent-To: diffserv@ietf.org Resent-Date: Mon, 25 Nov 2002 17:42:26 +0100 Resent-From: Roland Bless Subject: [Diffserv] I-D ACTION:draft-bless-diffserv-pdb-le-01.txt 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : A Lower Effort Per-Domain Behavior for Differentiated Services Author(s) : R. Bless et al. Filename : draft-bless-diffserv-pdb-le-01.txt Pages : 16 Date : 2002-11-21 This document proposes a differentiated services per-domain behavior (PDB) whose traffic may be 'starved' (although starvation is not strictly required) in a properly functioning network. This is in contrast to the Internet's 'best-effort' or 'normal Internet traffic' model where prolonged starvation indicates network problems. In this sense the proposed PDB's traffic is forwarded with a 'lower' priority than the normal 'best-effort' Internet traffic, thus the PDB is called 'Lower Effort' (LE). Use of this PDB permits a network operator to strictly limit the effect of its traffic on 'best- effort'/'normal' or all other Internet traffic. This document gives some example uses, but does not propose constraining the PDB's use to any particular type of traffic. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-bless-diffserv-pdb-le-01.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-bless-diffserv-pdb-le-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-bless-diffserv-pdb-le-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2002-11-21133626.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-bless-diffserv-pdb-le-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-bless-diffserv-pdb-le-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-11-21133626.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ 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 From mailnull@www1.ietf.org Tue Nov 26 18:29:06 2002 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 SAA26352 for ; Tue, 26 Nov 2002 18:29:06 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAQNVQI03120 for diffserv-archive@odin.ietf.org; Tue, 26 Nov 2002 18:31:26 -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 gAQNHDv02286; Tue, 26 Nov 2002 18:17:13 -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 gAQMwwv01081 for ; Tue, 26 Nov 2002 17:58:58 -0500 Received: from mailman.packetdesign.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24676 for ; Tue, 26 Nov 2002 17:56:07 -0500 (EST) Received: from packetdesign.com (dhcp-168-0-13.packetdesign.com [192.168.0.13]) by mailman.packetdesign.com (8.12.3/8.12.3) with ESMTP id gAQMwo4D003880 for ; Tue, 26 Nov 2002 14:58:51 -0800 (PST) (envelope-from nichols@packetdesign.com) Message-ID: <3DE3FE1F.1060700@packetdesign.com> Date: Tue, 26 Nov 2002 15:05:03 -0800 From: Kathleen Nichols User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20020930 X-Accept-Language: en-us, en MIME-Version: 1.0 To: diffserv@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Diffserv] new version of draft on LE PDB 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit There's a new version of the draft on the LE PDB at: http://www.ietf.org/internet-drafts/draft-bless-diffserv-pdb-le-01.txt The intention is to move this draft forward as a PDB RFC, according to RFC3086. So, with that in mind, we'd like to note that the draft is open for discussion on the list. Kathie Nichols Brian Carpenter Diffserv co-chairs _______________________________________________ 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 From mailnull@www1.ietf.org Wed Nov 27 09:54:43 2002 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 JAA13001 for ; Wed, 27 Nov 2002 09:54:43 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAREuwg31387 for diffserv-archive@odin.ietf.org; Wed, 27 Nov 2002 09:56:58 -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 gAREgYv30488; Wed, 27 Nov 2002 09:42:34 -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 gAREVBv29389 for ; Wed, 27 Nov 2002 09:31:11 -0500 Received: from smtp.postech.ac.kr (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11316 for ; Wed, 27 Nov 2002 09:28:24 -0500 (EST) Received: from comus (comus.postech.ac.kr [141.223.92.55]) by smtp.postech.ac.kr (v3smtp 8.11.6.6/8.11.1) with SMTP id gAREV4008406 for ; Wed, 27 Nov 2002 23:31:04 +0900 (KST) From: "Geunhyung Kim" To: "diffserv" Date: Wed, 27 Nov 2002 23:30:29 +0900 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by www1.ietf.org id gAREVCv29390 Subject: [Diffserv] SLA & admission control 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 8bit 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 From mailnull@www1.ietf.org Wed Nov 27 11:36:44 2002 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 ; 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 ; 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 ; 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 ; 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 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 Cc: diffserv Subject: Re: [Diffserv] SLA & admission control References: 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-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 From mailnull@www1.ietf.org Wed Nov 27 22:59:38 2002 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 WAA08078 for ; Wed, 27 Nov 2002 22:59:38 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAS421R14111 for diffserv-archive@odin.ietf.org; Wed, 27 Nov 2002 23:02:01 -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 gAS3klv13550; Wed, 27 Nov 2002 22:46:47 -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 gAS3Ziv12729 for ; Wed, 27 Nov 2002 22:35:44 -0500 Received: from augean.eleceng.adelaide.edu.au (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07604 for ; Wed, 27 Nov 2002 22:32:46 -0500 (EST) Received: from eleceng.adelaide.edu.au (citr2.eleceng.adelaide.edu.au [129.127.29.38]) by augean.eleceng.adelaide.edu.au (8.10.1/8.10.1/ElecEng-1.0) with ESMTP id gAS3ZPb06238; Thu, 28 Nov 2002 14:05:25 +1030 (CST) Message-ID: <3DE58EFD.1E7B72FE@eleceng.adelaide.edu.au> Date: Thu, 28 Nov 2002 14:05:25 +1030 From: Amoakoh Gyasi-Agyei Organization: Centre for Internet Technology Research (CITR) X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: diffserv@ietf.org, geunkim@postech.ac.kr, brian@hursley.ibm.com, Amoakoh References: <20021127170001.8078.4096.Mailman@www1.ietf.org> Content-Type: multipart/mixed; boundary="------------0E3310F016866FF5D62A29C6" Subject: [Diffserv] SLA & admission control in DiffServ 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , This is a multi-part message in MIME format. --------------0E3310F016866FF5D62A29C6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Should the SLA be static or dynamically negotiated? Assuming a static SLA with bandwidth limit, how can the service provider guarantee the SLA on a connection with a wireless component which is spatio-temporarily varying and whose bandwidth can degrade ungraciously? What is the need to differentiate a policer from an admission controller? So, Brian, do you mean that the admission controller in this case will operate in the traffic source while the policer sits somewhere else or be integrated? I just do not know why and how some of these functionalities were separated although their functionalities appear to be very similar, if not identical. Thanks, Amoakoh > > Message: 3 > Date: Wed, 27 Nov 2002 17:17:57 +0100 > From: Brian E Carpenter > Organization: IBM > To: Geunhyung Kim > Cc: diffserv > Subject: Re: [Diffserv] SLA & admission control > > 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 > _______________________________________________________ Amoakoh Gyasi-Agyei Centre for Internet Technology Research (CITR) Electrical & Electronic Engineering Department Adelaide University Tel: +61 8 8303 6209 (office) Tel: +61 402 638 141 (mbl) Fax: +61 8 8303 4405 http://aaron.eleceng.adelaide.edu.au/Personal/amoakoh/ --------------0E3310F016866FF5D62A29C6 Content-Type: text/x-vcard; charset=us-ascii; name="amoakoh.vcf" Content-Description: Card for Amoakoh Gyasi-Agyei Content-Disposition: attachment; filename="amoakoh.vcf" Content-Transfer-Encoding: 7bit begin:vcard n:Gyasi-Agyei;Amoakoh tel;cell:+61 402 638 141 tel;fax:+61 8 8303 4405 tel;work:+61 8 8303 6209 x-mozilla-html:FALSE adr:;;;;;; version:2.1 email;internet:Amoakoh@eleceng.adelaide.edu.au fn:Amoakoh end:vcard --------------0E3310F016866FF5D62A29C6-- _______________________________________________ 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 From mailnull@www1.ietf.org Thu Nov 28 03:50:38 2002 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 DAA23117 for ; Thu, 28 Nov 2002 03:50:38 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gAS8r2Y05709 for diffserv-archive@odin.ietf.org; Thu, 28 Nov 2002 03:53:02 -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 gAS8Zrv04427; Thu, 28 Nov 2002 03:35:53 -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 gAS8Pev04109 for ; Thu, 28 Nov 2002 03:25:40 -0500 Received: from d12lmsgate-3.de.ibm.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22752 for ; Thu, 28 Nov 2002 03:22:45 -0500 (EST) Received: from d12relay01.de.ibm.com (d12relay01.de.ibm.com [9.165.215.22]) by d12lmsgate-3.de.ibm.com (8.12.3/8.12.3) with ESMTP id gAS8P8C3077718; Thu, 28 Nov 2002 09:25:14 +0100 Received: from etzel.zurich.ibm.com (etzel.zurich.ibm.com [9.4.64.140]) by d12relay01.de.ibm.com (8.12.3/NCO/VER6.4) with SMTP id gAS8P4wW047486; Thu, 28 Nov 2002 09:25:06 +0100 Received: from dhcp23-27.zurich.ibm.com by etzel.zurich.ibm.com (AIX 4.3/UCB 5.64/4.03) id AA44872 from ; Thu, 28 Nov 2002 09:24:58 +0100 Message-Id: <3DE5D2C3.A315616E@hursley.ibm.com> Date: Thu, 28 Nov 2002 09:24:35 +0100 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en,fr,de Mime-Version: 1.0 To: Amoakoh Gyasi-Agyei Cc: diffserv@ietf.org Subject: Re: [Diffserv] SLA & admission control in DiffServ References: <20021127170001.8078.4096.Mailman@www1.ietf.org> <3DE58EFD.1E7B72FE@eleceng.adelaide.edu.au> 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Would you sign a contract to guarantee bandwidth on a variable bandwidth network? I wouldn't, so what you are describing is an SLA that should never exist. I don't know what a dynamic SLA is. We certainly don't have any standards for such things. You might well have rate control in a source, admission control in an ingress router, and policing in a downstream router. I suggest you read RFC 3086 and RFC 3290. Brian Amoakoh Gyasi-Agyei wrote: > > Hi, > > Should the SLA be static or dynamically negotiated? Assuming a static SLA with bandwidth limit, how can the service provider guarantee the > SLA on a connection with a wireless component which is spatio-temporarily varying and whose bandwidth can degrade ungraciously? What is > the need to differentiate a policer from an admission controller? > > So, Brian, do you mean that the admission controller in this case will operate in the traffic source while the policer sits somewhere else > or be integrated? I just do not know why and how some of these functionalities were separated although their functionalities appear to be > very similar, if not identical. > > Thanks, > Amoakoh > > > > > Message: 3 > > Date: Wed, 27 Nov 2002 17:17:57 +0100 > > From: Brian E Carpenter > > Organization: IBM > > To: Geunhyung Kim > > Cc: diffserv > > Subject: Re: [Diffserv] SLA & admission control > > > > 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 > > > > _______________________________________________________ > Amoakoh Gyasi-Agyei > Centre for Internet Technology Research (CITR) > Electrical & Electronic Engineering Department > Adelaide University > Tel: +61 8 8303 6209 (office) > Tel: +61 402 638 141 (mbl) > Fax: +61 8 8303 4405 > http://aaron.eleceng.adelaide.edu.au/Personal/amoakoh/ -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Brian E Carpenter Distinguished Engineer, Internet Standards & Technology, IBM On assignment at the IBM Zurich Laboratory, Switzerland _______________________________________________ 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 From mailnull@www1.ietf.org Thu Nov 28 05:19:56 2002 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 FAA24549 for ; Thu, 28 Nov 2002 05:19:56 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gASAMBx11052 for diffserv-archive@odin.ietf.org; Thu, 28 Nov 2002 05:22:11 -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 gASAAav10461; Thu, 28 Nov 2002 05:10:36 -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 gASA2Jv09595 for ; Thu, 28 Nov 2002 05:02:19 -0500 Received: from web13905.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA24164 for ; Thu, 28 Nov 2002 04:59:33 -0500 (EST) Message-ID: <20021128100217.39177.qmail@web13905.mail.yahoo.com> Received: from [138.96.192.3] by web13905.mail.yahoo.com via HTTP; Thu, 28 Nov 2002 02:02:17 PST Date: Thu, 28 Nov 2002 02:02:17 -0800 (PST) From: SERBAN Rares Subject: Re: [Diffserv] SLA & admission control in DiffServ To: Brian E Carpenter , Amoakoh Gyasi-Agyei Cc: diffserv@ietf.org In-Reply-To: <3DE5D2C3.A315616E@hursley.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: , List-Id: Diffserv Discussion List List-Post: List-Help: List-Subscribe: , I have a question: Which part from Diffserv SLA could be negotiated in the case of Dynamic SLA? Which are the funcionalities from Diffserv involved in this negociation/re-negotiation? Thank you, R. --- Brian E Carpenter wrote: > Would you sign a contract to guarantee bandwidth on > a variable > bandwidth network? I wouldn't, so what you are > describing is > an SLA that should never exist. > > I don't know what a dynamic SLA is. We certainly > don't have any > standards for such things. > > You might well have rate control in a source, > admission control > in an ingress router, and policing in a downstream > router. > I suggest you read RFC 3086 and RFC 3290. > > Brian > > Amoakoh Gyasi-Agyei wrote: > > > > Hi, > > > > Should the SLA be static or dynamically > negotiated? Assuming a static SLA with bandwidth > limit, how can the service provider guarantee the > > SLA on a connection with a wireless component > which is spatio-temporarily varying and whose > bandwidth can degrade ungraciously? What is > > the need to differentiate a policer from an > admission controller? > > > > So, Brian, do you mean that the admission > controller in this case will operate in the traffic > source while the policer sits somewhere else > > or be integrated? I just do not know why and how > some of these functionalities were separated > although their functionalities appear to be > > very similar, if not identical. > > > > Thanks, > > Amoakoh > > > > > > > > Message: 3 > > > Date: Wed, 27 Nov 2002 17:17:57 +0100 > > > From: Brian E Carpenter > > > Organization: IBM > > > To: Geunhyung Kim > > > Cc: diffserv > > > Subject: Re: [Diffserv] SLA & admission control > > > > > > 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 > > > > > > > > _______________________________________________________ > > Amoakoh Gyasi-Agyei > > Centre for Internet Technology Research (CITR) > > Electrical & Electronic Engineering Department > > Adelaide University > > Tel: +61 8 8303 6209 (office) > > Tel: +61 402 638 141 (mbl) > > Fax: +61 8 8303 4405 > > > http://aaron.eleceng.adelaide.edu.au/Personal/amoakoh/ > > -- > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - > Brian E Carpenter > Distinguished Engineer, Internet Standards & > Technology, IBM > On assignment at the IBM Zurich Laboratory, > Switzerland > _______________________________________________ > 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 > __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com _______________________________________________ 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