From owner-te-wg@ops.ietf.org  Sun Jun  1 20:05: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 UAA06803
	for <tewg-archive@lists.ietf.org>; Sun, 1 Jun 2003 20:05:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Mcis-0003wv-00
	for te-wg-data@psg.com; Sun, 01 Jun 2003 23:58:46 +0000
Received: from 75.209.219.209.transedge.com ([209.219.209.75] helo=ckmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Mcip-0003wj-00
	for te-wg@ops.ietf.org; Sun, 01 Jun 2003 23:58:43 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h51Nwbuq025409
	for <te-wg@ops.ietf.org>; Sun, 1 Jun 2003 19:58:42 -0400
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC766020048833C for te-wg@ops.ietf.org; Sun, 1 Jun 2003 19:58: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="iso-8859-1"
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Sun, 1 Jun 2003 18:58:42 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE984@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcow
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-Spam-Status: No, hits=-3.1 required=5.0
	tests=BAYES_20
	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 UAA06803

All,

I'm not sure where we stand on keeping LOM or dropping LOM.

If we keep LOM, it is possible to re-define LOM so as to simplify the rather complicated 3-way approach to overbooking that now exists:

LSPOMc = LSP overbooking multiplier for CTc
LSOM = link size overbooking multiplier
LOMc = local overbooking multiplier for CTc

If LOM is retained, Wai Sum and I propose to redefine LOM (calling it LOM') to provide an overall simplification of this 3-way overbooking complexity, as follows.

Define:

LSPOMc = LSP overbooking multiplier for CTc
LSOM = link size overbooking multiplier
LSOM = maximum reservable bandwidth/maximum link bandwidth
LOMc = local overbooking multiplier for CTc (original definition of LOMc)
LOM'c = redefined local overbooking multiplier LOMc for CTc
LOM'c = LSOM * LSPOMc * LOMc

Given:
requested LSP CTc = RSVP-TE Tspec LSP bandwidth specified in TLV

Then the following general equation applies:
reserved CTc = requested LSP CTc/LOM'c                       (1)

wherein there are several cases of equation (1) for reserved CTc:

1. Link Size Overbooking only:
    LSPOMc = 1, LOMc = 1, for all c
    LOM'c = LSOM, or equivalently
    reserved CTc = requested LSP CTc/LSOM = requested LSP CTc/LOM'c
2. LSP Size Overbooking only:
    LSOM = 1, LOMc = 1, for all c
    LOM'c = LSPOMc for all c, or equivalently
    reserved CTc = requested LSP CTc/LSPOMc = requested LSP CTc/LOM'c
3. Both Link Size Overbooking and LSP Size Overbooking:
    LOMc = 1, for all c
    LOM'c = LSOM * LSPOMc, or equivalently
    reserved CTc = requested LSP CTc/(LSOM * LSPOMc) = requested LSP CTc/LOM'c
 4. LOM in conjunction with the above cases 1, 2, or 3
    reserved CTc = requested LSP CTc/LOM'c

In this model, the aggregate constraint becomes:

 o SUM (Reserved(CTc)) <= MLBW                               (2)
     for all "c" in the range 0 <= c <= (MaxCT-1)

We believe that this simplification, as summarized in equations (1) and (2) above, is worthwhile if LOM is retained.

Comments welcome.

Thanks,
Jerry & Wai Sum




From owner-te-wg@ops.ietf.org  Mon Jun  2 04:51:18 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28360
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 04:51:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Mkyu-000MzA-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 08:47:52 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Mkyp-000Myn-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 08:47:47 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 02 Jun 2003 10:46:56 +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 h528jWsB014048;
	Mon, 2 Jun 2003 10:45: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, 2 Jun 2003 10:47:42 +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, 2 Jun 2003 09:47:23 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5255@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlQzWuVgqeN/SiQZ2rN9x9Kycs4QDnmC4g
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 02 Jun 2003 08:47:42.0575 (UTC) FILETIME=[A152C7F0:01C328E3]
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 EAA28360

Hello Sanjaya,

>> > 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, 

Noted.

>>but
>> 	I fail to understand: What good does it do, to remove the 
>> 	(already optional) LOM feature from the base spec? 
>> 

To me the main benefits are:
	- make the DS-TE core specifications simpler (to read,
implement, deploy) and thus maximise its chances of sucessful deployment
	- would allow us to progress LOM in the "Experimental" track,
which I think matches better the TEWG feel (ie something that may or may
not be useful and where experience will tell).

>> 	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?
>> 

My proposal would be that the single LOM draft discusses (i) the concept
of LOMs, (ii) the BC-model-independent aspects of LOMs (eg. IGP
extensions, applying constraints to Normalised vs Reserved) and (iii)
the BC-model-specific aspects (eg take the CAC/Unreserved-Bw formuals
that are currently in -russian and -mam ). So I think a single draft
could cover all the aspects of LOM. Again, that is a good property o
LOM, it has been defined as a pure "increment" of LSP/Size overbooking
and is thus very easy to keep in or out.

>> 	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.
>> 

Yes, as discussed, there is quite a lot we can do without LOM.

Thanks

Francois

>> 	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  Mon Jun  2 05: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 FAA29473
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 05:27:53 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Mlaa-000OWz-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 09:26:48 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19MlaX-000OWa-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 09:26:46 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 02 Jun 2003 11:25:51 +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 h529OcMH022415
	for <te-wg@ops.ietf.org>; Mon, 2 Jun 2003 11:24: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);
	 Mon, 2 Jun 2003 11:26: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: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Date: Mon, 2 Jun 2003 10:26:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5256@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABPsUAA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 02 Jun 2003 09:26:36.0590 (UTC) FILETIME=[108134E0:01C328E9]
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA29473

All,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 02 June 2003 01:59
>> To: te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
>> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> All,
>> 
>> I'm not sure where we stand on keeping LOM or dropping LOM.

My perception is that, so far, :
	- a number of people have argued in favor of taking LOM out of
the base spec (incl Dimitry, Jerry, Siva, myself)
	- some people (I believe this includes Sanjaya) would have a
problem if the LOM work was completely "dropped", but would not have a
problem if LOM is documented in a seperate document. 
	- some people (eg Sandy) inquired about whether we could not
achieve the same net effect without LOM anyway, but now agree that,
while we can do quite a lot without LOM, it is not possible to
(accurately) meet the (debated) extra requirement.
	- noone has expressed objections to taking LOM out of the base
spec to move it to another document.

Based on this, unless we hear different opinions shortly, my proposal
will be to:
	- issue the next versions of -proto, -russian and -mam without
LOM, so these can go to IESG Last Call promptly (Standards for -proto,
Experimental for -russian and -mam)
	- issue a separate document (-lom) on LOM which can be
progressed in Experimental track.

Please let me know if you have concerns with this proposal.

Cheers

Francois



From owner-te-wg@ops.ietf.org  Mon Jun  2 08:03: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 IAA03326
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 08:03:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Mo0S-0004Zr-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 12:01:40 +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 19Mo0O-0004Zf-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 12:01:36 +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 h52BiIlN005425
	for <te-wg@ops.ietf.org>; Mon, 2 Jun 2003 08:01:35 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC76602004A69B1; Mon, 2 Jun 2003 08:01:33 -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, 2 Jun 2003 07:01:34 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A67FD@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/A=
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>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.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 IAA03326

Francois, All,

> no one has expressed objections to taking LOM out of the base
> spec to move it to another document.

I believe Sanjay objected, and I think he made a good point.  Either we should agree to drop LOM completely (no 'separate document' and/or Experimental track for LOM), or leave it in.  If it is progressed as a separate document/Experimental track, this would complicate backward compatibility for all the BC models.
 
> Based on this, unless we hear different opinions shortly, my proposal
> will be to:
> 	- issue the next versions of -proto, -russian and -mam without
> LOM, so these can go to IESG Last Call promptly (Standards for -proto,
> Experimental for -russian and -mam)

Wai Sum and I have already expressed a different opinion in the proposed re-definition of LOM.  Before we agree to drop the LOM feature, we'd like to see some discussion on the alternative proposal to simplify the rather complicated 3-way approach to overbooking that now exists.  See below.

You've also forgotten to mention -mar in the above.

> 	- issue a separate document (-lom) on LOM which can be
> progressed in Experimental track.

As above, I'm against a separate Experimental track for LOM, because this would complicate backward compatibility for all the BC models.  Otherwise, we need to explain how LOM can be introduced into the BC models later on, and avoid a transition/interoperability problem.  It seems that with the proposed separate track, LOM is functionally dead, but not officially dead.  I think we should either officially kill LOM, or retain it (but perhaps re-defined).
 
> Please let me know if you have concerns with this proposal.

Yes, 2 concerns:

1. As above, if LOM is progressed separately, we need to explain how LOM can be introduced into the BC models later on, and avoid a transition/interoperability problem.  I think it would be preferable to officially kill LOM, rather than leave it in the proposed 'separate track'.

2. Before we agree to drop the LOM feature, we'd like to see some discussion on the alternative proposal to redefine LOM (to LOM'), in order to simplify the rather complicated 3-way approach to overbooking that now exists:

LSPOMc = LSP overbooking multiplier for CTc
LSOM = link size overbooking multiplier
LOMc = local overbooking multiplier for CTc

If LOM is retained, Wai Sum and I propose to redefine LOM (calling it LOM') to provide an overall simplification of this 3-way overbooking complexity, as follows.

Define:

LSPOMc = LSP overbooking multiplier for CTc
LSOM = link size overbooking multiplier
LSOM = maximum reservable bandwidth/maximum link bandwidth
LOMc = local overbooking multiplier for CTc (original definition of LOMc)
LOM'c = redefined local overbooking multiplier LOMc for CTc
LOM'c = LSOM * LSPOMc * LOMc

Given:
requested LSP CTc = RSVP-TE Tspec LSP bandwidth specified in TLV

Then the following general equation applies:
reserved CTc = requested LSP CTc/LOM'c                       (1)

wherein there are several cases of equation (1) for reserved CTc:

1. Link Size Overbooking only:
    LSPOMc = 1, LOMc = 1, for all c
    LOM'c = LSOM, or equivalently
    reserved CTc = requested LSP CTc/LSOM = requested LSP CTc/LOM'c
2. LSP Size Overbooking only:
    LSOM = 1, LOMc = 1, for all c
    LOM'c = LSPOMc for all c, or equivalently
    reserved CTc = requested LSP CTc/LSPOMc = requested LSP CTc/LOM'c
3. Both Link Size Overbooking and LSP Size Overbooking:
    LOMc = 1, for all c
    LOM'c = LSOM * LSPOMc, or equivalently
    reserved CTc = requested LSP CTc/(LSOM * LSPOMc) = requested LSP CTc/LOM'c
 4. LOM in conjunction with the above cases 1, 2, or 3
    reserved CTc = requested LSP CTc/LOM'c

In this model, the aggregate constraint becomes:

 o SUM (Reserved(CTc)) <= MLBW                               (2)
     for all "c" in the range 0 <= c <= (MaxCT-1)

We believe that this simplification, as summarized in equations (1) and (2) above, is worthwhile if LOM is retained.

Thanks,
Jerry & Wai Sum



From owner-te-wg@ops.ietf.org  Mon Jun  2 09:05: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 JAA05550
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 09:05:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Moxr-0007LM-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 13:03:03 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Moxb-0007Ij-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 13:02:51 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 02 Jun 2003 15:01:11 +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 h52CxAW8000174;
	Mon, 2 Jun 2003 14:59: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);
	 Mon, 2 Jun 2003 15:01:34 +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, 2 Jun 2003 14:01:33 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5257@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/AAAV41YA==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 02 Jun 2003 13:01:34.0281 (UTC) FILETIME=[1820AB90:01C32907]
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 JAA05550

Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 02 June 2003 14:02
>> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
>> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> Francois, All,
>> 
>> > no one has expressed objections to taking LOM out of the base
>> > spec to move it to another document.
>> 
>> I believe Sanjay objected, 

I am sure will hear from Sanjay soon, but quoting from his email:
>> 	I am not against moving the LOM feature into its own draft, 
Doesn't sound like an objection to me.

So I think it is fair to say that noone has expressed any objection (at
this stage anyway).

>>and I think he made a good point. 
>>  Either we should agree to drop LOM completely (no 'separate 
>> document' and/or Experimental track for LOM), or leave it 
>> in.  If it is progressed as a separate document/Experimental 
>> track, this would complicate backward compatibility for all 
>> the BC models.
>>

Whether we keep the text on LOM distributed over -proto, -russian, -mam
(and perhaps in MAR if you have added that in) as it is today or whether
we redistribute it into a single standalone document does not affect
backward compatibility. We're only talking about redistributing the same
text in a different set of documents so we can make one document
Experimental.
  
>> > Based on this, unless we hear different opinions shortly, 
>> my proposal
>> > will be to:
>> > 	- issue the next versions of -proto, -russian and -mam without
>> > LOM, so these can go to IESG Last Call promptly (Standards 
>> for -proto,
>> > Experimental for -russian and -mam)
>> 
>> Wai Sum and I have already expressed a different opinion in 
>> the proposed re-definition of LOM.  Before we agree to drop 
>> the LOM feature, we'd like to see some discussion on the 
>> alternative proposal to simplify the rather complicated 
>> 3-way approach to overbooking that now exists.  See below.

The current approach is NOT complicated. Please see the specific email
on this. Note that its two main components (Link/Size Overbooking) are
directly inherited from existing TE. These two should not be modified in
any way so they remain backward compatible with existing TE anyway.
The current model works, all formulas are documented and we had lots of
discussion so everybody is fully synched up on it now.
I see no justification to enter a new round of let's reinvent the
overbooking model for DS-TE at this post Last-Call stage.

>> 
>> You've also forgotten to mention -mar in the above.
>> 
>> > 	- issue a separate document (-lom) on LOM which can be
>> > progressed in Experimental track.
>> 
>> As above, I'm against a separate Experimental track for LOM, 
>> because this would complicate backward compatibility for all 
>> the BC models.  Otherwise, we need to explain how LOM can be 
>> introduced into the BC models later on, and avoid a 
>> transition/interoperability problem.  It seems that with the 
>> proposed separate track, LOM is functionally dead, but not 
>> officially dead.  I think we should either officially kill 
>> LOM, or retain it (but perhaps re-defined).
>>  

The idea of Experimental is that LOM would be neither "dead" nor
"standards". It would suggest that LOM is something we've discussed and
documented and some people may want to play with. Experience will tell
us what we should do with it.
Another good thing with Experimental is that I don't think we have to
all agree that it is a useful thing as long as some people do. I
personally would have no problem in dropping LOM altogether, but my
impression was that some people had a problem in dropping it altogether
because we just don't really know whether it will be useful or not. That
sounded like Experimental track to me.

Do you feel there is rough concensus to drop LOM altogether (that would
work for me)?

Cheers

Francois

>> > Please let me know if you have concerns with this proposal.
>> 
>> Yes, 2 concerns:
>> 
>> 1. As above, if LOM is progressed separately, we need to 
>> explain how LOM can be introduced into the BC models later 
>> on, and avoid a transition/interoperability problem.  I 
>> think it would be preferable to officially kill LOM, rather 
>> than leave it in the proposed 'separate track'.
>> 
>> 2. Before we agree to drop the LOM feature, we'd like to see 
>> some discussion on the alternative proposal to redefine LOM 
>> (to LOM'), in order to simplify the rather complicated 3-way 
>> approach to overbooking that now exists:
>> 
>> LSPOMc = LSP overbooking multiplier for CTc
>> LSOM = link size overbooking multiplier
>> LOMc = local overbooking multiplier for CTc
>> 
>> If LOM is retained, Wai Sum and I propose to redefine LOM 
>> (calling it LOM') to provide an overall simplification of 
>> this 3-way overbooking complexity, as follows.
>> 
>> Define:
>> 
>> LSPOMc = LSP overbooking multiplier for CTc
>> LSOM = link size overbooking multiplier
>> LSOM = maximum reservable bandwidth/maximum link bandwidth
>> LOMc = local overbooking multiplier for CTc (original 
>> definition of LOMc)
>> LOM'c = redefined local overbooking multiplier LOMc for CTc
>> LOM'c = LSOM * LSPOMc * LOMc
>> 
>> Given:
>> requested LSP CTc = RSVP-TE Tspec LSP bandwidth specified in TLV
>> 
>> Then the following general equation applies:
>> reserved CTc = requested LSP CTc/LOM'c                       (1)
>> 
>> wherein there are several cases of equation (1) for reserved CTc:
>> 
>> 1. Link Size Overbooking only:
>>     LSPOMc = 1, LOMc = 1, for all c
>>     LOM'c = LSOM, or equivalently
>>     reserved CTc = requested LSP CTc/LSOM = requested LSP CTc/LOM'c
>> 2. LSP Size Overbooking only:
>>     LSOM = 1, LOMc = 1, for all c
>>     LOM'c = LSPOMc for all c, or equivalently
>>     reserved CTc = requested LSP CTc/LSPOMc = requested LSP CTc/LOM'c
>> 3. Both Link Size Overbooking and LSP Size Overbooking:
>>     LOMc = 1, for all c
>>     LOM'c = LSOM * LSPOMc, or equivalently
>>     reserved CTc = requested LSP CTc/(LSOM * LSPOMc) = 
>> requested LSP CTc/LOM'c
>>  4. LOM in conjunction with the above cases 1, 2, or 3
>>     reserved CTc = requested LSP CTc/LOM'c
>> 
>> In this model, the aggregate constraint becomes:
>> 
>>  o SUM (Reserved(CTc)) <= MLBW                               (2)
>>      for all "c" in the range 0 <= c <= (MaxCT-1)
>> 
>> We believe that this simplification, as summarized in 
>> equations (1) and (2) above, is worthwhile if LOM is retained.
>> 
>> Thanks,
>> Jerry & Wai Sum
>> 



From owner-te-wg@ops.ietf.org  Mon Jun  2 10:39: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 KAA10171
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 10:39:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19MqNp-000BYz-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 14:33:57 +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 19MqNm-000BYl-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 14:33:54 +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 h52DwWmu023198
	for <te-wg@ops.ietf.org>; Mon, 2 Jun 2003 10:33:53 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC76602004B681E; Mon, 2 Jun 2003 10:33:50 -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, 2 Jun 2003 09:33:52 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE989@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/AAAV41YAAC+n9w
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>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.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 KAA10171

Francois, All,

> The current approach is NOT complicated. Please see the specific email
> on this. 

That's your view, but I don't think it constitutes a proof of same :-)

> Note that its two main components (Link/Size Overbooking) are
> directly inherited from existing TE. These two should not be modified in
> any way so they remain backward compatible with existing TE anyway.
> The current model works, all formulas are documented and we had lots of
> discussion so everybody is fully synched up on it now.
> I see no justification to enter a new round of let's reinvent the
> overbooking model for DS-TE at this post Last-Call stage.

I expected this comment, of course.  However, DS-TE is a *new* environment (CTs, BC models, etc.), and we should have the right to define things within that new environment.

However, so as to not drag this out, and come to closure, I'm OK to go with your proposed formulas, pending a final agreement on LOM (see below):


When LOM is NOT used (i.e. 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

When LOM is used 
===============================
o for each value of b in the range 0 <= b <= 7:
  Normalized (CTb) <= BCb,
o SUM (Normalized(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 (i.e. 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 ( Normalized(CTb,q) ) ] for q <= p,
[ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p and 0 <= b <= 7,]
where:
TE-Class [i] <--> < CTc , preemption p> 

> The idea of Experimental is that LOM would be neither "dead" nor
> "standards". It would suggest that LOM is something we've discussed and
> documented and some people may want to play with. Experience will tell
> us what we should do with it.
> Another good thing with Experimental is that I don't think we have to
> all agree that it is a useful thing as long as some people do. I
> personally would have no problem in dropping LOM altogether, but my
> impression was that some people had a problem in dropping it altogether
> because we just don't really know whether it will be useful or not. That
> sounded like Experimental track to me.
> 
> Do you feel there is rough consensus to drop LOM altogether (that would
> work for me)?

I have not seen anyone give an example of where LOM is needed.  Unless we see that, my preference would be to drop it.  LOM is a real parameter, and at present needs to be carried in the RSVP extensions for DS-TE.  It requires addition aggregation constraints in the BC models.

Considerations of per-CT and hi-speed vs. low-speed links can be easily accommodated, as I gave in an example by using just LSPOM and LSOM (see earlier post http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00314.html).  It seems like much more than enough flexibility to avoid any problems, without also further complication with LOM.  

Can anyone explain why LOM would be needed, and in particular, give a practical example of same?

It seems to have marginal value (I don't see anyone showing how it is needed, or really supporting it).  I think we can agree that simplification *will* be achieved if we eliminate LOM.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Mon Jun  2 11:21: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 LAA11779
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 11:21:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Mr60-000DmS-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 15:19:36 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Mr5w-000Dm4-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 15:19:32 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 02 Jun 2003 17:18:41 +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 h52FHSHE027439;
	Mon, 2 Jun 2003 17:17:32 +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, 2 Jun 2003 17:18:49 +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, 2 Jun 2003 16:18:48 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5259@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/AAAV41YAAC+n9wAAKjKrA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 02 Jun 2003 15:18:49.0584 (UTC) FILETIME=[44C02F00:01C3291A]
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 LAA11779

Hello Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 02 June 2003 16:34
>> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
>> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> Francois, All,
>> 
>> > The current approach is NOT complicated. Please see the 
>> specific email
>> > on this. 
>> 
>> That's your view, but I don't think it constitutes a proof 
>> of same :-)
>> 

Absolutely right. 
Just like I would rather see statement saying that someone finds the
current model rather complicated as opposed to statement saying it is
rather complicated. 8^)

>> > Note that its two main components (Link/Size Overbooking) are
>> > directly inherited from existing TE. These two should not 
>> be modified in
>> > any way so they remain backward compatible with existing TE anyway.
>> > The current model works, all formulas are documented and 
>> we had lots of
>> > discussion so everybody is fully synched up on it now.
>> > I see no justification to enter a new round of let's reinvent the
>> > overbooking model for DS-TE at this post Last-Call stage.
>> 
>> I expected this comment, of course.  However, DS-TE is a 
>> *new* environment (CTs, BC models, etc.), and we should have 
>> the right to define things within that new environment.
>> 
>> However, so as to not drag this out, and come to closure, 
>> I'm OK to go with your proposed formulas, pending a final 
>> agreement on LOM (see below):
>> 
>> 

Great. This should allow us to move ahead fast as soon as we make a
final call on what to do with LOM.

>> When LOM is NOT used (i.e. 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
>> 
>> When LOM is used 
>> ===============================
>> o for each value of b in the range 0 <= b <= 7:
>>   Normalized (CTb) <= BCb,
>> o SUM (Normalized(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 (i.e. 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 ( Normalized(CTb,q) ) ] for q <= p,
>> [ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p 
>> and 0 <= b <= 7,]
>> where:
>> TE-Class [i] <--> < CTc , preemption p> 
>> 
>> > The idea of Experimental is that LOM would be neither "dead" nor
>> > "standards". It would suggest that LOM is something we've 
>> discussed and
>> > documented and some people may want to play with. 
>> Experience will tell
>> > us what we should do with it.
>> > Another good thing with Experimental is that I don't think 
>> we have to
>> > all agree that it is a useful thing as long as some people do. I
>> > personally would have no problem in dropping LOM altogether, but my
>> > impression was that some people had a problem in dropping 
>> it altogether
>> > because we just don't really know whether it will be 
>> useful or not. That
>> > sounded like Experimental track to me.
>> > 
>> > Do you feel there is rough consensus to drop LOM 
>> altogether (that would
>> > work for me)?
>> 
>> I have not seen anyone give an example of where LOM is 
>> needed.  Unless we see that, my preference would be to drop 
>> it.  LOM is a real parameter, and at present needs to be 
>> carried in the RSVP extensions for DS-TE.  It requires 
>> addition aggregation constraints in the BC models.
>> 
>> Considerations of per-CT and hi-speed vs. low-speed links 
>> can be easily accommodated, as I gave in an example by using 
>> just LSPOM and LSOM (see earlier post 
>> http://ops.ietf.org/lists/te-wg/te->> wg.2003/msg00314.html).  
>> It seems like much more than 
>> enough flexibility to avoid any problems, without also 
>> further complication with LOM.  
>> 
>> Can anyone explain why LOM would be needed, and in 
>> particular, give a practical example of same?
>> 
>> It seems to have marginal value (I don't see anyone showing 
>> how it is needed, or really supporting it).  I think we can 
>> agree that simplification *will* be achieved if we eliminate LOM.

We can certainly agree on that.

So let's see if we hear some justiication for LOM or not, and based on
that we can finalise decision (hopefully within a few days) firstly to
take LOM out of base specs, and secondly to drop altogether (or document
as Experimental).

Cheers

Francois

>> 
>> Thanks,
>> Jerry
>> 



From owner-te-wg@ops.ietf.org  Mon Jun  2 12:04: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 MAA13395
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 12:04:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Mrl5-000GHW-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 16:02:03 +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 19Mrl2-000GFP-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 16:02:00 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F66A@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>, te-wg@ops.ietf.org
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method from D
	S-TE specs?
Date: Mon, 2 Jun 2003 12:00:28 -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

I agree with Francois. Let's remove LOM from the base spec and not to
venture on another round of unnecessary redefinitions of the base spec.

As a side note, I would not be too upset if no separate LOM spec follows any
soon. I'd let someone who feels that there is a real practical need for LOM
to pick up the LOM torch.

Dimitry

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Monday, June 02, 2003 9:02 AM
> To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> DS-TE specs?
> 
> 
> Jerry,
> 
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> >> Sent: 02 June 2003 14:02
> >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
> >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
> >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> >> method from DS-TE specs?
> >> 
> >> 
> >> Francois, All,
> >> 
> >> > no one has expressed objections to taking LOM out of the base
> >> > spec to move it to another document.
> >> 
> >> I believe Sanjay objected, 
> 
> I am sure will hear from Sanjay soon, but quoting from his email:
> >> 	I am not against moving the LOM feature into its own draft, 
> Doesn't sound like an objection to me.
> 
> So I think it is fair to say that noone has expressed any 
> objection (at
> this stage anyway).
> 
> >>and I think he made a good point. 
> >>  Either we should agree to drop LOM completely (no 'separate 
> >> document' and/or Experimental track for LOM), or leave it 
> >> in.  If it is progressed as a separate document/Experimental 
> >> track, this would complicate backward compatibility for all 
> >> the BC models.
> >>
> 
> Whether we keep the text on LOM distributed over -proto, 
> -russian, -mam
> (and perhaps in MAR if you have added that in) as it is today 
> or whether
> we redistribute it into a single standalone document does not affect
> backward compatibility. We're only talking about 
> redistributing the same
> text in a different set of documents so we can make one document
> Experimental.
>   
> >> > Based on this, unless we hear different opinions shortly, 
> >> my proposal
> >> > will be to:
> >> > 	- issue the next versions of -proto, -russian and -mam without
> >> > LOM, so these can go to IESG Last Call promptly (Standards 
> >> for -proto,
> >> > Experimental for -russian and -mam)
> >> 
> >> Wai Sum and I have already expressed a different opinion in 
> >> the proposed re-definition of LOM.  Before we agree to drop 
> >> the LOM feature, we'd like to see some discussion on the 
> >> alternative proposal to simplify the rather complicated 
> >> 3-way approach to overbooking that now exists.  See below.
> 
> The current approach is NOT complicated. Please see the specific email
> on this. Note that its two main components (Link/Size Overbooking) are
> directly inherited from existing TE. These two should not be 
> modified in
> any way so they remain backward compatible with existing TE anyway.
> The current model works, all formulas are documented and we 
> had lots of
> discussion so everybody is fully synched up on it now.
> I see no justification to enter a new round of let's reinvent the
> overbooking model for DS-TE at this post Last-Call stage.
> 
> >> 
> >> You've also forgotten to mention -mar in the above.
> >> 
> >> > 	- issue a separate document (-lom) on LOM which can be
> >> > progressed in Experimental track.
> >> 
> >> As above, I'm against a separate Experimental track for LOM, 
> >> because this would complicate backward compatibility for all 
> >> the BC models.  Otherwise, we need to explain how LOM can be 
> >> introduced into the BC models later on, and avoid a 
> >> transition/interoperability problem.  It seems that with the 
> >> proposed separate track, LOM is functionally dead, but not 
> >> officially dead.  I think we should either officially kill 
> >> LOM, or retain it (but perhaps re-defined).
> >>  
> 
> The idea of Experimental is that LOM would be neither "dead" nor
> "standards". It would suggest that LOM is something we've 
> discussed and
> documented and some people may want to play with. Experience will tell
> us what we should do with it.
> Another good thing with Experimental is that I don't think we have to
> all agree that it is a useful thing as long as some people do. I
> personally would have no problem in dropping LOM altogether, but my
> impression was that some people had a problem in dropping it 
> altogether
> because we just don't really know whether it will be useful 
> or not. That
> sounded like Experimental track to me.
> 
> Do you feel there is rough concensus to drop LOM altogether 
> (that would
> work for me)?
> 
> Cheers
> 
> Francois
> 
> >> > Please let me know if you have concerns with this proposal.
> >> 
> >> Yes, 2 concerns:
> >> 
> >> 1. As above, if LOM is progressed separately, we need to 
> >> explain how LOM can be introduced into the BC models later 
> >> on, and avoid a transition/interoperability problem.  I 
> >> think it would be preferable to officially kill LOM, rather 
> >> than leave it in the proposed 'separate track'.
> >> 
> >> 2. Before we agree to drop the LOM feature, we'd like to see 
> >> some discussion on the alternative proposal to redefine LOM 
> >> (to LOM'), in order to simplify the rather complicated 3-way 
> >> approach to overbooking that now exists:
> >> 
> >> LSPOMc = LSP overbooking multiplier for CTc
> >> LSOM = link size overbooking multiplier
> >> LOMc = local overbooking multiplier for CTc
> >> 
> >> If LOM is retained, Wai Sum and I propose to redefine LOM 
> >> (calling it LOM') to provide an overall simplification of 
> >> this 3-way overbooking complexity, as follows.
> >> 
> >> Define:
> >> 
> >> LSPOMc = LSP overbooking multiplier for CTc
> >> LSOM = link size overbooking multiplier
> >> LSOM = maximum reservable bandwidth/maximum link bandwidth
> >> LOMc = local overbooking multiplier for CTc (original 
> >> definition of LOMc)
> >> LOM'c = redefined local overbooking multiplier LOMc for CTc
> >> LOM'c = LSOM * LSPOMc * LOMc
> >> 
> >> Given:
> >> requested LSP CTc = RSVP-TE Tspec LSP bandwidth specified in TLV
> >> 
> >> Then the following general equation applies:
> >> reserved CTc = requested LSP CTc/LOM'c                       (1)
> >> 
> >> wherein there are several cases of equation (1) for reserved CTc:
> >> 
> >> 1. Link Size Overbooking only:
> >>     LSPOMc = 1, LOMc = 1, for all c
> >>     LOM'c = LSOM, or equivalently
> >>     reserved CTc = requested LSP CTc/LSOM = requested LSP CTc/LOM'c
> >> 2. LSP Size Overbooking only:
> >>     LSOM = 1, LOMc = 1, for all c
> >>     LOM'c = LSPOMc for all c, or equivalently
> >>     reserved CTc = requested LSP CTc/LSPOMc = requested 
> LSP CTc/LOM'c
> >> 3. Both Link Size Overbooking and LSP Size Overbooking:
> >>     LOMc = 1, for all c
> >>     LOM'c = LSOM * LSPOMc, or equivalently
> >>     reserved CTc = requested LSP CTc/(LSOM * LSPOMc) = 
> >> requested LSP CTc/LOM'c
> >>  4. LOM in conjunction with the above cases 1, 2, or 3
> >>     reserved CTc = requested LSP CTc/LOM'c
> >> 
> >> In this model, the aggregate constraint becomes:
> >> 
> >>  o SUM (Reserved(CTc)) <= MLBW                               (2)
> >>      for all "c" in the range 0 <= c <= (MaxCT-1)
> >> 
> >> We believe that this simplification, as summarized in 
> >> equations (1) and (2) above, is worthwhile if LOM is retained.
> >> 
> >> Thanks,
> >> Jerry & Wai Sum
> >> 
> 



From owner-te-wg@ops.ietf.org  Mon Jun  2 12:12: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 MAA13669
	for <tewg-archive@lists.ietf.org>; Mon, 2 Jun 2003 12:12:17 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19MruM-000GkI-00
	for te-wg-data@psg.com; Mon, 02 Jun 2003 16:11:38 +0000
Received: from sj-core-3.cisco.com ([171.68.223.137])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19MruI-000Gk4-00
	for te-wg@ops.ietf.org; Mon, 02 Jun 2003 16:11:34 +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 h52GAPHr023512;
	Mon, 2 Jun 2003 09:10:25 -0700 (PDT)
Received: from msiva-w2k01.cisco.com (dhcp-kta1-161-44-194-127.cisco.com [161.44.194.127])
	by toque.cisco.com (Mirapoint)
	with ESMTP id AEO02190;
	Mon, 2 Jun 2003 12:10:12 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030602120936.02072ea0@toque.cisco.com>
X-Sender: msiva@toque.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 02 Jun 2003 12:10:20 -0400
To: Dimitry Haskin <dhaskin@axiowave.com>
From: "Siva Sivabalan (msiva)" <msiva@cisco.com>
Subject: RE: Dropping the Local Overbooking Multiplier (LOM) method
  from D S-TE specs?
Cc: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, te-wg@ops.ietf.org
In-Reply-To: <EB5FFC72F183D411B3820006295734290125F66A@r2d2.axiowave.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

I agree with Francois and Dimitry.

Thanks,
Siva

At 12:00 PM 6/2/2003 -0400, Dimitry Haskin wrote:
>I agree with Francois. Let's remove LOM from the base spec and not to
>venture on another round of unnecessary redefinitions of the base spec.
>
>As a side note, I would not be too upset if no separate LOM spec follows any
>soon. I'd let someone who feels that there is a real practical need for LOM
>to pick up the LOM torch.
>
>Dimitry
>
> > -----Original Message-----
> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> > Sent: Monday, June 02, 2003 9:02 AM
> > To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM)
> > method from
> > DS-TE specs?
> >
> >
> > Jerry,
> >
> > >> -----Original Message-----
> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> > >> Sent: 02 June 2003 14:02
> > >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
> > >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
> > >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM)
> > >> method from DS-TE specs?
> > >>
> > >>
> > >> Francois, All,
> > >>
> > >> > no one has expressed objections to taking LOM out of the base
> > >> > spec to move it to another document.
> > >>
> > >> I believe Sanjay objected,
> >
> > I am sure will hear from Sanjay soon, but quoting from his email:
> > >>    I am not against moving the LOM feature into its own draft,
> > Doesn't sound like an objection to me.
> >
> > So I think it is fair to say that noone has expressed any
> > objection (at
> > this stage anyway).
> >
> > >>and I think he made a good point.
> > >>  Either we should agree to drop LOM completely (no 'separate
> > >> document' and/or Experimental track for LOM), or leave it
> > >> in.  If it is progressed as a separate document/Experimental
> > >> track, this would complicate backward compatibility for all
> > >> the BC models.
> > >>
> >
> > Whether we keep the text on LOM distributed over -proto,
> > -russian, -mam
> > (and perhaps in MAR if you have added that in) as it is today
> > or whether
> > we redistribute it into a single standalone document does not affect
> > backward compatibility. We're only talking about
> > redistributing the same
> > text in a different set of documents so we can make one document
> > Experimental.
> >
> > >> > Based on this, unless we hear different opinions shortly,
> > >> my proposal
> > >> > will be to:
> > >> >  - issue the next versions of -proto, -russian and -mam without
> > >> > LOM, so these can go to IESG Last Call promptly (Standards
> > >> for -proto,
> > >> > Experimental for -russian and -mam)
> > >>
> > >> Wai Sum and I have already expressed a different opinion in
> > >> the proposed re-definition of LOM.  Before we agree to drop
> > >> the LOM feature, we'd like to see some discussion on the
> > >> alternative proposal to simplify the rather complicated
> > >> 3-way approach to overbooking that now exists.  See below.
> >
> > The current approach is NOT complicated. Please see the specific email
> > on this. Note that its two main components (Link/Size Overbooking) are
> > directly inherited from existing TE. These two should not be
> > modified in
> > any way so they remain backward compatible with existing TE anyway.
> > The current model works, all formulas are documented and we
> > had lots of
> > discussion so everybody is fully synched up on it now.
> > I see no justification to enter a new round of let's reinvent the
> > overbooking model for DS-TE at this post Last-Call stage.
> >
> > >>
> > >> You've also forgotten to mention -mar in the above.
> > >>
> > >> >  - issue a separate document (-lom) on LOM which can be
> > >> > progressed in Experimental track.
> > >>
> > >> As above, I'm against a separate Experimental track for LOM,
> > >> because this would complicate backward compatibility for all
> > >> the BC models.  Otherwise, we need to explain how LOM can be
> > >> introduced into the BC models later on, and avoid a
> > >> transition/interoperability problem.  It seems that with the
> > >> proposed separate track, LOM is functionally dead, but not
> > >> officially dead.  I think we should either officially kill
> > >> LOM, or retain it (but perhaps re-defined).
> > >>
> >
> > The idea of Experimental is that LOM would be neither "dead" nor
> > "standards". It would suggest that LOM is something we've
> > discussed and
> > documented and some people may want to play with. Experience will tell
> > us what we should do with it.
> > Another good thing with Experimental is that I don't think we have to
> > all agree that it is a useful thing as long as some people do. I
> > personally would have no problem in dropping LOM altogether, but my
> > impression was that some people had a problem in dropping it
> > altogether
> > because we just don't really know whether it will be useful
> > or not. That
> > sounded like Experimental track to me.
> >
> > Do you feel there is rough concensus to drop LOM altogether
> > (that would
> > work for me)?
> >
> > Cheers
> >
> > Francois
> >
> > >> > Please let me know if you have concerns with this proposal.
> > >>
> > >> Yes, 2 concerns:
> > >>
> > >> 1. As above, if LOM is progressed separately, we need to
> > >> explain how LOM can be introduced into the BC models later
> > >> on, and avoid a transition/interoperability problem.  I
> > >> think it would be preferable to officially kill LOM, rather
> > >> than leave it in the proposed 'separate track'.
> > >>
> > >> 2. Before we agree to drop the LOM feature, we'd like to see
> > >> some discussion on the alternative proposal to redefine LOM
> > >> (to LOM'), in order to simplify the rather complicated 3-way
> > >> approach to overbooking that now exists:
> > >>
> > >> LSPOMc = LSP overbooking multiplier for CTc
> > >> LSOM = link size overbooking multiplier
> > >> LOMc = local overbooking multiplier for CTc
> > >>
> > >> If LOM is retained, Wai Sum and I propose to redefine LOM
> > >> (calling it LOM') to provide an overall simplification of
> > >> this 3-way overbooking complexity, as follows.
> > >>
> > >> Define:
> > >>
> > >> LSPOMc = LSP overbooking multiplier for CTc
> > >> LSOM = link size overbooking multiplier
> > >> LSOM = maximum reservable bandwidth/maximum link bandwidth
> > >> LOMc = local overbooking multiplier for CTc (original
> > >> definition of LOMc)
> > >> LOM'c = redefined local overbooking multiplier LOMc for CTc
> > >> LOM'c = LSOM * LSPOMc * LOMc
> > >>
> > >> Given:
> > >> requested LSP CTc = RSVP-TE Tspec LSP bandwidth specified in TLV
> > >>
> > >> Then the following general equation applies:
> > >> reserved CTc = requested LSP CTc/LOM'c                       (1)
> > >>
> > >> wherein there are several cases of equation (1) for reserved CTc:
> > >>
> > >> 1. Link Size Overbooking only:
> > >>     LSPOMc = 1, LOMc = 1, for all c
> > >>     LOM'c = LSOM, or equivalently
> > >>     reserved CTc = requested LSP CTc/LSOM = requested LSP CTc/LOM'c
> > >> 2. LSP Size Overbooking only:
> > >>     LSOM = 1, LOMc = 1, for all c
> > >>     LOM'c = LSPOMc for all c, or equivalently
> > >>     reserved CTc = requested LSP CTc/LSPOMc = requested
> > LSP CTc/LOM'c
> > >> 3. Both Link Size Overbooking and LSP Size Overbooking:
> > >>     LOMc = 1, for all c
> > >>     LOM'c = LSOM * LSPOMc, or equivalently
> > >>     reserved CTc = requested LSP CTc/(LSOM * LSPOMc) =
> > >> requested LSP CTc/LOM'c
> > >>  4. LOM in conjunction with the above cases 1, 2, or 3
> > >>     reserved CTc = requested LSP CTc/LOM'c
> > >>
> > >> In this model, the aggregate constraint becomes:
> > >>
> > >>  o SUM (Reserved(CTc)) <= MLBW                               (2)
> > >>      for all "c" in the range 0 <= c <= (MaxCT-1)
> > >>
> > >> We believe that this simplification, as summarized in
> > >> equations (1) and (2) above, is worthwhile if LOM is retained.
> > >>
> > >> Thanks,
> > >> Jerry & Wai Sum
> > >>
> >




From owner-te-wg@ops.ietf.org  Tue Jun  3 10:46: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 KAA07529
	for <tewg-archive@lists.ietf.org>; Tue, 3 Jun 2003 10:46:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NCxp-0000FA-00
	for te-wg-data@psg.com; Tue, 03 Jun 2003 14:40:37 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NCxb-000080-00
	for te-wg@ops.ietf.org; Tue, 03 Jun 2003 14:40:23 +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 KAA17895
	for <te-wg@ops.ietf.org>; Tue, 3 Jun 2003 10:10:04 -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 KAA10832
	for <te-wg@ops.ietf.org>; Tue, 3 Jun 2003 10:09:48 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L241HWYF>; Tue, 3 Jun 2003 10:09:47 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F54B0@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: Tue, 3 Jun 2003 10:09:46 -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 Francois, Jerry, All!

My first preference, would be to leave the DSTE-PROTO
as it is with the following changes:
	(i)  replace the max_link_bw by max_reservable_bw
	(ii) add some more text clarifying the LOM concept

If after another week of discussions, we are still at impasse,
my second preference would be to split the LOM text out of 
the DSTE-PROTO and make it its own draft. I do have serious 
reservations about the second approach, because we are just 
deferring the problem and not addressing the issue.

Now, lets examine the issues in little more detail::-

As of now, I have heard the following concerns about the 
LOM concept (as presented in the DSTE-PROTO):

	Issue-1: LOM is a complex concept.
	Issue-2: LOM makes DSTE-PROTO difficult to read
	Issue-3: LOM is difficult to implement
	Issue-4: LOM is difficult to deploy
	Issue-5: We don't know if LOM is a useful concept

Here are my take on these issues::-

Issue-1:: In my opinion the LOM concept is the _least_
complex part of DSTE-PROTO. I think, people are confused
by the mechanics behind the co-existence of LOM, with the 
two *legacy* overbooking techniques.

DSTE-PROTO did not introduce the concept of "LSP Size
Overbooking" or "Link Size Overbooking". 
It just (i) gave formal name to the existing techniques
and (ii) ensured that the new LOM co-exists with the 
existing overbooking approaches.

The above mentioned existing overbooking techniques work
in existing non-DSTE networks (and will continue to work
in DSTE domains).

=>We can address this issue, by adding some clarifying text.

Issue-2:: DSTE is all about, providing per-CT BW control to
the network administrator. I think it makes the solution 
more complete by leaving the LOM text in.

=>We can easily solve the readability problem by adding
some clarifying text [will it be useful, if I propose some
text in this section?]

Issues-3:: I can't tell for others, but personally I think 
it is not a difficult feature to implement. After all, it
is just a multiplier!

=>Vendors don't have to implement it, if they think it is
difficult to implement the concept.

Issue-4:: When fine grained BW optimization is needed, 
the administrator will use the per-CT BW controls 
provided by the DSTE-PROTO. When dealing with a per-CT
level BW control, it is more natural to expect a per-CT
overbooking factor. After all, providers are used to
per-CoS overbooking concepts from their experience with
ATM.

=>DSTE-PROTO does not force all users to use the LOM 
concept, but provides enough per-CT control for the 
interested users.

Issue-5: I think per-CT overbooking solution (LOM) can 
be a useful tool the network administrators. It complements
the existing overbooking techniques, seamlessly.

	-When the administrator has decided to deploy DSTE, 
	obviously, he wants per-CT BW control. It is only 
	natural to expect a per-CT overbooking knob 

	-Consider a situation, where the administrator wants
	to overbook his data traffic, but does not want to
	overbook the voice traffic on the link. In this case
	max_reservable_bw knob is too coarse to be used. LOM
	can aid with this configuration.

	-In the past, some of the providers have indicated
	their plans to use per CoS overbooking techniques.


Thanks,
sanjay


 




> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Monday, June 02, 2003 11:19 AM
> To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> DS-TE specs?
> 
> 
> Hello Jerry,
> 
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> >> Sent: 02 June 2003 16:34
> >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
> >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
> >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> >> method from DS-TE specs?
> >> 
> >> 
> >> Francois, All,
> >> 
> >> > The current approach is NOT complicated. Please see the 
> >> specific email
> >> > on this. 
> >> 
> >> That's your view, but I don't think it constitutes a proof 
> >> of same :-)
> >> 
> 
> Absolutely right. 
> Just like I would rather see statement saying that someone finds the
> current model rather complicated as opposed to statement saying it is
> rather complicated. 8^)
> 
> >> > Note that its two main components (Link/Size Overbooking) are
> >> > directly inherited from existing TE. These two should not 
> >> be modified in
> >> > any way so they remain backward compatible with existing 
> TE anyway.
> >> > The current model works, all formulas are documented and 
> >> we had lots of
> >> > discussion so everybody is fully synched up on it now.
> >> > I see no justification to enter a new round of let's reinvent the
> >> > overbooking model for DS-TE at this post Last-Call stage.
> >> 
> >> I expected this comment, of course.  However, DS-TE is a 
> >> *new* environment (CTs, BC models, etc.), and we should have 
> >> the right to define things within that new environment.
> >> 
> >> However, so as to not drag this out, and come to closure, 
> >> I'm OK to go with your proposed formulas, pending a final 
> >> agreement on LOM (see below):
> >> 
> >> 
> 
> Great. This should allow us to move ahead fast as soon as we make a
> final call on what to do with LOM.
> 
> >> When LOM is NOT used (i.e. 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
> >> 
> >> When LOM is used 
> >> ===============================
> >> o for each value of b in the range 0 <= b <= 7:
> >>   Normalized (CTb) <= BCb,
> >> o SUM (Normalized(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 (i.e. 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 ( Normalized(CTb,q) ) ] for q <= p,
> >> [ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p 
> >> and 0 <= b <= 7,]
> >> where:
> >> TE-Class [i] <--> < CTc , preemption p> 
> >> 
> >> > The idea of Experimental is that LOM would be neither "dead" nor
> >> > "standards". It would suggest that LOM is something we've 
> >> discussed and
> >> > documented and some people may want to play with. 
> >> Experience will tell
> >> > us what we should do with it.
> >> > Another good thing with Experimental is that I don't think 
> >> we have to
> >> > all agree that it is a useful thing as long as some people do. I
> >> > personally would have no problem in dropping LOM 
> altogether, but my
> >> > impression was that some people had a problem in dropping 
> >> it altogether
> >> > because we just don't really know whether it will be 
> >> useful or not. That
> >> > sounded like Experimental track to me.
> >> > 
> >> > Do you feel there is rough consensus to drop LOM 
> >> altogether (that would
> >> > work for me)?
> >> 
> >> I have not seen anyone give an example of where LOM is 
> >> needed.  Unless we see that, my preference would be to drop 
> >> it.  LOM is a real parameter, and at present needs to be 
> >> carried in the RSVP extensions for DS-TE.  It requires 
> >> addition aggregation constraints in the BC models.
> >> 
> >> Considerations of per-CT and hi-speed vs. low-speed links 
> >> can be easily accommodated, as I gave in an example by using 
> >> just LSPOM and LSOM (see earlier post 
> >> http://ops.ietf.org/lists/te-wg/te->> wg.2003/msg00314.html).  
> >> It seems like much more than 
> >> enough flexibility to avoid any problems, without also 
> >> further complication with LOM.  
> >> 
> >> Can anyone explain why LOM would be needed, and in 
> >> particular, give a practical example of same?
> >> 
> >> It seems to have marginal value (I don't see anyone showing 
> >> how it is needed, or really supporting it).  I think we can 
> >> agree that simplification *will* be achieved if we eliminate LOM.
> 
> We can certainly agree on that.
> 
> So let's see if we hear some justiication for LOM or not, and based on
> that we can finalise decision (hopefully within a few days) firstly to
> take LOM out of base specs, and secondly to drop altogether 
> (or document
> as Experimental).
> 
> Cheers
> 
> Francois
> 
> >> 
> >> Thanks,
> >> Jerry
> >> 
> 



From owner-te-wg@ops.ietf.org  Tue Jun  3 14:55: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 OAA19549
	for <tewg-archive@lists.ietf.org>; Tue, 3 Jun 2003 14:55:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NGt5-0009us-00
	for te-wg-data@psg.com; Tue, 03 Jun 2003 18:51:59 +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 19NGt1-0009ro-00
	for te-wg@ops.ietf.org; Tue, 03 Jun 2003 18:51:55 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F66D@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: Tue, 3 Jun 2003 14:33:56 -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

Sanjaya,

Let me take you on Issue-5 ("We don't know if LOM is a useful concept")
since if we new that it is really useful it would be a good reason to keep
LOM in the base spec.

> 	-When the administrator has decided to deploy DSTE, 
> 	obviously, he wants per-CT BW control. It is only 
> 	natural to expect a per-CT overbooking knob 
>

A per-CT overbooking knob will exist without LOM. However without LOM amount
of reservations in one CT may not accurately effect reservable bandwidths in
other CTs of the same link. So the real question is not if a per-CT
overbooking knob is need (of cause it does) but whether there are real uses
for LOM that can not be done without LOM. Which take us to your second
bullet.

> 	-Consider a situation, where the administrator wants
> 	to overbook his data traffic, but does not want to
> 	overbook the voice traffic on the link. In this case
> 	max_reservable_bw knob is too coarse to be used. LOM
> 	can aid with this configuration.

But is it really? My understanding is that in this particular case
administrators would like to allow reservations of the voice traffic,
presumably in its own CT, to reach its designated max level regardless of
the amount of reservations of data traffic. So LOM is no help here as far as
I can see. My educated guess is that in actual deployments a priority CT
will be admitted up to its max reservation level regardless and at expense
of the existing bookings at lower priority CTs.

> 	-In the past, some of the providers have indicated
> 	their plans to use per CoS overbooking techniques.

Definitely so but the most likely without LOM. Service providers may want to
comment.

Regards,
  Dimitry




> -----Original Message-----
> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@Marconi.com]
> Sent: Tuesday, June 03, 2003 10:10 AM
> To: te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> D S-TE specs?
> 
> 
> Hi Francois, Jerry, All!
> 
> My first preference, would be to leave the DSTE-PROTO
> as it is with the following changes:
> 	(i)  replace the max_link_bw by max_reservable_bw
> 	(ii) add some more text clarifying the LOM concept
> 
> If after another week of discussions, we are still at impasse,
> my second preference would be to split the LOM text out of 
> the DSTE-PROTO and make it its own draft. I do have serious 
> reservations about the second approach, because we are just 
> deferring the problem and not addressing the issue.
> 
> Now, lets examine the issues in little more detail::-
> 
> As of now, I have heard the following concerns about the 
> LOM concept (as presented in the DSTE-PROTO):
> 
> 	Issue-1: LOM is a complex concept.
> 	Issue-2: LOM makes DSTE-PROTO difficult to read
> 	Issue-3: LOM is difficult to implement
> 	Issue-4: LOM is difficult to deploy
> 	Issue-5: We don't know if LOM is a useful concept
> 
> Here are my take on these issues::-
> 
> Issue-1:: In my opinion the LOM concept is the _least_
> complex part of DSTE-PROTO. I think, people are confused
> by the mechanics behind the co-existence of LOM, with the 
> two *legacy* overbooking techniques.
> 
> DSTE-PROTO did not introduce the concept of "LSP Size
> Overbooking" or "Link Size Overbooking". 
> It just (i) gave formal name to the existing techniques
> and (ii) ensured that the new LOM co-exists with the 
> existing overbooking approaches.
> 
> The above mentioned existing overbooking techniques work
> in existing non-DSTE networks (and will continue to work
> in DSTE domains).
> 
> =>We can address this issue, by adding some clarifying text.
> 
> Issue-2:: DSTE is all about, providing per-CT BW control to
> the network administrator. I think it makes the solution 
> more complete by leaving the LOM text in.
> 
> =>We can easily solve the readability problem by adding
> some clarifying text [will it be useful, if I propose some
> text in this section?]
> 
> Issues-3:: I can't tell for others, but personally I think 
> it is not a difficult feature to implement. After all, it
> is just a multiplier!
> 
> =>Vendors don't have to implement it, if they think it is
> difficult to implement the concept.
> 
> Issue-4:: When fine grained BW optimization is needed, 
> the administrator will use the per-CT BW controls 
> provided by the DSTE-PROTO. When dealing with a per-CT
> level BW control, it is more natural to expect a per-CT
> overbooking factor. After all, providers are used to
> per-CoS overbooking concepts from their experience with
> ATM.
> 
> =>DSTE-PROTO does not force all users to use the LOM 
> concept, but provides enough per-CT control for the 
> interested users.
> 
> Issue-5: I think per-CT overbooking solution (LOM) can 
> be a useful tool the network administrators. It complements
> the existing overbooking techniques, seamlessly.
> 
> 	-When the administrator has decided to deploy DSTE, 
> 	obviously, he wants per-CT BW control. It is only 
> 	natural to expect a per-CT overbooking knob 
> 
> 	-Consider a situation, where the administrator wants
> 	to overbook his data traffic, but does not want to
> 	overbook the voice traffic on the link. In this case
> 	max_reservable_bw knob is too coarse to be used. LOM
> 	can aid with this configuration.
> 
> 	-In the past, some of the providers have indicated
> 	their plans to use per CoS overbooking techniques.
> 
> 
> Thanks,
> sanjay
> 
> 
>  
> 
> 
> 
> 
> > -----Original Message-----
> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> > Sent: Monday, June 02, 2003 11:19 AM
> > To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > method from
> > DS-TE specs?
> > 
> > 
> > Hello Jerry,
> > 
> > >> -----Original Message-----
> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> > >> Sent: 02 June 2003 16:34
> > >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
> > >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
> > >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > >> method from DS-TE specs?
> > >> 
> > >> 
> > >> Francois, All,
> > >> 
> > >> > The current approach is NOT complicated. Please see the 
> > >> specific email
> > >> > on this. 
> > >> 
> > >> That's your view, but I don't think it constitutes a proof 
> > >> of same :-)
> > >> 
> > 
> > Absolutely right. 
> > Just like I would rather see statement saying that someone finds the
> > current model rather complicated as opposed to statement 
> saying it is
> > rather complicated. 8^)
> > 
> > >> > Note that its two main components (Link/Size Overbooking) are
> > >> > directly inherited from existing TE. These two should not 
> > >> be modified in
> > >> > any way so they remain backward compatible with existing 
> > TE anyway.
> > >> > The current model works, all formulas are documented and 
> > >> we had lots of
> > >> > discussion so everybody is fully synched up on it now.
> > >> > I see no justification to enter a new round of let's 
> reinvent the
> > >> > overbooking model for DS-TE at this post Last-Call stage.
> > >> 
> > >> I expected this comment, of course.  However, DS-TE is a 
> > >> *new* environment (CTs, BC models, etc.), and we should have 
> > >> the right to define things within that new environment.
> > >> 
> > >> However, so as to not drag this out, and come to closure, 
> > >> I'm OK to go with your proposed formulas, pending a final 
> > >> agreement on LOM (see below):
> > >> 
> > >> 
> > 
> > Great. This should allow us to move ahead fast as soon as we make a
> > final call on what to do with LOM.
> > 
> > >> When LOM is NOT used (i.e. 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
> > >> 
> > >> When LOM is used 
> > >> ===============================
> > >> o for each value of b in the range 0 <= b <= 7:
> > >>   Normalized (CTb) <= BCb,
> > >> o SUM (Normalized(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 (i.e. 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 ( Normalized(CTb,q) ) ] for q <= p,
> > >> [ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p 
> > >> and 0 <= b <= 7,]
> > >> where:
> > >> TE-Class [i] <--> < CTc , preemption p> 
> > >> 
> > >> > The idea of Experimental is that LOM would be neither 
> "dead" nor
> > >> > "standards". It would suggest that LOM is something we've 
> > >> discussed and
> > >> > documented and some people may want to play with. 
> > >> Experience will tell
> > >> > us what we should do with it.
> > >> > Another good thing with Experimental is that I don't think 
> > >> we have to
> > >> > all agree that it is a useful thing as long as some 
> people do. I
> > >> > personally would have no problem in dropping LOM 
> > altogether, but my
> > >> > impression was that some people had a problem in dropping 
> > >> it altogether
> > >> > because we just don't really know whether it will be 
> > >> useful or not. That
> > >> > sounded like Experimental track to me.
> > >> > 
> > >> > Do you feel there is rough consensus to drop LOM 
> > >> altogether (that would
> > >> > work for me)?
> > >> 
> > >> I have not seen anyone give an example of where LOM is 
> > >> needed.  Unless we see that, my preference would be to drop 
> > >> it.  LOM is a real parameter, and at present needs to be 
> > >> carried in the RSVP extensions for DS-TE.  It requires 
> > >> addition aggregation constraints in the BC models.
> > >> 
> > >> Considerations of per-CT and hi-speed vs. low-speed links 
> > >> can be easily accommodated, as I gave in an example by using 
> > >> just LSPOM and LSOM (see earlier post 
> > >> http://ops.ietf.org/lists/te-wg/te->> wg.2003/msg00314.html).  
> > >> It seems like much more than 
> > >> enough flexibility to avoid any problems, without also 
> > >> further complication with LOM.  
> > >> 
> > >> Can anyone explain why LOM would be needed, and in 
> > >> particular, give a practical example of same?
> > >> 
> > >> It seems to have marginal value (I don't see anyone showing 
> > >> how it is needed, or really supporting it).  I think we can 
> > >> agree that simplification *will* be achieved if we eliminate LOM.
> > 
> > We can certainly agree on that.
> > 
> > So let's see if we hear some justiication for LOM or not, 
> and based on
> > that we can finalise decision (hopefully within a few days) 
> firstly to
> > take LOM out of base specs, and secondly to drop altogether 
> > (or document
> > as Experimental).
> > 
> > Cheers
> > 
> > Francois
> > 
> > >> 
> > >> Thanks,
> > >> Jerry
> > >> 
> > 
> 



From owner-te-wg@ops.ietf.org  Tue Jun  3 20:30: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 UAA01209
	for <tewg-archive@lists.ietf.org>; Tue, 3 Jun 2003 20:30:16 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NM7t-000Lt4-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 00:27:37 +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 19NM7r-000LrS-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 00:27: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 h53NFv1A005420
	for <te-wg@ops.ietf.org>; Tue, 3 Jun 2003 18:27:46 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EC7660200559CCE; Tue, 3 Jun 2003 19:27:43 -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: Tue, 3 Jun 2003 18:27:45 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE9A8@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/AAAV41YAAC+n9wAEW6giA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.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 UAA01209

All,

I had proposed earlier:

> Can anyone give a practical example of where LOM is needed? 
> Unless we see that, my preference would be to drop it.   

Since posting that, some examples have been given (on the list and privately) that perhaps illustrate how LOM can be used in practice.

Furthermore, based on the discussion so far:

1. many people support leaving LOM in because they're reluctant to give up the extra flexibility (even though they don't offer specific supporting examples).
2. many people feel that the LOM extension is very simple, therefore why the concern, just leave it there.

Also, I argued against having LOM progressed separately, I think that would just complicate matters, and leave the BC models, Proto extensions, etc. in a state of limbo (possible awaiting a LOM extension later).  I had argued to either keep LOM, or drop LOM, but not leave it in the 'in between' state.

Overall, I don't think the case has been made to drop LOM, and, given that, I believe the better option is to leave LOM as is and not progress it as a separate effort.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Wed Jun  4 09:16:46 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA18015
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 09:16:45 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NY3h-0007oa-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 13:12:05 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NY3b-0007oJ-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 13:11:59 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 04 Jun 2003 15:11: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 h54D9uQx025741;
	Wed, 4 Jun 2003 15:09:59 +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, 4 Jun 2003 15:11:12 +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, 4 Jun 2003 14:11:12 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5266@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMp3w0RW35USxAwR1aZX0R8Dy2ksgAtluAw
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@Marconi.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 04 Jun 2003 13:11:12.0812 (UTC) FILETIME=[C5C8FEC0:01C32A9A]
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA18015

Hello Sanjaya,

>> -----Original Message-----
>> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@Marconi.com] 
>> Sent: 03 June 2003 16:10
>> To: te-wg@ops.ietf.org
>> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> Hi Francois, Jerry, All!
>> 
>> My first preference, would be to leave the DSTE-PROTO
>> as it is with the following changes:
>> 	(i)  replace the max_link_bw by max_reservable_bw
>> 	(ii) add some more text clarifying the LOM concept
>>

Understood.
 
>> If after another week of discussions, we are still at impasse,
>> my second preference would be to split the LOM text out of 
>> the DSTE-PROTO and make it its own draft. 

Noted.
Unless the people who expressed first preference for taking LOM out of
base spec get convinced to change their mind soon, it seems likely we
won't all agree on our first preference. So this seems to me like a
likely avenue.

>>I do have serious 
>> reservations about the second approach, because we are just 
>> deferring the problem and not addressing the issue.
>> 
>> Now, lets examine the issues in little more detail::-
>> 
>> As of now, I have heard the following concerns about the 
>> LOM concept (as presented in the DSTE-PROTO):
>> 
>> 	Issue-1: LOM is a complex concept.
>> 	Issue-2: LOM makes DSTE-PROTO difficult to read
>> 	Issue-3: LOM is difficult to implement
>> 	Issue-4: LOM is difficult to deploy
>> 	Issue-5: We don't know if LOM is a useful concept
>>

I agree that neither of these issues individually is unsurmountable. 
But the real issue to consider seems rather that the ratio between the
extra functionality and the extra complexity is very high (not so much
because the extra complexity is high but mainly because the extra
functionality appears very low).

Another way to consider this question is the following. 
A general principle we've followed for the dste-proto is to only specify
protocol extensions necessary in order to carry all of, but no more
than, the mechanisms that exist in regular TE and make them work in the
presence of multiple CTs. I very much support that principle : make it
only as complicated as necessary to support multiple CTs, but no more.
As you've mentioned below, this is precisely the case for Link Size
Overbooking and LSP Size Overbooking. We only did what we had to do to
make these concepts from regular TE work with multiple CTs.
The one exception is LOM which is more like doing something beyond what
already exists in regular TE. Now all principles can be broken, but I
would expect a stronger case in terms of requirement to justify doing
so. 

I won't comment on your discussion of the individual issues below
because, as I said, the more relevant question is their combined
trade-off. I will just mention one thing relating to your issue 5 (which
I think is similar to Dimitry's point): of course we want to be able to
do per-CT overbooking. But this is in no way a justification for LOM.
You can do per-CT overbooking perfectly well without LOM. Again, the
only thing you cannot do is enforce an overbooking ratio which is
differnet on a per link and per CT basis. But you can certainly have
different overbooking ratios per CT and simultaneously have different
overbooking ratios per link. 
The meaningful formation here would be to hear if Service Providers feel
that being able to "simultaneously enforce different overbooking ratios
per CT and different overbooking ratios per link" may not be sufficient
for their environment and that different overbooking ratios per-CT AND
per-link are required. 

Thanks again for your thoughts.

Francois
 
>> Here are my take on these issues::-
>> 
>> Issue-1:: In my opinion the LOM concept is the _least_
>> complex part of DSTE-PROTO. I think, people are confused
>> by the mechanics behind the co-existence of LOM, with the 
>> two *legacy* overbooking techniques.
>> 
>> DSTE-PROTO did not introduce the concept of "LSP Size
>> Overbooking" or "Link Size Overbooking". 
>> It just (i) gave formal name to the existing techniques
>> and (ii) ensured that the new LOM co-exists with the 
>> existing overbooking approaches.
>> 
>> The above mentioned existing overbooking techniques work
>> in existing non-DSTE networks (and will continue to work
>> in DSTE domains).
>> 
>> =>We can address this issue, by adding some clarifying text.
>> 
>> Issue-2:: DSTE is all about, providing per-CT BW control to
>> the network administrator. I think it makes the solution 
>> more complete by leaving the LOM text in.
>> 
>> =>We can easily solve the readability problem by adding
>> some clarifying text [will it be useful, if I propose some
>> text in this section?]
>> 
>> Issues-3:: I can't tell for others, but personally I think 
>> it is not a difficult feature to implement. After all, it
>> is just a multiplier!
>> 
>> =>Vendors don't have to implement it, if they think it is
>> difficult to implement the concept.
>> 
>> Issue-4:: When fine grained BW optimization is needed, 
>> the administrator will use the per-CT BW controls 
>> provided by the DSTE-PROTO. When dealing with a per-CT
>> level BW control, it is more natural to expect a per-CT
>> overbooking factor. After all, providers are used to
>> per-CoS overbooking concepts from their experience with
>> ATM.
>> 
>> =>DSTE-PROTO does not force all users to use the LOM 
>> concept, but provides enough per-CT control for the 
>> interested users.
>> 
>> Issue-5: I think per-CT overbooking solution (LOM) can 
>> be a useful tool the network administrators. It complements
>> the existing overbooking techniques, seamlessly.
>> 
>> 	-When the administrator has decided to deploy DSTE, 
>> 	obviously, he wants per-CT BW control. It is only 
>> 	natural to expect a per-CT overbooking knob 
>> 
>> 	-Consider a situation, where the administrator wants
>> 	to overbook his data traffic, but does not want to
>> 	overbook the voice traffic on the link. In this case
>> 	max_reservable_bw knob is too coarse to be used. LOM
>> 	can aid with this configuration.
>> 
>> 	-In the past, some of the providers have indicated
>> 	their plans to use per CoS overbooking techniques.
>> 
>> 
>> Thanks,
>> sanjay
>> 
>> 
>>  
>> 
>> 
>> 
>> 
>> > -----Original Message-----
>> > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>> > Sent: Monday, June 02, 2003 11:19 AM
>> > To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
>> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> > method from
>> > DS-TE specs?
>> > 
>> > 
>> > Hello Jerry,
>> > 
>> > >> -----Original Message-----
>> > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> > >> Sent: 02 June 2003 16:34
>> > >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
>> > >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
>> > >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> > >> method from DS-TE specs?
>> > >> 
>> > >> 
>> > >> Francois, All,
>> > >> 
>> > >> > The current approach is NOT complicated. Please see the 
>> > >> specific email
>> > >> > on this. 
>> > >> 
>> > >> That's your view, but I don't think it constitutes a proof 
>> > >> of same :-)
>> > >> 
>> > 
>> > Absolutely right. 
>> > Just like I would rather see statement saying that someone 
>> finds the
>> > current model rather complicated as opposed to statement 
>> saying it is
>> > rather complicated. 8^)
>> > 
>> > >> > Note that its two main components (Link/Size Overbooking) are
>> > >> > directly inherited from existing TE. These two should not 
>> > >> be modified in
>> > >> > any way so they remain backward compatible with existing 
>> > TE anyway.
>> > >> > The current model works, all formulas are documented and 
>> > >> we had lots of
>> > >> > discussion so everybody is fully synched up on it now.
>> > >> > I see no justification to enter a new round of let's 
>> reinvent the
>> > >> > overbooking model for DS-TE at this post Last-Call stage.
>> > >> 
>> > >> I expected this comment, of course.  However, DS-TE is a 
>> > >> *new* environment (CTs, BC models, etc.), and we should have 
>> > >> the right to define things within that new environment.
>> > >> 
>> > >> However, so as to not drag this out, and come to closure, 
>> > >> I'm OK to go with your proposed formulas, pending a final 
>> > >> agreement on LOM (see below):
>> > >> 
>> > >> 
>> > 
>> > Great. This should allow us to move ahead fast as soon as we make a
>> > final call on what to do with LOM.
>> > 
>> > >> When LOM is NOT used (i.e. 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
>> > >> 
>> > >> When LOM is used 
>> > >> ===============================
>> > >> o for each value of b in the range 0 <= b <= 7:
>> > >>   Normalized (CTb) <= BCb,
>> > >> o SUM (Normalized(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 (i.e. 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 ( Normalized(CTb,q) ) ] for q <= p,
>> > >> [ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p 
>> > >> and 0 <= b <= 7,]
>> > >> where:
>> > >> TE-Class [i] <--> < CTc , preemption p> 
>> > >> 
>> > >> > The idea of Experimental is that LOM would be neither 
>> "dead" nor
>> > >> > "standards". It would suggest that LOM is something we've 
>> > >> discussed and
>> > >> > documented and some people may want to play with. 
>> > >> Experience will tell
>> > >> > us what we should do with it.
>> > >> > Another good thing with Experimental is that I don't think 
>> > >> we have to
>> > >> > all agree that it is a useful thing as long as some 
>> people do. I
>> > >> > personally would have no problem in dropping LOM 
>> > altogether, but my
>> > >> > impression was that some people had a problem in dropping 
>> > >> it altogether
>> > >> > because we just don't really know whether it will be 
>> > >> useful or not. That
>> > >> > sounded like Experimental track to me.
>> > >> > 
>> > >> > Do you feel there is rough consensus to drop LOM 
>> > >> altogether (that would
>> > >> > work for me)?
>> > >> 
>> > >> I have not seen anyone give an example of where LOM is 
>> > >> needed.  Unless we see that, my preference would be to drop 
>> > >> it.  LOM is a real parameter, and at present needs to be 
>> > >> carried in the RSVP extensions for DS-TE.  It requires 
>> > >> addition aggregation constraints in the BC models.
>> > >> 
>> > >> Considerations of per-CT and hi-speed vs. low-speed links 
>> > >> can be easily accommodated, as I gave in an example by using 
>> > >> just LSPOM and LSOM (see earlier post 
>> > >> http://ops.ietf.org/lists/te-wg/te->> wg.2003/msg00314.html).  
>> > >> It seems like much more than 
>> > >> enough flexibility to avoid any problems, without also 
>> > >> further complication with LOM.  
>> > >> 
>> > >> Can anyone explain why LOM would be needed, and in 
>> > >> particular, give a practical example of same?
>> > >> 
>> > >> It seems to have marginal value (I don't see anyone showing 
>> > >> how it is needed, or really supporting it).  I think we can 
>> > >> agree that simplification *will* be achieved if we 
>> eliminate LOM.
>> > 
>> > We can certainly agree on that.
>> > 
>> > So let's see if we hear some justiication for LOM or not, 
>> and based on
>> > that we can finalise decision (hopefully within a few 
>> days) firstly to
>> > take LOM out of base specs, and secondly to drop altogether 
>> > (or document
>> > as Experimental).
>> > 
>> > Cheers
>> > 
>> > Francois
>> > 
>> > >> 
>> > >> Thanks,
>> > >> Jerry
>> > >> 
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed Jun  4 09:31: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 JAA18571
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 09:31:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NYLv-0009Ng-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 13:30:55 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NYLs-0009NL-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 13:30:52 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 04 Jun 2003 15:30:00 +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 h54DSaeh029150;
	Wed, 4 Jun 2003 15:28: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, 4 Jun 2003 15:30:08 +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, 4 Jun 2003 14:29:09 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5267@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/AAAV41YAAC+n9wAEW6giAAHcr4gA==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
Cc: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-OriginalArrivalTime: 04 Jun 2003 13:30:08.0788 (UTC) FILETIME=[6AE12D40:01C32A9D]
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 JAA18571

Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 04 June 2003 01:28
>> To: te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS; Francois Le Faucheur 
>> (flefauch); Lai, Wai S (Waisum), ALABS
>> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
>> method from DS-TE specs?
>> 
>> 
>> All,
>> 
>> I had proposed earlier:
>> 
>> > Can anyone give a practical example of where LOM is needed? 
>> > Unless we see that, my preference would be to drop it.   
>> 
>> Since posting that, some examples have been given (on the 
>> list and privately) that perhaps illustrate how LOM can be 
>> used in practice.

Hm, I haven't seen a single example. What did I miss?

Sanjaya's message made the point that it is a common requirement to want
to do per-CT overbooking. This is not a justification for LOM as per-CT
overbooking can be done with LSP Size Overbooking.

Did my spam filter inadvertently trashed messages on the list?
Also, it is hard to take into examples communicated privately unless you
can share those with us?

Cheers

Francois



From owner-te-wg@ops.ietf.org  Wed Jun  4 09:32: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 JAA18715
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 09:32:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NYNm-0009VB-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 13:32:50 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NYNi-0009Up-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 13:32:46 +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 JAA15113
	for <te-wg@ops.ietf.org>; Wed, 4 Jun 2003 09:32:44 -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 JAA15261
	for <te-wg@ops.ietf.org>; Wed, 4 Jun 2003 09:32:45 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L2412P8C>; Wed, 4 Jun 2003 09:32:44 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F54B3@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM) meth
	od from D S-TE specs?
Date: Wed, 4 Jun 2003 09:32:41 -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 Dimitry!,

Here is what we seem to agree on: A per-CT overbooking knob
is useful for the administrators.

Now on to your second point: per-CT overbooking can be done
without overbooking. In my personal opinion, you might have
made few wrong assumptions:

	1. Your example requires the preemption to be enabled
	in the domain; which may not be true. 

	=>LOM gives user explicit control overbooking at a 
	per-CT level, without the need to preemption.

	2. You indicated "However without LOM amount of 
	reservations in one CT may not accurately effect 
	reservable bandwidths in other CTs of the same link"

	=>Don't you think this a problem? Head-end LSR computed
	the path based on the advertised BWs per-CT [which is
	is the foundation of DSTE], will now compute a wrong
	path. 

	2. For a moment let is assume that preemption *is* 
	deployed in the domain. Can you explain me how I 
	will achieve the following [please be specific in
	what the user will need to do and the BC model in 
	use]:

		case-1: want to overbook data-traffic without
		overbooking voice traffic.

		case-2: Want to overbook the voice traffic by
		10%, but want to overbook data traffic by 40%

		case-3: want to overbook gold-traffic by 10%,
		overbook silver-traffic by 15%, overbook 
		normal-traffic by 20%

	3. Can all of the above be achieved without the 
	use pre-emption?


Thanks,
sanjay
	

		


> -----Original Message-----
> From: Dimitry Haskin [mailto:dhaskin@axiowave.com]
> Sent: Tuesday, June 03, 2003 2:34 PM
> To: 'Choudhury, Sanjaya'; te-wg@ops.ietf.org
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> D S-TE specs?
> 
> 
> Sanjaya,
> 
> Let me take you on Issue-5 ("We don't know if LOM is a useful 
> concept")
> since if we new that it is really useful it would be a good 
> reason to keep
> LOM in the base spec.
> 
> > 	-When the administrator has decided to deploy DSTE, 
> > 	obviously, he wants per-CT BW control. It is only 
> > 	natural to expect a per-CT overbooking knob 
> >
> 
> A per-CT overbooking knob will exist without LOM. However 
> without LOM amount
> of reservations in one CT may not accurately effect 
> reservable bandwidths in
> other CTs of the same link. So the real question is not if a per-CT
> overbooking knob is need (of cause it does) but whether there 
> are real uses
> for LOM that can not be done without LOM. Which take us to your second
> bullet.
> 
> > 	-Consider a situation, where the administrator wants
> > 	to overbook his data traffic, but does not want to
> > 	overbook the voice traffic on the link. In this case
> > 	max_reservable_bw knob is too coarse to be used. LOM
> > 	can aid with this configuration.
> 
> But is it really? My understanding is that in this particular case
> administrators would like to allow reservations of the voice traffic,
> presumably in its own CT, to reach its designated max level 
> regardless of
> the amount of reservations of data traffic. So LOM is no help 
> here as far as
> I can see. My educated guess is that in actual deployments a 
> priority CT
> will be admitted up to its max reservation level regardless 
> and at expense
> of the existing bookings at lower priority CTs.
> 
> > 	-In the past, some of the providers have indicated
> > 	their plans to use per CoS overbooking techniques.
> 
> Definitely so but the most likely without LOM. Service 
> providers may want to
> comment.
> 
> Regards,
>   Dimitry
> 
> 
> 
> 
> > -----Original Message-----
> > From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@Marconi.com]
> > Sent: Tuesday, June 03, 2003 10:10 AM
> > To: te-wg@ops.ietf.org
> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > method from
> > D S-TE specs?
> > 
> > 
> > Hi Francois, Jerry, All!
> > 
> > My first preference, would be to leave the DSTE-PROTO
> > as it is with the following changes:
> > 	(i)  replace the max_link_bw by max_reservable_bw
> > 	(ii) add some more text clarifying the LOM concept
> > 
> > If after another week of discussions, we are still at impasse,
> > my second preference would be to split the LOM text out of 
> > the DSTE-PROTO and make it its own draft. I do have serious 
> > reservations about the second approach, because we are just 
> > deferring the problem and not addressing the issue.
> > 
> > Now, lets examine the issues in little more detail::-
> > 
> > As of now, I have heard the following concerns about the 
> > LOM concept (as presented in the DSTE-PROTO):
> > 
> > 	Issue-1: LOM is a complex concept.
> > 	Issue-2: LOM makes DSTE-PROTO difficult to read
> > 	Issue-3: LOM is difficult to implement
> > 	Issue-4: LOM is difficult to deploy
> > 	Issue-5: We don't know if LOM is a useful concept
> > 
> > Here are my take on these issues::-
> > 
> > Issue-1:: In my opinion the LOM concept is the _least_
> > complex part of DSTE-PROTO. I think, people are confused
> > by the mechanics behind the co-existence of LOM, with the 
> > two *legacy* overbooking techniques.
> > 
> > DSTE-PROTO did not introduce the concept of "LSP Size
> > Overbooking" or "Link Size Overbooking". 
> > It just (i) gave formal name to the existing techniques
> > and (ii) ensured that the new LOM co-exists with the 
> > existing overbooking approaches.
> > 
> > The above mentioned existing overbooking techniques work
> > in existing non-DSTE networks (and will continue to work
> > in DSTE domains).
> > 
> > =>We can address this issue, by adding some clarifying text.
> > 
> > Issue-2:: DSTE is all about, providing per-CT BW control to
> > the network administrator. I think it makes the solution 
> > more complete by leaving the LOM text in.
> > 
> > =>We can easily solve the readability problem by adding
> > some clarifying text [will it be useful, if I propose some
> > text in this section?]
> > 
> > Issues-3:: I can't tell for others, but personally I think 
> > it is not a difficult feature to implement. After all, it
> > is just a multiplier!
> > 
> > =>Vendors don't have to implement it, if they think it is
> > difficult to implement the concept.
> > 
> > Issue-4:: When fine grained BW optimization is needed, 
> > the administrator will use the per-CT BW controls 
> > provided by the DSTE-PROTO. When dealing with a per-CT
> > level BW control, it is more natural to expect a per-CT
> > overbooking factor. After all, providers are used to
> > per-CoS overbooking concepts from their experience with
> > ATM.
> > 
> > =>DSTE-PROTO does not force all users to use the LOM 
> > concept, but provides enough per-CT control for the 
> > interested users.
> > 
> > Issue-5: I think per-CT overbooking solution (LOM) can 
> > be a useful tool the network administrators. It complements
> > the existing overbooking techniques, seamlessly.
> > 
> > 	-When the administrator has decided to deploy DSTE, 
> > 	obviously, he wants per-CT BW control. It is only 
> > 	natural to expect a per-CT overbooking knob 
> > 
> > 	-Consider a situation, where the administrator wants
> > 	to overbook his data traffic, but does not want to
> > 	overbook the voice traffic on the link. In this case
> > 	max_reservable_bw knob is too coarse to be used. LOM
> > 	can aid with this configuration.
> > 
> > 	-In the past, some of the providers have indicated
> > 	their plans to use per CoS overbooking techniques.
> > 
> > 
> > Thanks,
> > sanjay
> > 
> > 
> >  
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> > > Sent: Monday, June 02, 2003 11:19 AM
> > > To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> > > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > > method from
> > > DS-TE specs?
> > > 
> > > 
> > > Hello Jerry,
> > > 
> > > >> -----Original Message-----
> > > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> > > >> Sent: 02 June 2003 16:34
> > > >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
> > > >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
> > > >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > > >> method from DS-TE specs?
> > > >> 
> > > >> 
> > > >> Francois, All,
> > > >> 
> > > >> > The current approach is NOT complicated. Please see the 
> > > >> specific email
> > > >> > on this. 
> > > >> 
> > > >> That's your view, but I don't think it constitutes a proof 
> > > >> of same :-)
> > > >> 
> > > 
> > > Absolutely right. 
> > > Just like I would rather see statement saying that 
> someone finds the
> > > current model rather complicated as opposed to statement 
> > saying it is
> > > rather complicated. 8^)
> > > 
> > > >> > Note that its two main components (Link/Size Overbooking) are
> > > >> > directly inherited from existing TE. These two should not 
> > > >> be modified in
> > > >> > any way so they remain backward compatible with existing 
> > > TE anyway.
> > > >> > The current model works, all formulas are documented and 
> > > >> we had lots of
> > > >> > discussion so everybody is fully synched up on it now.
> > > >> > I see no justification to enter a new round of let's 
> > reinvent the
> > > >> > overbooking model for DS-TE at this post Last-Call stage.
> > > >> 
> > > >> I expected this comment, of course.  However, DS-TE is a 
> > > >> *new* environment (CTs, BC models, etc.), and we should have 
> > > >> the right to define things within that new environment.
> > > >> 
> > > >> However, so as to not drag this out, and come to closure, 
> > > >> I'm OK to go with your proposed formulas, pending a final 
> > > >> agreement on LOM (see below):
> > > >> 
> > > >> 
> > > 
> > > Great. This should allow us to move ahead fast as soon as 
> we make a
> > > final call on what to do with LOM.
> > > 
> > > >> When LOM is NOT used (i.e. 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
> > > >> 
> > > >> When LOM is used 
> > > >> ===============================
> > > >> o for each value of b in the range 0 <= b <= 7:
> > > >>   Normalized (CTb) <= BCb,
> > > >> o SUM (Normalized(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 (i.e. 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 ( Normalized(CTb,q) ) ] for q <= p,
> > > >> [ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p 
> > > >> and 0 <= b <= 7,]
> > > >> where:
> > > >> TE-Class [i] <--> < CTc , preemption p> 
> > > >> 
> > > >> > The idea of Experimental is that LOM would be neither 
> > "dead" nor
> > > >> > "standards". It would suggest that LOM is something we've 
> > > >> discussed and
> > > >> > documented and some people may want to play with. 
> > > >> Experience will tell
> > > >> > us what we should do with it.
> > > >> > Another good thing with Experimental is that I don't think 
> > > >> we have to
> > > >> > all agree that it is a useful thing as long as some 
> > people do. I
> > > >> > personally would have no problem in dropping LOM 
> > > altogether, but my
> > > >> > impression was that some people had a problem in dropping 
> > > >> it altogether
> > > >> > because we just don't really know whether it will be 
> > > >> useful or not. That
> > > >> > sounded like Experimental track to me.
> > > >> > 
> > > >> > Do you feel there is rough consensus to drop LOM 
> > > >> altogether (that would
> > > >> > work for me)?
> > > >> 
> > > >> I have not seen anyone give an example of where LOM is 
> > > >> needed.  Unless we see that, my preference would be to drop 
> > > >> it.  LOM is a real parameter, and at present needs to be 
> > > >> carried in the RSVP extensions for DS-TE.  It requires 
> > > >> addition aggregation constraints in the BC models.
> > > >> 
> > > >> Considerations of per-CT and hi-speed vs. low-speed links 
> > > >> can be easily accommodated, as I gave in an example by using 
> > > >> just LSPOM and LSOM (see earlier post 
> > > >> http://ops.ietf.org/lists/te-wg/te->> wg.2003/msg00314.html).  
> > > >> It seems like much more than 
> > > >> enough flexibility to avoid any problems, without also 
> > > >> further complication with LOM.  
> > > >> 
> > > >> Can anyone explain why LOM would be needed, and in 
> > > >> particular, give a practical example of same?
> > > >> 
> > > >> It seems to have marginal value (I don't see anyone showing 
> > > >> how it is needed, or really supporting it).  I think we can 
> > > >> agree that simplification *will* be achieved if we 
> eliminate LOM.
> > > 
> > > We can certainly agree on that.
> > > 
> > > So let's see if we hear some justiication for LOM or not, 
> > and based on
> > > that we can finalise decision (hopefully within a few days) 
> > firstly to
> > > take LOM out of base specs, and secondly to drop altogether 
> > > (or document
> > > as Experimental).
> > > 
> > > Cheers
> > > 
> > > Francois
> > > 
> > > >> 
> > > >> Thanks,
> > > >> Jerry
> > > >> 
> > > 
> > 
> 



From owner-te-wg@ops.ietf.org  Wed Jun  4 09:48: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 JAA19351
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 09:48:42 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NYc9-000AiD-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 13:47:41 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NYc6-000Ai0-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 13:47: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 JAA15873
	for <te-wg@ops.ietf.org>; Wed, 4 Jun 2003 09:47:35 -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 JAA17745
	for <te-wg@ops.ietf.org>; Wed, 4 Jun 2003 09:47:37 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L2412Q3C>; Wed, 4 Jun 2003 09:47:36 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F54B4@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, 4 Jun 2003 09:47:35 -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

Hi!
comments in-line.

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> Sent: Tuesday, June 03, 2003 7:28 PM
> To: te-wg@ops.ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS; Francois Le Faucheur 
> (flefauch); Lai,
> Wai S (Waisum), ALABS
> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> method from
> DS-TE specs?
> 
> 
> All,
> 
> I had proposed earlier:
> 
> > Can anyone give a practical example of where LOM is needed? 
> > Unless we see that, my preference would be to drop it.   
> 
> Since posting that, some examples have been given (on the 
> list and privately) that perhaps illustrate how LOM can be 
> used in practice.
> 
> Furthermore, based on the discussion so far:
> 
> 1. many people support leaving LOM in because they're 
> reluctant to give up the extra flexibility (even though they 
> don't offer specific supporting examples).
> 2. many people feel that the LOM extension is very simple, 
> therefore why the concern, just leave it there.
  
  And possibly a third category:
  3. people who think the LOM extension is relatively simple
  and think LOM has potential usage. 
  [On complexity issue : see my previous e-mail,
   For specific example: see my previous e-mail on issues and
				 the e-mail response to Dimitry's e-mail]

> 
> Also, I argued against having LOM progressed separately, I 
> think that would just complicate matters, and leave the BC 
> models, Proto extensions, etc. in a state of limbo (possible 
> awaiting a LOM extension later).  I had argued to either keep 
> LOM, or drop LOM, but not leave it in the 'in between' state.
> 
> Overall, I don't think the case has been made to drop LOM, 

  Personally, I agree with this view [given that LOM is already
  an optional feature]
  
  Thanks,
  sanjay	
  
> and, given that, I believe the better option is to leave LOM 
> as is and not progress it as a separate effort.
> 
> Thanks,
> Jerry
> 



From owner-te-wg@ops.ietf.org  Wed Jun  4 09:50:45 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19456
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 09:50:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NYew-000Av1-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 13:50:34 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NYel-000Auk-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 13:50:23 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 04 Jun 2003 15:49: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 h54Dm79G002984;
	Wed, 4 Jun 2003 15:48: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, 4 Jun 2003 15:49:31 +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, 4 Jun 2003 14:49:30 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5268@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMlRZUe5zk0/RxfQYS6Eh3/pe2FSgDTqcowABnXt/AAAV41YAAC+n9wAEW6giAAHltCoA==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
Cc: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
X-OriginalArrivalTime: 04 Jun 2003 13:49:31.0014 (UTC) FILETIME=[1F9ECA60:01C32AA0]
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 JAA19456

Jerry,

>> Also, I argued against having LOM progressed separately, I 
>> think that would just complicate matters, and leave the BC 
>> models, Proto extensions, etc. in a state of limbo (possible 
>> awaiting a LOM extension later).  I had argued to either 
>> keep LOM, or drop LOM, but not leave it in the 'in between' state.

I'd like to come back to your point above because:
	- (i) it is a concern that Sanjaya also expressed
	- (ii) I think we can find a way which does not leave things
more in a limbo than keeping it in as an option
	- (iii) I have the impression that putting LOM in an
Experimental draft is a solution that everybody else could probably
leave with (even if not their first choice) so this may be a way to get
out of the "impasse". Ie it is the second choice of people who favor
keeping LOM in the spec and of those who favor dropping LOM altogether.

We could basically take the exact same text that is currently spread
over -proto, -mam, -russian (and perhaps -mar if you've put some in
there) and group it into this new -LOM draft. So frankly, it terms of
how things are specified to work it would just be perfectly equivalent.
If your concern is that MAR may get left out, we could work on that,
perhaps try to work together on a section for the MAR-specific LOM
aspects (just like there would be a russian-specific and mam-specific
section cut-and-pasted from -russian and -mam).

The only real difference in making the same text appears in Exeprimental
draft is really to say that the TEWG would like to get more live
experience on DS-TE before deciding whether this should make Standards
Track or not. This seems to perfectly reflect the situation.
We've made the same decision for RDM, MAM and MAR: we've made them
Experimental to indicate that we needed more experience to decide which
one should become Standards.
I can't see that LOM is less Experimental than some of the BC models ^)

If we go that way, could you not live with LOM as Experimental?

Thanks

Francois



From owner-te-wg@ops.ietf.org  Wed Jun  4 10:06: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 KAA20826
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 10:06:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NYtd-000CI5-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 14:05:45 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NYtZ-000CHm-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 14:05:41 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 04 Jun 2003 16:04:48 +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 h54E3e76006220;
	Wed, 4 Jun 2003 16:03: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, 4 Jun 2003 16:05: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, 4 Jun 2003 15:05:13 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D9E437D9@xbe-lon-313.cisco.com>
Thread-Topic: Dropping the Local Overbooking Multiplier (LOM) method from DS-TE specs?
Thread-Index: AcMqoCPlvK963jshS3KjjDuZ9PrKZwAAZuVg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 04 Jun 2003 14:05:14.0083 (UTC) FILETIME=[51BBB330:01C32AA2]
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 KAA20826

Sanjay,

>> > 
>> > Overall, I don't think the case has been made to drop LOM, 
>> 
>>   Personally, I agree with this view [given that LOM is already
>>   an optional feature]
>>

Fair enough. 
Now at the same time we have a number of people (Siva, I believe Dimitry
and Siva) who indicated preference for dropping LOM. So I'm trying to
find out something we can agree on. Which is why I am folloiwng up on
your "second choice" in my other email 8^)

Cheers

Francois



From owner-te-wg@ops.ietf.org  Wed Jun  4 11:20: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 LAA26071
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 11:20:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NZxK-000IZp-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 15:13:38 +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 19NZxF-000IZ9-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 15:13:33 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F66F@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Choudhury, Sanjaya'" <Sanjaya.Choudhury@marconi.com>, te-wg@ops.ietf.org
Subject: RE: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM) 
	meth od from D S-TE specs?
Date: Wed, 4 Jun 2003 11:13:24 -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



> -----Original Message-----
> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@marconi.com]
> Sent: Wednesday, June 04, 2003 9:33 AM
> To: te-wg@ops.ietf.org
> Subject: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM)
> meth od from D S-TE specs?
> 
> 
> Hi Dimitry!,
> 
> Here is what we seem to agree on: A per-CT overbooking knob
> is useful for the administrators.
> 
> Now on to your second point: per-CT overbooking can be done
> without overbooking.

:)) .. perhaps "without LOM".

>In my personal opinion, you might have
> made few wrong assumptions:
> 
> 	1. Your example requires the preemption to be enabled
> 	in the domain; which may not be true.

Not at all. An alternative to preemption would be to allow degradation of
lower priority services, which IMO could be preferred to outright
preemption.
> 
> 	=>LOM gives user explicit control overbooking at a 
> 	per-CT level, without the need to preemption.

Which imposes on the bw isolation objective (ie. a higher priority CT should
not have some of its bw taken
by a lower priority CT).

> 
> 	2. You indicated "However without LOM amount of 
> 	reservations in one CT may not accurately affect 
> 	reservable bandwidths in other CTs of the same link"
> 
> 	=>Don't you think this a problem? Head-end LSR computed
> 	the path based on the advertised BWs per-CT [which is
> 	is the foundation of DSTE], will now compute a wrong
> 	path.

Not at all. Path computations are based on the advertised "unreserved bw"
for each CT/link. So it is local matter for advertising nodes to correctly
reflect what they are planning to accept at a particular CT.

> 
> 	2. For a moment let is assume that preemption *is* 
> 	deployed in the domain. Can you explain me how I 
> 	will achieve the following [please be specific in
> 	what the user will need to do and the BC model in 
> 	use]:
> 
> 		case-1: want to overbook data-traffic without
> 		overbooking voice traffic.
> 
> 		case-2: Want to overbook the voice traffic by
> 		10%, but want to overbook data traffic by 40%
> 
> 		case-3: want to overbook gold-traffic by 10%,
> 		overbook silver-traffic by 15%, overbook 
> 		normal-traffic by 20%

What is the catch? Why would not you do just that? I.e., overbook each CT
independently to their respective designated level. 
Or, I supposed, you have missed the aggregate constraint from you examples
which would make them slightly more illustrative. Not that I want to help
you to make your case ;)

> 
> 	3. Can all of the above be achieved without the 
> 	use pre-emption?

To reiterate, yes it can. We had a long discussion on that a while ago in
respect of RD vs MA models.
> 
> 
> Thanks,
> sanjay

Regards,
  Dimitry
> 
> 		
> 
> 
> > -----Original Message-----
> > From: Dimitry Haskin [mailto:dhaskin@axiowave.com]
> > Sent: Tuesday, June 03, 2003 2:34 PM
> > To: 'Choudhury, Sanjaya'; te-wg@ops.ietf.org
> > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > method from
> > D S-TE specs?
> > 
> > 
> > Sanjaya,
> > 
> > Let me take you on Issue-5 ("We don't know if LOM is a useful 
> > concept")
> > since if we new that it is really useful it would be a good 
> > reason to keep
> > LOM in the base spec.
> > 
> > > 	-When the administrator has decided to deploy DSTE, 
> > > 	obviously, he wants per-CT BW control. It is only 
> > > 	natural to expect a per-CT overbooking knob 
> > >
> > 
> > A per-CT overbooking knob will exist without LOM. However 
> > without LOM amount
> > of reservations in one CT may not accurately effect 
> > reservable bandwidths in
> > other CTs of the same link. So the real question is not if a per-CT
> > overbooking knob is need (of cause it does) but whether there 
> > are real uses
> > for LOM that can not be done without LOM. Which take us to 
> your second
> > bullet.
> > 
> > > 	-Consider a situation, where the administrator wants
> > > 	to overbook his data traffic, but does not want to
> > > 	overbook the voice traffic on the link. In this case
> > > 	max_reservable_bw knob is too coarse to be used. LOM
> > > 	can aid with this configuration.
> > 
> > But is it really? My understanding is that in this particular case
> > administrators would like to allow reservations of the 
> voice traffic,
> > presumably in its own CT, to reach its designated max level 
> > regardless of
> > the amount of reservations of data traffic. So LOM is no help 
> > here as far as
> > I can see. My educated guess is that in actual deployments a 
> > priority CT
> > will be admitted up to its max reservation level regardless 
> > and at expense
> > of the existing bookings at lower priority CTs.
> > 
> > > 	-In the past, some of the providers have indicated
> > > 	their plans to use per CoS overbooking techniques.
> > 
> > Definitely so but the most likely without LOM. Service 
> > providers may want to
> > comment.
> > 
> > Regards,
> >   Dimitry
> > 
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@Marconi.com]
> > > Sent: Tuesday, June 03, 2003 10:10 AM
> > > To: te-wg@ops.ietf.org
> > > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > > method from
> > > D S-TE specs?
> > > 
> > > 
> > > Hi Francois, Jerry, All!
> > > 
> > > My first preference, would be to leave the DSTE-PROTO
> > > as it is with the following changes:
> > > 	(i)  replace the max_link_bw by max_reservable_bw
> > > 	(ii) add some more text clarifying the LOM concept
> > > 
> > > If after another week of discussions, we are still at impasse,
> > > my second preference would be to split the LOM text out of 
> > > the DSTE-PROTO and make it its own draft. I do have serious 
> > > reservations about the second approach, because we are just 
> > > deferring the problem and not addressing the issue.
> > > 
> > > Now, lets examine the issues in little more detail::-
> > > 
> > > As of now, I have heard the following concerns about the 
> > > LOM concept (as presented in the DSTE-PROTO):
> > > 
> > > 	Issue-1: LOM is a complex concept.
> > > 	Issue-2: LOM makes DSTE-PROTO difficult to read
> > > 	Issue-3: LOM is difficult to implement
> > > 	Issue-4: LOM is difficult to deploy
> > > 	Issue-5: We don't know if LOM is a useful concept
> > > 
> > > Here are my take on these issues::-
> > > 
> > > Issue-1:: In my opinion the LOM concept is the _least_
> > > complex part of DSTE-PROTO. I think, people are confused
> > > by the mechanics behind the co-existence of LOM, with the 
> > > two *legacy* overbooking techniques.
> > > 
> > > DSTE-PROTO did not introduce the concept of "LSP Size
> > > Overbooking" or "Link Size Overbooking". 
> > > It just (i) gave formal name to the existing techniques
> > > and (ii) ensured that the new LOM co-exists with the 
> > > existing overbooking approaches.
> > > 
> > > The above mentioned existing overbooking techniques work
> > > in existing non-DSTE networks (and will continue to work
> > > in DSTE domains).
> > > 
> > > =>We can address this issue, by adding some clarifying text.
> > > 
> > > Issue-2:: DSTE is all about, providing per-CT BW control to
> > > the network administrator. I think it makes the solution 
> > > more complete by leaving the LOM text in.
> > > 
> > > =>We can easily solve the readability problem by adding
> > > some clarifying text [will it be useful, if I propose some
> > > text in this section?]
> > > 
> > > Issues-3:: I can't tell for others, but personally I think 
> > > it is not a difficult feature to implement. After all, it
> > > is just a multiplier!
> > > 
> > > =>Vendors don't have to implement it, if they think it is
> > > difficult to implement the concept.
> > > 
> > > Issue-4:: When fine grained BW optimization is needed, 
> > > the administrator will use the per-CT BW controls 
> > > provided by the DSTE-PROTO. When dealing with a per-CT
> > > level BW control, it is more natural to expect a per-CT
> > > overbooking factor. After all, providers are used to
> > > per-CoS overbooking concepts from their experience with
> > > ATM.
> > > 
> > > =>DSTE-PROTO does not force all users to use the LOM 
> > > concept, but provides enough per-CT control for the 
> > > interested users.
> > > 
> > > Issue-5: I think per-CT overbooking solution (LOM) can 
> > > be a useful tool the network administrators. It complements
> > > the existing overbooking techniques, seamlessly.
> > > 
> > > 	-When the administrator has decided to deploy DSTE, 
> > > 	obviously, he wants per-CT BW control. It is only 
> > > 	natural to expect a per-CT overbooking knob 
> > > 
> > > 	-Consider a situation, where the administrator wants
> > > 	to overbook his data traffic, but does not want to
> > > 	overbook the voice traffic on the link. In this case
> > > 	max_reservable_bw knob is too coarse to be used. LOM
> > > 	can aid with this configuration.
> > > 
> > > 	-In the past, some of the providers have indicated
> > > 	their plans to use per CoS overbooking techniques.
> > > 
> > > 
> > > Thanks,
> > > sanjay
> > > 
> > > 
> > >  
> > > 
> > > 
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Francois Le Faucheur (flefauch) 
> [mailto:flefauch@cisco.com]
> > > > Sent: Monday, June 02, 2003 11:19 AM
> > > > To: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> > > > Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > > > method from
> > > > DS-TE specs?
> > > > 
> > > > 
> > > > Hello Jerry,
> > > > 
> > > > >> -----Original Message-----
> > > > >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
> > > > >> Sent: 02 June 2003 16:34
> > > > >> To: Francois Le Faucheur (flefauch); te-wg@ops.ietf.org
> > > > >> Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS
> > > > >> Subject: RE: Dropping the Local Overbooking Multiplier (LOM) 
> > > > >> method from DS-TE specs?
> > > > >> 
> > > > >> 
> > > > >> Francois, All,
> > > > >> 
> > > > >> > The current approach is NOT complicated. Please see the 
> > > > >> specific email
> > > > >> > on this. 
> > > > >> 
> > > > >> That's your view, but I don't think it constitutes a proof 
> > > > >> of same :-)
> > > > >> 
> > > > 
> > > > Absolutely right. 
> > > > Just like I would rather see statement saying that 
> > someone finds the
> > > > current model rather complicated as opposed to statement 
> > > saying it is
> > > > rather complicated. 8^)
> > > > 
> > > > >> > Note that its two main components (Link/Size 
> Overbooking) are
> > > > >> > directly inherited from existing TE. These two should not 
> > > > >> be modified in
> > > > >> > any way so they remain backward compatible with existing 
> > > > TE anyway.
> > > > >> > The current model works, all formulas are documented and 
> > > > >> we had lots of
> > > > >> > discussion so everybody is fully synched up on it now.
> > > > >> > I see no justification to enter a new round of let's 
> > > reinvent the
> > > > >> > overbooking model for DS-TE at this post Last-Call stage.
> > > > >> 
> > > > >> I expected this comment, of course.  However, DS-TE is a 
> > > > >> *new* environment (CTs, BC models, etc.), and we should have 
> > > > >> the right to define things within that new environment.
> > > > >> 
> > > > >> However, so as to not drag this out, and come to closure, 
> > > > >> I'm OK to go with your proposed formulas, pending a final 
> > > > >> agreement on LOM (see below):
> > > > >> 
> > > > >> 
> > > > 
> > > > Great. This should allow us to move ahead fast as soon as 
> > we make a
> > > > final call on what to do with LOM.
> > > > 
> > > > >> When LOM is NOT used (i.e. 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
> > > > >> 
> > > > >> When LOM is used 
> > > > >> ===============================
> > > > >> o for each value of b in the range 0 <= b <= 7:
> > > > >>   Normalized (CTb) <= BCb,
> > > > >> o SUM (Normalized(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 (i.e. 
> 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 ( Normalized(CTb,q) ) ] for q <= p,
> > > > >> [ Max_Reservable_Bw - SUM ( Normalized(CTb,q) ) ] for q <= p 
> > > > >> and 0 <= b <= 7,]
> > > > >> where:
> > > > >> TE-Class [i] <--> < CTc , preemption p> 
> > > > >> 
> > > > >> > The idea of Experimental is that LOM would be neither 
> > > "dead" nor
> > > > >> > "standards". It would suggest that LOM is something we've 
> > > > >> discussed and
> > > > >> > documented and some people may want to play with. 
> > > > >> Experience will tell
> > > > >> > us what we should do with it.
> > > > >> > Another good thing with Experimental is that I don't think 
> > > > >> we have to
> > > > >> > all agree that it is a useful thing as long as some 
> > > people do. I
> > > > >> > personally would have no problem in dropping LOM 
> > > > altogether, but my
> > > > >> > impression was that some people had a problem in dropping 
> > > > >> it altogether
> > > > >> > because we just don't really know whether it will be 
> > > > >> useful or not. That
> > > > >> > sounded like Experimental track to me.
> > > > >> > 
> > > > >> > Do you feel there is rough consensus to drop LOM 
> > > > >> altogether (that would
> > > > >> > work for me)?
> > > > >> 
> > > > >> I have not seen anyone give an example of where LOM is 
> > > > >> needed.  Unless we see that, my preference would be to drop 
> > > > >> it.  LOM is a real parameter, and at present needs to be 
> > > > >> carried in the RSVP extensions for DS-TE.  It requires 
> > > > >> addition aggregation constraints in the BC models.
> > > > >> 
> > > > >> Considerations of per-CT and hi-speed vs. low-speed links 
> > > > >> can be easily accommodated, as I gave in an example by using 
> > > > >> just LSPOM and LSOM (see earlier post 
> > > > >> http://ops.ietf.org/lists/te-wg/te->> 
> wg.2003/msg00314.html).  
> > > > >> It seems like much more than 
> > > > >> enough flexibility to avoid any problems, without also 
> > > > >> further complication with LOM.  
> > > > >> 
> > > > >> Can anyone explain why LOM would be needed, and in 
> > > > >> particular, give a practical example of same?
> > > > >> 
> > > > >> It seems to have marginal value (I don't see anyone showing 
> > > > >> how it is needed, or really supporting it).  I think we can 
> > > > >> agree that simplification *will* be achieved if we 
> > eliminate LOM.
> > > > 
> > > > We can certainly agree on that.
> > > > 
> > > > So let's see if we hear some justiication for LOM or not, 
> > > and based on
> > > > that we can finalise decision (hopefully within a few days) 
> > > firstly to
> > > > take LOM out of base specs, and secondly to drop altogether 
> > > > (or document
> > > > as Experimental).
> > > > 
> > > > Cheers
> > > > 
> > > > Francois
> > > > 
> > > > >> 
> > > > >> Thanks,
> > > > >> Jerry
> > > > >> 
> > > > 
> > > 
> > 
> 



From owner-te-wg@ops.ietf.org  Wed Jun  4 16:59:09 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12029
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 16:59:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NfIp-000PZS-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 20:56:11 +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 19NfIm-000PXz-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 20:56:08 +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 h54Iwdx3007970
	for <te-wg@ops.ietf.org>; Wed, 4 Jun 2003 16:55:30 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EDE22A40001B5CC for te-wg@ops.ietf.org; Wed, 4 Jun 2003 16:55:28 -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: Example of LOM usage
Date: Wed, 4 Jun 2003 15:55:31 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA1370BA@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM) meth od from D S-TE specs?
Thread-Index: AcMqrfdjpL+jBSEATm2xZNB2qxNORQAIKE1g
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
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 QAA12029

This is a response to the request for an example of LOM usage by
service providers in per-link per-CT overbooking.

Suppose link0 has 100 units (e.g., Mbps of link bandwidth), of which
say 30 is allocated to CT0, and 70 to CT1.  Similarly, link1 has 500
units, of which 150 is to CT0, and 350 to CT1.  That is, with 30%/70%
allocation for both links, the bandwidth constraints are in the same
proportion for both.  Then, in going from link0 to link1, CT0 sees an
increase from 30 to 150, while CT1 sees an increase from 70 to 350.

To get a feel for the change in per-CT overbooking needed for the two
links, at a very high level, we use the simple Erlang formula, assuming
1% LSP blocking for both CT0 and CT1.  (Obviously, this is very very
crude, without any consideration for sharing - but the idea is to
see the scaling effect of link speeds, to be explained below.)
 30 units support an offered load of  20.3 units (68% utilization)
150 units support an offered load of 131.6 units (88% utilization)
 70 units support an offered load of  56.1 units (80% utilization)
350 units support an offered load of 326.2 units (93% utilization)

With only 30 units in link0, CT0 has a much smaller overbooking to
start with.  Thus, CT0 should see a proportionally bigger increase
in overbooking in link1, as the utilization increases by 20% from
68% to 88%.

OTOH, CT1 has 70 units in link0 and can work with a higher overbooking.
Thus, CT1 should see a proportionally smaller increase in overbooking
in link1, as the utilization increase is much smaller, by 13% from 80%
to 93%.

In summary, depending on the relative traffic size, per-CT overbooking
may need to be proportionally different, even with LSPOM and LSOM in
use.  This is because different CTs may see different scaling effects
when link speeds change.  To support application scenarios like this,
the use of LOM is needed.

Given that LOM is to be retained, I agree with Jerry that we should
leave LOM as is and not progress it as a separate effort.  Thus, I
would like to see some discussion on how LOM could be simplified:
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00321.html
This proposal is FULLY backward compatible with existing TE.

The formulation currently described in existing drafts is complicated
with the use of different formulas in different components.  This will
lead to operational complexity, as well as operational errors such as
misconfigurations.  The above proposal does NOT call for a reinvention
or redefinition of the overbooking model, rather, just a simplification
of what already exists by a more coherent and seamless integration.

Thanks, Wai Sum 



From owner-te-wg@ops.ietf.org  Wed Jun  4 19:57: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 TAA18049
	for <tewg-archive@lists.ietf.org>; Wed, 4 Jun 2003 19:57:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Ni5f-000MAj-00
	for te-wg-data@psg.com; Wed, 04 Jun 2003 23:54:47 +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 19Ni5c-000M9a-00
	for te-wg@ops.ietf.org; Wed, 04 Jun 2003 23:54:45 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F673@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Lai, Wai S (Waisum), ALABS'" <wlai@att.com>, te-wg@ops.ietf.org
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Subject: RE: Example of LOM usage
Date: Wed, 4 Jun 2003 19:54:36 -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

Lai,

I understand that a provider may want different per CT overbooking ratios on
different links. However I still fail to understand why LOM would be
required to provide a good service in such a configuration. Can you clarify?

Thanks,
  Dimitry

> -----Original Message-----
> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
> Sent: Wednesday, June 04, 2003 4:56 PM
> To: te-wg@ops.ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: Example of LOM usage
> 
> 
> This is a response to the request for an example of LOM usage by
> service providers in per-link per-CT overbooking.
> 
> Suppose link0 has 100 units (e.g., Mbps of link bandwidth), of which
> say 30 is allocated to CT0, and 70 to CT1.  Similarly, link1 has 500
> units, of which 150 is to CT0, and 350 to CT1.  That is, with 30%/70%
> allocation for both links, the bandwidth constraints are in the same
> proportion for both.  Then, in going from link0 to link1, CT0 sees an
> increase from 30 to 150, while CT1 sees an increase from 70 to 350.
> 
> To get a feel for the change in per-CT overbooking needed for the two
> links, at a very high level, we use the simple Erlang 
> formula, assuming
> 1% LSP blocking for both CT0 and CT1.  (Obviously, this is very very
> crude, without any consideration for sharing - but the idea is to
> see the scaling effect of link speeds, to be explained below.)
>  30 units support an offered load of  20.3 units (68% utilization)
> 150 units support an offered load of 131.6 units (88% utilization)
>  70 units support an offered load of  56.1 units (80% utilization)
> 350 units support an offered load of 326.2 units (93% utilization)
> 
> With only 30 units in link0, CT0 has a much smaller overbooking to
> start with.  Thus, CT0 should see a proportionally bigger increase
> in overbooking in link1, as the utilization increases by 20% from
> 68% to 88%.
> 
> OTOH, CT1 has 70 units in link0 and can work with a higher 
> overbooking.
> Thus, CT1 should see a proportionally smaller increase in overbooking
> in link1, as the utilization increase is much smaller, by 13% from 80%
> to 93%.
> 
> In summary, depending on the relative traffic size, per-CT overbooking
> may need to be proportionally different, even with LSPOM and LSOM in
> use.  This is because different CTs may see different scaling effects
> when link speeds change.  To support application scenarios like this,
> the use of LOM is needed.
> 
> Given that LOM is to be retained, I agree with Jerry that we should
> leave LOM as is and not progress it as a separate effort.  Thus, I
> would like to see some discussion on how LOM could be simplified:
> http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00321.html
> This proposal is FULLY backward compatible with existing TE.
> 
> The formulation currently described in existing drafts is complicated
> with the use of different formulas in different components.  This will
> lead to operational complexity, as well as operational errors such as
> misconfigurations.  The above proposal does NOT call for a reinvention
> or redefinition of the overbooking model, rather, just a 
> simplification
> of what already exists by a more coherent and seamless integration.
> 
> Thanks, Wai Sum 
> 



From owner-te-wg@ops.ietf.org  Thu Jun  5 09:12: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 JAA23535
	for <tewg-archive@lists.ietf.org>; Thu, 5 Jun 2003 09:12:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NuRV-000EW2-00
	for te-wg-data@psg.com; Thu, 05 Jun 2003 13:06:09 +0000
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NuRR-000EVe-00
	for te-wg@ops.ietf.org; Thu, 05 Jun 2003 13:06:05 +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 JAA13724
	for <te-wg@ops.ietf.org>; Thu, 5 Jun 2003 09:06:03 -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 JAA22996
	for <te-wg@ops.ietf.org>; Thu, 5 Jun 2003 09:06:03 -0400 (EDT)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <L241JJA2>; Thu, 5 Jun 2003 09:06:03 -0400
Message-ID: <313680C9A886D511A06000204840E1CF8F54BB@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: RE: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM) 
	 meth od from D S-TE specs?
Date: Thu, 5 Jun 2003 09:06:00 -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 Dimitry!
> -----Original Message-----
> From: Dimitry Haskin [mailto:dhaskin@axiowave.com]
> Sent: Wednesday, June 04, 2003 11:13 AM
> To: 'Choudhury, Sanjaya'; te-wg@ops.ietf.org
> Subject: RE: Issue-5: RE: Dropping the Local Overbooking Multiplier
> (LOM) meth od from D S-TE specs?
> 
<snip..>
> > 
> > 	2. For a moment let is assume that preemption *is* 
> > 	deployed in the domain. Can you explain me how I 
> > 	will achieve the following [please be specific in
> > 	what the user will need to do and the BC model in 
> > 	use]:
> > 
> > 		case-1: want to overbook data-traffic without
> > 		overbooking voice traffic.
> > 
> > 		case-2: Want to overbook the voice traffic by
> > 		10%, but want to overbook data traffic by 40%
> > 
> > 		case-3: want to overbook gold-traffic by 10%,
> > 		overbook silver-traffic by 15%, overbook 
> > 		normal-traffic by 20%
> 
> What is the catch? Why would not you do just that? I.e., 
> overbook each CT
> independently to their respective designated level. 

  I am still trying to understand _how_ (you propose to
  overbook each CT independently)? DSTE-PROTO proposes
  3 approaches: 
	(i) LSP Size overbooking i.e user specifies a 
	higher/lower bw requirement for the LSP during 
	creation)
	(ii) Link Size overbooking (user modifies the 
	max_reservable_bw)
	(iii) LOM
  Which of these above three approaches, should the 
  administrator use (obviously you are not indicating
  (iii) ?

  Or are you proposing to manipulate the BCs (for 
  individual CTs)???

> Or, I supposed, you have missed the aggregate constraint from 
> you examples
> which would make them slightly more illustrative. Not that I 
> want to help
> you to make your case ;)

  Your help will be appreciated.

  Thanks,
  sanjay

>
<snip..>
> 



From owner-te-wg@ops.ietf.org  Thu Jun  5 09:16: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 JAA23809
	for <tewg-archive@lists.ietf.org>; Thu, 5 Jun 2003 09:16:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Nuah-000Exi-00
	for te-wg-data@psg.com; Thu, 05 Jun 2003 13:15:39 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Nuaf-000ExW-00
	for te-wg@ops.ietf.org; Thu, 05 Jun 2003 13:15:37 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 05 Jun 2003 15:14:43 +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 h55DDaYE011443;
	Thu, 5 Jun 2003 15:13:36 +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, 5 Jun 2003 15:15:25 +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: Example of LOM usage
Date: Thu, 5 Jun 2003 14:15:24 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5270@xbe-lon-313.cisco.com>
Thread-Topic: Example of LOM usage
Thread-Index: AcMq9RhlpX5y8b/UTEekwWPOFiI04gAbQZgQ
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: 05 Jun 2003 13:15:25.0118 (UTC) FILETIME=[869595E0:01C32B64]
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 JAA23809

Dimitry,

>> I understand that a provider may want different per CT 
>> overbooking ratios on
>> different links. However I still fail to understand why LOM would be
>> required to provide a good service in such a configuration. 
>> Can you clarify?
>> 

I believe we have already discuss when LOM is required or not and
concluded on that. Quoting from your message:
>> 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

To put the same thing in a different way:
	- if you don't need per-CT-per-link ratios, you do NOT need LOM
	- if you need per-CT-per-Link ratios and can tolerate some
inaccuracy in how a CT affects the global constraints (which I think you
also refer to as allowing some degradation on some CTs in your
discussion with Sanjaya), then you do NOT need LOM.
	- if you need per-CT-per-Link ratios and want accuracy in how a
CT affects the global constraints, then you do need LOM.

So the points I think you're getting at are that:
	1) needing per-CT-per-Link ratios does not always mean you need
LOM
	2) from your experience:
	- most SPs won't need per-CT-per-link ratios
	- the few SPs who may need per-CT-per-link ratios are likely to
tolerate some inaccuracy in bookeeping over the aggregate constraint,
Therefore the case for LOM is very slim.

Right?

Cheers

Francois



From owner-te-wg@ops.ietf.org  Thu Jun  5 09:23: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 JAA23995
	for <tewg-archive@lists.ietf.org>; Thu, 5 Jun 2003 09:23:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NuhY-000FNh-00
	for te-wg-data@psg.com; Thu, 05 Jun 2003 13:22:44 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NuhV-000FNU-00
	for te-wg@ops.ietf.org; Thu, 05 Jun 2003 13:22:41 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 05 Jun 2003 15:21:47 +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 h55DKXgf012583;
	Thu, 5 Jun 2003 15:20: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);
	 Thu, 5 Jun 2003 15:22: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: RE: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM)  meth od from D S-TE specs?
Date: Thu, 5 Jun 2003 14:22:36 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5271@xbe-lon-313.cisco.com>
Thread-Topic: Issue-5: RE: Dropping the Local Overbooking Multiplier (LOM)  meth od from D S-TE specs?
Thread-Index: AcMrZDnsaHs9p67mRwWkEDH5PJoOsQAAFwQg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 05 Jun 2003 13:22:37.0136 (UTC) FILETIME=[88164D00:01C32B65]
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 JAA23995

Sanjaya, Dimitry,

I could be wrong here (apologies if that is the case), but I have the
impression the point of disconnect between you two is that:

Dimitry's pretty much arguing that:
	- if you need per-CT-per-Link ratios and can tolerate some
inaccuracy in how a CT affects the global constraints, then you do NOT
need LOM.

While Sanjaya is pretty much arguing that:
	- if you need per-CT-per-Link ratios and want accuracy in how a
CT affects the global constraints, then you do need LOM.

Both are true. The trick is in accuracy of how a CT impacts other CTs
who share a global constraint.

Hope that helps 

Francois

>> -----Original Message-----
>> From: Choudhury, Sanjaya [mailto:Sanjaya.Choudhury@marconi.com] 
>> Sent: 05 June 2003 15:06
>> To: te-wg@ops.ietf.org
>> Subject: RE: Issue-5: RE: Dropping the Local Overbooking 
>> Multiplier (LOM) meth od from D S-TE specs?
>> 
>> 
>> 
>> Hi Dimitry!
>> > -----Original Message-----
>> > From: Dimitry Haskin [mailto:dhaskin@axiowave.com]
>> > Sent: Wednesday, June 04, 2003 11:13 AM
>> > To: 'Choudhury, Sanjaya'; te-wg@ops.ietf.org
>> > Subject: RE: Issue-5: RE: Dropping the Local Overbooking Multiplier
>> > (LOM) meth od from D S-TE specs?
>> > 
>> <snip..>
>> > > 
>> > > 	2. For a moment let is assume that preemption *is* 
>> > > 	deployed in the domain. Can you explain me how I 
>> > > 	will achieve the following [please be specific in
>> > > 	what the user will need to do and the BC model in 
>> > > 	use]:
>> > > 
>> > > 		case-1: want to overbook data-traffic without
>> > > 		overbooking voice traffic.
>> > > 
>> > > 		case-2: Want to overbook the voice traffic by
>> > > 		10%, but want to overbook data traffic by 40%
>> > > 
>> > > 		case-3: want to overbook gold-traffic by 10%,
>> > > 		overbook silver-traffic by 15%, overbook 
>> > > 		normal-traffic by 20%
>> > 
>> > What is the catch? Why would not you do just that? I.e., 
>> > overbook each CT
>> > independently to their respective designated level. 
>> 
>>   I am still trying to understand _how_ (you propose to
>>   overbook each CT independently)? DSTE-PROTO proposes
>>   3 approaches: 
>> 	(i) LSP Size overbooking i.e user specifies a 
>> 	higher/lower bw requirement for the LSP during 
>> 	creation)
>> 	(ii) Link Size overbooking (user modifies the 
>> 	max_reservable_bw)
>> 	(iii) LOM
>>   Which of these above three approaches, should the 
>>   administrator use (obviously you are not indicating
>>   (iii) ?
>> 
>>   Or are you proposing to manipulate the BCs (for 
>>   individual CTs)???
>> 
>> > Or, I supposed, you have missed the aggregate constraint from 
>> > you examples
>> > which would make them slightly more illustrative. Not that I 
>> > want to help
>> > you to make your case ;)
>> 
>>   Your help will be appreciated.
>> 
>>   Thanks,
>>   sanjay
>> 
>> >
>> <snip..>
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Thu Jun  5 09:59: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 JAA25957
	for <tewg-archive@lists.ietf.org>; Thu, 5 Jun 2003 09:59:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NvGS-000HPx-00
	for te-wg-data@psg.com; Thu, 05 Jun 2003 13:58:48 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19NvGO-000HPe-00
	for te-wg@ops.ietf.org; Thu, 05 Jun 2003 13:58:44 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 05 Jun 2003 15:57:49 +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 h55DubXY019381;
	Thu, 5 Jun 2003 15:56: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);
	 Thu, 5 Jun 2003 15:58: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: RE: Example of LOM usage
Date: Thu, 5 Jun 2003 14:58:37 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5272@xbe-lon-313.cisco.com>
Thread-Topic: Example of LOM usage
Thread-Index: AcMqrfdjpL+jBSEATm2xZNB2qxNORQAIKE1gACZWkzA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 05 Jun 2003 13:58:37.0743 (UTC) FILETIME=[8FE8C3F0:01C32B6A]
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 JAA25957

Waisum,

I think there is agreement that the fundamental theoretical reason why,
ideally, one way want to have different per-CT overbooking ratios on
different links is because a number of things don't grow linearly (like
the erlang formula).
Thanks for giving a quantified example illustrating the distortion.

But the input I am personally after is: are there service providers out
there who are likely to be really after that level of 2nd order of
optimisation in the next few years? My impression is that it is
interesting enough for an operator to try come up with the right
formula/heuristics for factoring some LSP size overbooking and some Link
size overbooking with a single class in regular TE today. When moving to
DS-TE, operators will have to extend the formulas/heuristics for LSP
size overbooking on a per-CT basis, so trying to factor it a second
level of distortion via a per-CT-per-link overbooking tweak seems a far
stretch in practise. Obviously, I could be wrong. But we still haven't
heard an operator saying he is likely to be interested in that level of
optimisation for DS-TE. 

This is also discounting Dimitry's point, thet operators could even do
that without LOM anyway if they accepted to tolerate some inacuracy on
the aggregate constraint.

Cheers

Francois

>> -----Original Message-----
>> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com] 
>> Sent: 04 June 2003 22:56
>> To: te-wg@ops.ietf.org
>> Cc: Ash, Gerald R (Jerry), ALABS
>> Subject: Example of LOM usage
>> 
>> 
>> This is a response to the request for an example of LOM usage by
>> service providers in per-link per-CT overbooking.
>> 
>> Suppose link0 has 100 units (e.g., Mbps of link bandwidth), of which
>> say 30 is allocated to CT0, and 70 to CT1.  Similarly, link1 has 500
>> units, of which 150 is to CT0, and 350 to CT1.  That is, with 30%/70%
>> allocation for both links, the bandwidth constraints are in the same
>> proportion for both.  Then, in going from link0 to link1, CT0 sees an
>> increase from 30 to 150, while CT1 sees an increase from 70 to 350.
>> 
>> To get a feel for the change in per-CT overbooking needed for the two
>> links, at a very high level, we use the simple Erlang 
>> formula, assuming
>> 1% LSP blocking for both CT0 and CT1.  (Obviously, this is very very
>> crude, without any consideration for sharing - but the idea is to
>> see the scaling effect of link speeds, to be explained below.)
>>  30 units support an offered load of  20.3 units (68% utilization)
>> 150 units support an offered load of 131.6 units (88% utilization)
>>  70 units support an offered load of  56.1 units (80% utilization)
>> 350 units support an offered load of 326.2 units (93% utilization)
>> 
>> With only 30 units in link0, CT0 has a much smaller overbooking to
>> start with.  Thus, CT0 should see a proportionally bigger increase
>> in overbooking in link1, as the utilization increases by 20% from
>> 68% to 88%.
>> 
>> OTOH, CT1 has 70 units in link0 and can work with a higher 
>> overbooking.
>> Thus, CT1 should see a proportionally smaller increase in overbooking
>> in link1, as the utilization increase is much smaller, by 
>> 13% from 80%
>> to 93%.
>> 
>> In summary, depending on the relative traffic size, per-CT 
>> overbooking
>> may need to be proportionally different, even with LSPOM and LSOM in
>> use.  This is because different CTs may see different scaling effects
>> when link speeds change.  To support application scenarios like this,
>> the use of LOM is needed.
>> 
>> Given that LOM is to be retained, I agree with Jerry that we should
>> leave LOM as is and not progress it as a separate effort.  Thus, I
>> would like to see some discussion on how LOM could be simplified:
>> http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00321.html
>> This proposal is FULLY backward compatible with existing TE.
>> 
>> The formulation currently described in existing drafts is complicated
>> with the use of different formulas in different components.  
>> This will
>> lead to operational complexity, as well as operational errors such as
>> misconfigurations.  The above proposal does NOT call for a 
>> reinvention
>> or redefinition of the overbooking model, rather, just a 
>> simplification
>> of what already exists by a more coherent and seamless integration.
>> 
>> Thanks, Wai Sum 
>> 
>> 



From owner-te-wg@ops.ietf.org  Thu Jun  5 11:29: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 LAA02765
	for <tewg-archive@lists.ietf.org>; Thu, 5 Jun 2003 11:29:29 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19NweG-000MRm-00
	for te-wg-data@psg.com; Thu, 05 Jun 2003 15:27:28 +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 19NweD-000MQr-00
	for te-wg@ops.ietf.org; Thu, 05 Jun 2003 15:27:25 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F674@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        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>
Subject: RE: Example of LOM usage
Date: Thu, 5 Jun 2003 11:27:02 -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,

Correct, these are points that I'm making.  A minor correction is that I'm
not claiming that "most SPs won't need per-CT-per-link ratios". Nevertheless
the second bullet in point 2 is largely correct.

There seems to be a persistent impression that use of LOM (as currently
specified) is absolutely necessary when different per-CT-per-link
overbooking ratios are required whereas the quite opposite is true in
practice. This level of confusion that LOM creates seems disproportional to
its dubious value. This is why removing it from the base spec appears to be
a desirable way to proceed.

Dimitry

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Thursday, June 05, 2003 9:15 AM
> To: Dimitry Haskin; Lai, Wai S (Waisum), ALABS; te-wg@ops.ietf.org
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: Example of LOM usage
> 
> 
> Dimitry,
> 
> >> I understand that a provider may want different per CT 
> >> overbooking ratios on
> >> different links. However I still fail to understand why 
> LOM would be
> >> required to provide a good service in such a configuration. 
> >> Can you clarify?
> >> 
> 
> I believe we have already discuss when LOM is required or not and
> concluded on that. Quoting from your message:
> >> 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
> 
> To put the same thing in a different way:
> 	- if you don't need per-CT-per-link ratios, you do NOT need LOM
> 	- if you need per-CT-per-Link ratios and can tolerate some
> inaccuracy in how a CT affects the global constraints (which 
> I think you
> also refer to as allowing some degradation on some CTs in your
> discussion with Sanjaya), then you do NOT need LOM.
> 	- if you need per-CT-per-Link ratios and want accuracy in how a
> CT affects the global constraints, then you do need LOM.
> 
> So the points I think you're getting at are that:
> 	1) needing per-CT-per-Link ratios does not always mean you need
> LOM
> 	2) from your experience:
> 	- most SPs won't need per-CT-per-link ratios
> 	- the few SPs who may need per-CT-per-link ratios are likely to
> tolerate some inaccuracy in bookeeping over the aggregate constraint,
> Therefore the case for LOM is very slim.
> 
> Right?
> 
> Cheers
> 
> Francois
> 



From owner-te-wg@ops.ietf.org  Thu Jun  5 13:43: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 NAA07636
	for <tewg-archive@lists.ietf.org>; Thu, 5 Jun 2003 13:43:32 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Nyji-0003IT-00
	for te-wg-data@psg.com; Thu, 05 Jun 2003 17:41:14 +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 19Nyjf-0003IH-00
	for te-wg@ops.ietf.org; Thu, 05 Jun 2003 17:41:11 +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 h55GwZo4023395
	for <te-wg@ops.ietf.org>; Thu, 5 Jun 2003 13:41:10 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EDE22A400074816; Thu, 5 Jun 2003 13:41:07 -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: Example of LOM usage
Date: Thu, 5 Jun 2003 12:41:09 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE9C0@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Example of LOM usage
Thread-Index: AcMqrfdjpL+jBSEATm2xZNB2qxNORQAIKE1gACZWkzAABio4AA==
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.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>
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 NAA07636

Francois, All,

> I think there is agreement that the fundamental theoretical reason why,
> ideally, one way want to have different per-CT overbooking ratios on
> different links is because a number of things don't grow linearly (like
> the erlang formula).
> Thanks for giving a quantified example illustrating the distortion.
> 
> But the input I am personally after is: are there service providers out
> there who are likely to be really after that level of 2nd order of
> optimization in the next few years? 

Wai Sum has given a good example of how/why LOM is needed, this is what we all were asking for in support of keeping LOM as is.  You call the effect '2nd order optimization', I don't think so, the differences can easily be above the 'tweaking threshold'.

> My impression is that it is
> interesting enough for an operator to try come up with the right
> formula/heuristics for factoring some LSP size overbooking and some Link
> size overbooking with a single class in regular TE today. When moving to
> DS-TE, operators will have to extend the formulas/heuristics for LSP
> size overbooking on a per-CT basis, so trying to factor it a second
> level of distortion via a per-CT-per-link overbooking tweak seems a far
> stretch in practice. Obviously, I could be wrong. But we still haven't
> heard an operator saying he is likely to be interested in that level of
> optimization for DS-TE.

Yes, you just heard a reasonable example of the need, from a SP who is likely interested in applying LOM as Wai Sum has illustrated.

> This is also discounting Dimitry's point, that operators could even do
> that without LOM anyway if they accepted to tolerate some inaccuracy on
> the aggregate constraint.

I'm a little baffled by this whole discussion.  A reasonable question was asked to provide justification for LOM.  In the ensuing discussion, most agreed that LOM is not complicated, and we have been given some reasonable examples of why/how it would be applied.  I see no reason to 'tolerate inaccuracy' if it is simple to avoid.

We've also agreed to progress LOM, either as is or 'split it off'.  There are still lots of questions surrounding the idea of splitting off LOM into a parallel effort.  Since LOM is already in the Proto spec, that is the easier option.  There does not seem to be a lot of justification now for splitting it off, especially given that its use has been illustrated.  Let's go with leaving it in, as is, and move on.

Also, I would observe that some aspects of the proposed 're-definition' of LOM, as described in http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00321.html, could be done within a given SP network without any changes to Proto or anything else.  All a SP needs to do is set LSPOM=1, LSOM=1.  Then

LOM'c = LSOM * LSPOMc * LOMc = LOMc

This would simplify the use of 3 types of overbooking in a SP network, would allow per-CT overbooking as well as per-link overbooking, and to me is a further justification to retain LOM as is.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue Jun 10 07:56: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 HAA22171
	for <tewg-archive@lists.ietf.org>; Tue, 10 Jun 2003 07:56:54 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19PhgL-0007Uu-00
	for te-wg-data@psg.com; Tue, 10 Jun 2003 11:52:53 +0000
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19PhgJ-0007UB-00
	for te-wg@ops.ietf.org; Tue, 10 Jun 2003 11:52:51 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21737;
	Tue, 10 Jun 2003 07:52:44 -0400 (EDT)
Message-Id: <200306101152.HAA21737@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: mpls@uu.net, ppvpn@nortelnetworks.com, te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mpls-mgmt-overview-06.txt
Date: Tue, 10 Jun 2003 07:52:44 -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-06.txt
	Pages		: 28
	Date		: 2003-6-9
	
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-06.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-06.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-06.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-6-9151134.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Tue Jun 10 09:45: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 JAA29876
	for <tewg-archive@lists.ietf.org>; Tue, 10 Jun 2003 09:45:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19PjOo-000Bze-00
	for te-wg-data@psg.com; Tue, 10 Jun 2003 13:42:54 +0000
Received: from webmail.movaz.com ([65.205.166.188] helo=jera.movaz.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19PjOm-000BzG-00
	for te-wg@ops.ietf.org; Tue, 10 Jun 2003 13:42:52 +0000
Received: from BLIULAPTOP (unknown [172.16.24.104])
	by jera.movaz.com (Postfix) with SMTP
	id 5892F637D; Tue, 10 Jun 2003 09:42:51 -0400 (EDT)
Message-ID: <018701c32f56$2ff23040$681810ac@movaz.com>
From: "Adrian Farrel" <afarrel@movaz.com>
To: <mpls@uu.net>, <ppvpn@nortelnetworks.com>, <te-wg@ops.ietf.org>
References: <200306101152.HAA21737@ietf.org>
Subject: Re: I-D ACTION:draft-ietf-mpls-mgmt-overview-06.txt
Date: Tue, 10 Jun 2003 09:42:51 -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=-21.8 required=5.0
	tests=BAYES_10,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

For those excited readers following this draft...

Version 6 includes updates
- to change all MIB module names to include "-STD" in line with changes to the
MIB documents
- in line with the latest TE-LINK MIB (thanks Martin)

I anticipate another set of changes to pick up the new indexing from the LSR MIB
once the WG has agreed it.

Adrian
----- Original Message -----
From: <Internet-Drafts@ietf.org>
To: <IETF-Announce: ;>
Cc: <mpls@uu.net>; <ppvpn@nortelnetworks.com>; <te-wg@ops.ietf.org>
Sent: Tuesday, June 10, 2003 7:52 AM
Subject: I-D ACTION:draft-ietf-mpls-mgmt-overview-06.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
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mpls-mgmt-overview-06.txt
>






From owner-te-wg@ops.ietf.org  Tue Jun 10 10:26: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 KAA02747
	for <tewg-archive@lists.ietf.org>; Tue, 10 Jun 2003 10:26:44 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Pk3v-000E9V-00
	for te-wg-data@psg.com; Tue, 10 Jun 2003 14:25:23 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Pk3s-000E8j-00
	for te-wg@ops.ietf.org; Tue, 10 Jun 2003 14:25:20 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 10 Jun 2003 16:24:20 +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 h5AENFs3018504;
	Tue, 10 Jun 2003 16:23: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);
	 Tue, 10 Jun 2003 16:24:54 +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: Example of LOM usage
Date: Tue, 10 Jun 2003 15:24:54 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B527E@xbe-lon-313.cisco.com>
Thread-Topic: Example of LOM usage
Thread-Index: AcMqrfdjpL+jBSEATm2xZNB2qxNORQAIKE1gACZWkzAABio4AAD0ebmw
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>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 10 Jun 2003 14:24:54.0763 (UTC) FILETIME=[0FF3ABB0:01C32F5C]
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA02747

Jerry,

<clip>
>> I'm a little baffled by this whole discussion.  A reasonable 
>> question was asked to provide justification for LOM.  In the 
>> ensuing discussion, most agreed that LOM is not complicated, 

I am losing track as to whether LOM is declared complicated or simple ^)

In any case, as mentioned before, the point at stake is not whether it
is inherently simple or complicated. (FWIW my take is that it is pretty
much as simple as could be to do what it has to do). The point at stake
is: does the extra functionality justifies the extensions (like the
extra IGP extensions for example) when we had been designing DSTE very
carefully to minimise IGP impact so far.

>> and we have been given some reasonable examples of why/how 
>> it would be applied. 

So, we've been calling for input on the whole list several times for who
would/may have a practical case for this and all we got is one single
input (which considered potential pros based on Erlang's formula but BTW
did not discuss potential cons on the practical/operational side such as
managing Nb_of_CTs-times-Nb_of_links additional configurable parameters,
additional IGP information). 

Based on this level of input, I wouldn't say that there is a clear
justification for the extra functionality which would justify the
corresponding extensions.

<clip>
>> There are still lots of questions surrounding the 
>> idea of splitting off LOM into a parallel effort.  

I sent a message earlier specifically on this recurring statement.
The proposal is to take the text that is currently in -proto-, -russian
and -mam (and on MAR if you want) on LOM and group that in a separate
document which could then go as Experimental.
It would be the same text.
What exactly are the questions surrounding this idea?

>> Since LOM 
>> is already in the Proto spec, that is the easier option.  
>> There does not seem to be a lot of justification now for 
>> splitting it off, especially given that its use has been 
>> illustrated.  Let's go with leaving it in, as is, and move on.
>> 

To me, and I suspect to the other folks who argued for taking LOM out,
the level of input (or lack of) we got so far is actually indeed
justification for taking it off the main specs. And even, at least to
me, justification to drop it altogether.

So, we really see things differently here. 

Documenting LOM as Experimental is an attempt at a compromised approach
to try move ahead considering this disagreement. It would allow folks
who see it as something worthwhile to have it documented so it can be
experimented with, and even easily added to standards track in some
future if backed by experience. It would allow folks who question the
practical use of LOM to see a leaner DS-TE solution (at least to start
with). 

Assuming we can close-off the potential questions you may have
surrounding the idea of splitting LOM in a separate document, could you
live with this compromised approach of an Experimental track for LOM?

Thanks

Francois



From owner-te-wg@ops.ietf.org  Tue Jun 10 13:24: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 NAA09844
	for <tewg-archive@lists.ietf.org>; Tue, 10 Jun 2003 13:24:00 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Pmnw-000N4T-00
	for te-wg-data@psg.com; Tue, 10 Jun 2003 17:21:04 +0000
Received: from ckmso1.att.com ([12.20.58.69] helo=ckmso1.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Pmnr-000N47-00
	for te-wg@ops.ietf.org; Tue, 10 Jun 2003 17:21:00 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by ckmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h5AGwnXC018670
	for <te-wg@ops.ietf.org>; Tue, 10 Jun 2003 13:20:58 -0400
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3EDE22A400228F69; Tue, 10 Jun 2003 13:20: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: Example of LOM usage
Date: Tue, 10 Jun 2003 12:20:58 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A6821@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Example of LOM usage
Thread-Index: AcMqrfdjpL+jBSEATm2xZNB2qxNORQAIKE1gACZWkzAABio4AAD0ebmwAAfS5lA=
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>,
        "Lai, Wai S (Waisum), ALABS" <wlai@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 NAA09844

Francois,

> Documenting LOM as Experimental is an attempt at a compromised approach
> to try move ahead considering this disagreement. It would allow folks
> who see it as something worthwhile to have it documented so it can be
> experimented with, and even easily added to standards track in some
> future if backed by experience. It would allow folks who question the
> practical use of LOM to see a leaner DS-TE solution (at least to start
> with). 
> 
> Assuming we can close-off the potential questions you may have
> surrounding the idea of splitting LOM in a separate document, could you
> live with this compromised approach of an Experimental track for LOM?

In the interest of moving ahead, I'm OK with the compromise to split off LOM from the Proto and BC drafts, and progress it separately on an Experimental track.  

However, I do not agree that the starting point for the separate effort on LOM should be the current proposal.  While I believe the concept of having a separate per-link, per-CT adjustment for overbooking, such as proposed with LOM, is worth pursuing, I also believe that the particular implementation proposed in Proto is problematic, and needs a re-work.  In particular, 

1. It's not at all clear what 'normalized CTc' really means: it's not reserved BW, it's not overbooked bandwidth, what is it?  It's not a physical quantity, which makes it abstract and confusing.

2. The router reserves Tspec(LSPc) (i.e., reserved(LSPc)=Tspec(LSPc), what does it do with normalized CTc?

3. It's not at all clear what SUM [normalized_CTc] should be constrained by.  Neither Maximum Reservable Bandwidth (MRBW) nor Maximum Link Bandwidth seem correct.

4. It's not at all clear how to set BCc in terms of normalized_CTc, how should that be done, and how do the BCs relate to MRBW?

If you can shed any light on these issues 1 --> 4, with some specific numerical examples, please do.

It is much easier to understand physical quantities like reserved_CTc, what they should sum to (MRBW), how they related to BCs, etc.

I think the concepts proposed in the post on June 1 http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00321.html have merit, and should be considered in the re-initiated effort on LOM.  Wai Sum and I have expanded this proposal in an I-D that we will soon submit for discussion.  The proposed approach is coherent, I believe, while the current approach is not.  I think the I-D with our proposal for LOM should be considered in this effort.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue Jun 10 19:45: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 TAA23033
	for <tewg-archive@lists.ietf.org>; Tue, 10 Jun 2003 19:45:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Pskm-000H6i-00
	for te-wg-data@psg.com; Tue, 10 Jun 2003 23:42:12 +0000
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Pskj-000H6S-00
	for te-wg@ops.ietf.org; Tue, 10 Jun 2003 23:42:09 +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 19Pskh-00019Z-00; Tue, 10 Jun 2003 19:42:07 -0400
From: "sanford goldfless" <sandy9@rcn.com>
To: "'Lai, Wai S \(Waisum\), ALABS'" <wlai@att.com>
Cc: <te-wg@ops.ietf.org>
Subject: RE: Proposal for Simplification of Overbooking
Date: Tue, 10 Jun 2003 19:42:16 -0400
Message-ID: <000001c32fa9$ed3a8640$6401a8c0@DASEP>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0001_01C32F88.6628E640"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
Importance: Normal
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA1370DA@KCCLUST06EVS1.ugd.att.com>
X-MS-TNEF-Correlator: 00000000078B08E293F2CE478794571894738D5D24D12100
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-11.1 required=5.0
	tests=BAYES_30,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

This is a multi-part message in MIME format.

------=_NextPart_000_0001_01C32F88.6628E640
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Wai Sum, Jerry -

I'm a little unclear as to your intention in the "integrated approach."  =
Is it
that the Local Overbooking Multiplier, instead of an independent =
representation
of a CT's overbooking policy (which is what the new term "OB(CTc)" would
signify), will now be rather a kind of correction factor, configured as =
needed
link by link, to other factors which are configured globally?

I think in general this wouldn't be a bad way to get compatibility with =
older TE
procedures. However, I'm still uncomfortable with how even network-wide =
per-CT
policies are supported using Link Size Overbooking.  And the integrated =
approach
appears to build on an understanding of how this is done: "For either =
per-domain
per-CT overbooking or per-link per-CT overbooking, we have Reserved(CTc) =
=3D
Tspec(LSPc) / OB(CTc)" and "OB(CTc) =3D LSOM * LSPOM(CTc) * LOM(CTc)." =20

Specifically, how do you calculate Unreserved (CTc) using "LSPOM" when =
there are
per-CT policies and an aggregate constraint?  I don't see that BCc - =
Reserved
(CTc) / (LSOM * LSPOM) yields an effective value to advertise. After =
all, if CT7
has a policy of no overbooking, even though the link generally is =
allowed to be
overbooked, if BC7 =3D 50 and the CT's  reservation total is 50, then =
Unreserved
(CT7) should be 0.     =20

Thanks for clarifying,=20
Sandy

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


-----Original Message-----
From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]=20
Sent: Tuesday, June 10, 2003 10:53 AM
To: Francois Le Faucheur (flefauch); Choudhury, Sanjaya; Dimitry Haskin; =
sanford
goldfless
Cc: Ash, Gerald R (Jerry), ALABS; Jim Boyle; Ed Kern
Subject: Proposal for Simplification of Overbooking

Attached is an I-D that provides more details on our proposal to =
simplify
overbooking from an operational perspective.  Before posting it, we =
would like
to hear your comments.
Thanks, Wai Sum and Jerry

------=_NextPart_000_0001_01C32F88.6628E640
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Disposition: attachment;
	filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IhEXAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANMHBgAKABMAKgAAAAIAKQEB
A5AGAMwRAAAsAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADAC4AAAAAAAMANgAA
AAAAHgBwAAEAAAArAAAAUHJvcG9zYWwgZm9yIFNpbXBsaWZpY2F0aW9uIG9mIE92ZXJib29raW5n
AAACAXEAAQAAABYAAAABwy+podi8KdRwbFlFZ7VBpJXxRr/jAAACAR0MAQAAABQAAABTTVRQOlNB
TkRZOUBSQ04uQ09NAAsAAQ4AAAAAQAAGDgAU8uKpL8MBAgEKDgEAAAAYAAAAAAAAAAeLCOKT8s5H
h5RXGJRzjV3CgAAAAwAUDgAAAAALAB8OAQAAAB4AKA4BAAAAJAAAADAwMDAwMDAzAXNhbmR5OUBy
Y24uY29tAXBvcC5yY24uY29tAB4AKQ4BAAAAJAAAADAwMDAwMDAzAXNhbmR5OUByY24uY29tAXBv
cC5yY24uY29tAAIBCRABAAAAwgwAAL4MAACdGAAATFpGdSlJuJkDAAoAcmNwZzEyNRoyDGBjAFAB
BHN0c+JoBXBiY2gO9QkAD4dmaA3gD5ZiaQFDC2BukQ4QMDMzEaZmZRIiPwH3AqQDYwIAD4AKwHNl
QnQC0XBycTIAACrJCqFubxTgIDAB0AHQwjYSMDA1MDQWsQHQ+RagNH0HbQKDDlAEVRSN6jEVjDcW
kTkWMxcCFuBPF2AIVQeyAoMzNhQeMhQzOBUkIAdtIENFPR0ENx1/FtAerx+1eXLlHQQ5FB4xNgBQ
Ie8Dc7pHCdFrAoMW4CPvNhjBeyU/A4JUCHAm1CUBJA03hyCRKJ8DgihIZWIJcPx3KSbUGMEqrh6f
LLYHEN8BoA3gLZUSUCdeOB1hL2/1A4JCB0B0DeAm1CHBJA4XMZEy/yzjVgiQdG5hdQeBZS2UNR1h
GP0edjH3IAAcaCAGNSCROQ4htTp9/SNVNSPRGP0k5jp8JogWgP8+/yhGOnwp5iTyQk4rlTp8/y0r
KFJFXzofR3IwyjYiQk73MrU6fDRJNiHBQk82NEbNVzfLApEI5jsJbzBTP2X9DjA1VGpVgVU/VklU
VFZyf1TfWK9YbVfvVh9UbxLwMv44XjpfUV8PYBlUVGBCXq/fYn9iPWG/X+9jtDkOUGcEn2hhYINo
YAKCDxB5bAeQqmgJ4HQAAHEDIWwRgYcFEAFAA/BkY3RsCrE9AGBzCrBroBSwa+JudYJtAgBhYXV0
bwBgGGRqdQ8QBRBnaHQvawEKAWrQCgFpAZBwMP0DsjIhwBHnEqgI0AnAa2A5b3NucG/JcWQDMHNu
/GV4FQAHsAWwAMACcxWgXGNzEiADMG1gZG7Aac52FhAPABTgbWkQwHRQOQnwIEQBEG0QNGAgUI0K
wGEJwG7gaCBGAiG7c4QPIDEAUA8gA2B3CzATbbABgHNXa2B0aELvElBtsAqwdFBsEiAvMHj0vnJ5
aBAAeNYBgHrXYnrXxnJ40QTwZWxsa1F4oP94QQFADyB0oAAgNFF3US1Q/3nwflYJUH50DLF+g2vQ
fnRcZGd/VoDQgFZofmV2/wMwap9rr2y/bc9u14aBEfP/b1US4m9RcMyIF4mUcpV3gL90zHMkNqAB
oGoAc4c1dCrvdeAI0BiwcpFihCAJgAIgD3QCadEU0IOQNzQ3NuMWgIqwSHlwBJBucSbD/XPDNo2f
DiCOv4/KdsB9EP934AmAkItz8CCQgs+D34Tv/4X/btVIgYd4b+9w/3IKkxXrk5KK8zeTr1ALYjag
ctF9c4c4dCuTGnT5DwCQoXPPAiCMcQ8ABaBtcBXyj4ZmNjjAkAAgRQDAAxBTX2niMqBSYxWgU1B2
AlEg7HtVkPAV4HcYYXOTDgD/BTCn4qjyDECpAW6llnd+gPkO8WEwp0WP0afSq9OmE+er0x5wG3A1
NCPQj8IXQa+NcBbAq9MW4DdXADMAUPeukxaAFrA4rnSQBavTEiB8NjkSIKzld4CvEFcAOeNdoLDT
MjE0r+BvUbJ0/xJAshCzF6YRd4CudLRRAcCqNK/QfQCxcoDgMa8g/yPQtcJ6ALYhAzCXAXfglzDj
f0EBgG5iagBgCfB0UDUQIFwV4HgLYAJAb3n1CfBcctBwDzAAIAuQFeB/deF/QJewAOECMAJgAIBi
3w9guIGXsXzwAhByjlG7sUZtDzCZEGVcaAWwet+4UoDQtcILgYDQaLtjDiD5AUFndr30r+G9wQWw
mYA7C4ArgDAOkb6Qv3U5OHchwL3CvLB3DlC+gsFDan+5UQBwCzC4UWngkKAOUHbpCJB3awuAZF2g
wzIE8N8HQBLxAUAOAIHTZZkQxJWNAhBvmbCXsGx5dKhw/wuAvJC3scYnmaAAwJjQl7D/uIG60Jmg
mREJMplAfQACUP8HQAuQyTECUcOBlnDGMMQh/5cwAmB38cYhAlEAIIGButC9LVBru9G8kBXgy7F3
eQD/CTJysG7gmOCcsguAfPLJYdWU4WYIkGx1YWTI4Zbw+XkAcHXNoJmwl6AHMMun/4/CA2DF0K7V
AzEU8hTglzD+ZJZicsEBQLghyDAEkLyQv9HS0kKcsh1Q0bV1tGPM0fvR4bAac7ezqWEVoQCABZD8
bHZ5UNbBDnBzQNbCAZDvACDXUsOBCfB0AcHWwRSwjxIAqWICMHLgYSAuqKX/1uUOUNdyuhHX39jv
2f/XMP8SUJhQBYHbv9zP3d/XMCHA35hQymDbj+Bf4WUp2kxdoPffL+Qf4UViLRACkeVP1wP/HWDi
7+e/6M/p39chIJDrMv/Xv+yf7a/lvS8w6z/wz/Hf//Lv1yEj0O/P9W/2f/eFCvn/cpGWH5cvmD+Z
T6oWCrEUwf+P6Jrfm++c/3ImCMET8aDwS3fApedXC3AgU/+wLIQgShkgcnkgLQqF4QqFSSdtIOGw
/cDLAL1qACDPUWoACTH+4CAAIFQgeRxhIKDwdPohac8TcAvBC0BqMCAiC9J2YS8L8NIQmpAVQG++
EGgu/CIgCcAv8JpwDJG40AyT1kzCsIxxT33xYsXAw3H94SBNdeGp0P3AGSAIYAch4wvwAFAgb2YK
AAxSdWD7kKD6AyBTUBVAODH74LjQpwwyEbIgAFQnL/BvD8nLpUD9wGMIwCh3dTAZcP8LwC/wFaAO
5XLARHAL8HNAcQzQT0IoFBAxEA4wdw+58dIQz7AFcGlmeSmfCGD+QH0QFrDBUCBiGuD/DUHS8QoB
UoIG/sNyEaIaT/+mQaUQgEDR4Qwy/+D+cL9w6whgpRBuzlBnKfANci/w/3LAU2ANcZDSGXAIwJDS
CGD/C1HF0BniHfQWEhXC/rAPMM8eeYDgzEDOAXk/CP0Mkfsf0qDxZ1PQP0CMcSSRFhH5GAJuJ3YA
GYHhsMkg0hD8d2EIwAtRJSB2AKUSE2H/MPAKMQjA/kB4oBGgzoFKoFxURRUQNTB88GQe0XP+LpBw
lPF98QhgCdJp0BkCf89RNUC7schQjMEolMFBIJ8qcf0QcsDGQL9way3+QfsPMJChLRQQFRQ30C/w
IhJ8c3XPMFLhDXHI0BAyTHEf0lNpeg8wD7kqICD+QRuhDKIM/yHizzAK4Qsz/GJ1pqARkf0QEeHP
UD8x//lhuDAQMhGxLKIloxYBk1HcZToM0HbASqBlKLEZ8f8uApNQpoH9EC4FFGo3QS4Cex/DOJ9n
GNEPMD+gdKFSz1IhgoBTYBeDID2MkKRRoGMoTFNQPPEvD6AfF3bCYRdHPRE9oE9NIPoqP5FQP8A8
xD/xQEUOIv0I/FM9YRiQS1AjQghgLKK/k1ALch0wylF14A1RIKgg3xMCPIJHkDzTL+QiQBMX0f9q
MAyDIiEiEi4PG6ER4XZQPWRBZ0RyHnEAkaDhdD8/DkE2siZRpWAPMA7DQkP+YwjQPDdFVT4APZE/
yD0A7nnOYkhyLNBmiIAdkXShfnbKUFQwC0IAUH3yFgBl/SogQdYwGfJ9EBEREcA40P+foEtALuEV
FhPBu0A67Czj/3igufAA0AyTH8MlJcYgFfL/zgMNcTQCDzAUZl5gUPNLgP+foD+ArmA+owyiFBMS
wTxi/xNkACB+IRXyrmAggUayRLzeNz0AwTEYEhmBMDGRXJL1CPxU4PFrLuC7sR0wh7DfALAYoDtz
QhbCYXkI/BwF/4e/b1G7QA3BE8AHG3PQS0DHgECP2ajCYmttXhD5cmggX02mkUEAETCQZ+59X7G7
sdIQRyjxerATEH5zCPVpYXawdeBqAEJhdLUI9ULQsWvSQhBgQVxgD29Qr5AI9bSQNy03M3w4LZ+Q
rZAI9atQX9E54EByY24upRFgDxw+X2PfZOa4IWW8CPUtchJP27+DjHFNZ3F2UGVyE9Iz63aw0LBt
NwBMoOAIYAfzFxWAB/EvQG0YwUFMQZpCdQBbpoIAIDp3oNH2QLjRbLJd0iQIIPohNwDyVE9Qc2Qn
IAhhz1APMN8D4F8gvlAD8HkROtEwMbD6TXO0VHaAdAHP0KUQFgGuTHPxAAAOAGULoShnUUPUoQ4A
KVwnM/bwQ7lT4WRoHtBDMV+xaicgc/9QfNJEaYugAKAIwEjf/uDDcXzDbBFmw2dnJnO020uQNwBB
wTBfIEclUtIQ3lIVgAiDdZZ8w0p+kEtw17kAzAF80kXSEEsIkMlQ3XeUdbfg0eE3AFDQsKVB/4xx
XkIwkCfg/cBC0hN2D7l9CPxBywAN8Q1xVXL9EEl8LUQOtA3BwzCkAC7gbf+/cA8wpADIUKagFEET
oQuhfw3BheQLUc+whqNSMQ/JZv90IRHSYqAlUQwipMGkYj1h+5ISMZFCu6JHcaVQKyDhEf+acDuj
F/T9wFbwC0LFAUJg+wuDpRFt+iEqEF1rdKX/sCc+owiDYHZ9AJbAAAAeAEIQAQAAAEMAAAA8N0FG
RTQwRUYzMEVFNzU0REE5NjdEMUI1OTY4NDU3Q0ExMzcwREFAS0NDTFVTVDA2RVZTMS51Z2QuYXR0
LmNvbT4AAAMAkhADAAAAAwDeP59OAAADAAlZAwAAAAMAQGUAAAAACwAWgAggBgAAAAAAwAAAAAAA
AEYAAAAAA4UAAAAAAAADABiACCAGAAAAAADAAAAAAAAARgAAAAAQhQAAAAAAAAMAHoAIIAYAAAAA
AMAAAAAAAABGAAAAAFKFAABZlAEAAwApgAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAABAACqA
CCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAAeAEGACCAGAAAAAADAAAAAAAAARgAAAABU
hQAAAQAAAAUAAAAxMC4wAAAAAAsAQoAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAACwBGgAgg
BgAAAAAAwAAAAAAAAEYAAAAADoUAAAAAAAADAEmACCAGAAAAAADAAAAAAAAARgAAAAAYhQAAAAAA
AAsAXoAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAAAAAAAAgH4DwEAAAAQAAAAB4sI4pPyzkeHlFcY
lHONXQIB+g8BAAAAEAAAAAeLCOKT8s5Hh5RXGJRzjV0CAfsPAQAAAJ8AAAAAAAAAOKG7EAXlEBqh
uwgAKypWwgAAbXNwc3QuZGxsAAAAAABOSVRB+b+4AQCqADfZbgAAAEM6XERvY3VtZW50cyBhbmQg
U2V0dGluZ3NcZWlsZWVuIGdvbGRmbGVzc1xMb2NhbCBTZXR0aW5nc1xBcHBsaWNhdGlvbiBEYXRh
XE1pY3Jvc29mdFxPdXRsb29rXE91dGxvb2syLnBzdAAAAwD+DwUAAAADAA00/TcCAAIBFDQBAAAA
EAAAAE5JVEH5v7gBAKoAN9luAAACAX8AAQAAADEAAAAwMDAwMDAwMDA3OEIwOEUyOTNGMkNFNDc4
Nzk0NTcxODk0NzM4RDVEMjREMTIxMDAAAAAAAwAGEAo8KvUDAAcQKgYAAAMAEBAAAAAAAwAREAAA
AAAeAAgQAQAAAGUAAABXQUlTVU0sSkVSUlktSU1BTElUVExFVU5DTEVBUkFTVE9ZT1VSSU5URU5U
SU9OSU5USEUiSU5URUdSQVRFREFQUFJPQUNIIklTSVRUSEFUVEhFTE9DQUxPVkVSQk9PS0lOR01V
AAAAADRg

------=_NextPart_000_0001_01C32F88.6628E640--





From owner-te-wg@ops.ietf.org  Wed Jun 11 05:30: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 FAA00432
	for <tewg-archive@lists.ietf.org>; Wed, 11 Jun 2003 05:30:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Q1t1-000J9U-00
	for te-wg-data@psg.com; Wed, 11 Jun 2003 09:27:19 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19Q1sx-000J99-00
	for te-wg@ops.ietf.org; Wed, 11 Jun 2003 09:27:16 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 11 Jun 2003 11:26:15 +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 h5B9P25G024567;
	Wed, 11 Jun 2003 11:25:14 +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, 11 Jun 2003 11:27:10 +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: Example of LOM usage
Date: Wed, 11 Jun 2003 10:27:09 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B5285@xbe-lon-313.cisco.com>
Thread-Topic: Example of LOM usage
Thread-Index: AcMqrfdjpL+jBSEATm2xZNB2qxNORQAIKE1gACZWkzAABio4AAD0ebmwAAfS5lAAIXvgAA==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 11 Jun 2003 09:27:10.0299 (UTC) FILETIME=[A2508AB0:01C32FFB]
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA00432

Hello Jerry,

>> In the interest of moving ahead, I'm OK with the compromise 
>> to split off LOM from the Proto and BC drafts, and progress 
>> it separately on an Experimental track.  
>> 

So we'll update asap the -proto, -russian and -mam drafts:
	- (i) removing all the LOM staff and 
	- (ii) reflecting our agreement regarding the use of Max
Reservable Bandwidth

>> However, I do not agree that the starting point for the 
>> separate effort on LOM should be the current proposal.  
>> While I believe the concept of having a separate per-link, 
>> per-CT adjustment for overbooking, such as proposed with 
>> LOM, is worth pursuing, I also believe that the particular 
>> implementation proposed in Proto is problematic, and needs a 
>> re-work.  In particular, 
>> 
>> 1. It's not at all clear what 'normalized CTc' really means: 
>> it's not reserved BW, it's not overbooked bandwidth, what is 
>> it?  It's not a physical quantity, which makes it abstract 
>> and confusing.
>> 
>> 2. The router reserves Tspec(LSPc) (i.e., 
>> reserved(LSPc)=Tspec(LSPc), what does it do with normalized CTc?
>> 
>> 3. It's not at all clear what SUM [normalized_CTc] should be 
>> constrained by.  Neither Maximum Reservable Bandwidth (MRBW) 
>> nor Maximum Link Bandwidth seem correct.
>> 
>> 4. It's not at all clear how to set BCc in terms of 
>> normalized_CTc, how should that be done, and how do the BCs 
>> relate to MRBW?
>> 
>> If you can shed any light on these issues 1 --> 4, with some 
>> specific numerical examples, please do.
>> 
>> It is much easier to understand physical quantities like 
>> reserved_CTc, what they should sum to (MRBW), how they 
>> related to BCs, etc.
>> 
>> I think the concepts proposed in the post on June 1 
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00321.html 
>> have merit, and should be considered in the re-initiated effort 
>> on LOM.  Wai Sum and I have expanded this proposal in an I-D that 
>> we will soon submit for discussion.  The proposed approach is
coherent, 
>>I believe, while the current approach is not.  I think the I-D with
our 
>> proposal for LOM should be considered in this effort.

Since it no longer impacts progress of the base DS-TE specs, I don't see
a major issue in reopening the discussion on what is the best LOM
solution, and in your proposal being considered.

I think the current LOM solution which we've had stable for a long time
in our Working Group documents is the most natural starting point until
it is actually shown "problematic" and that another proposal is
superior. So let's have the discussion first on the LOM approaches
before switching to a new proposal.

In the very short term, I'd like to focus on issuing the base specs. So
I'll get back to your points above re current LOM approach a little
later and will also look into your proposal in more details then.

Thanks

FRancois



From owner-te-wg@ops.ietf.org  Wed Jun 11 09:26: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 JAA08055
	for <tewg-archive@lists.ietf.org>; Wed, 11 Jun 2003 09:26:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19Q5Uj-0000tS-00
	for te-wg-data@psg.com; Wed, 11 Jun 2003 13:18:29 +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 19Q5Uf-0000t8-00
	for te-wg@ops.ietf.org; Wed, 11 Jun 2003 13:18:25 +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 h5BDFIix002475
	for <te-wg@ops.ietf.org>; Wed, 11 Jun 2003 09:18:22 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3EDE22A400280FBF for te-wg@ops.ietf.org; Wed, 11 Jun 2003 09:18:21 -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: Proposal for Simplification of Overbooking
Date: Wed, 11 Jun 2003 08:18:23 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BE9E6@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Proposal for Simplification of Overbooking
Thread-Index: AcMvqaHYvCnUcGxZRWe1QaSV8Ua/4wAbBHBAAADhfhA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "sanford goldfless" <sandy9@rcn.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>, <te-wg@ops.ietf.org>
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 JAA08055

Sandy,

> I'm a little unclear as to your intention in the "integrated 
> approach."  Is it that the Local Overbooking Multiplier, 
> instead of an independent representation of a CT's 
> overbooking policy (which is what the new term "OB(CTc)" 
> would signify), will now be rather a kind of correction 
> factor, configured as needed link by link, to other factors 
> which are configured globally?

Yes, the proposed OB(CTc) would be configured by link, by CT, just as in the current proposal for LOM(CTc).  However, OB(CTc) is meant to combine, functionally:

LSPOMc = LSP overbooking multiplier for CTc
LSOM = link size overbooking multiplier for a given link
LOMc = local overbooking multiplier, currently proposed per-link, per-CT adjustment factor

In our draft we propose:

OBc = LSPOMc * LSOM * LOMc

> I think in general this wouldn't be a bad way to get 
> compatibility with older TE procedures. However, I'm still 
> uncomfortable with how even network-wide per-CT policies are 
> supported using Link Size Overbooking.  And the integrated 
> approach appears to build on an understanding of how this is 
> done: "For either per-domain per-CT overbooking or per-link 
> per-CT overbooking, we have Reserved(CTc) = Tspec(LSPc) / 
> OB(CTc)" and "OB(CTc) = LSOM * LSPOM(CTc) * LOM(CTc)."  
> 
> Specifically, how do you calculate Unreserved (CTc) using 
> "LSPOM" when there are per-CT policies and an aggregate 
> constraint?  I don't see that BCc - Reserved (CTc) / (LSOM * 
> LSPOM) yields an effective value to advertise. After all, if 
> CT7 has a policy of no overbooking, even though the link 
> generally is allowed to be overbooked, if BC7 = 50 and the 
> CT's  reservation total is 50, then Unreserved (CT7) should 
> be 0.

I don't understand your example, I think we need a more detailed example.  

Let me try to create an example, and compare today's method of overbooking (Case A) and the proposed method of overbooking (Case B):

Take a link with:

Max link bandwidth = 100
Max reservable bandwidth = 200
(that is, in today's parlance, LSOM = 200/100 = 2, the link bandwidth is overbooked by a factor of 2)
BC0 = 50
BC1 = 150
LSPOB0 = 1
LSPOB1 = 4
(that is, in today's parlance, CT0 is not overbooked, CT1 is overbooked by a factor of 4)
LOM0 = 1
LOM1 = 1
(that is, in today's parlance, no per-link/per-CT overbooking adjustment is made for either CT0 or CT1 using LOM)

Suppose we have 2 LSPs set up over this link:
LSP0 requested bandwidth = 30
LSP1 requested bandwidth = 80

Case A: today's way of applying overbooking factors:
----------------------------------------------------

Tspec(LSP0) = LSP0 requested bandwidth/LSPOB0 = 30/1 = 30
Tspec(LSP1) = LSP1 requested bandwidth/LSPOB1 = 80/4 = 20

Reserved(LSP0) = Tspec(LSP0) = 30
Reserved(LSP1) = Tspec(LSP1) = 20

Then

Unreserved(CT0) = BC0 - Reserved(CT0) = 50 - 30 = 20
Unreserved(CT1) = BC1 - Reserved(CT1) = 150 - 20 = 130

These quantities are advertised.


Case B: the proposed modified way of applying overbooking factors:
------------------------------------------------------------------

First we adjust the BC0 and BC1 by the LSOM for this link:

BC0 = 50/2 = 25
BC1 = 150/2 = 75
(note that the proposed method uses Max link bandwidth as the aggregate constraint)

Then we determine the OB0 and OB1 factors:

OB0 = LSPOB0 * LSOM * LOM0 = 1 * 2 * 1 = 2
OB1 = LSPOB1 * LSOM * LOM1 = 4 * 2 * 1 = 8

Tspec(LSP0) = LSP0 requested bandwidth = 30
Tspec(LSP1) = LSP1 requested bandwidth = 80

Reserved(LSP0) = Tspec(LSP0)/OB0 = 30/2 = 15
Reserved(LSP1) = Tspec(LSP1)/OB1 = 80/8 = 10

Then

Unreserved(CT0) = BC0 - Reserved(CT0) = 25 - 15 = 10
Unreserved(CT1) = BC1 - Reserved(CT1) = 75 - 10 = 65

These quantities are advertised.

I hope this further clarifies the proposal.  Perhaps you can ask your question in terms of specifics in the above example.

Thanks,
Jerry




From owner-te-wg@ops.ietf.org  Wed Jun 11 18:24: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 SAA07047
	for <tewg-archive@lists.ietf.org>; Wed, 11 Jun 2003 18:24:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19QDyB-000Nle-00
	for te-wg-data@psg.com; Wed, 11 Jun 2003 22:21:27 +0000
Received: from smtp02.mrf.mail.rcn.net ([207.172.4.61])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19QDy5-000NlO-00
	for te-wg@ops.ietf.org; Wed, 11 Jun 2003 22:21:21 +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 19QDy5-0002mY-00; Wed, 11 Jun 2003 18:21:21 -0400
From: "sanford goldfless" <sandy9@rcn.com>
To: "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>
Cc: "'Lai, Wai S \(Waisum\), ALABS'" <wlai@att.com>, <te-wg@ops.ietf.org>
Subject: RE: Proposal for Simplification of Overbooking
Date: Wed, 11 Jun 2003 18:21:26 -0400
Message-ID: <000001c33067$cc50adb0$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: <9473683187ADC049A855ED2DA739ABCA011BE9E6@KCCLUST06EVS1.ugd.att.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-19.3 required=5.0
	tests=BAYES_01,IN_REP_TO,ORIGINAL_MESSAGE,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: 7bit

Jerry,	

Thanks for the example.  I see now that a key point in your proposal is
the treatment of the BCs: they will be reduced by the link overbooking
factor. 

Together with the combined normalizing factor applied to reservations,
this seems to allow a single calculation for Unreserved, against both
the aggregate and the per-CT constraint at the same time. Nice.

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 Ash, Gerald R (Jerry), ALABS
Sent: Wednesday, June 11, 2003 9:18 AM
To: sanford goldfless
Cc: Ash, Gerald R (Jerry), ALABS; Lai, Wai S (Waisum), ALABS;
te-wg@ops.ietf.org
Subject: RE: Proposal for Simplification of Overbooking

Sandy,

> I'm a little unclear as to your intention in the "integrated 
> approach."  Is it that the Local Overbooking Multiplier, 
> instead of an independent representation of a CT's 
> overbooking policy (which is what the new term "OB(CTc)" 
> would signify), will now be rather a kind of correction 
> factor, configured as needed link by link, to other factors 
> which are configured globally?

Yes, the proposed OB(CTc) would be configured by link, by CT, just as in
the current proposal for LOM(CTc).  However, OB(CTc) is meant to
combine, functionally:

LSPOMc = LSP overbooking multiplier for CTc
LSOM = link size overbooking multiplier for a given link
LOMc = local overbooking multiplier, currently proposed per-link, per-CT
adjustment factor

In our draft we propose:

OBc = LSPOMc * LSOM * LOMc

> I think in general this wouldn't be a bad way to get 
> compatibility with older TE procedures. However, I'm still 
> uncomfortable with how even network-wide per-CT policies are 
> supported using Link Size Overbooking.  And the integrated 
> approach appears to build on an understanding of how this is 
> done: "For either per-domain per-CT overbooking or per-link 
> per-CT overbooking, we have Reserved(CTc) = Tspec(LSPc) / 
> OB(CTc)" and "OB(CTc) = LSOM * LSPOM(CTc) * LOM(CTc)."  
> 
> Specifically, how do you calculate Unreserved (CTc) using 
> "LSPOM" when there are per-CT policies and an aggregate 
> constraint?  I don't see that BCc - Reserved (CTc) / (LSOM * 
> LSPOM) yields an effective value to advertise. After all, if 
> CT7 has a policy of no overbooking, even though the link 
> generally is allowed to be overbooked, if BC7 = 50 and the 
> CT's  reservation total is 50, then Unreserved (CT7) should 
> be 0.

I don't understand your example, I think we need a more detailed
example.  

Let me try to create an example, and compare today's method of
overbooking (Case A) and the proposed method of overbooking (Case B):

Take a link with:

Max link bandwidth = 100
Max reservable bandwidth = 200
(that is, in today's parlance, LSOM = 200/100 = 2, the link bandwidth is
overbooked by a factor of 2)
BC0 = 50
BC1 = 150
LSPOB0 = 1
LSPOB1 = 4
(that is, in today's parlance, CT0 is not overbooked, CT1 is overbooked
by a factor of 4)
LOM0 = 1
LOM1 = 1
(that is, in today's parlance, no per-link/per-CT overbooking adjustment
is made for either CT0 or CT1 using LOM)

Suppose we have 2 LSPs set up over this link:
LSP0 requested bandwidth = 30
LSP1 requested bandwidth = 80

Case A: today's way of applying overbooking factors:
----------------------------------------------------

Tspec(LSP0) = LSP0 requested bandwidth/LSPOB0 = 30/1 = 30
Tspec(LSP1) = LSP1 requested bandwidth/LSPOB1 = 80/4 = 20

Reserved(LSP0) = Tspec(LSP0) = 30
Reserved(LSP1) = Tspec(LSP1) = 20

Then

Unreserved(CT0) = BC0 - Reserved(CT0) = 50 - 30 = 20
Unreserved(CT1) = BC1 - Reserved(CT1) = 150 - 20 = 130

These quantities are advertised.


Case B: the proposed modified way of applying overbooking factors:
------------------------------------------------------------------

First we adjust the BC0 and BC1 by the LSOM for this link:

BC0 = 50/2 = 25
BC1 = 150/2 = 75
(note that the proposed method uses Max link bandwidth as the aggregate
constraint)

Then we determine the OB0 and OB1 factors:

OB0 = LSPOB0 * LSOM * LOM0 = 1 * 2 * 1 = 2
OB1 = LSPOB1 * LSOM * LOM1 = 4 * 2 * 1 = 8

Tspec(LSP0) = LSP0 requested bandwidth = 30
Tspec(LSP1) = LSP1 requested bandwidth = 80

Reserved(LSP0) = Tspec(LSP0)/OB0 = 30/2 = 15
Reserved(LSP1) = Tspec(LSP1)/OB1 = 80/8 = 10

Then

Unreserved(CT0) = BC0 - Reserved(CT0) = 25 - 15 = 10
Unreserved(CT1) = BC1 - Reserved(CT1) = 75 - 10 = 65

These quantities are advertised.

I hope this further clarifies the proposal.  Perhaps you can ask your
question in terms of specifics in the above example.

Thanks,
Jerry







From owner-te-wg@ops.ietf.org  Wed Jun 18 07:59: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 HAA28820
	for <tewg-archive@lists.ietf.org>; Wed, 18 Jun 2003 07:59:31 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19SbV7-0003hX-DK
	for te-wg-data@psg.com; Wed, 18 Jun 2003 11:53:17 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19SbV4-0003hK-Nv
	for te-wg@ops.ietf.org; Wed, 18 Jun 2003 11:53:14 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28169;
	Wed, 18 Jun 2003 07:53:13 -0400 (EDT)
Message-Id: <200306181153.HAA28169@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-diff-te-russian-03.txt
Date: Wed, 18 Jun 2003 07:53:13 -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		: Russian Dolls Bandwidth Constraints Model for 
                          Diff-Serv-aware MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur
	Filename	: draft-ietf-tewg-diff-te-russian-03.txt
	Pages		: 10
	Date		: 2003-6-17
	
This document provides specification for one Bandwidth Constraints 
model for Diff-Serv-aware MPLS Traffic Engineering, which is referred 
to as the Russian Dolls Model.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-03.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-diff-te-russian-03.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-diff-te-russian-03.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-6-17144524.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-russian-03.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Jun 18 08:00: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 IAA28854
	for <tewg-archive@lists.ietf.org>; Wed, 18 Jun 2003 08:00:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19SbV3-0003hH-02
	for te-wg-data@psg.com; Wed, 18 Jun 2003 11:53:13 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19SbUz-0003h2-PZ
	for te-wg@ops.ietf.org; Wed, 18 Jun 2003 11:53:09 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28147;
	Wed, 18 Jun 2003 07:53:08 -0400 (EDT)
Message-Id: <200306181153.HAA28147@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-diff-te-proto-04.txt
Date: Wed, 18 Jun 2003 07:53:08 -0400
X-Spam-Status: No, hits=-2.7 required=5.0
	tests=BAYES_10,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		: Protocol extensions for support of Diff-Serv-aware 
                          MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur
	Filename	: draft-ietf-tewg-diff-te-proto-04.txt
	Pages		: 25
	Date		: 2003-6-17
	
This document specifies the IGP and RSVP-TE signaling extensions 
(beyond those already specified for existing MPLS Traffic 
Engineering) for support of Diff-Serv-aware MPLS Traffic Engineering 
(DS-TE). These extensions address the Requirements for DS-TE spelt 
out in [DSTE-REQ].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-04.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-diff-te-proto-04.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-diff-te-proto-04.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-6-17144512.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-proto-04.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Tue Jun 24 06:42: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 GAA10347
	for <tewg-archive@lists.ietf.org>; Tue, 24 Jun 2003 06:42:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19UlAi-0007pe-1l
	for te-wg-data@psg.com; Tue, 24 Jun 2003 10:37:08 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19UlAc-0007p5-Ud; Tue, 24 Jun 2003 10:37:03 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10081;
	Tue, 24 Jun 2003 06:36:44 -0400 (EDT)
Message-Id: <200306241036.GAA10081@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
CC: ccamp@ops.ietf.org, te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ayyangar-inter-region-te-00.txt
Date: Tue, 24 Jun 2003 06:36:44 -0400
X-Spam-Status: No, hits=3.1 required=5.0
	tests=MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Level: ***
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.


	Title		: Inter-region MPLS Traffic Engineering
	Author(s)	: A. Ayyangar, J. Vasseur
	Filename	: draft-ayyangar-inter-region-te-00.txt
	Pages		: 20
	Date		: 2003-6-23
	
This draft proposes mechanisms for the establishment and maintenance of
MPLS Traffic Engineering (TE) Label Switched Paths (LSP) that traverse
multiple regions, where a region could be an IGP Area or an Autonomous
System or a GMPLS overlay network. This document also outlines different
mechanisms that an operator could employ within his region to facilitate
the setup of these inter-region TE LSPs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ayyangar-inter-region-te-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-ayyangar-inter-region-te-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-ayyangar-inter-region-te-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-6-23142125.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ayyangar-inter-region-te-00.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Thu Jun 26 08:14:46 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17511
	for <tewg-archive@lists.ietf.org>; Thu, 26 Jun 2003 08:14:46 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19VVWa-0009pr-SQ
	for te-wg-data@psg.com; Thu, 26 Jun 2003 12:06:48 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19VVWQ-0009pH-4q
	for te-wg@ops.ietf.org; Thu, 26 Jun 2003 12:06:38 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17000;
	Thu, 26 Jun 2003 08:05:40 -0400 (EDT)
Message-Id: <200306261205.IAA17000@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-diff-te-mam-00.txt
Date: Thu, 26 Jun 2003 08:05:24 -0400
X-Spam-Status: No, hits=1.5 required=5.0
	tests=BAYES_30,MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Level: *
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		: Maximum Allocation Bandwidth Constraints Model for   
                          Diff-Serv-aware MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur, W. Lai
	Filename	: draft-ietf-tewg-diff-te-mam-00.txt
	Pages		: 9
	Date		: 2003-6-25
	
This document provides specification for one Bandwidth Constraints 
model for Diff-Serv-aware MPLS Traffic Engineering, which is referred 
to as the Maximum Allocation Model.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mam-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-diff-te-mam-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-diff-te-mam-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-6-26080628.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-mam-00.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Thu Jun 26 11:17: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 LAA01263
	for <tewg-archive@lists.ietf.org>; Thu, 26 Jun 2003 11:17:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19VYPG-000IIR-MR
	for te-wg-data@psg.com; Thu, 26 Jun 2003 15:11:26 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19VYPD-000IGe-RI
	for te-wg@ops.ietf.org; Thu, 26 Jun 2003 15:11:23 +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 h5QFApqG005920
	for <te-wg@ops.ietf.org>; Thu, 26 Jun 2003 11:10:51 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h5QFApSN005916
	for <te-wg@ops.ietf.org>; Thu, 26 Jun 2003 11:10:51 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Thu, 26 Jun 2003 11:10:51 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: New I-D on inter-area (and inter-as) MPLS TE requirements
Message-ID: <Pine.LNX.4.44.0306261103470.5754-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-13.7 required=5.0
	tests=BAYES_01,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


This was written in about an hour, late the night before the deadline
(so show some mercy :)

draft-boyle-tewg-interarea-reqts-00.txt

The goal was to make sure that we cover requirements for inter-area TE.
To show that it's not that hard to couple in the requirements for inter-as
TE, I extended it to cover that as well.

regards,

Jim





From owner-te-wg@ops.ietf.org  Thu Jun 26 12:32:18 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07747
	for <tewg-archive@lists.ietf.org>; Thu, 26 Jun 2003 12:32:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19VZ7l-000Kgh-2U
	for te-wg-data@psg.com; Thu, 26 Jun 2003 15:57:25 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19VZ7h-000KeP-JH
	for te-wg@ops.ietf.org; Thu, 26 Jun 2003 15:57:21 +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 h5QFuQqG006014;
	Thu, 26 Jun 2003 11:56:26 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h5QFuQlj006010;
	Thu, 26 Jun 2003 11:56:26 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Thu, 26 Jun 2003 11:56:26 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
cc: msiva@cisco.com, <flefauch@cisco.com>, <raymond_zhang@infonet.com>
Subject: DSTE and link-bundling clarifications needed?
Message-ID: <Pine.LNX.4.44.0306261153540.5754-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-13.7 required=5.0
	tests=BAYES_01,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


In regards to draft-sivabalan-diff-te-bundling-02.txt,
it seems to state a lot of the obvious.

Are these clarifications substantial enough to justify an RFC?

Is it the author's intent that this would be informational?

thanks,

Jim





From owner-te-wg@ops.ietf.org  Fri Jun 27 19:37: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 TAA26262
	for <tewg-archive@lists.ietf.org>; Fri, 27 Jun 2003 19:37:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19W2eV-000DYl-55
	for te-wg-data@psg.com; Fri, 27 Jun 2003 23:29:11 +0000
Received: from [192.128.134.71] (helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 4.14)
	id 19W2eS-000DXE-J3
	for te-wg@ops.ietf.org; Fri, 27 Jun 2003 23:29:08 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h5RNSRnD025026
	for <te-wg@ops.ietf.org>; Fri, 27 Jun 2003 18:28:38 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3EE9217C005CDFDE; Fri, 27 Jun 2003 19:28:15 -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"
Content-Transfer-Encoding: quoted-printable
Subject: RE: New I-D on inter-area (and inter-as) MPLS TE requirements
Date: Fri, 27 Jun 2003 18:28:18 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A6883@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: New I-D on inter-area (and inter-as) MPLS TE requirements
Thread-Index: AcM79tZKVc8nFrZGSOWoMSeSZ3Cu3QBBxyow
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
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: quoted-printable

Jim,

> This was written in about an hour, late the night before the=20
> deadline (so show some mercy :)
> draft-boyle-tewg-interarea-reqts-00.txt

It's pretty good for an hour's worth :-)

> The goal was to make sure that we cover requirements for=20
> inter-area TE.  To show that it's not that hard to couple in=20
> the requirements for inter-as TE, I extended it to cover that=20
> as well.

General comments:
I'm glad you're providing inter-area TE requirements.  I agree that both =
inter-area TE and inter-AS TE should be progressed together, and would =
not favor progressing inter-AS TE without also progressing inter-area =
TE.  It would seem if a SP needed inter-AS TE, they would usually also =
need inter-area TE.  A while back vendors claimed that many SPs were =
requesting inter-area TE.  I assume that's still the case, else can =
someone explain why SPs would want inter-AS TE and not inter-area TE?

Specific comments:
1. Some of the functionality's in Section 1.1 should be more specific, =
e.g.,
- what bandwidth specification: Tspec parameters? overbooking =
considerations?  'reserved bandwidth' as per DSTE?
- what priorities: setup priority? holding priority? preemption priority =
as per DSTE?
2. Section 3.1:=20
"when the source is more than one area away from the destination, the =
destination's border router may send back a Path Error.  Ideally, the =
source's border router would try another border router into the =
destination's area, however with current protocol, the Path Error will =
propagate to the source."
sounds like a requirement for [crankback] functionality =
http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-06.txt
3. Section 3.4:
" Diffserv TE should be directly translatable at border-routers, as the =
class-type of an LSP is explicit for class-types greater than 0 and =
not-existent in the path message for class-type 0."
Are you proposing to standardize class-type 0 to mean best effort?  =
Section 1.4 also refers to 'conventions' for class-types 0, 1, and 2.

Regards,
Jerry

~ an hour's worth of commenting :-)




From owner-te-wg@ops.ietf.org  Sat Jun 28 07:18: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 HAA20877
	for <tewg-archive@lists.ietf.org>; Sat, 28 Jun 2003 07:18:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19WDdQ-0009i4-Tn
	for te-wg-data@psg.com; Sat, 28 Jun 2003 11:12:48 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.14)
	id 19WDdO-0009hB-AI
	for te-wg@ops.ietf.org; Sat, 28 Jun 2003 11:12:46 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 28 Jun 2003 13:12:19 +0100
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h5SBABtp006926;
	Sat, 28 Jun 2003 13:10:11 +0200 (MET DST)
Received: from jvasseur-w2k01.cisco.com ([10.49.250.130])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id NAA14401;
	Sat, 28 Jun 2003 13:12:10 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20030627194035.05a88fc8@paris.cisco.com>
X-Sender: jvasseur@paris.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sat, 28 Jun 2003 02:48:04 -0400
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: RE: New I-D on inter-area (and inter-as) MPLS TE requirements
Cc: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0A6883@KCCLUST06EVS1.ugd.a
 tt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-24.9 required=5.0
	tests=BAYES_10,DATE_IN_PAST_03_06,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 Jerry,

At 06:28 PM 6/27/2003 -0500, Ash, Gerald R (Jerry), ALABS wrote:
>Jim,
>
> > This was written in about an hour, late the night before the
> > deadline (so show some mercy :)
> > draft-boyle-tewg-interarea-reqts-00.txt
>
>It's pretty good for an hour's worth :-)
>
> > The goal was to make sure that we cover requirements for
> > inter-area TE.  To show that it's not that hard to couple in
> > the requirements for inter-as TE, I extended it to cover that
> > as well.
>
>General comments:
>I'm glad you're providing inter-area TE requirements.  I agree that both 
>inter-area TE and inter-AS TE should be progressed together, and would not 
>favor progressing inter-AS TE without also progressing inter-area TE.  It 
>would seem if a SP needed inter-AS TE, they would usually also need 
>inter-area TE.

Well no. I'm of course not against the idea of working on inter-area TE 
reqs but stating that the SPs that need Inter-AS TE also need inter-area is 
not correct. Several SPs have multiple ASes and single IGP area/level in 
each AS.

As I said during the last CCAMP meeting, although some mechanisms might 
work for both (see draft-ieft-mpls-nodeid-subobject-01.txt, 
draft-vasseur-mpls-loose-pah-reopt-02.txt, 
draft-ayyangar-inter-region-te-00.txt,...), the requirements are quite 
different. For instance, if you take a look at the TE WG Inter-AS TE 
requirement draft (draft-ietf-tewg-mpls-te-req.00.txt), you'll see that 
quite a few requirements are specific to inter-AS TE:
         - Policy control,
         - Confidentiality,
         - Some management functions,
         - ....

Moreover, the question on whether to combine the requirements of inter-area 
and inter-AS in the same document has been raised on the TW WG list and I 
think that there was a majority stating that there should be separate 
documents (NTT-C, EQUANT, FRANCE TELECOM, INFONET, SBC, ...).

>A while back vendors claimed that many SPs were requesting inter-area 
>TE.  I assume that's still the case, else can someone explain why SPs 
>would want inter-AS TE and not inter-area TE?

As stated before, many SPs have multiple ASes but single IGP area/level.

Of course your comments on draft-ietf-tewg-mpls-te-req.00.txt are very welcome.

JP.

>Specific comments:
>1. Some of the functionality's in Section 1.1 should be more specific, e.g.,
>- what bandwidth specification: Tspec parameters? overbooking 
>considerations?  'reserved bandwidth' as per DSTE?
>- what priorities: setup priority? holding priority? preemption priority 
>as per DSTE?
>2. Section 3.1:
>"when the source is more than one area away from the destination, the 
>destination's border router may send back a Path Error.  Ideally, the 
>source's border router would try another border router into the 
>destination's area, however with current protocol, the Path Error will 
>propagate to the source."
>sounds like a requirement for [crankback] functionality 
>http://www.ietf.org/internet-drafts/draft-iwata-mpls-crankback-06.txt
>3. Section 3.4:
>" Diffserv TE should be directly translatable at border-routers, as the 
>class-type of an LSP is explicit for class-types greater than 0 and 
>not-existent in the path message for class-type 0."
>Are you proposing to standardize class-type 0 to mean best 
>effort?  Section 1.4 also refers to 'conventions' for class-types 0, 1, and 2.
>
>Regards,
>Jerry
>
>~ an hour's worth of commenting :-)



From owner-te-wg@ops.ietf.org  Sat Jun 28 12:29: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 MAA27061
	for <tewg-archive@lists.ietf.org>; Sat, 28 Jun 2003 12:29:14 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19WIUy-000KDx-98
	for te-wg-data@psg.com; Sat, 28 Jun 2003 16:24:24 +0000
Received: from [192.128.166.71] (helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 4.14)
	id 19WIUv-000KCa-Gw
	for te-wg@ops.ietf.org; Sat, 28 Jun 2003 16:24:21 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h5SGNJl3011080
	for <te-wg@ops.ietf.org>; Sat, 28 Jun 2003 12:23:50 -0400
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EE9217C0060890F; Sat, 28 Jun 2003 12:23:31 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: New I-D on inter-area (and inter-as) MPLS TE requirements
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Date: Sat, 28 Jun 2003 11:23:11 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A6884@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: New I-D on inter-area (and inter-as) MPLS TE requirements
Thread-Index: AcM9ZiOMvN63hhCnSMqw1lAXwmKrzQAKOLKQ
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jean Philippe Vasseur" <jvasseur@cisco.com>,
        "Jim Boyle" <jboyle@pdnets.com>
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: quoted-printable

JP,

> >General comments:
> >I'm glad you're providing inter-area TE requirements.  I agree that =
both=20
> >inter-area TE and inter-AS TE should be progressed together, and =
would not=20
> >favor progressing inter-AS TE without also progressing inter-area TE. =
 It=20
> >would seem if a SP needed inter-AS TE, they would usually also need=20
> >inter-area TE.

> Well no. I'm of course not against the idea of working on inter-area =
TE=20
> reqs but stating that the SPs that need Inter-AS TE also need =
inter-area is=20
> not correct. Several SPs have multiple ASes and single IGP area/level =
in=20
> each AS.

Certainly not *all* SPs who have multiple AS's also have a single =
area/level in each (e.g., AT&T).  Further, George Swallow stated in an =
MPLS WG meeting that many SPs were requesting inter-area TE.  I'm glad =
that you agree with the need for both inter-area TE and inter-AS TE to =
be progressed. =20

> the question on whether to combine the requirements of inter-area=20
> and inter-AS in the same document has been raised on the TEWG list and =
I=20
> think that there was a majority stating that there should be separate=20
> documents (NTT-C, EQUANT, FRANCE TELECOM, INFONET, SBC, ...).

I also stated on the TEWG list that inter-area and inter-AS TE should be =
progressed separately, but in parallel.  So if you're associating =
individuals with SPs, you could also deduce 'AT&T' in the above =
'majority' list.  Others agreed that we should progress both in =
parallel. =20

I'm glad that Jim restarted the inter-area TE requirements effort, which =
you and I and several others first initiated in TEWG a while back.

Jerry



From owner-te-wg@ops.ietf.org  Sun Jun 29 13:04: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 NAA02204
	for <tewg-archive@lists.ietf.org>; Sun, 29 Jun 2003 13:03:52 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19WfPv-000Hse-Ss
	for te-wg-data@psg.com; Sun, 29 Jun 2003 16:52:43 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.14)
	id 19WfPs-000HpC-5k
	for te-wg@ops.ietf.org; Sun, 29 Jun 2003 16:52:40 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 29 Jun 2003 18:52:25 +0200
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h5TGo54q016408;
	Sun, 29 Jun 2003 18:50:05 +0200 (MET DST)
Received: from jvasseur-w2k01.cisco.com ([10.49.250.130])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id SAA11448;
	Sun, 29 Jun 2003 18:52:04 +0200 (MET DST)
Message-Id: <4.3.2.7.2.20030628151331.068bd498@paris.cisco.com>
X-Sender: jvasseur@paris.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 29 Jun 2003 12:52:03 -0400
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: RE: New I-D on inter-area (and inter-as) MPLS TE requirements
Cc: "Jim Boyle" <jboyle@pdnets.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0A6884@KCCLUST06EVS1.ugd.a
 tt.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 Jerry,

At 11:23 AM 6/28/2003 -0500, Ash, Gerald R (Jerry), ALABS wrote:
>JP,
>
> > >General comments:
> > >I'm glad you're providing inter-area TE requirements.  I agree that both
> > >inter-area TE and inter-AS TE should be progressed together, and would 
> not
> > >favor progressing inter-AS TE without also progressing inter-area TE.  It
> > >would seem if a SP needed inter-AS TE, they would usually also need
> > >inter-area TE.
>
> > Well no. I'm of course not against the idea of working on inter-area TE
> > reqs but stating that the SPs that need Inter-AS TE also need 
> inter-area is
> > not correct. Several SPs have multiple ASes and single IGP area/level in
> > each AS.
>
>Certainly not *all* SPs who have multiple AS's also have a single 
>area/level in each (e.g., AT&T).

sure this is why I said, "several" ;-) By the way, even if an SP have both, 
this does not mean that they need both inter-area and inter-AS TE ?

>   Further, George Swallow stated in an MPLS WG meeting that many SPs were 
> requesting inter-area TE.  I'm glad that you agree with the need for both 
> inter-area TE and inter-AS TE to be progressed.
>
> > the question on whether to combine the requirements of inter-area
> > and inter-AS in the same document has been raised on the TEWG list and I
> > think that there was a majority stating that there should be separate
> > documents (NTT-C, EQUANT, FRANCE TELECOM, INFONET, SBC, ...).
>
>I also stated on the TEWG list that inter-area and inter-AS TE should be 
>progressed separately, but in parallel.

So we're in sync !

Fee free to provide your comments on the ET WG req of inter-AS TE.

Thanks.

JP.

>So if you're associating individuals with SPs, you could also deduce 
>'AT&T' in the above 'majority' list.  Others agreed that we should 
>progress both in parallel.
>
>I'm glad that Jim restarted the inter-area TE requirements effort, which 
>you and I and several others first initiated in TEWG a while back.
>
>Jerry




From owner-te-wg@ops.ietf.org  Mon Jun 30 07:42: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 HAA11215
	for <tewg-archive@lists.ietf.org>; Mon, 30 Jun 2003 07:42:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19Wwzi-0001oM-NR
	for te-wg-data@psg.com; Mon, 30 Jun 2003 11:38:50 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19WwzY-0001nT-1a
	for te-wg@ops.ietf.org; Mon, 30 Jun 2003 11:38:40 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10918;
	Mon, 30 Jun 2003 07:38:19 -0400 (EDT)
Message-Id: <200306301138.HAA10918@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-wlai-tewg-bcmodel-02.txt,.pdf
Date: Mon, 30 Jun 2003 07:38:18 -0400
X-Spam-Status: No, hits=3.1 required=5.0
	tests=MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Level: ***
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.


	Title		: Bandwidth Constraints Models for Diffserv-aware MPLS 
                          Traffic Engineering: Performance Evaluation
	Author(s)	: W. Lai
	Filename	: draft-wlai-tewg-bcmodel-02.txt,.pdf
	Pages		: 18
	Date		: 2003-6-27
	
The Diffserv-aware MPLS Traffic Engineering Requirements RFCxxxx 
specifies the requirements and selection criteria for bandwidth 
constraints models.  Two such models, the Maximum Allocation and the 
Russian Dolls, are described therein.  This document complements 
RFCxxxx by describing in more details some of the selection criteria 
and their implications.  Results of a performance evaluation of the 
two models are also included.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-wlai-tewg-bcmodel-02.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-wlai-tewg-bcmodel-02.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-wlai-tewg-bcmodel-02.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-6-27150240.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-wlai-tewg-bcmodel-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-wlai-tewg-bcmodel-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Mon Jun 30 07:54: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 HAA12805
	for <tewg-archive@lists.ietf.org>; Mon, 30 Jun 2003 07:54:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19WxDc-0003Ed-JU
	for te-wg-data@psg.com; Mon, 30 Jun 2003 11:53:12 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19WxDV-0003E3-Tw
	for te-wg@ops.ietf.org; Mon, 30 Jun 2003 11:53:08 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12284;
	Mon, 30 Jun 2003 07:52:49 -0400 (EDT)
Message-Id: <200306301152.HAA12284@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-diff-te-mar-01.txt
Date: Mon, 30 Jun 2003 07:52:49 -0400
X-Spam-Status: No, hits=3.1 required=5.0
	tests=MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Level: ***
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		: Max Allocation with Reservation Bandwidth Constraint 
                          Model for MPLS/DiffServ TE & Performance Comparisons
	Author(s)	: J. Ash
	Filename	: draft-ietf-tewg-diff-te-mar-01.txt
	Pages		: 0
	Date		: 2003-6-27
	
This document complements the DiffServ-aware MPLS TE (DSTE) requirements 
document by giving a functional specification for the Maximum Allocation 
with Reservation (MAR) bandwidth constraint model.  Assumptions, 
applicability, and examples of the operation of the MAR bandwidth 
constraint model are presented.  MAR performance is analyzed relative to 
the criteria for selecting a bandwidth constraint model, in order to 
provide guidance to user implementation of the model in their networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-tewg-diff-te-mar-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tewg-diff-te-mar-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

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

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-mar-01.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Mon Jun 30 09:16: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 JAA20898
	for <tewg-archive@lists.ietf.org>; Mon, 30 Jun 2003 09:16:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19Wy5t-0008GN-7z
	for te-wg-data@psg.com; Mon, 30 Jun 2003 12:49:17 +0000
Received: from [202.3.77.131] (helo=web15201.mail.bjs.yahoo.com)
	by psg.com with smtp (Exim 4.14)
	id 19Wy5k-0008FG-9m
	for te-wg@ops.ietf.org; Mon, 30 Jun 2003 12:49:08 +0000
Message-ID: <20030630124903.3140.qmail@web15201.mail.bjs.yahoo.com>
Received: from [218.72.37.158] by web15201.mail.bjs.yahoo.com via HTTP; Mon, 30 Jun 2003 20:49:03 CST
Date: Mon, 30 Jun 2003 20:49:03 +0800 (CST)
From: =?gb2312?q?Jing=20Shen?= <jshen_cad@yahoo.com.cn>
Subject: Re: I-D ACTION:draft-wlai-tewg-bcmodel-02.txt,.pdf
To: te-wg@ops.ietf.org
In-Reply-To: <200306301138.HAA10918@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1916474385-1056977343=:2219"
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, hits=-3.2 required=5.0
	tests=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

--0-1916474385-1056977343=:2219
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit

My question:
 
How does the assumpiton of Possion Arrival and Erlang measurement relates to real network senerion? 
 
Why does the draft states "This allows us to express link 
   bandwidth usage simply in terms of the *number of simultaneously 
   established LSPs*"?  To my understanding, even overbooking is adopted BC should be interpreted as " the bandwidth utilized by special TC", because we could not assume every LSP has the same bandwidth requirement.
 


Internet-Drafts@ietf.org wrote:
A New Internet-Draft is available from the on-line Internet-Drafts directories.


Title : Bandwidth Constraints Models for Diffserv-aware MPLS 
Traffic Engineering: Performance Evaluation
Author(s) : W. Lai
Filename : draft-wlai-tewg-bcmodel-02.txt,.pdf
Pages : 18
Date : 2003-6-27

The Diffserv-aware MPLS Traffic Engineering Requirements RFCxxxx 
specifies the requirements and selection criteria for bandwidth 
constraints models. Two such models, the Maximum Allocation and the 
Russian Dolls, are described therein. This document complements 
RFCxxxx by describing in more details some of the selection criteria 
and their implications. Results of a performance evaluation of the 
two models are also included.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-wlai-tewg-bcmodel-02.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-wlai-tewg-bcmodel-02.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-wlai-tewg-bcmodel-02.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.



Jing Shen

State Key Lab of CAD&CG
ZheJiang University(YuQuan)
HangZhou, ZheJiang Province 310027
P.R.China


---------------------------------
Do You Yahoo!?
网恋的诠释：真情还是放纵？
--0-1916474385-1056977343=:2219
Content-Type: text/html; charset=gb2312
Content-Transfer-Encoding: 8bit

<DIV>
<DIV>My question:</DIV>
<DIV>&nbsp;</DIV>
<DIV>How does the assumpiton of Possion Arrival and Erlang measurement relates to real network senerion? </DIV>
<DIV>&nbsp;</DIV>
<DIV>Why does the draft states "This allows us to express link <BR>&nbsp;&nbsp; bandwidth usage simply in terms of the *number of simultaneously <BR>&nbsp;&nbsp; established LSPs*"?&nbsp; To my understanding, even overbooking is adopted BC should be interpreted as " the bandwidth utilized by special TC", because we could not assume every LSP has the same bandwidth requirement.</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR><BR><B><I>Internet-Drafts@ietf.org</I></B> wrote:</DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">A New Internet-Draft is available from the on-line Internet-Drafts directories.<BR><BR><BR>Title : Bandwidth Constraints Models for Diffserv-aware MPLS <BR>Traffic Engineering: Performance Evaluation<BR>Author(s) : W. Lai<BR>Filename : draft-wlai-tewg-bcmodel-02.txt,.pdf<BR>Pages : 18<BR>Date : 2003-6-27<BR><BR>The Diffserv-aware MPLS Traffic Engineering Requirements RFCxxxx <BR>specifies the requirements and selection criteria for bandwidth <BR>constraints models. Two such models, the Maximum Allocation and the <BR>Russian Dolls, are described therein. This document complements <BR>RFCxxxx by describing in more details some of the selection criteria <BR>and their implications. Results of a performance evaluation of the <BR>two models are also included.<BR><BR>A URL for this Internet-Draft is:<BR>http://www.ietf.org/internet-drafts/draft-wlai-tewg-bcmodel-02.txt<BR><BR>To remove yourself from the
 IETF Announcement list, send a message to <BR>ietf-announce-request with the word unsubscribe in the body of the message.<BR><BR>Internet-Drafts are also available by anonymous FTP. Login with the username<BR>"anonymous" and a password of your e-mail address. After logging in,<BR>type "cd internet-drafts" and then<BR>"get draft-wlai-tewg-bcmodel-02.txt".<BR><BR>A list of Internet-Drafts directories can be found in<BR>http://www.ietf.org/shadow.html <BR>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<BR><BR><BR>Internet-Drafts can also be obtained by e-mail.<BR><BR>Send a message to:<BR>mailserv@ietf.org.<BR>In the body type:<BR>"FILE /internet-drafts/draft-wlai-tewg-bcmodel-02.txt".<BR><BR>NOTE: The mail server at ietf.org can return the document in<BR>MIME-encoded form by using the "mpack" utility. To use this<BR>feature, insert the command "ENCODING mime" before the "FILE"<BR>command. To decode the response(s), you will need "munpack" or<BR>a MIME-compliant mail reader. Different
 MIME-compliant mail readers<BR>exhibit different behavior, especially when dealing with<BR>"multipart" MIME messages (i.e. documents which have been split<BR>up into multiple messages), so check your local documentation on<BR>how to manipulate these messages.<BR><BR><BR>Below is the data which will enable a MIME compliant mail reader<BR>implementation to automatically retrieve the ASCII version of the<BR>Internet-Draft.<BR></BLOCKQUOTE></DIV><BR><BR>Jing Shen<br><br>State Key Lab of CAD&amp;CG<br>ZheJiang University(YuQuan)<br>HangZhou, ZheJiang Province 310027<br>P.R.China<p><br><hr size=1><b>Do You Yahoo!?</b><br>
<a href="http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.surveys.yahoo.com/netlove">网恋的诠释：真情还是放纵？</a>
--0-1916474385-1056977343=:2219--



From owner-te-wg@ops.ietf.org  Mon Jun 30 11:38: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 LAA01678
	for <tewg-archive@lists.ietf.org>; Mon, 30 Jun 2003 11:38:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19X0dJ-000LgD-WC
	for te-wg-data@psg.com; Mon, 30 Jun 2003 15:31:57 +0000
Received: from [209.219.209.75] (helo=ckmso2.proxy.att.com)
	by psg.com with esmtp (Exim 4.14)
	id 19X0dD-000LeB-97
	for te-wg@ops.ietf.org; Mon, 30 Jun 2003 15:31:51 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h5UErUtl007867
	for <te-wg@ops.ietf.org>; Mon, 30 Jun 2003 11:31:20 -0400
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EE9217C006A3F7F for te-wg@ops.ietf.org; Mon, 30 Jun 2003 11:31:15 -0400
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: RE: I-D ACTION:draft-ietf-tewg-diff-te-mar-01.txt
Date: Mon, 30 Jun 2003 10:31:20 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BEACB@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-tewg-diff-te-mar-01.txt
Thread-Index: AcM+/usnDMRhsLKkRfCBvgzb1bjK2gAF4wUw
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
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: quoted-printable

All,

The updates to this version:

1. Some changes in notation to align better to DSTE notation: =
RESERVED_BW, UNRESERVED_BW, MAX_RESERVABLE_BW, bandwidth constraint =
(BCc), etc.  NORMALIZED(CTc) deleted.

2. Simplified functional specification in Section 4.
 =20
3. Added Section 5 to explain how BCck are set for MAR (also explain in =
ANNEX A how BCck set for MAM, and discuss some =
observations/sensitivities in setting MAM bandwidth constraints).

4. Added new simulation results in ANNEX A, which compare MAR, MAM, and =
No-DSTE, including:
- simulation for 50% general overload=20
- simulations for single link failure and multiple link failure
- simulations adjusting the MAM bandwidth allocations in various ways

Comments and suggestions are welcome.

Thanks,
Jerry

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Monday, June 30, 2003 7:53 AM
Cc: te-wg@ops.ietf.org
Subject: I-D ACTION:draft-ietf-tewg-diff-te-mar-01.txt

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		: Max Allocation with Reservation Bandwidth Constraint=20
                          Model for MPLS/DiffServ TE & Performance =
Comparisons
	Author(s)	: J. Ash
	Filename	: draft-ietf-tewg-diff-te-mar-01.txt
	Pages		: 0
	Date		: 2003-6-27
=09
This document complements the DiffServ-aware MPLS TE (DSTE) requirements =

document by giving a functional specification for the Maximum Allocation =

with Reservation (MAR) bandwidth constraint model.  Assumptions,=20
applicability, and examples of the operation of the MAR bandwidth=20
constraint model are presented.  MAR performance is analyzed relative to =

the criteria for selecting a bandwidth constraint model, in order to=20
provide guidance to user implementation of the model in their networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-01.txt



