Jerry, From I-D: "Under normal non-congested network conditions, all CTs/services fully share all available bandwidth. When congestion occurs for a particular CTi, bandwidth reservation acts to prohibit traffic from other CTs from seizing the allocated capacity for CTi." Very basic question: Leaving alone all parameters and actual decision algorithms, do I get it right that it works something like this: Let's say I have CT0, CT1, CT2. Let's consider a particular link with capacity 100. Let's say in periods of complete contention I want CT0 to have access to 30, CT1 to 30 and CT2 to 40. Let's say we currently have some CT0 but little CT1 and CT2 : CT0=30, CT2=10, CT3=10 Then I think the whole idea is that CT0 would need to be allowed to grab more than 30. Right? So let's say CT0 actually takes 50. So we have CT0=50, CT2=10, CT3=10. And we're happy because we're smarter than MAM by allowing CT0 to exceed its max bandwith and thus increasing efficiency. But what happens if CT2 and CT3 later want to get their 30 and 40? Do we use preemption? Thanks Francois >> -----Original Message----- >> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] >> Sent: 18 October 2002 13:30 >> Subject: I-D ACTION:draft-ash-mpls-dste-bcmodel-max-alloc-resv-00.txt >> >> >> A New Internet-Draft is available from the on-line >> Internet-Drafts directories. >> >> >> Title : Max Allocation with Reservation BW >> Constraint Model >> for MPLS/DiffServ TE >> Author(s) : J. Ash >> Filename : >> draft-ash-mpls-dste-bcmodel-max-alloc-resv-00.txt >> Pages : 0 >> Date : 2002-10-17 >> >> This document is intended to complement the DiffServ-aware MPLS TE >> (DSTE) requirements document by describing the implications >> of some of >> the criteria for selecting a default bandwidth constraint model. >> Properties of a candidate model called maximum allocation with >> reservation (MAR) are presented, and its performance analyzed, to >> provide guidance to the corresponding DSTE protocol >> extensions document >> for selection of the default model. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ash-mpls-dste-bcmod el-max-alloc-resv-00.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-ash-mpls-dste-bcmodel-max-alloc-resv-00.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-ash-mpls-dste-bcmodel-max-alloc-resv-00.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.
Attachment:
draft-ash-mpls-dste-bcmodel-max-alloc-resv-00.URL
Description: draft-ash-mpls-dste-bcmodel-max-alloc-resv-00.URL