From owner-te-wg@ops.ietf.org  Tue Apr  1 04:22: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 EAA01938
	for <tewg-archive@lists.ietf.org>; Tue, 1 Apr 2003 04:22:35 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190HvW-000D6L-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 01:19:30 -0800
Received: from mx1.fundp.ac.be ([138.48.4.207])
	by psg.com with esmtp (Exim 3.36 #1)
	id 190HvT-000D5w-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 01:19:27 -0800
Received: from pc10.infonet.fundp.ac.be (pc10.infonet.fundp.ac.be [138.48.33.210])
	by mx1.fundp.ac.be (8.11.6+Sun/8.11.6) with ESMTP id h319GNE07100;
	Tue, 1 Apr 2003 11:16:23 +0200 (MEST)
Received: from infonet.fundp.ac.be (alpha [138.48.33.210])
	by pc10.infonet.fundp.ac.be (8.11.6/8.11.6) with ESMTP id h319EPF20461;
	Tue, 1 Apr 2003 11:14:26 +0200
Message-ID: <3E895871.4070609@infonet.fundp.ac.be>
Date: Tue, 01 Apr 2003 11:14:25 +0200
From: Cristel Pelsser <cpe@infonet.fundp.ac.be>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Boyle <jboyle@pdnets.com>
CC: te-wg@ops.ietf.org
Subject: Re: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
References: <Pine.LNX.4.44.0303272131330.21532-100000@fido.nc.rr.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
X-Spam-Status: No, hits=-25.9 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,REFERENCES,USER_AGENT_MOZILLA_UA
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear all,

I also think that (a) and (b) should progress separately.

Cristel

Jim Boyle wrote:

>At the meeting, as you can tell in the minutes, it was clear to all that 
>there is plenty support to move forward on inter-as requirements (there 
>was at IETF55 too).
>
>There was a clear difference of opinion on how to do this though.
>
>Most felt the best approach would be to adopt 
>
>http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-02.txt
>(or -03)
>
>as a WG document.  This will put more focus and review on it, and in 
>general keep this work from stalling in discussion ad naseum.
>
>The counter view (held by me, and a handful of others) was that there are 
>clearly some that are also interested in multi-area TE, and that we should 
>consider working toward a WG requirements document that 
>- outlined the possible scope, and defined the scope of the draft
>- presented flushed out, coherent requirements
>
>At a minimum, I felt that we should not move anything to a WG document 
>until it was clear how this fitted into our charter, and had some 
>discussion on the list confirming the general consensus of the meeting 
>(which again, was to move forward independently on inter-as requirements, 
>with draft-zhang becoming a WG document, and focal point of this effort).
>
>In discussion with Bert, it looks like the charter is not an
>obstacle, in fact as Raymond pointed out, it currently covers this:
>
>"The working group may also consider the problems of traffic engineering 
>across autonomous systems boundaries."
>
>I'm just kidding about the (a) (b) (c) (d) thing, feel free to just tell 
>it like it is :)
>
>thanks,
>
>Jim
>
>
>







From owner-te-wg@ops.ietf.org  Tue Apr  1 04:25: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 EAA01987
	for <tewg-archive@lists.ietf.org>; Tue, 1 Apr 2003 04:25:56 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190I3X-000DO0-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 01:27:47 -0800
Received: from alc136.alcatel.be ([195.207.101.136] helo=bt0g2p.god.bel.alcatel.be)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190I3V-000DNm-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 01:27:45 -0800
Received: from bemail05.net.alcatel.be (relay3 [127.0.0.1])
	by bt0g2p.god.bel.alcatel.be (8.11.0/8.11.4) with ESMTP id h319RRf09253;
	Tue, 1 Apr 2003 11:27:27 +0200
Received: from alcatel.be ([138.203.67.27])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003040111272471:2518 ;
          Tue, 1 Apr 2003 11:27:24 +0200 
Message-ID: <3E895AE6.D4C2AA37@alcatel.be>
Date: Tue, 01 Apr 2003 11:24:54 +0200
From: Dimitri.Papadimitriou@alcatel.be
Organization: optical network architecture (nta - antwerpen)
X-Mailer: Mozilla 4.79 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: Jim Boyle <jboyle@pdnets.com>, te-wg@ops.ietf.org
Subject: Re: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
References: <9473683187ADC049A855ED2DA739ABCA0A6F64@KCCLUST06EVS1.ugd.att.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 04/01/2003 11:27:24,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 04/01/2003 11:27:26,
	Serialize complete at 04/01/2003 11:27:26
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-17.8 required=5.0
	tests=BAYES_10,EMAIL_ATTRIBUTION,NO_REAL_NAME,REFERENCES
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jerry, progress on inter-area requirements (a) may be done 
independently of inter-as (b) but as you said "synergies" 
should be also in the loop, keep a global architectural 
perspective (of protocols and mechanisms) is of primary 
importance (note: also we should probably also take into 
account that an internal lsr may have to reach another 
area in order to get out of its own as, thus to deliver 
e2e inter-as te, we will have cases where the inter-area 
solutions will be in the loop, anyway)

thanks,
- dimitri.

"Ash, Gerald R (Jerry), ALABS" wrote:
> 
> I agree that we should progress a) and b) independently, but take note of any possible synergies.
> 
> Also, icw item a):
> 
> Sudheer> Should we revive our inter-area drafts now
> Jim> yes, please do.
> 
> Several of us collaborated on multi-area TE requirements a while back: http://www1.ietf.org/mail-archive/ietf-announce/Current/msg15882.html
> has expired, but is still available at:
> http://www.watersprings.org/links/mlr/id/draft-ash-multi-area-te-reqmts-01.txt
> 
> This can be updated and progressed if there is interest.
> 
> Thanks,
> Jerry

-- 
Papadimitriou Dimitri 
E-mail : dimitri.papadimitriou@alcatel.be 
Private: http://www.rc.bel.alcatel.be/~papadimd/index.html
E-mail : dpapadimitriou@psg.com
Public : http://psg.com/~dpapadimitriou/
Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium
Phone  : +32 3 240-8491



From owner-te-wg@ops.ietf.org  Tue Apr  1 08:30: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 IAA09688
	for <tewg-archive@lists.ietf.org>; Tue, 1 Apr 2003 08:30:47 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190LpB-000PxB-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 05:29:13 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190Lp8-000Pwz-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 05:29:10 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h31DSMio002656
	for <te-wg@ops.ietf.org>; Tue, 1 Apr 2003 08:29:09 -0500 (EST)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh3i.attrh.att.com (6.5.032)
        id 3E8515600000DA3B; Tue, 1 Apr 2003 08:28:58 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: WG list confirmation - DSTE draft actions from meeting
Date: Tue, 1 Apr 2003 07:28:57 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A66FB@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: WG list confirmation - DSTE draft actions from meeting
Thread-Index: AcL01CwGiZ0BxRN/StCTCHQLN55kBADevzoQ
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-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 IAA09688

> Hi, this is to allow the WG list to weigh in the 
> consensus from the meeting.  This email is on the 
> DS-TE drafts...

> http://www.ietf.org/internet-drafts/draft-ash-mpls-dste-bcmodel-max-alloc-resv-01.txt

> This draft will be revised

Yes, as agreed, I'll add a section on 'assumptions & applicability' to the I-D.

> it was not discussed if it should be re-updated as 
> a WG document.  If that is the Jerry's intention, 
> he can bring that question to the WG list.

The agreement was to "progress MAR" (my notes), which is consistent with the proposal in my slides to "specify/progress MAR".
Also, the meeting minutes say "the way to go forward is to make all of them [BC models] experimental"

Thanks,
'the Jerry'









From owner-te-wg@ops.ietf.org  Tue Apr  1 10:14:59 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18524
	for <tewg-archive@lists.ietf.org>; Tue, 1 Apr 2003 10:14:58 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190NT4-000660-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 07:14:30 -0800
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190NT0-00065o-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 07:14:26 -0800
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 h31FEL4g002994;
	Tue, 1 Apr 2003 10:14:21 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h31FELhU002990;
	Tue, 1 Apr 2003 10:14:21 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Tue, 1 Apr 2003 10:14:21 -0500 (EST)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
cc: te-wg@ops.ietf.org
Subject: draft-ash-mpls-dste-bcmodel-max-alloc-resv -> WG document?
In-Reply-To: <9473683187ADC049A855ED2DA739ABCA0A66FB@KCCLUST06EVS1.ugd.att.com>
Message-ID: <Pine.LNX.4.44.0304011012360.1059-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-24.0 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTE_TWICE_1,
	      USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


When Jerry incorporates the discussed revisions, he would like to resubmit 
it as a WG document.  I think that makes sense, as it was the course of 
action on the other drafts (MAM, RDM).

Any comments?

thanks

Jim

On Tue, 1 Apr 2003, Ash, Gerald R (Jerry), ALABS wrote:

> > Hi, this is to allow the WG list to weigh in the 
> > consensus from the meeting.  This email is on the 
> > DS-TE drafts...
> 
> > http://www.ietf.org/internet-drafts/draft-ash-mpls-dste-bcmodel-max-alloc-resv-01.txt
> 
> > This draft will be revised
> 
> Yes, as agreed, I'll add a section on 'assumptions & applicability' to the I-D.
> 
> > it was not discussed if it should be re-updated as 
> > a WG document.  If that is the Jerry's intention, 
> > he can bring that question to the WG list.
> 
> The agreement was to "progress MAR" (my notes), which is consistent with the proposal in my slides to "specify/progress MAR".
> Also, the meeting minutes say "the way to go forward is to make all of them [BC models] experimental"
> 
> Thanks,
> 'the Jerry'
> 
> 
> 
> 
> 
> 
> 




From owner-te-wg@ops.ietf.org  Tue Apr  1 15:31: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 PAA13755
	for <tewg-archive@lists.ietf.org>; Tue, 1 Apr 2003 15:31:52 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190SQ0-000B0y-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 12:31:40 -0800
Received: from sp1isa2.optiglobe.com.br ([200.185.13.104] helo=smtp.optiglobe.net.br)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190SPw-000B0i-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 12:31:36 -0800
Received: from mail pickup service by smtp.optiglobe.net.br with Microsoft SMTPSVC;
	 Tue, 1 Apr 2003 17:29:07 -0300
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190I3X-000DO0-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 01:27:47 -0800
Received: from alc136.alcatel.be ([195.207.101.136] helo=bt0g2p.god.bel.alcatel.be)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190I3V-000DNm-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 01:27:45 -0800
Received: from bemail05.net.alcatel.be (relay3 [127.0.0.1])
	by bt0g2p.god.bel.alcatel.be (8.11.0/8.11.4) with ESMTP id h319RRf09253;
	Tue, 1 Apr 2003 11:27:27 +0200
Received: from alcatel.be ([138.203.67.27])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003040111272471:2518 ;
          Tue, 1 Apr 2003 11:27:24 +0200 
Message-ID: <3E895AE6.D4C2AA37@alcatel.be>
Date: Tue, 01 Apr 2003 11:24:54 +0200
From: Dimitri.Papadimitriou@alcatel.be
Organization: optical network architecture (nta - antwerpen)
X-Mailer: Mozilla 4.79 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: Jim Boyle <jboyle@pdnets.com>, te-wg@ops.ietf.org
Subject: Re: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
References: <9473683187ADC049A855ED2DA739ABCA0A6F64@KCCLUST06EVS1.ugd.att.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 04/01/2003 11:27:24,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 04/01/2003 11:27:26,
	Serialize complete at 04/01/2003 11:27:26
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 01 Apr 2003 20:29:07.0609 (UTC) FILETIME=[5858D890:01C2F88D]
X-Spam-Status: No, hits=-18.6 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,NO_REAL_NAME,REFERENCES
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jerry, progress on inter-area requirements (a) may be done 
independently of inter-as (b) but as you said "synergies" 
should be also in the loop, keep a global architectural 
perspective (of protocols and mechanisms) is of primary 
importance (note: also we should probably also take into 
account that an internal lsr may have to reach another 
area in order to get out of its own as, thus to deliver 
e2e inter-as te, we will have cases where the inter-area 
solutions will be in the loop, anyway)

thanks,
- dimitri.

"Ash, Gerald R (Jerry), ALABS" wrote:
> 
> I agree that we should progress a) and b) independently, but take note of any possible synergies.
> 
> Also, icw item a):
> 
> Sudheer> Should we revive our inter-area drafts now
> Jim> yes, please do.
> 
> Several of us collaborated on multi-area TE requirements a while back: http://www1.ietf.org/mail-archive/ietf-announce/Current/msg15882.html
> has expired, but is still available at:
> http://www.watersprings.org/links/mlr/id/draft-ash-multi-area-te-reqmts-01.txt
> 
> This can be updated and progressed if there is interest.
> 
> Thanks,
> Jerry

-- 
Papadimitriou Dimitri 
E-mail : dimitri.papadimitriou@alcatel.be 
Private: http://www.rc.bel.alcatel.be/~papadimd/index.html
E-mail : dpapadimitriou@psg.com
Public : http://psg.com/~dpapadimitriou/
Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium
Phone  : +32 3 240-8491




From owner-te-wg@ops.ietf.org  Tue Apr  1 15:32:22 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13772
	for <tewg-archive@lists.ietf.org>; Tue, 1 Apr 2003 15:32:21 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190SPg-000Ayc-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 12:31:20 -0800
Received: from sp1isa2.optiglobe.com.br ([200.185.13.104] helo=smtp.optiglobe.net.br)
	by psg.com with esmtp (Exim 3.36 #1)
	id 190SPb-000AyM-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 12:31:16 -0800
Received: from mail pickup service by smtp.optiglobe.net.br with Microsoft SMTPSVC;
	 Tue, 1 Apr 2003 17:28:46 -0300
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190HvW-000D6L-00
	for te-wg-data@psg.com; Tue, 01 Apr 2003 01:19:30 -0800
Received: from mx1.fundp.ac.be ([138.48.4.207])
	by psg.com with esmtp (Exim 3.36 #1)
	id 190HvT-000D5w-00
	for te-wg@ops.ietf.org; Tue, 01 Apr 2003 01:19:27 -0800
Received: from pc10.infonet.fundp.ac.be (pc10.infonet.fundp.ac.be [138.48.33.210])
	by mx1.fundp.ac.be (8.11.6+Sun/8.11.6) with ESMTP id h319GNE07100;
	Tue, 1 Apr 2003 11:16:23 +0200 (MEST)
Received: from infonet.fundp.ac.be (alpha [138.48.33.210])
	by pc10.infonet.fundp.ac.be (8.11.6/8.11.6) with ESMTP id h319EPF20461;
	Tue, 1 Apr 2003 11:14:26 +0200
Message-ID: <3E895871.4070609@infonet.fundp.ac.be>
Date: Tue, 01 Apr 2003 11:14:25 +0200
From: Cristel Pelsser <cpe@infonet.fundp.ac.be>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jim Boyle <jboyle@pdnets.com>
CC: te-wg@ops.ietf.org
Subject: Re: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
References: <Pine.LNX.4.44.0303272131330.21532-100000@fido.nc.rr.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MailScanner: Found to be clean
X-OriginalArrivalTime: 01 Apr 2003 20:28:46.0234 (UTC) FILETIME=[4B9B47A0:01C2F88D]
X-Spam-Status: No, hits=-25.9 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,REFERENCES,USER_AGENT_MOZILLA_UA
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear all,

I also think that (a) and (b) should progress separately.

Cristel

Jim Boyle wrote:

>At the meeting, as you can tell in the minutes, it was clear to all that 
>there is plenty support to move forward on inter-as requirements (there 
>was at IETF55 too).
>
>There was a clear difference of opinion on how to do this though.
>
>Most felt the best approach would be to adopt 
>
>http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-02.txt
>(or -03)
>
>as a WG document.  This will put more focus and review on it, and in 
>general keep this work from stalling in discussion ad naseum.
>
>The counter view (held by me, and a handful of others) was that there are 
>clearly some that are also interested in multi-area TE, and that we should 
>consider working toward a WG requirements document that 
>- outlined the possible scope, and defined the scope of the draft
>- presented flushed out, coherent requirements
>
>At a minimum, I felt that we should not move anything to a WG document 
>until it was clear how this fitted into our charter, and had some 
>discussion on the list confirming the general consensus of the meeting 
>(which again, was to move forward independently on inter-as requirements, 
>with draft-zhang becoming a WG document, and focal point of this effort).
>
>In discussion with Bert, it looks like the charter is not an
>obstacle, in fact as Raymond pointed out, it currently covers this:
>
>"The working group may also consider the problems of traffic engineering 
>across autonomous systems boundaries."
>
>I'm just kidding about the (a) (b) (c) (d) thing, feel free to just tell 
>it like it is :)
>
>thanks,
>
>Jim
>
>
>








From owner-te-wg@ops.ietf.org  Wed Apr  2 14:35:50 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24581
	for <tewg-archive@lists.ietf.org>; Wed, 2 Apr 2003 14:35:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190nxP-0009fT-00
	for te-wg-data@psg.com; Wed, 02 Apr 2003 11:31:35 -0800
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 190nxM-0009fG-00
	for te-wg@ops.ietf.org; Wed, 02 Apr 2003 11:31:32 -0800
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 OAA01394
	for <te-wg@ops.ietf.org>; Wed, 2 Apr 2003 14:31:29 -0500 (EST)
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 OAA27415
	for <te-wg@ops.ietf.org>; Wed, 2 Apr 2003 14:31:31 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <2BDHZ2BF>; Wed, 2 Apr 2003 14:31:30 -0500
Message-ID: <313680C9A886D511A06000204840E1CF8F53EE@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: RE: draft-ash-mpls-dste-bcmodel-max-alloc-resv -> WG document?
Date: Wed, 2 Apr 2003 14:31:29 -0500 
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.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi! Few comments:

Technical (Scope):
(i) The aim here is to defined a BC Model and not a 
DSTE-Solution. i.e define the BC Model as per the 
DSTE requirement document: 
(a) the maximum number of Bandwidth Constraints
(b) which CTs each Bandwidth Constraint applies to and how

The draft in its present form, goes way beyond the scope.
For example: 
The proposed solution (a) expects modifications to the 
DSTE Solution (ii) introduces CT priority concept that
is not in DSTE-requirement 

I am not sure this is the right approach ...

Editorial: 
(i) Personally, I think this draft needs some editorial 
changes to state the solution more clearly [explicitly 
and succinctly state the rules/necessary configurations/
protocol extensions etc.] 

(ii) The draft also needs to define the term it uses 
precisely (and use them consistently]
Example: "bandwidth-in-progress","bandwidth-in-use", 
	   "reserved-bandwidth", "BWalloc" ... ...

(iii) Separate specification from the examples

Thanks,
sanjay



> -----Original Message-----
> From: Jim Boyle [mailto:jboyle@pdnets.com]
> Sent: Tuesday, April 01, 2003 10:14 AM
> To: Ash, Gerald R (Jerry), ALABS
> Cc: te-wg@ops.ietf.org
> Subject: draft-ash-mpls-dste-bcmodel-max-alloc-resv -> WG document?
> 
> 
> 
> When Jerry incorporates the discussed revisions, he would 
> like to resubmit 
> it as a WG document.  I think that makes sense, as it was the 
> course of 
> action on the other drafts (MAM, RDM).
> 
> Any comments?
> 
> thanks
> 
> Jim
> 
> On Tue, 1 Apr 2003, Ash, Gerald R (Jerry), ALABS wrote:
> 
> > > Hi, this is to allow the WG list to weigh in the 
> > > consensus from the meeting.  This email is on the 
> > > DS-TE drafts...
> > 
> > > 
> http://www.ietf.org/internet-drafts/draft-ash-mpls-dste-bcmode
> l-max-alloc-resv-01.txt
> > 
> > > This draft will be revised
> > 
> > Yes, as agreed, I'll add a section on 'assumptions & 
> applicability' to the I-D.
> > 
> > > it was not discussed if it should be re-updated as 
> > > a WG document.  If that is the Jerry's intention, 
> > > he can bring that question to the WG list.
> > 
> > The agreement was to "progress MAR" (my notes), which is 
> consistent with the proposal in my slides to "specify/progress MAR".
> > Also, the meeting minutes say "the way to go forward is to 
> make all of them [BC models] experimental"
> > 
> > Thanks,
> > 'the Jerry'
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> 
> 



From owner-te-wg@ops.ietf.org  Wed Apr  2 14:53:06 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25539
	for <tewg-archive@lists.ietf.org>; Wed, 2 Apr 2003 14:53:06 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 190oJj-000Dey-00
	for te-wg-data@psg.com; Wed, 02 Apr 2003 11:54:39 -0800
Received: from rtp-core-1.cisco.com ([64.102.124.12])
	by psg.com with esmtp (Exim 3.36 #1)
	id 190oJf-000DeP-00; Wed, 02 Apr 2003 11:54:35 -0800
Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79])
	by rtp-core-1.cisco.com (8.12.6/8.12.6) with ESMTP id h32JsXiH002741;
	Wed, 2 Apr 2003 14:54:33 -0500 (EST)
Received: from bifocal.cisco.com (bifocal.cisco.com [161.44.172.150]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id OAA07483; Wed, 2 Apr 2003 14:54:32 -0500 (EST)
Received: from localhost (swallow@localhost) by bifocal.cisco.com (8.8.8-Cisco List Logging/CISCO.WS.1.2) with ESMTP id OAA29131; Wed, 2 Apr 2003 14:54:32 -0500 (EST)
Message-Id: <200304021954.OAA29131@bifocal.cisco.com>
X-Authentication-Warning: bifocal.cisco.com: swallow owned process doing -bs
To: ccamp@ops.ietf.org, te-wg@ops.ietf.org
Reply-To: mpls@uu.net
Subject: Last call in MPLS WG on TC MIB
Date: Wed, 02 Apr 2003 14:54:32 -0500
From: George Swallow <swallow@cisco.com>
X-Spam-Status: No, hits=-8.0 required=5.0
	tests=BAYES_01,X_AUTH_WARNING
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

The MPLS TC MIB is referred to by documents in CCAMP and TE-WG.  This
is to inform you that a last call is in progress in the MPLS WG on

  Definitions of Textual for Multiprotocol Label Switching (MPLS)
    Management
                         
    draft-ietf-mpls-tc-mib-06.txt


The last call closes 4/16 24:00 GMT.  Please make any and all comments
to the MPLS list only (mpls@uu.net).

Thanks,

...George


======================================================================
George Swallow          Cisco Systems                   (978) 936-1398
                        250 Apollo Drive
                        Chelmsford, Ma 01824







From owner-te-wg@ops.ietf.org  Thu Apr  3 16:00:21 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13540
	for <tewg-archive@lists.ietf.org>; Thu, 3 Apr 2003 16:00:21 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 191Bl7-000MPi-00
	for te-wg-data@psg.com; Thu, 03 Apr 2003 12:56:29 -0800
Received: from mail.ee.gatech.edu ([130.207.225.105])
	by psg.com with esmtp (Exim 3.36 #1)
	id 191Bl4-000MPQ-00
	for te-wg@ops.ietf.org; Thu, 03 Apr 2003 12:56:26 -0800
Received: from yamsrv2.ece.gatech.edu (yamsrv2.ece.gatech.edu [130.207.232.10])
	by mail.ee.gatech.edu (8.12.9/8.12.6) with ESMTP id h33KuM1f024401;
	Thu, 3 Apr 2003 15:56:22 -0500 (EST)
Received: from localhost (jau@localhost)
	by yamsrv2.ece.gatech.edu (8.12.0.Beta19/8.12.0.Beta19/Submit) with ESMTP id h33KuKUt029691;
	Thu, 3 Apr 2003 15:56:21 -0500 (EST)
Date: Thu, 3 Apr 2003 15:56:20 -0500 (EST)
From: Jaudelice Cavalcante de Oliveira <jau@ece.gatech.edu>
To: "Matthew Elvey (FM)" <matthew@elvey.fastmail.fm>
cc: te-wg@ops.ietf.org
Subject: Re: draft-deoliveira-diff-te-preemption-01.txt - 2 comments.
In-Reply-To: <3E7F5151.2040601@elvey.fastmail.fm>
Message-ID: <Pine.GSO.4.53.0304031507320.25957@yamsrv2.ece.gatech.edu>
References: <Pine.GSO.4.53.0303141359370.7685@yamsrv2.ece.gatech.edu>
 <3E7F5151.2040601@elvey.fastmail.fm>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-new
X-Spam-Status: No, hits=-31.7 required=5.0
	tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES,USER_AGENT_PINE
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Hello Matthew,

Thanks for your comments. See below.

As you pointed out, the draft -01 is now available at:

http://www.ietf.org/internet-drafts/draft-deoliveira-diff-te-preemption-01.txt


> Very interesting.
>
> 1)Possible spellings: analyzed (US) or analysed (British), but not
> analized.
> accommodate not accomodate ; achieved not acchieved ; successfully not
> succesfully.

Sorry for those... Sometimes the fact that Portuguese and English words
have similar spelling makes me confuse them...

> 2) I have a comment regarding the heuristics. I may be in over my head
> with this comment, but here goes. Summary: It seems to me that the
> heuristic will inadvertently prioritize high-bandwidth traffic over
> low-bandwidth traffic. The draft states that "gamma (b(l)-r)^2 penalizes
> a choice of an LSP to be preempted that would result in high bandwidth
> wastage."

r is the bandwidth needed to setup the high-priority LSP. The requested
bandwidth.

b(l) is the bandwidth of preemptable LSP l.

(b(l)-r)^2 will give LSPs with bandwidth closer to "r" a smaller "cost".
So if "r" is large, say 100, LSPs with bandwidth closer to 100 will be
preferred. If "r" is small, say 2, LSPs with bandwidth closer to 2 will be
preferred. So, the heuristic does not necessarily prefers low bandwidth
candidate LSPs.

> This necessarily implies that low-bandwidth LSPs are more vulnerable to
> being preempted than high-bandwidth LSPs of otherwise equal priority.
> This strikes me as not sensible*.

As explained above, the heuristic does not necessarily prefer low
bandwidth LSPs but rather the ones whose bandwidth is closer to the
requested value "r".

> Beta would tend to counteract this bias, but I can foresee where it
> would often be ineffective, e.g. where a low-bandwidth LSP or a
> high-bandwidth LSP could be preempted to make room for a high priority
> low-bandwidth LSP.  Beta is a constant (=1), and the low-bandwidth LSP
> will be preempted (bad).

I am not sure I understood your concern in the example above. Beta
minimizes the number of LSPs selected for preemption. If priority and
bandwidth are also taken into account, the heuristic will try to find a
small number of LSPs with low priority and bandwidth close to the
requested value "r".

>  In your first example, would an l17(b,p,y = 300,6,2) not be preempted,
> even using 'balanced' coefficients alpha=1, beta=1 and gamma=0.01?

l17 would be preferred from preemption if the bandwidth request for the
high-priority LSP is close to 300.

> In a state of bandwidth shortage, mabye it makes more sense not to weigh
> bandwidth wastage at all.  It seems to me that the gamma component
> should be eliminated.

The gamma component was included in order to control the preempted
bandwidth. E.g. Preempting LSPs that have bandwidth much larger that the
required one (r) might result in a high probability of not finding an
alternative route for such large preempted LSP (the rejected rate would
increase).

> I've continued reading and I see that this is the PN policy of 6.2.2. I
> would argue that PN is better than PB. The wasted bandwidth of this
> static moment in time should not be considered in evaluating the
> policies. (Really, it's not 'wasted' at all; it's being 'virtually
> reserved' (if I may call it that) for low-bandwidth LSPs, which, since
> we're in a state of bandwidth shortage, are likely to appear shortly.)

I believe the preference of PN over PB depends on the provider's interest.
I do agree that the extra bandwidth preempted could be used in the future,
but again it could become hard to reroute large LSPs.

> *E.g. a dozen users communicating using low-bandwidth communication,
> (e.g. something text based such as email or chat) should be rewarded
> over a pair of bandwidth hogs using videoconferencing.

I agree as long as the requested bandwidth is similar to the
videoconferencing, otherwise it could happen that an alternative path is
not available for such large LSP.

Cheers,

Jaudelice.



From owner-te-wg@ops.ietf.org  Thu Apr  3 17:57:29 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18009
	for <tewg-archive@lists.ietf.org>; Thu, 3 Apr 2003 17:57:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 191DcK-0002Rc-00
	for te-wg-data@psg.com; Thu, 03 Apr 2003 14:55:32 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 191DcB-0002RE-00
	for te-wg@ops.ietf.org; Thu, 03 Apr 2003 14:55:23 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h33MtLij019568
	for <te-wg@ops.ietf.org>; Thu, 3 Apr 2003 17:55:22 -0500 (EST)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh3i.attrh.att.com (6.5.032)
        id 3E85156000025BE7; Thu, 3 Apr 2003 17:55:21 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: draft-ash-mpls-dste-bcmodel-max-alloc-resv -> WG document?
Date: Thu, 3 Apr 2003 16:54:32 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A670E@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: draft-ash-mpls-dste-bcmodel-max-alloc-resv -> WG document?
Thread-Index: AcL5UK3s6ndw3ptWRAGj7Qr34qJDrAA32o3w
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.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.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-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 RAA18009

Sanjay,

Thanks for your comments, please see responses below.

Thanks,
Jerry

> Technical (Scope):
> (i) The aim here is to defined a BC Model and not a 
> DSTE-Solution. 

There is no intent to change the DSTE solution.  MAR is an extension of MAM which fits completely within the existing DSTE solution, as does MAM (and RDM).

> i.e define the BC Model as per the DSTE requirement document: 
> (a) the maximum number of Bandwidth Constraints

I think it already does that, e.g., in Section 2 it says "Up to 8 Bandwidth Constraints (MaxBC = 8) are supported and they are referred to as BCb, 0 <= b <= MaxBC-1 = 7."  

> (b) which CTs each Bandwidth Constraint applies to and how

OK, I'll clarify further along the lines of your suggestion.
 
> The draft in its present form, goes way beyond the scope.
> For example: 
> The proposed solution (a) expects modifications to the 
> DSTE Solution 

As I said above, MAR fits completely within the existing DSTE solution, no extension is intended or proposed.

> (ii) introduces CT priority concept that
> is not in DSTE-requirement

Priority, as discussed in the I-D, fits within the existing DSTE solution, and uses setup/holding priority capabilities as is.  This will be clarified in the next revision.

> Editorial: 
> (i) Personally, I think this draft needs some editorial 
> changes to state the solution more clearly [explicitly 
> and succinctly state the rules/necessary configurations/
> protocol extensions etc.]

OK.  I'll clarify further along the lines of your suggestions.

> (ii) The draft also needs to define the term it uses 
> precisely (and use them consistently]
> Example: "bandwidth-in-progress","bandwidth-in-use", 
> 	   "reserved-bandwidth", "BWalloc" ... ...

OK.  I'll include more definitions in Section 2.

> (iii) Separate specification from the examples

I think these are mostly separate already.  Section 3 contains the specification, Section 4 contains the examples (ANNEX A contains the analysis).



From owner-te-wg@ops.ietf.org  Mon Apr  7 10:04: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 KAA20057
	for <tewg-archive@lists.ietf.org>; Mon, 7 Apr 2003 10:04:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192XBV-000NNj-00
	for te-wg-data@psg.com; Mon, 07 Apr 2003 14:01:17 +0000
Received: from p-mail1.rd.francetelecom.com ([195.101.245.15])
	by psg.com with smtp (Exim 3.36 #1)
	id 192XBT-000NNV-00
	for te-wg@ops.ietf.org; Mon, 07 Apr 2003 07:01:15 -0700
Received: from parsmtp1.rd.francetelecom.com ([10.193.117.128]) by p-mail1 with InterScan Messaging Security Suite; Mon, 07 Apr 2003 16:00:28 +0200
Received: from lanmhs50.rd.francetelecom.fr ([10.193.21.52]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 7 Apr 2003 16:00:01 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
Date: Mon, 7 Apr 2003 16:00:01 +0200
Message-ID: <C691E039D3895C44AB8DFD006B950FB4011A2454@lanmhs50.rd.francetelecom.fr>
Thread-Topic: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
Thread-Index: AcL02RZ/koGUkqXQRIWhh23AgY3hcwINF/NQ
From: "BOUCADAIR Mohamed FTRD/DMI/CAE" <mohamed.boucadair@rd.francetelecom.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 07 Apr 2003 14:00:01.0828 (UTC) FILETIME=[FBA7DE40:01C2FD0D]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-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 KAA20057

Hi all,
 In my opinion, a) and b) should progress independently.
Regards,
Med 

-----Message d'origine-----
De : Jim Boyle [mailto:jboyle@pdnets.com]
Envoye : vendredi 28 mars 2003 03:49
A : te-wg@ops.ietf.org
Objet : (a) Inter-Area, (b) Inter-AS (c) both (d) neither



At the meeting, as you can tell in the minutes, it was clear to all that

there is plenty support to move forward on inter-as requirements (there 
was at IETF55 too).

There was a clear difference of opinion on how to do this though.

Most felt the best approach would be to adopt 

http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-02.t
xt
(or -03)

as a WG document.  This will put more focus and review on it, and in 
general keep this work from stalling in discussion ad naseum.

The counter view (held by me, and a handful of others) was that there
are 
clearly some that are also interested in multi-area TE, and that we
should 
consider working toward a WG requirements document that 
- outlined the possible scope, and defined the scope of the draft
- presented flushed out, coherent requirements

At a minimum, I felt that we should not move anything to a WG document 
until it was clear how this fitted into our charter, and had some 
discussion on the list confirming the general consensus of the meeting 
(which again, was to move forward independently on inter-as
requirements, 
with draft-zhang becoming a WG document, and focal point of this
effort).

In discussion with Bert, it looks like the charter is not an
obstacle, in fact as Raymond pointed out, it currently covers this:

"The working group may also consider the problems of traffic engineering

across autonomous systems boundaries."

I'm just kidding about the (a) (b) (c) (d) thing, feel free to just tell

it like it is :)

thanks,

Jim







From owner-te-wg@ops.ietf.org  Mon Apr  7 12:17: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 MAA25266
	for <tewg-archive@lists.ietf.org>; Mon, 7 Apr 2003 12:17:33 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192ZJj-00088z-00
	for te-wg-data@psg.com; Mon, 07 Apr 2003 16:17:55 +0000
Received: from pmesmtp01.wcom.com ([199.249.20.1])
	by psg.com with esmtp (Exim 3.36 #1)
	id 192ZJg-00088n-00
	for te-wg@ops.ietf.org; Mon, 07 Apr 2003 09:17:52 -0700
Received: from pmismtp06.wcomnet.com ([166.38.62.54])
 by firewall.wcom.com (Iplanet MTA 5.2)
 with ESMTP id <0HCZ00ANHEG9GW@firewall.wcom.com> for te-wg@ops.ietf.org; Mon,
 07 Apr 2003 16:14:33 +0000 (GMT)
Received: from pmismtp06.wcomnet.com by pmismtp06.wcomnet.com
 (iPlanet Messaging Server 5.1 HotFix 0.7 (built May  7 2002))
 with SMTP id <0HCZ00301EG9CH@pmismtp06.wcomnet.com>; Mon,
 07 Apr 2003 16:14:33 +0000 (GMT)
Received: from dmcdysan ([166.32.199.64])
 by pmismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7
 2002)) with SMTP id <0HCZ000EPEG9RW@pmismtp06.wcomnet.com>; Mon,
 07 Apr 2003 16:14:33 +0000 (GMT)
Date: Mon, 07 Apr 2003 12:12:26 -0400
From: Dave McDysan <dave.mcdysan@wcom.com>
Subject: RE: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
In-reply-to: <9473683187ADC049A855ED2DA739ABCA0A6F64@KCCLUST06EVS1.ugd.att.com>
To: Jim Boyle <jboyle@pdnets.com>, te-wg@ops.ietf.org
Message-id: <NBBBLDAKOPKFLNKDGDLGGECNIIAA.dave.mcdysan@wcom.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4920.2300
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-Spam-Status: No, hits=-21.8 required=5.0
	tests=BAYES_01,IN_REP_TO,MSGID_GOOD_EXCHANGE,ORIGINAL_MESSAGE
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I believe I agree with the sentiment of Jerry's note, but would say that we
are not only looking for synergies; but would aslo include assumptions or
implications in the coordination of these efforts. For example, I believe
that the draft on (b) inter-AS requirements makes some assumptions on what
(a) inter-area must do within a multi-area AS.

I suggest that (b) can advance independently as long as these implications
are assumptions are captured as part of the requirements documentation
process.

Dave

-----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: Monday, March 31, 2003 11:22 AM
To: Jim Boyle
Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
Subject: RE: (a) Inter-Area, (b) Inter-AS (c) both (d) neither


I agree that we should progress a) and b) independently, but take note of
any possible synergies.

Also, icw item a):

Sudheer> Should we revive our inter-area drafts now
Jim> yes, please do.

Several of us collaborated on multi-area TE requirements a while back:
http://www1.ietf.org/mail-archive/ietf-announce/Current/msg15882.html
has expired, but is still available at:
http://www.watersprings.org/links/mlr/id/draft-ash-multi-area-te-reqmts-01.t
xt

This can be updated and progressed if there is interest.

Thanks,
Jerry




From owner-te-wg@ops.ietf.org  Mon Apr  7 17:44: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 RAA06854
	for <tewg-archive@lists.ietf.org>; Mon, 7 Apr 2003 17:44:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192eP7-000DUJ-00
	for te-wg-data@psg.com; Mon, 07 Apr 2003 21:43:49 +0000
Received: from [64.221.212.135] (helo=ns2.vivacenetworks.com)
	by psg.com with smtp (Exim 3.36 #1)
	id 192eNL-000DNk-00
	for te-wg@ops.ietf.org; Mon, 07 Apr 2003 14:41:59 -0700
Received: from amalisxp.vivacenetworks.com ([10.120.0.2]) by vivacenetworks.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 7 Apr 2003 14:41:54 -0700
Message-Id: <5.2.1.1.0.20030407173957.04035a20@po1.vivacenetworks.com>
X-Sender: vivacenet\amalis@po1.vivacenetworks.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.2.1
Date: Mon, 07 Apr 2003 17:41:32 -0400
To: Jim Boyle <jboyle@pdnets.com>, te-wg@ops.ietf.org
From: "Andrew G. Malis" <Andy.Malis@vivacenetworks.com>
Subject: Re: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
In-Reply-To: <3E895871.4070609@infonet.fundp.ac.be>
References: <Pine.LNX.4.44.0303272131330.21532-100000@fido.nc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 07 Apr 2003 21:41:55.0346 (UTC) FILETIME=[82331F20:01C2FD4E]
X-Spam-Status: No, hits=-29.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,
	      REPLY_WITH_QUOTES
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

I also agree they should be progressed separately, with draft-zhang adopted 
as a WG draft.

Thanks,
Andy

------

At 4/1/2003 11:14 AM +0200, Cristel Pelsser wrote:

>Dear all,
>
>I also think that (a) and (b) should progress separately.
>
>Cristel
>
>Jim Boyle wrote:
>
>>At the meeting, as you can tell in the minutes, it was clear to all that 
>>there is plenty support to move forward on inter-as requirements (there 
>>was at IETF55 too).
>>
>>There was a clear difference of opinion on how to do this though.
>>
>>Most felt the best approach would be to adopt
>>http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-02.txt
>>(or -03)
>>
>>as a WG document.  This will put more focus and review on it, and in 
>>general keep this work from stalling in discussion ad naseum.
>>
>>The counter view (held by me, and a handful of others) was that there are 
>>clearly some that are also interested in multi-area TE, and that we 
>>should consider working toward a WG requirements document that - outlined 
>>the possible scope, and defined the scope of the draft
>>- presented flushed out, coherent requirements
>>
>>At a minimum, I felt that we should not move anything to a WG document 
>>until it was clear how this fitted into our charter, and had some 
>>discussion on the list confirming the general consensus of the meeting 
>>(which again, was to move forward independently on inter-as requirements, 
>>with draft-zhang becoming a WG document, and focal point of this effort).
>>
>>In discussion with Bert, it looks like the charter is not an
>>obstacle, in fact as Raymond pointed out, it currently covers this:
>>
>>"The working group may also consider the problems of traffic engineering 
>>across autonomous systems boundaries."
>>
>>I'm just kidding about the (a) (b) (c) (d) thing, feel free to just tell 
>>it like it is :)
>>
>>thanks,
>>
>>Jim
>>
>>
>
>
>
>
>
>




From owner-te-wg@ops.ietf.org  Mon Apr  7 23:53:51 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15906
	for <tewg-archive@lists.ietf.org>; Mon, 7 Apr 2003 23:53:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192kAK-00085s-00
	for te-wg-data@psg.com; Tue, 08 Apr 2003 03:52:56 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 192kAG-00085S-00; Mon, 07 Apr 2003 20:52:52 -0700
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 h383ql4g028479;
	Mon, 7 Apr 2003 23:52:47 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h383qkYQ028475;
	Mon, 7 Apr 2003 23:52:46 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 7 Apr 2003 23:52:46 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: mpls@uu.net, <ccamp@ops.ietf.org>, <ospf@discuss.microsoft.com>,
        <isis-wg@ietf.org>
cc: te-wg@ops.ietf.org
Subject: Notice of WG last call on Diff Serv TE Protocol draft in TEWG
Message-ID: <Pine.LNX.4.44.0304072225500.28304-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.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


In May 2001 the TEWG adopted the development of the requirements and 
necessary protocol extensions for Diff-Serv TE.  Upon completion, TEWG 
was to notify the various protocol WGs of the proposal to allow review 
of the proposed protocol changes (if any).  This note serves that purpose.

Please find the pointer for the protocol specification draft below and 
review the proposed changes required in the routing and signaling 
protocols.  

A WG last call on the protocol draft will start by separate email to the 
TEWG.  Be sure to follow-up with any discussion to the te-wg list.

http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-03.txt

It specifies extensions outlined as follows:
- IGP Reuse of unreserved bandwidth sub-tlv to carry 
	BW available per TE-Class
- IGP Optional use bandwidth constraints sub-tlv
- IGP Optional use local overbooking multiplier sub-tlv
- RSVP Class Type Object for signaling class-types other than 0.
- RSVP Diffserv TE error codes

The protocol supports the use of a variety of different bandwidth 
constraint models.  The following drafts are examples listed here for 
reference only.

http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.txt
http://www.ietf.org/internet-drafts/draft-lefaucheur-diff-te-mam-00.txt
http://www.ietf.org/internet-drafts/draft-ash-mpls-dste-bcmodel-max-alloc-resv-01.txt

Also for reference, the requirements are developed and with RFC-ED now. 

http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-reqts-07.txt







From owner-te-wg@ops.ietf.org  Mon Apr  7 23:54:21 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15928
	for <tewg-archive@lists.ietf.org>; Mon, 7 Apr 2003 23:54:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192kDW-0008k0-00
	for te-wg-data@psg.com; Tue, 08 Apr 2003 03:56:14 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 192kDU-0008jo-00
	for te-wg@ops.ietf.org; Mon, 07 Apr 2003 20:56:12 -0700
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 h383uB4g028486
	for <te-wg@ops.ietf.org>; Mon, 7 Apr 2003 23:56:11 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h383uBgv028482
	for <te-wg@ops.ietf.org>; Mon, 7 Apr 2003 23:56:11 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 7 Apr 2003 23:56:11 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Message-ID: <Pine.LNX.4.44.0304072352490.28304-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.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-03.txt

This is WG last call for this draft to be advanced standards track.
Since notice was sent to other WGs for review, we will take 3 weeks.

Last call for this draft closes 4/28.

thanks,

Jim Boyle





From owner-te-wg@ops.ietf.org  Tue Apr  8 04:10: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 EAA02066
	for <tewg-archive@lists.ietf.org>; Tue, 8 Apr 2003 04:10:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192oAr-000MbL-00
	for te-wg-data@psg.com; Tue, 08 Apr 2003 08:09:45 +0000
Received: from mx1.sita.int ([57.250.224.237])
	by psg.com with esmtp (Exim 3.36 #1)
	id 192oAn-000Mb4-00
	for te-wg@ops.ietf.org; Tue, 08 Apr 2003 01:09:41 -0700
Received: from nice1.nce.sita.int (nice1.nce.sita.int [57.6.189.38])
	by mx1.sita.int  with ESMTP id h3889cd8005950;
	Tue, 8 Apr 2003 08:09:39 GMT
Subject: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
To: te-wg@ops.ietf.org
Cc: jboyle@pdnets.com
X-Mailer: Lotus Notes Release 5.0.7  March 21, 2001
Message-ID: <OF99401F50.EEF4F134-ONC1256D02.002CB3FB@nce.sita.int>
From: Pierre.Merckx@equant.com
Date: Tue, 8 Apr 2003 10:09:37 +0200
X-MIMETrack: Serialize by Router on Nice1/Nice/SITA/WW(Release 5.0.9a |January 7, 2002) at
 04/08/2003 10:09:39 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-5.6 required=5.0
	tests=BAYES_01,NO_REAL_NAME
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Jim,

My preference is to have 2 separate drafts (I suppose it will be faster,
more
adapted  and more precise for each environement).
Brgds

Pierre


----- Forwarded by Pierre Merckx/France/Equant on 28/03/03 16:09 -----
                                                                                                                           
            Jim Boyle <jboyle@pdnets.com>                                                                                  
            Sent by:                                                                                                       
            owner-te-wg@ops.ietf.org           To: te-wg@ops.ietf.org                                                      
            28/03/03 03:49                     cc:                                                                         
                                               bcc:                                                                        
                                               Subject:  (a) Inter-Area, (b) Inter-AS (c) both (d) neither                 
                                                                                                                           
                                                                                                                           




At the meeting, as you can tell in the minutes, it was clear to all that
there is plenty support to move forward on inter-as requirements (there
was at IETF55 too).

There was a clear difference of opinion on how to do this though.

Most felt the best approach would be to adopt

http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-02.txt
(or -03)

as a WG document.  This will put more focus and review on it, and in
general keep this work from stalling in discussion ad naseum.

The counter view (held by me, and a handful of others) was that there are
clearly some that are also interested in multi-area TE, and that we should
consider working toward a WG requirements document that
- outlined the possible scope, and defined the scope of the draft
- presented flushed out, coherent requirements

At a minimum, I felt that we should not move anything to a WG document
until it was clear how this fitted into our charter, and had some
discussion on the list confirming the general consensus of the meeting
(which again, was to move forward independently on inter-as requirements,
with draft-zhang becoming a WG document, and focal point of this effort).

In discussion with Bert, it looks like the charter is not an
obstacle, in fact as Raymond pointed out, it currently covers this:

"The working group may also consider the problems of traffic engineering
across autonomous systems boundaries."

I'm just kidding about the (a) (b) (c) (d) thing, feel free to just tell
it like it is :)

thanks,

Jim












From owner-te-wg@ops.ietf.org  Tue Apr  8 05:44: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 FAA03551
	for <tewg-archive@lists.ietf.org>; Tue, 8 Apr 2003 05:44:12 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192ped-000PeW-00
	for te-wg-data@psg.com; Tue, 08 Apr 2003 09:44:35 +0000
Received: from byd.ocn.ad.jp ([203.139.162.147])
	by psg.com with esmtp (Exim 3.36 #1)
	id 192pea-000PeC-00
	for te-wg@ops.ietf.org; Tue, 08 Apr 2003 02:44:32 -0700
Received: from ibm (localhost [127.0.0.1])
	by byd.ocn.ad.jp (8.8.8/3.6W) with ESMTP id SAA27994;
	Tue, 8 Apr 2003 18:44:09 +0900 (JST)
Date: Tue, 08 Apr 2003 18:44:33 +0900
From: Yuichi Ikejiri <y.ikejiri@ntt.com>
To: "Jim Boyle" <jboyle@pdnets.com>
Subject: Re: (a) Inter-Area, (b) Inter-AS (c) both (d) neither
Cc: te-wg@ops.ietf.org
In-Reply-To: <Pine.LNX.4.44.0303272131330.21532-100000@fido.nc.rr.com>
References: <Pine.LNX.4.44.0303272131330.21532-100000@fido.nc.rr.com>
Message-Id: <20030408183500.E093.Y.IKEJIRI@ntt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.00.03
X-Spam-Status: No, hits=-33.1 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      QUOTE_TWICE_1,REFERENCES,REPLY_WITH_QUOTES
	autolearn=ham	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I think that (a) and (b) should be discussed and discussed independently.
There would be some different requirements in two environment from 
SP's view, so separate discussion could make things clear.

Regards,

Yuichi
NTT Communications Corporation.

On Thu, 27 Mar 2003 21:49:07 -0500 (EST)
"Jim Boyle" <jboyle@pdnets.com> wrote:

> 
> At the meeting, as you can tell in the minutes, it was clear to all that 
> there is plenty support to move forward on inter-as requirements (there 
> was at IETF55 too).
> 
> There was a clear difference of opinion on how to do this though.
> 
> Most felt the best approach would be to adopt 
> 
> http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-02.txt
> (or -03)
> 
> as a WG document.  This will put more focus and review on it, and in 
> general keep this work from stalling in discussion ad naseum.
> 
> The counter view (held by me, and a handful of others) was that there are 
> clearly some that are also interested in multi-area TE, and that we should 
> consider working toward a WG requirements document that 
> - outlined the possible scope, and defined the scope of the draft
> - presented flushed out, coherent requirements
> 
> At a minimum, I felt that we should not move anything to a WG document 
> until it was clear how this fitted into our charter, and had some 
> discussion on the list confirming the general consensus of the meeting 
> (which again, was to move forward independently on inter-as requirements, 
> with draft-zhang becoming a WG document, and focal point of this effort).
> 
> In discussion with Bert, it looks like the charter is not an
> obstacle, in fact as Raymond pointed out, it currently covers this:
> 
> "The working group may also consider the problems of traffic engineering 
> across autonomous systems boundaries."
> 
> I'm just kidding about the (a) (b) (c) (d) thing, feel free to just tell 
> it like it is :)
> 
> thanks,
> 
> Jim
> 
> 
> 




From owner-te-wg@ops.ietf.org  Tue Apr  8 10:54: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 KAA16285
	for <tewg-archive@lists.ietf.org>; Tue, 8 Apr 2003 10:54:36 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192uRF-000HoT-00
	for te-wg-data@psg.com; Tue, 08 Apr 2003 14:51:05 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 192uRD-000HoH-00
	for te-wg@ops.ietf.org; Tue, 08 Apr 2003 07:51:03 -0700
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 h38Ep04g030033
	for <te-wg@ops.ietf.org>; Tue, 8 Apr 2003 10:51:00 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h38Ep0Kq030029
	for <te-wg@ops.ietf.org>; Tue, 8 Apr 2003 10:51:00 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Tue, 8 Apr 2003 10:51:00 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Message-ID: <Pine.LNX.4.44.0304081048320.29948-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.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk



http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.txt

This is WG last call for this draft to be advanced as expiremental RFC.

Last call ends in 2 weeks (4/22).

thanks,

Jim Boyle






From owner-te-wg@ops.ietf.org  Tue Apr  8 11:28:06 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18829
	for <tewg-archive@lists.ietf.org>; Tue, 8 Apr 2003 11:28:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 192v2N-000Jhp-00
	for te-wg-data@psg.com; Tue, 08 Apr 2003 15:29:27 +0000
Received: from [193.205.242.5] (helo=nausicaa.coritel.it)
	by psg.com with esmtp (Exim 3.36 #1)
	id 192v2J-000JhZ-00
	for te-wg@ops.ietf.org; Tue, 08 Apr 2003 08:29:23 -0700
Received: from Hawking (host22-170.pool8173.interbusiness.it [81.73.170.22])
	by nausicaa.coritel.it (8.11.2/8.11.2) with SMTP id h38FSDh04254;
	Tue, 8 Apr 2003 17:28:23 +0200
Message-ID: <012c01c2fde2$8ac815c0$99256497@Coritel>
From: "Alessio Liburdi" <liburdi@coritel.it>
To: "Ash, Gerald R \(Jerry\), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
Subject: clarifications on MAR
Date: Tue, 8 Apr 2003 17:21:07 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0129_01C2FDF3.3E039E60"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Status: No, hits=-5.4 required=5.0
	tests=BAYES_10,HTML_40_50
	version=2.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0129_01C2FDF3.3E039E60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Jerry and all

I have a question regarding =
draft-ash-mpls-dste-bcmodel-max-alloc-resv-01 because
i don't understand the action of bandwidth reservation mechanism.


You write:

Bandwidth allocated to individual CTs is protected as=20
needed but otherwise shared. Under normal non-congested network=20
conditions, all CTs/services fully share all available bandwidth. When=20
congestion occurs for a particular CTi, bandwidth reservation acts to=20
prohibit traffic from other CTs from seizing the allocated capacity for=20
CTi

Now look at this example: I suppose 3 CTs all with normal priority

CT0-BWalloc =3D 30
CT1-BWalloc =3D 20
CT2-BWalloc =3D 20
Reserved Bandwidth (RBW) =3D 10

I suppose that :
CT0 has taken 80 units of bandwidth
CT1 has taken 5 units of bandwidth
CT2 has taken 0 units of bandwidth

Let'me say a flow arrives for CT2 needing 20 units of bandwidth (i.e., =
DBW=20
=3D 5). I need to decide based on Table 2 and Table 1 whether to admit=20
this flow or not.

Table 2  says Bandwidth -Not -Allowed

In this situation is the request for CT2 refuse or not? How bandwidth =
reservation acts to=20
prohibit traffic from other CTs from seizing the allocated capacity for =
CT2 ?
I would understand if CT0 frees band so I can accept the request for =
CT2.


Thank you for the clarifications

Alessio


------=_NextPart_000_0129_01C2FDF3.3E039E60
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi Jerry and all</FONT></DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT face=3DArial=20
size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I have a question regarding=20
draft-ash-mpls-dste-bcmodel-max-alloc-resv-01 because</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>i don't understand the action of =
bandwidth=20
reservation mechanism.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2><FONT face=3DArial=20
size=3D2></FONT></FONT></FONT>&nbsp;</DIV><FONT size=3D2>
<DIV><FONT face=3DArial>You write:</FONT></DIV>
<DIV><EM><FONT face=3DArial></FONT></EM>&nbsp;</DIV>
<DIV><EM><FONT face=3DArial>Bandwidth allocated to individual CTs is =
protected=20
as</FONT> </EM></DIV>
<DIV><EM><FONT face=3DArial>needed but otherwise shared. Under normal=20
non-congested network</FONT> </EM></DIV>
<DIV><EM><FONT face=3DArial>conditions, all CTs/services fully share all =
available=20
bandwidth. When</FONT> </EM></DIV>
<DIV><EM><FONT face=3DArial>congestion occurs for a particular CTi, =
bandwidth=20
reservation acts to</FONT> </EM></DIV>
<DIV><EM><FONT face=3DArial>prohibit traffic from other CTs from seizing =
the=20
allocated capacity for</FONT> </EM></DIV>
<DIV><FONT face=3DArial><EM>CTi</EM></FONT></DIV></FONT>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now look at this example: I suppose 3 =
CTs all with=20
normal priority</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV><FONT size=3D2>
<DIV><FONT face=3DArial>CT0-BWalloc =3D 30</FONT></DIV>
<DIV><FONT face=3DArial>CT1-BWalloc =3D 20</FONT></DIV>
<DIV><FONT face=3DArial>CT2-BWalloc =3D 20</FONT></DIV>
<DIV><FONT face=3DArial>Reserved Bandwidth (RBW) =3D 10</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial>I suppose that :</FONT></DIV>
<DIV><FONT face=3DArial>CT0 has taken 80 units of bandwidth</FONT></DIV>
<DIV><FONT face=3DArial>CT1 has taken&nbsp;5 units of =
bandwidth</FONT></DIV>
<DIV><FONT face=3DArial>CT2 has taken 0 units of bandwidth</FONT></DIV>
<DIV><FONT face=3DArial></FONT>&nbsp;</DIV><FONT face=3DArial><FONT =
size=3D2>
<DIV>Let'me say a flow arrives for CT2 needing&nbsp;20 units of =
bandwidth (i.e.,=20
DBW </DIV>
<DIV>=3D 5).&nbsp;I need to decide based on Table 2 and Table 1 whether =
to admit=20
</DIV>
<DIV>this flow or not.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Table 2&nbsp; says Bandwidth -Not -Allowed</DIV>
<DIV>&nbsp;</DIV>
<DIV>In this situation is the&nbsp;request&nbsp;for CT2 refuse or not? =
How=20
bandwidth reservation acts to=20
<DIV><FONT face=3DArial>prohibit traffic from other CTs from seizing the =
allocated=20
capacity for</FONT> <FONT face=3DArial>CT2 ?</FONT></DIV>
<DIV>I would understand if CT0 frees band so&nbsp;I can accept the =
request for=20
CT2.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thank you for the clarifications</DIV>
<DIV>&nbsp;</DIV>
<DIV>Alessio</DIV></DIV></FONT></FONT></FONT>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0129_01C2FDF3.3E039E60--




From owner-te-wg@ops.ietf.org  Fri Apr 11 15:10: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 PAA25555
	for <tewg-archive@lists.ietf.org>; Fri, 11 Apr 2003 15:10:07 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1943pg-000DqX-00
	for te-wg-data@psg.com; Fri, 11 Apr 2003 19:05:04 +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 1943pc-000DpP-00
	for te-wg@ops.ietf.org; Fri, 11 Apr 2003 12:05:00 -0700
Message-ID: <EB5FFC72F183D411B3820006295734290125F5DE@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Jim Boyle'" <jboyle@pdnets.com>, te-wg@ops.ietf.org
Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Date: Fri, 11 Apr 2003 15:04:51 -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.50
X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Section 5.1, page 10:

  "With DS-TE, the existing "Maximum Reservable Bw" sub-TLV is retained 
  with a generalized semantic so that it MUST now be interpreted as 
  Bandwidth Constraint 0 (BC0)."

also Section 5.1, page 10:

  "A DS-TE LSR which does advertise Bandwidth Constraints, MAY also 
  include the existing "Maximum Reservable Bw" sub-TLV. This may be 
  useful in migration situations where some LSRs in the network are not 
  DS-TE capable (see Appendix C) and thus do not understand the new 
  "Bandwidth Constraints" sub-TLV. In that case, the DS-TE LSR MUST set 
  the value of the "Maximum Reservable Bw" sub-TLV to the same value as 
  the one for BC0 encoded in the "Bandwidth Constraints" sub-TLV. 
   
  A DS-TE LSR receiving both the old "Maximum Reservable Bw" sub-TLV 
  and the new "Bandwidth Constraints" sub-TLV for a given link MAY 
  ignore the "Maximum Reservable Bw" sub-TLV." 

The above statements are implying that the "Maximum Reservable Bw" sub-TLV
is redundant in the presence of Bandwidth Constraints. Furthermore, they
indicate that BC0 has semantics of the maximum reservable bandwidth. This
could be true for the RD model. However it is clearly not true for other
models. Therefore these statements should be removed from the specification
or, even better, replaced with something along the following lines:

  The "Maximum Reservable Bw" sub-TLV represents the aggregate bandwidth
  constraint of the link and as such complements the advertised Bandwidth
  Constraints.
  

Section 10.2, page 20:

  "A DS-TE LSR MUST support the following admission control rule: 
   
  Regardless of how the admission control algorithm actually computes 
  the unreserved bandwidth for TE-Class[i] for one of its local link, 
  an LSP of bandwidth B, of set-up preemption priority p and of Class-
  Type CTc is admissible on that link iff: 
   
       B <= unreserved bandwidth for TE-Class[i], AND 
       B <= Max Link Bandwidth 
           
        Where  
            
        - TE-Class [i] maps to  < CTc , p > in the LSR's configured TE-
          Class mapping 
        - Max Link Bandwidth is the maximum link bandwidth configured 
          on the link and advertised in IGP." 


"Max Link Bandwidth" should be replaced with "Maximum
Reservable Bandwidth".


Section 10.3.4, page 22

  "Regardless of how the admission control algorithm actually computes 
  the unreserved bandwidth for TE-Class[i] for one of its local link, 
  an LSP of bandwidth B, of set-up preemption priority p and of Class-
  Type CTc is admissible on that link iff: 
   
       (i)  B <= unreserved bandwidth for TE-Class[i], AND 
       (ii) B <= Max Link Bandwidth 
           
        Where  
            
        - TE-Class [i] maps to  < CTc , p > in the LSR's configured TE-
          Class mapping 
        - Max Link Bandwidth is the maximum link bandwidth configured 
          on the link and advertised in IGP." 

"Max Link Bandwidth" should be replaced with "Maximum
Reservable Bandwidth".


Dimitry



> -----Original Message-----
> From: Jim Boyle [mailto:jboyle@pdnets.com]
> Sent: Monday, April 07, 2003 11:56 PM
> To: te-wg@ops.ietf.org
> Subject: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
> 
> 
> 
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-pr
> oto-03.txt
> 
> This is WG last call for this draft to be advanced standards track.
> Since notice was sent to other WGs for review, we will take 3 weeks.
> 
> Last call for this draft closes 4/28.
> 
> thanks,
> 
> Jim Boyle
> 
> 
> 



From owner-te-wg@ops.ietf.org  Thu Apr 17 07:34: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 HAA16306
	for <tewg-archive@lists.ietf.org>; Thu, 17 Apr 2003 07:34:18 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1967Zd-000HfM-00
	for te-wg-data@psg.com; Thu, 17 Apr 2003 11:29:01 +0000
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 1967ZH-000Hf3-00
	for te-wg@ops.ietf.org; Thu, 17 Apr 2003 11:28:39 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15757;
	Thu, 17 Apr 2003 07:25:57 -0400 (EDT)
Message-Id: <200304171125.HAA15757@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-00.txt
Date: Thu, 17 Apr 2003 07:25:57 -0400
X-Spam-Status: No, hits=-3.5 required=5.0
	tests=BAYES_01,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		: Max Allocation with Reservation Bandwidth Constraint  
                          Model for MPLS/DiffServ TE & Performance Comparisons
	Author(s)	: J. Ash
	Filename	: draft-ietf-tewg-diff-te-mar-00.txt
	Pages		: 0
	Date		: 2003-4-16
	
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-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-mar-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-mar-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-4-16135625.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Thu Apr 17 08:34:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19184
	for <tewg-archive@lists.ietf.org>; Thu, 17 Apr 2003 08:34:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1968bO-000Kku-00
	for te-wg-data@psg.com; Thu, 17 Apr 2003 12:34:54 +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 1968au-000Kii-00
	for te-wg@ops.ietf.org; Thu, 17 Apr 2003 12:34:24 +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 h3HCTwjH021278
	for <te-wg@ops.ietf.org>; Thu, 17 Apr 2003 08:34:24 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314300E6042B for te-wg@ops.ietf.org; Thu, 17 Apr 2003 08:34:23 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: I-D ACTION:draft-ietf-tewg-diff-te-mar-00.txt
Date: Thu, 17 Apr 2003 07:34:21 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A7012@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-tewg-diff-te-mar-00.txt
Thread-Index: AcME1rJgJF7Qj+VjTaCZukpTb4vL6QABMwHw
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=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA19184

All,

This update to the MAR bandwidth constraint model I-D contains the following changes:
- added Section 3 on 'assumptions & applicability', as agreed in the TEWG meeting;
- added definitions in Section 2, based on comments on the list;
- clarified the functional specification in Section 4, based on comments on the list;
- moved descriptive material on MAR operation to the Annex, based on comments on the list. 

Please let me know of any further comments or suggestions.

Thanks,
Jerry

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Thursday, April 17, 2003 7:26 AM
Cc: te-wg@ops.ietf.org
Subject: I-D ACTION:draft-ietf-tewg-diff-te-mar-00.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  
                          Model for MPLS/DiffServ TE & Performance Comparisons
	Author(s)	: J. Ash
	Filename	: draft-ietf-tewg-diff-te-mar-00.txt
	Pages		: 0
	Date		: 2003-4-16
	
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-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-mar-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-mar-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.



From owner-te-wg@ops.ietf.org  Thu Apr 17 08:34:56 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19205
	for <tewg-archive@lists.ietf.org>; Thu, 17 Apr 2003 08:34:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1968ax-000Kiq-00
	for te-wg-data@psg.com; Thu, 17 Apr 2003 12:34:27 +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 1968aR-000Khg-00
	for te-wg@ops.ietf.org; Thu, 17 Apr 2003 12:33:57 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h3HCTnjG021215
	for <te-wg@ops.ietf.org>; Thu, 17 Apr 2003 08:33:54 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314300E60304; Thu, 17 Apr 2003 08:33:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: clarifications on MAR
Date: Thu, 17 Apr 2003 07:33:52 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A7011@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: clarifications on MAR
Thread-Index: AcL946H0W96VNfA8RT6VXhFpLTDuLgCiE7EgAAAG3PA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Alessio Liburdi" <liburdi@coritel.it>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-9.1 required=5.0
	tests=BAYES_01,QUOTED_EMAIL_TEXT,SATISFACTION
	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 IAA19205

Alessio,

First, your example and questions are similar to those raised by Francois back in November.  E.g., see
http://ops.ietf.org/lists/te-wg/te-wg.2002/msg00245.html
http://ops.ietf.org/lists/te-wg/te-wg.2002/msg00247.html
http://ops.ietf.org/lists/te-wg/te-wg.2002/msg00248.html
http://ops.ietf.org/lists/te-wg/te-wg.2002/msg00251.html
http://ops.ietf.org/lists/te-wg/te-wg.2002/msg00268.html
etc.   Please take a look at the TEWG archive, and you'll see that discussion.

Regarding your specific example and questions:

> I have a question regarding 
> draft-ash-mpls-dste-bcmodel-max-alloc-resv-01 because
> i don't understand the action of bandwidth reservation mechanism.
> 
> You write:
> 
> Bandwidth allocated to individual CTs is protected as 
> needed but otherwise shared. Under normal non-congested network 
> conditions, all CTs/services fully share all available bandwidth. When 
> congestion occurs for a particular CTi, bandwidth reservation acts to 
> prohibit traffic from other CTs from seizing the allocated capacity for 
> CTi
> 
> Now look at this example: I suppose 3 CTs all with normal priority
> 
> CT0-BWalloc = 30
> CT1-BWalloc = 20
> CT2-BWalloc = 20
> Reserved Bandwidth (RBW) = 10
> 
> I suppose that :
> CT0 has taken 80 units of bandwidth
> CT1 has taken 5 units of bandwidth
> CT2 has taken 0 units of bandwidth
> 
> Let'me say a flow arrives for CT2 needing 20 units of bandwidth (i.e., DBW 
> = 5). I need to decide based on Table 2 and Table 1 whether to admit 
> this flow or not.
> 
> Table 2  says Bandwidth -Not -Allowed
> 
> In this situation is the request for CT2 refuse or not? 

As per Table 2, since the entire BW request=20 could not be admitted on this LSP, it could attempt alternate LSPs.  The request could be satisfied either entirely on an alternate LSP, or alternatively, the request could be satisfied with BW=5 on this (the primary) LSP, and BW=15 on an alternate LSP.

While the example you give is of course possible, it is not 'typical' or realistic in that this would be a rare event.  The example does not reflect the engineering of BWalloc according to bandwidth demand.  That is, it would be rare (although not impossible) for CT0 to need so much more BW (=80 in your example) than its BWalloc=30 (which is its engineered/expected BW level).  But if CT0 was that much above its engineered level, the expectation based on design and normal traffic fluctuations is that CT0 would quickly release unneeded bandwidth toward its BWalloc, freeing up bandwidth for other CTs.

Furthermore, your example has CT2 seizing its entire BWalloc=20 in one jump.  I'm not sure what traffic model you're assuming, but this would be highly atypical in an engineered network based on measured and forecast traffic demand.  

In doing BW allocation, the design of the BW limits and thresholds, for any of the BC models, must be based on BW demands of each CT.  That is, the engineering design of the BW allocation model by the user/service-provider must be based on some realistic traffic model to work properly. 

> How bandwidth reservation acts to 
> prohibit traffic from other CTs from seizing the allocated 
> capacity for CT2 ?
> I would understand if CT0 frees band so I can accept the 
> request for CT2.

Bandwidth reservation provides that a level of bandwidth will be available for CTs below their BWalloc to seize BW preferentially over CTs above their BWalloc.  The references in the I-D show how this works in practice, the technique is widely deployed.  

Also, your example has the bandwidth request = 20, which is much larger than the reserved RBW = 10.  So even if the RBW is available (which it isn't in your example), the request could not be satisfied anyway.  Again, I'm not sure what traffic model you're assuming, but this is quite atypical in an engineered network based on measured and forecast traffic demand, and a realistic traffic model. 

Finally, the draft has been revised http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-mar-00.txt (as agreed in the TEWG meeting and on the list) to add Section 3 on 'assumptions & applicability'.  This Section should help clarify the points made above in relationship to the questions you raised.  

Also, other changes have been incorporated in the updated I-D based on discussion/comments on the list (see separate post on changes).

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Fri Apr 18 12:26: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 MAA18677
	for <tewg-archive@lists.ietf.org>; Fri, 18 Apr 2003 12:26:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 196YbO-0003gV-00
	for te-wg-data@psg.com; Fri, 18 Apr 2003 16:20:38 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 196Yb2-0003fi-00
	for te-wg@ops.ietf.org; Fri, 18 Apr 2003 16:20:16 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 18 Apr 2003 18:20:16 +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 h3IGINQA017707;
	Fri, 18 Apr 2003 18:18:25 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 18 Apr 2003 18:20:14 +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: Suggestions on draft-wlai-tewg-bcmodel
Date: Fri, 18 Apr 2003 17:20:13 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B51B8@xbe-lon-313.cisco.com>
Thread-Topic: Suggestions on draft-wlai-tewg-bcmodel
Thread-Index: AcLs8gBvyWh/zSTvQT6ji54RHbTtsQAbbDiAAEXoyTAAAr/WIAXOQErw
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 18 Apr 2003 16:20:14.0105 (UTC) FILETIME=[644EB890:01C305C6]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id MAA18677

Waisum,

A couple of suggestions for your next rev:

1) Selection of BC values
==========================
Selecting BC values for the compared models (when the prime element of
comparison is LSP blocking) is clearly a key aspects of the comparison.
To illustrate that point:
	- If I configure MAM with BC1=BC2=BC3=1000 while I configure RDM
with BC1=30, BC2=20, BC3=10, it is pretty obvious that MAM will have
much lower blocking. 
	- Conversely if I configure MAM with BC1=BC2=BC3=30 while I
configure RDM with BC1=1000, BC2=900, BC3=800, it is pretty obvious that
RDM will have much lower blocking.
Now, the reason BC values cannot simply be arbitrarily inflated is
because they result in QoS degradation: if I configure  BCs=O(1000) on a
link of O(10), there will be QoS degradation across CTs.

Now, if I understand correctly, the approach you took for selecting BC
vales for RDM, was to pick BC values so that RDM would exhibit the same
blocking probabilities as MAM for a given reference LSP load. This gave
you :
	- for MAM: BC1=6, BC2=7 and BC3=15
	- for RDM: BC1=6, BC2=11, and BC3=15
And then you use this values to compare RDM and MAM blocking performance
when increasing the load beyond the reference LSP load. 

This does not seem to me like a good base for comparison, because these
values correspond to allowing much more QoS degradation for MAM than for
RDM. For example, these values would accept a total load of 6+7+15=28
with MAM , while the maximum load is limited to BC3=15 with RDM. 

An analogy would be where someone wants to compare a Porsche and the
cheapest-car-on-market in terms of performance going uphill. And to do
so, the first thing he would do is put a 3-ton-trailer beyond the
Porsche to make sure they have same performance on flat ground. Then ,
when comparing uphill performance, it may be that the
cheapest-car-on-market would perform better than the Porsche with its
3-ton-trailer. From this, we would conclude that cheapest-car-on-market
has better uphill performance than a Porsche. No?

So, I would more value in a comparison of MAM and RDM with BC values
which yields comparable QoS degradation.
Probably something like:
	- for MAM: BC1=6, BC2=7 and BC3=15
	- for RDM: BC1=6, BC2=13, and BC3=28
Could you use these sorts of BC values in your comparison?

Was there some rationale for the 3-ton-trailer that I missed?


2) MAM definition
==================
We have an open discussion on the list about the MAM definition, about
whether we should update the current definition to add an aggreagte
Bandwidth Constraint (on sum across all CTs) or not. This is something
we will need to discuss/conclude on, but in any case, I suggest you make
it explicit in your draft whether you apply an aggregate BC for MAM in
your analysis or not. (for example , currently you only mention 3 BC
values for 3 CTs so I assume you did not assume an aggregate BC). 


Thanks for considering this

Francois



From owner-te-wg@ops.ietf.org  Mon Apr 21 11:57: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 LAA20602
	for <tewg-archive@lists.ietf.org>; Mon, 21 Apr 2003 11:57:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 197dbA-0003Fl-00
	for te-wg-data@psg.com; Mon, 21 Apr 2003 15:52:52 +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 197dal-00038o-00
	for te-wg@ops.ietf.org; Mon, 21 Apr 2003 15:52:28 +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 h3LFXgMb010018
	for <te-wg@ops.ietf.org>; Mon, 21 Apr 2003 10:52:26 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A31430106A7B5; Mon, 21 Apr 2003 11:52:26 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Suggestions on draft-wlai-tewg-bcmodel
Date: Mon, 21 Apr 2003 10:52:24 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA13700E@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Suggestions on draft-wlai-tewg-bcmodel
Thread-Index: AcLs8gBvyWh/zSTvQT6ji54RHbTtsQAbbDiAAEXoyTAAAr/WIAXOQErwAJPJhVA=
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA20602

Francois,
  Thanks for your suggestions.  I think comment 1 is related to the
Russian Doll draft last call, and comment 2 is related to the DS-TE
proto draft last call.  Please see my next two messaes in this regard.
Thanks, Wai Sum

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Friday, April 18, 2003 12:20 PM
To: Lai, Wai S (Waisum), ALABS
Cc: te-wg@ops.ietf.org
Subject: Suggestions on draft-wlai-tewg-bcmodel


Waisum,

A couple of suggestions for your next rev:

1) Selection of BC values
==========================
Selecting BC values for the compared models (when the prime element of
comparison is LSP blocking) is clearly a key aspects of the comparison.
To illustrate that point:
	- If I configure MAM with BC1=BC2=BC3=1000 while I configure RDM
with BC1=30, BC2=20, BC3=10, it is pretty obvious that MAM will have
much lower blocking. 
	- Conversely if I configure MAM with BC1=BC2=BC3=30 while I
configure RDM with BC1=1000, BC2=900, BC3=800, it is pretty obvious that
RDM will have much lower blocking.
Now, the reason BC values cannot simply be arbitrarily inflated is
because they result in QoS degradation: if I configure  BCs=O(1000) on a
link of O(10), there will be QoS degradation across CTs.

Now, if I understand correctly, the approach you took for selecting BC
vales for RDM, was to pick BC values so that RDM would exhibit the same
blocking probabilities as MAM for a given reference LSP load. This gave
you :
	- for MAM: BC1=6, BC2=7 and BC3=15
	- for RDM: BC1=6, BC2=11, and BC3=15
And then you use this values to compare RDM and MAM blocking performance
when increasing the load beyond the reference LSP load. 

This does not seem to me like a good base for comparison, because these
values correspond to allowing much more QoS degradation for MAM than for
RDM. For example, these values would accept a total load of 6+7+15=28
with MAM , while the maximum load is limited to BC3=15 with RDM. 

An analogy would be where someone wants to compare a Porsche and the
cheapest-car-on-market in terms of performance going uphill. And to do
so, the first thing he would do is put a 3-ton-trailer beyond the
Porsche to make sure they have same performance on flat ground. Then ,
when comparing uphill performance, it may be that the
cheapest-car-on-market would perform better than the Porsche with its
3-ton-trailer. From this, we would conclude that cheapest-car-on-market
has better uphill performance than a Porsche. No?

So, I would more value in a comparison of MAM and RDM with BC values
which yields comparable QoS degradation.
Probably something like:
	- for MAM: BC1=6, BC2=7 and BC3=15
	- for RDM: BC1=6, BC2=13, and BC3=28
Could you use these sorts of BC values in your comparison?

Was there some rationale for the 3-ton-trailer that I missed?


2) MAM definition
==================
We have an open discussion on the list about the MAM definition, about
whether we should update the current definition to add an aggreagte
Bandwidth Constraint (on sum across all CTs) or not. This is something
we will need to discuss/conclude on, but in any case, I suggest you make
it explicit in your draft whether you apply an aggregate BC for MAM in
your analysis or not. (for example , currently you only mention 3 BC
values for 3 CTs so I assume you did not assume an aggregate BC). 


Thanks for considering this

Francois



From owner-te-wg@ops.ietf.org  Mon Apr 21 12:28:44 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21576
	for <tewg-archive@lists.ietf.org>; Mon, 21 Apr 2003 12:28:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 197e9T-0005qL-00
	for te-wg-data@psg.com; Mon, 21 Apr 2003 16:28:19 +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 197e8u-0005pg-00
	for te-wg@ops.ietf.org; Mon, 21 Apr 2003 16:27:44 +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 h3LFx0N1024997
	for <te-wg@ops.ietf.org>; Mon, 21 Apr 2003 11:27:42 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A31430106F323; Mon, 21 Apr 2003 12:27:37 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C30822.EB5AC3AC"
Subject: RE: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Date: Mon, 21 Apr 2003 11:27:36 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA13700F@KCCLUST06EVS1.ugd.att.com>
X-MS-Has-Attach: yes
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Thread-Index: AcL94J7ZoAVWCBFjRoyujPO67h6vJwKIfENw
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C30822.EB5AC3AC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Francois,
   This message addresses Comment 1 in your message
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00228.html
as it relates to the Russian Dolls draft Last Call.

   Your following statement in the above message correctly reflects my
intent:
"Now, if I understand correctly, the approach you took for selecting BC
vales for RDM, was to pick BC values so that RDM would exhibit the same
blocking probabilities as MAM for a given reference LSP load."

  However, this statement is incorrect with respect to my comparison:
"For example, these values would accept a total load of 6+7+15=3D28
with MAM , while the maximum load is limited to BC3=3D15 with RDM."

  In <draft-wlai-tewg-bcmodel>, first of all, both MAM and RDM are
being offered the same load: 2.7 + 3.5 + 3.5 units as stated on the
top of page 5.  Furthermore, it is stated that
"As an example, consider a link with a capacity that allows a maximum=20
of 15 LSPs from different classes to be established simultaneously. =20
Overbooking is allowed, ..."
  Also,=20
"bandwidth constraints (for MAM) are:=20
up to 6 simultaneous LSPs for class 1,
up to 7 simultaneous LSPs for class 2, and=20
up to 15 simultaneous LSPs for class 3."

  Note the wording "up to."  Thus, while it is true that the sum of
*maximum* bandwidth constraints can add up to 28, there can be no
more than 15 *simultaneous* LSPs allowed for all classes, since
this is the ultimate constraint imposed by the link capacity
(which is the same link for both MAM and RDM).
Thus, using your terminology in the above message, both MAM and RDM
in my draft are either (1) both are Porsches, or (2) both are backed
up by 3-ton-trailers.

  Per your request, the attached diagram shows the result for the
case you suggested for RDM: BC1=3D6, BC2=3D13, and BC3=3D28.  Comparing
this result with Figures 1 and 2 in <draft-wlai-tewg-bcmodel>,
it can be seen that the QoS degradation for class 1 is the same in
all three cases, even though the link capacity is now 28 is your case,
and 15 in the other two cases in my draft.

  This is contrary to the following claim made in
<draft-ietf-tewg-diff-te-russian-02.txt>:
"RDM can be used to simultaneously ensure bandwidth efficiency=20
and protection against QoS degradation of all Class-Types"

Thanks, Wai Sum

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Tuesday, April 08, 2003 10:51 AM
To: te-wg@ops.ietf.org
Subject: WG last call: draft-ietf-tewg-diff-te-russian-02.txt




http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.t
xt

This is WG last call for this draft to be advanced as expiremental RFC.

Last call ends in 2 weeks (4/22).

thanks,

Jim Boyle





------_=_NextPart_001_01C30822.EB5AC3AC
Content-Type: application/octet-stream;
	name="rd28.pdf"
Content-Description: rd28.pdf
Content-Disposition: attachment;
	filename="rd28.pdf"
Content-Transfer-Encoding: base64

JVBERi0xLjINJeLjz9MNCjMgMCBvYmoNPDwgDS9MaW5lYXJpemVkIDEgDS9PIDUgDS9IIFsgMTA2
MCAxNzggXSANL0wgODU3MiANL0UgODMyMiANL04gMSANL1QgODM5NSANPj4gDWVuZG9iag0gICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICB4cmVmDTMgMzAgDTAwMDAwMDAwMTYgMDAwMDAgbg0KMDAwMDAwMDk0NCAwMDAwMCBuDQowMDAw
MDAxMjM4IDAwMDAwIG4NCjAwMDAwMDE0NDIgMDAwMDAgbg0KMDAwMDAwMTU5OCAwMDAwMCBuDQow
MDAwMDAxNzg0IDAwMDAwIG4NCjAwMDAwMDE5NjMgMDAwMDAgbg0KMDAwMDAwMjE0MiAwMDAwMCBu
DQowMDAwMDAyMTYzIDAwMDAwIG4NCjAwMDAwMDI3NDIgMDAwMDAgbg0KMDAwMDAwMjc2MyAwMDAw
MCBuDQowMDAwMDAzNDE0IDAwMDAwIG4NCjAwMDAwMDM0MzUgMDAwMDAgbg0KMDAwMDAwMzkwOSAw
MDAwMCBuDQowMDAwMDAzOTMwIDAwMDAwIG4NCjAwMDAwMDQ0OTIgMDAwMDAgbg0KMDAwMDAwNDUx
MyAwMDAwMCBuDQowMDAwMDA1MDU5IDAwMDAwIG4NCjAwMDAwMDUyNDUgMDAwMDAgbg0KMDAwMDAw
NTY2NSAwMDAwMCBuDQowMDAwMDA1Njg2IDAwMDAwIG4NCjAwMDAwMDYyMjYgMDAwMDAgbg0KMDAw
MDAwNjYyNSAwMDAwMCBuDQowMDAwMDA2ODA0IDAwMDAwIG4NCjAwMDAwMDY4MjUgMDAwMDAgbg0K
MDAwMDAwNzMxNyAwMDAwMCBuDQowMDAwMDA3MzM4IDAwMDAwIG4NCjAwMDAwMDgwNjEgMDAwMDAg
bg0KMDAwMDAwMTA2MCAwMDAwMCBuDQowMDAwMDAxMjE4IDAwMDAwIG4NCnRyYWlsZXINPDwNL1Np
emUgMzMNL0luZm8gMSAwIFIgDS9Sb290IDQgMCBSIA0vUHJldiA4Mzg2IA0vSURbPDA4OGYyZGVh
NmUwOTYzMGQzNDFlYmQxOGNjMGYwMTc4PjwwODhmMmRlYTZlMDk2MzBkMzQxZWJkMThjYzBmMDE3
OD5dDT4+DXN0YXJ0eHJlZg0wDSUlRU9GDSAgICAgIA00IDAgb2JqDTw8IA0vVHlwZSAvQ2F0YWxv
ZyANL1BhZ2VzIDIgMCBSIA0vT3BlbkFjdGlvbiBbIDUgMCBSIC9YWVogbnVsbCBudWxsIG51bGwg
XSANL1BhZ2VNb2RlIC9Vc2VOb25lIA0+PiANZW5kb2JqDTMxIDAgb2JqDTw8IC9TIDM2IC9GaWx0
ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMzIgMCBSID4+IA1zdHJlYW0NCkiJYmBgkGFgYFFhAAKp
rwzYAAeUFgApgWIGBlEGLt0TRVPmqTdw7GCY28AuwtDuwGGyNPkAh2yVegN7DMP65gkgdQABBgB7
bQ0tDWVuZHN0cmVhbQ1lbmRvYmoNMzIgMCBvYmoNNzQgDWVuZG9iag01IDAgb2JqDTw8IA0vVHlw
ZSAvUGFnZSANL1BhcmVudCAyIDAgUiANL1Jlc291cmNlcyA2IDAgUiANL0NvbnRlbnRzIFsgMTEg
MCBSIDEzIDAgUiAxNSAwIFIgMTcgMCBSIDE5IDAgUiAyMyAwIFIgMjcgMCBSIDI5IDAgUiBdIA0v
TWVkaWFCb3ggWyAwIDAgNjEyIDc5MiBdIA0vQ3JvcEJveCBbIDAgMCA2MTIgNzkyIF0gDS9Sb3Rh
dGUgMCANPj4gDWVuZG9iag02IDAgb2JqDTw8IA0vUHJvY1NldCBbIC9QREYgL1RleHQgXSANL0Zv
bnQgPDwgL1RUMiA4IDAgUiAvVFQ0IDIxIDAgUiAvVFQ2IDI0IDAgUiA+PiANL0V4dEdTdGF0ZSA8
PCAvR1MxIDMwIDAgUiA+PiANL0NvbG9yU3BhY2UgPDwgL0NzNSA5IDAgUiA+PiANPj4gDWVuZG9i
ag03IDAgb2JqDTw8IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQgODkxIA0vQ2FwSGVp
Z2h0IDAgDS9EZXNjZW50IC0yMTYgDS9GbGFncyAzNCANL0ZvbnRCQm94IFsgLTU2OCAtMzA3IDIw
MjggMTAwNyBdIA0vRm9udE5hbWUgL1RpbWVzTmV3Um9tYW4gDS9JdGFsaWNBbmdsZSAwIA0vU3Rl
bVYgMCANPj4gDWVuZG9iag04IDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1RydWVU
eXBlIA0vRmlyc3RDaGFyIDMyIA0vTGFzdENoYXIgMzIgDS9XaWR0aHMgWyAyNTAgXSANL0VuY29k
aW5nIC9XaW5BbnNpRW5jb2RpbmcgDS9CYXNlRm9udCAvVGltZXNOZXdSb21hbiANL0ZvbnREZXNj
cmlwdG9yIDcgMCBSIA0+PiANZW5kb2JqDTkgMCBvYmoNWyANL0NhbFJHQiA8PCAvV2hpdGVQb2lu
dCBbIDAuOTUwNSAxIDEuMDg5IF0gL0dhbW1hIFsgMi4yMjIyMSAyLjIyMjIxIDIuMjIyMjEgXSAN
L01hdHJpeCBbIDAuNDEyNCAwLjIxMjYgMC4wMTkzIDAuMzU3NiAwLjcxNTE5IDAuMTE5MiAwLjE4
MDUgMC4wNzIyIDAuOTUwNSBdID4+IA0NXQ1lbmRvYmoNMTAgMCBvYmoNNTAxIA1lbmRvYmoNMTEg
MCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAxMCAwIFIgPj4gDXN0cmVhbQ0K
SImslU9r3DAQxe/6FHNsCpnVSCNZumYbCoUeigU9lJ42TWloCu0e8vUztv5Y8pacFsNinn87bzTz
vHuX1CElAwTpUUWMHrRc603UqFl7mHiC9KwOx7OD03l9ruF8UoePM8HPs9KQTsvHi3oHN+lJbm8n
QrLGQfrQNGY03tEm3SdFsFxSiuAXKDIOfSDwgZEMWEtoDdySE5nh3w/1+F79bZRzEZkrpZdvCPIV
/uRGj3NpdD5K9U9i85ShFyANn+Hbdw0PQzHn4Vmxm1DrJvxWs/rSm8pM/NVMpdg0mGZhb+oN4WSu
ZLoUC9yZFuHC1BmMVzN1VqLUm2bhwjRca7YlQ51jFrJjK4hOm+FzKC7vwFvFLwM6q9Ziae2yobZ9
E5CDNERmedKEt4ia0l1sO6JGapexjWj73wWiI+qydtvriP1Z2nB3rXfR3s5SCb/k63+nFTszEE2o
RNAYBqIJhTB6uemITaiE9agHogmV8HbsdBMqEQlZ90QTCmEpluMXYhMqwR79QDShEpP8cg5EEwoh
lhh6YhMqYeLY6SZUoi2qEvvNSbjzG6HIxjLMiGtg/ZRH5wjdGoPIORfaLr9cMilj1hV678voOOaN
5a/IoazJLdca1uvcYSWYbT52Jerbtvx/2FACIONdW2JXphhR2FcBBgBbf14kDWVuZHN0cmVhbQ1l
bmRvYmoNMTIgMCBvYmoNNTczIA1lbmRvYmoNMTMgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNv
ZGUgL0xlbmd0aCAxMiAwIFIgPj4gDXN0cmVhbQ0KSIl8VTmSGzEMzPWKiV1lFnHwepAdSYn/HxgN
gJpZ7UqZpsFu4mhCx420lcF0NJ6F9bjfSFapNQBiA/7+skOrqAJbhY/HjVov1ONbcAYAzyBJB2CM
1i+yUOk1laEGmd7zbhwGy4CpwYrvajnEt86t0u33k2QqQwqnbMchAJKswSnb6ykLlTFKzYomRKaU
kRUt5xgws6LluRiDsqK5K5ojhMUq84qWxtUGkLMMODt3d8Yuue6K7EydT9LjxrWWmbKMQwAWX/tt
lF1zzoirlq5PkqkQ2SwCQL743o1TB4wxrlOECrUQNlLDqJkprjagO4v52TlvNyhynSJkbPx8ds9k
zCB79l43gD1atxkoGkNKjbbSDGE6tim2a7oA+tV0YKwX0/GoKZumY8zxmi4AvpgOjPZiOh493ZCm
Y7OHN1Mo0zdgW4G2bP1qOrbhR3Mpu7IkKhBBt+8OxOQ5kzNKGIpSY43IThRFP25iU/R7pIVzAVCe
cOeCEs6Qkl3Bmci2h1mkrvCCVs8W316wbYO2Vd24dk16RYhDVwU9MBEakb2OcBgAN4/2mBAocQ1M
lDJcowm6oivCLQbfNOwPwOfaxO8GI+6xpzi3yoz8zFdekBXrz7XXLMAAt2RL+4s/ZAAt1gRU4KDT
HFhPx++KtP798TjcND/EJz0fx8/xnN67+JqxCt7Etc5o+bu4vUX6oK/Wyf5JH374oH/9czAQq+Fr
XPdKeRNv59v6Od6ve+N7vO/l8y5+bvrX+H8BBgBqwFqlDWVuZHN0cmVhbQ1lbmRvYmoNMTQgMCBv
YmoNMzk2IA1lbmRvYmoNMTUgMCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAx
NCAwIFIgPj4gDXN0cmVhbQ0KSIl8VUtuQzEI3L9TeF2pyHyM7eu0alfppr2/VPx4aeJFR9kEA5OB
AVKOz5eDu5A6lyaDphemKeW1rq/fH+kfxAL8Q2kM5J/kBvzTSCryzzD+90tt1AE/YSYD/IQ7CeAn
NskAP2mNGPHzMBA/d3LEL/QxxK93qojfEOqI3xjUEL+lD+CntVIF/LQa1Ee5Qn2UHeqjIrB+lQ7r
1zahPuoN6qOdoT4a+qD51tAHzbeODvXRqVif2B+kj4U+A/Cz0KcBfsYN3geTCu+DicP7YCpw/0wH
3D8u6/PzfrDOHLQAVClfB9t9ckKhUW4R4ZcUfw9byu14CzyPfVtvzaKvC8bjwC0YmyvFLdt1WVtw
AsRCrYHyugZ7AcyckACh9SM85azoYW8JJ4jE1C/V3WcgiKSG7roKv8VRm+fQPx6e4hMgztp4LkPa
1eeTuFjPf4XL2oITIObaNoBRs52Z0i17eVlb8AmgcbjPxbgDaO15Kc4UrZJ7d1lbcAKEKmMD0BYy
/aVozcVY1q8AAwANHV4PDWVuZHN0cmVhbQ1lbmRvYmoNMTYgMCBvYmoNNDg0IA1lbmRvYmoNMTcg
MCBvYmoNPDwgL0ZpbHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAxNiAwIFIgPj4gDXN0cmVhbQ0K
SImUlM1uHSEMhffzFLOuVAtsY+Axoiyyj9SuciO177+owWaYnztRurgjXTh8Pgbb60KEUEJcU2II
vH4s7z8WkgA81x66gFBRF7iqglKGUrZ/R7EBSoFwANQAaQJKAp6Ao7gDOCaQPYBjgbgBOBKEMv8d
xAZgAjwAOEGeAA4gE3AUd8CfJZJAYV3FBFVWtaw/LOvfX8vb+jm3KQJy3/7ZPrr9e3nR7Wo5YgHR
+E1exeQRNcZrD1HsJi0EKVA/yDPGCcJoV4Wi+XfIizsl+Q/M8LLH3MaahqMwsKec8ZRylGxvgrVB
H12dPGMZCYt4kL1TZQ2nV0i1t1WrSWbGQp7BtzluZs+5j7ZZjlVvoaeMQJeUK1sV6Xnp51UdxdTt
yp4IslUaZhU+VzjiC4UzPMjrglG33GQ5eURUVTtOofEeXZzdo7THvyqQbSSoBeGnisG4VwzGiNJe
H1mdnztK5f5o27ZV3LmjkKs3S9EaajFUT1ZgW4BqNg5lEXFGOCMS2vCyA6O8kMXz+y5nWNlz7qO5
Ycy8jZBLP2HO3ipenE1dT/2EWZ4MkNkHV0gJ2wTZ9VNjXyfIV5xhZs+5j7ZZpoA+FPROzlOTQvLK
TtCON3EvfRVTK/WrINtQJ2qT+SL4J8AAybBZvA1lbmRzdHJlYW0NZW5kb2JqDTE4IDAgb2JqDTQ2
OCANZW5kb2JqDTE5IDAgb2JqDTw8IC9GaWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMTggMCBS
ID4+IA1zdHJlYW0NCkiJjJW9jtwwDIR7P4XqACH0b+oxDinSZ5FUuQDJ+xcZHkmtvV4trlmYEmf4
jS17w1Zips4ptFIoc/iNhUY5ykIjDu+od9qz1Ewlo+HbVkqk1LHURRsa1fBVfv793H5hMxOLvkeK
VQzQnVm7W5cJ144Gayy0nVp+3mEeLzrMw6cAE827YJaEBI+YEFYxyIPiR050M2u36v9ibeiU3Gj0
UIgrfuAFi+/hzxMTTB9CkbtTvH347Ir/aR+HOfqsp03kwrgLy8jMFE96dNfHyLzbkAXqxWREPJJr
ZK6W4LM+DnOKvJw2kWvCTVhFrqlRP+prKrg4R5am+CLyExOmdI0sJPVF5DXM0Wc97R654iYsI9ei
7+/Uo7s/Rq7ZhixQryZNvwIPkeEdX0VewpwiL6dN5FSTHSfGyvuhHngFQrpnDKkMfwfCbUv4bMXq
O12PiolmKZ7S6rW8rWEqgRr5bqsl2g9RZH8SqfoEfNt+fNlSH3Y+LMOsFaezfiSEtHc/1DKp40h4
hl712bvIS8swa6VwpTG67czgM33fiUx9BNYMY7cHbhlmrTij+UcU19VPqUwaeMaeYWT9/3CRl5Zh
1krhSmN025nBZ/q+E5n6CHz7L8AAwqxaFQ1lbmRzdHJlYW0NZW5kb2JqDTIwIDAgb2JqDTw8IA0v
VHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQgOTA1IA0vQ2FwSGVpZ2h0IDAgDS9EZXNjZW50
IC0yMTEgDS9GbGFncyAzMiANL0ZvbnRCQm94IFsgLTYyOCAtMzc2IDIwMzQgMTA0OCBdIA0vRm9u
dE5hbWUgL0FyaWFsLEJvbGQgDS9JdGFsaWNBbmdsZSAwIA0vU3RlbVYgMTMzIA0+PiANZW5kb2Jq
DTIxIDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1RydWVUeXBlIA0vRmlyc3RDaGFy
IDMyIA0vTGFzdENoYXIgMTIxIA0vV2lkdGhzIFsgMjc4IDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAy
NzggMCAwIDI3OCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgDTAgMCAwIDAgNzIyIDcyMiA3
MjIgMCAwIDAgMCAwIDAgMCA2MTEgMCAwIDc3OCA2NjcgMCA3MjIgMCAwIDAgMCANOTQ0IDAgMCAw
IDAgMCAwIDAgMCAwIDU1NiA2MTEgNTU2IDYxMSA1NTYgMzMzIDYxMSA2MTEgMjc4IDAgNTU2IA0y
NzggODg5IDYxMSA2MTEgNjExIDAgMzg5IDU1NiAzMzMgNjExIDAgMCAwIDU1NiBdIA0vRW5jb2Rp
bmcgL1dpbkFuc2lFbmNvZGluZyANL0Jhc2VGb250IC9BcmlhbCxCb2xkIA0vRm9udERlc2NyaXB0
b3IgMjAgMCBSIA0+PiANZW5kb2JqDTIyIDAgb2JqDTQ2MiANZW5kb2JqDTIzIDAgb2JqDTw8IC9G
aWx0ZXIgL0ZsYXRlRGVjb2RlIC9MZW5ndGggMjIgMCBSID4+IA1zdHJlYW0NCkiJVJQ7kqAwDETz
OQXxBCp/ZGOuM8R7/3QNrW6bjC4h6b0y5vj5+/0pxa2PfLQyrB//tnzZVY5SqvkTa57PxXLH8z1f
TDY8Kvmys68mxWfmfFX5tDIOdZZuaayxiM/k2Mk6iaJ7B75fh1ZmZXNQBk7Lc06QeqDAwYc5Hfy0
ujkohoMyKNgZjBwrB+6MuojQ/QGGw3nZ2B2UgXMOWD+kZ6DA4Zwb6HC6XZuDYjgog4KdwcixcuBO
1kkU3Tvw61DTaT0th5VfnJq6eQJpTU1ncs8Xq06lprJ/gCtizcovhTrBqLF00E7WSRTdOzAcarOy
OygDp7olOtSiM5mbatap1Jr2D3DFcFAGBTuDkWPlwJ2skyi6d2A49GJjd1AGTs+wfkh7oMChDXwg
T6Wd+we4Yjgog4KdwcixcuBO1kmE7g8wHK4UBxcOysAZF6wf0hEocBjdGh1Giz9JNDGGgzIo2BmM
HCsH7oy6iND9AX4dPI84ODis/OJ47rCepJ6b/rP3fNH1p/Vc45OOJkasWfmlUCcYNZYO2sk6iaJ7
B4aDt8+dXhk47rrT7nW70/PvqDvtnvY7vWI4KIOCncHIsXLgTtbbfqe/wPd/AQYA3U9QWg1lbmRz
dHJlYW0NZW5kb2JqDTI0IDAgb2JqDTw8IA0vVHlwZSAvRm9udCANL1N1YnR5cGUgL1RydWVUeXBl
IA0vRmlyc3RDaGFyIDMyIA0vTGFzdENoYXIgMTI1IA0vV2lkdGhzIFsgMjc4IDAgMCAwIDAgMCAw
IDAgMCAwIDAgNTg0IDI3OCAwIDI3OCAwIDU1NiA1NTYgNTU2IDU1NiA1NTYgNTU2IDAgDTU1NiAw
IDAgMCAwIDAgMCAwIDAgMCAwIDY2NyA3MjIgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgNjY3IDAg
MCANMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDAgMCAwIDU1NiAwIDAgMCAwIDAgMCAwIDAgMCAwIDIy
MiAwIDAgMCAwIA0wIDAgNTAwIDAgMCAwIDAgMCAwIDAgMzM0IDAgMzM0IF0gDS9FbmNvZGluZyAv
V2luQW5zaUVuY29kaW5nIA0vQmFzZUZvbnQgL0FyaWFsIA0vRm9udERlc2NyaXB0b3IgMjUgMCBS
IA0+PiANZW5kb2JqDTI1IDAgb2JqDTw8IA0vVHlwZSAvRm9udERlc2NyaXB0b3IgDS9Bc2NlbnQg
OTA1IA0vQ2FwSGVpZ2h0IDAgDS9EZXNjZW50IC0yMTEgDS9GbGFncyAzMiANL0ZvbnRCQm94IFsg
LTY2NSAtMzI1IDIwMjggMTAzNyBdIA0vRm9udE5hbWUgL0FyaWFsIA0vSXRhbGljQW5nbGUgMCAN
L1N0ZW1WIDAgDT4+IA1lbmRvYmoNMjYgMCBvYmoNNDE0IA1lbmRvYmoNMjcgMCBvYmoNPDwgL0Zp
bHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAyNiAwIFIgPj4gDXN0cmVhbQ0KSInUkztPwzAQx3d/
Co82Ssz5nayoExNClhgqBkAgivpAFMRQ8d05P9KkRVCKoBLJ4Mvlf4/fXULJ9RE5CeQ4BEMlDXfE
Cu8o4J0M5UFYBY56MMIZGmYE0tvlDalBALiWhmICxr+SMTvntdSiZS8c3Yot06Mup2KTq+KY01FR
LrJyOq3oxeSZ1x4f7rOPnvHaCceektSx25KlO2fF/1jCJos5vwynEch1QGAKEBpStgIaBLLKC+ky
EBJA7J0BDw+klkI3kjp87TwNo0zX2CgbMxBY0QnDwKZCOB+Dg0J1CzaqBxKZFHUvKQmHkt1Z1O4s
KmfRObzWKhGgBjuXcW1xL6s4oRabAtbFaVsVi+rOh66YSwoDpqFxGHilXDlNL3xLQpMFAx1Oy7d5
Wive4HIUTwHC57OiujiwFVt8pSjuZ1hzY/QfK0Nr1WblbVozoIXD0BYiYQ5N2+Cge1qP9ppXrr3/
ab1R/eV2P+W1/Z+xN6/brrqBaz/i+h63Kn9zY73cA/T3Rryj9OA7+B7uH25Xx0b3GvRPoN8FGAB7
1WSLDWVuZHN0cmVhbQ1lbmRvYmoNMjggMCBvYmoNNjQ1IA1lbmRvYmoNMjkgMCBvYmoNPDwgL0Zp
bHRlciAvRmxhdGVEZWNvZGUgL0xlbmd0aCAyOCAwIFIgPj4gDXN0cmVhbQ0KSImUVMFu2zAMvfsr
eJS7WZVkiZKubXcZBqxAfRt6SLN0CJY0Q12gGIb9+0hKjpt2ybAEiCzy8Yl+jwo0X1TQbWdRe+XC
7/Z2+Nh4jTaD1T19YLhqjDYmZhiWBP7VJh2Ua6VAx7K+h74GWqNCjQmV1d74BN1M1jFbCoUtTkeX
g8+HwYOF4b7p+qARMXJlMjnMlT1X0pNFB8MzcXwSiqB2dV20Rjv1te7gszw4dd92SaOCq/VhoC4r
qXpcPdS6pwq/3FT4YhxXo3RpIGjjoZNfA9ZEnZ1BCBi18zBsRbBkuVHp2dROL0gZtZGDdktWCdX3
sqwl+PDt/Jrk9eqRoz31JMm6bEvwx1MbdVLr3QMcgHd3i4K7W2/WBfNT2v0wNBb4Oy4bj0FbtED+
akyATtN7ONQpweOquafGrYNnEJzxFkJ2WmDBgYuMuSFMxoKh1zXMRVbBtvE5aJem/YaQPlkShCOR
TmVIIjop8azdpvGR+3gZOCzZNHdnzcXAg4FlMKro1QOfaXgSaY+2JyKiZvUlPxbxXZ/qwPQ2Fhsu
ydGgMznR9VlHGhje92ocwdZHuJik84g6OmqIXDYkBW2gEwlYsDN6g1je+lg+kRP+eH62hqQIbI1J
RAi95msjv+LMXhiDRe1JOYKLUG8Ak9YmvJL2DcMxwJ6hHnHDVhwzwPi3BpzU2s1ad66nK/eu5Vtv
1fVr7UNOrJ2la/ZKe5rfdCqf5IWO5hNNnTmVp5bxRJ4mPsz9Gb79f/eWlERpNLL/2xcB+jdFYOWz
HJRZad5at99yvZEhm/LVual6vxX2ZTMH5GbP1XjIjhP7dHrNu8Nqd8hebuSRMQgkyf+NQf/PMfgj
wAAHaVqhDWVuZHN0cmVhbQ1lbmRvYmoNMzAgMCBvYmoNPDwgDS9UeXBlIC9FeHRHU3RhdGUgDS9T
QSBmYWxzZSANL1NNIDAuMDIgDS9UUiAvSWRlbnRpdHkgDT4+IA1lbmRvYmoNMSAwIG9iag08PCAN
L1Byb2R1Y2VyIChBY3JvYmF0IERpc3RpbGxlciA0LjA1IGZvciBXaW5kb3dzKQ0vTW9kRGF0ZSAo
RDoyMDAzMDQyMTA5MjEyMy0wNCcwMCcpDS9BdXRob3IgKEFUJlQpDS9DcmVhdGlvbkRhdGUgKEQ6
MjAwMzA0MjEwOTE4MDMpDS9DcmVhdG9yIChNaWNyb3NvZnQgV29yZCA5LjApDT4+IA1lbmRvYmoN
MiAwIG9iag08PCANL1R5cGUgL1BhZ2VzIA0vS2lkcyBbIDUgMCBSIF0gDS9Db3VudCAxIA0+PiAN
ZW5kb2JqDXhyZWYNMCAzIA0wMDAwMDAwMDAwIDY1NTM1IGYNCjAwMDAwMDgxMzkgMDAwMDAgbg0K
MDAwMDAwODMyMiAwMDAwMCBuDQp0cmFpbGVyDTw8DS9TaXplIDMNL0lEWzwwODhmMmRlYTZlMDk2
MzBkMzQxZWJkMThjYzBmMDE3OD48MDg4ZjJkZWE2ZTA5NjMwZDM0MWViZDE4Y2MwZjAxNzg+XQ0+
Pg1zdGFydHhyZWYNMTczDSUlRU9GDQ==

------_=_NextPart_001_01C30822.EB5AC3AC--



From owner-te-wg@ops.ietf.org  Mon Apr 21 16:46:02 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01557
	for <tewg-archive@lists.ietf.org>; Mon, 21 Apr 2003 16:46:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 197i9Y-000026-00
	for te-wg-data@psg.com; Mon, 21 Apr 2003 20:44:40 +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 197i8w-000Pt4-00
	for te-wg@ops.ietf.org; Mon, 21 Apr 2003 20:44:02 +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 h3LGCMP1003182
	for <te-wg@ops.ietf.org>; Mon, 21 Apr 2003 11:55:22 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314301072AF0; Mon, 21 Apr 2003 12:55:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Date: Mon, 21 Apr 2003 11:55:22 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137010@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Thread-Index: AcL9hkdP8xdPzaZVRW+kJKjXc2qB+gKgz8Ew
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA01557

Francois,
   This message addresses Comment 2 in your message
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00228.html
as it relates to the DS-TE proto draft Last Call.

   Per your suggestion, I will add some clarification to my
draft.  Also, I think it would be good to resolve the issue
along with the comments of the following two messages:
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00224.html
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00128.html

Thanks, Wai Sum

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Monday, April 07, 2003 11:56 PM
To: te-wg@ops.ietf.org
Subject: WG last call: draft-ietf-tewg-diff-te-proto-03.txt



http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto-03.txt

This is WG last call for this draft to be advanced standards track.
Since notice was sent to other WGs for review, we will take 3 weeks.

Last call for this draft closes 4/28.

thanks,

Jim Boyle






From owner-te-wg@ops.ietf.org  Tue Apr 22 12:56: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 MAA16169
	for <tewg-archive@lists.ietf.org>; Tue, 22 Apr 2003 12:56:47 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19810Z-000DRU-00
	for te-wg-data@psg.com; Tue, 22 Apr 2003 16:52:39 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19810C-000DQt-00
	for te-wg@ops.ietf.org; Tue, 22 Apr 2003 16:52:16 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 22 Apr 2003 18:52: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 h3MGoNp3024031;
	Tue, 22 Apr 2003 18:50:24 +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, 22 Apr 2003 18:52: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: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Date: Tue, 22 Apr 2003 17:52:12 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B51C0@xbe-lon-313.cisco.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Thread-Index: AcL94J7ZoAVWCBFjRoyujPO67h6vJwKIfENwADqKrCA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 22 Apr 2003 16:52:13.0466 (UTC) FILETIME=[85FCF7A0:01C308EF]
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 MAA16169

Waisum,

So the bottom line is that we assumed different definitions for MAM.
Your analysis assumed the model recently discussed on the list (ie "MAM
with the additional implied bandwidth constraint") as opposed to MAM as
currently defined. We do need to make some decision on this issue. And
then your analysis should be based on the outcome of that discussion.

Let me think more about the MAM definition issue.

Cheers

Francois

PS: What I mean by QoS degradation does not relate to blocking
probability. It refers to ensuring that the maximum amount of
established LSPs for a given CT is in line with the service rate that
the scheduler can provide to that CT. Please see the draft I issued a
while back on "BC Model considerations".

>> -----Original Message-----
>> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com] 
>> Sent: 21 April 2003 18:28
>> To: Francois Le Faucheur (flefauch)
>> Cc: Jim Boyle; te-wg@ops.ietf.org
>> Subject: RE: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
>> 
>> 
>> Francois,
>>    This message addresses Comment 1 in your message
>> http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00228.html
>> as it relates to the Russian Dolls draft Last Call.
>> 
>>    Your following statement in the above message correctly 
>> reflects my
>> intent:
>> "Now, if I understand correctly, the approach you took for 
>> selecting BC
>> vales for RDM, was to pick BC values so that RDM would 
>> exhibit the same
>> blocking probabilities as MAM for a given reference LSP load."
>> 
>>   However, this statement is incorrect with respect to my comparison:
>> "For example, these values would accept a total load of 6+7+15=28
>> with MAM , while the maximum load is limited to BC3=15 with RDM."
>> 
>>   In <draft-wlai-tewg-bcmodel>, first of all, both MAM and RDM are
>> being offered the same load: 2.7 + 3.5 + 3.5 units as stated on the
>> top of page 5.  Furthermore, it is stated that
>> "As an example, consider a link with a capacity that allows 
>> a maximum 
>> of 15 LSPs from different classes to be established simultaneously.  
>> Overbooking is allowed, ..."
>>   Also, 
>> "bandwidth constraints (for MAM) are: 
>> up to 6 simultaneous LSPs for class 1,
>> up to 7 simultaneous LSPs for class 2, and 
>> up to 15 simultaneous LSPs for class 3."
>> 
>>   Note the wording "up to."  Thus, while it is true that the sum of
>> *maximum* bandwidth constraints can add up to 28, there can be no
>> more than 15 *simultaneous* LSPs allowed for all classes, since
>> this is the ultimate constraint imposed by the link capacity
>> (which is the same link for both MAM and RDM).
>> Thus, using your terminology in the above message, both MAM and RDM
>> in my draft are either (1) both are Porsches, or (2) both are backed
>> up by 3-ton-trailers.
>> 
>>   Per your request, the attached diagram shows the result for the
>> case you suggested for RDM: BC1=6, BC2=13, and BC3=28.  Comparing
>> this result with Figures 1 and 2 in <draft-wlai-tewg-bcmodel>,
>> it can be seen that the QoS degradation for class 1 is the same in
>> all three cases, even though the link capacity is now 28 is 
>> your case,
>> and 15 in the other two cases in my draft.
>> 
>>   This is contrary to the following claim made in
>> <draft-ietf-tewg-diff-te-russian-02.txt>:
>> "RDM can be used to simultaneously ensure bandwidth efficiency 
>> and protection against QoS degradation of all Class-Types"
>> 
>> Thanks, Wai Sum
>> 
>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com]
>> Sent: Tuesday, April 08, 2003 10:51 AM
>> To: te-wg@ops.ietf.org
>> Subject: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
>> 
>> 
>> 
>> 
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.t
xt

This is WG last call for this draft to be advanced as expiremental RFC.

Last call ends in 2 weeks (4/22).

thanks,

Jim Boyle






From owner-te-wg@ops.ietf.org  Wed Apr 23 05:26:55 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08819
	for <tewg-archive@lists.ietf.org>; Wed, 23 Apr 2003 05:26:55 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 198GPd-00098N-00
	for te-wg-data@psg.com; Wed, 23 Apr 2003 09:19:33 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 198GPY-00098A-00
	for te-wg@ops.ietf.org; Wed, 23 Apr 2003 09:19:29 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 23 Apr 2003 11:19:23 +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 h3N9HJp6028010
	for <te-wg@ops.ietf.org>; Wed, 23 Apr 2003 11:17: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);
	 Wed, 23 Apr 2003 11:19:21 +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: MAM Definition
Date: Wed, 23 Apr 2003 10:19:20 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B51C1@xbe-lon-313.cisco.com>
Thread-Topic: MAM Definition
Thread-Index: AcMJeWwQB2RQJKEbQLWinzy3SZe6Pw==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 23 Apr 2003 09:19:21.0179 (UTC) FILETIME=[6C74C2B0:01C30979]
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 FAA08819

Hello,

The current MAM definition purely specifies one Bandwidth Constraint per
CT (as per -diff-te-reqts and diff-te-mam). It was proposed that this
definition be enhanced by applying one additional bandwidth constraint
which would be an aggregate constraint across all CTs (in fact it
appeared that a few people had been assuming this was already part of
the definition).

Just to illustrate this, with the new definition one could ensure, on a
given link, that:
	Reserved (CT0=Voice)              <=   CT0=50%-of-link
	Reserved (CT1=Premium)            <=   CT1=40%-of-link
	Reserved (CT2=Best-Effort)        <=   CT2=60%-of-link
      Reserved (CT0+CT1+CT2=everything) <=   Max Reservable=120%-of-link

I don't have objections to adding this enhancement to the MAM
definition.

Other opinions?

Assuming we go down that path, one issue we would need to address is the
fact that the diff-te-reqts draft is going to be published as an RFC and
will mention MAM with its "old" definition, which would result in
inconsistency and confusion. One simple solution to this would be to
give a different name to the model with the "new" definition. I don't
have a specific proposal, but I'm sure we could come up with some name
which better reflects the fact that we have both a per-CT constraint and
an aggregate constraint (better than "Maximum Allocation"). Come to
think of it, I do have a proposal, maybe something like "Separate and
Aggregate constraints Model (SAM)".

Thoughts?

Cheers

Francois

PS: Changing MAM definition actually has quite a few ramifications in
the -proto draft (eg about advertisement of Max Reservable and BC
sub-TLV) and probably some in -russian draft. I will send a separate
email with a detailed proposal on how to reflect this.



From owner-te-wg@ops.ietf.org  Wed Apr 23 05:28: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 FAA08849
	for <tewg-archive@lists.ietf.org>; Wed, 23 Apr 2003 05:28:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 198GWP-0009l8-00
	for te-wg-data@psg.com; Wed, 23 Apr 2003 09:26:33 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 198GWM-0009kw-00
	for te-wg@ops.ietf.org; Wed, 23 Apr 2003 09:26:30 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 23 Apr 2003 11:26:25 +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 h3N9OG6c029408
	for <te-wg@ops.ietf.org>; Wed, 23 Apr 2003 11:24:38 +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, 23 Apr 2003 11:26:26 +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: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Wed, 23 Apr 2003 10:26:26 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B9494@xbe-lon-313.cisco.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMJeml8BmEjHSmTTr+3lnTgXloVOw==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 23 Apr 2003 09:26:26.0338 (UTC) FILETIME=[69DEE020:01C3097A]
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id FAA08849

Hello,

Assuming there is agreement to add the enhancement to the current MAM
definition, below is a first cut at the main changes that would result
in the diff-te drafts. 
Could you check these out?

Thanks

Francois




MAM/SAM draft - Definition
===========================
The "newMAM/SAM" definition could look like this:

	o Maximum Number of Bandwidth Constraints (MaxBC)= 
		  Maximum Number of Class-Types (MaxCT) + 1 = 9
        (where one of the bandwidth constraints is the "Max reservable
Bandwidth")
	o for each value of b in the range 0 <= b <= 7: 
		Reserved (CTb) <= BCb, 
	o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
		for all "c" in the range 0 <= c <= (MaxCT-1)

Illustration diagram would look like: 
   
  I------------------------------------------------------------I
  I--------------II-------------II-------------I               I
  I    CT2       II   CT1       II     CT0     I  CT2+CT1+CT0  I
  I--------------II-------------II-------------I               I
  I------------------------------------------------------------I
   
  <-----BC2------><-----BC1-----><-----BC0-----> 
  <------------------------Max Reservable Bandwidth------------>


MAM/SAM draft - Formulas for computing Unreserved bandwidth
============================================================
 The example formulas for computing Unreeserved Bandwidth would be
changed to:
   
        "Unreserved TE-Class [i]" = 
	 MIN [
	   [ BCc - SUM ( Reserved(CTc,q) ) ] for q <= p  ,
	   [Max Reservable Bandwidth - SUM ( Reserved (CTb,q) ) ] for q
<= p and 0 <= b <= 7,
           ]


RDM draft - Definition
===========================
The RDM definition could be slightly updated (to clarify relationship to
Max Res Bw which is differnet to new-MAM/SAM) like this:

	o Maximum Number of Bandwidth Constraints (MaxBC)= Maximum 
		Number of Class-Types (MaxCT) = 8 	
	 (where BC0 is the "Max reservable Bandwidth")
	o for each value of b in the range 0 <= b <= (MaxCT - 1): 
		SUM (Reserved (CTc)) <= BCb, 
		for all "c" in the range b <= c <= (MaxCT - 1)

Illustration diagram becomes:
   
  I------------------------------------------------------I 
  I-------------------------------I                      I 
  I--------------I                I                      I 
  I    CT2       I    CT2+CT1     I      CT2+CT1+CT0     I 
  I--------------I                I                      I 
  I-------------------------------I                      I 
  I------------------------------------------------------I 
   
  I-----BC2------> 
  I----------------------BC1------> 
  I-------------------------BC0 = Max Reservable Bw------> 


Protocol draft "4.1.1. Bandwidth Constraints (BCs)"
==============================================

For DS-TE, the existing "Maximum Reservable link bandwidth" parameter 
is retained and its semantic is generalized as the aggregate bandwidth 
constraints across all Class-Types. So that, independently of the
Bandwidth 
Constraint Model in use, :
	SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
      for all "c" in the range 0 <= c <= (MaxCT-1). 

Additionally, on every link, a DS-TE implementation MUST provide for 
configuration of up to 8 additional link parameters which are the 
eight other potential Bandwidth Constraints i.e. BC0, BC1 , ... BC7. 
The LSR MUST interpret these Bandwidth Constraints in accordance with 
the supported Bandwidth Constraint Model (i.e. what bandwidth 
constraint applies to what Class-Type and how). 

Where the Bandwidth Constraint Model imposes some relationship among 
the values to be configured for these Bandwidth Constraints, the LSR 
MUST enforce those at configuration time. For example, when the 
"Russian Doll" Bandwidth Constraints Model is used (See [DSTE-
RUSSIAN]), the LSR must ensure that BCi is configured smaller or 
equal to BCj, where i is greater than j, and that BC0 is equal 
to the Max Reservable Link Bandwidth. 
As another example, when the "Separate and Aggregate constraint Model"
is used 
(See [DSTE-SAM]), the LSR must ensure that all BCi are configured
smaller or 
equal to the Maximum Reservable Bandwidth.


Protocol draft "5.1. Bandwidth Constraints "
============================================
(this should also address some of Dimitry's Last Call comments on -proto
draft).

As detailed above in section 4.1.1, up to 8 Bandwidth Constraints 
( BCb, 0 <= b <= 7) are configurable on any given link. 

With DS-TE, the existing "Maximum Reservable Bw" sub-TLV is retained 
with a generalized semantic so that it MUST now be interpreted as 
the aggregate bandwidth constraint across all Class-Types, independently

of the Bandwidth Constraints Model.
 
This document also defines the following new optional sub-TLV to 
advertise the eight potential Bandwidth Constraints (BC0 to BC7): 

"Bandwidth Constraints" sub-TLV: 
Bla, bla, bla : unchanged

A DS-TE LSR MAY optionally advertise Bandwidth Constraints. 

A DS-TE LSR which does advertise Bandwidth Constraints MUST use the 
"Maximum Reservable Bw" sub-TLV and the new "Bandwidth Constraints" 
sub-TLV to do so. For example, 
considering the case where a Service Provider deploys DS-TE with TE-
classes associated with CT0 and CT1 only, and where the Bandwidth 
Constraints model is such that only BC0 and BC1 are relevant to CT0 
and CT1: a DS-TE LSR which does advertise Bandwidth Constraint would 
include the "Max Reservable Bw" sub-TLV and the "Bandwidth Constraints" 
sub-TLV in the IGP advertisement 
and the latter should contain only BC0 and BC1. 

Note that including the existing "Maximum Reservable Bw" sub-TLV when 
advertising Bandwidth Constraints is 
useful in migration situations where some LSRs in the network are not 
DS-TE capable (see Appendix C) and thus do not understand the new 
"Bandwidth Constraints" sub-TLV.  

Rest of section is unchanged.


RDM draft - handling advertisement of both "Max Res bw" and BC0
===============================================================
Some of the text that usd to be in proto needs to be moved (somewhere)
into Russian draft, as it is now specific to RDM. This text relates to
behaviour when receiving in IGP advertisment both a "Max Res Bw" and
BC0. It could read :

[DSTE-PROTO] states that 
"A DS-TE LSR which does advertise Bandwidth Constraints MUST use the 
"Maximum Reservable Bw" sub-TLV and the new "Bandwidth Constraints" 
sub-TLV to do so. " 
With RDM, BC0 is the Maximum Reservable Bandwidth. A DS-TE LSR receiving
both the 
old "Maximum Reservable Bw" sub-TLV and the new "Bandwidth Constraints"
sub-TLV for 
a given link where the RDM model is used, MAY ignore the "Maximum
Reservable Bw" sub-TLV.



From owner-te-wg@ops.ietf.org  Thu Apr 24 15:48:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00349
	for <tewg-archive@lists.ietf.org>; Thu, 24 Apr 2003 15:48:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 198mY7-0005Sx-00
	for te-wg-data@psg.com; Thu, 24 Apr 2003 19:38:27 +0000
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 198mY4-0005Sk-00
	for te-wg@ops.ietf.org; Thu, 24 Apr 2003 19:38:24 +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 h3OJcLfQ029941
	for <te-wg@ops.ietf.org>; Thu, 24 Apr 2003 15:38:21 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h3OJcK0S029937
	for <te-wg@ops.ietf.org>; Thu, 24 Apr 2003 15:38:21 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Thu, 24 Apr 2003 15:38:20 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: Re: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
In-Reply-To: <Pine.LNX.4.44.0304081048320.29948-100000@fido.nc.rr.com>
Message-ID: <Pine.LNX.4.44.0304241533430.29926-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-33.7 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      QUOTE_TWICE_1,REPLY_WITH_QUOTES,USER_AGENT_PINE,
	      X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


This WG last call has ended.  There was one comment by Waisum, I don't 
think it was to object to this document.

Therefore this document is completed for WG discussion at this time.

It will be forwarded to IESG with the PROTO draft, which is through the 
2nd week of it's 3 week WG last call.  

thanks,

Jim

On Tue, 8 Apr 2003, Jim Boyle wrote:

> 
> 
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.txt
> 
> This is WG last call for this draft to be advanced as expiremental RFC.
> 
> Last call ends in 2 weeks (4/22).
> 
> thanks,
> 
> Jim Boyle
> 
> 
> 
> 




From owner-te-wg@ops.ietf.org  Thu Apr 24 21:18: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 VAA12286
	for <tewg-archive@lists.ietf.org>; Thu, 24 Apr 2003 21:18:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 198rmc-0001Gh-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 01:13:46 +0000
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 198rm8-0001Fe-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 01:13:17 +0000
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3P1DFj15093
	for <te-wg@ops.ietf.org>; Thu, 24 Apr 2003 21:13:15 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R19YY4R>; Fri, 25 Apr 2003 03:13:14 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155016A3AFF@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Fri, 25 Apr 2003 03:13:12 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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

My summary:

- a lot of text... but not very focused and to the point (or at least
  I have trouble seeing the main points)
- not a "framework", rather an exploration of TE measurement related topics
  (more like  a summary-introduction)
- I am not an operator, but I think if I were one, then
  - if we were already doing TE measurement stuff (most likely) then 
    reading it seems a waste of time
  - if we were not yet doing any of it... then I wonder if this would
    be helpfull at all.
- W.r.t. the TEM WG work item, it says:
     The tewg interacts with the common control and measurement plane
     working group to abstract and define those parameters, measurements,
     and controls that traffic engineering needs in order to engineer
     the network. 
  So I would expect a CRISP set of "requirements for additional measurements,
  configurable/negotiable parameters/controls" ... but not the extensive
  exploration and text that I now see. Why do people (or the WG) think
  that this document meets the WG deliverable for TEM ??
- W.r.t. review:
  - 4 people from ATT support it. Waisum is one of them and is main editor.
    Others (Nick Duffield, Bob Cole) have some of their material listed in
    the doc.
  - 3 EDU users commented, 2 said they found it a good doc
    3rd one asked a few questions
  - Raymond Zhang is positive. He is from info.net ??? is that an operator?
  - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
    What role/function does he play/have? Operator, code/tool-developer?
  - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
    he/she added any comment. Do we know him/her?
    What role/function does he/she play/have? Operator, code/tool-developer?
  - Dimitri Papadimitrou (Alcatel) asked a question/suggested some text.
    I did not see if he likes the doc or not
  - Blain Christian (uunet, so maybe a real operator?) withdrew as co-editor
    That does not sound good (in my view)
- So where are the real operators that support this?

My thought is that I can do two things:

- send back to WG and say that this is "not good enough" and that I do not 
  feel comforatable to present it to IESG for approval.
  It does NOT meet (in my eyes) the WG deliverable for TEM.
- send it to IESG with my recommendation to NOT approve for same reasons.

So let me try the first option first and ask the WG what they have to say
to my review.

Bert




From owner-te-wg@ops.ietf.org  Fri Apr 25 09:09:04 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07558
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 09:09:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1992w4-000Pdp-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 13:08:16 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 1992w2-000Pdc-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 13:08:14 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 25 Apr 2003 15:08:06 +0100
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h3PD6Lqx007946;
	Fri, 25 Apr 2003 15:06:22 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 25 Apr 2003 15:08: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: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Date: Fri, 25 Apr 2003 14:08:11 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B51CC@xbe-lon-313.cisco.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Thread-Index: AcMKmwFf7JkHLw/kRTiRWoLGZDYSsQAj5AKg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 25 Apr 2003 13:08:12.0033 (UTC) FILETIME=[B9824F10:01C30B2B]
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 JAA07558

Jim,

The enhancement to the MAM definition that we're discussing has ripple
effects into -proto and into -russian (BTW from memory I think that
would address part, or all, of Waisum's comment).

So I would suggest issueing a new rev of -proto and -russian with the
corresponding edits before posting to IESG. I could post those fairly
quickly once we've concluded on the MAM definition on the list.

Makes sense?

Cheers

Francois

>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com] 
>> Sent: 24 April 2003 21:38
>> To: te-wg@ops.ietf.org
>> Subject: Re: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
>> 
>> 
>> 
>> This WG last call has ended.  There was one comment by 
>> Waisum, I don't 
>> think it was to object to this document.
>> 
>> Therefore this document is completed for WG discussion at this time.
>> 
>> It will be forwarded to IESG with the PROTO draft, which is 
>> through the 
>> 2nd week of it's 3 week WG last call.  
>> 
>> thanks,
>> 
>> Jim
>> 
>> On Tue, 8 Apr 2003, Jim Boyle wrote:
>> 
>> > 
>> > 
>> > 
>> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-r
ussian-02.txt
> 
> This is WG last call for this draft to be advanced as expiremental
RFC.
> 
> Last call ends in 2 weeks (4/22).
> 
> thanks,
> 
> Jim Boyle
> 
> 
> 
> 




From owner-te-wg@ops.ietf.org  Fri Apr 25 09:49: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 JAA08648
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 09:49:05 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1993bC-0004RP-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 13:50:46 +0000
Received: from ams-iport-1.cisco.com ([144.254.74.5])
	by psg.com with esmtp (Exim 3.36 #1)
	id 1993b8-0004R3-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 13:50:42 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 25 Apr 2003 15:50:32 +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 h3PDmiYa015848;
	Fri, 25 Apr 2003 15:48: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);
	 Fri, 25 Apr 2003 15:50:33 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Date: Fri, 25 Apr 2003 14:50:09 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B51CE@xbe-lon-313.cisco.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Thread-Index: AcMAXm/If2H0hERUSTegvFhodX9//wK0BUtA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Dimitry Haskin" <dhaskin@axiowave.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 25 Apr 2003 13:50:33.0909 (UTC) FILETIME=[A495CE50:01C30B31]
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 JAA08648

Dimitry,

Please check the draft text I proposed in message titled "Reflecting
new-MAM/SAM definition in diff-te drafts" (assuming the enhancement to
MAM definition). This should address your comments on section 5.1.

BTW: any thoughts on the "SAM" name?

Regarding your other comment, I actually think that "Max Link Bw" is
correct in the CAC formulas. 
draft-ietf-isis-traffic-xx says:
"This sub-TLV contains the maximum bandwidth that can be used on this
   link in this direction (from the system originating the LSP to its
   neighbors). This is useful for traffic engineering."
I believe the intent is that one given TE-tunnel can not exceed the max
link Bw. I believe this check is commonly implemented by multiple
implementations. Perhaps the text of draft-ietf-isis-traffic could be
made a little clearer on that. I will mention this to the authors (and
same for OSPF draft).
Also, it wouldn't make much sense to me to check separately that B is
below Max Reservable Bw, since Unreserved Bw will always be smaller than
Max Reservable bw.

Thanks for your review.

Francois

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 11 April 2003 21:05
>> To: 'Jim Boyle'; te-wg@ops.ietf.org
>> Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
>> 
>> 
>> 
>> Section 5.1, page 10:
>> 
>>   "With DS-TE, the existing "Maximum Reservable Bw" sub-TLV 
>> is retained 
>>   with a generalized semantic so that it MUST now be interpreted as 
>>   Bandwidth Constraint 0 (BC0)."
>> 
>> also Section 5.1, page 10:
>> 
>>   "A DS-TE LSR which does advertise Bandwidth Constraints, MAY also 
>>   include the existing "Maximum Reservable Bw" sub-TLV. This may be 
>>   useful in migration situations where some LSRs in the 
>> network are not 
>>   DS-TE capable (see Appendix C) and thus do not understand the new 
>>   "Bandwidth Constraints" sub-TLV. In that case, the DS-TE 
>> LSR MUST set 
>>   the value of the "Maximum Reservable Bw" sub-TLV to the 
>> same value as 
>>   the one for BC0 encoded in the "Bandwidth Constraints" sub-TLV. 
>>    
>>   A DS-TE LSR receiving both the old "Maximum Reservable Bw" sub-TLV 
>>   and the new "Bandwidth Constraints" sub-TLV for a given link MAY 
>>   ignore the "Maximum Reservable Bw" sub-TLV." 
>> 
>> The above statements are implying that the "Maximum 
>> Reservable Bw" sub-TLV
>> is redundant in the presence of Bandwidth Constraints. 
>> Furthermore, they
>> indicate that BC0 has semantics of the maximum reservable 
>> bandwidth. This
>> could be true for the RD model. However it is clearly not 
>> true for other
>> models. Therefore these statements should be removed from 
>> the specification
>> or, even better, replaced with something along the following lines:
>> 
>>   The "Maximum Reservable Bw" sub-TLV represents the 
>> aggregate bandwidth
>>   constraint of the link and as such complements the 
>> advertised Bandwidth
>>   Constraints.
>>   
>> 
>> Section 10.2, page 20:
>> 
>>   "A DS-TE LSR MUST support the following admission control rule: 
>>    
>>   Regardless of how the admission control algorithm actually 
>> computes 
>>   the unreserved bandwidth for TE-Class[i] for one of its 
>> local link, 
>>   an LSP of bandwidth B, of set-up preemption priority p and 
>> of Class-
>>   Type CTc is admissible on that link iff: 
>>    
>>        B <= unreserved bandwidth for TE-Class[i], AND 
>>        B <= Max Link Bandwidth 
>>            
>>         Where  
>>             
>>         - TE-Class [i] maps to  < CTc , p > in the LSR's 
>> configured TE-
>>           Class mapping 
>>         - Max Link Bandwidth is the maximum link bandwidth 
>> configured 
>>           on the link and advertised in IGP." 
>> 
>> 
>> "Max Link Bandwidth" should be replaced with "Maximum
>> Reservable Bandwidth".
>> 
>> 
>> Section 10.3.4, page 22
>> 
>>   "Regardless of how the admission control algorithm 
>> actually computes 
>>   the unreserved bandwidth for TE-Class[i] for one of its 
>> local link, 
>>   an LSP of bandwidth B, of set-up preemption priority p and 
>> of Class-
>>   Type CTc is admissible on that link iff: 
>>    
>>        (i)  B <= unreserved bandwidth for TE-Class[i], AND 
>>        (ii) B <= Max Link Bandwidth 
>>            
>>         Where  
>>             
>>         - TE-Class [i] maps to  < CTc , p > in the LSR's 
>> configured TE-
>>           Class mapping 
>>         - Max Link Bandwidth is the maximum link bandwidth 
>> configured 
>>           on the link and advertised in IGP." 
>> 
>> "Max Link Bandwidth" should be replaced with "Maximum
>> Reservable Bandwidth".
>> 
>> 
>> Dimitry
>> 
>> 
>> 
>> > -----Original Message-----
>> > From: Jim Boyle [mailto:jboyle@pdnets.com]
>> > Sent: Monday, April 07, 2003 11:56 PM
>> > To: te-wg@ops.ietf.org
>> > Subject: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
>> > 
>> > 
>> > 
>> > http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-pr
>> > oto-03.txt
>> > 
>> > This is WG last call for this draft to be advanced standards track.
>> > Since notice was sent to other WGs for review, we will 
>> take 3 weeks.
>> > 
>> > Last call for this draft closes 4/28.
>> > 
>> > thanks,
>> > 
>> > Jim Boyle
>> > 
>> > 
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Fri Apr 25 14:41: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 OAA18571
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 14:41:19 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19988b-000FjO-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 18:41:33 +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 19988V-000Fio-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 18:41:27 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F5F5@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        te-wg@ops.ietf.org
Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Date: Fri, 25 Apr 2003 14:41:17 -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

Francois,

See comments inline.

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: Friday, April 25, 2003 9:50 AM
> To: Dimitry Haskin; te-wg@ops.ietf.org
> Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
> 
> 
> Dimitry,
> 
> Please check the draft text I proposed in message titled "Reflecting
> new-MAM/SAM definition in diff-te drafts" (assuming the enhancement to
> MAM definition). This should address your comments on section 5.1.

I have no problems with the proposed text.

> 
> BTW: any thoughts on the "SAM" name?

No idea.

> 
> Regarding your other comment, I actually think that "Max Link Bw" is
> correct in the CAC formulas. 
> draft-ietf-isis-traffic-xx says:
> "This sub-TLV contains the maximum bandwidth that can be used on this
>    link in this direction (from the system originating the LSP to its
>    neighbors). This is useful for traffic engineering."
> I believe the intent is that one given TE-tunnel can not 
> exceed the max link Bw. I believe this check is commonly implemented by
multiple
> implementations. Perhaps the text of draft-ietf-isis-traffic could be
> made a little clearer on that. I will mention this to the authors (and
> same for OSPF draft).

I have to disagree. The quoted text refer to the bandwidth that can be
*used*. The disputed text in the proto draft talks about the admission
rules, i.e. bandwidth that can be admitted. There is a clear difference
between how much Bw can be used and how mach can be admitted. Otherwise,
what would be intended difference between "Max Link Bw" and "Maximum
Reservable Bw"? Furthermore, the same draft (draft-ietf-isis-traffic)
defines the max reservable link Bw as "maximum amount of bandwidth that can
be reserved in this direction on this link" which is  clearly applicable to
the traffic admission rules.

BTW, the OSPF TE draft (draft-katz-yeung-ospf-traffic-09.txt) make it
somewhat clearer by adding a sentence to the definition of the max link Bw:
   "The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
   can be used on this link in this direction (from the system
   originating the LSA to its neighbor), in IEEE floating point format.
   This is the true link capacity."

By any chance, are you confusing the "Max Link Bw" for the "Max LSP
Bandwidth" that is defined in draft-ietf-isis-gmpls-extensions-16? 

> Also, it wouldn't make much sense to me to check separately that B is
> below Max Reservable Bw, since Unreserved Bw will always be 
> smaller than
> Max Reservable bw.

If you're doing a path computation then checking only against the advertised
Unreserved Bw should be sufficient since the max reservable limit should
have already been taken in consideration when the advertised Unreserved Bw
was computed. However the disputed text talks about traffic admission not
path computation rules.

> 
> Thanks for your review.
> 
> Francois

You are welcome,
  Dimitry

> 
> >> -----Original Message-----
> >> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
> >> Sent: 11 April 2003 21:05
> >> To: 'Jim Boyle'; te-wg@ops.ietf.org
> >> Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
> >> 
> >> 
> >> 
> >> Section 5.1, page 10:
> >> 
> >>   "With DS-TE, the existing "Maximum Reservable Bw" sub-TLV 
> >> is retained 
> >>   with a generalized semantic so that it MUST now be 
> interpreted as 
> >>   Bandwidth Constraint 0 (BC0)."
> >> 
> >> also Section 5.1, page 10:
> >> 
> >>   "A DS-TE LSR which does advertise Bandwidth Constraints, 
> MAY also 
> >>   include the existing "Maximum Reservable Bw" sub-TLV. 
> This may be 
> >>   useful in migration situations where some LSRs in the 
> >> network are not 
> >>   DS-TE capable (see Appendix C) and thus do not 
> understand the new 
> >>   "Bandwidth Constraints" sub-TLV. In that case, the DS-TE 
> >> LSR MUST set 
> >>   the value of the "Maximum Reservable Bw" sub-TLV to the 
> >> same value as 
> >>   the one for BC0 encoded in the "Bandwidth Constraints" sub-TLV. 
> >>    
> >>   A DS-TE LSR receiving both the old "Maximum Reservable 
> Bw" sub-TLV 
> >>   and the new "Bandwidth Constraints" sub-TLV for a given link MAY 
> >>   ignore the "Maximum Reservable Bw" sub-TLV." 
> >> 
> >> The above statements are implying that the "Maximum 
> >> Reservable Bw" sub-TLV
> >> is redundant in the presence of Bandwidth Constraints. 
> >> Furthermore, they
> >> indicate that BC0 has semantics of the maximum reservable 
> >> bandwidth. This
> >> could be true for the RD model. However it is clearly not 
> >> true for other
> >> models. Therefore these statements should be removed from 
> >> the specification
> >> or, even better, replaced with something along the following lines:
> >> 
> >>   The "Maximum Reservable Bw" sub-TLV represents the 
> >> aggregate bandwidth
> >>   constraint of the link and as such complements the 
> >> advertised Bandwidth
> >>   Constraints.
> >>   
> >> 
> >> Section 10.2, page 20:
> >> 
> >>   "A DS-TE LSR MUST support the following admission control rule: 
> >>    
> >>   Regardless of how the admission control algorithm actually 
> >> computes 
> >>   the unreserved bandwidth for TE-Class[i] for one of its 
> >> local link, 
> >>   an LSP of bandwidth B, of set-up preemption priority p and 
> >> of Class-
> >>   Type CTc is admissible on that link iff: 
> >>    
> >>        B <= unreserved bandwidth for TE-Class[i], AND 
> >>        B <= Max Link Bandwidth 
> >>            
> >>         Where  
> >>             
> >>         - TE-Class [i] maps to  < CTc , p > in the LSR's 
> >> configured TE-
> >>           Class mapping 
> >>         - Max Link Bandwidth is the maximum link bandwidth 
> >> configured 
> >>           on the link and advertised in IGP." 
> >> 
> >> 
> >> "Max Link Bandwidth" should be replaced with "Maximum
> >> Reservable Bandwidth".
> >> 
> >> 
> >> Section 10.3.4, page 22
> >> 
> >>   "Regardless of how the admission control algorithm 
> >> actually computes 
> >>   the unreserved bandwidth for TE-Class[i] for one of its 
> >> local link, 
> >>   an LSP of bandwidth B, of set-up preemption priority p and 
> >> of Class-
> >>   Type CTc is admissible on that link iff: 
> >>    
> >>        (i)  B <= unreserved bandwidth for TE-Class[i], AND 
> >>        (ii) B <= Max Link Bandwidth 
> >>            
> >>         Where  
> >>             
> >>         - TE-Class [i] maps to  < CTc , p > in the LSR's 
> >> configured TE-
> >>           Class mapping 
> >>         - Max Link Bandwidth is the maximum link bandwidth 
> >> configured 
> >>           on the link and advertised in IGP." 
> >> 
> >> "Max Link Bandwidth" should be replaced with "Maximum
> >> Reservable Bandwidth".
> >> 
> >> 
> >> Dimitry
> >> 
> >> 
> >> 
> >> > -----Original Message-----
> >> > From: Jim Boyle [mailto:jboyle@pdnets.com]
> >> > Sent: Monday, April 07, 2003 11:56 PM
> >> > To: te-wg@ops.ietf.org
> >> > Subject: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
> >> > 
> >> > 
> >> > 
> >> > http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-pr
> >> > oto-03.txt
> >> > 
> >> > This is WG last call for this draft to be advanced 
> standards track.
> >> > Since notice was sent to other WGs for review, we will 
> >> take 3 weeks.
> >> > 
> >> > Last call for this draft closes 4/28.
> >> > 
> >> > thanks,
> >> > 
> >> > Jim Boyle
> >> > 
> >> > 
> >> > 
> >> 
> >> 
> 



From owner-te-wg@ops.ietf.org  Fri Apr 25 14:41:39 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18616
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 14:41:39 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1998B5-000G83-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 18:44:07 +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 1998AY-000G77-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 18:43:34 +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 h3PHwqnB026949
	for <te-wg@ops.ietf.org>; Fri, 25 Apr 2003 14:43:33 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314301369E0B; Fri, 25 Apr 2003 14:43:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Date: Fri, 25 Apr 2003 13:43:32 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137033@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
Thread-Index: AcMAXm/If2H0hERUSTegvFhodX9//wK0BUtAAAesseA=
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Dimitry Haskin" <dhaskin@axiowave.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 OAA18616

Francois,
  Since "Max Link Bw" is correct in the CAC formulas, where is
"Max Reservable Bw" used?
  Also, I agree with Dimitry's suggested replacement text below
for "Max Reservable Bw," which is more neutral and independent
of BC models.  I think the current text in the Proto draft is
slanted towards RDM.
  As discussed in
http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00184.html
the current MAM definition in the Requirements draft allows
preemption across CTs.  Clarification as described in this
posting can be added to the MAM spec.  Thus, there is no
inconsistency in the Requirements draft.  We do not need a
new name for an old model.
Thanks, Wai Sum 

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Friday, April 25, 2003 9:50 AM
To: Dimitry Haskin; te-wg@ops.ietf.org
Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt


Dimitry,

Please check the draft text I proposed in message titled "Reflecting
new-MAM/SAM definition in diff-te drafts" (assuming the enhancement to
MAM definition). This should address your comments on section 5.1.

BTW: any thoughts on the "SAM" name?

Regarding your other comment, I actually think that "Max Link Bw" is
correct in the CAC formulas. 
draft-ietf-isis-traffic-xx says:
"This sub-TLV contains the maximum bandwidth that can be used on this
   link in this direction (from the system originating the LSP to its
   neighbors). This is useful for traffic engineering."
I believe the intent is that one given TE-tunnel can not exceed the max
link Bw. I believe this check is commonly implemented by multiple
implementations. Perhaps the text of draft-ietf-isis-traffic could be
made a little clearer on that. I will mention this to the authors (and
same for OSPF draft).
Also, it wouldn't make much sense to me to check separately that B is
below Max Reservable Bw, since Unreserved Bw will always be smaller than
Max Reservable bw.

Thanks for your review.

Francois

>> -----Original Message-----
>> From: Dimitry Haskin [mailto:dhaskin@axiowave.com] 
>> Sent: 11 April 2003 21:05
>> To: 'Jim Boyle'; te-wg@ops.ietf.org
>> Subject: RE: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
>> 
>> 
>> 
>> Section 5.1, page 10:
>> 
>>   "With DS-TE, the existing "Maximum Reservable Bw" sub-TLV 
>> is retained 
>>   with a generalized semantic so that it MUST now be interpreted as 
>>   Bandwidth Constraint 0 (BC0)."
>> 
>> also Section 5.1, page 10:
>> 
>>   "A DS-TE LSR which does advertise Bandwidth Constraints, MAY also 
>>   include the existing "Maximum Reservable Bw" sub-TLV. This may be 
>>   useful in migration situations where some LSRs in the 
>> network are not 
>>   DS-TE capable (see Appendix C) and thus do not understand the new 
>>   "Bandwidth Constraints" sub-TLV. In that case, the DS-TE 
>> LSR MUST set 
>>   the value of the "Maximum Reservable Bw" sub-TLV to the 
>> same value as 
>>   the one for BC0 encoded in the "Bandwidth Constraints" sub-TLV. 
>>    
>>   A DS-TE LSR receiving both the old "Maximum Reservable Bw" sub-TLV 
>>   and the new "Bandwidth Constraints" sub-TLV for a given link MAY 
>>   ignore the "Maximum Reservable Bw" sub-TLV." 
>> 
>> The above statements are implying that the "Maximum 
>> Reservable Bw" sub-TLV
>> is redundant in the presence of Bandwidth Constraints. 
>> Furthermore, they
>> indicate that BC0 has semantics of the maximum reservable 
>> bandwidth. This
>> could be true for the RD model. However it is clearly not 
>> true for other
>> models. Therefore these statements should be removed from 
>> the specification
>> or, even better, replaced with something along the following lines:
>> 
>>   The "Maximum Reservable Bw" sub-TLV represents the 
>> aggregate bandwidth
>>   constraint of the link and as such complements the 
>> advertised Bandwidth
>>   Constraints.
>>   
>> 
>> Section 10.2, page 20:
>> 
>>   "A DS-TE LSR MUST support the following admission control rule: 
>>    
>>   Regardless of how the admission control algorithm actually 
>> computes 
>>   the unreserved bandwidth for TE-Class[i] for one of its 
>> local link, 
>>   an LSP of bandwidth B, of set-up preemption priority p and 
>> of Class-
>>   Type CTc is admissible on that link iff: 
>>    
>>        B <= unreserved bandwidth for TE-Class[i], AND 
>>        B <= Max Link Bandwidth 
>>            
>>         Where  
>>             
>>         - TE-Class [i] maps to  < CTc , p > in the LSR's 
>> configured TE-
>>           Class mapping 
>>         - Max Link Bandwidth is the maximum link bandwidth 
>> configured 
>>           on the link and advertised in IGP." 
>> 
>> 
>> "Max Link Bandwidth" should be replaced with "Maximum
>> Reservable Bandwidth".
>> 
>> 
>> Section 10.3.4, page 22
>> 
>>   "Regardless of how the admission control algorithm 
>> actually computes 
>>   the unreserved bandwidth for TE-Class[i] for one of its 
>> local link, 
>>   an LSP of bandwidth B, of set-up preemption priority p and 
>> of Class-
>>   Type CTc is admissible on that link iff: 
>>    
>>        (i)  B <= unreserved bandwidth for TE-Class[i], AND 
>>        (ii) B <= Max Link Bandwidth 
>>            
>>         Where  
>>             
>>         - TE-Class [i] maps to  < CTc , p > in the LSR's 
>> configured TE-
>>           Class mapping 
>>         - Max Link Bandwidth is the maximum link bandwidth 
>> configured 
>>           on the link and advertised in IGP." 
>> 
>> "Max Link Bandwidth" should be replaced with "Maximum
>> Reservable Bandwidth".
>> 
>> 
>> Dimitry
>> 
>> 
>> 
>> > -----Original Message-----
>> > From: Jim Boyle [mailto:jboyle@pdnets.com]
>> > Sent: Monday, April 07, 2003 11:56 PM
>> > To: te-wg@ops.ietf.org
>> > Subject: WG last call: draft-ietf-tewg-diff-te-proto-03.txt
>> > 
>> > 
>> > 
>> > http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-pr
>> > oto-03.txt
>> > 
>> > This is WG last call for this draft to be advanced standards track.
>> > Since notice was sent to other WGs for review, we will 
>> take 3 weeks.
>> > 
>> > Last call for this draft closes 4/28.
>> > 
>> > thanks,
>> > 
>> > Jim Boyle
>> > 
>> > 
>> > 
>> 
>> 




From owner-te-wg@ops.ietf.org  Fri Apr 25 15: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 PAA19149
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 15:00:01 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1998SE-000Ijy-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 19:01:50 +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 1998SB-000Ijk-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 19:01:47 +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 h3PHMq9p026025
	for <te-wg@ops.ietf.org>; Fri, 25 Apr 2003 14:01:46 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A31430136C8C4; Fri, 25 Apr 2003 15:01:46 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Date: Fri, 25 Apr 2003 14:01:34 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137034@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Thread-Index: AcL94J7ZoAVWCBFjRoyujPO67h6vJwKIfENwADqKrCAAkSPsYA==
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: <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 PAA19149

Francois,
   Since definitional issues of MAM are being addressed in
another thread, I've responded there.

   Based on your response below regarding QoS degradation in
RDM, I think some clarification is needed.  After the following
statement in page 5 of <draft-ietf-tewg-diff-te-russian-02.txt>:
"RDM can be used to simultaneously ensure bandwidth efficiency 
and protection against QoS degradation of all Class-Types"

something along the following line should be added:
"However, this may incur increased LSP blocking probability as
the maximum amount of established LSPs for a given CT needs to
be kept in line with the service rate that the scheduler can
provide to that CT."

Thanks, Wai Sum

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Tuesday, April 22, 2003 12:52 PM
To: Lai, Wai S (Waisum), ALABS
Cc: te-wg@ops.ietf.org
Subject: RE: WG last call: draft-ietf-tewg-diff-te-russian-02.txt


Waisum,

So the bottom line is that we assumed different definitions for MAM.
Your analysis assumed the model recently discussed on the list (ie "MAM
with the additional implied bandwidth constraint") as opposed to MAM as
currently defined. We do need to make some decision on this issue. And
then your analysis should be based on the outcome of that discussion.

Let me think more about the MAM definition issue.

Cheers

Francois

PS: What I mean by QoS degradation does not relate to blocking
probability. It refers to ensuring that the maximum amount of
established LSPs for a given CT is in line with the service rate that
the scheduler can provide to that CT. Please see the draft I issued a
while back on "BC Model considerations".

>> -----Original Message-----
>> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com] 
>> Sent: 21 April 2003 18:28
>> To: Francois Le Faucheur (flefauch)
>> Cc: Jim Boyle; te-wg@ops.ietf.org
>> Subject: RE: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
>> 
>> 
>> Francois,
>>    This message addresses Comment 1 in your message
>> http://ops.ietf.org/lists/te-wg/te-wg.2003/msg00228.html
>> as it relates to the Russian Dolls draft Last Call.
>> 
>>    Your following statement in the above message correctly 
>> reflects my
>> intent:
>> "Now, if I understand correctly, the approach you took for 
>> selecting BC
>> vales for RDM, was to pick BC values so that RDM would 
>> exhibit the same
>> blocking probabilities as MAM for a given reference LSP load."
>> 
>>   However, this statement is incorrect with respect to my comparison:
>> "For example, these values would accept a total load of 6+7+15=28
>> with MAM , while the maximum load is limited to BC3=15 with RDM."
>> 
>>   In <draft-wlai-tewg-bcmodel>, first of all, both MAM and RDM are
>> being offered the same load: 2.7 + 3.5 + 3.5 units as stated on the
>> top of page 5.  Furthermore, it is stated that
>> "As an example, consider a link with a capacity that allows 
>> a maximum 
>> of 15 LSPs from different classes to be established simultaneously.  
>> Overbooking is allowed, ..."
>>   Also, 
>> "bandwidth constraints (for MAM) are: 
>> up to 6 simultaneous LSPs for class 1,
>> up to 7 simultaneous LSPs for class 2, and 
>> up to 15 simultaneous LSPs for class 3."
>> 
>>   Note the wording "up to."  Thus, while it is true that the sum of
>> *maximum* bandwidth constraints can add up to 28, there can be no
>> more than 15 *simultaneous* LSPs allowed for all classes, since
>> this is the ultimate constraint imposed by the link capacity
>> (which is the same link for both MAM and RDM).
>> Thus, using your terminology in the above message, both MAM and RDM
>> in my draft are either (1) both are Porsches, or (2) both are backed
>> up by 3-ton-trailers.
>> 
>>   Per your request, the attached diagram shows the result for the
>> case you suggested for RDM: BC1=6, BC2=13, and BC3=28.  Comparing
>> this result with Figures 1 and 2 in <draft-wlai-tewg-bcmodel>,
>> it can be seen that the QoS degradation for class 1 is the same in
>> all three cases, even though the link capacity is now 28 is 
>> your case,
>> and 15 in the other two cases in my draft.
>> 
>>   This is contrary to the following claim made in
>> <draft-ietf-tewg-diff-te-russian-02.txt>:
>> "RDM can be used to simultaneously ensure bandwidth efficiency 
>> and protection against QoS degradation of all Class-Types"
>> 
>> Thanks, Wai Sum
>> 
>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com]
>> Sent: Tuesday, April 08, 2003 10:51 AM
>> To: te-wg@ops.ietf.org
>> Subject: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
>> 
>> 
>> 
>> 
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.t
xt

This is WG last call for this draft to be advanced as expiremental RFC.

Last call ends in 2 weeks (4/22).

thanks,

Jim Boyle






From owner-te-wg@ops.ietf.org  Fri Apr 25 15:11:02 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19404
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 15:11:02 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1998co-000KNR-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 19:12:46 +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 1998cm-000KNE-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 19:12:44 +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 h3PIwfkA028687
	for <te-wg@ops.ietf.org>; Fri, 25 Apr 2003 15:12:43 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A31430136E408; Fri, 25 Apr 2003 15:12:32 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Date: Fri, 25 Apr 2003 14:12:14 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA15774D@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: WG last call: draft-ietf-tewg-diff-te-russian-02.txt
Thread-Index: AcMKnQpgaXvDKIyMSySpI6JcjXR18wAvmyhw
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-16.9 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA19404

Jim,
  I think the issue that was brought up by my comment during the Last
Call needs resolution and requires a response in the current I-D.
Thanks, Wai Sum

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Thursday, April 24, 2003 3:38 PM
To: te-wg@ops.ietf.org
Subject: Re: WG last call: draft-ietf-tewg-diff-te-russian-02.txt



This WG last call has ended.  There was one comment by Waisum, I don't 
think it was to object to this document.

Therefore this document is completed for WG discussion at this time.

It will be forwarded to IESG with the PROTO draft, which is through the 
2nd week of it's 3 week WG last call.  

thanks,

Jim

On Tue, 8 Apr 2003, Jim Boyle wrote:

> 
> 
>
http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-russian-02.t
xt
> 
> This is WG last call for this draft to be advanced as expiremental
RFC.
> 
> Last call ends in 2 weeks (4/22).
> 
> thanks,
> 
> Jim Boyle
> 
> 
> 
> 





From owner-te-wg@ops.ietf.org  Fri Apr 25 15:30: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 PAA19762
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 15:30:35 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1998w6-000NLA-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 19:32:42 +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 1998w0-000NKm-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 19:32:36 +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 h3PIwf3a016249
	for <te-wg@ops.ietf.org>; Fri, 25 Apr 2003 14:32:35 -0500 (CDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314301371B58; Fri, 25 Apr 2003 15:32:35 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Fri, 25 Apr 2003 14:32:23 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A7072@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Reflecting new-MAM/SAM definition in diff-te drafts
Thread-Index: AcMJeml8BmEjHSmTTr+3lnTgXloVOwAVN74AAGNusgA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA19762

Francois,

I have some major concerns about your proposed MAM/SAM direction.  I don't think we want to introduce all this increased complexity in the BC models.  We can resolve the issues raised in recent discussions much more easily:

1. The MAM definition can be clarified in the current MAM specification draft to address the possible ambiguity in the DSTE requirements draft.  The DSTE requirements draft doesn't serve to be the defining I-D for any of the BC models, that's the purpose of the functional specifications of the various BC models.
2. Regarding the allowance of cross-CT preemption in MAM, it should be allowed (as several have assumed/interpreted), and that point should be clarified in the MAM specification draft. 
3. The 'maximum link bandwidth' parameter is a physical constraint and serves to limit the assignable sum of link bandwidth across class types.  In the recent discussion, this constraint has sometimes been referred to as an 'implicit max link BW constraint'.  However there is nothing 'implicit' about this constraint/parameter, it is an existing link parameter and a physical constraint on assignable link bandwidth.
4. Given comment #3, we don't need to use the 'max reservable link bandwidth' parameter instead of the 'maximum link bandwidth' parameter, as you have proposed.

Other related comments:

1. We definitely don't want to further extend ospf/isis to advertise more bandwidth constraints, as you stated in your email on 3/25/03:
"Where MAM currently has a Maximum Number of Bandwidth Constraints of 8 (i.e. one per CT), this model would have a maximum of 9 BCs (i.e. one per CT plus one aggregate). BTW, this in turn, would require change to the ISIS/OSPF extensions which can only advertise 8 Bandwidth Constraints."
Further complexity in ospf/isis lsa advertisements is unacceptable.
2. There is no need to add another BW constraint model (SAM), as you have proposed, to serve as an 'enhanced MAM'.  The point is to clarify MAM as stated above, which in fact has the same functionality you propose for SAM, we only need to make the clarifications in the MAM functional specification I-D.

Once again, we don't want to introduce all this additional complexity.  All we need to do at this point is to make some clarifications in the MAM functional specification I-D.

Thanks,
Jerry

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Wednesday, April 23, 2003 5:26 AM
To: te-wg@ops.ietf.org
Subject: Reflecting new-MAM/SAM definition in diff-te drafts

Hello,

Assuming there is agreement to add the enhancement to the current MAM
definition, below is a first cut at the main changes that would result
in the diff-te drafts. 
Could you check these out?

Thanks

Francois

MAM/SAM draft - Definition
===========================
The "newMAM/SAM" definition could look like this:

	o Maximum Number of Bandwidth Constraints (MaxBC)= 
		  Maximum Number of Class-Types (MaxCT) + 1 = 9
        (where one of the bandwidth constraints is the "Max reservable
Bandwidth")
	o for each value of b in the range 0 <= b <= 7: 
		Reserved (CTb) <= BCb, 
	o SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
		for all "c" in the range 0 <= c <= (MaxCT-1)

Illustration diagram would look like: 
   
  I------------------------------------------------------------I
  I--------------II-------------II-------------I               I
  I    CT2       II   CT1       II     CT0     I  CT2+CT1+CT0  I
  I--------------II-------------II-------------I               I
  I------------------------------------------------------------I
   
  <-----BC2------><-----BC1-----><-----BC0-----> 
  <------------------------Max Reservable Bandwidth------------>


MAM/SAM draft - Formulas for computing Unreserved bandwidth
============================================================
 The example formulas for computing Unreeserved Bandwidth would be
changed to:
   
        "Unreserved TE-Class [i]" = 
	 MIN [
	   [ BCc - SUM ( Reserved(CTc,q) ) ] for q <= p  ,
	   [Max Reservable Bandwidth - SUM ( Reserved (CTb,q) ) ] for q
<= p and 0 <= b <= 7,
           ]


RDM draft - Definition
===========================
The RDM definition could be slightly updated (to clarify relationship to
Max Res Bw which is differnet to new-MAM/SAM) like this:

	o Maximum Number of Bandwidth Constraints (MaxBC)= Maximum 
		Number of Class-Types (MaxCT) = 8 	
	 (where BC0 is the "Max reservable Bandwidth")
	o for each value of b in the range 0 <= b <= (MaxCT - 1): 
		SUM (Reserved (CTc)) <= BCb, 
		for all "c" in the range b <= c <= (MaxCT - 1)

Illustration diagram becomes:
   
  I------------------------------------------------------I 
  I-------------------------------I                      I 
  I--------------I                I                      I 
  I    CT2       I    CT2+CT1     I      CT2+CT1+CT0     I 
  I--------------I                I                      I 
  I-------------------------------I                      I 
  I------------------------------------------------------I 
   
  I-----BC2------> 
  I----------------------BC1------> 
  I-------------------------BC0 = Max Reservable Bw------> 


Protocol draft "4.1.1. Bandwidth Constraints (BCs)"
==============================================

For DS-TE, the existing "Maximum Reservable link bandwidth" parameter 
is retained and its semantic is generalized as the aggregate bandwidth 
constraints across all Class-Types. So that, independently of the
Bandwidth 
Constraint Model in use, :
	SUM (Reserved (CTc)) <= Max Reservable Bandwidth, 
      for all "c" in the range 0 <= c <= (MaxCT-1). 

Additionally, on every link, a DS-TE implementation MUST provide for 
configuration of up to 8 additional link parameters which are the 
eight other potential Bandwidth Constraints i.e. BC0, BC1 , ... BC7. 
The LSR MUST interpret these Bandwidth Constraints in accordance with 
the supported Bandwidth Constraint Model (i.e. what bandwidth 
constraint applies to what Class-Type and how). 

Where the Bandwidth Constraint Model imposes some relationship among 
the values to be configured for these Bandwidth Constraints, the LSR 
MUST enforce those at configuration time. For example, when the 
"Russian Doll" Bandwidth Constraints Model is used (See [DSTE-
RUSSIAN]), the LSR must ensure that BCi is configured smaller or 
equal to BCj, where i is greater than j, and that BC0 is equal 
to the Max Reservable Link Bandwidth. 
As another example, when the "Separate and Aggregate constraint Model"
is used 
(See [DSTE-SAM]), the LSR must ensure that all BCi are configured
smaller or 
equal to the Maximum Reservable Bandwidth.


Protocol draft "5.1. Bandwidth Constraints "
============================================
(this should also address some of Dimitry's Last Call comments on -proto
draft).

As detailed above in section 4.1.1, up to 8 Bandwidth Constraints 
( BCb, 0 <= b <= 7) are configurable on any given link. 

With DS-TE, the existing "Maximum Reservable Bw" sub-TLV is retained 
with a generalized semantic so that it MUST now be interpreted as 
the aggregate bandwidth constraint across all Class-Types, independently

of the Bandwidth Constraints Model.
 
This document also defines the following new optional sub-TLV to 
advertise the eight potential Bandwidth Constraints (BC0 to BC7): 

"Bandwidth Constraints" sub-TLV: 
Bla, bla, bla : unchanged

A DS-TE LSR MAY optionally advertise Bandwidth Constraints. 

A DS-TE LSR which does advertise Bandwidth Constraints MUST use the 
"Maximum Reservable Bw" sub-TLV and the new "Bandwidth Constraints" 
sub-TLV to do so. For example, 
considering the case where a Service Provider deploys DS-TE with TE-
classes associated with CT0 and CT1 only, and where the Bandwidth 
Constraints model is such that only BC0 and BC1 are relevant to CT0 
and CT1: a DS-TE LSR which does advertise Bandwidth Constraint would 
include the "Max Reservable Bw" sub-TLV and the "Bandwidth Constraints" 
sub-TLV in the IGP advertisement 
and the latter should contain only BC0 and BC1. 

Note that including the existing "Maximum Reservable Bw" sub-TLV when 
advertising Bandwidth Constraints is 
useful in migration situations where some LSRs in the network are not 
DS-TE capable (see Appendix C) and thus do not understand the new 
"Bandwidth Constraints" sub-TLV.  

Rest of section is unchanged.


RDM draft - handling advertisement of both "Max Res bw" and BC0
===============================================================
Some of the text that usd to be in proto needs to be moved (somewhere)
into Russian draft, as it is now specific to RDM. This text relates to
behaviour when receiving in IGP advertisment both a "Max Res Bw" and
BC0. It could read :

[DSTE-PROTO] states that 
"A DS-TE LSR which does advertise Bandwidth Constraints MUST use the 
"Maximum Reservable Bw" sub-TLV and the new "Bandwidth Constraints" 
sub-TLV to do so. " 
With RDM, BC0 is the Maximum Reservable Bandwidth. A DS-TE LSR receiving
both the 
old "Maximum Reservable Bw" sub-TLV and the new "Bandwidth Constraints"
sub-TLV for 
a given link where the RDM model is used, MAY ignore the "Maximum
Reservable Bw" sub-TLV.




From owner-te-wg@ops.ietf.org  Fri Apr 25 16:31: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 QAA21915
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 16:31:34 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 1999o1-0006kx-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 20:28:25 +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 1999nz-0006kl-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 20:28:23 +0000
Message-ID: <EB5FFC72F183D411B3820006295734290125F5F8@r2d2.axiowave.com>
From: Dimitry Haskin <dhaskin@axiowave.com>
To: "'Ash, Gerald R (Jerry), ALABS'" <gash@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: te-wg@ops.ietf.org
Subject: RE: Reflecting new-MAM/SAM definition in diff-te drafts
Date: Fri, 25 Apr 2003 16:28:14 -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

Gerald,

> 3. The 'maximum link bandwidth' parameter is a physical 
> constraint and serves to limit the assignable sum of link 
> bandwidth across class types.  In the recent discussion, this 
> constraint has sometimes been referred to as an 'implicit max 
> link BW constraint'.  However there is nothing 'implicit' 
> about this constraint/parameter, it is an existing link 
> parameter and a physical constraint on assignable link bandwidth.
> 4. Given comment #3, we don't need to use the 'max reservable 
> link bandwidth' parameter instead of the 'maximum link 
> bandwidth' parameter, as you have proposed.

The 'maximum link bandwidth' as defined is the actual link capacity and not
meant to be used as a reservation constraint. The 'max reservable link
bandwidth' was originally defined for this purpose. The amount of confusion
around these definitions puzzles me.

Dimitry

P.S. Excerpts from draft-katz-yeung-ospf-traffic-09.txt:


 2.5.6. Maximum Bandwidth

   The Maximum Bandwidth sub-TLV specifies the maximum bandwidth that
   can be used on this link in this direction (from the system
   originating the LSA to its neighbor), in IEEE floating point format.
   This is the true link capacity.  The units are bytes per second.

   The Maximum Bandwidth sub-TLV is TLV type 6, and is four octets in
   length.

 2.5.7. Maximum Reservable Bandwidth

   The Maximum Reservable Bandwidth sub-TLV specifies the maximum
   bandwidth that may be reserved on this link in this direction, in
   IEEE floating point format.  Note that this may be greater than the
   maximum bandwidth (in which case the link may be oversubscribed).
   This SHOULD be user-configurable; the default value should be the
   Maximum Bandwidth.  The units are bytes per second.

   The Maximum Reservable Bandwidth sub-TLV is TLV type 7, and is four
   octets in length.



From owner-te-wg@ops.ietf.org  Fri Apr 25 17:43: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 RAA24375
	for <tewg-archive@lists.ietf.org>; Fri, 25 Apr 2003 17:43:27 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 199Az6-000J2b-00
	for te-wg-data@psg.com; Fri, 25 Apr 2003 21:43:56 +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 199AyZ-000IyO-00
	for te-wg@ops.ietf.org; Fri, 25 Apr 2003 21:43:24 +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 h3PLCCm2004678
	for <te-wg@ops.ietf.org>; Fri, 25 Apr 2003 17:43:23 -0400 (EDT)
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 3E7A314301386365; Fri, 25 Apr 2003 17:43:22 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Fri, 25 Apr 2003 16:43:23 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA0A7073@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: AD review of: draft-ietf-tewg-measure-05.txt 
Thread-Index: AcMKyei94jXIoC4ISP+NbbMndpuEXgAl88bA
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@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 RAA24375

Bert,

Let's not throw the baby out with the bath-water.  The I-D serves a critical need and should go forward.

Regarding your comment:
'I would expect a CRISP set of "requirements for additional measurements, configurable/negotiable parameters/controls" ... but not the extensive exploration and text that I now see'.
The requirements *are* there for additional measurements, configurable/negotiable parameters/controls, but they need to be made more prominent and crisp (as you say).

I'd suggest to focus the main body of the I-D on these requirements/recommendations, and move the descriptive material to Annex(es).  The text has evolved over a long time with many comments and responses, as such it has gathered some moss along the way...  But the critical essence is there, and the requirements *need* to move forward to provide essential TE measurements.

Regarding your comment:
'if we were not yet doing any of it... then I wonder if this would be helpful at all.'
There are many important requirements/recommendations in the I-D.  As one example, the ability to collect traffic data to generate a traffic matrix (e.g., 'node-pair data', see Table in Section 10.1) is woefully lacking.  To get a flavor of the problem/need, see these papers on the topic (links to papers at http://www.research.att.com/~jrex/papers.html#tmeas):
A. Feldmann, A. Greenberg, C. Lund, N. Reingold, J. Rexford, G. True, "Deriving traffic demands for operational IP networks: Methodology and experience," IEEE/ACM Transactions on Networking, June 2001, pp. 265-279. (An earlier version appeared in Proc. ACM SIGCOMM, August/September 2000.)

This work shows the difficulty in deriving a traffic matrix with today's measurements.  A traffic matrix is basic to any network engineering or planning task.

Other critical traffic/performance measurement requirements identified in the I-D are also lacking and need to go forward.

A few more comments below.

Jerry
 
> - a lot of text... but not very focused and to the point (or at least
>   I have trouble seeing the main points)
> - not a "framework", rather an exploration of TE measurement related topics
>   (more like  a summary-introduction)

As above, the I-D serves a critical need.  The text can be focused on the requirements/recommendations, as suggested, and the descriptive stuff moved to an Annex.

> - I am not an operator, but I think if I were one, then
>   - if we were already doing TE measurement stuff (most likely) then 
>     reading it seems a waste of time
>   - if we were not yet doing any of it... then I wonder if this would
>     be helpful at all.

Operators have to get by with what is available, what else can we do?  This does not mean operators are already doing 'TE measurement stuff' in an adequate way, and that nothing further is required.  E.g., see comments above on derivation of a traffic matrix.

> - W.r.t. the TEM WG work item, it says:
>      The tewg interacts with the common control and measurement plane
>      working group to abstract and define those parameters, measurements,
>      and controls that traffic engineering needs in order to engineer
>      the network. 
>   So I would expect a CRISP set of "requirements for additional measurements,
>   configurable/negotiable parameters/controls" ... but not the extensive
>   exploration and text that I now see. Why do people (or the WG) think
>   that this document meets the WG deliverable for TEM ??

The requirements are there, and are critically needed.  They need to be brought out in a clear and crisp way, as suggested above.

> - W.r.t. review:
>   - 4 people from ATT support it. Waisum is one of them and is main editor.
>     Others (Nick Duffield, Bob Cole) have some of their material listed in
>     the doc.

So AT&T is stuffing the ballot box?  I'm mentioned in acknowledgements, others in references, are we disqualified to comment?  A certain set of people (*individuals*) who are the ones most interested/knowledgeable are the ones also most likely to comment.
 
>   - 3 EDU users commented, 2 said they found it a good doc
>     3rd one asked a few questions
>   - Raymond Zhang is positive. He is from info.net ??? is that an operator?

yes.

>   - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
>     What role/function does he play/have? Operator, code/tool-developer?

co-author.

>   - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
>     he/she added any comment. Do we know him/her?
>     What role/function does he/she play/have? Operator, code/tool-developer?

Level-3 employee?

>   - Dimitri Papadimitrou (Alcatel) asked a question/suggested some text.
>     I did not see if he likes the doc or not

did not object.

>   - Blain Christian (uunet, so maybe a real operator?) withdrew as co-editor
>     That does not sound good (in my view)
> - So where are the real operators that support this?

So *individuals* from AT&T, Infonet, France Telecom, and Level-3 (?) supported this, IETF does not have companies/operators positions.  Also, are you saying that the above operators are not 'real' operators versus other operators who you think are real operators?

> My thought is that I can do two things:
> 
> - send back to WG and say that this is "not good enough" and 
> that I do not 
>   feel comfortable to present it to IESG for approval.
>   It does NOT meet (in my eyes) the WG deliverable for TEM.
> - send it to IESG with my recommendation to NOT approve for 
> same reasons.
> 
> So let me try the first option first and ask the WG what they 
> have to say to my review.

I find it rather disappointing that you waited this long to come down on this I-D so hard.  If you had this level of concern, I think you should have tipped your hand long ago, but perhaps this is first time you have read the draft.  We have been admonished many times to read the draft and comment on this list, and many folks have abided by your wish.  

If we discard this I-D, the TEWG charter item also will go unfulfilled.  That's bad. I think the I-D serves an important need, and can address your comments, as above.  



From owner-te-wg@ops.ietf.org  Sat Apr 26 12:25:05 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22764
	for <tewg-archive@lists.ietf.org>; Sat, 26 Apr 2003 12:25:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 199STB-0003ul-00
	for te-wg-data@psg.com; Sat, 26 Apr 2003 16:24:09 +0000
Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 199ST5-0003uJ-00
	for te-wg@ops.ietf.org; Sat, 26 Apr 2003 16:24:03 +0000
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3QGO1O18673
	for <te-wg@ops.ietf.org>; Sat, 26 Apr 2003 12:24:01 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R19ZTAF>; Sat, 26 Apr 2003 18:23:59 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155016A3D2C@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Tewg (E-mail)"
	 <te-wg@ops.ietf.org>
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Sat, 26 Apr 2003 18:23:52 +0200
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

WG,

I'd like to hear/read more comments/feedback on my review.

Inline responses to the comments from Jerry

Thanks,
Bert 

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> Sent: vrijdag 25 april 2003 23:43
> To: Wijnen, Bert (Bert); Tewg (E-mail)
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
> 
> 
> Bert,
> 
> Let's not throw the baby out with the bath-water.  The I-D 
> serves a critical need and should go forward.
> 
Can you formulate the "critical need" that is being served?

> Regarding your comment:
> 'I would expect a CRISP set of "requirements for additional 
> measurements, configurable/negotiable parameters/controls" 
> ... but not the extensive exploration and text that I now see'.
> The requirements *are* there for additional measurements, 
> configurable/negotiable parameters/controls, but they need to 
> be made more prominent and crisp (as you say).
> 
Well cedrtainly I could not see them... they are too well hidden 
I guess :-(. So making them CRISP is certainly a good thing.

> I'd suggest to focus the main body of the I-D on these 
> requirements/recommendations, and move the descriptive 
> material to Annex(es).  The text has evolved over a long time 
> with many comments and responses, as such it has gathered 
> some moss along the way...  But the critical essence is 
> there, and the requirements *need* to move forward to provide 
> essential TE measurements.
> 
So.... it seems we agree that this title:
    A Framework for Internet Traffic Engineering Measurement
is not good and should be something aka
    Requirements for essential TE measurements, parameters and controls
and then of course the main body of the document should focus on
that and be clear as to waht is a real requirement and why.

> Regarding your comment:
> 'if we were not yet doing any of it... then I wonder if this 
> would be helpful at all.'
> There are many important requirements/recommendations in the 
> I-D.  As one example, the ability to collect traffic data to 
> generate a traffic matrix (e.g., 'node-pair data', see Table 
> in Section 10.1) is woefully lacking.  To get a flavor of the 
> problem/need, see these papers on the topic (links to papers 
> at http://www.research.att.com/~jrex/papers.html#tmeas):
> A. Feldmann, A. Greenberg, C. Lund, N. Reingold, J. Rexford, 
> G. True, "Deriving traffic demands for operational IP 
> networks: Methodology and experience," IEEE/ACM Transactions 
> on Networking, June 2001, pp. 265-279. (An earlier version 
> appeared in Proc. ACM SIGCOMM, August/September 2000.)
> 
I'd like to see in the document something aka:

   REQUIREMENT: ability to collect traffic data to generate trafix matrices
   DESCRIPTION: describe the details as to what traffic data is needed
   JUSTIFICATION: describe what the problem is that needs to be solved
   PRIORITY: x

Don't need to dwell too much on that... but have a concise and crisp
writeup. Maybe RFC3216 can serve as a good example.

> This work shows the difficulty in deriving a traffic matrix 
> with today's measurements.  A traffic matrix is basic to any 
> network engineering or planning task.
> 
> Other critical traffic/performance measurement requirements 
> identified in the I-D are also lacking and need to go forward.
> 
> A few more comments below.
> 
> Jerry
>  
> > - a lot of text... but not very focused and to the point 
> (or at least I have trouble seeing the main points)
> > - not a "framework", rather an exploration of TE measurement 
> >   related topics (more like  a summary-introduction)
> 
> As above, the I-D serves a critical need.  The text can be 
> focused on the requirements/recommendations, as suggested, 
> and the descriptive stuff moved to an Annex.
> 
One could wonder how much of the descriptive stuff is really
helpful or usefull. But if it is in an ANEX, then maybe that is
OK. I would say however, that if we have the requirements
crisply formulated, with description, justification and priority,
then one would hope that a lot of additional text is not needed
(not even in an anex). Think about the audience. It would be
protocol developers and/or vendors who have to understand the
requirement and be able to make modifications to their protocol
and/or products to meet the requirement.


> > - I am not an operator, but I think if I were one, then
> >   - if we were already doing TE measurement stuff (most 
> >     likely) then reading it seems a waste of time
> >   - if we were not yet doing any of it... then I wonder if 
> >     this would be helpful at all.
> 
> Operators have to get by with what is available, what else 
> can we do?  This does not mean operators are already doing 
> 'TE measurement stuff' in an adequate way, and that nothing 
> further is required.  E.g., see comments above on derivation 
> of a traffic matrix.
> 
I would hope operators can also understand and support the 
requirements. If not, then I really doubt that they are valid
requirements. And they must understand them, so that together
the operators can say to protocol developing WGs and to vendors
that these are the set of requirements to be met.

> > - W.r.t. the TEM WG work item, it says:
> >      The tewg interacts with the common control and measurement plane
> >      working group to abstract and define those parameters, measurements,
> >      and controls that traffic engineering needs in order to engineer
> >      the network. 
> >   So I would expect a CRISP set of "requirements for additional measurements,
> >   configurable/negotiable parameters/controls" ... but not the extensive
> >   exploration and text that I now see. Why do people (or the WG) think
> >   that this document meets the WG deliverable for TEM ??
> 
> The requirements are there, and are critically needed.  They 
> need to be brought out in a clear and crisp way, as suggested above.
> 
Yea.. you keep repeating that.

> > - W.r.t. review:
> >   - 4 people from ATT support it. Waisum is one of them and is main editor.
> >     Others (Nick Duffield, Bob Cole) have some of their material listed in
> >     the doc.
> 
> So AT&T is stuffing the ballot box?

That was not what I am saying. My point was more: it is clear that those
people who have contributed support the document. Would be strange if they
did not, would it not? But I can see now that maybe I should have made
my statement a bit different.

> I'm mentioned in acknowledgements, others in references, are we
> disqualified to comment?  A certain set of people (*individuals*)
> who are  the ones most interested/knowledgeable are the ones also
> most likely to comment.
>  
> >   - 3 EDU users commented, 2 said they found it a good doc
> >     3rd one asked a few questions
> >   - Raymond Zhang is positive. He is from info.net ???
> >     is that an operator?
> 
> yes.
I thought so but was not sure. Maybe Raymond can answer himself, no?
Raymond, can you fill me in what sort of network you operate?
Feel free to do so privately if you prefer that.

> 
> >   - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
> >     What role/function does he play/have? Operator, code/tool-developer?
> 
> co-author.
> 
Ah... ok, so obvious that he would support it. Should have been in
my first list of people above. 
You did not answer (but better if Richard does himself) if he is
and operator or what role plays in his daily life. The reason I ask
this is because I want to udnerstand their background and the eyes
and context that they probably have used to review.

> >   - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
> >     he/she added any comment. Do we know him/her?
> >     What role/function does he/she play/have? Operator, code/tool-developer?
> 
> Level-3 employee?
> 
Can you be more specific? Is he/she in the accounting dept? I guess not.
But again, I want to understand the context within which the review was done.

> >   - Dimitri Papadimitrou (Alcatel) asked a question/suggested some text.
> >     I did not see if he likes the doc or not
> 
> did not object.
> 
> >   - Blain Christian (uunet, so maybe a real operator?) 
> >     withdrew as co-editor
> >     That does not sound good (in my view)
> > - So where are the real operators that support this?
> 
> So *individuals* from AT&T, Infonet, France Telecom, and 
> Level-3 (?) supported this, IETF does not have 
> companies/operators positions.  Also, are you saying that the 
> above operators are not 'real' operators versus other 
> operators who you think are real operators?
> 
Sorry for the bad wording. When I use company names, I try to
see how many differnt viewpoints from people active in different 
types of networks have looked at it. From their operational experience.
I do not consider them as speaking for their company, but indeed as
individuals. I'd like to see comments/review/support from all 
types of operators, that is carriers, telecom operators, cors ISPs,
Access ISPs, small ISPs, Enterpise Networks... etc.

> > My thought is that I can do two things:
> > 
> > - send back to WG and say that this is "not good enough" and 
> >   that I do not 
> >   feel comfortable to present it to IESG for approval.
> >   It does NOT meet (in my eyes) the WG deliverable for TEM.
> > - send it to IESG with my recommendation to NOT approve for 
> >   same reasons.
> > 
> > So let me try the first option first and ask the WG what they 
> > have to say to my review.
> 
> I find it rather disappointing that you waited this long to 
> come down on this I-D so hard.  If you had this level of 
> concern, I think you should have tipped your hand long ago, 
> but perhaps this is first time you have read the draft.

That is a valid complaint. We are aware that a lot of the AD/IESG level
review takes place too late in the process. Not easy to fix, we (ADs)
all have trouble to keep up with what we have on IESG agenda, let alone
to dive into many WG docuemnts early. We try to improve... but in this
case I missed it.

Now I do understand that the WG chairs have been pushing back on this
in the beginning quite a bit too. I believe that the doc has improved 
quite a bit since the earlier versions... but when I review it in
the context of the WG deliverable, then I am clearly still very
dissappointed. If you say that all the "requirements" are hidden in
that doc, then pls try to make them clear. It seems that needs major
rework.

> We have been admonished many times to read the draft and comment 
> on this list, and many folks have abided by your wish.  
> 
I guess it depends on what you count as "many". When I was a kid,
we joked about people counting:  1,2,3,many. Mmm.. maybe that statement
is not appropriate. 

> If we discard this I-D, the TEWG charter item also will go 
> unfulfilled.  That's bad. I think the I-D serves an important 
> need, and can address your comments, as above.  
> 
But I'd rather have us confess that we were unable to deliver on a
WG item than us delivering something that is not in good shape
(or bad quality, which I think is the case).

Hope this explains my posting a bit better.
Bert



From owner-te-wg@ops.ietf.org  Sun Apr 27 06:49:38 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22118
	for <tewg-archive@lists.ietf.org>; Sun, 27 Apr 2003 06:49:37 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 199jgL-0003gp-00
	for te-wg-data@psg.com; Sun, 27 Apr 2003 10:46:53 +0000
Received: from relais-inet.francetelecom.com ([212.234.67.6] helo=relais-inet-03.francetelecom.fr)
	by psg.com with esmtp (Exim 3.36 #1)
	id 199jgF-0003gY-00
	for te-wg@ops.ietf.org; Sun, 27 Apr 2003 10:46:48 +0000
Received: from [193.248.188.47] by relais-filtrant-03.francetelecom.fr with ESMTP for te-wg@ops.ietf.org; Sun, 27 Apr 2003 12:46:45 +0200
Received: from fedft01a.francetelecom.fr by relais-filtrant-03.francetelecom.fr with ESMTP for te-wg@ops.ietf.org; Sun, 27 Apr 2003 12:46:45 +0200
Received: from [193.249.139.219] by fedft01a.francetelecom.fr with ESMTP for te-wg@ops.ietf.org; Sun, 27 Apr 2003 12:46:44 +0200
Received: from igt2bg036 ([10.172.1.10]) by
          smtp7.smtpft.francetelecom.fr (Netscape Messaging Server 4.15)
          with SMTP id HE00LS01.G0G; Sun, 27 Apr 2003 12:46:40 +0200 
Reply-To: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
From: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
To: "'Wijnen, Bert \(Bert\)'" <bwijnen@lucent.com>,
        "'Ash, Gerald R \(Jerry\), ALABS'" <gash@att.com>,
        "'Tewg \(E-mail\)'" <te-wg@ops.ietf.org>
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Sun, 27 Apr 2003 12:41:11 +0200
Message-Id: <001b01c30ca9$858e07b0$0a01ac0a@buriapren.w2k.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155016A3D2C@nl0006exch001u.nl.lucent.com>
X-Spam-Status: No, hits=-13.6 required=5.0
	tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Dear all,

Additional comments below.

-----Message d'origine-----
De : owner-te-wg@ops.ietf.org [mailto:owner-te-wg@ops.ietf.org]De la
part de Wijnen, Bert (Bert)
Envoyé : samedi 26 avril 2003 18:24
À : Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
Objet : RE: AD review of: draft-ietf-tewg-measure-05.txt


WG,

I'd like to hear/read more comments/feedback on my review.

Inline responses to the comments from Jerry

Thanks,
Bert

> -----Original Message-----
> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> Sent: vrijdag 25 april 2003 23:43
> To: Wijnen, Bert (Bert); Tewg (E-mail)
> Cc: Ash, Gerald R (Jerry), ALABS
> Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt
>
>
> Bert,
>
> Let's not throw the baby out with the bath-water.  The I-D
> serves a critical need and should go forward.
>
Can you formulate the "critical need" that is being served?

CJ: the specification and the enforcement of a traffic engineering policy
(or a set of) rely upon the activation of complex features, hence yielding
the critical need to qualify how well is such a policy enforced and how
efficient it is, from both a network resource optimization standpoint (hence
affecting the network planning policy) and from a QoS standpoint (like the
provisioning of (hard) guarantees (loss, inter-packet delay variation,
one-way transit delay, etc.) as far as the level of quality associated to a
given service is concerned). Qualification of the efficiency of such
policies obviously rely upon measurement techniques and parameters, and
IMHO, this draft depicts a pretty good set of requirements that not only
reflect the aforementioned (and defined) critical need, but which also
provides an accurate reference/cornerstone for the definition of TE
measurement framework and tools. That's the reason why I fully support this
draft.

> Regarding your comment:
> 'I would expect a CRISP set of "requirements for additional
> measurements, configurable/negotiable parameters/controls"
> ... but not the extensive exploration and text that I now see'.
> The requirements *are* there for additional measurements,
> configurable/negotiable parameters/controls, but they need to
> be made more prominent and crisp (as you say).
>
Well cedrtainly I could not see them... they are too well hidden
I guess :-(. So making them CRISP is certainly a good thing.

CJ: I'd like to hear other comments about the readability of the contents of
this draft. The fact you find these requirements hard too find does not
necessarily mean that all the reading community (including IESG members)
shares this point of view.

> I'd suggest to focus the main body of the I-D on these
> requirements/recommendations, and move the descriptive
> material to Annex(es).  The text has evolved over a long time
> with many comments and responses, as such it has gathered
> some moss along the way...  But the critical essence is
> there, and the requirements *need* to move forward to provide
> essential TE measurements.
>
So.... it seems we agree that this title:
    A Framework for Internet Traffic Engineering Measurement
is not good and should be something aka
    Requirements for essential TE measurements, parameters and controls
and then of course the main body of the document should focus on
that and be clear as to waht is a real requirement and why.

CJ: "Requirements for TE measurement" should be sufficient.

> Regarding your comment:
> 'if we were not yet doing any of it... then I wonder if this
> would be helpful at all.'
> There are many important requirements/recommendations in the
> I-D.  As one example, the ability to collect traffic data to
> generate a traffic matrix (e.g., 'node-pair data', see Table
> in Section 10.1) is woefully lacking.  To get a flavor of the
> problem/need, see these papers on the topic (links to papers
> at http://www.research.att.com/~jrex/papers.html#tmeas):
> A. Feldmann, A. Greenberg, C. Lund, N. Reingold, J. Rexford,
> G. True, "Deriving traffic demands for operational IP
> networks: Methodology and experience," IEEE/ACM Transactions
> on Networking, June 2001, pp. 265-279. (An earlier version
> appeared in Proc. ACM SIGCOMM, August/September 2000.)
>
I'd like to see in the document something aka:

   REQUIREMENT: ability to collect traffic data to generate trafix matrices
   DESCRIPTION: describe the details as to what traffic data is needed
   JUSTIFICATION: describe what the problem is that needs to be solved
   PRIORITY: x

Don't need to dwell too much on that... but have a concise and crisp
writeup. Maybe RFC3216 can serve as a good example.

CJ: it's basically a matter of presenting things (and I don't like the
notion of priority you seem to intriduce in your suggestion, because (1) the
so-called importance of a requirement may very well vary from one operator
to another (because of the range of service offerings actually supported,
because of the network topology, etc.), and (2) priority generally implies
classification and reference, which to me, is pointless as far as a
requirements document is concerned - see RFC 3139, for example).

> This work shows the difficulty in deriving a traffic matrix
> with today's measurements.  A traffic matrix is basic to any
> network engineering or planning task.
>
> Other critical traffic/performance measurement requirements
> identified in the I-D are also lacking and need to go forward.
>
> A few more comments below.
>
> Jerry
>
> > - a lot of text... but not very focused and to the point
> (or at least I have trouble seeing the main points)
> > - not a "framework", rather an exploration of TE measurement
> >   related topics (more like  a summary-introduction)
>
> As above, the I-D serves a critical need.  The text can be
> focused on the requirements/recommendations, as suggested,
> and the descriptive stuff moved to an Annex.
>
One could wonder how much of the descriptive stuff is really
helpful or usefull. But if it is in an ANEX, then maybe that is
OK. I would say however, that if we have the requirements
crisply formulated, with description, justification and priority,
then one would hope that a lot of additional text is not needed
(not even in an anex). Think about the audience. It would be
protocol developers and/or vendors who have to understand the
requirement and be able to make modifications to their protocol
and/or products to meet the requirement.

CJ: your suggestion of putting examples in an appendix is fine, but I'm
still not convinced of the efficiency of your proposal (description,
justification, etc. - see above comment), simply because you personally
found this document hard to read.


> > - I am not an operator, but I think if I were one, then
> >   - if we were already doing TE measurement stuff (most
> >     likely) then reading it seems a waste of time
> >   - if we were not yet doing any of it... then I wonder if
> >     this would be helpful at all.
>
> Operators have to get by with what is available, what else
> can we do?  This does not mean operators are already doing
> 'TE measurement stuff' in an adequate way, and that nothing
> further is required.  E.g., see comments above on derivation
> of a traffic matrix.
>
I would hope operators can also understand and support the
requirements. If not, then I really doubt that they are valid
requirements. And they must understand them, so that together
the operators can say to protocol developing WGs and to vendors
that these are the set of requirements to be met.

CJ: I fully understand and support the requirements described in this draft.
And I'm pretty sure I'm not the only operator's representative who fully
understands and supports the contents of this draft.

> > - W.r.t. the TEM WG work item, it says:
> >      The tewg interacts with the common control and measurement plane
> >      working group to abstract and define those parameters,
measurements,
> >      and controls that traffic engineering needs in order to engineer
> >      the network.
> >   So I would expect a CRISP set of "requirements for additional
measurements,
> >   configurable/negotiable parameters/controls" ... but not the extensive
> >   exploration and text that I now see. Why do people (or the WG) think
> >   that this document meets the WG deliverable for TEM ??
>
> The requirements are there, and are critically needed.  They
> need to be brought out in a clear and crisp way, as suggested above.
>
Yea.. you keep repeating that.

CJ: being ironic and cynical doesn't help the discussion that much.

> > - W.r.t. review:
> >   - 4 people from ATT support it. Waisum is one of them and is main
editor.
> >     Others (Nick Duffield, Bob Cole) have some of their material listed
in
> >     the doc.
>
> So AT&T is stuffing the ballot box?

That was not what I am saying. My point was more: it is clear that those
people who have contributed support the document. Would be strange if they
did not, would it not? But I can see now that maybe I should have made
my statement a bit different.

> I'm mentioned in acknowledgements, others in references, are we
> disqualified to comment?  A certain set of people (*individuals*)
> who are  the ones most interested/knowledgeable are the ones also
> most likely to comment.
>
> >   - 3 EDU users commented, 2 said they found it a good doc
> >     3rd one asked a few questions
> >   - Raymond Zhang is positive. He is from info.net ???
> >     is that an operator?
>
> yes.
I thought so but was not sure. Maybe Raymond can answer himself, no?
Raymond, can you fill me in what sort of network you operate?
Feel free to do so privately if you prefer that.

CJ: I'm not sure I understand what you're trying to get to here. Are we
supposed to *justify* our position and/or our networking conditions to have
the right to write and submit a document to the IETF? I'd like to hear  the
opinion of IESG representatives on this subject.

>
> >   - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
> >     What role/function does he play/have? Operator, code/tool-developer?
>
> co-author.
>
Ah... ok, so obvious that he would support it. Should have been in
my first list of people above.
You did not answer (but better if Richard does himself) if he is
and operator or what role plays in his daily life. The reason I ask
this is because I want to udnerstand their background and the eyes
and context that they probably have used to review.

> >   - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
> >     he/she added any comment. Do we know him/her?
> >     What role/function does he/she play/have? Operator,
code/tool-developer?
>
> Level-3 employee?
>
Can you be more specific? Is he/she in the accounting dept? I guess not.
But again, I want to understand the context within which the review was
done.

CJ: as far as the document's review is concerned, it has followed the basic
rules - submitted to the tewg WG mailing list, waited for comments, issued
the updated version, gone into a WG last call procedure and then submitted
to the IESG for review. Why are you *demanding* the background, the position
(maybe the skills, resumes while you're in this questioning process?), etc.
of the people who took some of their time to writte and/or review this
document and possibly make some comments/suggestions? What's so specific
with this document that justifies this kind of inquisition?
> >   - Dimitri Papadimitrou (Alcatel) asked a question/suggested some text.
> >     I did not see if he likes the doc or not
>
> did not object.
>
> >   - Blain Christian (uunet, so maybe a real operator?)
> >     withdrew as co-editor
> >     That does not sound good (in my view)
> > - So where are the real operators that support this?
>
> So *individuals* from AT&T, Infonet, France Telecom, and
> Level-3 (?) supported this, IETF does not have
> companies/operators positions.  Also, are you saying that the
> above operators are not 'real' operators versus other
> operators who you think are real operators?
>
Sorry for the bad wording. When I use company names, I try to
see how many differnt viewpoints from people active in different
types of networks have looked at it. From their operational experience.
I do not consider them as speaking for their company, but indeed as
individuals. I'd like to see comments/review/support from all
types of operators, that is carriers, telecom operators, cors ISPs,
Access ISPs, small ISPs, Enterpise Networks... etc.

CJ: why don't you clearly state what you dislike about this document instead
of demanding an echo from all the Internet community (you should also
include end customers, since TE may have an impact on the level of quality
of the service they've subscribed to, hence imposing service providers that
they fulfill their commitment by providing the appropriate measurements on a
regular basis)?

> > My thought is that I can do two things:
> >
> > - send back to WG and say that this is "not good enough" and
> >   that I do not
> >   feel comfortable to present it to IESG for approval.
> >   It does NOT meet (in my eyes) the WG deliverable for TEM.
> > - send it to IESG with my recommendation to NOT approve for
> >   same reasons.
> >
> > So let me try the first option first and ask the WG what they
> > have to say to my review.
>
> I find it rather disappointing that you waited this long to
> come down on this I-D so hard.  If you had this level of
> concern, I think you should have tipped your hand long ago,
> but perhaps this is first time you have read the draft.

That is a valid complaint. We are aware that a lot of the AD/IESG level
review takes place too late in the process. Not easy to fix, we (ADs)
all have trouble to keep up with what we have on IESG agenda, let alone
to dive into many WG docuemnts early. We try to improve... but in this
case I missed it.

Now I do understand that the WG chairs have been pushing back on this
in the beginning quite a bit too. I believe that the doc has improved
quite a bit since the earlier versions... but when I review it in
the context of the WG deliverable, then I am clearly still very
dissappointed. If you say that all the "requirements" are hidden in
that doc, then pls try to make them clear. It seems that needs major
rework.

> We have been admonished many times to read the draft and comment
> on this list, and many folks have abided by your wish.
>
I guess it depends on what you count as "many". When I was a kid,
we joked about people counting:  1,2,3,many. Mmm.. maybe that statement
is not appropriate.

CJ: this is the kind of argument we could also put forward when considering
other initiatives, such as the recent creation of the netconf WG for
example, based on an individual contribution that didn't get too much echo.
In this case, surprisingly enough, I can see that a silent majority was good
enough to launch yet another WG (hence additional contributions).

But when, say, 5 to 10 people have expressed their opinions on a
*requirements* document that is part of the tewg WG charter, and that this
document has been updated accordingly so that yet another silent majority
didn't make any specific objection so far, then the document is judged of
bad quality by a single person.

This is simply *unfair*, especially when this person is ready to consider
specifications of solutions (I'm referring to the inter-domain TE stuff -
see the IETF56 tewg WG minutes) *before* the accompanying/reference
requirements document has been accepted by the tewg WG as a WG document, and
discussed by the WG members.

Cheers,

Christian.

> If we discard this I-D, the TEWG charter item also will go
> unfulfilled.  That's bad. I think the I-D serves an important
> need, and can address your comments, as above.
>
But I'd rather have us confess that we were unable to deliver on a
WG item than us delivering something that is not in good shape
(or bad quality, which I think is the case).

Hope this explains my posting a bit better.
Bert




From owner-te-wg@ops.ietf.org  Sun Apr 27 08:01: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 IAA23086
	for <tewg-archive@lists.ietf.org>; Sun, 27 Apr 2003 08:01:06 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 199kqm-000BvT-00
	for te-wg-data@psg.com; Sun, 27 Apr 2003 12:01:44 +0000
Received: from alc245.alcatel.be ([195.207.101.245] helo=relay4.alcatel.be)
	by psg.com with esmtp (Exim 3.36 #1)
	id 199kqg-000BvD-00
	for te-wg@ops.ietf.org; Sun, 27 Apr 2003 12:01:38 +0000
Received: from bemail05.net.alcatel.be (bemail05.net.alcatel.be [138.203.144.16])
	by relay4.alcatel.be (8.12.9/8.12.9) with ESMTP id h3RC3rLC000608;
	Sun, 27 Apr 2003 14:03:53 +0200
Received: from alcatel.be ([138.203.137.2])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003042714012397:1460 ;
          Sun, 27 Apr 2003 14:01:23 +0200 
Message-ID: <3EABC82B.3050208@alcatel.be>
Date: Sun, 27 Apr 2003 14:08:11 +0200
From: Dimitri.Papadimitriou@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt
References: <7D5D48D2CAA3D84C813F5B154F43B155016A3D2C@nl0006exch001u.nl.lucent.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 04/27/2003 14:01:25,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 04/27/2003 14:01:27,
	Serialize complete at 04/27/2003 14:01:27
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Status: No, hits=-34.4 required=5.0
	tests=BAYES_00,EMAIL_ATTRIBUTION,NO_REAL_NAME,QUOTED_EMAIL_TEXT,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

bert,

the proposed update meets the comments i raised,

now my two cents, as it stands now i see this i-d more
as an "analysis of the requirements for tem models and
techniques" since imho the authors took an analytical
approach and in order to probably to come with more
"crispy" input for the tewg (since the objective was
here to "Document additional measurements needed for
TE (TEM)") expansion starting from the conclusion
might be a way to proceed (take this as a suggestion
to help things moving forward) if this is what the
tewg consents to do.

see also in-line...

Wijnen, Bert (Bert) wrote:
> WG,
> 
> I'd like to hear/read more comments/feedback on my review.
> 
> Inline responses to the comments from Jerry
> 
> Thanks,
> Bert 
> 
> 
>>-----Original Message-----
>>From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
>>Sent: vrijdag 25 april 2003 23:43
>>To: Wijnen, Bert (Bert); Tewg (E-mail)
>>Cc: Ash, Gerald R (Jerry), ALABS
>>Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
>>
>>
>>Bert,
>>
>>Let's not throw the baby out with the bath-water.  The I-D 
>>serves a critical need and should go forward.
>>
> 
> Can you formulate the "critical need" that is being served?
> 

well, i think here you ask a critical question but is your
question not just expanding on the reasons why this has
been included within the charter of the wg ? i think that
section 4.4 of RFC 3346 expand on this

>>Regarding your comment:
>>'I would expect a CRISP set of "requirements for additional 
>>measurements, configurable/negotiable parameters/controls" 
>>... but not the extensive exploration and text that I now see'.
>>The requirements *are* there for additional measurements, 
>>configurable/negotiable parameters/controls, but they need to 
>>be made more prominent and crisp (as you say).
> 
> Well cedrtainly I could not see them... they are too well hidden 
> I guess :-(. So making them CRISP is certainly a good thing. 

this is what i'd suggest also (in case of re-spin), expand
section were such statement can be summarized in order to
reflect the achievements here for the tewg ...

>>I'd suggest to focus the main body of the I-D on these 
>>requirements/recommendations, and move the descriptive 
>>material to Annex(es).  The text has evolved over a long time 
>>with many comments and responses, as such it has gathered 
>>some moss along the way...  But the critical essence is 
>>there, and the requirements *need* to move forward to provide 
>>essential TE measurements.
> 
> So.... it seems we agree that this title:
>     A Framework for Internet Traffic Engineering Measurement
> is not good and should be something aka
>     Requirements for essential TE measurements, parameters and controls
> and then of course the main body of the document should focus on
> that and be clear as to waht is a real requirement and why.

well your question make sense in terms of "ease of read and
further use" and i think the reason why "content has been
spread" is also due to what kind of requirement (functional
vs protocol) where drafted wrt to the wg expectations - does
this just not translate the complexity of the subject ? -

>>Regarding your comment:
>>'if we were not yet doing any of it... then I wonder if this 
>>would be helpful at all.'
>>There are many important requirements/recommendations in the 
>>I-D.  As one example, the ability to collect traffic data to 
>>generate a traffic matrix (e.g., 'node-pair data', see Table 
>>in Section 10.1) is woefully lacking.  To get a flavor of the 
>>problem/need, see these papers on the topic (links to papers 
>>at http://www.research.att.com/~jrex/papers.html#tmeas):
>>A. Feldmann, A. Greenberg, C. Lund, N. Reingold, J. Rexford, 
>>G. True, "Deriving traffic demands for operational IP 
>>networks: Methodology and experience," IEEE/ACM Transactions 
>>on Networking, June 2001, pp. 265-279. (An earlier version 
>>appeared in Proc. ACM SIGCOMM, August/September 2000.)
> 
> I'd like to see in the document something aka:
> 
>    REQUIREMENT: ability to collect traffic data to generate trafix matrices
>    DESCRIPTION: describe the details as to what traffic data is needed
>    JUSTIFICATION: describe what the problem is that needs to be solved
>    PRIORITY: x
> 
> Don't need to dwell too much on that... but have a concise and crisp
> writeup. Maybe RFC3216 can serve as a good example.

again, this is probably the issue but i'd like to mention that
the priority and justification may depend on a per user basis

also i took a look at this RFC and compare for instance the abstract

"This document describes the objectives for a new data definition
  language, suitable for the modeling of network management constructs,
  that can be directly mapped into SNMP and COPS-PR protocol
  operations."

well let's try and see if this is achievable here..

"For interoperable compatibility, uniform definitions across vendors
  and operators must be ensured, e.g., in the distinction between
   offered load and achieved throughput

=> so covers terminology

"To aid network dimensioning, mechanisms to collect node-pair-based 
traffic data should be developed to facilitate the derivation of 
per-service-class traffic matrix statistics.

=> associated requirements to acheive node-pair-based traffic data
    and expectation in terms of derivation mechanisms in providing
    stat's

"For service assurance, there is a need for the use of higher-order 
statistics. To preserve representative traffic detail at manageable 
sample volumes, there is a need for packet-sampled measurements.

=> requirements in terms packet-sampling measurements

"To manage large volume of measured data, use of bulk transfer and 
filtering/aggregation mechanisms may be appropriate."

if a re-spin is needed this might be a way to proceed.

>>This work shows the difficulty in deriving a traffic matrix 
>>with today's measurements.  A traffic matrix is basic to any 
>>network engineering or planning task.
>>
>>Other critical traffic/performance measurement requirements 
>>identified in the I-D are also lacking and need to go forward.
>>
>>A few more comments below.
>>
>>Jerry
>> 
>>
>>>- a lot of text... but not very focused and to the point 
>>
>>(or at least I have trouble seeing the main points)
>>
>>>- not a "framework", rather an exploration of TE measurement 
>>>  related topics (more like  a summary-introduction)
>>
>>As above, the I-D serves a critical need.  The text can be 
>>focused on the requirements/recommendations, as suggested, 
>>and the descriptive stuff moved to an Annex.
>>
> 
> One could wonder how much of the descriptive stuff is really
> helpful or usefull. But if it is in an ANEX, then maybe that is
> OK. I would say however, that if we have the requirements
> crisply formulated, with description, justification and priority,
> then one would hope that a lot of additional text is not needed
> (not even in an anex). Think about the audience. It would be
> protocol developers and/or vendors who have to understand the
> requirement and be able to make modifications to their protocol
> and/or products to meet the requirement.

bert, here that's a critical point, i have mentioned it here
above as well => where the expected outcomes in terms of functions/
protocol aspects or both ?

now annex might be useful if using the proposed scheme as
per RFC 3216, expansion on the "why" (as you have mentioned
here above) might difficult to infer, for instance - let's
first see what it gives before expanding on whether it belongs
to an annex or should be dropped from the i-d - i am afraid
that if we use one short paragraph or sentence for the why
people will show up and ask for more content afterwards -

>>>- I am not an operator, but I think if I were one, then
>>>  - if we were already doing TE measurement stuff (most 
>>>    likely) then reading it seems a waste of time
>>>  - if we were not yet doing any of it... then I wonder if 
>>>    this would be helpful at all.
>>
>>Operators have to get by with what is available, what else 
>>can we do?  This does not mean operators are already doing 
>>'TE measurement stuff' in an adequate way, and that nothing 
>>further is required.  E.g., see comments above on derivation 
>>of a traffic matrix.

jerry, as a suggestion this might be a way to introduce the
topic, "why operators think that current TEM when available
is not performed adequately and what's expected to achieve
what you need"

> I would hope operators can also understand and support the 
> requirements. If not, then I really doubt that they are valid
> requirements. And they must understand them, so that together
> the operators can say to protocol developing WGs and to vendors
> that these are the set of requirements to be met.
>  
>>>- W.r.t. the TEM WG work item, it says:
>>>     The tewg interacts with the common control and measurement plane
>>>     working group to abstract and define those parameters, measurements,
>>>     and controls that traffic engineering needs in order to engineer
>>>     the network. 
>>>  So I would expect a CRISP set of "requirements for additional measurements,
>>>  configurable/negotiable parameters/controls" ... but not the extensive
>>>  exploration and text that I now see. Why do people (or the WG) think
>>>  that this document meets the WG deliverable for TEM ??
>>
>>The requirements are there, and are critically needed.  They 
>>need to be brought out in a clear and crisp way, as suggested above.
>>
> 
> Yea.. you keep repeating that.

bert, i think the content is there ... imho we speak
about the form it took rather than the content here
(it might always be improved but this is the case for
any standard track rfc) in all the comments you have
listed i do not see any major "content" issue

section 4.4 of RFC 3346 shows that this aspect must
be covered by the wg

last, i don't want to expand too much on the below, i
think it becomes a bit touchy

thanks,
- dimitri.

>>>- W.r.t. review:
>>>  - 4 people from ATT support it. Waisum is one of them and is main editor.
>>>    Others (Nick Duffield, Bob Cole) have some of their material listed in
>>>    the doc.
>>
>>So AT&T is stuffing the ballot box?
> 
> That was not what I am saying. My point was more: it is clear that those
> people who have contributed support the document. Would be strange if they
> did not, would it not? But I can see now that maybe I should have made
> my statement a bit different.
 >
>>I'm mentioned in acknowledgements, others in references, are we
>>disqualified to comment?  A certain set of people (*individuals*)
>>who are  the ones most interested/knowledgeable are the ones also
>>most likely to comment.
>> 
>>>  - 3 EDU users commented, 2 said they found it a good doc
>>>    3rd one asked a few questions
>>>  - Raymond Zhang is positive. He is from info.net ???
>>>    is that an operator?
>>
>>yes.
> 
> I thought so but was not sure. Maybe Raymond can answer himself, no?
> Raymond, can you fill me in what sort of network you operate?
> Feel free to do so privately if you prefer that.
> 
>>>  - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
>>>    What role/function does he play/have? Operator, code/tool-developer?
>>
>>co-author.
>>
> 
> Ah... ok, so obvious that he would support it. Should have been in
> my first list of people above. 
> You did not answer (but better if Richard does himself) if he is
> and operator or what role plays in his daily life. The reason I ask
> this is because I want to udnerstand their background and the eyes
> and context that they probably have used to review.
> 
>>>  - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
>>>    he/she added any comment. Do we know him/her?
>>>    What role/function does he/she play/have? Operator, code/tool-developer?
>>
>>Level-3 employee?
>>
> 
> Can you be more specific? Is he/she in the accounting dept? I guess not.
> But again, I want to understand the context within which the review was done.
> 
>>>  - Dimitri Papadimitrou (Alcatel) asked a question/suggested some text.
>>>    I did not see if he likes the doc or not
>>
>>did not object
>>
>>>  - Blain Christian (uunet, so maybe a real operator?) 
>>>    withdrew as co-editor
>>>    That does not sound good (in my view)
>>>- So where are the real operators that support this?
>>
>>So *individuals* from AT&T, Infonet, France Telecom, and 
>>Level-3 (?) supported this, IETF does not have 
>>companies/operators positions.  Also, are you saying that the 
>>above operators are not 'real' operators versus other 
>>operators who you think are real operators?
> 
> Sorry for the bad wording. When I use company names, I try to
> see how many differnt viewpoints from people active in different 
> types of networks have looked at it. From their operational experience.
> I do not consider them as speaking for their company, but indeed as
> individuals. I'd like to see comments/review/support from all 
> types of operators, that is carriers, telecom operators, cors ISPs,
> Access ISPs, small ISPs, Enterpise Networks... etc.
 >
>>>My thought is that I can do two things:
>>>
>>>- send back to WG and say that this is "not good enough" and 
>>>  that I do not 
>>>  feel comfortable to present it to IESG for approval.
>>>  It does NOT meet (in my eyes) the WG deliverable for TEM.
>>>- send it to IESG with my recommendation to NOT approve for 
>>>  same reasons.
>>>
>>>So let me try the first option first and ask the WG what they 
>>>have to say to my review.
>>
>>I find it rather disappointing that you waited this long to 
>>come down on this I-D so hard.  If you had this level of 
>>concern, I think you should have tipped your hand long ago, 
>>but perhaps this is first time you have read the draft.
> 
> That is a valid complaint. We are aware that a lot of the AD/IESG level
> review takes place too late in the process. Not easy to fix, we (ADs)
> all have trouble to keep up with what we have on IESG agenda, let alone
> to dive into many WG docuemnts early. We try to improve... but in this
> case I missed it.
> 
> Now I do understand that the WG chairs have been pushing back on this
> in the beginning quite a bit too. I believe that the doc has improved 
> quite a bit since the earlier versions... but when I review it in
> the context of the WG deliverable, then I am clearly still very
> dissappointed. If you say that all the "requirements" are hidden in
> that doc, then pls try to make them clear. It seems that needs major
> rework.
>  
>>We have been admonished many times to read the draft and comment 
>>on this list, and many folks have abided by your wish.  
> 
> I guess it depends on what you count as "many". When I was a kid,
> we joked about people counting:  1,2,3,many. Mmm.. maybe that statement
> is not appropriate. 
> 
>>If we discard this I-D, the TEWG charter item also will go 
>>unfulfilled.  That's bad. I think the I-D serves an important 
>>need, and can address your comments, as above.  
 >
> But I'd rather have us confess that we were unable to deliver on a
> WG item than us delivering something that is not in good shape
> (or bad quality, which I think is the case).
> 
> Hope this explains my posting a bit better.
> Bert

-- 
Papadimitriou Dimitri
E-mail : dimitri.papadimitriou@alcatel.be
Private: http://www.rc.bel.alcatel.be/~papadimd/index.html
E-mail : dpapadimitriou@psg.com
Public : http://psg.com/~dpapadimitriou/
Address: Fr. Wellesplein 1, B-2018 Antwerpen, Belgium
Phone  : +32 3 240-8491




From owner-te-wg@ops.ietf.org  Mon Apr 28 09:54: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 JAA00888
	for <tewg-archive@lists.ietf.org>; Mon, 28 Apr 2003 09:54:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19A91c-000GYc-00
	for te-wg-data@psg.com; Mon, 28 Apr 2003 13:50:32 +0000
Received: from mail1.telekom.de ([62.225.183.235])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19A91U-000GYK-00
	for te-wg@ops.ietf.org; Mon, 28 Apr 2003 13:50:24 +0000
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Mon, 28 Apr 2003 15:50:17 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <JZJH6CFA>; Mon, 28 Apr 2003 15:50:17 +0200
Message-Id: <9F8582E37B2EE5498E76392AEDDCD3FE03DBB410@G8PQD.blf01.telekom.de>
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: bwijnen@lucent.com
Cc: te-wg@ops.ietf.org
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Mon, 28 Apr 2003 15:50:10 +0200
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=-4.9 required=5.0
	tests=BAYES_10,MSG_ID_ADDED_BY_MTA_3
	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 JAA00888

Bert,

| > 'I would expect a CRISP set of "requirements for additional 
| > measurements, configurable/negotiable parameters/controls" 
| > ... but not the extensive exploration and text that I now see'.

I understood the document to be a Framework Document. Crisp 
requirements may be part of a requirements doc or the like. 

The quality of the document is good as a Framework Document.
I'd agree that an architecture or requirements doc 
getting more precise might be useful.  
Different network types and design philosophies result 
in different measurement requirements. I'm not sure whether an 
acceptable "General TE measurement requirements" doc is feasible.

| I do not consider them as speaking for their company, but indeed as
| individuals. I'd like to see comments/review/support from all 
| types of operators, that is carriers, telecom operators, cors ISPs,
| Access ISPs, small ISPs, Enterpise Networks... etc.

I wasn't aware that there's something like an IESG qualification 
profile if you want to vote on last call. I'd suggest that these 
profiles are published with the last call, so that people whose opinion 
isn't asked may save the time they've wasted on reading the document.

Regards, Rüdiger 



From owner-te-wg@ops.ietf.org  Mon Apr 28 11:46:58 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05182
	for <tewg-archive@lists.ietf.org>; Mon, 28 Apr 2003 11:46:57 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19AAr8-000N56-00
	for te-wg-data@psg.com; Mon, 28 Apr 2003 15:47:50 +0000
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 19AAr5-000N4s-00
	for te-wg@ops.ietf.org; Mon, 28 Apr 2003 15:47:47 +0000
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3SFljM01347
	for <te-wg@ops.ietf.org>; Mon, 28 Apr 2003 11:47:45 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R195MBB>; Mon, 28 Apr 2003 17:47:44 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155017C0CC5@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>, bwijnen@lucent.com
Cc: te-wg@ops.ietf.org
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Mon, 28 Apr 2003 17:47:41 +0200
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.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 LAA05182

Inline

> -----Original Message-----
> From: Geib, Ruediger [mailto:Ruediger.Geib@t-systems.com]
> Sent: maandag 28 april 2003 15:50
> To: bwijnen@lucent.com
> Cc: te-wg@ops.ietf.org
> Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
> 
> 
> Bert,
> 
> | > 'I would expect a CRISP set of "requirements for additional 
> | > measurements, configurable/negotiable parameters/controls" 
> | > ... but not the extensive exploration and text that I now see'.
> 
> I understood the document to be a Framework Document. Crisp 
> requirements may be part of a requirements doc or the like. 
> 
In my view, a "framework" or "architecture" document is totally 
different from what the current ID describes. 

> The quality of the document is good as a Framework Document.

But the WG charter does not ask for a "framework doc" or at least not
the way I understand it.

> I'd agree that an architecture or requirements doc 
> getting more precise might be useful.  
> Different network types and design philosophies result 
> in different measurement requirements. I'm not sure whether an 
> acceptable "General TE measurement requirements" doc is feasible.
> 
Well, Jeryr claims all the requirements are in the doc. Just too bad
that it is very difficult to find them. That is why I asked for such
a crsip list of requirements.

> | I do not consider them as speaking for their company, but indeed as
> | individuals. I'd like to see comments/review/support from all 
> | types of operators, that is carriers, telecom operators, cors ISPs,
> | Access ISPs, small ISPs, Enterpise Networks... etc.
> 
> I wasn't aware that there's something like an IESG qualification 
> profile if you want to vote on last call. I'd suggest that these 
> profiles are published with the last call, so that people whose opinion 
> isn't asked may save the time they've wasted on reading the document.
> 
The IESG does NOT have a "qualification profile". 
And EVERYONE's input and review is usefull and is welcome.
What we DO want is that if we write something for OPERATIONAL networks
that we DO get the input from the various types of OPERATORS that we
know about.

Why does everybody look at my comments as an attack on their personal input?
It is rather an attack (if you can speak of that) to those type of OPERATORS
that have NOT yet given review input (positive or negative). I am (in my
responsibility as AD) trying to get sufficient and wide enough review of
the document before I feel comfortable passing it to the IESG.

Hope this explains, Bert

> Regards, Rüdiger 
> 



From owner-te-wg@ops.ietf.org  Tue Apr 29 03:08: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 DAA09008
	for <tewg-archive@lists.ietf.org>; Tue, 29 Apr 2003 03:08:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19APDf-000G09-00
	for te-wg-data@psg.com; Tue, 29 Apr 2003 07:08:03 +0000
Received: from mail1.telekom.de ([62.225.183.235])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19APDc-000Fzh-00
	for te-wg@ops.ietf.org; Tue, 29 Apr 2003 07:08:01 +0000
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Tue, 29 Apr 2003 09:07:54 +0200
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <JZJH6ZHD>; Tue, 29 Apr 2003 09:07:53 +0200
Message-Id: <9F8582E37B2EE5498E76392AEDDCD3FE03DBB412@G8PQD.blf01.telekom.de>
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: bwijnen@lucent.com
Cc: te-wg@ops.ietf.org
Subject: RE: AD review of: draft-ietf-tewg-measure-05.txt 
Date: Tue, 29 Apr 2003 09:07:51 +0200
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=-5.7 required=5.0
	tests=BAYES_01,MSG_ID_ADDED_BY_MTA_3
	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 DAA09008

Inline

| > The quality of the document is good as a Framework Document.
| 
| But the WG charter does not ask for a "framework doc" or at least not
| the way I understand it.

It says "Document additional measurements needed for TE (TEM)". That's 
the most precise reference I've found regarding measurements. 
 
| > I'd agree that an architecture or requirements doc 
| > getting more precise might be useful.  
| > Different network types and design philosophies result 
| > in different measurement requirements. I'm not sure whether an 
| > acceptable "General TE measurement requirements" doc is feasible.
| > 
| Well, Jeryr claims all the requirements are in the doc. Just too bad
| that it is very difficult to find them. That is why I asked for such
| a crsip list of requirements.

Jerry is absolutely right. The document lists everything which could 
be of use to support TE measurements. That's a kind of toolbox. 
It contains everything which is required and some hints how you'd
apply it. It doesn't contain a building plan. The first steps to this 
direction were an architecture document and some specific 
requirements.

| The IESG does NOT have a "qualification profile". 
| And EVERYONE's input and review is usefull and is welcome.
| What we DO want is that if we write something for OPERATIONAL networks
| that we DO get the input from the various types of OPERATORS that we
| know about.

Like Infonet.

Regards, Rüdiger



From owner-te-wg@ops.ietf.org  Tue Apr 29 16:01:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08641
	for <tewg-archive@lists.ietf.org>; Tue, 29 Apr 2003 16:01:30 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 19AbF7-000AML-00
	for te-wg-data@psg.com; Tue, 29 Apr 2003 19:58:21 +0000
Received: from listserv2.radford.edu ([137.45.126.15])
	by psg.com with esmtp (Exim 3.36 #1)
	id 19AbEv-000AKC-00
	for te-wg@ops.ietf.org; Tue, 29 Apr 2003 19:58:09 +0000
Received: from virus-mail.radford.edu (virus-mail.radford.edu [137.45.126.10])
	by listserv2.radford.edu (8.11.6/8.11.6) with SMTP id h3TJw4X23917
	for <te-wg@ops.ietf.org>; Tue, 29 Apr 2003 15:58:04 -0400 (EDT)
Received: FROM mail-in.radford.edu BY virus-mail.radford.edu ; Tue Apr 29 15:59:18 2003 -0700
Received: from oakcitysolutions.com (dhcp-192-86.radford.edu [137.45.192.86] (may be forged))
	by mail-in.radford.edu (Switch-3.0.4/Switch-3.0.0) with ESMTP id h3TJw1q4018442;
	Tue, 29 Apr 2003 15:58:02 -0400
Message-ID: <3EAED94B.2010704@oakcitysolutions.com>
Date: Tue, 29 Apr 2003 15:58:03 -0400
From: "Dr. Richard W. Tibbs" <tewg@oakcitysolutions.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
CC: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: Re: AD review of: draft-ietf-tewg-measure-05.txt
References: <7D5D48D2CAA3D84C813F5B154F43B155016A3AFF@nl0006exch001u.nl.lucent.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=-32.7 required=5.0
	tests=BAYES_20,EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT,QUOTE_TWICE_1,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bert, sorry for the delay responding -- just getting back to tewg list now.
Some information for you inline below to some of your questions.

(I am a co-author, Dr. Richard Tibbs, whom you mention below.  FYI, I am 
a faculty at Radford University , Radford VA and my consulting company 
is oakcitysolutions.com)

Wijnen, Bert (Bert) wrote:

>My summary:
>
>- a lot of text... but not very focused and to the point (or at least
>  I have trouble seeing the main points)
>- not a "framework", rather an exploration of TE measurement related topics
>  (more like  a summary-introduction)
>- I am not an operator, but I think if I were one, then
>  - if we were already doing TE measurement stuff (most likely) then 
>    reading it seems a waste of time
>  - if we were not yet doing any of it... then I wonder if this would
>    be helpfull at all.
>- W.r.t. the TEM WG work item, it says:
>     The tewg interacts with the common control and measurement plane
>     working group to abstract and define those parameters, measurements,
>     and controls that traffic engineering needs in order to engineer
>     the network. 
>  So I would expect a CRISP set of "requirements for additional measurements,
>  configurable/negotiable parameters/controls" ... but not the extensive
>  exploration and text that I now see. Why do people (or the WG) think
>  that this document meets the WG deliverable for TEM ??
>- W.r.t. review:
>  - 4 people from ATT support it. Waisum is one of them and is main editor.
>    Others (Nick Duffield, Bob Cole) have some of their material listed in
>    the doc.
>  - 3 EDU users commented, 2 said they found it a good doc
>    3rd one asked a few questions
>  - Raymond Zhang is positive. He is from info.net ??? is that an operator?
>  - Richard Tibbs gave a thumbs up, he is from oakcitusolutions.com.
>    What role/function does he play/have? Operator, code/tool-developer?
>  - One hotmail user (Spyrokontigiogis) gave a thumbs up. Not that
>    he/she added any comment. Do we know him/her?
>
Dr. Kontogiorgis was formerly with the Business Optimization Group, 
Level 3 Communications out in CO.  He is currently with Colo. School of 
Mines.  So, his comments represent operator viewpoint, I believe.

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





