From owner-te-wg@ops.ietf.org  Thu May  1 11:49:52 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18395
	for <tewg-archive@lists.ietf.org>; Thu, 1 May 2003 11:49:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19BGG5-000Bey-00
	for te-wg-data@psg.com; Thu, 01 May 2003 15:46:05 +0000
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19BGFf-000Bdx-00
	for te-wg@ops.ietf.org; Thu, 01 May 2003 15:45:39 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h41FjaMp021047;
	Thu, 1 May 2003 15:45:36 GMT
Received: from zhangr2.info.net (lasi254.us.info.net [204.140.71.254])
	by delta.info.net  with ESMTP id PAA15725;
	Thu, 1 May 2003 15:45:33 GMT
Message-Id: <5.2.0.9.2.20030501072128.02619d68@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Thu, 01 May 2003 07:44:34 -0700
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
From: raymond zhang <zhangr@info.net>
Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt 
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155016A3AFF@nl0006exch001u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-26.0 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REPLY_WITH_QUOTES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Bert,
Sorry for the delayed response...

At 03:13 AM 4/25/2003 +0200, Wijnen, Bert (Bert) wrote:
>My summary:
>
>- a lot of text... but not very focused and to the point (or at least
>   I have trouble seeing the main points)
>- not a "framework", rather an exploration of TE measurement related topics
>   (more like  a summary-introduction)
>- I am not an operator, but I think if I were one, then
>   - if we were already doing TE measurement stuff (most likely) then
>     reading it seems a waste of time

Ray - Well, we have policies and implementations at different degrees for 
many of the areas touched upon by the draft but not all... It is indeed 
helpful to look at this as framework for any further work to refine our 
current processes.

>   - if we were not yet doing any of it... then I wonder if this would
>     be helpfull at all.
>- W.r.t. the TEM WG work item, it says:
>      The tewg interacts with the common control and measurement plane
>      working group to abstract and define those parameters, measurements,
>      and controls that traffic engineering needs in order to engineer
>      the network.
>   So I would expect a CRISP set of "requirements for additional measurements,
>   configurable/negotiable parameters/controls" ... but not the extensive
>   exploration and text that I now see. Why do people (or the WG) think
>   that this document meets the WG deliverable for TEM ??
>- W.r.t. review:
>   - 4 people from ATT support it. Waisum is one of them and is main editor.
>     Others (Nick Duffield, Bob Cole) have some of their material listed in
>     the doc.
>   - 3 EDU users commented, 2 said they found it a good doc
>     3rd one asked a few questions
>   - Raymond Zhang is positive. He is from info.net ??? is that an operator?

I am form INFONET ( a global SP).

>   - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
>     What role/function does he play/have? Operator, code/tool-developer?
>   - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
>     he/she added any comment. Do we know him/her?
>     What role/function does he/she play/have? Operator, code/tool-developer?
>   - Dimitri Papadimitrou (Alcatel) asked a question/suggested some text.
>     I did not see if he likes the doc or not
>   - Blain Christian (uunet, so maybe a real operator?) withdrew as co-editor
>     That does not sound good (in my view)
>- So where are the real operators that support this?
>
>My thought is that I can do two things:
>
>- send back to WG and say that this is "not good enough" and that I do not
>   feel comforatable to present it to IESG for approval.
>   It does NOT meet (in my eyes) the WG deliverable for TEM.
>- send it to IESG with my recommendation to NOT approve for same reasons.
>
>So let me try the first option first and ask the WG what they have to say
>to my review.
>
>Bert





From owner-te-wg@ops.ietf.org  Mon May  5 09:55:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA01984
	for <tewg-archive@lists.ietf.org>; Mon, 5 May 2003 09:55:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19CgNu-0004GG-00
	for te-wg-data@psg.com; Mon, 05 May 2003 13:52:02 +0000
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19CgNr-0004G2-00
	for te-wg@ops.ietf.org; Mon, 05 May 2003 13:51:59 +0000
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h45DpvW15854
	for <te-wg@ops.ietf.org>; Mon, 5 May 2003 09:51:57 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R198XQ3>; Mon, 5 May 2003 15:51:56 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155017C1829@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: raymond zhang <zhangr@info.net>, "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Mon, 5 May 2003 15:51:53 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-9.6 required=5.0
	tests=BAYES_10,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Inline
> -----Original Message-----
> From: raymond zhang [mailto:zhangr@info.net]
> Sent: donderdag 1 mei 2003 16:45
> To: Wijnen, Bert (Bert); Tewg (E-mail)
> Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt 
> 
> Hi Bert,
> Sorry for the delayed response...
> 
No problem.

> At 03:13 AM 4/25/2003 +0200, Wijnen, Bert (Bert) wrote:
> >My summary:
> >
> >- a lot of text... but not very focused and to the point (or at least
> >   I have trouble seeing the main points)
> >- not a "framework", rather an exploration of TE measurement 
> >   related topics (more like  a summary-introduction)
> >- I am not an operator, but I think if I were one, then
> >   - if we were already doing TE measurement stuff (most likely) then
> >     reading it seems a waste of time
> 
> Ray - Well, we have policies and implementations at different 
> degrees for many of the areas touched upon by the draft but 
> not all... It is indeed helpful to look at this as framework for
> any further work to refine our current processes.
> 
Do you really mean "framework" or is it more 
a "pool of things to consider"?

.. snip ..

> >   - Raymond Zhang is positive. He is from info.net ??? is that an operator?
> 
> I am form INFONET ( a global SP).
> 
Thanks for informing me. And appology that I did not know.

.. snip ..

Bert



From owner-te-wg@ops.ietf.org  Mon May  5 22:22:05 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24742
	for <tewg-archive@lists.ietf.org>; Mon, 5 May 2003 22:22:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Cs5Q-0002J3-00
	for te-wg-data@psg.com; Tue, 06 May 2003 02:21:44 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Cs5N-0002IS-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 02:21:41 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h462LZfQ028818;
	Mon, 5 May 2003 22:21:35 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h462LY0P028814;
	Mon, 5 May 2003 22:21:35 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 5 May 2003 22:21:34 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt 
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155016A3AFF@nl0006exch001u.nl.lucent.com>
Message-ID: <Pine.LNX.4.44.0305052209400.28411-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-16.1 required=5.0
	tests=BAYES_10,IN_REP_TO,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


So I think it is clear that we need to distill what is being recommended.

A bit of background - this WG item was intended to make the essential 
measurements needed well defined enough that the way these "entities" were 
measured across implementations (e.g. vendors) would be consistent.  There 
was some discussion about "chocolate ice cream" and consistency by an AD 
at one point but no-one understood the departed AD at that time - let 
alone now.  Suffice it to say that we are looking for a succinct enough 
set of definitions and recommendations that one could take a look at
an an instantiation of that (e.g. a mib) and know if we are measuring
things in the correct manner, and do we have a complete set of the
measurements we will need.

What we have at hand may or may not be a framework, however I think
at least some would agree that it is currently too abstract.  

I recommend we do the following clean up

- Somewhere provide a CRISP set of recommendations
- Remove all discussion which does not directly re-enforce a
  recommendation
- Run it back through WG last call
  - Maybe one option will be to remove the WG item completely

I have some specific feedback, but I'll do that separately.

thanks,

Jim




From owner-te-wg@ops.ietf.org  Mon May  5 23:26:12 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25544
	for <tewg-archive@lists.ietf.org>; Mon, 5 May 2003 23:26:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Ct6c-0006vC-00
	for te-wg-data@psg.com; Tue, 06 May 2003 03:27:02 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Ct6X-0006uv-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 03:26:57 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h463QufQ028910
	for <te-wg@ops.ietf.org>; Mon, 5 May 2003 23:26:56 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h463Qu3x028906
	for <te-wg@ops.ietf.org>; Mon, 5 May 2003 23:26:56 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 5 May 2003 23:26:56 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: draft-ietf-tewg-measure-05.txt comments
Message-ID: <Pine.LNX.4.44.0305052221520.28411-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-10.2 required=5.0
	tests=BAYES_20,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


At a high level the document is broken up into the following outline

1-3 Introduction
4   Definitions
5   Rational / Uses
6   Time scales
7   Readout / sampling / summarization
8   Bases  (e.g. node, link, path, node-pair)
9   Entities (e.g. traffic volume, delay, ...)
10  Types (Permute Bases x Entities - define what's valid)
11-14 Some blah blah (see specific comments too :)
15  Recommendations and Conclusion

At a high level I think we can ditch section 4 and move these into section 
8 and 9 as appropriate.  Sections 10-14 are interesting, but I don't think 
they are directly necessary in specifying recommendations on *measurement* 
(maybe what to do with the measurements, but no bearing on the measurement 
itself).  Section 10 or 15 would be good places for the CRISP 
recommendations.

Here are general comments:

- there is no discussion of the form of a measurement, e.g. should traffic 
volume be accumulated or a rate, should time (E.g. delay) be ms, ns, or 
seconds.  These twists could lead to inconsistency - where is that to be 
defined?

- "hold-time" of an LSP (aka uptime).  What about an RSVP session with
  signalled make-before-break?  If it were initially signalled at t=0,
  and then at t=5 it changed it's path, and let's say at t=10 it
  increased it's bandwidth, if at t=15 we ask how long it's been up
  what is the answer? 
  - also t=15, is that minutes - or hours? or do we not care as long
    as it is specified :)

- Statistical measures such as "variance" and other second order
  measurements.  I don't think this is a raw measurement as much as a
  calculated value.  Should nodes calculate this?  Over how many
  samples?  Why not just calculate offline based on the raw
  measurement?

- maybe expand on what you mean by per service class

- Flow measurement is a deep-hole, we should either defer to other
  standardization efforts on this, or we need to be a lot more
  concrete on what we need to know here.

- Node Pair -v- Path.  The Node-pair could replicate a lot of
  information that is available on a path basis.  Do we want that?
  The advantage might be some persistence in the measurement.  I think
  every router should have a counter for bytes switched to bgp
  nexthops, maybe something similar to a Node's known MPLS
  destinations (e.g. egresses for *mine* LSPs)

Here are specific comments:

Section 3, first sentence - the goal is not to have a "framework", the
goal is to foster consistent measurements across implementations for
traffic engineering purposes.

"To achieve multi-vendor interoperability..."  Not sure how
measurements on different systems can not be interoperable, maybe
multi-vendor consistency.

"Other principles such as concise reprensentation" - we should be
focussing on more than principles.  Maybe we should identify
guidelines for measurements.  E.g. not that we should have "accurate"
measurements, or even "traffic volume" -as much as that volume should
be represented in accumulated bytes.

"average hold-time" - you can only measure hold-time (more precisely
up-time of an LSP or Path).  You can calculate average hold-time
offline.  Are you suggesting that it is important that the node also
calculate this value?

Througput in section 4.3 suggest a possible sustainable rate, e.g. the
throughput of an OC192 is 10 Gbs (or something close to that), in
section 9.1 it looks like it is the amount of traffic which "passes".
I think 4.3 is more correct, is througput actually needed in 9.1?

Section 5.1 second paragraph (the one that is not bulletized).  I see
no value in this and suggest striking it.

Section 5.3.... hmmm...  Where is this applied?

Section 7.1 (data reduction), are we saying we want the node to store
data for periodic retrieval (e.g record retrieval) - or do we prefer
near real time polling techniques like SNMP (or both?).  Unless we are
saying exactly where we want record retrieval capability, I suggest
removing section 7.1

Similar argument on section 7.3 (summarization) - unless we say what
we want summarized on the node, and how, I suggest removing section
7.3

Ditto on section 7.4 (sampling).  Unless we say what should be sampled
how, why discuss?

Section 8.2 (interface / link base), on bundled links.  Bundled links
are links, so why call them out as special unless we have some
concrete way to handle them.  For instance do we want to somehow
stipulate that there should be measurement visibility on the bundle
and the component links, that they should somehow be tied together?
if so, what is the recommendation?

Section 8.4 (path-based base).  In first sentence, is it the
"route-pinning" that gives MPLS the means to develop path-based
measurement.  It think it's more the ability to tie an edge-to-edge
FEC into a specific LSP and then to have that FEC not visible (or
tunnelled) through transit nodes.  Thus ingress, transit and egress
nodes have the ability to distinquish and count on a per macro-flow
basis, and they all know what role they are relative to a particular LSP.

Section 9.1 (entities).  It may be best to move definities into here.
Currently you have "entitied, measurment unit class" and a bunch of
notes.  Some concise definitions might firm these up.

Delay - what if a node can not truly measure delay?  Should we say
there needs to be a way to state this?  Do we recommend active
measurement devices for this?

Packet Loss - It is said that it should be monitored, but no where
have we stated that we want to monitor the offered load, the accepted
load and the delivered load.  Or where we measure this (e.g if we
measure delivered load at the head-end, that implies some way to
propogate the information).  If we have accepted load at head-end and
delivered load at tail-end we can infer the packet loss - is this the
approach?  Are we missing a policed load on an LSP at the head end
(does anyone care?)

Section 9.2 - "To characterize paths ... the following entities may
possibly be dfined" (either say they need definition, or don't mention
them.

  - path setup / release delay - an interesting measurement, currently
    not readilly available.

  - path setup denial / error / etc probability - an offline calculation, so
    nix?

  - path restoration time - what about FRR?  would this be measured at
    transit node? communicated to head-end?

  At a node base, you may want to track setup attempts, failures,
  preempted sessions, optimization checks, maybe even average LSP
  uptime...

Section 10.1 Types.

No "X" on Interface / Throughput, should there be?

For Delay of a node-pair, what if you have multiple paths with
different delays.  Maybe "X" on node-pair delay is not good, as it can
be readily calculated from path delays for that node-pair.

Section 10.2 - does anyone really care how much control traffic is
consuming on their network.  For BGP traffic, was the intent the
sourced or anything that transits the node/link (and distinquish
in-my-net -v- across-my-net?) I suggest removing section 10.2 unless
folks care and can show where it is applied in a recommendation
(e.g. a type).

Section 10.2 through 14 was interesting to read, but did not provide
any direct bearing on what measurements are needed.  I suggest that
they be removed.

Section 15 -

"a standardized mechanism to detect ... label binding changes for LDP
..."  Why?

"Need for uniform measurement definitions across vendors and
operators" - that's the crux! that should be in the first sentance of
section 3 :)

" Need for higher order statistics... "  push it to the offline hosts

"Need for packet-sampled..."  "Need for offline bulk file transfer..."
The need needs to be better justified or removed.











From owner-te-wg@ops.ietf.org  Tue May  6 08:31:47 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18156
	for <tewg-archive@lists.ietf.org>; Tue, 6 May 2003 08:31:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19D1Z1-0007Jx-00
	for te-wg-data@psg.com; Tue, 06 May 2003 12:28:55 +0000
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19D1Yw-0007Je-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 12:28:50 +0000
Received: from bucket.cisco.com (IDENT:mirapoint@bucket.cisco.com [161.44.167.72])
	by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h46CSl4c000602;
	Tue, 6 May 2003 08:28:48 -0400 (EDT)
Received: from tnadeauw2k (che-vpn-cluster-1-4.cisco.com [10.86.240.4])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ADB16664;
	Tue, 6 May 2003 08:28:42 -0400 (EDT)
Reply-To: <tnadeau@cisco.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
To: "'Jim Boyle'" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Subject: RE: draft-ietf-tewg-measure-05.txt comments
Date: Tue, 6 May 2003 08:28:30 -0400
Organization: Cisco Systems, Inc.
Message-ID: <318c01c313cb$04473450$6401a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <Pine.LNX.4.44.0305052221520.28411-100000@fido.nc.rr.com>
Importance: Normal
X-Spam-Status: No, hits=-13.6 required=5.0
	tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


	A few comments inline.


> -----Original Message-----
> From: owner-te-wg@ops.ietf.org 
> [mailto:owner-te-wg@ops.ietf.org] On Behalf Of Jim Boyle
> Sent: Monday, May 05, 2003 11:27 PM
> To: te-wg@ops.ietf.org
> Subject: draft-ietf-tewg-measure-05.txt comments
> 
> 
> 
> At a high level the document is broken up into the following outline
> 
> 1-3 Introduction
> 4   Definitions
> 5   Rational / Uses
> 6   Time scales
> 7   Readout / sampling / summarization
> 8   Bases  (e.g. node, link, path, node-pair)
> 9   Entities (e.g. traffic volume, delay, ...)
> 10  Types (Permute Bases x Entities - define what's valid) 
> 11-14 Some blah blah (see specific comments too :) 15  
> Recommendations and Conclusion
> 
> At a high level I think we can ditch section 4 and move these 
> into section 
> 8 and 9 as appropriate.  Sections 10-14 are interesting, but 
> I don't think 
> they are directly necessary in specifying recommendations on 
> *measurement* 
> (maybe what to do with the measurements, but no bearing on 
> the measurement 
> itself).  Section 10 or 15 would be good places for the CRISP 
> recommendations.
> 
> Here are general comments:
> 
> - there is no discussion of the form of a measurement, e.g. 
> should traffic 
> volume be accumulated or a rate, should time (E.g. delay) be 
> ms, ns, or 
> seconds.  These twists could lead to inconsistency - where is 
> that to be 
> defined?
> 
> - "hold-time" of an LSP (aka uptime).  What about an RSVP session with
>   signalled make-before-break?  If it were initially signalled at t=0,
>   and then at t=5 it changed it's path, and let's say at t=10 it
>   increased it's bandwidth, if at t=15 we ask how long it's been up
>   what is the answer? 
>   - also t=15, is that minutes - or hours? or do we not care as long
>     as it is specified :)
> 
> - Statistical measures such as "variance" and other second order
>   measurements.  I don't think this is a raw measurement as much as a
>   calculated value.  Should nodes calculate this?  Over how many
>   samples?  Why not just calculate offline based on the raw
>   measurement?
> 
> - maybe expand on what you mean by per service class
> 
> - Flow measurement is a deep-hole, we should either defer to other
>   standardization efforts on this, or we need to be a lot more
>   concrete on what we need to know here.	

	Defer to the IPFX WG that is tackling this problem
right now.


> 
> - Node Pair -v- Path.  The Node-pair could replicate a lot of
>   information that is available on a path basis.  Do we want that?
>   The advantage might be some persistence in the measurement.  I think
>   every router should have a counter for bytes switched to bgp
>   nexthops, maybe something similar to a Node's known MPLS
>   destinations (e.g. egresses for *mine* LSPs)
> 
> Here are specific comments:
> 
> Section 3, first sentence - the goal is not to have a 
> "framework", the goal is to foster consistent measurements 
> across implementations for traffic engineering purposes.
> 
> "To achieve multi-vendor interoperability..."  Not sure how 
> measurements on different systems can not be interoperable, 
> maybe multi-vendor consistency.

	I think he might have been referring to the management
interfaces (i.e.: SNMP, CLI, XML, etc...), but you are
right that consistent is important as well (or at least 
well-understood).  For example, it is useful to know the
sampling rates/update times for statistics updates from
line cards, as they may be cached for some seconds.
If you are collecting stats from two different boxes with
two different intervals and your collection period is
small enough, this might make a difference.

> "Other principles such as concise reprensentation" - we 
> should be focussing on more than principles.  Maybe we should 
> identify guidelines for measurements.  E.g. not that we 
> should have "accurate" measurements, or even "traffic volume" 
> -as much as that volume should be represented in accumulated bytes.
> 
> "average hold-time" - you can only measure hold-time (more 
> precisely up-time of an LSP or Path).  You can calculate 
> average hold-time offline.  Are you suggesting that it is 
> important that the node also calculate this value?
> 
> Througput in section 4.3 suggest a possible sustainable rate, 
> e.g. the throughput of an OC192 is 10 Gbs (or something close 
> to that), in section 9.1 it looks like it is the amount of 
> traffic which "passes". I think 4.3 is more correct, is 
> througput actually needed in 9.1?
> 
> Section 5.1 second paragraph (the one that is not 
> bulletized).  I see no value in this and suggest striking it.
> 
> Section 5.3.... hmmm...  Where is this applied?
> 
> Section 7.1 (data reduction), are we saying we want the node 
> to store data for periodic retrieval (e.g record retrieval) - 
> or do we prefer near real time polling techniques like SNMP 
> (or both?).  

	I think that both types are needed depending on the
type of TE stats being gathered and what they are 
going to be used for later.

> Unless we are saying exactly where we want 
> record retrieval capability, I suggest removing section 7.1
> Similar argument on section 7.3 (summarization) - unless we 
> say what we want summarized on the node, and how, I suggest 
> removing section 7.3
> 
> Ditto on section 7.4 (sampling).  Unless we say what should 
> be sampled how, why discuss?
> 
> Section 8.2 (interface / link base), on bundled links.  
> Bundled links are links, so why call them out as special 
> unless we have some concrete way to handle them.  For 
> instance do we want to somehow stipulate that there should be 
> measurement visibility on the bundle and the component links, 
> that they should somehow be tied together? if so, what is the 
> recommendation?
> 
> Section 8.4 (path-based base).  In first sentence, is it the 
> "route-pinning" that gives MPLS the means to develop 
> path-based measurement.  It think it's more the ability to 
> tie an edge-to-edge FEC into a specific LSP and then to have 
> that FEC not visible (or
> tunnelled) through transit nodes.  Thus ingress, transit and 
> egress nodes have the ability to distinquish and count on a 
> per macro-flow basis, and they all know what role they are 
> relative to a particular LSP.
> 
> Section 9.1 (entities).  It may be best to move definities 
> into here. Currently you have "entitied, measurment unit 
> class" and a bunch of notes.  Some concise definitions might 
> firm these up.
> 
> Delay - what if a node can not truly measure delay?  Should 
> we say there needs to be a way to state this?  Do we 
> recommend active measurement devices for this?
> 
> Packet Loss - It is said that it should be monitored, but no 
> where have we stated that we want to monitor the offered 
> load, the accepted load and the delivered load.  Or where we 
> measure this (e.g if we measure delivered load at the 
> head-end, that implies some way to propogate the 
> information).  If we have accepted load at head-end and 
> delivered load at tail-end we can infer the packet loss - is 
> this the approach?  Are we missing a policed load on an LSP 
> at the head end (does anyone care?)
> 
> Section 9.2 - "To characterize paths ... the following 
> entities may possibly be dfined" (either say they need 
> definition, or don't mention them.
> 
>   - path setup / release delay - an interesting measurement, currently
>     not readilly available.
> 
>   - path setup denial / error / etc probability - an offline 
> calculation, so
>     nix?
> 
>   - path restoration time - what about FRR?  would this be measured at
>     transit node? communicated to head-end?
> 
>   At a node base, you may want to track setup attempts, failures,
>   preempted sessions, optimization checks, maybe even average LSP
>   uptime...
> 
> Section 10.1 Types.
> 
> No "X" on Interface / Throughput, should there be?
> 
> For Delay of a node-pair, what if you have multiple paths 
> with different delays.  Maybe "X" on node-pair delay is not 
> good, as it can be readily calculated from path delays for 
> that node-pair.
> 
> Section 10.2 - does anyone really care how much control 
> traffic is consuming on their network.  For BGP traffic, was 
> the intent the sourced or anything that transits the 
> node/link (and distinquish in-my-net -v- across-my-net?) I 
> suggest removing section 10.2 unless folks care and can show 
> where it is applied in a recommendation (e.g. a type).
> 
> Section 10.2 through 14 was interesting to read, but did not 
> provide any direct bearing on what measurements are needed.  
> I suggest that they be removed.
> 
> Section 15 -
> 
> "a standardized mechanism to detect ... label binding changes 
> for LDP ..."  Why?

	I agree. I have no idea why LDP bindings affect
the TE matrix.  This should probably be removed.

> 
> "Need for uniform measurement definitions across vendors and 
> operators" - that's the crux! that should be in the first 
> sentance of section 3 :)
> 
> " Need for higher order statistics... "  push it to the offline hosts
> 
> "Need for packet-sampled..."  "Need for offline bulk file 
> transfer..." The need needs to be better justified or removed.
> 

	I asked to have the offline stuff added. For the
collection of a traffic matrix, as you know, this 
entails the collection of a lot of data especially on
big core routers. It is preferable to use offline
bulk file transfer mechanisms such as NetFlow (being
standardized in IPFX now) or offline SNMP file transfers
of statistics snapshots.  This reduces the overhead of
the box having to service network management requests,
and also reduces the amount of network mgmt overhead
required to fetch the same amount of data if you 
collect your data as one big batch at some longer periodic
interval.

	--Tom


> 
> 
> 
> 
> 
> 
> 
> 
> 





From owner-te-wg@ops.ietf.org  Tue May  6 09:02:14 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19256
	for <tewg-archive@lists.ietf.org>; Tue, 6 May 2003 09:02:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19D273-000C8c-00
	for te-wg-data@psg.com; Tue, 06 May 2003 13:04:05 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19D270-000C8L-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 13:04:03 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h46CBaoH026208
	for <te-wg@ops.ietf.org>; Tue, 6 May 2003 09:04:01 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314301986AD4; Tue, 6 May 2003 09:03:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Tue, 6 May 2003 08:03:55 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A6794@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: AD review of: draft-ietf-tewg-measure-05.txt 
Thread-Index: AcMTeFaVViDXQGsMQESl/NOXEeZRMgAVjeIw
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA19256

Jim,

> A bit of background - this WG item was intended to make the essential 
> measurements needed well defined enough that the way these "entities" were 
> measured across implementations (e.g. vendors) would be consistent.  

Yes, a critical need.

<...>

> I recommend we do the following clean up
> 
> - Somewhere provide a CRISP set of recommendations

Yes.

> - Remove all discussion which does not directly re-enforce a recommendation

Or move the discussion to an Annex if it is useful in supporting the recommendations.

>   - Maybe one option will be to remove the WG item completely

Disagree.  The need is important (some say 'critical'), I don't recall anyone saying the WG item in not important and should be dropped.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue May  6 09:40:17 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21085
	for <tewg-archive@lists.ietf.org>; Tue, 6 May 2003 09:40:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19D2gu-000HAG-00
	for te-wg-data@psg.com; Tue, 06 May 2003 13:41:08 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19D2gr-000HA1-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 13:41:05 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h46CwM3v001870
	for <te-wg@ops.ietf.org>; Tue, 6 May 2003 08:41:04 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A31430198BFFB; Tue, 6 May 2003 09:40:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: draft-ietf-tewg-measure-05.txt comments
Date: Tue, 6 May 2003 08:40:59 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A6795@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: draft-ietf-tewg-measure-05.txt comments
Thread-Index: AcMTzfbC6Wdz33AQSrSh8ltjtzBJ/gAAfywg
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <tnadeau@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA21085

Jim,

Your detailed comments and suggestions are very helpful, and should help improve the quality of the document.  

I have some comments below on Tom's and your comments.

Thanks,
Jerry

Jim> Flow measurement is a deep-hole, we should either defer to other
Jim> standardization efforts on this, or we need to be a lot more
Jim> concrete on what we need to know here.	

Tom> 	Defer to the IPFX WG that is tackling this problem right now.

Let's be more concrete in the TEM draft re flow measurement requirements.  I don't see a lot on TE measurement requirements in the IPFIX charter or requirements document http://ietf.org/internet-drafts/draft-ietf-ipfix-reqs-09.txt.  Let's be sure all the requirements get stated.

Jim> " Need for higher order statistics... "  push it to the offline hosts
Jim> "Need for packet-sampled..."  "Need for offline bulk file 
Jim> transfer..." The need needs to be better justified or removed.
 
Tom> 	I asked to have the offline stuff added. For the
Tom> collection of a traffic matrix, as you know, this 
Tom> entails the collection of a lot of data especially on
Tom> big core routers. It is preferable to use offline
Tom> bulk file transfer mechanisms such as NetFlow (being
Tom> standardized in IPFX now) or offline SNMP file transfers
Tom> of statistics snapshots.  This reduces the overhead of
Tom> the box having to service network management requests,
Tom> and also reduces the amount of network mgmt overhead
Tom> required to fetch the same amount of data if you 
Tom> collect your data as one big batch at some longer periodic
Tom> interval.

Quite unclear that moving massive amounts of data for offline processing is always 'preferable' to online statistics to meet all requirements.  Data collection/summarization in the 'big core routers', e.g., on a node-pair basis, is very desirable for traffic matrix derivation in some applications.



From owner-te-wg@ops.ietf.org  Tue May  6 11:03:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25285
	for <tewg-archive@lists.ietf.org>; Tue, 6 May 2003 11:03:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19D3ui-0002oR-00
	for te-wg-data@psg.com; Tue, 06 May 2003 14:59:28 +0000
Received: from mail.cleangreentradingco.net ([208.201.152.19] helo=Modus.surfnetusa.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19D3uf-0002mJ-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 14:59:25 +0000
Received: from seabreeze (unverified [4.46.12.10]) by Modus.surfnetusa.com
 (Vircom SMTPRS 2.0.244) with SMTP id <B0013416459@Modus.surfnetusa.com>;
 Tue, 6 May 2003 07:59:18 -0700
Message-ID: <003501c313e0$0b5b7110$6401a8c0@seabreeze>
From: "Merike Kaeo" <kaeo@merike.com>
To: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
        "Jim Boyle" <jboyle@pdnets.com>
Cc: "Tewg \(E-mail\)" <te-wg@ops.ietf.org>
References: <9473683187ADC049A855ED2DA739ABCA0A6794@KCCLUST06EVS1.ugd.att.com>
Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Tue, 6 May 2003 07:58:58 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Status: No, hits=-21.4 required=5.0
	tests=BAYES_01,ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,RCVD_IN_NJABL,
	      REFERENCES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

There is indeed a critical need for this sort of document and I strongly
agree that the recommendations need to be made more succinct.....there are
hints of what is recommended but specific recommendation details should be
explicitly stated without ambiguity in them.  Jim has made some excellent
comments to that effect.

- merike

----- Original Message -----
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>; "Tewg (E-mail)"
<te-wg@ops.ietf.org>
Sent: Tuesday, May 06, 2003 6:03 AM
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt


Jim,

> A bit of background - this WG item was intended to make the essential
> measurements needed well defined enough that the way these "entities" were
> measured across implementations (e.g. vendors) would be consistent.

Yes, a critical need.

<...>

> I recommend we do the following clean up
>
> - Somewhere provide a CRISP set of recommendations

Yes.

> - Remove all discussion which does not directly re-enforce a
recommendation

Or move the discussion to an Annex if it is useful in supporting the
recommendations.

>   - Maybe one option will be to remove the WG item completely

Disagree.  The need is important (some say 'critical'), I don't recall
anyone saying the WG item in not important and should be dropped.

Thanks,
Jerry







From owner-te-wg@ops.ietf.org  Tue May  6 11:29:16 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26267
	for <tewg-archive@lists.ietf.org>; Tue, 6 May 2003 11:29:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19D4Oj-0007sf-00
	for te-wg-data@psg.com; Tue, 06 May 2003 15:30:29 +0000
Received: from listserv2.radford.edu ([137.45.126.15])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19D4Of-0007s8-00
	for te-wg@ops.ietf.org; Tue, 06 May 2003 15:30:25 +0000
Received: from virus-mail.radford.edu (virus-mail.radford.edu [137.45.126.10])
	by listserv2.radford.edu (8.11.6/8.11.6) with SMTP id h46FULX10625
	for <te-wg@ops.ietf.org>; Tue, 6 May 2003 11:30:21 -0400 (EDT)
Received: FROM mail-in.radford.edu BY virus-mail.radford.edu ; Tue May 06 11:30:58 2003 -0700
Received: from oakcitysolutions.com (dhcp-192-86.radford.edu [137.45.192.86] (may be forged))
	by mail-in.radford.edu (Switch-3.0.4/Switch-3.0.0) with ESMTP id h46FUHBm018662;
	Tue, 6 May 2003 11:30:17 -0400
Message-ID: <3EB7D509.6030504@oakcitysolutions.com>
Date: Tue, 06 May 2003 11:30:17 -0400
From: "Dr. Richard W. Tibbs" <tewg@oakcitysolutions.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
CC: Jim Boyle <jboyle@pdnets.com>, tnadeau@cisco.com, te-wg@ops.ietf.org
Subject: Re: draft-ietf-tewg-measure-05.txt comments
References: <9473683187ADC049A855ED2DA739ABCA0A6795@KCCLUST06EVS1.ugd.att.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=-25.1 required=5.0
	tests=BAYES_10,EMAIL_ATTRIBUTION,REFERENCES,USER_AGENT_MOZILLA_UA
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jim, Jerry, etal:
Your comments are indeed helpful.  I have agreed with Wai to try a new 
version of our draft, based on the feedback we have had in the last 
couple of weeks.  It will take me  a while to do what is proposed -- 
which is significant "thinning" and re-organizing of the document --  in 
your comments, but I am willing.    As I do this, I may need to clarify 
some of your comments and I will mail the list to do so.  

Yours,
Dr. Richard W. Tibbs



Ash, Gerald R (Jerry), ALABS wrote:

>Jim,
>
>Your detailed comments and suggestions are very helpful, and should help improve the quality of the document.  
>
>I have some comments below on Tom's and your comments.
>
>Thanks,
>Jerry
>
>Jim> Flow measurement is a deep-hole, we should either defer to other
>Jim> standardization efforts on this, or we need to be a lot more
>Jim> concrete on what we need to know here.	
>
>Tom> 	Defer to the IPFX WG that is tackling this problem right now.
>
>Let's be more concrete in the TEM draft re flow measurement requirements.  I don't see a lot on TE measurement requirements in the IPFIX charter or requirements document http://ietf.org/internet-drafts/draft-ietf-ipfix-reqs-09.txt.  Let's be sure all the requirements get stated.
>
>Jim> " Need for higher order statistics... "  push it to the offline hosts
>Jim> "Need for packet-sampled..."  "Need for offline bulk file 
>Jim> transfer..." The need needs to be better justified or removed.
> 
>Tom> 	I asked to have the offline stuff added. For the
>Tom> collection of a traffic matrix, as you know, this 
>Tom> entails the collection of a lot of data especially on
>Tom> big core routers. It is preferable to use offline
>Tom> bulk file transfer mechanisms such as NetFlow (being
>Tom> standardized in IPFX now) or offline SNMP file transfers
>Tom> of statistics snapshots.  This reduces the overhead of
>Tom> the box having to service network management requests,
>Tom> and also reduces the amount of network mgmt overhead
>Tom> required to fetch the same amount of data if you 
>Tom> collect your data as one big batch at some longer periodic
>Tom> interval.
>
>Quite unclear that moving massive amounts of data for offline processing is always 'preferable' to online statistics to meet all requirements.  Data collection/summarization in the 'big core routers', e.g., on a node-pair basis, is very desirable for traffic matrix derivation in some applications.
>





From owner-te-wg@ops.ietf.org  Wed May  7 00:44:28 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20408
	for <tewg-archive@lists.ietf.org>; Wed, 7 May 2003 00:44:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19DGmX-000ETJ-00
	for te-wg-data@psg.com; Wed, 07 May 2003 04:43:53 +0000
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19DGm0-000EPV-00
	for te-wg@ops.ietf.org; Wed, 07 May 2003 04:43:20 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h474hIqo019407;
	Wed, 7 May 2003 04:43:18 GMT
Received: from zhangr2.info.net (lasi254.us.info.net [204.140.71.254])
	by delta.info.net  with ESMTP id EAA10168;
	Wed, 7 May 2003 04:43:16 GMT
Message-Id: <5.2.0.9.2.20030506214003.02d941c0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 06 May 2003 21:43:14 -0700
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
From: raymond zhang <zhangr@info.net>
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155017C1829@nl0006exch001u.nl
 .lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-26.0 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REPLY_WITH_QUOTES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Bert,

At 03:51 PM 5/5/2003 +0200, Wijnen, Bert (Bert) wrote:
>Inline
> > -----Original Message-----
> > From: raymond zhang [mailto:zhangr@info.net]
> > Sent: donderdag 1 mei 2003 16:45
> > To: Wijnen, Bert (Bert); Tewg (E-mail)
> > Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt
> >
> > Hi Bert,
> > Sorry for the delayed response...
> >
>No problem.
>
> > At 03:13 AM 4/25/2003 +0200, Wijnen, Bert (Bert) wrote:
> > >My summary:
> > >
> > >- a lot of text... but not very focused and to the point (or at least
> > >   I have trouble seeing the main points)
> > >- not a "framework", rather an exploration of TE measurement
> > >   related topics (more like  a summary-introduction)
> > >- I am not an operator, but I think if I were one, then
> > >   - if we were already doing TE measurement stuff (most likely) then
> > >     reading it seems a waste of time
> >
> > Ray - Well, we have policies and implementations at different
> > degrees for many of the areas touched upon by the draft but
> > not all... It is indeed helpful to look at this as framework for
> > any further work to refine our current processes.
> >
>Do you really mean "framework" or is it more
>a "pool of things to consider"?

You may have a point there.  Maybe more like a set of 
guidelines.  Important ones though in my view...

>.. snip ..
>
> > >   - Raymond Zhang is positive. He is from info.net ??? is that an 
> operator?
> >
> > I am form INFONET ( a global SP).
> >
>Thanks for informing me. And appology that I did not know.

No problem at all...

Cheers,
Raymond

>.. snip ..
>
>Bert





From owner-te-wg@ops.ietf.org  Thu May 15 17:08:57 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23151
	for <tewg-archive@lists.ietf.org>; Thu, 15 May 2003 17:08:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19GPx7-0003ud-00
	for te-wg-data@psg.com; Thu, 15 May 2003 21:07:49 +0000
Received: from howler.tri.sbc.com ([205.173.58.4])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19GPwc-0003ow-00
	for te-wg@ops.ietf.org; Thu, 15 May 2003 21:07:18 +0000
Received: from sbctri.tri.sbc.com (mayhem-web-dmz.tri.sbc.com [144.60.9.137])
	by howler.tri.sbc.com (8.12.9/8.12.9) with ESMTP id h4FL7H2j008829
	for <te-wg@ops.ietf.org>; Thu, 15 May 2003 16:07:17 -0500 (CDT)
Received: from tripacific.nttl.ad.tri.sbc.com (localhost [127.0.0.1])
	by sbctri.tri.sbc.com (8.11.6+Sun/8.9.3) with ESMTP id h4FL7GI20614
	for <te-wg@ops.ietf.org>; Thu, 15 May 2003 16:07:16 -0500 (CDT)
Received: by tripacific.nttl.ad.tri.sbc.com with Internet Mail Service (5.5.2656.59)
	id <HAJ5YJYT>; Thu, 15 May 2003 14:07:15 -0700
Message-ID: <CC16687B8C7AA1419B47057C36B1E98D7BC9AD@tripacific.nttl.ad.tri.sbc.com>
From: "Kim, Yonghwan" <ykim@tri.sbc.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: Support draft-zhang-mpls-interas-te-req-03.txt as a WG Doc.
Date: Thu, 15 May 2003 14:07:13 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi,

I support the following draft to be a WG document.
http://ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-03.txt

I also want to see (a) Inter-AS and (b) Inter-Area TE separately.

Thanks,

Yonghwan Kim




From owner-te-wg@ops.ietf.org  Fri May 16 10:27:59 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27264
	for <tewg-archive@lists.ietf.org>; Fri, 16 May 2003 10:27:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19GgAb-000Fbx-00
	for te-wg-data@psg.com; Fri, 16 May 2003 14:26:49 +0000
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19GgAY-000Fbk-00
	for te-wg@ops.ietf.org; Fri, 16 May 2003 14:26:46 +0000
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4GEOHRx029001;
	Fri, 16 May 2003 16:24:17 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 16 May 2003 16:26:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Fri, 16 May 2003 15:26:11 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5220@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQSqpBQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 16 May 2003 14:26:11.0605 (UTC) FILETIME=[196D1450:01C31BB7]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA27264

Hello Dimitry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 25 April 2003 22:28
>> To: 'Ash, Gerald R (Jerry), ALABS'; Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Gerald,
>> 
>> > 3. The 'maximum link bandwidth' parameter is a physical 
>> > constraint and serves to limit the assignable sum of link 
>> > bandwidth across class types.  In the recent discussion, this 
>> > constraint has sometimes been referred to as an 'implicit max 
>> > link BW constraint'.  However there is nothing 'implicit' 
>> > about this constraint/parameter, it is an existing link 
>> > parameter and a physical constraint on assignable link bandwidth.
>> > 4. Given comment #3, we don't need to use the 'max reservable 
>> > link bandwidth' parameter instead of the 'maximum link 
>> > bandwidth' parameter, as you have proposed.
>> 
>> The 'maximum link bandwidth' as defined is the actual link 
>> capacity and not
>> meant to be used as a reservation constraint. The 'max 
>> reservable link
>> bandwidth' was originally defined for this purpose. The 
>> amount of confusion
>> around these definitions puzzles me.
>>

After some investigation, here's my understanding:

1) At the time where "Max Link Bandwidth" was specified, (at least some
of) the folks involved were intending it as a constraint on the single
size of an LSP. Now, this didn't actually quite make it in the text of
the OSPF/ISIS specs, yet arguably the text doesn't either completely
exclude this interpretation. I suspect this may be (part of) the
explanation for the confusion around this. But that doesn't matter too
much...I guess.

2) Anyway, today, it seems that using "Max Link Bandwidth" to limit the
size of an individual LSP is not supported by all implementations, and
where supported, is not commonly used by SPs.
Based on this, I propose to follow Dimitry's suggestion and remove the
2nd check in the CAC formulas.
ie remove the following check:
"> >>        B <= Max Link Bandwidth "
(for memory, B is the size of the LSP being admitted)

Cheers

Francois

 
>> Dimitry
>> 
>> P.S. Excerpts from draft-katz-yeung-ospf-traffic-09.txt:
>> 
>> 
>>  2.5.6. Maximum Bandwidth
>> 
>>    The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
>>    can be used on this link in this direction (from the system
>>    originating the LSA to its neighbor), in IEEE floating 
>> point format.
>>    This is the true link capacity.  The units are bytes per second.
>> 
>>    The Maximum Bandwidth sub-TLV is TLV type 6, and is four octets in
>>    length.
>> 
>>  2.5.7. Maximum Reservable Bandwidth
>> 
>>    The Maximum Reservable Bandwidth sub-TLV specifies the maximum
>>    bandwidth that may be reserved on this link in this direction, in
>>    IEEE floating point format.  Note that this may be 
>> greater than the
>>    maximum bandwidth (in which case the link may be oversubscribed).
>>    This SHOULD be user-configurable; the default value should be the
>>    Maximum Bandwidth.  The units are bytes per second.
>> 
>>    The Maximum Reservable Bandwidth sub-TLV is TLV type 7, 
>> and is four
>>    octets in length.
>> 



From owner-te-wg@ops.ietf.org  Fri May 16 10:39:27 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27686
	for <tewg-archive@lists.ietf.org>; Fri, 16 May 2003 10:39:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19GgPE-000Hx9-00
	for te-wg-data@psg.com; Fri, 16 May 2003 14:41:56 +0000
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19GgP9-000Hs5-00
	for te-wg@ops.ietf.org; Fri, 16 May 2003 14:41:51 +0000
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4GEcmxY001514;
	Fri, 16 May 2003 16:38:49 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 16 May 2003 16:40:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Fri, 16 May 2003 15:40:31 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9565@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0g
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>, "Dimitry Haskin" <dhaskin@axiowave.com>
X-OriginalArrivalTime: 16 May 2003 14:40:32.0157 (UTC) FILETIME=[1A5AE4D0:01C31BB9]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA27686

Hello Jerry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 25 April 2003 22:28
>> To: 'Ash, Gerald R (Jerry), ALABS'; Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Gerald,
>> 
>> > 3. The 'maximum link bandwidth' parameter is a physical 
>> > constraint and serves to limit the assignable sum of link 
>> > bandwidth across class types.  In the recent discussion, this 
>> > constraint has sometimes been referred to as an 'implicit max 
>> > link BW constraint'.  However there is nothing 'implicit' 
>> > about this constraint/parameter, it is an existing link 
>> > parameter and a physical constraint on assignable link bandwidth.
>> > 4. Given comment #3, we don't need to use the 'max reservable 
>> > link bandwidth' parameter instead of the 'maximum link 
>> > bandwidth' parameter, as you have proposed.
>> 
>> The 'maximum link bandwidth' as defined is the actual link 
>> capacity and not
>> meant to be used as a reservation constraint. The 'max 
>> reservable link
>> bandwidth' was originally defined for this purpose. The 
>> amount of confusion
>> around these definitions puzzles me.
>> 

Do you agree with Dimitry's point that it is the "Max Reservable
Bandwidth" that should be used for constraining reservations (across
Class-Types) - not the "Max Link Bw"- ?  

If yes, would you agree that the following rules would apply for the
"new MAM" definition:
	o for each value of b in the range 0 <= b <= 7: 
		Reserved (CTb) <= BCb, 
	o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
		for all "c" in the range 0 <= c <= (MaxCT-1)

Thanks

Francois

>> Dimitry
>> 
>> P.S. Excerpts from draft-katz-yeung-ospf-traffic-09.txt:
>> 
>> 
>>  2.5.6. Maximum Bandwidth
>> 
>>    The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
>>    can be used on this link in this direction (from the system
>>    originating the LSA to its neighbor), in IEEE floating 
>> point format.
>>    This is the true link capacity.  The units are bytes per second.
>> 
>>    The Maximum Bandwidth sub-TLV is TLV type 6, and is four octets in
>>    length.
>> 
>>  2.5.7. Maximum Reservable Bandwidth
>> 
>>    The Maximum Reservable Bandwidth sub-TLV specifies the maximum
>>    bandwidth that may be reserved on this link in this direction, in
>>    IEEE floating point format.  Note that this may be 
>> greater than the
>>    maximum bandwidth (in which case the link may be oversubscribed).
>>    This SHOULD be user-configurable; the default value should be the
>>    Maximum Bandwidth.  The units are bytes per second.
>> 
>>    The Maximum Reservable Bandwidth sub-TLV is TLV type 7, 
>> and is four
>>    octets in length.
>> 



From owner-te-wg@ops.ietf.org  Mon May 19 16:48:22 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05353
	for <tewg-archive@lists.ietf.org>; Mon, 19 May 2003 16:48:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19HrWu-00075g-00
	for te-wg-data@psg.com; Mon, 19 May 2003 20:46:44 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19HrWr-00075E-00
	for te-wg@ops.ietf.org; Mon, 19 May 2003 20:46:42 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4JKYA1g001173
	for <te-wg@ops.ietf.org>; Mon, 19 May 2003 15:46:40 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020008D241; Mon, 19 May 2003 16:46:40 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: link capacity and reservable
Date: Mon, 19 May 2003 15:46:37 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137083@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAJM3joA=
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA05353

This is in response to the discussion of maximum reservable
bandwidth in
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
As the issue is not restricted solely to MAM, and has impact on
RDM and in fact all BC models, I am talking about it in a more
general context.

Current TE extension in IGP deals with aggregate traffic.
There is thus a simple average-overall relationship:
max link bandwidth = max reservable bandwidth/overbooking.
As a result, whether "max link bandwidth" is supported or
commonly used or not is immaterial.

In DS-TE, there is per-CT bandwidth contstraint and per-CT
overbooking.  Max reservable bandwidth should accordingly be
treated as a vector quantity.  Reflecting this view, the
following definition for MAM in <tewg-diff-te-reqts> is
adequate:
  for each value of b in the range 0 <= b <= 7:
    Reserved (CTb) <= BCb
(with some clarification in MAM spec regarding overbooking)

Also, the following additional condition for MAM definition as
proposed in the second message quoted above is both unneccsary
and incorrect:
  SUM (Reserved (CTc)) <= Max Reservable Bandwidth
    for all "c" in the range 0 <= c <= (MaxCT-1)

This is like when I have 15 dollars and 10 euros in my pocket,
then my max reserve is 25 (of what unit).

The "max link bandwidth," being a normalized quantity, is more
meaningful.  For admission control under MAM, in addition to
the observing the bandwidth constraints as specified in the
above deinition, something like the following may be used:
  SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
    for all "c" in the range 0 <= c <= (MaxCT-1)
(with some tweaks to account for priorities)

Thanks, Wai Sum



From owner-te-wg@ops.ietf.org  Mon May 19 17:26:11 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06168
	for <tewg-archive@lists.ietf.org>; Mon, 19 May 2003 17:26:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19HsA3-0008ci-00
	for te-wg-data@psg.com; Mon, 19 May 2003 21:27:11 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19HsA1-0008cW-00
	for te-wg@ops.ietf.org; Mon, 19 May 2003 21:27:09 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4JLQ3xs026454
	for <te-wg@ops.ietf.org>; Mon, 19 May 2003 16:27:08 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC7660200091773; Mon, 19 May 2003 17:27:08 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Mon, 19 May 2003 16:27:08 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67C5@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA06168

Hi Francois,

Welcome back, I notice you've been off the list for a while.  

Regarding:

> Do you agree with Dimitry's point that it is the "Max Reservable
> Bandwidth" that should be used for constraining reservations (across
> Class-Types) - not the "Max Link Bw"- ?

No, I think more clarifications are needed, see below.
 
> If yes, would you agree that the following rules would apply for the
> "new MAM" definition:
> 	o for each value of b in the range 0 <= b <= 7: 
> 		Reserved (CTb) <= BCb, 

This definition is OK, wherein the formula can be applied to either 'normalized' (by the overbooking factor) or 'unnormalized' bandwidth.

> 	o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> 		for all "c" in the range 0 <= c <= (MaxCT-1)

I agree with Wai Sum that this formula is incorrect for DS-TE, since the above formula only reflects the Max Reservable Bandwidth for the entire link, and does not reflect the per-CT overbooking factor.

Since there is a per-CT overbooking factor, this must be reflected in a summation of reserved bandwidth.  As such, use of the following formula would appear to more correct:

  SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
    for all "c" in the range 0 <= c <= (MaxCT-1)

Thanks,
Jerry




From owner-te-wg@ops.ietf.org  Tue May 20 05:58:10 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04303
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 05:58:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I3qs-000Hxc-00
	for te-wg-data@psg.com; Tue, 20 May 2003 09:56:10 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I3qp-000HxO-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 09:56:07 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 20 May 2003 11:55:31 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4K9s7TI027038;
	Tue, 20 May 2003 11:54:10 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:56:05 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 10:56:04 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522C@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0A==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 20 May 2003 09:56:05.0282 (UTC) FILETIME=[075B7020:01C31EB6]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA04303

Jerry, Waisum and all,

>> > If yes, would you agree that the following rules would 
>> apply for the
>> > "new MAM" definition:
>> > 	o for each value of b in the range 0 <= b <= 7: 
>> > 		Reserved (CTb) <= BCb, 
>> 
>> This definition is OK, wherein the formula can be applied to 
>> either 'normalized' (by the overbooking factor) or 
>> 'unnormalized' bandwidth.
>> 

Yes, absolutely, in case the per-CT Local Overbooking Multipliers (LOM)
are used, then the formulas need to be applied to the normalised
bandwidth (I was only trying to get some agreement first on the
definition in the simpler case where per-CT overbooking is not used,
sorry I didn't make that explicit).

Anyway, this part of the formula would not change from current version
of MAM draft:

1)when per-CT LOMs are not used:
"o	for each value of b in the range 0 <= b <= (MaxCT - 1):
            		Reserved (CTb) <= BCb,"

1)when per-CT LOMs are  used:
"-	for each value of b in the range 0 <= b <= (MaxCT - 1):
            		Normalised(CTb) <= BCb,"

So I think we all agree with that part of the formula, right?

>> > 	o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > 		for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> I agree with Wai Sum that this formula is incorrect for 
>> DS-TE, since the above formula only reflects the Max 
>> Reservable Bandwidth for the entire link, and does not 
>> reflect the per-CT overbooking factor.
>> 
>> Since there is a per-CT overbooking factor, this must be 
>> reflected in a summation of reserved bandwidth.  As such, 
>> use of the following formula would appear to more correct:
>> 
>>   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>>     for all "c" in the range 0 <= c <= (MaxCT-1)

Again, here I agree that the formula needs to be applied to Normalised
bandwidth when per-CT LOMs are used. 

Also, I think we are in agreement that we should include an explicit
condition in the MAM definition which constraints "SUM (Normalised
(CTc))" (ie to make explicit the formally "implicit" constraint). Am I
right that we agree on that?

So, the only divergence seems to be that when doing the check on SUM
(Normalised (CTc)):
	- you propose to use "Max Link Bandwidth"
	- I propose to use "Max Reservable Bandwidth"

Again this seems to be coming from different interpretations of these
two IGP parameters. 
Like Dimitry pointed out, to me the parameter which is meant to be used
for reservations is "Max Reservable Bandwidth". This what I read in the
IGP extension text. Also, as mentioned earlier, the TE implementations
that I am familiar with are currently all using "Max Reservable
Bandwidth" for aggregate admission control decisions and not "Max Link
Bandwdith".

Cheers

Francois


>> 
>> Thanks,
>> Jerry
>> 
>> 



From owner-te-wg@ops.ietf.org  Tue May 20 08:45:07 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10562
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 08:45:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I6Up-0001e9-00
	for te-wg-data@psg.com; Tue, 20 May 2003 12:45:35 +0000
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by psg.com with smtp (Exim 3.36 #1)
	id 19I6Um-0001bY-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 12:45:32 +0000
Received: from parsmtp1.rd.francetelecom.com ([10.193.117.128]) by p-mail1 with InterScan Messaging Security Suite; Tue, 20 May 2003 14:46:02 +0200
Received: from lanmhs30.rd.francetelecom.fr ([10.193.21.61]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 14:45:30 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
x-mimeole: Produced By Microsoft Exchange V6.0.6375.0
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 14:45:29 +0200
Message-ID: <1FB136FD10CE33409C882630E299F5BE1EDC81@lanmhs30.rd.francetelecom.fr>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0AAGEjvQ
From: "LE ROUX Jean-Louis FTRD/DAC/LAN" <jeanlouis.leroux@rd.francetelecom.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 20 May 2003 12:45:30.0054 (UTC) FILETIME=[B2088E60:01C31ECD]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA10562

Francois, Waisum and all

IMHO "max reservable bandwidth" should be used rather than
max-link-bandwidth to control the aggregate bandwidth in MAM.
Indeed max-link-bandwidth should be rather used to limit bandwidth of
one LSP.
Overbooking allows to take into account the fact that statiscally, not
all LSPs are simultaneously loaded, but we should also limit the
bandwidth of one LSP

So I agree with Francois regarding the use of max-reservalbe-bandwidth,
and I suggest to add a third rule that is 

An LSP of bandwidth B can be accepted if 
	B < max-link-bandwidth 

Note that this rule also applies to RDM

Regards 

JL

-----Message d'origine-----
De : Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Envoye : mardi 20 mai 2003 11:56
A : Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS; Dimitry
Haskin
Cc : te-wg@ops.ietf.org
Objet : RE: Reflecting new-MAM/SAM definition in diff-te drafts


Jerry, Waisum and all,

>> > If yes, would you agree that the following rules would 
>> apply for the
>> > "new MAM" definition:
>> > 	o for each value of b in the range 0 <= b <= 7: 
>> > 		Reserved (CTb) <= BCb, 
>> 
>> This definition is OK, wherein the formula can be applied to 
>> either 'normalized' (by the overbooking factor) or 
>> 'unnormalized' bandwidth.
>> 

Yes, absolutely, in case the per-CT Local Overbooking Multipliers (LOM)
are used, then the formulas need to be applied to the normalised
bandwidth (I was only trying to get some agreement first on the
definition in the simpler case where per-CT overbooking is not used,
sorry I didn't make that explicit).

Anyway, this part of the formula would not change from current version
of MAM draft:

1)when per-CT LOMs are not used:
"o	for each value of b in the range 0 <= b <= (MaxCT - 1):
            		Reserved (CTb) <= BCb,"

1)when per-CT LOMs are  used:
"-	for each value of b in the range 0 <= b <= (MaxCT - 1):
            		Normalised(CTb) <= BCb,"

So I think we all agree with that part of the formula, right?

>> > 	o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > 		for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> I agree with Wai Sum that this formula is incorrect for 
>> DS-TE, since the above formula only reflects the Max 
>> Reservable Bandwidth for the entire link, and does not 
>> reflect the per-CT overbooking factor.
>> 
>> Since there is a per-CT overbooking factor, this must be 
>> reflected in a summation of reserved bandwidth.  As such, 
>> use of the following formula would appear to more correct:
>> 
>>   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>>     for all "c" in the range 0 <= c <= (MaxCT-1)

Again, here I agree that the formula needs to be applied to Normalised
bandwidth when per-CT LOMs are used. 

Also, I think we are in agreement that we should include an explicit
condition in the MAM definition which constraints "SUM (Normalised
(CTc))" (ie to make explicit the formally "implicit" constraint). Am I
right that we agree on that?

So, the only divergence seems to be that when doing the check on SUM
(Normalised (CTc)):
	- you propose to use "Max Link Bandwidth"
	- I propose to use "Max Reservable Bandwidth"

Again this seems to be coming from different interpretations of these
two IGP parameters. 
Like Dimitry pointed out, to me the parameter which is meant to be used
for reservations is "Max Reservable Bandwidth". This what I read in the
IGP extension text. Also, as mentioned earlier, the TE implementations
that I am familiar with are currently all using "Max Reservable
Bandwidth" for aggregate admission control decisions and not "Max Link
Bandwdith".

Cheers

Francois


>> 
>> Thanks,
>> Jerry
>> 
>> 




From owner-te-wg@ops.ietf.org  Tue May 20 10:18:41 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15034
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 10:18:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I7xq-0009ED-00
	for te-wg-data@psg.com; Tue, 20 May 2003 14:19:38 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I7xn-0009CR-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 14:19:35 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KDw01d013298
	for <te-wg@ops.ietf.org>; Tue, 20 May 2003 09:19:29 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC76602000D7B5F; Tue, 20 May 2003 10:19:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 09:19:28 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67C8@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0AAJAOIA
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA15034

Francois, All,

> 1)when per-CT LOMs are not used:
> "o	for each value of b in the range 0 <= b <= (MaxCT - 1):
>             		Reserved (CTb) <= BCb,"
> 
> 1)when per-CT LOMs are  used:
> "-	for each value of b in the range 0 <= b <= (MaxCT - 1):
>             		Normalised(CTb) <= BCb,"
> 
> So I think we all agree with that part of the formula, right?

Yes, I think we agree on this.

> Again, here I agree that the formula needs to be applied to Normalised
> bandwidth when per-CT LOMs are used.

Right.  So we need to specify what that formula is.  We have suggested this formula:

    SUM (Reserved(CTc)/LOM(CTc)) <= Max Link Bandwidth
     for all "c" in the range 0 <= c <= (MaxCT-1)

or, equivalently:

   SUM (Normalized(CTc)) <= Max Link Bandwidth
     for all "c" in the range 0 <= c <= (MaxCT-1)

> Also, I think we are in agreement that we should include an explicit
> condition in the MAM definition which constraints "SUM (Normalised
> (CTc))" (ie to make explicit the formally "implicit" constraint). Am I
> right that we agree on that?

Yes, we need a formula to make explicit the 'implicit' constraint (and for all the BC models, not just MAM).

> So, the only divergence seems to be that when doing the check on SUM
> (Normalised (CTc)):
> 	- you propose to use "Max Link Bandwidth"
> 	- I propose to use "Max Reservable Bandwidth"
> 
> Again this seems to be coming from different interpretations of these
> two IGP parameters. 
> Like Dimitry pointed out, to me the parameter which is meant 
> to be used for reservations is "Max Reservable Bandwidth". This what 
> I read in the IGP extension text. Also, as mentioned earlier, the TE 
> implementations that I am familiar with are currently all using "Max 
> Reservable Bandwidth" for aggregate admission control decisions and 
> not "Max Link Bandwidth".

Use of "Max Reservable Bandwidth" appears to be OK without per-CT Local Overbooking Multipliers (LOMs).  That is, when there is only *one* LOM for the entire link, then the formula you give appears to be correct:

    o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
        for all "c" in the range 0 <= c <= (MaxCT-1)

However, this formula is incorrect for DS-TE when per-CT LOM's are used, since the above formula only reflects the Max Reservable Bandwidth for the entire link, and does not reflect the per-CT local overbooking factors.  So what formula do you suggest when per-CT LOM's are used?

The formula we suggested appears to be correct when per-CT LOM's are used:

    SUM (Reserved(CTc)/LOM(CTc)) <= Max Link Bandwidth
     for all "c" in the range 0 <= c <= (MaxCT-1)

or, equivalently:

   SUM (Normalized(CTc)) <= Max Link Bandwidth
     for all "c" in the range 0 <= c <= (MaxCT-1)

Please suggest what formula you propose for when per-CT LOM's are used, and which also reflects Max Reservable Bandwidth instead of Max Link Bandwidth.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue May 20 10:43:23 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16129
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 10:43:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I8Mx-000KiU-00
	for te-wg-data@psg.com; Tue, 20 May 2003 14:45:35 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I8Mt-000Kf6-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 14:45:31 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F63B@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Lai, Wai S (Waisum), ALABS'" <wlai@att.com>, te-wg@ops.ietf.org
Cc: Dimitry Haskin <dhaskin@axiowave.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: link capacity and reservable
Date: Tue, 20 May 2003 10:44:46 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Waisum, Jerry,

IMO, both yours and Francois' formulas for the aggregate reservation
constrain would achieve identical results. Note that max reservable b/w
constraint is simply applied to the sum of reservations at each CT which
already account for individual overbooking factors at each CT. However with
the formula that you are proposing we would completely shut the door for
other uses of the max link b/w TLV, for instance as a constraint on the max
LSP b/w. Since we have already a parameter that was explicitly defined as
the aggregate reservation constrain, there is no need to close door for a
different use of the max link b/w parameter at this point.

Regards,
  Dimitry  

> -----Original Message-----
> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
> Sent: Monday, May 19, 2003 4:47 PM
> To: te-wg@ops.ietf.org
> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, Gerald R
> (Jerry), ALABS
> Subject: link capacity and reservable
> 
> 
> This is in response to the discussion of maximum reservable
> bandwidth in
> http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
> http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
> As the issue is not restricted solely to MAM, and has impact on
> RDM and in fact all BC models, I am talking about it in a more
> general context.
> 
> Current TE extension in IGP deals with aggregate traffic.
> There is thus a simple average-overall relationship:
> max link bandwidth = max reservable bandwidth/overbooking.
> As a result, whether "max link bandwidth" is supported or
> commonly used or not is immaterial.
> 
> In DS-TE, there is per-CT bandwidth contstraint and per-CT
> overbooking.  Max reservable bandwidth should accordingly be
> treated as a vector quantity.  Reflecting this view, the
> following definition for MAM in <tewg-diff-te-reqts> is
> adequate:
>   for each value of b in the range 0 <= b <= 7:
>     Reserved (CTb) <= BCb
> (with some clarification in MAM spec regarding overbooking)
> 
> Also, the following additional condition for MAM definition as
> proposed in the second message quoted above is both unneccsary
> and incorrect:
>   SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>     for all "c" in the range 0 <= c <= (MaxCT-1)
> 
> This is like when I have 15 dollars and 10 euros in my pocket,
> then my max reserve is 25 (of what unit).
> 
> The "max link bandwidth," being a normalized quantity, is more
> meaningful.  For admission control under MAM, in addition to
> the observing the bandwidth constraints as specified in the
> above deinition, something like the following may be used:
>   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>     for all "c" in the range 0 <= c <= (MaxCT-1)
> (with some tweaks to account for priorities)
> 
> Thanks, Wai Sum
> 



From owner-te-wg@ops.ietf.org  Tue May 20 10:55:55 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16547
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 10:55:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I8ZE-0001wX-00
	for te-wg-data@psg.com; Tue, 20 May 2003 14:58:16 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I8Yx-0001up-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 14:57:59 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F63C@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Ash, Gerald R (Jerry), ALABS'" <gash@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: te-wg@ops.ietf.org, "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        Dimitry Haskin <dhaskin@axiowave.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 10:57:50 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-10.4 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> 
> Use of "Max Reservable Bandwidth" appears to be OK without 
> per-CT Local Overbooking Multipliers (LOMs).  That is, when 
> there is only *one* LOM for the entire link, then the formula 
> you give appears to be correct:
> 
>     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>         for all "c" in the range 0 <= c <= (MaxCT-1)
> 
> However, this formula is incorrect for DS-TE when per-CT 
> LOM's are used, since the above formula only reflects the Max 
> Reservable Bandwidth for the entire link, and does not 
> reflect the per-CT local overbooking factors.  So what 
> formula do you suggest when per-CT LOM's are used?
>

Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
overbooking multiplier at CTc?  I don't see how this formula precludes
per-CT LOM's to be used. Please explain.

Regards,
  Dimitry 



From owner-te-wg@ops.ietf.org  Tue May 20 11:22:47 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17461
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:22:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I8yT-0006Ul-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:24:21 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I8yR-0006UU-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:24:19 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:20:44 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:25:06 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 48AB99F612; Tue, 20 May 2003 11:10:48 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 06B199F605; Tue, 20 May 2003 11:10:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I8ZE-0001wX-00 for te-wg-data@psg.com; Tue, 20 May 2003 14:58:16 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com) by psg.com with esmtp (Exim 3.36 #1) id 19I8Yx-0001up-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 14:57:59 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F63C@r2d2.axiowave.com>
Date: Tue, 20 May 2003 10:57:50 -0400
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 15:25:06.0187 (UTC) FILETIME=[FDDA7DB0:01C31EE3]
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Dimitry Haskin" <dhaskin@axiowave.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-6.1 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,RCVD_IN_DSBL
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> 
> Use of "Max Reservable Bandwidth" appears to be OK without 
> per-CT Local Overbooking Multipliers (LOMs).  That is, when 
> there is only *one* LOM for the entire link, then the formula 
> you give appears to be correct:
> 
>     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>         for all "c" in the range 0 <= c <= (MaxCT-1)
> 
> However, this formula is incorrect for DS-TE when per-CT 
> LOM's are used, since the above formula only reflects the Max 
> Reservable Bandwidth for the entire link, and does not 
> reflect the per-CT local overbooking factors.  So what 
> formula do you suggest when per-CT LOM's are used?
>

Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
overbooking multiplier at CTc?  I don't see how this formula precludes
per-CT LOM's to be used. Please explain.

Regards,
  Dimitry 





From owner-te-wg@ops.ietf.org  Tue May 20 11:32:49 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17889
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:32:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I996-0008Pz-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:35:20 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I993-0008PL-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:35:18 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KF911n000590
	for <te-wg@ops.ietf.org>; Tue, 20 May 2003 10:35:17 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC76602000E210F; Tue, 20 May 2003 11:35:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 10:35:16 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE91E@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KA
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-Spam-Status: No, hits=-10.4 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA17889

Dimitry, Francois,

> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> >         for all "c" in the range 0 <= c <= (MaxCT-1)
> > 
> > However, this formula is incorrect for DS-TE when per-CT 
> > LOM's are used, since the above formula only reflects the Max 
> > Reservable Bandwidth for the entire link, and does not 
> > reflect the per-CT local overbooking factors.  So what 
> > formula do you suggest when per-CT LOM's are used?

> Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
> overbooking multiplier at CTc?  I don't see how this formula precludes
> per-CT LOM's to be used. Please explain.

Are you then proposing these formulas:

1. When per-CT LOMs are not used:

     o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

2. When per-CT LOMs are used:

     o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

Is that correct?  Please confirm, and/or give the formulas you propose.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue May 20 11:36:01 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18095
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:36:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9Cb-0008pQ-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:38:57 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9CZ-0008p4-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:38:55 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:38:18 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFakMu001005;
	Tue, 20 May 2003 17:36:57 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 17:38:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 16:38:51 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522D@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>, "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-OriginalArrivalTime: 20 May 2003 15:38:51.0883 (UTC) FILETIME=[EA01B3B0:01C31EE5]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA18095

Hello Dimitry, Jerry, Waisum,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:58
>> To: 'Ash, Gerald R (Jerry), ALABS'; Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org; Lai, Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> > 
>> > Use of "Max Reservable Bandwidth" appears to be OK without 
>> > per-CT Local Overbooking Multipliers (LOMs).  That is, when 
>> > there is only *one* LOM for the entire link, then the formula 
>> > you give appears to be correct:
>> > 
>> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > However, this formula is incorrect for DS-TE when per-CT 
>> > LOM's are used, since the above formula only reflects the Max 
>> > Reservable Bandwidth for the entire link, and does not 
>> > reflect the per-CT local overbooking factors.  So what 
>> > formula do you suggest when per-CT LOM's are used?
>> >
>> 
>> Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> overbooking multiplier at CTc?  I don't see how this formula 
>> precludes
>> per-CT LOM's to be used. Please explain.
>>

I've been using "Reserved" and "Normalised" as per their definitions in
the proto draft, the RDM draft and the MAM draft.

Quoting from these drafts:

==================================
- "Reserved (CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
established LSPs which belong to CTc. 
- Normalised(CTc) : let us define "Normalised(CTc)" as
"Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
Multiplier for CTc defined in [DSTE-PROTO].
=====================================

What that means is that "Reserved(CTc)" does factor in the overbooking
method which is refered to as "LSP/link size overbooking" method and is
the overbooking method commonly used in TE networks. However, it does
NOT factor in the optional "Local Overbooking Multiplier" method.

"Normalised (CTc)"  factors-in both the "LSP/link size overbooking" and
the optional "Local Overbooking Multiplier" method.

Definitions of the "LSP/link size overbooking" method and "Local
overbooking Multiplier" method can be found in section "4.1.2. per-CT
Local Overbooking Multipliers (LOMs) of the dste-proto draft.

Based on this, my proposal is to include the following condition to
reflect the aggregate constraint when both overbooking methods are used
(ie "LSP/link size overbooking" method and "Local overbooking
Multiplier" method):

    o SUM (Normalised (CTc)) <= Max Reservable Bandwidth, 
        for all "c" in the range 0 <= c <= (MaxCT-1)

where "Normalised (CTc) is equal to "Reserved(CTc)/LOM(c)" as currently
defined in RDM and MAM drafts.

Thanks

Francois

>> Regards,
>>   Dimitry 
>> 



From owner-te-wg@ops.ietf.org  Tue May 20 11:38:38 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18207
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:38:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9F0-0009Oj-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:41:26 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9Ex-0009KS-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:41:23 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:40:46 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFdPAc001592;
	Tue, 20 May 2003 17:39:26 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 17:41:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 16:41:21 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9584@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KAAABaVhA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
Cc: <te-wg@ops.ietf.org>, "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-OriginalArrivalTime: 20 May 2003 15:41:22.0056 (UTC) FILETIME=[43844880:01C31EE6]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA18207

Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 17:35
>> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Dimitry, Francois,
>> 
>> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > > 
>> > > However, this formula is incorrect for DS-TE when per-CT 
>> > > LOM's are used, since the above formula only reflects the Max 
>> > > Reservable Bandwidth for the entire link, and does not 
>> > > reflect the per-CT local overbooking factors.  So what 
>> > > formula do you suggest when per-CT LOM's are used?
>> 
>> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> > overbooking multiplier at CTc?  I don't see how this 
>> formula precludes
>> > per-CT LOM's to be used. Please explain.
>> 
>> Are you then proposing these formulas:
>> 
>> 1. When per-CT LOMs are not used:
>> 
>>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> 2. When per-CT LOMs are used:
>> 
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that correct?  Please confirm, and/or give the formulas 
>> you propose.

Yes, this is exactly what I propose.
I think this is similar to what you were proposing, only using "Max Res
Bw" instead of "Max Link Bw". 

Sorry I didn't make that very clear before.

Cheers

FRancois

>> 
>> Thanks,
>> Jerry
>> 



From owner-te-wg@ops.ietf.org  Tue May 20 11:44:12 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18513
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:44:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9KA-000Adl-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:46:46 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9K7-000AdM-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:46:43 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:43:09 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:47:01 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 5E9689F605; Tue, 20 May 2003 11:33:12 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 8FA049F605; Tue, 20 May 2003 11:33:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I8yT-0006Ul-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:24:21 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I8yR-0006UU-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:24:19 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:20:44 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:25:06 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 48AB99F612; Tue, 20 May 2003 11:10:48 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 06B199F605; Tue, 20 May 2003 11:10:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I8ZE-0001wX-00 for te-wg-data@psg.com; Tue, 20 May 2003 14:58:16 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com) by psg.com with esmtp (Exim 3.36 #1) id 19I8Yx-0001up-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 14:57:59 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F63C@r2d2.axiowave.com>
Date: Tue, 20 May 2003 10:57:50 -0400
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 15:25:06.0187 (UTC) FILETIME=[FDDA7DB0:01C31EE3]
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Dimitry Haskin" <dhaskin@axiowave.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-6.1 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,RCVD_IN_DSBL
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> 
> Use of "Max Reservable Bandwidth" appears to be OK without 
> per-CT Local Overbooking Multipliers (LOMs).  That is, when 
> there is only *one* LOM for the entire link, then the formula 
> you give appears to be correct:
> 
>     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>         for all "c" in the range 0 <= c <= (MaxCT-1)
> 
> However, this formula is incorrect for DS-TE when per-CT 
> LOM's are used, since the above formula only reflects the Max 
> Reservable Bandwidth for the entire link, and does not 
> reflect the per-CT local overbooking factors.  So what 
> formula do you suggest when per-CT LOM's are used?
>

Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
overbooking multiplier at CTc?  I don't see how this formula precludes
per-CT LOM's to be used. Please explain.

Regards,
  Dimitry 







From owner-te-wg@ops.ietf.org  Tue May 20 11:44:41 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18559
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:44:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9KI-000Aju-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:46:54 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9K8-000AdM-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:46:44 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:43:09 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:47:30 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 6965E9F614; Tue, 20 May 2003 11:33:12 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 8FA049F605; Tue, 20 May 2003 11:33:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I8yT-0006Ul-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:24:21 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I8yR-0006UU-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:24:19 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:20:44 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:25:06 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 48AB99F612; Tue, 20 May 2003 11:10:48 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 06B199F605; Tue, 20 May 2003 11:10:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I8ZE-0001wX-00 for te-wg-data@psg.com; Tue, 20 May 2003 14:58:16 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com) by psg.com with esmtp (Exim 3.36 #1) id 19I8Yx-0001up-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 14:57:59 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F63C@r2d2.axiowave.com>
Date: Tue, 20 May 2003 10:57:50 -0400
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 15:25:06.0187 (UTC) FILETIME=[FDDA7DB0:01C31EE3]
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Dimitry Haskin" <dhaskin@axiowave.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-6.1 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,RCVD_IN_DSBL
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> 
> Use of "Max Reservable Bandwidth" appears to be OK without 
> per-CT Local Overbooking Multipliers (LOMs).  That is, when 
> there is only *one* LOM for the entire link, then the formula 
> you give appears to be correct:
> 
>     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>         for all "c" in the range 0 <= c <= (MaxCT-1)
> 
> However, this formula is incorrect for DS-TE when per-CT 
> LOM's are used, since the above formula only reflects the Max 
> Reservable Bandwidth for the entire link, and does not 
> reflect the per-CT local overbooking factors.  So what 
> formula do you suggest when per-CT LOM's are used?
>

Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
overbooking multiplier at CTc?  I don't see how this formula precludes
per-CT LOM's to be used. Please explain.

Regards,
  Dimitry 







From owner-te-wg@ops.ietf.org  Tue May 20 11:48:57 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18683
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:48:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9P3-000BiW-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:51:49 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9Oy-000BgG-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:51:44 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:51:08 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFnhWs003626;
	Tue, 20 May 2003 17:49:43 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 17:51:38 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Tue, 20 May 2003 16:51:38 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9586@xbe-lon-313.cisco.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+Q
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-OriginalArrivalTime: 20 May 2003 15:51:38.0607 (UTC) FILETIME=[B3027FF0:01C31EE7]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA18683

Dimitry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:45
>> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, 
>> Gerald R (Jerry), ALABS
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Waisum, Jerry,
>> 
>> IMO, both yours and Francois' formulas for the aggregate reservation
>> constrain would achieve identical results. 

I guess you're right that at the end of the day it would be pretty much
the same thing functionnally.

>>Note that max 
>> reservable b/w
>> constraint is simply applied to the sum of reservations at 
>> each CT which
>> already account for individual overbooking factors at each 
>> CT. However with
>> the formula that you are proposing we would completely shut 
>> the door for
>> other uses of the max link b/w TLV, for instance as a 
>> constraint on the max
>> LSP b/w. Since we have already a parameter that was 
>> explicitly defined as
>> the aggregate reservation constrain, there is no need to 
>> close door for a
>> different use of the max link b/w parameter at this point.
>> 

Agreed.

Thanks

FRancois

>> Regards,
>>   Dimitry  
>> 
>> > -----Original Message-----
>> > From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
>> > Sent: Monday, May 19, 2003 4:47 PM
>> > To: te-wg@ops.ietf.org
>> > Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, Gerald R
>> > (Jerry), ALABS
>> > Subject: link capacity and reservable
>> > 
>> > 
>> > This is in response to the discussion of maximum reservable
>> > bandwidth in
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
>> > As the issue is not restricted solely to MAM, and has impact on
>> > RDM and in fact all BC models, I am talking about it in a more
>> > general context.
>> > 
>> > Current TE extension in IGP deals with aggregate traffic.
>> > There is thus a simple average-overall relationship:
>> > max link bandwidth = max reservable bandwidth/overbooking.
>> > As a result, whether "max link bandwidth" is supported or
>> > commonly used or not is immaterial.
>> > 
>> > In DS-TE, there is per-CT bandwidth contstraint and per-CT
>> > overbooking.  Max reservable bandwidth should accordingly be
>> > treated as a vector quantity.  Reflecting this view, the
>> > following definition for MAM in <tewg-diff-te-reqts> is
>> > adequate:
>> >   for each value of b in the range 0 <= b <= 7:
>> >     Reserved (CTb) <= BCb
>> > (with some clarification in MAM spec regarding overbooking)
>> > 
>> > Also, the following additional condition for MAM definition as
>> > proposed in the second message quoted above is both unneccsary
>> > and incorrect:
>> >   SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > This is like when I have 15 dollars and 10 euros in my pocket,
>> > then my max reserve is 25 (of what unit).
>> > 
>> > The "max link bandwidth," being a normalized quantity, is more
>> > meaningful.  For admission control under MAM, in addition to
>> > the observing the bandwidth constraints as specified in the
>> > above deinition, something like the following may be used:
>> >   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> > (with some tweaks to account for priorities)
>> > 
>> > Thanks, Wai Sum
>> > 
>> 



From owner-te-wg@ops.ietf.org  Tue May 20 11:49:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18732
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:49:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9Pa-000Bmj-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:52:22 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9PX-000BmV-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:52:19 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:48:45 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:52:37 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 713B39F103; Tue, 20 May 2003 11:40:25 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id D3D969F103; Tue, 20 May 2003 11:40:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Cb-0008pQ-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:38:57 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19I9CZ-0008p4-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:38:55 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:38:18 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFakMu001005; Tue, 20 May 2003 17:36:57 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 17:38:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 16:38:51 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522D@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQ
X-OriginalArrivalTime: 20 May 2003 15:38:51.0883 (UTC) FILETIME=[EA01B3B0:01C31EE5]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA18732

Hello Dimitry, Jerry, Waisum,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:58
>> To: 'Ash, Gerald R (Jerry), ALABS'; Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org; Lai, Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> > 
>> > Use of "Max Reservable Bandwidth" appears to be OK without 
>> > per-CT Local Overbooking Multipliers (LOMs).  That is, when 
>> > there is only *one* LOM for the entire link, then the formula 
>> > you give appears to be correct:
>> > 
>> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > However, this formula is incorrect for DS-TE when per-CT 
>> > LOM's are used, since the above formula only reflects the Max 
>> > Reservable Bandwidth for the entire link, and does not 
>> > reflect the per-CT local overbooking factors.  So what 
>> > formula do you suggest when per-CT LOM's are used?
>> >
>> 
>> Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> overbooking multiplier at CTc?  I don't see how this formula 
>> precludes
>> per-CT LOM's to be used. Please explain.
>>

I've been using "Reserved" and "Normalised" as per their definitions in
the proto draft, the RDM draft and the MAM draft.

Quoting from these drafts:

==================================
- "Reserved (CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
established LSPs which belong to CTc. 
- Normalised(CTc) : let us define "Normalised(CTc)" as
"Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
Multiplier for CTc defined in [DSTE-PROTO].
=====================================

What that means is that "Reserved(CTc)" does factor in the overbooking
method which is refered to as "LSP/link size overbooking" method and is
the overbooking method commonly used in TE networks. However, it does
NOT factor in the optional "Local Overbooking Multiplier" method.

"Normalised (CTc)"  factors-in both the "LSP/link size overbooking" and
the optional "Local Overbooking Multiplier" method.

Definitions of the "LSP/link size overbooking" method and "Local
overbooking Multiplier" method can be found in section "4.1.2. per-CT
Local Overbooking Multipliers (LOMs) of the dste-proto draft.

Based on this, my proposal is to include the following condition to
reflect the aggregate constraint when both overbooking methods are used
(ie "LSP/link size overbooking" method and "Local overbooking
Multiplier" method):

    o SUM (Normalised (CTc)) <= Max Reservable Bandwidth, 
        for all "c" in the range 0 <= c <= (MaxCT-1)

where "Normalised (CTc) is equal to "Reserved(CTc)/LOM(c)" as currently
defined in RDM and MAM drafts.

Thanks

Francois

>> Regards,
>>   Dimitry 
>> 





From owner-te-wg@ops.ietf.org  Tue May 20 11:49:27 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18735
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:49:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9Pg-000BnM-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:52:28 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9Pe-000Bn5-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:52:26 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:48:51 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:53:13 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C05039F614; Tue, 20 May 2003 11:38:54 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 287FA9F614; Tue, 20 May 2003 11:38:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I996-0008Pz-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:35:20 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19I993-0008PL-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:35:18 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KF911n000590 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 10:35:17 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC76602000E210F; Tue, 20 May 2003 11:35:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 10:35:16 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE91E@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KA
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 15:53:13.0046 (UTC) FILETIME=[EB4CBF60:01C31EE7]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-10.4 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA18735

Dimitry, Francois,

> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> >         for all "c" in the range 0 <= c <= (MaxCT-1)
> > 
> > However, this formula is incorrect for DS-TE when per-CT 
> > LOM's are used, since the above formula only reflects the Max 
> > Reservable Bandwidth for the entire link, and does not 
> > reflect the per-CT local overbooking factors.  So what 
> > formula do you suggest when per-CT LOM's are used?

> Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
> overbooking multiplier at CTc?  I don't see how this formula precludes
> per-CT LOM's to be used. Please explain.

Are you then proposing these formulas:

1. When per-CT LOMs are not used:

     o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

2. When per-CT LOMs are used:

     o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

Is that correct?  Please confirm, and/or give the formulas you propose.

Thanks,
Jerry





From owner-te-wg@ops.ietf.org  Tue May 20 11:52:22 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18896
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 11:52:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9SO-000C9q-00
	for te-wg-data@psg.com; Tue, 20 May 2003 15:55:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9SM-000C9d-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 15:55:14 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 11:51:40 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:56:01 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 0CDE09F605; Tue, 20 May 2003 11:41:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id AF88C9F605; Tue, 20 May 2003 11:41:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9F0-0009Oj-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:41:26 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19I9Ex-0009KS-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:41:23 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:40:46 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFdPAc001592; Tue, 20 May 2003 17:39:26 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 17:41:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 16:41:21 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9584@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KAAABaVhA=
X-OriginalArrivalTime: 20 May 2003 15:41:22.0056 (UTC) FILETIME=[43844880:01C31EE6]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA18896

Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 17:35
>> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Dimitry, Francois,
>> 
>> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > > 
>> > > However, this formula is incorrect for DS-TE when per-CT 
>> > > LOM's are used, since the above formula only reflects the Max 
>> > > Reservable Bandwidth for the entire link, and does not 
>> > > reflect the per-CT local overbooking factors.  So what 
>> > > formula do you suggest when per-CT LOM's are used?
>> 
>> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> > overbooking multiplier at CTc?  I don't see how this 
>> formula precludes
>> > per-CT LOM's to be used. Please explain.
>> 
>> Are you then proposing these formulas:
>> 
>> 1. When per-CT LOMs are not used:
>> 
>>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> 2. When per-CT LOMs are used:
>> 
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that correct?  Please confirm, and/or give the formulas 
>> you propose.

Yes, this is exactly what I propose.
I think this is similar to what you were proposing, only using "Max Res
Bw" instead of "Max Link Bw". 

Sorry I didn't make that very clear before.

Cheers

FRancois

>> 
>> Thanks,
>> Jerry
>> 





From owner-te-wg@ops.ietf.org  Tue May 20 12:01:40 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19276
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:01:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9bF-000Dir-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:04:25 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9b4-000Dhd-01
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:04:14 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:00:39 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:05:00 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id A26759F615; Tue, 20 May 2003 11:50:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 009CF9F612; Tue, 20 May 2003 11:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Pg-000BnM-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:52:28 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I9Pe-000Bn5-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:52:26 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:48:51 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:53:13 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C05039F614; Tue, 20 May 2003 11:38:54 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 287FA9F614; Tue, 20 May 2003 11:38:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I996-0008Pz-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:35:20 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19I993-0008PL-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:35:18 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KF911n000590 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 10:35:17 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC76602000E210F; Tue, 20 May 2003 11:35:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 10:35:16 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE91E@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KA
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 15:53:13.0046 (UTC) FILETIME=[EB4CBF60:01C31EE7]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-10.4 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19276

Dimitry, Francois,

> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> >         for all "c" in the range 0 <= c <= (MaxCT-1)
> > 
> > However, this formula is incorrect for DS-TE when per-CT 
> > LOM's are used, since the above formula only reflects the Max 
> > Reservable Bandwidth for the entire link, and does not 
> > reflect the per-CT local overbooking factors.  So what 
> > formula do you suggest when per-CT LOM's are used?

> Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
> overbooking multiplier at CTc?  I don't see how this formula precludes
> per-CT LOM's to be used. Please explain.

Are you then proposing these formulas:

1. When per-CT LOMs are not used:

     o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

2. When per-CT LOMs are used:

     o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

Is that correct?  Please confirm, and/or give the formulas you propose.

Thanks,
Jerry







From owner-te-wg@ops.ietf.org  Tue May 20 12:02:10 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19327
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:02:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9b6-000Dhw-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:04:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9b4-000Dhd-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:04:14 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:00:39 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:04:32 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 6D1D49F612; Tue, 20 May 2003 11:50:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 009CF9F612; Tue, 20 May 2003 11:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Pg-000BnM-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:52:28 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I9Pe-000Bn5-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:52:26 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:48:51 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:53:13 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C05039F614; Tue, 20 May 2003 11:38:54 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 287FA9F614; Tue, 20 May 2003 11:38:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I996-0008Pz-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:35:20 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19I993-0008PL-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:35:18 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KF911n000590 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 10:35:17 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC76602000E210F; Tue, 20 May 2003 11:35:17 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 10:35:16 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE91E@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KA
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 15:53:13.0046 (UTC) FILETIME=[EB4CBF60:01C31EE7]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-10.4 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19327

Dimitry, Francois,

> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> >         for all "c" in the range 0 <= c <= (MaxCT-1)
> > 
> > However, this formula is incorrect for DS-TE when per-CT 
> > LOM's are used, since the above formula only reflects the Max 
> > Reservable Bandwidth for the entire link, and does not 
> > reflect the per-CT local overbooking factors.  So what 
> > formula do you suggest when per-CT LOM's are used?

> Wouldn't 'Reserved (CTc)' it the above formula already accounts for the
> overbooking multiplier at CTc?  I don't see how this formula precludes
> per-CT LOM's to be used. Please explain.

Are you then proposing these formulas:

1. When per-CT LOMs are not used:

     o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

2. When per-CT LOMs are used:

     o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
         for all "c" in the range 0 <= c <= (MaxCT-1)

Is that correct?  Please confirm, and/or give the formulas you propose.

Thanks,
Jerry







From owner-te-wg@ops.ietf.org  Tue May 20 12:04:19 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19405
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:04:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9dr-000Dvc-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:07:07 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9do-000DvF-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:07:04 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:03:29 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:07:22 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C833A9F612; Tue, 20 May 2003 11:53:32 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id BF2E59F605; Tue, 20 May 2003 11:53:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Pa-000Bmj-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:52:22 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I9PX-000BmV-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:52:19 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:48:45 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:52:37 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 713B39F103; Tue, 20 May 2003 11:40:25 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id D3D969F103; Tue, 20 May 2003 11:40:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Cb-0008pQ-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:38:57 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19I9CZ-0008p4-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:38:55 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:38:18 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFakMu001005; Tue, 20 May 2003 17:36:57 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 17:38:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 16:38:51 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522D@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQ
X-OriginalArrivalTime: 20 May 2003 15:38:51.0883 (UTC) FILETIME=[EA01B3B0:01C31EE5]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19405

Hello Dimitry, Jerry, Waisum,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:58
>> To: 'Ash, Gerald R (Jerry), ALABS'; Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org; Lai, Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> > 
>> > Use of "Max Reservable Bandwidth" appears to be OK without 
>> > per-CT Local Overbooking Multipliers (LOMs).  That is, when 
>> > there is only *one* LOM for the entire link, then the formula 
>> > you give appears to be correct:
>> > 
>> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > However, this formula is incorrect for DS-TE when per-CT 
>> > LOM's are used, since the above formula only reflects the Max 
>> > Reservable Bandwidth for the entire link, and does not 
>> > reflect the per-CT local overbooking factors.  So what 
>> > formula do you suggest when per-CT LOM's are used?
>> >
>> 
>> Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> overbooking multiplier at CTc?  I don't see how this formula 
>> precludes
>> per-CT LOM's to be used. Please explain.
>>

I've been using "Reserved" and "Normalised" as per their definitions in
the proto draft, the RDM draft and the MAM draft.

Quoting from these drafts:

==================================
- "Reserved (CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
established LSPs which belong to CTc. 
- Normalised(CTc) : let us define "Normalised(CTc)" as
"Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
Multiplier for CTc defined in [DSTE-PROTO].
=====================================

What that means is that "Reserved(CTc)" does factor in the overbooking
method which is refered to as "LSP/link size overbooking" method and is
the overbooking method commonly used in TE networks. However, it does
NOT factor in the optional "Local Overbooking Multiplier" method.

"Normalised (CTc)"  factors-in both the "LSP/link size overbooking" and
the optional "Local Overbooking Multiplier" method.

Definitions of the "LSP/link size overbooking" method and "Local
overbooking Multiplier" method can be found in section "4.1.2. per-CT
Local Overbooking Multipliers (LOMs) of the dste-proto draft.

Based on this, my proposal is to include the following condition to
reflect the aggregate constraint when both overbooking methods are used
(ie "LSP/link size overbooking" method and "Local overbooking
Multiplier" method):

    o SUM (Normalised (CTc)) <= Max Reservable Bandwidth, 
        for all "c" in the range 0 <= c <= (MaxCT-1)

where "Normalised (CTc) is equal to "Reserved(CTc)/LOM(c)" as currently
defined in RDM and MAM drafts.

Thanks

Francois

>> Regards,
>>   Dimitry 
>> 







From owner-te-wg@ops.ietf.org  Tue May 20 12:04:34 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19441
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:04:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9eL-000E01-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:07:37 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9eI-000Dzg-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:07:34 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:03:59 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:08:21 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 979029F112; Tue, 20 May 2003 11:55:39 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 55C759F112; Tue, 20 May 2003 11:55:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9SO-000C9q-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:55:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I9SM-000C9d-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:55:14 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:51:40 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:56:01 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 0CDE09F605; Tue, 20 May 2003 11:41:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id AF88C9F605; Tue, 20 May 2003 11:41:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9F0-0009Oj-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:41:26 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19I9Ex-0009KS-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:41:23 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:40:46 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFdPAc001592; Tue, 20 May 2003 17:39:26 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 17:41:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 16:41:21 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9584@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KAAABaVhA=
X-OriginalArrivalTime: 20 May 2003 15:41:22.0056 (UTC) FILETIME=[43844880:01C31EE6]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19441

Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 17:35
>> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Dimitry, Francois,
>> 
>> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > > 
>> > > However, this formula is incorrect for DS-TE when per-CT 
>> > > LOM's are used, since the above formula only reflects the Max 
>> > > Reservable Bandwidth for the entire link, and does not 
>> > > reflect the per-CT local overbooking factors.  So what 
>> > > formula do you suggest when per-CT LOM's are used?
>> 
>> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> > overbooking multiplier at CTc?  I don't see how this 
>> formula precludes
>> > per-CT LOM's to be used. Please explain.
>> 
>> Are you then proposing these formulas:
>> 
>> 1. When per-CT LOMs are not used:
>> 
>>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> 2. When per-CT LOMs are used:
>> 
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that correct?  Please confirm, and/or give the formulas 
>> you propose.

Yes, this is exactly what I propose.
I think this is similar to what you were proposing, only using "Max Res
Bw" instead of "Max Link Bw". 

Sorry I didn't make that very clear before.

Cheers

FRancois

>> 
>> Thanks,
>> Jerry
>> 







From owner-te-wg@ops.ietf.org  Tue May 20 12:04:51 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19459
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:04:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9eS-000E0m-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:07:44 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9eI-000Dzg-01
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:07:34 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:03:59 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:07:52 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id B53529F113; Tue, 20 May 2003 11:55:39 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 55C759F112; Tue, 20 May 2003 11:55:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9SO-000C9q-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:55:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I9SM-000C9d-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:55:14 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:51:40 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:56:01 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 0CDE09F605; Tue, 20 May 2003 11:41:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id AF88C9F605; Tue, 20 May 2003 11:41:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9F0-0009Oj-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:41:26 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19I9Ex-0009KS-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:41:23 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:40:46 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFdPAc001592; Tue, 20 May 2003 17:39:26 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 17:41:22 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 16:41:21 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9584@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4D4FVXsju3SNRFmiqEAKaT/2cwABE3KAAABaVhA=
X-OriginalArrivalTime: 20 May 2003 15:41:22.0056 (UTC) FILETIME=[43844880:01C31EE6]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19459

Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 17:35
>> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Dimitry, Francois,
>> 
>> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > > 
>> > > However, this formula is incorrect for DS-TE when per-CT 
>> > > LOM's are used, since the above formula only reflects the Max 
>> > > Reservable Bandwidth for the entire link, and does not 
>> > > reflect the per-CT local overbooking factors.  So what 
>> > > formula do you suggest when per-CT LOM's are used?
>> 
>> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> > overbooking multiplier at CTc?  I don't see how this 
>> formula precludes
>> > per-CT LOM's to be used. Please explain.
>> 
>> Are you then proposing these formulas:
>> 
>> 1. When per-CT LOMs are not used:
>> 
>>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> 2. When per-CT LOMs are used:
>> 
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that correct?  Please confirm, and/or give the formulas 
>> you propose.

Yes, this is exactly what I propose.
I think this is similar to what you were proposing, only using "Max Res
Bw" instead of "Max Link Bw". 

Sorry I didn't make that very clear before.

Cheers

FRancois

>> 
>> Thanks,
>> Jerry
>> 







From owner-te-wg@ops.ietf.org  Tue May 20 12:04:54 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19458
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:04:50 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19I9dz-000Dw5-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:07:15 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19I9do-000DvF-01
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:07:04 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:03:29 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:07:51 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id BD73A9F605; Tue, 20 May 2003 11:53:32 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id BF2E59F605; Tue, 20 May 2003 11:53:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Pa-000Bmj-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:52:22 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19I9PX-000BmV-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:52:19 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:48:45 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 11:52:37 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 713B39F103; Tue, 20 May 2003 11:40:25 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id D3D969F103; Tue, 20 May 2003 11:40:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19I9Cb-0008pQ-00 for te-wg-data@psg.com; Tue, 20 May 2003 15:38:57 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19I9CZ-0008p4-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 15:38:55 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 17:38:18 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KFakMu001005; Tue, 20 May 2003 17:36:57 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 17:38:51 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 16:38:51 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522D@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQ
X-OriginalArrivalTime: 20 May 2003 15:38:51.0883 (UTC) FILETIME=[EA01B3B0:01C31EE5]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA19458

Hello Dimitry, Jerry, Waisum,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:58
>> To: 'Ash, Gerald R (Jerry), ALABS'; Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org; Lai, Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> > 
>> > Use of "Max Reservable Bandwidth" appears to be OK without 
>> > per-CT Local Overbooking Multipliers (LOMs).  That is, when 
>> > there is only *one* LOM for the entire link, then the formula 
>> > you give appears to be correct:
>> > 
>> >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > However, this formula is incorrect for DS-TE when per-CT 
>> > LOM's are used, since the above formula only reflects the Max 
>> > Reservable Bandwidth for the entire link, and does not 
>> > reflect the per-CT local overbooking factors.  So what 
>> > formula do you suggest when per-CT LOM's are used?
>> >
>> 
>> Wouldn't 'Reserved (CTc)' it the above formula already 
>> accounts for the
>> overbooking multiplier at CTc?  I don't see how this formula 
>> precludes
>> per-CT LOM's to be used. Please explain.
>>

I've been using "Reserved" and "Normalised" as per their definitions in
the proto draft, the RDM draft and the MAM draft.

Quoting from these drafts:

==================================
- "Reserved (CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
established LSPs which belong to CTc. 
- Normalised(CTc) : let us define "Normalised(CTc)" as
"Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
Multiplier for CTc defined in [DSTE-PROTO].
=====================================

What that means is that "Reserved(CTc)" does factor in the overbooking
method which is refered to as "LSP/link size overbooking" method and is
the overbooking method commonly used in TE networks. However, it does
NOT factor in the optional "Local Overbooking Multiplier" method.

"Normalised (CTc)"  factors-in both the "LSP/link size overbooking" and
the optional "Local Overbooking Multiplier" method.

Definitions of the "LSP/link size overbooking" method and "Local
overbooking Multiplier" method can be found in section "4.1.2. per-CT
Local Overbooking Multipliers (LOMs) of the dste-proto draft.

Based on this, my proposal is to include the following condition to
reflect the aggregate constraint when both overbooking methods are used
(ie "LSP/link size overbooking" method and "Local overbooking
Multiplier" method):

    o SUM (Normalised (CTc)) <= Max Reservable Bandwidth, 
        for all "c" in the range 0 <= c <= (MaxCT-1)

where "Normalised (CTc) is equal to "Reserved(CTc)/LOM(c)" as currently
defined in RDM and MAM drafts.

Thanks

Francois

>> Regards,
>>   Dimitry 
>> 







From owner-te-wg@ops.ietf.org  Tue May 20 12:32:25 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20400
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:32:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IA1s-000Iap-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:31:56 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IA1a-000IZl-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:31:38 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 20 May 2003 18:31:03 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KGSvHY010251;
	Tue, 20 May 2003 18:29:42 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:31:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 17:31:33 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9589@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0AAJAOIAAAVjGLA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 20 May 2003 16:31:34.0208 (UTC) FILETIME=[46E63400:01C31EED]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA20400

Jerry,

>> 
>> Yes, we need a formula to make explicit the 'implicit' 
>> constraint (and for all the BC models, not just MAM).
>> 

That's a good point.

With RDM, the proposed formula of:
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)

already applies, since we have:
	- SUM (Normalised(CTc)) <= BC0, and
	- BC0=Max Reservable Bw

It would be nice to have exact same formula also apply to MAM.

Cheers

Francois



From owner-te-wg@ops.ietf.org  Tue May 20 12:41:34 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20765
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:41:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IABU-000L2P-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:41:52 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IABS-000L28-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:41:50 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:38:15 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:42:37 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 94AB59F612; Tue, 20 May 2003 12:28:18 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id D22799F612; Tue, 20 May 2003 12:28:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IA1s-000Iap-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:31:56 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19IA1a-000IZl-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:31:38 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 18:31:03 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KGSvHY010251; Tue, 20 May 2003 18:29:42 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:31:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 17:31:33 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9589@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0AAJAOIAAAVjGLA=
X-OriginalArrivalTime: 20 May 2003 16:31:34.0208 (UTC) FILETIME=[46E63400:01C31EED]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA20765

Jerry,

>> 
>> Yes, we need a formula to make explicit the 'implicit' 
>> constraint (and for all the BC models, not just MAM).
>> 

That's a good point.

With RDM, the proposed formula of:
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)

already applies, since we have:
	- SUM (Normalised(CTc)) <= BC0, and
	- BC0=Max Reservable Bw

It would be nice to have exact same formula also apply to MAM.

Cheers

Francois





From owner-te-wg@ops.ietf.org  Tue May 20 12:50:41 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21052
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IAKO-000Myv-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:51:04 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IAKE-000My9-01
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:50:54 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:47:19 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:51:12 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 49E729F114; Tue, 20 May 2003 12:38:59 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id BDF449F112; Tue, 20 May 2003 12:38:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IABU-000L2P-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:41:52 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IABS-000L28-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:41:50 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:38:15 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:42:37 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 94AB59F612; Tue, 20 May 2003 12:28:18 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id D22799F612; Tue, 20 May 2003 12:28:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IA1s-000Iap-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:31:56 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19IA1a-000IZl-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:31:38 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 18:31:03 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KGSvHY010251; Tue, 20 May 2003 18:29:42 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:31:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 17:31:33 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9589@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0AAJAOIAAAVjGLA=
X-OriginalArrivalTime: 20 May 2003 16:31:34.0208 (UTC) FILETIME=[46E63400:01C31EED]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA21052

Jerry,

>> 
>> Yes, we need a formula to make explicit the 'implicit' 
>> constraint (and for all the BC models, not just MAM).
>> 

That's a good point.

With RDM, the proposed formula of:
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)

already applies, since we have:
	- SUM (Normalised(CTc)) <= BC0, and
	- BC0=Max Reservable Bw

It would be nice to have exact same formula also apply to MAM.

Cheers

Francois







From owner-te-wg@ops.ietf.org  Tue May 20 12:51:10 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21073
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:51:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IAKG-000MyP-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:50:56 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IAKE-000My9-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:50:54 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:47:19 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:51:41 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 3F5CA9F112; Tue, 20 May 2003 12:38:59 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id BDF449F112; Tue, 20 May 2003 12:38:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IABU-000L2P-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:41:52 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IABS-000L28-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:41:50 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:38:15 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:42:37 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 94AB59F612; Tue, 20 May 2003 12:28:18 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id D22799F612; Tue, 20 May 2003 12:28:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IA1s-000Iap-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:31:56 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19IA1a-000IZl-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:31:38 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 20 May 2003 18:31:03 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4KGSvHY010251; Tue, 20 May 2003 18:29:42 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:31:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Tue, 20 May 2003 17:31:33 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9589@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMLaTrf3clPEVebRUm+03EM7seKdgQTzP0gAKSaqLAAGg9l0AAJAOIAAAVjGLA=
X-OriginalArrivalTime: 20 May 2003 16:31:34.0208 (UTC) FILETIME=[46E63400:01C31EED]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA21073

Jerry,

>> 
>> Yes, we need a formula to make explicit the 'implicit' 
>> constraint (and for all the BC models, not just MAM).
>> 

That's a good point.

With RDM, the proposed formula of:
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)

already applies, since we have:
	- SUM (Normalised(CTc)) <= BC0, and
	- BC0=Max Reservable Bw

It would be nice to have exact same formula also apply to MAM.

Cheers

Francois







From owner-te-wg@ops.ietf.org  Tue May 20 12:53:19 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21138
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 12:53:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IANA-000Nak-00
	for te-wg-data@psg.com; Tue, 20 May 2003 16:53:56 +0000
Received: from pushme.nist.gov ([129.6.16.92] helo=postmark.nist.gov)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IAN7-000NaU-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 16:53:53 +0000
Received: from P612156.antd.nist.gov (genets.antd.nist.gov [129.6.60.42])
	by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h4KGrLbe007177;
	Tue, 20 May 2003 12:53:21 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030520124024.0258d600@fs3.antd.nist.gov>
X-Sender: marbukh@fs3.antd.nist.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 20 May 2003 12:53:12 -0400
To: gash@att.com
From: marbukh@antd.nist.gov
Subject: bandwidth reservation
Cc: te-wg@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-5.6 required=5.0
	tests=BAYES_01,NO_REAL_NAME
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi all,

In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
protection through reservation can be strengthen by referring to [2].

As it has been pointed out in [1], bandwidth reservation is beneficial for 
heavily and maybe moderately loaded networks.  However, for lightly loaded 
network complete bandwidth sharing is superior to bandwidth 
reservation.  The question remains what is the right strategy if load is 
uncertain, as in a case of default parameter setting or highly volatile 
load.  Obviously, load uncertainty creates risks of bandwidth over and 
under-provisioning.  The risk of over-provisioning is realized if bandwidth 
reservation is employed in expectation of high load, while the actual load 
is light.  In opposite case the risk of under-provisioning is realized.

Paper [2] has quantified these risks and proposed to optimize the default 
parameters by minimizing the worst-case scenario risk.  The main conclusion 
of [2] is that increase in the load uncertainty increases risk of bandwidth 
under-provisioning and thus strengthen case for bandwidth protection 
through reservation, especially in default setting context.

Some extensions of this approach to other situations of network 
provisioning under uncertain demands can be found in [3]-[5].

Appreciate any comments.

Thanks,
Vladimir

Ref.
[1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
[2]  V. Marbukh, "Network management under incomplete information on the 
operational environment," IEEE Int. Symp. on Information Theory and its 
Applications (ISITA2000), Honolulu, Hawaii, 2000.
[3]  V. Marbukh, "Robust traffic engineering: game theoretic perspective," 
ACM SIGMETRICS Performance Evaluation Review, Vol. 30, Issue 3, Dec. 2002.
[4]  V. Marbukh, "A scenario based framework for robust network 
provisioning," International Teletraffic Congress (ITC), Berlin, Germany, 2003.
[5]  V. Marbukh, "Network provisioning as a game against nature," IEEE 
International Communications Conference (ICC), Anchorage, AK, 2003.





From owner-te-wg@ops.ietf.org  Tue May 20 13:02:19 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21419
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 13:02:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IAVc-000Pjt-00
	for te-wg-data@psg.com; Tue, 20 May 2003 17:02:40 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IAVZ-000Pj6-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 17:02:37 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 12:59:03 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 13:03:24 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 8EC7B9F112; Tue, 20 May 2003 12:50:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 0347D9F103; Tue, 20 May 2003 12:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IANA-000Nak-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:53:56 +0000
Received: from pushme.nist.gov ([129.6.16.92] helo=postmark.nist.gov) by psg.com with esmtp (Exim 3.36 #1) id 19IAN7-000NaU-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:53:53 +0000
Received: from P612156.antd.nist.gov (genets.antd.nist.gov [129.6.60.42]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h4KGrLbe007177; Tue, 20 May 2003 12:53:21 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030520124024.0258d600@fs3.antd.nist.gov>
X-Sender: marbukh@fs3.antd.nist.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 20 May 2003 12:53:12 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 17:03:24.0609 (UTC) FILETIME=[B9964310:01C31EF1]
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org
To: braja@tellium.com
From: marbukh@antd.nist.gov
Subject: bandwidth reservation [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-5.6 required=5.0
	tests=BAYES_01,NO_REAL_NAME
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi all,

In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
protection through reservation can be strengthen by referring to [2].

As it has been pointed out in [1], bandwidth reservation is beneficial for 
heavily and maybe moderately loaded networks.  However, for lightly loaded 
network complete bandwidth sharing is superior to bandwidth 
reservation.  The question remains what is the right strategy if load is 
uncertain, as in a case of default parameter setting or highly volatile 
load.  Obviously, load uncertainty creates risks of bandwidth over and 
under-provisioning.  The risk of over-provisioning is realized if bandwidth 
reservation is employed in expectation of high load, while the actual load 
is light.  In opposite case the risk of under-provisioning is realized.

Paper [2] has quantified these risks and proposed to optimize the default 
parameters by minimizing the worst-case scenario risk.  The main conclusion 
of [2] is that increase in the load uncertainty increases risk of bandwidth 
under-provisioning and thus strengthen case for bandwidth protection 
through reservation, especially in default setting context.

Some extensions of this approach to other situations of network 
provisioning under uncertain demands can be found in [3]-[5].

Appreciate any comments.

Thanks,
Vladimir

Ref.
[1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
[2]  V. Marbukh, "Network management under incomplete information on the 
operational environment," IEEE Int. Symp. on Information Theory and its 
Applications (ISITA2000), Honolulu, Hawaii, 2000.
[3]  V. Marbukh, "Robust traffic engineering: game theoretic perspective," 
ACM SIGMETRICS Performance Evaluation Review, Vol. 30, Issue 3, Dec. 2002.
[4]  V. Marbukh, "A scenario based framework for robust network 
provisioning," International Teletraffic Congress (ITC), Berlin, Germany, 2003.
[5]  V. Marbukh, "Network provisioning as a game against nature," IEEE 
International Communications Conference (ICC), Anchorage, AK, 2003.







From owner-te-wg@ops.ietf.org  Tue May 20 13:11:08 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21622
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 13:11:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IAeI-00026t-00
	for te-wg-data@psg.com; Tue, 20 May 2003 17:11:38 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IAe7-00022c-01
	for te-wg@ops.ietf.org; Tue, 20 May 2003 17:11:27 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 13:07:52 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 13:11:45 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id E437E9F605; Tue, 20 May 2003 12:57:54 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 855EC9F605; Tue, 20 May 2003 12:57:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IAVc-000Pjt-00 for te-wg-data@psg.com; Tue, 20 May 2003 17:02:40 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IAVZ-000Pj6-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 17:02:37 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:59:03 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 13:03:24 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 8EC7B9F112; Tue, 20 May 2003 12:50:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 0347D9F103; Tue, 20 May 2003 12:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IANA-000Nak-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:53:56 +0000
Received: from pushme.nist.gov ([129.6.16.92] helo=postmark.nist.gov) by psg.com with esmtp (Exim 3.36 #1) id 19IAN7-000NaU-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:53:53 +0000
Received: from P612156.antd.nist.gov (genets.antd.nist.gov [129.6.60.42]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h4KGrLbe007177; Tue, 20 May 2003 12:53:21 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030520124024.0258d600@fs3.antd.nist.gov>
X-Sender: marbukh@fs3.antd.nist.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 20 May 2003 12:53:12 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 17:03:24.0609 (UTC) FILETIME=[B9964310:01C31EF1]
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org
To: braja@tellium.com
From: marbukh@antd.nist.gov
Subject: bandwidth reservation [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-5.6 required=5.0
	tests=BAYES_01,NO_REAL_NAME
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi all,

In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
protection through reservation can be strengthen by referring to [2].

As it has been pointed out in [1], bandwidth reservation is beneficial for 
heavily and maybe moderately loaded networks.  However, for lightly loaded 
network complete bandwidth sharing is superior to bandwidth 
reservation.  The question remains what is the right strategy if load is 
uncertain, as in a case of default parameter setting or highly volatile 
load.  Obviously, load uncertainty creates risks of bandwidth over and 
under-provisioning.  The risk of over-provisioning is realized if bandwidth 
reservation is employed in expectation of high load, while the actual load 
is light.  In opposite case the risk of under-provisioning is realized.

Paper [2] has quantified these risks and proposed to optimize the default 
parameters by minimizing the worst-case scenario risk.  The main conclusion 
of [2] is that increase in the load uncertainty increases risk of bandwidth 
under-provisioning and thus strengthen case for bandwidth protection 
through reservation, especially in default setting context.

Some extensions of this approach to other situations of network 
provisioning under uncertain demands can be found in [3]-[5].

Appreciate any comments.

Thanks,
Vladimir

Ref.
[1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
[2]  V. Marbukh, "Network management under incomplete information on the 
operational environment," IEEE Int. Symp. on Information Theory and its 
Applications (ISITA2000), Honolulu, Hawaii, 2000.
[3]  V. Marbukh, "Robust traffic engineering: game theoretic perspective," 
ACM SIGMETRICS Performance Evaluation Review, Vol. 30, Issue 3, Dec. 2002.
[4]  V. Marbukh, "A scenario based framework for robust network 
provisioning," International Teletraffic Congress (ITC), Berlin, Germany, 2003.
[5]  V. Marbukh, "Network provisioning as a game against nature," IEEE 
International Communications Conference (ICC), Anchorage, AK, 2003.









From owner-te-wg@ops.ietf.org  Tue May 20 13:11:38 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21687
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 13:11:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IAeA-00025r-00
	for te-wg-data@psg.com; Tue, 20 May 2003 17:11:30 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IAe7-00022c-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 17:11:27 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 13:07:52 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 13:12:14 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id EE69E9F612; Tue, 20 May 2003 12:57:54 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 855EC9F605; Tue, 20 May 2003 12:57:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IAVc-000Pjt-00 for te-wg-data@psg.com; Tue, 20 May 2003 17:02:40 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IAVZ-000Pj6-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 17:02:37 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 12:59:03 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 13:03:24 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 8EC7B9F112; Tue, 20 May 2003 12:50:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 0347D9F103; Tue, 20 May 2003 12:50:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IANA-000Nak-00 for te-wg-data@psg.com; Tue, 20 May 2003 16:53:56 +0000
Received: from pushme.nist.gov ([129.6.16.92] helo=postmark.nist.gov) by psg.com with esmtp (Exim 3.36 #1) id 19IAN7-000NaU-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 16:53:53 +0000
Received: from P612156.antd.nist.gov (genets.antd.nist.gov [129.6.60.42]) by postmark.nist.gov (8.12.5/8.12.5) with ESMTP id h4KGrLbe007177; Tue, 20 May 2003 12:53:21 -0400 (EDT)
Message-Id: <5.1.0.14.2.20030520124024.0258d600@fs3.antd.nist.gov>
X-Sender: marbukh@fs3.antd.nist.gov
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 20 May 2003 12:53:12 -0400
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 17:03:24.0609 (UTC) FILETIME=[B9964310:01C31EF1]
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org
To: braja@tellium.com
From: marbukh@antd.nist.gov
Subject: bandwidth reservation [owner-te-wg@ops.ietf.org in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List]
X-Spam-Status: No, hits=-5.6 required=5.0
	tests=BAYES_01,NO_REAL_NAME
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi all,

In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
protection through reservation can be strengthen by referring to [2].

As it has been pointed out in [1], bandwidth reservation is beneficial for 
heavily and maybe moderately loaded networks.  However, for lightly loaded 
network complete bandwidth sharing is superior to bandwidth 
reservation.  The question remains what is the right strategy if load is 
uncertain, as in a case of default parameter setting or highly volatile 
load.  Obviously, load uncertainty creates risks of bandwidth over and 
under-provisioning.  The risk of over-provisioning is realized if bandwidth 
reservation is employed in expectation of high load, while the actual load 
is light.  In opposite case the risk of under-provisioning is realized.

Paper [2] has quantified these risks and proposed to optimize the default 
parameters by minimizing the worst-case scenario risk.  The main conclusion 
of [2] is that increase in the load uncertainty increases risk of bandwidth 
under-provisioning and thus strengthen case for bandwidth protection 
through reservation, especially in default setting context.

Some extensions of this approach to other situations of network 
provisioning under uncertain demands can be found in [3]-[5].

Appreciate any comments.

Thanks,
Vladimir

Ref.
[1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
[2]  V. Marbukh, "Network management under incomplete information on the 
operational environment," IEEE Int. Symp. on Information Theory and its 
Applications (ISITA2000), Honolulu, Hawaii, 2000.
[3]  V. Marbukh, "Robust traffic engineering: game theoretic perspective," 
ACM SIGMETRICS Performance Evaluation Review, Vol. 30, Issue 3, Dec. 2002.
[4]  V. Marbukh, "A scenario based framework for robust network 
provisioning," International Teletraffic Congress (ITC), Berlin, Germany, 2003.
[5]  V. Marbukh, "Network provisioning as a game against nature," IEEE 
International Communications Conference (ICC), Anchorage, AK, 2003.









From owner-te-wg@ops.ietf.org  Tue May 20 14:57:29 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25093
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 14:57:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19ICGS-000PSA-00
	for te-wg-data@psg.com; Tue, 20 May 2003 18:55:08 +0000
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19ICGM-000PQs-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 18:55:02 +0000
Received: from 146-115-64-2.c3-0.bkl-ubr2.sbo-bkl.ma.cable.rcn.com ([146.115.64.2] helo=DASEP)
	by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
	id 19ICGI-0006hW-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 14:54:58 -0400
From: "sanford goldfless" <sandy9@rcn.com>
To: <te-wg@ops.ietf.org>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 14:55:12 -0400
Message-ID: <000001c31f01$5803ac90$6401a8c0@DASEP>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
In-Reply-To: <AC60B39EEE7320498063D37799FB82D93B9589@xbe-lon-313.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-15.3 required=5.0
	tests=BAYES_10,IN_REP_TO,ORIGINAL_MESSAGE
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Francois,

At this time, could you please clear up one point regarding overbooking
with RDM?

Max Reservable is now back as the  choice for the parameter indicating
the aggregate overbooking factor.  You also show nicely that it can
indeed be used in a CAC rule together with per-CT LOMs, by normalizing
the per-CT reservations and then comparing to Max Reservable.  A setting
of Max Reservable could be used to enforce a lower aggregate reservation
amount than the sum of the normalized per-TE-Class advertisements of
Unreserved would. 

So, therefore, doesn't the semantic of this parameter and that of BCO
now need to be kept distinct?  I say this because it was my
understanding that the advertised  bw constraints would not be adjusted
for link overbooking.  Or is this not right, and the BCs themselves in
RDM must somehow be adjusted for overbooking?

Thanks,
Sandy Goldfless  

Sanford Goldfless
192 Fuller St
Brookline MA 02446
617-738-1754
sandy9@rcn.com

-----Original Message-----
From: owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org] On
Behalf Of Francois Le Faucheur (flefauch)
Sent: Tuesday, May 20, 2003 12:32 PM
To: Ash, Gerald R (Jerry), ALABS
Cc: te-wg@ops.ietf.org
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts

Jerry,

>> 
>> Yes, we need a formula to make explicit the 'implicit' 
>> constraint (and for all the BC models, not just MAM).
>> 

That's a good point.

With RDM, the proposed formula of:
>>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>>          for all "c" in the range 0 <= c <= (MaxCT-1)

already applies, since we have:
	- SUM (Normalised(CTc)) <= BC0, and
	- BC0=Max Reservable Bw

It would be nice to have exact same formula also apply to MAM.

Cheers

Francois






From owner-te-wg@ops.ietf.org  Tue May 20 18:03:54 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02182
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:03:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IF7G-000BCs-00
	for te-wg-data@psg.com; Tue, 20 May 2003 21:57:50 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IF7D-000BCa-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 21:57:48 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLitkL018692
	for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:57:47 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020010BC57; Tue, 20 May 2003 17:57:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Tue, 20 May 2003 16:57:46 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CD@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA02182

Francois, All,

> I've been using "Reserved" and "Normalised" as per their definitions in
> the proto draft, the RDM draft and the MAM draft.
> 
> Quoting from these drafts:
> 
> ==================================
> - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
> us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
> established LSPs which belong to CTc. 
> - Normalised(CTc) : let us define "Normalised(CTc)" as
> "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
> Multiplier for CTc defined in [DSTE-PROTO].
> =====================================
> 
> What that means is that "Reserved(CTc)" does factor in the overbooking
> method which is referred to as "LSP/link size overbooking" method and is
> the overbooking method commonly used in TE networks. However, it does
> NOT factor in the optional "Local Overbooking Multiplier" method.
> 
> "Normalised(CTc)"  factors-in both the "LSP/link size overbooking" and
> the optional "Local Overbooking Multiplier" method.

Thank you for reviewing this.  

I had not appreciated that 'Reserved(CTc)' is actually a normalized quantity, normalized by the 'LSP/link size overbooking multiplier' (LSOM).

Just to further clarify, in terms of the actual bandwidth requested, I suppose this relationship must hold:

Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM

where

Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum of the bandwidth requested by all established LSPs which belong to CTc. 

Is that correct?  If so, then 'Reserved(CTc)' is also a 'normalized' quantity, but this time it is normalized by the LSOM, right?

Thanks for the clarifications,
Jerry



From owner-te-wg@ops.ietf.org  Tue May 20 18:09:04 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02729
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:09:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFGf-000Br3-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:07:33 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFGc-000Bqq-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:07:31 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLTi3l028200
	for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:07:30 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020010CA49; Tue, 20 May 2003 18:07:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: bandwidth reservation
Date: Tue, 20 May 2003 17:07:29 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CE@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: bandwidth reservation
Thread-Index: AcMe8G091Z8hY+nGTQi1hXQ2zdmZ2gAKnedA
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: <marbukh@antd.nist.gov>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA02729

Hi Vladimir,

> In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
> protection through reservation can be strengthen by referring to [2].
> 
> As it has been pointed out in [1], bandwidth reservation is beneficial for 
> heavily and maybe moderately loaded networks.  However, for lightly loaded 
> network complete bandwidth sharing is superior to bandwidth reservation.  
> The question remains what is the right strategy if load is uncertain, as 
> in a case of default parameter setting or highly volatile load.  Obviously,
> load uncertainty creates risks of bandwidth over and under-provisioning.  
> The risk of over-provisioning is realized if bandwidth reservation is 
> employed in expectation of high load, while the actual load is light.  
> In opposite case the risk of under-provisioning is realized.
> 
> Paper [2] has quantified these risks and proposed to optimize the default 
> parameters by minimizing the worst-case scenario risk.  The main conclusion 
> of [2] is that increase in the load uncertainty increases risk of bandwidth 
> under-provisioning and thus strengthen case for bandwidth protection 
> through reservation, especially in default setting context.
> ...
> Ref.
> [1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
> [2]  V. Marbukh, "Network management under incomplete information on the 
> operational environment," IEEE Int. Symp. on Information Theory and its 
> Applications (ISITA2000), Honolulu, Hawaii, 2000.

Thank you for your comments.  The work you describe in Ref. [2] sounds interesting.  Do you have a link to the paper, or, if not, could you send me the paper directly (in a private email)?

Good to hear from you.

Thanks,
Jerry




From owner-te-wg@ops.ietf.org  Tue May 20 18:19:37 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03473
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:19:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFR2-000CZv-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:18:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFQz-000CZV-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:18:13 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:14:38 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:18:59 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 227B19F605; Tue, 20 May 2003 18:04:37 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 90DB19F605; Tue, 20 May 2003 18:04:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IF7G-000BCs-00 for te-wg-data@psg.com; Tue, 20 May 2003 21:57:50 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19IF7D-000BCa-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 21:57:48 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLitkL018692 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:57:47 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC766020010BC57; Tue, 20 May 2003 17:57:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 16:57:46 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CD@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtA=
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 22:18:59.0984 (UTC) FILETIME=[CFF33100:01C31F1D]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA03473

Francois, All,

> I've been using "Reserved" and "Normalised" as per their definitions in
> the proto draft, the RDM draft and the MAM draft.
> 
> Quoting from these drafts:
> 
> ==================================
> - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
> us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
> established LSPs which belong to CTc. 
> - Normalised(CTc) : let us define "Normalised(CTc)" as
> "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
> Multiplier for CTc defined in [DSTE-PROTO].
> =====================================
> 
> What that means is that "Reserved(CTc)" does factor in the overbooking
> method which is referred to as "LSP/link size overbooking" method and is
> the overbooking method commonly used in TE networks. However, it does
> NOT factor in the optional "Local Overbooking Multiplier" method.
> 
> "Normalised(CTc)"  factors-in both the "LSP/link size overbooking" and
> the optional "Local Overbooking Multiplier" method.

Thank you for reviewing this.  

I had not appreciated that 'Reserved(CTc)' is actually a normalized quantity, normalized by the 'LSP/link size overbooking multiplier' (LSOM).

Just to further clarify, in terms of the actual bandwidth requested, I suppose this relationship must hold:

Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM

where

Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum of the bandwidth requested by all established LSPs which belong to CTc. 

Is that correct?  If so, then 'Reserved(CTc)' is also a 'normalized' quantity, but this time it is normalized by the LSOM, right?

Thanks for the clarifications,
Jerry





From owner-te-wg@ops.ietf.org  Tue May 20 18:23:01 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03549
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:23:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFUl-000CuY-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:22:07 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFUj-000CuK-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:22:05 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:18:30 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:22:23 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id ABB2D9F112; Tue, 20 May 2003 18:10:06 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 65C679F103; Tue, 20 May 2003 18:10:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFGf-000Br3-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:07:33 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFGc-000Bqq-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:07:31 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLTi3l028200 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:07:30 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC766020010CA49; Tue, 20 May 2003 18:07:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 17:07:29 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CE@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: bandwidth reservation
Thread-Index: AcMe8G091Z8hY+nGTQi1hXQ2zdmZ2gAKnedA
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 22:22:23.0171 (UTC) FILETIME=[490F1130:01C31F1E]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: bandwidth reservation [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA03549

Hi Vladimir,

> In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
> protection through reservation can be strengthen by referring to [2].
> 
> As it has been pointed out in [1], bandwidth reservation is beneficial for 
> heavily and maybe moderately loaded networks.  However, for lightly loaded 
> network complete bandwidth sharing is superior to bandwidth reservation.  
> The question remains what is the right strategy if load is uncertain, as 
> in a case of default parameter setting or highly volatile load.  Obviously,
> load uncertainty creates risks of bandwidth over and under-provisioning.  
> The risk of over-provisioning is realized if bandwidth reservation is 
> employed in expectation of high load, while the actual load is light.  
> In opposite case the risk of under-provisioning is realized.
> 
> Paper [2] has quantified these risks and proposed to optimize the default 
> parameters by minimizing the worst-case scenario risk.  The main conclusion 
> of [2] is that increase in the load uncertainty increases risk of bandwidth 
> under-provisioning and thus strengthen case for bandwidth protection 
> through reservation, especially in default setting context.
> ...
> Ref.
> [1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
> [2]  V. Marbukh, "Network management under incomplete information on the 
> operational environment," IEEE Int. Symp. on Information Theory and its 
> Applications (ISITA2000), Honolulu, Hawaii, 2000.

Thank you for your comments.  The work you describe in Ref. [2] sounds interesting.  Do you have a link to the paper, or, if not, could you send me the paper directly (in a private email)?

Good to hear from you.

Thanks,
Jerry






From owner-te-wg@ops.ietf.org  Tue May 20 18:43:57 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04368
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:43:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFoD-000EaB-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:42:13 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFoA-000EZu-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:42:10 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:38:36 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:42:28 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 12ABD9F103; Tue, 20 May 2003 18:30:11 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 890139F114; Tue, 20 May 2003 18:30:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFR2-000CZv-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:18:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFQz-000CZV-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:18:13 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:14:38 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:18:59 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 227B19F605; Tue, 20 May 2003 18:04:37 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 90DB19F605; Tue, 20 May 2003 18:04:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IF7G-000BCs-00 for te-wg-data@psg.com; Tue, 20 May 2003 21:57:50 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19IF7D-000BCa-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 21:57:48 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLitkL018692 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:57:47 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC766020010BC57; Tue, 20 May 2003 17:57:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 16:57:46 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CD@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtA=
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 22:18:59.0984 (UTC) FILETIME=[CFF33100:01C31F1D]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA04368

Francois, All,

> I've been using "Reserved" and "Normalised" as per their definitions in
> the proto draft, the RDM draft and the MAM draft.
> 
> Quoting from these drafts:
> 
> ==================================
> - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
> us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
> established LSPs which belong to CTc. 
> - Normalised(CTc) : let us define "Normalised(CTc)" as
> "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
> Multiplier for CTc defined in [DSTE-PROTO].
> =====================================
> 
> What that means is that "Reserved(CTc)" does factor in the overbooking
> method which is referred to as "LSP/link size overbooking" method and is
> the overbooking method commonly used in TE networks. However, it does
> NOT factor in the optional "Local Overbooking Multiplier" method.
> 
> "Normalised(CTc)"  factors-in both the "LSP/link size overbooking" and
> the optional "Local Overbooking Multiplier" method.

Thank you for reviewing this.  

I had not appreciated that 'Reserved(CTc)' is actually a normalized quantity, normalized by the 'LSP/link size overbooking multiplier' (LSOM).

Just to further clarify, in terms of the actual bandwidth requested, I suppose this relationship must hold:

Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM

where

Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum of the bandwidth requested by all established LSPs which belong to CTc. 

Is that correct?  If so, then 'Reserved(CTc)' is also a 'normalized' quantity, but this time it is normalized by the LSOM, right?

Thanks for the clarifications,
Jerry







From owner-te-wg@ops.ietf.org  Tue May 20 18:44:27 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04400
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:44:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFpR-000EgX-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:43:29 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFpN-000Efz-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:43:25 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:39:51 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:43:43 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 3A4449F114; Tue, 20 May 2003 18:31:27 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id AF1879F114; Tue, 20 May 2003 18:31:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFUl-000CuY-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:22:07 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFUj-000CuK-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:22:05 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:18:30 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:22:23 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id ABB2D9F112; Tue, 20 May 2003 18:10:06 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 65C679F103; Tue, 20 May 2003 18:10:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFGf-000Br3-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:07:33 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFGc-000Bqq-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:07:31 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLTi3l028200 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:07:30 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC766020010CA49; Tue, 20 May 2003 18:07:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 17:07:29 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CE@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: bandwidth reservation
Thread-Index: AcMe8G091Z8hY+nGTQi1hXQ2zdmZ2gAKnedA
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 22:22:23.0171 (UTC) FILETIME=[490F1130:01C31F1E]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: bandwidth reservation [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA04400

Hi Vladimir,

> In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
> protection through reservation can be strengthen by referring to [2].
> 
> As it has been pointed out in [1], bandwidth reservation is beneficial for 
> heavily and maybe moderately loaded networks.  However, for lightly loaded 
> network complete bandwidth sharing is superior to bandwidth reservation.  
> The question remains what is the right strategy if load is uncertain, as 
> in a case of default parameter setting or highly volatile load.  Obviously,
> load uncertainty creates risks of bandwidth over and under-provisioning.  
> The risk of over-provisioning is realized if bandwidth reservation is 
> employed in expectation of high load, while the actual load is light.  
> In opposite case the risk of under-provisioning is realized.
> 
> Paper [2] has quantified these risks and proposed to optimize the default 
> parameters by minimizing the worst-case scenario risk.  The main conclusion 
> of [2] is that increase in the load uncertainty increases risk of bandwidth 
> under-provisioning and thus strengthen case for bandwidth protection 
> through reservation, especially in default setting context.
> ...
> Ref.
> [1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
> [2]  V. Marbukh, "Network management under incomplete information on the 
> operational environment," IEEE Int. Symp. on Information Theory and its 
> Applications (ISITA2000), Honolulu, Hawaii, 2000.

Thank you for your comments.  The work you describe in Ref. [2] sounds interesting.  Do you have a link to the paper, or, if not, could you send me the paper directly (in a private email)?

Good to hear from you.

Thanks,
Jerry








From owner-te-wg@ops.ietf.org  Tue May 20 18:44:28 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04415
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:44:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFpY-000EhD-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:43:36 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFpO-000Efz-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:43:26 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:39:51 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:44:12 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 451469F115; Tue, 20 May 2003 18:31:27 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id AF1879F114; Tue, 20 May 2003 18:31:24 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFUl-000CuY-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:22:07 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFUj-000CuK-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:22:05 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:18:30 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:22:23 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id ABB2D9F112; Tue, 20 May 2003 18:10:06 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 65C679F103; Tue, 20 May 2003 18:10:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFGf-000Br3-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:07:33 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFGc-000Bqq-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:07:31 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLTi3l028200 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:07:30 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC766020010CA49; Tue, 20 May 2003 18:07:29 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 17:07:29 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CE@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: bandwidth reservation
Thread-Index: AcMe8G091Z8hY+nGTQi1hXQ2zdmZ2gAKnedA
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 22:22:23.0171 (UTC) FILETIME=[490F1130:01C31F1E]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: bandwidth reservation [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA04415

Hi Vladimir,

> In my opinion, Draft's [1] claim of the beneficial effect of bandwidth 
> protection through reservation can be strengthen by referring to [2].
> 
> As it has been pointed out in [1], bandwidth reservation is beneficial for 
> heavily and maybe moderately loaded networks.  However, for lightly loaded 
> network complete bandwidth sharing is superior to bandwidth reservation.  
> The question remains what is the right strategy if load is uncertain, as 
> in a case of default parameter setting or highly volatile load.  Obviously,
> load uncertainty creates risks of bandwidth over and under-provisioning.  
> The risk of over-provisioning is realized if bandwidth reservation is 
> employed in expectation of high load, while the actual load is light.  
> In opposite case the risk of under-provisioning is realized.
> 
> Paper [2] has quantified these risks and proposed to optimize the default 
> parameters by minimizing the worst-case scenario risk.  The main conclusion 
> of [2] is that increase in the load uncertainty increases risk of bandwidth 
> under-provisioning and thus strengthen case for bandwidth protection 
> through reservation, especially in default setting context.
> ...
> Ref.
> [1]  http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt
> [2]  V. Marbukh, "Network management under incomplete information on the 
> operational environment," IEEE Int. Symp. on Information Theory and its 
> Applications (ISITA2000), Honolulu, Hawaii, 2000.

Thank you for your comments.  The work you describe in Ref. [2] sounds interesting.  Do you have a link to the paper, or, if not, could you send me the paper directly (in a private email)?

Good to hear from you.

Thanks,
Jerry








From owner-te-wg@ops.ietf.org  Tue May 20 18:44:57 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04438
	for <tewg-archive@lists.ietf.org>; Tue, 20 May 2003 18:44:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IFoL-000EaL-00
	for te-wg-data@psg.com; Tue, 20 May 2003 22:42:21 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IFoB-000Ea4-00
	for te-wg@ops.ietf.org; Tue, 20 May 2003 22:42:11 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 May 2003 18:38:36 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:42:57 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 1E3179F114; Tue, 20 May 2003 18:30:11 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 890139F114; Tue, 20 May 2003 18:30:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IFR2-000CZv-00 for te-wg-data@psg.com; Tue, 20 May 2003 22:18:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IFQz-000CZV-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 22:18:13 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:14:38 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Tue, 20 May 2003 18:18:59 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 227B19F605; Tue, 20 May 2003 18:04:37 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 90DB19F605; Tue, 20 May 2003 18:04:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IF7G-000BCs-00 for te-wg-data@psg.com; Tue, 20 May 2003 21:57:50 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19IF7D-000BCa-00 for te-wg@ops.ietf.org; Tue, 20 May 2003 21:57:48 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4KLitkL018692 for <te-wg@ops.ietf.org>; Tue, 20 May 2003 17:57:47 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC766020010BC57; Tue, 20 May 2003 17:57:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Tue, 20 May 2003 16:57:46 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67CD@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtA=
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 20 May 2003 22:18:59.0984 (UTC) FILETIME=[CFF33100:01C31F1D]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA04438

Francois, All,

> I've been using "Reserved" and "Normalised" as per their definitions in
> the proto draft, the RDM draft and the MAM draft.
> 
> Quoting from these drafts:
> 
> ==================================
> - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= MaxCT ) ,let
> us define "Reserved(CTc)" as the sum of the bandwidth reserved by all
> established LSPs which belong to CTc. 
> - Normalised(CTc) : let us define "Normalised(CTc)" as
> "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
> Multiplier for CTc defined in [DSTE-PROTO].
> =====================================
> 
> What that means is that "Reserved(CTc)" does factor in the overbooking
> method which is referred to as "LSP/link size overbooking" method and is
> the overbooking method commonly used in TE networks. However, it does
> NOT factor in the optional "Local Overbooking Multiplier" method.
> 
> "Normalised(CTc)"  factors-in both the "LSP/link size overbooking" and
> the optional "Local Overbooking Multiplier" method.

Thank you for reviewing this.  

I had not appreciated that 'Reserved(CTc)' is actually a normalized quantity, normalized by the 'LSP/link size overbooking multiplier' (LSOM).

Just to further clarify, in terms of the actual bandwidth requested, I suppose this relationship must hold:

Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM

where

Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum of the bandwidth requested by all established LSPs which belong to CTc. 

Is that correct?  If so, then 'Reserved(CTc)' is also a 'normalized' quantity, but this time it is normalized by the LSOM, right?

Thanks for the clarifications,
Jerry







From owner-te-wg@ops.ietf.org  Wed May 21 05:08:01 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12528
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 05:08:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IPWc-000J54-00
	for te-wg-data@psg.com; Wed, 21 May 2003 09:04:42 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IPWZ-000J4F-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 09:04:39 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 21 May 2003 11:04:02 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4L92eeM005861;
	Wed, 21 May 2003 11:02:41 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 11:04:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Wed, 21 May 2003 10:04:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522F@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0A==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>, "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
X-OriginalArrivalTime: 21 May 2003 09:04:36.0989 (UTC) FILETIME=[010112D0:01C31F78]
X-Spam-Status: No, hits=-9.0 required=5.0
	tests=BAYES_10,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA12528

Hello Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 23:58
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Francois, All,
>> 
>> > I've been using "Reserved" and "Normalised" as per their 
>> definitions in
>> > the proto draft, the RDM draft and the MAM draft.
>> > 
>> > Quoting from these drafts:
>> > 
>> > ==================================
>> > - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= 
>> MaxCT ) ,let
>> > us define "Reserved(CTc)" as the sum of the bandwidth 
>> reserved by all
>> > established LSPs which belong to CTc. 
>> > - Normalised(CTc) : let us define "Normalised(CTc)" as
>> > "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
>> > Multiplier for CTc defined in [DSTE-PROTO].
>> > =====================================
>> > 
>> > What that means is that "Reserved(CTc)" does factor in the 
>> overbooking
>> > method which is referred to as "LSP/link size overbooking" 
>> method and is
>> > the overbooking method commonly used in TE networks. 
>> However, it does
>> > NOT factor in the optional "Local Overbooking Multiplier" method.
>> > 
>> > "Normalised(CTc)"  factors-in both the "LSP/link size 
>> overbooking" and
>> > the optional "Local Overbooking Multiplier" method.
>> 
>> Thank you for reviewing this.  
>> 
>> I had not appreciated that 'Reserved(CTc)' is actually a 
>> normalized quantity, normalized by the 'LSP/link size 
>> overbooking multiplier' (LSOM).
>> 
>> Just to further clarify, in terms of the actual bandwidth 
>> requested, I suppose this relationship must hold:
>> 
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc. 
>> 
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
>>

Yes, I do agree with your statement that "Reserved(CTc)" is also
normalised in the sense that it reflects the LSP/link size overbooking.

This is analogous to what happens today with regular TE. The bandwidth
that is configured as the LSP size may reflect some over/underbooking
factor. Similarly the Max Reservable bandwidth may reflect some
over/underbooking ratio.
The good thing is that from TE's perspective, the only thing we have to
worry about are these "normalised" bandwidth (reflecting LSP/link size
Overbooking).
If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
TE) whether the SP expects a peak load of 200 on that LSP and applied an
LSP overbooking of 2, or whether the SP actually expects a peak load of
100 and applied no overbooking.
Similarly, the relevant constraint is the Max Reservable Bandwidth
(which can be configured smaller or larger than real link capacity). For
TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
doesn't really matter whether the link is actually indeed of 1000 or
whether it is actually a link of 500 with an link overbooking of 2.
Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
link of 1000. That's it.
This is why, in regular TE, only the LSP bandwidth is the one considered
(and is indeed a normalised bandwidth factoring LSP Size Overbooking)
and only Max Reservable is considered (which is also a normalised value
factoring in the link size overbooking). 
One interesting point is that TE does not explicitely need the concept
of LSP size Overbooking *Multiplier" and the Link Size Overbooking
*Multiplier". They are effectively transparent to TE which works only on
normalised bandwidth. 

The DS-TE approach is the same with respect to LSP/link Size Overbooking
ie the only "bandwidth" we are concerned about is the actual LSP size,
which factors in the LSP Size Overbooking (ie which is normalised , as
you stated) and the BCs [+ Max Reservable Bw (as proposed)].
For DS-TE, like for TE, I think we don't need to explicitely define in
the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
nor formulas using them because we operate directly/exclusively on
"normalised" values. But I think we  agree in spirit in what those would
be anyway, based on our discussion.

Thanks

Francois


PS: of course, as mentioned earlier, "Reserved(CTc)" factors LSOMs but
does not factor the LOMs. "Normalised(CTc)" does factor both.


 
>> Thanks for the clarifications,
>> Jerry
>> 



From owner-te-wg@ops.ietf.org  Wed May 21 05:22:07 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12759
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 05:22:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IPmn-000Krc-00
	for te-wg-data@psg.com; Wed, 21 May 2003 09:21:25 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IPmk-000KrJ-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 09:21:22 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 21 May 2003 11:20:45 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4L9JNiW009194;
	Wed, 21 May 2003 11:19:25 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 11:21:20 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Wed, 21 May 2003 10:21:19 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5230@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMfCFyoVEUfZOB2SrqctSbiT0CA4QAb+OKA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "sanford goldfless" <sandy9@rcn.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 21 May 2003 09:21:20.0292 (UTC) FILETIME=[5704F640:01C31F7A]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA12759

Hello Sandy,

>> -----Original Message-----
>> From: sanford goldfless [mailto:sandy9@rcn.com] 
>> Sent: 20 May 2003 20:55
>> To: te-wg@ops.ietf.org
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Francois,
>> 
>> At this time, could you please clear up one point regarding 
>> overbooking
>> with RDM?
>> 
>> Max Reservable is now back as the  choice for the parameter 
>> indicating
>> the aggregate overbooking factor.  

Yes, but note that this was the asumption already in current RDM draft.

>>You also show nicely that it can
>> indeed be used in a CAC rule together with per-CT LOMs, by 
>> normalizing
>> the per-CT reservations and then comparing to Max 
>> Reservable.  A setting
>> of Max Reservable could be used to enforce a lower aggregate 
>> reservation
>> amount than the sum of the normalized per-TE-Class advertisements of
>> Unreserved would. 
>> 
>> So, therefore, doesn't the semantic of this parameter and that of BCO
>> now need to be kept distinct?  I say this because it was my
>> understanding that the advertised  bw constraints would not 
>> be adjusted
>> for link overbooking.  

Actually, again here, we need to distinguish the overbooking related to
LSP/Link Size Overbooking and realted to the per-CT Link Overbooking
Multipliers.

Advertised BCs are not adjusted to reflect the Local Overbooking
Multipliers, nor is Max Reservable Bw.
But advertised BCs do inherently reflect the LSP/Link Size overbooking
factors (as discussed in previous message to Jerry, BCs are "normalised"
bandwidth which factor in the Link Size Overbooking, just like Max
Reservable Bandwidth).

Refering to section "6.3 Example Usage of LOM" of diff-te-russian-01:
	 -the advertised BCs are BC0=200 and BC1=100 (regardless of the
LOM values).
	- However, it may very well be that the actual link bandwidth is
in reality only of 100 and that BC0=Max-Res-Bw effectively=200 already
factors in an overbooking factor of 2.

So I think BC0 does coincide with Max Reservable Bw (in the case of RDM
only of course).

Thanks

Francois

>>Or is this not right, and the BCs 
>> themselves in
>> RDM must somehow be adjusted for overbooking?
>> 
>> Thanks,
>> Sandy Goldfless  
>> 
>> Sanford Goldfless
>> 192 Fuller St
>> Brookline MA 02446
>> 617-738-1754
>> sandy9@rcn.com
>> 
>> -----Original Message-----
>> From: owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org] On
>> Behalf Of Francois Le Faucheur (flefauch)
>> Sent: Tuesday, May 20, 2003 12:32 PM
>> To: Ash, Gerald R (Jerry), ALABS
>> Cc: te-wg@ops.ietf.org
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> Jerry,
>> 
>> >> 
>> >> Yes, we need a formula to make explicit the 'implicit' 
>> >> constraint (and for all the BC models, not just MAM).
>> >> 
>> 
>> That's a good point.
>> 
>> With RDM, the proposed formula of:
>> >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>> >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> already applies, since we have:
>> 	- SUM (Normalised(CTc)) <= BC0, and
>> 	- BC0=Max Reservable Bw
>> 
>> It would be nice to have exact same formula also apply to MAM.
>> 
>> Cheers
>> 
>> Francois
>> 
>> 
>> 
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed May 21 05:26:03 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA12831
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 05:26:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IPr4-000LKw-00
	for te-wg-data@psg.com; Wed, 21 May 2003 09:25:50 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IPr1-000LKi-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 09:25:47 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 05:22:12 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:26:34 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 7D8389F614; Wed, 21 May 2003 05:12:03 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id BD4939F605; Wed, 21 May 2003 05:11:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IPWc-000J54-00 for te-wg-data@psg.com; Wed, 21 May 2003 09:04:42 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19IPWZ-000J4F-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 09:04:39 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 21 May 2003 11:04:02 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4L92eeM005861; Wed, 21 May 2003 11:02:41 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 11:04:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Wed, 21 May 2003 10:04:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522F@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0A==
X-OriginalArrivalTime: 21 May 2003 09:04:36.0989 (UTC) FILETIME=[010112D0:01C31F78]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA12831

Hello Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 23:58
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Francois, All,
>> 
>> > I've been using "Reserved" and "Normalised" as per their 
>> definitions in
>> > the proto draft, the RDM draft and the MAM draft.
>> > 
>> > Quoting from these drafts:
>> > 
>> > ==================================
>> > - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= 
>> MaxCT ) ,let
>> > us define "Reserved(CTc)" as the sum of the bandwidth 
>> reserved by all
>> > established LSPs which belong to CTc. 
>> > - Normalised(CTc) : let us define "Normalised(CTc)" as
>> > "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
>> > Multiplier for CTc defined in [DSTE-PROTO].
>> > =====================================
>> > 
>> > What that means is that "Reserved(CTc)" does factor in the 
>> overbooking
>> > method which is referred to as "LSP/link size overbooking" 
>> method and is
>> > the overbooking method commonly used in TE networks. 
>> However, it does
>> > NOT factor in the optional "Local Overbooking Multiplier" method.
>> > 
>> > "Normalised(CTc)"  factors-in both the "LSP/link size 
>> overbooking" and
>> > the optional "Local Overbooking Multiplier" method.
>> 
>> Thank you for reviewing this.  
>> 
>> I had not appreciated that 'Reserved(CTc)' is actually a 
>> normalized quantity, normalized by the 'LSP/link size 
>> overbooking multiplier' (LSOM).
>> 
>> Just to further clarify, in terms of the actual bandwidth 
>> requested, I suppose this relationship must hold:
>> 
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc. 
>> 
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
>>

Yes, I do agree with your statement that "Reserved(CTc)" is also
normalised in the sense that it reflects the LSP/link size overbooking.

This is analogous to what happens today with regular TE. The bandwidth
that is configured as the LSP size may reflect some over/underbooking
factor. Similarly the Max Reservable bandwidth may reflect some
over/underbooking ratio.
The good thing is that from TE's perspective, the only thing we have to
worry about are these "normalised" bandwidth (reflecting LSP/link size
Overbooking).
If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
TE) whether the SP expects a peak load of 200 on that LSP and applied an
LSP overbooking of 2, or whether the SP actually expects a peak load of
100 and applied no overbooking.
Similarly, the relevant constraint is the Max Reservable Bandwidth
(which can be configured smaller or larger than real link capacity). For
TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
doesn't really matter whether the link is actually indeed of 1000 or
whether it is actually a link of 500 with an link overbooking of 2.
Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
link of 1000. That's it.
This is why, in regular TE, only the LSP bandwidth is the one considered
(and is indeed a normalised bandwidth factoring LSP Size Overbooking)
and only Max Reservable is considered (which is also a normalised value
factoring in the link size overbooking). 
One interesting point is that TE does not explicitely need the concept
of LSP size Overbooking *Multiplier" and the Link Size Overbooking
*Multiplier". They are effectively transparent to TE which works only on
normalised bandwidth. 

The DS-TE approach is the same with respect to LSP/link Size Overbooking
ie the only "bandwidth" we are concerned about is the actual LSP size,
which factors in the LSP Size Overbooking (ie which is normalised , as
you stated) and the BCs [+ Max Reservable Bw (as proposed)].
For DS-TE, like for TE, I think we don't need to explicitely define in
the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
nor formulas using them because we operate directly/exclusively on
"normalised" values. But I think we  agree in spirit in what those would
be anyway, based on our discussion.

Thanks

Francois


PS: of course, as mentioned earlier, "Reserved(CTc)" factors LSOMs but
does not factor the LOMs. "Normalised(CTc)" does factor both.


 
>> Thanks for the clarifications,
>> Jerry
>> 





From owner-te-wg@ops.ietf.org  Wed May 21 05:41:12 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13307
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 05:41:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IQ5C-000N0G-00
	for te-wg-data@psg.com; Wed, 21 May 2003 09:40:26 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IQ59-000Mzz-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 09:40:23 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 05:36:49 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:41:10 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 1BAEA9F612; Wed, 21 May 2003 05:26:40 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id A4CAE9F612; Wed, 21 May 2003 05:26:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IPr4-000LKw-00 for te-wg-data@psg.com; Wed, 21 May 2003 09:25:50 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IPr1-000LKi-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 09:25:47 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:22:12 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:26:34 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 7D8389F614; Wed, 21 May 2003 05:12:03 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id BD4939F605; Wed, 21 May 2003 05:11:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IPWc-000J54-00 for te-wg-data@psg.com; Wed, 21 May 2003 09:04:42 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19IPWZ-000J4F-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 09:04:39 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 21 May 2003 11:04:02 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4L92eeM005861; Wed, 21 May 2003 11:02:41 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 11:04:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Wed, 21 May 2003 10:04:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522F@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0A==
X-OriginalArrivalTime: 21 May 2003 09:04:36.0989 (UTC) FILETIME=[010112D0:01C31F78]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA13307

Hello Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 23:58
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Francois, All,
>> 
>> > I've been using "Reserved" and "Normalised" as per their 
>> definitions in
>> > the proto draft, the RDM draft and the MAM draft.
>> > 
>> > Quoting from these drafts:
>> > 
>> > ==================================
>> > - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= 
>> MaxCT ) ,let
>> > us define "Reserved(CTc)" as the sum of the bandwidth 
>> reserved by all
>> > established LSPs which belong to CTc. 
>> > - Normalised(CTc) : let us define "Normalised(CTc)" as
>> > "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
>> > Multiplier for CTc defined in [DSTE-PROTO].
>> > =====================================
>> > 
>> > What that means is that "Reserved(CTc)" does factor in the 
>> overbooking
>> > method which is referred to as "LSP/link size overbooking" 
>> method and is
>> > the overbooking method commonly used in TE networks. 
>> However, it does
>> > NOT factor in the optional "Local Overbooking Multiplier" method.
>> > 
>> > "Normalised(CTc)"  factors-in both the "LSP/link size 
>> overbooking" and
>> > the optional "Local Overbooking Multiplier" method.
>> 
>> Thank you for reviewing this.  
>> 
>> I had not appreciated that 'Reserved(CTc)' is actually a 
>> normalized quantity, normalized by the 'LSP/link size 
>> overbooking multiplier' (LSOM).
>> 
>> Just to further clarify, in terms of the actual bandwidth 
>> requested, I suppose this relationship must hold:
>> 
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc. 
>> 
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
>>

Yes, I do agree with your statement that "Reserved(CTc)" is also
normalised in the sense that it reflects the LSP/link size overbooking.

This is analogous to what happens today with regular TE. The bandwidth
that is configured as the LSP size may reflect some over/underbooking
factor. Similarly the Max Reservable bandwidth may reflect some
over/underbooking ratio.
The good thing is that from TE's perspective, the only thing we have to
worry about are these "normalised" bandwidth (reflecting LSP/link size
Overbooking).
If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
TE) whether the SP expects a peak load of 200 on that LSP and applied an
LSP overbooking of 2, or whether the SP actually expects a peak load of
100 and applied no overbooking.
Similarly, the relevant constraint is the Max Reservable Bandwidth
(which can be configured smaller or larger than real link capacity). For
TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
doesn't really matter whether the link is actually indeed of 1000 or
whether it is actually a link of 500 with an link overbooking of 2.
Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
link of 1000. That's it.
This is why, in regular TE, only the LSP bandwidth is the one considered
(and is indeed a normalised bandwidth factoring LSP Size Overbooking)
and only Max Reservable is considered (which is also a normalised value
factoring in the link size overbooking). 
One interesting point is that TE does not explicitely need the concept
of LSP size Overbooking *Multiplier" and the Link Size Overbooking
*Multiplier". They are effectively transparent to TE which works only on
normalised bandwidth. 

The DS-TE approach is the same with respect to LSP/link Size Overbooking
ie the only "bandwidth" we are concerned about is the actual LSP size,
which factors in the LSP Size Overbooking (ie which is normalised , as
you stated) and the BCs [+ Max Reservable Bw (as proposed)].
For DS-TE, like for TE, I think we don't need to explicitely define in
the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
nor formulas using them because we operate directly/exclusively on
"normalised" values. But I think we  agree in spirit in what those would
be anyway, based on our discussion.

Thanks

Francois


PS: of course, as mentioned earlier, "Reserved(CTc)" factors LSOMs but
does not factor the LOMs. "Normalised(CTc)" does factor both.


 
>> Thanks for the clarifications,
>> Jerry
>> 







From owner-te-wg@ops.ietf.org  Wed May 21 05:41:42 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13334
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 05:41:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IQ5K-000N0P-00
	for te-wg-data@psg.com; Wed, 21 May 2003 09:40:34 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IQ5A-000Mzz-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 09:40:24 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 05:36:49 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:40:41 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 263899F615; Wed, 21 May 2003 05:26:40 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id A4CAE9F612; Wed, 21 May 2003 05:26:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IPr4-000LKw-00 for te-wg-data@psg.com; Wed, 21 May 2003 09:25:50 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IPr1-000LKi-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 09:25:47 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:22:12 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 05:26:34 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 7D8389F614; Wed, 21 May 2003 05:12:03 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id BD4939F605; Wed, 21 May 2003 05:11:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IPWc-000J54-00 for te-wg-data@psg.com; Wed, 21 May 2003 09:04:42 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19IPWZ-000J4F-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 09:04:39 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 21 May 2003 11:04:02 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4L92eeM005861; Wed, 21 May 2003 11:02:41 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 11:04:36 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Wed, 21 May 2003 10:04:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B522F@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0A==
X-OriginalArrivalTime: 21 May 2003 09:04:36.0989 (UTC) FILETIME=[010112D0:01C31F78]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA13334

Hello Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 20 May 2003 23:58
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Francois, All,
>> 
>> > I've been using "Reserved" and "Normalised" as per their 
>> definitions in
>> > the proto draft, the RDM draft and the MAM draft.
>> > 
>> > Quoting from these drafts:
>> > 
>> > ==================================
>> > - "Reserved(CTc)": For a given Class-Type CTc ( 0 <= c <= 
>> MaxCT ) ,let
>> > us define "Reserved(CTc)" as the sum of the bandwidth 
>> reserved by all
>> > established LSPs which belong to CTc. 
>> > - Normalised(CTc) : let us define "Normalised(CTc)" as
>> > "Reserved(CTc)/LOM(c)", where LOM (c) is the Local Overbooking
>> > Multiplier for CTc defined in [DSTE-PROTO].
>> > =====================================
>> > 
>> > What that means is that "Reserved(CTc)" does factor in the 
>> overbooking
>> > method which is referred to as "LSP/link size overbooking" 
>> method and is
>> > the overbooking method commonly used in TE networks. 
>> However, it does
>> > NOT factor in the optional "Local Overbooking Multiplier" method.
>> > 
>> > "Normalised(CTc)"  factors-in both the "LSP/link size 
>> overbooking" and
>> > the optional "Local Overbooking Multiplier" method.
>> 
>> Thank you for reviewing this.  
>> 
>> I had not appreciated that 'Reserved(CTc)' is actually a 
>> normalized quantity, normalized by the 'LSP/link size 
>> overbooking multiplier' (LSOM).
>> 
>> Just to further clarify, in terms of the actual bandwidth 
>> requested, I suppose this relationship must hold:
>> 
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc. 
>> 
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
>>

Yes, I do agree with your statement that "Reserved(CTc)" is also
normalised in the sense that it reflects the LSP/link size overbooking.

This is analogous to what happens today with regular TE. The bandwidth
that is configured as the LSP size may reflect some over/underbooking
factor. Similarly the Max Reservable bandwidth may reflect some
over/underbooking ratio.
The good thing is that from TE's perspective, the only thing we have to
worry about are these "normalised" bandwidth (reflecting LSP/link size
Overbooking).
If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
TE) whether the SP expects a peak load of 200 on that LSP and applied an
LSP overbooking of 2, or whether the SP actually expects a peak load of
100 and applied no overbooking.
Similarly, the relevant constraint is the Max Reservable Bandwidth
(which can be configured smaller or larger than real link capacity). For
TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
doesn't really matter whether the link is actually indeed of 1000 or
whether it is actually a link of 500 with an link overbooking of 2.
Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
link of 1000. That's it.
This is why, in regular TE, only the LSP bandwidth is the one considered
(and is indeed a normalised bandwidth factoring LSP Size Overbooking)
and only Max Reservable is considered (which is also a normalised value
factoring in the link size overbooking). 
One interesting point is that TE does not explicitely need the concept
of LSP size Overbooking *Multiplier" and the Link Size Overbooking
*Multiplier". They are effectively transparent to TE which works only on
normalised bandwidth. 

The DS-TE approach is the same with respect to LSP/link Size Overbooking
ie the only "bandwidth" we are concerned about is the actual LSP size,
which factors in the LSP Size Overbooking (ie which is normalised , as
you stated) and the BCs [+ Max Reservable Bw (as proposed)].
For DS-TE, like for TE, I think we don't need to explicitely define in
the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
nor formulas using them because we operate directly/exclusively on
"normalised" values. But I think we  agree in spirit in what those would
be anyway, based on our discussion.

Thanks

Francois


PS: of course, as mentioned earlier, "Reserved(CTc)" factors LSOMs but
does not factor the LOMs. "Normalised(CTc)" does factor both.


 
>> Thanks for the clarifications,
>> Jerry
>> 







From owner-te-wg@ops.ietf.org  Wed May 21 09:27:54 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20554
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 09:27:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19ITZZ-000CUB-00
	for te-wg-data@psg.com; Wed, 21 May 2003 13:24:01 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19ITZR-000CTq-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 13:23:53 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4LDFYjM001106
	for <te-wg@ops.ietf.org>; Wed, 21 May 2003 09:23:52 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC7660200142CD5; Wed, 21 May 2003 09:23:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Wed, 21 May 2003 08:23:51 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67D0@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwg
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA20554

Hi Francois,

>> I suppose this relationship must hold:
>>
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc.
>>
>> LSOM: 'LSP/link size overbooking multiplier'
>>
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
 
> Yes, I do agree with your statement that "Reserved(CTc)" is also
> normalised in the sense that it reflects the LSP/link size 
> overbooking.
> 
> This is analogous to what happens today with regular TE. The bandwidth
> that is configured as the LSP size may reflect some over/underbooking
> factor. Similarly the Max Reservable bandwidth may reflect some
> over/underbooking ratio.
> The good thing is that from TE's perspective, the only thing we have to
> worry about are these "normalised" bandwidth (reflecting LSP/link size
> Overbooking).
> If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
> TE) whether the SP expects a peak load of 200 on that LSP and applied an
> LSP overbooking of 2, or whether the SP actually expects a peak load of
> 100 and applied no overbooking.
> Similarly, the relevant constraint is the Max Reservable Bandwidth
> (which can be configured smaller or larger than real link capacity). For
> TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
> doesn't really matter whether the link is actually indeed of 1000 or
> whether it is actually a link of 500 with an link overbooking of 2.
> Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
> link of 1000. That's it.
> This is why, in regular TE, only the LSP bandwidth is the one considered
> (and is indeed a normalised bandwidth factoring LSP Size Overbooking)
> and only Max Reservable is considered (which is also a normalised value
> factoring in the link size overbooking). 
> One interesting point is that TE does not explicitly need the concept
> of LSP size Overbooking *Multiplier" and the Link Size Overbooking
> *Multiplier". They are effectively transparent to TE which works only on
> normalised bandwidth. 
> 
> The DS-TE approach is the same with respect to LSP/link Size Overbooking
> ie the only "bandwidth" we are concerned about is the actual LSP size,
> which factors in the LSP Size Overbooking (ie which is normalised , as
> you stated) and the BCs [+ Max Reservable Bw (as proposed)].
> For DS-TE, like for TE, I think we don't need to explicitly define in
> the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
> nor formulas using them because we operate directly/exclusively on
> "normalised" values. But I think we  agree in spirit in what those would
> be anyway, based on our discussion.

Thank you for the good and clear explanation.

Then, to clarify further, the following relationship would seem to hold:

LSOM = Max Reservable Bandwidth/Max Link Bandwidth

Is that correct?

If so, then another way to write your proposed formula for the sum of reserved bandwidth would be:

  o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
      for all "c" in the range 0 <= c <= (MaxCT-1)

Is that right?

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Wed May 21 09:37:08 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20830
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 09:37:08 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19ITlg-000DaU-00
	for te-wg-data@psg.com; Wed, 21 May 2003 13:36:32 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19ITld-000DaI-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 13:36:29 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 09:32:54 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:36:47 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C5F189F615; Wed, 21 May 2003 09:22:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 3F7A39F605; Wed, 21 May 2003 09:22:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITZZ-000CUB-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:24:01 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19ITZR-000CTq-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:23:53 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4LDFYjM001106 for <te-wg@ops.ietf.org>; Wed, 21 May 2003 09:23:52 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC7660200142CD5; Wed, 21 May 2003 09:23:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Wed, 21 May 2003 08:23:51 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67D0@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwg
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 21 May 2003 13:36:47.0437 (UTC) FILETIME=[06B5AFD0:01C31F9E]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA20830

Hi Francois,

>> I suppose this relationship must hold:
>>
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc.
>>
>> LSOM: 'LSP/link size overbooking multiplier'
>>
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
 
> Yes, I do agree with your statement that "Reserved(CTc)" is also
> normalised in the sense that it reflects the LSP/link size 
> overbooking.
> 
> This is analogous to what happens today with regular TE. The bandwidth
> that is configured as the LSP size may reflect some over/underbooking
> factor. Similarly the Max Reservable bandwidth may reflect some
> over/underbooking ratio.
> The good thing is that from TE's perspective, the only thing we have to
> worry about are these "normalised" bandwidth (reflecting LSP/link size
> Overbooking).
> If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
> TE) whether the SP expects a peak load of 200 on that LSP and applied an
> LSP overbooking of 2, or whether the SP actually expects a peak load of
> 100 and applied no overbooking.
> Similarly, the relevant constraint is the Max Reservable Bandwidth
> (which can be configured smaller or larger than real link capacity). For
> TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
> doesn't really matter whether the link is actually indeed of 1000 or
> whether it is actually a link of 500 with an link overbooking of 2.
> Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
> link of 1000. That's it.
> This is why, in regular TE, only the LSP bandwidth is the one considered
> (and is indeed a normalised bandwidth factoring LSP Size Overbooking)
> and only Max Reservable is considered (which is also a normalised value
> factoring in the link size overbooking). 
> One interesting point is that TE does not explicitly need the concept
> of LSP size Overbooking *Multiplier" and the Link Size Overbooking
> *Multiplier". They are effectively transparent to TE which works only on
> normalised bandwidth. 
> 
> The DS-TE approach is the same with respect to LSP/link Size Overbooking
> ie the only "bandwidth" we are concerned about is the actual LSP size,
> which factors in the LSP Size Overbooking (ie which is normalised , as
> you stated) and the BCs [+ Max Reservable Bw (as proposed)].
> For DS-TE, like for TE, I think we don't need to explicitly define in
> the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
> nor formulas using them because we operate directly/exclusively on
> "normalised" values. But I think we  agree in spirit in what those would
> be anyway, based on our discussion.

Thank you for the good and clear explanation.

Then, to clarify further, the following relationship would seem to hold:

LSOM = Max Reservable Bandwidth/Max Link Bandwidth

Is that correct?

If so, then another way to write your proposed formula for the sum of reserved bandwidth would be:

  o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
      for all "c" in the range 0 <= c <= (MaxCT-1)

Is that right?

Thanks,
Jerry





From owner-te-wg@ops.ietf.org  Wed May 21 09:49:00 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21100
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 09:48:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19ITx9-000Egv-00
	for te-wg-data@psg.com; Wed, 21 May 2003 13:48:23 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19ITwl-000Ef6-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 13:47:59 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 21 May 2003 15:47:21 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4LDk0tp025238;
	Wed, 21 May 2003 15:46:01 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 15:47:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Wed, 21 May 2003 14:47:55 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5232@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwgAAE8rXA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>, "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
X-OriginalArrivalTime: 21 May 2003 13:47:55.0769 (UTC) FILETIME=[95110E90:01C31F9F]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA21100

Jerry,

See very far below: 

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 21 May 2003 15:24
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Hi Francois,
>> 
>> >> I suppose this relationship must hold:
>> >>
>> >> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> >> 
>> >> where
>> >> 
>> >> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> >> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> >> of the bandwidth requested by all established LSPs which 
>> >> belong to CTc.
>> >>
>> >> LSOM: 'LSP/link size overbooking multiplier'
>> >>
>> >> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> >> 'normalized' quantity, but this time it is normalized by the 
>> >> LSOM, right?
>>  
>> > Yes, I do agree with your statement that "Reserved(CTc)" is also
>> > normalised in the sense that it reflects the LSP/link size 
>> > overbooking.
>> > 
>> > This is analogous to what happens today with regular TE. 
>> The bandwidth
>> > that is configured as the LSP size may reflect some 
>> over/underbooking
>> > factor. Similarly the Max Reservable bandwidth may reflect some
>> > over/underbooking ratio.
>> > The good thing is that from TE's perspective, the only 
>> thing we have to
>> > worry about are these "normalised" bandwidth (reflecting 
>> LSP/link size
>> > Overbooking).
>> > If an LSP bandwidth is configured/signaled as 100, it is 
>> irrelevant (for
>> > TE) whether the SP expects a peak load of 200 on that LSP 
>> and applied an
>> > LSP overbooking of 2, or whether the SP actually expects a 
>> peak load of
>> > 100 and applied no overbooking.
>> > Similarly, the relevant constraint is the Max Reservable Bandwidth
>> > (which can be configured smaller or larger than real link 
>> capacity). For
>> > TE, what matters is that the Max Reservable Bw is set to, 
>> say, 1000. It
>> > doesn't really matter whether the link is actually indeed 
>> of 1000 or
>> > whether it is actually a link of 500 with an link overbooking of 2.
>> > Basically, TE will establish 10 LSPs of configured 
>> bandwidth 100 on that
>> > link of 1000. That's it.
>> > This is why, in regular TE, only the LSP bandwidth is the 
>> one considered
>> > (and is indeed a normalised bandwidth factoring LSP Size 
>> Overbooking)
>> > and only Max Reservable is considered (which is also a 
>> normalised value
>> > factoring in the link size overbooking). 
>> > One interesting point is that TE does not explicitly need 
>> the concept
>> > of LSP size Overbooking *Multiplier" and the Link Size Overbooking
>> > *Multiplier". They are effectively transparent to TE which 
>> works only on
>> > normalised bandwidth. 
>> > 
>> > The DS-TE approach is the same with respect to LSP/link 
>> Size Overbooking
>> > ie the only "bandwidth" we are concerned about is the 
>> actual LSP size,
>> > which factors in the LSP Size Overbooking (ie which is 
>> normalised , as
>> > you stated) and the BCs [+ Max Reservable Bw (as proposed)].
>> > For DS-TE, like for TE, I think we don't need to 
>> explicitly define in
>> > the drafts the concepts of LSP/Link Size overbooking 
>> Multipliers (LSOMs)
>> > nor formulas using them because we operate directly/exclusively on
>> > "normalised" values. But I think we  agree in spirit in 
>> what those would
>> > be anyway, based on our discussion.
>> 
>> Thank you for the good and clear explanation.
>> 
>> Then, to clarify further, the following relationship would 
>> seem to hold:
>> 
>> LSOM = Max Reservable Bandwidth/Max Link Bandwidth
>> 

In the "LSP/Link Size Overbooking" method one can apply overbooking by
tweaking the LSP size (lets' call this the "LSP Size Overbooking")
and/or by tweaking the Max Reservable Bw (lets' call this the "Link Size
Overbooking").

Assuming we define LSOM as the "Link Size Overbooking Multiplier" (as
opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with the above relationship.

Just to be clear, what I am trying to say is that the above relationship
you stated relates to the overbooking applied on the Link (but that the
overbooking applied on the LSP size is transparent to that because it is
already factored in the LSP size configured/signaled).

>> Is that correct?
>> 
>> If so, then another way to write your proposed formula for 
>> the sum of reserved bandwidth would be:
>> 
>>   o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
>>       for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that right?
>>

Again, assuming we define LSOM as the "Link Size Overbooking Multiplier"
(as opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with your relationship.

Thanks for helping get all this clarified.

Francois
 
>> Thanks,
>> Jerry
>> 



From owner-te-wg@ops.ietf.org  Wed May 21 09:52:20 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21210
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 09:52:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IU0r-000F6t-00
	for te-wg-data@psg.com; Wed, 21 May 2003 13:52:13 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IU0W-000F5e-01
	for te-wg@ops.ietf.org; Wed, 21 May 2003 13:51:52 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 09:48:17 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:52:10 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 8FCD19F116; Wed, 21 May 2003 09:39:44 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 241DD9F103; Wed, 21 May 2003 09:39:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITlg-000DaU-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:36:32 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19ITld-000DaI-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:36:29 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:32:54 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:36:47 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C5F189F615; Wed, 21 May 2003 09:22:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 3F7A39F605; Wed, 21 May 2003 09:22:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITZZ-000CUB-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:24:01 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19ITZR-000CTq-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:23:53 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4LDFYjM001106 for <te-wg@ops.ietf.org>; Wed, 21 May 2003 09:23:52 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC7660200142CD5; Wed, 21 May 2003 09:23:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Wed, 21 May 2003 08:23:51 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67D0@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwg
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 21 May 2003 13:36:47.0437 (UTC) FILETIME=[06B5AFD0:01C31F9E]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA21210

Hi Francois,

>> I suppose this relationship must hold:
>>
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc.
>>
>> LSOM: 'LSP/link size overbooking multiplier'
>>
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
 
> Yes, I do agree with your statement that "Reserved(CTc)" is also
> normalised in the sense that it reflects the LSP/link size 
> overbooking.
> 
> This is analogous to what happens today with regular TE. The bandwidth
> that is configured as the LSP size may reflect some over/underbooking
> factor. Similarly the Max Reservable bandwidth may reflect some
> over/underbooking ratio.
> The good thing is that from TE's perspective, the only thing we have to
> worry about are these "normalised" bandwidth (reflecting LSP/link size
> Overbooking).
> If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
> TE) whether the SP expects a peak load of 200 on that LSP and applied an
> LSP overbooking of 2, or whether the SP actually expects a peak load of
> 100 and applied no overbooking.
> Similarly, the relevant constraint is the Max Reservable Bandwidth
> (which can be configured smaller or larger than real link capacity). For
> TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
> doesn't really matter whether the link is actually indeed of 1000 or
> whether it is actually a link of 500 with an link overbooking of 2.
> Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
> link of 1000. That's it.
> This is why, in regular TE, only the LSP bandwidth is the one considered
> (and is indeed a normalised bandwidth factoring LSP Size Overbooking)
> and only Max Reservable is considered (which is also a normalised value
> factoring in the link size overbooking). 
> One interesting point is that TE does not explicitly need the concept
> of LSP size Overbooking *Multiplier" and the Link Size Overbooking
> *Multiplier". They are effectively transparent to TE which works only on
> normalised bandwidth. 
> 
> The DS-TE approach is the same with respect to LSP/link Size Overbooking
> ie the only "bandwidth" we are concerned about is the actual LSP size,
> which factors in the LSP Size Overbooking (ie which is normalised , as
> you stated) and the BCs [+ Max Reservable Bw (as proposed)].
> For DS-TE, like for TE, I think we don't need to explicitly define in
> the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
> nor formulas using them because we operate directly/exclusively on
> "normalised" values. But I think we  agree in spirit in what those would
> be anyway, based on our discussion.

Thank you for the good and clear explanation.

Then, to clarify further, the following relationship would seem to hold:

LSOM = Max Reservable Bandwidth/Max Link Bandwidth

Is that correct?

If so, then another way to write your proposed formula for the sum of reserved bandwidth would be:

  o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
      for all "c" in the range 0 <= c <= (MaxCT-1)

Is that right?

Thanks,
Jerry







From owner-te-wg@ops.ietf.org  Wed May 21 09:52:50 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21228
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 09:52:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IU0m-000F6a-00
	for te-wg-data@psg.com; Wed, 21 May 2003 13:52:08 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IU0W-000F5e-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 13:51:52 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 09:48:17 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:52:39 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 8549A9F103; Wed, 21 May 2003 09:39:44 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 241DD9F103; Wed, 21 May 2003 09:39:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITlg-000DaU-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:36:32 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19ITld-000DaI-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:36:29 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:32:54 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:36:47 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id C5F189F615; Wed, 21 May 2003 09:22:42 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id 3F7A39F605; Wed, 21 May 2003 09:22:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITZZ-000CUB-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:24:01 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com) by psg.com with esmtp (Exim 3.36 #1) id 19ITZR-000CTq-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:23:53 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12]) by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4LDFYjM001106 for <te-wg@ops.ietf.org>; Wed, 21 May 2003 09:23:52 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032) id 3EC7660200142CD5; Wed, 21 May 2003 09:23:52 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Date: Wed, 21 May 2003 08:23:51 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67D0@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwg
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
X-OriginalArrivalTime: 21 May 2003 13:36:47.0437 (UTC) FILETIME=[06B5AFD0:01C31F9E]
x-contentCatcher: ContentCatcher build 0407021738
Cc: "Ash, Gerald R , ALABS" <gash@att.com>, te-wg@ops.ietf.org,
        "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA21228

Hi Francois,

>> I suppose this relationship must hold:
>>
>> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> 
>> where
>> 
>> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> of the bandwidth requested by all established LSPs which 
>> belong to CTc.
>>
>> LSOM: 'LSP/link size overbooking multiplier'
>>
>> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> 'normalized' quantity, but this time it is normalized by the 
>> LSOM, right?
 
> Yes, I do agree with your statement that "Reserved(CTc)" is also
> normalised in the sense that it reflects the LSP/link size 
> overbooking.
> 
> This is analogous to what happens today with regular TE. The bandwidth
> that is configured as the LSP size may reflect some over/underbooking
> factor. Similarly the Max Reservable bandwidth may reflect some
> over/underbooking ratio.
> The good thing is that from TE's perspective, the only thing we have to
> worry about are these "normalised" bandwidth (reflecting LSP/link size
> Overbooking).
> If an LSP bandwidth is configured/signaled as 100, it is irrelevant (for
> TE) whether the SP expects a peak load of 200 on that LSP and applied an
> LSP overbooking of 2, or whether the SP actually expects a peak load of
> 100 and applied no overbooking.
> Similarly, the relevant constraint is the Max Reservable Bandwidth
> (which can be configured smaller or larger than real link capacity). For
> TE, what matters is that the Max Reservable Bw is set to, say, 1000. It
> doesn't really matter whether the link is actually indeed of 1000 or
> whether it is actually a link of 500 with an link overbooking of 2.
> Basically, TE will establish 10 LSPs of configured bandwidth 100 on that
> link of 1000. That's it.
> This is why, in regular TE, only the LSP bandwidth is the one considered
> (and is indeed a normalised bandwidth factoring LSP Size Overbooking)
> and only Max Reservable is considered (which is also a normalised value
> factoring in the link size overbooking). 
> One interesting point is that TE does not explicitly need the concept
> of LSP size Overbooking *Multiplier" and the Link Size Overbooking
> *Multiplier". They are effectively transparent to TE which works only on
> normalised bandwidth. 
> 
> The DS-TE approach is the same with respect to LSP/link Size Overbooking
> ie the only "bandwidth" we are concerned about is the actual LSP size,
> which factors in the LSP Size Overbooking (ie which is normalised , as
> you stated) and the BCs [+ Max Reservable Bw (as proposed)].
> For DS-TE, like for TE, I think we don't need to explicitly define in
> the drafts the concepts of LSP/Link Size overbooking Multipliers (LSOMs)
> nor formulas using them because we operate directly/exclusively on
> "normalised" values. But I think we  agree in spirit in what those would
> be anyway, based on our discussion.

Thank you for the good and clear explanation.

Then, to clarify further, the following relationship would seem to hold:

LSOM = Max Reservable Bandwidth/Max Link Bandwidth

Is that correct?

If so, then another way to write your proposed formula for the sum of reserved bandwidth would be:

  o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
      for all "c" in the range 0 <= c <= (MaxCT-1)

Is that right?

Thanks,
Jerry







From owner-te-wg@ops.ietf.org  Wed May 21 10:01:40 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21494
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 10:01:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IU9M-000G3F-00
	for te-wg-data@psg.com; Wed, 21 May 2003 14:01:00 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IU9J-000G32-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 14:00:57 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 09:57:23 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 10:01:45 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 130B29F112; Wed, 21 May 2003 09:48:49 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 5B88D9F112; Wed, 21 May 2003 09:48:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITx9-000Egv-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:48:23 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19ITwl-000Ef6-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:47:59 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 21 May 2003 15:47:21 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4LDk0tp025238; Wed, 21 May 2003 15:46:01 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 15:47:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Wed, 21 May 2003 14:47:55 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5232@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwgAAE8rXA=
X-OriginalArrivalTime: 21 May 2003 13:47:55.0769 (UTC) FILETIME=[95110E90:01C31F9F]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA21494

Jerry,

See very far below: 

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 21 May 2003 15:24
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Hi Francois,
>> 
>> >> I suppose this relationship must hold:
>> >>
>> >> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> >> 
>> >> where
>> >> 
>> >> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> >> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> >> of the bandwidth requested by all established LSPs which 
>> >> belong to CTc.
>> >>
>> >> LSOM: 'LSP/link size overbooking multiplier'
>> >>
>> >> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> >> 'normalized' quantity, but this time it is normalized by the 
>> >> LSOM, right?
>>  
>> > Yes, I do agree with your statement that "Reserved(CTc)" is also
>> > normalised in the sense that it reflects the LSP/link size 
>> > overbooking.
>> > 
>> > This is analogous to what happens today with regular TE. 
>> The bandwidth
>> > that is configured as the LSP size may reflect some 
>> over/underbooking
>> > factor. Similarly the Max Reservable bandwidth may reflect some
>> > over/underbooking ratio.
>> > The good thing is that from TE's perspective, the only 
>> thing we have to
>> > worry about are these "normalised" bandwidth (reflecting 
>> LSP/link size
>> > Overbooking).
>> > If an LSP bandwidth is configured/signaled as 100, it is 
>> irrelevant (for
>> > TE) whether the SP expects a peak load of 200 on that LSP 
>> and applied an
>> > LSP overbooking of 2, or whether the SP actually expects a 
>> peak load of
>> > 100 and applied no overbooking.
>> > Similarly, the relevant constraint is the Max Reservable Bandwidth
>> > (which can be configured smaller or larger than real link 
>> capacity). For
>> > TE, what matters is that the Max Reservable Bw is set to, 
>> say, 1000. It
>> > doesn't really matter whether the link is actually indeed 
>> of 1000 or
>> > whether it is actually a link of 500 with an link overbooking of 2.
>> > Basically, TE will establish 10 LSPs of configured 
>> bandwidth 100 on that
>> > link of 1000. That's it.
>> > This is why, in regular TE, only the LSP bandwidth is the 
>> one considered
>> > (and is indeed a normalised bandwidth factoring LSP Size 
>> Overbooking)
>> > and only Max Reservable is considered (which is also a 
>> normalised value
>> > factoring in the link size overbooking). 
>> > One interesting point is that TE does not explicitly need 
>> the concept
>> > of LSP size Overbooking *Multiplier" and the Link Size Overbooking
>> > *Multiplier". They are effectively transparent to TE which 
>> works only on
>> > normalised bandwidth. 
>> > 
>> > The DS-TE approach is the same with respect to LSP/link 
>> Size Overbooking
>> > ie the only "bandwidth" we are concerned about is the 
>> actual LSP size,
>> > which factors in the LSP Size Overbooking (ie which is 
>> normalised , as
>> > you stated) and the BCs [+ Max Reservable Bw (as proposed)].
>> > For DS-TE, like for TE, I think we don't need to 
>> explicitly define in
>> > the drafts the concepts of LSP/Link Size overbooking 
>> Multipliers (LSOMs)
>> > nor formulas using them because we operate directly/exclusively on
>> > "normalised" values. But I think we  agree in spirit in 
>> what those would
>> > be anyway, based on our discussion.
>> 
>> Thank you for the good and clear explanation.
>> 
>> Then, to clarify further, the following relationship would 
>> seem to hold:
>> 
>> LSOM = Max Reservable Bandwidth/Max Link Bandwidth
>> 

In the "LSP/Link Size Overbooking" method one can apply overbooking by
tweaking the LSP size (lets' call this the "LSP Size Overbooking")
and/or by tweaking the Max Reservable Bw (lets' call this the "Link Size
Overbooking").

Assuming we define LSOM as the "Link Size Overbooking Multiplier" (as
opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with the above relationship.

Just to be clear, what I am trying to say is that the above relationship
you stated relates to the overbooking applied on the Link (but that the
overbooking applied on the LSP size is transparent to that because it is
already factored in the LSP size configured/signaled).

>> Is that correct?
>> 
>> If so, then another way to write your proposed formula for 
>> the sum of reserved bandwidth would be:
>> 
>>   o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
>>       for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that right?
>>

Again, assuming we define LSOM as the "Link Size Overbooking Multiplier"
(as opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with your relationship.

Thanks for helping get all this clarified.

Francois
 
>> Thanks,
>> Jerry
>> 





From owner-te-wg@ops.ietf.org  Wed May 21 10:18:41 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23047
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 10:18:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IUPv-000HIn-00
	for te-wg-data@psg.com; Wed, 21 May 2003 14:18:07 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IUPs-000HIW-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 14:18:04 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 10:14:29 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 10:18:51 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 8D93B9F616; Wed, 21 May 2003 10:04:17 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id B7DCB9F612; Wed, 21 May 2003 10:04:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IU9M-000G3F-00 for te-wg-data@psg.com; Wed, 21 May 2003 14:01:00 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IU9J-000G32-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 14:00:57 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:57:23 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 10:01:45 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 130B29F112; Wed, 21 May 2003 09:48:49 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 5B88D9F112; Wed, 21 May 2003 09:48:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITx9-000Egv-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:48:23 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19ITwl-000Ef6-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:47:59 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 21 May 2003 15:47:21 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4LDk0tp025238; Wed, 21 May 2003 15:46:01 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 15:47:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Wed, 21 May 2003 14:47:55 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5232@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwgAAE8rXA=
X-OriginalArrivalTime: 21 May 2003 13:47:55.0769 (UTC) FILETIME=[95110E90:01C31F9F]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA23047

Jerry,

See very far below: 

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 21 May 2003 15:24
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Hi Francois,
>> 
>> >> I suppose this relationship must hold:
>> >>
>> >> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> >> 
>> >> where
>> >> 
>> >> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> >> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> >> of the bandwidth requested by all established LSPs which 
>> >> belong to CTc.
>> >>
>> >> LSOM: 'LSP/link size overbooking multiplier'
>> >>
>> >> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> >> 'normalized' quantity, but this time it is normalized by the 
>> >> LSOM, right?
>>  
>> > Yes, I do agree with your statement that "Reserved(CTc)" is also
>> > normalised in the sense that it reflects the LSP/link size 
>> > overbooking.
>> > 
>> > This is analogous to what happens today with regular TE. 
>> The bandwidth
>> > that is configured as the LSP size may reflect some 
>> over/underbooking
>> > factor. Similarly the Max Reservable bandwidth may reflect some
>> > over/underbooking ratio.
>> > The good thing is that from TE's perspective, the only 
>> thing we have to
>> > worry about are these "normalised" bandwidth (reflecting 
>> LSP/link size
>> > Overbooking).
>> > If an LSP bandwidth is configured/signaled as 100, it is 
>> irrelevant (for
>> > TE) whether the SP expects a peak load of 200 on that LSP 
>> and applied an
>> > LSP overbooking of 2, or whether the SP actually expects a 
>> peak load of
>> > 100 and applied no overbooking.
>> > Similarly, the relevant constraint is the Max Reservable Bandwidth
>> > (which can be configured smaller or larger than real link 
>> capacity). For
>> > TE, what matters is that the Max Reservable Bw is set to, 
>> say, 1000. It
>> > doesn't really matter whether the link is actually indeed 
>> of 1000 or
>> > whether it is actually a link of 500 with an link overbooking of 2.
>> > Basically, TE will establish 10 LSPs of configured 
>> bandwidth 100 on that
>> > link of 1000. That's it.
>> > This is why, in regular TE, only the LSP bandwidth is the 
>> one considered
>> > (and is indeed a normalised bandwidth factoring LSP Size 
>> Overbooking)
>> > and only Max Reservable is considered (which is also a 
>> normalised value
>> > factoring in the link size overbooking). 
>> > One interesting point is that TE does not explicitly need 
>> the concept
>> > of LSP size Overbooking *Multiplier" and the Link Size Overbooking
>> > *Multiplier". They are effectively transparent to TE which 
>> works only on
>> > normalised bandwidth. 
>> > 
>> > The DS-TE approach is the same with respect to LSP/link 
>> Size Overbooking
>> > ie the only "bandwidth" we are concerned about is the 
>> actual LSP size,
>> > which factors in the LSP Size Overbooking (ie which is 
>> normalised , as
>> > you stated) and the BCs [+ Max Reservable Bw (as proposed)].
>> > For DS-TE, like for TE, I think we don't need to 
>> explicitly define in
>> > the drafts the concepts of LSP/Link Size overbooking 
>> Multipliers (LSOMs)
>> > nor formulas using them because we operate directly/exclusively on
>> > "normalised" values. But I think we  agree in spirit in 
>> what those would
>> > be anyway, based on our discussion.
>> 
>> Thank you for the good and clear explanation.
>> 
>> Then, to clarify further, the following relationship would 
>> seem to hold:
>> 
>> LSOM = Max Reservable Bandwidth/Max Link Bandwidth
>> 

In the "LSP/Link Size Overbooking" method one can apply overbooking by
tweaking the LSP size (lets' call this the "LSP Size Overbooking")
and/or by tweaking the Max Reservable Bw (lets' call this the "Link Size
Overbooking").

Assuming we define LSOM as the "Link Size Overbooking Multiplier" (as
opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with the above relationship.

Just to be clear, what I am trying to say is that the above relationship
you stated relates to the overbooking applied on the Link (but that the
overbooking applied on the LSP size is transparent to that because it is
already factored in the LSP size configured/signaled).

>> Is that correct?
>> 
>> If so, then another way to write your proposed formula for 
>> the sum of reserved bandwidth would be:
>> 
>>   o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
>>       for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that right?
>>

Again, assuming we define LSOM as the "Link Size Overbooking Multiplier"
(as opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with your relationship.

Thanks for helping get all this clarified.

Francois
 
>> Thanks,
>> Jerry
>> 







From owner-te-wg@ops.ietf.org  Wed May 21 10:19:11 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23065
	for <tewg-archive@lists.ietf.org>; Wed, 21 May 2003 10:19:10 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IUQ4-000HJh-00
	for te-wg-data@psg.com; Wed, 21 May 2003 14:18:16 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IUPt-000HIg-00
	for te-wg@ops.ietf.org; Wed, 21 May 2003 14:18:05 +0000
Received: from CC1 ([192.168.200.2]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 21 May 2003 10:14:30 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf1.contentcatcher.com ([192.168.100.2]) by CC1 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 10:18:23 -0400
Received: by pf1.contentcatcher.com (Postfix, from userid 502) id 79DE29F612; Wed, 21 May 2003 10:04:18 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf1.contentcatcher.com (Postfix) with ESMTP id B7DCB9F612; Wed, 21 May 2003 10:04:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19IU9M-000G3F-00 for te-wg-data@psg.com; Wed, 21 May 2003 14:01:00 +0000
Received: from [64.19.188.18] (helo=db1.contentcatcher.com) by psg.com with esmtp (Exim 3.36 #1) id 19IU9J-000G32-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 14:00:57 +0000
Received: from CC2 ([192.168.200.3]) by db1.contentcatcher.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 09:57:23 -0400
x-sender: owner-te-wg@ops.ietf.org
x-receiver: spamtrap@spam.clearnetwork.com
Received: from pf2.contentcatcher.com ([192.168.100.3]) by CC2 with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 10:01:45 -0400
Received: by pf2.contentcatcher.com (Postfix, from userid 500) id 130B29F112; Wed, 21 May 2003 09:48:49 -0400 (EDT)
Received: from psg.com (psg.com [147.28.0.62]) by pf2.contentcatcher.com (Postfix) with ESMTP id 5B88D9F112; Wed, 21 May 2003 09:48:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1) id 19ITx9-000Egv-00 for te-wg-data@psg.com; Wed, 21 May 2003 13:48:23 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5]) by psg.com with esmtp (Exim 3.36 #1) id 19ITwl-000Ef6-00 for te-wg@ops.ietf.org; Wed, 21 May 2003 13:47:59 +0000
Received: from cisco.com (144.254.74.60) by ams-iport-1.cisco.com with ESMTP; 21 May 2003 15:47:21 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1]) by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4LDk0tp025238; Wed, 21 May 2003 15:46:01 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 21 May 2003 15:47:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="us-ascii"
Date: Wed, 21 May 2003 14:47:55 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5232@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMe4Do0MmHWvSS/TkixXhP4Np5hdQAAt7jQAA0kEtAAFpOU0AAJ0cwgAAE8rXA=
X-OriginalArrivalTime: 21 May 2003 13:47:55.0769 (UTC) FILETIME=[95110E90:01C31F9F]
X-VIRUS-FOUND: NO
X-GHOST-SENDER: owner-te-wg@ops.ietf.org
X-GHOST-RECEIVER: braja@tellium.com
x-contentCatcher: ContentCatcher build 0407021738
Cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
To: braja@tellium.com
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA23065

Jerry,

See very far below: 

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 21 May 2003 15:24
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> Wai S (Waisum), ALABS; Dimitry Haskin
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> 
>> 
>> Hi Francois,
>> 
>> >> I suppose this relationship must hold:
>> >>
>> >> Reserved(CTc) = Bandwidth-Requested(CTc)/LSOM
>> >> 
>> >> where
>> >> 
>> >> Bandwidth-Requested(CTc): For a given Class-Type CTc ( 0 <= 
>> >> c <= MaxCT ), define "Bandwidth-Requested(CTc)" as the sum 
>> >> of the bandwidth requested by all established LSPs which 
>> >> belong to CTc.
>> >>
>> >> LSOM: 'LSP/link size overbooking multiplier'
>> >>
>> >> Is that correct?  If so, then 'Reserved(CTc)' is also a 
>> >> 'normalized' quantity, but this time it is normalized by the 
>> >> LSOM, right?
>>  
>> > Yes, I do agree with your statement that "Reserved(CTc)" is also
>> > normalised in the sense that it reflects the LSP/link size 
>> > overbooking.
>> > 
>> > This is analogous to what happens today with regular TE. 
>> The bandwidth
>> > that is configured as the LSP size may reflect some 
>> over/underbooking
>> > factor. Similarly the Max Reservable bandwidth may reflect some
>> > over/underbooking ratio.
>> > The good thing is that from TE's perspective, the only 
>> thing we have to
>> > worry about are these "normalised" bandwidth (reflecting 
>> LSP/link size
>> > Overbooking).
>> > If an LSP bandwidth is configured/signaled as 100, it is 
>> irrelevant (for
>> > TE) whether the SP expects a peak load of 200 on that LSP 
>> and applied an
>> > LSP overbooking of 2, or whether the SP actually expects a 
>> peak load of
>> > 100 and applied no overbooking.
>> > Similarly, the relevant constraint is the Max Reservable Bandwidth
>> > (which can be configured smaller or larger than real link 
>> capacity). For
>> > TE, what matters is that the Max Reservable Bw is set to, 
>> say, 1000. It
>> > doesn't really matter whether the link is actually indeed 
>> of 1000 or
>> > whether it is actually a link of 500 with an link overbooking of 2.
>> > Basically, TE will establish 10 LSPs of configured 
>> bandwidth 100 on that
>> > link of 1000. That's it.
>> > This is why, in regular TE, only the LSP bandwidth is the 
>> one considered
>> > (and is indeed a normalised bandwidth factoring LSP Size 
>> Overbooking)
>> > and only Max Reservable is considered (which is also a 
>> normalised value
>> > factoring in the link size overbooking). 
>> > One interesting point is that TE does not explicitly need 
>> the concept
>> > of LSP size Overbooking *Multiplier" and the Link Size Overbooking
>> > *Multiplier". They are effectively transparent to TE which 
>> works only on
>> > normalised bandwidth. 
>> > 
>> > The DS-TE approach is the same with respect to LSP/link 
>> Size Overbooking
>> > ie the only "bandwidth" we are concerned about is the 
>> actual LSP size,
>> > which factors in the LSP Size Overbooking (ie which is 
>> normalised , as
>> > you stated) and the BCs [+ Max Reservable Bw (as proposed)].
>> > For DS-TE, like for TE, I think we don't need to 
>> explicitly define in
>> > the drafts the concepts of LSP/Link Size overbooking 
>> Multipliers (LSOMs)
>> > nor formulas using them because we operate directly/exclusively on
>> > "normalised" values. But I think we  agree in spirit in 
>> what those would
>> > be anyway, based on our discussion.
>> 
>> Thank you for the good and clear explanation.
>> 
>> Then, to clarify further, the following relationship would 
>> seem to hold:
>> 
>> LSOM = Max Reservable Bandwidth/Max Link Bandwidth
>> 

In the "LSP/Link Size Overbooking" method one can apply overbooking by
tweaking the LSP size (lets' call this the "LSP Size Overbooking")
and/or by tweaking the Max Reservable Bw (lets' call this the "Link Size
Overbooking").

Assuming we define LSOM as the "Link Size Overbooking Multiplier" (as
opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with the above relationship.

Just to be clear, what I am trying to say is that the above relationship
you stated relates to the overbooking applied on the Link (but that the
overbooking applied on the LSP size is transparent to that because it is
already factored in the LSP size configured/signaled).

>> Is that correct?
>> 
>> If so, then another way to write your proposed formula for 
>> the sum of reserved bandwidth would be:
>> 
>>   o SUM (Normalized(CTc)) <= Max Link Bandwidth X LSOM
>>       for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> Is that right?
>>

Again, assuming we define LSOM as the "Link Size Overbooking Multiplier"
(as opposed to the "LSP/Link Size Overbooking Multiplier"), then I agree
with your relationship.

Thanks for helping get all this clarified.

Francois
 
>> Thanks,
>> Jerry
>> 







From owner-te-wg@ops.ietf.org  Thu May 22 09:38:32 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13501
	for <tewg-archive@lists.ietf.org>; Thu, 22 May 2003 09:38:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19IqAy-000JFA-00
	for te-wg-data@psg.com; Thu, 22 May 2003 13:32:08 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19IqAS-000JCO-00
	for te-wg@ops.ietf.org; Thu, 22 May 2003 13:31:36 +0000
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA00857
	for <te-wg@ops.ietf.org>; Thu, 22 May 2003 09:31:33 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id JAA27992
	for <te-wg@ops.ietf.org>; Thu, 22 May 2003 09:31:34 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L241A6XV>; Thu, 22 May 2003 09:30:09 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F5498@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te
	-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [own
	er-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
Date: Thu, 22 May 2003 09:30:08 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-10.4 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> 
> Again, assuming we define LSOM as the "Link Size Overbooking 
> Multiplier"
> (as opposed to the "LSP/Link Size Overbooking Multiplier"), 
> then I agree
> with your relationship.
> 
> Thanks for helping get all this clarified.
> 
> Francois

Hi! I am not sure it is necessary to introduce the concept 
of a new multiplier ("LSOM") in DSTE-PROTO. 

Only change that should probably goto the draft is to replace
"Max Link Bw" in formulas by "Max reservable Bw", when user  
overrides the maxLinkBw (with a max reservable bw).

Here is how I understand the types of overbookings:-
1. Link size  overbooking
	-user overrides the 'max link bw' (dictated by 
	the hardware), with a larger/smaller bandwidth 
	reservable on the link, be by configuring a 
	'max reservable bw'.
	-no additional multipliers are needed 
2. LSP size overbooking
	-user reserves more/less amount of BW for the LSP
	compared to the actual amount of traffic the LSP
	is expected to carry.
	-No additional 'multipliers' are needed. The LSP
	BW follows the normal BCs based on the CTs
3. per CT overbooking
	-user specifies the LOM on a per CT per interface
	basis. LSP BW adheres to BCs dictated by the CT it
	is associated with
	-when user has overridden the 'max link bw' by 
	configuring a explicit 'max reservable bw', the 
	user specified value should be used as the upper
	limit for the link.

Reserved(CTx) vs Normalized(CTx):
If no LOM is being used, we can assume the LOM to be
1 (100% no over/underbooking). This will allows us
to use Normalized(CTx) in all the formulas (instead
of two sets -one with Reserved and the other with 
Normalized).

Thanks,
sanjay


 	



From owner-te-wg@ops.ietf.org  Thu May 22 10:29:48 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16244
	for <tewg-archive@lists.ietf.org>; Thu, 22 May 2003 10:29:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Ir3h-0005pa-00
	for te-wg-data@psg.com; Thu, 22 May 2003 14:28:41 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Ir3A-0005nx-00
	for te-wg@ops.ietf.org; Thu, 22 May 2003 14:28:09 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 22 May 2003 16:27:30 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4MEQ8ml020696;
	Thu, 22 May 2003 16:26:11 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Thu, 22 May 2003 16:27:57 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
Date: Thu, 22 May 2003 15:27:56 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5235@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in Pass-Through List] ['from' in Pass-Through List]
Thread-Index: AcMgZ4kjDu/Y+DaISo+tOthQikZnhgAA9YBg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 22 May 2003 14:27:57.0267 (UTC) FILETIME=[56E25230:01C3206E]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA16244

Hello Sanjaya,

>> -----Original Message-----
>> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@marconi.com] 
>> Sent: 22 May 2003 15:30
>> To: te-wg@ops.ietf.org
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te 
>> drafts [owner-te-wg@ops.ietf.org in Pass-Through List] 
>> ['from' in Pass-Through List] [owner-te-wg@ops.ietf.org in 
>> Pass-Through List] ['from' in Pass-Through List]
>> 
>> 
>> > 
>> > Again, assuming we define LSOM as the "Link Size Overbooking 
>> > Multiplier"
>> > (as opposed to the "LSP/Link Size Overbooking Multiplier"), 
>> > then I agree
>> > with your relationship.
>> > 
>> > Thanks for helping get all this clarified.
>> > 
>> > Francois
>> 
>> Hi! I am not sure it is necessary to introduce the concept 
>> of a new multiplier ("LSOM") in DSTE-PROTO. 
>>

Oh. I couldn't agree more. 

This is what I tried to indicate also in my earlier message:
[FLF] For DS-TE, like for TE, I think we don't need to explicitely 
[FLF] define in
[FLF] the drafts the concepts of LSP/Link Size overbooking 
[FLF] Multipliers (LSOMs)
[FLF] nor formulas using them because we operate directly/exclusively on
[FLF] "normalised" values.  

We only defined LSOM fo the purpose of the email discussion to
facilitate the discussions and confirmed we were all in synch in terms
of overbooking model. But I don't propose to add the LSOM
concept/formulas into the drafts.
 
>> Only change that should probably goto the draft is to replace
>> "Max Link Bw" in formulas by "Max reservable Bw", when user  
>> overrides the maxLinkBw (with a max reservable bw).
>> 

Right. "Max Reservable Bw" will be the value used as the aggregate
constraint on all CTs. 

>> Here is how I understand the types of overbookings:-
>> 1. Link size  overbooking
>> 	-user overrides the 'max link bw' (dictated by 
>> 	the hardware), with a larger/smaller bandwidth 
>> 	reservable on the link, be by configuring a 
>> 	'max reservable bw'.

Yes.
Minor detail. I am not sure what you meant exactly by "override". The
way I would put it is that we always use the Max Reservable bw (which
may be set by default to the actual Link Bandwidth or may be configured
by operator to some larger/smaller value). I think we agree.

>> 	-no additional multipliers are needed 

Yep.

>> 2. LSP size overbooking
>> 	-user reserves more/less amount of BW for the LSP
>> 	compared to the actual amount of traffic the LSP
>> 	is expected to carry.
>> 	-No additional 'multipliers' are needed. The LSP
>> 	BW follows the normal BCs based on the CTs

Yep.

>> 3. per CT overbooking
>> 	-user specifies the LOM on a per CT per interface
>> 	basis. LSP BW adheres to BCs dictated by the CT it
>> 	is associated with 

Yes. Factoring in the LOM, of course.

Good summary of overbooking methods. Thanks.

>> 	-when user has overridden the 'max link bw' by 
>> 	configuring a explicit 'max reservable bw', the 
>> 	user specified value should be used as the upper
>> 	limit for the link.
>> 
>> Reserved(CTx) vs Normalized(CTx):
>> If no LOM is being used, we can assume the LOM to be
>> 1 (100% no over/underbooking). This will allows us
>> to use Normalized(CTx) in all the formulas (instead
>> of two sets -one with Reserved and the other with 
>> Normalized).
>> 

The drafts already state that when LOM are not used it means they are
set to 1.
I had put the two sets of formulas with/without LOM because LOM is
purely an optional mechanism [ and frankly I don't expect it to be used
that often considering how much you can achieve with Link overbooking
and LSP overbooking] so I thought it would be useful to state the
formulas without LOM . 
Note that while the CAC formulas are pretty much the same with/without
LOM (with simple substitution of "reserved" by "normalised") the
formulas for computing Unreserved BW do get less intuitive with LOM than
without.

Thanks for your comments and analysis.

Francois

>> Thanks,
>> sanjay
>> 
>> 
>>  	
>> 
>> 



From owner-te-wg@ops.ietf.org  Fri May 23 11:30:02 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09691
	for <tewg-archive@lists.ietf.org>; Fri, 23 May 2003 11:30:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19JEEt-0006ne-00
	for te-wg-data@psg.com; Fri, 23 May 2003 15:13:47 +0000
Received: from sj-core-2.cisco.com ([171.71.177.254])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19JEEr-0006nS-00
	for te-wg@ops.ietf.org; Fri, 23 May 2003 15:13:45 +0000
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h4NFDh9N001810
	for <te-wg@ops.ietf.org>; Fri, 23 May 2003 08:13:43 -0700 (PDT)
Received: from dhcp-171-71-139-23.cisco.com (dhcp-171-71-139-23.cisco.com [171.71.139.23]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA08043 for <te-wg@ops.ietf.org>; Fri, 23 May 2003 08:13:42 -0700 (PDT)
Date: Fri, 23 May 2003 08:13:53 -0700
From: Ed Kern <ejk@tech.org>
To: te-wg@ops.ietf.org
Subject: agenda items for vienna?
Message-ID: <2147483647.1053677633@dhcp-171-71-139-23.cisco.com>
X-Mailer: Mulberry/3.0.3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, hits=-5.8 required=5.0
	tests=BAYES_10
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Due to various vacations we need to close on the agenda for vienna in the 
next week or so.

Please submit any work items with a suggested speaker and time estimate 
directly to jim and myself by next Friday the 30th of May.



thanks,

Ed



From owner-te-wg@ops.ietf.org  Fri May 23 13:23:32 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15153
	for <tewg-archive@lists.ietf.org>; Fri, 23 May 2003 13:23:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19JGED-000Cgy-00
	for te-wg-data@psg.com; Fri, 23 May 2003 17:21:13 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19JGEA-000Cgi-00
	for te-wg@ops.ietf.org; Fri, 23 May 2003 17:21:10 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F647@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>,
        te-wg@ops.ietf.org
Subject: RE: Reflecting new-MAM/SAM definition in diff-te draftsh
Date: Fri, 23 May 2003 13:20:59 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-6.3 required=5.0
	tests=BAYES_20,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Francois and all,

 
> The drafts already state that when LOM are not used it means they are
> set to 1.
> I had put the two sets of formulas with/without LOM because LOM is
> purely an optional mechanism [ and frankly I don't expect it 
> to be used
> that often considering how much you can achieve with Link overbooking
> and LSP overbooking] so I thought it would be useful to state the
> formulas without LOM . 
> Note that while the CAC formulas are pretty much the same with/without
> LOM (with simple substitution of "reserved" by "normalised") the
> formulas for computing Unreserved BW do get less intuitive 
> with LOM than
> without.
> 

I agree that there is not much practical use for LOM, if any. Can someone
define the real need for it? If not, wouldn't it be beneficial to remove it
from the current -proto spec? IMO, it would make spec less confusing and
easier to conceptualize. If someone ever finds a real rather than
theoretical need for LOM, it always can be handled as an extension in a
different spec. I think making the base spec as simple as possible by
removing concepts that presently don't appear to have any practical value is
of a great importance.

Regards,
  Dimitry



From owner-te-wg@ops.ietf.org  Fri May 23 15:00:16 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20162
	for <tewg-archive@lists.ietf.org>; Fri, 23 May 2003 15:00:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19JHjq-000JeX-00
	for te-wg-data@psg.com; Fri, 23 May 2003 18:57:58 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19JHjk-000JeK-00
	for te-wg@ops.ietf.org; Fri, 23 May 2003 18:57:53 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4NHQPAh019173
	for <te-wg@ops.ietf.org>; Fri, 23 May 2003 13:57:52 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC7660200210F04; Fri, 23 May 2003 14:57:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Fri, 23 May 2003 13:57:51 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137090@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+QAGnzyQA=
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Spam-Status: No, hits=-9.0 required=5.0
	tests=BAYES_10,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA20162

Thanks to the responses from Jean-Louis, Dimitry, and Francois
regarding the issue on the use of max link bw versus max
reservable bw in my previous mesage (contained here at the end).

The main point underlying the issue that has so far not been
discussed is this, because of per-CT overbooking, max reservable
bw should be treated as a vector quantity (as in my previous
dollar/euro analogy).  Let me illustrate by an example.

Max link bw = 100 (assuming some bw unit)
CT1: bw constraint = 80, LSP bw = 10
CT2: bw constraint = 70, LSP bw =  7

In this setting (with all the quantities above being normalized
with respect to link bw), we can accommodate under MAM any one
of these combinations:
8 CT1-LSPs + 2 CT2-LSPs = 94, 7 CT1-LSPs + 4 CT2-LSPs = 98,
6 CT1-LSPs + 5 CT2-LSPs = 95, 5 CT1-LSPs + 7 CT2-LSPs = 99,
4 CT1-LSPs + 8 CT2-LSPs = 96, 3 CT1-LSPs + 10 CT2-LSPs = 100.
The aggregate link bw's are all within the max link bw of 100.

Now consider the usage of reservable bw:
CT1: overbooking = 2, LSP reserved bw = 2 x 10 = 20
CT2: overbooking = 4, LSP reserved bw = 4 x  7 = 28

The corresponding max reservable bw's would be:
8 CT1-LSPs + 2 CT2-LSPs = 216
7 CT1-LSPs + 4 CT2-LSPs = 252
6 CT1-LSPs + 5 CT2-LSPs = 260
5 CT1-LSPs + 7 CT2-LSPs = 296
4 CT1-LSPs + 8 CT2-LSPs = 304
3 CT1-LSPs + 10 CT2-LSPs = 340

In contrast with max link bw, it's not clear what criterion
should be used to pick *a single value* from the above list
and use it as the "aggregate" max reservable bw.  While MAM
is being used here for illustration, this problem is generic
and affects RDM as well.

As pointed out in my previous message, in current TE for
aggregate traffic, it is possible to define a single
"aggregate" max reservable bw value, since an average-overall
can be assumed.  Once different overbooking factors are used
for different traffic components (e.g., CT's), this is no longer
the case, and each traffic component has its own max reservable
bw.  That's what I mean by treating max reservable bw as a vector
quantity with distinct components.  This fact is actually also
independent of the type of overbooking methods used, i.e., LOM
or not LOM.

Thus, the proper way to do the computation is to first convert
reservable bw to link bw (or some equivalent normalized quantity),
and then check against the max link bw (or some equivalent
normalized quantity).  Checking against the "aggregate" max
reservable bw is problematic since it is a list and not a single
value, as shown above.

Regarding the limit of bandwidth for a single LSP, that's already
taken care of by the per-CT bw constraint (since it is assumed
to be normalized).  If folks want to use the max link bw for this
purpose, it's not precluded by the above consideration either
(because if the max link bw puts a contraint on the aggregate
traffic, it certainly puts a contraint on a single LSP).

Thanks, Wai Sum

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Tuesday, May 20, 2003 11:52 AM
To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: RE: link capacity and reservable


Dimitry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:45
>> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, 
>> Gerald R (Jerry), ALABS
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Waisum, Jerry,
>> 
>> IMO, both yours and Francois' formulas for the aggregate reservation
>> constrain would achieve identical results. 

I guess you're right that at the end of the day it would be pretty much
the same thing functionnally.

>>Note that max 
>> reservable b/w
>> constraint is simply applied to the sum of reservations at 
>> each CT which
>> already account for individual overbooking factors at each 
>> CT. However with
>> the formula that you are proposing we would completely shut 
>> the door for
>> other uses of the max link b/w TLV, for instance as a 
>> constraint on the max
>> LSP b/w. Since we have already a parameter that was 
>> explicitly defined as
>> the aggregate reservation constrain, there is no need to 
>> close door for a
>> different use of the max link b/w parameter at this point.
>> 

Agreed.

Thanks

FRancois

>> Regards,
>>   Dimitry  
>> 
>> > -----Original Message-----
>> > From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
>> > Sent: Monday, May 19, 2003 4:47 PM
>> > To: te-wg@ops.ietf.org
>> > Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, Gerald R
>> > (Jerry), ALABS
>> > Subject: link capacity and reservable
>> > 
>> > 
>> > This is in response to the discussion of maximum reservable
>> > bandwidth in
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
>> > As the issue is not restricted solely to MAM, and has impact on
>> > RDM and in fact all BC models, I am talking about it in a more
>> > general context.
>> > 
>> > Current TE extension in IGP deals with aggregate traffic.
>> > There is thus a simple average-overall relationship:
>> > max link bandwidth = max reservable bandwidth/overbooking.
>> > As a result, whether "max link bandwidth" is supported or
>> > commonly used or not is immaterial.
>> > 
>> > In DS-TE, there is per-CT bandwidth contstraint and per-CT
>> > overbooking.  Max reservable bandwidth should accordingly be
>> > treated as a vector quantity.  Reflecting this view, the
>> > following definition for MAM in <tewg-diff-te-reqts> is
>> > adequate:
>> >   for each value of b in the range 0 <= b <= 7:
>> >     Reserved (CTb) <= BCb
>> > (with some clarification in MAM spec regarding overbooking)
>> > 
>> > Also, the following additional condition for MAM definition as
>> > proposed in the second message quoted above is both unneccsary
>> > and incorrect:
>> >   SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > This is like when I have 15 dollars and 10 euros in my pocket,
>> > then my max reserve is 25 (of what unit).
>> > 
>> > The "max link bandwidth," being a normalized quantity, is more
>> > meaningful.  For admission control under MAM, in addition to
>> > the observing the bandwidth constraints as specified in the
>> > above deinition, something like the following may be used:
>> >   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> > (with some tweaks to account for priorities)
>> > 
>> > Thanks, Wai Sum
>> > 
>> 



From owner-te-wg@ops.ietf.org  Fri May 23 20:34:42 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA01639
	for <tewg-archive@lists.ietf.org>; Fri, 23 May 2003 20:34:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19JMwf-0009Qu-00
	for te-wg-data@psg.com; Sat, 24 May 2003 00:31:33 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19JMwY-0009QG-00
	for te-wg@ops.ietf.org; Sat, 24 May 2003 00:31:26 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h4O0VFfQ011881;
	Fri, 23 May 2003 20:31:15 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h4O0VDoc011877;
	Fri, 23 May 2003 20:31:14 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Fri, 23 May 2003 20:31:13 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
cc: te-wg@ops.ietf.org, "Lai, Wai S , ALABS" <wlai@att.com>
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 
In-Reply-To: <AC60B39EEE7320498063D37799FB82D93B9584@xbe-lon-313.cisco.com>
Message-ID: <Pine.LNX.4.44.0305232028380.20376-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-33.1 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REPLY_WITH_QUOTES,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


So is there agreement now?

If so, what's the fallout?

I don't want to pull the reqt's out of IESG, and as stated in the list, it 
isnt the place MAM is defined (sorry SAM, I think we have enough bandwidth 
models).

Francois, can you re-propose changes for proto, RDM and MAM?

thanks,

Jim

btw... I also think LOMs are lots of complexity for little gain :)



On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:

> Jerry,
> 
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> >> Sent: 20 May 2003 17:35
> >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
> >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
> >> Wai S (Waisum), ALABS
> >> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
> >> 
> >> 
> >> Dimitry, Francois,
> >> 
> >> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
> >> > > 
> >> > > However, this formula is incorrect for DS-TE when per-CT 
> >> > > LOM's are used, since the above formula only reflects the Max 
> >> > > Reservable Bandwidth for the entire link, and does not 
> >> > > reflect the per-CT local overbooking factors.  So what 
> >> > > formula do you suggest when per-CT LOM's are used?
> >> 
> >> > Wouldn't 'Reserved (CTc)' it the above formula already 
> >> accounts for the
> >> > overbooking multiplier at CTc?  I don't see how this 
> >> formula precludes
> >> > per-CT LOM's to be used. Please explain.
> >> 
> >> Are you then proposing these formulas:
> >> 
> >> 1. When per-CT LOMs are not used:
> >> 
> >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
> >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> 
> >> 2. When per-CT LOMs are used:
> >> 
> >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
> >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> 
> >> Is that correct?  Please confirm, and/or give the formulas 
> >> you propose.
> 
> Yes, this is exactly what I propose.
> I think this is similar to what you were proposing, only using "Max Res
> Bw" instead of "Max Link Bw". 
> 
> Sorry I didn't make that very clear before.
> 
> Cheers
> 
> FRancois
> 
> >> 
> >> Thanks,
> >> Jerry
> >> 
> 
> 
> 
> 




From owner-te-wg@ops.ietf.org  Sun May 25 04:06:39 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26101
	for <tewg-archive@lists.ietf.org>; Sun, 25 May 2003 04:06:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19JqNy-000Ezm-00
	for te-wg-data@psg.com; Sun, 25 May 2003 07:57:42 +0000
Received: from web15214.mail.bjs.yahoo.com ([202.3.77.144])
	by psg.com with smtp (Exim 3.36 #1)
	id 19JqNs-000EzT-00
	for te-wg@ops.ietf.org; Sun, 25 May 2003 07:57:36 +0000
Message-ID: <20030525075732.35244.qmail@web15214.mail.bjs.yahoo.com>
Received: from [218.72.38.168] by web15214.mail.bjs.yahoo.com via HTTP; Sun, 25 May 2003 15:57:32 CST
Date: Sun, 25 May 2003 15:57:32 +0800 (CST)
From: =?gb2312?q?Jing=20Shen?= <jshen_cad@yahoo.com.cn>
Subject: RE: link capacity and reservable
To: "Lai, Wai S \(Waisum\), ALABS" <wlai@att.com>, te-wg@ops.ietf.org
Cc: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>,
        Dimitry Haskin <dhaskin@axiowave.com>,
        "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA137090@KCCLUST06EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-871062811-1053849452=:34996"
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, hits=-11.2 required=5.0
	tests=BAYES_10,HTML_10_20,IN_REP_TO,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--0-871062811-1053849452=:34996
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit

My question, if parameters in a new LSP setup request are converted as Lai stated, how could we select best path for new traffic flows?
 
for example, 
       /-----------b \
s----/                \--------t
    a \              /d
        \---------c/
 
 
S want to set up LSP of CT1  to T with bandwidth 5Mbps, while at node A there is tow branch ( to B or to C),  if link AC allow more overbooking than AB, but residual BW for CT1 is the same. 
 
Which path should we take ?  or should OSPF  use which value ( real BW or reservable BW) ? 
 
thanks 
 
Jing Shen
 
 
 

"Lai, Wai S (Waisum), ALABS" <wlai@att.com> wrote:
Thanks to the responses from Jean-Louis, Dimitry, and Francois
regarding the issue on the use of max link bw versus max
reservable bw in my previous mesage (contained here at the end).

The main point underlying the issue that has so far not been
discussed is this, because of per-CT overbooking, max reservable
bw should be treated as a vector quantity (as in my previous
dollar/euro analogy). Let me illustrate by an example.

Max link bw = 100 (assuming some bw unit)
CT1: bw constraint = 80, LSP bw = 10
CT2: bw constraint = 70, LSP bw = 7

In this setting (with all the quantities above being normalized
with respect to link bw), we can accommodate under MAM any one
of these combinations:
8 CT1-LSPs + 2 CT2-LSPs = 94, 7 CT1-LSPs + 4 CT2-LSPs = 98,
6 CT1-LSPs + 5 CT2-LSPs = 95, 5 CT1-LSPs + 7 CT2-LSPs = 99,
4 CT1-LSPs + 8 CT2-LSPs = 96, 3 CT1-LSPs + 10 CT2-LSPs = 100.
The aggregate link bw's are all within the max link bw of 100.

Now consider the usage of reservable bw:
CT1: overbooking = 2, LSP reserved bw = 2 x 10 = 20
CT2: overbooking = 4, LSP reserved bw = 4 x 7 = 28

The corresponding max reservable bw's would be:
8 CT1-LSPs + 2 CT2-LSPs = 216
7 CT1-LSPs + 4 CT2-LSPs = 252
6 CT1-LSPs + 5 CT2-LSPs = 260
5 CT1-LSPs + 7 CT2-LSPs = 296
4 CT1-LSPs + 8 CT2-LSPs = 304
3 CT1-LSPs + 10 CT2-LSPs = 340

In contrast with max link bw, it's not clear what criterion
should be used to pick *a single value* from the above list
and use it as the "aggregate" max reservable bw. While MAM
is being used here for illustration, this problem is generic
and affects RDM as well.

As pointed out in my previous message, in current TE for
aggregate traffic, it is possible to define a single
"aggregate" max reservable bw value, since an average-overall
can be assumed. Once different overbooking factors are used
for different traffic components (e.g., CT's), this is no longer
the case, and each traffic component has its own max reservable
bw. That's what I mean by treating max reservable bw as a vector
quantity with distinct components. This fact is actually also
independent of the type of overbooking methods used, i.e., LOM
or not LOM.

Thus, the proper way to do the computation is to first convert
reservable bw to link bw (or some equivalent normalized quantity),
and then check against the max link bw (or some equivalent
normalized quantity). Checking against the "aggregate" max
reservable bw is problematic since it is a list and not a single
value, as shown above.

Regarding the limit of bandwidth for a single LSP, that's already
taken care of by the per-CT bw constraint (since it is assumed
to be normalized). If folks want to use the max link bw for this
purpose, it's not precluded by the above consideration either
(because if the max link bw puts a contraint on the aggregate
traffic, it certainly puts a contraint on a single LSP).

Thanks, Wai Sum

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Tuesday, May 20, 2003 11:52 AM
To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: RE: link capacity and reservable


Dimitry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:45
>> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, 
>> Gerald R (Jerry), ALABS
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Waisum, Jerry,
>> 
>> IMO, both yours and Francois' formulas for the aggregate reservation
>> constrain would achieve identical results. 

I guess you're right that at the end of the day it would be pretty much
the same thing functionnally.

>>Note that max 
>> reservable b/w
>> constraint is simply applied to the sum of reservations at 
>> each CT which
>> already account for individual overbooking factors at each 
>> CT. However with
>> the formula that you are proposing we would completely shut 
>> the door for
>> other uses of the max link b/w TLV, for instance as a 
>> constraint on the max
>> LSP b/w. Since we have already a parameter that was 
>> explicitly defined as
>> the aggregate reservation constrain, there is no need to 
>> close door for a
>> different use of the max link b/w parameter at this point.
>> 

Agreed.

Thanks

FRancois

>> Regards,
>> Dimitry 
>> 
>> > -----Original Message-----
>> > From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
>> > Sent: Monday, May 19, 2003 4:47 PM
>> > To: te-wg@ops.ietf.org
>> > Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, Gerald R
>> > (Jerry), ALABS
>> > Subject: link capacity and reservable
>> > 
>> > 
>> > This is in response to the discussion of maximum reservable
>> > bandwidth in
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
>> > As the issue is not restricted solely to MAM, and has impact on
>> > RDM and in fact all BC models, I am talking about it in a more
>> > general context.
>> > 
>> > Current TE extension in IGP deals with aggregate traffic.
>> > There is thus a simple average-overall relationship:
>> > max link bandwidth = max reservable bandwidth/overbooking.
>> > As a result, whether "max link bandwidth" is supported or
>> > commonly used or not is immaterial.
>> > 
>> > In DS-TE, there is per-CT bandwidth contstraint and per-CT
>> > overbooking. Max reservable bandwidth should accordingly be
>> > treated as a vector quantity. Reflecting this view, the
>> > following definition for MAM in is
>> > adequate:
>> > for each value of b in the range 0 <= b <= 7:
>> > Reserved (CTb) <= BCb
>> > (with some clarification in MAM spec regarding overbooking)
>> > 
>> > Also, the following additional condition for MAM definition as
>> > proposed in the second message quoted above is both unneccsary
>> > and incorrect:
>> > SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>> > for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>> > This is like when I have 15 dollars and 10 euros in my pocket,
>> > then my max reserve is 25 (of what unit).
>> > 
>> > The "max link bandwidth," being a normalized quantity, is more
>> > meaningful. For admission control under MAM, in addition to
>> > the observing the bandwidth constraints as specified in the
>> > above deinition, something like the following may be used:
>> > SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>> > for all "c" in the range 0 <= c <= (MaxCT-1)
>> > (with some tweaks to account for priorities)
>> > 
>> > Thanks, Wai Sum
>> > 
>> 



---------------------------------
Do You Yahoo!?
"Ïà¼û²»ÈçÁÄÌì!²»³öÃÅÒ»ÑùÃæ¶ÔÃæ£¡ÍøÂçÉãÏñÍ·¶Ô¶ÔÅÉËÍÖÐ~¸Ï¿ìÓÃÄãµÄÑÅ»¢µçÓÊÕÊºÅ²ÎÓë°É¡­¡­
--0-871062811-1053849452=:34996
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: 8bit

<DIV>My question, if parameters in a new LSP setup request are converted as Lai stated, how could we select best path for new traffic flows?</DIV>
<DIV>&nbsp;</DIV>
<DIV>for example, </DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /-----------b \</DIV>
<DIV>s----/&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \--------t</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;a \&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /d</DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; \---------c/</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>S want to set up LSP of CT1 &nbsp;to T with bandwidth 5Mbps, while at node A there is tow branch ( to B or to C),&nbsp; if link AC allow more overbooking than AB, but residual BW for CT1 is the same. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Which path should we take ?&nbsp; or should OSPF&nbsp; use which value ( real BW or reservable BW) ? </DIV>
<DIV>&nbsp;</DIV>
<DIV>thanks </DIV>
<DIV>&nbsp;</DIV>
<DIV>Jing Shen</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR><B><I>"Lai, Wai S (Waisum), ALABS" &lt;wlai@att.com&gt;</I></B> wrote:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Thanks to the responses from Jean-Louis, Dimitry, and Francois<BR>regarding the issue on the use of max link bw versus max<BR>reservable bw in my previous mesage (contained here at the end).<BR><BR>The main point underlying the issue that has so far not been<BR>discussed is this, because of per-CT overbooking, max reservable<BR>bw should be treated as a vector quantity (as in my previous<BR>dollar/euro analogy). Let me illustrate by an example.<BR><BR>Max link bw = 100 (assuming some bw unit)<BR>CT1: bw constraint = 80, LSP bw = 10<BR>CT2: bw constraint = 70, LSP bw = 7<BR><BR>In this setting (with all the quantities above being normalized<BR>with respect to link bw), we can accommodate under MAM any one<BR>of these combinations:<BR>8 CT1-LSPs + 2 CT2-LSPs = 94, 7 CT1-LSPs + 4 CT2-LSPs = 98,<BR>6 CT1-LSPs + 5 CT2-LSPs = 95, 5 CT1-LSPs + 7 CT2-LSPs = 99,<BR>4 CT1-LSPs + 8 CT2-LSPs = 96, 3 CT1-LSPs + 10 CT2-LSPs = 100.<BR>The aggregate link bw's are all within the max link bw of 100.<BR><BR>Now consider the usage of reservable bw:<BR>CT1: overbooking = 2, LSP reserved bw = 2 x 10 = 20<BR>CT2: overbooking = 4, LSP reserved bw = 4 x 7 = 28<BR><BR>The corresponding max reservable bw's would be:<BR>8 CT1-LSPs + 2 CT2-LSPs = 216<BR>7 CT1-LSPs + 4 CT2-LSPs = 252<BR>6 CT1-LSPs + 5 CT2-LSPs = 260<BR>5 CT1-LSPs + 7 CT2-LSPs = 296<BR>4 CT1-LSPs + 8 CT2-LSPs = 304<BR>3 CT1-LSPs + 10 CT2-LSPs = 340<BR><BR>In contrast with max link bw, it's not clear what criterion<BR>should be used to pick *a single value* from the above list<BR>and use it as the "aggregate" max reservable bw. While MAM<BR>is being used here for illustration, this problem is generic<BR>and affects RDM as well.<BR><BR>As pointed out in my previous message, in current TE for<BR>aggregate traffic, it is possible to define a single<BR>"aggregate" max reservable bw value, since an average-overall<BR>can be assumed. Once different overbooking factors are used<BR>for different tr
affic components (e.g., CT's), this is no longer<BR>the case, and each traffic component has its own max reservable<BR>bw. That's what I mean by treating max reservable bw as a vector<BR>quantity with distinct components. This fact is actually also<BR>independent of the type of overbooking methods used, i.e., LOM<BR>or not LOM.<BR><BR>Thus, the proper way to do the computation is to first convert<BR>reservable bw to link bw (or some equivalent normalized quantity),<BR>and then check against the max link bw (or some equivalent<BR>normalized quantity). Checking against the "aggregate" max<BR>reservable bw is problematic since it is a list and not a single<BR>value, as shown above.<BR><BR>Regarding the limit of bandwidth for a single LSP, that's already<BR>taken care of by the per-CT bw constraint (since it is assumed<BR>to be normalized). If folks want to use the max link bw for this<BR>purpose, it's not precluded by the above consideration either<BR>(because if the max link bw puts a contraint on the aggregate<BR>traffic, it certainly puts a contraint on a single LSP).<BR><BR>Thanks, Wai Sum<BR><BR>-----Original Message-----<BR>From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]<BR>Sent: Tuesday, May 20, 2003 11:52 AM<BR>To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org<BR>Cc: Ash, Gerald R (Jerry), ALABS<BR>Subject: RE: link capacity and reservable<BR><BR><BR>Dimitry,<BR><BR>&gt;&gt; -----Original Message-----<BR>&gt;&gt; From: Dimitry Haskin [mailto:dhaskin@axiowave.com] <BR>&gt;&gt; Sent: 20 May 2003 16:45<BR>&gt;&gt; To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org<BR>&gt;&gt; Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, <BR>&gt;&gt; Gerald R (Jerry), ALABS<BR>&gt;&gt; Subject: RE: link capacity and reservable<BR>&gt;&gt; <BR>&gt;&gt; <BR>&gt;&gt; Waisum, Jerry,<BR>&gt;&gt; <BR>&gt;&gt; IMO, both yours and Francois' formulas for the aggregate reservation<BR>&gt;&gt; constrain would achieve identical results. <BR><BR>I guess you're right that at the end of the da
y it would be pretty much<BR>the same thing functionnally.<BR><BR>&gt;&gt;Note that max <BR>&gt;&gt; reservable b/w<BR>&gt;&gt; constraint is simply applied to the sum of reservations at <BR>&gt;&gt; each CT which<BR>&gt;&gt; already account for individual overbooking factors at each <BR>&gt;&gt; CT. However with<BR>&gt;&gt; the formula that you are proposing we would completely shut <BR>&gt;&gt; the door for<BR>&gt;&gt; other uses of the max link b/w TLV, for instance as a <BR>&gt;&gt; constraint on the max<BR>&gt;&gt; LSP b/w. Since we have already a parameter that was <BR>&gt;&gt; explicitly defined as<BR>&gt;&gt; the aggregate reservation constrain, there is no need to <BR>&gt;&gt; close door for a<BR>&gt;&gt; different use of the max link b/w parameter at this point.<BR>&gt;&gt; <BR><BR>Agreed.<BR><BR>Thanks<BR><BR>FRancois<BR><BR>&gt;&gt; Regards,<BR>&gt;&gt; Dimitry <BR>&gt;&gt; <BR>&gt;&gt; &gt; -----Original Message-----<BR>&gt;&gt; &gt; From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]<BR>&gt;&gt; &gt; Sent: Monday, May 19, 2003 4:47 PM<BR>&gt;&gt; &gt; To: te-wg@ops.ietf.org<BR>&gt;&gt; &gt; Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, Gerald R<BR>&gt;&gt; &gt; (Jerry), ALABS<BR>&gt;&gt; &gt; Subject: link capacity and reservable<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; This is in response to the discussion of maximum reservable<BR>&gt;&gt; &gt; bandwidth in<BR>&gt;&gt; &gt; http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html<BR>&gt;&gt; &gt; http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html<BR>&gt;&gt; &gt; As the issue is not restricted solely to MAM, and has impact on<BR>&gt;&gt; &gt; RDM and in fact all BC models, I am talking about it in a more<BR>&gt;&gt; &gt; general context.<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; Current TE extension in IGP deals with aggregate traffic.<BR>&gt;&gt; &gt; There is thus a simple average-overall relationship:<BR>&gt;&gt; &gt; max link bandwidth = max reservable bandwidth/overbooking.<BR>&gt;&gt; &gt; As a result, whether "max 
link bandwidth" is supported or<BR>&gt;&gt; &gt; commonly used or not is immaterial.<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; In DS-TE, there is per-CT bandwidth contstraint and per-CT<BR>&gt;&gt; &gt; overbooking. Max reservable bandwidth should accordingly be<BR>&gt;&gt; &gt; treated as a vector quantity. Reflecting this view, the<BR>&gt;&gt; &gt; following definition for MAM in <TEWG-DIFF-TE-REQTS>is<BR>&gt;&gt; &gt; adequate:<BR>&gt;&gt; &gt; for each value of b in the range 0 &lt;= b &lt;= 7:<BR>&gt;&gt; &gt; Reserved (CTb) &lt;= BCb<BR>&gt;&gt; &gt; (with some clarification in MAM spec regarding overbooking)<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; Also, the following additional condition for MAM definition as<BR>&gt;&gt; &gt; proposed in the second message quoted above is both unneccsary<BR>&gt;&gt; &gt; and incorrect:<BR>&gt;&gt; &gt; SUM (Reserved (CTc)) &lt;= Max Reservable Bandwidth<BR>&gt;&gt; &gt; for all "c" in the range 0 &lt;= c &lt;= (MaxCT-1)<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; This is like when I have 15 dollars and 10 euros in my pocket,<BR>&gt;&gt; &gt; then my max reserve is 25 (of what unit).<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; The "max link bandwidth," being a normalized quantity, is more<BR>&gt;&gt; &gt; meaningful. For admission control under MAM, in addition to<BR>&gt;&gt; &gt; the observing the bandwidth constraints as specified in the<BR>&gt;&gt; &gt; above deinition, something like the following may be used:<BR>&gt;&gt; &gt; SUM (Reserved (CTc)/overbooking(CTc)) &lt;= Max Link Bandwidth<BR>&gt;&gt; &gt; for all "c" in the range 0 &lt;= c &lt;= (MaxCT-1)<BR>&gt;&gt; &gt; (with some tweaks to account for priorities)<BR>&gt;&gt; &gt; <BR>&gt;&gt; &gt; Thanks, Wai Sum<BR>&gt;&gt; &gt; <BR>&gt;&gt; <BR></BLOCKQUOTE><p><br><hr size=1><b>Do You Yahoo!?</b><br>
<a href="http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.messenger.yahoo.com/">"Ïà¼û²»ÈçÁÄÌì!²»³öÃÅÒ»ÑùÃæ¶ÔÃæ£¡ÍøÂçÉãÏñÍ·¶Ô¶ÔÅÉËÍÖÐ~¸Ï¿ìÓÃÄãµÄÑÅ»¢µçÓÊÕÊºÅ²ÎÓë°É¡­¡­</a>
--0-871062811-1053849452=:34996--



From owner-te-wg@ops.ietf.org  Sun May 25 15:29:49 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09755
	for <tewg-archive@lists.ietf.org>; Sun, 25 May 2003 15:29:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19K176-00027v-00
	for te-wg-data@psg.com; Sun, 25 May 2003 19:25:00 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19K173-00027j-00
	for te-wg@ops.ietf.org; Sun, 25 May 2003 19:24:57 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4PJOeil013112
	for <te-wg@ops.ietf.org>; Sun, 25 May 2003 15:24:56 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020026514D; Sun, 25 May 2003 15:24:45 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 
Date: Sun, 25 May 2003 14:24:45 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137093@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts 
Thread-Index: AcMhi8vm+javnb6sSX2QFm1JtYs8nQBXn6Vg
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-16.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA09755

Jim,
  I think we still need some more discussion.  Please see
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00290.html
as a result of the complexity of the overbooking options.
Thanks, Wai Sum

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Friday, May 23, 2003 8:31 PM
To: Francois Le Faucheur (flefauch)
Cc: te-wg@ops.ietf.org; Lai, Wai S (Waisum), ALABS
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 



So is there agreement now?

If so, what's the fallout?

I don't want to pull the reqt's out of IESG, and as stated in the list,
it 
isnt the place MAM is defined (sorry SAM, I think we have enough
bandwidth 
models).

Francois, can you re-propose changes for proto, RDM and MAM?

thanks,

Jim

btw... I also think LOMs are lots of complexity for little gain :)



On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:

> Jerry,
> 
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> >> Sent: 20 May 2003 17:35
> >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
> >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
> >> Wai S (Waisum), ALABS
> >> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
> >> 
> >> 
> >> Dimitry, Francois,
> >> 
> >> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
> >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
> >> > > 
> >> > > However, this formula is incorrect for DS-TE when per-CT 
> >> > > LOM's are used, since the above formula only reflects the Max 
> >> > > Reservable Bandwidth for the entire link, and does not 
> >> > > reflect the per-CT local overbooking factors.  So what 
> >> > > formula do you suggest when per-CT LOM's are used?
> >> 
> >> > Wouldn't 'Reserved (CTc)' it the above formula already 
> >> accounts for the
> >> > overbooking multiplier at CTc?  I don't see how this 
> >> formula precludes
> >> > per-CT LOM's to be used. Please explain.
> >> 
> >> Are you then proposing these formulas:
> >> 
> >> 1. When per-CT LOMs are not used:
> >> 
> >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
> >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> 
> >> 2. When per-CT LOMs are used:
> >> 
> >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
> >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> 
> >> Is that correct?  Please confirm, and/or give the formulas 
> >> you propose.
> 
> Yes, this is exactly what I propose.
> I think this is similar to what you were proposing, only using "Max
Res
> Bw" instead of "Max Link Bw". 
> 
> Sorry I didn't make that very clear before.
> 
> Cheers
> 
> FRancois
> 
> >> 
> >> Thanks,
> >> Jerry
> >> 
> 
> 
> 
> 




From owner-te-wg@ops.ietf.org  Sun May 25 16:11:33 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10407
	for <tewg-archive@lists.ietf.org>; Sun, 25 May 2003 16:11:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19K1oN-0006zh-00
	for te-wg-data@psg.com; Sun, 25 May 2003 20:09:43 +0000
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19K1oK-0006zV-00
	for te-wg@ops.ietf.org; Sun, 25 May 2003 20:09:40 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4PK70iv018327
	for <te-wg@ops.ietf.org>; Sun, 25 May 2003 16:09:39 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC7660200266387; Sun, 25 May 2003 16:09:39 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="GB2312"
Subject: RE: link capacity and reservable
Date: Sun, 25 May 2003 15:09:39 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137094@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMik12tBZzgoxEvShyv7qfiECpI3QAL20UA
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jing Shen" <jshen_cad@yahoo.com.cn>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA10407

Jing,
  Many thanks for your example.
  As I stated earlier, current TE extension in IGP deals with
aggregate traffic.  Through a simple average-overall relationship:
max link bw = max reservable bw/overbooking,
it does not matter which quantity is used - in some sense they are
immutable under overbooking.
  But when different per-CT and per-link overbooking factors
are allowed, the use of "max reservable bw" in bw constraint
computation for admission control makes the rules more complex.
I think both your example and mine show that this is the case.
The use of some quantity that is normalized with respect to
the "max link bw" would be much more straightforward.
Thanks, Wai Sum

-----Original Message-----
From: Jing Shen [mailto:jshen_cad@yahoo.com.cn]
Sent: Sunday, May 25, 2003 3:58 AM
To: Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
Cc: Ash, Gerald R (Jerry), ALABS; Dimitry Haskin; Francois Le Faucheur (flefauch)
Subject: RE: link capacity and reservable


My question, if parameters in a new LSP setup request are converted as Lai stated, how could we select best path for new traffic flows?

for example, 
       /-----------b \
s----/                \--------t
    a \              /d
        \---------c/


S want to set up LSP of CT1  to T with bandwidth 5Mbps, while at node A there is tow branch ( to B or to C),  if link AC allow more overbooking than AB, but residual BW for CT1 is the same. 

Which path should we take ?  or should OSPF  use which value ( real BW or reservable BW) ? 

thanks 

Jing Shen




"Lai, Wai S (Waisum), ALABS" <wlai@att.com> wrote:
Thanks to the responses from Jean-Louis, Dimitry, and Francois
regarding the issue on the use of max link bw versus max
reservable bw in my previous mesage (contained here at the end).

The main point underlying the issue that has so far not been
discussed is this, because of per-CT overbooking, max reservable
bw should be treated as a vector quantity (as in my previous
dollar/euro analogy). Let me illustrate by an example.

Max link bw = 100 (assuming some bw unit)
CT1: bw constraint = 80, LSP bw = 10
CT2: bw constraint = 70, LSP bw = 7

In this setting (with all the quantities above being normalized
with respect to link bw), we can accommodate under MAM any one
of these combinations:
8 CT1-LSPs + 2 CT2-LSPs = 94, 7 CT1-LSPs + 4 CT2-LSPs = 98,
6 CT1-LSPs + 5 CT2-LSPs = 95, 5 CT1-LSPs + 7 CT2-LSPs = 99,
4 CT1-LSPs + 8 CT2-LSPs = 96, 3 ! CT1-LSPs + 10 CT2-LSPs = 100.
The aggregate link bw's are all within the max link bw of 100.

Now consider the usage of reservable bw:
CT1: overbooking = 2, LSP reserved bw = 2 x 10 = 20
CT2: overbooking = 4, LSP reserved bw = 4 x 7 = 28

The corresponding max reservable bw's would be:
8 CT1-LSPs + 2 CT2-LSPs = 216
7 CT1-LSPs + 4 CT2-LSPs = 252
6 CT1-LSPs + 5 CT2-LSPs = 260
5 CT1-LSPs + 7 CT2-LSPs = 296
4 CT1-LSPs + 8 CT2-LSPs = 304
3 CT1-LSPs + 10 CT2-LSPs = 340

In contrast with max link bw, it's not clear what criterion
should be used to pick *a single value* from the above list
and use it as the "aggregate" max reservable bw. While MAM
is being used here for illustration, this problem is generic
and affects RDM as well.

As pointed out in my previous message, in current TE for
aggregate traffic, it is possible to define a single
"aggregate" max reservable bw value, since an average-overall
can be as! sumed. Once different overbooking factors are used
for different tr affic components (e.g., CT's), this is no longer
the case, and each traffic component has its own max reservable
bw. That's what I mean by treating max reservable bw as a vector
quantity with distinct components. This fact is actually also
independent of the type of overbooking methods used, i.e., LOM
or not LOM.

Thus, the proper way to do the computation is to first convert
reservable bw to link bw (or some equivalent normalized quantity),
and then check against the max link bw (or some equivalent
normalized quantity). Checking against the "aggregate" max
reservable bw is problematic since it is a list and not a single
value, as shown above.

Regarding the limit of bandwidth for a single LSP, that's already
taken care of by the per-CT bw constraint (since it is assumed
to be normalized). If folks want to use the max link bw for this
purpose, it's not precluded by the above consideration either
(because if the max link b! w puts a contraint on the aggregate
traffic, it certainly puts a contraint on a single LSP).

Thanks, Wai Sum

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Tuesday, May 20, 2003 11:52 AM
To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
Cc: Ash, Gerald R (Jerry), ALABS
Subject: RE: link capacity and reservable


Dimitry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 20 May 2003 16:45
>> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, 
>> Gerald R (Jerry), ALABS
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Waisum, Jerry,
>> 
>> IMO, both yours and Francois' formulas for the aggregate reservation
>> constrain would achieve ide! ntical results. 

I guess you're right that at the end of the da y it would be pretty much
the same thing functionnally.

>>Note that max 
>> reservable b/w
>> constraint is simply applied to the sum of reservations at 
>> each CT which
>> already account for individual overbooking factors at each 
>> CT. However with
>> the formula that you are proposing we would completely shut 
>> the door for
>> other uses of the max link b/w TLV, for instance as a 
>> constraint on the max
>> LSP b/w. Since we have already a parameter that was 
>> explicitly defined as
>> the aggregate reservation constrain, there is no need to 
>> close door for a
>> different use of the max link b/w parameter at this point.
>> 

Agreed.

Thanks

FRancois

>> Regards,
>> Dimitry 
>> 
>> > -----Original Message-----
>> > From: Lai, Wai S (Waisum), A! LABS [mailto:wlai@att.com]
>> > Sent: Monday, May 19, 2003 4:47 PM
>> > To: te-wg@ops.ietf.org
>> > Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, Gerald R
>> > (Jerry), ALABS
>> > Subject: link capacity and reservable
>> > 
>> > 
>> > This is in response to the discussion of maximum reservable
>> > bandwidth in
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
>> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
>> > As the issue is not restricted solely to MAM, and has impact on
>> > RDM and in fact all BC models, I am talking about it in a more
>> > general context.
>> > 
>> > Current TE extension in IGP deals with aggregate traffic.
>> > There is thus a simple average-overall relationship:
>> > max link bandwidth = max reserva! ble bandwidth/overbooking.
>> > As a result, whether "max link bandwidth" is supported or
>> > commonly used or not is immaterial.
>> > 
>> > In DS-TE, there is per-CT bandwidth contstraint and per-CT
>> > overbooking. Max reservable bandwidth should accordingly be
>> > treated as a vector quantity. Reflecting this view, the
>> > following definition for MAM in is
>> > adequate:
>> > for each value of b in the range 0 <= b <= 7:
>> > Reserved (CTb) <= BCb
>> > (with some clarification in MAM spec regarding overbooking)
>> > 
>> > Also, the following additional condition for MAM definition as
>> > proposed in the second message quoted above is both unneccsary
>> > and incorrect:
>> > SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>> > for all "c" in the range 0 <= c <= (MaxCT-1)
>> > 
>&! gt; > This is like when I have 15 dollars and 10 euros in my pocket,
>> > then my max reserve is 25 (of what unit).
>> > 
>> > The "max link bandwidth," being a normalized quantity, is more
>> > meaningful. For admission control under MAM, in addition to
>> > the observing the bandwidth constraints as specified in the
>> > above deinition, something like the following may be used:
>> > SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>> > for all "c" in the range 0 <= c <= (MaxCT-1)
>> > (with some tweaks to account for priorities)
>> > 
>> > Thanks, Wai Sum
>> >



From owner-te-wg@ops.ietf.org  Mon May 26 08:16:03 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09753
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 08:16:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KGne-000MLD-00
	for te-wg-data@psg.com; Mon, 26 May 2003 12:09:58 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KGnZ-000MKm-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 12:09:53 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 May 2003 14:09:08 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4QC7XIt008358;
	Mon, 26 May 2003 14:07:53 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 26 May 2003 14:09:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Mon, 26 May 2003 13:09:32 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5238@xbe-lon-313.cisco.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+QAGnzyQAAuRfBcA==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 26 May 2003 12:09:33.0104 (UTC) FILETIME=[AADE9B00:01C3237F]
X-Spam-Status: No, hits=-4.8 required=5.0
	tests=BAYES_30,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA09753

Hello Waisum,

Thanks for your analysis.

The point you raise (aka is there a need for vectorisation of aggregate
constraints?) was actually one of the key technical points behind the
discussion we had at the time of breaking-out "Overbooking" into (i) LSP
Size Overbooking, (ii) Link Size Overbooking and (iii) per-CT Local
Overbooking Multiplier;

I believe there was clear agreement that:
	- there was a strong need for SPs to be able to apply, on a
network wide basis, a different level of overbooking for different CTs
(typically high overbooking on best-effort, low/no overbooking on
premium/voice)
	- this was well supported by the "Link Size Overbooking" method
(effectively just pretending to have a bigger link than the real one ;
and thus effectively applying a single per link overbooking which is
COMMON to all CTs)
	- there was a strong need for SPs to be able to apply a
different level of overbooking on differnet links (typically higher
overbooking on higher speed links)
	- this was well supported by the "LSP Size Overbooking" method
(which allows different overbooking per CT - it even offers finer
granularity of per-LSP overbooking) 
	- there was only a weak potential need for being able to apply
different overbooking ratios which need to be different for each CT on
different links.
	- this should be OPTIONAL
	- this would be well supported by the per-CT Local Overbooking
Multiplier.

A related conclusion of the above is that the "Link Size Overbooking"
method does NOT need to enforce different overbooking ratios for
different CTs. If the SP needs different overbooking ratios for
different CTs, then, in the context of DS-TE, this can be achieved via
the "LSP Size Overbooking" method.

Since the "Max Reservable Bandwidth" is involved only in the "LSP Size
Overbooking" method, it does NOT need to enforce a different level of
overbooking for different CTs; enforcing the same one across all CTs is
all what's required. This means that, taking into account the specific
environment of DS-TE, the aggregate constraint does not need to be
vectorised (although I agree that in a completely generic world it would
have to).

Now, in the case where the SP wants to enforce different overbooking
ratios for different CTs on different links, then this needs to be
achieved via the LOMs (and not via the "Link Size Overbooking"). Then
the LOMs need to be applied individually to each CT which effectively
results in the vectorisation you described. This will be reflected in
the CAC formulas when updated to reflect the aggregate constraint (which
will be applied to the "Normalised Bw"). 

So to recap in a nutshell, I believe the generic "vectorisation" issue
you discussed:
	- does not apply to Link Size Overbooking in the particular case
of DS-TE (since Link Size Overbooking does not need to enforce different
overbooking ratios across CT) and thus we only need a single "Max Res
Bw" value
	- does apply to the Local Overbooking Multiplier method and
is/will be reflected by applying the "Normalised Bw" when applying the
aggregate constraint.

Thanks for helping getting to the bottom of this question.

Cheers

Francois

>> -----Original Message-----
>> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com] 
>> Sent: 23 May 2003 20:58
>> To: te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS; Dimitry Haskin; Francois 
>> Le Faucheur (flefauch)
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Thanks to the responses from Jean-Louis, Dimitry, and Francois
>> regarding the issue on the use of max link bw versus max
>> reservable bw in my previous mesage (contained here at the end).
>> 
>> The main point underlying the issue that has so far not been
>> discussed is this, because of per-CT overbooking, max reservable
>> bw should be treated as a vector quantity (as in my previous
>> dollar/euro analogy).  Let me illustrate by an example.
>> 
>> Max link bw = 100 (assuming some bw unit)
>> CT1: bw constraint = 80, LSP bw = 10
>> CT2: bw constraint = 70, LSP bw =  7
>> 
>> In this setting (with all the quantities above being normalized
>> with respect to link bw), we can accommodate under MAM any one
>> of these combinations:
>> 8 CT1-LSPs + 2 CT2-LSPs = 94, 7 CT1-LSPs + 4 CT2-LSPs = 98,
>> 6 CT1-LSPs + 5 CT2-LSPs = 95, 5 CT1-LSPs + 7 CT2-LSPs = 99,
>> 4 CT1-LSPs + 8 CT2-LSPs = 96, 3 CT1-LSPs + 10 CT2-LSPs = 100.
>> The aggregate link bw's are all within the max link bw of 100.
>> 
>> Now consider the usage of reservable bw:
>> CT1: overbooking = 2, LSP reserved bw = 2 x 10 = 20
>> CT2: overbooking = 4, LSP reserved bw = 4 x  7 = 28
>> 
>> The corresponding max reservable bw's would be:
>> 8 CT1-LSPs + 2 CT2-LSPs = 216
>> 7 CT1-LSPs + 4 CT2-LSPs = 252
>> 6 CT1-LSPs + 5 CT2-LSPs = 260
>> 5 CT1-LSPs + 7 CT2-LSPs = 296
>> 4 CT1-LSPs + 8 CT2-LSPs = 304
>> 3 CT1-LSPs + 10 CT2-LSPs = 340
>> 
>> In contrast with max link bw, it's not clear what criterion
>> should be used to pick *a single value* from the above list
>> and use it as the "aggregate" max reservable bw.  While MAM
>> is being used here for illustration, this problem is generic
>> and affects RDM as well.
>> 
>> As pointed out in my previous message, in current TE for
>> aggregate traffic, it is possible to define a single
>> "aggregate" max reservable bw value, since an average-overall
>> can be assumed.  Once different overbooking factors are used
>> for different traffic components (e.g., CT's), this is no longer
>> the case, and each traffic component has its own max reservable
>> bw.  That's what I mean by treating max reservable bw as a vector
>> quantity with distinct components.  This fact is actually also
>> independent of the type of overbooking methods used, i.e., LOM
>> or not LOM.
>> 
>> Thus, the proper way to do the computation is to first convert
>> reservable bw to link bw (or some equivalent normalized quantity),
>> and then check against the max link bw (or some equivalent
>> normalized quantity).  Checking against the "aggregate" max
>> reservable bw is problematic since it is a list and not a single
>> value, as shown above.
>> 
>> Regarding the limit of bandwidth for a single LSP, that's already
>> taken care of by the per-CT bw constraint (since it is assumed
>> to be normalized).  If folks want to use the max link bw for this
>> purpose, it's not precluded by the above consideration either
>> (because if the max link bw puts a contraint on the aggregate
>> traffic, it certainly puts a contraint on a single LSP).
>> 
>> Thanks, Wai Sum
>> 
>> -----Original Message-----
>> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>> Sent: Tuesday, May 20, 2003 11:52 AM
>> To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Dimitry,
>> 
>> >> -----Original Message-----
>> >> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> >> Sent: 20 May 2003 16:45
>> >> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> >> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, 
>> >> Gerald R (Jerry), ALABS
>> >> Subject: RE: link capacity and reservable
>> >> 
>> >> 
>> >> Waisum, Jerry,
>> >> 
>> >> IMO, both yours and Francois' formulas for the aggregate 
>> reservation
>> >> constrain would achieve identical results. 
>> 
>> I guess you're right that at the end of the day it would be 
>> pretty much
>> the same thing functionnally.
>> 
>> >>Note that max 
>> >> reservable b/w
>> >> constraint is simply applied to the sum of reservations at 
>> >> each CT which
>> >> already account for individual overbooking factors at each 
>> >> CT. However with
>> >> the formula that you are proposing we would completely shut 
>> >> the door for
>> >> other uses of the max link b/w TLV, for instance as a 
>> >> constraint on the max
>> >> LSP b/w. Since we have already a parameter that was 
>> >> explicitly defined as
>> >> the aggregate reservation constrain, there is no need to 
>> >> close door for a
>> >> different use of the max link b/w parameter at this point.
>> >> 
>> 
>> Agreed.
>> 
>> Thanks
>> 
>> FRancois
>> 
>> >> Regards,
>> >>   Dimitry  
>> >> 
>> >> > -----Original Message-----
>> >> > From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
>> >> > Sent: Monday, May 19, 2003 4:47 PM
>> >> > To: te-wg@ops.ietf.org
>> >> > Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); 
>> Ash, Gerald R
>> >> > (Jerry), ALABS
>> >> > Subject: link capacity and reservable
>> >> > 
>> >> > 
>> >> > This is in response to the discussion of maximum reservable
>> >> > bandwidth in
>> >> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
>> >> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
>> >> > As the issue is not restricted solely to MAM, and has impact on
>> >> > RDM and in fact all BC models, I am talking about it in a more
>> >> > general context.
>> >> > 
>> >> > Current TE extension in IGP deals with aggregate traffic.
>> >> > There is thus a simple average-overall relationship:
>> >> > max link bandwidth = max reservable bandwidth/overbooking.
>> >> > As a result, whether "max link bandwidth" is supported or
>> >> > commonly used or not is immaterial.
>> >> > 
>> >> > In DS-TE, there is per-CT bandwidth contstraint and per-CT
>> >> > overbooking.  Max reservable bandwidth should accordingly be
>> >> > treated as a vector quantity.  Reflecting this view, the
>> >> > following definition for MAM in <tewg-diff-te-reqts> is
>> >> > adequate:
>> >> >   for each value of b in the range 0 <= b <= 7:
>> >> >     Reserved (CTb) <= BCb
>> >> > (with some clarification in MAM spec regarding overbooking)
>> >> > 
>> >> > Also, the following additional condition for MAM definition as
>> >> > proposed in the second message quoted above is both unneccsary
>> >> > and incorrect:
>> >> >   SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>> >> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> > 
>> >> > This is like when I have 15 dollars and 10 euros in my pocket,
>> >> > then my max reserve is 25 (of what unit).
>> >> > 
>> >> > The "max link bandwidth," being a normalized quantity, is more
>> >> > meaningful.  For admission control under MAM, in addition to
>> >> > the observing the bandwidth constraints as specified in the
>> >> > above deinition, something like the following may be used:
>> >> >   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>> >> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> > (with some tweaks to account for priorities)
>> >> > 
>> >> > Thanks, Wai Sum
>> >> > 
>> >> 
>> 



From owner-te-wg@ops.ietf.org  Mon May 26 08:33:20 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10263
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 08:33:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KH9J-000N4k-00
	for te-wg-data@psg.com; Mon, 26 May 2003 12:32:21 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KH9E-000N4X-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 12:32:17 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 May 2003 14:31:34 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4QCU6LW011528;
	Mon, 26 May 2003 14:30:18 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 26 May 2003 14:31:59 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Mon, 26 May 2003 13:31:59 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5239@xbe-lon-313.cisco.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+QAGnzyQAAuRfBcAADQmsA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Dimitry Haskin" <dhaskin@axiowave.com>
X-OriginalArrivalTime: 26 May 2003 12:31:59.0738 (UTC) FILETIME=[CD86A5A0:01C32382]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA10263

Hello again,

Specifically, here are the proposed updated formulas for MAM:

MAM Definition when LOM is NOT used (ie LOM[i]=1)
=================================================
o	for each value of b in the range 0 <= b <= 7:
            		Reserved (CTb) <= BCb,
o	SUM (Reserved(CTc)) <= Max-Reservable-Bw,   
		where the SUM is across all values of c in the range 0
<= c <= 7

MAM Definition when LOM is used 
===============================
o	for each value of b in the range 0 <= b <= 7:
            		Normalised (CTb) <= BCb,
o	SUM (Normalised(CTc)) <= Max-Reservable-Bw,   
		where the SUM is across all values of c in the range 0
<= c <= 7


"Unreserved TE-Class [i]" when LOM is NOT used (ie LOM[i]=1)
============================================================
	MIN  [
	[ BCc - SUM ( Reserved(CTc,q) ) ] for q <= p ,
	[ Max_Reservable_Bw - SUM ( Reserved(CTb,q) ) ] for q <= p and 0
<= b <= 7,
         ]
where:
TE-Class [i] <--> < CTc , preemption p>
in the configured TE-Class mapping.


"Unreserved TE-Class [i]" when LOM is used
==========================================
	LOM(c) x MIN  [
	[ BCc - SUM ( Normalised(CTb,q) ) ] for q <= p,
	[ Max_Reservable_Bw - SUM ( Normalised(CTb,q) ) ] for q <= p and
0 <= b <= 7,
          ]
where:
TE-Class [i] <--> < CTc , preemption p> 
in the configured TE-Class mapping.

Cheers

Francois

>> -----Original Message-----
>> From: Francois Le Faucheur (flefauch) 
>> Sent: 26 May 2003 14:10
>> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS; Dimitry Haskin; Francois 
>> Le Faucheur (flefauch)
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Hello Waisum,
>> 
>> Thanks for your analysis.
>> 
>> The point you raise (aka is there a need for vectorisation 
>> of aggregate constraints?) was actually one of the key 
>> technical points behind the discussion we had at the time of 
>> breaking-out "Overbooking" into (i) LSP Size Overbooking, 
>> (ii) Link Size Overbooking and (iii) per-CT Local 
>> Overbooking Multiplier;
>> 
>> I believe there was clear agreement that:
>> 	- there was a strong need for SPs to be able to apply, 
>> on a network wide basis, a different level of overbooking 
>> for different CTs (typically high overbooking on 
>> best-effort, low/no overbooking on premium/voice)
>> 	- this was well supported by the "Link Size 
>> Overbooking" method (effectively just pretending to have a 
>> bigger link than the real one ; and thus effectively 
>> applying a single per link overbooking which is COMMON to all CTs)
>> 	- there was a strong need for SPs to be able to apply a 
>> different level of overbooking on differnet links (typically 
>> higher overbooking on higher speed links)
>> 	- this was well supported by the "LSP Size Overbooking" 
>> method (which allows different overbooking per CT - it even 
>> offers finer granularity of per-LSP overbooking) 
>> 	- there was only a weak potential need for being able 
>> to apply different overbooking ratios which need to be 
>> different for each CT on different links.
>> 	- this should be OPTIONAL
>> 	- this would be well supported by the per-CT Local 
>> Overbooking Multiplier.
>> 
>> A related conclusion of the above is that the "Link Size 
>> Overbooking" method does NOT need to enforce different 
>> overbooking ratios for different CTs. If the SP needs 
>> different overbooking ratios for different CTs, then, in the 
>> context of DS-TE, this can be achieved via the "LSP Size 
>> Overbooking" method.
>> 
>> Since the "Max Reservable Bandwidth" is involved only in the 
>> "LSP Size Overbooking" method, it does NOT need to enforce a 
>> different level of overbooking for different CTs; enforcing 
>> the same one across all CTs is all what's required. This 
>> means that, taking into account the specific environment of 
>> DS-TE, the aggregate constraint does not need to be 
>> vectorised (although I agree that in a completely generic 
>> world it would have to).
>> 
>> Now, in the case where the SP wants to enforce different 
>> overbooking ratios for different CTs on different links, 
>> then this needs to be achieved via the LOMs (and not via the 
>> "Link Size Overbooking"). Then the LOMs need to be applied 
>> individually to each CT which effectively results in the 
>> vectorisation you described. This will be reflected in the 
>> CAC formulas when updated to reflect the aggregate 
>> constraint (which will be applied to the "Normalised Bw"). 
>> 
>> So to recap in a nutshell, I believe the generic 
>> "vectorisation" issue you discussed:
>> 	- does not apply to Link Size Overbooking in the 
>> particular case of DS-TE (since Link Size Overbooking does 
>> not need to enforce different overbooking ratios across CT) 
>> and thus we only need a single "Max Res Bw" value
>> 	- does apply to the Local Overbooking Multiplier method 
>> and is/will be reflected by applying the "Normalised Bw" 
>> when applying the aggregate constraint.
>> 
>> Thanks for helping getting to the bottom of this question.
>> 
>> Cheers
>> 
>> Francois
>> 
>> >> -----Original Message-----
>> >> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com] 
>> >> Sent: 23 May 2003 20:58
>> >> To: te-wg@ops.ietf.org
>> >> Cc: Ash, Gerald R (Jerry), ALABS; Dimitry Haskin; Francois 
>> >> Le Faucheur (flefauch)
>> >> Subject: RE: link capacity and reservable
>> >> 
>> >> 
>> >> Thanks to the responses from Jean-Louis, Dimitry, and Francois
>> >> regarding the issue on the use of max link bw versus max
>> >> reservable bw in my previous mesage (contained here at the end).
>> >> 
>> >> The main point underlying the issue that has so far not been
>> >> discussed is this, because of per-CT overbooking, max reservable
>> >> bw should be treated as a vector quantity (as in my previous
>> >> dollar/euro analogy).  Let me illustrate by an example.
>> >> 
>> >> Max link bw = 100 (assuming some bw unit)
>> >> CT1: bw constraint = 80, LSP bw = 10
>> >> CT2: bw constraint = 70, LSP bw =  7
>> >> 
>> >> In this setting (with all the quantities above being normalized
>> >> with respect to link bw), we can accommodate under MAM any one
>> >> of these combinations:
>> >> 8 CT1-LSPs + 2 CT2-LSPs = 94, 7 CT1-LSPs + 4 CT2-LSPs = 98,
>> >> 6 CT1-LSPs + 5 CT2-LSPs = 95, 5 CT1-LSPs + 7 CT2-LSPs = 99,
>> >> 4 CT1-LSPs + 8 CT2-LSPs = 96, 3 CT1-LSPs + 10 CT2-LSPs = 100.
>> >> The aggregate link bw's are all within the max link bw of 100.
>> >> 
>> >> Now consider the usage of reservable bw:
>> >> CT1: overbooking = 2, LSP reserved bw = 2 x 10 = 20
>> >> CT2: overbooking = 4, LSP reserved bw = 4 x  7 = 28
>> >> 
>> >> The corresponding max reservable bw's would be:
>> >> 8 CT1-LSPs + 2 CT2-LSPs = 216
>> >> 7 CT1-LSPs + 4 CT2-LSPs = 252
>> >> 6 CT1-LSPs + 5 CT2-LSPs = 260
>> >> 5 CT1-LSPs + 7 CT2-LSPs = 296
>> >> 4 CT1-LSPs + 8 CT2-LSPs = 304
>> >> 3 CT1-LSPs + 10 CT2-LSPs = 340
>> >> 
>> >> In contrast with max link bw, it's not clear what criterion
>> >> should be used to pick *a single value* from the above list
>> >> and use it as the "aggregate" max reservable bw.  While MAM
>> >> is being used here for illustration, this problem is generic
>> >> and affects RDM as well.
>> >> 
>> >> As pointed out in my previous message, in current TE for
>> >> aggregate traffic, it is possible to define a single
>> >> "aggregate" max reservable bw value, since an average-overall
>> >> can be assumed.  Once different overbooking factors are used
>> >> for different traffic components (e.g., CT's), this is no longer
>> >> the case, and each traffic component has its own max reservable
>> >> bw.  That's what I mean by treating max reservable bw as a vector
>> >> quantity with distinct components.  This fact is actually also
>> >> independent of the type of overbooking methods used, i.e., LOM
>> >> or not LOM.
>> >> 
>> >> Thus, the proper way to do the computation is to first convert
>> >> reservable bw to link bw (or some equivalent normalized quantity),
>> >> and then check against the max link bw (or some equivalent
>> >> normalized quantity).  Checking against the "aggregate" max
>> >> reservable bw is problematic since it is a list and not a single
>> >> value, as shown above.
>> >> 
>> >> Regarding the limit of bandwidth for a single LSP, that's already
>> >> taken care of by the per-CT bw constraint (since it is assumed
>> >> to be normalized).  If folks want to use the max link bw for this
>> >> purpose, it's not precluded by the above consideration either
>> >> (because if the max link bw puts a contraint on the aggregate
>> >> traffic, it certainly puts a contraint on a single LSP).
>> >> 
>> >> Thanks, Wai Sum
>> >> 
>> >> -----Original Message-----
>> >> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>> >> Sent: Tuesday, May 20, 2003 11:52 AM
>> >> To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
>> >> Cc: Ash, Gerald R (Jerry), ALABS
>> >> Subject: RE: link capacity and reservable
>> >> 
>> >> 
>> >> Dimitry,
>> >> 
>> >> >> -----Original Message-----
>> >> >> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> >> >> Sent: 20 May 2003 16:45
>> >> >> To: 'Lai, Wai S (Waisum), ALABS'; te-wg@ops.ietf.org
>> >> >> Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); Ash, 
>> >> >> Gerald R (Jerry), ALABS
>> >> >> Subject: RE: link capacity and reservable
>> >> >> 
>> >> >> 
>> >> >> Waisum, Jerry,
>> >> >> 
>> >> >> IMO, both yours and Francois' formulas for the aggregate 
>> >> reservation
>> >> >> constrain would achieve identical results. 
>> >> 
>> >> I guess you're right that at the end of the day it would be 
>> >> pretty much
>> >> the same thing functionnally.
>> >> 
>> >> >>Note that max 
>> >> >> reservable b/w
>> >> >> constraint is simply applied to the sum of reservations at 
>> >> >> each CT which
>> >> >> already account for individual overbooking factors at each 
>> >> >> CT. However with
>> >> >> the formula that you are proposing we would completely shut 
>> >> >> the door for
>> >> >> other uses of the max link b/w TLV, for instance as a 
>> >> >> constraint on the max
>> >> >> LSP b/w. Since we have already a parameter that was 
>> >> >> explicitly defined as
>> >> >> the aggregate reservation constrain, there is no need to 
>> >> >> close door for a
>> >> >> different use of the max link b/w parameter at this point.
>> >> >> 
>> >> 
>> >> Agreed.
>> >> 
>> >> Thanks
>> >> 
>> >> FRancois
>> >> 
>> >> >> Regards,
>> >> >>   Dimitry  
>> >> >> 
>> >> >> > -----Original Message-----
>> >> >> > From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
>> >> >> > Sent: Monday, May 19, 2003 4:47 PM
>> >> >> > To: te-wg@ops.ietf.org
>> >> >> > Cc: Dimitry Haskin; Francois Le Faucheur (flefauch); 
>> >> Ash, Gerald R
>> >> >> > (Jerry), ALABS
>> >> >> > Subject: link capacity and reservable
>> >> >> > 
>> >> >> > 
>> >> >> > This is in response to the discussion of maximum reservable
>> >> >> > bandwidth in
>> >> >> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00264.html
>> >> >> > http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00265.html
>> >> >> > As the issue is not restricted solely to MAM, and 
>> has impact on
>> >> >> > RDM and in fact all BC models, I am talking about it 
>> in a more
>> >> >> > general context.
>> >> >> > 
>> >> >> > Current TE extension in IGP deals with aggregate traffic.
>> >> >> > There is thus a simple average-overall relationship:
>> >> >> > max link bandwidth = max reservable bandwidth/overbooking.
>> >> >> > As a result, whether "max link bandwidth" is supported or
>> >> >> > commonly used or not is immaterial.
>> >> >> > 
>> >> >> > In DS-TE, there is per-CT bandwidth contstraint and per-CT
>> >> >> > overbooking.  Max reservable bandwidth should accordingly be
>> >> >> > treated as a vector quantity.  Reflecting this view, the
>> >> >> > following definition for MAM in <tewg-diff-te-reqts> is
>> >> >> > adequate:
>> >> >> >   for each value of b in the range 0 <= b <= 7:
>> >> >> >     Reserved (CTb) <= BCb
>> >> >> > (with some clarification in MAM spec regarding overbooking)
>> >> >> > 
>> >> >> > Also, the following additional condition for MAM 
>> definition as
>> >> >> > proposed in the second message quoted above is both 
>> unneccsary
>> >> >> > and incorrect:
>> >> >> >   SUM (Reserved (CTc)) <= Max Reservable Bandwidth
>> >> >> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> >> > 
>> >> >> > This is like when I have 15 dollars and 10 euros in 
>> my pocket,
>> >> >> > then my max reserve is 25 (of what unit).
>> >> >> > 
>> >> >> > The "max link bandwidth," being a normalized 
>> quantity, is more
>> >> >> > meaningful.  For admission control under MAM, in addition to
>> >> >> > the observing the bandwidth constraints as specified in the
>> >> >> > above deinition, something like the following may be used:
>> >> >> >   SUM (Reserved (CTc)/overbooking(CTc)) <= Max Link Bandwidth
>> >> >> >     for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> >> > (with some tweaks to account for priorities)
>> >> >> > 
>> >> >> > Thanks, Wai Sum
>> >> >> > 
>> >> >> 
>> >> 
>> 



From owner-te-wg@ops.ietf.org  Mon May 26 08:59:59 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10620
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 08:59:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KHZH-000O4J-00
	for te-wg-data@psg.com; Mon, 26 May 2003 12:59:11 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KHYs-000O3n-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 12:58:46 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 May 2003 14:58:03 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4QCulvZ015741;
	Mon, 26 May 2003 14:56:48 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 26 May 2003 14:58:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Mon, 26 May 2003 13:58:41 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B523A@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMhi9GwxDxJUyNeQZu6Rf0Jhhch/AB9wv1w
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Kireeti Kompella" <kireeti@juniper.net>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 26 May 2003 12:58:41.0529 (UTC) FILETIME=[88448E90:01C32386]
X-Spam-Status: No, hits=-9.6 required=5.0
	tests=BAYES_10,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA10620

Kireeti,

Once upon a time, we merged 3 technical proposals for DS-TE (one of
which was yours) into a common one. One of the capabilities that was
unique to your proposal was the ability to support overbooking ratios
which are different on a per CT AND per link basis (while the other
methods supported different ratios on different links and different
ratios on a per CT basis, not not on a per CT and per-link basis). Back
then you made a argument that there was some value in allowing this.
This resulted in the addition of the optional Local Overbooking
Multiplier (LOM) method in the DS-TE specs.

A number of people commented that considering the ratio of complexity vs
functionality for this particular capability, we may be better off
issueing the base DS-TE specs without this for now and then add this
capability later or in a separate document. I personnally also favors
such an approach.

What is your take on this?

Cheers

Francois

>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com] 
>> Sent: 24 May 2003 02:31
>> To: Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 
>> 
>> 
<clip>
>> 
>> btw... I also think LOMs are lots of complexity for little gain :)
>> 
>> 
>> 
>> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
>> 
>> > Jerry,
>> > 
>> > >> -----Original Message-----
>> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> > >> Sent: 20 May 2003 17:35
>> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> > >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> > >> Wai S (Waisum), ALABS
>> > >> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> > >> 
>> > >> 
>> > >> Dimitry, Francois,
>> > >> 
>> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> > > 
>> > >> > > However, this formula is incorrect for DS-TE when per-CT 
>> > >> > > LOM's are used, since the above formula only 
>> reflects the Max 
>> > >> > > Reservable Bandwidth for the entire link, and does not 
>> > >> > > reflect the per-CT local overbooking factors.  So what 
>> > >> > > formula do you suggest when per-CT LOM's are used?
>> > >> 
>> > >> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> > >> accounts for the
>> > >> > overbooking multiplier at CTc?  I don't see how this 
>> > >> formula precludes
>> > >> > per-CT LOM's to be used. Please explain.
>> > >> 
>> > >> Are you then proposing these formulas:
>> > >> 
>> > >> 1. When per-CT LOMs are not used:
>> > >> 
>> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> 
>> > >> 2. When per-CT LOMs are used:
>> > >> 
>> > >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> 
>> > >> Is that correct?  Please confirm, and/or give the formulas 
>> > >> you propose.
>> > 
>> > Yes, this is exactly what I propose.
>> > I think this is similar to what you were proposing, only 
>> using "Max Res
>> > Bw" instead of "Max Link Bw". 
>> > 
>> > Sorry I didn't make that very clear before.
>> > 
>> > Cheers
>> > 
>> > FRancois
>> > 
>> > >> 
>> > >> Thanks,
>> > >> Jerry
>> > >> 
>> > 
>> > 
>> > 
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Mon May 26 09:05:04 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10718
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 09:05:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KHec-000OJS-00
	for te-wg-data@psg.com; Mon, 26 May 2003 13:04:42 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KHeZ-000OJE-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 13:04:39 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 May 2003 15:03:57 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4QD2SLl016840;
	Mon, 26 May 2003 15:02:41 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 26 May 2003 15:04:32 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 
Date: Mon, 26 May 2003 14:04:32 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B523B@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts 
Thread-Index: AcMhi9GwxDxJUyNeQZu6Rf0Jhhch/AB+tz/A
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Jim Boyle" <jboyle@pdnets.com>
Cc: <te-wg@ops.ietf.org>, "Lai, Wai S , ALABS" <wlai@att.com>
X-OriginalArrivalTime: 26 May 2003 13:04:32.0953 (UTC) FILETIME=[59BB9A90:01C32387]
X-Spam-Status: No, hits=-9.0 required=5.0
	tests=BAYES_10,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA10718

Hi Jim,

>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com] 
>> Sent: 24 May 2003 02:31
>> To: Francois Le Faucheur (flefauch)
>> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
>> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 
>> 
>> 
>> 
>> So is there agreement now?
>> 

Working on it. Almost there (I think).

>> If so, what's the fallout?
>> 
>> I don't want to pull the reqt's out of IESG, and as stated 
>> in the list, it 
>> isnt the place MAM is defined (sorry SAM, I think we have 
>> enough bandwidth 
>> models).

Alright. It seems the potential inconsistency I was worrying about
between the current MAM definition in -rqts and the upcoming MAM spec
isn't such a worry for most people, so let's take the easiest path:
	- leave -reqts as it is
	- keep the MAM name for the MAM spec and update the definition
in there.

>> 
>> Francois, can you re-propose changes for proto, RDM and MAM?
>>

Will try do as soon as we have closed on the overbooking discussion (and
perhaps also on the removal/keeping of LOM).

Thanks

Francois
 
>> thanks,
>> 
>> Jim
>> 
>> btw... I also think LOMs are lots of complexity for little gain :)
>> 
>> 
>> 
>> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
>> 
>> > Jerry,
>> > 
>> > >> -----Original Message-----
>> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> > >> Sent: 20 May 2003 17:35
>> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> > >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> > >> Wai S (Waisum), ALABS
>> > >> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
>> > >> 
>> > >> 
>> > >> Dimitry, Francois,
>> > >> 
>> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> > > 
>> > >> > > However, this formula is incorrect for DS-TE when per-CT 
>> > >> > > LOM's are used, since the above formula only 
>> reflects the Max 
>> > >> > > Reservable Bandwidth for the entire link, and does not 
>> > >> > > reflect the per-CT local overbooking factors.  So what 
>> > >> > > formula do you suggest when per-CT LOM's are used?
>> > >> 
>> > >> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> > >> accounts for the
>> > >> > overbooking multiplier at CTc?  I don't see how this 
>> > >> formula precludes
>> > >> > per-CT LOM's to be used. Please explain.
>> > >> 
>> > >> Are you then proposing these formulas:
>> > >> 
>> > >> 1. When per-CT LOMs are not used:
>> > >> 
>> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> 
>> > >> 2. When per-CT LOMs are used:
>> > >> 
>> > >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> 
>> > >> Is that correct?  Please confirm, and/or give the formulas 
>> > >> you propose.
>> > 
>> > Yes, this is exactly what I propose.
>> > I think this is similar to what you were proposing, only 
>> using "Max Res
>> > Bw" instead of "Max Link Bw". 
>> > 
>> > Sorry I didn't make that very clear before.
>> > 
>> > Cheers
>> > 
>> > FRancois
>> > 
>> > >> 
>> > >> Thanks,
>> > >> Jerry
>> > >> 
>> > 
>> > 
>> > 
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Mon May 26 09:05:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10736
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 09:05:25 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KHfD-000OLl-00
	for te-wg-data@psg.com; Mon, 26 May 2003 13:05:19 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KHfB-000OLX-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 13:05:17 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 26 May 2003 15:04:34 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4QD33gB016936
	for <te-wg@ops.ietf.org>; Mon, 26 May 2003 15:03:19 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 26 May 2003 15:05:15 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Mon, 26 May 2003 14:05:15 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B95B8@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMhi9GwxDxJUyNeQZu6Rf0Jhhch/AB9wv1wAAEfiqA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 26 May 2003 13:05:15.0954 (UTC) FILETIME=[735D0920:01C32387]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA10736

All TEWGers,

Thoughts on dropping/keeping LOM in base DS-TE specs?

Thanks

Francois

>> -----Original Message-----
>> From: Francois Le Faucheur (flefauch) 
>> Sent: 26 May 2003 14:59
>> To: Kireeti Kompella; te-wg@ops.ietf.org
>> Subject: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> Kireeti,
>> 
>> Once upon a time, we merged 3 technical proposals for DS-TE (one of
>> which was yours) into a common one. One of the capabilities that was
>> unique to your proposal was the ability to support overbooking ratios
>> which are different on a per CT AND per link basis (while the other
>> methods supported different ratios on different links and different
>> ratios on a per CT basis, not not on a per CT and per-link 
>> basis). Back
>> then you made a argument that there was some value in allowing this.
>> This resulted in the addition of the optional Local Overbooking
>> Multiplier (LOM) method in the DS-TE specs.
>> 
>> A number of people commented that considering the ratio of 
>> complexity vs
>> functionality for this particular capability, we may be better off
>> issueing the base DS-TE specs without this for now and then add this
>> capability later or in a separate document. I personnally also favors
>> such an approach.
>> 
>> What is your take on this?
>> 
>> Cheers
>> 
>> Francois
>> 
>> >> -----Original Message-----
>> >> From: Jim Boyle [mailto:jboyle@pdnets.com] 
>> >> Sent: 24 May 2003 02:31
>> >> To: Francois Le Faucheur (flefauch)
>> >> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
>> >> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts 
>> >> 
>> >> 
>> <clip>
>> >> 
>> >> btw... I also think LOMs are lots of complexity for little gain :)
>> >> 
>> >> 
>> >> 
>> >> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
>> >> 
>> >> > Jerry,
>> >> > 
>> >> > >> -----Original Message-----
>> >> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> >> > >> Sent: 20 May 2003 17:35
>> >> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> >> > >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
>> >> > >> Wai S (Waisum), ALABS
>> >> > >> Subject: RE: Reflecting new-MAM/SAM definition in 
>> diff-te drafts
>> >> > >> 
>> >> > >> 
>> >> > >> Dimitry, Francois,
>> >> > >> 
>> >> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
>> >> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> > >> > > 
>> >> > >> > > However, this formula is incorrect for DS-TE when per-CT 
>> >> > >> > > LOM's are used, since the above formula only 
>> >> reflects the Max 
>> >> > >> > > Reservable Bandwidth for the entire link, and does not 
>> >> > >> > > reflect the per-CT local overbooking factors.  So what 
>> >> > >> > > formula do you suggest when per-CT LOM's are used?
>> >> > >> 
>> >> > >> > Wouldn't 'Reserved (CTc)' it the above formula already 
>> >> > >> accounts for the
>> >> > >> > overbooking multiplier at CTc?  I don't see how this 
>> >> > >> formula precludes
>> >> > >> > per-CT LOM's to be used. Please explain.
>> >> > >> 
>> >> > >> Are you then proposing these formulas:
>> >> > >> 
>> >> > >> 1. When per-CT LOMs are not used:
>> >> > >> 
>> >> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> > >> 
>> >> > >> 2. When per-CT LOMs are used:
>> >> > >> 
>> >> > >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
>> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> >> > >> 
>> >> > >> Is that correct?  Please confirm, and/or give the formulas 
>> >> > >> you propose.
>> >> > 
>> >> > Yes, this is exactly what I propose.
>> >> > I think this is similar to what you were proposing, only 
>> >> using "Max Res
>> >> > Bw" instead of "Max Link Bw". 
>> >> > 
>> >> > Sorry I didn't make that very clear before.
>> >> > 
>> >> > Cheers
>> >> > 
>> >> > FRancois
>> >> > 
>> >> > >> 
>> >> > >> Thanks,
>> >> > >> Jerry
>> >> > >> 
>> >> > 
>> >> > 
>> >> > 
>> >> > 
>> >> 
>> >> 
>> 
>> 



From owner-te-wg@ops.ietf.org  Mon May 26 09:34:12 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11402
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 09:34:11 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KI5X-000PYZ-00
	for te-wg-data@psg.com; Mon, 26 May 2003 13:32:31 +0000
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KI5U-000PYK-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 13:32:28 +0000
Received: from toque.cisco.com (IDENT:mirapoint@toque.cisco.com [161.44.201.11])
	by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h4QDWOAV025419;
	Mon, 26 May 2003 06:32:25 -0700 (PDT)
Received: from msiva-w2k01.cisco.com (dhcp-kta1-161-44-193-233.cisco.com [161.44.193.233])
	by toque.cisco.com (Mirapoint)
	with ESMTP id ADY00371;
	Mon, 26 May 2003 09:21:24 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030526092612.02029720@toque.cisco.com>
X-Sender: msiva@toque.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 26 May 2003 09:32:22 -0400
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
From: "Siva Sivabalan (msiva)" <msiva@cisco.com>
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method
  from DS-TE specs?
Cc: <te-wg@ops.ietf.org>
In-Reply-To: <AC60B39EEE7320498063D37799FB82D93B95B8@xbe-lon-313.cisco.c
 om>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-25.2 required=5.0
	tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REPLY_WITH_QUOTES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Francois,

I would also think LOM adds extra complexity for a little gain. So,
you may want to avoid LOM in DS-TE spec for now. Its usefulness
can be evaluated in the future as we gain experience with DS-TE.

Thanks,
Siva

At 02:05 PM 5/26/2003 +0100, Francois Le Faucheur (flefauch) wrote:
>All TEWGers,
>
>Thoughts on dropping/keeping LOM in base DS-TE specs?
>
>Thanks
>
>Francois
>
> >> -----Original Message-----
> >> From: Francois Le Faucheur (flefauch)
> >> Sent: 26 May 2003 14:59
> >> To: Kireeti Kompella; te-wg@ops.ietf.org
> >> Subject: Dropping the Local Overbooking Multiplier (LOM)
> >> method from DS-TE specs?
> >>
> >>
> >> Kireeti,
> >>
> >> Once upon a time, we merged 3 technical proposals for DS-TE (one of
> >> which was yours) into a common one. One of the capabilities that was
> >> unique to your proposal was the ability to support overbooking ratios
> >> which are different on a per CT AND per link basis (while the other
> >> methods supported different ratios on different links and different
> >> ratios on a per CT basis, not not on a per CT and per-link
> >> basis). Back
> >> then you made a argument that there was some value in allowing this.
> >> This resulted in the addition of the optional Local Overbooking
> >> Multiplier (LOM) method in the DS-TE specs.
> >>
> >> A number of people commented that considering the ratio of
> >> complexity vs
> >> functionality for this particular capability, we may be better off
> >> issueing the base DS-TE specs without this for now and then add this
> >> capability later or in a separate document. I personnally also favors
> >> such an approach.
> >>
> >> What is your take on this?
> >>
> >> Cheers
> >>
> >> Francois
> >>
> >> >> -----Original Message-----
> >> >> From: Jim Boyle [mailto:jboyle@pdnets.com]
> >> >> Sent: 24 May 2003 02:31
> >> >> To: Francois Le Faucheur (flefauch)
> >> >> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
> >> >> Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
> >> >>
> >> >>
> >> <clip>
> >> >>
> >> >> btw... I also think LOMs are lots of complexity for little gain :)
> >> >>
> >> >>
> >> >>
> >> >> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
> >> >>
> >> >> > Jerry,
> >> >> >
> >> >> > >> -----Original Message-----
> >> >> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >> >> > >> Sent: 20 May 2003 17:35
> >> >> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
> >> >> > >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai,
> >> >> > >> Wai S (Waisum), ALABS
> >> >> > >> Subject: RE: Reflecting new-MAM/SAM definition in
> >> diff-te drafts
> >> >> > >>
> >> >> > >>
> >> >> > >> Dimitry, Francois,
> >> >> > >>
> >> >> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable Bandwidth,
> >> >> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
> >> >> > >> > >
> >> >> > >> > > However, this formula is incorrect for DS-TE when per-CT
> >> >> > >> > > LOM's are used, since the above formula only
> >> >> reflects the Max
> >> >> > >> > > Reservable Bandwidth for the entire link, and does not
> >> >> > >> > > reflect the per-CT local overbooking factors.  So what
> >> >> > >> > > formula do you suggest when per-CT LOM's are used?
> >> >> > >>
> >> >> > >> > Wouldn't 'Reserved (CTc)' it the above formula already
> >> >> > >> accounts for the
> >> >> > >> > overbooking multiplier at CTc?  I don't see how this
> >> >> > >> formula precludes
> >> >> > >> > per-CT LOM's to be used. Please explain.
> >> >> > >>
> >> >> > >> Are you then proposing these formulas:
> >> >> > >>
> >> >> > >> 1. When per-CT LOMs are not used:
> >> >> > >>
> >> >> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth,
> >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> >> > >>
> >> >> > >> 2. When per-CT LOMs are used:
> >> >> > >>
> >> >> > >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth,
> >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> >> > >>
> >> >> > >> Is that correct?  Please confirm, and/or give the formulas
> >> >> > >> you propose.
> >> >> >
> >> >> > Yes, this is exactly what I propose.
> >> >> > I think this is similar to what you were proposing, only
> >> >> using "Max Res
> >> >> > Bw" instead of "Max Link Bw".
> >> >> >
> >> >> > Sorry I didn't make that very clear before.
> >> >> >
> >> >> > Cheers
> >> >> >
> >> >> > FRancois
> >> >> >
> >> >> > >>
> >> >> > >> Thanks,
> >> >> > >> Jerry
> >> >> > >>
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >>
> >>




From owner-te-wg@ops.ietf.org  Mon May 26 16:52:54 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26645
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 16:52:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KOu9-0004l2-00
	for te-wg-data@psg.com; Mon, 26 May 2003 20:49:13 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KOu6-0004ha-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 20:49:10 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4QKm6xt013072
	for <te-wg@ops.ietf.org>; Mon, 26 May 2003 15:49:09 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020028BD0B; Mon, 26 May 2003 16:49:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: link capacity and reservable
Date: Mon, 26 May 2003 15:49:08 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67DC@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+QAGnzyQAAuRfBcAAUYYvg
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA26645

Francois,

I must say that there seems to be an over-complexity of over-booking options in DS-TE.  What is making this discussion over-ly confusing for me is that I think your explanation reversed the use of 'Link Size Overbooking' and 'LSP Size Overbooking' a couple of times.  Please check below between the ** marks where I've substituted what I thought was the correct explanation and/or term.

Sorry to add confusion if this 'correction' is incorrect :-)

Also, your discussion implies that LSP Size Overbooking and Link Size Overbooking are used individually, but not together.  If so, why can't they (or shouldn't they) be used together?

Thanks,
Jerry

I believe there was clear agreement that:
	- there was a strong need for SPs to be able to apply, on a
network wide basis, a different level of overbooking for different CTs
(typically high overbooking on best-effort, low/no overbooking on
premium/voice)
*	- this was well supported by the "LSP Size Overbooking" method
(which allows different overbooking per CT - it even offers finer
granularity of per-LSP overbooking)*
	- there was a strong need for SPs to be able to apply a
different level of overbooking on differnet links (typically higher
overbooking on higher speed links)
*	- this was well supported by the "Link Size Overbooking" method
(effectively just pretending to have a bigger link than the real one ;
and thus effectively applying a single per link overbooking which is
COMMON to all CTs)*
	- there was only a weak potential need for being able to apply
different overbooking ratios which need to be different for each CT on
different links.
	- this should be OPTIONAL
	- this would be well supported by the per-CT Local Overbooking
Multiplier.

A related conclusion of the above is that the "Link Size Overbooking"
method does NOT need to enforce different overbooking ratios for
different CTs. If the SP needs different overbooking ratios for
different CTs, then, in the context of DS-TE, this can be achieved via
the "LSP Size Overbooking" method.

Since the "Max Reservable Bandwidth" is involved only in the "*Link* Size
Overbooking" method, it does NOT need to enforce a different level of
overbooking for different CTs; enforcing the same one across all CTs is
all what's required. This means that, taking into account the specific
environment of DS-TE, the aggregate constraint does not need to be
vectorised (although I agree that in a completely generic world it would
have to).

Now, in the case where the SP wants to enforce different overbooking
ratios for different CTs on different links, then this needs to be
achieved via the LOMs (and not via the "Link Size Overbooking"). Then
the LOMs need to be applied individually to each CT which effectively
results in the vectorisation you described. This will be reflected in
the CAC formulas when updated to reflect the aggregate constraint (which
will be applied to the "Normalised Bw"). 

So to recap in a nutshell, I believe the generic "vectorisation" issue
you discussed:
	- does not apply to Link Size Overbooking in the particular case
of DS-TE (since Link Size Overbooking does not need to enforce different
overbooking ratios across CT) and thus we only need a single "Max Res
Bw" value
	- does apply to the Local Overbooking Multiplier method and
is/will be reflected by applying the "Normalised Bw" when applying the
aggregate constraint.



From owner-te-wg@ops.ietf.org  Mon May 26 16:53:35 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26682
	for <tewg-archive@lists.ietf.org>; Mon, 26 May 2003 16:53:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KOy4-0005x1-00
	for te-wg-data@psg.com; Mon, 26 May 2003 20:53:16 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KOy2-0005wd-00
	for te-wg@ops.ietf.org; Mon, 26 May 2003 20:53:14 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4QKm60I013072
	for <te-wg@ops.ietf.org>; Mon, 26 May 2003 15:53:13 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020028BEBE; Mon, 26 May 2003 16:53:13 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Mon, 26 May 2003 15:53:13 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE945@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMhi9GwxDxJUyNeQZu6Rf0Jhhch/AB9wv1wAAEfiqAAEDxKwA==
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA26682

Francois,

> Thoughts on dropping/keeping LOM in base DS-TE specs?

I certainly favor dropping LOM if there is only weak justification.  There seems to be ample flexibility in overbooking with both 'Link Size Overbooking' and 'LSP Size Overbooking' options available.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue May 27 04:44:33 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04510
	for <tewg-archive@lists.ietf.org>; Tue, 27 May 2003 04:44:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Ka11-000AfE-00
	for te-wg-data@psg.com; Tue, 27 May 2003 08:41:03 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Ka0t-000AaF-00
	for te-wg@ops.ietf.org; Tue, 27 May 2003 08:40:55 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 27 May 2003 10:40:06 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4R8cpFa022289;
	Tue, 27 May 2003 10:38:53 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 27 May 2003 10:40:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Tue, 27 May 2003 09:40:39 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5241@xbe-lon-313.cisco.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+QAGnzyQAAuRfBcAAUYYvgABg+QAA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 27 May 2003 08:40:48.0281 (UTC) FILETIME=[ABE80890:01C3242B]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA04510

Hello Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 26 May 2003 22:49
>> To: Francois Le Faucheur (flefauch)
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Francois,
>> 
>> I must say that there seems to be an over-complexity of 
>> over-booking options in DS-TE.  What is making this 
>> discussion over-ly confusing for me is that I think your 
>> explanation reversed the use of 'Link Size Overbooking' and 
>> 'LSP Size Overbooking' a couple of times.  Please check 
>> below between the ** marks where I've substituted what I 
>> thought was the correct explanation and/or term.
>> 
>> Sorry to add confusion if this 'correction' is incorrect :-)
>> 

You are absolutely correct that I did swap "LSP"/"Link". How silly is
that ... right in the middle of a text attempting to clarify things...
Thanks a lot for correcting it. Hope this removes the "over-confusion".

>> Also, your discussion implies that LSP Size Overbooking and 
>> Link Size Overbooking are used individually, but not 
>> together.  If so, why can't they (or shouldn't they) be used 
>> together?
>> 

I absolutely agree that "LSP Size Overbooking" and "Link Size
Overbooking" can be used simultaneously (I like that sentence because
even if I swap "LSP"/"Link" it is still correct 8^)).
This allows to simultaneously enforce overbooking ratios on a
per-CT-basis (eg. CT0 is overbooked by factor 2, CT1 is not overbooked)
and overbooking ratios on a per-link-basis (ie link0 is overbooked by
factor 1.3 and link1 is overbooked by factor 1.1). 

My point below was about enforcing overbooking ratios on a
per-CT-and-per-link basis (ie CT0 is overbooked by factor 2 on link 0
and overbooked by factor 3 on link 1, while CT1 is not overbooked on
link0 nor on link1). This could NOT be achieved just by combination of
"LSP Size overbooking" and "Link Size Overbooking"; it could only be
achieved via the use of the LOM method. But, as being discussed, it is
not obvious that the nbeed for this justifies the extra complexity.

Thank you

Francois

>> Thanks,
>> Jerry
>> 
>> I believe there was clear agreement that:
>> 	- there was a strong need for SPs to be able to apply, on a
>> network wide basis, a different level of overbooking for 
>> different CTs
>> (typically high overbooking on best-effort, low/no overbooking on
>> premium/voice)
>> *	- this was well supported by the "LSP Size Overbooking" method
>> (which allows different overbooking per CT - it even offers finer
>> granularity of per-LSP overbooking)*
>> 	- there was a strong need for SPs to be able to apply a
>> different level of overbooking on differnet links (typically higher
>> overbooking on higher speed links)
>> *	- this was well supported by the "Link Size Overbooking" method
>> (effectively just pretending to have a bigger link than the 
>> real one ;
>> and thus effectively applying a single per link overbooking which is
>> COMMON to all CTs)*
>> 	- there was only a weak potential need for being able to apply
>> different overbooking ratios which need to be different for 
>> each CT on
>> different links.
>> 	- this should be OPTIONAL
>> 	- this would be well supported by the per-CT Local Overbooking
>> Multiplier.
>> 
>> A related conclusion of the above is that the "Link Size Overbooking"
>> method does NOT need to enforce different overbooking ratios for
>> different CTs. If the SP needs different overbooking ratios for
>> different CTs, then, in the context of DS-TE, this can be 
>> achieved via
>> the "LSP Size Overbooking" method.
>> 
>> Since the "Max Reservable Bandwidth" is involved only in the 
>> "*Link* Size
>> Overbooking" method, it does NOT need to enforce a different level of
>> overbooking for different CTs; enforcing the same one across 
>> all CTs is
>> all what's required. This means that, taking into account 
>> the specific
>> environment of DS-TE, the aggregate constraint does not need to be
>> vectorised (although I agree that in a completely generic 
>> world it would
>> have to).
>> 
>> Now, in the case where the SP wants to enforce different overbooking
>> ratios for different CTs on different links, then this needs to be
>> achieved via the LOMs (and not via the "Link Size Overbooking"). Then
>> the LOMs need to be applied individually to each CT which effectively
>> results in the vectorisation you described. This will be reflected in
>> the CAC formulas when updated to reflect the aggregate 
>> constraint (which
>> will be applied to the "Normalised Bw"). 
>> 
>> So to recap in a nutshell, I believe the generic 
>> "vectorisation" issue
>> you discussed:
>> 	- does not apply to Link Size Overbooking in the particular case
>> of DS-TE (since Link Size Overbooking does not need to 
>> enforce different
>> overbooking ratios across CT) and thus we only need a single "Max Res
>> Bw" value
>> 	- does apply to the Local Overbooking Multiplier method and
>> is/will be reflected by applying the "Normalised Bw" when 
>> applying the
>> aggregate constraint.
>> 



From owner-te-wg@ops.ietf.org  Tue May 27 05:28:44 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05691
	for <tewg-archive@lists.ietf.org>; Tue, 27 May 2003 05:28:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KajC-000JS0-00
	for te-wg-data@psg.com; Tue, 27 May 2003 09:26:42 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Kaj8-000JOd-00
	for te-wg@ops.ietf.org; Tue, 27 May 2003 09:26:39 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 27 May 2003 11:25:55 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4R9OeeJ001368
	for <te-wg@ops.ietf.org>; Tue, 27 May 2003 11:24:40 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 27 May 2003 11:26:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: DS-TE overbooking model - Not that complicated
Date: Tue, 27 May 2003 10:26:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5242@xbe-lon-313.cisco.com>
Thread-Topic: DS-TE overbooking model - Not that complicated
Thread-Index: AcMe3omngfieWX17RmG2C9lCOLygEQACPR+QAGnzyQAAuRfBcAAUYYvgABixJxA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 27 May 2003 09:26:37.0221 (UTC) FILETIME=[1266FD50:01C32432]
X-Spam-Status: No, hits=-5.8 required=5.0
	tests=BAYES_10
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA05691

Hello,

We have been through fairly detailed discussions on the overbooking
models, which I believe have been very useful to synch up. This involved
a lot of synching up on various terminology and concepts that come to
mind to each of us (only in slightly different form for each individual)
on the topic of overbooking. This may have generated a perception that
the overbooking model for DS-TE is fairly complex. I would like to
address this potential perception and make the case that the overbooking
model actually selected for DS-TE is (i) quite simple and (ii)
structured as minimum possible increment over existing TE overbooking
model.

Again, the DS-TE overbooking model has:
	*  two MANDATORY components :
		-A- LSP Size Overbooking
		-B- Link Size Overbooking
	* and one OPTIONAL component:
		-C- Local Overbooking Multiplier

The two main and mandatory components are actually an integral part of
the existing TE. Just they never got discussed that much explicitely in
existing TE documents, but they are fully part of TE. They are commonly
used in TE live deployments today. They have just been inherited by
DS-TE and we applied them in the exact same way. Only, they got
discussed more explicitely (eg when doing the exercise of providing CAC
formulas and "Unreserved Bw" formulas) to ensure they were understood
consistently in the context of multiple CTs. 
Note also that like with existing TE, -A- and -B- don't result in any
specific protocol extensions (ie you would have the exact same
extensions even if you decided to not support Link/LSP Size
Overbooking).
So I can't see how we could do any simpler here, short of losing
overbooking functionality as compared to existing TE.

The third component is the only one where additional complexity over
existing TE really comes in. But this all hinges on the potential
requirement for overbooking ratios on a per-CT-and-per-link basis which
was identified at some stage as a potential requirements. If there is
such a requirement, we do need something beyond Link/LSP Sie
Overbooking; no way around it. Rather than re-invent a complete
overbooking model for DS-TE, the LOM method is structured as a pure
optional increment over Link/LSP overbooking to address this
requirement. This is purely optional anyway (and may even be removed, as
being currently discussed).

So, in summary, :
	- the mandatory components of the DS-TE overbooking model are
strictly identical to the ones of existing TE (no more, no less)
	- the one optional component is structured as a pure increment
over the other components, and is required to provide a specifc DS-TE
functionality identified as (potential) requirement. If the requirement
is dropped, this component can also be dropped (we would then be left
with an overbooking model for DS-TE which is strictly identical to the
overbooking model of existing TE).

Hope this is useful.

Cheers

Francois



From owner-te-wg@ops.ietf.org  Tue May 27 11:43:23 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17428
	for <tewg-archive@lists.ietf.org>; Tue, 27 May 2003 11:43:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KgX9-0000VA-00
	for te-wg-data@psg.com; Tue, 27 May 2003 15:38:39 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KgWt-0000RK-00
	for te-wg@ops.ietf.org; Tue, 27 May 2003 15:38:23 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F650@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: te-wg@ops.ietf.org
Subject: RE: link capacity and reservable
Date: Tue, 27 May 2003 11:37:20 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-9.0 required=5.0
	tests=BAYES_10,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Francois,

> My point below was about enforcing overbooking ratios on a
> per-CT-and-per-link basis (ie CT0 is overbooked by factor 2 on link 0
> and overbooked by factor 3 on link 1, while CT1 is not overbooked on
> link0 nor on link1). This could NOT be achieved just by combination of
> "LSP Size overbooking" and "Link Size Overbooking"; it could only be
> achieved via the use of the LOM method. But, as being discussed, it is
> not obvious that the nbeed for this justifies the extra complexity.
>

For my sake.. Since b/w constrains are advertised and handled per CT per TE
link (i.e. there are separate BCn values on each visible link in a TE
domain), why is LOM necessary to achieve overbooking per  CT per link?  Or
is it that link0 and link1 in your example form a some kind link bundle, i.e
form a single TE link as far as OSPF/ISIS TE extensions are concerned?

Thanks,
 Dimitry




From owner-te-wg@ops.ietf.org  Tue May 27 16:50:43 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01685
	for <tewg-archive@lists.ietf.org>; Tue, 27 May 2003 16:50:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KlN2-000NKm-00
	for te-wg-data@psg.com; Tue, 27 May 2003 20:48:32 +0000
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KlMt-000NJz-00
	for te-wg@ops.ietf.org; Tue, 27 May 2003 20:48:23 +0000
Received: from 146-115-64-2.c3-0.bkl-ubr2.sbo-bkl.ma.cable.rcn.com ([146.115.64.2] helo=DASEP)
	by smtp02.mrf.mail.rcn.net with esmtp (Exim 3.35 #4)
	id 19KlMt-0002Bd-00; Tue, 27 May 2003 16:48:23 -0400
From: "sanford goldfless" <sandy9@rcn.com>
To: "'Francois Le Faucheur \(flefauch\)'" <flefauch@cisco.com>
Cc: <te-wg@ops.ietf.org>
Subject: RE: DS-TE overbooking model - Not that complicated
Date: Tue, 27 May 2003 16:48:35 -0400
Message-ID: <000001c32491$57b20c10$6401a8c0@DASEP>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
In-Reply-To: <AC60B39EEE7320498063D37799FB82D93B5242@xbe-lon-313.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-15.3 required=5.0
	tests=BAYES_10,IN_REP_TO,ORIGINAL_MESSAGE
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Francois, all --

Before closing the door on LOMs, I'd like to ask that we address the
following  issues for completeness in stating the DS-TE overbooking
model. (Hope this isn't too big a post.)

1) A precise definition of "per-CT overbooking".  Link overbooking
allows total reservation to exceed the link size.  Which quantity does
CT overbooking exceed:  the expected load for the CT?  the advertised
admission constraint for the CT?  or perhaps any current reservation for
the CT, whenever the reservation total for all CTs has reached Max Link
(i.e., admission for certain CTs is closed whenever the link becomes
overbooked)? 

I think that what we've been talking about so far is accepting
reservations that exceed the expected load for the CT. 
  
2) An explicit statement on overbooking and BC usage. The nested values
in the RD BC model are primarily for bandwidth sharing among CTs, rather
than for "overbooking" as such.  However, BCs in RDM implicitly
advertise limits on link overbooking, since they are aggregate
bandwidths across sets of CTs, which may or may not exceed the link
size. In fact, the value for the total set, BC0, has the same semantic
as Max Reservable, as you say.  Max Reservable expresses the link
overbooking factor.

Would it be too much of a change to add a per-CT capability directly to
this overbooking semantic for the RD model? In order to allow different
CTs to exceed their expected loads to differing degrees, let the user
simply include the allowed excess in each case within the appropriate BC
value.  For example, on a link where Max Link = 100, Max Reservable =
150, and there are two CTs, one voice one data, to allow data to
overbook its expected load but not voice, set BC1 = 50 and BC0 = 150
when the expected load is 50 for each.

For MAM, the current definition update doesn't currently have a
reference to allowed overbooking in respect to BC values (although it
does in respect to total reservation).  But as for RDM, adding the
explicit option to include an overbooking allowance in each BC doesn't
appear to contradict the MAM definition.  

As BCs are by definition advertised (and set) per link, DS-TE would have
a per-link-per-CT overbooking capability through them, if this is
correct.  

3) A precise definition of LSP Size Overbooking. I think this is the
general understanding: In LSP Size Overbooking, LSPs of a class that can
be overbooked reserve less than their corresponding service
specifications explicitly call for, so that enough LSPs of that class
can be accepted until the capacity held for the expected load is
reached.  Anything more?

4) LSP Size Overbooking and DiffServ resources.  That it is suitable for
a network-wide approach to per-CT overbooking but not to a per-link
approach  seems to me not to be the only drawback in LSP Size
Overbooking . It also upsets the relationship between bw reservation
signaling and real-time adjustment to scheduling parameters that some
networks want to maintain. 

This is especially so when LSPs within a particular CT may vary greatly
in size and where a single LSP in that CT can reserve an amount that is
significant to the scheduler's ability to guarantee bw to the CT as a
whole. Sure, *after* the entire set of LSPs for a CT have been set up,
the end result might be the same as using LOMs:  CAC will allow enough
LSPs in so that the actual load on the CT will approach the expected
load.

But to guarantee minimum bw for an LSP or for a CT as its LSPs are set
up over time, there's got to be a way for upstream nodes to learn the
LSP under-sizing factor that is in use. 

I'm hoping that instead of LOMs and instead of LSP under-sizing, BC
over-sizing will be deemed sufficient to support "per-CT overbooking"!

Thanks,
Sandy
  
Sanford Goldfless
192 Fuller St
Brookline MA 02446
617-738-1754
sandy9@rcn.com


-----Original Message-----
From: owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org] On
Behalf Of Francois Le Faucheur (flefauch)
Sent: Tuesday, May 27, 2003 5:27 AM
To: te-wg@ops.ietf.org
Subject: DS-TE overbooking model - Not that complicated

Hello,

We have been through fairly detailed discussions on the overbooking
models, which I believe have been very useful to synch up. This involved
a lot of synching up on various terminology and concepts that come to
mind to each of us (only in slightly different form for each individual)
on the topic of overbooking. This may have generated a perception that
the overbooking model for DS-TE is fairly complex. I would like to
address this potential perception and make the case that the overbooking
model actually selected for DS-TE is (i) quite simple and (ii)
structured as minimum possible increment over existing TE overbooking
model.

Again, the DS-TE overbooking model has:
	*  two MANDATORY components :
		-A- LSP Size Overbooking
		-B- Link Size Overbooking
	* and one OPTIONAL component:
		-C- Local Overbooking Multiplier

The two main and mandatory components are actually an integral part of
the existing TE. Just they never got discussed that much explicitely in
existing TE documents, but they are fully part of TE. They are commonly
used in TE live deployments today. They have just been inherited by
DS-TE and we applied them in the exact same way. Only, they got
discussed more explicitely (eg when doing the exercise of providing CAC
formulas and "Unreserved Bw" formulas) to ensure they were understood
consistently in the context of multiple CTs. 
Note also that like with existing TE, -A- and -B- don't result in any
specific protocol extensions (ie you would have the exact same
extensions even if you decided to not support Link/LSP Size
Overbooking).
So I can't see how we could do any simpler here, short of losing
overbooking functionality as compared to existing TE.

The third component is the only one where additional complexity over
existing TE really comes in. But this all hinges on the potential
requirement for overbooking ratios on a per-CT-and-per-link basis which
was identified at some stage as a potential requirements. If there is
such a requirement, we do need something beyond Link/LSP Sie
Overbooking; no way around it. Rather than re-invent a complete
overbooking model for DS-TE, the LOM method is structured as a pure
optional increment over Link/LSP overbooking to address this
requirement. This is purely optional anyway (and may even be removed, as
being currently discussed).

So, in summary, :
	- the mandatory components of the DS-TE overbooking model are
strictly identical to the ones of existing TE (no more, no less)
	- the one optional component is structured as a pure increment
over the other components, and is required to provide a specifc DS-TE
functionality identified as (potential) requirement. If the requirement
is dropped, this component can also be dropped (we would then be left
with an overbooking model for DS-TE which is strictly identical to the
overbooking model of existing TE).

Hope this is useful.

Cheers

Francois






From owner-te-wg@ops.ietf.org  Tue May 27 23:05:36 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16592
	for <tewg-archive@lists.ietf.org>; Tue, 27 May 2003 23:05:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19KrAq-000Mco-00
	for te-wg-data@psg.com; Wed, 28 May 2003 03:00:20 +0000
Received: from mgw2.noc.ntt.com ([210.163.32.69])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19KrAa-000MaJ-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 03:00:04 +0000
Received: from mop2.noc.ntt.com
	by mgw2.noc.ntt.com (NTT-Com MailSV) with ESMTP id h4S2xx3g022871
	for <te-wg@ops.ietf.org>; Wed, 28 May 2003 11:59:59 +0900 (JST)
Received: from mip1.noc.ntt.com (mvi1.noc.ntt.com)
 by mop2.noc.ntt.com (NTT-Com MailSV) with ESMTP id <0HFK008P1TNYDF@ntt.com>
 for te-wg@ops.ietf.org; Wed, 28 May 2003 11:59:59 +0900 (JST)
Received: from KAMITE2 by mip1.noc.ntt.com (NTT-Com MailSV)
 with SMTP id <0HFK00GKGTNYXX@ntt.com> for te-wg@ops.ietf.org; Wed,
 28 May 2003 11:59:58 +0900 (JST)
Content-return: prohibited
Date: Wed, 28 May 2003 11:59:58 +0900
From: "Yuji KAMITE" <y.kamite@ntt.com>
Subject: RE: DS-TE overbooking model - Not that complicated
In-reply-to: <000001c32491$57b20c10$6401a8c0@DASEP>
To: te-wg@ops.ietf.org
Message-id: <NDECIBNHBBMLPBCLGINEGEKJDDAA.y.kamite@ntt.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Status: No, hits=-17.9 required=5.0
	tests=BAYES_10,IN_REP_TO,MSGID_GOOD_EXCHANGE,PRIORITY_NO_NAME,
	      QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> 
> But to guarantee minimum bw for an LSP or for a CT as its LSPs are set
> up over time, there's got to be a way for upstream nodes to learn the
> LSP under-sizing factor that is in use. 
> 
> I'm hoping that instead of LOMs and instead of LSP under-sizing, BC
> over-sizing will be deemed sufficient to support "per-CT overbooking"!

I think LSP under-sizing is difficult solution, too.
LSP under-sizing approach will be burden on operators because it will
 occur significant discrepancy between LSP's size and expected traffic size.
(In other words, for practical usage, complicated implementation
 must be done such that it can take care of all these  under-sizing factors at
 upstream and can adjust rousources if necessary, automatically and dynamically.)
In my opinion, it will be easy to start with LSP size is set the same as 
expected bw ( this value is not under-sized). if overbooking is necessary,
BC is adjusted first. seems quite simple.

From the same reason, I think the place where LOM is used might be very small
at first deployment.

But,  I'm not sure if closing LOM itself is really valid answer now.
Perhaps it is useful for changing reservation capacity temorarily for a short time
For example, due to link construction or rapid load increase,  SP might want to
change capacity temporarily althogh it does not want to change BC or LSP size
itself. ( because of SP's policy.) 

Actually SP would select the best solution from various perspective.
While avoiding complexity might be a key factor for some SP,
another SP will flexibility is important.

However, as for LOM, I'm wondering where it can be applied and useful.
Actually, I'm not sure the example written above is good one.
Today there seem few applicability suggenstions.
Requirement says DS-TE must support overbooking, but is LOM regareded
necessary and sufficient ? Possibly other approaches can provide the same function.

 In order to support LOM, LOM's advantage and applicability must be clarified.

Any ideas?


---
Yuji KAMITE  (e-mail: y.kamite@ntt.com)
  Innovative IP Architecture Center, NTT Communications
   Tel:+81-3-6800-3261, Fax:+81-3-5365-2990




From owner-te-wg@ops.ietf.org  Wed May 28 05:01:31 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22346
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 05:01:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Kwks-0008wO-00
	for te-wg-data@psg.com; Wed, 28 May 2003 08:57:54 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Kwko-0008wA-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 08:57:50 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 28 May 2003 10:57:05 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4S8tNuQ003512;
	Wed, 28 May 2003 10:55:52 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 10:57:43 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Wed, 28 May 2003 09:57:42 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B524B@xbe-lon-313.cisco.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMkZfC/weAr46AnTjSbdUSSgCGPNgAjE4lg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 28 May 2003 08:57:43.0044 (UTC) FILETIME=[332A5440:01C324F7]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA22346

Hello Dimitry,

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 27 May 2003 17:37
>> To: Francois Le Faucheur (flefauch); Ash, Gerald R (Jerry), ALABS
>> Cc: te-wg@ops.ietf.org
>> Subject: RE: link capacity and reservable
>> 
>> 
>> Francois,
>> 
>> > My point below was about enforcing overbooking ratios on a
>> > per-CT-and-per-link basis (ie CT0 is overbooked by factor 
>> 2 on link 0
>> > and overbooked by factor 3 on link 1, while CT1 is not 
>> overbooked on
>> > link0 nor on link1). This could NOT be achieved just by 
>> combination of
>> > "LSP Size overbooking" and "Link Size Overbooking"; it 
>> could only be
>> > achieved via the use of the LOM method. But, as being 
>> discussed, it is
>> > not obvious that the nbeed for this justifies the extra complexity.
>> >
>> 
>> For my sake.. Since b/w constrains are advertised and 
>> handled per CT per TE
>> link (i.e. there are separate BCn values on each visible link in a TE
>> domain), why is LOM necessary to achieve overbooking per  CT 
>> per link?  

LOM is necessary because the BC Models we are considering enforce one
(or more) shared/aggregate constraint(s).

If we had a trivial BC model of pure independent bandwidth constraints,
then yes, each CT could operate independently and do its own computation
of how much is taken from its own BC. And we would not need LOM.

But since we have shared aggregate constraints (aka Max Reservable Bw)
you need to somehow configure what is the individual overbooking ratio
that is to be considered on that link for that CT, for the purpose of
deducting bandwidth from the shared/aggregate constraint. This is the
vectorisation issue that Waisum raised. The "euro vs dollar" question as
Wai put it.

In other words, considering MAM (with new definition), imagine you
configure BC0=1000 (probably reflecting some high overbooking) and
BC1=100 (probably reflecting some low overbooking), and
Max-Reservable-Bw=300 (probably reflecting an average overbooking on an
aggregate basis). One would not know exactly how to apply the Max
Reservable Bandwidth differntly to CT0 LSPs and CT1 LSPs in order to
compute the. For example if you have established one CT0 LSP of 500 and
one CT1 LSP of 50, how much exactly is left available to CT0 and CT1?

With the LOM solution, you configure BC0=100, BC1=50 , Max Reservable
Bw=130, LOM(0)=10 and LOM(1)=2. Then you know exactly how to apply the
Max Reservable Bandw constraints (see formulas in dste drafts) and how
to compute the available bandwidth for each CT dependeing on how much
LSPs are established acros ALL other CTs.

I suggest looking at section 6.2 of diff-te-russian where the formulas
make clear the role of LOM in various computation.

One could probably come up with solutions which are slightly different
to LOM, but the LOM solution is very attractive because, again, it is a
pure increment to the other overbooking methods which exist in TE today.

Cheers

Francois

>>Or
>> is it that link0 and link1 in your example form a some kind 
>> link bundle, i.e
>> form a single TE link as far as OSPF/ISIS TE extensions are 
>> concerned?
>> 
>> Thanks,
>>  Dimitry
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed May 28 05:21:22 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22800
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 05:21:22 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Kx6S-000Cki-00
	for te-wg-data@psg.com; Wed, 28 May 2003 09:20:12 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Kx6O-000CgR-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 09:20:08 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 28 May 2003 11:19:24 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4S9Hojm008342;
	Wed, 28 May 2003 11:18:10 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 11:19:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: DS-TE overbooking model - Not that complicated
Date: Wed, 28 May 2003 10:19:55 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B524C@xbe-lon-313.cisco.com>
Thread-Topic: DS-TE overbooking model - Not that complicated
Thread-Index: AcMkkVky+BfI1tyrRryyo9CeGs2KagAZwd9w
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "sanford goldfless" <sandy9@rcn.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 28 May 2003 09:19:56.0552 (UTC) FILETIME=[4DFF8080:01C324FA]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA22800

Sandy,
 
>> I'm hoping that instead of LOMs and instead of LSP under-sizing, BC
>> over-sizing will be deemed sufficient to support "per-CT 
>> overbooking"!
>> 

The underlying issue behind this point is pretty much the same as behind
Dimitry's question. Because our BC models (MAM, RDM, MAR,..) enforce one
or more shared/aggregate constraint (as opposed to independent
constraint), there is a fundamental need to be able to "normalise" those
ie make them somehow comparable for applying a shared constraint. Just
configuring (an inflated) BC for each CT does not give enough
information on what is the per-CT overbooking ratio in order to make
them comparable for applying the aggregate constraint. There are two
main conceptual ways to make them comparable:
	- factoring the per-CT overbooking ratio in the LSP size. This
is what the LSP-Size overbooking method recommends.
	- configure locally per-CT overbooking multipliers which contain
information on how to normalise those. This is precisely what the LOM
parameters are.

So the bottom line is that it is not possible to support "per-CT
overboking" purely by adjusting the size of the BCs (when
shared/aggregate constraints are used). The simplest way is to reflect
per-CT overbooking in the LSP Size. The other option is to reflect local
per-CT overbooking multipliers as per LOM.

Thanks

Francois


>> Thanks,
>> Sandy
>>   
>> Sanford Goldfless
>> 192 Fuller St
>> Brookline MA 02446
>> 617-738-1754
>> sandy9@rcn.com
>> 
>> 
>> -----Original Message-----
>> From: owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org] On
>> Behalf Of Francois Le Faucheur (flefauch)
>> Sent: Tuesday, May 27, 2003 5:27 AM
>> To: te-wg@ops.ietf.org
>> Subject: DS-TE overbooking model - Not that complicated
>> 
>> Hello,
>> 
>> We have been through fairly detailed discussions on the overbooking
>> models, which I believe have been very useful to synch up. 
>> This involved
>> a lot of synching up on various terminology and concepts that come to
>> mind to each of us (only in slightly different form for each 
>> individual)
>> on the topic of overbooking. This may have generated a 
>> perception that
>> the overbooking model for DS-TE is fairly complex. I would like to
>> address this potential perception and make the case that the 
>> overbooking
>> model actually selected for DS-TE is (i) quite simple and (ii)
>> structured as minimum possible increment over existing TE overbooking
>> model.
>> 
>> Again, the DS-TE overbooking model has:
>> 	*  two MANDATORY components :
>> 		-A- LSP Size Overbooking
>> 		-B- Link Size Overbooking
>> 	* and one OPTIONAL component:
>> 		-C- Local Overbooking Multiplier
>> 
>> The two main and mandatory components are actually an 
>> integral part of
>> the existing TE. Just they never got discussed that much 
>> explicitely in
>> existing TE documents, but they are fully part of TE. They 
>> are commonly
>> used in TE live deployments today. They have just been inherited by
>> DS-TE and we applied them in the exact same way. Only, they got
>> discussed more explicitely (eg when doing the exercise of 
>> providing CAC
>> formulas and "Unreserved Bw" formulas) to ensure they were understood
>> consistently in the context of multiple CTs. 
>> Note also that like with existing TE, -A- and -B- don't result in any
>> specific protocol extensions (ie you would have the exact same
>> extensions even if you decided to not support Link/LSP Size
>> Overbooking).
>> So I can't see how we could do any simpler here, short of losing
>> overbooking functionality as compared to existing TE.
>> 
>> The third component is the only one where additional complexity over
>> existing TE really comes in. But this all hinges on the potential
>> requirement for overbooking ratios on a per-CT-and-per-link 
>> basis which
>> was identified at some stage as a potential requirements. If there is
>> such a requirement, we do need something beyond Link/LSP Sie
>> Overbooking; no way around it. Rather than re-invent a complete
>> overbooking model for DS-TE, the LOM method is structured as a pure
>> optional increment over Link/LSP overbooking to address this
>> requirement. This is purely optional anyway (and may even be 
>> removed, as
>> being currently discussed).
>> 
>> So, in summary, :
>> 	- the mandatory components of the DS-TE overbooking model are
>> strictly identical to the ones of existing TE (no more, no less)
>> 	- the one optional component is structured as a pure increment
>> over the other components, and is required to provide a specifc DS-TE
>> functionality identified as (potential) requirement. If the 
>> requirement
>> is dropped, this component can also be dropped (we would then be left
>> with an overbooking model for DS-TE which is strictly 
>> identical to the
>> overbooking model of existing TE).
>> 
>> Hope this is useful.
>> 
>> Cheers
>> 
>> Francois
>> 
>> 
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed May 28 10:39:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06505
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 10:39:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L21V-00099f-00
	for te-wg-data@psg.com; Wed, 28 May 2003 14:35:25 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L21R-00099O-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 14:35:21 +0000
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA04114
	for <te-wg@ops.ietf.org>; Wed, 28 May 2003 10:35:18 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA01956
	for <te-wg@ops.ietf.org>; Wed, 28 May 2003 10:35:20 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L2411A0C>; Wed, 28 May 2003 10:35:19 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F549F@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from D
	S-TE specs?
Date: Wed, 28 May 2003 10:35:12 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi! DSTE-REQ already states that the per-CT overbooking
is an optional feature and does not require the vendors
to implement it.

We already discussed the overbooking/underbooking issues
quite some time back. I don't think we, should change
requirement [DSTE-REQ] at this stage (past last call),
unless there is a real problem or limitation.

If we are trying to change the requirement because the 
LOM concept is difficult, let's take steps to clarify
the concept by necessary editorial changes (and examples).

Thanks,
sanjay

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Monday, May 26, 2003 9:05 AM
> To: te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> DS-TE specs?
> 
> 
> All TEWGers,
> 
> Thoughts on dropping/keeping LOM in base DS-TE specs?
> 
> Thanks
> 
> Francois
> 
> >> -----Original Message-----
> >> From: Francois Le Faucheur (flefauch) 
> >> Sent: 26 May 2003 14:59
> >> To: Kireeti Kompella; te-wg@ops.ietf.org
> >> Subject: Dropping the Local Overbooking Multiplier (LOM) 
> >> method from DS-TE specs?
> >> 
> >> 
> >> Kireeti,
> >> 
> >> Once upon a time, we merged 3 technical proposals for DS-TE (one of
> >> which was yours) into a common one. One of the 
> capabilities that was
> >> unique to your proposal was the ability to support 
> overbooking ratios
> >> which are different on a per CT AND per link basis (while the other
> >> methods supported different ratios on different links and different
> >> ratios on a per CT basis, not not on a per CT and per-link 
> >> basis). Back
> >> then you made a argument that there was some value in 
> allowing this.
> >> This resulted in the addition of the optional Local Overbooking
> >> Multiplier (LOM) method in the DS-TE specs.
> >> 
> >> A number of people commented that considering the ratio of 
> >> complexity vs
> >> functionality for this particular capability, we may be better off
> >> issueing the base DS-TE specs without this for now and 
> then add this
> >> capability later or in a separate document. I personnally 
> also favors
> >> such an approach.
> >> 
> >> What is your take on this?
> >> 
> >> Cheers
> >> 
> >> Francois
> >> 
> >> >> -----Original Message-----
> >> >> From: Jim Boyle [mailto:jboyle@pdnets.com] 
> >> >> Sent: 24 May 2003 02:31
> >> >> To: Francois Le Faucheur (flefauch)
> >> >> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
> >> >> Subject: RE: Reflecting new-MAM/SAM definition in 
> diff-te drafts 
> >> >> 
> >> >> 
> >> <clip>
> >> >> 
> >> >> btw... I also think LOMs are lots of complexity for 
> little gain :)
> >> >> 
> >> >> 
> >> >> 
> >> >> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
> >> >> 
> >> >> > Jerry,
> >> >> > 
> >> >> > >> -----Original Message-----
> >> >> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> >> >> > >> Sent: 20 May 2003 17:35
> >> >> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
> >> >> > >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org; Lai, 
> >> >> > >> Wai S (Waisum), ALABS
> >> >> > >> Subject: RE: Reflecting new-MAM/SAM definition in 
> >> diff-te drafts
> >> >> > >> 
> >> >> > >> 
> >> >> > >> Dimitry, Francois,
> >> >> > >> 
> >> >> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable 
> Bandwidth, 
> >> >> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
> >> >> > >> > > 
> >> >> > >> > > However, this formula is incorrect for DS-TE 
> when per-CT 
> >> >> > >> > > LOM's are used, since the above formula only 
> >> >> reflects the Max 
> >> >> > >> > > Reservable Bandwidth for the entire link, and does not 
> >> >> > >> > > reflect the per-CT local overbooking factors.  So what 
> >> >> > >> > > formula do you suggest when per-CT LOM's are used?
> >> >> > >> 
> >> >> > >> > Wouldn't 'Reserved (CTc)' it the above formula already 
> >> >> > >> accounts for the
> >> >> > >> > overbooking multiplier at CTc?  I don't see how this 
> >> >> > >> formula precludes
> >> >> > >> > per-CT LOM's to be used. Please explain.
> >> >> > >> 
> >> >> > >> Are you then proposing these formulas:
> >> >> > >> 
> >> >> > >> 1. When per-CT LOMs are not used:
> >> >> > >> 
> >> >> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
> >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> >> > >> 
> >> >> > >> 2. When per-CT LOMs are used:
> >> >> > >> 
> >> >> > >>      o SUM (Normalized(CTc)) <= Max Reservable Bandwidth, 
> >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> >> > >> 
> >> >> > >> Is that correct?  Please confirm, and/or give the formulas 
> >> >> > >> you propose.
> >> >> > 
> >> >> > Yes, this is exactly what I propose.
> >> >> > I think this is similar to what you were proposing, only 
> >> >> using "Max Res
> >> >> > Bw" instead of "Max Link Bw". 
> >> >> > 
> >> >> > Sorry I didn't make that very clear before.
> >> >> > 
> >> >> > Cheers
> >> >> > 
> >> >> > FRancois
> >> >> > 
> >> >> > >> 
> >> >> > >> Thanks,
> >> >> > >> Jerry
> >> >> > >> 
> >> >> > 
> >> >> > 
> >> >> > 
> >> >> > 
> >> >> 
> >> >> 
> >> 
> >> 
> 



From owner-te-wg@ops.ietf.org  Wed May 28 11:37:32 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08857
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 11:37:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L2y6-000CXZ-00
	for te-wg-data@psg.com; Wed, 28 May 2003 15:35:58 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L2y1-000CX8-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 15:35:53 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F656@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        Dimitry Haskin <dhaskin@axiowave.com>,
        "Ash, Gerald R (Jerry), ALABS"
	 <gash@att.com>
Cc: te-wg@ops.ietf.org
Subject: RE: link capacity and reservable
Date: Wed, 28 May 2003 11:33:37 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Francois,

Thanks for your clear explanation. What has escaped me before is that LOM is
useful only for those cases where both of the following must be true:

 1) CTs of the same link have different overbooking ratios.
 2) The amount of reservations in one CT must precisely effect reservable
bandwidths in other CTs of the same link.

If I am correct, then it is quite possible to support different overbooking
ratios per CT per link without LOM, provided that 2) is not required (or at
least not with the same level of precision that LOM can provide).

Thanks,
 Dimitry




> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Wednesday, May 28, 2003 4:58 AM
> To: Dimitry Haskin; Ash, Gerald R (Jerry), ALABS
> Cc: te-wg@ops.ietf.org
> Subject: RE: link capacity and reservable
> 
> 
> Hello Dimitry,
> 
> >> -----Original Message-----
> >> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
> >> Sent: 27 May 2003 17:37
> >> To: Francois Le Faucheur (flefauch); Ash, Gerald R (Jerry), ALABS
> >> Cc: te-wg@ops.ietf.org
> >> Subject: RE: link capacity and reservable
> >> 
> >> 
> >> Francois,
> >> 
> >> > My point below was about enforcing overbooking ratios on a
> >> > per-CT-and-per-link basis (ie CT0 is overbooked by factor 
> >> 2 on link 0
> >> > and overbooked by factor 3 on link 1, while CT1 is not 
> >> overbooked on
> >> > link0 nor on link1). This could NOT be achieved just by 
> >> combination of
> >> > "LSP Size overbooking" and "Link Size Overbooking"; it 
> >> could only be
> >> > achieved via the use of the LOM method. But, as being 
> >> discussed, it is
> >> > not obvious that the nbeed for this justifies the extra 
> complexity.
> >> >
> >> 
> >> For my sake.. Since b/w constrains are advertised and 
> >> handled per CT per TE
> >> link (i.e. there are separate BCn values on each visible 
> link in a TE
> >> domain), why is LOM necessary to achieve overbooking per  CT 
> >> per link?  
> 
> LOM is necessary because the BC Models we are considering enforce one
> (or more) shared/aggregate constraint(s).
> 
> If we had a trivial BC model of pure independent bandwidth 
> constraints,
> then yes, each CT could operate independently and do its own 
> computation
> of how much is taken from its own BC. And we would not need LOM.
> 
> But since we have shared aggregate constraints (aka Max Reservable Bw)
> you need to somehow configure what is the individual overbooking ratio
> that is to be considered on that link for that CT, for the purpose of
> deducting bandwidth from the shared/aggregate constraint. This is the
> vectorisation issue that Waisum raised. The "euro vs dollar" 
> question as
> Wai put it.
> 
> In other words, considering MAM (with new definition), imagine you
> configure BC0=1000 (probably reflecting some high overbooking) and
> BC1=100 (probably reflecting some low overbooking), and
> Max-Reservable-Bw=300 (probably reflecting an average 
> overbooking on an
> aggregate basis). One would not know exactly how to apply the Max
> Reservable Bandwidth differntly to CT0 LSPs and CT1 LSPs in order to
> compute the. For example if you have established one CT0 LSP 
> of 500 and
> one CT1 LSP of 50, how much exactly is left available to CT0 and CT1?
> 
> With the LOM solution, you configure BC0=100, BC1=50 , Max Reservable
> Bw=130, LOM(0)=10 and LOM(1)=2. Then you know exactly how to apply the
> Max Reservable Bandw constraints (see formulas in dste drafts) and how
> to compute the available bandwidth for each CT dependeing on how much
> LSPs are established acros ALL other CTs.
> 
> I suggest looking at section 6.2 of diff-te-russian where the formulas
> make clear the role of LOM in various computation.
> 
> One could probably come up with solutions which are slightly different
> to LOM, but the LOM solution is very attractive because, 
> again, it is a
> pure increment to the other overbooking methods which exist 
> in TE today.
> 
> Cheers
> 
> Francois
> 
> >>Or
> >> is it that link0 and link1 in your example form a some kind 
> >> link bundle, i.e
> >> form a single TE link as far as OSPF/ISIS TE extensions are 
> >> concerned?
> >> 
> >> Thanks,
> >>  Dimitry
> >> 
> >> 
> 



From owner-te-wg@ops.ietf.org  Wed May 28 11:38:02 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08892
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 11:38:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L2yB-000CXt-00
	for te-wg-data@psg.com; Wed, 28 May 2003 15:36:03 +0000
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L2y5-000CXO-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 15:35:57 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h4SFZbtE015922;
	Wed, 28 May 2003 15:35:37 GMT
Received: from zhangr2.info.net (lasi254.us.info.net [204.140.71.254])
	by delta.info.net  with ESMTP id PAA05952;
	Wed, 28 May 2003 15:35:35 GMT
Message-Id: <5.2.0.9.2.20030528083416.00ad94c0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 28 May 2003 08:35:21 -0700
To: Ed Kern <ejk@tech.org>, te-wg@ops.ietf.org
From: raymond zhang <zhangr@info.net>
Subject: Re: agenda items for vienna?
Cc: Jean Philippe Vasseur <jvasseur@cisco.com>
In-Reply-To: <2147483647.1053677633@dhcp-171-71-139-23.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-12.8 required=5.0
	tests=BAYES_20,EMAIL_ATTRIBUTION,IN_REP_TO
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Ed and Jim,

Can you allocate a time slot for us in Vienna to provide a status update on 
the inter-as req's drafts ?

Thanks,
Raymond

At 08:13 AM 5/23/2003 -0700, Ed Kern wrote:


>Due to various vacations we need to close on the agenda for vienna in the 
>next week or so.
>
>Please submit any work items with a suggested speaker and time estimate 
>directly to jim and myself by next Friday the 30th of May.
>
>
>
>thanks,
>
>Ed
>





From owner-te-wg@ops.ietf.org  Wed May 28 11:56:13 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09578
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 11:56:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L3E6-000DVw-00
	for te-wg-data@psg.com; Wed, 28 May 2003 15:52:30 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L3Dy-000DVj-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 15:52:22 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 28 May 2003 17:51:36 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4SFoMZs026334;
	Wed, 28 May 2003 17:50:23 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 17:52:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: link capacity and reservable
Date: Wed, 28 May 2003 16:52:19 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5252@xbe-lon-313.cisco.com>
Thread-Topic: link capacity and reservable
Thread-Index: AcMlLqYweyqfrPbxTI6eZIPeyrRP2gAAdLgQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 28 May 2003 15:52:19.0469 (UTC) FILETIME=[1EAB8BD0:01C32531]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA09578

Dimitry,

>> Francois,
>> 
>> Thanks for your clear explanation. What has escaped me 
>> before is that LOM is
>> useful only for those cases where both of the following must be true:
>> 
>>  1) CTs of the same link have different overbooking ratios.
>>  2) The amount of reservations in one CT must precisely 
>> effect reservable
>> bandwidths in other CTs of the same link.
>>

Yes.
 
>> If I am correct, then it is quite possible to support 
>> different overbooking
>> ratios per CT per link without LOM, provided that 2)
>> is not 
>> required 

I would agree with that statement.
But in general,  2) seems highly desirable (ie it would seem odd to have
BC models which enforce aggregate constraints without having the ability
to apply this constraint fairly acurately over the various CTs).

Cheers

Francois

>>(or at
>> least not with the same level of precision that LOM can provide).
>> 
>> Thanks,
>>  Dimitry
>> 
>> 
>> 
>> 
>> > -----Original Message-----
>> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>> > Sent: Wednesday, May 28, 2003 4:58 AM
>> > To: Dimitry Haskin; Ash, Gerald R (Jerry), ALABS
>> > Cc: te-wg@ops.ietf.org
>> > Subject: RE: link capacity and reservable
>> > 
>> > 
>> > Hello Dimitry,
>> > 
>> > >> -----Original Message-----
>> > >> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> > >> Sent: 27 May 2003 17:37
>> > >> To: Francois Le Faucheur (flefauch); Ash, Gerald R 
>> (Jerry), ALABS
>> > >> Cc: te-wg@ops.ietf.org
>> > >> Subject: RE: link capacity and reservable
>> > >> 
>> > >> 
>> > >> Francois,
>> > >> 
>> > >> > My point below was about enforcing overbooking ratios on a
>> > >> > per-CT-and-per-link basis (ie CT0 is overbooked by factor 
>> > >> 2 on link 0
>> > >> > and overbooked by factor 3 on link 1, while CT1 is not 
>> > >> overbooked on
>> > >> > link0 nor on link1). This could NOT be achieved just by 
>> > >> combination of
>> > >> > "LSP Size overbooking" and "Link Size Overbooking"; it 
>> > >> could only be
>> > >> > achieved via the use of the LOM method. But, as being 
>> > >> discussed, it is
>> > >> > not obvious that the nbeed for this justifies the extra 
>> > complexity.
>> > >> >
>> > >> 
>> > >> For my sake.. Since b/w constrains are advertised and 
>> > >> handled per CT per TE
>> > >> link (i.e. there are separate BCn values on each visible 
>> > link in a TE
>> > >> domain), why is LOM necessary to achieve overbooking per  CT 
>> > >> per link?  
>> > 
>> > LOM is necessary because the BC Models we are considering 
>> enforce one
>> > (or more) shared/aggregate constraint(s).
>> > 
>> > If we had a trivial BC model of pure independent bandwidth 
>> > constraints,
>> > then yes, each CT could operate independently and do its own 
>> > computation
>> > of how much is taken from its own BC. And we would not need LOM.
>> > 
>> > But since we have shared aggregate constraints (aka Max 
>> Reservable Bw)
>> > you need to somehow configure what is the individual 
>> overbooking ratio
>> > that is to be considered on that link for that CT, for the 
>> purpose of
>> > deducting bandwidth from the shared/aggregate constraint. 
>> This is the
>> > vectorisation issue that Waisum raised. The "euro vs dollar" 
>> > question as
>> > Wai put it.
>> > 
>> > In other words, considering MAM (with new definition), imagine you
>> > configure BC0=1000 (probably reflecting some high overbooking) and
>> > BC1=100 (probably reflecting some low overbooking), and
>> > Max-Reservable-Bw=300 (probably reflecting an average 
>> > overbooking on an
>> > aggregate basis). One would not know exactly how to apply the Max
>> > Reservable Bandwidth differntly to CT0 LSPs and CT1 LSPs 
>> in order to
>> > compute the. For example if you have established one CT0 LSP 
>> > of 500 and
>> > one CT1 LSP of 50, how much exactly is left available to 
>> CT0 and CT1?
>> > 
>> > With the LOM solution, you configure BC0=100, BC1=50 , Max 
>> Reservable
>> > Bw=130, LOM(0)=10 and LOM(1)=2. Then you know exactly how 
>> to apply the
>> > Max Reservable Bandw constraints (see formulas in dste 
>> drafts) and how
>> > to compute the available bandwidth for each CT dependeing 
>> on how much
>> > LSPs are established acros ALL other CTs.
>> > 
>> > I suggest looking at section 6.2 of diff-te-russian where 
>> the formulas
>> > make clear the role of LOM in various computation.
>> > 
>> > One could probably come up with solutions which are 
>> slightly different
>> > to LOM, but the LOM solution is very attractive because, 
>> > again, it is a
>> > pure increment to the other overbooking methods which exist 
>> > in TE today.
>> > 
>> > Cheers
>> > 
>> > Francois
>> > 
>> > >>Or
>> > >> is it that link0 and link1 in your example form a some kind 
>> > >> link bundle, i.e
>> > >> form a single TE link as far as OSPF/ISIS TE extensions are 
>> > >> concerned?
>> > >> 
>> > >> Thanks,
>> > >>  Dimitry
>> > >> 
>> > >> 
>> > 
>> 



From owner-te-wg@ops.ietf.org  Wed May 28 12:02:02 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10029
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 12:02:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L3Ms-000E5Y-00
	for te-wg-data@psg.com; Wed, 28 May 2003 16:01:34 +0000
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L3Mk-000E54-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 16:01:26 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4SFRX1K015882
	for <te-wg@ops.ietf.org>; Wed, 28 May 2003 11:01:23 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020030E62C; Wed, 28 May 2003 12:01:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Wed, 28 May 2003 11:01:22 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE956@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlKT9yy/j1E32MQz2QBPdePjfxJAAAjM8Q
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA10029

Sanjay, All,

> DSTE-REQ already states that the per-CT overbooking
> is an optional feature and does not require the vendors
> to implement it.
> 
> We already discussed the overbooking/underbooking issues
> quite some time back. I don't think we, should change
> requirement [DSTE-REQ] at this stage (past last call),
> unless there is a real problem or limitation.

The DSTE-REQ say:

" The DS-TE solution MUST also allow overbooking and MUST effectively 
   allow different overbooking ratios to be enforced for different CTs. 
    
   The DS-TE solution SHOULD optionally allow the effective overbooking 
   ratio of a given CT to be tweaked differently in different parts of 
   the network."

This does not exactly *require* LOM.  As we've discussed, by using Link Size Overbooking Multipliers (LSOM) and LSP Size overbooking multipliers (LSPOM), we can achieve some degree of per-CT overbooking that is tweaked differently in different parts of the network.  

For example, by setting
LSOM0 = 1 on link 0,
LSOM1 = 1.5 on link 1,
LSPOM0 = 2 for LSPs on CT0,
LSPOM1 = 1 for LSPs on CT1,
we could overbook CT0 by 2 on link 0 and 3 on link 1 (LSPOM0 * LSOM1 = 2 * 1.5 = 3),
while overbooking CT1 by 1 on link 0 and 1.5 on link 1.

However, for the example Francois gave:
"CT0 is overbooked by factor 2 on link 0 and overbooked by factor 3 on link 1, while CT1 is not overbooked on link0 nor on link1. This could NOT be achieved just by combination of "LSP Size overbooking" and "Link Size Overbooking"; it could only be achieved via the use of the LOM method. But, as being discussed, it is not obvious that the need for this justifies the extra complexity."

I agree that this example requires LOM, but I also agree that the need for this is not obvious.  Can anyone explain why such a capability would be needed?

It is also not obvious that the above flexibility (i.e., need for LOM) is *required* by DSTE-REQ.
 
> If we are trying to change the requirement because the 
> LOM concept is difficult, let's take steps to clarify
> the concept by necessary editorial changes (and examples).

I'm not sure we are trying to change the requirement, however I agree that we need good examples of how/why LOM is absolutely needed to achieve the requirements.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Wed May 28 12:03:19 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10080
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 12:03:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L3OH-000EBA-00
	for te-wg-data@psg.com; Wed, 28 May 2003 16:03:01 +0000
Received: from ppp-64-115-125-242.broadviewnet.net ([64.115.125.242] helo=bridge.axiowave.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L3O8-000EAZ-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 16:02:52 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F657@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Choudhury, Sanjaya'" <Sanjaya.Choudhury@marconi.com>, te-wg@ops.ietf.org
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from D
	 S-TE specs?
Date: Wed, 28 May 2003 12:02:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Sanjay,

I don't think there has been any attempt to change the per-CT overbooking
requirement. Indeed this requirement shell be supported.  I don't think
dropping LOM from the base protocol extensions draft would alter the DSTE
requirements as currently specified.

Dimitry

> -----Original Message-----
> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@marconi.com]
> Sent: Wednesday, May 28, 2003 10:35 AM
> To: te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> D S-TE specs?
> 
> 
> Hi! DSTE-REQ already states that the per-CT overbooking
> is an optional feature and does not require the vendors
> to implement it.
> 
> We already discussed the overbooking/underbooking issues
> quite some time back. I don't think we, should change
> requirement [DSTE-REQ] at this stage (past last call),
> unless there is a real problem or limitation.
> 
> If we are trying to change the requirement because the 
> LOM concept is difficult, let's take steps to clarify
> the concept by necessary editorial changes (and examples).
> 
> Thanks,
> sanjay
> 
> > -----Original Message-----
> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> > Sent: Monday, May 26, 2003 9:05 AM
> > To: te-wg@ops.ietf.org
> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > method from
> > DS-TE specs?
> > 
> > 
> > All TEWGers,
> > 
> > Thoughts on dropping/keeping LOM in base DS-TE specs?
> > 
> > Thanks
> > 
> > Francois
> > 
> > >> -----Original Message-----
> > >> From: Francois Le Faucheur (flefauch) 
> > >> Sent: 26 May 2003 14:59
> > >> To: Kireeti Kompella; te-wg@ops.ietf.org
> > >> Subject: Dropping the Local Overbooking Multiplier (LOM) 
> > >> method from DS-TE specs?
> > >> 
> > >> 
> > >> Kireeti,
> > >> 
> > >> Once upon a time, we merged 3 technical proposals for 
> DS-TE (one of
> > >> which was yours) into a common one. One of the 
> > capabilities that was
> > >> unique to your proposal was the ability to support 
> > overbooking ratios
> > >> which are different on a per CT AND per link basis 
> (while the other
> > >> methods supported different ratios on different links 
> and different
> > >> ratios on a per CT basis, not not on a per CT and per-link 
> > >> basis). Back
> > >> then you made a argument that there was some value in 
> > allowing this.
> > >> This resulted in the addition of the optional Local Overbooking
> > >> Multiplier (LOM) method in the DS-TE specs.
> > >> 
> > >> A number of people commented that considering the ratio of 
> > >> complexity vs
> > >> functionality for this particular capability, we may be 
> better off
> > >> issueing the base DS-TE specs without this for now and 
> > then add this
> > >> capability later or in a separate document. I personnally 
> > also favors
> > >> such an approach.
> > >> 
> > >> What is your take on this?
> > >> 
> > >> Cheers
> > >> 
> > >> Francois
> > >> 
> > >> >> -----Original Message-----
> > >> >> From: Jim Boyle [mailto:jboyle@pdnets.com] 
> > >> >> Sent: 24 May 2003 02:31
> > >> >> To: Francois Le Faucheur (flefauch)
> > >> >> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
> > >> >> Subject: RE: Reflecting new-MAM/SAM definition in 
> > diff-te drafts 
> > >> >> 
> > >> >> 
> > >> <clip>
> > >> >> 
> > >> >> btw... I also think LOMs are lots of complexity for 
> > little gain :)
> > >> >> 
> > >> >> 
> > >> >> 
> > >> >> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
> > >> >> 
> > >> >> > Jerry,
> > >> >> > 
> > >> >> > >> -----Original Message-----
> > >> >> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> > >> >> > >> Sent: 20 May 2003 17:35
> > >> >> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
> > >> >> > >> Cc: Ash, Gerald R (Jerry), ALABS; 
> te-wg@ops.ietf.org; Lai, 
> > >> >> > >> Wai S (Waisum), ALABS
> > >> >> > >> Subject: RE: Reflecting new-MAM/SAM definition in 
> > >> diff-te drafts
> > >> >> > >> 
> > >> >> > >> 
> > >> >> > >> Dimitry, Francois,
> > >> >> > >> 
> > >> >> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable 
> > Bandwidth, 
> > >> >> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
> > >> >> > >> > > 
> > >> >> > >> > > However, this formula is incorrect for DS-TE 
> > when per-CT 
> > >> >> > >> > > LOM's are used, since the above formula only 
> > >> >> reflects the Max 
> > >> >> > >> > > Reservable Bandwidth for the entire link, 
> and does not 
> > >> >> > >> > > reflect the per-CT local overbooking 
> factors.  So what 
> > >> >> > >> > > formula do you suggest when per-CT LOM's are used?
> > >> >> > >> 
> > >> >> > >> > Wouldn't 'Reserved (CTc)' it the above formula already 
> > >> >> > >> accounts for the
> > >> >> > >> > overbooking multiplier at CTc?  I don't see how this 
> > >> >> > >> formula precludes
> > >> >> > >> > per-CT LOM's to be used. Please explain.
> > >> >> > >> 
> > >> >> > >> Are you then proposing these formulas:
> > >> >> > >> 
> > >> >> > >> 1. When per-CT LOMs are not used:
> > >> >> > >> 
> > >> >> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
> > >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> > >> >> > >> 
> > >> >> > >> 2. When per-CT LOMs are used:
> > >> >> > >> 
> > >> >> > >>      o SUM (Normalized(CTc)) <= Max Reservable 
> Bandwidth, 
> > >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> > >> >> > >> 
> > >> >> > >> Is that correct?  Please confirm, and/or give 
> the formulas 
> > >> >> > >> you propose.
> > >> >> > 
> > >> >> > Yes, this is exactly what I propose.
> > >> >> > I think this is similar to what you were proposing, only 
> > >> >> using "Max Res
> > >> >> > Bw" instead of "Max Link Bw". 
> > >> >> > 
> > >> >> > Sorry I didn't make that very clear before.
> > >> >> > 
> > >> >> > Cheers
> > >> >> > 
> > >> >> > FRancois
> > >> >> > 
> > >> >> > >> 
> > >> >> > >> Thanks,
> > >> >> > >> Jerry
> > >> >> > >> 
> > >> >> > 
> > >> >> > 
> > >> >> > 
> > >> >> > 
> > >> >> 
> > >> >> 
> > >> 
> > >> 
> > 
> 



From owner-te-wg@ops.ietf.org  Wed May 28 12:32:13 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11057
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 12:32:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L3pi-000G9k-00
	for te-wg-data@psg.com; Wed, 28 May 2003 16:31:22 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L3pb-000G7X-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 16:31:15 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 28 May 2003 18:30:30 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h4SGTGG0003139;
	Wed, 28 May 2003 18:29:16 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 28 May 2003 18:31:13 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Wed, 28 May 2003 17:31:12 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D9E437AC@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlKQkJxItyUxscTQmbJY1LjPlqPAACOvWg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 28 May 2003 16:31:13.0336 (UTC) FILETIME=[8DC36380:01C32536]
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA11057

Hello Sanjaya,

>> -----Original Message-----
>> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@marconi.com] 
>> Sent: 28 May 2003 16:35
>> To: te-wg@ops.ietf.org
>> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> Hi! DSTE-REQ already states that the per-CT overbooking
>> is an optional feature and does not require the vendors
>> to implement it.
>>

For the record, the DSTE-REQTS spec does not define requirements for
implementation/vendors. It defines requirements for the ds-te solution.
So, my interpretation of what its text says is just that the DS-TE
solution should try to cope with the corresponding requirement. In other
words, to me, it is identified as an optional feature for the
DSTE-solution (a feature that the DSTE solution should try address, but
may not address).

I really don't want to start a "DSTE-REQTS interpretation" argument. The
only reason I bring that up is to address your point below. ie I don't
think the discussion we're having on taking LOM out of the base specs
would require any change to the DSTE-REQTS document.

Note also that the proposal is just to take it out of the base spec, not
necessarily to drop it altogether (eg it could be documented separately
- perhaps as an experimetal RFC, like the BC Models). 

>> We already discussed the overbooking/underbooking issues
>> quite some time back. I don't think we, should change
>> requirement [DSTE-REQ] at this stage (past last call),
>> unless there is a real problem or limitation.
>> 
>> If we are trying to change the requirement because the 
>> LOM concept is difficult, 

I don't think the concern is that the LOM solution itself is too
complicated for the given requirement or not understood. To me it's more
a question of saying: now that we understand the ratio between the
functional benefit of the particular optional requirement and the
complexity associated with it, do we actually think it is worth keeping
in the base spec?

Now, you may feel that indeed it is worth and that LOM should stay in
base spec. But I wanted to be sure we were all looking at the same
question, and you're not feeling LOM should stay in simply because you
felt it is somehow mandated by the DSTE-REQTS.

Thanks

Francois

>>let's take steps to clarify
>> the concept by necessary editorial changes (and examples).
>> 
>> Thanks,
>> sanjay
>> 
>> > -----Original Message-----
>> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>> > Sent: Monday, May 26, 2003 9:05 AM
>> > To: te-wg@ops.ietf.org
>> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> > method from
>> > DS-TE specs?
>> > 
>> > 
>> > All TEWGers,
>> > 
>> > Thoughts on dropping/keeping LOM in base DS-TE specs?
>> > 
>> > Thanks
>> > 
>> > Francois
>> > 
>> > >> -----Original Message-----
>> > >> From: Francois Le Faucheur (flefauch) 
>> > >> Sent: 26 May 2003 14:59
>> > >> To: Kireeti Kompella; te-wg@ops.ietf.org
>> > >> Subject: Dropping the Local Overbooking Multiplier (LOM) 
>> > >> method from DS-TE specs?
>> > >> 
>> > >> 
>> > >> Kireeti,
>> > >> 
>> > >> Once upon a time, we merged 3 technical proposals for 
>> DS-TE (one of
>> > >> which was yours) into a common one. One of the 
>> > capabilities that was
>> > >> unique to your proposal was the ability to support 
>> > overbooking ratios
>> > >> which are different on a per CT AND per link basis 
>> (while the other
>> > >> methods supported different ratios on different links 
>> and different
>> > >> ratios on a per CT basis, not not on a per CT and per-link 
>> > >> basis). Back
>> > >> then you made a argument that there was some value in 
>> > allowing this.
>> > >> This resulted in the addition of the optional Local Overbooking
>> > >> Multiplier (LOM) method in the DS-TE specs.
>> > >> 
>> > >> A number of people commented that considering the ratio of 
>> > >> complexity vs
>> > >> functionality for this particular capability, we may be 
>> better off
>> > >> issueing the base DS-TE specs without this for now and 
>> > then add this
>> > >> capability later or in a separate document. I personnally 
>> > also favors
>> > >> such an approach.
>> > >> 
>> > >> What is your take on this?
>> > >> 
>> > >> Cheers
>> > >> 
>> > >> Francois
>> > >> 
>> > >> >> -----Original Message-----
>> > >> >> From: Jim Boyle [mailto:jboyle@pdnets.com] 
>> > >> >> Sent: 24 May 2003 02:31
>> > >> >> To: Francois Le Faucheur (flefauch)
>> > >> >> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
>> > >> >> Subject: RE: Reflecting new-MAM/SAM definition in 
>> > diff-te drafts 
>> > >> >> 
>> > >> >> 
>> > >> <clip>
>> > >> >> 
>> > >> >> btw... I also think LOMs are lots of complexity for 
>> > little gain :)
>> > >> >> 
>> > >> >> 
>> > >> >> 
>> > >> >> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
>> > >> >> 
>> > >> >> > Jerry,
>> > >> >> > 
>> > >> >> > >> -----Original Message-----
>> > >> >> > >> From: Ash, Gerald R (Jerry), ALABS 
>> [mailto:gash@att.com] 
>> > >> >> > >> Sent: 20 May 2003 17:35
>> > >> >> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
>> > >> >> > >> Cc: Ash, Gerald R (Jerry), ALABS; 
>> te-wg@ops.ietf.org; Lai, 
>> > >> >> > >> Wai S (Waisum), ALABS
>> > >> >> > >> Subject: RE: Reflecting new-MAM/SAM definition in 
>> > >> diff-te drafts
>> > >> >> > >> 
>> > >> >> > >> 
>> > >> >> > >> Dimitry, Francois,
>> > >> >> > >> 
>> > >> >> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable 
>> > Bandwidth, 
>> > >> >> > >> > >         for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> >> > >> > > 
>> > >> >> > >> > > However, this formula is incorrect for DS-TE 
>> > when per-CT 
>> > >> >> > >> > > LOM's are used, since the above formula only 
>> > >> >> reflects the Max 
>> > >> >> > >> > > Reservable Bandwidth for the entire link, 
>> and does not 
>> > >> >> > >> > > reflect the per-CT local overbooking 
>> factors.  So what 
>> > >> >> > >> > > formula do you suggest when per-CT LOM's are used?
>> > >> >> > >> 
>> > >> >> > >> > Wouldn't 'Reserved (CTc)' it the above 
>> formula already 
>> > >> >> > >> accounts for the
>> > >> >> > >> > overbooking multiplier at CTc?  I don't see how this 
>> > >> >> > >> formula precludes
>> > >> >> > >> > per-CT LOM's to be used. Please explain.
>> > >> >> > >> 
>> > >> >> > >> Are you then proposing these formulas:
>> > >> >> > >> 
>> > >> >> > >> 1. When per-CT LOMs are not used:
>> > >> >> > >> 
>> > >> >> > >>      o SUM (Reserved(CTc)) <= Max Reservable Bandwidth, 
>> > >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> >> > >> 
>> > >> >> > >> 2. When per-CT LOMs are used:
>> > >> >> > >> 
>> > >> >> > >>      o SUM (Normalized(CTc)) <= Max Reservable 
>> Bandwidth, 
>> > >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
>> > >> >> > >> 
>> > >> >> > >> Is that correct?  Please confirm, and/or give 
>> the formulas 
>> > >> >> > >> you propose.
>> > >> >> > 
>> > >> >> > Yes, this is exactly what I propose.
>> > >> >> > I think this is similar to what you were proposing, only 
>> > >> >> using "Max Res
>> > >> >> > Bw" instead of "Max Link Bw". 
>> > >> >> > 
>> > >> >> > Sorry I didn't make that very clear before.
>> > >> >> > 
>> > >> >> > Cheers
>> > >> >> > 
>> > >> >> > FRancois
>> > >> >> > 
>> > >> >> > >> 
>> > >> >> > >> Thanks,
>> > >> >> > >> Jerry
>> > >> >> > >> 
>> > >> >> > 
>> > >> >> > 
>> > >> >> > 
>> > >> >> > 
>> > >> >> 
>> > >> >> 
>> > >> 
>> > >> 
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed May 28 13:59:53 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA13676
	for <tewg-archive@lists.ietf.org>; Wed, 28 May 2003 13:59:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19L5AI-000Nq3-00
	for te-wg-data@psg.com; Wed, 28 May 2003 17:56:42 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19L5AE-000Nft-00
	for te-wg@ops.ietf.org; Wed, 28 May 2003 17:56:38 +0000
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA11156
	for <te-wg@ops.ietf.org>; Wed, 28 May 2003 13:54:42 -0400 (EDT)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA29774
	for <te-wg@ops.ietf.org>; Wed, 28 May 2003 13:54:43 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L2411G8Y>; Wed, 28 May 2003 13:54:42 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F54A1@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from D
	S-TE specs?
Date: Wed, 28 May 2003 13:54:34 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-9.8 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Hi!

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Wednesday, May 28, 2003 12:31 PM
> To: Choudhury, Sanjaya; te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> DS-TE specs?
> 
> 
> Hello Sanjaya,
> 
> >> -----Original Message-----
> >> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@marconi.com] 
> >> Sent: 28 May 2003 16:35
> >> To: te-wg@ops.ietf.org
> >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> >> method from DS-TE specs?
> >> 
> >> 
> >> Hi! DSTE-REQ already states that the per-CT overbooking
> >> is an optional feature and does not require the vendors
> >> to implement it.
> >>
> 
> For the record, the DSTE-REQTS spec does not define requirements for
> implementation/vendors. It defines requirements for the ds-te 
> solution.

	Missed "DSTE-PROTO" before the "and" in the original e-mail.
	Anyway, DSTE-REQ calls out for the solution draft to optionally
	support ability to tweak the overbooking factor of a CT in 
	different parts of the network. DSTE-PROTO already provides a 
	solution for this (as an optional feature). 

	I am not against moving the LOM feature into its own draft, but
	I fail to understand: What good does it do, to remove the 
	(already optional) LOM feature from the base spec? 

	If we move the LOM into its own draft, do the BC model drafts 
	still need to ensure that the model still works when LOM is in
	use? Or do we need more drafts to extend the BC model drafts?

	An aside: DSTE basically provides a per-CT knob on the LSRs. 
	And a per CT overbooking knob, might allow a provider to overbook
	the data traffic on a link, without overbooking the real-time
	traffic (on the same link) at the same level.

	Thanks,
	sanjay

> So, my interpretation of what its text says is just that the DS-TE
> solution should try to cope with the corresponding 
> requirement. In other
> words, to me, it is identified as an optional feature for the
> DSTE-solution (a feature that the DSTE solution should try 
> address, but
> may not address).
> 
> I really don't want to start a "DSTE-REQTS interpretation" 
> argument. The
> only reason I bring that up is to address your point below. ie I don't
> think the discussion we're having on taking LOM out of the base specs
> would require any change to the DSTE-REQTS document.
> 
> Note also that the proposal is just to take it out of the 
> base spec, not
> necessarily to drop it altogether (eg it could be documented 
> separately
> - perhaps as an experimetal RFC, like the BC Models). 
> 
> >> We already discussed the overbooking/underbooking issues
> >> quite some time back. I don't think we, should change
> >> requirement [DSTE-REQ] at this stage (past last call),
> >> unless there is a real problem or limitation.
> >> 
> >> If we are trying to change the requirement because the 
> >> LOM concept is difficult, 
> 
> I don't think the concern is that the LOM solution itself is too
> complicated for the given requirement or not understood. To 
> me it's more
> a question of saying: now that we understand the ratio between the
> functional benefit of the particular optional requirement and the
> complexity associated with it, do we actually think it is 
> worth keeping
> in the base spec?
> 
> Now, you may feel that indeed it is worth and that LOM should stay in
> base spec. But I wanted to be sure we were all looking at the same
> question, and you're not feeling LOM should stay in simply because you
> felt it is somehow mandated by the DSTE-REQTS.
> 
> Thanks
> 
> Francois
> 
> >>let's take steps to clarify
> >> the concept by necessary editorial changes (and examples).
> >> 
> >> Thanks,
> >> sanjay
> >> 
> >> > -----Original Message-----
> >> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> >> > Sent: Monday, May 26, 2003 9:05 AM
> >> > To: te-wg@ops.ietf.org
> >> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> >> > method from
> >> > DS-TE specs?
> >> > 
> >> > 
> >> > All TEWGers,
> >> > 
> >> > Thoughts on dropping/keeping LOM in base DS-TE specs?
> >> > 
> >> > Thanks
> >> > 
> >> > Francois
> >> > 
> >> > >> -----Original Message-----
> >> > >> From: Francois Le Faucheur (flefauch) 
> >> > >> Sent: 26 May 2003 14:59
> >> > >> To: Kireeti Kompella; te-wg@ops.ietf.org
> >> > >> Subject: Dropping the Local Overbooking Multiplier (LOM) 
> >> > >> method from DS-TE specs?
> >> > >> 
> >> > >> 
> >> > >> Kireeti,
> >> > >> 
> >> > >> Once upon a time, we merged 3 technical proposals for 
> >> DS-TE (one of
> >> > >> which was yours) into a common one. One of the 
> >> > capabilities that was
> >> > >> unique to your proposal was the ability to support 
> >> > overbooking ratios
> >> > >> which are different on a per CT AND per link basis 
> >> (while the other
> >> > >> methods supported different ratios on different links 
> >> and different
> >> > >> ratios on a per CT basis, not not on a per CT and per-link 
> >> > >> basis). Back
> >> > >> then you made a argument that there was some value in 
> >> > allowing this.
> >> > >> This resulted in the addition of the optional Local 
> Overbooking
> >> > >> Multiplier (LOM) method in the DS-TE specs.
> >> > >> 
> >> > >> A number of people commented that considering the ratio of 
> >> > >> complexity vs
> >> > >> functionality for this particular capability, we may be 
> >> better off
> >> > >> issueing the base DS-TE specs without this for now and 
> >> > then add this
> >> > >> capability later or in a separate document. I personnally 
> >> > also favors
> >> > >> such an approach.
> >> > >> 
> >> > >> What is your take on this?
> >> > >> 
> >> > >> Cheers
> >> > >> 
> >> > >> Francois
> >> > >> 
> >> > >> >> -----Original Message-----
> >> > >> >> From: Jim Boyle [mailto:jboyle@pdnets.com] 
> >> > >> >> Sent: 24 May 2003 02:31
> >> > >> >> To: Francois Le Faucheur (flefauch)
> >> > >> >> Cc: te-wg@ops.ietf.org; Lai, Wai S , ALABS
> >> > >> >> Subject: RE: Reflecting new-MAM/SAM definition in 
> >> > diff-te drafts 
> >> > >> >> 
> >> > >> >> 
> >> > >> <clip>
> >> > >> >> 
> >> > >> >> btw... I also think LOMs are lots of complexity for 
> >> > little gain :)
> >> > >> >> 
> >> > >> >> 
> >> > >> >> 
> >> > >> >> On Tue, 20 May 2003, Francois Le Faucheur (flefauch) wrote:
> >> > >> >> 
> >> > >> >> > Jerry,
> >> > >> >> > 
> >> > >> >> > >> -----Original Message-----
> >> > >> >> > >> From: Ash, Gerald R (Jerry), ALABS 
> >> [mailto:gash@att.com] 
> >> > >> >> > >> Sent: 20 May 2003 17:35
> >> > >> >> > >> To: Dimitry Haskin; Francois Le Faucheur (flefauch)
> >> > >> >> > >> Cc: Ash, Gerald R (Jerry), ALABS; 
> >> te-wg@ops.ietf.org; Lai, 
> >> > >> >> > >> Wai S (Waisum), ALABS
> >> > >> >> > >> Subject: RE: Reflecting new-MAM/SAM definition in 
> >> > >> diff-te drafts
> >> > >> >> > >> 
> >> > >> >> > >> 
> >> > >> >> > >> Dimitry, Francois,
> >> > >> >> > >> 
> >> > >> >> > >> > >     o SUM (Reserved (CTc)) <= Max Reservable 
> >> > Bandwidth, 
> >> > >> >> > >> > >         for all "c" in the range 0 <= c 
> <= (MaxCT-1)
> >> > >> >> > >> > > 
> >> > >> >> > >> > > However, this formula is incorrect for DS-TE 
> >> > when per-CT 
> >> > >> >> > >> > > LOM's are used, since the above formula only 
> >> > >> >> reflects the Max 
> >> > >> >> > >> > > Reservable Bandwidth for the entire link, 
> >> and does not 
> >> > >> >> > >> > > reflect the per-CT local overbooking 
> >> factors.  So what 
> >> > >> >> > >> > > formula do you suggest when per-CT LOM's are used?
> >> > >> >> > >> 
> >> > >> >> > >> > Wouldn't 'Reserved (CTc)' it the above 
> >> formula already 
> >> > >> >> > >> accounts for the
> >> > >> >> > >> > overbooking multiplier at CTc?  I don't see 
> how this 
> >> > >> >> > >> formula precludes
> >> > >> >> > >> > per-CT LOM's to be used. Please explain.
> >> > >> >> > >> 
> >> > >> >> > >> Are you then proposing these formulas:
> >> > >> >> > >> 
> >> > >> >> > >> 1. When per-CT LOMs are not used:
> >> > >> >> > >> 
> >> > >> >> > >>      o SUM (Reserved(CTc)) <= Max Reservable 
> Bandwidth, 
> >> > >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> > >> >> > >> 
> >> > >> >> > >> 2. When per-CT LOMs are used:
> >> > >> >> > >> 
> >> > >> >> > >>      o SUM (Normalized(CTc)) <= Max Reservable 
> >> Bandwidth, 
> >> > >> >> > >>          for all "c" in the range 0 <= c <= (MaxCT-1)
> >> > >> >> > >> 
> >> > >> >> > >> Is that correct?  Please confirm, and/or give 
> >> the formulas 
> >> > >> >> > >> you propose.
> >> > >> >> > 
> >> > >> >> > Yes, this is exactly what I propose.
> >> > >> >> > I think this is similar to what you were proposing, only 
> >> > >> >> using "Max Res
> >> > >> >> > Bw" instead of "Max Link Bw". 
> >> > >> >> > 
> >> > >> >> > Sorry I didn't make that very clear before.
> >> > >> >> > 
> >> > >> >> > Cheers
> >> > >> >> > 
> >> > >> >> > FRancois
> >> > >> >> > 
> >> > >> >> > >> 
> >> > >> >> > >> Thanks,
> >> > >> >> > >> Jerry
> >> > >> >> > >> 
> >> > >> >> > 
> >> > >> >> > 
> >> > >> >> > 
> >> > >> >> > 
> >> > >> >> 
> >> > >> >> 
> >> > >> 
> >> > >> 
> >> > 
> >> 
> >> 
> 



From owner-te-wg@ops.ietf.org  Thu May 29 07:25:58 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27128
	for <tewg-archive@lists.ietf.org>; Thu, 29 May 2003 07:25:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19LLSL-000Mu9-00
	for te-wg-data@psg.com; Thu, 29 May 2003 11:20:25 +0000
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19LLSG-000MsR-00; Thu, 29 May 2003 11:20:20 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26929;
	Thu, 29 May 2003 07:20:18 -0400 (EDT)
Message-Id: <200305291120.HAA26929@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mpls@uu.net, te-wg@ops.ietf.org, ccamp@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-mgmt-overview-05.txt
Date: Thu, 29 May 2003 07:20:17 -0400
X-Spam-Status: No, hits=0.0 required=5.0
	tests=BAYES_20,MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF.

	Title		: Multiprotocol Label Switching (MPLS) Management    
                          Overview
	Author(s)	: T. Nadeau, C. Srinivasan, A. Farrel
	Filename	: draft-ietf-mpls-mgmt-overview-05.txt
	Pages		: 28
	Date		: 2003-5-28
	
A range of Management Information Base (MIB) modules has
been developed to help model and manage the various aspects
of Multiprotocol Label Switching (MPLS) networks.  These MIB
modules are defined in separate documents that focus on the
specific areas of responsibility of the modules that they
describe.
This memo describes the management architecture for MPLS
and indicates the inter-relationships between the different
MIB modules used for MPLS network management.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mpls-mgmt-overview-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-ietf-mpls-mgmt-overview-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-ietf-mpls-mgmt-overview-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:	<2003-5-29072815.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-mpls-mgmt-overview-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-mpls-mgmt-overview-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-5-29072815.I-D@ietf.org>

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Thu May 29 09:18:03 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02526
	for <tewg-archive@lists.ietf.org>; Thu, 29 May 2003 09:18:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19LNFo-000Gw5-00
	for te-wg-data@psg.com; Thu, 29 May 2003 13:15:36 +0000
Received: from webmail.movaz.com ([65.205.166.188] helo=jera.movaz.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19LNFl-000Gvi-00; Thu, 29 May 2003 13:15:33 +0000
Received: from BLIULAPTOP (unknown [172.16.24.104])
	by jera.movaz.com (Postfix) with ESMTP
	id 954C01483; Thu, 29 May 2003 09:15:32 -0400 (EDT)
Message-ID: <028801c325e4$622fb210$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <mpls@UU.NET>, <te-wg@ops.ietf.org>, <ccamp@ops.ietf.org>
References: <200305291120.HAA26929@ietf.org>
Subject: Re: I-D ACTION:draft-ietf-mpls-mgmt-overview-05.txt
Date: Thu, 29 May 2003 09:15:32 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
X-Spam-Status: No, hits=-19.1 required=5.0
	tests=BAYES_20,ORIGINAL_MESSAGE,QUOTED_EMAIL_TEXT,REFERENCES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

FYI,

Changes are minor nits and synchronization of new (final?) versions of the MIB
drafts that have come out.

Adrian
----- Original Message -----
From: <Internet-Drafts@ietf.org>
To: <IETF-Announce: ;>
Cc: <mpls@UU.NET>; <te-wg@ops.ietf.org>; <ccamp@ops.ietf.org>
Sent: Thursday, May 29, 2003 7:20 AM
Subject: I-D ACTION:draft-ietf-mpls-mgmt-overview-05.txt


> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> This draft is a work item of the Multiprotocol Label Switching Working Group
of the IETF.
>
> Title : Multiprotocol Label Switching (MPLS) Management
>                           Overview
> Author(s) : T. Nadeau, C. Srinivasan, A. Farrel
> Filename : draft-ietf-mpls-mgmt-overview-05.txt
> Pages : 28
> Date : 2003-5-28
>
> A range of Management Information Base (MIB) modules has
> been developed to help model and manage the various aspects
> of Multiprotocol Label Switching (MPLS) networks.  These MIB
> modules are defined in separate documents that focus on the
> specific areas of responsibility of the modules that they
> describe.
> This memo describes the management architecture for MPLS
> and indicates the inter-relationships between the different
> MIB modules used for MPLS network management.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-mgmt-overview-05.txt
>






From owner-te-wg@ops.ietf.org  Fri May 30 07:19:15 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28727
	for <tewg-archive@lists.ietf.org>; Fri, 30 May 2003 07:19:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19LhqW-0001Yi-00
	for te-wg-data@psg.com; Fri, 30 May 2003 11:14:52 +0000
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19LhqU-0001YU-00
	for te-wg@ops.ietf.org; Fri, 30 May 2003 11:14:50 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28358;
	Fri, 30 May 2003 07:14:46 -0400 (EDT)
Message-Id: <200305301114.HAA28358@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-00.txt
Date: Fri, 30 May 2003 07:14:46 -0400
X-Spam-Status: No, hits=0.0 required=5.0
	tests=BAYES_20,MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Traffic Engineering Working Group of the IETF.

	Title		: MPLS Inter-AS Traffic Engineering requirements
	Author(s)	: R. Zhang, J. Vasseur
	Filename	: draft-ietf-tewg-interas-mpls-te-req-00.txt
	Pages		: 23
	Date		: 2003-5-29
	
This document discusses requirements for the support of inter-AS
MPLS Traffic Engineering (MPLS TE).  The main objective of this
document is to present a set of requirements which would result in
a set of general guidelines in the definition, selection and
specification development for any technical solution(s) meeting
these requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-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-ietf-tewg-interas-mpls-te-req-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-ietf-tewg-interas-mpls-te-req-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.

--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:	<2003-5-29161629.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-interas-mpls-te-req-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-tewg-interas-mpls-te-req-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-5-29161629.I-D@ietf.org>

--OtherAccess--

--NextPart--





