From owner-te-wg@ops.ietf.org  Thu Jul  1 09:26:35 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23602
	for <tewg-archive@lists.ietf.org>; Thu, 1 Jul 2004 09:26:35 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1Bg1Tt-0002rR-ND
	for te-wg-data@psg.com; Thu, 01 Jul 2004 13:20:01 +0000
Received: from [147.234.1.11] (helo=ilsmtp01.ecitele.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1Bg1Tp-0002qJ-Td
	for te-wg@ops.ietf.org; Thu, 01 Jul 2004 13:20:00 +0000
Subject: TE/CT Configuration scalability
To: te-wg@ops.ietf.org
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OFC06721A6.836256AF-ONC2256EC4.00445DD4@ecitele.com>
From: Lionel.Silman@ecitele.com
Date: Thu, 1 Jul 2004 15:38:06 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5|September 18, 2003) at
 07/01/2004 16:22:57
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.7 required=5.0 tests=BAYES_00,NO_REAL_NAME 
	autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk





draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for support of
Differentiated-Service-aware MPLS Traffic Engineering" states:-

"To ensure coherent DS-TE operation, the network administrator MUST
configure exactly the same TE-Class Mapping on all LSRs of the DS-TE
domain"

How does this idea of identical TE/CT configuration work over multiple
domains? Is there any possibility of interoperability?

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

Lionel Silman,  System, Optical Networks Division, ECI Telecom
Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464




From owner-te-wg@ops.ietf.org  Thu Jul  1 10:57:25 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA07365
	for <tewg-archive@lists.ietf.org>; Thu, 1 Jul 2004 10:57:24 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1Bg2yD-000BhY-0g
	for te-wg-data@psg.com; Thu, 01 Jul 2004 14:55:25 +0000
Received: from [68.71.231.98] (helo=fido.pdnets.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1Bg2yB-000Bh3-In
	for te-wg@ops.ietf.org; Thu, 01 Jul 2004 14:55:24 +0000
Received: from fido.pdnets.com (localhost [127.0.0.1])
	by fido.pdnets.com (8.12.8/8.12.5) with ESMTP id i61EtKN1018526;
	Thu, 1 Jul 2004 10:55:20 -0400
Received: from localhost (jboyle@localhost)
	by fido.pdnets.com (8.12.8/8.12.5/Submit) with ESMTP id i61EtK0H018522;
	Thu, 1 Jul 2004 10:55:20 -0400
X-Authentication-Warning: fido.pdnets.com: jboyle owned process doing -bs
Date: Thu, 1 Jul 2004 10:55:20 -0400 (EDT)
From: Jim Boyle <jboyle@pdnets.com>
X-X-Sender: jboyle@localhost
To: Lionel.Silman@ecitele.com
cc: te-wg@ops.ietf.org
Subject: Re: TE/CT Configuration scalability
In-Reply-To: <OFC06721A6.836256AF-ONC2256EC4.00445DD4@ecitele.com>
Message-ID: <Pine.LNX.4.44.0407011047510.18499-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-2.1 required=5.0 tests=BAYES_00,RCVD_IN_DYNABLOCK,
	RCVD_IN_RFCI,RCVD_IN_SORBS autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


See 
http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-07.txt

Section 5.1.7, this references section 4.1, of 

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

which doesn't exist.

Also

http://www.ietf.org/internet-drafts/draft-ietf-tewg-interarea-mpls-te-req-02.txt

Section 7.11

For interarea - I don't see a problem, as it's one administrative domain.

For interas - there may need to be use of diff-serv mpls signalling, or 
"careful" coordination between domains.

Jim

On Thu, 1 Jul 2004 Lionel.Silman@ecitele.com wrote:

> 
> 
> 
> 
> draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for support of
> Differentiated-Service-aware MPLS Traffic Engineering" states:-
> 
> "To ensure coherent DS-TE operation, the network administrator MUST
> configure exactly the same TE-Class Mapping on all LSRs of the DS-TE
> domain"
> 
> How does this idea of identical TE/CT configuration work over multiple
> domains? Is there any possibility of interoperability?
> 
> ----------------------------------------------------------------------------------------------------
> 
> Lionel Silman,  System, Optical Networks Division, ECI Telecom
> Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464
> 
> 

-- 




From owner-te-wg@ops.ietf.org  Thu Jul  1 13:28:48 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19447
	for <tewg-archive@lists.ietf.org>; Thu, 1 Jul 2004 13:28:47 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1Bg5Js-0001E3-4m
	for te-wg-data@psg.com; Thu, 01 Jul 2004 17:25:56 +0000
Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1Bg5Jr-0001Dp-2w
	for te-wg@ops.ietf.org; Thu, 01 Jul 2004 17:25:55 +0000
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id i61HPs969171;
	Thu, 1 Jul 2004 10:25:54 -0700 (PDT)
	(envelope-from ina@juniper.net)
Received: from garnet.juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i61HPnd26783;
	Thu, 1 Jul 2004 10:25:49 -0700 (PDT)
	(envelope-from ina@juniper.net)
Date: Thu, 1 Jul 2004 10:25:49 -0700 (PDT)
From: Ina Minei <ina@juniper.net>
To: Lionel.Silman@ecitele.com
cc: te-wg@ops.ietf.org
Subject: Re: TE/CT Configuration scalability
In-Reply-To: <OFC06721A6.836256AF-ONC2256EC4.00445DD4@ecitele.com>
Message-ID: <20040701100533.C59482@garnet.juniper.net>
References: <OFC06721A6.836256AF-ONC2256EC4.00445DD4@ecitele.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


	Lionel,

	I assume your question is "can I establish an inter-as diffserv-te
lsp given the requirement for uniform TE-class configuration" ? The answer
is yes.

	The reason for having a requirement for uniform TE-Class
configuration is because of the way IGP siganling is defined in the
te-proto draft. If instead of only advertising 8 values out of the 64
possible (ct, prio) combinations we would have advertised all 64, there
wouldn't have been the concept of TE-classes or the requirement to keep
them uniform.

	The only thing we get from the requirement is to be able to
consistently set up an LSP conforming to some SLAs within one domain. So
what happens when you cross to a different domain? All you need to do is
translate the LSP's SLAs to the necessary parameters in the new domain.

	There is no requirement to signal the TE-class matrix across
domains.

			Ina

On Thu, 1 Jul 2004 Lionel.Silman@ecitele.com wrote:

>
>
>
>
> draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for support of
> Differentiated-Service-aware MPLS Traffic Engineering" states:-
>
> "To ensure coherent DS-TE operation, the network administrator MUST
> configure exactly the same TE-Class Mapping on all LSRs of the DS-TE
> domain"
>
> How does this idea of identical TE/CT configuration work over multiple
> domains? Is there any possibility of interoperability?
>
> ----------------------------------------------------------------------------------------------------
>
> Lionel Silman,  System, Optical Networks Division, ECI Telecom
> Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464
>
>



From owner-te-wg@ops.ietf.org  Thu Jul  1 13:58:38 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21354
	for <tewg-archive@lists.ietf.org>; Thu, 1 Jul 2004 13:58:38 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1Bg5oj-00056b-F4
	for te-wg-data@psg.com; Thu, 01 Jul 2004 17:57:49 +0000
Received: from [204.127.202.64] (helo=sccrmhc13.comcast.net)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1Bg5oY-00054k-CM
	for te-wg@ops.ietf.org; Thu, 01 Jul 2004 17:57:38 +0000
Received: from [192.168.1.3] (c-24-5-4-40.client.comcast.net[24.5.4.40])
          by comcast.net (sccrmhc13) with SMTP
          id <2004070117573201600k6f9he>; Thu, 1 Jul 2004 17:57:37 +0000
In-Reply-To: <Pine.LNX.4.44.0407011047510.18499-100000@localhost>
References: <Pine.LNX.4.44.0407011047510.18499-100000@localhost>
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BD8A1786-CB88-11D8-BC93-000A95D1475E@tony.li>
Content-Transfer-Encoding: 7bit
Cc: Lionel.Silman@ecitele.com, te-wg@ops.ietf.org
From: Tony Li <tony.li@tony.li>
Subject: Re: TE/CT Configuration scalability
Date: Thu, 1 Jul 2004 11:01:56 -0700
To: Jim Boyle <jboyle@pdnets.com>
X-Mailer: Apple Mail (2.618)
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS 
	autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The other possibility is for someone to propose a "standard" mapping.   
For
anti-trust reasons, I don't believe that this would be best coming from  
a
non-carrier.  For IETF reasons, I believe that this would be best if it
was proposed as "one possible" mapping, not _THE DEFINITIVE SINGULAR_  
mapping.

Tony


On Jul 1, 2004, at 7:55 AM, Jim Boyle wrote:

>
> See
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te- 
> req-07.txt
>
> Section 5.1.7, this references section 4.1, of
>
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-proto 
> -07.txt
>
> which doesn't exist.
>
> Also
>
> http://www.ietf.org/internet-drafts/draft-ietf-tewg-interarea-mpls-te- 
> req-02.txt
>
> Section 7.11
>
> For interarea - I don't see a problem, as it's one administrative  
> domain.
>
> For interas - there may need to be use of diff-serv mpls signalling, or
> "careful" coordination between domains.
>
> Jim
>
> On Thu, 1 Jul 2004 Lionel.Silman@ecitele.com wrote:
>
>>
>>
>>
>>
>> draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for support of
>> Differentiated-Service-aware MPLS Traffic Engineering" states:-
>>
>> "To ensure coherent DS-TE operation, the network administrator MUST
>> configure exactly the same TE-Class Mapping on all LSRs of the DS-TE
>> domain"
>>
>> How does this idea of identical TE/CT configuration work over multiple
>> domains? Is there any possibility of interoperability?
>>
>> ---------------------------------------------------------------------- 
>> ------------------------------
>>
>> Lionel Silman,  System, Optical Networks Division, ECI Telecom
>> Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464
>>
>>
>
> -- 
>
>




From owner-te-wg@ops.ietf.org  Thu Jul  1 19:37:04 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08811
	for <tewg-archive@lists.ietf.org>; Thu, 1 Jul 2004 19:37:04 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BgB4V-000Jfn-EX
	for te-wg-data@psg.com; Thu, 01 Jul 2004 23:34:27 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BgB4U-000Jf7-De
	for te-wg@ops.ietf.org; Thu, 01 Jul 2004 23:34:26 +0000
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 01 Jul 2004 16:39:32 +0000
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i61NYNSc011501;
	Thu, 1 Jul 2004 16:34:23 -0700 (PDT)
Received: from [127.0.0.1] (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id QAA20800; Thu, 1 Jul 2004 16:34:22 -0700 (PDT)
Mime-Version: 1.0 (Apple Message framework v618)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2EBB4259-CBB7-11D8-B689-000A957B871E@tech.org>
Content-Transfer-Encoding: 7bit
Cc: Jean Philippe Vasseur <jvasseur@cisco.com>,
        LE Jean-Louis FTRD/DAC/LAN ROUX <jeanlouis.leroux@francetelecom.com>
From: Ed Kern <ejk@tech.org>
Subject: Last call status draft-ietf-tewg-interarea-mpls-te-req-01.txt
Date: Thu, 1 Jul 2004 16:34:23 -0700
To: te-wg@ops.ietf.org
X-Mailer: Apple Mail (2.618)
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-3.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DSBL,
	RCVD_IN_SORBS,RCVD_IN_SORBS_HTTP autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hi folks,

We delayed last call closure for a bit to give the authors time to  
incorporate comments into a new revision.

And here it is:

http://www.ietf.org/internet-drafts/draft-ietf-tewg-interarea-mpls-te- 
req-02.txt


The authors feel they have dealt with all last call comments in this  
draft.   Please read and comment  by July 12 otherwise we will advance  
the revision (with AD approval etc etc).

Thanks for your patience around the longer then expected last call and  
the quick turnaround time on this revision.

Ed




From owner-te-wg@ops.ietf.org  Fri Jul  2 04:45:15 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15575
	for <tewg-archive@lists.ietf.org>; Fri, 2 Jul 2004 04:45:14 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BgJbx-0000p6-3M
	for te-wg-data@psg.com; Fri, 02 Jul 2004 08:41:33 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BgJbv-0000nu-NH
	for te-wg@ops.ietf.org; Fri, 02 Jul 2004 08:41:31 +0000
Received: from ams-core-1.cisco.com (144.254.224.150)
  by ams-iport-1.cisco.com with ESMTP; 02 Jul 2004 10:59:26 +0200
X-BrightmailFiltered: true
Received: from xbe-lon-312.cisco.com (xbe-lon-312.cisco.com [64.103.99.72])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i628fEU9016694;
	Fri, 2 Jul 2004 10:41:26 +0200 (MEST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-312.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 2 Jul 2004 09:42:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6521.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: TE/CT Configuration scalability
Date: Fri, 2 Jul 2004 09:42:25 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D903A34EA2@xbe-lon-313.cisco.com>
Thread-Topic: TE/CT Configuration scalability
Thread-Index: AcRfe/CBN/QWeFMbQz2OajjP9bXQkwAk3dgg
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: "Jim Boyle" <jboyle@pdnets.com>, <Lionel.Silman@ecitele.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 02 Jul 2004 08:42:26.0124 (UTC) FILETIME=[804930C0:01C46010]
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi Jim,=20

>> See=20
>> http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-m
>> pls-te-req-07.txt
>>=20
>> Section 5.1.7, this references section 4.1, of=20
>>=20
>> http://www.ietf.org/internet-drafts/draft-ietf-tewg-diff-te-p
>> roto-07.txt
>>=20
>> which doesn't exist.

Hm... Yes, we have a little numbering glitch in diff-te-proto-07. But
the authors of interas-mpls-te-req-07 had read it right: section 4.1.1
should be numbered 4.1.

Specifically:

"4.1.1. Link Parameters"  should read "4.1.  Link Parameters"

"4.1.2. Bandwidth Constraints (BCs)" should read "4.1.1. Bandwidth
Constraints (BCs)"

"4.1.3. Overbooking" should read "4.1.2. Overbooking"

So again, the reference in interas-mpls-te-req-07 is correct and should
be kept as is, and we will correct diff-te-proto.

Thanks

Francois



From owner-te-wg@ops.ietf.org  Fri Jul  2 04:45:23 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15614
	for <tewg-archive@lists.ietf.org>; Fri, 2 Jul 2004 04:45:23 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BgJc5-0000px-CD
	for te-wg-data@psg.com; Fri, 02 Jul 2004 08:41:41 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BgJbw-0000nu-AO
	for te-wg@ops.ietf.org; Fri, 02 Jul 2004 08:41:32 +0000
Received: from ams-core-1.cisco.com (144.254.224.150)
  by ams-iport-1.cisco.com with ESMTP; 02 Jul 2004 10:59:26 +0200
X-BrightmailFiltered: true
Received: from xbe-lon-302.cisco.com (xbe-lon-302.cisco.com [64.103.98.21])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i628f7UJ016678;
	Fri, 2 Jul 2004 10:41:27 +0200 (MEST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Fri, 2 Jul 2004 09:42:26 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6521.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: TE/CT Configuration scalability
Date: Fri, 2 Jul 2004 09:42:25 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D903A34EA3@xbe-lon-313.cisco.com>
Thread-Topic: TE/CT Configuration scalability
Thread-Index: AcRfkpDkE0arD98HR/6iVhhWMHumSQAeznyA
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: "Ina Minei" <ina@juniper.net>, <Lionel.Silman@ecitele.com>
Cc: <te-wg@ops.ietf.org>, "FLF" <flefauch@cisco.com>
X-OriginalArrivalTime: 02 Jul 2004 08:42:26.0868 (UTC) FILETIME=[80BAB740:01C46010]
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hello,

Expanding on Ina's response.

The TE-Class Mapping need NOT be the same in different Autonomous
Systems which are span by a given inter-AS DS-TE LSP. It may be that AS1
supports 4 preemption priorities within its AS for CT1, while AS2 only
supports 2 preemption priorities within its AS for CT1.=20

Now, the two AS administrators certainly have to carefully agree on a
number of things before they can support inter-AS LSPs; like which CTs
they are allowed to use across ASes,  which preemption, how much maximum
bandwidth etc. But but this is how Diffserv works anyway independently
of DS-TE: for inter-AS Diffserv, operators have to agree on which
classes they want to share, which marking, what maximum rate for each,
and then configure mechansisms such as Traffic Conditioning accordingly.
DS-TE just fits in this existing Diffserv mode of operations.

Cheers

Francois

>> -----Original Message-----
>> From: owner-te-wg@ops.ietf.org=20
>> [mailto:owner-te-wg@ops.ietf.org] On Behalf Of Ina Minei
>> Sent: jeudi 1 juillet 2004 19:26
>> To: Lionel.Silman@ecitele.com
>> Cc: te-wg@ops.ietf.org
>> Subject: Re: TE/CT Configuration scalability
>>=20
>>=20
>> 	Lionel,
>>=20
>> 	I assume your question is "can I establish an inter-as=20
>> diffserv-te
>> lsp given the requirement for uniform TE-class=20
>> configuration" ? The answer
>> is yes.
>>=20
>> 	The reason for having a requirement for uniform TE-Class
>> configuration is because of the way IGP siganling is defined in the
>> te-proto draft. If instead of only advertising 8 values out of the 64
>> possible (ct, prio) combinations we would have advertised=20
>> all 64, there
>> wouldn't have been the concept of TE-classes or the=20
>> requirement to keep
>> them uniform.
>>=20
>> 	The only thing we get from the requirement is to be able to
>> consistently set up an LSP conforming to some SLAs within=20
>> one domain. So
>> what happens when you cross to a different domain? All you=20
>> need to do is
>> translate the LSP's SLAs to the necessary parameters in the=20
>> new domain.
>>=20
>> 	There is no requirement to signal the TE-class matrix across
>> domains.
>>=20
>> 			Ina
>>=20
>> On Thu, 1 Jul 2004 Lionel.Silman@ecitele.com wrote:
>>=20
>> >
>> >
>> >
>> >
>> > draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for=20
>> support of
>> > Differentiated-Service-aware MPLS Traffic Engineering" states:-
>> >
>> > "To ensure coherent DS-TE operation, the network administrator MUST
>> > configure exactly the same TE-Class Mapping on all LSRs of=20
>> the DS-TE
>> > domain"
>> >
>> > How does this idea of identical TE/CT configuration work=20
>> over multiple
>> > domains? Is there any possibility of interoperability?
>> >
>> >=20
>> -------------------------------------------------------------
>> ---------------------------------------
>> >
>> > Lionel Silman,  System, Optical Networks Division, ECI Telecom
>> > Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464
>> >
>> >
>>=20
>>=20



From owner-te-wg@ops.ietf.org  Sun Jul  4 04:33:07 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00732
	for <tewg-archive@lists.ietf.org>; Sun, 4 Jul 2004 04:33:06 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1Bh2MX-0008nw-Cu
	for te-wg-data@psg.com; Sun, 04 Jul 2004 08:28:37 +0000
Received: from [147.234.1.11] (helo=ilsmtp01.ecitele.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1Bh2MT-0008mt-E3
	for te-wg@ops.ietf.org; Sun, 04 Jul 2004 08:28:35 +0000
Subject: RE: TE/CT Configuration scalability
To: te-wg@ops.ietf.org,
        "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
Cc: ina@juniper.net
X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999
Message-ID: <OFACA1006E.F3081226-ONC2256EC7.002C8F68@ecitele.com>
From: Lionel.Silman@ecitele.com
Date: Sun, 4 Jul 2004 11:28:24 +0300
X-MIMETrack: Serialize by Router on ILSMTP01/ECI Telecom(Release 6.5|September 18, 2003) at
 07/04/2004 11:31:33
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.7 required=5.0 tests=BAYES_00,NO_REAL_NAME 
	autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk






As far as I can see there is a considerable difference bteween the inter-AS
Diffserv case and the inter-AS DS-TE case.

In Diffserv, the DIFFSERV TLV uses a standard PSC coding.  This promotes
the possibility of  agreement between the AS. They have to agree on the
PSC/Classes implemented and perhaps on policing, etc. There are no coding
issues.

In the DS-TE, there is no standard CLASSTYPE coding.  As Tony Li writes, a
"standard" mapping may be useful. But given that the idea of TE/CT is to
define a  limited number of combinations from a set prevalent alternatives,
this may be difficult.  In the absence of a standard mapping, it is
presumably necessary to have a mechanism to explicitly map between the
TE/CT codes of every AS pair.

Do you agree that this is required? if so, is it feasible?

Lionel Silman,  System, Optical Networks Division, ECI Telecom



                                                                                                        
                      "Francois Le                                                                      
                      Faucheur                 To:      "Ina Minei" <ina@juniper.net>,                  
                      \(flefauch\)"            <Lionel.Silman@ecitele.com>                              
                      <flefauch@cisco.         cc:      <te-wg@ops.ietf.org>, "FLF"                     
                      com>                     <flefauch@cisco.com>                                     
                                               Subject: RE: TE/CT Configuration scalability             
                      02/07/2004 11:42                                                                  
                                                                                                        
                                                                                                        



Hello,

Expanding on Ina's response.

The TE-Class Mapping need NOT be the same in different Autonomous
Systems which are span by a given inter-AS DS-TE LSP. It may be that AS1
supports 4 preemption priorities within its AS for CT1, while AS2 only
supports 2 preemption priorities within its AS for CT1.

Now, the two AS administrators certainly have to carefully agree on a
number of things before they can support inter-AS LSPs; like which CTs
they are allowed to use across ASes,  which preemption, how much maximum
bandwidth etc. But but this is how Diffserv works anyway independently
of DS-TE: for inter-AS Diffserv, operators have to agree on which
classes they want to share, which marking, what maximum rate for each,
and then configure mechansisms such as Traffic Conditioning accordingly.
DS-TE just fits in this existing Diffserv mode of operations.

Cheers

Francois

>> -----Original Message-----
>> From: owner-te-wg@ops.ietf.org
>> [mailto:owner-te-wg@ops.ietf.org] On Behalf Of Ina Minei
>> Sent: jeudi 1 juillet 2004 19:26
>> To: Lionel.Silman@ecitele.com
>> Cc: te-wg@ops.ietf.org
>> Subject: Re: TE/CT Configuration scalability
>>
>>
>>           Lionel,
>>
>>           I assume your question is "can I establish an inter-as
>> diffserv-te
>> lsp given the requirement for uniform TE-class
>> configuration" ? The answer
>> is yes.
>>
>>           The reason for having a requirement for uniform TE-Class
>> configuration is because of the way IGP siganling is defined in the
>> te-proto draft. If instead of only advertising 8 values out of the 64
>> possible (ct, prio) combinations we would have advertised
>> all 64, there
>> wouldn't have been the concept of TE-classes or the
>> requirement to keep
>> them uniform.
>>
>>           The only thing we get from the requirement is to be able to
>> consistently set up an LSP conforming to some SLAs within
>> one domain. So
>> what happens when you cross to a different domain? All you
>> need to do is
>> translate the LSP's SLAs to the necessary parameters in the
>> new domain.
>>
>>           There is no requirement to signal the TE-class matrix across
>> domains.
>>
>>                                   Ina
>>
>> On Thu, 1 Jul 2004 Lionel.Silman@ecitele.com wrote:
>>
>> >
>> >
>> >
>> >
>> > draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for
>> support of
>> > Differentiated-Service-aware MPLS Traffic Engineering" states:-
>> >
>> > "To ensure coherent DS-TE operation, the network administrator MUST
>> > configure exactly the same TE-Class Mapping on all LSRs of
>> the DS-TE
>> > domain"
>> >
>> > How does this idea of identical TE/CT configuration work
>> over multiple
>> > domains? Is there any possibility of interoperability?
>> >
>> >
>> -------------------------------------------------------------
>> ---------------------------------------
>> >
>> > Lionel Silman,  System, Optical Networks Division, ECI Telecom
>> > Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464
>> >
>> >
>>
>>






From owner-te-wg@ops.ietf.org  Mon Jul  5 03:05:48 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA11009
	for <tewg-archive@lists.ietf.org>; Mon, 5 Jul 2004 03:05:47 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BhNUZ-000K0d-6H
	for te-wg-data@psg.com; Mon, 05 Jul 2004 07:02:19 +0000
Received: from [144.254.224.140] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BhNUX-000K0G-K4
	for te-wg@ops.ietf.org; Mon, 05 Jul 2004 07:02:18 +0000
Received: from ams-core-1.cisco.com (144.254.224.150)
  by ams-iport-1.cisco.com with ESMTP; 05 Jul 2004 09:21:06 +0200
X-BrightmailFiltered: true
Received: from xbe-lon-302.cisco.com (xbe-lon-302.cisco.com [64.103.98.21])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i6572AU9007267;
	Mon, 5 Jul 2004 09:02:13 +0200 (MEST)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Mon, 5 Jul 2004 08:03:16 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.0.6521.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: TE/CT Configuration scalability
Date: Mon, 5 Jul 2004 08:03:15 +0100
Message-ID: <AC60B39EEE7320498063D37799FB82D903A34EBB@xbe-lon-313.cisco.com>
Thread-Topic: TE/CT Configuration scalability
Thread-Index: AcRhoRJGUqWbvHUpSEyDPgj8kP+uzAAuhtbw
From: "Francois Le Faucheur \(flefauch\)" <flefauch@cisco.com>
To: <Lionel.Silman@ecitele.com>, <te-wg@ops.ietf.org>
Cc: <ina@juniper.net>
X-OriginalArrivalTime: 05 Jul 2004 07:03:16.0221 (UTC) FILETIME=[251B4AD0:01C4625E]
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

>>=20
>> As far as I can see there is a considerable difference=20
>> bteween the inter-AS
>> Diffserv case and the inter-AS DS-TE case.
>>=20
>> In Diffserv, the DIFFSERV TLV uses a standard PSC coding. =20

Let's forget MPLS for a second. In non-MPLS IP Diffserv, there is no
signaling whatsoever across AS, with respect to Diffserv. Operators who
wish to offer inter-AS Diffserv just agree on a common set of classes,
markings, traffic contracts, QoS commitments, compensation,  ...=20

Currently there is no "recommended/standard" set of Diffserv classes. It
is up to each operator to decide what set of classes is optimum for
their environment, and this choice, along with corresponding QoS
commitments, is a strong differentiation factor.

If, in the future, operators feel that it is desirable to convergence on
a "recommended/standard" set of Diffserv classes and specify those, then
we could look at how to support that set of classes when TE/DS-TE
mechanisms are used. For now, I am not aware of the existence of such a
"recommended/standard" set. I am not even sure that there is convergence
among operators that it makes sense to specify that.

Francois

>> This promotes
>> the possibility of  agreement between the AS. They have to=20
>> agree on the
>> PSC/Classes implemented and perhaps on policing, etc. There=20
>> are no coding
>> issues.
>>=20
>> In the DS-TE, there is no standard CLASSTYPE coding.  As=20
>> Tony Li writes, a
>> "standard" mapping may be useful. But given that the idea of=20
>> TE/CT is to
>> define a  limited number of combinations from a set=20
>> prevalent alternatives,
>> this may be difficult.  In the absence of a standard mapping, it is
>> presumably necessary to have a mechanism to explicitly map=20
>> between the
>> TE/CT codes of every AS pair.
>>=20
>> Do you agree that this is required? if so, is it feasible?
>>=20
>> Lionel Silman,  System, Optical Networks Division, ECI Telecom
>>=20
>>=20
>>=20
>>                                                             =20
>>                                           =20
>>                       "Francois Le                          =20
>>                                           =20
>>                       Faucheur                 To:      "Ina=20
>> Minei" <ina@juniper.net>,                 =20
>>                       \(flefauch\)"           =20
>> <Lionel.Silman@ecitele.com>                             =20
>>                       <flefauch@cisco.         cc:     =20
>> <te-wg@ops.ietf.org>, "FLF"                    =20
>>                       com>                    =20
>> <flefauch@cisco.com>                                    =20
>>                                                Subject: RE:=20
>> TE/CT Configuration scalability            =20
>>                       02/07/2004 11:42                      =20
>>                                           =20
>>                                                             =20
>>                                           =20
>>                                                             =20
>>                                           =20
>>=20
>>=20
>>=20
>> Hello,
>>=20
>> Expanding on Ina's response.
>>=20
>> The TE-Class Mapping need NOT be the same in different Autonomous
>> Systems which are span by a given inter-AS DS-TE LSP. It may=20
>> be that AS1
>> supports 4 preemption priorities within its AS for CT1,=20
>> while AS2 only
>> supports 2 preemption priorities within its AS for CT1.
>>=20
>> Now, the two AS administrators certainly have to carefully agree on a
>> number of things before they can support inter-AS LSPs; like=20
>> which CTs
>> they are allowed to use across ASes,  which preemption, how=20
>> much maximum
>> bandwidth etc. But but this is how Diffserv works anyway=20
>> independently
>> of DS-TE: for inter-AS Diffserv, operators have to agree on which
>> classes they want to share, which marking, what maximum rate=20
>> for each,
>> and then configure mechansisms such as Traffic Conditioning=20
>> accordingly.
>> DS-TE just fits in this existing Diffserv mode of operations.
>>=20
>> Cheers
>>=20
>> Francois
>>=20
>> >> -----Original Message-----
>> >> From: owner-te-wg@ops.ietf.org
>> >> [mailto:owner-te-wg@ops.ietf.org] On Behalf Of Ina Minei
>> >> Sent: jeudi 1 juillet 2004 19:26
>> >> To: Lionel.Silman@ecitele.com
>> >> Cc: te-wg@ops.ietf.org
>> >> Subject: Re: TE/CT Configuration scalability
>> >>
>> >>
>> >>           Lionel,
>> >>
>> >>           I assume your question is "can I establish an inter-as
>> >> diffserv-te
>> >> lsp given the requirement for uniform TE-class
>> >> configuration" ? The answer
>> >> is yes.
>> >>
>> >>           The reason for having a requirement for uniform TE-Class
>> >> configuration is because of the way IGP siganling is=20
>> defined in the
>> >> te-proto draft. If instead of only advertising 8 values=20
>> out of the 64
>> >> possible (ct, prio) combinations we would have advertised
>> >> all 64, there
>> >> wouldn't have been the concept of TE-classes or the
>> >> requirement to keep
>> >> them uniform.
>> >>
>> >>           The only thing we get from the requirement is=20
>> to be able to
>> >> consistently set up an LSP conforming to some SLAs within
>> >> one domain. So
>> >> what happens when you cross to a different domain? All you
>> >> need to do is
>> >> translate the LSP's SLAs to the necessary parameters in the
>> >> new domain.
>> >>
>> >>           There is no requirement to signal the TE-class=20
>> matrix across
>> >> domains.
>> >>
>> >>                                   Ina
>> >>
>> >> On Thu, 1 Jul 2004 Lionel.Silman@ecitele.com wrote:
>> >>
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > draft-ietf-tewg-diff-te-proto-07, "Protocol extensions for
>> >> support of
>> >> > Differentiated-Service-aware MPLS Traffic Engineering" states:-
>> >> >
>> >> > "To ensure coherent DS-TE operation, the network=20
>> administrator MUST
>> >> > configure exactly the same TE-Class Mapping on all LSRs of
>> >> the DS-TE
>> >> > domain"
>> >> >
>> >> > How does this idea of identical TE/CT configuration work
>> >> over multiple
>> >> > domains? Is there any possibility of interoperability?
>> >> >
>> >> >
>> >> -------------------------------------------------------------
>> >> ---------------------------------------
>> >> >
>> >> > Lionel Silman,  System, Optical Networks Division, ECI Telecom
>> >> > Tel    Work: +972 (3) 9266007; Home: +972 (3) 6417464
>> >> >
>> >> >
>> >>
>> >>
>>=20
>>=20
>>=20
>>=20



From owner-te-wg@ops.ietf.org  Thu Jul  8 15:21:26 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21272
	for <tewg-archive@lists.ietf.org>; Thu, 8 Jul 2004 15:21:26 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BieNE-0008jg-A6
	for te-wg-data@psg.com; Thu, 08 Jul 2004 19:16:00 +0000
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BieN4-0008i1-4x; Thu, 08 Jul 2004 19:15:50 +0000
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id i68JFVBm011784;
	Thu, 8 Jul 2004 12:15:31 -0700 (PDT)
	(envelope-from arthi@juniper.net)
Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i68JFUd48386;
	Thu, 8 Jul 2004 12:15:31 -0700 (PDT)
	(envelope-from arthi@juniper.net)
Date: Thu, 8 Jul 2004 12:15:30 -0700 (PDT)
From: Arthi Ayyangar <arthi@juniper.net>
To: LE ROUX Jean-Louis FTRD/DAC/LAN <jeanlouis.leroux@francetelecom.com>
cc: v.sharma@ieee.org, TE <te-wg@ops.ietf.org>, CCAMP <ccamp@ops.ietf.org>
Subject: Re: RE : RE : RE : Last call comments: draft-ietf-tewg-interarea-mpls-te-req-01.txt
In-Reply-To: <D109C8C97C15294495117745780657AE2BA646@ftrdmel1.rd.francetelecom.fr>
Message-ID: <20040708115903.W20800@zircon.juniper.net>
References: <D109C8C97C15294495117745780657AE2BA646@ftrdmel1.rd.francetelecom.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=no 
	version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi JL,

Sorry for the delay in replying. Please see my answer below.

> And what about FRR: if I want FRR protection of ABRs with no impact on
> backup length and recovery delay, I definitely need contiguous LSPs.
> This is actually the only signaling mode allowing this service. Thus I
> prefer to signal directly the signaling mode "Contiguous LSP", rather
> than the required service, in order to avoid any misinterpretation of
> this service ...
----> I understand that you may want some control on the backup
path length. Even for intra-domain TE LSPs today, (which are contiguous),
depending on topology or constraints you may end up computing longer
paths than desired. So, in order to provide control on backup hops, one
probably specifies a constraint in backup path computation. Won't
specifying a similar constraint for inter-domain backup paths suffice ?
Ofcourse, the constraint may need to take into account forwarding hops
instead of control plane hops (aka RRO).

Also, I agree that with non-contiguous LSPs, you cannot merge back at
intermediate nodes between the FA-LSP or LSP segment end-points, that may
increase the number of forwarding nexthops for the backup. But, that is a
direct consequence of what any hierarchy does...information hiding.
However, even with contiguous LSPs, say for an inter-provider TE LSP
case, if the hops with the provider domain are not exposed via RRO (for
confidentiality reasons), you would still have the same issue. i.e.
you may need to merge back at the boundary node.

So, what I am trying to suggest is that these issues are not entirely tied
to a signaling method, (although there may be some which may be blatant with
one signaling method versus the other). So, instead of signaling the
method, we could solve the problem generically.

thanks,
-arthi



From owner-te-wg@ops.ietf.org  Sun Jul 18 19:30:43 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA11160
	for <tewg-archive@lists.ietf.org>; Sun, 18 Jul 2004 19:30:42 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BmKyq-0003Pf-SD
	for te-wg-data@psg.com; Sun, 18 Jul 2004 23:22:04 +0000
Received: from [66.163.168.185] (helo=smtp806.mail.sc5.yahoo.com)
	by psg.com with smtp (Exim 4.34 (FreeBSD))
	id 1BmKyp-0003PN-TF
	for te-wg@ops.ietf.org; Sun, 18 Jul 2004 23:22:04 +0000
Received: from unknown (HELO RAKHILAPTOP) (vishal.sharma@sbcglobal.net@63.206.90.49 with login)
  by smtp806.mail.sc5.yahoo.com with SMTP; 18 Jul 2004 23:22:03 -0000
Reply-To: <v.sharma@ieee.org>
From: "Vishal Sharma" <v.sharma@ieee.org>
To: <te-wg@ops.ietf.org>
Cc: "Monique J. Morrow" <mmorrow@cisco.com>,
        "Thomas Nadeau" <tnadeau@cisco.com>, "Loa Andersson" <loa@pi.se>
Subject: "Inter-Provider Service Quality on the Internet": IEEE Comm. Mag. CFP
Date: Sun, 18 Jul 2004 16:21:33 -0700
Message-ID: <MMECLKMDFPCEJFECIBCMIELBEKAA.v.sharma@ieee.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS 
	autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

The IEEE Communications Magazine has just approved the publication of
a Feature Topic issue on "Challenges in Enabling Inter-Provider
Service Quality on the Internet." The CFP is
attached below.

We invite those working in this area to consider sending in
their contributions. If you intend to submit a paper for this
special issue, please do drop one of the Guest Editors a
note, so that we can plan the issue.

We look forward to your participation!

Thanks,
-Vishal

****************************************************************
Vishal Sharma, Ph.D.
Metanoia, Inc.
Email: v.sharma@ieee.org.
http://www.metanoia-inc.com
****************************************************************

=========================================================================
CALL FOR PAPERS
IEEE Communications Magazine

Feature Topic on
"Challenges in Enabling Inter-Provider Service Quality on the Internet"
*************************************************************************

As carriers and service providers build multi-services networks based on
IP/MPLS-
enabled infrastructures that are able to meet evermore stringent service
level
agreements (SLAs) and quality-of-service (QoS) requirements, it becomes a
key
issue to extend the ability to deliver these services across carrier and
service
provider domain boundaries, while at the same time preserving the same SLAs
and
QoS assurances as those provided within a given provider's network.

The advent of new end-user applications, as well as new services based on
MPLS  technology, such as Layer 2 Virtual Private LAN Services (VPLS) and
Layer 3 Virtual  Private Networks (L3VPNs), also means the emergence of
added service quality
requirements from operators deploying and interoperating these networks and
the
end-users themselves. As a result, providers and vendors require efficient
means to
enable inter-provider service quality, which comprises of several key
elements
including quality of service, class of service, security, OAM, and
restoration and
repair.

This will is lead to the emergence of improved or novel tools and techniques
to address these aspects, with the goal of guaranteeing service quality
end-to-end,
improving security and billing/accounting, and reducing operating costs.
Standards
organizations such as the IETF and the ITU are taking on significant work in
this
area, and various aspects of this subject are also being investigated by
bodies such
as the OIF, the MSF, the MPLS/Frame Relay Alliance, the IEEE, and the Metro
Ethernet Forum, and are the themes for numerous upcoming conferences.

This feature topic issue of the IEEE Communications Magazine has a
multi-pronged
focus on the delivery of inter-provider service quality:

*	Highlight operator and end-user concerns and requirements.
*	Feature current and/or planned deployment experiences.
*	Survey modern research and engineering developments.
*	Spotlight contemporary standards activity.

Thus, focused tutorial and survey contributions as well as research papers
are
solicited on (but certainly not limited to) the following topics:

*	Carrier requirements for efficient inter-provider service quality: Current
        operational needs, bottlenecks, future demands
*	Deployment experience with inter-provider service quality on IP/MPLS-
         based networks: comparative analysis, case studies
*	QoS management in an inter-provider environment: interconnection
        architectures using MPLS, Diffserv, QoS performance, path
        characterization, routing policies
*	Service assurance in inter-provider infrastructures: End-to-end SLA
        management, service billing/reporting, admission control
*	Failure and restoration requirements/challenges in inter-provider contexts
*	Interoperability and inter-working of diverse equipment types and
        technologies (ATM, FR, Ethernet)
*	Current engineering and research developments: E.g. Passive and active
        performance measurement and monitoring, TE, modelling and simulation
*	Standards activities and initiatives: new services and network
architectures

On-line CFP with submission instructions can be found at:
http://www.metanoia-inc.com/IEEECommMag_InterProviderQoS_CFP.htm

Submission

Articles should be tutorial in nature and should be written in a style
comprehensible
to readers outside the specialty of the article. Articles may be edited for
clarity  and grammatical accuracy, and will be copyedited according to the
Magazine's style.
Mathematical equations should not be used (in justified cases up to three
simple
equations could be allowed, provided there is consent of the Guest Editor;
more than
three equations require permission from the Editor-in-Chief). Articles
should have no
more than 4,500 words, no more than 6 tables/figures, and no more than 15
references. Guidelines for prospective authors can be found on-line at
http://www.comsoc.org/pubs/commag/sub_guidelines.html.

** Please submit no later than 30 October 2004.**
Accepted papers will also be included in Communications
Interactive (CI), the online version of Communications Magazine.


Manuscript Due:                                          30 October 2004
Acceptance Notification:                                 15 January  2004
Final Manuscript Due:                                    28 February 2005
Publication Date:                                        June  2005

Guest Editors

Monique J. Morrow, Cisco Systems, (mmorrow@cisco.com)
Vishal Sharma, Metanoia, Inc. (v.sharma@ieee.org)
Thomas D.Nadeau, Cisco Systems (tnadeau@cisco.com)
Loa Andersson, Acreo (loa@pi.se)





From owner-te-wg@ops.ietf.org  Mon Jul 19 01:42:05 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA00476
	for <tewg-archive@lists.ietf.org>; Mon, 19 Jul 2004 01:42:05 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BmQo9-0000hi-Br
	for te-wg-data@psg.com; Mon, 19 Jul 2004 05:35:25 +0000
Received: from [192.11.226.163] (helo=hoemail2.lucent.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BmQo8-0000h5-4k
	for te-wg@ops.ietf.org; Mon, 19 Jul 2004 05:35:24 +0000
Received: from ci0026keqinli.org (h135-252-6-200.lucent.com [135.252.6.200])
	by hoemail2.lucent.com (8.12.11/8.12.11) with SMTP id i6J5ZJ5o027363
	for <te-wg@ops.ietf.org>; Mon, 19 Jul 2004 00:35:20 -0500 (CDT)
Date: Mon, 19 Jul 2004 13:35:03 +0800
To: "Te-wg" <te-wg@ops.ietf.org>
From: "Fiffi" <Fiffi@nortelnetworks.com>
Subject: Re:
Message-ID: <kapuqxclmiussbqkuzj@ops.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------svbaqlxzhbywyabkmhek"
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=0.1 required=5.0 tests=BAYES_20,HTML_IMAGE_ONLY_06,
	HTML_MESSAGE autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

----------svbaqlxzhbywyabkmhek
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on the network)

Found virus WORM_BAGLE.GEN-1 in file foto3.zip
The file foto3.zip can not be moved because /var/quarantine/virus/virXSUlnVUjW: No space left on device.

This is a machine-generated message, please do not reply via e-mail. If you have questions, please contact the Lucent Help Desk at +1 888 300 0770.

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

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

<html><body>
The snake<br><br>


<br>Password:  <img src="cid:unhzlbhwaj.bmp"><br>
<br>
</body></html>

----------svbaqlxzhbywyabkmhek
Content-Type: image/bmp; name="unhzlbhwaj.bmp"
Content-Disposition: attachment; filename="unhzlbhwaj.bmp"
Content-ID: <unhzlbhwaj.bmp>
Content-Transfer-Encoding: base64

Qk3GBgAAAAAAADYAAAAoAAAANwAAAA8AAAABABAAAAAAAJAGAAAAAAAAAAAAAAAAAAAAAAAA
/3//f/9//3//f/9//3//f/9//3+AfIB8gHyAfIB8gHyAfIB8gHyAfIB8gHyAfIB8gHyAfIB8
gHyAfIB8gHyAfIB8gHyAfIB8gHyAfIB8gHyAfIB8gHyAfIB8/3//f/9//3//f/9//3//f/9/
/38AAP9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
/3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
/3//f/9/AAD/f/9//3//f/9//3//f/9//3//f/9//3+TfoB87X1af/9//3//f5N+gHztfVp/
/3//f/9//3+JfYB83n//f/9//3//f4l9gHzef/9//39af4l9gHyTfv9//3//f/9//3//f/9/
/3//f/9//3//fwAA/3//f/9//3//f/9//3//f/9//3//f9R+gHycfxd/gHycf/9/1H6AfJx/
F3+AfJx//3//f/9/cX6AfJx//3//f/9//39xfoB8nH//f/9/7X2AfN5/7X1xfv9//3//f/9/
/3//f/9//3//f/9//38AAP9//3//f/9//3//f/9//3//f/9//3+JfYB8/3/ef4B8k37/f4l9
gHz/f95/gHyTfv9//3//f/Z+gHwXf/9//3//f/9/9n6AfBd//3//f/9//3//f9R+gHx7f/9/
/3//f/9//3//f/9//3//f/9/AAD/f/9//3//f/9//3//f/9//3//f/9/gHyAfP9//3+AfIB8
/3+AfIB8/3//f4B8gHz/f/9//39af4B81H7/f/9//3//f1p/gHzUfv9//3+9fy9+iX3UfoB8
1H7/f/9//3//f/9//3//f/9//3//fwAA/3//f/9//3//f/9//3//f/9//3//f4B8gHx7f/9/
gHyAfP9/gHyAfHt//3+AfIB8/3//f/9/nH+AfC9+/3//f/9//3+cf4B8L37/f/9/k36AfJx/
F3+AfO19/3//f/9//3//f/9//3//f/9//38AAP9//3//f/9//3//f/9//3//f/9//3/tfYB8
cX6cf4B8k37/f+19gHxxfpx/gHyTfv9//3//f/9/gHyAfP9//3//f/9//3+AfIB8/3//f4B8
gHz/f71/gHyAfP9//3//f/9//3//f/9//3//f/9/AAD/f/9//3//f/9//3//f/9//3//f/9/
1H6AfJN+iX1xft5//3/UfoB8k36JfXF+3n//f/9/nH//f+19gHy9f/9//3+cf/9/7X2AfL1/
/3+AfIB8/3//f4B8gHz/f/9//3//f/9//3//f/9//3//fwAA/3//f/9//3//f/9//3//f/9/
/3//f3t/gHwXf/9//3//f/9/e3+AfBd//3//f/9//3//f4B8gHyJfYB8e3//f/9/gHyAfIl9
gHx7f/9/L36AfN5//3+AfO19/3//f/9//3//f/9//3//f/9//38AAP9//3//f/9//3//f/9/
/3//f/9//3//f3F+7X3ef4B87X3/f/9/cX7tfd5/gHztff9//3+9f/Z+iX2AfBd//3//f71/
9n6JfYB8F3//f3t/gHwXf5x/gHzUfv9//3//f/9//3//f/9//3//f/9/AAD/f/9//3//f/9/
/3//f/9//3//f/9//3//f5N+gHyJfVp//3//f/9/k36AfIl9Wn//f/9//3//f/9/k35xfv9/
/3//f/9//3+TfnF+/3//f1p/7X2AfHF+/3//f/9//3//f/9//3//f/9//3//fwAA/3//f/9/
/3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
/3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//38AAP9/
/3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
/3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
AAD/f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
/3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9//3//f/9/
/3//fwAA

----------svbaqlxzhbywyabkmhek
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on the network)

foto3.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------svbaqlxzhbywyabkmhek--




From owner-te-wg@ops.ietf.org  Mon Jul 19 02:30:46 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA17157
	for <tewg-archive@lists.ietf.org>; Mon, 19 Jul 2004 02:30:45 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1BmRdD-0006z1-7d
	for te-wg-data@psg.com; Mon, 19 Jul 2004 06:28:11 +0000
Received: from [192.11.226.161] (helo=hoemail1.lucent.com)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1BmRdC-0006yf-8X
	for te-wg@ops.ietf.org; Mon, 19 Jul 2004 06:28:10 +0000
Received: from ci0026keqinli.com (h135-252-6-200.lucent.com [135.252.6.200])
	by hoemail1.lucent.com (8.12.11/8.12.11) with SMTP id i6J6S58L011715
	for <te-wg@ops.ietf.org>; Mon, 19 Jul 2004 01:28:06 -0500 (CDT)
Date: Mon, 19 Jul 2004 14:27:49 +0800
To: "Te-wg" <te-wg@ops.ietf.org>
From: "Fiffi" <Fiffi@nortelnetworks.com>
Subject: Re:
Message-ID: <fwytffjrjycasxpwhgi@ops.ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------wmmluztnybqwopcrctim"
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE 
	autolearn=ham version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

----------wmmluztnybqwopcrctim
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on the network)

Found virus WORM_BAGLE.AG in file Cat.scr
The file Cat.scr can not be moved because /var/quarantine/virus/virYBRP9FxMt: No space left on device.

This is a machine-generated message, please do not reply via e-mail. If you have questions, please contact the Lucent Help Desk at +1 888 300 0770.

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

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

<html><body>
Predators<br><br>

<br>
</body></html>

----------wmmluztnybqwopcrctim
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on the network)

Cat.scr is removed from here because it contains a virus.

---------------------------------------------------------
----------wmmluztnybqwopcrctim--




From owner-te-wg@ops.ietf.org  Fri Jul 23 17:10:32 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27534
	for <tewg-archive@lists.ietf.org>; Fri, 23 Jul 2004 17:10:31 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.34 (FreeBSD))
	id 1Bo7DS-000DR3-Gm
	for te-wg-data@psg.com; Fri, 23 Jul 2004 21:04:30 +0000
Received: from [80.168.70.141] (helo=relay1.mail.uk.clara.net)
	by psg.com with esmtp (Exim 4.34 (FreeBSD))
	id 1Bo7DR-000DQc-5i; Fri, 23 Jul 2004 21:04:29 +0000
Received: from du-069-0204.access.clara.net ([217.158.132.204] helo=Puppy)
	by relay1.mail.uk.clara.net with smtp (Exim 4.34)
	id 1Bo7DP-0004cF-4A; Fri, 23 Jul 2004 22:04:28 +0100
Message-ID: <0c5e01c470f8$a5cde130$45849ed9@Puppy>
Reply-To: "Adrian Farrel" <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ccamp@ops.ietf.org>, <mpls@ietf.org>, "TEWG" <te-wg@ops.ietf.org>,
        <rtgwg@ietf.org>
Cc: "'Jean Philippe Vasseur'" <jvasseur@cisco.com>
Subject: Path Computation Element BOF
Date: Fri, 23 Jul 2004 21:52:48 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_SORBS 
	autolearn=no version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Just a reminder that a PCE BOF will be held at San Diego in the Wednesday 9am slot.

See below for a summary of the objectives.

You might also like to look at a problem statement draft...
http://www.ietf.org/internet-drafts/draft-ash-pce-problem-statement-00.txt

Cheers,
Adrian
===

Path Computation Element BOF (PCE BOF)
60th IETF, San Diego, August 2004

Routing Area Ads: Alex Zinin (zinin@psg.com),
                  Bill Fenner (fenner@research.att.com)

BOF Chairs: JP Vasseur (jvasseur@cisco.com), 
            Adrian Farrel (adrian@olddog.co.uk)

Description:
In certain MPLS TE networks it may be beneficial or desirable to have path 
computation performed by a distinct node (termed the Path Computation 
Element  PCE) that is not the LSR that needs to know the path. This BOF 
 examines the scope of such function, what extensions to existing protocols 
 might required, what additional protocols may need to be developed, and 
 whether there is cuase and support for this work within the IETF.
 
 
 Proposed WG Charter
 
 Organizational Overview
The PCE working group coordinates the work within the IETF of defining the 
 operation of path computation elements within the Internet. Path 
 computation elements are responsible for computing paths through IP 
 networks for uses such as traffic engineering so that a prime consumer of 
 such paths might be an MPLS-TE LSR. Areas of responsibility will include 
 the collection of attributes relevant to the computation of paths, the 
 discovery by LSRs of available path computation elements, the communication 
 with LSRs for the request of path computation, the collaboration between 
 path computation elements within the network, and analysis of path 
 computation algorithms with a view to ensuring consistency between computed 
 paths. The working group will work closely with many working groups in the 
 Routing Area including the OSPF, IS-IS, IDR, MPLS and CCAMP working groups.
 
 Working Group Scope
The PCE working group scope includes:
- Definition  of Generalized Traffic Engineered LSP paths computation 
  techniques involving Path Computation Element(s). This includes the intra 
  IGP area, inter IGP area, inter-AS and inter-provider TE LSPs path 
  computation for Point-to-Point, Point-to-Multipoint and 
  Multipoint-to-Multipoint TE LSPs.
- Definition of protocol-independent metrics and constraints defining path 
  quality measurement criteria, algorithm complexity and scalability criteria 
  related to path computation techniques.
- Definition of requirements for communication between LSRs and PCEs  
  including routing extensions in support of PCE discovery techniques within 
  an IGP area and across multiple IGP areas, ASes and Provider networks, and 
  including the development of new protocols or protocol extensions for 
  requesting path computation and supplying responses. Any protocol 
  extensions will developed in conjunction with the working groups in charge 
  of the specific protocols.
- Specification of routing (OSPF, ISIS, BGP) and signalling extensions 
  (RSVP-TE) required by PCE-based path computation techniques. The extensions 
  will developed in conjunction with the working groups in charge of the 
  specific protocols.
- Specification of requirements and protocol extensions related to the 
  policy, security and confidentiality aspects of PCE-based path computation 
  techniques involving PCEs of multiple Providers.
- Definition of MIBs, management procedures related to the protocol 
  extensions defined by the WG
 
In doing this work, the WG will closely work with at least the following 
other WGs: CCAMP, MPLS, ISIS, OSPF, IDR. The WG will also cooperate with 
the ITU-T  and OIF.
 
 Goals and Milestones
 
Dates for milestones to be decided later.
- Post strawman WG goals and charter.
- Submit WG document defining the framework and applicability of the 
  PCE model.
- Select a single candidate protocol from communication between LSRs 
  and PCEs.
- Submit document(s) that define various path computation models
- Submit an analysis document examining the requirements for coherent
  computation techniques and the implication of cooperation between 
  PCEs.
- Submit a document defining the protocol for communication between 
  LSRs and PCEs.
- Submit document(s) defining extensions to routing and signalling 
  protocols necessary to support the use of a PCE model within MPLS
  networks.
- Submit a document defining MIB modules for modeling and management 
  of PCE systems.



From owner-te-wg@ops.ietf.org  Tue Jul 27 05:49:03 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01265
	for <tewg-archive@lists.ietf.org>; Tue, 27 Jul 2004 05:49:02 -0400 (EDT)
Received: from majordom by psg.com with local (Exim 4.41 (FreeBSD))
	id 1BpOTo-000Kay-Vi
	for te-wg-data@psg.com; Tue, 27 Jul 2004 09:42:40 +0000
Received: from [80.168.70.142] (helo=relay2.mail.uk.clara.net)
	by psg.com with esmtp (Exim 4.41 (FreeBSD))
	id 1BpOTo-000KaS-0t; Tue, 27 Jul 2004 09:42:40 +0000
Received: from du-027-0014.claranet.co.uk ([195.8.81.14] helo=Puppy)
	by relay2.mail.uk.clara.net with smtp (Exim 4.34)
	id 1BpOTm-000LN3-Au; Tue, 27 Jul 2004 10:42:39 +0100
Message-ID: <004c01c473be$0e9f5500$455708c3@Puppy>
Reply-To: "Adrian Farrel" <adrian@olddog.co.uk>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ccamp@ops.ietf.org>, <mpls@ietf.org>, "TEWG" <te-wg@ops.ietf.org>
Subject: PCE BOF date/time
Date: Tue, 27 Jul 2004 10:17:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psg.com
X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham 
	version=2.63
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

Apologies for the confusion about the date and time of this BOF.

The latest version of the agenda appears to have moved it to 

THURSDAY, August 5, 2004
1300-1500 Afternoon Sessions I
RTG   pce       Path Computation Element BOF

No idea whether this is final.

Adrian



