From owner-te-wg@ops.ietf.org  Sun Feb  2 15:30:21 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11475
	for <tewg-archive@lists.ietf.org>; Sun, 2 Feb 2003 15:30:21 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18fQgA-000Pxt-00
	for te-wg-data@psg.com; Sun, 02 Feb 2003 12:25:26 -0800
Received: from f234.law8.hotmail.com ([216.33.241.234] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18fQg8-000Pxh-00
	for te-wg@ops.ietf.org; Sun, 02 Feb 2003 12:25:24 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 2 Feb 2003 12:25:24 -0800
Received: from 12.86.6.192 by lw8fd.law8.hotmail.msn.com with HTTP;
	Sun, 02 Feb 2003 20:25:23 GMT
X-Originating-IP: [12.86.6.192]
From: "Spyros Kontogiorgis" <spyroskon@hotmail.com>
To: te-wg@ops.ietf.org
Subject: Re: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Sun, 02 Feb 2003 13:25:23 -0700
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F234tPJkRK0D8LEHlA90000650d@hotmail.com>
X-OriginalArrivalTime: 02 Feb 2003 20:25:24.0089 (UTC) FILETIME=[3728E690:01C2CAF9]
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Thumbs up from me for the doc. Glad to see some of
my suggestions incorporated.

Spyros Kontogiorgis.

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




From owner-te-wg@ops.ietf.org  Sun Feb  2 16:27:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12104
	for <tewg-archive@lists.ietf.org>; Sun, 2 Feb 2003 16:27:26 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18fRfm-0001aN-00
	for te-wg-data@psg.com; Sun, 02 Feb 2003 13:29:06 -0800
Received: from byd.ocn.ad.jp ([203.139.162.147])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18fRfj-0001aB-00
	for te-wg@ops.ietf.org; Sun, 02 Feb 2003 13:29:03 -0800
Received: from ibm (localhost [127.0.0.1])
	by byd.ocn.ad.jp (8.8.8/3.6W) with ESMTP id GAA11794;
	Mon, 3 Feb 2003 06:28:51 +0900 (JST)
Date: Mon, 03 Feb 2003 06:30:40 +0900
From: Yuichi Ikejiri <y.ikejiri@ntt.com>
To: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: Re: new version: draft-zhang-mpls-interas-te-req-01.txt
Cc: te-wg@ops.ietf.org
In-Reply-To: <4.3.2.7.2.20021220121148.051b97c0@paris.cisco.com>
References: <4.3.2.7.2.20021220121148.051b97c0@paris.cisco.com>
Message-Id: <20030203061704.9E16.Y.IKEJIRI@ntt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.00.03
X-Spam-Status: No, hits=-2.1 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi, 

I think that this requirement documents are basically good to 
develop further inter-as discussion.

I am not sure if some possible scenario or function are addressed 
explicitly in this document.

 - the case of inter-as tunnel between PE/RSP and PE/GSP, not ce-to-ce.
      - there could be some cases that SPs don't want to 
        establish tunnels between ce-to-ce in the case of Scenario
        III, equal peering type.
 - the functionality or case of interconencting each MPLS TE LSP at ASBR.
      - there could be some cases that RSP or GRP's internal 
        MPLS TEs are connected to Inter-AS TE at ASBR.

Regards,
Yuichi Ikejiri
NTT Communications Corporation

On Fri, 20 Dec 2002 13:39:28 -0500
Jean Philippe Vasseur <jvasseur@cisco.com> wrote:

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




From owner-te-wg@ops.ietf.org  Mon Feb  3 08:57:08 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07789
	for <tewg-archive@lists.ietf.org>; Mon, 3 Feb 2003 08:57:08 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18fh3D-0009e1-00
	for te-wg-data@psg.com; Mon, 03 Feb 2003 05:54:19 -0800
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18fh3B-0009dj-00
	for te-wg@ops.ietf.org; Mon, 03 Feb 2003 05:54:17 -0800
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h13DsFd17887
	for <te-wg@ops.ietf.org>; Mon, 3 Feb 2003 08:54:15 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <DVZNP0P1>; Mon, 3 Feb 2003 14:54:10 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155C83ECE@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Kireeti Kompella (E-mail)" <kireeti@juniper.net>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: tewg-mib revision 3
Date: Mon, 3 Feb 2003 14:54:04 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=0.7 required=5.0
	tests=EXCHANGE_SERVER,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

I should do an AD or MIB-doctor review of this MIB again
I think. But for now, I see things like:

   tePathTunnelIndex OBJECT-TYPE
       SYNTAX     Unsigned32
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that identifies the Tunnel to which this path
            belongs.  A Tunnel Path index MUST NOT be zero."
       ::= { tePathEntry 1 }

   tePathIndex OBJECT-TYPE
       SYNTAX     Unsigned32
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that uniquely identifies a path within a Tunnel.
            The combination of <tePathTunnelIndex, tePathIndex> thus
            uniquely identifies a path among all paths on this router.
            This index MUST NOT be zero."
       ::= { tePathEntry 2 }

The way to specify that an INDEX (or actually any object) MUST NOT
be zero is with a range, as follows:

   tePathTunnelIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that identifies the Tunnel to which this path
            belongs."
       ::= { tePathEntry 1 }

   tePathIndex OBJECT-TYPE
       SYNTAX     Unsigned32 (1..4294967295)
       MAX-ACCESS not-accessible
       STATUS     current
       DESCRIPTION
           "An index that uniquely identifies a path within a Tunnel.
            The combination of <tePathTunnelIndex, tePathIndex> thus
            uniquely identifies a path among all paths on this router."
       ::= { tePathEntry 2 }

That way, it is programmatically parsable too!

Thanks,
Bert 



From owner-te-wg@ops.ietf.org  Mon Feb  3 13:01:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15127
	for <tewg-archive@lists.ietf.org>; Mon, 3 Feb 2003 13:01:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18fktX-000GpD-00
	for te-wg-data@psg.com; Mon, 03 Feb 2003 10:00:35 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18fktT-000Gow-00
	for te-wg@ops.ietf.org; Mon, 03 Feb 2003 10:00:31 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h13I0IUq002196;
	Mon, 3 Feb 2003 18:00:18 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id SAA08946;
	Mon, 3 Feb 2003 18:00:16 GMT
Message-Id: <5.1.0.14.0.20030203094555.027ed5b0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 03 Feb 2003 10:00:08 -0800
To: Yuichi Ikejiri <y.ikejiri@ntt.com>,
        Jean Philippe Vasseur <jvasseur@cisco.com>
From: raymond zhang <zhangr@info.net>
Subject: Re: new version: draft-zhang-mpls-interas-te-req-01.txt
Cc: te-wg@ops.ietf.org
In-Reply-To: <20030203061704.9E16.Y.IKEJIRI@ntt.com>
References: <4.3.2.7.2.20021220121148.051b97c0@paris.cisco.com>
 <4.3.2.7.2.20021220121148.051b97c0@paris.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-1.3 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yuichi,

At 06:30 AM 2/3/2003 +0900, Yuichi Ikejiri wrote:
>Hi,
>
>I think that this requirement documents are basically good to
>develop further inter-as discussion.
>
>I am not sure if some possible scenario or function are addressed
>explicitly in this document.
>
>  - the case of inter-as tunnel between PE/RSP and PE/GSP, not ce-to-ce.
>       - there could be some cases that SPs don't want to
>         establish tunnels between ce-to-ce in the case of Scenario
>         III, equal peering type.

This case can be covered in case I of Scenario II, section 4.2 by extending 
the inter-AS TE tunnel ending from GSP/ASBR to GSP/PE...  I'll update the 
draft in -02 to reflect this point. Thanks.


>  - the functionality or case of interconencting each MPLS TE LSP at ASBR.
>       - there could be some cases that RSP or GRP's internal
>         MPLS TEs are connected to Inter-AS TE at ASBR.

I am not sure of this point... it would be good if you could provide an 
example or elaborate a bit more ?  Inter-AS TE tunnel as defined in this 
draft is intended to be established end-to-end, not by segments stitched 
together...  Section 5.8 defines the requirements of TE LSP aggregation 
whereby an Inter-AS TE tunnel may be aggregated onto the intra-AS MPLS-TE 
LSP so as to reduce the # of tunnel states...



>Regards,
>Yuichi Ikejiri
>NTT Communications Corporation
>
>On Fri, 20 Dec 2002 13:39:28 -0500
>Jean Philippe Vasseur <jvasseur@cisco.com> wrote:
>
> > Hi,
> >
> > First of all, thanks for the various comments we received and that are now
> > integrated in the version -01 of the inter-AS TE requirements draft (just
> > posted:
> > 
> http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-01.txt).
> > Some other Service Providers will join the draft in the next release. Your
> > comments on the list are very welcome.
> >
> > Thanks.
> >
> > JP.
> >
> >





From owner-te-wg@ops.ietf.org  Wed Feb  5 08:52:33 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25113
	for <tewg-archive@lists.ietf.org>; Wed, 5 Feb 2003 08:52:32 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gPu3-000Fz4-00
	for te-wg-data@psg.com; Wed, 05 Feb 2003 05:47:51 -0800
Received: from byd.ocn.ad.jp ([203.139.162.147])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gPtt-000Fxe-00
	for te-wg@ops.ietf.org; Wed, 05 Feb 2003 05:47:41 -0800
Received: from ibm (localhost [127.0.0.1])
	by byd.ocn.ad.jp (8.8.8/3.6W) with ESMTP id WAA08989;
	Wed, 5 Feb 2003 22:47:05 +0900 (JST)
Date: Wed, 05 Feb 2003 22:48:50 +0900
From: Yuichi Ikejiri <y.ikejiri@ntt.com>
To: "raymond zhang" <zhangr@info.net>
Subject: Re: new version: draft-zhang-mpls-interas-te-req-01.txt
Cc: "Jean Philippe Vasseur" <jvasseur@cisco.com>, te-wg@ops.ietf.org
In-Reply-To: <5.1.0.14.0.20030203094555.027ed5b0@delta.info.net>
References: <20030203061704.9E16.Y.IKEJIRI@ntt.com> <5.1.0.14.0.20030203094555.027ed5b0@delta.info.net>
Message-Id: <20030205203043.3F46.Y.IKEJIRI@ntt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.00.03
X-Spam-Status: No, hits=-1.3 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Raymond,

> >  - the functionality or case of interconencting each MPLS TE LSP at ASBR.
> >       - there could be some cases that RSP or GRP's internal
> >         MPLS TEs are connected to Inter-AS TE at ASBR.
> 
> I am not sure of this point... it would be good if you could provide an 
> example or elaborate a bit more ?  Inter-AS TE tunnel as defined in this 
> draft is intended to be established end-to-end, not by segments stitched 
> together...  Section 5.8 defines the requirements of TE LSP aggregation 
> whereby an Inter-AS TE tunnel may be aggregated onto the intra-AS MPLS-TE 
> LSP so as to reduce the # of tunnel states...
I assume the case below.

CE1--RSP(PE)---ASBR----ASBR----GSP(PE)----CE2
 <------Inter-AS-TE---------><----Internal-TE--->
                                      ~~~~
                  (interconnecting or mapping)

You mention vrf to inter-as-TE mapping at ASBR in Section5.9 but  
I think that the mapping function would not be limmited to vrf cases 
as a general requirement, even if any specific function might not be
needed as a result or be out of scope of this document.

Regards,
Yuichi 

> 
> 
> >Regards,
> >Yuichi Ikejiri
> >NTT Communications Corporation
> >
> >On Fri, 20 Dec 2002 13:39:28 -0500
> >Jean Philippe Vasseur <jvasseur@cisco.com> wrote:
> >
> > > Hi,
> > >
> > > First of all, thanks for the various comments we received and that are now
> > > integrated in the version -01 of the inter-AS TE requirements draft (just
> > > posted:
> > > 
> > http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-01.txt).
> > > Some other Service Providers will join the draft in the next release. Your
> > > comments on the list are very welcome.
> > >
> > > Thanks.
> > >
> > > JP.
> > >
> > >
> 





From owner-te-wg@ops.ietf.org  Wed Feb  5 09:29: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 JAA26530
	for <tewg-archive@lists.ietf.org>; Wed, 5 Feb 2003 09:29:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gQVe-000He8-00
	for te-wg-data@psg.com; Wed, 05 Feb 2003 06:26:42 -0800
Received: from plinius.intec2.rug.ac.be ([157.193.122.4])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gQVb-000Hdw-00
	for te-wg@ops.ietf.org; Wed, 05 Feb 2003 06:26:39 -0800
Received: from localhost (localhost [127.0.0.1])
	by plinius.intec2.rug.ac.be (Postfix) with ESMTP
	id 22706BD2F; Wed,  5 Feb 2003 15:26:37 +0100 (CET)
Received: from daisne.intec2.rug.ac.be (daisne.intec2.rug.ac.be [157.193.122.92])
	by plinius.intec2.rug.ac.be (Postfix) with ESMTP
	id B8CF7BD28; Wed,  5 Feb 2003 15:26:35 +0100 (CET)
From: Steven Van den Berghe <steven.vandenberghe@intec.rug.ac.be>
To: te-wg@ops.ietf.org
Subject: Fwd: TR: Comments on draft-ietf-tewg-measure-04.txt
Date: Wed, 5 Feb 2003 15:26:33 +0100
User-Agent: KMail/1.5
MIME-Version: 1.0
Cc: "Lai, Wai S (Waisum), ALASO" <wlai@att.com>,
        "Dr. Richard W. Tibbs" <drtibbs@oakcitysolutions.com>,
        <rwtibbs@radford.edu>, christian.jacquenet@francetelecom.com
Content-Type: Multipart/Mixed;
  boundary="Boundary-00=_Z8RQ+7suKEfYa5x"
Message-Id: <200302051526.33875.steven.vandenberghe@intec.rug.ac.be>
X-Virus-Scanned: by AMaViS snapshot-20020222
X-Spam-Status: No, hits=-1.1 required=5.0
	tests=FWD_MSG,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01,USER_AGENT
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


--Boundary-00=_Z8RQ+7suKEfYa5x
Content-Type: text/plain;
  charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit


-- 
Steven Van den Berghe
steven.vandenberghe@intec.rug.ac.be
Workgroup Broadband Communication Networks
Department Information Technology
Ghent University - Belgium
Phone:  +32 (0)9 267 35 86 | Fax  :  +32 (0)9 267 35 99
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
A computer scientist is someone who, when told to 'Go to Hell',
sees the 'go to', rather than the destination, as harmful.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

--Boundary-00=_Z8RQ+7suKEfYa5x
Content-Type: message/rfc822;
  name="forwarded message"
Content-Description: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>: TR: Comments on draft-ietf-tewg-measure-04.txt

Received: by plinius (mbox svdberg)
 (with Cubic Circle's cucipop (v1.31 1998/05/13) Wed Feb  5 12:15:00 2003)
X-From_: christian.jacquenet@francetelecom.com  Wed Feb  5 12:13:03 2003
Return-Path: <christian.jacquenet@francetelecom.com>
Delivered-To: svdberg@intec2.rug.ac.be
Received: from localhost (localhost [127.0.0.1])
	by plinius.intec2.rug.ac.be (Postfix) with ESMTP id 628C1BD2F
	for <svdberg@intec2.rug.ac.be>; Wed,  5 Feb 2003 12:13:03 +0100 (CET)
Received: from intec.rug.ac.be (mail.intec.rug.ac.be [157.193.172.4])
	by plinius.intec2.rug.ac.be (Postfix) with ESMTP id F0F97BD28
	for <steven.vandenberghe@intec2.rug.ac.be>; Wed,  5 Feb 2003 12:13:02 +0100 (CET)
Received: by intec.rug.ac.be (Postfix)
	id 8F528BD3D; Wed,  5 Feb 2003 12:13:31 +0100 (CET)
Delivered-To: svdberg@intec.rug.ac.be
Received: from mserv.rug.ac.be (mserv.rug.ac.be [157.193.40.37])
	by intec.rug.ac.be (Postfix) with ESMTP id 7AB44BD3A
	for <steven.vandenberghe@intec.rug.ac.be>; Wed,  5 Feb 2003 12:13:31 +0100 (CET)
Received: from relais-inet-04.francetelecom.fr (relais-inet.francetelecom.com [212.234.67.6])
	by mserv.rug.ac.be (8.12.6/8.12.6) with ESMTP id h15BCwmB019453
	for <steven.vandenberghe@intec.rug.ac.be>; Wed, 5 Feb 2003 12:12:58 +0100 (MET)
Received: from [193.248.188.48] by relais-filtrant-04.francetelecom.fr with ESMTP for steven.vandenberghe@intec.rug.ac.be; Wed, 5 Feb 2003 12:10:52 +0100
Received: from fedft01a.francetelecom.fr by relais-filtrant-04.francetelecom.fr with ESMTP for steven.vandenberghe@intec.rug.ac.be; Wed, 5 Feb 2003 12:10:52 +0100
Received: from [193.249.139.219] by fedft01a.francetelecom.fr with ESMTP for steven.vandenberghe@intec.rug.ac.be; Wed, 5 Feb 2003 12:10:51 +0100
Received: from igt2bg036 ([10.165.209.44]) by
          smtp7.smtpft.francetelecom.fr (Netscape Messaging Server 4.15)
          with SMTP id H9U1Q200.79B for
          <steven.vandenberghe@intec.rug.ac.be>; Wed, 5 Feb 2003 12:10:50 +0100 
Reply-To: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
From: "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
To: <steven.vandenberghe@intec.rug.ac.be>
Subject: TR: Comments on draft-ietf-tewg-measure-04.txt
Date: Wed, 5 Feb 2003 12:10:24 +0100
Message-Id: <003601c2cd07$2ef57aa0$2cd1a50a@buriapren.w2k.francetelecom.fr>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
X-Priority: 1 (Highest)
X-MSMail-Priority: High
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: High
X-Virus-Scanned: by AMaViS snapshot-20020222
Status: R 
X-Status: N
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
Content-Transfer-Encoding: 8bit

Steven,

For some reason, it seems I've been unsusbcribed from the tewg list:
therefore, I'm not sure this mail has been actually received by the WG
members - it doesn't appear on the archive yet) - could you check this for
me and possibliy forward it to the list, since I'll be out of my office
until next tuesday?

Thanx and cheers,

Christian.

>  -----Message d'origine-----
> De : 	Christian JACQUENET
> [mailto:christian.jacquenet@francetelecom.com]
> Envoyé :	mercredi 5 février 2003 11:39
> À :	'te-wg@ops.ietf.org'
> Objet :	Comments on draft-ietf-tewg-measure-04.txt
> Importance :	Haute
>
> Dear all,
>
> Since the last call deadline for the aforementioned document
> is now very close, here's a couple of comments on this draft
> (sorry about the late show-up).
>
> 1. First of all, to answer Jim's question about the on/off
> target topic, I think the document is perfectly on target, as
> it represents a concise and valuable input for addressing the
> TE measurement issue.
>
> 2. Section 1 (page 1) and in other sections as well: why not
> simply talk about IP networks, rather than "IP-based"
> networks, which may somehow introduce confusion?
>
> 3. Section 4.1. (page 4): I think a MPLS tunnel is an
> *example* of a LSP, but there is no strict equivalence, since
> classical MPLS/LDP operation also refers to the (dynamic)
> establishement of LSP paths, without explicitly activating
> MPLS TE functions. I would therefore suggest a slight
> rewording of the definition of a path, stating that "a path
> refers to an MPLS LSP, this LSP possibly being a
> trafrfic-engineered LSP."
>
> 4. Section 4.2 (page 5): I think the definition of the
> traffic volume (second paragraph) is too restrictive, since
> the network may not have been *designed* to support the
> volume of traffic measured at a given period of time (hence
> the need for planning activities). I'm not a big fan of the
> notion of "level of traffic" either, and I would tehrefore
> suggest slight rewording such as "Traffic volume is the
> amount of traffic measured at a given period of time. Such
> measurement may/should be performed on a regular basis."
>
> 5. Section 5.2 (page 6): two comments.
> 5.1.: generally speaking, there are additional terms that are
> defined in sections different from section 4 (such as "peg
> count" (section 9.2) or  "goodput" (section 8.2): why not
> gather all these definitions in section 4, so as to provide
> some consistency as far as the organization of the document
> is concerned?
> 5.2. I can see a contradiction between the definition of
> QoS/GoS (BTW, the notion of GoS is not that widely used by
> Internet service providers - e.g. we prefer the "Class of
> Service" wording for IP networks where DiffServ mechanisms
> have been activated), as it appears in the second bullet
> (referring to end users), and as it appears in the last
> paragraph of the section (referring to inter-domain QoS). I
> would either provide a reference to RFC 2475, or simply
> delete the last sentence of the paragraph, which is rather
> confusing ("QoS delivered to external peers by an autonomous
> system" is a bit fuzzy to me).
>
> 6. Section 8 (page 9): in the second paragraph, "Currently,
> there *IS* a number of 3rd-party...".
>
> 7. Section 8 (page 10): "...a passive measurement may be to
> obtain packet inter-arrival times by time-stamping *succesive
> packets of the offered traffic* at a selected point in the
> network..." (I think it's more readable). The notion of
> *offered* traffic should deserve some elaboration, otherwise
> I would simply mention "traffic".
>
> 8. Section 9.1 (page 12): the notion of "MPLS path duration"
> should deserve some elaboration.
>
> 9. Section 9.1(page 13):
> - (first paragraph) "...and hence may *BE* used to derive..."
> - I would summarize the note about the delay variation,
> because it somehow unbalances the text with the rest of the
> section, and also because the corresponding text can be found
> in the ITU reference, hence no need to reproduce it in the draft.
>
> 10. Section 11(page 16): I think the second sentence of the
> paragraph is a bit too radical. How about: "This data may be
> gracefully used for the dynamic computation and selection of
> traffic-engineered routes that aim at complying as much as
> possible with the forementioned demands, be they p2p or p2mp"?
>
> 11. Section 11 (page 17): in the second paragraph, I would
> refer to section 8.4 instead of "section on path-based
> measurement bases" for a better readability.
>
> 12. Section 12 (page 18): in the last sentence before section
> 13, I would quote draft-ietf-mpls-lsp-ping-01.txt as a reference.
>
> 13. Section 13 (page 19): (second paragraph) "...these
> functionS to provide..."
>
> 14. Section 14.2 (page 21):
> - COPS is not an information model per se, rather a protocol.
> I would tehrefore suggest a reference to RFC 2753 instead.
> - I would talk about "policy decision points" rather than
> "policy control points"
> - I would introduce the notion of PIB rather than "LDAP
> repositories", to balance with the MIB quotation. After all,
> LDAP is a protocol (among others) to access a
> database/directory. BTW, you might want to take a look at
> http://www.ietf.org/internet-drafts/draft-jacquenet-ip-te-cops-04.txt.
>
> 15. Before section 15 (page 22): I would be tempted to drop
> some lines about some requirements on what could be the basic
> characteristics of a protocol to convey traffic measurement
> data. Something like:
>
> "Although this draft focuses on the motivation for providing
> Internet traffic measurement information, it is assumed that
> this information should be provided to the participating
> devices by means of a communication protocol that would be
> used between the aforementioned participating devices and a
> presumably centralized entity that would aim at storing,
> maintaining and updating this information, as well as making
> appropriate decisions at the right time and under various conditions.
>
> This communication protocol should have the following characteristics:
>
> 1. The protocol should use of a reliable transport mode,
> given the importance of configuration information,
> 2. The protocol architecture should provide a means for
> dynamically provision the configuration information to the
> participating devices, so that it may introduce/contribute to
> a high level of automation in the actual Internet traffic
> measurement operation,
> 3. The protocol should support a reporting mechanism that may
> be used for statistical information retrieval,
> 4. The protocol should support the appropriate security
> mechanisms to provide some guarantees as far as the
> preservation of the confidentiality of the configuration
> information is concerned."
>
> Best regards,
>
> Christian.
>     _________________    ________  ______  ______
>    /_____________   /__ /_    _ / /     / /     /   Christian
> "I'm a ZZ Fan" Jacquenet
>       /_________/  /  /   /  /   /  /  / /  /__/    France
> Telecom Long Distance IAP/CTO
>                /  /  /___/__/___/_____/_/__/____   "The blues
> has got a hold on me,
>               /__/  /__________________________/_ I believe
> I'm gettin' dizzy."
>                 /_______________________________/ - My heads
> in Mississippi.
>
>


--Boundary-00=_Z8RQ+7suKEfYa5x--




From owner-te-wg@ops.ietf.org  Wed Feb  5 09:43:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26977
	for <tewg-archive@lists.ietf.org>; Wed, 5 Feb 2003 09:43:25 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gQlT-000IMD-00
	for te-wg-data@psg.com; Wed, 05 Feb 2003 06:43:03 -0800
Received: from listserv2.radford.edu ([137.45.126.15])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gQlP-000IM0-00
	for te-wg@ops.ietf.org; Wed, 05 Feb 2003 06:42:59 -0800
Received: from virus-mail.radford.edu (virus-mail.radford.edu [137.45.126.10])
	by listserv2.radford.edu (8.11.6/8.11.6) with SMTP id h15EgtX06815
	for <te-wg@ops.ietf.org>; Wed, 5 Feb 2003 09:42:56 -0500 (EST)
Received: FROM mail-in.radford.edu BY virus-mail.radford.edu ; Wed Feb 05 09:41:14 2003 -0800
Received: from oakcitysolutions.com (dhcp-192-86.radford.edu [137.45.192.86] (may be forged))
	by mail-in.radford.edu (Switch-2.2.0/Switch-2.2.0) with ESMTP id h15EeJm32241;
	Wed, 5 Feb 2003 09:40:20 -0500
Message-ID: <3E412252.6090306@oakcitysolutions.com>
Date: Wed, 05 Feb 2003 09:40:18 -0500
From: "Dr. Richard W. Tibbs" <tewg@oakcitysolutions.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: Steven Van den Berghe <steven.vandenberghe@intec.rug.ac.be>
CC: te-wg@ops.ietf.org, "Lai, Wai S (Waisum), ALASO" <wlai@att.com>,
        rwtibbs@radford.edu, christian.jacquenet@francetelecom.com
Subject: Re: Fwd: TR: Comments on draft-ietf-tewg-measure-04.txt
References: <200302051526.33875.steven.vandenberghe@intec.rug.ac.be>
Content-Type: multipart/alternative;
 boundary="------------030003060605040209090208"
X-Spam-Status: No, hits=-3.8 required=5.0
	tests=EMAIL_ATTRIBUTION,FWD_MSG,MAILTO_LINK,MAY_BE_FORGED,
	      QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,
	      USER_AGENT_MOZILLA_UA,X_ACCEPT_LANG
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


--------------030003060605040209090208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Thanks, Christian.  This kind of critical review is very welcome.
I will be looking closely at the sections of the document that you 
identified and respond with more comments in a few days.
Rick.


Steven Van den Berghe wrote:

>
> ------------------------------------------------------------------------
>
> Subject:
>
> TR: Comments on draft-ietf-tewg-measure-04.txt
> From:
>
> "JACQUENET Christian FTLD/IAP" <christian.jacquenet@francetelecom.com>
> Date:
>
> Wed, 5 Feb 2003 12:10:24 +0100
> To:
>
> <steven.vandenberghe@intec.rug.ac.be>
>
>
>Steven,
>
>For some reason, it seems I've been unsusbcribed from the tewg list:
>therefore, I'm not sure this mail has been actually received by the WG
>members - it doesn't appear on the archive yet) - could you check this for
>me and possibliy forward it to the list, since I'll be out of my office
>until next tuesday?
>
>Thanx and cheers,
>
>Christian.
>
>> -----Message d'origine-----
>>De : 	Christian JACQUENET
>>[mailto:christian.jacquenet@francetelecom.com]
>>Envoyé :	mercredi 5 février 2003 11:39
>>À :	'te-wg@ops.ietf.org'
>>Objet :	Comments on draft-ietf-tewg-measure-04.txt
>>Importance :	Haute
>>
>>Dear all,
>>
>>Since the last call deadline for the aforementioned document
>>is now very close, here's a couple of comments on this draft
>>(sorry about the late show-up).
>>
>>1. First of all, to answer Jim's question about the on/off
>>target topic, I think the document is perfectly on target, as
>>it represents a concise and valuable input for addressing the
>>TE measurement issue.
>>
>>2. Section 1 (page 1) and in other sections as well: why not
>>simply talk about IP networks, rather than "IP-based"
>>networks, which may somehow introduce confusion?
>>
>>3. Section 4.1. (page 4): I think a MPLS tunnel is an
>>*example* of a LSP, but there is no strict equivalence, since
>>classical MPLS/LDP operation also refers to the (dynamic)
>>establishement of LSP paths, without explicitly activating
>>MPLS TE functions. I would therefore suggest a slight
>>rewording of the definition of a path, stating that "a path
>>refers to an MPLS LSP, this LSP possibly being a
>>trafrfic-engineered LSP."
>>
>>4. Section 4.2 (page 5): I think the definition of the
>>traffic volume (second paragraph) is too restrictive, since
>>the network may not have been *designed* to support the
>>volume of traffic measured at a given period of time (hence
>>the need for planning activities). I'm not a big fan of the
>>notion of "level of traffic" either, and I would tehrefore
>>suggest slight rewording such as "Traffic volume is the
>>amount of traffic measured at a given period of time. Such
>>measurement may/should be performed on a regular basis."
>>
>>5. Section 5.2 (page 6): two comments.
>>5.1.: generally speaking, there are additional terms that are
>>defined in sections different from section 4 (such as "peg
>>count" (section 9.2) or  "goodput" (section 8.2): why not
>>gather all these definitions in section 4, so as to provide
>>some consistency as far as the organization of the document
>>is concerned?
>>5.2. I can see a contradiction between the definition of
>>QoS/GoS (BTW, the notion of GoS is not that widely used by
>>Internet service providers - e.g. we prefer the "Class of
>>Service" wording for IP networks where DiffServ mechanisms
>>have been activated), as it appears in the second bullet
>>(referring to end users), and as it appears in the last
>>paragraph of the section (referring to inter-domain QoS). I
>>would either provide a reference to RFC 2475, or simply
>>delete the last sentence of the paragraph, which is rather
>>confusing ("QoS delivered to external peers by an autonomous
>>system" is a bit fuzzy to me).
>>
>>6. Section 8 (page 9): in the second paragraph, "Currently,
>>there *IS* a number of 3rd-party...".
>>
>>7. Section 8 (page 10): "...a passive measurement may be to
>>obtain packet inter-arrival times by time-stamping *succesive
>>packets of the offered traffic* at a selected point in the
>>network..." (I think it's more readable). The notion of
>>*offered* traffic should deserve some elaboration, otherwise
>>I would simply mention "traffic".
>>
>>8. Section 9.1 (page 12): the notion of "MPLS path duration"
>>should deserve some elaboration.
>>
>>9. Section 9.1(page 13):
>>- (first paragraph) "...and hence may *BE* used to derive..."
>>- I would summarize the note about the delay variation,
>>because it somehow unbalances the text with the rest of the
>>section, and also because the corresponding text can be found
>>in the ITU reference, hence no need to reproduce it in the draft.
>>
>>10. Section 11(page 16): I think the second sentence of the
>>paragraph is a bit too radical. How about: "This data may be
>>gracefully used for the dynamic computation and selection of
>>traffic-engineered routes that aim at complying as much as
>>possible with the forementioned demands, be they p2p or p2mp"?
>>
>>11. Section 11 (page 17): in the second paragraph, I would
>>refer to section 8.4 instead of "section on path-based
>>measurement bases" for a better readability.
>>
>>12. Section 12 (page 18): in the last sentence before section
>>13, I would quote draft-ietf-mpls-lsp-ping-01.txt as a reference.
>>
>>13. Section 13 (page 19): (second paragraph) "...these
>>functionS to provide..."
>>
>>14. Section 14.2 (page 21):
>>- COPS is not an information model per se, rather a protocol.
>>I would tehrefore suggest a reference to RFC 2753 instead.
>>- I would talk about "policy decision points" rather than
>>"policy control points"
>>- I would introduce the notion of PIB rather than "LDAP
>>repositories", to balance with the MIB quotation. After all,
>>LDAP is a protocol (among others) to access a
>>database/directory. BTW, you might want to take a look at
>>http://www.ietf.org/internet-drafts/draft-jacquenet-ip-te-cops-04.txt.
>>
>>15. Before section 15 (page 22): I would be tempted to drop
>>some lines about some requirements on what could be the basic
>>characteristics of a protocol to convey traffic measurement
>>data. Something like:
>>
>>"Although this draft focuses on the motivation for providing
>>Internet traffic measurement information, it is assumed that
>>this information should be provided to the participating
>>devices by means of a communication protocol that would be
>>used between the aforementioned participating devices and a
>>presumably centralized entity that would aim at storing,
>>maintaining and updating this information, as well as making
>>appropriate decisions at the right time and under various conditions.
>>
>>This communication protocol should have the following characteristics:
>>
>>1. The protocol should use of a reliable transport mode,
>>given the importance of configuration information,
>>2. The protocol architecture should provide a means for
>>dynamically provision the configuration information to the
>>participating devices, so that it may introduce/contribute to
>>a high level of automation in the actual Internet traffic
>>measurement operation,
>>3. The protocol should support a reporting mechanism that may
>>be used for statistical information retrieval,
>>4. The protocol should support the appropriate security
>>mechanisms to provide some guarantees as far as the
>>preservation of the confidentiality of the configuration
>>information is concerned."
>>
>>Best regards,
>>
>>Christian.
>>    _________________    ________  ______  ______
>>   /_____________   /__ /_    _ / /     / /     /   Christian
>>"I'm a ZZ Fan" Jacquenet
>>      /_________/  /  /   /  /   /  /  / /  /__/    France
>>Telecom Long Distance IAP/CTO
>>               /  /  /___/__/___/_____/_/__/____   "The blues
>>has got a hold on me,
>>              /__/  /__________________________/_ I believe
>>I'm gettin' dizzy."
>>                /_______________________________/ - My heads
>>in Mississippi.
>>
>>
>


--------------030003060605040209090208
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<html>
<head>
</head>
<body>
Thanks, Christian. &nbsp;This kind of critical review is very welcome. <br>
I will be looking closely at the sections of the document that you identified
and respond with more comments in a few days.<br>
Rick.<br>
<br>
<br>
Steven Van den Berghe wrote:<br>
<blockquote type="cite" cite="mid:200302051526.33875.steven.vandenberghe@intec.rug.ac.be"><br>
  <hr width="90%" size="4"><br>
  <table border="0" cellspacing="0" cellpadding="0" width="100%" name="header-part1">
    <tbody>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline; ">Subject:
        </div>
TR: Comments on draft-ietf-tewg-measure-04.txt</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline; ">From: </div>
"JACQUENET Christian FTLD/IAP" <a class="moz-txt-link-rfc2396E" href="mailto:christian.jacquenet@francetelecom.com">&lt;christian.jacquenet@francetelecom.com&gt;</a></td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline; ">Date: </div>
Wed, 5 Feb 2003 12:10:24 +0100</td>
      </tr>
      <tr>
        <td>
        <div class="headerdisplayname" style="display: inline; ">To: </div>
<a class="moz-txt-link-rfc2396E" href="mailto:steven.vandenberghe@intec.rug.ac.be">&lt;steven.vandenberghe@intec.rug.ac.be&gt;</a></td>
      </tr>
    </tbody>
  </table>
  <br>
  <pre wrap="">Steven,<br><br>For some reason, it seems I've been unsusbcribed from the tewg list:<br>therefore, I'm not sure this mail has been actually received by the WG<br>members - it doesn't appear on the archive yet) - could you check this for<br>me and possibliy forward it to the list, since I'll be out of my office<br>until next tuesday?<br><br>Thanx and cheers,<br><br>Christian.<br><br></pre>
  <blockquote type="cite">
    <pre wrap=""> -----Message d'origine-----<br>De&nbsp;: 	Christian JACQUENET<br>[<a class="moz-txt-link-freetext" href="mailto:christian.jacquenet@francetelecom.com">mailto:christian.jacquenet@francetelecom.com</a>]<br>Envoy&eacute;&nbsp;:	mercredi 5 f&eacute;vrier 2003 11:39<br>&Agrave;&nbsp;:	'<a class="moz-txt-link-abbreviated" href="mailto:te-wg@ops.ietf.org">te-wg@ops.ietf.org</a>'<br>Objet&nbsp;:	Comments on draft-ietf-tewg-measure-04.txt<br>Importance&nbsp;:	Haute<br><br>Dear all,<br><br>Since the last call deadline for the aforementioned document<br>is now very close, here's a couple of comments on this draft<br>(sorry about the late show-up).<br><br>1. First of all, to answer Jim's question about the on/off<br>target topic, I think the document is perfectly on target, as<br>it represents a concise and valuable input for addressing the<br>TE measurement issue.<br><br>2. Section 1 (page 1) and in other sections as well: why not<br>simply talk about IP networks, rat
her than "IP-based"<br>networks, which may somehow introduce confusion?<br><br>3. Section 4.1. (page 4): I think a MPLS tunnel is an<br>*example* of a LSP, but there is no strict equivalence, since<br>classical MPLS/LDP operation also refers to the (dynamic)<br>establishement of LSP paths, without explicitly activating<br>MPLS TE functions. I would therefore suggest a slight<br>rewording of the definition of a path, stating that "a path<br>refers to an MPLS LSP, this LSP possibly being a<br>trafrfic-engineered LSP."<br><br>4. Section 4.2 (page 5): I think the definition of the<br>traffic volume (second paragraph) is too restrictive, since<br>the network may not have been *designed* to support the<br>volume of traffic measured at a given period of time (hence<br>the need for planning activities). I'm not a big fan of the<br>notion of "level of traffic" either, and I would tehrefore<br>suggest slight rewording such as "Traffic volume is the<br>amount of traffic measured at a gi
ven period of time. Such<br>measurement may/should be performed on a regular basis."<br><br>5. Section 5.2 (page 6): two comments.<br>5.1.: generally speaking, there are additional terms that are<br>defined in sections different from section 4 (such as "peg<br>count" (section 9.2) or  "goodput" (section 8.2): why not<br>gather all these definitions in section 4, so as to provide<br>some consistency as far as the organization of the document<br>is concerned?<br>5.2. I can see a contradiction between the definition of<br>QoS/GoS (BTW, the notion of GoS is not that widely used by<br>Internet service providers - e.g. we prefer the "Class of<br>Service" wording for IP networks where DiffServ mechanisms<br>have been activated), as it appears in the second bullet<br>(referring to end users), and as it appears in the last<br>paragraph of the section (referring to inter-domain QoS). I<br>would either provide a reference to RFC 2475, or simply<br>delete the last sentence of the paragra
ph, which is rather<br>confusing ("QoS delivered to external peers by an autonomous<br>system" is a bit fuzzy to me).<br><br>6. Section 8 (page 9): in the second paragraph, "Currently,<br>there *IS* a number of 3rd-party...".<br><br>7. Section 8 (page 10): "...a passive measurement may be to<br>obtain packet inter-arrival times by time-stamping *succesive<br>packets of the offered traffic* at a selected point in the<br>network..." (I think it's more readable). The notion of<br>*offered* traffic should deserve some elaboration, otherwise<br>I would simply mention "traffic".<br><br>8. Section 9.1 (page 12): the notion of "MPLS path duration"<br>should deserve some elaboration.<br><br>9. Section 9.1(page 13):<br>- (first paragraph) "...and hence may *BE* used to derive..."<br>- I would summarize the note about the delay variation,<br>because it somehow unbalances the text with the rest of the<br>section, and also because the corresponding text can be found<br>in the ITU referenc
e, hence no need to reproduce it in the draft.<br><br>10. Section 11(page 16): I think the second sentence of the<br>paragraph is a bit too radical. How about: "This data may be<br>gracefully used for the dynamic computation and selection of<br>traffic-engineered routes that aim at complying as much as<br>possible with the forementioned demands, be they p2p or p2mp"?<br><br>11. Section 11 (page 17): in the second paragraph, I would<br>refer to section 8.4 instead of "section on path-based<br>measurement bases" for a better readability.<br><br>12. Section 12 (page 18): in the last sentence before section<br>13, I would quote draft-ietf-mpls-lsp-ping-01.txt as a reference.<br><br>13. Section 13 (page 19): (second paragraph) "...these<br>functionS to provide..."<br><br>14. Section 14.2 (page 21):<br>- COPS is not an information model per se, rather a protocol.<br>I would tehrefore suggest a reference to RFC 2753 instead.<br>- I would talk about "policy decision points" rather th
an<br>"policy control points"<br>- I would introduce the notion of PIB rather than "LDAP<br>repositories", to balance with the MIB quotation. After all,<br>LDAP is a protocol (among others) to access a<br>database/directory. BTW, you might want to take a look at<br><a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-jacquenet-ip-te-cops-04.txt">http://www.ietf.org/internet-drafts/draft-jacquenet-ip-te-cops-04.txt</a>.<br><br>15. Before section 15 (page 22): I would be tempted to drop<br>some lines about some requirements on what could be the basic<br>characteristics of a protocol to convey traffic measurement<br>data. Something like:<br><br>"Although this draft focuses on the motivation for providing<br>Internet traffic measurement information, it is assumed that<br>this information should be provided to the participating<br>devices by means of a communication protocol that would be<br>used between the aforementioned participating devices and a<br
>presumably centralized entity that would aim at storing,<br>maintaining and updating this information, as well as making<br>appropriate decisions at the right time and under various conditions.<br><br>This communication protocol should have the following characteristics:<br><br>1. The protocol should use of a reliable transport mode,<br>given the importance of configuration information,<br>2. The protocol architecture should provide a means for<br>dynamically provision the configuration information to the<br>participating devices, so that it may introduce/contribute to<br>a high level of automation in the actual Internet traffic<br>measurement operation,<br>3. The protocol should support a reporting mechanism that may<br>be used for statistical information retrieval,<br>4. The protocol should support the appropriate security<br>mechanisms to provide some guarantees as far as the<br>preservation of the confidentiality of the configuration<br>information is concerned."<br><br>
Best regards,<br><br>Christian.<br>    _________________    ________  ______  ______<br>   /_____________   /__ /_    _ / /     / /     /   Christian<br>"I'm a ZZ Fan" Jacquenet<br>      /_________/  /  /   /  /   /  /  / /  /__/    France<br>Telecom Long Distance IAP/CTO<br>               /  /  /___/__/___/_____/_/__/____   "The blues<br>has got a hold on me,<br>              /__/  /__________________________/_ I believe<br>I'm gettin' dizzy."<br>                /_______________________________/ - My heads<br>in Mississippi.<br><br><br></pre>
    </blockquote>
    <pre wrap=""><!----><br></pre>
    </blockquote>
    <br>
    </body>
    </html>

--------------030003060605040209090208--




From owner-te-wg@ops.ietf.org  Wed Feb  5 15:23: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 PAA09386
	for <tewg-archive@lists.ietf.org>; Wed, 5 Feb 2003 15:23:03 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gW2q-0009Xk-00
	for te-wg-data@psg.com; Wed, 05 Feb 2003 12:21:20 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gW2n-0009XU-00
	for te-wg@ops.ietf.org; Wed, 05 Feb 2003 12:21:17 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h15JTYKx001224
	for <te-wg@ops.ietf.org>; Wed, 5 Feb 2003 15:21:13 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01FBDDF7; Wed, 5 Feb 2003 15:21:13 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Wed, 5 Feb 2003 15:21:14 -0500
Message-ID: <A66DDF82468CDA44BEC0D63F91E4000B033A2ADE@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Thread-Index: AcLK+4zDX2O8QSz/RVWo9d2QXL20WQCV5x3w
From: "Cole, Robert G (Bob), ALABS" <rgcole@att.com>
To: "Spyros Kontogiorgis" <spyroskon@hotmail.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA09386


I give the draft a 'thumbs up' as well.  (IMO) There is value
documenting in one place the issues wrt TE-measurements
and recommendations for future areas of work.

Thanks,
Bob Cole

> -----Original Message-----
> From:	Spyros Kontogiorgis [SMTP:spyroskon@hotmail.com]
> Sent:	Sunday, February 02, 2003 8:25 PM
> To:	te-wg@ops.ietf.org
> Subject:	Re: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
> 
> 
> Thumbs up from me for the doc. Glad to see some of
> my suggestions incorporated.
> 
> Spyros Kontogiorgis.
> 
> _________________________________________________________________
> The new MSN 8: advanced junk mail protection and 2 months FREE*  
> http://join.msn.com/?page=features/junkmail
> 
> 



From owner-te-wg@ops.ietf.org  Wed Feb  5 16:35:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11831
	for <tewg-archive@lists.ietf.org>; Wed, 5 Feb 2003 16:35:26 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gXDc-000ERR-00
	for te-wg-data@psg.com; Wed, 05 Feb 2003 13:36:32 -0800
Received: from mail.ee.gatech.edu ([130.207.225.105])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gXDY-000EPp-00
	for te-wg@ops.ietf.org; Wed, 05 Feb 2003 13:36:28 -0800
Received: from dkny.ece.gatech.edu (dkny.ece.gatech.edu [199.77.155.27])
	by mail.ee.gatech.edu (8.12.3/8.12.3) with ESMTP id h15LaPUF009664
	for <te-wg@ops.ietf.org>; Wed, 5 Feb 2003 16:36:25 -0500 (EST)
Received: from localhost (tricha@localhost)
	by dkny.ece.gatech.edu (8.12.0.Beta19/8.12.0.Beta19/Submit) with ESMTP id h15LaP5s026862
	for <te-wg@ops.ietf.org>; Wed, 5 Feb 2003 16:36:25 -0500 (EST)
Date: Wed, 5 Feb 2003 16:36:25 -0500 (EST)
From: Tricha Anjali <tricha@ece.gatech.edu>
To: te-wg@ops.ietf.org
Subject: RE: draft-ietf-tewg-measure-04.txt
In-Reply-To: <A66DDF82468CDA44BEC0D63F91E4000B033A2ADE@OCCLUST04EVS1.ugd.att.com>
Message-ID: <Pine.GSO.4.50.0302051632340.26133-100000@dkny.ece.gatech.edu>
References: <A66DDF82468CDA44BEC0D63F91E4000B033A2ADE@OCCLUST04EVS1.ugd.att.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
X-Spam-Status: No, hits=-1.1 required=5.0
	tests=IN_REP_TO,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT_PINE
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


I have read the draft and like it. It addresses the issues
related to network measurement within a domain which are
essential for traffic engineering.

Regards,

Tricha

-------------------------------
Tricha Anjali
Broadband & Wireless Networking Lab
School of Electrical and Computer Engineering
Georgia Institute of Technology
http://users.ece.gatech.edu/~tricha/





From owner-te-wg@ops.ietf.org  Thu Feb  6 12:50:14 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27743
	for <tewg-archive@lists.ietf.org>; Thu, 6 Feb 2003 12:50:13 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gq4k-0007GA-00
	for te-wg-data@psg.com; Thu, 06 Feb 2003 09:44:38 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gq4h-0007Fq-00
	for te-wg@ops.ietf.org; Thu, 06 Feb 2003 09:44:35 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h16HiWYA002014;
	Thu, 6 Feb 2003 17:44:32 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id RAA25249;
	Thu, 6 Feb 2003 17:44:31 GMT
Message-Id: <5.1.0.14.0.20030205111950.027dfe10@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 05 Feb 2003 12:58:20 -0800
To: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
From: raymond zhang <zhangr@info.net>
Subject: Re: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Cc: <te-wg@ops.ietf.org>
In-Reply-To: <28F05913385EAC43AF019413F674A01702E5E019@OCCLUST04EVS1.ugd
 .att.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=DATE_IN_PAST_12_24,IN_REP_TO,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Wai Sum,

Indeed, this is  a well structured document.  I found it is rather 
beneficial in setting out such a framework as one documented here as a 
system for it provides a set of common foundations (which now differs quite 
a bit from SP to SP) as we further our discussions in this area...

I just have a few minor comments listed as below after reviewing the document:
1. Tho defined in the IPPM framework, it would be probably make it a bit 
more clearer if active/passive measurement can be re-iterated at the 
beginning of section 4.
2. Sec 7, the end of the 2nd paragraph - is it probably too late to launch 
active measurement in an attempt to seek ways of redistributing the traffic 
in resolving local congestions after the fact (congestions) ?  This is 
certainly not our current practice today.
3. Sec 9.1, LSP holding time...  Perhaps it is worth mentioning here a "up" 
duration property to be introduced to each pair of label bindings in the 
LFIB from RSVP-TE, LDP or MP-BGP or BGP distributed labels.  This way the 
value of this property can be gathered via passive means such that the 
derivation of LSP average holding time does not need to be finely 
correlated with network events.
4. Sec. 9.2, path establishment entities for MPLS TE maybe 
routing/signaling plane convergence dependent properties which may further 
be eschewed by FRR and preemptions.  Path establishments shouldn't be 
frequent events in the network and I wonder if it is beneficial to have 
these entities collected and if it is even realistic to attain its 
statistical properties such as blocking due to insufficient event 
population... Not sure of this point.


Regards,
Raymond






At 03:38 PM 1/31/2003 -0500, Lai, Wai S (Waisum), ALABS wrote:
>Following on Jim's request, please review the TE Measurement draft,
>which is currently under last call (terminates on Feb. 7).
>
>About 20-30 people who attended the IETF-55 TEWG meeting indicated
>that they planned to review the document when it went to last call.
>
>Please indicate to the TEWG list that you have reviewed the document,
>even if you have no comments of suggestions.
>
>Thanks, Wai Sum
>
>-----Original Message-----
>From: Jim Boyle [mailto:jboyle@pdnets.com]
>Sent: Saturday, January 25, 2003 11:53 AM
>To: te-wg@ops.ietf.org
>Cc: Wijnen, Bert (Bert)
>Subject: RE: Weak turnout : FINAL COMMENT (? :)
>
>
>
>I think we've discussed an important topic.  We have over a lots of
>people
>on this list, we should have a good participation on subjects such as
>revision of drafts that have past last call and are with the IESG, or
>drafts that are in last call.  Even for drafts that are earlier in the
>development cycle, more perspective is a good thing.
>
>That said, reminder:  draft-ietf-tewg-measurement-04.txt is currently
>under last call until Feb 7th.
>
>thanks,
>
>Jim





From owner-te-wg@ops.ietf.org  Thu Feb  6 12:50:43 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27764
	for <tewg-archive@lists.ietf.org>; Thu, 6 Feb 2003 12:50:43 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18gq6h-0007NB-00
	for te-wg-data@psg.com; Thu, 06 Feb 2003 09:46:39 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18gq6d-0007My-00
	for te-wg@ops.ietf.org; Thu, 06 Feb 2003 09:46:35 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h16HiXYA002034;
	Thu, 6 Feb 2003 17:44:33 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id RAA25252;
	Thu, 6 Feb 2003 17:44:32 GMT
Message-Id: <5.1.0.14.0.20030205131039.027e28f8@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 05 Feb 2003 13:27:17 -0800
To: Yuichi Ikejiri <y.ikejiri@ntt.com>
From: raymond zhang <zhangr@info.net>
Subject: Re: new version: draft-zhang-mpls-interas-te-req-01.txt
Cc: "Jean Philippe Vasseur" <jvasseur@cisco.com>, te-wg@ops.ietf.org
In-Reply-To: <20030205203043.3F46.Y.IKEJIRI@ntt.com>
References: <5.1.0.14.0.20030203094555.027ed5b0@delta.info.net>
 <20030203061704.9E16.Y.IKEJIRI@ntt.com>
 <5.1.0.14.0.20030203094555.027ed5b0@delta.info.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-1.1 required=5.0
	tests=DATE_IN_PAST_12_24,IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,
	      SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yuichi,

At 10:48 PM 2/5/2003 +0900, Yuichi Ikejiri wrote:
>Hi Raymond,
>
> > >  - the functionality or case of interconencting each MPLS TE LSP at ASBR.
> > >       - there could be some cases that RSP or GRP's internal
> > >         MPLS TEs are connected to Inter-AS TE at ASBR.
> >
> > I am not sure of this point... it would be good if you could provide an
> > example or elaborate a bit more ?  Inter-AS TE tunnel as defined in this
> > draft is intended to be established end-to-end, not by segments stitched
> > together...  Section 5.8 defines the requirements of TE LSP aggregation
> > whereby an Inter-AS TE tunnel may be aggregated onto the intra-AS MPLS-TE
> > LSP so as to reduce the # of tunnel states...
>I assume the case below.
>
>CE1--RSP(PE)---ASBR----ASBR----GSP(PE)----CE2
>  <------Inter-AS-TE---------><----Internal-TE--->
>                                       ~~~~
>                   (interconnecting or mapping)
>
>You mention vrf to inter-as-TE mapping at ASBR in Section5.9 but
>I think that the mapping function would not be limmited to vrf cases
>as a general requirement, even if any specific function might not be
>needed as a result or be out of scope of this document.

Thanks for the clarification.  Section 5.9 presents a requirement for case 
2 of Scenario II in sec. 4.2.  The Inter-AS TE tunnels are meant to be 
extended virtual local loops over RSP's network which maybe terminated at 
the ASBR or any PE in the GSP's network (I will update case 2 diagram to 
reflect your diagram above).  In other words, the inter-AS TE and 
Internal-TE are essentially the same RSVP-TE tunnel.

Your are right on the point of not being limited to vrf cases, it could be 
in global space as well.  Thanks for pointing this out.

>Regards,
>Yuichi
>
> >
> >
> > >Regards,
> > >Yuichi Ikejiri
> > >NTT Communications Corporation
> > >
> > >On Fri, 20 Dec 2002 13:39:28 -0500
> > >Jean Philippe Vasseur <jvasseur@cisco.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > First of all, thanks for the various comments we received and that 
> are now
> > > > integrated in the version -01 of the inter-AS TE requirements draft 
> (just
> > > > posted:
> > > >
> > > 
> http://www.ietf.org/internet-drafts/draft-zhang-mpls-interas-te-req-01.txt).
> > > > Some other Service Providers will join the draft in the next 
> release. Your
> > > > comments on the list are very welcome.
> > > >
> > > > Thanks.
> > > >
> > > > JP.
> > > >
> > > >
> >





From owner-te-wg@ops.ietf.org  Fri Feb  7 10:30:44 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13454
	for <tewg-archive@lists.ietf.org>; Fri, 7 Feb 2003 10:30:43 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18hAQb-000Cth-00
	for te-wg-data@psg.com; Fri, 07 Feb 2003 07:28:33 -0800
Received: from wire.cs.nthu.edu.tw ([140.114.79.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18hAQW-000CtR-00
	for te-wg@ops.ietf.org; Fri, 07 Feb 2003 07:28:29 -0800
Received: (from apache@localhost)
	by wire.cs.nthu.edu.tw (8.11.6/8.11.6) id h17FUUQ14087;
	Fri, 7 Feb 2003 23:30:30 +0800
Date: Fri, 7 Feb 2003 23:30:30 +0800
Message-Id: <200302071530.h17FUUQ14087@wire.cs.nthu.edu.tw>
From: "Chia-Feng Kang" <cfk@wire.cs.nthu.edu.tw>
To: te-wg@ops.ietf.org
Subject: Re: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
X-Mailer: NeoMail 1.25
X-IPAddress: 140.114.79.53
MIME-Version: 1.0
Content-Type: text/plain; charset=big5
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Dear all,
  I am a new member in traffic engineering field.
  I have reviewed the draft. Although I am still unfamiliar with some 
specific aspects, I think that the draft is on-target for TEM milestone.

Best Regards,

Chia-Feng Kang
WIRE Lab/CS/NTHU/TW
cfk@wire.cs.nthu.edu.tw



From owner-te-wg@ops.ietf.org  Sat Feb  8 01:01:25 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02800
	for <tewg-archive@lists.ietf.org>; Sat, 8 Feb 2003 01:01:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18hO14-0000i3-00
	for te-wg-data@psg.com; Fri, 07 Feb 2003 21:59:06 -0800
Received: from h-135-207-26-243.research.att.com ([135.207.26.243] helo=NJFPSRVEXG2KCL.research.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18hO12-0000hq-00
	for te-wg@ops.ietf.org; Fri, 07 Feb 2003 21:59:04 -0800
Subject: RE: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Sat, 8 Feb 2003 00:59:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
Message-ID: <387B5A9BF31B5D43A2B18DD9F326B8E11ED971@NJFPSRVEXG2KCL.research.att.com>
Thread-Topic: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Thread-Index: AcLElk0Rmd+kcarWToeJTh4Agt+N3AE0fkmAAXOXiUA=
From: <duffield@research.att.com>
To: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=1.3 required=5.0
	tests=NO_REAL_NAME,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id BAA02800

I have reviewed this document and contributed material. I'm happy to see
it go forward.

Nick

> -----Original Message-----
> From: Lai, Wai S (Waisum), ALABS [mailto:wlai@att.com]
> Sent: Friday, January 31, 2003 3:39 PM
> To: Jim Boyle; te-wg@ops.ietf.org
> Cc: Wijnen, Bert (Bert)
> Subject: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
> 
> Following on Jim's request, please review the TE Measurement draft,
> which is currently under last call (terminates on Feb. 7).
> 
> About 20-30 people who attended the IETF-55 TEWG meeting indicated
> that they planned to review the document when it went to last call.
> 
> Please indicate to the TEWG list that you have reviewed the document,
> even if you have no comments of suggestions.
> 
> Thanks, Wai Sum
> 
> -----Original Message-----
> From: Jim Boyle [mailto:jboyle@pdnets.com]
> Sent: Saturday, January 25, 2003 11:53 AM
> To: te-wg@ops.ietf.org
> Cc: Wijnen, Bert (Bert)
> Subject: RE: Weak turnout : FINAL COMMENT (? :)
> 
> 
> 
> I think we've discussed an important topic.  We have over a lots of
> people
> on this list, we should have a good participation on subjects such as
> revision of drafts that have past last call and are with the IESG, or
> drafts that are in last call.  Even for drafts that are earlier in the
> development cycle, more perspective is a good thing.
> 
> That said, reminder:  draft-ietf-tewg-measurement-04.txt is currently
> under last call until Feb 7th.
> 
> thanks,
> 
> Jim
> 
> 




From owner-te-wg@ops.ietf.org  Sat Feb  8 03:49:11 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA15932
	for <tewg-archive@lists.ietf.org>; Sat, 8 Feb 2003 03:49:10 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18hQgB-0004iI-00
	for te-wg-data@psg.com; Sat, 08 Feb 2003 00:49:43 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18hQg7-0004i6-00
	for te-wg@ops.ietf.org; Sat, 08 Feb 2003 00:49:39 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h188m2v2012379
	for <te-wg@ops.ietf.org>; Sat, 8 Feb 2003 09:48:03 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Sat, 8 Feb 2003 09:49:37 +0100
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: DSTE Reqts draft
Date: Sat, 8 Feb 2003 08:49:36 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F901EDE2E2@xbe-lon-303.cisco.com>
Thread-Topic: DSTE Reqts draft
Thread-Index: AcLD8oHcRv3yePk3R7OoukUQTKqCUwKz8Exg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 08 Feb 2003 08:49:37.0247 (UTC) FILETIME=[0294D6F0:01C2CF4F]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id DAA15932

>> > seems to have resolved with you.  My assumption is that 
>> > Francois and Wai Sum will now make the proposed changes, and 
>> > re-submit the DSTE requirements draft to the IESG, correct?
>> > 
>> That is what I heard.
>> 

Yes, we'll issue the updated rev of diff-te-reqts asap.

Francois



From owner-te-wg@ops.ietf.org  Mon Feb 10 07:41:30 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA07091
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 07:41:30 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iDEf-000NSe-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 04:40:33 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18iDEb-000NSI-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 04:40:30 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e480880; Mon, 10 Feb 2003 12:38:37 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm4b3e3b1496; Fri, 31 Jan 2003 16:53:25 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18edan-000Fvb-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 08:00:37 -0800
Received: from f20.law10.hotmail.com ([64.4.15.20] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18edal-000FvP-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 08:00:35 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 31 Jan 2003 07:59:48 -0800
Received: from 206.47.0.172 by lw10fd.law10.hotmail.msn.com with HTTP;
	Fri, 31 Jan 2003 15:59:47 GMT
X-Originating-IP: [206.47.0.172]
From: "Ting Chung" <twchungca@hotmail.com>
To: te-wg@ops.ietf.org
Subject: draft-ietf-tewg-diff-te-reqts-06.txt
Date: Fri, 31 Jan 2003 10:59:47 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F20g800QT7MkpyWGH5j0000a30e@hotmail.com>
X-OriginalArrivalTime: 31 Jan 2003 15:59:48.0072 (UTC) FILETIME=[C7BA2E80:01C2C941]
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


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

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

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




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





From owner-te-wg@ops.ietf.org  Mon Feb 10 07:42: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 HAA07113
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 07:41:59 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iDCu-000NQ2-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 04:38:44 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18iDCr-000NPk-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 04:38:41 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e480880; Mon, 10 Feb 2003 12:38:37 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm4b3e3b1496; Fri, 31 Jan 2003 16:53:25 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18edan-000Fvb-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 08:00:37 -0800
Received: from f20.law10.hotmail.com ([64.4.15.20] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18edal-000FvP-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 08:00:35 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 31 Jan 2003 07:59:48 -0800
Received: from 206.47.0.172 by lw10fd.law10.hotmail.msn.com with HTTP;
	Fri, 31 Jan 2003 15:59:47 GMT
X-Originating-IP: [206.47.0.172]
From: "Ting Chung" <twchungca@hotmail.com>
To: te-wg@ops.ietf.org
Subject: draft-ietf-tewg-diff-te-reqts-06.txt
Date: Fri, 31 Jan 2003 10:59:47 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F20g800QT7MkpyWGH5j0000a30e@hotmail.com>
X-OriginalArrivalTime: 31 Jan 2003 15:59:48.0072 (UTC) FILETIME=[C7BA2E80:01C2C941]
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


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

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

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




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





From owner-te-wg@ops.ietf.org  Mon Feb 10 08:35:01 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08390
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 08:35:01 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iE6S-000Odv-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 05:36:08 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18iE6P-000Odi-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 05:36:05 -0800
Received: from attrh0i.attrh.att.com ([135.37.94.54])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h1ADSJI5028705
	for <te-wg@ops.ietf.org>; Mon, 10 Feb 2003 08:36:03 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh0i.attrh.att.com (6.5.019)
        id 3E39EBFA0087F3E8 for te-wg@ops.ietf.org; Mon, 10 Feb 2003 08:36:03 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_001_01C2D109.21B85364"
Subject: FW: [Re: question on draft-ietf-tewg-measure-04.txt]
Date: Mon, 10 Feb 2003 08:34:27 -0500
Message-ID: <28F05913385EAC43AF019413F674A017044A34F5@OCCLUST04EVS1.ugd.att.com>
X-MS-Has-Attach: yes
Thread-Topic: [Re: question on draft-ietf-tewg-measure-04.txt]
Thread-Index: AcLP+4C/NUzHATTSS0KDSacPap2pcABDcQGg
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=0.7 required=5.0
	tests=OUTLOOK_FW_MSG,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2D109.21B85364
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Forwarding on behalf of Al Morton.
Thanks, Wai Sum

-----Original Message-----
From: Al Morton [mailto:acm@palm.net]
Sent: Sunday, February 09, 2003 12:24 AM
To: Lai, Wai S (Waisum), ALABS
Cc: Ash, Gerald R (Jerry), ALABS
Subject: Fwd: [Re: question on draft-ietf-tewg-measure-04.txt]


Wai Sum,
I sent this to the tewg list last nite, but it does
not appear in the archive.  If you did not receive
the message, please forward it to the tewg list.

Al


____________________________________________________________________
This message was sent from my Palm wireless email account.

------_=_NextPart_001_01C2D109.21B85364
Content-Type: message/rfc822

X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Mailer: USANET web-mailer (CM.0402.4.13A)
content-class: urn:content-classes:message
Subject: Re: question on draft-ietf-tewg-measure-04.txt
Date: Fri, 7 Feb 2003 22:32:21 -0500
Message-ID: <112HBHDGV5392S20.1044675141@uwdvg020.cms.usa.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Al Morton" <acm@palm.net>
To: <te-wg@ops.ietf.org>
Content-Transfer-Encoding: quoted-printable

tewg,

I can live with this draft as-is, but assuming there
are revisions in response to the last call,
here are a few questions and suggestions:
(I have read only part of the list archive, and the draft)

In general, it reduces clarity to introduce new terminology
(e.g., Sec 9: Meas. Type =3D Meas. Entity + Meas. Basis).
It would have been better to take an existing set of=20
terms and definitions (IPPM's for example) and add new terms
only as needed.

Section 4.1 Route, Path
This distinction overlaps the IPPM definition of path,
and path is used to mean route in several places.
(Sec 8.4 "paths for routing traffic, so called route-pinning".
Later on in Section 12, "route tracing" for MPLS is discussed.)

Section 4.2
The "Throughput of a network" definition lacks a basis
(or more clearly, the measurement points are omitted).
Is this a single entrance node to all possible network exits,
or all inputs, or all outputs?

Section 5.2,  second bullet:
How is continuity monitored?

Section 7,  Read-Out Periods
The hierarchy of measurements, raw data, measurement intervals,
read-out periods, and summarization/reporting should be more clear.
A measurement interval appears to contain multiple measurements
(this is unusual usage).

Section 9.1
"goodput" also excludes retransmitted packets in common usage.
Packet loss:  in most active measurements, the cause of loss
is not distinguished.
Delay Variation:  Reference 11 has been revised and approved Dec 2002,
and revisions affect the text in this section (Appendix II has changed
substantially, the two-point method is now normative in clause 6).

hope this helps,
Al


____________________________________________________________________
This message was sent from my Palm wireless email account.

------_=_NextPart_001_01C2D109.21B85364--



From owner-te-wg@ops.ietf.org  Mon Feb 10 08:59:37 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09169
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 08:59:37 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iEUB-000P9B-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 06:00:39 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18iEU8-000P8x-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 06:00:37 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm163e47b607; Mon, 10 Feb 2003 14:00:32 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm63e3b3f70; Fri, 31 Jan 2003 21:23:10 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18ehx3-0003ZR-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 12:39:53 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18ehx1-0003ZF-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 12:39:51 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0VJu0Kk026182
	for <te-wg@ops.ietf.org>; Fri, 31 Jan 2003 15:39:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01CFC878; Fri, 31 Jan 2003 15:38:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Fri, 31 Jan 2003 15:38:41 -0500
Message-ID: <28F05913385EAC43AF019413F674A01702E5E019@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Weak turnout : FINAL COMMENT (? :)
Thread-Index: AcLElk0Rmd+kcarWToeJTh4Agt+N3AE0fkmA
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id IAA09169

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

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

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

Thanks, Wai Sum

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



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

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

thanks,

Jim






From owner-te-wg@ops.ietf.org  Mon Feb 10 09:49:11 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10893
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 09:49:11 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iFGh-0000gd-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 06:50:47 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18iFGe-0000gE-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 06:50:44 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm183e48043f; Mon, 10 Feb 2003 14:50:40 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm4b3e3b1496; Fri, 31 Jan 2003 16:53:25 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18edan-000Fvb-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 08:00:37 -0800
Received: from f20.law10.hotmail.com ([64.4.15.20] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18edal-000FvP-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 08:00:35 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Fri, 31 Jan 2003 07:59:48 -0800
Received: from 206.47.0.172 by lw10fd.law10.hotmail.msn.com with HTTP;
	Fri, 31 Jan 2003 15:59:47 GMT
X-Originating-IP: [206.47.0.172]
From: "Ting Chung" <twchungca@hotmail.com>
To: te-wg@ops.ietf.org
Subject: draft-ietf-tewg-diff-te-reqts-06.txt
Date: Fri, 31 Jan 2003 10:59:47 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F20g800QT7MkpyWGH5j0000a30e@hotmail.com>
X-OriginalArrivalTime: 31 Jan 2003 15:59:48.0072 (UTC) FILETIME=[C7BA2E80:01C2C941]
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


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

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

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




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





From owner-te-wg@ops.ietf.org  Mon Feb 10 11:14: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 LAA13957
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 11:14:08 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iGYx-0002tH-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 08:13:43 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18iGYu-0002t5-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 08:13:40 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm303e481226; Mon, 10 Feb 2003 16:13:37 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm63e3b3f70; Fri, 31 Jan 2003 21:23:10 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18ehx3-0003ZR-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 12:39:53 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18ehx1-0003ZF-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 12:39:51 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0VJu0Kk026182
	for <te-wg@ops.ietf.org>; Fri, 31 Jan 2003 15:39:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01CFC878; Fri, 31 Jan 2003 15:38:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Fri, 31 Jan 2003 15:38:41 -0500
Message-ID: <28F05913385EAC43AF019413F674A01702E5E019@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Weak turnout : FINAL COMMENT (? :)
Thread-Index: AcLElk0Rmd+kcarWToeJTh4Agt+N3AE0fkmA
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA13957

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

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

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

Thanks, Wai Sum

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



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

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

thanks,

Jim






From owner-te-wg@ops.ietf.org  Mon Feb 10 16:25:40 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26563
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 16:25:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iLPt-000FMQ-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 13:24:41 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18iLPo-000FLw-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 13:24:37 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm43e482512; Mon, 10 Feb 2003 21:24:34 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm63e3b3f70; Fri, 31 Jan 2003 21:23:10 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18ehx3-0003ZR-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 12:39:53 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18ehx1-0003ZF-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 12:39:51 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0VJu0Kk026182
	for <te-wg@ops.ietf.org>; Fri, 31 Jan 2003 15:39:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01CFC878; Fri, 31 Jan 2003 15:38:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Fri, 31 Jan 2003 15:38:41 -0500
Message-ID: <28F05913385EAC43AF019413F674A01702E5E019@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Weak turnout : FINAL COMMENT (? :)
Thread-Index: AcLElk0Rmd+kcarWToeJTh4Agt+N3AE0fkmA
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA26563

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

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

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

Thanks, Wai Sum

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



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

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

thanks,

Jim






From owner-te-wg@ops.ietf.org  Mon Feb 10 21:49:29 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06106
	for <tewg-archive@lists.ietf.org>; Mon, 10 Feb 2003 21:49:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iQRE-0000j3-00
	for te-wg-data@psg.com; Mon, 10 Feb 2003 18:46:24 -0800
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18iQRA-0000io-00
	for te-wg@ops.ietf.org; Mon, 10 Feb 2003 18:46:20 -0800
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.5/8.12.5) with ESMTP id h1B2k1Ek015217;
	Mon, 10 Feb 2003 21:46:02 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.5/8.12.5/Submit) with ESMTP id h1B2ju5e015161;
	Mon, 10 Feb 2003 21:45:59 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Mon, 10 Feb 2003 21:45:56 -0500 (EST)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: te-wg@ops.ietf.org
cc: bwijnen@lucent.com, <sob@harvard.edu>
Subject: WG Last Call Result:  draft-ietf-tewg-measure-04.txt
In-Reply-To: <Pine.LNX.4.44.0301182233570.13232-100000@fido.nc.rr.com>
Message-ID: <Pine.LNX.4.44.0302102142520.2830-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-1.4 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SEARCH_ENGINE_PROMO,SPAM_PHRASE_01_02,USER_AGENT_PINE,
	      X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Looks like most people who replied think this draft is on-target and ready 
to go.  There were some comments, so I believe we will wait for the 
authors to revise the draft, then it will be sent up to IESG for 
consideration as an informational RFC.

thanks,

Jim

On Sat, 18 Jan 2003, Jim Boyle wrote:

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




From owner-te-wg@ops.ietf.org  Tue Feb 11 06:49:26 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28953
	for <tewg-archive@lists.ietf.org>; Tue, 11 Feb 2003 06:49:26 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18iYud-000Lmj-00
	for te-wg-data@psg.com; Tue, 11 Feb 2003 03:49:19 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18iYua-000LmW-00
	for te-wg@ops.ietf.org; Tue, 11 Feb 2003 03:49:16 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28550;
	Tue, 11 Feb 2003 06:45:31 -0500 (EST)
Message-Id: <200302111145.GAA28550@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org, ospf@discuss.microsoft.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-srisuresh-ospf-te-05.txt
Date: Tue, 11 Feb 2003 06:45:31 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: OSPF-xTE: An experimental extension to OSPF for 
                          Traffic Engineering
	Author(s)	: P. Srisuresh, P. Joseph
	Filename	: draft-srisuresh-ospf-te-05.txt
	Pages		: 49
	Date		: 2003-2-10
	
This document defines OSPF-xTE, an experimental traffic engineering
(TE) extension to the link-state routing protocol OSPF. New TE LSAs
are defined to disseminate TE metrics within an autonomous 
System (AS) - intra-area as well as inter-area. An Autonomous 
System may consist of TE and non-TE nodes. Non-TE nodes are 
uneffected by the distribution of TE LSAs. A stand-alone TE Link
State Database (TE-LSDB), separate from the native OSPF LSDB, is
generated for the computation of TE circuit paths. OSPF-xTE is 
also extendible to non-packet networks such as SONET/TDM and 
optical networks. A transition path is provided for those using
[OPQLSA-TE] and wish to adapt OSPF-xTE.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-srisuresh-ospf-te-05.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-srisuresh-ospf-te-05.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Tue Feb 11 11:07: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 LAA09391
	for <tewg-archive@lists.ietf.org>; Tue, 11 Feb 2003 11:07:48 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18icsF-0005nC-00
	for te-wg-data@psg.com; Tue, 11 Feb 2003 08:03:07 -0800
Received: from host1.btamail.net.cn ([202.106.196.71] helo=btmail.net.cn)
	by psg.com with smtp (Exim 3.36 #1)
	id 18ics9-0005mk-00
	for te-wg@ops.ietf.org; Tue, 11 Feb 2003 08:03:02 -0800
Received: from btmail.net.cn([202.106.196.71]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm23e491fce; Tue, 11 Feb 2003 16:02:56 -0000
Received: from psg.com([147.28.0.62]) by btamail.net.cn(JetMail 2.5.3.0)
	with SMTP id jm63e3b3f70; Fri, 31 Jan 2003 21:23:10 -0000
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18ehx3-0003ZR-00
	for te-wg-data@psg.com; Fri, 31 Jan 2003 12:39:53 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18ehx1-0003ZF-00
	for te-wg@ops.ietf.org; Fri, 31 Jan 2003 12:39:51 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h0VJu0Kk026182
	for <te-wg@ops.ietf.org>; Fri, 31 Jan 2003 15:39:06 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E01CFC878; Fri, 31 Jan 2003 15:38:41 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: draft-ietf-tewg-measure-04.txt: FINAL COMMENT
Date: Fri, 31 Jan 2003 15:38:41 -0500
Message-ID: <28F05913385EAC43AF019413F674A01702E5E019@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Weak turnout : FINAL COMMENT (? :)
Thread-Index: AcLElk0Rmd+kcarWToeJTh4Agt+N3AE0fkmA
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
X-Auto-Forward: nixianle@btamail.net.cn
 nxl@bupt-bcnl.com
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA09391

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

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

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

Thanks, Wai Sum

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



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

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

thanks,

Jim






From owner-te-wg@ops.ietf.org  Tue Feb 11 11:32: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 LAA10474
	for <tewg-archive@lists.ietf.org>; Tue, 11 Feb 2003 11:32:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18idMi-00071b-00
	for te-wg-data@psg.com; Tue, 11 Feb 2003 08:34:36 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18idMe-00071E-00
	for te-wg@ops.ietf.org; Tue, 11 Feb 2003 08:34:32 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1BGWnSZ003063;
	Tue, 11 Feb 2003 17:32:55 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 11 Feb 2003 17:34:29 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: "Security Considerations" for draft-ietf-tewg-diff-te-reqts-07.txt
Date: Tue, 11 Feb 2003 16:34:29 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E79D@xbe-lon-303.cisco.com>
Thread-Topic: "Security Considerations" for draft-ietf-tewg-diff-te-reqts-07.txt
Thread-Index: AcLBi2GfFa7ueisQSjSRzaXza0Qu/wQRRi2Q
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>,
        "David Meyer (E-mail)" <dmm@sprint.net>
X-OriginalArrivalTime: 11 Feb 2003 16:34:29.0818 (UTC) FILETIME=[7316A9A0:01C2D1EB]
X-Spam-Status: No, hits=1.0 required=5.0
	tests=MIME_EXCESSIVE_QP,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id LAA10474

Hello,

We are doing the final edits in order to issue reqts-07. But before
issueing it, I would like to close-off the final wording for the updated
"Security Considerations" section.

Here is what I anm proposing to incorporate:

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

This is attempting to address both the concerns from Bert and those from
David on DOS attacks (see excerpts below).

Please let us know promptly if you still see any issue with this
wording.
Thanks

Francois


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

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

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

>> If nothing else, then at least list the fact that
>> any protocols that get developed need to pay specific attention to
>> ensure that DoS attackes are prevented as much as possible.



From owner-te-wg@ops.ietf.org  Tue Feb 11 14:57: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 OAA16963
	for <tewg-archive@lists.ietf.org>; Tue, 11 Feb 2003 14:57:06 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18igWX-000DSo-00
	for te-wg-data@psg.com; Tue, 11 Feb 2003 11:56:57 -0800
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18igWU-000DSX-00
	for te-wg@ops.ietf.org; Tue, 11 Feb 2003 11:56:54 -0800
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA03360
	for <te-wg@ops.ietf.org>; Tue, 11 Feb 2003 14:56:50 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA20160
	for <te-wg@ops.ietf.org>; Tue, 11 Feb 2003 14:56:51 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <D3QMJD8R>; Tue, 11 Feb 2003 14:56:50 -0500
Message-ID: <313680C9A886D511A06000204840E1CF8F535A@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: "'te-wg@ops.ietf.org'" <te-wg@ops.ietf.org>
Subject: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Date: Tue, 11 Feb 2003 14:56:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=0.7 required=5.0
	tests=EXCHANGE_SERVER,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


Hi! Your comments on the following draft will be appreciated:
 <http://www.ietf.org/internet-drafts/draft-nadeau-mpls-dste-mib-00.txt>

Known TBDs:
	1. Update to reflect the latest DSTE-REQ and DSTE-PROTO
	2. Update to handle MAR BC Model
	3. reorg. the reference section.

Thanks,
sanjay



From owner-te-wg@ops.ietf.org  Thu Feb 13 07:00:32 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA10276
	for <tewg-archive@lists.ietf.org>; Thu, 13 Feb 2003 07:00:31 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18jHvC-000FYO-00
	for te-wg-data@psg.com; Thu, 13 Feb 2003 03:52:54 -0800
Received: from usjk1004.kddi.com ([211.4.169.26])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18jHv7-000FY7-00
	for te-wg@ops.ietf.org; Thu, 13 Feb 2003 03:52:49 -0800
Received: from usjk1006.kddi.com (usjk1006 [10.96.2.3]) by usjk1004.kddi.com (3.7W-020809151234) with ESMTP id UAA01911 for <te-wg@ops.ietf.org>; Thu, 13 Feb 2003 20:52:46 +0900 (JST)
Received: from usjk1010.kddi.com (localhost [127.0.0.1]) by usjk1006.kddi.com (3.7W-021210104931) with ESMTP id UAA22807 for <te-wg@ops.ietf.org>; Thu, 13 Feb 2003 20:52:46 +0900 (JST)
Received: from [133.128.75.224] by usjk1010.kddi.com
          (InterMail vM.5.01.02.00 201-253-116-121-20001201) with ESMTP
          id <20030213115245.TSBJ1017.usjk1010.kddi.com@[133.128.75.224]>;
          Thu, 13 Feb 2003 20:52:45 +0900
Date: Thu, 13 Feb 2003 20:52:44 +0900
From: Kenji Kumaki <ke-kumaki@kddi.com>
To: te-wg@ops.ietf.org
Subject: Inter-AS TE requirements draft: draft-zhang-mpls-interas-te-req-01.txt
Cc: ke-kumaki@kddi.com
Message-Id: <20030213201923.6D19.KE-KUMAKI@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.05.08
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Traffic control between SP's is difficult under the present condition.
This draft arranges the requirement to be able to control traffic using
RSVP-TE between SP's.
Many SP's(INFONET, KDDI, QWEST, EQUANT, BELL CANADA,NTT-C, FT,....) hope
for this requirement.

I hope this draft is adopted as a WG doc.

Regards,
Kenji

-- 
Kenji Kumaki <ke-kumaki@kddi.com>




From owner-te-wg@ops.ietf.org  Fri Feb 14 18:14: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 SAA09013
	for <tewg-archive@lists.ietf.org>; Fri, 14 Feb 2003 18:14:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18jp0y-000Ge1-00
	for te-wg-data@psg.com; Fri, 14 Feb 2003 15:13:04 -0800
Received: from kcmso2.att.com ([192.128.134.71] helo=kcmso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18jp0w-000Gdp-00
	for te-wg@ops.ietf.org; Fri, 14 Feb 2003 15:13:02 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h1EMwQYm021462
	for <te-wg@ops.ietf.org>; Fri, 14 Feb 2003 17:13:01 -0600 (CST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E026CCC0B; Fri, 14 Feb 2003 18:13:00 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Date: Fri, 14 Feb 2003 18:13:00 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704CB8722@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Thread-Index: AcLSCYcf5RyPNDQMTqOuIlBQJKnT7QCc/K7Q
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03,SUPERLONG_LINE
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA09013

Sanjay,

> Hi! Your comments on the following draft will be appreciated:
> http://www.ietf.org/internet-drafts/draft-nadeau-mpls-dste-mib-00.txt
> 
> Known TBDs:
> 	1. Update to reflect the latest DSTE-REQ and DSTE-PROTO
> 	2. Update to handle MAR BC Model
> 	3. reorg. the reference section.

I'm glad to see that you will include updates to handle the MAR (Maximum Allocation with Reservation) Model.  I presume you will also include updates to handle the Maximum Allocation Model (MAM).  The only model discussed in the MIB at present is the Russian Doll Model.

Just to be sure we're in sync, the MAR model is discussed in http://ietf.org/internet-drafts/draft-ash-mpls-dste-bcmodel-max-alloc-resv-00.txt, and the MAM model is discussed in http://ietf.org/internet-drafts/draft-wlai-tewg-bcmodel-00.txt.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Mon Feb 17 09:25: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 JAA22836
	for <tewg-archive@lists.ietf.org>; Mon, 17 Feb 2003 09:25:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18km7I-0002iU-00
	for te-wg-data@psg.com; Mon, 17 Feb 2003 06:19:32 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18km7F-0002iI-00
	for te-wg@ops.ietf.org; Mon, 17 Feb 2003 06:19:29 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1HEHRjC004024;
	Mon, 17 Feb 2003 15:17:38 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Mon, 17 Feb 2003 15:18:47 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: RE: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Date: Mon, 17 Feb 2003 14:18:18 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E7BD@xbe-lon-303.cisco.com>
Thread-Topic: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Thread-Index: AcLSCYcf5RyPNDQMTqOuIlBQJKnT7QCc/K7QAIOF9TA=
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 17 Feb 2003 14:18:47.0740 (UTC) FILETIME=[7C82A7C0:01C2D68F]
X-Spam-Status: No, hits=0.3 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_03_05
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id JAA22836

Hello Sanjay, Jerry,

>> -----Original Message-----
>> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com] 
>> Sent: 15 February 2003 00:13
>> To: Choudhury, Sanjaya
>> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
>> Subject: RE: Request for comments: DSTE-MIB 
>> (draft-nadeau-mpls-dste-mib-00)
>> 
>> 
>> Sanjay,
>> 
>> > Hi! Your comments on the following draft will be appreciated:
>> > 
>> http://www.ietf.org/internet-drafts/draft->>
nadeau-mpls-dste-mib-00.txt
>> > 
>> > Known TBDs:
>> > 	1. Update to reflect the latest DSTE-REQ and DSTE-PROTO
>> > 	2. Update to handle MAR BC Model
>> > 	3. reorg. the reference section.
>> 
>> I'm glad to see that you will include updates to handle the 
>> MAR (Maximum Allocation with Reservation) Model.  I presume 
>> you will also include updates to handle the Maximum 
>> Allocation Model (MAM).  The only model discussed in the MIB 
>> at present is the Russian Doll Model.

I agree with Jerry that MAM should be covered in addition to RDM since
the WG agrees on their respective definition and has agreed to specify
these two BC models asap.

With respect to MAR, while I agree in principle that it will need to
have MIB support once it is specified, I would recommend that this piece
of work is progressed outside of the main DS-TE MIB work. This is
because while the WG agrees that we should investigate MAR further, I
think we are still some time away before we have converged on a final
MAR specification. So we should make sure we don't end up holding the
core DS-TE MIB because of discussion on a longer term model.

Does that make sense?

Cheers

Francois








From owner-te-wg@ops.ietf.org  Mon Feb 17 12:08:49 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26228
	for <tewg-archive@lists.ietf.org>; Mon, 17 Feb 2003 12:08:48 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18kol5-0006Gp-00
	for te-wg-data@psg.com; Mon, 17 Feb 2003 09:08:47 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18kol2-0006Gc-00
	for te-wg@ops.ietf.org; Mon, 17 Feb 2003 09:08:44 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1HH6p43007980;
	Mon, 17 Feb 2003 18:07:06 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Mon, 17 Feb 2003 18:08:40 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2D6A7.371C9328"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: Security Considerations for <draft-ietf-tewg-diff-te-proto-03.txt>
Date: Mon, 17 Feb 2003 17:08:39 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E7C2@xbe-lon-303.cisco.com>
Thread-Topic: Security Considerations for <draft-ietf-tewg-diff-te-proto-03.txt>
Thread-Index: AcLWpzbsMDxpLmDmRAix6Jo0iiKCHg==
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Cc: <dmm@sprint.net>
X-OriginalArrivalTime: 17 Feb 2003 17:08:40.0126 (UTC) FILETIME=[37A555E0:01C2D6A7]
X-Spam-Status: No, hits=1.1 required=5.0
	tests=HTML_50_70,SPAM_PHRASE_00_01
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C2D6A7.371C9328
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,
=20
Here is an updated "Security Considerations" section proposed for the
next rev of diff-te-proto. Please let us know if you have
issues/concerns/suggestions on this:
=20
"
This document does not introduce additional security threats beyond
those inherent to Diff-Serv and MPLS Traffic Engineering and the same
security mechanisms proposed for these technologies are applicable and
may be used. For example, the approach for defense against theft- and
denial-of-service attacks discussed in [DIFF-ARCH], which consists of
the combination of traffic conditioning at DS boundary nodes along with
security and integrity of the network infrastructure within a Diff-Serv
domain, may be followed when DS-TE is in use. Also, as stated in
[TE-REQ], it is specifically important that manipulation of
administratively configurable parameters (such as those related to DS-TE
LSPs) be executed in a secure manner by authorized entities.
"
=20
Thanks
=20
Francois

------_=_NextPart_001_01C2D6A7.371C9328
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D085520317-17022003>Hello,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><SPAN=20
class=3D085520317-17022003></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><SPAN class=3D085520317-17022003>Here =
is&nbsp;an=20
updated "Security Considerations" section proposed for the next rev of=20
diff-te-proto. Please let us know if you have =
issues/concerns/suggestions on=20
this:</SPAN></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><SPAN class=3D085520317-17022003><FONT face=3DArial=20
size=3D2>"</FONT></SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA">This=20
document does not introduce additional security threats beyond those =
inherent to=20
Diff-Serv and MPLS Traffic Engineering and the same security mechanisms =
proposed=20
for these technologies are applicable and may be used. For example, the =
approach=20
for defense against theft- and denial-of-service attacks discussed in=20
[DIFF-ARCH], which consists of the combination of traffic conditioning =
at DS=20
boundary nodes along with security and integrity of the network =
infrastructure=20
within a D<SPAN class=3D085520317-17022003>iff-</SPAN>S<SPAN=20
class=3D085520317-17022003>erv</SPAN> domain, may be followed when DS-TE =
is in=20
use. Also, as stated in [TE-REQ], it is specifically important that =
manipulation=20
of administratively configurable parameters (such as those related to =
DS-TE=20
LSPs) be executed in a secure manner by authorized =
entities.</SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D085520317-17022003>"</SPAN></SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D085520317-17022003></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D085520317-17022003><FONT face=3DArial=20
size=3D2>Thanks</FONT></SPAN></SPAN></DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D085520317-17022003><FONT face=3DArial=20
size=3D2></FONT></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN=20
style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; =
mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; =
mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><SPAN=20
class=3D085520317-17022003><FONT face=3DArial=20
size=3D2>Francois</FONT></SPAN></SPAN></DIV></BODY></HTML>
=00
------_=_NextPart_001_01C2D6A7.371C9328--



From owner-te-wg@ops.ietf.org  Tue Feb 18 10:32: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 KAA00101
	for <tewg-archive@lists.ietf.org>; Tue, 18 Feb 2003 10:32:42 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18l9eI-0009Mm-00
	for te-wg-data@psg.com; Tue, 18 Feb 2003 07:27:10 -0800
Received: from mailgate.pit.comms.marconi.com ([169.144.68.6])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18l9eD-0009MQ-00
	for te-wg@ops.ietf.org; Tue, 18 Feb 2003 07:27:05 -0800
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA04305;
	Tue, 18 Feb 2003 10:27:02 -0500 (EST)
Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA27302;
	Tue, 18 Feb 2003 10:27:03 -0500 (EST)
Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19)
	id <D3QM3BA1>; Tue, 18 Feb 2003 10:27:02 -0500
Message-ID: <313680C9A886D511A06000204840E1CF8F5376@whq-msgusr-02.pit.comms.marconi.com>
From: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
To: "'Francois Le Faucheur (flefauch)'" <flefauch@cisco.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: te-wg@ops.ietf.org
Subject: RE: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00
	)
Date: Tue, 18 Feb 2003 10:27:01 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Status: No, hits=-0.1 required=5.0
	tests=EXCHANGE_SERVER,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


-----Original Message-----
>From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
>Sent: Monday, February 17, 2003 9:18 AM
>To: Ash, Gerald R (Jerry), ALABS; Choudhury, Sanjaya
>Cc: te-wg@ops.ietf.org
>Subject: RE: Request for comments: DSTE-MIB
>(draft-nadeau-mpls-dste-mib-00)

<snip....>

>> > Known TBDs:
>> > 	1. Update to reflect the latest DSTE-REQ and DSTE-PROTO
>> > 	2. Update to handle MAR BC Model
>> > 	3. reorg. the reference section.
>> 
>> I'm glad to see that you will include updates to handle the 
>> MAR (Maximum Allocation with Reservation) Model.  I presume 
>> you will also include updates to handle the Maximum 
>> Allocation Model (MAM).  The only model discussed in the MIB 
>> at present is the Russian Doll Model.

>I agree with Jerry that MAM should be covered in addition to RDM since
>the WG agrees on their respective definition and has agreed to specify
>these two BC models asap.

>With respect to MAR, while I agree in principle that it will need to
>have MIB support once it is specified, I would recommend that this piece
>of work is progressed outside of the main DS-TE MIB work. This is
>because while the WG agrees that we should investigate MAR further, I
>think we are still some time away before we have converged on a final
>MAR specification. So we should make sure we don't end up holding the
>core DS-TE MIB because of discussion on a longer term model.

>Does that make sense?

 Hi!
 The MIB as defined today is quite independent of individual BC
 Models(RD/MAM/MAR). The only reference to the BC models are 
 made in the following contexts:
 (i)  Examples of overall configurations (for sample scenarios)
 (ii) Examples of rules to be enforced to for different
	BC models, based on the configured BC model.
	[The draft requests user to refer to the BC Models 
	drafts for details.]

 No structural changes will be need to support MAM. Just need
 to update the examples. I will incorporate these in rev-02
 of the draft.

 Supporting MAR BC Model, will need only incremental work (
 addition/extension of a table ). I can post the necessary 
 changes to the list (instead of directly adding them to
 the draft) for review. Once the WG finalizes the MAR BC
 model, we can update the MIB. 
 
 Does this sound like a plan? [Any other alternatives?]
 
 Thanks,
 sanjay
 

 

 
	     
 
 


>Cheers

>Francois








From owner-te-wg@ops.ietf.org  Tue Feb 18 10:43:14 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00359
	for <tewg-archive@lists.ietf.org>; Tue, 18 Feb 2003 10:43:13 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18l9wI-000AEj-00
	for te-wg-data@psg.com; Tue, 18 Feb 2003 07:45:46 -0800
Received: from ams-msg-core-1.cisco.com ([144.254.74.60])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18l9wE-000AEX-00
	for te-wg@ops.ietf.org; Tue, 18 Feb 2003 07:45:42 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1IFi0ev011698;
	Tue, 18 Feb 2003 16:44:01 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 18 Feb 2003 16:45:37 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Date: Tue, 18 Feb 2003 15:45:36 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F901EDE35C@xbe-lon-303.cisco.com>
Thread-Topic: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Thread-Index: AcLXYmev+ahk1wG+SoedhFIX2jRN0AAAjfbQ
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 18 Feb 2003 15:45:37.0545 (UTC) FILETIME=[C8358F90:01C2D764]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA00359

Sanjaya,

>>  Hi!
>>  The MIB as defined today is quite independent of individual BC
>>  Models(RD/MAM/MAR). The only reference to the BC models are 
>>  made in the following contexts:
>>  (i)  Examples of overall configurations (for sample scenarios)
>>  (ii) Examples of rules to be enforced to for different
>> 	BC models, based on the configured BC model.
>> 	[The draft requests user to refer to the BC Models 
>> 	drafts for details.]
>> 
>>  No structural changes will be need to support MAM. Just need
>>  to update the examples. I will incorporate these in rev-02
>>  of the draft.
>> 
>>  Supporting MAR BC Model, will need only incremental work (
>>  addition/extension of a table ). I can post the necessary 
>>  changes to the list (instead of directly adding them to
>>  the draft) for review. Once the WG finalizes the MAR BC
>>  model, we can update the MIB. 
>>  
>>  Does this sound like a plan? [Any other alternatives?]
>>  

This works me.
Thanks
Francois

>>  Thanks,
>>  sanjay
>>  
>> 
>>  
>> 
>>  
>> 	     
>>  
>>  
>> 
>> 
>> >Cheers
>> 
>> >Francois
>> 
>> 
>> 
>> 
>> 
>> 



From owner-te-wg@ops.ietf.org  Tue Feb 18 10:55:36 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00544
	for <tewg-archive@lists.ietf.org>; Tue, 18 Feb 2003 10:55:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18lA8U-000AnP-00
	for te-wg-data@psg.com; Tue, 18 Feb 2003 07:58:22 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18lA8R-000AnD-00
	for te-wg@ops.ietf.org; Tue, 18 Feb 2003 07:58:19 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h1IFuDxS004836
	for <te-wg@ops.ietf.org>; Tue, 18 Feb 2003 10:58:17 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E028D00CD; Tue, 18 Feb 2003 10:58:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Date: Tue, 18 Feb 2003 10:58:18 -0500
Message-ID: <28F05913385EAC43AF019413F674A01704A1774F@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: Request for comments: DSTE-MIB (draft-nadeau-mpls-dste-mib-00)
Thread-Index: AcLXYjRyBPo+GlE7RH+iwhr/NbUwYQAA//3g
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>, <te-wg@ops.ietf.org>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id KAA00544

Sanjay,

>  No structural changes will be need to support MAM. Just need
>  to update the examples. I will incorporate these in rev-02
>  of the draft.
> 
>  Supporting MAR BC Model, will need only incremental work (
>  addition/extension of a table ). I can post the necessary 
>  changes to the list (instead of directly adding them to
>  the draft) for review. Once the WG finalizes the MAR BC
>  model, we can update the MIB. 
>  
>  Does this sound like a plan? [Any other alternatives?]

This sounds good to me.

Thanks,
Jerry



From owner-te-wg@ops.ietf.org  Tue Feb 18 13:37: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 NAA04243
	for <tewg-archive@lists.ietf.org>; Tue, 18 Feb 2003 13:37:43 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18lCcj-000J6A-00
	for te-wg-data@psg.com; Tue, 18 Feb 2003 10:37:45 -0800
Received: from rtp-core-2.cisco.com ([64.102.124.13])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18lCcc-000J4K-00
	for te-wg@ops.ietf.org; Tue, 18 Feb 2003 10:37:38 -0800
Received: from bucket.cisco.com (IDENT:mirapoint@bucket.cisco.com [161.44.167.72])
	by rtp-core-2.cisco.com (8.12.6/8.12.6) with ESMTP id h1IIbRNh029573;
	Tue, 18 Feb 2003 13:37:28 -0500 (EST)
Received: from tnadeau-w2k.cisco.com (che-vpn-cluster-1-20.cisco.com [10.86.240.20])
	by bucket.cisco.com (Mirapoint)
	with ESMTP id ACP30226;
	Tue, 18 Feb 2003 13:37:26 -0500 (EST)
Message-Id: <5.2.0.9.2.20030218133604.021b8cf0@bucket.cisco.com>
X-Sender: tnadeau@bucket.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 18 Feb 2003 13:37:24 -0500
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
Subject: RE: Request for comments: DSTE-MIB
  (draft-nadeau-mpls-dste-mib-00)
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Choudhury, Sanjaya" <Sanjaya.Choudhury@marconi.com>,
        <te-wg@ops.ietf.org>
In-Reply-To: <BC2F7EDC0F122B439B4AF1C656BA34F90168E7BD@xbe-lon-303.cisco
 .com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

At 02:18 PM 2/17/2003 +0000, Francois Le Faucheur (flefauch) wrote:
>Hello Sanjay, Jerry,
>
> >> -----Original Message-----
> >> From: Ash, Gerald R (Jerry), ALABS [mailto:gash@att.com]
> >> Sent: 15 February 2003 00:13
> >> To: Choudhury, Sanjaya
> >> Cc: Ash, Gerald R (Jerry), ALABS; te-wg@ops.ietf.org
> >> Subject: RE: Request for comments: DSTE-MIB
> >> (draft-nadeau-mpls-dste-mib-00)
> >>
> >>
> >> Sanjay,
> >>
> >> > Hi! Your comments on the following draft will be appreciated:
> >> >
> >> http://www.ietf.org/internet-drafts/draft->>
>nadeau-mpls-dste-mib-00.txt
> >> >
> >> > Known TBDs:
> >> >    1. Update to reflect the latest DSTE-REQ and DSTE-PROTO
> >> >    2. Update to handle MAR BC Model
> >> >    3. reorg. the reference section.
> >>
> >> I'm glad to see that you will include updates to handle the
> >> MAR (Maximum Allocation with Reservation) Model.  I presume
> >> you will also include updates to handle the Maximum
> >> Allocation Model (MAM).  The only model discussed in the MIB
> >> at present is the Russian Doll Model.
>
>I agree with Jerry that MAM should be covered in addition to RDM since
>the WG agrees on their respective definition and has agreed to specify
>these two BC models asap.
>
>With respect to MAR, while I agree in principle that it will need to
>have MIB support once it is specified, I would recommend that this piece
>of work is progressed outside of the main DS-TE MIB work. This is
>because while the WG agrees that we should investigate MAR further, I
>think we are still some time away before we have converged on a final
>MAR specification. So we should make sure we don't end up holding the
>core DS-TE MIB because of discussion on a longer term model.
>
>Does that make sense?

         Yes, it does to me.  We will put the core DS-TE functionality into
the DS-TE MIB and additional functions can be appended at a later time.
I believe that the MIB is constructed in such a way as to facilitate
this -- or at least we have tried to design it that way.

         --Tom


>Cheers
>
>Francois

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

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







From owner-te-wg@ops.ietf.org  Wed Feb 19 07:08:33 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20266
	for <tewg-archive@lists.ietf.org>; Wed, 19 Feb 2003 07:08:32 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18lT1V-0004xh-00
	for te-wg-data@psg.com; Wed, 19 Feb 2003 04:08:25 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18lT1Q-0004xL-00
	for te-wg@ops.ietf.org; Wed, 19 Feb 2003 04:08:20 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20084;
	Wed, 19 Feb 2003 07:04:29 -0500 (EST)
Message-Id: <200302191204.HAA20084@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-05.txt
Date: Wed, 19 Feb 2003 07:04:28 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: A Framework for Internet Traffic Engineering 
                          Measurement
	Author(s)	: W. Lai, R. Tibbs, S. Van den Berghe
	Filename	: draft-ietf-tewg-measure-05.txt
	Pages		: 28
	Date		: 2003-2-14
	
In this document, a measurement framework for supporting the traffic 
engineering of IP-based networks is presented.  Uses of traffic 
measurement in service provider environments are described, and 
issues related to time scale and read-out period are discussed.  
Different measurement types are classified, with each being 
specified as a meaningful combination of a measurement entity and a 
measurement basis. 
For interoperable compatibility, uniform definitions across vendors 
and operators must be ensured, e.g., in the distinction between 
offered load and achieved throughput.  To aid network dimensioning, 
mechanisms to collect node-pair-based traffic data should be 
developed to facilitate the derivation of per-service-class traffic 
matrix statistics.  For service assurance, there is a need for the 
use of higher-order statistics.  To preserve representative traffic 
detail at manageable sample volumes, there is a need for packet-
sampled measurements.  To manage large volume of measured data, use 
of bulk transfer and filtering/aggregation mechanisms may be 
appropriate.

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Feb 19 15:17:37 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07543
	for <tewg-archive@lists.ietf.org>; Wed, 19 Feb 2003 15:17:36 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18laab-0001ic-00
	for te-wg-data@psg.com; Wed, 19 Feb 2003 12:13:09 -0800
Received: from almso2.att.com ([192.128.166.71] helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18laaY-0001iO-00
	for te-wg@ops.ietf.org; Wed, 19 Feb 2003 12:13:06 -0800
Received: from attrh3i.attrh.att.com ([135.71.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h1JJwbds019241
	for <te-wg@ops.ietf.org>; Wed, 19 Feb 2003 15:13:04 -0500 (EST)
Received: from occlust04evs1.ugd.att.com (135.71.164.13) by attrh3i.attrh.att.com (6.5.032)
        id 3DF6BD4E029C267D; Wed, 19 Feb 2003 15:13:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: WG Last Call Result:  draft-ietf-tewg-measure-04.txt
Date: Wed, 19 Feb 2003 15:12:51 -0500
Message-ID: <28F05913385EAC43AF019413F674A01702E5E051@OCCLUST04EVS1.ugd.att.com>
Thread-Topic: WG Last Call Result:  draft-ietf-tewg-measure-04.txt
Thread-Index: AcLRecVQ4oKPRT4TTHmJ9wETM8TCxQG10whg
From: "Lai, Wai S (Waisum), ALABS" <wlai@att.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <te-wg@ops.ietf.org>
Cc: <bwijnen@lucent.com>, <sob@harvard.edu>
X-Spam-Status: No, hits=0.5 required=5.0
	tests=SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA07543

TEWG,
   I would like to thank all of you who responded to the Last Call
on the TE Measurement draft issued by the WG chairs.  A new version
is now available:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-measure-05.txt
My co-authors and I believe that we have incorporated all comments
received during the Last Call in this version.
Thanks, Wai Sum

-----Original Message-----
From: Jim Boyle [mailto:jboyle@pdnets.com]
Sent: Monday, February 10, 2003 9:46 PM
To: te-wg@ops.ietf.org
Cc: bwijnen@lucent.com; sob@harvard.edu
Subject: WG Last Call Result: draft-ietf-tewg-measure-04.txt



Looks like most people who replied think this draft is on-target and
ready 
to go.  There were some comments, so I believe we will wait for the 
authors to revise the draft, then it will be sent up to IESG for 
consideration as an informational RFC.

thanks,

Jim



From owner-te-wg@ops.ietf.org  Thu Feb 20 07:10:29 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08426
	for <tewg-archive@lists.ietf.org>; Thu, 20 Feb 2003 07:10:29 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18lpSz-000PeV-00
	for te-wg-data@psg.com; Thu, 20 Feb 2003 04:06:17 -0800
Received: from halt-in.cisco.com ([171.70.144.185])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18lpSw-000PeH-00
	for te-wg@ops.ietf.org; Thu, 20 Feb 2003 04:06:14 -0800
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 20 Feb 2003 04:06:13 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1KC4YJ5010496;
	Thu, 20 Feb 2003 13:04:35 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Thu, 20 Feb 2003 13:06:11 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: Alignment with Diff-Serv terminology in draft-tewg-diff-te-reqts-07.txt
Date: Thu, 20 Feb 2003 12:06:10 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F90168E7D0@xbe-lon-303.cisco.com>
Thread-Topic: Alignment with Diff-Serv terminology in draft-tewg-diff-te-reqts-07.txt
Thread-Index: AcLWjd6AkuUY253LQJmFZuwSWsIuBgAAdcXAAGaL/XAAAFXaQAAqoh1A
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Cc: "Kathleen Nichols" <kmn@mountainfog.com>,
        "Brian E Carpenter" <brian@hursley.ibm.com>
X-OriginalArrivalTime: 20 Feb 2003 12:06:11.0756 (UTC) FILETIME=[759D16C0:01C2D8D8]
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_02_03
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id HAA08426

Hello,

As part of the IESG last call on -reqts-06, Kathie commented on how to
improve the use of Diff-Serv terminology and constructs. With the help
of the Diff-Serv chairs (Brian and Kathie), we've come up with an
approach to address this. This message highlights the principle of this
approach. Please let us know if you have any issues/concerns with this.
If we don't hear any objections, we will post -reqts-07 by next Monday
incorporating the changes reflecting this approach.
Also, if anyone would like to see the working draft of -reqts-07 in
order to review the actual edits reflecting this approach, just drop me
a note off-line and I'll be happy to forward it.

Thanks

Francois

Principles of the approach:
===========================
 	- incorporate the definition of PDB (from RFC3086 "Definition of
Differentiated Services Per Domain Behaviors and Rules for their
Specification")
 	- use the term PDB when refering to the "treatement" of packets
in the DS domain (as opposed to the set of packets experiencing this
treatment)
 	- relate the concept of PDB and TA{PSC} : "A given {TA}PSC will
receive the treatment of the PDB associated with the corresponding PSC"
 	- systematically put quotation marks around the term "class of
service" and state that this term is used "loosely" and is used only "in
this document". This is to insist on the non-universality/looseness of
the term "class of service".
 	- only use the term "class of service" in the first high-level
sections (ie problem statement + scenarios) - these sections use layman
terminology to introduce high level concepts of DS-TE, so "class of
service" is acceptable/preferable in that context.



From owner-te-wg@ops.ietf.org  Thu Feb 20 11:47:44 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20884
	for <tewg-archive@lists.ietf.org>; Thu, 20 Feb 2003 11:47:44 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18ltrr-000AkS-00
	for te-wg-data@psg.com; Thu, 20 Feb 2003 08:48:15 -0800
Received: from oe48.pav0.hotmail.com ([64.4.32.128] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18ltrn-000AkF-00
	for te-wg@ops.ietf.org; Thu, 20 Feb 2003 08:48:11 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 20 Feb 2003 08:48:08 -0800
X-Originating-IP: [63.15.53.98]
Reply-To: "Victoria Fineberg" <fineberg@illinoisalumni.org>
From: "Victoria Fineberg" <fineberg@illinoisalumni.org>
To: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
        "Tewg \(E-mail\)" <te-wg@ops.ietf.org>
Cc: "Kathleen Nichols" <kmn@mountainfog.com>,
        "Brian E Carpenter" <brian@hursley.ibm.com>
References: <BC2F7EDC0F122B439B4AF1C656BA34F90168E7D0@xbe-lon-303.cisco.com>
Subject: Re: Alignment with Diff-Serv terminology in draft-tewg-diff-te-reqts-07.txt
Date: Thu, 20 Feb 2003 11:49:16 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <OE485wAz8AWiZAtGYkN0000048c@hotmail.com>
X-OriginalArrivalTime: 20 Feb 2003 16:48:08.0588 (UTC) FILETIME=[D8D4CCC0:01C2D8FF]
X-Spam-Status: No, hits=0.2 required=5.0
	tests=REFERENCES,SPAM_PHRASE_01_02,USER_AGENT_OE
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello All,

I think it is a very good idea to clean up the DS-TE
terminology.  When I was reading diff-te-reqts-06
I developed the following table:

---------------------------------------------------------------
Packet        Microflow     Externally      Network      FEC
handling      aggregation    observable     level view     view
                  on a link         router
                                         behavior
----------------------------------------------------------------
scheduling        BA           PHB            TA               FEC/TA
and dropping
-----------------------------------------------------------------
scheduling        OA          PSC        {TA}PSC    {FEC/TA}/PSC
only                                                    or CoS
                                                          or DS-CoS
-----------------------------------------------------------------

In the table, "Network level view" stands for generalization of
aggregation from the link level to the network level; and
"FEC view" stands for network-level aggregation associated
with a FEC.

When you finalize the new terminology, perhaps you can include
a similar table in Version-07?

Regards,

Victoria

Victoria Fineberg
fineberg@illinoisalumni.org


----- Original Message -----
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Cc: "Kathleen Nichols" <kmn@mountainfog.com>; "Brian E Carpenter"
<brian@hursley.ibm.com>
Sent: Thursday, February 20, 2003 7:06 AM
Subject: Alignment with Diff-Serv terminology in draft-tewg-diff-te-reqts-07.txt


Hello,

As part of the IESG last call on -reqts-06, Kathie commented on how to
improve the use of Diff-Serv terminology and constructs. With the help
of the Diff-Serv chairs (Brian and Kathie), we've come up with an
approach to address this. This message highlights the principle of this
approach. Please let us know if you have any issues/concerns with this.
If we don't hear any objections, we will post -reqts-07 by next Monday
incorporating the changes reflecting this approach.
Also, if anyone would like to see the working draft of -reqts-07 in
order to review the actual edits reflecting this approach, just drop me
a note off-line and I'll be happy to forward it.

Thanks

Francois

Principles of the approach:
===========================
  - incorporate the definition of PDB (from RFC3086 "Definition of
Differentiated Services Per Domain Behaviors and Rules for their
Specification")
  - use the term PDB when refering to the "treatement" of packets
in the DS domain (as opposed to the set of packets experiencing this
treatment)
  - relate the concept of PDB and TA{PSC} : "A given {TA}PSC will
receive the treatment of the PDB associated with the corresponding PSC"
  - systematically put quotation marks around the term "class of
service" and state that this term is used "loosely" and is used only "in
this document". This is to insist on the non-universality/looseness of
the term "class of service".
  - only use the term "class of service" in the first high-level
sections (ie problem statement + scenarios) - these sections use layman
terminology to introduce high level concepts of DS-TE, so "class of
service" is acceptable/preferable in that context.



From owner-te-wg@ops.ietf.org  Mon Feb 24 14:30:25 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23652
	for <tewg-archive@lists.ietf.org>; Mon, 24 Feb 2003 14:30:24 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nOGq-0006RS-00
	for te-wg-data@psg.com; Mon, 24 Feb 2003 11:28:12 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nOGe-0006Pq-00
	for te-wg@ops.ietf.org; Mon, 24 Feb 2003 11:28:00 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h1OJOObP019225;
	Mon, 24 Feb 2003 19:24:25 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id TAA16804;
	Mon, 24 Feb 2003 19:24:23 GMT
Message-Id: <5.1.0.14.0.20030224112001.0277a7a8@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 24 Feb 2003 11:24:16 -0800
To: <te-wg@ops.ietf.org>
From: raymond zhang <zhangr@info.net>
Subject: Fwd: Re: Inter AS TE Req'ts draft
Cc: Jean Philippe Vasseur <jvasseur@cisco.com>,
        "David Allan" <dallan@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=0.5 required=5.0
	tests=FWD_MSG,SPAM_PHRASE_03_05
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi,

I am forwarding this correspondence to the list on behalf of Dave (with his 
permission) so that we can carry out this discussion on the list..

Regards,
Raymond


>Date: Sat, 22 Feb 2003 01:45:27 -0800
>To: "David Allan" <dallan@nortelnetworks.com>
>From: raymond zhang <zhangr@info.net>
>Subject: Re: Inter AS TE Req'ts draft
>Cc: Jean Philippe Vasseur <jvasseur@cisco.com>
>
>Hi Dave,
>
>Thank you very much for your comments.  See my comments in lines below.
>
>I wonder if it is ok with you to take this discussion on the tewg 
>mailing-list ?  The chair is concerned in adopting this draft as a wg 
>document due to not enough comments on the list ?
>
>Regards,
>Raymond
>
>
>At 02:57 PM 2/20/2003 -0500, David Allan wrote:
>
>>  A few comments...
>>
>>section 5.2 statement that tools to check LSPs haven't been established 
>>yet. There's actually a few, Y.1711 would work for TE LSPs and provide 
>>automated e2e fault detection. LSP_PING would have similar capability, 
>>but provides a more ambiguous result as it would depend on a working 
>>return path.
>
>I am not familiar with Y.1711 and will download from ITU site and 
>review.  Thanks for suggesting.
>
>>BTW the draft should mention that the tunnel HE needs to be routable 
>>inter area and that means the HE address needs to be advertised to peer 
>>areas. I think this also has implications with respect to the nodeid 
>>subobject draft.
>
>You mean inter igp areas (ospf) or levels (is-is)... Good point.  Will 
>incorporate. As for the nodeid draft, I assume you are referring to 
>"draft-vasseur-mpls-nodeid-subobject-00.txt"...  In our thinking, this 
>draft actually proposes a solution which may be used in leaking NHOP in 
>FRR where the HE/TE backup tunnels reside in two different ASes across the 
>ASBR.
>
>
>>I'm not sure why you postulate automated diagnosis is required (and we're 
>>looking at rather strange black hole effects that do not appear as link 
>>or node outages that would appear only to Y.1711/LSP_PING).
>
>This is actually per requirement from a couple of SP contributors to this 
>draft.   Today, as you know, when the LSP is broken, we have to examine 
>hop by hop along the path and check if the problem lies with control 
>plane/node/link/router/interface events...  It is rather cumbersome. A 
>tool that can provide both data and control information assisting 
>isolating the trouble areas would be very helpful - that's the level of 
>automation (cohesive trouble-shooting tools for both data forwarding and 
>control plane)...
>
>
>>Section 5.5 Diverse routing between providers may be problematic as SRLG 
>>admin is not global. Probably less of a problem than I imagine as the 
>>liklihood of two areas using the same duct while the asociated SRLGs are 
>>enumerated under different plans is probably not that high. Coordinating 
>>setup of working and diverse paths would be a bit trickier as graph 
>>splitting probably cannot work without a god box.
>
>Indeed, the implementation of which needs to be coordinated on a case by 
>case basis depending upon the physical path layout.  Not a straightforward 
>process.
>
>>When considering path protection mechanisms, a reference to Y.1720 (1:1 
>>and 1+1 protection switching structures for MPLS) may be a useful 
>>reference in addition to other multiple path schemes.
>
>Good point.  Will review Y.1720 a bit further and incorporate.  Thanks.
>
>>section 5.10: This gets interesting w.r.t LSP-PING and GTTP. Ideally if 
>>you really want to hide stuff while permitting at least some superficial 
>>testability, you'd need to run a one hop label between ASBR2 and B such 
>>that the intervening topology was hidden from any TTL based tools used 
>>from A....or depend on one way tools (e.g. Y1711 CV) only and obstruct 
>>responding to LSP_PING at 'B' for anything outside the local AS.
>
>I am not sure how this "one hop label" may be implemented in this 
>case.  Would you elaborate it a bit ? Maybe use the label for ASBR2 from 
>ASBR1 to represent the LSP to B inside AS2.  As a general practice today, 
>ttl propagation is disabled at the edge of the network.  So TTL based 
>tools will not able to see the explicit path within a different AS 
>expanded by a loose ASBR node...  By the way, this section is trying to 
>scope out the requirements where A in AS1 needs to be able to seek an 
>optimum path to B in AS2 without knowing the details of AS2, as one of the 
>options.
>
>>interesting work...
>
>Thanks for your comments once again.
>
>>cheers
>>Dave





From owner-te-wg@ops.ietf.org  Mon Feb 24 15:09: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 PAA24892
	for <tewg-archive@lists.ietf.org>; Mon, 24 Feb 2003 15:09:23 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nOwH-00091r-00
	for te-wg-data@psg.com; Mon, 24 Feb 2003 12:11:01 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nOwA-00091P-00
	for te-wg@ops.ietf.org; Mon, 24 Feb 2003 12:10:54 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h1OJwabP025415;
	Mon, 24 Feb 2003 19:58:37 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id TAA17326;
	Mon, 24 Feb 2003 19:58:35 GMT
Message-Id: <5.1.0.14.0.20030224112431.027aca78@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 24 Feb 2003 11:48:30 -0800
To: "David Allan" <dallan@nortelnetworks.com>
From: raymond zhang <zhangr@info.net>
Subject: RE: Inter AS TE Req'ts draft
Cc: Jean Philippe Vasseur <jvasseur@cisco.com>, <te-wg@ops.ietf.org>
In-Reply-To: <FFFC48AEAA5F7447929F4F0D93FCC12D0165D427@zcard031.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-2.7 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Dave,

Please see comments in line...

Regards.
Raymond
At 11:32 AM 2/24/2003 -0500, David Allan wrote:

>Hi Raymond:
>
>No issue with moving the discussion to the list....
>
>Snipped down to only discussion points.....
>
><snip>
> > >section 5.2 statement that tools to check LSPs haven't been
> > established
> > >yet. There's actually a few, Y.1711 would work for TE LSPs
> > and provide
> > >automated e2e fault detection. LSP_PING would have similar
> > capability, but
> > >provides a more ambiguous result as it would depend on a
> > working return path.
> >
> > I am not familiar with Y.1711 and will download from ITU site and
> > review.  Thanks for suggesting.
>
>If you need any clarifications, consider me a resource....

Surely.. Thanks in advance.

> >
> > >BTW the draft should mention that the tunnel HE needs to be
> > routable inter
> > >area and that means the HE address needs to be advertised to
> > peer areas. I
> > >think this also has implications with respect to the nodeid
> > subobject draft.
> >
> > You mean inter igp areas (ospf) or levels (is-is)... Good
> > point.  Will
> > incorporate.
>
>Yes, I meant inter area(OSPF)/level(ISIS).
>
> > As for the nodeid draft, I assume you are referring to
> > "draft-vasseur-mpls-nodeid-subobject-00.txt"...  In our
> > thinking, this
> > draft actually proposes a solution which may be used in
> > leaking NHOP in FRR
> > where the HE/TE backup tunnels reside in two different ASes
> > across the ASBR.
>
>Yes I was referring to that draft. Understood it's applicability to FRR, 
>not sure if there were other implications w.r.t. ensuring that the tunnel 
>head end was properly advertised to other areas/levels so that diagnositic 
>tools had a viable return path.

Right...

>Perhaps simply ensuring that there is a viable return path is the 
>requirement. (e.g. if we pursue bi-directional LSPs at some point in the 
>future, a return path is not dependent on the routing system).

Interesting point.  Will consider to include some wording about this...

> >
> >
> > >I'm not sure why you postulate automated diagnosis is
> > required (and we're
> > >looking at rather strange black hole effects that do not
> > appear as link or
> > >node outages that would appear only to Y.1711/LSP_PING).
> >
> > This is actually per requirement from a couple of SP
> > contributors to this
> > draft.   Today, as you know, when the LSP is broken, we have
> > to examine hop
> > by hop along the path and check if the problem lies with control
> > plane/node/link/router/interface events...  It is rather
> > cumbersome. A tool
> > that can provide both data and control information assisting
> > isolating the
> > trouble areas would be very helpful - that's the level of automation
> > (cohesive trouble-shooting tools for both data forwarding and control
> > plane)...
>
>Then my question assumed a different interpretation of "automated tool". 
>If by automated, you mean can be executed from a single point in the 
>network by a craftsperson and does not reuqire manual examination of 
>forwarding tables, then I am in complete agreement :-)

Right... We don't mean the sense of automation in your previous comments. 
That's level of requirement we have so far...  Do you have different 
suggestions in terms of automation ?

> > >Section 5.5 Diverse routing between providers may be
> > problematic as SRLG
> > >admin is not global. Probably less of a problem than I
> > imagine as the
> > >liklihood of two areas using the same duct while the
> > asociated SRLGs are
> > >enumerated under different plans is probably not that high.
> > Coordinating
> > >setup of working and diverse paths would be a bit trickier as graph
> > >splitting probably cannot work without a god box.
> >
> > Indeed, the implementation of which needs to be coordinated
> > on a case by
> > case basis depending upon the physical path layout.  Not a
> > straightforward
> > process.
> >
> > >When considering path protection mechanisms, a reference to
> > Y.1720 (1:1
> > >and 1+1 protection switching structures for MPLS) may be a useful
> > >reference in addition to other multiple path schemes.
> >
> > Good point.  Will review Y.1720 a bit further and
> > incorporate.  Thanks.
>
>Note 1720 is only consented, not a reccomendation as of yet.

Understood...

> >
> > >section 5.10: This gets interesting w.r.t LSP-PING and GTTP.
> > Ideally if
> > >you really want to hide stuff while permitting at least some
> > superficial
> > >testability, you'd need to run a one hop label between ASBR2
> > and B such
> > >that the intervening topology was hidden from any TTL based
> > tools used
> > >from A....or depend on one way tools (e.g. Y1711 CV) only
> > and obstruct
> > >responding to LSP_PING at 'B' for anything outside the local AS.
> >
> > I am not sure how this "one hop label" may be implemented in this
> > case.  Would you elaborate it a bit ? Maybe use the label for
> > ASBR2 from
> > ASBR1 to represent the LSP to B inside AS2.
>
>I was actually thinking that connectivity from ASBR2 to B was overlaid via 
>a single label so that there was only one TTL hop and any traceroute tool 
>would only see ASBR2 and B and no intervening network. Adds some 
>complexity but the alternative is authentication/permissions etc.

Maybe a requirement for tracing loosely routed LSP to a known specific 
tunnel ending address ?

> > As a general
> > practice today,
> > ttl propagation is disabled at the edge of the network.
>
>Wasn't aware of that. Need to think that one through as it both simplifies 
>and complicates life. Presumably it would introduce a discontinuity in 
>tracing that would have the same effect as my one hop LSP. (e.g. if ttl is 
>overwritten with 255 at an ASBR, then any traceroute would never see 
>details outside of the originating area/level).
>
> > So TTL based tools
> > will not able to see the explicit path within a different AS
> > expanded by a
> > loose ASBR node...  By the way, this section is trying to
> > scope out the
> > requirements where A in AS1 needs to be able to seek an
> > optimum path to B
> > in AS2 without knowing the details of AS2, as one of the options.
>
>Understood. Presumably ASBR2 owns that problem... ;-)
>
>cheers
>Dave





From owner-te-wg@ops.ietf.org  Mon Feb 24 18:53:02 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00697
	for <tewg-archive@lists.ietf.org>; Mon, 24 Feb 2003 18:53:01 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nSPe-000NHT-00
	for te-wg-data@psg.com; Mon, 24 Feb 2003 15:53:34 -0800
Received: from sa.infonet.com ([192.157.130.21])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nSP7-000NDs-00
	for te-wg@ops.ietf.org; Mon, 24 Feb 2003 15:53:01 -0800
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id h1ONqibP028428;
	Mon, 24 Feb 2003 23:52:44 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id XAA19842;
	Mon, 24 Feb 2003 23:52:43 GMT
Message-Id: <5.1.0.14.0.20030224150804.02813df0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 24 Feb 2003 15:52:36 -0800
To: "David Allan" <dallan@nortelnetworks.com>
From: raymond zhang <zhangr@info.net>
Subject: RE: Inter AS TE Req'ts draft
Cc: Jean Philippe Vasseur <jvasseur@cisco.com>, <te-wg@ops.ietf.org>
In-Reply-To: <FFFC48AEAA5F7447929F4F0D93FCC12D0165D427@zcard031.ca.norte
 l.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-0.8 required=5.0
	tests=IN_REP_TO,QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Dave,

><snip>
> > >section 5.2 statement that tools to check LSPs haven't been
> > established
> > >yet. There's actually a few, Y.1711 would work for TE LSPs
> > and provide
> > >automated e2e fault detection. LSP_PING would have similar
> > capability, but
> > >provides a more ambiguous result as it would depend on a
> > working return path.
> >

I'd like to get back to this point...  An end-to-end automated OAM 
mechanism over LSP in Y.1711 sounds indeed very interesting.  Now I 
understand the working return path issue brought forth by LSP_PING.  I am 
sure this has been discussed in the ITU wg but I am a bit concerned as to 
how scalable would this be since for the most cases, these LSPs are 
terminated at P/PE devices...  If implemented, it may be turned on as 
needed basis should some LSP path become chronically unstable ?

The other question is how to extend this over AS boundaries with revealing 
network details in a loose LSP path ?

Regards,
Raymond




From owner-te-wg@ops.ietf.org  Tue Feb 25 04:26:58 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21583
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 04:26:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nbL6-00075A-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 01:25:28 -0800
Received: from halt-in.cisco.com ([171.70.144.185])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nbKb-000739-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 01:24:57 -0800
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 25 Feb 2003 01:24:54 -0800
Received: from xbe-ams-313.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1P9NGkK025015;
	Tue, 25 Feb 2003 10:23:17 +0100 (MET)
Received: from xbe-lon-303.cisco.com ([64.103.98.22]) by xbe-ams-313.cisco.com with Microsoft SMTPSVC(5.0.2195.4453);
	 Tue, 25 Feb 2003 10:24:55 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: Max Reservable Bandwidth in diff-te-proto
Date: Tue, 25 Feb 2003 09:24:54 -0000
Message-ID: <BC2F7EDC0F122B439B4AF1C656BA34F901EDE3B2@xbe-lon-303.cisco.com>
Thread-Topic: Max Reservable Bandwidth in diff-te-proto
Thread-Index: AcLBqZqecqlTNYABTpG+TBf5cL/FRwa+rGVw
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Victoria Fineberg" <fineberg@illinoisalumni.org>,
        "IETF TE-WG" <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 25 Feb 2003 09:24:55.0217 (UTC) FILETIME=[C2032A10:01C2DCAF]
X-Spam-Status: No, hits=0.0 required=5.0
	tests=QUOTED_EMAIL_TEXT,SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id EAA21583

Victoria,

>> -----Original Message-----
>> From: Victoria Fineberg [mailto:fineberg@illinoisalumni.org] 
>> Sent: 22 January 2003 09:04
>> To: Francois Le Faucheur (flefauch); IETF TE-WG
>> Subject: Protocols: BC in DS-TE IGPs
>> 
>> 
>> Francois, et al,
>> 
>> Sorry if this comment is coming late just before the "last call,"

just-before-last-call is much better than after-last-call.
Sorry for getting back to you late ^)

>> but if I am correct, it may be worthwhile to take care of it now.
>> 
>> draft-ietf-tewg-diff-te-proto-02.txt, Section 5.1, states that
>> 
>> "
>> 'existing Maximum Reservable Bandwidth' ... in now
>> interpreted as Bandwidth Constraint 0 (BC0).
>> "
>> 
>> This is true for the Russian Dolls BC Model, but not for
>> the Maximum Allocation Model (MAM), where BC0 is just
>> one of several components.  In the MAM, the existing
>> Maximum Reservable Bandwidth is the sum of BCb.
>> 

Actually, I think interpreting Max Reservable Bandwidth as BC0 is the
right thing to do for MAM. 
One reason is that we want to achieve interoperability between "old"
nodes supporting regular TE and "new" nodes supporting DSTE (for
establishment for CT0 LSPs). See diff-te-proto Appendix C. This involves
advertising the Max Reservable Bandwidth to old LSRs. Thus, Max
Reservable Bandwidth needs to indicate the Bandwidth Constraint for CT0
(not for the aggregate across all CTs).

Thanks

Francois 

>> Cheers
>> 
>> Victoria
>> 
>> Victoria Fineberg
>> fineberg@illinoisalumni.org
>> 
>> 



From owner-te-wg@ops.ietf.org  Tue Feb 25 07:47:46 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28527
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 07:47:45 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18neVO-000DkA-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 04:48:18 -0800
Received: from oe42.pav0.hotmail.com ([64.4.32.122] helo=hotmail.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18neVL-000Djp-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 04:48:15 -0800
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 25 Feb 2003 04:48:14 -0800
X-Originating-IP: [63.15.53.153]
Reply-To: "Victoria Fineberg" <fineberg@illinoisalumni.org>
From: "Victoria Fineberg" <fineberg@illinoisalumni.org>
To: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>,
        "IETF TE-WG" <te-wg@ops.ietf.org>
References: <BC2F7EDC0F122B439B4AF1C656BA34F901EDE3B2@xbe-lon-303.cisco.com>
Subject: Re: Max Reservable Bandwidth in diff-te-proto
Date: Tue, 25 Feb 2003 07:49:22 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <OE42Ki3s1wsXZZTHfyQ0000077b@hotmail.com>
X-OriginalArrivalTime: 25 Feb 2003 12:48:14.0838 (UTC) FILETIME=[298D9960:01C2DCCC]
X-Spam-Status: No, hits=-0.6 required=5.0
	tests=QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,
	      USER_AGENT_OE
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Francois,

Thanks.  I agree with your explanation and
diff-te-proto Appendix C supports it.

Cheers,

Victoria

Victoria Fineberg
fineberg@illinoisalumni.org


----- Original Message -----
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Victoria Fineberg" <fineberg@illinoisalumni.org>; "IETF TE-WG"
<te-wg@ops.ietf.org>
Sent: Tuesday, February 25, 2003 4:24 AM
Subject: RE: Max Reservable Bandwidth in diff-te-proto


Victoria,

>> -----Original Message-----
>> From: Victoria Fineberg [mailto:fineberg@illinoisalumni.org]
>> Sent: 22 January 2003 09:04
>> To: Francois Le Faucheur (flefauch); IETF TE-WG
>> Subject: Protocols: BC in DS-TE IGPs
>>
>>
>> Francois, et al,
>>
>> Sorry if this comment is coming late just before the "last call,"

just-before-last-call is much better than after-last-call.
Sorry for getting back to you late ^)

>> but if I am correct, it may be worthwhile to take care of it now.
>>
>> draft-ietf-tewg-diff-te-proto-02.txt, Section 5.1, states that
>>
>> "
>> 'existing Maximum Reservable Bandwidth' ... in now
>> interpreted as Bandwidth Constraint 0 (BC0).
>> "
>>
>> This is true for the Russian Dolls BC Model, but not for
>> the Maximum Allocation Model (MAM), where BC0 is just
>> one of several components.  In the MAM, the existing
>> Maximum Reservable Bandwidth is the sum of BCb.
>>

Actually, I think interpreting Max Reservable Bandwidth as BC0 is the
right thing to do for MAM.
One reason is that we want to achieve interoperability between "old"
nodes supporting regular TE and "new" nodes supporting DSTE (for
establishment for CT0 LSPs). See diff-te-proto Appendix C. This involves
advertising the Max Reservable Bandwidth to old LSRs. Thus, Max
Reservable Bandwidth needs to indicate the Bandwidth Constraint for CT0
(not for the aggregate across all CTs).

Thanks

Francois

>> Cheers
>>
>> Victoria
>>
>> Victoria Fineberg
>> fineberg@illinoisalumni.org
>>
>>



From owner-te-wg@ops.ietf.org  Tue Feb 25 13:35: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 NAA09902
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 13:35:21 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18njtQ-0003Rb-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 10:33:28 -0800
Received: from halt-in.cisco.com ([171.70.144.185])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18njtK-0003QC-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 10:33:22 -0800
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 25 Feb 2003 10:33:14 -0800
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1PIVghM018989;
	Tue, 25 Feb 2003 19:31:42 +0100 (MET)
Received: from JVASSEUR-W2K.cisco.com (sjc-vpn3-23.cisco.com [10.21.64.23])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA04256;
	Tue, 25 Feb 2003 19:33:18 +0100 (MET)
Message-Id: <4.3.2.7.2.20030225132521.03b74a58@paris.cisco.com>
X-Sender: jvasseur@paris.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 25 Feb 2003 13:33:16 -0500
To: mpls@UU.NET
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: FYI:
  http://www.ietf.org/internet-drafts/draft-vasseur-mpls-nodeid-subobject
 -00.txt
Cc: zali@cisco.com, Siva Sivabalan <msiva@cisco.com>,
        raymond_Zhang@infonet.com, te-wg@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi,

Just to let you know that we recently published 
http://www.ietf.org/internet-drafts/draft-vasseur-mpls-nodeid-subobject-00.txt. 
This draft just defines a very simple extension (basically a new flag in 
the IPv4 /IPv6 RRO sub-object) that allows to use MPLS TE Fast Reroute to 
protect against the link/node failure in the context of inter-area and 
inter-AS TE. Regarding inter-AS TE, this was clearly a requirement as per 
draft-zhang-mpls-interas-te-req, so I cc the TE WG here.

Any comment is as usual very welcome.

Thanks.

JP.



From owner-te-wg@ops.ietf.org  Tue Feb 25 15:10:08 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13260
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 15:10:08 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nlNn-0008h6-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 12:08:55 -0800
Received: from nitrous.tech.org ([207.168.1.229])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nlNk-0008gn-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 12:08:52 -0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by nitrous.tech.org (8.11.6+Sun/8.11.6) with ESMTP id h1PK9uh25030
	for <te-wg@ops.ietf.org>; Tue, 25 Feb 2003 15:09:56 -0500 (EST)
Date: Tue, 25 Feb 2003 15:08:51 -0500
From: Ed Kern <ejk@tech.org>
To: te-wg@ops.ietf.org
Subject: TE-operator call for presentations/input (multi-area) 
Message-ID: <2147483647.1046185731@[207.168.1.230]>
X-Mailer: Mulberry/3.0.0 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, hits=1.1 required=5.0
	tests=SPAM_PHRASE_03_05
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



 We are starting to take the first steps in the direction of defining
 requirements for multi-area TE.


 This was not fully fleshed out in Network Hierarchy and Multilayer
 Survivability (RFC3386) for several reasons.  At the time, the
 chairs, AD's, design team and WG simply werent sure if this was
 necessary or that if there was enough operator need to properly scope
 this work.

 Currently on the list we have been discussing requirements in the
 context of draft-zhang-mpls-interas-te-req-01.txt.  Before we proceed
 much further, the chairs would like to hear from operators who are:

 1. *Currently* in need of a multi-area solution on a production
 2. Currently deploying a version/flavor of multi-area TE.
 3. Waiting on a standard/guidance before planning/deploying
 4. Feel that these requirements should be scoped out regardless of
    current operational requirements.

 This is not an attempt to rope you into assisting with the current
 draft but more a request to:

 1. Present current protocol limitations/concerns at next ietf
 2. Discuss them on the list here

 We are specifically trying to target front-line engineering and
 operational efforts.  We understand that from an architectural
 perspective, having the path to multi-area and multi-as solutions
 is desirable.  However, we are uncertain how much of this is pulling
 up into *real* obstacles at this time.

Ed & Jim



From owner-te-wg@ops.ietf.org  Tue Feb 25 15:11:15 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13316
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 15:11:14 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nlTG-00094o-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 12:14:34 -0800
Received: from p-mail2.rd.francetelecom.com ([193.49.124.32] helo=p-mail2)
	by psg.com with smtp (Exim 3.36 #1)
	id 18nlTB-00094J-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 12:14:29 -0800
Received: from parsmtp2.rd.francetelecom.com ([10.193.117.129]) by 192.144.74.32 with InterScan Messaging Security Suite; Tue, 25 Feb 2003 21:19:18 +0100
Received: from lanmhs30.rd.francetelecom.fr ([10.193.21.61]) by parsmtp2.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 25 Feb 2003 21:14:25 +0100
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: Comments on draft-zhang-mpls-interas-te-req
Date: Tue, 25 Feb 2003 21:14:24 +0100
Message-ID: <1FB136FD10CE33409C882630E299F5BE1EDC0F@lanmhs30.rd.francetelecom.fr>
Thread-Topic: Max Reservable Bandwidth in diff-te-proto
Thread-Index: AcLBqZqecqlTNYABTpG+TBf5cL/FRwa+rGVwABjI7RA=
From: "LE ROUX Jean-Louis FTRD/DAC/LAN" <jeanlouis.leroux@rd.francetelecom.com>
To: "IETF TE-WG" <te-wg@ops.ietf.org>, <raymond_zhang@infonet.com>,
        <jpv@cisco.com>
X-OriginalArrivalTime: 25 Feb 2003 20:14:25.0647 (UTC) FILETIME=[7E32DFF0:01C2DD0A]
X-Spam-Status: No, hits=0.8 required=5.0
	tests=SPAM_PHRASE_00_01
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id PAA13316


Hi folks,

I have several comments regarding draft-zhang-mpls-interas-te-req-01:

-4.2 Scenario II
Does the final comments "please note that the inter-AS MPLS TE..."
refers only to case 2.
If yes does it mean that, in case 1, the VRF functionality is located on
the RSP PE ? 
This section could require several clarifications...

-4.4 Scenario IV
It could be relevant to illustrate this scenario with severals
application cases, including for instance the following case : A PE-PE
tunnel crossing two ASs of the same SP, for a L2VPN service (ie with
high QoS requirements)

Paragraph 2 : section 3.2 instead of "section 2.2"


-5.9 
"Application scenario II presented in section 3.2 above requires
multiple TE tunnels...". 
This is true only for scenario II case 2. 
(minor :  Section 4.2 instead of 3.2).

-5.10 Confidentiality 
"Optionally the TE LSP path cost within AS2 could be provided to A".
Do you mean that this cost could be provided "a posteriori" within the
Resv message, or "a priori" via PCC-PCS signaling. In the first case
this would require an RSVP extension, that could consist in adding a RRO
Cost subobject.

-6.2 Scalability

-"RSVP-TE"
-"RSVP message flooding"

Why such distinction? IMHO these two points can be grouped together.

Finally, note that we find a real interest in this document, as it
adresses our deployment cases.

Regards,

JL



From owner-te-wg@ops.ietf.org  Tue Feb 25 15:44:56 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15014
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 15:44:56 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nlxe-000Ako-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 12:45:58 -0800
Received: from halt-in.cisco.com ([171.70.144.185])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nlxZ-000AkX-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 12:45:53 -0800
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 25 Feb 2003 12:45:42 -0800
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1PKiDIa001649;
	Tue, 25 Feb 2003 21:44:13 +0100 (MET)
Received: from JVASSEUR-W2K.cisco.com (sjc-vpn3-23.cisco.com [10.21.64.23])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id VAA09516;
	Tue, 25 Feb 2003 21:45:49 +0100 (MET)
Message-Id: <4.3.2.7.2.20030225152946.037fc490@paris.cisco.com>
X-Sender: jvasseur@paris.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 25 Feb 2003 15:45:47 -0500
To: "LE ROUX Jean-Louis FTRD/DAC/LAN" <jeanlouis.leroux@rd.francetelecom.com>
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: Re: Comments on draft-zhang-mpls-interas-te-req
Cc: "IETF TE-WG" <te-wg@ops.ietf.org>, <raymond_zhang@infonet.com>,
        <jpv@cisco.com>
In-Reply-To: <1FB136FD10CE33409C882630E299F5BE1EDC0F@lanmhs30.rd.francet
 elecom.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-1.9 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,SPAM_PHRASE_01_02
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Jean-Louis,

Thanks for your comments, see bellow,

At 21:14 25/02/2003 +0100, LE ROUX Jean-Louis FTRD/DAC/LAN wrote:

>Hi folks,
>
>I have several comments regarding draft-zhang-mpls-interas-te-req-01:
>
>-4.2 Scenario II
>Does the final comments "please note that the inter-AS MPLS TE..."
>refers only to case 2.

Yes indeed as the CE is the inter-AS TE LSP Head-end so the TE LSP 
terminates within a VRF (if the CE is connected to a VRF in the context of 
MPLS VPN) or in the global routing table otherwise.

>If yes does it mean that, in case 1, the VRF functionality is located on
>the RSP PE ?

Correct (again, in the context of MPLS VPN).

Just remember that the CE is a generic term here.

>This section could require several clarifications...
>
>-4.4 Scenario IV
>It could be relevant to illustrate this scenario with severals
>application cases, including for instance the following case : A PE-PE
>tunnel crossing two ASs of the same SP, for a L2VPN service (ie with
>high QoS requirements)

Right, I agree, we'll illustrate this in the next rev (02) that will be 
published this week.

>Paragraph 2 : section 3.2 instead of "section 2.2"

thanks


>-5.9
>"Application scenario II presented in section 3.2 above requires
>multiple TE tunnels...".
>This is true only for scenario II case 2.
>(minor :  Section 4.2 instead of 3.2).

Right

>-5.10 Confidentiality
>"Optionally the TE LSP path cost within AS2 could be provided to A".
>Do you mean that this cost could be provided "a posteriori" within the
>Resv message, or "a priori" via PCC-PCS signaling. In the first case
>this would require an RSVP extension, that could consist in adding a RRO
>Cost subobject.

We mean "a priori". The point here is to be able, when sending a request to 
another AS, to get a response (positive or negative) with potentially the 
path cost even if the computed path is not provided (for confidentiality 
reasons). This way, the requesting LSR (PCC) could use this information to 
compute an optimal path (see the definition of "optimal" provided in this 
draft as well as the associated limitations). For instance [PATH-COMP] 
proposed such a mechanism where the Path computation request specifies that 
the path cost should be provided in the reply and the Path Computation 
reply contains an object (PATH-COST) specifying the path cost.

We'll clarify this in rev -02, thanks.

>-6.2 Scalability
>
>-"RSVP-TE"
>-"RSVP message flooding"
>
>Why such distinction? IMHO these two points can be grouped together.

Agree

>Finally, note that we find a real interest in this document, as it
>adresses our deployment cases.

That's an important feed-back, thanks.

JP.

>Regards,
>
>JL



From owner-te-wg@ops.ietf.org  Tue Feb 25 15:48: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 PAA15425
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 15:48:38 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nm2j-000B2R-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 12:51:13 -0800
Received: from alc136.alcatel.be ([195.207.101.136] helo=mail.alcatel.be)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nm2D-000B20-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 12:50:42 -0800
Received: from bemail05.net.alcatel.be (relay3 [127.0.0.1])
	by mail.alcatel.be (8.11.0/8.11.4) with ESMTP id h1PKoVY09262;
	Tue, 25 Feb 2003 21:50:31 +0100
Received: from alcatel.be ([138.203.64.155])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003022521502950:6870 ;
          Tue, 25 Feb 2003 21:50:29 +0100 
Message-ID: <3E5BD6D0.2C71C247@alcatel.be>
Date: Tue, 25 Feb 2003 21:49:20 +0100
From: Dimitri.Papadimitriou@alcatel.be
Organization: Optical Network Architecture (NTA - Antwerpen)
X-Mailer: Mozilla 4.79 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ed Kern <ejk@tech.org>
CC: te-wg@ops.ietf.org
Subject: Re: TE-operator call for presentations/input (multi-area)
References: <2147483647.1046185731@[207.168.1.230]>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 02/25/2003 21:50:29,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 02/25/2003 21:50:31,
	Serialize complete at 02/25/2003 21:50:31
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=0.0 required=5.0
	tests=NOSPAM_INC,NO_REAL_NAME,QUOTED_EMAIL_TEXT,REFERENCES,
	      SIGNATURE_SHORT_DENSE,SPAM_PHRASE_02_03,
	      USER_AGENT_MOZILLA_XM,X_ACCEPT_LANG
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

ed, 

i have a question directed to the user community
on inter-as srlg diverse path, how can we ensure
a single srlg id space exists ? i.e. even if the
signalling allows for carrying an exclusion set 
(for inst. is as_1 uses set {1,2,3} and as_2 the 
set {4,5,6} the rro gives the set {2,5}, and the
for the protecting lsp the he selects 1, how to 
be sure that 1 and 5 do not share a common risk,
for inst. a common fiber cable ?)

thanks,
- dimitri.

Ed Kern wrote:
> 
>  We are starting to take the first steps in the direction of defining
>  requirements for multi-area TE.
> 
>  This was not fully fleshed out in Network Hierarchy and Multilayer
>  Survivability (RFC3386) for several reasons.  At the time, the
>  chairs, AD's, design team and WG simply werent sure if this was
>  necessary or that if there was enough operator need to properly scope
>  this work.
> 
>  Currently on the list we have been discussing requirements in the
>  context of draft-zhang-mpls-interas-te-req-01.txt.  Before we proceed
>  much further, the chairs would like to hear from operators who are:
> 
>  1. *Currently* in need of a multi-area solution on a production
>  2. Currently deploying a version/flavor of multi-area TE.
>  3. Waiting on a standard/guidance before planning/deploying
>  4. Feel that these requirements should be scoped out regardless of
>     current operational requirements.
> 
>  This is not an attempt to rope you into assisting with the current
>  draft but more a request to:
> 
>  1. Present current protocol limitations/concerns at next ietf
>  2. Discuss them on the list here
> 
>  We are specifically trying to target front-line engineering and
>  operational efforts.  We understand that from an architectural
>  perspective, having the path to multi-area and multi-as solutions
>  is desirable.  However, we are uncertain how much of this is pulling
>  up into *real* obstacles at this time.
> 
> Ed & 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  : Work: +32 3 2408491 - Home: +32 2 3434361



From owner-te-wg@ops.ietf.org  Tue Feb 25 16:02:44 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16423
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 16:02:44 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nmGP-000Br6-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 13:05:21 -0800
Received: from halt-in.cisco.com ([171.70.144.185])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nmGL-000Bqq-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 13:05:17 -0800
Received: from cisco.com (144.254.74.60)
  by halt-in.cisco.com with ESMTP; 25 Feb 2003 13:05:06 -0800
Received: from cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id h1PL3aTw003286;
	Tue, 25 Feb 2003 22:03:37 +0100 (MET)
Received: from JVASSEUR-W2K.cisco.com (sjc-vpn3-23.cisco.com [10.21.64.23])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id WAA10426;
	Tue, 25 Feb 2003 22:05:13 +0100 (MET)
Message-Id: <4.3.2.7.2.20030225160229.03ef0848@paris.cisco.com>
X-Sender: jvasseur@paris.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 25 Feb 2003 16:05:11 -0500
To: Ed Kern <ejk@tech.org>
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: Re: TE-operator call for presentations/input (multi-area) 
Cc: te-wg@ops.ietf.org, raymond_Zhang@infonet.com
In-Reply-To: <2147483647.1046185731@[207.168.1.230]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Status: No, hits=-1.3 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,SPAM_PHRASE_03_05
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Ed,

I think your request is really legitimate. Now I'd just like to reenforce 
the fact that the requirements for inter-AS and multi-area should not be 
mixed as they are pretty much different. So the requirements for inter-AS 
TE are discussed in draft-zhang-mpls-interas-te-req-01.txt (we'll publish 
the next revision this week) and your question specifically refers to the 
requirements for multi-area, correct ?

Thanks.

JP.

At 15:08 25/02/2003 -0500, Ed Kern wrote:


>We are starting to take the first steps in the direction of defining
>requirements for multi-area TE.
>
>
>This was not fully fleshed out in Network Hierarchy and Multilayer
>Survivability (RFC3386) for several reasons.  At the time, the
>chairs, AD's, design team and WG simply werent sure if this was
>necessary or that if there was enough operator need to properly scope
>this work.
>
>Currently on the list we have been discussing requirements in the
>context of draft-zhang-mpls-interas-te-req-01.txt.  Before we proceed
>much further, the chairs would like to hear from operators who are:
>
>1. *Currently* in need of a multi-area solution on a production
>2. Currently deploying a version/flavor of multi-area TE.
>3. Waiting on a standard/guidance before planning/deploying
>4. Feel that these requirements should be scoped out regardless of
>    current operational requirements.
>
>This is not an attempt to rope you into assisting with the current
>draft but more a request to:
>
>1. Present current protocol limitations/concerns at next ietf
>2. Discuss them on the list here
>
>We are specifically trying to target front-line engineering and
>operational efforts.  We understand that from an architectural
>perspective, having the path to multi-area and multi-as solutions
>is desirable.  However, we are uncertain how much of this is pulling
>up into *real* obstacles at this time.
>
>Ed & Jim



From owner-te-wg@ops.ietf.org  Tue Feb 25 17:44:13 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20500
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 17:44:12 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nnpF-000HVk-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 14:45:25 -0800
Received: from h-135-207-21-32.research.att.com ([135.207.21.32] helo=NJFPSRVEXG2KCL.research.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nnoj-000HTD-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 14:44:53 -0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: TE-operator call for presentations/input (multi-area)
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Tue, 25 Feb 2003 17:44:51 -0500
Message-ID: <387B5A9BF31B5D43A2B18DD9F326B8E13009C1@NJFPSRVEXG2KCL.research.att.com>
Thread-Topic: TE-operator call for presentations/input (multi-area)
Thread-Index: AcLdD9W49JD0sKdYRrOoD2LzO7PmdgADvdUA
From: <jls@research.att.com>
To: <Dimitri.Papadimitriou@alcatel.be>, <ejk@tech.org>
Cc: <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=1.3 required=5.0
	tests=NO_REAL_NAME,QUOTED_EMAIL_TEXT,SPAM_PHRASE_02_03
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id RAA20500

Dimitri,
Assuming a single inter-as srlg space would be folly at present.
In fact, even within a single carrier network it is more likely
than not that there isn't a single srlg space - for example, most
large carriers have acquired other carriers in the last few years,
and I would bet a large amount of money that they haven't
integrated their physical maps in the detail required if there is
any significant overlap.

John

-----Original Message-----
From: Dimitri.Papadimitriou@alcatel.be [mailto:Dimitri.Papadimitriou@alcatel.be] 
Sent: Tuesday, February 25, 2003 3:49 PM
To: Ed Kern
Cc: te-wg@ops.ietf.org
Subject: Re: TE-operator call for presentations/input (multi-area)

ed, 

i have a question directed to the user community
on inter-as srlg diverse path, how can we ensure
a single srlg id space exists ? i.e. even if the
signalling allows for carrying an exclusion set 
(for inst. is as_1 uses set {1,2,3} and as_2 the 
set {4,5,6} the rro gives the set {2,5}, and the
for the protecting lsp the he selects 1, how to 
be sure that 1 and 5 do not share a common risk,
for inst. a common fiber cable ?)

thanks,
- dimitri.

Ed Kern wrote:
> 
>  We are starting to take the first steps in the direction of defining
>  requirements for multi-area TE.
> 
>  This was not fully fleshed out in Network Hierarchy and Multilayer
>  Survivability (RFC3386) for several reasons.  At the time, the
>  chairs, AD's, design team and WG simply werent sure if this was
>  necessary or that if there was enough operator need to properly scope
>  this work.
> 
>  Currently on the list we have been discussing requirements in the
>  context of draft-zhang-mpls-interas-te-req-01.txt.  Before we proceed
>  much further, the chairs would like to hear from operators who are:
> 
>  1. *Currently* in need of a multi-area solution on a production
>  2. Currently deploying a version/flavor of multi-area TE.
>  3. Waiting on a standard/guidance before planning/deploying
>  4. Feel that these requirements should be scoped out regardless of
>     current operational requirements.
> 
>  This is not an attempt to rope you into assisting with the current
>  draft but more a request to:
> 
>  1. Present current protocol limitations/concerns at next ietf
>  2. Discuss them on the list here
> 
>  We are specifically trying to target front-line engineering and
>  operational efforts.  We understand that from an architectural
>  perspective, having the path to multi-area and multi-as solutions
>  is desirable.  However, we are uncertain how much of this is pulling
>  up into *real* obstacles at this time.
> 
> Ed & 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  : Work: +32 3 2408491 - Home: +32 2 3434361




From owner-te-wg@ops.ietf.org  Tue Feb 25 18:15:15 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21817
	for <tewg-archive@lists.ietf.org>; Tue, 25 Feb 2003 18:15:15 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18noKc-000JLc-00
	for te-wg-data@psg.com; Tue, 25 Feb 2003 15:17:50 -0800
Received: from rdu57-28-045.nc.rr.com ([66.57.28.45] helo=fido.nc.rr.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18noK6-000JIv-00
	for te-wg@ops.ietf.org; Tue, 25 Feb 2003 15:17:18 -0800
Received: from fido.nc.rr.com (fido.nc.rr.com [127.0.0.1])
	by fido.nc.rr.com (8.12.5/8.12.5) with ESMTP id h1PNGPqk020239;
	Tue, 25 Feb 2003 18:16:25 -0500
Received: from localhost (jboyle@localhost)
	by fido.nc.rr.com (8.12.5/8.12.5/Submit) with ESMTP id h1PNGNE5020235;
	Tue, 25 Feb 2003 18:16:23 -0500
X-Authentication-Warning: fido.nc.rr.com: jboyle owned process doing -bs
Date: Tue, 25 Feb 2003 18:16:23 -0500 (EST)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@fido.nc.rr.com
To: Jean Philippe Vasseur <jvasseur@cisco.com>
cc: Ed Kern <ejk@tech.org>, <te-wg@ops.ietf.org>, <raymond_Zhang@infonet.com>
Subject: Re: TE-operator call for presentations/input (multi-area) 
In-Reply-To: <4.3.2.7.2.20030225160229.03ef0848@paris.cisco.com>
Message-ID: <Pine.LNX.4.44.0302251813350.20214-100000@fido.nc.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=-3.2 required=5.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT,
	      SPAM_PHRASE_02_03,USER_AGENT_PINE,X_AUTH_WARNING
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


The request is for anything that folks feel they require beyond RFC3386.
If that's multi-area only, fine, if it's multi-as only, fine.
If it's both, fine. Your draft has proven useful in being a catylyst
for this topic in general.

thanks,

Jim


On Tue, 25 Feb 2003, Jean Philippe Vasseur wrote:

> Hi Ed,
> 
> I think your request is really legitimate. Now I'd just like to reenforce 
> the fact that the requirements for inter-AS and multi-area should not be 
> mixed as they are pretty much different. So the requirements for inter-AS 
> TE are discussed in draft-zhang-mpls-interas-te-req-01.txt (we'll publish 
> the next revision this week) and your question specifically refers to the 
> requirements for multi-area, correct ?
> 
> Thanks.
> 
> JP.
> 
> At 15:08 25/02/2003 -0500, Ed Kern wrote:
> 
> 
> >We are starting to take the first steps in the direction of defining
> >requirements for multi-area TE.
> >
> >
> >This was not fully fleshed out in Network Hierarchy and Multilayer
> >Survivability (RFC3386) for several reasons.  At the time, the
> >chairs, AD's, design team and WG simply werent sure if this was
> >necessary or that if there was enough operator need to properly scope
> >this work.
> >
> >Currently on the list we have been discussing requirements in the
> >context of draft-zhang-mpls-interas-te-req-01.txt.  Before we proceed
> >much further, the chairs would like to hear from operators who are:
> >
> >1. *Currently* in need of a multi-area solution on a production
> >2. Currently deploying a version/flavor of multi-area TE.
> >3. Waiting on a standard/guidance before planning/deploying
> >4. Feel that these requirements should be scoped out regardless of
> >    current operational requirements.
> >
> >This is not an attempt to rope you into assisting with the current
> >draft but more a request to:
> >
> >1. Present current protocol limitations/concerns at next ietf
> >2. Discuss them on the list here
> >
> >We are specifically trying to target front-line engineering and
> >operational efforts.  We understand that from an architectural
> >perspective, having the path to multi-area and multi-as solutions
> >is desirable.  However, we are uncertain how much of this is pulling
> >up into *real* obstacles at this time.
> >
> >Ed & Jim
> 





From owner-te-wg@ops.ietf.org  Wed Feb 26 03:23:55 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28062
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 03:23:54 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18nwpe-0000Ao-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 00:22:26 -0800
Received: from mail1.telekom.de ([62.225.183.235])
	by psg.com with esmtp (Exim 3.36 #1)
	id 18nwpX-0000AZ-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 00:22:19 -0800
Received: from g8pbr.blf01.telekom.de by G8SBV.dmz.telekom.de with ESMTP; Wed, 26 Feb 2003 09:21:54 +0100
Received: by G8PBR.blf01.telekom.de with Internet Mail Service (5.5.2653.19)
	id <FRNPCBTD>; Wed, 26 Feb 2003 09:21:53 +0100
Message-Id: <9F8582E37B2EE5498E76392AEDDCD3FE23B36E@G8PQD.blf01.telekom.de>
From: "Geib, Ruediger" <Ruediger.Geib@t-systems.com>
To: ejk@tech.org
Cc: te-wg@ops.ietf.org
Subject: AW: TE-operator call for presentations/input (multi-area) 
Date: Wed, 26 Feb 2003 09:21:50 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Status: No, hits=1.9 required=5.0
	tests=EXCHANGE_SERVER,MSG_ID_ADDED_BY_MTA_3,SPAM_PHRASE_03_05
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Ed,

I can't collect real requirements this time, so please just take this message as a notion of interest:

|  1. *Currently* in need of a multi-area solution on a production

Talking as a individual, I'm pretty sure my company would be 
interested if implementations were available.

|  2. Currently deploying a version/flavor of multi-area TE.

Please let me know which vendors offer solutions. 

|  3. Waiting on a standard/guidance before planning/deploying

That's what I've did so far.

|  4. Feel that these requirements should be scoped out regardless of
|     current operational requirements.

This is not a good idea.
 
....
 
|  We are specifically trying to target front-line engineering and
|  operational efforts.  We understand that from an architectural
|  perspective, having the path to multi-area and multi-as solutions
|  is desirable.  However, we are uncertain how much of this is pulling
|  up into *real* obstacles at this time.

You forgot to mention heterogeneously equipped networks requiring 
standard solutions to all these issues.

Regards, Rudiger

 



From owner-te-wg@ops.ietf.org  Wed Feb 26 09:05:40 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05588
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 09:05:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18o2Bf-000C7P-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 06:05:31 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18o2Bb-000C79-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 06:05:27 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05286;
	Wed, 26 Feb 2003 09:01:31 -0500 (EST)
Message-Id: <200302261401.JAA05286@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-diff-te-russian-01.txt
Date: Wed, 26 Feb 2003 09:01:30 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Russian Dolls Bandwidth Constraints Model for 
                          Diff-Serv-aware MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur
	Filename	: draft-ietf-tewg-diff-te-russian-01.txt
	Pages		: 12
	Date		: 2003-2-25
	
This document provides specification for one Bandwidth Constraints 
model for Diff-Serv-aware MPLS Traffic Engineering, which is referred 
to as the Russian Dolls Model.

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

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Feb 26 09:06: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 JAA05611
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 09:06:10 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18o2Bd-000C7L-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 06:05:29 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18o2BY-000C6z-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 06:05:24 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05267;
	Wed, 26 Feb 2003 09:01:26 -0500 (EST)
Message-Id: <200302261401.JAA05267@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-diff-te-reqts-07.txt
Date: Wed, 26 Feb 2003 09:01:26 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Requirements for support of Diff-Serv-aware MPLS 
                          Traffic Engineering
	Author(s)	: F. Le Faucheur, W. Lai
	Filename	: draft-ietf-tewg-diff-te-reqts-07.txt
	Pages		: 19
	Date		: 2003-2-25
	
This document presents the Service Provider requirements for support 
of Diff-Serv aware MPLS Traffic Engineering (DS-TE).  
Its objective is to provide guidance for the definition, selection 
and specification of a technical solution addressing these  
requirements. Specification for this solution itself is outside the 
scope of this document. 
A problem statement is first provided. Then, the document describes 
example applications scenarios identified by Service Providers where 
existing MPLS Traffic Engineering mechanisms fall short and Diff-
Serv-aware Traffic Engineering is required. The detailed 
requirements that need to be addressed by the technical solution are 
also reviewed. Finally, the document identifies the evaluation 
criteria that should be considered for selection and definition of 
the technical solution.

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

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

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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tewg-diff-te-reqts-07.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-2-25160315.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-reqts-07.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Feb 26 09:06: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 JAA05656
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 09:06:40 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18o2A7-000C3X-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 06:03:55 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18o2A2-000C3L-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 06:03:50 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04806;
	Wed, 26 Feb 2003 08:59:53 -0500 (EST)
Message-Id: <200302261359.IAA04806@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-lefaucheur-diff-te-mam-00.txt
Date: Wed, 26 Feb 2003 08:59:53 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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


	Title		: Maximum Allocation Bandwidth Constraints Model for   
                          Diff-Serv-aware MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur
	Filename	: draft-lefaucheur-diff-te-mam-00.txt
	Pages		: 8
	Date		: 2003-2-25
	
This document provides specification for one Bandwidth Constraints 
model for Diff-Serv-aware MPLS Traffic Engineering, which is referred 
to as the Maximum Allocation Model.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-lefaucheur-diff-te-mam-00.txt

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Feb 26 09:07:11 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05700
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 09:07:10 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18o29w-000C3H-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 06:03:44 -0800
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18o29r-000C33-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 06:03:39 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04769;
	Wed, 26 Feb 2003 08:59:42 -0500 (EST)
Message-Id: <200302261359.IAA04769@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-deoliveira-diff-te-preemption-00.txt
Date: Wed, 26 Feb 2003 08:59:41 -0500
X-Spam-Status: No, hits=4.6 required=5.0
	tests=MIME_SUSPECT_NAME,NO_REAL_NAME,SEARCH_ENGINE_PROMO,
	      SPAM_PHRASE_01_02,TO_MALFORMED
	version=2.43
X-Spam-Level: ****
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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


	Title		: LSP Preemption policies for Diff-Serv-aware MPLS 
                          Traffic Engineering
	Author(s)	: J. de Oliveira et al.
	Filename	: draft-deoliveira-diff-te-preemption-00.txt
	Pages		: 0
	Date		: 2003-2-25
	
When the establishment of a higher priority LSP requires the preemption 
of a set of lower priority LSPs, the node has to make a local decision 
on the set of preemptable LSPs and select which LSPs will be preempted,
based on a certain objective, in order to accomodate the newly signaled 
high priority LSP. The preempted LSPs are then rerouted. This draft 
documents a preemption policy which can be modified in order to stress 
different objectives: preempt the lowest priority LSPs, preempt the 
minimum number of LSPs, preempt the exact required bandwidth in order 
to fit the new LSP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-deoliveira-diff-te-preemption-00.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-deoliveira-diff-te-preemption-00.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Feb 26 15:04:31 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22116
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 15:04:30 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18o7nG-0004Y2-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 12:04:42 -0800
Received: from alc136.alcatel.be ([195.207.101.136] helo=bt0g2p.god.bel.alcatel.be)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18o7nB-0004WC-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 12:04:37 -0800
Received: from bemail05.net.alcatel.be (relay3 [127.0.0.1])
	by bt0g2p.god.bel.alcatel.be (8.11.0/8.11.4) with ESMTP id h1QK4Ho07285;
	Wed, 26 Feb 2003 21:04:22 +0100
Received: from alcatel.be ([138.203.64.155])
          by bemail05.net.alcatel.be (Lotus Domino Release 5.0.11)
          with ESMTP id 2003022621041656:4776 ;
          Wed, 26 Feb 2003 21:04:16 +0100 
Message-ID: <3E5D1D7E.D4BA29DA@alcatel.be>
Date: Wed, 26 Feb 2003 21:03:10 +0100
From: Dimitri.Papadimitriou@alcatel.be
Organization: optical network architecture (nta - antwerpen)
X-Mailer: Mozilla 4.79 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: jls@research.att.com
Cc: ejk@tech.org, te-wg@ops.ietf.org
Subject: Re: TE-operator call for presentations/input (multi-area)
References: <387B5A9BF31B5D43A2B18DD9F326B8E13009C1@NJFPSRVEXG2KCL.research.att.com>
X-MIMETrack: Itemize by SMTP Server on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 02/26/2003 21:04:16,
	Serialize by Router on BEMAIL05/BE/ALCATEL(Release 5.0.11  |July 24, 2002) at
 02/26/2003 21:04:21,
	Serialize complete at 02/26/2003 21:04:21
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-0.3 required=5.0
	tests=NOSPAM_INC,NO_REAL_NAME,QUOTED_EMAIL_TEXT,REFERENCES,
	      SIGNATURE_SHORT_DENSE,SPAM_PHRASE_01_02,
	      USER_AGENT_MOZILLA_XM,X_ACCEPT_LANG
	version=2.43
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

john,

thanks, this means (following your below observation) 
that the most we could achieve is a 1:n diversity on 
a per as basis, and even then multiple spaces might
have to be considered; as such the constraint you 
mention here below says there is no way today to 
device any mapping between these spaces, so if an lsp 
covers several as's and has to be diverse from n other 
lsp's, the "exclusion" mechanism would allow to ensure
1:n diversity on a "per common topological segment" 
basis but not an global end-to-end one; please correct 
me if i misunderstood the below statement

thanks,
- dimitri.

jls@research.att.com wrote:
> 
> Dimitri,
> Assuming a single inter-as srlg space would be folly at present.
> In fact, even within a single carrier network it is more likely
> than not that there isn't a single srlg space - for example, most
> large carriers have acquired other carriers in the last few years,
> and I would bet a large amount of money that they haven't
> integrated their physical maps in the detail required if there is
> any significant overlap.
> 
> John
> 
> -----Original Message-----
> From: Dimitri.Papadimitriou@alcatel.be [mailto:Dimitri.Papadimitriou@alcatel.be]
> Sent: Tuesday, February 25, 2003 3:49 PM
> To: Ed Kern
> Cc: te-wg@ops.ietf.org
> Subject: Re: TE-operator call for presentations/input (multi-area)
> 
> ed,
> 
> i have a question directed to the user community
> on inter-as srlg diverse path, how can we ensure
> a single srlg id space exists ? i.e. even if the
> signalling allows for carrying an exclusion set
> (for inst. is as_1 uses set {1,2,3} and as_2 the
> set {4,5,6} the rro gives the set {2,5}, and the
> for the protecting lsp the he selects 1, how to
> be sure that 1 and 5 do not share a common risk,
> for inst. a common fiber cable ?)
> 
> thanks,
> - dimitri.
> 
> Ed Kern wrote:
> >
> >  We are starting to take the first steps in the direction of defining
> >  requirements for multi-area TE.
> >
> >  This was not fully fleshed out in Network Hierarchy and Multilayer
> >  Survivability (RFC3386) for several reasons.  At the time, the
> >  chairs, AD's, design team and WG simply werent sure if this was
> >  necessary or that if there was enough operator need to properly scope
> >  this work.
> >
> >  Currently on the list we have been discussing requirements in the
> >  context of draft-zhang-mpls-interas-te-req-01.txt.  Before we proceed
> >  much further, the chairs would like to hear from operators who are:
> >
> >  1. *Currently* in need of a multi-area solution on a production
> >  2. Currently deploying a version/flavor of multi-area TE.
> >  3. Waiting on a standard/guidance before planning/deploying
> >  4. Feel that these requirements should be scoped out regardless of
> >     current operational requirements.
> >
> >  This is not an attempt to rope you into assisting with the current
> >  draft but more a request to:
> >
> >  1. Present current protocol limitations/concerns at next ietf
> >  2. Discuss them on the list here
> >
> >  We are specifically trying to target front-line engineering and
> >  operational efforts.  We understand that from an architectural
> >  perspective, having the path to multi-area and multi-as solutions
> >  is desirable.  However, we are uncertain how much of this is pulling
> >  up into *real* obstacles at this time.
> >
> > Ed & 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  : Work: +32 3 2408491 - Home: +32 2 3434361

-- 
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 Feb 26 16:20:21 2003
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26122
	for <tewg-archive@lists.ietf.org>; Wed, 26 Feb 2003 16:20:20 -0500 (EST)
Received: from lserv by psg.com with local (Exim 3.36 #1)
	id 18o8wd-0008xc-00
	for te-wg-data@psg.com; Wed, 26 Feb 2003 13:18:27 -0800
Received: from h-135-207-21-32.research.att.com ([135.207.21.32] helo=NJFPSRVEXG2KCL.research.att.com)
	by psg.com with esmtp (Exim 3.36 #1)
	id 18o8wX-0008xP-00
	for te-wg@ops.ietf.org; Wed, 26 Feb 2003 13:18:21 -0800
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0
Subject: RE: TE-operator call for presentations/input (multi-area)
Date: Wed, 26 Feb 2003 16:18:21 -0500
Message-ID: <387B5A9BF31B5D43A2B18DD9F326B8E1300A0E@NJFPSRVEXG2KCL.research.att.com>
Thread-Topic: TE-operator call for presentations/input (multi-area)
Thread-Index: AcLd0kWlaKLm4y8pTIOoVqMa+azYPgACV5ng
From: <jls@research.att.com>
To: <Dimitri.Papadimitriou@alcatel.be>
Cc: <ejk@tech.org>, <te-wg@ops.ietf.org>
X-Spam-Status: No, hits=1.0 required=5.0
	tests=NO_REAL_NAME,QUOTED_EMAIL_TEXT,SPAM_PHRASE_01_02
	version=2.43
X-Spam-Level: *
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id QAA26122

Dimitri,
It's a little worse than that. It's likely that as's physically overlap ...
for example if they separately lease lines from the same transport carrier.
It's also common for 2 separate transport carriers to unknowingly have a
single shared point of failure ... for example they both might have fiber
buried under the same street in Manhattan.

I have a little on these problems in the 2/2001 article Angela Chiu and I
did in IEEE Communications, along with some suggestions on approaches for
optical networks.

John

John Strand
  AT&T Transport Network Evolution Dept.
  200 Laurel Ave., Room A5-1D33
  Middletown, NJ 07748
  +1 732 420-9036
  jls@research.att.com 

-----Original Message-----
From: Dimitri.Papadimitriou@alcatel.be [mailto:Dimitri.Papadimitriou@alcatel.be] 
Sent: Wednesday, February 26, 2003 3:03 PM
To: Strand,John L
Cc: ejk@tech.org; te-wg@ops.ietf.org
Subject: Re: TE-operator call for presentations/input (multi-area)


john,

thanks, this means (following your below observation) 
that the most we could achieve is a 1:n diversity on 
a per as basis, and even then multiple spaces might
have to be considered; as such the constraint you 
mention here below says there is no way today to 
device any mapping between these spaces, so if an lsp 
covers several as's and has to be diverse from n other 
lsp's, the "exclusion" mechanism would allow to ensure
1:n diversity on a "per common topological segment" 
basis but not an global end-to-end one; please correct 
me if i misunderstood the below statement

thanks,
- dimitri.

jls@research.att.com wrote:
> 
> Dimitri,
> Assuming a single inter-as srlg space would be folly at present. In 
> fact, even within a single carrier network it is more likely than not 
> that there isn't a single srlg space - for example, most large 
> carriers have acquired other carriers in the last few years, and I 
> would bet a large amount of money that they haven't integrated their 
> physical maps in the detail required if there is any significant 
> overlap.
> 
> John
> 
> -----Original Message-----
> From: Dimitri.Papadimitriou@alcatel.be 
> [mailto:Dimitri.Papadimitriou@alcatel.be]
> Sent: Tuesday, February 25, 2003 3:49 PM
> To: Ed Kern
> Cc: te-wg@ops.ietf.org
> Subject: Re: TE-operator call for presentations/input (multi-area)
> 
> ed,
> 
> i have a question directed to the user community
> on inter-as srlg diverse path, how can we ensure
> a single srlg id space exists ? i.e. even if the
> signalling allows for carrying an exclusion set
> (for inst. is as_1 uses set {1,2,3} and as_2 the
> set {4,5,6} the rro gives the set {2,5}, and the
> for the protecting lsp the he selects 1, how to
> be sure that 1 and 5 do not share a common risk,
> for inst. a common fiber cable ?)
> 
> thanks,
> - dimitri.
> 
> Ed Kern wrote:
> >
> >  We are starting to take the first steps in the direction of 
> > defining  requirements for multi-area TE.
> >
> >  This was not fully fleshed out in Network Hierarchy and Multilayer  
> > Survivability (RFC3386) for several reasons.  At the time, the  
> > chairs, AD's, design team and WG simply werent sure if this was  
> > necessary or that if there was enough operator need to properly 
> > scope  this work.
> >
> >  Currently on the list we have been discussing requirements in the  
> > context of draft-zhang-mpls-interas-te-req-01.txt.  Before we 
> > proceed  much further, the chairs would like to hear from operators 
> > who are:
> >
> >  1. *Currently* in need of a multi-area solution on a production  2. 
> > Currently deploying a version/flavor of multi-area TE.  3. Waiting 
> > on a standard/guidance before planning/deploying  4. Feel that these 
> > requirements should be scoped out regardless of
> >     current operational requirements.
> >
> >  This is not an attempt to rope you into assisting with the current  
> > draft but more a request to:
> >
> >  1. Present current protocol limitations/concerns at next ietf  2. 
> > Discuss them on the list here
> >
> >  We are specifically trying to target front-line engineering and  
> > operational efforts.  We understand that from an architectural  
> > perspective, having the path to multi-area and multi-as solutions  
> > is desirable.  However, we are uncertain how much of this is pulling  
> > up into *real* obstacles at this time.
> >
> > Ed & 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  : Work: +32 3 2408491 - Home: +32 2 3434361

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



