From owner-te-wg@ops.ietf.org  Mon Jan  6 03:30: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 DAA29157
	for <tewg-archive@lists.ietf.org>; Mon, 6 Jan 2003 03:30:38 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18VSYH-0009kj-00
	for te-wg-data@psg.com; Mon, 06 Jan 2003 00:24:05 -0800
Received: from mail1.telekom.de ([62.225.183.235])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18VSYF-0009jy-00
	for te-wg@ops.ietf.org; Mon, 06 Jan 2003 00:24:03 -0800
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Mon, 6 Jan 2003 09:23:30 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <CF4XSTJL>; Mon, 6 Jan 2003 09:23:30 +0100
Message-Id: <9F8582E37B2EE5498E76392AEDDCD3FE23B296@G8PQD.blf01.telekom.de>
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: jboyle@pdnets.com
Cc: te-wg@ops.ietf.org
Subject: AW: A proposal for moving ahead on BC models
Date: Mon, 6 Jan 2003 09:23:26 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=1.6 required=5.0
	tests=EXCHANGE_SERVER,MSG_ID_ADDED_BY_MTA_3,SPAM_PHRASE_00_01
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Jim,

as feedback on the issue was asked for, my 2 cents:

 
| The real question is whether folks think there is a *need* (for 
| consistent/interoperable implementations) to require one (or two)
| BC model(s)?  Or not.

During the Atlanta meeting the point was raised that depending on 
the mode of operation of a link, each BC model may have 
its merits. So it seems sound to have both of them available and 
they may both be applied within a single network.

Consistency and interoperability also strongly depend on a simple 
and well defined specification, default settings and reduction 
of options. If both BC models are specified that way, both 
should be implemented.

Regards, Rudiger





From owner-te-wg@ops.ietf.org  Wed Jan  8 11:29: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 LAA23855
	for <tewg-archive@lists.ietf.org>; Wed, 8 Jan 2003 11:29:08 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18WJ00-000Ml3-00
	for te-wg-data@psg.com; Wed, 08 Jan 2003 08:24:12 -0800
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18WIzs-000Mim-00
	for te-wg@ops.ietf.org; Wed, 08 Jan 2003 08:24:05 -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 LAA10038
	for <te-wg@ops.ietf.org>; Wed, 8 Jan 2003 11:23:31 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id LAA22398
	for <te-wg@ops.ietf.org>; Wed, 8 Jan 2003 11:23:32 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <ZVACLKHW>; Wed, 8 Jan 2003 11:23:31 -0500
Message-ID: <313680C9A886D511A06000204840E1CF8F52F5@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: te-wg@ops.ietf.org
Subject: RE: A proposal for moving ahead on BC models
Date: Wed, 8 Jan 2003 11:23:30 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi!
> -----Original Message-----
> From: Geib, Ruediger [mailto:Ruediger.Geib@t-systems.com]
> Sent: Monday, January 06, 2003 3:23 AM
> To: jboyle@pdnets.com
> Cc: te-wg@ops.ietf.org
> Subject: AW: A proposal for moving ahead on BC models
> 
> 
> Jim,
> 
> as feedback on the issue was asked for, my 2 cents:
> 
>  
> | The real question is whether folks think there is a *need* (for 
> | consistent/interoperable implementations) to require one (or two)
> | BC model(s)?  Or not.
> 
> During the Atlanta meeting the point was raised that depending on 
> the mode of operation of a link, each BC model may have 
> its merits. So it seems sound to have both of them available and 
> they may both be applied within a single network.
> 
	In this case, may be Francois's original proposal to separate
	the specification of _a_ default model, from the DSTE-PROTO 
      is the way to go.

	Since the DSTE solution draft as specified, is independent
	of the underlying BC Models and does not cause any 
	interoperability problems, may be the DSTE_REQ draft should
	be updated to relax the requirement of a "default" BC Model.
		
	Administrator then can decide to use one or more than one
	BC Models in the network based on his requirement.

	Thanks,
	sanjay

> Consistency and interoperability also strongly depend on a simple 
> and well defined specification, default settings and reduction 
> of options. If both BC models are specified that way, both 
> should be implemented.
> 
> Regards, Rudiger
> 
> 
> 



From owner-te-wg@ops.ietf.org  Fri Jan 10 12:45:42 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05937
	for <tewg-archive@lists.ietf.org>; Fri, 10 Jan 2003 12:45:41 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18X38J-0001C8-00
	for te-wg-data@psg.com; Fri, 10 Jan 2003 09:39:51 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18X38G-0001Bw-00
	for te-wg@ops.ietf.org; Fri, 10 Jan 2003 09:39:49 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05489;
	Fri, 10 Jan 2003 12:36:30 -0500 (EST)
Message-Id: <200301101736.MAA05489@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-measure-04.txt
Date: Fri, 10 Jan 2003 12:36:29 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
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		: A Framework for Internet Traffic Engineering 
                          Measurement
	Author(s)	: W. Lai, R. Tibbs, S. Van den Berghe
	Filename	: draft-ietf-tewg-measure-04.txt
	Pages		: 26
	Date		: 2003-1-10
	
In this document, a measurement framework for supporting the traffic 
engineering of IP-based networks is presented.  Uses of traffic 
measurement in service provider environments are described, and 
issues related to time scale and read-out period are discussed.  
Different measurement types are classified, with each being 
specified as a meaningful combination of a measurement entity and a 
measurement basis. 
For interoperable compatibility, uniform definitions across vendors 
and operators must be ensured, e.g., in the distinction between 
offered load and achieved throughput.  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.  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.  To manage large volume of measured data, use 
of bulk transfer and filtering/aggregation mechanisms may be 
appropriate.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-04.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-measure-04.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Sun Jan 12 01:50: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 BAA26104
	for <tewg-archive@lists.ietf.org>; Sun, 12 Jan 2003 01:50:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18XbsI-000Kdn-00
	for te-wg-data@psg.com; Sat, 11 Jan 2003 22:45:38 -0800
Received: from cad.zju.edu.cn ([210.32.131.2] helo=mail.cad.zju.edu.cn)
	by psg.com with smtp (Exim 3.36 #2)
	id 18XbsE-000Kcq-00
	for te-wg@ops.ietf.org; Sat, 11 Jan 2003 22:45:34 -0800
Received: (qmail 1216 invoked from network); 12 Jan 2003 06:51:29 -0000
Received: from unknown (HELO cad.zju.edu.cn) (210.32.131.97)
  by 210.32.131.2 with SMTP; 12 Jan 2003 06:51:29 -0000
Message-ID: <3E210F29.82EF6DE0@cad.zju.edu.cn>
Date: Sun, 12 Jan 2003 14:46:01 +0800
From: Jing Shen <jshen@cad.zju.edu.cn>
Reply-To: jshen@cad.zju.edu.cn
Organization: State Key Lab of CAD&CG
X-Mailer: Mozilla 4.79 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: te-wg@ops.ietf.org
Subject: question on draft-ietf-tewg-measure-04.txt
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=0.0 required=5.0
	tests=NOSPAM_INC,SIGNATURE_LONG_SPARSE,SPAM_PHRASE_00_01,
	      USER_AGENT_MOZILLA_XM,X_ACCEPT_LANG
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,


in sec10.1, there is a "Delay Variation" measured at Interface, 
to my understanding IPDV is a type of measurement at e2e level or link
level. Why does the draft propose that? and how to measure it?

I'm not clear what's the relationship between "throughput" and "goodput"
used in the draft. If they all refer to the amount  of traffic
successfully
delivered,  do we need to measure network traffic sent by source nodes?


And, what about the measurement precision? I means should the accuracy
of measurement be discussed? 



regards

-- 
Jing Shen

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

**********************************************************************
* The SunShine of life is made up of very little beams which is      *
*  bright all the time                                               *
**********************************************************************



From owner-te-wg@ops.ietf.org  Mon Jan 13 15:02:03 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21876
	for <tewg-archive@lists.ietf.org>; Mon, 13 Jan 2003 15:02:00 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18YAhm-000Bsp-00
	for te-wg-data@psg.com; Mon, 13 Jan 2003 11:57:06 -0800
Received: from listserv2.radford.edu ([137.45.126.15])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18YAhi-000Bsb-00
	for te-wg@ops.ietf.org; Mon, 13 Jan 2003 11:57:02 -0800
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 h0DJv0X24743
	for <te-wg@ops.ietf.org>; Mon, 13 Jan 2003 14:57:00 -0500 (EST)
Received: FROM mail-in.radford.edu BY virus-mail.radford.edu ; Mon Jan 13 14:57:55 2003 -0800
Received: from oakcitysolutions.com (dhcp-192-86.radford.edu [137.45.192.86] (may be forged))
	by mail-in.radford.edu (Switch-2.2.0/Switch-2.2.0) with ESMTP id h0DJupm27843;
	Mon, 13 Jan 2003 14:56:57 -0500
Message-ID: <3E2319FA.7000003@oakcitysolutions.com>
Date: Mon, 13 Jan 2003 14:56:42 -0500
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: jshen@cad.zju.edu.cn
CC: te-wg@ops.ietf.org
Subject: Re: question on draft-ietf-tewg-measure-04.txt
References: <3E210F29.82EF6DE0@cad.zju.edu.cn>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, hits=-2.6 required=5.0
	tests=EMAIL_ATTRIBUTION,MAY_BE_FORGED,REFERENCES,
	      SPAM_PHRASE_02_03,USER_AGENT,USER_AGENT_MOZILLA_UA,
	      X_ACCEPT_LANG
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings, and thanks for your question. Apologies if you get this twice.

A one-point delay is sometimes desirable in several situations.
First, ITU Y.1540 states in appendix II:
<quote>
II.4 Guidance on Applying the Different Parameters
Guidance that serves the practical side of measurement is as follows:
- When synchronized clocks are not possible (or temporarily unavailable)
in measurement devices,
1. 1-point Packet Delay Variation (PDV) is a possible substitute for
1-way delay range/histogram, applicable for measurements on packet
streams with periodic sending times (once the reference arrival time is
appropriately set).
2. IPPM Inter-packet delay variation is applicable to all traffic flow
types.
</quote>
Second,
when flows must be regulated to ensure QoS, as for example in RSVP, a
similar reference arrival time exists based on the negotiated traffic
envelope parameters, e.g.,
1/peak_rate or 1/mean_rate, etc.
Our draft is intended as a framework document, and we wish to be quite
general in our definitions, so that subsequent drafts may focus on such
areas for TE measurement.


Hope this helps.

Yours truly,
Dr. Richard W. Tibbs.
Radford University
Dept. of Information Technology



Jing Shen wrote:

>Hi,
>
>
>in sec10.1, there is a "Delay Variation" measured at Interface, 
>to my understanding IPDV is a type of measurement at e2e level or link
>level. Why does the draft propose that? and how to measure it?
>
>I'm not clear what's the relationship between "throughput" and "goodput"
>used in the draft. If they all refer to the amount  of traffic
>successfully
>delivered,  do we need to measure network traffic sent by source nodes?
>
>
>And, what about the measurement precision? I means should the accuracy
>of measurement be discussed? 
>
>
>
>regards
>





From owner-te-wg@ops.ietf.org  Fri Jan 17 20:09: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 UAA08466
	for <tewg-archive@lists.ietf.org>; Fri, 17 Jan 2003 20:09:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18ZhRu-000K9c-00
	for te-wg-data@psg.com; Fri, 17 Jan 2003 17:07:02 -0800
Received: from 197.69-4-133-nokia-dsl.dhcp.surewest.net ([69.4.133.197] helo=adelphia.gblx.net)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18ZhRq-000K9O-00
	for te-wg@ops.ietf.org; Fri, 17 Jan 2003 17:06:58 -0800
Received: (from dcooper@localhost)
	by adelphia.gblx.net (8.11.6/8.11.6) id h0I11kl05442;
	Fri, 17 Jan 2003 17:01:46 -0800 (PST)
	(envelope-from cooper@GBLX.net)
X-Authentication-Warning: adelphia.gblx.net: dcooper set sender to cooper@GBLX.net using -f
Date: Fri, 17 Jan 2003 17:01:46 -0800
From: Dave Cooper <dcooper@GBLX.net>
To: flefauch@cisco.com
Cc: te-wg@ops.ietf.org
Subject: Re: A proposal for moving ahead on BC models
Message-ID: <20030117170146.A5415@gblx.net>
References: <20030118002818.GA84886@nitrous.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <20030118002818.GA84886@nitrous.net>; from cooper@nitrous.net on Fri, Jan 17, 2003 at 05:28:18PM -0700
X-Spam-Status: No, hits=-2.9 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_03_05,
	      USER_AGENT,USER_AGENT_MUTT,X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

I think we should drop the mandate on a default
BC model and just move on.

-dave

On Fri, Jan 17, 2003 at 05:28:18PM -0700, Dave Cooper wrote:
> > Hi all,
> > 
> > >> However, we have 
> > >> multiple BC
> > >>    models on the table here, and the requirements document says there
> > >>    must be a default BC model for implementation.  So the question
> > >>    becomes: Is "one" of these the default?  Or both? Or maybe should
> > >>    neither really be required, they proceed non-standard until
> > >>    operational experience shows what people really use (and thus
> > >>    should be required for implementation). 
> > 
> > It's occurred to me that there is an interesting analogy between the
> > situation we are in with respect to BC Models, and the situation the
> > Diff-Serv WG was a little while back with respect to PHBs:
> > 	- the architecture + basic on-the-wire "protocol" extensions
> > were defined (e.g. DSCP for Diff-Serv; IGP/RSVP for DSTE)
> > 	- PHB is local to a box, but to achieve something end-to-end you
> > generally want to run the same PHB on all boxes (as externally visible).
> > Similarly, BC Model is a local behaviour but to achieve something
> > end-to-end you want the same BC Model on all boxes.
> > 	- it was clear that more than one PHB would be needed for
> > different applications. A number of specific PHBs (EF, AFxy,..) were
> > recognised as clearly useful for respective applications. It was
> > recognised that additional PHBs may be required in the future. It was
> > unclear which exact set of PHBs were going to be eventually deployed in
> > the long run, it was unclear that all networks would require the same
> > set of PHBs anyway, and more operational experience was required. All of
> > this applies to the BC models.
> > 
> > The Diff-Serv WG approach has been to:
> > 	- document each PHB (or group of PHBs) which were clearly
> > recognised as useful in a separate standards track RFC (eg EF, AFxy  ).
> > Tis basically says : "if you're going to support this PHB, here is what
> > you MUST do".
> > 	- allow additional PHBs to be specified in the future as deemed
> > necessary from experience
> > 	- NOT mandate which PHB to support (*) and let user/vendor
> > determine the right set of PHBs to deploy/support as experience grows.
> > 
> > So my proposal would be to handle BC models in the same way, i.e. :
> > 	- document Russian Dolls model in a standards track RFC. This
> > would basically say, "if you're going to support RDM, here is what you
> > MUST do".
> > 	- document MAM in a standards track RFC. This would basically
> > say, "if you're going to support MAM, here is what you MUST do".
> > 	- in the future, allow additional models (eg something
> > incorporating some MAR concepts) to be defined as required from
> > operational experience
> > 	- do NOT mandate in the "diff-te-proto" draft which BC model is
> > to be used
> > 	- update "diff-te-reqts" to reflect this (get rid of concept of
> > "Default BC model"). This draft is with IESG so it should still be
> > possible to update it.
> > 
> > I think this approach would allow us to achieve standardised
> > interoperable DSTE deployment in short timeframes, yet at the same time
> > would prepare us well for adjusting in the future as we gather more
> > operational expertise.
> > 
> > Thoughts/comments on this approach?
> > 
> > Francois
> > 
> > 
> > 
> > 
> > (*) the Diff-Serv spec actually mandates support of the
> > Default/Best-Effort PHB (and some Class Selector PHBs). But note that
> > this is not analogous to supporting a Default BC model. It is in effect
> > the minimum required to maintain operation as BEFORE Diff-Serv service.
> > So in the DS-TE context, it is analogous to the minimum required to
> > operate without DS-TE (ie to support regular TE) and that would be
> > support of the existing TE trivial BC Model with a single CT.
> > 
> 
> ----- End forwarded message -----



From owner-te-wg@ops.ietf.org  Sat Jan 18 22:26:42 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05445
	for <tewg-archive@lists.ietf.org>; Sat, 18 Jan 2003 22:26:41 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18a61s-000O7r-00
	for te-wg-data@psg.com; Sat, 18 Jan 2003 19:21:48 -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 #2)
	id 18a61p-000O4t-00
	for te-wg@ops.ietf.org; Sat, 18 Jan 2003 19:21:45 -0800
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.5/8.12.5) with ESMTP id h0J3LDBr018530
	for <te-wg@ops.ietf.org>; Sat, 18 Jan 2003 22:21:14 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.5/8.12.5/Submit) with ESMTP id h0J3LBd6018526
	for <te-wg@ops.ietf.org>; Sat, 18 Jan 2003 22:21:13 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Sat, 18 Jan 2003 22:21:11 -0500 (EST)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: Re: A proposal for moving ahead on BC models (conclusion?)
In-Reply-To: <20030117170146.A5415@gblx.net>
Message-ID: <Pine.LNX.4.44.0301182209080.13232-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-1.1 required=5.0
	tests=IN_REP_TO,SPAM_PHRASE_01_02,USER_AGENT_PINE,X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


For the record, I think it best to specify a default model.

However, assuming Sanjay's second vote masks his first, and including my 
vote above, that would leave us with 6 folks who think we should pull the 
requirement for a default, specified model, and 2 who think we should keep 
it.  That gives us a voter turn-out on our list of less than 1% ;-(

So we'll update the requirements document (currently with IESG) to reflect 
no need for a required default BC model.

Jim






From owner-te-wg@ops.ietf.org  Sat Jan 18 22:37:49 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05903
	for <tewg-archive@lists.ietf.org>; Sat, 18 Jan 2003 22:37:48 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18a6Jn-000P4W-00
	for te-wg-data@psg.com; Sat, 18 Jan 2003 19:40:19 -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 #2)
	id 18a6Jk-000P3X-00
	for te-wg@ops.ietf.org; Sat, 18 Jan 2003 19:40:16 -0800
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.5/8.12.5) with ESMTP id h0J3djBr018580
	for <te-wg@ops.ietf.org>; Sat, 18 Jan 2003 22:39:45 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.5/8.12.5/Submit) with ESMTP id h0J3dj2x018576
	for <te-wg@ops.ietf.org>; Sat, 18 Jan 2003 22:39:45 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Sat, 18 Jan 2003 22:39:45 -0500 (EST)
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-measure-04.txt
In-Reply-To: <200301101736.MAA05489@ietf.org>
Message-ID: <Pine.LNX.4.44.0301182233570.13232-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-1.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SEARCH_ENGINE_PROMO,SPAM_PHRASE_01_02,USER_AGENT_PINE,
	      X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


This draft has definitely honed itself to its purpose from its earliest 
versions.  However it never appears to get wide comment or show of hands 
of folks that have reviewed it. 

So... Please do so.

I'll give us 3 weeks for folks to comment along these lines.

1) is this draft on-target for the TE measurements milestone we have in 
   our charter?  If you think it is off-target I would be interested 
   in hearing how we should deal with this portion of our charter.

2) minor / editorial comments to list and/or author

3) substantial comments to list

Last call will end February 7.

thanks!

Jim Boyle












On Fri, 10 Jan 2003 Internet-Drafts@ietf.org wrote:

> 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		: A Framework for Internet Traffic Engineering 
>                           Measurement
> 	Author(s)	: W. Lai, R. Tibbs, S. Van den Berghe
> 	Filename	: draft-ietf-tewg-measure-04.txt
> 	Pages		: 26
> 	Date		: 2003-1-10
> 	
> In this document, a measurement framework for supporting the traffic 
> engineering of IP-based networks is presented.  Uses of traffic 
> measurement in service provider environments are described, and 
> issues related to time scale and read-out period are discussed.  
> Different measurement types are classified, with each being 
> specified as a meaningful combination of a measurement entity and a 
> measurement basis. 
> For interoperable compatibility, uniform definitions across vendors 
> and operators must be ensured, e.g., in the distinction between 
> offered load and achieved throughput.  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.  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.  To manage large volume of measured data, use 
> of bulk transfer and filtering/aggregation mechanisms may be 
> appropriate.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-04.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-tewg-measure-04.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-tewg-measure-04.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 




From owner-te-wg@ops.ietf.org  Sun Jan 19 07:39: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 HAA19793
	for <tewg-archive@lists.ietf.org>; Sun, 19 Jan 2003 07:39:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18aEji-000Lha-00
	for te-wg-data@psg.com; Sun, 19 Jan 2003 04:39:38 -0800
Received: from alc250.alcatel.be ([195.207.101.250] helo=mail.alcatel.be)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18aEje-000Lh5-00
	for te-wg@ops.ietf.org; Sun, 19 Jan 2003 04:39:34 -0800
Received: from bemail05.net.alcatel.be (relay3 [127.0.0.1])
	by mail.alcatel.be (8.11.0/8.11.4) with ESMTP id h0JCdT426083
	for <te-wg@ops.ietf.org>; Sun, 19 Jan 2003 13:39:29 +0100
Received: from alcatel.be ([138.203.137.3])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003011913392809:1298 ;
          Sun, 19 Jan 2003 13:39:28 +0100 
Message-ID: <3E2A9C5B.43BF205D@alcatel.be>
Date: Sun, 19 Jan 2003 13:38:51 +0100
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: Jim Boyle <jboyle@pdnets.com>
CC: te-wg@ops.ietf.org
Subject: Re: WG Last Call :  draft-ietf-tewg-measure-04.txt
References: <Pine.LNX.4.44.0301182233570.13232-100000@fido.nc.rr.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 01/19/2003 13:39:28,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 01/19/2003 13:39:29,
	Serialize complete at 01/19/2003 13:39:29
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=1.8 required=5.0
	tests=NOSPAM_INC,NO_REAL_NAME,QUOTED_EMAIL_TEXT,REFERENCES,
	      SEARCH_ENGINE_PROMO,SIGNATURE_SHORT_DENSE,
	      SPAM_PHRASE_01_02,USER_AGENT_MOZILLA_XM,X_ACCEPT_LANG
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jim, all,

in section 5.3, would it be possible to detail the
real scope behind the following paragraph:

"Providing a feedback mechanism in the reverse flow messaging of 
 RSVP-TE or CR-LDP signaling in MPLS to report on actual topology 
 state information such as link bandwidth availability."

more precisely, detail the relationship between "signalling
in mpls" and the report to "actual topology state information" 
since there are imho several ways to interpret the above 
sentence

thanks,
- dimitri.

Jim Boyle wrote:
> 
> This draft has definitely honed itself to its purpose from its earliest
> versions.  However it never appears to get wide comment or show of hands
> of folks that have reviewed it.
> 
> So... Please do so.
> 
> I'll give us 3 weeks for folks to comment along these lines.
> 
> 1) is this draft on-target for the TE measurements milestone we have in
>    our charter?  If you think it is off-target I would be interested
>    in hearing how we should deal with this portion of our charter.
> 
> 2) minor / editorial comments to list and/or author
> 
> 3) substantial comments to list
> 
> Last call will end February 7.
> 
> thanks!
> 
> Jim Boyle
> 
> On Fri, 10 Jan 2003 Internet-Drafts@ietf.org wrote:
> 
> > 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           : A Framework for Internet Traffic Engineering
> >                           Measurement
> >       Author(s)       : W. Lai, R. Tibbs, S. Van den Berghe
> >       Filename        : draft-ietf-tewg-measure-04.txt
> >       Pages           : 26
> >       Date            : 2003-1-10
> >
> > In this document, a measurement framework for supporting the traffic
> > engineering of IP-based networks is presented.  Uses of traffic
> > measurement in service provider environments are described, and
> > issues related to time scale and read-out period are discussed.
> > Different measurement types are classified, with each being
> > specified as a meaningful combination of a measurement entity and a
> > measurement basis.
> > For interoperable compatibility, uniform definitions across vendors
> > and operators must be ensured, e.g., in the distinction between
> > offered load and achieved throughput.  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.  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.  To manage large volume of measured data, use
> > of bulk transfer and filtering/aggregation mechanisms may be
> > appropriate.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-04.txt
> >
> > To remove yourself from the IETF Announcement list, send a message to
> > ietf-announce-request with the word unsubscribe in the body of the message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with the username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> >       "get draft-ietf-tewg-measure-04.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> >       mailserv@ietf.org.
> > In the body type:
> >       "FILE /internet-drafts/draft-ietf-tewg-measure-04.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> >       MIME-encoded form by using the "mpack" utility.  To use this
> >       feature, insert the command "ENCODING mime" before the "FILE"
> >       command.  To decode the response(s), you will need "munpack" or
> >       a MIME-compliant mail reader.  Different MIME-compliant mail readers
> >       exhibit different behavior, especially when dealing with
> >       "multipart" MIME messages (i.e. documents which have been split
> >       up into multiple messages), so check your local documentation on
> >       how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >

-- 
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  : Work: +32 3 2408491 - Home: +32 2 3434361



From owner-te-wg@ops.ietf.org  Sun Jan 19 13:27: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 NAA23527
	for <tewg-archive@lists.ietf.org>; Sun, 19 Jan 2003 13:27:03 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18aKA0-000C7Z-00
	for te-wg-data@psg.com; Sun, 19 Jan 2003 10:27:08 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18aK9e-000C3v-00
	for te-wg@ops.ietf.org; Sun, 19 Jan 2003 10:26:46 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0JIQEj05861
	for <te-wg@ops.ietf.org>; Sun, 19 Jan 2003 13:26:14 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ2650H7>; Sun, 19 Jan 2003 19:26:13 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155AA9C41@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Te-Wg (E-mail)" <te-wg@ops.ietf.org>
Subject: Review of draft-tewg-diff-te-reqts-06.txt
Date: Sun, 19 Jan 2003 19:25:31 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

First, I need to appologize, this review got done
quite a while ago, and I now found that I did not
forward it to the WG.
The good news: I have it on my radar again.

Kathie (DIFFSERV WG co-chair) has reviewed (at my
request) and has come up with these comments.
I am forwarding this with her permission.

Can the authors and WG pls check and suggest answers 
to the issues raised.

I am digging up more... which will follow soon.

Thanks,
Bert 

-----Original Message-----
From: Kathleen Nichols [mailto:nichols@packetdesign.com]
Sent: vrijdag 15 november 2002 2:08
To: Wijnen, Bert (Bert)
Cc: Scott Bradner (E-mail)
Subject: Re: Diffserv-aware Traffic Engineering




Wijnen, Bert (Bert) wrote:
> Could you (either yourslef or one of the DIFFSERV WG members)
> take a look at 
> 
>   draft-tewg-diff-te-reqts-06.txt
> 
> from a DIFFSERV point of view.
> 
> The TEWG has asked me to consider it for publication as 
> Informational RFC
> 
> Thanks,
> Bert 

I took a fairly quick view. I suppose I could say "mostly harmless"
but I do have a question of what the purpose of this document
is. That is, what light is it shedding on the Internet? It claims
in the abstract that it presents Service Provider requirements
for support of Diff-Serv aware MPLS Traffic Engineering. But
the "requirements" seem quite general. (I'm looking in
sections 4 and 5). On the other hand, Section 5 says that
some solutions may require that all current TE protocols syntax
be extended. This seems like off-handedly proposing a lot of
possible standards action. The paragraph at the bottom of page
9 is saying that a good deal of the model it is discussing has
not a clear needs case. So, at the high level, I'm wondering
why this document is being written now, what problem is it
solving. It does not present "example applications scenarios identified
by Service Providers" in my opinion. Its examples are very
general and there is no case made about how anyone is planning
a deployment. But, as relevance does not appear to be a
criterion for publication of Informational RFCs, I'll
move on to other concerns.

The third paragraph of section 1.1 states that "where optimization
of transmission resources is sought, Diff-Serv mechanisms [DIFF-
MPLS] need to be complemented by existing MPLS Traffic Engineering
mechanisms..." this in concert with the previous paragraph
seems to state that network-wide optimization of resources
*requires* MPLS. This is not a statement of fact, but of
opinion.

Near the end of section 3.2 there is a definition of "flows
of the same class" in terms of "Forwarding Equivalence Class"
which perhaps should be defined.

There are a few tortured sentences, particularly the first
sentence of the second paragraph of section 1.3 and last
sentence of first paragraph of section 3.3.

3.1, scenario 1, the example of 10,000 uncompressed calls
seems a bit specious. What grounding in reality does
that have? This is supposed to be giving requirements so
it seems the examples should not be merely illustrative.

3.1, second sentence. So I know how to determine the
"certain percentage" of VoIP traffic and it has to
do with a number of factors including the type of
scheduler in the forwarding path. But this sounds like
a lot of handwaving on the part of the authors.

Section 4.2: there seems to be some confusion of defining
a traffic class by the PHB it uses. This has been a problem
for a while and why the Diffserv WG did more work on defining
PDBs. A PHB is a mechanism and a bit low level to use to
define a traffic class.

My main concern is that the document does not meet its
stated objective of "to provide guidance for the definition,
selection and specification of a technical solution
addressing these requirements." The examples and discussion
are very "uncooked" and the document says so in itself.
I don't see that the introduction of more terminology is
needed at this point, but real documentation of real
problems and real solutions might be more useful.

	Kathie




From owner-te-wg@ops.ietf.org  Sun Jan 19 13:30:37 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23587
	for <tewg-archive@lists.ietf.org>; Sun, 19 Jan 2003 13:30:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18aKG3-000CTp-00
	for te-wg-data@psg.com; Sun, 19 Jan 2003 10:33:23 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18aKFi-000CSr-00
	for te-wg@ops.ietf.org; Sun, 19 Jan 2003 10:33:02 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0JIWTj06761
	for <te-wg@ops.ietf.org>; Sun, 19 Jan 2003 13:32:29 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ26502Q>; Sun, 19 Jan 2003 19:32:28 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155AA9C45@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Sun, 19 Jan 2003 19:31:34 +0100
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=0.7 required=5.0
	tests=EXCHANGE_SERVER,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Mix of nits, admin comments, and serious comments

- general... I find it difficult to extract the list of requirements
  from your document. I think the last 2 lines of sect 4.3 for example
  is one of the requirements. It also seems to me that the 2nd and 6th
  paragraphs on page 12 are requirments. The last sentence of the one
  but last para on page 13 also seems a requirement... and so on.
  Would it make sense to eitehr MARK them very clearly in the text,
  or to sumamry them in a separate section?
- sect 1.1 says:
   In other networks, where optimization of transmission resources is
   sought, Diff-Serv mechanisms [DIFF-MPLS] need to be complemented by
   existing MPLS Traffic Engineering mechanisms [TE-REQ] [ISIS-TE]
   [OSPF-TE] [RSVP-TE] [CR-LDP] which operate on an aggregate basis
  I wonder about the "complemented by existing ... mechanisms"
  Several of the references documents are still work-in-progress.
  Would a s/existing/other/ be more appropriate?
- sect 3.2 talks (two places) about "the order in which tunnels are
  routed". What does that (ordering of tunnels) mean ?
- what are thelast 2 paragraphs on page 7 trying to say?
  sounds like blabla and handwaving to me, no?
- sect 4. 1st sentence
  s/implementations/techniques or protocols/ ??
  In other words... we are not mandating any "implementation" are we.
  We are specifying functionality for (potential) DS-TE protocols are
  we not?
- sect 4.2 
  Is the first sentence not a generic TE requirement and not specific
  to DS-TE? Maybe I get confused since you did not define the term
  "Traffic Trunc"
- Is most of the text in sect 4.2 on page 9 not just another 
  scenario that belongs in sect 3?
- does the "criteria to be considered" on page 11 not belong in
  section 5?
- On page 11 you reference [BC-MODEL] but it is not listed in the
  references section I think.
- Page 13. Maybe I just do not udnerstand... but it seems to me 
  that this text:

    The network administrator would then, in particular, NOT be able
    to :
    - transport a CT0 Traffic Trunk over an LSP with setup priority=1
      and holding priority=1
    - transport a CT1 Traffic Trunk over an LSP with setup priority=0
      and holding priority=0
   
  Conflicts with the immediately following text:

    DS-TE must allow two LSPs transporting Traffic Trunks from different
    Class-Types to use the same preemption priority. In other words, the
    DS-TE solution must allow TE-classes using different CTs to use the
    same preemption priority. This effectively allows the network
    administrator to ensure that no preemption happens across Class-
    Types, if so desired.

    As an example, the DS-TE solution must allow the network
    administrator to define three Class-Types (CT0, CT1 and CT2) each
    comprising one TE-Class which uses preemption 0. In that case, no
    preemption will ever occur.

  Or do I indeed not understand?
- May I assume that all TE-WG members understand the notations used in 
  section 4.5 ?? Cause I would have to go and study in detail if I
  want to get it.
- sect 4.6
  I guess the reference to sect 2.2 should be to 3.2 ??
- The last 2 sentences of 1st para of sect 4.6 mean what?
  Is it an "optional requirement" or is it "ou of scope" ??
  if out of scope, then why is sect 4.6 present?
- sect 5.1 refers to sections 2 and 3, which I think should respectively
  be 3 and 4
- The security considerations section seems very weak, see underlined:

   The solution developed to address the requirements defined in this
   document must address security aspects. DS-TE is not expected to add
   specific security requirements beyond those of Diff-Serv and
   existing TE.  Networks which employ Diff-Serv techniques might offer
                                                           ------
   some protection between classes for denial of service attacks.
   ------
   Though depending on how the technology is employed, it is possible
   for some (lower scheduled) traffic to be more susceptible to traffic
   anomalies (which include denial of service attacks) occurring within
   other (higher scheduled) classes.

  See also comments by others from ops-directorate reviewers
  

spelling nits:
- first linbe page 6
  s/be able/be possible/ ??
- first 2 paragaraphs on page 7 have conflicting current and past
  tense usage of verbs
- setc 3.3 5th line
  s/ to and egress port/to an egress port/
- bottom of page 8
  s/section 3.4 below/section 4.3 below/
- page 11, inconsistent use of "criteria" and "criterion"

Thanks,
Bert 



From owner-te-wg@ops.ietf.org  Mon Jan 20 06:15:11 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16123
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 06:15:10 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18aZp9-00038V-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 03:10:39 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18aZp5-000384-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 03:10:35 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0KB8RS6024560;
	Mon, 20 Jan 2003 12:08:31 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Mon, 20 Jan 2003 12:09:55 +0100
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: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Mon, 20 Jan 2003 11:09:26 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E773@xbe-lon-303.cisco.com>
Thread-Topic: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Thread-Index: AcK/6XOVxzUignAYRZumFpaaUrR/iwAgGBuQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 20 Jan 2003 11:09:55.0115 (UTC) FILETIME=[762C4FB0:01C2C074]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
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 GAA16123

Bert,

Thanks for the thorough review. 
Thanks also to ops-directorate reviewers.

Comments/proposed-resolution embedded below:


>> -----Original Message-----
>> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
>> Sent: 19 January 2003 19:32
>> To: Tewg (E-mail)
>> Subject: comments on draft-ietf-tewg-diff-te-reqts-06.txt
>> 
>> 
>> Mix of nits, admin comments, and serious comments
>> 
>> - general... I find it difficult to extract the list of requirements
>>   from your document. I think the last 2 lines of sect 4.3 
>> for example
>>   is one of the requirements. It also seems to me that the 
>> 2nd and 6th
>>   paragraphs on page 12 are requirments. The last sentence of the one
>>   but last para on page 13 also seems a requirement... and so on.
>>   Would it make sense to eitehr MARK them very clearly in the text,
>>   or to sumamry them in a separate section?

Well, all the detailed requirements are grouped under section 4 and they
are all "marked" with a "must" (or "should/may"). Seems like a
reasonably clear way to present them.
There is some (non-requirement) text preceding the actual requirements
to provide background/definition for the formulation of the requirement.
I think it is best to keep all that together so one can understand the
requirements.

The reason we did not capitalise the "must/should/may" is that this
document is going for Informational track so we were not sure
MUST/SHOULD/MAY were appropriate. Sounds like they are, so we will
follow your suggestion and capitalize them.

>> - sect 1.1 says:
>>    In other networks, where optimization of transmission resources is
>>    sought, Diff-Serv mechanisms [DIFF-MPLS] need to be 
>> complemented by
>>    existing MPLS Traffic Engineering mechanisms [TE-REQ] [ISIS-TE]
>>    [OSPF-TE] [RSVP-TE] [CR-LDP] which operate on an aggregate basis
>>   I wonder about the "complemented by existing ... mechanisms"
>>   Several of the references documents are still work-in-progress.
>>   Would a s/existing/other/ be more appropriate?

Noted.

>> - sect 3.2 talks (two places) about "the order in which tunnels are
>>   routed". What does that (ordering of tunnels) mean ?

Before being available, TE tunnels need to be established. This
establishment includes computing route for the tunnel and signaling
tunnel establishment (and thus reserving bandwidth). The order in which
these tunnels are established/routed can greatly affect which tunnels
can grab bandwidth and which cannot, and thus greatly affects the state
of the final system. 

>> - what are thelast 2 paragraphs on page 7 trying to say?
>>   sounds like blabla and handwaving to me, no?

They are trying to say something specific :
Some SPs would like to simultaneously:
	- offer "Very High QoS Guaranteed Traffic" and "Normal Traffic"
	- they want to do admission control of "Very High QoS Guaranteed
Traffic" to ensure it fits in the queue dedicated to that service
	- they want to do regular TE of Normal traffic

This leads to the need for doing TE CAC on more than one Bandwidth pools
(which is what DS-TE is all about).

>> - sect 4. 1st sentence
>>   s/implementations/techniques or protocols/ ??

Agreed. Since we already mention several times the "DS-TE solution" , we
could s/implementations/solution/

>>   In other words... we are not mandating any "implementation" are we.
>>   We are specifying functionality for (potential) DS-TE protocols are
>>   we not?
>> - sect 4.2 
>>   Is the first sentence not a generic TE requirement and not specific
>>   to DS-TE? Maybe I get confused since you did not define the term
>>   "Traffic Trunc"

Section "1.2 Definitions" contains a definition for "Traffic Trunks".

>> - Is most of the text in sect 4.2 on page 9 not just another 
>>   scenario that belongs in sect 3?

We tried to keep things simple in the scenarios (eg only talked about
"classes of service"). The objectives of the scenarios is to give a
simple-to-grab understanding of what SPs want to do.
In section 4.2 we are trying to describe the relationship between CTs
and classes/PHBs. This requires more complex terminology and mapping
examples. Also, in section 4.2 we are not describing what application
the is trying to achieve, just how CTs may be "mapped".

>> - does the "criteria to be considered" on page 11 not belong in
>>   section 5?

Agreed.
When updating the text of 4.2 about Default model, we will move the BC
Model criteria to section 5. 

>> - On page 11 you reference [BC-MODEL] but it is not listed in the
>>   references section I think.

Noted.

>> - Page 13. Maybe I just do not udnerstand... but it seems to me 
>>   that this text:
>> 
>>     The network administrator would then, in particular, NOT be able
>>     to :
>>     - transport a CT0 Traffic Trunk over an LSP with setup priority=1
>>       and holding priority=1
>>     - transport a CT1 Traffic Trunk over an LSP with setup priority=0
>>       and holding priority=0
>>    
>>   Conflicts with the immediately following text:
>> 

In the previous paragraph, it is important to note the word "then".
"Then" was intended to mean "in the case of the example  CTs definition
which is given above". Given this "CT definition", the text is correct.
The paragraph below would require a differnet "CT definition".

>>     DS-TE must allow two LSPs transporting Traffic Trunks 
>> from different
>>     Class-Types to use the same preemption priority. In 
>> other words, the
>>     DS-TE solution must allow TE-classes using different CTs 
>> to use the
>>     same preemption priority. This effectively allows the network
>>     administrator to ensure that no preemption happens across Class-
>>     Types, if so desired.
>> 
>>     As an example, the DS-TE solution must allow the network
>>     administrator to define three Class-Types (CT0, CT1 and CT2) each
>>     comprising one TE-Class which uses preemption 0. In that case, no
>>     preemption will ever occur.
>> 
>>   Or do I indeed not understand?
>> - May I assume that all TE-WG members understand the 
>> notations used in 
>>   section 4.5 ?? Cause I would have to go and study in detail if I
>>   want to get it.

A definition for these terms is actually provided in section "1.2
Definitions".

>> - sect 4.6
>>   I guess the reference to sect 2.2 should be to 3.2 ??

Right.

>> - The last 2 sentences of 1st para of sect 4.6 mean what?
>>   Is it an "optional requirement" or is it "ou of scope" ??
>>   if out of scope, then why is sect 4.6 present?

Yeah, a little confusing right now ^)
I propose to just specify it as optional and get rid of the "out of
scope" statement. 

>> - sect 5.1 refers to sections 2 and 3, which I think should 
>> respectively
>>   be 3 and 4

Noted.

>> - The security considerations section seems very weak, see 
>> underlined:
>> 
>>    The solution developed to address the requirements defined in this
>>    document must address security aspects. DS-TE is not 
>> expected to add
>>    specific security requirements beyond those of Diff-Serv and
>>    existing TE.  Networks which employ Diff-Serv techniques 
>> might offer
>>                                                            ------
>>    some protection between classes for denial of service attacks.
>>    ------
>>    Though depending on how the technology is employed, it is possible
>>    for some (lower scheduled) traffic to be more susceptible 
>> to traffic
>>    anomalies (which include denial of service attacks) 
>> occurring within
>>    other (higher scheduled) classes.
>> 

My proposal would be to just keep the two first sentences (ie DSTE
solution must address security. DS-TE not expected to add new security
issues beyond those of Diff-Serv and TE) and get rid of the rest since
we do not have to start discussing how security may be achieved in the
Reqt document itself.


>>   See also comments by others from ops-directorate reviewers
>>   
>> 
>> spelling nits:
>> - first linbe page 6
>>   s/be able/be possible/ ??

I think "be able" is correct.
Before, we already say " VoIP traffic should be able ..." and here we
mean that the VoIP traffic should be able to use the shortest path.

>> - first 2 paragaraphs on page 7 have conflicting current and past
>>   tense usage of verbs

Noted

>> - setc 3.3 5th line
>>   s/ to and egress port/to an egress port/

Noted

>> - bottom of page 8
>>   s/section 3.4 below/section 4.3 below/

Actually it should be section 4.4.

>> - page 11, inconsistent use of "criteria" and "criterion"
>> 

Noted.


>> Thanks,
>> Bert 
>> 
>> 



From owner-te-wg@ops.ietf.org  Mon Jan 20 09:06: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 JAA20526
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 09:06:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18acZk-000BGa-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 06:06:56 -0800
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18acZh-000BED-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 06:06:53 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0KDxbhL016897
	for <te-wg@ops.ietf.org>; Mon, 20 Jan 2003 08:06:23 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E015DD5DE; Mon, 20 Jan 2003 09:06:06 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: A proposal for moving ahead on BC models (conclusion?)
Date: Mon, 20 Jan 2003 09:05:59 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A17674@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: A proposal for moving ahead on BC models (conclusion?)
Thread-Index: AcK/bL3wGIaipINjQQCvaPjw12HHvABHrTQw
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SPAM_PHRASE_01_02
	version=2.43
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 JAA20526

1. my count is 6 to 3.
2. a majority, yes, but a thin margin and small sample on which to base this decision...

Jerry

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Saturday, January 18, 2003 10:21 PM
To: te-wg@ops.ietf.org
Subject: Re: A proposal for moving ahead on BC models (conclusion?)

For the record, I think it best to specify a default model.

However, assuming Sanjay's second vote masks his first, and including my 
vote above, that would leave us with 6 folks who think we should pull the 
requirement for a default, specified model, and 2 who think we should keep 
it.  That gives us a voter turn-out on our list of less than 1% ;-(

So we'll update the requirements document (currently with IESG) to reflect 
no need for a required default BC model.

Jim




From owner-te-wg@ops.ietf.org  Mon Jan 20 09:43: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 JAA21068
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 09:43:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18adAy-000D6i-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 06:45:24 -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 #2)
	id 18adAr-000D2d-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 06:45:17 -0800
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.5/8.12.5) with ESMTP id h0KEifBr030686;
	Mon, 20 Jan 2003 09:44:41 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.5/8.12.5/Submit) with ESMTP id h0KEieeX030682;
	Mon, 20 Jan 2003 09:44:41 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 20 Jan 2003 09:44:40 -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: Weak turnout : was-> A proposal for moving ahead on BC models
In-Reply-To: <28F05913385EAC43AF019413F674A01704A17674@OCCLUST04EVS1.ugd.att.com>
Message-ID: <Pine.LNX.4.44.0301200939530.29292-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-3.5 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_01_02,USER_AGENT_PINE,X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Hopefully for other calls we can get better turnout than 9 members out of 
1100.


On Mon, 20 Jan 2003, Ash, Gerald R (Jerry), ALABS wrote:

> 1. my count is 6 to 3.
> 2. a majority, yes, but a thin margin and small sample on which to base this decision...
> 
> Jerry
> 
> -----Original Message-----
> From: Jim Boyle [mailto:jboyle@pdnets.com]
> Sent: Saturday, January 18, 2003 10:21 PM
> To: te-wg@ops.ietf.org
> Subject: Re: A proposal for moving ahead on BC models (conclusion?)
> 
> For the record, I think it best to specify a default model.
> 
> However, assuming Sanjay's second vote masks his first, and including my 
> vote above, that would leave us with 6 folks who think we should pull the 
> requirement for a default, specified model, and 2 who think we should keep 
> it.  That gives us a voter turn-out on our list of less than 1% ;-(
> 
> So we'll update the requirements document (currently with IESG) to reflect 
> no need for a required default BC model.
> 
> Jim
> 
> 




From owner-te-wg@ops.ietf.org  Mon Jan 20 10:20:16 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21695
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 10:20:16 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18adju-000F0D-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 07:21:30 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18adjq-000Ey6-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 07:21:27 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0KFJ8gd002006;
	Mon, 20 Jan 2003 16:19:09 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Mon, 20 Jan 2003 16:20:31 +0100
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: Review of draft-tewg-diff-te-reqts-06.txt
Date: Mon, 20 Jan 2003 15:20:30 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E775@xbe-lon-303.cisco.com>
Thread-Topic: Review of draft-tewg-diff-te-reqts-06.txt
Thread-Index: AcK/6Psw+AZ+ILINTpWRkwea8MUAJwAjjHyQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Te-Wg (E-mail)" <te-wg@ops.ietf.org>, <telkamp@gblx.net>
Cc: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        <dallan@nortelnetworks.com>
X-OriginalArrivalTime: 20 Jan 2003 15:20:31.0430 (UTC) FILETIME=[7883E660:01C2C097]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
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 KAA21695

Bert and all,

>> 
>> Can the authors and WG pls check and suggest answers 
>> to the issues raised.
>> 

Below are some thoughts and suggested resolution.
Cheers

Francois

=========================================================

>> It does not present "example applications scenarios 
>> identified
>> by Service Providers" in my opinion. 

Hmm. The text of section 3 was edited from text provided by the Service
Provider co-authors to describe what they are considering deploying and
what application they are trying to support. So, to me, to all the draft
co-authors, and I think to many people -if not the whole TEWG who passed
last call on this document- this does provide "example applications
scenarios identified by Service Providers".

>> there is no case made about how anyone is planning
>> a deployment. 

A number of Service Providers co-authors contributed to this document
because they are considering/planning to deploy this.
The whole document is precisely a case that some SPs are
considering/planning deployment for this.

>>But, as relevance does not appear to be a
>> criterion for publication of Informational RFCs, I'll
>> move on to other concerns.
>>

Well, this is felt relevant by a number of Service Providers, which was
the essential consideration for progressing that document.

In any case, I agree that we don't need to discuss it any further and
can just "move on to other concerns".
 
>> The third paragraph of section 1.1 states that "where optimization
>> of transmission resources is sought, Diff-Serv mechanisms [DIFF-
>> MPLS] need to be complemented by existing MPLS Traffic Engineering
>> mechanisms..." this in concert with the previous paragraph
>> seems to state that network-wide optimization of resources
>> *requires* MPLS. This is not a statement of fact, but of
>> opinion.

Agreed.
This will be edited along the lines of replacing "need to/necessary" by
"may". 

For example, 
"... Diff-Serv mechanisms [DIFF-MPLS] need to be complemented by
existing MPLS Traffic Engineering mechanisms...".
Could be replaced by:
"... Diff-Serv mechanisms [DIFF-MPLS] may be complemented by existing
MPLS Traffic Engineering mechanisms...".

>> 
>> Near the end of section 3.2 there is a definition of "flows
>> of the same class" in terms of "Forwarding Equivalence Class"
>> which perhaps should be defined.

Reference to the MPLS Architecture RFC will be added in the "Normative
Reference" list. It contains definition of FEC and other fundamental
MPLS concepts which are required for understanding of this document.

>> 
>> There are a few tortured sentences, particularly the first
>> sentence of the second paragraph of section 1.3 

1st sentence of 2nd paragraph of 1.3 is:
"
One option is to not split this set of <FEC/{TA}PSC> so that each 
   Traffic Trunk comprises traffic from all the {TA}/PSC .
"
Is this the sentence in question?
Is this really unaceptably tortured (considering the previous sentence
explains there are several options on how these things can be split)?

>>and last
>> sentence of first paragraph of section 3.3.
>>

Here is what I read:
"
The goal is to ensure all "guaranteed" traffic within a subscribed
traffic contract, will be delivered within stated tolerances."
I guess I must have a tortured mind because I can't quite see the
"torturedness"?

If it can make someone happier, all the enhancement I can suggest would
be:
"The goal is to ensure that all the "guaranteed" traffic under the scope
of a subscribed service level specification, will be delivered within
the tolerances of this service level specification."
Otherwise, I'll need specific suggestions.

>> 3.1, scenario 1, the example of 10,000 uncompressed calls
>> seems a bit specious. What grounding in reality does
>> that have? This is supposed to be giving requirements so
>> it seems the examples should not be merely illustrative.
>>

Some Service Providers are carrying part of their national PSTN traffic
over their packet network today. Voice VPN traffic is also transported
over the core. As migration of those continues, 10000 calls is felt as a
realistic order of magnitude for 1-3 year requirements.

But this text was provided by Thomas from Global Crossing, so Thomas may
want to add his view.
 
>> 3.1, second sentence. So I know how to determine the
>> "certain percentage" of VoIP traffic and it has to
>> do with a number of factors including the type of
>> scheduler in the forwarding path. But this sounds like
>> a lot of handwaving on the part of the authors.
>> 

I am not sure what is the specific concern/suggestion.
Effectively what we're trying to say is:
	- VoIP load can be significant compared to link capacity
	- some SPs feel that controlling the maximum load of VoIP on
all/some links is one of the tools that will help them control the level
of QoS [even if this document does not discuss the actual relationship
between (i) VoIP load, (ii) QoS levels and (iii) other factors including
type of scheduler]

To be able to address this I'd need to know whether:
	- there is a disagreement that some SPs feel that way
	- we are not phrasing the above clearly enough (specific
suggestions will help)

>> Section 4.2: there seems to be some confusion of defining
>> a traffic class by the PHB it uses. This has been a problem
>> for a while and why the Diffserv WG did more work on defining
>> PDBs. A PHB is a mechanism and a bit low level to use to
>> define a traffic class.

The trick is that PHBs have been complemented by the concept of PSC to
introduce the notion of "sharing a scheduling constraint". But PDBs have
not. So to be able to use this notion of "sharing a scheduling
constraint" we somehow have to refer to the PHB/PSC. But to address the
specific concern in this section, we can replace
   "... running 4 Diff-Serv classes of services respectively based on
the EF 
   PHB [EF], the AF1x PSC [AF], the AF2x PSC and the Default (i.e. 
   Best-Effort) PHB [DIFF-FIELD]. "
by:
   "running 4 Diff-Serv classes of services whose {TA}PSCs are
respectively based on the EF 
   PHB [EF], the AF1x PSC [AF], the AF2x PSC and the Default (i.e. 
   Best-Effort) PHB [DIFF-FIELD]. "

Note that section 1.2 already contains a definition for "class of
service" which uses the concept of TA:
   "We also loosely refer to a {TA}PSC as a 
   Diff-Serv class of service, or class-of service."

(BTW, as a suggestion to the Diff-Serv WG, my impression is that this
{TA}PSC concept we're defining here, would actually be very handy in a
broader context as people are very often trying to refer to a "class of
service". Something like:
   "
   A Scheduling Aggregate: the set of TAs corresponding to the set of
PHBs of a 
   given PSC. 
   "
I wonder if this has/is/could been/be considered by the Diff-Serv WG) 

>> 
>> My main concern is that the document does not meet its
>> stated objective of "to provide guidance for the definition,
>> selection and specification of a technical solution
>> addressing these requirements." 

Well it contains the requirements to the level expressed by Service
Providers and it has provided us enough guidance to progress the DS-TE
protocol extensions to readiness for WG Last Call. Seems to fit the
bill.

Cheers

Francois



From owner-te-wg@ops.ietf.org  Mon Jan 20 14:40: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 OAA28709
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 14:40:55 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18ahne-0002I7-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 11:41:38 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18ahna-0002Gr-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 11:41:34 -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 h0KJcYHe007752
	for <te-wg@ops.ietf.org>; Mon, 20 Jan 2003 14:41:02 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E0160CE5B for te-wg@ops.ietf.org; Mon, 20 Jan 2003 14:41:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2C0BB.DDE88258"
Subject: RE: question on draft-ietf-tewg-measure-04.txt
Date: Mon, 20 Jan 2003 14:41:03 -0500
Message-ID: <28F05913385EAC43AF019413F674A017044A3488@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: question on draft-ietf-tewg-measure-04.txt
Thread-Index: AcK7QKIY0raVwtUSTcC/QOplcx2POwBWS8gg
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-0.6 required=5.0
	tests=EMAIL_ATTRIBUTION,MAILTO_LINK,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2C0BB.DDE88258
Content-Type: text/plain;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

Jing,
  Thanks for your comments on our draft.  We'll add appropriate text to
clarify the points you raised.
  As Richard described below, delay variation can be measured by either
1-point or 2-point methods, depending on the intent.  Y.1541 is already
referred to in our draft, but we will make an explicit reference to its
Appendix II in Section 10.1.  (As indicated in the 3rd paragraph in page
4, our intent is to avoid duplication of effort, by referring to other
standards documents as far as possible.)
  As defined in Section 4.2 (and also later in Section 9.1), throughput
and goodput are the same in our draft.  Also, as indicated in Note (5)
in Section 10.1, traffic sent by source nodes are indeed measured, as
you pointed out.
  Our draft's focus is currently mainly on identifying additional
measurements for TE as described by the TEWG charter.  (Non-goals are
described in the second paragraph in page 4.)  While measurement
precision/accuracy are important issues, the authors feel that such
issues should be dealt with in future drafts.  As an example of
precision/accuracy issues, see RFC 2679, section 3.7, "Errors &
Uncertainties".  There, the accuracy issues for one-way delay are
dealt with in great detail.  Each measure potentially has its own
unique precision/accuracy issues, and to deal with them in the
framework draft would make it quite voluminous.
However, I would like to hear if there is a general
interest in this area.
Thanks, Wai Sum

-----Original Message-----
From: Dr. Richard W. Tibbs [  <mailto:tewg@oakcitysolutions.com> =
mailto:tewg@oakcitysolutions.com]
Sent: Monday, January 13, 2003 2:57 PM
To: jshen@cad.zju.edu.cn
Cc: te-wg@ops.ietf.org
Subject: Re: question on draft-ietf-tewg-measure-04.txt


Greetings, and thanks for your question. Apologies if you get this =
twice.

A one-point delay is sometimes desirable in several situations.
First, ITU Y.1540 states in appendix II:
<quote>
II.4 Guidance on Applying the Different Parameters
Guidance that serves the practical side of measurement is as follows:
- When synchronized clocks are not possible (or temporarily unavailable)
in measurement devices,
1. 1-point Packet Delay Variation (PDV) is a possible substitute for
1-way delay range/histogram, applicable for measurements on packet
streams with periodic sending times (once the reference arrival time is
appropriately set).
2. IPPM Inter-packet delay variation is applicable to all traffic flow
types.
</quote>
Second,
when flows must be regulated to ensure QoS, as for example in RSVP, a
similar reference arrival time exists based on the negotiated traffic
envelope parameters, e.g.,
1/peak_rate or 1/mean_rate, etc.
Our draft is intended as a framework document, and we wish to be quite
general in our definitions, so that subsequent drafts may focus on such
areas for TE measurement.


Hope this helps.

Yours truly,
Dr. Richard W. Tibbs.
Radford University
Dept. of Information Technology



Jing Shen wrote:

>Hi,
>
>
>in sec10.1, there is a "Delay Variation" measured at Interface,
>to my understanding IPDV is a type of measurement at e2e level or link
>level. Why does the draft propose that? and how to measure it?
>
>I'm not clear what's the relationship between "throughput" and =
"goodput"
>used in the draft. If they all refer to the amount  of traffic
>successfully
>delivered,  do we need to measure network traffic sent by source nodes?
>
>
>And, what about the measurement precision? I means should the accuracy
>of measurement be discussed?
>
>
>
>regards
>






------_=_NextPart_001_01C2C0BB.DDE88258
Content-Type: text/html;
	charset="GB2312"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dgb2312">
<TITLE></TITLE>

<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003>Jing,</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>&nbsp;=20
Thanks for your comments on our draft.&nbsp; We'll add appropriate text=20
to</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>clarify the=20
points you raised.</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>&nbsp; As=20
Richard described below, delay variation can be measured by=20
either</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>1-point or=20
2-point methods, depending on the intent.&nbsp;&nbsp;Y.1541 is=20
already</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>referred to=20
in our draft,</SPAN></FONT><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003> but we will make an explicit reference to=20
its</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT size=3D2><SPAN=20
class=3D439242913-15012003>Appendix II&nbsp;in Section</SPAN><SPAN=20
class=3D439242913-15012003> 10.1.&nbsp; (As indicated in the 3rd =
paragraph in=20
page</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT size=3D2><SPAN =
class=3D439242913-15012003>4, our=20
intent is to avoid duplication of effort, by referring to=20
other</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3D"Courier New"><FONT size=3D2><SPAN=20
class=3D439242913-15012003>standards documents as far as=20
possible.)</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>&nbsp; As=20
defined in Section 4.2 (and also later in Section 9.1),=20
throughput</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>and goodput=20
are the same in our draft.&nbsp; Also, as indicated in Note=20
(5)</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003>in</SPAN></FONT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
class=3D439242913-15012003> Section 10.1, traffic sent by source nodes =
are indeed=20
measured, as</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003>you</SPAN></FONT><FONT face=3D"Courier New" =
size=3D2><SPAN=20
class=3D439242913-15012003> pointed out.</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>&nbsp; Our=20
draft's focus is currently mainly on identifying =
additional</SPAN></FONT><FONT=20
face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003></SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>measurements=20
for TE as described by the TEWG charter.&nbsp; (Non-goals=20
are</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>described in=20
the second paragraph in page 4.)&nbsp; While =
measurement</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003>precision/accuracy are important issues, the =
authors=20
feel that such</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>issues=20
should be dealt with in future drafts.&nbsp; As an example=20
of</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003>precision/accuracy issues, see RFC 2679, =
section 3.7,=20
"Errors &amp;</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN=20
class=3D439242913-15012003>Uncertainties".&nbsp; There, the accuracy =
issues for=20
one-way delay are</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>dealt with=20
in great detail.&nbsp; Each measure potentially has its =
own</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>unique=20
precision/accuracy issues, and to deal with them in =
the</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>framework=20
draft would make it quite voluminous.<BR>However, I would like to hear =
if there=20
is a general<BR>interest in this area.</SPAN></FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2><SPAN =
class=3D439242913-15012003>Thanks, Wai=20
Sum</SPAN></FONT></DIV>
<P><FONT face=3D"Courier New" size=3D2>-----Original =
Message-----<BR>From: Dr.=20
Richard W. Tibbs [</FONT><A =
href=3D"mailto:tewg@oakcitysolutions.com"><FONT=20
face=3D"Courier New" =
size=3D2>mailto:tewg@oakcitysolutions.com</FONT></A><FONT=20
face=3D"Courier New" size=3D2>]<BR>Sent: Monday, January 13, 2003 2:57 =
PM<BR>To:=20
jshen@cad.zju.edu.cn<BR>Cc: te-wg@ops.ietf.org<BR>Subject: Re: question =
on=20
draft-ietf-tewg-measure-04.txt<BR><BR><BR>Greetings, and thanks for your =

question. Apologies if you get this twice.<BR><BR>A one-point delay is =
sometimes=20
desirable in several situations.<BR>First, ITU Y.1540 states in appendix =

II:<BR>&lt;quote&gt;<BR>II.4 Guidance on Applying the Different=20
Parameters<BR>Guidance that serves the practical side of measurement is =
as=20
follows:<BR>- When synchronized clocks are not possible (or temporarily=20
unavailable)<BR>in measurement devices,<BR>1. 1-point Packet Delay =
Variation=20
(PDV) is a possible substitute for<BR>1-way delay range/histogram, =
applicable=20
for measurements on packet<BR>streams with periodic sending times (once =
the=20
reference arrival time is<BR>appropriately set).<BR>2. IPPM Inter-packet =
delay=20
variation is applicable to all traffic=20
flow<BR>types.<BR>&lt;/quote&gt;<BR>Second,<BR>when flows must be =
regulated to=20
ensure QoS, as for example in RSVP, a<BR>similar reference arrival time =
exists=20
based on the negotiated traffic<BR>envelope parameters, =
e.g.,<BR>1/peak_rate or=20
1/mean_rate, etc.<BR>Our draft is intended as a framework document, and =
we wish=20
to be quite<BR>general in our definitions, so that subsequent drafts may =
focus=20
on such<BR>areas for TE measurement.<BR><BR><BR>Hope this =
helps.<BR><BR>Yours=20
truly,<BR>Dr. Richard W. Tibbs.<BR>Radford University<BR>Dept. of =
Information=20
Technology<BR><BR><BR><BR>Jing Shen=20
wrote:<BR><BR>&gt;Hi,<BR>&gt;<BR>&gt;<BR>&gt;in sec10.1, there is a =
"Delay=20
Variation" measured at Interface,<BR>&gt;to my understanding IPDV is a =
type of=20
measurement at e2e level or link<BR>&gt;level. Why does the draft =
propose that?=20
and how to measure it?<BR>&gt;<BR>&gt;I'm not clear what's the =
relationship=20
between "throughput" and "goodput"<BR>&gt;used in the draft. If they all =
refer=20
to the amount&nbsp; of =
traffic<BR>&gt;successfully<BR>&gt;delivered,&nbsp; do we=20
need to measure network traffic sent by source=20
nodes?<BR>&gt;<BR>&gt;<BR>&gt;And, what about the measurement precision? =
I means=20
should the accuracy<BR>&gt;of measurement be=20
discussed?<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;regards<BR>&gt;<BR><BR><BR><BR>=
</FONT></P></BODY></HTML>

------_=_NextPart_001_01C2C0BB.DDE88258--



From owner-te-wg@ops.ietf.org  Mon Jan 20 16:40: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 QAA01858
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 16:40:56 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18ajfc-0008Iq-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 13:41:28 -0800
Received: from rtp-msg-core-1.cisco.com ([161.44.11.97])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18ajfU-0008Fj-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 13:41:20 -0800
Received: from bucket.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0KLfYqR022201;
	Mon, 20 Jan 2003 16:41:35 -0500 (EST)
Received: from tnadeau-w2k.cisco.com (che-vpn-cluster-1-69.cisco.com [10.86.240.69])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ACL08638;
	Mon, 20 Jan 2003 16:40:47 -0500 (EST)
Message-Id: <5.2.0.9.2.20030120163934.05ae79c8@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 20 Jan 2003 16:40:36 -0500
To: Jim Boyle <jboyle@pdnets.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: Re: WG Last Call :  draft-ietf-tewg-measure-04.txt
Cc: te-wg@ops.ietf.org
In-Reply-To: <Pine.LNX.4.44.0301182233570.13232-100000@fido.nc.rr.com>
References: <200301101736.MAA05489@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=0.5 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk



>This draft has definitely honed itself to its purpose from its earliest
>versions.  However it never appears to get wide comment or show of hands
>of folks that have reviewed it.
>
>So... Please do so.
>
>I'll give us 3 weeks for folks to comment along these lines.
>
>1) is this draft on-target for the TE measurements milestone we have in
>    our charter?  If you think it is off-target I would be interested
>    in hearing how we should deal with this portion of our charter.

         I think it reasonably addresses the requirement.  I
reviewed the document a few months back and made
suggestions for corrections to the list which seem to have
been made in the current version.

         --Tom


>2) minor / editorial comments to list and/or author
>
>3) substantial comments to list
>
>Last call will end February 7.
>
>thanks!
>
>Jim Boyle
>
>
>
>
>
>
>
>
>
>
>
>
>On Fri, 10 Jan 2003 Internet-Drafts@ietf.org wrote:
>
> > 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           : A Framework for Internet Traffic Engineering
> >                           Measurement
> >       Author(s)       : W. Lai, R. Tibbs, S. Van den Berghe
> >       Filename        : draft-ietf-tewg-measure-04.txt
> >       Pages           : 26
> >       Date            : 2003-1-10
> >
> > In this document, a measurement framework for supporting the traffic
> > engineering of IP-based networks is presented.  Uses of traffic
> > measurement in service provider environments are described, and
> > issues related to time scale and read-out period are discussed.
> > Different measurement types are classified, with each being
> > specified as a meaningful combination of a measurement entity and a
> > measurement basis.
> > For interoperable compatibility, uniform definitions across vendors
> > and operators must be ensured, e.g., in the distinction between
> > offered load and achieved throughput.  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.  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.  To manage large volume of measured data, use
> > of bulk transfer and filtering/aggregation mechanisms may be
> > appropriate.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-04.txt
> >
> > To remove yourself from the IETF Announcement list, send a message to
> > ietf-announce-request with the word unsubscribe in the body of the message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with the 
> username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> >       "get draft-ietf-tewg-measure-04.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> >       mailserv@ietf.org.
> > In the body type:
> >       "FILE /internet-drafts/draft-ietf-tewg-measure-04.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> >       MIME-encoded form by using the "mpack" utility.  To use this
> >       feature, insert the command "ENCODING mime" before the "FILE"
> >       command.  To decode the response(s), you will need "munpack" or
> >       a MIME-compliant mail reader.  Different MIME-compliant mail readers
> >       exhibit different behavior, especially when dealing with
> >       "multipart" MIME messages (i.e. documents which have been split
> >       up into multiple messages), so check your local documentation on
> >       how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >

"The difficult, we do immediately.  The impossible takes a little longer." 
-- Air Force Motto

http://www.mkp.com/books_catalog/catalog.asp?ISBN=1-55860-751-X







From owner-te-wg@ops.ietf.org  Mon Jan 20 17:19:42 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02745
	for <tewg-archive@lists.ietf.org>; Mon, 20 Jan 2003 17:19:42 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18akIr-000AKS-00
	for te-wg-data@psg.com; Mon, 20 Jan 2003 14:22:01 -0800
Received: from oe157.pav0.hotmail.com ([64.4.33.150] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18akIp-000AI0-00
	for te-wg@ops.ietf.org; Mon, 20 Jan 2003 14:21:59 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 20 Jan 2003 14:21:28 -0800
X-Originating-IP: [63.15.53.163]
Reply-To: "Victoria Fineberg" <fineberg@illinoisalumni.org>
From: "Victoria Fineberg" <fineberg@illinoisalumni.org>
To: <te-wg@ops.ietf.org>
Cc: "Goldfless, Sandy - private" <sandy9@rcn.com>
Subject: Suggestion about Russian Dolls
Date: Mon, 20 Jan 2003 17:22:30 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <OE157SWoBDyseVwrblZ00020d59@hotmail.com>
X-OriginalArrivalTime: 20 Jan 2003 22:21:28.0412 (UTC) FILETIME=[46D981C0:01C2C0D2]
X-Spam-Status: No, hits=1.0 required=5.0
	tests=SPAM_PHRASE_00_01,USER_AGENT_OE
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello,

I just joint this list.

I have been reading

draft-ietf-tewg-diff-te-russian-00.txt
and
draft-ietf-tewg-diff-te-reqts-06.txt

and I thought that the algorithm for the Russian Dolls
Bandwidth Constraint model was not well defined.

Below is my suggestion for the algorithm to be included
in Section 4.3 of "reqts-06" and Section 4 of "russian-00":

---------------------------------
Formula:
---------
Let M be MaxCT = MaxBC

for 0 <= b <= (M - 1)
BW of (sum of CTc) <= BCb
where
b <= c <= (M - 1)

Examples:
-----------
E.g., M = 3
then 0 <= b <= 2

for b = 0
0 <= c <= 2
BW (CT0 + CT1 + CT2) <= BC0

for b = 1
1 <= c <= 2
BW (CT1 + CT2) <= BC1

for b=2
2 <= c <= 2
BW (CT2) <= BC2


Regards,

Victoria Fineberg
fineberg@illinoisalumni.org




From owner-te-wg@ops.ietf.org  Tue Jan 21 04:42: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 EAA24524
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 04:42:29 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18auvL-000J5s-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 01:42:27 -0800
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18auvH-000J4F-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 01:42:23 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0L9fpM13564
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 04:41:51 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ2668KD>; Tue, 21 Jan 2003 10:41:50 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BADD88@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 10:41:32 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> Well, all the detailed requirements are grouped under section 
> 4 and they
> are all "marked" with a "must" (or "should/may"). Seems like a
> reasonably clear way to present them.
> There is some (non-requirement) text preceding the actual requirements
> to provide background/definition for the formulation of the 
> requirement.
> I think it is best to keep all that together so one can understand the
> requirements.
> 
> The reason we did not capitalise the "must/should/may" is that this
> document is going for Informational track so we were not sure
> MUST/SHOULD/MAY were appropriate. Sounds like they are, so we will
> follow your suggestion and capitalize them.
> 
Mmmm.. take a look at RFC3216 sect 4 for example. I think such a form
makes it really clear as to what exactly the requirement is and what
type of requirement it is and what the motivation/explanation is.

I was not so much worried aboutMUST/SHOULD/MAY not being capitalized.
More that the explanantory text and the actual requirements and
sometimes examples/scenario-text is all mixed. 

For example, could you easily tell me how many mandatoty and
how many optional requirements there are?

Bert



From owner-te-wg@ops.ietf.org  Tue Jan 21 05:25: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 FAA25148
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 05:25:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18avco-000KBv-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 02:27:22 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18avcm-000KBQ-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 02:27:20 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0LAPARi017568;
	Tue, 21 Jan 2003 11:25:11 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 21 Jan 2003 11:26:15 +0100
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: Suggestion about Russian Dolls
Date: Tue, 21 Jan 2003 10:26:13 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E77A@xbe-lon-303.cisco.com>
Thread-Topic: Suggestion about Russian Dolls
Thread-Index: AcLA0qnZ7qlxvGn9TSWtjETJ5dfZVAAYElBA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Victoria Fineberg" <fineberg@illinoisalumni.org>, <te-wg@ops.ietf.org>
Cc: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-OriginalArrivalTime: 21 Jan 2003 10:26:15.0518 (UTC) FILETIME=[872F47E0:01C2C137]
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.43
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 FAA25148

Victoria,

>> Below is my suggestion for the algorithm to be included
>> in Section 4.3 of "reqts-06" and Section 4 of "russian-00":
>> 
>> ---------------------------------
>> Formula:
>> ---------
>> Let M be MaxCT = MaxBC
>> 
>> for 0 <= b <= (M - 1)
>> BW of (sum of CTc) <= BCb
>> where
>> b <= c <= (M - 1)
>> 

If we want to go for a definition with formulas, then I'd suggest
something like this:
"
Let us define "Reserved(CTb)" as the sum of the bandwidth reserved by
all established LSPs which belong to CTb.
- MaxBC= MaxCT
- for 0 <= b <= (MaxCT - 1):
	* sum (Reserved (CTc)) <= BCb, where b <= c <= (MaxCT - 1)
"

But then we should probably also update the definition for MAM also for
consistency. It would read:
"
Let us define "Reserved(CTb)" as the sum of the bandwidth reserved by
all established LSPs which belong to CTb.
- MaxBC= MaxCT
- for 0 <= b <= (MaxCT - 1):
	* Reserved (CTb) <= BCb
"

Let's see if everyone is comfortable with these formula-based
definitions. If yes, we can include them in the updates of "-reqts" and
"russian" instead of the current text-based definitions.

Cheers

Francois





From owner-te-wg@ops.ietf.org  Tue Jan 21 06:48:16 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26378
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 06:48:15 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18awp4-000Lvy-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 03:44:06 -0800
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18awp1-000Lv2-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 03:44:03 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LBhTM16982
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 06:43:29 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ267A55>; Tue, 21 Jan 2003 12:43:28 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BADE38@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 12:43:18 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.4 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

> >> - sect 3.2 talks (two places) about "the order in which tunnels are
> >>   routed". What does that (ordering of tunnels) mean ?
> 
> Before being available, TE tunnels need to be established. This
> establishment includes computing route for the tunnel and signaling
> tunnel establishment (and thus reserving bandwidth). The 
> order in which these tunnels are established/routed can greatly
> affect which tunnels can grab bandwidth and which cannot, and thus
> greatly affects the state of the final system. 
> 
OK, that explains it somewhat to me... but I cannot get that from
the text in the I-D. Maybe add something about that.
Or is it clear to all TE-WGers and is it just me?

> >> - what are thelast 2 paragraphs on page 7 trying to say?
> >>   sounds like blabla and handwaving to me, no?
> 
> They are trying to say something specific :
> Some SPs would like to simultaneously:
> 	- offer "Very High QoS Guaranteed Traffic" and "Normal Traffic"
> 	- they want to do admission control of "Very High QoS Guaranteed
> Traffic" to ensure it fits in the queue dedicated to that service
> 	- they want to do regular TE of Normal traffic
>
How is "Very High QoS Guaranteed Traffic" defined? What does it mean.
What do you mean by "Normal Traffic" ??
 
> This leads to the need for doing TE CAC on more than one 
> Bandwidth pools (which is what DS-TE is all about).
> 
> >> - sect 4. 1st sentence
> >>   s/implementations/techniques or protocols/ ??
> 
> Agreed. Since we already mention several times the "DS-TE 
> solution" , we could s/implementations/solution/
> 
OK

> >>   In other words... we are not mandating any "implementation" are we.
> >>   We are specifying functionality for (potential) DS-TE protocols are
> >>   we not?
> >> - sect 4.2 
> >>   Is the first sentence not a generic TE requirement and not specific
> >>   to DS-TE? Maybe I get confused since you did not define the term
> >>   "Traffic Trunc"
> 
> Section "1.2 Definitions" contains a definition for "Traffic Trunks".
> 
Ooops... sorry

> >> - Is most of the text in sect 4.2 on page 9 not just another 
> >>   scenario that belongs in sect 3?
> 
> We tried to keep things simple in the scenarios (eg only talked about
> "classes of service"). The objectives of the scenarios is to give a
> simple-to-grab understanding of what SPs want to do.
> In section 4.2 we are trying to describe the relationship between CTs
> and classes/PHBs. This requires more complex terminology and mapping
> examples. Also, in section 4.2 we are not describing what application
> the is trying to achieve, just how CTs may be "mapped".
> 
Section 4 I thought was to list the requirements.... 
I think it all boils down to the fact that it is really difficult
to find exactly what the requirements are. It is too much intermingled
with other text (at least to my taste).

> >> - does the "criteria to be considered" on page 11 not belong in
> >>   section 5?
> 
> Agreed.
> When updating the text of 4.2 about Default model, we will move the BC
> Model criteria to section 5. 
> 
thanks

> >> - On page 11 you reference [BC-MODEL] but it is not listed in the
> >>   references section I think.
> 
> Noted.
> 
> >> - Page 13. Maybe I just do not udnerstand... but it seems to me 
> >>   that this text:
> >> 
> >>     The network administrator would then, in particular, NOT be able
> >>     to :
> >>     - transport a CT0 Traffic Trunk over an LSP with setup priority=1
> >>       and holding priority=1
> >>     - transport a CT1 Traffic Trunk over an LSP with setup priority=0
> >>       and holding priority=0
> >>    
> >>   Conflicts with the immediately following text:
> >> 
> 
> In the previous paragraph, it is important to note the word "then".
> "Then" was intended to mean "in the case of the example  CTs definition
> which is given above". Given this "CT definition", the text is correct.
> The paragraph below would require a differnet "CT definition".
> 
Now that you point it out, I think I see it... 
Maybe just me ??!!

> >>     DS-TE must allow two LSPs transporting Traffic Trunks from different
> >>     Class-Types to use the same preemption priority. In other words, the
> >>     DS-TE solution must allow TE-classes using different CTs to use the
> >>     same preemption priority. This effectively allows the network
> >>     administrator to ensure that no preemption happens across Class-
> >>     Types, if so desired.
> >> 
> >>     As an example, the DS-TE solution must allow the network
> >>     administrator to define three Class-Types (CT0, CT1 and CT2) each
> >>     comprising one TE-Class which uses preemption 0. In that case, no
> >>     preemption will ever occur.
> >> 
> >>   Or do I indeed not understand?
> >> - May I assume that all TE-WG members understand the notations used in 
> >>   section 4.5 ?? Cause I would have to go and study in detail if I
> >>   want to get it.
> 
> A definition for these terms is actually provided in section "1.2
> Definitions".
> 
I was not speaking about the definitions alone.

> >> - sect 4.6
> >>   I guess the reference to sect 2.2 should be to 3.2 ??
> 
> Right.
> 
> >> - The last 2 sentences of 1st para of sect 4.6 mean what?
> >>   Is it an "optional requirement" or is it "ou of scope" ??
> >>   if out of scope, then why is sect 4.6 present?
> 
> Yeah, a little confusing right now ^)
> I propose to just specify it as optional and get rid of the "out of
> scope" statement. 
> 
> >> - sect 5.1 refers to sections 2 and 3, which I think should 
> >> respectively
> >>   be 3 and 4
> 
> Noted.
> 
> >> - The security considerations section seems very weak, see 
> >> underlined:
> >> 
> >>    The solution developed to address the requirements 
> defined in this
> >>    document must address security aspects. DS-TE is not 
> >> expected to add
> >>    specific security requirements beyond those of Diff-Serv and
> >>    existing TE.  Networks which employ Diff-Serv techniques 
> >> might offer
> >>                                                            ------
> >>    some protection between classes for denial of service attacks.
> >>    ------
> >>    Though depending on how the technology is employed, it 
> is possible
> >>    for some (lower scheduled) traffic to be more susceptible 
> >> to traffic
> >>    anomalies (which include denial of service attacks) 
> >> occurring within
> >>    other (higher scheduled) classes.
> >> 
> 
> My proposal would be to just keep the two first sentences (ie DSTE
> solution must address security. DS-TE not expected to add new security
> issues beyond those of Diff-Serv and TE) and get rid of the rest since
> we do not have to start discussing how security may be achieved in the
> Reqt document itself.
> 
The "not expected" does not sound right. It sounds as if you have no
real clue what security impacts/requirements these DS-TE requirements
bring to the table.

> 
> >>   See also comments by others from ops-directorate reviewers
> >>   
> >> 
> >> spelling nits:
> >> - first linbe page 6
> >>   s/be able/be possible/ ??
> 
> I think "be able" is correct.
> Before, we already say " VoIP traffic should be able ..." and here we
> mean that the VoIP traffic should be able to use the shortest path.
> 
Mmm... so yout "it" stands for "VoIP traffic" ...
got it now.

> >> - first 2 paragaraphs on page 7 have conflicting current and past
> >>   tense usage of verbs
> 
> Noted
> 
> >> - setc 3.3 5th line
> >>   s/ to and egress port/to an egress port/
> 
> Noted
> 
> >> - bottom of page 8
> >>   s/section 3.4 below/section 4.3 below/
> 
> Actually it should be section 4.4.
> 
> >> - page 11, inconsistent use of "criteria" and "criterion"
> >> 
> 
> Noted.
> 
> 
> >> Thanks,
> >> Bert 
> >> 

Bert



From owner-te-wg@ops.ietf.org  Tue Jan 21 06:51: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 GAA26411
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 06:51:01 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18awxJ-000MA2-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 03:52:37 -0800
Received: from ux2.ibb.net ([62.8.32.147])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18awxG-000M9p-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 03:52:35 -0800
Received: from ttz505ls (oudkerkhof.xs4all.nl [213.84.183.141])
	by ux2.ibb.net (8.11.3/8.11.3/UX2TT) with SMTP id h0LBqMp09637;
	Tue, 21 Jan 2003 12:52:23 +0100 (MET)
Message-ID: <007d01c2c143$7746e660$1701a8c0@gblx.net>
From: "Thomas Telkamp" <telkamp@gblx.net>
To: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
        "Wijnen, Bert \(Bert\)" <bwijnen@lucent.com>,
        "Te-Wg \(E-mail\)" <te-wg@ops.ietf.org>
Cc: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
        <dallan@nortelnetworks.com>
References: <BC2F7EDC0F122B439B4AF1C656BA34F90168E775@xbe-lon-303.cisco.com>
Subject: Re: Review of draft-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 12:51:34 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Status: No, hits=2.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,RCVD_IN_RFCI,REFERENCES,
	      SPAM_PHRASE_00_01,USER_AGENT_OE
	version=2.43
X-Spam-Level: **
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> >> 3.1, scenario 1, the example of 10,000 uncompressed calls
> >> seems a bit specious. What grounding in reality does
> >> that have? This is supposed to be giving requirements so
> >> it seems the examples should not be merely illustrative.
>
> Some Service Providers are carrying part of their national PSTN traffic
> over their packet network today. Voice VPN traffic is also transported
> over the core. As migration of those continues, 10000 calls is felt as a
> realistic order of magnitude for 1-3 year requirements.
>
> But this text was provided by Thomas from Global Crossing, so Thomas may
> want to add his view.

Indeed, 10000 calls is not a 'specious' number. We currently do more than 1
billion VoIP minutes per month, and around busy sites you will have links
with that amount of traffic (peak).

This example was meant to illustrate that VoIP traffic is not necessarily an
insignificant percentage of the total traffic carried, and therefore
relevant for this draft.

> >> 3.1, second sentence. So I know how to determine the
> >> "certain percentage" of VoIP traffic and it has to
> >> do with a number of factors including the type of
> >> scheduler in the forwarding path. But this sounds like
> >> a lot of handwaving on the part of the authors.
>
> I am not sure what is the specific concern/suggestion.
> Effectively what we're trying to say is:
> - VoIP load can be significant compared to link capacity
> - some SPs feel that controlling the maximum load of VoIP on
> all/some links is one of the tools that will help them control the level
> of QoS [even if this document does not discuss the actual relationship
> between (i) VoIP load, (ii) QoS levels and (iii) other factors including
> type of scheduler]
>
> To be able to address this I'd need to know whether:
> - there is a disagreement that some SPs feel that way
> - we are not phrasing the above clearly enough (specific
> suggestions will help)

The purpose of this draft is not to define such a percentage, but to present
a requirement/solution to maintain a maximum load for this type of traffic.
How this will be used in real networks (what percentage) depends on a lot of
factors that are different for each network, and will be determined by the
SPs.

---
Thomas





From owner-te-wg@ops.ietf.org  Tue Jan 21 08:24: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 IAA28731
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 08:24:53 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18ayN7-000Oq1-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 05:23:21 -0800
Received: from oe13.pav0.hotmail.com ([64.4.32.93] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18ayN4-000OoK-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 05:23:19 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 21 Jan 2003 05:22:47 -0800
X-Originating-IP: [63.15.53.216]
Reply-To: "Victoria Fineberg" <fineberg@illinoisalumni.org>
From: "Victoria Fineberg" <fineberg@illinoisalumni.org>
To: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
Cc: "Te-Wg \(E-mail\)" <te-wg@ops.ietf.org>
References: <BC2F7EDC0F122B439B4AF1C656BA34F90168E77A@xbe-lon-303.cisco.com>
Subject: Re: Suggestion about Russian Dolls
Date: Tue, 21 Jan 2003 08:23:48 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <OE13pHa4qAINZ42EOJ800008d92@hotmail.com>
X-OriginalArrivalTime: 21 Jan 2003 13:22:47.0753 (UTC) FILETIME=[30A61390:01C2C150]
X-Spam-Status: No, hits=-0.3 required=5.0
	tests=QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,
	      USER_AGENT_OE
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Francois,

Thanks.  I provided some comments in-line.

Cheers

Victoria


----- Original Message ----- 
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Victoria Fineberg" <fineberg@illinoisalumni.org>; <te-wg@ops.ietf.org>
Cc: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Sent: Tuesday, January 21, 2003 5:26 AM
Subject: RE: Suggestion about Russian Dolls


> Victoria,

>> Below is my suggestion for the algorithm to be included
>> in Section 4.3 of "reqts-06" and Section 4 of "russian-00":
>> 
>> ---------------------------------
>> Formula:
>> ---------
>> Let M be MaxCT = MaxBC
>> 
>> for 0 <= b <= (M - 1)
>> BW of (sum of CTc) <= BCb
>> where
>> b <= c <= (M - 1)
>> 

> If we want to go for a definition with formulas, then I'd suggest
> something like this:

> "
> Let us define "Reserved(CTb)" as the sum of the bandwidth reserved by
> all established LSPs which belong to CTb.

Should not these be "Reserved(CTc)" and CTc ?


> - MaxBC= MaxCT
> - for 0 <= b <= (MaxCT - 1):
> * sum (Reserved (CTc)) <= BCb, where b <= c <= (MaxCT - 1)
> "

May be it would be even more clear if we say:

- MaxBC= MaxCT
- for each 0 <= b <= (MaxCT - 1):
        SUM (Reserved (CTc)) <= BCb,
        for all "c" in the range  b <= c <= (MaxCT - 1)

?


> But then we should probably also update the definition for MAM also for
> consistency. It would read:
> "
> Let us define "Reserved(CTb)" as the sum of the bandwidth reserved by
> all established LSPs which belong to CTb.
> - MaxBC= MaxCT
> - for 0 <= b <= (MaxCT - 1):
> * Reserved (CTb) <= BCb
> "

I suggest to still use "Reserved(CTc)" and CTc and add a line
b = c.  Then it would read:

"
Let us define "Reserved(CTc)" as the sum of the bandwidth reserved by
all established LSPs which belong to CTc.
- MaxBC= MaxCT
- b = c
- for each 0 <= b <= (MaxCT - 1):
        Reserved (CTc) <= BCb
"

If we then provide examples that closely replicate formulas, that should
make it clear enough.


> Let's see if everyone is comfortable with these formula-based
> definitions. If yes, we can include them in the updates of "-reqts" and
> "russian" instead of the current text-based definitions.

> Cheers

> Francois



From owner-te-wg@ops.ietf.org  Tue Jan 21 08:34: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 IAA29396
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 08:34:30 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18ayaQ-000PKL-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 05:37:06 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18ayaN-000PIn-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 05:37:03 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0LDYuvo024515;
	Tue, 21 Jan 2003 14:34:58 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 21 Jan 2003 14:36:28 +0100
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: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 13:36:27 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E77C@xbe-lon-303.cisco.com>
Thread-Topic: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Thread-Index: AcLBQlr0k/JTj0FoRQeg7rk3xPcqcwACHCmA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 21 Jan 2003 13:36:28.0841 (UTC) FILETIME=[1A0E2990:01C2C152]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
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 IAA29396

Bert,

I removed all the items we agreed on. See below on the open ones:

>> > >> - sect 3.2 talks (two places) about "the order in which 
>> tunnels are
>> > >>   routed". What does that (ordering of tunnels) mean ?
>> > 
>> > Before being available, TE tunnels need to be established. This
>> > establishment includes computing route for the tunnel and signaling
>> > tunnel establishment (and thus reserving bandwidth). The 
>> > order in which these tunnels are established/routed can greatly
>> > affect which tunnels can grab bandwidth and which cannot, and thus
>> > greatly affects the state of the final system. 
>> > 
>> OK, that explains it somewhat to me... but I cannot get that from
>> the text in the I-D. Maybe add something about that.
>> Or is it clear to all TE-WGers and is it just me?
>> 

I would expect that to be clear to people who are familiar with the
[TEWG-FW] and [TE-REQ] documents we included as Normative References.
Still, we can replace:
 "   - in which order the different TE-LSPs are routed"
by
 "   - in which order the different TE-LSPs are routed (since this
affects which TE-LSP can reserve bandwidth first)"


>> > >> - what are thelast 2 paragraphs on page 7 trying to say?
>> > >>   sounds like blabla and handwaving to me, no?
>> > 
>> > They are trying to say something specific :
>> > Some SPs would like to simultaneously:
>> > 	- offer "Very High QoS Guaranteed Traffic" and "Normal Traffic"
>> > 	- they want to do admission control of "Very High QoS Guaranteed
>> > Traffic" to ensure it fits in the queue dedicated to that service
>> > 	- they want to do regular TE of Normal traffic
>> >
>> How is "Very High QoS Guaranteed Traffic" defined? What does it mean.
>> What do you mean by "Normal Traffic" ??
>>  

"Very High QoS" translates into different Service Level Specification
(SLS) with different operators. That's a desired property of IP QoS.
Here , we don't want to define it very precisely. The text just says
that when supporting such "Guaranteed Bandwidth" service, "it may be
necessary to ensure that ...".
The practical thing behind is that indeed some SPs want to market SLS
with very tight commitment and perform separate admission control of
this traffic as one of the mechanisms to ensure the SLS.

In the document we don't actually use the term "Normal Traffic". We just
refer to "the rest of the traffic".

>> > >> - Is most of the text in sect 4.2 on page 9 not just another 
>> > >>   scenario that belongs in sect 3?
>> > 
>> > We tried to keep things simple in the scenarios (eg only 
>> talked about
>> > "classes of service"). The objectives of the scenarios is to give a
>> > simple-to-grab understanding of what SPs want to do.
>> > In section 4.2 we are trying to describe the relationship 
>> between CTs
>> > and classes/PHBs. This requires more complex terminology 
>> and mapping
>> > examples. Also, in section 4.2 we are not describing what 
>> application
>> > the is trying to achieve, just how CTs may be "mapped".
>> > 
>> Section 4 I thought was to list the requirements.... 

Yes, the objective of section 4.2 is to list the requirements related to
Class-Types. But before we do so, we define exactly what CTs are and
their relationship to relevant concepts. This is part of the definitions
necessary for formulating the related requirements.

>> I think it all boils down to the fact that it is really difficult
>> to find exactly what the requirements are. It is too much 
>> intermingled
>> with other text (at least to my taste).
>> 

You raised this in a separate email, so I'll follow that up there.

>> > >> - May I assume that all TE-WG members understand the 
>> notations used in 
>> > >>   section 4.5 ?? Cause I would have to go and study in 
>> detail if I
>> > >>   want to get it.
>> > 
>> > A definition for these terms is actually provided in section "1.2
>> > Definitions".
>> > 
>> I was not speaking about the definitions alone.
>>

FEC, E-LSP and L-LSP are really well-known terms in MPLS land.
TA and PSC are well-known in Diff-Serv land.
The only new things are {TA}PSC and <FEC/{TA}PSC> which are defined in
the definition section.
So I think we can assume the notations are understood.
We didn't get any concern even at Last Call.
 
>> > My proposal would be to just keep the two first sentences (ie DSTE
>> > solution must address security. DS-TE not expected to add 
>> new security
>> > issues beyond those of Diff-Serv and TE) and get rid of 
>> the rest since
>> > we do not have to start discussing how security may be 
>> achieved in the
>> > Reqt document itself.
>> > 
>> The "not expected" does not sound right. It sounds as if you have no
>> real clue what security impacts/requirements these DS-TE requirements
>> bring to the table.
>>

I see your point.
I guess the "not expected" stems from the fact that we may have been
trying to bundle two things (requirements vs mechanisms):
	- there is no identified specific security requirements for DSTE
beyond those of TE and Diff-Serv
	- without assuming anything about DS-TE solution, we can't be
quite sure that existing security mechanisms won't get broken by DS-TE.

So how about breaking this up into something like :

"
The solution developed to address the requirements defined in this
document must address security aspects. DS-TE does not raise any
specific additional security requirements beyond the existing security
requirements of MPLS TE and Diff-Serv. The solution must ensure that the
existing security mechanisms of MPLS TE and Diff-Serv are not
compromised by the solution protocol/procedure extensions or otherwise
must provide security mechanisms to address this. 
"

Thanks 

Francois



From owner-te-wg@ops.ietf.org  Tue Jan 21 08:53: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 IAA00152
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 08:53:04 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18ayri-000Pzn-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 05:54:58 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18ayrc-000Pz3-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 05:54:52 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0LDqh6U027869;
	Tue, 21 Jan 2003 14:52:47 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 21 Jan 2003 14:54:17 +0100
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: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 13:54:16 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E77B@xbe-lon-303.cisco.com>
Thread-Topic: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Thread-Index: AcLBMVl4B2I20bcvSCWHMzaRYuBSmgADOOag
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 21 Jan 2003 13:54:17.0348 (UTC) FILETIME=[96EF6440:01C2C154]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
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 IAA00152

Hello Bert,

>> -----Original Message-----
>> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
>> Sent: 21 January 2003 10:42
>> To: Francois Le Faucheur (flefauch); Tewg (E-mail)
>> Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
>> 
>> 
>> > Well, all the detailed requirements are grouped under section 
>> > 4 and they
>> > are all "marked" with a "must" (or "should/may"). Seems like a
>> > reasonably clear way to present them.
>> > There is some (non-requirement) text preceding the actual 
>> requirements
>> > to provide background/definition for the formulation of the 
>> > requirement.
>> > I think it is best to keep all that together so one can 
>> understand the
>> > requirements.
>> > 
>> > The reason we did not capitalise the "must/should/may" is that this
>> > document is going for Informational track so we were not sure
>> > MUST/SHOULD/MAY were appropriate. Sounds like they are, so we will
>> > follow your suggestion and capitalize them.
>> > 
>> Mmmm.. take a look at RFC3216 sect 4 for example. I think such a form
>> makes it really clear as to what exactly the requirement is and what
>> type of requirement it is and what the motivation/explanation is.
>> 

Yes, very neat. The structuring makes all of this very obvious, and I'll
certainly look at this as a good model for requirements documents.

But, while you cannot just have a quick look at the diff-te-reqts
document and immediately count how many items are mandatory and how many
are optional, my impression is that when you read the various
sub-sections of section "4 Detailed Requirements", it is reasonably
clear whether something is background, example, mandatory requirement or
optional (It will be even clearer when capitalised). It is not as neat,
since you do have to read the whole text and couldn't easily fill-in
"compliance statements" saying we meet items x,y,z and don't meet items
a,b,c;  But practically speaking it has proved quite appropriate for
guiding us in developping the DS-TE protocol extensions (which are due
for WG Last Call very shortly).

So, considering that the WG has been in agreement on the actual content
for a while, and that the corresponding protocol extensions based on
this are ready for Last Call, I'm inclined towards the approach of "not
perfect, but does the job" and avoid significant editing changes just
for easier identification of same content. This is all in the view of
finalising that document asap, since it conditions all the DSTE work.

Is there any way you could live with the current structure (ie
background/definition + requirement/MUST in same sub-section)?
 
Thanks

Francois

>> I was not so much worried aboutMUST/SHOULD/MAY not being capitalized.
>> More that the explanantory text and the actual requirements and
>> sometimes examples/scenario-text is all mixed. 
>> 
>> For example, could you easily tell me how many mandatoty and
>> how many optional requirements there are?
>> 
>> Bert
>> 



From owner-te-wg@ops.ietf.org  Tue Jan 21 11:06: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 LAA03691
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 11:06:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b0wA-0004wV-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 08:07:42 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b0w3-0004w6-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 08:07:35 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LG7Fx07348
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 11:07:16 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ26720T>; Tue, 21 Jan 2003 17:07:14 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BADFBC@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: more review comments: draft-tewg-ietf-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 17:06:53 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.9 required=5.0
	tests=BALANCE_FOR_LONG_20K,BALANCE_FOR_LONG_40K,EXCHANGE_SERVER,
	      QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Again, sorry for late forwarding. This is the last one
I had to dig up.

Thanks,
Bert 

-----Original Message-----
From: David Meyer [mailto:dmm@sprint.net]
Sent: woensdag 6 november 2002 15:34
To: Randy Bush
Cc: ops directorate
Subject: Re: early peek at draft-tewg-ietf-diff-te-reqts-06.txt


One thing I forgot to mention is that any draft proposing a
service (or set of services) based on diff-serv should describe
in it's security section what kind of DoS vulnerabilities the
service might incur. While this is alluded to below, more detail
would be useful. For example, while they say:

"Though depending on how the technology is employed, it is
possible for some (lower scheduled) traffic to be more
susceptible to traffic anomalies (which include denial of service
attacks) occurring within other (higher scheduled) classes."

I can think of several ways to DoS the higher class (under certain
conditions). However, it sounds (from this text) that the DoS
would "spill over" into lower classes and not affect the "higher
scheduled class". 

Dave


On Wed, Nov 06, 2002 at 06:25:09AM -0800, David Meyer wrote:
>> On Wed, Nov 06, 2002 at 05:28:32AM -0800, Randy Bush wrote:
>> >> From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
>> >> To: "Randy Bush (E-mail)" <randy@psg.com>
>> >> Subject: draft-tewg-ietf-diff-te-reqts-06.txt
>> >> Date: Wed, 6 Nov 2002 14:24:09 +0100 
>> >> 
>> >> Randy, I am doing AD review now.
>> >> I have all sorts of NITs, but would you rather have ops-dir
>> >> take a look at it now (while still in AD review) as opposed
>> >> to later (when I put it on IESG agenda)?
>> 
>> Some initital comments, mostly nits (search for @@@). Will look
>> it over again this afternoon. 
>> 
>> 
>> Dave
>> ----
>> 
>> 
>> 
>>                                             Francois Le Faucheur, Editor 
>>                                                      Cisco Systems, Inc. 
>>     
>>                                                    Waisum Lai, Co-editor 
>>                                                                     AT&T 
>>  
>>                                                                          
>> IETF Internet Draft 
>> Expires: March, 2003                                                
>> Document: draft-ietf-tewg-diff-te-reqts-06.txt         September 2002 
>>  
>>  
>>                       Requirements for support of  
>>                 Diff-Serv-aware MPLS Traffic Engineering 
>>  
>>  
>> Status of this Memo 
>>     
>>    This document is an Internet-Draft and is in full conformance with 
>>    all provisions of Section 10 of RFC2026. Internet-Drafts are 
>>    Working documents of the Internet Engineering Task Force (IETF), its 
>>    areas, and its working groups.  Note that other groups may also 
>>    distribute working documents as Internet-Drafts. 
>>     
>>    Internet-Drafts are draft documents valid for a maximum of six 
>>    months and may be updated, replaced, or obsoleted by other documents 
>>    at any time. It is inappropriate to use Internet-Drafts as reference 
>>    material or to cite them other than as "work in progress." 
>>     
>>    The list of current Internet-Drafts can be accessed at 
>>    http://www.ietf.org/ietf/1id-abstracts.txt. 
>>    The list of Internet-Draft Shadow Directories can be accessed at 
>>    http://www.ietf.org/shadow.html. 
>>     
>>     
>> Abstract 
>>     
>>    This document presents the Service Provider requirements for support 
>>    of Diff-Serv aware MPLS Traffic Engineering (DS-TE).  
>>     
>>    Its objective is to provide guidance for the definition, selection 
>>    and specification of a technical solution addressing these  
>>    requirements. Specification for this solution itself is outside the 
>>    scope of this document. 
>>     
>>    A problem statement is first provided. Then, the document describes 
>>    example applications scenarios identified by Service Providers where 
>>    existing MPLS Traffic Engineering mechanisms fall short and Diff-
>>    Serv-aware Traffic Engineering is required. The detailed 
>>    requirements that need to be addressed by the technical solution are 
>>    also reviewed. Finally, the document identifies the evaluation 
>>    criteria that should be considered for selection and definition of 
>>    the technical solution. 
>>   
>> Le Faucheur, et. al                                                  1 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>     
>>     
>> 1.      Introduction 
>>     
>> 1.1.    Problem Statement 
>>  
>>    Diff-Serv is becoming prominent in providing scalable network 
>>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>    designs supporting multiple classes of services.  
>>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
>> @@@ This is a marketing statement, as I know of at least one
>> @@@ provider who sees it differently
>> 
>>    In some Diff-Serv networks where optimization of transmission 
>>    resources on a network-wide basis is not sought, MPLS Traffic 
>>    Engineering (TE) mechanisms may simply not be used.  
>>     
>>    In other networks, where optimization of transmission resources is 
>>    sought, Diff-Serv mechanisms [DIFF-MPLS] need to be complemented by 
>>    existing MPLS Traffic Engineering mechanisms [TE-REQ] [ISIS-TE] 
>>    [OSPF-TE] [RSVP-TE] [CR-LDP] which operate on an aggregate basis 
>>    across all Diff-Serv classes of service. In this case, Diff-Serv and 
>>    MPLS TE both provide their respective benefits.  
>> 
>> @@@ Again, what is meant in the above by "optimization" I presume
>> @@@ is CAPEX optimization (i.e., optimized utilization)? Even
>> @@@ that much doesn't seem to be supported.
>> 
>>    Where fine-grained optimization of transmission resources is sought, 
>>    it is necessary to perform traffic engineering at a per-class level 
>>    instead of an aggregate level, in order to further enhance networks 
>>    in performance and efficiency as discussed in [TEWG-FW]. By mapping 
>>    the traffic from a given Diff-Serv class of service on a separate 
>>    LSP, it allows this traffic to utilize resources available to the 
>>    given class on both shortest path and non-shortest paths and follow 
>>    paths that meet engineering constraints which are specific to the 
>>    given class. This is what we refer to as "Diff-Serv-aware Traffic 
>>    Engineering (DS-TE)". 
>>     
>>    This document focuses exclusively on the specific environments which 
>>    would benefit from DS-TE. Some examples include: 
>>     
>>      -    networks where bandwidth is scarce (e.g. transcontinental 
>>           networks) 
>> 
>> @@@ ?
>>      -    networks with significant amounts of delay-sensitive traffic 
>>      -    networks where the relative proportion of traffic across 
>>           classes of service is not uniform  
>>     
>>    This document focuses on intra-domain operation. Inter-domain 
>>    operation is not considered. 
>>     
>> 1.2.    Definitions 
>>     
>>    For the convenience of the reader, relevant Diffserv ([DIFF-ARCH], 
>>    [DIFF-NEW] and [DIFF-PDB]) definitions are repeated herein. 
>>     
>>        Behavior Aggregate (BA): a collection of packets with the same 
>>        (Diff-Serv) codepoint crossing a link in a particular direction. 
>>         
>> 
>>  
>>  Le Faucheur et. al                                                  2 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>        Per-Hop-Behavior (PHB): the externally observable forwarding                  
>>        behavior applied at a DS-compliant node to a Diff-Serv behavior 
>>        aggregate. 
>>         
>>        PHB Scheduling Class (PSC): A PHB group for which a common 
>>        constraint is that ordering of at least those packets belonging 
>>        to the same microflow must be preserved. 
>>     
>>        Ordered Aggregate (OA): a set of BAs that share an ordering 
>>        constraint. The set of PHBs that are applied to this set of 
>>        Behavior Aggregates constitutes a PHB scheduling class. 
>>         
>>        Traffic Aggregate (TA): a collection of packets with a codepoint 
>>        that maps to the same PHB, usually in a DS domain or some subset 
>>        of a DS domain.  A traffic aggregate marked for the foo PHB is 
>>        referred to as the "foo traffic aggregate" or "foo aggregate" 
>>        interchangeably. This generalizes the concept of Behavior 
>>        Aggregate from a link to a network. 
>>     
>>    We also repeat the following definition from [TE-REQ]: 
>>     
>>        Traffic Trunk: an aggregation of traffic flows of the same class 
>>        which are placed inside a Label Switched Path. 
>>         
>>   In the context of the present document, "flows of the same class" is 
>>   to be interpreted as "flows from the same Forwarding Equivalence 
>>   Class which are to be treated equivalently from the DS-TE 
>>   perspective". 
>>     
>>    We refer to the set of TAs corresponding to the set of PHBs of a 
>>    given PSC, as a {TA}PSC. We also loosely refer to a {TA}PSC as a 
>>    Diff-Serv class of service, or class-of service. 
>>     
>>    We refer to the collection of packets which belong to a given Traffic 
>>    Aggregate and are associated with a given MPLS Forwarding Equivalence 
>>    Class (FEC) as a <FEC/TA>. 
>>     
>>    We refer to the set of <FEC/TA> whose TAs belong to a given {TA}PSC 
>>    as a <FEC/{TA}PSC>. 
>> 
>> 1.3.    Mapping of traffic to LSPs 
>>     
>>    A network may have multiple Traffic Aggregates (TAs) it wishes to 
>>    service. Recalling from [DIFF-MPLS], there are several options on 
>>    how the set of <FEC/{TA}PSC> of a given FEC can be split into 
>>    Traffic Trunks for mapping onto LSPs when running MPLS Traffic 
>>    Engineering.  
>>     
>>    One option is to not split this set of <FEC/{TA}PSC> so that each 
>>    Traffic Trunk comprises traffic from all the {TA}/PSC . This option 
>>    is typically used when aggregate traffic engineering is deployed 
>>    using current MPLS TE mechanisms. In that case, all the 
>>  
>>  Le Faucheur et. al                                                  3 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    <FEC/{TA}PSC> of a given FEC are routed collectively according to a 
>>    single shared set of constraints and will follow the same path. Note 
>>    that the LSP transporting such a Traffic Trunk is, by definition, an 
>>    E-LSP as defined in [DIFF-MPLS]. 
>>     
>>    Another option is to split the different <FEC/{TA}PSC> of a given 
>>    FEC into multiple Traffic Trunks on the basis of the {TA}PSC. In 
>>    other words, traffic from a given node to another given node, is 
>>    split based on the classes of service, into multiple Traffic Trunks 
>>    which are transported over separate LSPs, which can potentially 
>>    follow a different path through the network. DS-TE precisely takes 
>>    advantage of this fact and indeed computes a separate path for each 
>>    LSP.
>> 
>> @@@ It would be nice if they quantified the complexity here. 
>> @@@ In addition, the a discussion of the interaction with FRR
>> @@@ would be useful at this point.
>> 
>>    In so doing, DS-TE can take into account the specific 
>>    requirements of the Traffic Trunk transported on each LSP (e.g. 
>>    bandwidth requirement, preemption priority). Moreover DS-TE can take 
>>    into account specific engineering constraints to be enforced for 
>>    these sets of Traffic Trunks (e.g. limit all Traffic Trunks 
>>    transporting a particular {TA}PSC to x% of link capacity). In brief, 
>>    DS-TE achieves per LSP constraint based routing with paths that 
>>    tightly match the specific objectives of the traffic forming the 
>>    ^^^^^^^
>> 
>> @@@ what is the defn of "tightly"?
>> 
>>    corresponding Traffic Trunk. 
>>     
>>    For simplicity, and because this is the specific topic of this 
>>    document, the above paragraphs in this section only considered 
>>    splitting traffic of a given FEC into multiple Traffic Aggregates on 
>>    the basis of {TA}PSC. However, it must be noted that, in addition to 
>>    this, traffic from every {TA}PSC may also be split into multiple 
>>    Traffic Trunks for load balancing purposes. 
>>     
>>     
>> 2.      Contributing Authors 
>>     
>>    This document was the collective work of several. The text and 
>>    content of this document was contributed by the editors and the co-
>>    authors listed below. (The contact information for the editors 
>>    appears in Section 9, and is not repeated below.) 
>>     
>>    Martin Tatham                        Thomas Telkamp 
>>    BT                                   Global Crossing 
>>    Adastral Park, Martlesham Heath,     Oudkerkhof 51,  3512 GJ Utrecht 
>>    Ipswich IP5 3RE, UK                  The Netherlands 
>>    Phone: +44-1473-606349               Phone: +31 30 238 1250 
>>    Email: martin.tatham@bt.com          Email: telkamp@gblx.net 
>>                                          
>>    David Cooper                         Jim Boyle 
>>    Global Crossing                      Protocol Driven Networks, Inc. 
>>    960 Hamlin Court                     1381 Kildaire Farm Road #288 
>>    Sunnyvale, CA 94089, USA             Cary, NC 27511, USA 
>>    Phone: (916) 415-0437                Phone: (919) 852-5160 
>>    Email: dcooper@gblx.net              Email: jboyle@pdnets.com 
>>                                          
>>                                          
>>  
>>  Le Faucheur et. al                                                  4 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    Luyuan Fang                          Gerald R. Ash 
>>    AT&T Labs                            AT&T Labs 
>>    200 Laurel Avenue                    200 Laurel Avenue 
>>    Middletown, New Jersey 07748, USA    Middletown, New Jersey 07748,USA 
>>    Phone: (732) 420-1921                Phone: (732) 420-4578 
>>    Email: luyuanfang@att.com            Email: gash@att.com 
>>                                          
>>    Pete Hicks                           Angela Chiu 
>>    CoreExpress, Inc                     Celion Networks 
>>    12655 Olive Blvd, Suite 500          1 Sheila Drive, Suite 2 
>>    St. Louis, MO 63141, USA             Tinton Falls, NJ 07724, USA 
>>    Phone: (314) 317-7504                Phone: (732) 747-9987 
>>    Email: pete.hicks@coreexpress.net    Email: angela.chiu@celion.com 
>>                                          
>>    William Townsend                     Thomas D. Nadeau 
>>    Tenor Networks                       Cisco Systems, Inc. 
>>    100 Nagog Park                       250 Apollo Drive 
>>    Acton, MA 01720, USA                 Chelmsford, MA 01824, USA 
>>    Phone: +1 978-264-4900               Phone: (978) 244-3051 
>>    Email:btownsend@tenornetworks.com    Email: tnadeau@cisco.com 
>>                                          
>>    Darek Skalecki                        
>>    Nortel Networks                       
>>    3500 Carling Ave,                     
>>    Nepean K2H 8E9,                       
>>    Phone: (613) 765-2252                 
>>    Email: dareks@nortelnetworks.com      
>>     
>>     
>>     
>> 3.      Application Scenarios 
>>  
>> 3.1.    Scenario 1: Limiting Proportion of Classes on a Link 
>>     
>>    An IP/MPLS network may need to carry a significant amount of VoIP 
>>    traffic compared to its link capacity. For example, 10,000 
>>    uncompressed calls at 20ms packetization result in about 1Gbps of IP 
>>    traffic, which is significant on an OC-48c based network. In case of 
>>    topology changes such as link/node failure, VoIP traffic levels can 
>>    even approach the full bandwidth on certain links. 
>> 
>> @@@ this last sentence doesn't really make sense in the absence
>> @@@ of an understanding of the provider's network (like if I
>> @@@ protect all of my packets, the statement doesn't apply)
>>      
>>    For delay/jitter reasons it is undesirable to carry more than a 
>>    certain percentage of VoIP traffic on any link. 
>> 
>> @@@ but we understand that we can run in the region about 80%
>> @@@ utilization with small jitter and delay (with >= OC48). So
>> @@@ why is it undesirable? This seems statement seems to be unsupported.
>> 
>>    The rest of the available link bandwidth can be used to route
>>    other classes corresponding to delay/jitter insensitive
>>    traffic (e.g. Best Effort Internet traffic). The exact
>>    determination of this "certain" percentage is outside the
>>    scope of this requirements document.  
>>      
>>    During normal operations, the VoIP traffic should be able to preempt 
>>    other classes of traffic (if these other classes are designated as 
>>    preemptable and they have lower preemption priority),  
>> 
>>  
>>  Le Faucheur et. al                                                  5 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    so that it will be able to use the shortest available path, only 
>>    constrained by the maximum defined link utilization ratio/percentage 
>>    of the VoIP class. 
>> 
>>    Existing TE mechanisms only allow constraint based routing of 
>>    traffic based on a single bandwidth constraint common to all 
>>    classes, which does not satisfy the needs described here. This leads 
>>    to the requirement for DS-TE to be able to enforce a different 
>>    bandwidth constraint for different classes of traffic. In the above 
>>    example, the bandwidth constraint to be enforced for VoIP traffic 
>>    may be the "certain" percentage of each link capacity, while the 
>>    bandwidth constraint to be enforced for the rest of the classes 
>>    might have their own constraints or have access to the rest of the 
>>    link capacity.  
>> 
>> 3.2.    Scenario 2: Maintain relative proportion of traffic classes 
>>     
>>    Suppose an IP/MPLS network supports 3 classes of traffic. The 
>>    network administrator wants to perform Traffic Engineering to 
>>    distribute the traffic load. Assume also that proportion across 
>>    traffic classes varies significantly depending on the 
>>    source/destination POPs. 
>>     
>>    With existing TE mechanisms, the proportion of traffic from each 
>>    class on a given link will vary depending on multiple factors 
>>    including: 
>>    - in which order the different TE-LSPs are routed 
>>    - the preemption priority associated with the different TE-LSPs 
>>    - link/node failure situations  
>>     
>>    This may make it difficult or impossible for the network 
>>    administrator to configure the Diff-Serv PHBs (e.g. queue bandwidth) 
>>    to ensure that each traffic class gets the appropriate treatment. 
>>    This leads again to the requirement for DS-TE to be able to enforce 
>>    a different bandwidth constraint for different classes of traffic. 
>>    This could be used to ensure that, regardless of the order in which 
>>    tunnels are routed, regardless of their preemption priority and 
>>    regardless of the failure situation, the amount of traffic of each 
>>    class routed over a link matches the Diff-Serv scheduler 
>>    configuration on that link for the corresponding class (e.g. queue 
>>    bandwidth). 
>>     
>>    As an illustration of how DS-TE would address this scenario, the 
>>    network administrator may configure the service rate of Diff-Serv 
>>    queues to (45%,35%,20%) for classes (1,2,3) respectively. The 
>>    administrator would then split the traffic into separate Traffic 
>>    Trunks for each class and associate a bandwidth to each LSP 
>>    transporting those Traffic Trunks. The network administrator may 
>>    also want to configure preemption priorities of each LSP in order to 
>>    give highest restoration priority to the highest priority class and 
>>    medium priority to the medium class. Then DS-TE could ensure that 
>>    after a failure, class 1 traffic would be rerouted with first access 
>>  
>>  Le Faucheur et. al                                                  6 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    at link capacity but without exceeding its service rate of 45% of 
>>    the link bandwidth. Class 2 traffic would be rerouted with second 
>>    access at the link capacity but without exceeding its allotment. 
>> 
>>    Note that where class 3 is the Best-Effort service, the requirement 
>>    on DS-TE may be to ensure that the total amount of traffic routed 
>>    across all classes does not exceed the total link capacity of 100% 
>>    (as opposed to separately limiting the amount of Best Effort traffic 
>>    to 20 even if there was little class 1 and class 2 traffic). 
>> 
>>    In this scenario, DS-TE allowed for the maintenance of a more steady 
>>    distribution of classes, even during rerouting. This relied on the 
>>    required capability of DS-TE to adjust the amount of traffic of each 
>>    class routed on a link based on the configuration of the scheduler 
>>    and the amount of bandwidth available for each class. 
>>     
>>    Alternatively, some network administrators may want to solve the 
>>    problem by having the scheduler dynamically adjusted based on the 
>>    amount of bandwidth of the LSPs admitted for each class. This is an 
>>    additional requirement on DS-TE. 
>>     
>> 3.3.    Scenario 3: Guaranteed Bandwidth Services 
>>     
>>    In addition to the Best effort service, an IP/MPLS network operator 
>>    may desire to offer a point-to-point "guaranteed bandwidth" service 
>>    whereby the provider pledges to provide a given level of performance 
>>    (bandwidth/delay/loss...) end-to-end through its network from an 
>>    ingress port to and egress port.  The goal is to ensure all 
>>    "guaranteed" traffic within a subscribed traffic contract, will be 
>>    delivered within stated tolerances.   
>>     
>>    One approach for deploying such "guaranteed" service involves: 
>>    - dedicating a Diff-Serv PHB (or a Diff-Serv PSC as defined in 
>>      [DIFF-NEW]) to the "guaranteed" traffic 
>>    - policing guaranteed traffic on ingress against the traffic 
>>      contract and marking the "guaranteed" packets with the 
>>      corresponding DSCP/EXP value 
>>     
>>    Where very high level of performance is targeted for the 
>>    "guaranteed" service, it may be necessary to ensure that the amount 
>>    of "guaranteed" traffic remains below a given percentage of link 
>>    capacity on every link. Where the proportion of "guaranteed" traffic 
>>    is high, constraint based routing can be used to enforce such a 
>>    constraint.  
>>     
>>    However, the network operator may also want to simultaneously 
>>    perform Traffic Engineering of the rest of the traffic (i.e. non-
>>    guaranteed traffic) which would require that constraint based 
>>    routing is also capable of enforcing a different bandwidth 
>>    constraint, which would be less stringent than the one for 
>>    guaranteed traffic. 
>>     
>> 
>>  
>>  Le Faucheur et. al                                                  7 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    Again, this combination of requirements can not be addressed with 
>>    existing TE mechanisms. DS-TE mechanisms allowing enforcement of a 
>>    different bandwidth constraint for guaranteed traffic and for non-
>>    guaranteed traffic are required. 
>>     
>>     
>> 4.      Detailed Requirements for DS-TE 
>>     
>>    This section specifies the functionality that the above scenarios 
>>    require out of DS-TE implementations. Actual technical protocol 
>>    mechanisms and procedures to achieve such functionality are outside 
>>    the scope of this document. 
>>  
>> 4.1.    DS-TE Compatibility 
>>  
>>    While DS-TE is required in a number of situations such as the ones 
>>    described above, it is important to keep in mind that using DS-TE 
>>    may impact scalability (as discussed later in this document) and 
>>    operational practices. DS-TE should only be used when existing TE 
>>    mechanisms combined with Diff-Serv cannot address the network design 
>>    requirements.
>> 
>> @@@ can these cases be described in any general way? That would
>> @@@ seem to be useful (as useful as making the statement in the
>> @@@ first place).
>> 
>>    Many network operators may choose to not use DS-TE, or 
>>    to only use it in a limited scope within their network.  
>>     
>>    Thus, the DS-TE solution must be developed in such a way that: 
>>      
>>     (i)    it raises no interoperability issues with existing deployed 
>>            TE mechanisms.  
>>     (ii)   it allows DS-TE deployment to the required level of 
>>            granularity and scope (e.g. only in a subset of the 
>>            topology, or only for the number of classes required in the 
>>            considered network) 
>> 
>> 4.2.    Class-Types 
>>     
>>    The fundamental requirement for DS-TE is to be able to enforce 
>>    different bandwidth constraints for different sets of Traffic 
>>    Trunks. 
>>     
>>    [TEWG-FW] introduces the concept of Class-Types when discussing 
>>    operations of MPLS Traffic Engineering in a Diff-Serv environment.  
>>     
>>    We refine this definition into the following: 
>>     
>>            Class-Type (CT): the set of Traffic Trunks crossing a link, 
>>            that is governed by  a specific set of Bandwidth 
>>            constraints. CT is used for the purposes of link bandwidth 
>>            allocation, constraint based routing and admission control. 
>>            A given Traffic Trunk belongs to the same CT on all links. 
>>  
>>    Note that different LSPs transporting Traffic Trunks from the same 
>>    CT may be using the same or different preemption priorities as 
>>    explained in more details in section 3.4 below. 
>>  
>>  Le Faucheur et. al                                                  8 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>     
>>    Mapping of {TA}PSC to Class-Types is flexible. Different {TA}PSC can 
>>    be mapped to different CTs, multiple {TA}PSC can be mapped to the 
>>    same CT and one {TA}PSC can be mapped to multiple CTs. 
>>     
>>    For illustration purposes, let's consider the case of a network 
>>    running 4 Diff-Serv classes of services respectively based on the EF 
>>    PHB [EF], the AF1x PSC [AF], the AF2x PSC and the Default (i.e. 
>>    Best-Effort) PHB [DIFF-FIELD]. The network administrator may decide 
>>    to deploy DS-TE in the following way: 
>>         o from every DS-TE Head-end to every DS-TE Tail-end, split 
>>           traffic into 4 Traffic Trunks: one for traffic of each Diff-
>>           Serv class 
>>         o because the QoS objectives for the AF1x Traffic Trunks and 
>>           for the AF2x Traffic Trunks may be of similar nature (e.g. 
>>           both targeting low loss albeit at different levels perhaps), 
>>           the same (set of) Bandwidth Constraint(s) may be applied 
>>           collectively over the AF1x Traffic Trunks and the AF2x 
>>           Traffic Trunks. Thus, the network administrator may only 
>>           define three CTs: one for the EF Traffic Trunks, one for the 
>>           AF1x and AF2x Traffic Trunks and one for the Best Effort 
>>           Traffic Trunks. 
>>     
>>    As another example of mapping of {TA}PSC to CTs, a network operator 
>>    may split the EF traffic into two different sets of traffic trunks, 
>>    so that each set of traffic trunks is subject to different 
>>    constraints on the bandwidth it can access. In this case, two 
>>    distinct CTs are defined for EF: one for the EF traffic subject to 
>>    the first (set of) bandwidth constraint(s), the other for the EF 
>>    traffic subject to the second (set of) bandwidth constraint(s). 
>>     
>>    DS-TE must support at least 2 CTs and up to 8 CTs. Those are 
>>    referred to as CTc, 0 <= c <= MaxCT-1 = 7. 
>>     
>>    In a given network, DS-TE must not require the network administrator 
>>    to always deploy the maximum number of CTs. The network 
>>    administrator must be able to deploy only the number of CTs actually 
>>    utilized. 
>>     
>> 4.3.    Bandwidth Constraints 
>>     
>>    We refer to a Bandwidth Constraint Model as the set of rules 
>>    defining: 
>>    - the maximum number of Bandwidth Constraints; and 
>>    - which CTs each Bandwidth Constraint applies to and how. 
>>     
>>    By definition of CT, each CT is assigned either a Bandwidth 
>>    Constraint, or a set of Bandwidth Constraints. 
>>     
>>    We refer to the Bandwidth Constraints as BCb, 0 <= b <= MaxBC-1   
>>     
>> 
>>  
>>  Le Faucheur et. al                                                  9 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    Different models of Bandwidth Constraints are conceivable for 
>>    control of the CTs. 
>>     
>>    For example, a model with one separate Bandwidth Constraint per CT 
>>    could be defined. This model is defined by: 
>>    - MaxBC= MaxCT 
>>    - All LSPs supporting Traffic Trunks from CTc use no more than BCc 
>>     
>>    For illustration purposes, on a link of 100 unit of bandwidth where 
>>    three CTs are used, the network administrator might then configure 
>>    BC0=30, BC1= 50, BC2=20 such that: 
>>    - All LSPs supporting Traffic Trunks from CT0 use no more than 30 
>>      (e.g. Voice <= 30) 
>>    - All LSPs supporting Traffic Trunks from CT1 use no more than 50 
>>      (e.g. Premium Data <= 50) 
>>    - All LSPs supporting Traffic Trunks from CT2 use no more than 20 
>>      (e.g. Best Effort <= 20) 
>>     
>>    As another example, a "Russian Doll" model of Bandwidth Constraints 
>>    may be defined whereby: 
>>    - MaxBC= MaxCT 
>>    - All LSPs supporting Traffic Trunks from CTc (with b<=c<=7) use no 
>>      more than BCb 
>>     
>>    For illustration purposes, on a link of 100 units of bandwidth where 
>>    three CTs are used, the network administrator might then configure 
>>    BC0=100, BC1= 80, BC2=60 such that: 
>>    - All LSPs supporting Traffic Trunks from CT2 use no more than 60 
>>      (e.g. Voice <= 60) 
>>    - All LSPs supporting Traffic Trunks from CT1 or CT2 use no more 
>>      than 80 (e.g. Voice + Premium Data <= 80) 
>>    - All LSPs supporting Traffic Trunks from CT0 or CT1 or CT2 use no 
>>      more than 100 (e.g. Voice + Premium Data + Best Effort <= 100). 
>>     
>>    Other Bandwidth Constraints model can also be conceived. Those could 
>>    involve arbitrary relationships between BCb and CTc. Those could 
>>    also involve additional concepts such as associating minimum 
>>    reservable bandwidth to a CT. 
>>     
>>    At the time of writing this document, it is not clear whether a 
>>    single model of Bandwidth Constraints is sufficient, which one it 
>>    should be and how flexible this model really needs to be and what 
>>    are the implications on the DS-TE technical solution and its 
>>    implementations.  Work is currently in progress to investigate the 
>>    performance and trade-offs of different operational aspects of 
>>    Bandwidth Constraints models.
>> 
>> @@@ can these tradeoffs (and additionaly, complexity tradeoffs)
>> @@@ be quantified in any way? I would imagine that this would 
>> @@@ be useful for anyone wanting to deploy this technology?
>> 
>>    The DS-TE technical solution must specify one default
>>    bandwidth constraint model which must be supported by any
>>    DS-TE implementation. However, additional bandwidth  
>>    constraint models may also be specified. The purpose of such a 
>>    default model is to ensure that there is at least one common 
>>    Bandwidth Constraints model implementation across various vendors 
>>    equipment and allows for easier deployment of DS-TE. However, this 
>>  
>>  Le Faucheur et. al                                                 10 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    does not preclude a network operator to activate different Bandwidth 
>>    Constraints models on different links in a network, if he/she wishes 
>>    to do so. 
>>     
>>    In the selection of a default model, at least the following criteria 
>>    are expected to be considered: 
>>    (1) addresses the scenarios in Section 2 
>>    (2) works well under both normal and overload conditions 
>>    (3) applies equally when preemption is either enabled or disabled 
>>    (4) minimizes signaling load processing requirements 
>>    (5) maximizes efficient use of the network 
>> 
>> @@@ (6) Minimizes implementation and deployment complexity?
>>     
>>    In selection criteria (2), "normal condition" means that the network 
>>    is attempting to establish a volume of DS-TE LSPs for which it is 
>>    designed; "overload condition" means that the network is attempting 
>>    to establish a volume of DS-TE LSPs beyond the one it is designed 
>>    for; "works well" means that under these conditions, the network 
>>    should be able to sustain the expected performance, e.g., under 
>>    overload it is x times worse than its normal performance [BC-MODEL]. 
>>     
>>    These selection criteria will be further discussed and refined as 
>>    part of the ongoing work on BC model selection. In particular, the 
>>    applicability of criterion (5) needs to be qualified. 
>>     
>>    Regardless of the Bandwidth Constraint Model, the DS-TE solution 
>>    must allow support for up to 8 BCs. 
>>     
>> 4.4.    Preemption and TE-Classes 
>>     
>>    [TEWG-FW] defines the notion of preemption and preemption priority. 
>>    DS-TE must retain full support of such preemption. However, a 
>>    network administrator preferring not to use preemption for user 
>>    traffic should be able to disable the preemption mechanisms 
>>    described below. 
>>     
>>    The preemption attributes defined in [TE-REQ] must be retained and  
>>    applicable across all Class Types. The preemption attributes of 
>>    setup priority and holding priority must retain existing semantics, 
>>    and in particular these semantics must not be affected by the 
>>    Ordered Aggregate transported by the LSP or by the LSP's Class Type. 
>>    This means that if LSP1 contends with LSP2 for resources, LSP1 may 
>>    preempt LSP2 if LSP1 has a higher set-up preemption priority (i.e. 
>>    lower numerical priority value) than LSP2's holding preemption 
>>    priority regardless of LSP1's OA/CT and LSP2's OA/CT. 
>>     
>>    We introduce the following definition: 
>>     
>>        TE-Class: A pair of: 
>>                (i)    a Class-Type 
>>                (ii)   a preemption priority allowed for that Class-
>>                       Type. This means that an LSP transporting a 
>>                       Traffic Trunk from that Class-Type can use that 
>>  
>>  Le Faucheur et. al                                                 11 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>                       preemption priority as the set-up priority, as 
>>                       the holding priority or both. 
>>     
>>    Note that by definition: 
>>    - for a given Class-Type, there may be one or multiple TE-classes 
>>      using that Class-Type, each using a different preemption priority 
>>    - for a given preemption priority, there may be one or multiple TE-
>>      Class(es) using that preemption priority, each using a different 
>>      Class-Type. 
>>     
>>    DS-TE must allow all LSPs transporting Traffic Trunks of a given 
>>    Class-Type to use the same preemption priority. In other words, DS-
>>    TE must allow a Class-Type to be used by single TE-Class. This 
>>    effectively allows the network administrator to ensure that no 
>>    preemption happens within that Class-Type, when so desired. 
>>     
>>    As an example, the DS-TE solution must allow the network 
>>    administrator to define a Class-Type comprising a single TE-class 
>>    using preemption 0. 
>>     
>>    DS-TE must allow two LSPs transporting Traffic Trunks of the same 
>>    Class-Type to use different preemption priorities, and allow the LSP 
>>    with higher (numerically lower) set-up priority to preempt the LSP 
>>    with lower (numerically higher) holding priority when they contend 
>>    for resources. In other words, DS-TE must allow multiple TE-Classes 
>>    to be defined for a given Class-Type. This effectively allows the 
>>    network administrator to enable preemption within a Class-Type, when 
>>    so desired. 
>>     
>>    As an example, the DS-TE solution must allow the network 
>>    administrator to define a Class-Type comprising three TE-Classes; 
>>    one using preemption 0, one using preemption 1 and one using 
>>    preemption 4. 
>>     
>>    DS-TE must allow two LSPs transporting Traffic Trunks from different 
>>    Class-Types to use different preemption priorities, and allow the 
>>    LSP with higher setup priority to preempt the one with lower holding 
>>    priority when they contend for resources.  
>>     
>>    As an example, the DS-TE solution must allow the network 
>>    administrator to define two Class-Types (CT0 and CT1) each 
>>    comprising two TE-Classes where say: 
>>       -one TE-Class groups CT0 and preemption 0 
>>       -one TE-Class groups CT0 and preemption 2 
>>       -one TE-Class groups CT1 and preemption 1 
>>       -one TE-Class groups CT1 and preemption 3 
>>     
>>    The network administrator would then, in particular, be able to : 
>>    - transport a CT0 Traffic Trunk over an LSP with setup priority=0 
>>      and holding priority=0 
>>    - transport a CT0 Traffic Trunk over an LSP with setup priority=2 
>>      and holding priority=0 
>>  
>>  Le Faucheur et. al                                                 12 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    - transport a CT1 Traffic Trunk over an LSP with setup priority=1 
>>      and holding priority=1 
>>    - transport a CT1 Traffic Trunk over an LSP with setup priority=3 
>>      and holding priority=1. 
>>     
>>    The network administrator would then, in particular, NOT be able  
>>    to : 
>>    - transport a CT0 Traffic Trunk over an LSP with setup priority=1 
>>      and holding priority=1 
>>    - transport a CT1 Traffic Trunk over an LSP with setup priority=0 
>>      and holding priority=0 
>>     
>>    DS-TE must allow two LSPs transporting Traffic Trunks from different 
>>    Class-Types to use the same preemption priority. In other words, the 
>>    DS-TE solution must allow TE-classes using different CTs to use the 
>>    same preemption priority. This effectively allows the network 
>>    administrator to ensure that no preemption happens across Class-
>>    Types, if so desired. 
>>     
>>    As an example, the DS-TE solution must allow the network 
>>    administrator to define three Class-Types (CT0, CT1 and CT2) each 
>>    comprising one TE-Class which uses preemption 0. In that case, no 
>>    preemption will ever occur. 
>>     
>>    Since there are 8 preemption priorities and up to 8 Class-Types, 
>>    there could theoretically be up to 64 TE-Classes in a network. This 
>>    is felt to be beyond current practical requirements. The current 
>>    practical requirement is that the DS-TE solution must allow support 
>>    for up to 8 TE-classes. The DS-TE solution must allow these TE-
>>    classes to comprise any arbitrary subset of 8 (or less) from the 
>>    (64) possible combinations of (8) Class-Types and (8) preemption 
>>    priorities. 
>> 
>> @@@ what are these numbers based on (what does "current practical
>> @@@ requirements" mean)? 
>> 
>>    As with existing TE, an LSP which gets preempted is torn down at 
>>    preemption time. The Head-end of the preempted LSP may then attempt 
>>    to reestablish that LSP, which involves recomputing a path by 
>>    Constraint Based Routing based on updated available bandwidth 
>>    information and then signaling for LSP establishment along the new 
>>    path. It must be noted that there may be cases where the preempted 
>>    LSP cannot be reestablished (e.g. no possible path satisfying LSP 
>>    bandwidth constraints as well as other constraints). In such cases, 
>>    the Head-end behavior is left to implementation. It may involve 
>>    periodic attempts at reestablishing the LSP, relaxing of the LSP 
>>    constraints, or other behaviors.  
>>     
>> 4.5.    Mapping of Traffic to LSPs 
>>     
>>    The DS-TE solution must allow operation over E-LSPs onto which a 
>>    single <FEC/{TA}PSC> is transported. 
>>     
>>    The DS-TE solution must allow operation over L-LSPs. 
>>     
>>  
>>  Le Faucheur et. al                                                 13 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    The DS-TE solution may allow operation over E-LSPs onto which 
>>    multiple <FEC/{TA}PSC> of a given FEC are transported, under the 
>>    condition that those multiple <FEC/{TA}PSC> can effectively be 
>>    treated by DS-TE as a single atomic traffic trunk (in particular 
>>    this means that those multiple <FEC/{TA}PSC> are routed as a whole 
>>    based on a single collective bandwidth requirement, a single 
>>    affinity attribute, a single preemption level, a single Class-Type, 
>>    ...). In that case, it is also assumed that the multiple {TA}PSCs 
>>    are grouped together in a consistent manner throughout the DS-TE 
>>    domain (e.g. if <FECx/{TA}PSC1> and <FECx/{TA}PSC2> are transported 
>>    together on an E-LSP, then there will not be any L-LSP transporting 
>>    <FECy/{TA}PSC1> or <FECy/{TA}PSC2> on its own, and there will not be 
>>    any E-LSP transporting <FECz/{TA}PSC1> and/or <FECz/{TA}PSC2> with 
>>    <FECz/{TA}PSC3>). 
>>     
>> 4.6.    Dynamic Adjustment of Diff-Serv PHBs 
>>     
>>    As discussed in section 2.2, DS-TE may support adjustment of Diff-
>>    Serv PHBs parameters (e.g. queue bandwidth) based on the amount of 
>>    TE-LSPs established for each OA/Class-Type. Such dynamic adjustment 
>>    is optional. It is a local matter to the LSR and as such is outside 
>>    the scope of this specification. 
>>     
>>    Where this dynamic adjustment is supported, it must allow for 
>>    disabling via configuration (thus reverting to PHB treatment with 
>>    static scheduler configuration independent of DS-TE operations). It 
>>    may involve a number of configurable parameters which are outside 
>>    the scope of this specification. Those may include configurable 
>>    parameters controlling how scheduling resources (e.g. service rates) 
>>    need to be apportioned across multiple OAs when those belong to the 
>>    same Class-Type and are transported together on the same E-LSP. 
>>     
>>    The dynamic adjustment must take account of the performance 
>>    requirements of each class when computing required adjustments. 
>>  
>> 4.7.    Overbooking 
>>     
>>    Existing TE mechanisms allow overbooking to be applied on LSPs for 
>>    Constraint Based Routing and admission control. Historically this 
>>    has been achieved in TE deployment through factoring overbooking 
>>    ratios at the time of sizing the LSP bandwidth and/or at the time of 
>>    configuring the Maximum Reservable Bandwidth on links. 
>>     
>>    DS-TE must also allow overbooking and must effectively allow 
>>    different overbooking ratios to be enforced for different CTs. 
>>     
>>    DS-TE should optionally allow the effective overbooking ratio of a 
>>    given CT to be tweaked differently in different parts of the 
>>    network. 
>>     
>> 4.8.    Restoration 
>>     
>>  
>>  Le Faucheur et. al                                                 14 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>    With existing TE, restoration policies use standard priority 
>>    mechanisms such as, for example, the preemption priority to 
>>    effectively control the order/importance of LSPs for restoration 
>>    purposes. 
>>     
>>    DS-TE must ensure that similar application of the  use of standard 
>>    priority mechanisms for implementation of restoration policy are not 
>>    prevented since those are expected to be required for achieving the 
>>    survivability requirements of DS-TE networks. 
>>     
>>    Further discussion of restoration requirements are presented in the 
>>    output document of the TEWG Requirements Design Team [SURVIV-REQ]. 
>>     
>>     
>> 5.      Solution Evaluation Criteria 
>>     
>>    A range of solutions is possible for the support of the DS-TE 
>>    requirements discussed above. For example, some solutions may 
>>    require that all current TE protocols syntax (IGP, RSVP-TE, CR-LDP) 
>>    be extended in various ways.  For instance, current TE protocols 
>>    could be modified to support multiple bandwidth constraints rather 
>>    than the existing single aggregate bandwidth constraint. 
>>    Alternatively, other solutions may keep the existing TE protocols 
>>    syntax unchanged but modify their semantic to allow for the multiple 
>>    bandwidth constraints.  
>>     
>>    This section identifies the evaluation criteria that should be used 
>>    to assess potential DS-TE solutions for selection. 
>>     
>> 5.1.    Satisfying detailed requirements 
>>     
>>    The solution must address all the scenarios described in section 2 
>>    and satisfy all the requirements listed in section 3. 
>>     
>> 5.2.    Flexibility 
>>  
>>         -      number of Class Types that can be supported, compared to 
>>                number identified in Requirements section 
>>         -      number of Classes within a Class-Type 
>>     
>>     
>> 5.3.    Extendibility 
>>  
>>         -      how far can the solution be extended in the future if 
>>                requirements for more Class-Types are  identified in the 
>>                future.  
>>     
>> 5.4.    Scalability 
>>  
>>         -      impact on network scalability in what is propagated, 
>>                processed, stored and computed (IGP signaling, IGP 
>>                processing, IGP database, TE-Tunnel signaling ,...). 
>>  
>>  Le Faucheur et. al                                                 15 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>         -      how does scalability impact evolve with number of Class-
>>                Types/Classes actually deployed in a network. In 
>>                particular, is it possible to keep overhead small for a 
>>                large networks which only use a small number of Class-
>>                Types/Classes, while allowing higher number of Class-
>>                Types/Classes in smaller networks which can bear higher 
>>                overhead) 
>>     
>> 5.5.    Backward compatibility/Migration 
>>  
>>         -      backward compatibility/migration with/from existing TE 
>>                mechanisms 
>>         -      backward compatibility/migration when 
>>                increasing/decreasing the number of Class-Types actually 
>>                deployed in a given network. 
>>     
>> @@@ I guess Scalability (5.4) is a metric of complexity, but I'd
>> @@@ like to see something more specific, e.g. "Minimizes <foo>"
>> @@@ etc
>> 
>> 6.      Security Considerations 
>>     
>>    The solution developed to address the requirements defined in this 
>>    document must address security aspects. DS-TE is not expected to add 
>>                                                     ^^^^^^^^^^^^^^^^^^^
>>    specific security requirements beyond those of Diff-Serv and 
>>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>    existing TE.
>> 
>> @@@ I would venture to guess that no one tries to "add specific
>> @@@ security requirements". That's why we have this section...
>> 
>>    Networks which employ Diff-Serv techniques might offer 
>>    some protection between classes for denial of service attacks.  
>>    Though depending on how the technology is employed, it is possible 
>>    for some (lower scheduled) traffic to be more susceptible to traffic 
>>    anomalies (which include denial of service attacks) occurring within 
>>    other (higher scheduled) classes. 
>> 
>> @@@ indeed
>> 
>>     
>> 7.      Acknowledgemnt 
>>     
>>    We thank David Allen for his help in aligning with up-to-date  
>>    Diff-Serv terminology. 
>>     
>>     
>> 8.      Normative References 
>>     
>>     
>>    [AF] Heinanen, J et al., "Assured Forwarding PHB Group", RFC2597 
>>      
>>    [DIFF-ARCH] Blake et al., "An Architecture for Differentiated 
>>    Services", RFC2475. 
>>     
>>    [DIFF-MPLS] Le Faucheur et al, "Multi-Protocol Label Switching 
>>    (MPLS) Support of Differentiated Services", RFC3270, May 2002. 
>>     
>>    [DIFF-NEW] Grossman, " New Terminology and Clarifications for 
>>    Diffserv ", RFC3260, April 2002. 
>>     
>>    [EF] Davie et al., "An Expedited Forwarding PHB (Per-Hop Behavior)", 
>>    RFC3246, March 2002. 
>>  
>>  Le Faucheur et. al                                                 16 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>     
>>    [TEWG-FW] Awduche et al, Overview and Principles of Internet Traffic 
>>    Engineering, RFC3272, May 2002.  
>>     
>>    [TE-REQ] Awduche et al, Requirements for Traffic Engineering over 
>>    MPLS, RFC2702, September 1999. 
>>     
>>     
>> 9.      Informative References 
>>     
>>    [CR-LDP] Jamoussi et al., "Constraint-Based LSP Setup using LDP", 
>>    RFC3212, January 2002 
>>     
>>     
>>    [DIFF-FIELD] Nichols et al., "Definition of the Differentiated 
>>    Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC2474. 
>>     
>>    [DIFF-PDB] Nichols et al., "Definition of Differentiated Services 
>>    Per Domain Behaviors and Rules for their Specification", RFC3086. 
>>      
>>    [ISIS-TE] Smit, Li, IS-IS extensions for Traffic Engineering, draft-
>>    ietf-isis-traffic-04.txt, August 2001. 
>>     
>>    [OSPF-TE] Katz, Yeung, Traffic Engineering Extensions to OSPF, 
>>    draft-katz-yeung-ospf-traffic-06.txt, October 2001.  
>>     
>>    [RSVP-TE] Awduche et al, "RSVP-TE: Extensions to RSVP for LSP 
>>    Tunnels", RFC 3209, December 2001. 
>>     
>>    [SURVIV-REQ] W.S. Lai, D. McDysan, J. Boyle, M. Carlzon, R. Coltun, 
>>    T, Griffin, E. Kern, and T. Reddington, "Network Hierarchy and 
>>    Multilayer Survivability," work in progress, October 2001. 
>>     
>>     
>> 10.     Editors' Address: 
>>     
>>    Francois Le Faucheur 
>>    Cisco Systems, Inc. 
>>    Village d'Entreprise Green Side - Batiment T3 
>>    400, Avenue de Roumanille 
>>    06410 Biot-Sophia Antipolis, France 
>>    Phone: +33 4 97 23 26 19 
>>    Email: flefauch@cisco.com 
>>     
>>    Wai Sum Lai 
>>    AT&T Labs 
>>    200 Laurel Avenue 
>>    Middletown, New Jersey 07748, USA 
>>    Phone: (732) 420-3712 
>>    Email: wlai@att.com 
>>     
>>     
>>  
>>  Le Faucheur et. al                                                 17 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>          Requirements for Diff-Serv-aware Traffic Engineering Sep 2002 
>>  
>>     
>>     
>>     
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>>  Le Faucheur et. al                                                 18 
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 



From owner-te-wg@ops.ietf.org  Tue Jan 21 11:07:20 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03735
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 11:07:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b0wK-0004wm-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 08:07:52 -0800
Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b0wH-0004w5-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 08:07:49 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LG7Fg10144
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 11:07:15 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ26720R>; Tue, 21 Jan 2003 17:07:14 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BADFBB@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 17:06:49 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=0.0 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02,
	      THE_FOLLOWING_FORM
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Inline

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: dinsdag 21 januari 2003 14:54
> To: Wijnen, Bert (Bert)
> Cc: Tewg (E-mail)
> Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
> 
> 
> Hello Bert,
> 
> >> -----Original Message-----
> >> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
> >> Sent: 21 January 2003 10:42
> >> To: Francois Le Faucheur (flefauch); Tewg (E-mail)
> >> Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
> >> 
> >> 
> >> > Well, all the detailed requirements are grouped under section 
> >> > 4 and they
> >> > are all "marked" with a "must" (or "should/may"). Seems like a
> >> > reasonably clear way to present them.
> >> > There is some (non-requirement) text preceding the actual 
> >> requirements
> >> > to provide background/definition for the formulation of the 
> >> > requirement.
> >> > I think it is best to keep all that together so one can 
> >> understand the
> >> > requirements.
> >> > 
> >> > The reason we did not capitalise the "must/should/may" 
> is that this
> >> > document is going for Informational track so we were not sure
> >> > MUST/SHOULD/MAY were appropriate. Sounds like they are, 
> so we will
> >> > follow your suggestion and capitalize them.
> >> > 
> >> Mmmm.. take a look at RFC3216 sect 4 for example. I think 
> such a form
> >> makes it really clear as to what exactly the requirement 
> is and what
> >> type of requirement it is and what the motivation/explanation is.
> >> 
> 
> Yes, very neat. The structuring makes all of this very 
> obvious, and I'll
> certainly look at this as a good model for requirements documents.
> 
> But, while you cannot just have a quick look at the diff-te-reqts
> document and immediately count how many items are mandatory 
> and how many
> are optional, my impression is that when you read the various
> sub-sections of section "4 Detailed Requirements", it is reasonably
> clear whether something is background, example, mandatory 
> requirement or
> optional (It will be even clearer when capitalised). It is 
> not as neat,
> since you do have to read the whole text and couldn't easily fill-in
> "compliance statements" saying we meet items x,y,z and don't 
> meet items
> a,b,c;  But practically speaking it has proved quite appropriate for
> guiding us in developping the DS-TE protocol extensions (which are due
> for WG Last Call very shortly).
> 
> So, considering that the WG has been in agreement on the 
> actual content
> for a while, and that the corresponding protocol extensions based on
> this are ready for Last Call, I'm inclined towards the 
> approach of "not
> perfect, but does the job" and avoid significant editing changes just
> for easier identification of same content. This is all in the view of
> finalising that document asap, since it conditions all the DSTE work.
> 
You should also wonder: can people who need to evaluate your protocol
specs (which I guess will go also through IETF Last Call, they
are intended for stds track, are they not?) can easily check how you
do in terms of meeting the requirments.

> Is there any way you could live with the current structure (ie
> background/definition + requirement/MUST in same sub-section)?
>  
Although I think such a major editorial change would be VERY helpful
and useful, I can understand that you are a bit reluctant.

A simpler change could be in the following form (this is one example):
Take top of Page 12. It says:
   Note that by definition:
   - for a given Class-Type, there may be one or multiple TE-classes
     using that Class-Type, each using a different preemption priority
   - for a given preemption priority, there may be one or multiple TE-
     Class(es) using that preemption priority, each using a different
     Class-Type.

   DS-TE must allow all LSPs transporting Traffic Trunks of a given
   Class-Type to use the same preemption priority. In other words, DS-
   TE must allow a Class-Type to be used by single TE-Class. This
   effectively allows the network administrator to ensure that no
   preemption happens within that Class-Type, when so desired.

If you would change it to (assuming I have destilled the requirement
correctly):
   Note that by definition:
   - for a given Class-Type, there may be one or multiple TE-classes
     using that Class-Type, each using a different preemption priority
   - for a given preemption priority, there may be one or multiple TE-
     Class(es) using that preemption priority, each using a different
     Class-Type.

   MANDATORY REQUIREMENT: DS-TE must allow all LSPs transporting
   Traffic Trunks of a given Class-Type to use the same preemption
   priority. In other words, DS-TE must allow a Class-Type to be
   used by single TE-Class. This effectively allows the network
   administrator to ensure that no preemption happens within that
   Class-Type, when so desired.

So start each paragraph that actually is a short description of 
a requirement statement such that is is prefixed with the text
MANDATYORY REQUIRMENT: or OPTIONAL REQUIREMENT: as the case may be.
So they would still not be numberd (which makes referencing them much
easier) but at least they clearly stand out.

Maybe you could even do: MANDATORY REQUIREMENT nn:
where nn is a sequential number for each of the requirements, so 
they in fact CAN be easily referenced later.

Bert
> Thanks
> 
> Francois
> 
> >> I was not so much worried aboutMUST/SHOULD/MAY not being 
> capitalized.
> >> More that the explanantory text and the actual requirements and
> >> sometimes examples/scenario-text is all mixed. 
> >> 
> >> For example, could you easily tell me how many mandatoty and
> >> how many optional requirements there are?
> >> 
> >> Bert
> >> 
> 



From owner-te-wg@ops.ietf.org  Tue Jan 21 13:55: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 NAA08714
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 13:55:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b3Z2-000CMO-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 10:56:00 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b3Yy-000CLy-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 10:55:56 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0LIrgVc026371;
	Tue, 21 Jan 2003 19:53:50 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 21 Jan 2003 19:55:19 +0100
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: more review comments: draft-tewg-ietf-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 18:55:18 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E77F@xbe-lon-303.cisco.com>
Thread-Topic: more review comments: draft-tewg-ietf-diff-te-reqts-06.txt
Thread-Index: AcLBZ9gUYMQa7+gjSSSmcK71ICrZtAABXX2w
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 21 Jan 2003 18:55:19.0072 (UTC) FILETIME=[A48FC200:01C2C17E]
X-Spam-Status: No, hits=-0.3 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
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 NAA08714

Hi again Bert,

>> -----Original Message-----
>> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
>> Sent: 21 January 2003 17:07
>> To: Tewg (E-mail)
>> Subject: more review comments: draft-tewg-ietf-diff-te-reqts-06.txt
>> 
>> 
>> Again, sorry for late forwarding. This is the last one
>> I had to dig up.
>> 

That's good news. ^)

Thanks to David for these comments. Proposed resolution embedded:

>> Thanks,
>> Bert 
>> 
>> -----Original Message-----
>> From: David Meyer [mailto:dmm@sprint.net]
>> Sent: woensdag 6 november 2002 15:34
>> To: Randy Bush
>> Cc: ops directorate
>> Subject: Re: early peek at draft-tewg-ietf-diff-te-reqts-06.txt
>> 
>> 
>> One thing I forgot to mention is that any draft proposing a
>> service (or set of services) based on diff-serv should describe
>> in it's security section what kind of DoS vulnerabilities the
>> service might incur. 

We are already discussing security in the other thread. Since this is a
requirements document I assume we need to focus on the security
requirements here and that the DOS thing need to be discussed in the
DSTE solution. Anyway, see actual proposal in other email.

>> >> 1.      Introduction 
>> >>     
>> >> 1.1.    Problem Statement 
>> >>  
>> >>    Diff-Serv is becoming prominent in providing scalable network 
>> >>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >>    designs supporting multiple classes of services.  
>> >>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >> 
>> >> @@@ This is a marketing statement, as I know of at least one
>> >> @@@ provider who sees it differently
>> >> 

Can replace with:
"Diff-Serv is used by some Service Providers to achieve scalable network
designs supporting multiple classes of services."
 

>> >>    In some Diff-Serv networks where optimization of transmission 
>> >>    resources on a network-wide basis is not sought, MPLS Traffic 
>> >>    Engineering (TE) mechanisms may simply not be used.  
>> >>     
>> >>    In other networks, where optimization of transmission 
>> resources is 
>> >>    sought, Diff-Serv mechanisms [DIFF-MPLS] need to be 
>> complemented by 
>> >>    existing MPLS Traffic Engineering mechanisms [TE-REQ] 
>> [ISIS-TE] 
>> >>    [OSPF-TE] [RSVP-TE] [CR-LDP] which operate on an 
>> aggregate basis 
>> >>    across all Diff-Serv classes of service. In this case, 
>> Diff-Serv and 
>> >>    MPLS TE both provide their respective benefits.  
>> >> 
>> >> @@@ Again, what is meant in the above by "optimization" I presume
>> >> @@@ is CAPEX optimization (i.e., optimized utilization)? Even
>> >> @@@ that much doesn't seem to be supported.
>> >> 

As previously agreed "need to be" will be replaced by "may be". 

   
>> >>    This document focuses exclusively on the specific 
>> environments which 
>> >>    would benefit from DS-TE. Some examples include: 
>> >>     
>> >>      -    networks where bandwidth is scarce (e.g. 
>> transcontinental 
>> >>           networks) 
>> >> 
>> >> @@@ ?

Not sure what the issue is here.

>> >>    Another option is to split the different <FEC/{TA}PSC> 
>> of a given 
>> >>    FEC into multiple Traffic Trunks on the basis of the 
>> {TA}PSC. In 
>> >>    other words, traffic from a given node to another 
>> given node, is 
>> >>    split based on the classes of service, into multiple 
>> Traffic Trunks 
>> >>    which are transported over separate LSPs, which can 
>> potentially 
>> >>    follow a different path through the network. DS-TE 
>> precisely takes 
>> >>    advantage of this fact and indeed computes a separate 
>> path for each 
>> >>    LSP.
>> >> 
>> >> @@@ It would be nice if they quantified the complexity here. 

Scalability is discussed in section 5 as an evaluation criteria.
The DSTE solution contains a discussion on scalability impact on IGP,
signaling, path computation etc. 

>> >> @@@ In addition, the a discussion of the interaction with FRR
>> >> @@@ would be useful at this point.
>> >> 

No specific requirements was identified by SPs for DS-TE in terms of FRR
(primarily because FRR operations was seen as defined independently of
what gets transported on top of the tunnel). Any specific aspects of
interaction with FRR that would be worth detailing?


>> >>    In so doing, DS-TE can take into account the specific 
>> >>    requirements of the Traffic Trunk transported on each 
>> LSP (e.g. 
>> >>    bandwidth requirement, preemption priority). Moreover 
>> DS-TE can take 
>> >>    into account specific engineering constraints to be 
>> enforced for 
>> >>    these sets of Traffic Trunks (e.g. limit all Traffic Trunks 
>> >>    transporting a particular {TA}PSC to x% of link 
>> capacity). In brief, 
>> >>    DS-TE achieves per LSP constraint based routing with 
>> paths that 
>> >>    tightly match the specific objectives of the traffic 
>> forming the 
>> >>    ^^^^^^^
>> >> 
>> >> @@@ what is the defn of "tightly"?

Will replace "that tightly match" by "that better match".

 >> >> 3.1.    Scenario 1: Limiting Proportion of Classes on a Link 
>> >>     
>> >>    An IP/MPLS network may need to carry a significant 
>> amount of VoIP 
>> >>    traffic compared to its link capacity. For example, 10,000 
>> >>    uncompressed calls at 20ms packetization result in 
>> about 1Gbps of IP 
>> >>    traffic, which is significant on an OC-48c based 
>> network. In case of 
>> >>    topology changes such as link/node failure, VoIP 
>> traffic levels can 
>> >>    even approach the full bandwidth on certain links. 
>> >> 
>> >> @@@ this last sentence doesn't really make sense in the absence
>> >> @@@ of an understanding of the provider's network (like if I
>> >> @@@ protect all of my packets, the statement doesn't apply)

I assume the last line was meant to say "if I protect all my links"
(instead of "all my packets"). No?

Anyway, this is not trying to say that VoIP will approach link bandwidth
in every network. Just that it can happen in some networks in some
situations. Which reflects the concern of the SP who provided this text.
The description above starts with "For example". Statement seems valid
in the context of an example.

>> >>      
>> >>    For delay/jitter reasons it is undesirable to carry 
>> more than a 
>> >>    certain percentage of VoIP traffic on any link. 
>> >> 
>> >> @@@ but we understand that we can run in the region about 80%
>> >> @@@ utilization with small jitter and delay (with >= OC48). So
>> >> @@@ why is it undesirable? This seems statement seems to 
>> be unsupported.

I think the comment points out that the "certain percentage" may be as
high as 80% in some cases (eg high speed link, strict priority provided
to VoIP by scheduler without any rate limitation activated,...). It
doesn't seem to invalidate the fact that if you may encounter a very
high VoIP load on some links, you may want to control it to a certain
percentage below 100% (be it 80%). 
Also, while the fastest backbone links in many networks are OC48 and
above, lower speed links are also found in many networks where the
"certain percentage" may be lower. Also, scheduler might be configured
by SP with some rate limitation for the VoIP queue below 100% (for
policy purposes to keep bandwidth for some other traffic such as Premium
VPN).

But again, this was not meant to suggest that this is something you need
to do everywhere. Just that it makes sense in some environments and that
some SPs want to do it there.
 
So, to better reflect this, we will adjust the statement above into: 
"For delay/jitter reasons, some network administrators see it as
undesirable to carry more than a certain percentage of VoIP traffic on
any link. "

 
>> >>  
>> >> 4.1.    DS-TE Compatibility 
>> >>  
>> >>    While DS-TE is required in a number of situations such 
>> as the ones 
>> >>    described above, it is important to keep in mind that 
>> using DS-TE 
>> >>    may impact scalability (as discussed later in this 
>> document) and 
>> >>    operational practices. DS-TE should only be used when 
>> existing TE 
>> >>    mechanisms combined with Diff-Serv cannot address the 
>> network design 
>> >>    requirements.
>> >> 
>> >> @@@ can these cases be described in any general way? That would
>> >> @@@ seem to be useful (as useful as making the statement in the
>> >> @@@ first place).


Can update last sentence with:
"
DS-TE should only be used when existing TE mechanisms combined with
Diff-Serv cannot address the network design requirements (i.e. where
constraint based routing is required and where it needs to enforce
different bandwidth constraints for different classes of traffic, such
as in the scenarios described above in section 3). 
"

   
>> >>    At the time of writing this document, it is not clear 
>> whether a 
>> >>    single model of Bandwidth Constraints is sufficient, 
>> which one it 
>> >>    should be and how flexible this model really needs to 
>> be and what 
>> >>    are the implications on the DS-TE technical solution and its 
>> >>    implementations.  Work is currently in progress to 
>> investigate the 
>> >>    performance and trade-offs of different operational aspects of 
>> >>    Bandwidth Constraints models.
>> >> 
>> >> @@@ can these tradeoffs (and additionaly, complexity tradeoffs)
>> >> @@@ be quantified in any way? I would imagine that this would 
>> >> @@@ be useful for anyone wanting to deploy this technology?
>> >>

This has been discussed outside of the this document.
For example, see draft-wlai-tewg-bcmodel-00.txt for quantified
comparison.
 
     
>> >>    In the selection of a default model, at least the 
>> following criteria 
>> >>    are expected to be considered: 
>> >>    (1) addresses the scenarios in Section 2 
>> >>    (2) works well under both normal and overload conditions 
>> >>    (3) applies equally when preemption is either enabled 
>> or disabled 
>> >>    (4) minimizes signaling load processing requirements 
>> >>    (5) maximizes efficient use of the network 
>> >> 
>> >> @@@ (6) Minimizes implementation and deployment complexity?
>> >>

Agreed.
     
    
>> >>    Since there are 8 preemption priorities and up to 8 
>> Class-Types, 
>> >>    there could theoretically be up to 64 TE-Classes in a 
>> network. This 
>> >>    is felt to be beyond current practical requirements. 
>> The current 
>> >>    practical requirement is that the DS-TE solution must 
>> allow support 
>> >>    for up to 8 TE-classes. The DS-TE solution must allow these TE-
>> >>    classes to comprise any arbitrary subset of 8 (or 
>> less) from the 
>> >>    (64) possible combinations of (8) Class-Types and (8) 
>> preemption 
>> >>    priorities. 
>> >> 
>> >> @@@ what are these numbers based on (what does "current practical
>> >> @@@ requirements" mean)? 
>> >> 

"Current practical requirements" means based on what the SP co-authors
of that draft and others SPs from the TEWG are considering deploying in
the coming years. 
To give you a feel , in the case of number of CTs, some argued 3 CTs
were enough, others argued 4 CTs were enough, some argued they may use 5
or more, no one argued for more than 8. We settled for 8 since this
there were no scalability impact in a solution supporting 3,4 or 8.

>> >> @@@ I guess Scalability (5.4) is a metric of complexity, but I'd
>> >> @@@ like to see something more specific, e.g. "Minimizes <foo>"
>> >> @@@ etc

Section 5.4 already lists the specific aspects of scalability that we
want to be considered:
"IGP signaling, IGP processing, IGP database, TE-tunnel signaling"


>> >> 
>> >> 6.      Security Considerations 
>> >>     
>> >>    The solution developed to address the requirements 
>> defined in this 
>> >>    document must address security aspects. DS-TE is not 
>> expected to add 
>> >>                                                     
>> ^^^^^^^^^^^^^^^^^^^
>> >>    specific security requirements beyond those of Diff-Serv and 
>> >>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> >>    existing TE.
>> >> 
>> >> @@@ I would venture to guess that no one tries to "add specific
>> >> @@@ security requirements". That's why we have this section...
>> >> 

See above re security.

Cheers

Francois



From owner-te-wg@ops.ietf.org  Tue Jan 21 15:25:24 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11090
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 15:25:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b4yx-000GlH-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 12:26:51 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b4yu-000GkU-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 12:26:48 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LKQFJ16331
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 15:26:16 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ267M02>; Tue, 21 Jan 2003 21:26:07 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE011@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Jim Boyle <jboyle@pdnets.com>,
        "Ash, Gerald R (Jerry), ALABS"
	 <gash@att.com>
Cc: te-wg@ops.ietf.org
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Tue, 21 Jan 2003 21:25:13 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.4 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

I would contend that if we onlu have 9 reactions out of 1100
or so WG subscribers/members that there is NO WG consensus 
to work on this topic.

Thanks,
Bert 

> -----Original Message-----
> From: Jim Boyle [mailto:jboyle@pdnets.com]
> Sent: maandag 20 januari 2003 15:45
> To: Ash, Gerald R (Jerry), ALABS
> Cc: te-wg@ops.ietf.org
> Subject: Weak turnout : was-> A proposal for moving ahead on BC models
> 
> 
> 
> Hopefully for other calls we can get better turnout than 9 
> members out of 
> 1100.
> 
> 
> On Mon, 20 Jan 2003, Ash, Gerald R (Jerry), ALABS wrote:
> 
> > 1. my count is 6 to 3.
> > 2. a majority, yes, but a thin margin and small sample on 
> which to base this decision...
> > 
> > Jerry
> > 
> > -----Original Message-----
> > From: Jim Boyle [mailto:jboyle@pdnets.com]
> > Sent: Saturday, January 18, 2003 10:21 PM
> > To: te-wg@ops.ietf.org
> > Subject: Re: A proposal for moving ahead on BC models (conclusion?)
> > 
> > For the record, I think it best to specify a default model.
> > 
> > However, assuming Sanjay's second vote masks his first, and 
> including my 
> > vote above, that would leave us with 6 folks who think we 
> should pull the 
> > requirement for a default, specified model, and 2 who think 
> we should keep 
> > it.  That gives us a voter turn-out on our list of less than 1% ;-(
> > 
> > So we'll update the requirements document (currently with 
> IESG) to reflect 
> > no need for a required default BC model.
> > 
> > Jim
> > 
> > 
> 
> 



From owner-te-wg@ops.ietf.org  Tue Jan 21 15:25: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 PAA11104
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 15:25:54 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b4yR-000GkX-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 12:26:19 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b4yO-000GkK-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 12:26:16 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LKQDJ16294
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 15:26:14 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ267M0H>; Tue, 21 Jan 2003 21:26:07 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE012@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 21:25:14 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.4 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Inline
> Bert,
> 
> I removed all the items we agreed on. See below on the open ones:
> 
> >> > >> - sect 3.2 talks (two places) about "the order in which 
> >> > >>   tunnels are
> >> > >>   routed". What does that (ordering of tunnels) mean ?
> >> > 
> >> > Before being available, TE tunnels need to be established. This
> >> > establishment includes computing route for the tunnel 
> >> > and signaling
> >> > tunnel establishment (and thus reserving bandwidth). The 
> >> > order in which these tunnels are established/routed can greatly
> >> > affect which tunnels can grab bandwidth and which 
> >> > cannot, and thus
> >> > greatly affects the state of the final system. 
> >> > 
> >> OK, that explains it somewhat to me... but I cannot get that from
> >> the text in the I-D. Maybe add something about that.
> >> Or is it clear to all TE-WGers and is it just me?
> >> 
> 
> I would expect that to be clear to people who are familiar with the
> [TEWG-FW] and [TE-REQ] documents we included as Normative References.
> Still, we can replace:
>  "   - in which order the different TE-LSPs are routed"
> by
>  "   - in which order the different TE-LSPs are routed (since this
>        affects which TE-LSP can reserve bandwidth first)"
> 
I now see why I did not understand. When you say "TE-LSPs are routed"
then I think of "routing happens all the time for all packets".
From what you suggest to add, it sounds as if you mean that at the
time a TE-LSP is configured, that that is the time when bandwidth
is reserved. So I guess you mean
     - in which order the different TE-LSPs are configured
       (or established or created) 

Did I get that? If so, then my text if probably even better.

> 
> >> > >> - what are thelast 2 paragraphs on page 7 trying to say?
> >> > >>   sounds like blabla and handwaving to me, no?
> >> > 
> >> > They are trying to say something specific :
> >> > Some SPs would like to simultaneously:
> >> > 	- offer "Very High QoS Guaranteed Traffic" and "Normal Traffic"
> >> > 	- they want to do admission control of "Very High QoS Guaranteed
> >> > Traffic" to ensure it fits in the queue dedicated to that service
> >> > 	- they want to do regular TE of Normal traffic
> >> >
> >> How is "Very High QoS Guaranteed Traffic" defined? What 
> >> does it mean. What do you mean by "Normal Traffic" ??
> >>  
> 
> "Very High QoS" translates into different Service Level Specification
> (SLS) with different operators. That's a desired property of IP QoS.
> Here , we don't want to define it very precisely. The text just says
> that when supporting such "Guaranteed Bandwidth" service, "it may be
> necessary to ensure that ...".
> The practical thing behind is that indeed some SPs want to market SLS
> with very tight commitment and perform separate admission control of
> this traffic as one of the mechanisms to ensure the SLS.
> 
> In the document we don't actually use the term "Normal 
> Traffic". We just refer to "the rest of the traffic".
> 
OK, I give in

> >> > >> - Is most of the text in sect 4.2 on page 9 not just another 
> >> > >>   scenario that belongs in sect 3?
> >> > 
> >> > We tried to keep things simple in the scenarios (eg only 
> >> talked about
> >> > "classes of service"). The objectives of the scenarios 
> is to give a
> >> > simple-to-grab understanding of what SPs want to do.
> >> > In section 4.2 we are trying to describe the relationship 
> >> between CTs
> >> > and classes/PHBs. This requires more complex terminology 
> >> and mapping
> >> > examples. Also, in section 4.2 we are not describing what 
> >> application
> >> > the is trying to achieve, just how CTs may be "mapped".
> >> > 
> >> Section 4 I thought was to list the requirements.... 
> 
> Yes, the objective of section 4.2 is to list the requirements 
> related to
> Class-Types. But before we do so, we define exactly what CTs are and
> their relationship to relevant concepts. This is part of the 
> definitions
> necessary for formulating the related requirements.
> 
> >> I think it all boils down to the fact that it is really difficult
> >> to find exactly what the requirements are. It is too much 
> >> intermingled
> >> with other text (at least to my taste).
> >> 
> 
> You raised this in a separate email, so I'll follow that up there.
> 
And I responded there also

> >> > >> - May I assume that all TE-WG members understand the 
> >> notations used in 
> >> > >>   section 4.5 ?? Cause I would have to go and study in 
> >> detail if I
> >> > >>   want to get it.
> >> > 
> >> > A definition for these terms is actually provided in section "1.2
> >> > Definitions".
> >> > 
> >> I was not speaking about the definitions alone.
> >>
> 
> FEC, E-LSP and L-LSP are really well-known terms in MPLS land.
> TA and PSC are well-known in Diff-Serv land.
> The only new things are {TA}PSC and <FEC/{TA}PSC> which are defined in
> the definition section.
> So I think we can assume the notations are understood.
> We didn't get any concern even at Last Call.
>  
So can you tell me (I am thick, sorry) what means:
  - {TA}PSC
  - <FEC/{TA}/PSC>

Maybe once you explain it to me I will get it and maybe there is an Aha

> >> > My proposal would be to just keep the two first 
> sentences (ie DSTE
> >> > solution must address security. DS-TE not expected to add 
> >> new security
> >> > issues beyond those of Diff-Serv and TE) and get rid of 
> >> the rest since
> >> > we do not have to start discussing how security may be 
> >> achieved in the
> >> > Reqt document itself.
> >> > 
> >> The "not expected" does not sound right. It sounds as if 
> you have no
> >> real clue what security impacts/requirements these DS-TE 
> requirements
> >> bring to the table.
> >>
> 
> I see your point.
> I guess the "not expected" stems from the fact that we may have been
> trying to bundle two things (requirements vs mechanisms):
> 	- there is no identified specific security requirements for DSTE
> beyond those of TE and Diff-Serv
> 	- without assuming anything about DS-TE solution, we can't be
> quite sure that existing security mechanisms won't get broken 
> by DS-TE.
> 
> So how about breaking this up into something like :
> 
> "
> The solution developed to address the requirements defined in this
> document must address security aspects. DS-TE does not raise any
> specific additional security requirements beyond the existing security
> requirements of MPLS TE and Diff-Serv. The solution must 
> ensure that the
> existing security mechanisms of MPLS TE and Diff-Serv are not
> compromised by the solution protocol/procedure extensions or otherwise
> must provide security mechanisms to address this. 
> "
> 
That sounds much better to me. 

Pls check that you also addres the comments about DoS attacks as
reaided by David Meyer.

Bert
> Thanks 
> 
> Francois
> 



From owner-te-wg@ops.ietf.org  Tue Jan 21 16:58: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 QAA13264
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 16:58:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b6Q8-000Lgz-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 13:59:00 -0800
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b6Q4-000LgD-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 13:58:56 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0LLwO719761
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 16:58:25 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ267NVX>; Tue, 21 Jan 2003 22:58:23 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE017@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
Cc: "David Meyer (E-mail)" <dmm@sprint.net>
Subject: RE: more review comments: draft-tewg-ietf-diff-te-reqts-06.txt
Date: Tue, 21 Jan 2003 22:56:57 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

I am cc:-ing David Meyer so he can jump in if he feels
I am not properrly answering.

Inline
> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: dinsdag 21 januari 2003 19:55
> To: Wijnen, Bert (Bert); Tewg (E-mail)
> Subject: RE: more review comments: 
> draft-tewg-ietf-diff-te-reqts-06.txt
> 
> 
> Hi again Bert,
> 
> >> -----Original Message-----
> >> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
> >> Sent: 21 January 2003 17:07
> >> To: Tewg (E-mail)
> >> Subject: more review comments: draft-tewg-ietf-diff-te-reqts-06.txt
> >> 
> >> 
> >> Again, sorry for late forwarding. This is the last one
> >> I had to dig up.
> >> 
> 
> That's good news. ^)
> 
> Thanks to David for these comments. Proposed resolution embedded:
> 
> >> Thanks,
> >> Bert 
> >> 
> >> -----Original Message-----
> >> From: David Meyer [mailto:dmm@sprint.net]
> >> Sent: woensdag 6 november 2002 15:34
> >> To: Randy Bush
> >> Cc: ops directorate
> >> Subject: Re: early peek at draft-tewg-ietf-diff-te-reqts-06.txt
> >> 
> >> 
> >> One thing I forgot to mention is that any draft proposing a
> >> service (or set of services) based on diff-serv should describe
> >> in it's security section what kind of DoS vulnerabilities the
> >> service might incur. 
> 
> We are already discussing security in the other thread. Since this is a
> requirements document I assume we need to focus on the security
> requirements here and that the DOS thing need to be discussed in the
> DSTE solution. Anyway, see actual proposal in other email.
> 
Well, in my other email, I also proposed that you try to address this
isseu. If Dave suggests that he can immediately think of a few ways for
DoS attacks, then it seems appropriate to think them through and write
something about it. If nothing else, then at least list the fact that
any protocols that get developed need to pay specific attention to
ensure that DoS attackes are prevented as much as possible.

> >> >> 1.      Introduction 
> >> >>     
> >> >> 1.1.    Problem Statement 
> >> >>  
> >> >>    Diff-Serv is becoming prominent in providing 
> scalable network 
> >> >>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> >>    designs supporting multiple classes of services.  
> >> >>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> >> 
> >> >> @@@ This is a marketing statement, as I know of at least one
> >> >> @@@ provider who sees it differently
> >> >> 
> 
> Can replace with:
> "Diff-Serv is used by some Service Providers to achieve scalable network
> designs supporting multiple classes of services."
>  
Seems to be much better already.

> 
> >> >>    In some Diff-Serv networks where optimization of 
> transmission 
> >> >>    resources on a network-wide basis is not sought, 
> MPLS Traffic 
> >> >>    Engineering (TE) mechanisms may simply not be used.  
> >> >>     
> >> >>    In other networks, where optimization of transmission 
> >> resources is 
> >> >>    sought, Diff-Serv mechanisms [DIFF-MPLS] need to be 
> >> complemented by 
> >> >>    existing MPLS Traffic Engineering mechanisms [TE-REQ] 
> >> [ISIS-TE] 
> >> >>    [OSPF-TE] [RSVP-TE] [CR-LDP] which operate on an 
> >> aggregate basis 
> >> >>    across all Diff-Serv classes of service. In this case, 
> >> Diff-Serv and 
> >> >>    MPLS TE both provide their respective benefits.  
> >> >> 
> >> >> @@@ Again, what is meant in the above by "optimization" 
> I presume
> >> >> @@@ is CAPEX optimization (i.e., optimized utilization)? Even
> >> >> @@@ that much doesn't seem to be supported.
> >> >> 
> 
> As previously agreed "need to be" will be replaced by "may be". 
> 
Dave, does that address your issue enuf?

>    
> >> >>    This document focuses exclusively on the specific 
> >> environments which 
> >> >>    would benefit from DS-TE. Some examples include: 
> >> >>     
> >> >>      -    networks where bandwidth is scarce (e.g. 
> >> transcontinental 
> >> >>           networks) 
> >> >> 
> >> >> @@@ ?
> 
> Not sure what the issue is here.
> 
I think David means that he wonder if there is any such scarceness
of bandwidth across the atlantic. Is not the fact that there is
abundant bandwidth these days on of the reasons why we have such 
a bad downturn in the telecom world?

> >> >>    Another option is to split the different <FEC/{TA}PSC> 
> >> of a given 
> >> >>    FEC into multiple Traffic Trunks on the basis of the 
> >> {TA}PSC. In 
> >> >>    other words, traffic from a given node to another 
> >> given node, is 
> >> >>    split based on the classes of service, into multiple 
> >> Traffic Trunks 
> >> >>    which are transported over separate LSPs, which can 
> >> potentially 
> >> >>    follow a different path through the network. DS-TE 
> >> precisely takes 
> >> >>    advantage of this fact and indeed computes a separate 
> >> path for each 
> >> >>    LSP.
> >> >> 
> >> >> @@@ It would be nice if they quantified the complexity here. 
> 
> Scalability is discussed in section 5 as an evaluation criteria.
> The DSTE solution contains a discussion on scalability impact on IGP,
> signaling, path computation etc. 
> 
Dave? is that sufficient for you?

> >> >> @@@ In addition, the a discussion of the interaction with FRR
> >> >> @@@ would be useful at this point.
> >> >> 
> 
> No specific requirements was identified by SPs for DS-TE in terms of FRR
> (primarily because FRR operations was seen as defined independently of
> what gets transported on top of the tunnel). Any specific aspects of
> interaction with FRR that would be worth detailing?
> 
I will let Dave answer which aspects he would like to see.
If no specific aspects, then maybe you can add some of the text of
your answer above.

> 
> >> >>    In so doing, DS-TE can take into account the specific 
> >> >>    requirements of the Traffic Trunk transported on each 
> >> LSP (e.g. 
> >> >>    bandwidth requirement, preemption priority). Moreover 
> >> DS-TE can take 
> >> >>    into account specific engineering constraints to be 
> >> enforced for 
> >> >>    these sets of Traffic Trunks (e.g. limit all Traffic Trunks 
> >> >>    transporting a particular {TA}PSC to x% of link 
> >> capacity). In brief, 
> >> >>    DS-TE achieves per LSP constraint based routing with 
> >> paths that 
> >> >>    tightly match the specific objectives of the traffic 
> >> forming the 
> >> >>    ^^^^^^^
> >> >> 
> >> >> @@@ what is the defn of "tightly"?
> 
> Will replace "that tightly match" by "that better match".
> 
I would think that that is better understood.

>  >> >> 3.1.    Scenario 1: Limiting Proportion of Classes on a Link 
> >> >>     
> >> >>    An IP/MPLS network may need to carry a significant 
> >> amount of VoIP 
> >> >>    traffic compared to its link capacity. For example, 10,000 
> >> >>    uncompressed calls at 20ms packetization result in 
> >> about 1Gbps of IP 
> >> >>    traffic, which is significant on an OC-48c based 
> >> network. In case of 
> >> >>    topology changes such as link/node failure, VoIP 
> >> traffic levels can 
> >> >>    even approach the full bandwidth on certain links. 
> >> >> 
> >> >> @@@ this last sentence doesn't really make sense in the absence
> >> >> @@@ of an understanding of the provider's network (like if I
> >> >> @@@ protect all of my packets, the statement doesn't apply)
> 
> I assume the last line was meant to say "if I protect all my links"
> (instead of "all my packets"). No?
> 
Dave?

> Anyway, this is not trying to say that VoIP will approach link bandwidth
> in every network. Just that it can happen in some networks in some
> situations. Which reflects the concern of the SP who provided this text.
> The description above starts with "For example". Statement seems valid
> in the context of an example.
> 
Dave?

> >> >>      
> >> >>    For delay/jitter reasons it is undesirable to carry 
> >> more than a 
> >> >>    certain percentage of VoIP traffic on any link. 
> >> >> 
> >> >> @@@ but we understand that we can run in the region about 80%
> >> >> @@@ utilization with small jitter and delay (with >= OC48). So
> >> >> @@@ why is it undesirable? This seems statement seems to 
> >> be unsupported.
> 
> I think the comment points out that the "certain percentage" may be as
> high as 80% in some cases (eg high speed link, strict priority provided
> to VoIP by scheduler without any rate limitation activated,...). It
> doesn't seem to invalidate the fact that if you may encounter a very
> high VoIP load on some links, you may want to control it to a certain
> percentage below 100% (be it 80%). 
> Also, while the fastest backbone links in many networks are OC48 and
> above, lower speed links are also found in many networks where the
> "certain percentage" may be lower. Also, scheduler might be configured
> by SP with some rate limitation for the VoIP queue below 100% (for
> policy purposes to keep bandwidth for some other traffic such 
> as Premium VPN).
> 
> But again, this was not meant to suggest that this is something you need
> to do everywhere. Just that it makes sense in some environments and that
> some SPs want to do it there.
>  
> So, to better reflect this, we will adjust the statement above into: 
> "For delay/jitter reasons, some network administrators see it as
> undesirable to carry more than a certain percentage of VoIP traffic on
> any link. "
> 
Dave, does that address your concern?

>  
> >> >>  
> >> >> 4.1.    DS-TE Compatibility 
> >> >>  
> >> >>    While DS-TE is required in a number of situations such 
> >> as the ones 
> >> >>    described above, it is important to keep in mind that 
> >> using DS-TE 
> >> >>    may impact scalability (as discussed later in this 
> >> document) and 
> >> >>    operational practices. DS-TE should only be used when 
> >> existing TE 
> >> >>    mechanisms combined with Diff-Serv cannot address the 
> >> network design 
> >> >>    requirements.
> >> >> 
> >> >> @@@ can these cases be described in any general way? That would
> >> >> @@@ seem to be useful (as useful as making the statement in the
> >> >> @@@ first place).
> 
> 
> Can update last sentence with:
> "
> DS-TE should only be used when existing TE mechanisms combined with
> Diff-Serv cannot address the network design requirements (i.e. where
> constraint based routing is required and where it needs to enforce
> different bandwidth constraints for different classes of traffic, such
> as in the scenarios described above in section 3). 
> "
> 
Dave?

>    
> >> >>    At the time of writing this document, it is not clear 
> >> whether a 
> >> >>    single model of Bandwidth Constraints is sufficient, 
> >> which one it 
> >> >>    should be and how flexible this model really needs to 
> >> be and what 
> >> >>    are the implications on the DS-TE technical solution and its 
> >> >>    implementations.  Work is currently in progress to 
> >> investigate the 
> >> >>    performance and trade-offs of different operational 
> aspects of 
> >> >>    Bandwidth Constraints models.
> >> >> 
> >> >> @@@ can these tradeoffs (and additionaly, complexity tradeoffs)
> >> >> @@@ be quantified in any way? I would imagine that this would 
> >> >> @@@ be useful for anyone wanting to deploy this technology?
> >> >>
> 
> This has been discussed outside of the this document.
> For example, see draft-wlai-tewg-bcmodel-00.txt for quantified
> comparison.
>  
Maybe add a ref to those "work in progress" docs.

>      
> >> >>    In the selection of a default model, at least the 
> >> following criteria 
> >> >>    are expected to be considered: 
> >> >>    (1) addresses the scenarios in Section 2 
> >> >>    (2) works well under both normal and overload conditions 
> >> >>    (3) applies equally when preemption is either enabled 
> >> or disabled 
> >> >>    (4) minimizes signaling load processing requirements 
> >> >>    (5) maximizes efficient use of the network 
> >> >> 
> >> >> @@@ (6) Minimizes implementation and deployment complexity?
> >> >>
> 
> Agreed.
>      
>     
> >> >>    Since there are 8 preemption priorities and up to 8 
> >> Class-Types, 
> >> >>    there could theoretically be up to 64 TE-Classes in a 
> >> network. This 
> >> >>    is felt to be beyond current practical requirements. 
> >> The current 
> >> >>    practical requirement is that the DS-TE solution must 
> >> allow support 
> >> >>    for up to 8 TE-classes. The DS-TE solution must 
> allow these TE-
> >> >>    classes to comprise any arbitrary subset of 8 (or 
> >> less) from the 
> >> >>    (64) possible combinations of (8) Class-Types and (8) 
> >> preemption 
> >> >>    priorities. 
> >> >> 
> >> >> @@@ what are these numbers based on (what does "current 
> practical
> >> >> @@@ requirements" mean)? 
> >> >> 
> 
> "Current practical requirements" means based on what the SP co-authors
> of that draft and others SPs from the TEWG are considering deploying in
> the coming years. 
> To give you a feel , in the case of number of CTs, some argued 3 CTs
> were enough, others argued 4 CTs were enough, some argued 
> they may use 5
> or more, no one argued for more than 8. We settled for 8 since this
> there were no scalability impact in a solution supporting 3,4 or 8.
> 
Dave are you happy with this answer?

> >> >> @@@ I guess Scalability (5.4) is a metric of complexity, but I'd
> >> >> @@@ like to see something more specific, e.g. "Minimizes <foo>"
> >> >> @@@ etc
> 
> Section 5.4 already lists the specific aspects of scalability that we
> want to be considered:
> "IGP signaling, IGP processing, IGP database, TE-tunnel signaling"
> 
> 
> >> >> 
> >> >> 6.      Security Considerations 
> >> >>     
> >> >>    The solution developed to address the requirements 
> >> defined in this 
> >> >>    document must address security aspects. DS-TE is not 
> >> expected to add 
> >> >>                                                     
> >> ^^^^^^^^^^^^^^^^^^^
> >> >>    specific security requirements beyond those of Diff-Serv and 
> >> >>    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> >>    existing TE.
> >> >> 
> >> >> @@@ I would venture to guess that no one tries to "add specific
> >> >> @@@ security requirements". That's why we have this section...
> >> >> 
> 
> See above re security.
> 
> Cheers
> 
> Francois
> 
Bert



From owner-te-wg@ops.ietf.org  Tue Jan 21 19:02: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 TAA15915
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 19:02:51 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b8MO-0002Wj-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 16:03:16 -0800
Received: from oe149.pav0.hotmail.com ([64.4.33.142] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b8MK-0002SR-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 16:03:12 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 21 Jan 2003 16:02:41 -0800
X-Originating-IP: [63.15.53.235]
Reply-To: "Victoria Fineberg" <fineberg@illinoisalumni.org>
From: "Victoria Fineberg" <fineberg@illinoisalumni.org>
To: "Le Faucheur, Francois - TE-WG" <flefauch@cisco.com>,
        "IETF TE-WG" <te-wg@ops.ietf.org>
Subject: Protocols: BC in DS-TE IGPs
Date: Tue, 21 Jan 2003 19:03:44 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <OE149NSWYUyEUDfBaO8000265a0@hotmail.com>
X-OriginalArrivalTime: 22 Jan 2003 00:02:41.0432 (UTC) FILETIME=[95109180:01C2C1A9]
X-Spam-Status: No, hits=1.0 required=5.0
	tests=SPAM_PHRASE_00_01,USER_AGENT_OE
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Francois, et al,

Sorry if this comment is coming late just before the "last call,"
but if I am correct, it may be worthwhile to take care of it now.

draft-ietf-tewg-diff-te-proto-02.txt, Section 5.1, states that

"
'existing Maximum Reservable Bandwidth' ... in now
interpreted as Bandwidth Constraint 0 (BC0).
"

This is true for the Russian Dolls BC Model, but not for
the Maximum Allocation Model (MAM), where BC0 is just
one of several components.  In the MAM, the existing
Maximum Reservable Bandwidth is the sum of BCb.

Cheers

Victoria

Victoria Fineberg
fineberg@illinoisalumni.org




From owner-te-wg@ops.ietf.org  Tue Jan 21 20:09:03 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17008
	for <tewg-archive@lists.ietf.org>; Tue, 21 Jan 2003 20:09:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18b9PT-0006CO-00
	for te-wg-data@psg.com; Tue, 21 Jan 2003 17:10:31 -0800
Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18b9PR-0006CC-00
	for te-wg@ops.ietf.org; Tue, 21 Jan 2003 17:10:29 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0M1ARr05478
	for <te-wg@ops.ietf.org>; Tue, 21 Jan 2003 20:10:27 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ267PBJ>; Wed, 22 Jan 2003 02:10:26 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE023@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: FW: FW: Review of draft-tewg-diff-te-reqts-06.txt
Date: Wed, 22 Jan 2003 02:09:24 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.2 required=5.0
	tests=EXCHANGE_SERVER,OUTLOOK_FW_MSG,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Here is the response to Francois' answer on Kathie's
comments. I have even added additional text from me.

Thanks,
Bert 
> -----Original Message-----
> From: Kathleen Nichols [mailto:nichols@packetdesign.com]
> Sent: woensdag 22 januari 2003 1:29
> To: Wijnen, Bert (Bert)
> Cc: Brian Carpenter (E-mail)
> Subject: Re: FW: Review of draft-tewg-diff-te-reqts-06.txt
> 
> Look, I think the notion that "service providers contributed
> to this" doesn't make the examples more crisp.

To which I clearly MUST agree.

> However, I just don't think it's important enough to worry about.
> Similarly, if the authors are happy with the current wordings,
> then they should use them.
> 
So... up to you if you try to make it "crsiper".

> The business of a sharing a scheduling class within a router
> still seems a bit low level for a notion of a traffic class
> that is defined on a network. The reason for this is that
> different scheduling mechanisms could be used in different
> routers within the same network to implement a particular
> class of service. It sounds like we're not communicating
> on this notion of a per-hop behavior being identical to a
> class of service. This is true even if the per hop behavior
> is further modified by saying that it shares a scheduling
> constraint.
> 
I think that is something to try and address though.

Bert
> 	Kathie



From owner-te-wg@ops.ietf.org  Wed Jan 22 05:23: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 FAA21185
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 05:23:18 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bI2W-000A4F-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 02:23:24 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bI2T-000A3i-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 02:23:21 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0MAKxc8022196;
	Wed, 22 Jan 2003 11:21:11 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Wed, 22 Jan 2003 11:22:41 +0100
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: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Wed, 22 Jan 2003 10:22:40 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E781@xbe-lon-303.cisco.com>
Thread-Topic: Weak turnout : was-> A proposal for moving ahead on BC models
Thread-Index: AcLByRrtZUfQjAOJQ1aN+bJ3rWo7vgALiXUg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Jim Boyle" <jboyle@pdnets.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 22 Jan 2003 10:22:41.0046 (UTC) FILETIME=[31C33360:01C2C200]
X-Spam-Status: No, hits=-0.3 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
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 FAA21185

Bert,

>> -----Original Message-----
>> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
>> Sent: 21 January 2003 21:25
>> To: Jim Boyle; Ash, Gerald R (Jerry), ALABS
>> Cc: te-wg@ops.ietf.org
>> Subject: RE: Weak turnout : was-> A proposal for moving 
>> ahead on BC models
>> 
>> 
>> I would contend that if we onlu have 9 reactions out of 1100
>> or so WG subscribers/members that there is NO WG consensus 
>> to work on this topic.
>> 

What do you mean by ... "no concensus to work on this topic"???

There may be some confusion here. The topic that generated "9 reactions"
was not about whether we should work on BC models. We have been working
on BC models for a while now. It is part of the work on DSTE which
appears on the TEWG charter. BC Models has been, by far, the single item
generating the most dicussion on the TEWG list. It has been, by far, the
single item generating the most discussion at the TEWG meeting itself
(TEWG minutes say "Lots of discussion on this"). These discussions were
not about whether we needed to work on it, but were actually about
comparing/progressing them.
Based on this, I would contend that there is strong concensus to work on
the topic of BC models. 
Are we in line on this?

The specific item that triggered the "9 reactions" related purely to one
particular aspect of how to move ahead on these models: specifically how
the two models we specified should actually be referenced (ie should
they be both default models, one default & one optional and then which
is which, should they go for Informational, Standards track). This is
not necessarily a topic of most passionate debate in a technical
communitee. 

Considering that:
	- this had been discussed extensively at the Atlanta meeting
	- it has been discussed extensively on the list
	- everybody had ample opportunity/time to comment
	- this discussion item only relates to how the models would be
referenced (default/optional)
do we agree this item is suitably closed and we can move ahead on
updating the corresponding refences in the various document (which is
pretty much the last thing holding those)?

Thanks

Francois

 
PS: I am also wondering if we wouldn't have had a few more reactions,
had we issued a slightly more formal call for vote on that topic with a
deadline and a fixed set of options to choose from which reflected the
final part of the discussion we had on the list. But that's beside the
point.

>> Thanks,
>> Bert 
>> 
>> > -----Original Message-----
>> > From: Jim Boyle [mailto:jboyle@pdnets.com]
>> > Sent: maandag 20 januari 2003 15:45
>> > To: Ash, Gerald R (Jerry), ALABS
>> > Cc: te-wg@ops.ietf.org
>> > Subject: Weak turnout : was-> A proposal for moving ahead 
>> on BC models
>> > 
>> > 
>> > 
>> > Hopefully for other calls we can get better turnout than 9 
>> > members out of 
>> > 1100.
>> > 
>> > 
>> > On Mon, 20 Jan 2003, Ash, Gerald R (Jerry), ALABS wrote:
>> > 
>> > > 1. my count is 6 to 3.
>> > > 2. a majority, yes, but a thin margin and small sample on 
>> > which to base this decision...
>> > > 
>> > > Jerry
>> > > 
>> > > -----Original Message-----
>> > > From: Jim Boyle [mailto:jboyle@pdnets.com]
>> > > Sent: Saturday, January 18, 2003 10:21 PM
>> > > To: te-wg@ops.ietf.org
>> > > Subject: Re: A proposal for moving ahead on BC models 
>> (conclusion?)
>> > > 
>> > > For the record, I think it best to specify a default model.
>> > > 
>> > > However, assuming Sanjay's second vote masks his first, and 
>> > including my 
>> > > vote above, that would leave us with 6 folks who think we 
>> > should pull the 
>> > > requirement for a default, specified model, and 2 who think 
>> > we should keep 
>> > > it.  That gives us a voter turn-out on our list of less 
>> than 1% ;-(
>> > > 
>> > > So we'll update the requirements document (currently with 
>> > IESG) to reflect 
>> > > no need for a required default BC model.
>> > > 
>> > > Jim
>> > > 
>> > > 
>> > 
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed Jan 22 06:01:46 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21631
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 06:01:45 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bIfs-000B7N-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 03:04:04 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bIfp-000B6U-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 03:04:01 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0MB1t7D000609;
	Wed, 22 Jan 2003 12:01:56 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Wed, 22 Jan 2003 12:03:27 +0100
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: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Wed, 22 Jan 2003 11:03:26 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E782@xbe-lon-303.cisco.com>
Thread-Topic: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Thread-Index: AcLByRo3O9PDAZLyQl+mYsrwNwLi8gAOVDWQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 22 Jan 2003 11:03:27.0140 (UTC) FILETIME=[E3BF8640:01C2C205]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
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 GAA21631




>> I now see why I did not understand. When you say "TE-LSPs are routed"
>> then I think of "routing happens all the time for all packets".
>> From what you suggest to add, it sounds as if you mean that at the
>> time a TE-LSP is configured, that that is the time when bandwidth
>> is reserved. So I guess you mean
>>      - in which order the different TE-LSPs are configured
>>        (or established or created) 
>> 
>> Did I get that? If so, then my text if probably even better.
>> 

Alright then let's go for:
"      - in which order the different TE-LSPs are configured
        (or established)
"

(as I couldn't explain the difference between "created".


>> So can you tell me (I am thick, sorry) what means:
>>   - {TA}PSC
>>   - <FEC/{TA}/PSC>
>> 
>> Maybe once you explain it to me I will get it and maybe 
>> there is an Aha
>> 

How about an example:

Say SP supports a class of service C1 with committed/excess concepts
using the AF11 and AF12 PHBs.

Diff-Serv has defined a convenient term to designate all the packets of
the DS domain whose DSCP correspond to AF11 . It is called a Traffic
Aggregate. Let me call it, loosely, the AF11 TA.
Clearly we also have the AF12 TA.

We look at the packets belonging to AF11 TA and AF12 TA as the ones
forming the C1 class of service. To indicate that the reason those two
are grouped together is because they "share a ordering constraints" (ie
they MUST not be reordered) we call this set a {TA}PSC.
The PSC is an existing Disff-Serv concept that precisely designates the
set of PHBs sharing the "same ordering constraint".
Hence the notation of "{TA}PSC" to suggest that it is a set of several
TA whose relationship is that their PHBs belong to the same PSC.
In brief it is really nothing else that the set of all packets in that
domain which belong to a given "class of service".

Now clearly, depending on their destination, packets of a given class of
service (ie packets from a given {TA}PSC ) will be transported on
different TE tunnels. FEC is an MPLS term that sort of designate the set
of packets that are "going on the same path from MPLS perspective".  The
set of packets of a given class of service which are transported on a
given tunnel are called a  <FEC/{TA}/PSC> to indicate it is basically
the intersection of a FEC and a {TA}/PSC. 

Aha?

>> > So how about breaking this up into something like :
>> > 
>> > "
>> > The solution developed to address the requirements defined in this
>> > document must address security aspects. DS-TE does not raise any
>> > specific additional security requirements beyond the 
>> existing security
>> > requirements of MPLS TE and Diff-Serv. The solution must 
>> > ensure that the
>> > existing security mechanisms of MPLS TE and Diff-Serv are not
>> > compromised by the solution protocol/procedure extensions 
>> or otherwise
>> > must provide security mechanisms to address this. 
>> > "
>> > 
>> That sounds much better to me. 
>>

Will update.
 
>> Pls check that you also addres the comments about DoS attacks as
>> reaided by David Meyer.
>> 

Discussed separately.

Francois

>> Bert
>> > Thanks 
>> > 
>> > Francois
>> > 
>> 
>> 



From owner-te-wg@ops.ietf.org  Wed Jan 22 07:57:32 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23480
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 07:57:31 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bKQA-000EHD-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 04:55:58 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bKQ7-000EFy-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 04:55:55 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0MCtNk21401
	for <te-wg@ops.ietf.org>; Wed, 22 Jan 2003 07:55:23 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ2675YA>; Wed, 22 Jan 2003 13:55:22 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE1E3@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
Date: Wed, 22 Jan 2003 13:54:11 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.4 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Inline

> -----Original Message-----
> From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
> Sent: woensdag 22 januari 2003 12:03
> To: Wijnen, Bert (Bert)
> Cc: Tewg (E-mail)
> Subject: RE: comments on draft-ietf-tewg-diff-te-reqts-06.txt
> 
> >> I now see why I did not understand. When you say "TE-LSPs are routed"
> >> then I think of "routing happens all the time for all packets".
> >> From what you suggest to add, it sounds as if you mean that at the
> >> time a TE-LSP is configured, that that is the time when bandwidth
> >> is reserved. So I guess you mean
> >>      - in which order the different TE-LSPs are configured
> >>        (or established or created) 
> >> 
> >> Did I get that? If so, then my text if probably even better.
> >> 
> 
> Alright then let's go for:
> "      - in which order the different TE-LSPs are configured
>         (or established)
> "
> 
MUCH better. Thanks

> (as I couldn't explain the difference between "created".
> 
they were choices I gave you.

> 
> >> So can you tell me (I am thick, sorry) what means:
> >>   - {TA}PSC
> >>   - <FEC/{TA}/PSC>
> >> 
> >> Maybe once you explain it to me I will get it and maybe 
> >> there is an Aha
> >> 
> 
> How about an example:
> 
> Say SP supports a class of service C1 with committed/excess concepts
> using the AF11 and AF12 PHBs.
> 
> Diff-Serv has defined a convenient term to designate all the packets of
> the DS domain whose DSCP correspond to AF11 . It is called a Traffic
> Aggregate. Let me call it, loosely, the AF11 TA.
> Clearly we also have the AF12 TA.
> 
> We look at the packets belonging to AF11 TA and AF12 TA as the ones
> forming the C1 class of service. To indicate that the reason those two
> are grouped together is because they "share a ordering constraints" (ie
> they MUST not be reordered) we call this set a {TA}PSC.
> The PSC is an existing Disff-Serv concept that precisely designates the
> set of PHBs sharing the "same ordering constraint".
> Hence the notation of "{TA}PSC" to suggest that it is a set of several
> TA whose relationship is that their PHBs belong to the same PSC.
> In brief it is really nothing else that the set of all packets in that
> domain which belong to a given "class of service".
> 
> Now clearly, depending on their destination, packets of a given class of
> service (ie packets from a given {TA}PSC ) will be transported on
> different TE tunnels. FEC is an MPLS term that sort of designate the set
> of packets that are "going on the same path from MPLS perspective".  The
> set of packets of a given class of service which are transported on a
> given tunnel are called a  <FEC/{TA}/PSC> to indicate it is basically
> the intersection of a FEC and a {TA}/PSC. 
> 
> Aha?
> 
Somewhat... but I am not a TE expert, nor an Diffserv or MPLS expert.
I can at least follow/understand the above explanation. That helps me,
thanks. If everyone else is happy with the text you have in sect 4.5,
then I won't object any longer.

I did see that Panos TRIMINTZIOS already wonders if you are inventing
new (and more complex) terminology. 

> >> > So how about breaking this up into something like :
> >> > 
> >> > "
> >> > The solution developed to address the requirements defined in this
> >> > document must address security aspects. DS-TE does not raise any
> >> > specific additional security requirements beyond the existing security
> >> > requirements of MPLS TE and Diff-Serv. The solution must 
> >> > ensure that the
> >> > existing security mechanisms of MPLS TE and Diff-Serv are not
> >> > compromised by the solution protocol/procedure extensions or otherwise
> >> > must provide security mechanisms to address this. 
> >> > "
> >> > 
> >> That sounds much better to me. 
> >>
> 
> Will update.
>  
> >> Pls check that you also addres the comments about DoS attacks as
> >> reaided by David Meyer.
> >> 
> 
> Discussed separately.
> 
Yes, but no I don't think I have seen a proposed (re)solution yet, have I?

Bert



From owner-te-wg@ops.ietf.org  Wed Jan 22 09:16: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 JAA25386
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 09:16:35 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bLeq-000Gm4-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 06:15:12 -0800
Received: from rtp-msg-core-1.cisco.com ([161.44.11.97])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bLeo-000Gkk-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 06:15:10 -0800
Received: from bucket.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0MEFNOR003410;
	Wed, 22 Jan 2003 09:15:24 -0500 (EST)
Received: from tnadeau-w2k.cisco.com (che-vpn-cluster-1-101.cisco.com [10.86.240.101])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ACL37537;
	Wed, 22 Jan 2003 09:14:35 -0500 (EST)
Message-Id: <5.2.0.9.2.20030122091315.02e80ec0@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 22 Jan 2003 09:14:32 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
  models
Cc: te-wg@ops.ietf.org
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE011@nl0006exch001u.nl.l
 ucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


         How has this discussion gone down the road of
being a discussion of consensus or not?  There has been
lots and lots of discussion on this topic, it is part of
the charter, and has been discussed at numerous
TE WG meetings over the past few years.

         --Tom

>I would contend that if we onlu have 9 reactions out of 1100
>or so WG subscribers/members that there is NO WG consensus
>to work on this topic.
>
>Thanks,
>Bert
>
> > -----Original Message-----
> > From: Jim Boyle [mailto:jboyle@pdnets.com]
> > Sent: maandag 20 januari 2003 15:45
> > To: Ash, Gerald R (Jerry), ALABS
> > Cc: te-wg@ops.ietf.org
> > Subject: Weak turnout : was-> A proposal for moving ahead on BC models
> >
> >
> >
> > Hopefully for other calls we can get better turnout than 9
> > members out of
> > 1100.
> >
> >
> > On Mon, 20 Jan 2003, Ash, Gerald R (Jerry), ALABS wrote:
> >
> > > 1. my count is 6 to 3.
> > > 2. a majority, yes, but a thin margin and small sample on
> > which to base this decision...
> > >
> > > Jerry
> > >
> > > -----Original Message-----
> > > From: Jim Boyle [mailto:jboyle@pdnets.com]
> > > Sent: Saturday, January 18, 2003 10:21 PM
> > > To: te-wg@ops.ietf.org
> > > Subject: Re: A proposal for moving ahead on BC models (conclusion?)
> > >
> > > For the record, I think it best to specify a default model.
> > >
> > > However, assuming Sanjay's second vote masks his first, and
> > including my
> > > vote above, that would leave us with 6 folks who think we
> > should pull the
> > > requirement for a default, specified model, and 2 who think
> > we should keep
> > > it.  That gives us a voter turn-out on our list of less than 1% ;-(
> > >
> > > So we'll update the requirements document (currently with
> > IESG) to reflect
> > > no need for a required default BC model.
> > >
> > > Jim
> > >
> > >
> >
> >

"The difficult, we do immediately.  The impossible takes a little longer." 
-- Air Force Motto

http://www.mkp.com/books_catalog/catalog.asp?ISBN=1-55860-751-X







From owner-te-wg@ops.ietf.org  Wed Jan 22 10:47: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 KAA28501
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 10:47:27 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bN6f-000Jfy-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 07:48:01 -0800
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bN6b-000JfX-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 07:47:57 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0MFlmq00316
	for <te-wg@ops.ietf.org>; Wed, 22 Jan 2003 10:47:48 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ268AHV>; Wed, 22 Jan 2003 16:47:46 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE2E4@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Thomas D. Nadeau" <tnadeau@cisco.com>
Cc: te-wg@ops.ietf.org
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Wed, 22 Jan 2003 16:47:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Maybe it is just your (stupid) AD who does not understand 
how it is possible that these days we seem to only be
able to get VERY FEW people to speak up (pro or against
or even declaring a don't care) when WG chairs ask for
opinions to try and gauge consensus. How are they 
expected to read if teh WG indeed has consensus on anything?
How do they know that the majority of the WG members have
even read (parts of) an I-D that they want to pass to their
ADs for consideration as an RFC.

I can accept if there are only a small set of people that do
the extual writing and word-smitting, but I would hope that
many people are willing to read, try to understand, and to
then give a yes, no, don't case answer when asked.

Thanks,
Bert 

> -----Original Message-----
> From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> Sent: woensdag 22 januari 2003 15:15
> To: Wijnen, Bert (Bert)
> Cc: te-wg@ops.ietf.org
> Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
> models
> 
> 
> 
>          How has this discussion gone down the road of
> being a discussion of consensus or not?  There has been
> lots and lots of discussion on this topic, it is part of
> the charter, and has been discussed at numerous
> TE WG meetings over the past few years.
> 
>          --Tom
> 
> >I would contend that if we onlu have 9 reactions out of 1100
> >or so WG subscribers/members that there is NO WG consensus
> >to work on this topic.
> >
> >Thanks,
> >Bert



From owner-te-wg@ops.ietf.org  Wed Jan 22 11:09: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 LAA29268
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 11:09:09 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bNTM-000KZ8-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 08:11:28 -0800
Received: from rtp-msg-core-1.cisco.com ([161.44.11.97])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bNTJ-000KX1-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 08:11:25 -0800
Received: from bucket.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id h0MGBcmU022407;
	Wed, 22 Jan 2003 11:11:38 -0500 (EST)
Received: from tnadeau-w2k.cisco.com (che-vpn-cluster-1-101.cisco.com [10.86.240.101])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ACL40027;
	Wed, 22 Jan 2003 11:10:50 -0500 (EST)
Message-Id: <5.2.0.9.2.20030122110859.040d5c28@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 22 Jan 2003 11:10:39 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
  models
Cc: te-wg@ops.ietf.org
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE2E4@nl0006exch001u.nl.l
 ucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

At 04:47 PM 1/22/2003 +0100, Wijnen, Bert (Bert) wrote:
>Maybe it is just your (stupid) AD who does not understand
>how it is possible that these days we seem to only be
>able to get VERY FEW people to speak up (pro or against
>or even declaring a don't care) when WG chairs ask for
>opinions to try and gauge consensus. How are they
>expected to read if teh WG indeed has consensus on anything?
>How do they know that the majority of the WG members have
>even read (parts of) an I-D that they want to pass to their
>ADs for consideration as an RFC.
>
>I can accept if there are only a small set of people that do
>the extual writing and word-smitting, but I would hope that
>many people are willing to read, try to understand, and to
>then give a yes, no, don't case answer when asked.
>
>Thanks,
>Bert

         Point taken. I agree that there is no question that
folks need to jump in more.  The point I was making is that
people have discussed these documents quite a bit, at
least in the past, so the current apathy is not IMHO an
indication of lack of support for the documents.

         --Tom


> > -----Original Message-----
> > From: Thomas D. Nadeau [mailto:tnadeau@cisco.com]
> > Sent: woensdag 22 januari 2003 15:15
> > To: Wijnen, Bert (Bert)
> > Cc: te-wg@ops.ietf.org
> > Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
> > models
> >
> >
> >
> >          How has this discussion gone down the road of
> > being a discussion of consensus or not?  There has been
> > lots and lots of discussion on this topic, it is part of
> > the charter, and has been discussed at numerous
> > TE WG meetings over the past few years.
> >
> >          --Tom
> >
> > >I would contend that if we onlu have 9 reactions out of 1100
> > >or so WG subscribers/members that there is NO WG consensus
> > >to work on this topic.
> > >
> > >Thanks,
> > >Bert

"The difficult, we do immediately.  The impossible takes a little longer." 
-- Air Force Motto

http://www.mkp.com/books_catalog/catalog.asp?ISBN=1-55860-751-X







From owner-te-wg@ops.ietf.org  Wed Jan 22 11:57:45 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00937
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 11:57:44 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bOCz-000MBg-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 08:58:37 -0800
Received: from mx2out.umbc.edu ([130.85.25.11])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bOCw-000MBS-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 08:58:34 -0800
Received: from gl.umbc.edu (vijay@irix2.gl.umbc.edu [130.85.60.11])
	by mx2out.umbc.edu (8.12.1/8.12.0/UMBC-Central 1.11 mxout  1.2.2.3 $) with ESMTP id h0MGwJ2X020392;
	Wed, 22 Jan 2003 11:58:20 -0500 (EST)
Received: from localhost (vijay@localhost)
	by gl.umbc.edu (8.9.0/8.9.0) with ESMTP id LAA4837025;
	Wed, 22 Jan 2003 11:58:20 -0500 (EST)
X-Authentication-Warning: irix2.gl.umbc.edu: vijay owned process doing -bs
Date: Wed, 22 Jan 2003 11:58:20 -0500
From: Vijay Gill <vijay@umbc.edu>
X-X-Sender: vijay@irix2.gl.umbc.edu
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
cc: "Thomas D. Nadeau" <tnadeau@cisco.com>, <te-wg@ops.ietf.org>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC models
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE2E4@nl0006exch001u.nl.lucent.com>
Message-ID: <Pine.SGI.4.44L.01.0301221149470.4930561-100000@irix2.gl.umbc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AvMilter-Key: 1043255002:2b265a36d453b94bd716533a00b51bf7
X-Avmilter: Message Skipped, too small
X-Processed-By: MilterMonkey Version 0.9 -- http://www.membrain.com/miltermonkey
X-Spam-Status: No, hits=-3.2 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_00_01,USER_AGENT_PINE,X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

On Wed, 22 Jan 2003, Wijnen, Bert (Bert) wrote:

> Maybe it is just your (stupid) AD who does not understand
> how it is possible that these days we seem to only be
> able to get VERY FEW people to speak up (pro or against
> or even declaring a don't care) when WG chairs ask for
> opinions to try and gauge consensus. How are they
> expected to read if teh WG indeed has consensus on anything?

While I can't speak for others, I tend to only read on issues I feel are
relevant to my day job because of job load. Some of the proposals put
forward are a waste of time (for my network requirements), ergo, I do not
bother reading or commenting on them.  Others may be in the same boat.

In this case, silence does NOT mean consent.

/vijay






From owner-te-wg@ops.ietf.org  Wed Jan 22 18:57:40 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11647
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 18:57:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bUkB-000BUg-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 15:57:19 -0800
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bUk8-000BUA-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 15:57:17 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0MNuib24340
	for <te-wg@ops.ietf.org>; Wed, 22 Jan 2003 18:56:45 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ268G5W>; Thu, 23 Jan 2003 00:56:44 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE369@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Vijay Gill <vijay@umbc.edu>
Cc: "Thomas D. Nadeau" <tnadeau@cisco.com>, te-wg@ops.ietf.org
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Thu, 23 Jan 2003 00:56:16 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=-2.0 required=5.0
	tests=EMAIL_ATTRIBUTION,EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Vijay writes:

> On Wed, 22 Jan 2003, Wijnen, Bert (Bert) wrote:
> 
> > Maybe it is just your (stupid) AD who does not understand
> > how it is possible that these days we seem to only be
> > able to get VERY FEW people to speak up (pro or against
> > or even declaring a don't care) when WG chairs ask for
> > opinions to try and gauge consensus. How are they
> > expected to read if teh WG indeed has consensus on anything?
> 
> While I can't speak for others, I tend to only read on issues 
> I feel are relevant to my day job because of job load.
> Some of the proposals put forward are a waste of time
> (for my network requirements),  ergo, I do not bother reading
> or commenting on them.  Others may be in the same boat.
> 
> In this case, silence does NOT mean consent.
>
Thank you very much Vijay. That was/is exactly what I worry about.
If not enough people (and 10 is the absolute minumum, but having seen
the attendence of TWEG sessions, I'd expect 25 or more) can speak up
to state one of:

 - I read it and I am positive, it is good stuff
 - I read it and I see no problems or objections
 - I read it but I cannot determine if it is bad, but I can see that
   what has been discussed in the WG is indeed in the document
 - I read it and I have these nits/objections...
 - I did not read it cause this is not relevant to my xxx job/work/function
 - I did not read it cause I think this is nonsense 

Then I get the feeling that we're just allowing a small group of
people push their petty-project through the process. That seems NOT
good to me. We need serious WG participation in reading and commenting
in one of these forums above, before we can declare that we have WG
consensus on a document to be presented to IESG for approval as RFC
(in whatever form).

Bert
> /vijay
> 
> 
> 



From owner-te-wg@ops.ietf.org  Wed Jan 22 22:33: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 WAA15755
	for <tewg-archive@lists.ietf.org>; Wed, 22 Jan 2003 22:33:46 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bY7T-000M0N-00
	for te-wg-data@psg.com; Wed, 22 Jan 2003 19:33:35 -0800
Received: from mandala.kddlabs.co.jp ([192.26.91.6])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bY7Q-000LxA-00
	for te-wg@ops.ietf.org; Wed, 22 Jan 2003 19:33:32 -0800
Received: from localhost (localhost.kddlabs.co.jp [127.0.0.1])
	by mandala.kddlabs.co.jp (Postfix) with ESMTP id 6103F2B6F1
	for <te-wg@ops.ietf.org>; Thu, 23 Jan 2003 12:33:01 +0900 (JST)
Received: from mandala.kddlabs.co.jp ([127.0.0.1])
 by localhost (mandala.kddlabs.co.jp [127.0.0.1:10024]) (amavisd-new)
 with SMTP id 38993-17 for <te-wg@ops.ietf.org>;
 Thu, 23 Jan 2003 12:32:59 +0900 (JST)
Received: from server1.onw.kddlabs.co.jp (silver.onw.kddlabs.co.jp [172.19.83.4])
	by mandala.kddlabs.co.jp (Postfix) with ESMTP id 630D22B6F7
	for <te-wg@ops.ietf.org>; Thu, 23 Jan 2003 12:32:59 +0900 (JST)
Received: from DNS.kddilabs.jp ([172.19.83.29])
	by server1.onw.kddlabs.co.jp (ExpressMail 4.01) with ESMTP id DAA197902
	for <te-wg@ops.ietf.org>; Thu, 23 Jan 2003 12:32:59 +0900 (JST)
Message-Id: <5.1.1.8.2.20030123122644.00b50680@172.19.83.4>
X-Sender: ogino@172.19.83.4
X-Mailer: QUALCOMM Windows Eudora Version 5.1.1-J
Date: Thu, 23 Jan 2003 12:33:17 +0900
To: te-wg@ops.ietf.org
From: ogino <ogino@kddilabs.jp>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
  models
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE369@nl0006exch001u.nl.l
 ucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-2022-jp"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear TEWGers:

I read it and now I see no problems or objections through the discussion on 
the TEWG mailing list.

Best regards,

Nagao Ogino


At 00:56 03/01/23 +0100, Wijnen, Bert (Bert) wrote:
>Thank you very much Vijay. That was/is exactly what I worry about.
>If not enough people (and 10 is the absolute minumum, but having seen
>the attendence of TWEG sessions, I'd expect 25 or more) can speak up
>to state one of:
>
>  - I read it and I am positive, it is good stuff
>  - I read it and I see no problems or objections
>  - I read it but I cannot determine if it is bad, but I can see that
>    what has been discussed in the WG is indeed in the document
>  - I read it and I have these nits/objections...
>  - I did not read it cause this is not relevant to my xxx job/work/function
>  - I did not read it cause I think this is nonsense
>
>Then I get the feeling that we're just allowing a small group of
>people push their petty-project through the process. That seems NOT
>good to me. We need serious WG participation in reading and commenting
>in one of these forums above, before we can declare that we have WG
>consensus on a document to be presented to IESG for approval as RFC
>(in whatever form).
>
>Bert

******************************
Nagao Ogino, Dr. Eng.
KDDI R & D Laboratories Inc.
2-1-15 Ohara, Kamifukuoka-shi,
Saitama 356-8502 Japan
TEL   +81 49 278 7860
FAX   +81 49 278 7516
E-mail   ogino@kddilabs.jp
****************************** 





From owner-te-wg@ops.ietf.org  Thu Jan 23 04:53: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 EAA01815
	for <tewg-archive@lists.ietf.org>; Thu, 23 Jan 2003 04:53:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18be2R-000Cdu-00
	for te-wg-data@psg.com; Thu, 23 Jan 2003 01:52:47 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18be2N-000Cd5-00
	for te-wg@ops.ietf.org; Thu, 23 Jan 2003 01:52:43 -0800
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 h0N9oVFN009885;
	Thu, 23 Jan 2003 10:50:38 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Thu, 23 Jan 2003 10:51:58 +0100
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: Weak turnout : was-> A proposal for moving ahead on BC  models
Date: Thu, 23 Jan 2003 09:51:46 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E787@xbe-lon-303.cisco.com>
Thread-Topic: Weak turnout : was-> A proposal for moving ahead on BC  models
Thread-Index: AcLCkNqTuHSueeN8TP2UWshAUzJNHQAJXuaw
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 23 Jan 2003 09:51:58.0782 (UTC) FILETIME=[1219C5E0:01C2C2C5]
X-Spam-Status: No, hits=-0.3 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
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 EAA01815

Bert,

I'd like to repeat the point I made Yesterday. The "Weak turnout" DID
NOT relate to the question of wether we should go ahead with BC Models
or not (or whether we should go ahead with DS-TE or not). The "Weak
turnout" DID relate to just one of the many incremental steps that one
makes along the way, specifically : which of the two models should be
default and which should be optional (which is not the most exciting
decision we ever had to make).
For such a decision, I'd say a turnout of 9 is quite usual (even if far
from ideal) as compared to other turnout for that sort of incremental
decisions in IETF.

So, I think we are now clear that the refered "Weak Turnout" is NOT a
reflection of interest in BC models (or of DSTE in general) but probably
a reflection of the fact that it is hard for all of us to closely follow
every incremental steps and sometimes difficult to get excited about
whether something is refered to as Default or as Optional.

Still, I understand your valid concern for making sure that the WGs are
working on something useful. 
With respect to DSTE, this is something we've obviously debated in the
TEWG, BEFORE starting the work on DSTE. It was kind of a "hot topic".
For memory, here's (my recollection of) what we concluded:
	- while this is not expected to apply to the majority of
networks, there is a sufficient base of operators interested in the
technology and wanting to have it standardised. Thus, the corresponding
item of work was incorporated in the TEWG charter.
	- a DSTE-reqts document was to be produced to clarify (i) what
these operators want to do and (ii) if/why existing mechanisms are not
sufficient
	- if existing mechanisms are not sufficient, develop necessary
extensions.
This is what we have been doing over the last two years.

With respect to level of interest in DSTE, you may have noticed that
this topic amounted to the majority of the exchanges on the TEWG list
and of the discussions at TEWG meetings. Without doing the actual name
count, I'd guess that more than 25 people have been involved authoring
I-Ds, contributing or making detailed comments about DS-TE. This
includes major SPs.
For what it is worth, there are also implementations of this technology
today (which don't interwork for lack of standards).

There is no dispute that this technology is of no applicability to
some/many environments. And this explains why this question of "should
we really be working on DSTE" comes up occasionaly.
But at the same time, it is of applicability to other environments and
justifies the corresponding work. 
Having a "Weak turnout" on how to reference model_A vs model_B, does not
seem to be in contradiction with that. Having a number of SPs confirming
DSTE is not applicable to their environments does not seem to contradict
that either.


Cheers

Francois


>> 
>> At 00:56 03/01/23 +0100, Wijnen, Bert (Bert) wrote:
>> >Thank you very much Vijay. That was/is exactly what I worry about.
>> >If not enough people (and 10 is the absolute minumum, but 
>> having seen
>> >the attendence of TWEG sessions, I'd expect 25 or more) can speak up
>> >to state one of:
>> >
>> >  - I read it and I am positive, it is good stuff
>> >  - I read it and I see no problems or objections
>> >  - I read it but I cannot determine if it is bad, but I 
>> can see that
>> >    what has been discussed in the WG is indeed in the document
>> >  - I read it and I have these nits/objections...
>> >  - I did not read it cause this is not relevant to my xxx 
>> job/work/function
>> >  - I did not read it cause I think this is nonsense
>> >
>> >Then I get the feeling that we're just allowing a small group of
>> >people push their petty-project through the process. That seems NOT
>> >good to me. We need serious WG participation in reading and 
>> commenting
>> >in one of these forums above, before we can declare that we have WG
>> >consensus on a document to be presented to IESG for approval as RFC
>> >(in whatever form).
>> >
>> >Bert
>> 
>> ******************************
>> Nagao Ogino, Dr. Eng.
>> KDDI R & D Laboratories Inc.
>> 2-1-15 Ohara, Kamifukuoka-shi,
>> Saitama 356-8502 Japan
>> TEL   +81 49 278 7860
>> FAX   +81 49 278 7516
>> E-mail   ogino@kddilabs.jp
>> ****************************** 
>> 
>> 
>> 
>> 



From owner-te-wg@ops.ietf.org  Thu Jan 23 08:11:12 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06358
	for <tewg-archive@lists.ietf.org>; Thu, 23 Jan 2003 08:11:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18bh3l-000Gk8-00
	for te-wg-data@psg.com; Thu, 23 Jan 2003 05:06:21 -0800
Received: from ux2.ibb.net ([62.8.32.147])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18bh3h-000Gji-00
	for te-wg@ops.ietf.org; Thu, 23 Jan 2003 05:06:18 -0800
Received: from ttz505ls (unknown-237-UK.globalcrossing.com [195.166.116.237])
	by ux2.ibb.net (8.11.3/8.11.3/UX2TT) with SMTP id h0ND6Ep14007
	for <te-wg@ops.ietf.org>; Thu, 23 Jan 2003 14:06:15 +0100 (MET)
Message-ID: <014b01c2c2e0$1bb67380$8602c90a@eur.gblxint.com>
From: "Thomas Telkamp" <telkamp@gblx.net>
To: "Te-Wg \(E-mail\)" <te-wg@ops.ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B155BAE369@nl0006exch001u.nl.lucent.com>
Subject: Re: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Thu, 23 Jan 2003 14:05:24 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Status: No, hits=2.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,RCVD_IN_RFCI,REFERENCES,
	      SPAM_PHRASE_02_03,USER_AGENT_OE
	version=2.43
X-Spam-Level: **
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


No objections, and suggest we move this forward.

---
Thomas


> Thank you very much Vijay. That was/is exactly what I worry about.
> If not enough people (and 10 is the absolute minumum, but having seen
> the attendence of TWEG sessions, I'd expect 25 or more) can speak up
> to state one of:
>
>  - I read it and I am positive, it is good stuff
>  - I read it and I see no problems or objections
>  - I read it but I cannot determine if it is bad, but I can see that
>    what has been discussed in the WG is indeed in the document
>  - I read it and I have these nits/objections...
>  - I did not read it cause this is not relevant to my xxx
job/work/function
>  - I did not read it cause I think this is nonsense
>
> Then I get the feeling that we're just allowing a small group of
> people push their petty-project through the process. That seems NOT
> good to me. We need serious WG participation in reading and commenting
> in one of these forums above, before we can declare that we have WG
> consensus on a document to be presented to IESG for approval as RFC
> (in whatever form).





From owner-te-wg@ops.ietf.org  Fri Jan 24 11:10: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 LAA23621
	for <tewg-archive@lists.ietf.org>; Fri, 24 Jan 2003 11:10:58 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18c6Lv-0009zV-00
	for te-wg-data@psg.com; Fri, 24 Jan 2003 08:06:47 -0800
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18c6Ls-0009yp-00
	for te-wg@ops.ietf.org; Fri, 24 Jan 2003 08:06:44 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0OFPKk1001418
	for <te-wg@ops.ietf.org>; Fri, 24 Jan 2003 10:06:04 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E018E277A; Fri, 24 Jan 2003 11:06:03 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Fri, 24 Jan 2003 11:06:02 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A1769B@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Weak turnout : was-> A proposal for moving ahead on BC models
Thread-Index: AcLCdFWpadInh2+oQH2pGfE0ejCvfQBR7K7Q
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Angela Chiu" <chiu@research.att.com>,
        "Fang, Luyuan, ALABS" <luyuanfang@att.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03,SUPERLONG_LINE
	version=2.43
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 LAA23621

Bert,

> If not enough people (and 10 is the absolute minimum, but having seen
> the attendance of TEWG sessions, I'd expect 25 or more) can speak up
> to state one of:
> 
>  - I read it and I am positive, it is good stuff
>  - I read it and I see no problems or objections
>  - I read it but I cannot determine if it is bad, but I can see that
>    what has been discussed in the WG is indeed in the document
>  - I read it and I have these nits/objections...
>  - I did not read it cause this is not relevant to my xxx 
> job/work/function
>  - I did not read it cause I think this is nonsense

Can you clarify if you're asking for us to vote/comment on something, and if so, what?

The 'weak turnout' comments were in regard to the BC model references, and I think Francois explained that there has been much discussion of that topic along the way.  As you might recall, at least 30-40 people 'voted' on this issue at the Atlanta meeting.  Why there were few comments in the last iteration on this discussion is unclear.
 
Are you perhaps asking us to reaffirm interest in DSTE, and if so, why?  

I believe the 'weak turnout' discussion may have gotten a bit confused between a BC model reference discussion and DSTE requirements updates in response to IESG comments.  Many people have commented on the DSTE requirements draft, clearly many have read it several times.  The requirements draft has just been through IESG review, and that's what is being discussed, right?  There are various changes that Francois seems to have resolved with you.  My assumption is that Francois and Wai Sum will now make the proposed changes, and re-submit the DSTE requirements draft to the IESG, correct?

Please clarify if you are asking for TEWG members to comment on anything further.

Thanks,
Jerry 




From owner-te-wg@ops.ietf.org  Fri Jan 24 12:36:25 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25917
	for <tewg-archive@lists.ietf.org>; Fri, 24 Jan 2003 12:36:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18c7lY-000CMY-00
	for te-wg-data@psg.com; Fri, 24 Jan 2003 09:37:20 -0800
Received: from sj-msg-core-3.cisco.com ([171.70.157.152])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18c7lU-000CLO-00
	for te-wg@ops.ietf.org; Fri, 24 Jan 2003 09:37:16 -0800
Received: from toque.cisco.com (IDENT:mirapoint@toque.cisco.com [161.44.201.11])
	by sj-msg-core-3.cisco.com (8.12.2/8.12.6) with ESMTP id h0OHaVB6012428;
	Fri, 24 Jan 2003 09:36:31 -0800 (PST)
Received: from msiva-w2k01.cisco.com (dhcp-kta1-10-85-24-44.cisco.com [10.85.24.44])
	by toque.cisco.com (Mirapoint)
	with ESMTP id AFC10721;
	Fri, 24 Jan 2003 12:28:02 -0500 (EST)
Message-Id: <4.3.2.7.2.20030124123154.0390ac50@toque.cisco.com>
X-Sender: msiva@toque.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 24 Jan 2003 12:36:33 -0500
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
From: "Siva Sivabalan (msiva)" <msiva@cisco.com>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
  models
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Angela Chiu" <chiu@research.att.com>,
        "Fang, Luyuan, ALABS" <luyuanfang@att.com>,
        "Lai, Wai S (Waisum), ALABS" <wlai@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
In-Reply-To: <28F05913385EAC43AF019413F674A01704A1769B@OCCLUST04EVS1.ugd
 .att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


I have followed DS-TE requirements and protocol development very closely, and
feel that "it is good stuff" and should be moving on.


Thanks,

Siva

At 11:06 AM 1/24/2003 -0500, Ash, Gerald R (Jerry), ALABS wrote:
>Bert,
>
> > If not enough people (and 10 is the absolute minimum, but having seen
> > the attendance of TEWG sessions, I'd expect 25 or more) can speak up
> > to state one of:
> >
> >  - I read it and I am positive, it is good stuff
> >  - I read it and I see no problems or objections
> >  - I read it but I cannot determine if it is bad, but I can see that
> >    what has been discussed in the WG is indeed in the document
> >  - I read it and I have these nits/objections...
> >  - I did not read it cause this is not relevant to my xxx
> > job/work/function
> >  - I did not read it cause I think this is nonsense
>
>Can you clarify if you're asking for us to vote/comment on something, and 
>if so, what?
>
>The 'weak turnout' comments were in regard to the BC model references, and 
>I think Francois explained that there has been much discussion of that 
>topic along the way.  As you might recall, at least 30-40 people 'voted' 
>on this issue at the Atlanta meeting.  Why there were few comments in the 
>last iteration on this discussion is unclear.
>
>Are you perhaps asking us to reaffirm interest in DSTE, and if so, why?
>
>I believe the 'weak turnout' discussion may have gotten a bit confused 
>between a BC model reference discussion and DSTE requirements updates in 
>response to IESG comments.  Many people have commented on the DSTE 
>requirements draft, clearly many have read it several times.  The 
>requirements draft has just been through IESG review, and that's what is 
>being discussed, right?  There are various changes that Francois seems to 
>have resolved with you.  My assumption is that Francois and Wai Sum will 
>now make the proposed changes, and re-submit the DSTE requirements draft 
>to the IESG, correct?
>
>Please clarify if you are asking for TEWG members to comment on anything 
>further.
>
>Thanks,
>Jerry




From owner-te-wg@ops.ietf.org  Fri Jan 24 13:11:54 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27091
	for <tewg-archive@lists.ietf.org>; Fri, 24 Jan 2003 13:11:54 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18c8Kx-000DBc-00
	for te-wg-data@psg.com; Fri, 24 Jan 2003 10:13:55 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18c8Kt-000DAq-00
	for te-wg@ops.ietf.org; Fri, 24 Jan 2003 10:13:52 -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 h0OHepKP009680
	for <te-wg@ops.ietf.org>; Fri, 24 Jan 2003 13:13:19 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E018F61E0; Fri, 24 Jan 2003 13:13:06 -0500
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Subject: RE: WG Last Call :  draft-ietf-tewg-measure-04.txt
Date: Fri, 24 Jan 2003 13:12:53 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704CB86E8@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: WG Last Call :  draft-ietf-tewg-measure-04.txt
Thread-Index: AcK/bXew6ucbzrE4Romcpd+RWsGjBwEZSoHQ
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=0.2 required=5.0
	tests=EMAIL_ATTRIBUTION,QUOTED_EMAIL_TEXT,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02
	version=2.43
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 NAA27091

Jim,

The draft is on-target and satisfies this important TEM charter-milestone.  

I've reviewed it numerous times, and all my comments to the authors have been incorporated.  The latest update/comments from Merike further strengthen the draft.

I hope others read and comment, as many said they would at the TEWG meeting in Atlanta,

Thanks,
Jerry

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Saturday, January 18, 2003 10:40 PM
To: te-wg@ops.ietf.org
Subject: WG Last Call : draft-ietf-tewg-measure-04.txt

This draft has definitely honed itself to its purpose from its earliest 
versions.  However it never appears to get wide comment or show of hands 
of folks that have reviewed it. 

So... Please do so.

I'll give us 3 weeks for folks to comment along these lines.

1) is this draft on-target for the TE measurements milestone we have in 
   our charter?  If you think it is off-target I would be interested 
   in hearing how we should deal with this portion of our charter.

2) minor / editorial comments to list and/or author

3) substantial comments to list

Last call will end February 7.

thanks!

Jim Boyle












On Fri, 10 Jan 2003 Internet-Drafts@ietf.org wrote:

> 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		: A Framework for Internet Traffic Engineering 
>                           Measurement
> 	Author(s)	: W. Lai, R. Tibbs, S. Van den Berghe
> 	Filename	: draft-ietf-tewg-measure-04.txt
> 	Pages		: 26
> 	Date		: 2003-1-10
> 	
> In this document, a measurement framework for supporting the traffic 
> engineering of IP-based networks is presented.  Uses of traffic 
> measurement in service provider environments are described, and 
> issues related to time scale and read-out period are discussed.  
> Different measurement types are classified, with each being 
> specified as a meaningful combination of a measurement entity and a 
> measurement basis. 
> For interoperable compatibility, uniform definitions across vendors 
> and operators must be ensured, e.g., in the distinction between 
> offered load and achieved throughput.  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.  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.  To manage large volume of measured data, use 
> of bulk transfer and filtering/aggregation mechanisms may be 
> appropriate.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-04.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-tewg-measure-04.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-tewg-measure-04.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 





From owner-te-wg@ops.ietf.org  Fri Jan 24 15:26: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 PAA01491
	for <tewg-archive@lists.ietf.org>; Fri, 24 Jan 2003 15:26:04 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18cAO4-000JiE-00
	for te-wg-data@psg.com; Fri, 24 Jan 2003 12:25:16 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18cAO1-000Jhx-00
	for te-wg@ops.ietf.org; Fri, 24 Jan 2003 12:25:14 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h0OKP7uD000100;
	Fri, 24 Jan 2003 20:25:08 GMT
Received: from zhangr2.info.net (sfjl13.us.info.net [204.79.139.13])
	by delta.info.net  with ESMTP id UAA24046;
	Fri, 24 Jan 2003 20:25:06 GMT
Message-Id: <5.1.0.14.0.20030124120935.027a0fd0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Fri, 24 Jan 2003 12:25:01 -0800
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, Vijay Gill <vijay@umbc.edu>
From: raymond zhang <zhangr@info.net>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC
  models
Cc: "Thomas D. Nadeau" <tnadeau@cisco.com>, te-wg@ops.ietf.org
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE369@nl0006exch001u.nl.l
 ucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-1.1 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi,

I've discussed quite a bit with Francois on this draft in many occasions 
and clarified my understanding of draft in which we have a key interest to 
deploy such a solution over our global network.  I thought there were a lot 
of discussions took place at Atlanta meeting as well.  No objections and 
recommend that we move forward with this...

Regards,
Raymond

At 12:56 AM 1/23/2003 +0100, Wijnen, Bert (Bert) wrote:
>Vijay writes:
>
> > On Wed, 22 Jan 2003, Wijnen, Bert (Bert) wrote:
> >
> > > Maybe it is just your (stupid) AD who does not understand
> > > how it is possible that these days we seem to only be
> > > able to get VERY FEW people to speak up (pro or against
> > > or even declaring a don't care) when WG chairs ask for
> > > opinions to try and gauge consensus. How are they
> > > expected to read if teh WG indeed has consensus on anything?
> >
> > While I can't speak for others, I tend to only read on issues
> > I feel are relevant to my day job because of job load.
> > Some of the proposals put forward are a waste of time
> > (for my network requirements),  ergo, I do not bother reading
> > or commenting on them.  Others may be in the same boat.
> >
> > In this case, silence does NOT mean consent.
> >
>Thank you very much Vijay. That was/is exactly what I worry about.
>If not enough people (and 10 is the absolute minumum, but having seen
>the attendence of TWEG sessions, I'd expect 25 or more) can speak up
>to state one of:
>
>  - I read it and I am positive, it is good stuff
>  - I read it and I see no problems or objections
>  - I read it but I cannot determine if it is bad, but I can see that
>    what has been discussed in the WG is indeed in the document
>  - I read it and I have these nits/objections...
>  - I did not read it cause this is not relevant to my xxx job/work/function
>  - I did not read it cause I think this is nonsense
>
>Then I get the feeling that we're just allowing a small group of
>people push their petty-project through the process. That seems NOT
>good to me. We need serious WG participation in reading and commenting
>in one of these forums above, before we can declare that we have WG
>consensus on a document to be presented to IESG for approval as RFC
>(in whatever form).
>
>Bert
> > /vijay
> >
> >
> >





From owner-te-wg@ops.ietf.org  Fri Jan 24 16:07:17 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02485
	for <tewg-archive@lists.ietf.org>; Fri, 24 Jan 2003 16:07:16 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18cB23-000FLw-00
	for te-wg-data@psg.com; Fri, 24 Jan 2003 13:06:35 -0800
Received: from mail.ee.gatech.edu ([130.207.225.105])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18cB1z-000FLH-00
	for te-wg@ops.ietf.org; Fri, 24 Jan 2003 13:06:31 -0800
Received: from hugoboss.ece.gatech.edu (hugoboss.ece.gatech.edu [199.77.155.31])
	by mail.ee.gatech.edu (8.12.3/8.12.3) with ESMTP id h0OL6RlC022763;
	Fri, 24 Jan 2003 16:06:27 -0500 (EST)
Received: from localhost (jau@localhost)
	by hugoboss.ece.gatech.edu (8.12.0.Beta19/8.12.0.Beta19/Submit) with ESMTP id h0OL6Rxp009447;
	Fri, 24 Jan 2003 16:06:27 -0500 (EST)
Date: Fri, 24 Jan 2003 16:06:27 -0500 (EST)
From: Jaudelice Cavalcante de Oliveira <jau@ece.gatech.edu>
To: te-wg@ops.ietf.org
cc: Jaudelice Cavalcante deOliveira <jau@ece.gatech.edu>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC  models
Message-ID: <Pine.GSO.4.50.0301241603250.29540-100000@hugoboss.ece.gatech.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
X-Spam-Status: No, hits=-0.9 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02,USER_AGENT_PINE
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Hi,

I have followed DS-TE requirements and protocol development very closely.
I feel that Francois' proposal of not mandating a default model in
diff-te-proto and updating diff-te-reqts to reflect the same, and to
document RDM, MAM, and whatever other model that may be developed in the
future, as standards track RFCs is the way to go.

I want to add a few comments, even though I know we are not discussing the
importance of diff-te-reqts and diff-te-proto.

diff-te-reqts (and also more recently diff-te-proto) has been read,
commented, used and referred to by many researchers. I myself have
proposed a preemption policy (following diff-te-reqts), which used RDM as
BC model, and was published and presented at INFOCOM 2002.

As a reviewer of papers submitted to IEEE conferences, I have seen the
growing interest in DSTE related topics (impossible to count how many
authors cite diff-te-reqts and diff-te-proto) and also particularly in
preemption, although I can only speak from the research community point of
view.

Regards,
Jaudelice.

>Thank you very much Vijay. That was/is exactly what I worry about.
>If not enough people (and 10 is the absolute minumum, but having seen
>the attendence of TWEG sessions, I'd expect 25 or more) can speak up
>to state one of:
>
>  - I read it and I am positive, it is good stuff
>  - I read it and I see no problems or objections
>  - I read it but I cannot determine if it is bad, but I can see that
>    what has been discussed in the WG is indeed in the document
>  - I read it and I have these nits/objections...
>  - I did not read it cause this is not relevant to my xxx
job/work/function
>  - I did not read it cause I think this is nonsense
>
>Then I get the feeling that we're just allowing a small group of
>people push their petty-project through the process. That seems NOT
>good to me. We need serious WG participation in reading and commenting
>in one of these forums above, before we can declare that we have WG
>consensus on a document to be presented to IESG for approval as RFC
>(in whatever form).
>
>Bert


______________________________________________
Jaudelice Cavalcante de Oliveira
Broadband and Wireless Networking Laboratory
Georgia Institute of Technology
School of Electrical an Computer Engineering
Phone: (404) 8946616 ~ FAX: (404) 894-7883
http://www.ece.gatech.edu/~jau





From owner-te-wg@ops.ietf.org  Fri Jan 24 16:48: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 QAA03442
	for <tewg-archive@lists.ietf.org>; Fri, 24 Jan 2003 16:48:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18cBi5-000PPm-00
	for te-wg-data@psg.com; Fri, 24 Jan 2003 13:50:01 -0800
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #2)
	id 18cBi1-000PPD-00
	for te-wg@ops.ietf.org; Fri, 24 Jan 2003 13:49:57 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0OLnWx29452
	for <te-wg@ops.ietf.org>; Fri, 24 Jan 2003 16:49:33 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <YJ269STL>; Fri, 24 Jan 2003 22:49:31 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE8DA@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: te-wg@ops.ietf.org, Angela Chiu <chiu@research.att.com>,
        "Fang, Luyuan, ALABS" <luyuanfang@att.com>,
        "Lai, Wai S (Waisum), ALABS"
	 <wlai@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
Subject: RE: Weak turnout : was-> A proposal for moving ahead on BC models
Date: Fri, 24 Jan 2003 22:49:14 +0100
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=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Inline
> > If not enough people (and 10 is the absolute minimum, but having seen
> > the attendance of TEWG sessions, I'd expect 25 or more) can speak up
> > to state one of:
> > 
> >  - I read it and I am positive, it is good stuff
> >  - I read it and I see no problems or objections
> >  - I read it but I cannot determine if it is bad, but I can see that
> >    what has been discussed in the WG is indeed in the document
> >  - I read it and I have these nits/objections...
> >  - I did not read it cause this is not relevant to my xxx 
> >    job/work/function
> >  - I did not read it cause I think this is nonsense
> 
> Can you clarify if you're asking for us to vote/comment on 
> something, and if so, what?
> 
I am not specifically asking to vote/comment on anything
specifically. I am trying to let the WG members know that
we (that is the editors/authors, the WG chairs, teh ADs, the IETF)
need the members to participate ans help us get the best
specifications out of the WG. That can only happen if people
indeed read and if they comment in one of the ways I suggested.

Imagine if you were a WG chair, how would you gauge consensus
if there are just a few people speaking up on any topic.
Would you not love to get 100s of responses posted that
make a statement that they read the issue/document/mail and
that they feel it is good stuff or that they don;t care or
that they have concerns about x,y or z etc..

> The 'weak turnout' comments were in regard to the BC model 
> references, and I think Francois explained that there has 
> been much discussion of that topic along the way.  As you 
> might recall, at least 30-40 people 'voted' on this issue at 
> the Atlanta meeting.  Why there were few comments in the last 
> iteration on this discussion is unclear.
>  
We also all know that final WG consensus is sought on the WG
mailing list. So when teh WG chairs have a record of some
40 or so hands raised at a WG f2f meeting that people are happy
with solution/proposal x. Then they can include that in the
posting in which they ask for WG opinions/consensus, and so
the 40 do then count (if any of those change their mind
based on discussions on the list or for whatever reason,
they can also post that they changed their mind).

As Vijay said... SILENCE is not consent.

> Are you perhaps asking us to reaffirm interest in DSTE, and 
> if so, why?  
> 
I ask WG members, as many as possible to participate in all
discussions. If they speak up and say:
  This particial topic is not improtant and I can live
  with any resolution that other members present... 
then we know at least that. I do not know how to interpret
SILENECE. Do you ??

> I believe the 'weak turnout' discussion may have gotten a bit 
> confused between a BC model reference discussion and DSTE 
> requirements updates in response to IESG comments.  Many 
> people have commented on the DSTE requirements draft, clearly 
> many have read it several times.  The requirements draft has 
> just been through IESG review, and that's what is being 
> discussed, right?  There are various changes that Francois 
> seems to have resolved with you.  My assumption is that 
> Francois and Wai Sum will now make the proposed changes, and 
> re-submit the DSTE requirements draft to the IESG, correct?
> 
That is what I heard.

> Please clarify if you are asking for TEWG members to comment 
> on anything further.
> 
Sorry of I made people think that I was picking on a specific 
topic. I was picking the "we have a turnout of 8 or so" as
a handle to try and motivate people to speak up and let their
opinion (positive, negative, indifferent) be known. And we 
best hear it on the list. I'd rather see someone state it
twice than keeping silence.

Hope this explains.

I see that several people are now starting to speak up.
I like that.

Bert
> Thanks,
> Jerry 
> 



From owner-te-wg@ops.ietf.org  Sat Jan 25 08:52: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 IAA24274
	for <tewg-archive@lists.ietf.org>; Sat, 25 Jan 2003 08:52:47 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #2)
	id 18cQX5-000GOP-00
	for te-wg-data@psg.com; Sat, 25 Jan 2003 05:39:39 -0800
Received: from byd.ocn.ad.jp ([203.139.162.147])
	by psg.com with esmtp (Exim 3.36 #2)
	id 18cQX1-000GOB-00
	for te-wg@ops.ietf.org; Sat, 25 Jan 2003 05:39:35 -0800
Received: from ibm (localhost [127.0.0.1])
	by byd.ocn.ad.jp (8.8.8/3.6W) with ESMTP id WAA14311
	for <te-wg@ops.ietf.org>; Sat, 25 Jan 2003 22:39:34 +0900 (JST)
Date: Sat, 25 Jan 2003 22:41:35 +0900
From: Yuichi Ikejiri <y.ikejiri@ntt.com>
To: te-wg@ops.ietf.org
Subject: Re: Weak turnout : was-> A proposal for moving ahead on BC  models
In-Reply-To: <Pine.GSO.4.50.0301241603250.29540-100000@hugoboss.ece.gatech.edu>
References: <Pine.GSO.4.50.0301241603250.29540-100000@hugoboss.ece.gatech.edu>
Message-Id: <20030125222201.088A.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=-2.9 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, 

On Fri, 24 Jan 2003 16:06:27 -0500 (EST)
Jaudelice Cavalcante de Oliveira <jau@ece.gatech.edu> wrote:

> 
> Hi,
> 
> I have followed DS-TE requirements and protocol development very closely.
> I feel that Francois' proposal of not mandating a default model in
> diff-te-proto and updating diff-te-reqts to reflect the same, and to
> document RDM, MAM, and whatever other model that may be developed in the
> future, as standards track RFCs is the way to go.
I have the same opinion too.

I think that DS-TE has many applicablity from our perspective as one of
SPs. Therefore I strongly hope that things move on and reach the standard
as soon as possible.

Regards, 
Yuichi Ikejiri
NTT Communications Corp.

> 
> I want to add a few comments, even though I know we are not discussing the
> importance of diff-te-reqts and diff-te-proto.
> 
> diff-te-reqts (and also more recently diff-te-proto) has been read,
> commented, used and referred to by many researchers. I myself have
> proposed a preemption policy (following diff-te-reqts), which used RDM as
> BC model, and was published and presented at INFOCOM 2002.
> 
> As a reviewer of papers submitted to IEEE conferences, I have seen the
> growing interest in DSTE related topics (impossible to count how many
> authors cite diff-te-reqts and diff-te-proto) and also particularly in
> preemption, although I can only speak from the research community point of
> view.
> 
> Regards,
> Jaudelice.
> 
> >Thank you very much Vijay. That was/is exactly what I worry about.
> >If not enough people (and 10 is the absolute minumum, but having seen
> >the attendence of TWEG sessions, I'd expect 25 or more) can speak up
> >to state one of:
> >
> >  - I read it and I am positive, it is good stuff
> >  - I read it and I see no problems or objections
> >  - I read it but I cannot determine if it is bad, but I can see that
> >    what has been discussed in the WG is indeed in the document
> >  - I read it and I have these nits/objections...
> >  - I did not read it cause this is not relevant to my xxx
> job/work/function
> >  - I did not read it cause I think this is nonsense
> >
> >Then I get the feeling that we're just allowing a small group of
> >people push their petty-project through the process. That seems NOT
> >good to me. We need serious WG participation in reading and commenting
> >in one of these forums above, before we can declare that we have WG
> >consensus on a document to be presented to IESG for approval as RFC
> >(in whatever form).
> >
> >Bert
> 
> 
> ______________________________________________
> Jaudelice Cavalcante de Oliveira
> Broadband and Wireless Networking Laboratory
> Georgia Institute of Technology
> School of Electrical an Computer Engineering
> Phone: (404) 8946616 ~ FAX: (404) 894-7883
> http://www.ece.gatech.edu/~jau
> 
> 
> 





From owner-te-wg@ops.ietf.org  Sat Jan 25 12:03:23 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25857
	for <tewg-archive@lists.ietf.org>; Sat, 25 Jan 2003 12:03:23 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18cTaM-000OWr-00
	for te-wg-data@psg.com; Sat, 25 Jan 2003 08:55:14 -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 #2)
	id 18cTaJ-000OTD-00
	for te-wg@ops.ietf.org; Sat, 25 Jan 2003 08:55:11 -0800
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.5/8.12.5) with ESMTP id h0PGscs9000744;
	Sat, 25 Jan 2003 11:54:38 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.5/8.12.5/Submit) with ESMTP id h0PGqZeJ012621;
	Sat, 25 Jan 2003 11:52:38 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Sat, 25 Jan 2003 11:52:35 -0500 (EST)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: RE: Weak turnout : FINAL COMMENT (? :)
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155BAE8DA@nl0006exch001u.nl.lucent.com>
Message-ID: <Pine.LNX.4.44.0301251144420.32553-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,SPAM_PHRASE_00_01,USER_AGENT_PINE,X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


I think we've discussed an important topic.  We have over a lots of people 
on this list, we should have a good participation on subjects such as 
revision of drafts that have past last call and are with the IESG, or 
drafts that are in last call.  Even for drafts that are earlier in the 
development cycle, more perspective is a good thing.

That said, reminder:  draft-ietf-tewg-measurement-04.txt is currently 
under last call until Feb 7th.  

thanks,

Jim




From owner-te-wg@ops.ietf.org  Mon Jan 27 17:46:53 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29728
	for <tewg-archive@lists.ietf.org>; Mon, 27 Jan 2003 17:46:52 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18dHyq-000CvZ-00
	for te-wg-data@psg.com; Mon, 27 Jan 2003 14:43:52 -0800
Received: from f87.law10.hotmail.com ([64.4.15.87] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18dHyo-000CvM-00
	for te-wg@ops.ietf.org; Mon, 27 Jan 2003 14:43:50 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 27 Jan 2003 14:36:06 -0800
Received: from 206.47.0.171 by lw10fd.law10.hotmail.msn.com with HTTP;
	Mon, 27 Jan 2003 22:36:06 GMT
X-Originating-IP: [206.47.0.171]
From: "Ting Chung" <twchungca@hotmail.com>
To: te-wg@ops.ietf.org
Date: Mon, 27 Jan 2003 17:36:06 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F870QUUBPcZi71mrvoG00000142@hotmail.com>
X-OriginalArrivalTime: 27 Jan 2003 22:36:06.0258 (UTC) FILETIME=[7AFA6D20:01C2C654]
X-Spam-Status: No, hits=1.1 required=5.0
	tests=SPAM_PHRASE_00_01,SUBJ_MISSING
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


I would like to express my opinion in supporting the suggestion to adopt 
this draft as a WG draft document. Recently, my company has been working 
closely with other service providers to set up Inter-AS MPLS VPN 
connections. To enable inter-service provider QoS support, there are 
currently only limited number of tools available and most of them are at 
best interim steps toward a complete solution. The draft highlights a number 
of scenarios that match exactly our requirements and hence I believe the WG 
should allow further contributions of efforts so that this draft can be 
further developed to serve this community.



new version: draft-zhang-mpls-interas-te-req-01.txt

--------------------------------------------------------------------------------

To: te-wg@ops.ietf.org
Subject: new version: draft-zhang-mpls-interas-te-req-01.txt
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Date: Fri, 20 Dec 2002 13:39:28 -0500

--------------------------------------------------------------------------------
Hi,

First of all, thanks for the various comments we received and that are now 
integrated in the version -01 of the inter-AS TE requirements draft (just 
posted: 
http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-01.txt). 
Some other Service Providers will join the draft in the next release. Your 
comments on the list are very welcome.

Thanks.

JP.





Ting Wo Chung
Senior Network Architect, IP Technology, Bell Canada
181 Bay Street, Suite 350, Toronto, Canada, M5J2T3
Tel : 416-353-0741        Fax : 416-350-2148





_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*.  
http://join.msn.com/?page=features/featuredemail




From owner-te-wg@ops.ietf.org  Tue Jan 28 08:49:42 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25810
	for <tewg-archive@lists.ietf.org>; Tue, 28 Jan 2003 08:49:42 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18dW4x-000LmF-00
	for te-wg-data@psg.com; Tue, 28 Jan 2003 05:47:07 -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 18dW4v-000Lm3-00
	for te-wg@ops.ietf.org; Tue, 28 Jan 2003 05:47:05 -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 h0SCwdN5005876
	for <te-wg@ops.ietf.org>; Tue, 28 Jan 2003 08:47:03 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01AEE16E for te-wg@ops.ietf.org; Tue, 28 Jan 2003 08:47:03 -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="us-ascii"
Subject: RE: WG Last Call :  draft-ietf-tewg-measure-04.txt
Date: Tue, 28 Jan 2003 08:47:01 -0500
Message-ID: <28F05913385EAC43AF019413F674A017044A34B2@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: WG Last Call :  draft-ietf-tewg-measure-04.txt
Thread-Index: AcK/uinb1vof2Um4SvK7bfESEE06TQBlEg4g
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=1.8 required=5.0
	tests=QUOTED_EMAIL_TEXT,SEARCH_ENGINE_PROMO,SPAM_PHRASE_01_02
	version=2.43
X-Spam-Level: *
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 IAA25810

Dimitri,
  Many thanks for your comment on our draft.  Based on our
discusssion, to clarify the intent of the quoted paragraph (in
Section 5.3) below, we are going to add right after it the
following text:

(An example of such a feedback mechanism is described in [Ref].
As described therein, care should be exercised to ensure network
stability and consistency for any mechanism that makes direct
operational use of measurement (e.g., to use as feedback into path
computation).  However, such issues will not be dealt with here
as this framework document is mainly concerned with the definitions
and principles of measurements, rather than their usage to
subsequently ensure other network features such as accurate
bandwidth allocation.)
[Ref] P. Ashwood-Smith, B. Jamoussi, D. Fedyk, and D. Skalecki,
"Improving Topology Data Base Accuracy with Label Switched Path
Feedback in Constraint Based Label Distribution Protocol,"
Internet-Draft, Work in Progress, November 2002.

Thanks, Wai Sum

-----Original Message-----
From: Dimitri.Papadimitriou@alcatel.be
[mailto:Dimitri.Papadimitriou@alcatel.be]
Sent: Sunday, January 19, 2003 7:39 AM
To: Jim Boyle
Cc: te-wg@ops.ietf.org
Subject: Re: WG Last Call : draft-ietf-tewg-measure-04.txt


jim, all,

in section 5.3, would it be possible to detail the
real scope behind the following paragraph:

"Providing a feedback mechanism in the reverse flow messaging of 
 RSVP-TE or CR-LDP signaling in MPLS to report on actual topology 
 state information such as link bandwidth availability."

more precisely, detail the relationship between "signalling
in mpls" and the report to "actual topology state information" 
since there are imho several ways to interpret the above 
sentence

thanks,
- dimitri.

Jim Boyle wrote:
> 
> This draft has definitely honed itself to its purpose from its
earliest
> versions.  However it never appears to get wide comment or show of
hands
> of folks that have reviewed it.
> 
> So... Please do so.
> 
> I'll give us 3 weeks for folks to comment along these lines.
> 
> 1) is this draft on-target for the TE measurements milestone we have
in
>    our charter?  If you think it is off-target I would be interested
>    in hearing how we should deal with this portion of our charter.
> 
> 2) minor / editorial comments to list and/or author
> 
> 3) substantial comments to list
> 
> Last call will end February 7.
> 
> thanks!
> 
> Jim Boyle
> 
> On Fri, 10 Jan 2003 Internet-Drafts@ietf.org wrote:
> 
> > 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           : A Framework for Internet Traffic Engineering
> >                           Measurement
> >       Author(s)       : W. Lai, R. Tibbs, S. Van den Berghe
> >       Filename        : draft-ietf-tewg-measure-04.txt
> >       Pages           : 26
> >       Date            : 2003-1-10
> >
> > In this document, a measurement framework for supporting the traffic
> > engineering of IP-based networks is presented.  Uses of traffic
> > measurement in service provider environments are described, and
> > issues related to time scale and read-out period are discussed.
> > Different measurement types are classified, with each being
> > specified as a meaningful combination of a measurement entity and a
> > measurement basis.
> > For interoperable compatibility, uniform definitions across vendors
> > and operators must be ensured, e.g., in the distinction between
> > offered load and achieved throughput.  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.  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.  To manage large volume of measured data, use
> > of bulk transfer and filtering/aggregation mechanisms may be
> > appropriate.
> >
> > A URL for this Internet-Draft is:
> > http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-04.txt
> >
> > To remove yourself from the IETF Announcement list, send a message
to
> > ietf-announce-request with the word unsubscribe in the body of the
message.
> >
> > Internet-Drafts are also available by anonymous FTP. Login with the
username
> > "anonymous" and a password of your e-mail address. After logging in,
> > type "cd internet-drafts" and then
> >       "get draft-ietf-tewg-measure-04.txt".
> >
> > A list of Internet-Drafts directories can be found in
> > http://www.ietf.org/shadow.html
> > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >
> > Internet-Drafts can also be obtained by e-mail.
> >
> > Send a message to:
> >       mailserv@ietf.org.
> > In the body type:
> >       "FILE /internet-drafts/draft-ietf-tewg-measure-04.txt".
> >
> > NOTE: The mail server at ietf.org can return the document in
> >       MIME-encoded form by using the "mpack" utility.  To use this
> >       feature, insert the command "ENCODING mime" before the "FILE"
> >       command.  To decode the response(s), you will need "munpack"
or
> >       a MIME-compliant mail reader.  Different MIME-compliant mail
readers
> >       exhibit different behavior, especially when dealing with
> >       "multipart" MIME messages (i.e. documents which have been
split
> >       up into multiple messages), so check your local documentation
on
> >       how to manipulate these messages.
> >
> >
> > Below is the data which will enable a MIME compliant mail reader
> > implementation to automatically retrieve the ASCII version of the
> > Internet-Draft.
> >

-- 
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  : Work: +32 3 2408491 - Home: +32 2 3434361




From owner-te-wg@ops.ietf.org  Tue Jan 28 09:18: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 JAA26366
	for <tewg-archive@lists.ietf.org>; Tue, 28 Jan 2003 09:18:26 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18dWag-000Mh8-00
	for te-wg-data@psg.com; Tue, 28 Jan 2003 06:19:54 -0800
Received: from f40.law10.hotmail.com ([64.4.15.40] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18dWaW-000Mgs-00
	for te-wg@ops.ietf.org; Tue, 28 Jan 2003 06:19:44 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 28 Jan 2003 06:17:33 -0800
Received: from 206.47.0.172 by lw10fd.law10.hotmail.msn.com with HTTP;
	Tue, 28 Jan 2003 14:17:33 GMT
X-Originating-IP: [206.47.0.172]
From: "Ting Chung" <twchungca@hotmail.com>
To: te-wg@ops.ietf.org
Subject: draft-zhang-mpls-interas-te-req-01.txt
Date: Tue, 28 Jan 2003 09:17:33 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F40HToG3ASeOxV2RQHt00001745@hotmail.com>
X-OriginalArrivalTime: 28 Jan 2003 14:17:33.0756 (UTC) FILETIME=[002697C0:01C2C6D8]
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Sorry, group, it is a resend since I pressed send before I have put in the 
subject title last time........

I would like to express my opinion in supporting the suggestion to adopt 
this draft as a WG draft document. Recently, my company has been working 
closely with other service providers to set up Inter-AS MPLS VPN 
connections. To enable inter-service provider QoS support, there are 
currently only limited number of tools available and most of them are at 
best interim steps toward a complete solution. The draft highlights a number 
of scenarios that match exactly our requirements and hence I believe the WG 
should allow further contributions of efforts so that this draft can be 
further developed to serve this community.



new version: draft-zhang-mpls-interas-te-req-01.txt

--------------------------------------------------------------------------------

To: te-wg@ops.ietf.org
Subject: new version: draft-zhang-mpls-interas-te-req-01.txt
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Date: Fri, 20 Dec 2002 13:39:28 -0500

--------------------------------------------------------------------------------
Hi,

First of all, thanks for the various comments we received and that are now 
integrated in the version -01 of the inter-AS TE requirements draft (just 
posted: 
http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-01.txt). 
Some other Service Providers will join the draft in the next release. Your 
comments on the list are very welcome.

Thanks.

JP.

Ting Wo Chung
Senior Network Architect, IP Technology, Bell Canada
181 Bay Street, Suite 350, Toronto, Canada, M5J2T3
Tel : 416-353-0741        Fax : 416-350-2148





_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*   
http://join.msn.com/?page=features/junkmail




From owner-te-wg@ops.ietf.org  Fri Jan 31 11:03:53 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10746
	for <tewg-archive@lists.ietf.org>; Fri, 31 Jan 2003 11:03:52 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18edan-000Fvb-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 08:00:37 -0800
Received: from f20.law10.hotmail.com ([64.4.15.20] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18edal-000FvP-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 08:00:35 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 31 Jan 2003 07:59:48 -0800
Received: from 206.47.0.172 by lw10fd.law10.hotmail.msn.com with HTTP;
	Fri, 31 Jan 2003 15:59:47 GMT
X-Originating-IP: [206.47.0.172]
From: "Ting Chung" <twchungca@hotmail.com>
To: te-wg@ops.ietf.org
Subject: draft-ietf-tewg-diff-te-reqts-06.txt
Date: Fri, 31 Jan 2003 10:59:47 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F20g800QT7MkpyWGH5j0000a30e@hotmail.com>
X-OriginalArrivalTime: 31 Jan 2003 15:59:48.0072 (UTC) FILETIME=[C7BA2E80:01C2C941]
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


As a service provider, we have looked at the DiffServ-TE (DS-TE) feature for 
awhile now. Back then, we are still struggling to find an application for 
these features, especially if we just confine ourselves to the Internet 
world of traffic which are mostly connectionless and best effort in nature. 
With the recent push of L2 over MPLS technologies, and our intention to 
utilize these L2 over MPLS technologies to reduce our wide area transport 
cost, we find the DS-TE can help us quite a lot during implementation of 
these plans.
In the normal IP world, traffic is connectionless in nature and packets 
transiting through the network does not usually have a fixed path. However, 
when tunneling L2 (in particular ATM) traffic over our MPLS backbone, the 
DS-TE can be used as a CAC-like mechanism to ensure the the LSP bandwidth 
that we are reserving through the network is being accounted for properly on 
the hopto-hop bases. For example, the bandwidth constraint concept 
introduced in the DS-TE can be used to ensure the amount reserved CBR type 
of LSP's does not exceed a certain percentage of the total link bandwidth. 
By setting up different LSP's for different classes of ATM traffic (CBR, VBR 
and UBR, etc.), the corresponding composition of the different classes of 
traffic and their respective overbooking ratio can be better managed and 
accounted for. Although this may be only a coarse way to simulate the 
traditional ATM CAC mechanism, but this can help to secure our first step 
towards ATM over MPLS implementation. In Canada, long haul bandwidth is 
still an expensive asset and the ability to overbook these long haul links 
by consolidating all the layer 2 and layer 3 services onto them and turning 
on QoS to differentiate the different types of traffic classes is crucial in 
helping us to lower our cost.

I therefore believe that it is worth spending efforts to further develop the 
DS-TE concepts and protocols.

Ting Wo Chung
Senior Network Architect, IP Technology, Bell Canada
181 Bay Street, Suite 350, Toronto, Canada, M5J2T3




_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail




From owner-te-wg@ops.ietf.org  Fri Jan 31 15:41:34 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18292
	for <tewg-archive@lists.ietf.org>; Fri, 31 Jan 2003 15:41:34 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18ehx3-0003ZR-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 12:39:53 -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 18ehx1-0003ZF-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 12:39:51 -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 h0VJu0Kk026182
	for <te-wg@ops.ietf.org>; Fri, 31 Jan 2003 15:39:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01CFC878; Fri, 31 Jan 2003 15:38:41 -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="us-ascii"
Subject: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Fri, 31 Jan 2003 15:38:41 -0500
Message-ID: <28F05913385EAC43AF019413F674A01702E5E019@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Weak turnout : FINAL COMMENT (? :)
Thread-Index: AcLElk0Rmd+kcarWToeJTh4Agt+N3AE0fkmA
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.43
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 PAA18292

Following on Jim's request, please review the TE Measurement draft,
which is currently under last call (terminates on Feb. 7).

About 20-30 people who attended the IETF-55 TEWG meeting indicated
that they planned to review the document when it went to last call.

Please indicate to the TEWG list that you have reviewed the document,
even if you have no comments of suggestions.

Thanks, Wai Sum

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Saturday, January 25, 2003 11:53 AM
To: te-wg@ops.ietf.org
Cc: Wijnen, Bert (Bert)
Subject: RE: Weak turnout : FINAL COMMENT (? :)



I think we've discussed an important topic.  We have over a lots of
people 
on this list, we should have a good participation on subjects such as 
revision of drafts that have past last call and are with the IESG, or 
drafts that are in last call.  Even for drafts that are earlier in the 
development cycle, more perspective is a good thing.

That said, reminder:  draft-ietf-tewg-measurement-04.txt is currently 
under last call until Feb 7th.  

thanks,

Jim





