From owner-te-wg@ops.ietf.org  Wed Jul  2 15:04:10 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06598
	for <tewg-archive@lists.ietf.org>; Wed, 2 Jul 2003 15:04:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19XmpJ-000MzQ-M6
	for te-wg-data@psg.com; Wed, 02 Jul 2003 18:59:33 +0000
Received: from [209.219.209.75] (helo=ckmso2.proxy.att.com)
	by psg.com with esmtp (Exim 4.14)
	id 19XmpE-000Mwd-VQ
	for te-wg@ops.ietf.org; Wed, 02 Jul 2003 18:59:29 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h62IwWoM022800
	for <te-wg@ops.ietf.org>; Wed, 2 Jul 2003 14:58:58 -0400
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EE9217C007A31F1; Wed, 2 Jul 2003 14:58:53 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C340CB.FE696B6A"
Subject: RE: I-D ACTION:draft-wlai-tewg-bcmodel-02.txt,.pdf
Date: Wed, 2 Jul 2003 13:58:58 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA137186@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-wlai-tewg-bcmodel-02.txt,.pdf
Thread-Index: AcM/B1wa3uJfbTZCRrGsqdBj3LIjgwAAl8Cw
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jing Shen" <jshen_cad@yahoo.com.cn>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=-12.0 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,HTML_10_20,HTML_FONT_COLOR_BLUE
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

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

Jing,
   Thanks for your query.
   As explained in the draft, the performance of BC models is evaluated =
in terms of the blocking/preemption of LSPs, and not that of packets.  =
Poisson assumption for LSP requests is therefore relevant.  Also as =
discussed in the draft, the erlang is used to reflect LSP utilization of =
a link (as a result of bandwidth allocation and not the traffic volume).
   By ignoring the effect of overbooking, we basically assume that all =
the LSPs within a class are multiplied by the same overbooking factor.  =
For simplicity and tractability, we assume that LSPs in each class =
behave similarly.
Thanks, Wai Sum

-----Original Message-----
From: Jing Shen [mailto:jshen_cad@yahoo.com.cn]
Sent: Monday, June 30, 2003 8:49 AM
To: te-wg@ops.ietf.org
Subject: Re: I-D ACTION:draft-wlai-tewg-bcmodel-02.txt,.pdf


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


Internet-Drafts@ietf.org wrote:

A New Internet-Draft is available from the on-line Internet-Drafts =
directories.


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

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

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

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

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

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


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

Send a message to:
mailserv@ietf.org.
In the body type:
"FILE /internet-drafts/draft-wlai-tewg-bcmodel-02.txt".

NOTE: The mail server at ietf.org can return the document in
MIME-encoded form by using the "mpack" utility. To use this
feature, insert the command "ENCODING mime" before the "FILE"
command. To decode the response(s), you will need "munpack" or
a MIME-compliant mail reader. Diff! erent MIME-compliant mail readers
exhibit different behavior, especially when dealing with
"multipart" MIME messages (i.e. documents which have been split
up into multiple messages), so check your local documentation on
how to manipulate these messages.


Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.




Jing Shen

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




  _____ =20

Do You Yahoo!?
=CD=F8=C1=B5=B5=C4=DA=B9=CA=CD=A3=BA=D5=E6=C7=E9=BB=B9=CA=C7=B7=C5=D7=DD=A3=
=BF =
<http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.surveys.yahoo.com/netlove>=
=20


------_=_NextPart_001_01C340CB.FE696B6A
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">


<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D479531513-30062003>Jing,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D479531513-30062003>&nbsp;&nbsp; Thanks for your =
query.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D479531513-30062003>&nbsp;&nbsp; As explained in the draft, the =
performance=20
of BC models is evaluated in terms of the blocking/preemption of LSPs, =
and not=20
that of packets.&nbsp; Poisson assumption for LSP requests is therefore=20
relevant.&nbsp; Also as discussed in the draft, the erlang is used to =
reflect=20
LSP utilization of&nbsp;a link (as a result of bandwidth allocation and =
not the=20
traffic volume).</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D479531513-30062003>&nbsp;&nbsp;&nbsp;By ignoring the effect of=20
overbooking, we basically assume that all the LSPs within a class are =
multiplied=20
by the same overbooking factor.&nbsp; For simplicity and tractability, =
we assume=20
that LSPs in each class behave similarly.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D479531513-30062003></SPAN></FONT><FONT color=3D#0000ff =
face=3DArial=20
size=3D2><SPAN class=3D479531513-30062003>Thanks, Wai =
Sum</SPAN></FONT></DIV>
<BLOCKQUOTE>
  <DIV align=3Dleft class=3DOutlookMessageHeader dir=3Dltr><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Jing Shen=20
  [mailto:jshen_cad@yahoo.com.cn]<BR><B>Sent:</B> Monday, June 30, 2003 =
8:49=20
  AM<BR><B>To:</B> te-wg@ops.ietf.org<BR><B>Subject:</B> Re: I-D=20
  ACTION:draft-wlai-tewg-bcmodel-02.txt,.pdf<BR><BR></DIV></FONT>
  <DIV>
  <DIV>My question:</DIV>
  <DIV>&nbsp;</DIV>
  <DIV>How does the assumpiton of Possion Arrival and Erlang measurement =
relates=20
  to real network senerion? </DIV>
  <DIV>&nbsp;</DIV>
  <DIV>Why does the draft states "This allows us to express link=20
  <BR>&nbsp;&nbsp; bandwidth usage simply in terms of the *number of=20
  simultaneously <BR>&nbsp;&nbsp; established LSPs*"?&nbsp; To my =
understanding,=20
  even overbooking is adopted BC should be interpreted as " the =
bandwidth=20
  utilized by special TC", because we could not assume every LSP has the =
same=20
  bandwidth requirement.</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><BR><BR><B><I>Internet-Drafts@ietf.org</I></B> wrote:</DIV>
  <BLOCKQUOTE=20
  style=3D"BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; =
PADDING-LEFT: 5px">A=20
    New Internet-Draft is available from the on-line Internet-Drafts=20
    directories.<BR><BR><BR>Title : Bandwidth Constraints Models for=20
    Diffserv-aware MPLS <BR>Traffic Engineering: Performance=20
    Evaluation<BR>Author(s) : W. Lai<BR>Filename :=20
    draft-wlai-tewg-bcmodel-02.txt,.pdf<BR>Pages : 18<BR>Date :=20
    2003-6-27<BR><BR>The Diffserv-aware MPLS Traffic Engineering =
Requirements=20
    RFCxxxx <BR>specifies the requirements and selection criteria for =
bandwidth=20
    <BR>constraints models. Two such models, the Maximum Allocation and =
the=20
    <BR>Russian Dolls, are described therein. This document complements=20
    <BR>RFCxxxx by describing in more details some of the selection =
criteria=20
    <BR>and their implications. Results of a performance evaluation of =
the=20
    <BR>two models are also included.<BR><BR>A URL for this =
Internet-Draft=20
    =
is:<BR>http://www.ietf.org/internet-drafts/draft-wlai-tewg-bcmodel-02.txt=
<BR><BR>To=20
    remove yourself ! from the IETF Announcement list, send a message to =

    <BR>ietf-announce-request with the word unsubscribe in the body of =
the=20
    message.<BR><BR>Internet-Drafts are also available by anonymous FTP. =
Login=20
    with the username<BR>"anonymous" and a password of your e-mail =
address.=20
    After logging in,<BR>type "cd internet-drafts" and then<BR>"get=20
    draft-wlai-tewg-bcmodel-02.txt".<BR><BR>A list of Internet-Drafts=20
    directories can be found in<BR>http://www.ietf.org/shadow.html =
<BR>or=20
    ftp://ftp.ietf.org/ietf/1shadow-sites.txt<BR><BR><BR>Internet-Drafts =
can=20
    also be obtained by e-mail.<BR><BR>Send a message=20
    to:<BR>mailserv@ietf.org.<BR>In the body type:<BR>"FILE=20
    /internet-drafts/draft-wlai-tewg-bcmodel-02.txt".<BR><BR>NOTE: The =
mail=20
    server at ietf.org can return the document in<BR>MIME-encoded form =
by using=20
    the "mpack" utility. To use this<BR>feature, insert the command =
"ENCODING=20
    mime" before the "FILE"<BR>command. To decode the response(s), you =
will need=20
    "munpack" or<BR>a MIME-compliant mail reader. Diff! erent =
MIME-compliant=20
    mail readers<BR>exhibit different behavior, especially when dealing=20
    with<BR>"multipart" MIME messages (i.e. documents which have been=20
    split<BR>up into multiple messages), so check your local =
documentation=20
    on<BR>how to manipulate these messages.<BR><BR><BR>Below is the data =
which=20
    will enable a MIME compliant mail reader<BR>implementation to =
automatically=20
    retrieve the ASCII version of=20
  the<BR>Internet-Draft.<BR></BLOCKQUOTE></DIV><BR><BR>Jing =
Shen<BR><BR>State=20
  Key Lab of CAD&amp;CG<BR>ZheJiang University(YuQuan)<BR>HangZhou, =
ZheJiang=20
  Province 310027<BR>P.R.China=20
  <P><BR>
  <HR SIZE=3D1>
  <B>Do You Yahoo!?</B><BR><A=20
  =
href=3D"http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.surveys.yahoo.com/n=
etlove">=CD=F8=C1=B5=B5=C4=DA=B9=CA=CD=A3=BA=D5=E6=C7=E9=BB=B9=CA=C7=B7=C5=
=D7=DD=A3=BF</A></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C340CB.FE696B6A--



From owner-te-wg@ops.ietf.org  Wed Jul  2 20:44: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 UAA06914
	for <tewg-archive@lists.ietf.org>; Wed, 2 Jul 2003 20:44:09 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19XsA3-000H76-Ca
	for te-wg-data@psg.com; Thu, 03 Jul 2003 00:41:19 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.14)
	id 19XsA0-000H6u-HD
	for te-wg@ops.ietf.org; Thu, 03 Jul 2003 00:41:16 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h630djtk023267;
	Thu, 3 Jul 2003 00:39:45 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id AAA14644;
	Thu, 3 Jul 2003 00:39:43 GMT
Message-Id: <5.2.0.9.2.20030702155839.0267b590@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 02 Jul 2003 17:39:39 -0700
To: Jean Philippe Vasseur <jvasseur@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
From: raymond zhang <zhangr@info.net>
Subject: RE: New I-D on inter-area (and inter-as) MPLS TE requirements
Cc: "Jim Boyle" <jboyle@pdnets.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
In-Reply-To: <4.3.2.7.2.20030628151331.068bd498@paris.cisco.com>
References: <9473683187ADC049A855ED2DA739ABCA0A6884@KCCLUST06EVS1.ugd.a tt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-25.2 required=5.0
	tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      REPLY_WITH_QUOTES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Jerry, JP and Jim,



At 12:52 PM 6/29/2003 -0400, Jean Philippe Vasseur wrote:
>Hi Jerry,
>
>At 11:23 AM 6/28/2003 -0500, Ash, Gerald R (Jerry), ALABS wrote:
>>JP,
>>
>> > >General comments:
>> > >I'm glad you're providing inter-area TE requirements.  I agree that both
>> > >inter-area TE and inter-AS TE should be progressed together, and 
>> would not
>> > >favor progressing inter-AS TE without also progressing inter-area TE.  It
>> > >would seem if a SP needed inter-AS TE, they would usually also need
>> > >inter-area TE.
>>
>> > Well no. I'm of course not against the idea of working on inter-area TE
>> > reqs but stating that the SPs that need Inter-AS TE also need 
>> inter-area is
>> > not correct. Several SPs have multiple ASes and single IGP area/level in
>> > each AS.
>>
>>Certainly not *all* SPs who have multiple AS's also have a single 
>>area/level in each (e.g., AT&T).
>
>sure this is why I said, "several" ;-) By the way, even if an SP have 
>both, this does not mean that they need both inter-area and inter-AS TE ?
>
>>   Further, George Swallow stated in an MPLS WG meeting that many SPs 
>> were requesting inter-area TE.  I'm glad that you agree with the need 
>> for both inter-area TE and inter-AS TE to be progressed.
>>
>> > the question on whether to combine the requirements of inter-area
>> > and inter-AS in the same document has been raised on the TEWG list and I
>> > think that there was a majority stating that there should be separate
>> > documents (NTT-C, EQUANT, FRANCE TELECOM, INFONET, SBC, ...).
>>
>>I also stated on the TEWG list that inter-area and inter-AS TE should be 
>>progressed separately, but in parallel.
>
>So we're in sync !

May be we can get together in Vienna to scope out some specifics on this 
parallel track ?

Cheers,
Raymond


>Fee free to provide your comments on the ET WG req of inter-AS TE.
>
>Thanks.
>
>JP.
>
>>So if you're associating individuals with SPs, you could also deduce 
>>'AT&T' in the above 'majority' list.  Others agreed that we should 
>>progress both in parallel.
>>
>>I'm glad that Jim restarted the inter-area TE requirements effort, which 
>>you and I and several others first initiated in TEWG a while back.
>>
>>Jerry
>





From owner-te-wg@ops.ietf.org  Wed Jul  2 22:50: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 WAA12045
	for <tewg-archive@lists.ietf.org>; Wed, 2 Jul 2003 22:50:15 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19Xu8j-000NKD-Hh
	for te-wg-data@psg.com; Thu, 03 Jul 2003 02:48:05 +0000
Received: from [202.3.77.137] (helo=web15207.mail.bjs.yahoo.com)
	by psg.com with smtp (Exim 4.14)
	id 19Xu6b-000NBN-QC
	for te-wg@ops.ietf.org; Thu, 03 Jul 2003 02:48:01 +0000
Message-ID: <20030703024512.1939.qmail@web15207.mail.bjs.yahoo.com>
Received: from [218.72.37.158] by web15207.mail.bjs.yahoo.com via HTTP; Thu, 03 Jul 2003 10:45:12 CST
Date: Thu, 3 Jul 2003 10:45:12 +0800 (CST)
From: =?gb2312?q?Jing=20Shen?= <jshen_cad@yahoo.com.cn>
Subject: RE: I-D ACTION:draft-wlai-tewg-bcmodel-02.txt,.pdf
To: "Lai, Wai S \(Waisum\), ALABS" <wlai@att.com>, te-wg@ops.ietf.org
In-Reply-To: <7AFE40EF30EE754DA967D1B5968457CA137186@KCCLUST06EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, hits=-9.0 required=5.0
	tests=BAYES_10,IN_REP_TO
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Thanks for the reply, but still have some questions ,
read inline please.

>&nbsp;&nbsp; As explained in the draft, the
performance of BC >models is evaluated in terms of the
>blocking/preemption of LSPs, and not that of
>packets.&nbsp; Poisson assumption for LSP requests is
>therefore relevant.&nbsp; Also as discussed in the
draft, >the erlang is used to reflect LSP utilization
of&nbsp;a >link (as a result of bandwidth allocation
and not >the traffic volume).
&nbsp;
&nbsp;
If LSP is considered as SVC across MPLS networks, why
could we assume the&nbsp;arrival and lifetime of LSP
conforms to that of telephone networks?&nbsp; The only
situation&nbsp;I can see: VoIP&nbsp;system which sets
up LSP for each phonecall. But for data communication
network,&nbsp; self-similarity and heavy-tail
characterizes the network traffic. Although prof.
cleverland showed there is trends to poisson arrival
in their network, but no others report results
alike.&nbsp; Would you please tell me&nbsp; at which
level LSP is assumed to work, packet? connection?
session? host-to-host or network-to-network? 
&nbsp;
&nbsp;
Thanks a lot.




=====
Jing Shen

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

_________________________________________________________
Do You Yahoo!? 
网恋的诠释：真情还是放纵？
http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.surveys.yahoo.com/netlove



From owner-te-wg@ops.ietf.org  Thu Jul  3 11:48: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 LAA18925
	for <tewg-archive@lists.ietf.org>; Thu, 3 Jul 2003 11:48:41 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19Y6GS-00082y-Uc
	for te-wg-data@psg.com; Thu, 03 Jul 2003 15:44:52 +0000
Received: from [212.234.67.6] (helo=relais-inet-04.francetelecom.fr)
	by psg.com with esmtp (Exim 4.14)
	id 19Y6GN-00081n-AP
	for te-wg@ops.ietf.org; Thu, 03 Jul 2003 15:44:47 +0000
Received: from [193.248.188.48] by relais-filtrant-04.francetelecom.fr with ESMTP for te-wg@ops.ietf.org; Thu, 3 Jul 2003 17:44:15 +0200
Received: from fedft02a.francetelecom.fr by relais-filtrant-04.francetelecom.fr with ESMTP for te-wg@ops.ietf.org; Thu, 3 Jul 2003 17:44:14 +0200
Received: from [193.249.139.219] by fedft02a.francetelecom.fr with ESMTP for te-wg@ops.ietf.org; Thu, 3 Jul 2003 17:44:12 +0200
Received: from igt2bg036 ([10.134.121.112]) by
          smtp7.smtpft.francetelecom.fr (Netscape Messaging Server 4.15)
          with SMTP id HHGH1O00.FHA; Thu, 3 Jul 2003 17:44:12 +0200 
Reply-To: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
From: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
To: "'Arthi Ayyangar \(Juniper\)'" <arthi@juniper.net>,
        "'Jean-Philippe Vasseur \(Cisco\)'" <jpv@cisco.com>
Cc: <te-wg@ops.ietf.org>
Subject: Comments and questions to draft-ayyangar-inter-region-te-00.txt (long message)
Date: Thu, 3 Jul 2003 17:41:00 +0200
Message-Id: <005e01c34179$819798b0$7079860a@buriapren.w2k.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Status: No, hits=-5.8 required=5.0
	tests=BAYES_10
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dear colleagues,

Having read the aforementioned document, please find herein a list of
comments and questions.

Section 1, page 2:

To me, BGP clusters and confederations could also be examples of an AS which
would be composed of multiple regions,
I assume that there may be several LSP segments that may be inserted into an
inter-region LSP split, correct, although the last sentence of this
paragraph seems to tell the contrary (and I don't see the restriction in
such a case)?

Section 1, page 3: the notion of *local* protection should deserve some
elaboration, unless the notion of "local" is applied to the scale of a
region, as defined previously. If so, I would replace the current wording by
"...requesting protection at the scale of a region (as defined previously)
within the context of [FAST-REROUTE]..."

Section 2, page 3:

I would spend a line or two in this introductory section explaining the
interaction between this document and the [INTER-AS] document: maybe the
intent is to incorporate the contents of [INTER-AS] into this document?
The fact that ASes are mentioned in parenthesis when quoting "different
regions" is somehow confusing, since it introduces a 1:1 relationship
between the two notions, as opposed to the more generic definition stated in
section 1. I would either delete the parenthesis or extend it to areas,
sub-ASes, etc. Furthermore, I think the "other differences between the two
solutions" (end of the first paragraph) could find a natural place in a
specific section that would elaborate on the interaction between the two
documents.
The notion of "complete control" on FA-LSP and LSP segment should deserve
some elaboration as well, especially when the corresponding path computation
MAY be triggered by an incoming inter-region LSP Setup request, which, by
definition, is out of the control of a given ISP. Also, the notion of
"transit LSPs transported across that region" should be defined, including a
comparison with FA-LSP and LSP segments...since both the latter may *also*
be viewed as transit LSP paths, at least from an intra-region TE policy.

Section 3, page 4:

According to the first paragraph, I assume inter-area TE is a usage example
of the solution proposed in this document. I would tehrefore suggest a
reference to Jim's recent contribution as far as inter-area TE requirements
are concerned, and how (well) this document addresses such requirements.
The penultimate sentence of the third paragraph seems to make auto-discovery
mechanism (at least for the dynamic resolution of a next-hop boundary LSR)
somewhat *mandatory* for the completion of an inter-region TE solution, and
I think this should be clarified, especially when reading the previous
sentence ("In the absence of...").
The wording "...depending on the requirement of the operator of the transit
region" in the last paragraph should also deserve some elaboration, since I
suspect the need for (contractual) agreements between (participating)
operators (i.e. operators who would participate in the dynamic enforcement
of an inter-region TE policy), hence the need to exchange and possibly
negotiate related QoS requirements and (TE) capabilities.

Section 3, page 4:

Dynamic bandwidth adjustment by HE LSR routers which computre FA LSP paths
relies upon a specific knowledge which is the number of inter-region LSP
paths that may be carried by the FA LSP: how such a knowledge can be
acquired, since I assume this knowledge refers to predictable requests?
Traffic matrices? Else? I would suggest that this document be more explicit
on this engineering issue, which is one of the primary concerns of
operators, from a resource planning and optimisation standpoint.
What's a "resource affinity"? Does the notion of "color" refer to a specific
DSCP marking (if so, I would use this wording)?
What's the use for an exit point to be able to determine the FA LSP or the
LSP segment thje received Path message relates to, since I understand this
exit point is mostly used to propagate the inter-region LSP path Setup
towards the next hop region?

Section 4.1, page 5:

The second sentence introduces quite an important restriction I don't
understand. I guess operators could engineer FA LSP paths (if not LSP
segments) as specific transit LSP paths, without waiting for an incoming
inter-region LSP path Setup message, i.e. intra-region MPLS TE could also be
used to somehow *dedicate* specific LSPs for the "provisioning" of FA-LSP
that would convey the traffic transported in inter-region LSP paths. Also,
the notion of "source" should be more explicit: I assume you meant the
originating region or HE LSR for the computation of a given inter-region LSP
path, correct?

Section 4.1, page 6:

In the first paragraph, what if there is no auto-discovery mechanism
(somewhat related to one of the previous comments above)?
In the third paragraph, the notion of "FA-LSP/LSP segment candidate" should
deserve some elaboration. What would be the rules for eligibility, and do
you envision a dynamic "election" mechanism?

Section 4.2, page 7:

In the example, I'm not sure I understand the decision criteria which would
make router B establish a FA-LSP rather than a LSP segment (or vice versa).

Section 4.2, page 8:

The notion of "some specific inter-region LSPs" (end of first paragraph)
should be defined.
In the second paragraph, I still don't see the triggering mechanism that
makes B select a FA or a LSP segment in area 0, sicne the problem is related
to area 2 (hence the business of C, apart from sending the PathErr message
to B).
Also, I don't see the need of mentioning R0, R1 and R2 for this example.

Section 4.3, page 9:

Does the notion of "a single hop link (between two ASBR routers" implicitly
refer to the notion of eBGP multihop? If so, please be more specific.
In the case of ASBR-ASBR links and the corresponding TE information, you
mention the possibility of using a CSPF algorithm for path computation,
which seems rather odd from an inter-domain path computation standpoint,
especially because flooding path computation information between domains is
not really recommended.
Also, I somehow disagree with the assmption that states that propagation of
TE-related information between routers of a domain is implementation
specific: my guess is that such routers should support Opaque LSAs (in the
case of OSPF, together with the support of the TE extensions of OSPF as
defined in Katz' draft) and the equivalent in IS-IS, and the document should
at least provide a pointer to these references.
The advertisement of ASBR-ASBR-link-related TE information should be more
precisely defined: do you mean the propagation of such information between
ASBR routers and/or within a given domain, for redistribution purposes for
example?

Section 4.3, page 10:

The first sentence of the paragraph may yield some scalability issue, as far
as the volume of the TE information that will be flooded (presumably across
domains) is concerned.
The last paragraph before section 5 implicitly extends the definition of FA
LSP *beyond* the scope of a region.

Section 5, page 10:

Again the stitching decision criteria should deserve some elaboration, and
there may be an issue as far as the consistency (as well as the chronology)
of the RSVP setup messages related to the FA (or LSP segment) *and* the
inter-region LSP path computation is concerned. Also, the last sentence of
the first paragraph ("This may be desired...") is somewhat confusing as far
as the expectation on the number of LSP requests to be processed towards the
same destination is concerned.

Section 5, page 11:

What are the "in-between" LSRs (under the 0x04 LSP stitching wording)? What
would happen is such LSR changed the flag?
In the example provided, the question of the chronology is raised again.
Also, according to the penultimate sentence of this page, the "memory"
capabilities of C should deserve some elaboration: how control the
appropriate behavior of C?

Scetion 6.1, page 12:

I don't understand why there is no traffic disruption during the repair
period (end of the page), while C is computing a new path for the FA/LSP
segment that are affected by the "old" path which has been torn down.

Section 6.2, page 13:

What's the influence of having the knowledge of the TE information on the
backup path algorithm?
The notion of "partial" CSPF computation should deserve some elaboration -
does that refer to vendor-specific incremental SPF computations?
Also, the notion of "main" LSP path has not been defined (before section
6.3).

Section 7, page 15:

Should the re-optimisation parameters be taken into account by the CSPF
computation?

Section 8: I would put the contents of this section in the appropriate
requirements document ([INTER-AS]?).

Section 8.4, page 17:

Instead of "...there may be other inter-AS agreements...", I would put a
MUST (related to one of the previous comments above).

Section 10, page 17:

IPR issues should be elaborated and the IPR page of the IETF web site should
be updated accordingly.

Cheers,

Christian.


    _________________    ________  ______  ______
   /_____________   /__ /_    _ / /     / /     /   Christian "I'm a ZZ Fan"
Jacquenet
      /_________/  /  /   /  /   /  /  / /  /__/    France Telecom Long
Distance ITP/CTO
               /  /  /___/__/___/_____/_/__/____   "'Been a while since I
made her smile,
              /__/  /__________________________/_ And I know she's gonna dig
my style."
                /_______________________________/ - Enjoy and get it on.




From owner-te-wg@ops.ietf.org  Mon Jul  7 20:53: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 UAA23199
	for <tewg-archive@lists.ietf.org>; Mon, 7 Jul 2003 20:53:49 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19Zgeq-000549-HZ
	for te-wg-data@psg.com; Tue, 08 Jul 2003 00:48:36 +0000
Received: from [207.17.136.129] (helo=merlot.juniper.net)
	by psg.com with esmtp (Exim 4.14)
	id 19Zgek-00052G-MX; Tue, 08 Jul 2003 00:48:30 +0000
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id h680lpu19157;
	Mon, 7 Jul 2003 17:47:51 -0700 (PDT)
	(envelope-from arthi@juniper.net)
Date: Mon, 7 Jul 2003 17:47:51 -0700 (PDT)
From: Arthi Ayyangar <arthi@juniper.net>
To: JACQUENET Christian FTLD/IAP <christian.jacquenet@francetelecom.com>
cc: "'Jean-Philippe Vasseur (Cisco)'" <jpv@cisco.com>, "" <te-wg@ops.ietf.org>,
        "" <ccamp@ops.ietf.org>
Subject: Re: Comments and questions to draft-ayyangar-inter-region-te-00.txt
 (long message)
In-Reply-To: <005e01c34179$819798b0$7079860a@buriapren.w2k.francetelecom.fr>
Message-ID: <20030707102807.L34579@zircon.juniper.net>
References: <005e01c34179$819798b0$7079860a@buriapren.w2k.francetelecom.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-21.0 required=5.0
	tests=BAYES_30,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      REPLY_WITH_QUOTES
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Christian,

Thanks a lot for your detailed comments. I have tried to address
most of your questions/comments. Please find my replies inline.

> To me, BGP clusters and confederations could also be examples of an AS which
> would be composed of multiple regions,
--------> Yes, BGP confederation could be yet another example of a region.
But if all the members of a confed run a single IGP, then it's not
clear why each member would form a region.

> I assume that there may be several LSP segments that may be inserted into an
> inter-region LSP split, correct, although the last sentence of this
> paragraph seems to tell the contrary (and I don't see the restriction in
> such a case)?
--------> Do you mean per region or overall ? So, as the inter-region
TE LSP traverses different regions, more that one region along the
path could decide to stitch this TE LSP onto some intra-region LSP segment.
In any case, I will modify the text to clarify this.

> Section 1, page 3: the notion of *local* protection should
deserve some elaboration, unless the notion of "local" is applied to the
scale of a region, as defined previously. If so, I would replace the
current wording by "...requesting protection at the scale of a region (as
defined previously) within the context of [FAST-REROUTE]..."
--------> The notion of 'local protection' here is applicable within a
region as well as across regions as explained in Section 6.

> I would spend a line or two in this introductory section explaining the
> interaction between this document and the [INTER-AS] document: maybe the
> intent is to incorporate the contents of [INTER-AS] into this document?
-------> Not as of now; the solution proposed in [INTER-AS] is different
from the solution proposed here. Section 2 which is the introductory
section does explain the basic difference.

> The fact that ASes are mentioned in parenthesis when quoting "different
> regions" is somehow confusing, since it introduces a 1:1 relationship
> between the two notions, as opposed to the more generic definition stated in
> section 1. I would either delete the parenthesis or extend it to areas,
> sub-ASes, etc.
--------> I'll delete the parenthesis.

[clipped..]

> The notion of "complete control" on FA-LSP and LSP segment should deserve
> some elaboration as well, especially when the corresponding path computation
> MAY be triggered by an incoming inter-region LSP Setup request, which, by
> definition, is out of the control of a given ISP.
---------> The idea is that since the FA-LSP and LSP segment are
originated per region, local policies/configurations can control how
and when these get setup. I shall elaborate on the above in the next
revision.

Also, the notion of
> "transit LSPs transported across that region" should be defined, including a
> comparison with FA-LSP and LSP segments...since both the latter may *also*
> be viewed as transit LSP paths, at least from an intra-region TE policy.
----------> The notion of 'transit' here depends on the originating and
terminating regions. While FA-LSPs and LSP segments start and terminate in
the same region (they are intra-region), LSPs that originate in some other
region and traverse this region are viewed to be 'transit LSPs'. As far as
the inter-region TE policy goes, therefore, the inter-region LSPs would be
treated as 'transit'. Ofcourse, other TE policies, local to the region,
could also be applicable to the intra-region LSPs that transport the
inter-region LSPs.
	I am not quite clear about your last sentence "since both the
latter may *also* be viewed as transit LSP paths, at least from an
intra-region TE policy". Could you elaborate ?

> Section 3, page 4:
>
> According to the first paragraph, I assume inter-area TE is a usage example
> of the solution proposed in this document. I would tehrefore suggest a
> reference to Jim's recent contribution as far as inter-area TE requirements
> are concerned, and how (well) this document addresses such requirements.
--------> Will do so in the next revision.

> The penultimate sentence of the third paragraph seems to make auto-discovery
> mechanism (at least for the dynamic resolution of a next-hop boundary LSR)
> somewhat *mandatory* for the completion of an inter-region TE solution, and
> I think this should be clarified, especially when reading the previous
> sentence ("In the absence of...").
--------> Auto-discovery was not intended to be a mandatory mechanism. The
reason it was stressed here was so that the LSP paths (EROs) are specified
correctly.

> The wording "...depending on the requirement of the operator of the transit
> region" in the last paragraph should also deserve some elaboration, since I
> suspect the need for (contractual) agreements between (participating)
> operators (i.e. operators who would participate in the dynamic enforcement
> of an inter-region TE policy), hence the need to exchange and possibly
> negotiate related QoS requirements and (TE) capabilities.
---------> Wouldn't this depend on the nature of the region itself ?
i.e. while the above may be true for an inter-AS LSP setup, especially
when the ASes belong to different SPs, it need not be applicable to an
inter-area LSP setup. Section 8.4 addresses this for inter-AS case.

> Section 3, page 4:
>
> Dynamic bandwidth adjustment by HE LSR routers which computre FA LSP paths
> relies upon a specific knowledge which is the number of inter-region LSP
> paths that may be carried by the FA LSP: how such a knowledge can be
> acquired, since I assume this knowledge refers to predictable requests?
> Traffic matrices? Else? I would suggest that this document be more explicit
> on this engineering issue, which is one of the primary concerns of
> operators, from a resource planning and optimisation standpoint.
--------> This is an error in the text. I will correct it.
The dynamic bandwidth adjustment was to be based not on the number of
inter-region TE LSPs, but on the cumulative b/w requested by these
inter-region TE LSPs.

> What's a "resource affinity"? Does the notion of "color" refer to a specific
> DSCP marking (if so, I would use this wording)?
---------> The semantics are as defined in RFC 2702. I will add
the appropriate reference there.

> What's the use for an exit point to be able to determine the FA LSP or the
> LSP segment the received Path message relates to, since I understand this
> exit point is mostly used to propagate the inter-region LSP path Setup
> towards the next hop region?
------------> One of the reasons it is needed, is because depending on
whether the HE has done stitching or nesting, the egress LSR for the
FA-LSP/LSP segment needs to do correct label allocations (in the Resv
messages sent back upstream). This has been explained in section 5.

> Section 4.1, page 5:
>
> The second sentence introduces quite an important restriction I don't
> understand. I guess operators could engineer FA LSP paths (if not LSP
> segments) as specific transit LSP paths, without waiting for an incoming
> inter-region LSP path Setup message, i.e. intra-region MPLS TE could also be
> used to somehow *dedicate* specific LSPs for the "provisioning" of FA-LSP
> that would convey the traffic transported in inter-region LSP paths.
--------> Absolutely. That is exactly what the first sentence tries to
convey: "FA-LSPs or LSP segments can be pre-configured on any region
boundary LSR".
	The second sentence only says that in case of dynamic FA-LSP or
LSP segment setup (i.e. when they are *not* pre-provisioned), it is the
region boundary LSRs which are at the entry to the region which will
trigger the setup of the intra-region LSPs. So this is just stating who
is the default candidate for dynamic FA-LSP/LSP segment setup. This is
useful so that a region boundary LSR can determine if it needs to trigger
the setup of an intra-region LSP.

>Also,
> the notion of "source" should be more explicit: I assume you meant the
> originating region or HE LSR for the computation of a given inter-region LSP
> path, correct?
---------> Yes, the "source" here is the HE LSR for the inter-region LSP.
I will calrify this.


> Section 4.1, page 6:
>
> In the first paragraph, what if there is no auto-discovery mechanism
> (somewhat related to one of the previous comments above)?
---------> Then it is assumed that the nexthop in the ERO would specify
the region boundary LSR for that region, so that the previous hop can
expand the loose hop and compute a path to the region boundary LSR.
Section 3 explains this in detail.


> In the third paragraph, the notion of "FA-LSP/LSP segment candidate" should
> deserve some elaboration. What would be the rules for eligibility, and do
> you envision a dynamic "election" mechanism?
---------> By default, it would be the entry region boundary LSR. The
first paragraph in 4.1 defines exactly this.

> Section 4.2, page 7:
>
> In the example, I'm not sure I understand the decision criteria which would
> make router B establish a FA-LSP rather than a LSP segment (or vice versa).
---------> That is a decision local to the region (based on configuration
on the LSR) whether it wants to do nesting or stitching. If the goal is
say, scalability, then in order to transport several inter-region LSPs
over an intra-region LSP the operator may want to nest all the
inter-region LSPs on a FA-LSP. On the other hand, if the operator would
rather have one intra-region LSP per inter-region LSP, then he may choose
to do stitching with an LSP segment in that region.


> Section 4.2, page 8:
>
> The notion of "some specific inter-region LSPs" (end of first paragraph)
> should be defined.
> In the second paragraph, I still don't see the triggering mechanism that
> makes B select a FA or a LSP segment in area 0, sicne the problem is related
> to area 2 (hence the business of C, apart from sending the PathErr message
> to B).
---------> Please see explanation above.

> Also, I don't see the need of mentioning R0, R1 and R2 for this example.
---------> Okay. I'll remove them if they remain unused.

> Section 4.3, page 9:
>
> Does the notion of "a single hop link (between two ASBR routers" implicitly
> refer to the notion of eBGP multihop? If so, please be more specific.
> In the case of ASBR-ASBR links and the corresponding TE information, you
> mention the possibility of using a CSPF algorithm for path computation,
> which seems rather odd from an inter-domain path computation standpoint,
> especially because flooding path computation information between domains is
> not really recommended.
----------> It is not expected that path computation information be
flooded between different domains (regions). Here, we are only interested
in obtaining the TE-information associated with the local links originated
by the ASBR in the ASBR's TED. e.g. in the example discussed in 4.3, the
TE information associated with link BC would be added to B's TED.
Secondly, so that path computation in AS1 can take into account the TE
information for links BC, B'C', the ASBRs B and B' would need to advertise
the TE information for BC, B'C' in AS1's IGP.

> Also, I somehow disagree with the assmption that states that propagation of
> TE-related information between routers of a domain is implementation
> specific: my guess is that such routers should support Opaque LSAs (in the
> case of OSPF, together with the support of the TE extensions of OSPF as
> defined in Katz' draft) and the equivalent in IS-IS, and the document should
> at least provide a pointer to these references.
------------> I will add the references to these documents. Also, it was
*not* the mechanism used for propagation of TE information (TE extensions
for OSPF/ISIS) which was to be 'implementation specific'. It was the
mechanism used to determine the node (ASBR) and the links to the node
(ASBR-ASBR links) for which TE information is to be advertised, that was
supposed to be implementation specific.  I will rephrase the document to
clarify this.

> The advertisement of ASBR-ASBR-link-related TE information should be more
> precisely defined: do you mean the propagation of such information between
> ASBR routers and/or within a given domain, for redistribution purposes for
> example?
---------> See explanation above.

> Section 4.3, page 10:
>
> The first sentence of the paragraph may yield some scalability issue, as far
> as the volume of the TE information that will be flooded (presumably across
> domains) is concerned.
-----------> No TE information is expected to be flooded across domains,
as explained above.

[clipped..]

> Section 5, page 11:
>
> What are the "in-between" LSRs (under the 0x04 LSP stitching wording)? What
> would happen is such LSR changed the flag?
-----------> In case a region boundary LSR decides to do LSP stitching
then it would set the above flag for the intra-region LSP segment. The
flag is examined by the egress LSR for the intra-region LSP segment. All
other LSRs in that region are "in-between". This flag is not expected to
be changed because it is used for signaling an attribute for that
intra-region LSP session and indicates the behavior of the HE LSR.

[clipped..]
> Scetion 6.1, page 12:
>
> I don't understand why there is no traffic disruption during the repair
> period (end of the page), while C is computing a new path for the FA/LSP
> segment that are affected by the "old" path which has been torn down.
-----------> The paths for local protection are pre-computed and
pre-established as per [FAST-REROUTE]. So when failure occurs, you would
only need to switch to the backup path causing minimum traffic loss.
This is similar to MPLS Fast-reroute mechanisms which exist today.
Will rephrase.

> Section 6.2, page 13:
>
> What's the influence of having the knowledge of the TE information on the
> backup path algorithm?
-------> So that they can be computed instead of being configured
statically.

> The notion of "partial" CSPF computation should deserve some elaboration -
> does that refer to vendor-specific incremental SPF computations?
-------> No, it does not refer to any vendor-specific incremental SPF
computations. It means expanding the ERO upto the first reachable
boundary LSR in the region (which has either been specified as loose hop
in the ERO or has been determined via auto-discovery mechanism). I will
fix the text to elaborate this.

> Also, the notion of "main" LSP path has not been defined (before section
> 6.3).
-------> This is an error in text, I'll fix it.

> Section 7, page 15:
>
> Should the re-optimisation parameters be taken into account by the CSPF
> computation?
--------> Yes.

> Section 8: I would put the contents of this section in the appropriate
> requirements document ([INTER-AS]?).
----------> This section is meant to show that the solution proposed
in this draft satisfies requirements for Inter-AS TE as specified in
[INTER-AS-TE-REQTS] in case the region is an AS.

Thanks again for all the comments!

thanks,
-arthi



From owner-te-wg@ops.ietf.org  Mon Jul  7 22:20:41 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24626
	for <tewg-archive@lists.ietf.org>; Mon, 7 Jul 2003 22:20:40 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19Zi24-00098f-Sj
	for te-wg-data@psg.com; Tue, 08 Jul 2003 02:16:40 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19Zi21-00095V-FS
	for te-wg@ops.ietf.org; Tue, 08 Jul 2003 02:16:37 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h682G0qG002550
	for <te-wg@ops.ietf.org>; Mon, 7 Jul 2003 22:16:06 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h682Fn2I002546
	for <te-wg@ops.ietf.org>; Mon, 7 Jul 2003 22:16:00 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 7 Jul 2003 22:15:49 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: TEWG 57th IETF Agenda
Message-ID: <Pine.LNX.4.44.0307072214370.1973-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-12.9 required=5.0
	tests=BAYES_10,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


        Agenda for the Internet Traffic Engineering WG
        57th IETF - Vienna, Austria
        14 July, 2003 1300-1500 pm.

1300-1315  Agenda and WG status update - Chairs
          - draft-ietf-tewg-te-metric-igp-02.txt
                 - On ref hold for isis/ospf-traffic drafts
           - draft-ietf-tewg-diff-te-reqts-07.txt
                 - RFC editor review / final author review
           - draft-ietf-tewg-measure-05.txt
                 - Awaiting revision by author

1310-1315  TEWG MIB update - Kireeti
           - draft-ietf-tewg-mib-04.txt

1315-1415  DiffServ TE - Francois, Waisum, Jerry
           - draft-ietf-tewg-diff-te-proto-04.txt
           - draft-ietf-tewg-diff-te-russian-03.txt
           - draft-ietf-tewg-diff-te-mam-00.txt
           - draft-ietf-tewg-diff-te-mar-01.txt
	   - draft-wlai-tewg-bcmodel-02.txt          
	   - draft-wlai-tewg-overbook-00.txt 
           - draft-sivabalan-diff-te-bundling-02.txt (not being discussed)

1415-1500  Interarea and Inter-AS TE - Jean-Phillipe, Raymond, Arthi, Jim
           - draft-ietf-tewg-interas-mpls-te-req-00.txt
           - draft-boyle-tewg-interarea-reqts-00.txt
           - draft-ayyangar-inter-region-te-00.txt
	   - draft-vasseur-inter-as-te-01.txt
	   - draft-vasseur-mpls-loose-path-reopt-02.txt





From owner-te-wg@ops.ietf.org  Tue Jul  8 11:30: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 LAA26764
	for <tewg-archive@lists.ietf.org>; Tue, 8 Jul 2003 11:30:51 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19ZuLr-0009CC-Df
	for te-wg-data@psg.com; Tue, 08 Jul 2003 15:25:55 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.14)
	id 19ZuLm-0009B6-Vn
	for te-wg@ops.ietf.org; Tue, 08 Jul 2003 15:25:51 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 08 Jul 2003 17:25:29 +0200
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 h68FNDnJ024184;
	Tue, 8 Jul 2003 17:23:13 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 8 Jul 2003 17:25:18 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: DSTE and link-bundling clarifications needed?
Date: Tue, 8 Jul 2003 16:25:17 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B52B6@xbe-lon-313.cisco.com>
Thread-Topic: DSTE and link-bundling clarifications needed?
Thread-Index: AcM7+5ffBissNLkVQeyINWShdW73IQJZrJMg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Siva Sivabalan (msiva)" <msiva@cisco.com>, <raymond_zhang@infonet.com>
X-OriginalArrivalTime: 08 Jul 2003 15:25:18.0189 (UTC) FILETIME=[233F99D0:01C34565]
X-Spam-Status: No, hits=-7.0 required=5.0
	tests=BAYES_10,NEW_DOMAIN_EXTENSIONS,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hello Jim,

The diff-te-bundling draft does not define any new protocol extensions;
but it updates the definition/semantics of protocol extensions defined
in other documents. Very analogous to the diff-te-proto spec redefining
the semantic of the "unreserved Bw" sub-TLV. So to me it also fits in
the Standards track (it can be seen as a complement to the diff-te-proto
draft for operations over bundled links). =20

As you indicated, some of it is simply stating what anyone very familiar
with DSTE, GMPLS and TE-Bundle could guess (just like the spec for MPLS
TE bundle does in some places as well). Some of it is a little less
obvious such as the change in the semantic of the Max LSP Bandwidth
(which prompted a yet to be included correction in the GMPLS base spec).

So to come back to your specific questions:
	- yes, to us, these clarifications are worth putting down in
writing to facilitate interoperation of DSTE over bundled links
	- the intent is to progress in standards track (again because it
does redefine semantic of existing protocol elements).

Cheers

Francois

>> -----Original Message-----
>> From: Jim Boyle [mailto:jboyle@pdnets.com]=20
>> Sent: 26 June 2003 17:56
>> To: te-wg@ops.ietf.org
>> Cc: Siva Sivabalan (msiva); Francois Le Faucheur (flefauch);=20
>> raymond_zhang@infonet.com
>> Subject: DSTE and link-bundling clarifications needed?
>>=20
>>=20
>>=20
>> In regards to draft-sivabalan-diff-te-bundling-02.txt,
>> it seems to state a lot of the obvious.
>>=20
>> Are these clarifications substantial enough to justify an RFC?
>>=20
>> Is it the author's intent that this would be informational?
>>=20
>> thanks,
>>=20
>> Jim
>>=20
>>=20



From owner-te-wg@ops.ietf.org  Thu Jul 10 05:24: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 FAA23680
	for <tewg-archive@lists.ietf.org>; Thu, 10 Jul 2003 05:24:13 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19aXW3-000DgA-0g
	for te-wg-data@psg.com; Thu, 10 Jul 2003 09:15:03 +0000
Received: from [212.234.67.6] (helo=relais-inet-03.francetelecom.fr)
	by psg.com with esmtp (Exim 4.14)
	id 19aXVt-000Ddj-MY; Thu, 10 Jul 2003 09:14:53 +0000
Received: from [193.248.188.47] by relais-filtrant-03.francetelecom.fr with ESMTP; Thu, 10 Jul 2003 11:14:22 +0200
Received: from fedft01a.francetelecom.fr by relais-filtrant-03.francetelecom.fr with ESMTP; Thu, 10 Jul 2003 11:14:22 +0200
Received: from [193.249.139.219] by fedft01a.francetelecom.fr with ESMTP; Thu, 10 Jul 2003 11:14:19 +0200
Received: from igt2bg036 ([10.134.121.112]) by
          smtp7.smtpft.francetelecom.fr (Netscape Messaging Server 4.15)
          with SMTP id HHSXNV01.S62; Thu, 10 Jul 2003 11:14:19 +0200 
Reply-To: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
From: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
To: "'Arthi Ayyangar'" <arthi@juniper.net>
Cc: "'Jean-Philippe Vasseur \(Cisco\)'" <jpv@cisco.com>, <te-wg@ops.ietf.org>,
        <ccamp@ops.ietf.org>
Subject: RE: Comments and questions to draft-ayyangar-inter-region-te-00.txt(long message)
Date: Thu, 10 Jul 2003 11:11:07 +0200
Message-Id: <001b01c346c3$32d4f4d0$7079860a@buriapren.w2k.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <20030707102807.L34579@zircon.juniper.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Status: No, hits=-13.0 required=5.0
	tests=BAYES_01,IN_REP_TO,QUOTED_EMAIL_TEXT
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Arthi,

Thanks for your clarifications - a couple of additional comments below.

[snip]

Hi Christian,

Thanks a lot for your detailed comments. I have tried to address
most of your questions/comments. Please find my replies inline.

> To me, BGP clusters and confederations could also be examples of an AS
which
> would be composed of multiple regions,
--------> Yes, BGP confederation could be yet another example of a region.
But if all the members of a confed run a single IGP, then it's not
clear why each member would form a region.

CJ: I'm not sure I understand your point. All I meant is that a sub-AS (as
part of a BGP confederation) could be viewed as a region by itself.

[snip]
Also, the notion of
> "transit LSPs transported across that region" should be defined, including
a
> comparison with FA-LSP and LSP segments...since both the latter may *also*
> be viewed as transit LSP paths, at least from an intra-region TE policy.
----------> The notion of 'transit' here depends on the originating and
terminating regions. While FA-LSPs and LSP segments start and terminate in
the same region (they are intra-region), LSPs that originate in some other
region and traverse this region are viewed to be 'transit LSPs'. As far as
the inter-region TE policy goes, therefore, the inter-region LSPs would be
treated as 'transit'. Ofcourse, other TE policies, local to the region,
could also be applicable to the intra-region LSPs that transport the
inter-region LSPs.
	I am not quite clear about your last sentence "since both the
latter may *also* be viewed as transit LSP paths, at least from an
intra-region TE policy". Could you elaborate ?

CJ: what I meant is that, since FA and segments are computed to convey
traffics that relate to inter-region LSP paths, both the FA and segment LSPS
can be viewed as transit LSPs within a given domain, whereas they may have
been (pre)-computed as part of the enforcement of an intra-domain TE policy.

[snip]

> The wording "...depending on the requirement of the operator of the
transit
> region" in the last paragraph should also deserve some elaboration, since
I
> suspect the need for (contractual) agreements between (participating)
> operators (i.e. operators who would participate in the dynamic enforcement
> of an inter-region TE policy), hence the need to exchange and possibly
> negotiate related QoS requirements and (TE) capabilities.
---------> Wouldn't this depend on the nature of the region itself ?
i.e. while the above may be true for an inter-AS LSP setup, especially
when the ASes belong to different SPs, it need not be applicable to an
inter-area LSP setup. Section 8.4 addresses this for inter-AS case.

CJ: I tend to agree with you, but I'm not sure your comment is strictly
relevant since the text refers to *the operator of the transit region*,
which, to me, implictly assumes an inter-AS context: otherwise, I don't see
why an operator of a given *area* should be different from the one who
manages another area...within a given domain.

Cheers,

Christian.




From owner-te-wg@ops.ietf.org  Fri Jul 11 11:57:43 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04332
	for <tewg-archive@lists.ietf.org>; Fri, 11 Jul 2003 11:57:43 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19b0BN-000HaG-Lv
	for te-wg-data@psg.com; Fri, 11 Jul 2003 15:51:37 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.14)
	id 19b0BK-000HTx-08
	for te-wg@ops.ietf.org; Fri, 11 Jul 2003 15:51:34 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 11 Jul 2003 17:51:09 +0200
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 h6BFmsPB004388
	for <te-wg@ops.ietf.org>; Fri, 11 Jul 2003 17:48:56 +0200 (MET DST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 11 Jul 2003 17:51:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.6410.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Concern with <draft-wlai-tewg-bcmodel-02.txt>
Date: Fri, 11 Jul 2003 16:51:01 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D93B52CC@xbe-lon-313.cisco.com>
Thread-Topic: Concern with <draft-wlai-tewg-bcmodel-02.txt>
Thread-Index: AcNE96iCOCab/UrxTKuwclkLdrkAIACxaqlA
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 11 Jul 2003 15:51:02.0175 (UTC) FILETIME=[3AC66AF0:01C347C4]
X-Spam-Status: No, hits=-3.1 required=5.0
	tests=BAYES_20
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Waisum and all,

I would like to share with the group the concern I have expressed to
Waisum on current version of <draft-wlai-tewg-bcmodel-02.txt>.

Clearly, when looking at BC Model performance purely from the viewpoint
of LSP blocking/preemption, the choice of the BC values is key. If I
arbitrarily increase the BC values, I can accept more LSP and reduce (or
completely eliminate) blocking and preemption. The reason those can not
simply be arbitrarily increased is because they would result in
potential QoS degradation (ie accepting more LSP traffic than the
correponding Diff-Serv scheduler can service).

So, it seems most relevant to compare models using BC values which
correspond to similar QoS degradation (on the higher priority classes)
in both models. For example, MAM(6/7/15) should actually be compared
with RDM(6/13/15). This is because [assuming fairly typical Diff-Serv
scheduler configuration so that if bandwidth is not used by EF queue ,
most of it can be allocated to "Premium Data" queue] you can indeed, in
case there is no EF LSP, accept up to 13 worth of Premium LSP, without
any QoS degradation on Premium traffic. (Really, this is a KEY point of
RDM: be able to have the unused bandwidth of class N being reallocated
in priority to Class N+1).
So, the bottom line is that both MAM(6/7/15) and RDM(6/13/15) behave
very much the same (ie equally well) in terms of QoS degradation for
Voice+Premium.

However, draft-wlai-tewg-bcmodel-02.txt currently compares MAM(6/7/15)
with RDM(6/**11**/15) and the justification for arbitrarily picking
these values of BCs is so that the two models happen to have equal
blocking/preemption under the reference load. Then this same BC values
are used when increasing the load. I don't see the rationale for saying:
"in order to compare two models let us start by tweaking one down so
they both have the same performance level". As I explained earlier on
this list, to me this is like deciding to attach a 3-ton trailer behind
a Porsche so it has the same performance on flat ground as a low-end
vehicle, and then conclude that the low-end vehicle has higher
performance than a Porsche going uphill because it behaves better than
the Porsche with its 3-ton trailer.

Another way to look at this is the following:
I think we agree that BC models performance is a multi-dimension thing
(one dimension being blocking/preemption, another dimension being QoS
degradation of premium classes, ...). While there is some merit in
comparing performance of BC models in one single dimension (ie
blocking/preemption) and ignoring other dimensions (ie QoS degradation),
this is only meaningful if the parameter settings are such that the
various models are on equal footage in the ignored dimensions (eg QoS
degradation).

My objective is not to tweak comparison so that RDM systematically has
better performance than MAM in all cases. We know that MAM behaves
better for example in terms of class isolation when preemption is not
used. But I think the comparison needs to put models on equal footage
and should reflect one of the key benefit of RDM (again this
reallocation of bandwidth from Class N to Class N+1).

Would it be possible for <draft-wlai-tewg-bcmodel-02.txt> to use BC
values 6/13/15 for RDM (instead of 6/11/15) when comparing to
MAM(6/7/15)?

Thanks

Francois




From owner-te-wg@ops.ietf.org  Tue Jul 15 09:19:00 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17660
	for <tewg-archive@lists.ietf.org>; Tue, 15 Jul 2003 09:18:59 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19cPcF-000ELj-7J
	for te-wg-data@psg.com; Tue, 15 Jul 2003 13:13:11 +0000
Received: from [209.171.43.51] (helo=relay0.netfirms.com)
	by psg.com with smtp (Exim 4.14)
	id 19cPcC-000ELD-4W
	for te-wg@ops.ietf.org; Tue, 15 Jul 2003 13:13:08 +0000
Received: (qmail 23511 invoked from network); 15 Jul 2003 13:13:06 -0000
Received: from puppy.ietf57.telekom.at (HELO Puppy) (81.160.194.120)
  by 0 with SMTP; 15 Jul 2003 13:13:06 -0000
Message-ID: <00b701c34ad2$d4bfc0f0$78c2a051@Puppy>
Reply-To: "Adrian Farrel" <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "TEWG" <te-wg@ops.ietf.org>
Subject: Solutions in support of multi-region
Date: Tue, 15 Jul 2003 14:12:23 +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.2800.1158
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Status: No, hits=-3.1 required=5.0
	tests=BAYES_20
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

After the discussions on the Multi-Region family of requirement
drafts, I just wanted to draw the list's attention to the work in
ccamp on crankback and route exclusion
(draft-iwata-mpls-crankback-06.txt and
draft-ietf-ccamp-rsvp-te-exclude-route-00.txt).

One or two of the requirements draft mention the need for either
of these functions. The authors of the others might like to
consider whether they need the functions as well.

We would, of course, welcome opinions on the ccamp list as to
whether these drafts address the requirements.

Cheers,
Adrian




From owner-te-wg@ops.ietf.org  Tue Jul 22 11:12: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 LAA16857
	for <tewg-archive@lists.ietf.org>; Tue, 22 Jul 2003 11:12:26 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19eyi2-000JiD-Ui
	for te-wg-data@psg.com; Tue, 22 Jul 2003 15:05:46 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19eyi0-000Jff-0U
	for te-wg@ops.ietf.org; Tue, 22 Jul 2003 15:05:44 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h6MF52lO014636
	for <te-wg@ops.ietf.org>; Tue, 22 Jul 2003 11:05:13 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h6MF4jA9014632
	for <te-wg@ops.ietf.org>; Tue, 22 Jul 2003 11:05:02 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Tue, 22 Jul 2003 11:04:45 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: Minutes and Presentations from TEWG at IETF57
Message-ID: <Pine.LNX.4.44.0307221103530.12216-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-13.7 required=5.0
	tests=BAYES_01,USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


They are available at wwww.pdnets.com/ietf/tewg/ietf57

thanks!

Jim




From owner-te-wg@ops.ietf.org  Tue Jul 22 14:21: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 OAA21651
	for <tewg-archive@lists.ietf.org>; Tue, 22 Jul 2003 14:21:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19f1fI-000GMh-1x
	for te-wg-data@psg.com; Tue, 22 Jul 2003 18:15:08 +0000
Received: from [209.171.43.54] (helo=m6.netfirms.com)
	by psg.com with smtp (Exim 4.14)
	id 19f1fE-000GLz-Ro
	for te-wg@ops.ietf.org; Tue, 22 Jul 2003 18:15:05 +0000
Received: (qmail 68471 invoked by uid 0); 22 Jul 2003 17:59:52 -0000
Received: (qmail 81275 invoked from network); 22 Jul 2003 15:48:05 -0000
Received: from mail14.easyspace.com (198.64.148.137)
  by m0.netfirms.com with SMTP; 22 Jul 2003 15:48:05 -0000
Received: from psg.com (psg.com [147.28.0.62])
	by mail14.easyspace.com (EasyPost) with ESMTP id AF347841E2
	for <adrian@olddog.co.uk>; Tue, 22 Jul 2003 15:47:30 +0000 (GMT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19eyi2-000JiD-Ui
	for te-wg-data@psg.com; Tue, 22 Jul 2003 15:05:46 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19eyi0-000Jff-0U
	for te-wg@ops.ietf.org; Tue, 22 Jul 2003 15:05:44 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h6MF52lO014636
	for <te-wg@ops.ietf.org>; Tue, 22 Jul 2003 11:05:13 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h6MF4jA9014632
	for <te-wg@ops.ietf.org>; Tue, 22 Jul 2003 11:05:02 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Tue, 22 Jul 2003 11:04:45 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: Minutes and Presentations from TEWG at IETF57
Message-ID: <Pine.LNX.4.44.0307221103530.12216-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-13.7 required=5.0
	tests=BAYES_01,USER_AGENT_PINE,X_AUTH_WARNING
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


They are available at wwww.pdnets.com/ietf/tewg/ietf57

thanks!

Jim





From owner-te-wg@ops.ietf.org  Tue Jul 22 19:32:57 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA00892
	for <tewg-archive@lists.ietf.org>; Tue, 22 Jul 2003 19:32:56 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19f6ZV-0006rp-H7
	for te-wg-data@psg.com; Tue, 22 Jul 2003 23:29:29 +0000
Received: from [171.68.223.138] (helo=sj-core-4.cisco.com)
	by psg.com with esmtp (Exim 4.14)
	id 19f6ZR-0006q6-8K
	for te-wg@ops.ietf.org; Tue, 22 Jul 2003 23:29:25 +0000
Received: from mira-kan-a.cisco.com (IDENT:mirapoint@mira-kan-a.cisco.com [161.44.201.17])
	by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h6MLqRpp025993;
	Tue, 22 Jul 2003 14:52:28 -0700 (PDT)
Received: from msiva-w2k01.cisco.com (dhcp-kta1-161-44-193-203.cisco.com [161.44.193.203])
	by mira-kan-a.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR)
	with ESMTP id AAD24632;
	Tue, 22 Jul 2003 14:52:26 -0700 (PDT)
Message-Id: <4.3.2.7.2.20030722175124.0236c7d0@toque.cisco.com>
X-Sender: msiva@toque.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 22 Jul 2003 17:52:25 -0400
To: Jim Boyle <jboyle@pdnets.com>
From: "Siva Sivabalan (msiva)" <msiva@cisco.com>
Subject: Re: Minutes and Presentations from TEWG at IETF57
Cc: te-wg@ops.ietf.org
In-Reply-To: <Pine.LNX.4.44.0307221103530.12216-100000@fido.nc.rr.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-16.3 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Jim,

The correct site is www.pdnets.com/ietf/tewg/ietf57

-Siva

At 11:04 AM 7/22/2003 -0400, Jim Boyle wrote:

>They are available at wwww.pdnets.com/ietf/tewg/ietf57
>
>thanks!
>
>Jim




From owner-te-wg@ops.ietf.org  Wed Jul 23 09:02:06 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10583
	for <tewg-archive@lists.ietf.org>; Wed, 23 Jul 2003 09:02:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19fJAS-000L6p-2M
	for te-wg-data@psg.com; Wed, 23 Jul 2003 12:56:28 +0000
Received: from [202.3.77.137] (helo=web15207.mail.bjs.yahoo.com)
	by psg.com with smtp (Exim 4.14)
	id 19fJ9v-000L2E-Dk
	for te-wg@ops.ietf.org; Wed, 23 Jul 2003 12:55:55 +0000
Message-ID: <20030723125521.55088.qmail@web15207.mail.bjs.yahoo.com>
Received: from [218.72.17.156] by web15207.mail.bjs.yahoo.com via HTTP; Wed, 23 Jul 2003 20:55:21 CST
Date: Wed, 23 Jul 2003 20:55:21 +0800 (CST)
From: =?gb2312?q?Jing=20Shen?= <jshen_cad@yahoo.com.cn>
Subject: load distribution and smoothing when route flaps
To: end2end-interest@postel.org
Cc: routing-discussion@ietf.org, OSPF@PEACH.EASE.LSOFT.COM, te-wg@ops.ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=gb2312
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, hits=-1.6 required=5.0
	tests=BAYES_30
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi, (' spamcontrol ')

In past days, we talked with someone from one of the
main ISP in China. He present us a question as: how to
smooth load migration when the primary outgoing link
goes down? The network topo. could be abbreviated as:

   Secondary outgoing link           backup link
    -----                      ------
         \                   /
          \                 /
          --------------------
          |     AS (OSPF)    |
          --------------------
                  |
                  | primary outgoing link
                  |

In normal state, about 90% outgoing traffic flows
through primary outgoing link, 10% or less on
Secondary link.( the bandwidht of primary is times of
secondary link, which is more than backup link)


The problem comes when primary outgoing link goes
down. At this time, they(ISP engineers) have to
redirect traffic to backup link and secondary link
manually if the other two links are needed to be used,
or only secondary link will carry all traffic. When
primary link comes up, the phenomenon is: neary all
traffic migrates to primary link and load on primary
link may reach 100% or so. 

the questions:

1. How does those ISPs around make full use of
outgoing link capacity as well as guaranteeing service
quality?

2. Is there any method proposed to smooth traffic
migration in either intra-AS or inter-AS situation?
How does those ISPs deal with such situation?

3. Although DiffServ has been discussed for years,
they do not deploy it. Why should we talk so much
about DS-TE ?  

4. We've spent a lot time with e2e policy around, but
if the traffic delivery method is kept to very simple
one, is that skeptible to achive a cost-effective and
high performance network without introducing more
intellenge into core networks? 

thanks a lot.

regards



=====
Jing Shen

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

_________________________________________________________
Do You Yahoo!? 
暑期大片齐聚雅虎通 网络摄像头+雅虎通调频收音机等你来拿
http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.promo.yahoo.com/minisite/messenger1/



From owner-te-wg@ops.ietf.org  Wed Jul 23 09:13: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 JAA11101
	for <tewg-archive@lists.ietf.org>; Wed, 23 Jul 2003 09:13:48 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19fJPs-000M6p-TX
	for te-wg-data@psg.com; Wed, 23 Jul 2003 13:12:24 +0000
Received: from [195.207.101.240] (helo=relay1.alcatel.be)
	by psg.com with esmtp (Exim 4.14)
	id 19fJPW-000M5r-NP
	for te-wg@ops.ietf.org; Wed, 23 Jul 2003 13:12:02 +0000
Received: from bemail05.net.alcatel.be (bemail05.net.alcatel.be [138.203.144.16])
	by relay1.alcatel.be (8.12.9/8.12.4) with ESMTP id h6NDBlrH000072;
	Wed, 23 Jul 2003 15:11:48 +0200 (MEST)
Received: from alcatel.be ([138.203.64.173])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003072315114669:2925 ;
          Wed, 23 Jul 2003 15:11:46 +0200 
Message-ID: <3F1E8999.9070800@alcatel.be>
Date: Wed, 23 Jul 2003 15:11:53 +0200
From: Dimitri.Papadimitriou@alcatel.be
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: te-wg@ops.ietf.org
CC: Jim Boyle <jboyle@pdnets.com>
Subject: Re: Minutes and Presentations from TEWG at IETF57
References: <Pine.LNX.4.44.0307221103530.12216-100000@fido.nc.rr.com>
In-Reply-To: <Pine.LNX.4.44.0307221103530.12216-100000@fido.nc.rr.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 07/23/2003 15:11:46,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 07/23/2003 15:11:48,
	Serialize complete at 07/23/2003 15:11:48
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
X-Spam-Status: No, hits=-33.8 required=5.0
	tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,NO_REAL_NAME,
	      REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_MOZILLA_UA
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

jim,

would you please rephrase:

 > Dmitri P: What new from hierarchy is crossing a region as opposed
 > to only a technology-driven interface from the hierarchy draft (??)

"Dimitri P: What's new here is the rules for crossing a region as
opposed to (as specified in the LSP hierarchy draft using the
switching capability field of the ISC descriptor sub-TLV) the
crossing of a technology boundary to form forwarding adjacencies
It would be worth to be expand on this."

note: i've asked this because in the case of ABR, AS's it is
clear, but for gmpls-overlay i would think that a clearer def.
for region crossing would be advisable ? this i-d mentions:

"The solution, therefore, also aims to be applicable to the GMPLS
overlay model ([GMPLS-OVERLAY]), where the client requesting the
LSP setup would belong to a region different from the core network
region."

Taking the following example is the boundary at the Edge_Node, the
Core_Node (or both) or at the Edge-to-Core boundary ?

Edge_Node --- Core_Node --- ... --- Core_Node --- Edge_Node

as notice in gmpls-overlay which refers to the lsp-hierarchy i-d
the former is assumed (since using the "technology boundary"
between the Edge and the Core node) thus should i infer here
that it refers to the Core_Node here (it seems to be the case,
from explanations received offline)? but clarifications wouldn't
hurt anyway

thanks,
- dimitri.
Jim Boyle wrote:

> They are available at wwww.pdnets.com/ietf/tewg/ietf57
> 
> thanks!
> 
> Jim
> 
> 

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




From owner-te-wg@ops.ietf.org  Wed Jul 23 09:33: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 JAA12173
	for <tewg-archive@lists.ietf.org>; Wed, 23 Jul 2003 09:33:04 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19fJiF-000NJj-8q
	for te-wg-data@psg.com; Wed, 23 Jul 2003 13:31:23 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19fJiC-000NIO-HD
	for te-wg@ops.ietf.org; Wed, 23 Jul 2003 13:31:20 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h6NDUllO018146
	for <te-wg@ops.ietf.org>; Wed, 23 Jul 2003 09:30:47 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h6NDUlrK018142
	for <te-wg@ops.ietf.org>; Wed, 23 Jul 2003 09:30:47 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Wed, 23 Jul 2003 09:30:47 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: Re: Minutes and Presentations from TEWG at IETF57
In-Reply-To: <Pine.LNX.4.44.0307221103530.12216-100000@fido.nc.rr.com>
Message-ID: <Pine.LNX.4.44.0307230929440.18138-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-24.0 required=5.0
	tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTE_TWICE_1,
	      USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


that should be www.pdnets.com/ietf/tewg/ietf57
(had an extra w in there)
Also, it was pointed out that Kireeti's presentation is not
in there so this directory will be updated in the next day
or so (then they all will be posted to IETF proceedings).

thanks.

Jim

On Tue, 22 Jul 2003, Jim Boyle wrote:

> 
> They are available at wwww.pdnets.com/ietf/tewg/ietf57
> 
> thanks!
> 
> Jim
> 
> 
> 




From owner-te-wg@ops.ietf.org  Thu Jul 24 12:36:22 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13474
	for <tewg-archive@lists.ietf.org>; Thu, 24 Jul 2003 12:36:21 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19fizA-000BC2-Kt
	for te-wg-data@psg.com; Thu, 24 Jul 2003 16:30:32 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.14)
	id 19fiz7-000BBg-Mo
	for te-wg@ops.ietf.org; Thu, 24 Jul 2003 16:30:29 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13015;
	Thu, 24 Jul 2003 12:30:24 -0400 (EDT)
Message-Id: <200307241630.MAA13015@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-06.txt
Date: Thu, 24 Jul 2003 12:30:23 -0400
X-Spam-Status: No, hits=-2.7 required=5.0
	tests=BAYES_10,MIME_BOUND_NEXTPART,NO_REAL_NAME,TO_MALFORMED
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Requirements for Internet Traffic Engineering 
                          Measurement
	Author(s)	: W. Lai, R. Tibbs, S. Van den Berghe
	Filename	: draft-ietf-tewg-measure-06.txt
	Pages		: 27
	Date		: 2003-7-24
	
In this document, we identify requirements for supporting the 
traffic engineering of IP networks.  Requirements for traffic 
measurement in service provider environments are presented and 
justified, and related issues are discussed. 
Highlights of requirements are: 
1. To aid network dimensioning, mechanisms to collect node-pair-
based traffic data are required to facilitate the derivation of per-
service-class traffic matrix statistics.  
2. For service assurance, the use of higher-order statistics is 
required. 
3. To preserve representative traffic detail at manageable sample 
volumes, packet-sampled measurements are required. 
4. To manage large volumes of measured data, use of bulk transfer 
and filtering/aggregation mechanisms are required.

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Fri Jul 25 09:18: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 JAA04077
	for <tewg-archive@lists.ietf.org>; Fri, 25 Jul 2003 09:18:23 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14)
	id 19g2Mx-000N7x-8G
	for te-wg-data@psg.com; Fri, 25 Jul 2003 13:12:23 +0000
Received: from [66.57.28.45] (helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 4.14)
	id 19g2Mu-000N6A-Aw
	for te-wg@ops.ietf.org; Fri, 25 Jul 2003 13:12:20 +0000
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.8/8.12.5) with ESMTP id h6PDBmlO022108
	for <te-wg@ops.ietf.org>; Fri, 25 Jul 2003 09:11:49 -0400
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.8/8.12.5/Submit) with ESMTP id h6PDBeIB022104
	for <te-wg@ops.ietf.org>; Fri, 25 Jul 2003 09:11:48 -0400
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Fri, 25 Jul 2003 09:11:40 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
Subject: Re: Minutes and Presentations from TEWG at IETF57
In-Reply-To: <Pine.LNX.4.44.0307230929440.18138-100000@fido.nc.rr.com>
Message-ID: <Pine.LNX.4.44.0307250911140.18138-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-23.2 required=5.0
	tests=BAYES_10,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTE_TWICE_1,
	      USER_AGENT_PINE,X_AUTH_WARNING
	autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


It's a wrap - all presentations are up there (and I changed Dimitri's 
comment in the minutes).

Thanks!

Jim

On Wed, 23 Jul 2003, Jim Boyle wrote:

> 
> that should be www.pdnets.com/ietf/tewg/ietf57
> (had an extra w in there)
> Also, it was pointed out that Kireeti's presentation is not
> in there so this directory will be updated in the next day
> or so (then they all will be posted to IETF proceedings).
> 
> thanks.
> 
> Jim
> 
> On Tue, 22 Jul 2003, Jim Boyle wrote:
> 
> > 
> > They are available at wwww.pdnets.com/ietf/tewg/ietf57
> > 
> > thanks!
> > 
> > Jim
> > 
> > 
> > 
> 
> 




From owner-te-wg@ops.ietf.org  Mon Jul 28 08:05:39 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28716
	for <tewg-archive@lists.ietf.org>; Mon, 28 Jul 2003 08:05:38 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19h6cG-000GDZ-Ng
	for te-wg-data@psg.com; Mon, 28 Jul 2003 11:56:36 +0000
Received: from [192.128.134.71] (helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 4.20)
	id 19h6cE-000G9S-F1
	for te-wg@ops.ietf.org; Mon, 28 Jul 2003 11:56:34 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h6SBkQ0c006055
	for <te-wg@ops.ietf.org>; Mon, 28 Jul 2003 06:56:04 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EE9217C00FC341C; Mon, 28 Jul 2003 07:55:56 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: I-D ACTION:draft-ietf-tewg-measure-06.txt
Date: Mon, 28 Jul 2003 06:56:03 -0500
Message-ID: <7AFE40EF30EE754DA967D1B5968457CA02165CFF@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: I-D ACTION:draft-ietf-tewg-measure-06.txt
Thread-Index: AcNSAwntnVJHFebaQv+ERDUnKS2GTQAuRPfg
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=0.0 required=5.0
	tests=none
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Bert and all,
  Many thanks for the AD review and the subsequent comments.
We have now completed our revision of the TE Measurement draft
based on your inputs.  The main body of document has been much
shortened and streamlined - with requirements clearly identified.
Supporting materials have been moved to Appendices.
  Please review.
Thanks, Wai Sum

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
Sent: Thursday, July 24, 2003 12:30 PM
Cc: te-wg@ops.ietf.org
Subject: I-D ACTION:draft-ietf-tewg-measure-06.txt


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

	Title		: Requirements for Internet Traffic Engineering=20
                          Measurement
	Author(s)	: W. Lai, R. Tibbs, S. Van den Berghe
	Filename	: draft-ietf-tewg-measure-06.txt
	Pages		: 27
	Date		: 2003-7-24
=09
In this document, we identify requirements for supporting the=20
traffic engineering of IP networks.  Requirements for traffic=20
measurement in service provider environments are presented and=20
justified, and related issues are discussed.=20
Highlights of requirements are:=20
1. To aid network dimensioning, mechanisms to collect node-pair-
based traffic data are required to facilitate the derivation of per-
service-class traffic matrix statistics. =20
2. For service assurance, the use of higher-order statistics is=20
required.=20
3. To preserve representative traffic detail at manageable sample=20
volumes, packet-sampled measurements are required.=20
4. To manage large volumes of measured data, use of bulk transfer=20
and filtering/aggregation mechanisms are required.

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



From owner-te-wg@ops.ietf.org  Thu Jul 31 14:55: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 OAA08221
	for <tewg-archive@lists.ietf.org>; Thu, 31 Jul 2003 14:55:03 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.20)
	id 19iITD-000Kcq-AW
	for te-wg-data@psg.com; Thu, 31 Jul 2003 18:48:11 +0000
Received: from [192.128.133.69] (helo=kcmso1.proxy.att.com)
	by psg.com with esmtp (Exim 4.20)
	id 19iITA-000KcV-Ie
	for te-wg@ops.ietf.org; Thu, 31 Jul 2003 18:48:08 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by kcmso1.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h6VIfU3D003377
	for <te-wg@ops.ietf.org>; Thu, 31 Jul 2003 13:48:08 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (6.5.032)
        id 3EE9217C0112EB3D for te-wg@ops.ietf.org; Thu, 31 Jul 2003 14:47:59 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: BCP Documents on ISP Uses, Requirements, Desires for TE (TEBCPs)
Date: Thu, 31 Jul 2003 13:48:07 -0500
Message-ID: <9473683187ADC049A855ED2DA739ABCA011BEBB5@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Could you assist
Thread-Index: AcMilx3COfGZ6QJeQGeN1KLlDYCe4QBxKEYgDMlQc9A=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
X-Spam-Status: No, hits=-6.6 required=5.0
	tests=BAYES_01
	version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

All,

Regarding the TEWG milestone 'BCP documents on ISP uses, requirements, =
desires (TEBCPs)', various drafts were submitted, including:

http://www.watersprings.org/links/mlr/id/draft-springer-te-level3bcp-00.t=
xt (expired)
http://www.faqs.org/ftp/internet-drafts/draft-liljenstolpe-tewg-cwbcp-02.=
txt (expired)
http://www.watersprings.org/links/mlr/id/draft-ietf-tewg-qos-routing-04.t=
xt (not accepted by IESG for publication)
=20
To date, no BCPs have been published by the TEWG related to this work =
item.

However, the ITU-T has recently published the E.360 Series of 7 =
Recommendations on 'QoS Routing & Traffic Engineering Methods' (the full =
text and summaries are available at =
http://www.research.att.com/~jrex/jerry/ and a Liaison Statement to the =
IETF is posted at http://www.ietf.org/IESG/LIAISON/COM2-076.htm).  The =
Recommendations provide a basis for QoS routing and TE for IP-based =
multiservice networks, based on widely deployed best practices and =
network modeling/analysis.  As such, they are relevant to the request =
from the TEWG for service provider uses, requirements, and desires for =
traffic engineering best current practices. =20

In the E.360 Series, analysis models are used to demonstrate that =
currently operational TE/QoS routing methods and best current practices =
are extensible to QoS routing and TE for IP/MPLS networks.  The methods =
addressed include call and connection routing, QoS resource management, =
routing table management, dynamic transport routing, capacity =
management, and operational requirements.  Based on the results of these =
studies as well as established practice and experience, methods for =
dynamic QoS routing and admission control are proposed for consideration =
in network migration to IP-based technologies.=20

Also available at http://www.research.att.com/~jrex/jerry/ is a recently =
published Computer Communications paper based on this work, entitled =
"Performance evaluation of QoS-routing methods for IP-based multiservice =
networks'.  The paper provides a performance analysis of lost/delayed =
traffic and control load for various QoS routing methods, and shows that =
a) aggregated per-virtual-network bandwidth allocation compares =
favorably with per-flow allocation, and b) event-dependent routing =
methods for management of LSPs perform as well or better than =
state-dependent routing methods with flooding, and significantly enhance =
network scalability.

Thanks,
Jerry Ash




