From owner-te-wg@ops.ietf.org  Fri Jan  9 13:13: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 NAA20132
	for <tewg-archive@lists.ietf.org>; Fri, 9 Jan 2004 13:13:05 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Af12u-0007QY-MV
	for te-wg-data@psg.com; Fri, 09 Jan 2004 18:07:44 +0000
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Af12g-0007Oe-TF
	for te-wg@ops.ietf.org; Fri, 09 Jan 2004 18:07:30 +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 i09I7QBm084608;
	Fri, 9 Jan 2004 10:07:26 -0800 (PST)
	(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 i09I7Qh50702;
	Fri, 9 Jan 2004 10:07:26 -0800 (PST)
	(envelope-from ina@juniper.net)
Date: Fri, 9 Jan 2004 10:07:26 -0800 (PST)
From: Ina Minei <ina@juniper.net>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Tewg (E-mail)" <te-wg@ops.ietf.org>
Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B155033D3A15@nl0006exch001u.nl.lucent.com>
Message-ID: <20040109095525.G62398@garnet.juniper.net>
References: <7D5D48D2CAA3D84C813F5B154F43B155033D3A15@nl0006exch001u.nl.lucent.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


	Bert,

	Nobody else seems to care about this issue, or at least they are
not expressing an opinion on the list, so this is why I was carrying on
this email thread. I personally would like to see the issue closed and
the draft moved forward.

	This issue is not such a big one, so let's not spend too much
time on it. So far there are two proposals: 3 numbers or 32 numbers.
I have explained why I think 3 is not enough, and you have explained why
you think 32 is too much.

	Let's propose 16 and put it to vote on the list and be done with
it. Perhaps the WG chairs can help with this?

			Ina

On Fri, 9 Jan 2004, Wijnen, Bert (Bert) wrote:

> Not sure why some people think (or that is how I
> perceive your last email) that an AD has any more weight than
> other WG members. I have made my opinion clear that I think
> that 32 is far too much.
>
> I have asked WG chairs to check this also.
>
> It is best if WG chairs take initiative to drive resolution of
> these questions.
>
> Thanks,
> Bert
>
> > -----Original Message-----
> > From: Ina Minei [mailto:ina@juniper.net]
> > Sent: vrijdag 9 januari 2004 1:19
> > To: Wijnen, Bert (Bert)
> > Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
> > Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
> >
> >
> >
> > 	Bert,
> >
> > 	So can we just agree on 32 "experimental/vendor private"
> > numbers starting at 255 and down?
> >
> > 			Thank you,
> >
> > 				Ina
> >
> > On Mon, 29 Dec 2003, Ina Minei wrote:
> >
> > >
> > >
> > > 	Bert,
> > >
> > > 	I think we both agree :). and in the end it all boils down to
> > > experimental vs vendor-private. What I am thinking of
> > > is vendor-private numbers, and what you are thinking of is
> > experimental.
> > > We are both right. How we decide to solve it is a different issue.
> > >
> > > 	We can  either: 1) allocate two spaces, one for experimental and
> > > one for vendor-private. In that case, 3 should be enough
> > for experimental,
> > > but as  for vendor-private more than 3 would be required,
> > for the reason I
> > > was  mentioning in the original mail or 2) allocate one
> > bigger space for
> > > both experimental and vendor-private. I prefer (2).
> > >
> > > 	Let's just pick one of the options, and carry it forward. Let me
> > > know what you prefer.
> > >
> > > 			Ina
> > >
> >
>



From owner-te-wg@ops.ietf.org  Sun Jan 11 18:04:34 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20296
	for <tewg-archive@lists.ietf.org>; Sun, 11 Jan 2004 18:04:34 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1AfoWn-000Pst-8I
	for te-wg-data@psg.com; Sun, 11 Jan 2004 22:57:53 +0000
Received: from [192.11.223.163] (helo=auemail2.firewall.lucent.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AfoWZ-000PaG-EQ
	for te-wg@ops.ietf.org; Sun, 11 Jan 2004 22:57:39 +0000
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail2.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id i0BMwBi10595
	for <te-wg@ops.ietf.org>; Sun, 11 Jan 2004 16:58:25 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72)
	id <ZPPAGMZ5>; Sun, 11 Jan 2004 23:36:17 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155033D3C7A@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Ina Minei <ina@juniper.net>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Tewg (E-mail)"
	 <te-wg@ops.ietf.org>
Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
Date: Sun, 11 Jan 2004 23:36:15 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Some people who want to form an opinion on the size of
experimental/vendor-private name-space may find it
useful to check draft-narten-iana-experimental-allocations-05.txt
and specificall ysect 1.1. It is only a few pages...

Thanks,
Bert 

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: vrijdag 9 januari 2004 12:10
> To: Ina Minei; Wijnen, Bert (Bert)
> Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
> Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
> 
> 
> Not sure why some people think (or that is how I 
> perceive your last email) that an AD has any more weight than
> other WG members. I have made my opinion clear that I think
> that 32 is far too much.
> 
> I have asked WG chairs to check this also.
> 
> It is best if WG chairs take initiative to drive resolution of
> these questions.
> 
> Thanks,
> Bert 
> 
> > -----Original Message-----
> > From: Ina Minei [mailto:ina@juniper.net]
> > Sent: vrijdag 9 januari 2004 1:19
> > To: Wijnen, Bert (Bert)
> > Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
> > Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
> > 
> > 
> > 
> > 	Bert,
> > 
> > 	So can we just agree on 32 "experimental/vendor private"
> > numbers starting at 255 and down?
> > 
> > 			Thank you,
> > 
> > 				Ina
> > 
> > On Mon, 29 Dec 2003, Ina Minei wrote:
> > 
> > >
> > >
> > > 	Bert,
> > >
> > > 	I think we both agree :). and in the end it all boils down to
> > > experimental vs vendor-private. What I am thinking of
> > > is vendor-private numbers, and what you are thinking of is 
> > experimental.
> > > We are both right. How we decide to solve it is a different issue.
> > >
> > > 	We can  either: 1) allocate two spaces, one for experimental and
> > > one for vendor-private. In that case, 3 should be enough 
> > for experimental,
> > > but as  for vendor-private more than 3 would be required, 
> > for the reason I
> > > was  mentioning in the original mail or 2) allocate one 
> > bigger space for
> > > both experimental and vendor-private. I prefer (2).
> > >
> > > 	Let's just pick one of the options, and carry it forward. Let me
> > > know what you prefer.
> > >
> > > 			Ina
> > >
> > 
> 



From owner-te-wg@ops.ietf.org  Mon Jan 12 06:05:57 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21876
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 06:05:57 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Afzoz-00099d-EQ
	for te-wg-data@psg.com; Mon, 12 Jan 2004 11:01:25 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Afzol-0008rJ-9T
	for te-wg@ops.ietf.org; Mon, 12 Jan 2004 11:01:11 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 12 Jan 2004 12:01:57 +0100
Received: from xbe-lon-302.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id i0CB0opi023452;
	Mon, 12 Jan 2004 12:00:50 +0100 (MET)
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, 12 Jan 2004 11:01:08 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
Date: Mon, 12 Jan 2004 11:01:07 -0000
Message-ID: <AC60B39EEE7320498063D37799FB82D902213CF2@xbe-lon-313.cisco.com>
Thread-Topic: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
Thread-Index: AcPW3FNm/pkwU2grQbCj2oEzbC9hywCHNDPg
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Tewg (E-mail)" <te-wg@ops.ietf.org>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Ina Minei" <ina@juniper.net>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
X-OriginalArrivalTime: 12 Jan 2004 11:01:08.0786 (UTC) FILETIME=[61EDA120:01C3D8FB]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hello,

I think a BC Model ID space of 256 is comfortable and provides more than
enough codepoints. I also feel this is not a big issue and we just need
someone, like our chairs, to pick a size for the experimental/vendor
space. Any value among { 4, 8, 16, 32 } works for me.=20
I'll put that number in the next rev as soon as I hear a conclusion from
the chairs.=20

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: vendredi 9 janvier 2004 19:07
>> To: Wijnen, Bert (Bert)
>> Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
>> Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
>>=20
>>=20
>>=20
>> 	Bert,
>>=20
>> 	Nobody else seems to care about this issue, or at least they are
>> not expressing an opinion on the list, so this is why I was=20
>> carrying on
>> this email thread. I personally would like to see the issue=20
>> closed and
>> the draft moved forward.
>>=20
>> 	This issue is not such a big one, so let's not spend too much
>> time on it. So far there are two proposals: 3 numbers or 32 numbers.
>> I have explained why I think 3 is not enough, and you have=20
>> explained why
>> you think 32 is too much.
>>=20
>> 	Let's propose 16 and put it to vote on the list and be done with
>> it. Perhaps the WG chairs can help with this?
>>=20
>> 			Ina
>>=20
>> On Fri, 9 Jan 2004, Wijnen, Bert (Bert) wrote:
>>=20
>> > Not sure why some people think (or that is how I
>> > perceive your last email) that an AD has any more weight than
>> > other WG members. I have made my opinion clear that I think
>> > that 32 is far too much.
>> >
>> > I have asked WG chairs to check this also.
>> >
>> > It is best if WG chairs take initiative to drive resolution of
>> > these questions.
>> >
>> > Thanks,
>> > Bert
>> >
>> > > -----Original Message-----
>> > > From: Ina Minei [mailto:ina@juniper.net]
>> > > Sent: vrijdag 9 januari 2004 1:19
>> > > To: Wijnen, Bert (Bert)
>> > > Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
>> > > Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
>> > >
>> > >
>> > >
>> > > 	Bert,
>> > >
>> > > 	So can we just agree on 32 "experimental/vendor private"
>> > > numbers starting at 255 and down?
>> > >
>> > > 			Thank you,
>> > >
>> > > 				Ina
>> > >
>> > > On Mon, 29 Dec 2003, Ina Minei wrote:
>> > >
>> > > >
>> > > >
>> > > > 	Bert,
>> > > >
>> > > > 	I think we both agree :). and in the end it all=20
>> boils down to
>> > > > experimental vs vendor-private. What I am thinking of
>> > > > is vendor-private numbers, and what you are thinking of is
>> > > experimental.
>> > > > We are both right. How we decide to solve it is a=20
>> different issue.
>> > > >
>> > > > 	We can  either: 1) allocate two spaces, one for=20
>> experimental and
>> > > > one for vendor-private. In that case, 3 should be enough
>> > > for experimental,
>> > > > but as  for vendor-private more than 3 would be required,
>> > > for the reason I
>> > > > was  mentioning in the original mail or 2) allocate one
>> > > bigger space for
>> > > > both experimental and vendor-private. I prefer (2).
>> > > >
>> > > > 	Let's just pick one of the options, and carry=20
>> it forward. Let me
>> > > > know what you prefer.
>> > > >
>> > > > 			Ina
>> > > >
>> > >
>> >
>>=20
>>=20



From owner-te-wg@ops.ietf.org  Mon Jan 12 11:34: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 LAA04633
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 11:34:06 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Ag4wP-000FhV-2Z
	for te-wg-data@psg.com; Mon, 12 Jan 2004 16:29:25 +0000
Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ag4w2-000FDV-TW
	for te-wg@ops.ietf.org; Mon, 12 Jan 2004 16:29:02 +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 i0CGT2l23131;
	Mon, 12 Jan 2004 08:29:02 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0CGSuh97495;
	Mon, 12 Jan 2004 08:28:56 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401121628.i0CGSuh97495@merlot.juniper.net>
To: raymond zhang <zhangr@info.net>
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen,
    Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-03.txt 
In-Reply-To: Your message of "Thu, 08 Jan 2004 09:47:28 PST."
             <5.2.0.9.2.20040108093904.02a52ba0@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <21500.1073924936.1@juniper.net>
Date: Mon, 12 Jan 2004 08:28:56 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

> Hi Jim and Ed,
> 
> Happy new year !
> 
> The following emails were sent to both of you nearly a month ago.  I am not 
> sure if you are having problem receiving email again so I am copying Bert 
> and posting to the list also.
> 
> The -03 version of the draft 
> (http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-03.t
xt) 
> is ready for last call as per our minutes from the Minneapolis meeting.

I think that the latest version of the draft still require few
changes/updates.

1. The document should state up front the following:

      This document doesn't make any claims with respect to whether
      it is possible to have a practical solution that meets all the
      requirements listed in this document.

(That point have been discussed before, and I thought the authors
agreed to include the above in the text, but I wasn't able to find
it in the -03 version).

2. From 5.1.5 ("Re-optimization"):

   Once an inter-AS TE LSP has been established and should there be any
   resource or other changes inside anyone of transiting ASes, the
   solution MUST be able to re-optimize the LSP accordingly and
   non-disruptively, either upon expiration of a configurable timer or
   triggered by a network event or a manual request at the TE tunnel
   Head-end.

   The solution SHOULD provide an option for the Head-End LSRs to
   control if re-optimizing or not should there exist a more optimal
   path in one of the transit ASes along the inter-AS TE LSP path.

The above it too restrictive, as it restricts re-optimization to
only the case where resource changes are in the set of ASs (currently)
transited by the LSP. To remove this restriction I'd like to propose the
following replacement:

   Once an inter-AS TE LSP has been established and should there be any
   resource or other changes inside anyone of the ASes, the
   solution MUST be able to re-optimize the LSP accordingly and
   non-disruptively, either upon expiration of a configurable timer or
   triggered by a network event or a manual request at the TE tunnel
   Head-end.

   The solution SHOULD provide an option for the Head-End LSRs to
   control if re-optimizing or not should there exist a more optimal
   path in one of the ASes.

3. Section 6.2 ("Performance") should include control plane overhead
as one of the criteria. Ditto for data plane overhead.

4. In 5.1.6 replace "CSPF" with "Path computation").

Yakov.



From owner-te-wg@ops.ietf.org  Mon Jan 12 12:37: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 MAA07328
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 12:37:23 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Ag5wc-000DwH-Gd
	for te-wg-data@psg.com; Mon, 12 Jan 2004 17:33:42 +0000
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ag5wO-000Dd0-7T
	for te-wg@ops.ietf.org; Mon, 12 Jan 2004 17:33:28 +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 i0CHX9Bm096950;
	Mon, 12 Jan 2004 09:33:10 -0800 (PST)
	(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 i0CHX9h03115;
	Mon, 12 Jan 2004 09:33:09 -0800 (PST)
	(envelope-from ina@juniper.net)
Date: Mon, 12 Jan 2004 09:33:09 -0800 (PST)
From: Ina Minei <ina@juniper.net>
To: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
In-Reply-To: <AC60B39EEE7320498063D37799FB82D902213CF2@xbe-lon-313.cisco.com>
Message-ID: <20040112092759.G33455@garnet.juniper.net>
References: <AC60B39EEE7320498063D37799FB82D902213CF2@xbe-lon-313.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk


	Agreed. let's carry this forward. I think picking 4 for both
vendor/experimental will eventually get us in trouble, since the number is
too small (we are likely to have 3 vendor-specific already, by extending
the existing models)  8, 16, 32 can all be made to work.

			Ina

On Mon, 12 Jan 2004, Francois Le Faucheur (flefauch) wrote:

> Hello,
>
> I think a BC Model ID space of 256 is comfortable and provides more than
> enough codepoints. I also feel this is not a big issue and we just need
> someone, like our chairs, to pick a size for the experimental/vendor
> space. Any value among { 4, 8, 16, 32 } works for me.
> I'll put that number in the next rev as soon as I hear a conclusion from
> the chairs.
>
> Cheers
> Francois
>
>
> >> -----Original Message-----
> >> From: owner-te-wg@ops.ietf.org
> >> [mailto:owner-te-wg@ops.ietf.org] On Behalf Of Ina Minei
> >> Sent: vendredi 9 janvier 2004 19:07
> >> To: Wijnen, Bert (Bert)
> >> Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
> >> Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
> >>
> >>
> >>
> >> 	Bert,
> >>
> >> 	Nobody else seems to care about this issue, or at least they are
> >> not expressing an opinion on the list, so this is why I was
> >> carrying on
> >> this email thread. I personally would like to see the issue
> >> closed and
> >> the draft moved forward.
> >>
> >> 	This issue is not such a big one, so let's not spend too much
> >> time on it. So far there are two proposals: 3 numbers or 32 numbers.
> >> I have explained why I think 3 is not enough, and you have
> >> explained why
> >> you think 32 is too much.
> >>
> >> 	Let's propose 16 and put it to vote on the list and be done with
> >> it. Perhaps the WG chairs can help with this?
> >>
> >> 			Ina
> >>
> >> On Fri, 9 Jan 2004, Wijnen, Bert (Bert) wrote:
> >>
> >> > Not sure why some people think (or that is how I
> >> > perceive your last email) that an AD has any more weight than
> >> > other WG members. I have made my opinion clear that I think
> >> > that 32 is far too much.
> >> >
> >> > I have asked WG chairs to check this also.
> >> >
> >> > It is best if WG chairs take initiative to drive resolution of
> >> > these questions.
> >> >
> >> > Thanks,
> >> > Bert
> >> >
> >> > > -----Original Message-----
> >> > > From: Ina Minei [mailto:ina@juniper.net]
> >> > > Sent: vrijdag 9 januari 2004 1:19
> >> > > To: Wijnen, Bert (Bert)
> >> > > Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
> >> > > Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
> >> > >
> >> > >
> >> > >
> >> > > 	Bert,
> >> > >
> >> > > 	So can we just agree on 32 "experimental/vendor private"
> >> > > numbers starting at 255 and down?
> >> > >
> >> > > 			Thank you,
> >> > >
> >> > > 				Ina
> >> > >
> >> > > On Mon, 29 Dec 2003, Ina Minei wrote:
> >> > >
> >> > > >
> >> > > >
> >> > > > 	Bert,
> >> > > >
> >> > > > 	I think we both agree :). and in the end it all
> >> boils down to
> >> > > > experimental vs vendor-private. What I am thinking of
> >> > > > is vendor-private numbers, and what you are thinking of is
> >> > > experimental.
> >> > > > We are both right. How we decide to solve it is a
> >> different issue.
> >> > > >
> >> > > > 	We can  either: 1) allocate two spaces, one for
> >> experimental and
> >> > > > one for vendor-private. In that case, 3 should be enough
> >> > > for experimental,
> >> > > > but as  for vendor-private more than 3 would be required,
> >> > > for the reason I
> >> > > > was  mentioning in the original mail or 2) allocate one
> >> > > bigger space for
> >> > > > both experimental and vendor-private. I prefer (2).
> >> > > >
> >> > > > 	Let's just pick one of the options, and carry
> >> it forward. Let me
> >> > > > know what you prefer.
> >> > > >
> >> > > > 			Ina
> >> > > >
> >> > >
> >> >
> >>
> >>
>



From owner-te-wg@ops.ietf.org  Mon Jan 12 14:41:02 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12939
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 14:41:02 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Ag7rq-000HnW-4f
	for te-wg-data@psg.com; Mon, 12 Jan 2004 19:36:54 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ag7ra-000HVs-SU
	for te-wg@ops.ietf.org; Mon, 12 Jan 2004 19:36:38 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id i0CJa9Hu006377;
	Mon, 12 Jan 2004 19:36:09 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id TAA25954;
	Mon, 12 Jan 2004 19:36:08 GMT
Message-Id: <5.2.0.9.2.20040112091601.00a41d00@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 Jan 2004 09:23:41 -0800
To: Yakov Rekhter <yakov@juniper.net>
From: raymond zhang <zhangr@info.net>
Subject: Re: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-03.txt 
Cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
In-Reply-To: <200401121628.i0CGSuh97495@merlot.juniper.net>
References: <Your message of "Thu, 08 Jan 2004 09:47:28 PST." <5.2.0.9.2.20040108093904.02a52ba0@delta.info.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yakov,

Thanks for the additional input...

At 08:28 AM 1/12/2004 -0800, Yakov Rekhter wrote:
>Raymond,
>
> > Hi Jim and Ed,
> >
> > Happy new year !
> >
> > The following emails were sent to both of you nearly a month ago.  I am 
> not
> > sure if you are having problem receiving email again so I am copying Bert
> > and posting to the list also.
> >
> > The -03 version of the draft
> > 
> (http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-03.t
>xt)
> > is ready for last call as per our minutes from the Minneapolis meeting.
>
>I think that the latest version of the draft still require few
>changes/updates.
>
>1. The document should state up front the following:
>
>       This document doesn't make any claims with respect to whether
>       it is possible to have a practical solution that meets all the
>       requirements listed in this document.
>
>(That point have been discussed before, and I thought the authors
>agreed to include the above in the text, but I wasn't able to find
>it in the -03 version).

In section 6.1, I included wording "

If a solution can fulfill just a subset of those requirements in
    section 5, then it MUST be explicitly documented"

Would this reflect your point above ?


>2. From 5.1.5 ("Re-optimization"):
>
>    Once an inter-AS TE LSP has been established and should there be any
>    resource or other changes inside anyone of transiting ASes, the
>    solution MUST be able to re-optimize the LSP accordingly and
>    non-disruptively, either upon expiration of a configurable timer or
>    triggered by a network event or a manual request at the TE tunnel
>    Head-end.
>
>    The solution SHOULD provide an option for the Head-End LSRs to
>    control if re-optimizing or not should there exist a more optimal
>    path in one of the transit ASes along the inter-AS TE LSP path.
>
>The above it too restrictive, as it restricts re-optimization to
>only the case where resource changes are in the set of ASs (currently)
>transited by the LSP. To remove this restriction I'd like to propose the
>following replacement:
>
>    Once an inter-AS TE LSP has been established and should there be any
>    resource or other changes inside anyone of the ASes, the
>    solution MUST be able to re-optimize the LSP accordingly and
>    non-disruptively, either upon expiration of a configurable timer or
>    triggered by a network event or a manual request at the TE tunnel
>    Head-end.
>
>    The solution SHOULD provide an option for the Head-End LSRs to
>    control if re-optimizing or not should there exist a more optimal
>    path in one of the ASes.

"along the inter-AS TE LSP path" was left there by mistake, sorry...  As 
per our last discussion, the text should appear exactly the same as you 
proposed above.  Thanks for catching it !

>3. Section 6.2 ("Performance") should include control plane overhead
>as one of the criteria. Ditto for data plane overhead.

Will do, thanks.

>4. In 5.1.6 replace "CSPF" with "Path computation").

You meant 5.1.8 ?  Will do...

Cheers,
Raymond
>Yakov.





From owner-te-wg@ops.ietf.org  Mon Jan 12 14:46: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 OAA13134
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 14:46:03 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Ag7yn-00007R-B2
	for te-wg-data@psg.com; Mon, 12 Jan 2004 19:44:05 +0000
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ag7yX-000PoB-6N
	for te-wg@ops.ietf.org; Mon, 12 Jan 2004 19:43:49 +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 i0CJh2Bm097360;
	Mon, 12 Jan 2004 11:43:02 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0CJgwh16686;
	Mon, 12 Jan 2004 11:42:58 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401121942.i0CJgwh16686@merlot.juniper.net>
To: raymond zhang <zhangr@info.net>
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-03.txt 
In-Reply-To: Your message of "Mon, 12 Jan 2004 09:23:41 PST."
             <5.2.0.9.2.20040112091601.00a41d00@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <71355.1073936578.1@juniper.net>
Date: Mon, 12 Jan 2004 11:42:58 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

> Hi Yakov,
> 
> Thanks for the additional input...

welcome !

> At 08:28 AM 1/12/2004 -0800, Yakov Rekhter wrote:
> >Raymond,
> >
> > > Hi Jim and Ed,
> > >
> > > Happy new year !
> > >
> > > The following emails were sent to both of you nearly a month ago.  I am 
> > not
> > > sure if you are having problem receiving email again so I am copying Bert
> > > and posting to the list also.
> > >
> > > The -03 version of the draft
> > > 
> > (http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-03
.t
> >xt)
> > > is ready for last call as per our minutes from the Minneapolis meeting.
> >
> >I think that the latest version of the draft still require few
> >changes/updates.
> >
> >1. The document should state up front the following:
> >
> >       This document doesn't make any claims with respect to whether
> >       it is possible to have a practical solution that meets all the
> >       requirements listed in this document.
> >
> >(That point have been discussed before, and I thought the authors
> >agreed to include the above in the text, but I wasn't able to find
> >it in the -03 version).
> 
> In section 6.1, I included wording "
> 
> If a solution can fulfill just a subset of those requirements in
>     section 5, then it MUST be explicitly documented"
> 
Would this reflect your point above ?

No, I don't think this is sufficient. I really like to have the
sentence I suggested up front in the document.
  
> >2. From 5.1.5 ("Re-optimization"):
> >
> >    Once an inter-AS TE LSP has been established and should there be any
> >    resource or other changes inside anyone of transiting ASes, the
> >    solution MUST be able to re-optimize the LSP accordingly and
> >    non-disruptively, either upon expiration of a configurable timer or
> >    triggered by a network event or a manual request at the TE tunnel
> >    Head-end.
> >
> >    The solution SHOULD provide an option for the Head-End LSRs to
> >    control if re-optimizing or not should there exist a more optimal
> >    path in one of the transit ASes along the inter-AS TE LSP path.
> >
> >The above it too restrictive, as it restricts re-optimization to
> >only the case where resource changes are in the set of ASs (currently)
> >transited by the LSP. To remove this restriction I'd like to propose the
> >following replacement:
> >
> >    Once an inter-AS TE LSP has been established and should there be any
> >    resource or other changes inside anyone of the ASes, the
> >    solution MUST be able to re-optimize the LSP accordingly and
> >    non-disruptively, either upon expiration of a configurable timer or
> >    triggered by a network event or a manual request at the TE tunnel
> >    Head-end.
> >
> >    The solution SHOULD provide an option for the Head-End LSRs to
> >    control if re-optimizing or not should there exist a more optimal
> >    path in one of the ASes.
> 
> "along the inter-AS TE LSP path" was left there by mistake, sorry...  As 
> per our last discussion, the text should appear exactly the same as you 
> proposed above.  Thanks for catching it !

welcome !

> 
> >3. Section 6.2 ("Performance") should include control plane overhead
> >as one of the criteria. Ditto for data plane overhead.
> 
> Will do, thanks.

Ok.

> >4. In 5.1.6 replace "CSPF" with "Path computation").
> 
> You meant 5.1.8 ?  

Yes.

> Will do...

Thanks !!!

Yakov.



From owner-te-wg@ops.ietf.org  Mon Jan 12 19:36:28 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02065
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 19:36:28 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1AgCRU-000KRr-EW
	for te-wg-data@psg.com; Tue, 13 Jan 2004 00:30:00 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AgCR8-000KPX-M0
	for te-wg@ops.ietf.org; Tue, 13 Jan 2004 00:29:38 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id i0D0TUPA010434;
	Tue, 13 Jan 2004 00:29:31 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id AAA07546;
	Tue, 13 Jan 2004 00:29:29 GMT
Message-Id: <5.2.0.9.2.20040112162822.02d74548@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 12 Jan 2004 16:29:23 -0800
To: Yakov Rekhter <yakov@juniper.net>
From: raymond zhang <zhangr@info.net>
Subject: Re: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-03.txt 
Cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
In-Reply-To: <200401121942.i0CJgwh16686@merlot.juniper.net>
References: <Your message of "Mon, 12 Jan 2004 09:23:41 PST." <5.2.0.9.2.20040112091601.00a41d00@delta.info.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yakov,


At 11:42 AM 1/12/2004 -0800, Yakov Rekhter wrote:
>Raymond,
>
> > Hi Yakov,
> >
> > Thanks for the additional input...
>
>welcome !
>
> > At 08:28 AM 1/12/2004 -0800, Yakov Rekhter wrote:
> > >Raymond,
> > >
> > > > Hi Jim and Ed,
> > > >
> > > > Happy new year !
> > > >
> > > > The following emails were sent to both of you nearly a month 
> ago.  I am
> > > not
> > > > sure if you are having problem receiving email again so I am 
> copying Bert
> > > > and posting to the list also.
> > > >
> > > > The -03 version of the draft
> > > >
> > > 
> (http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-03
>.t
> > >xt)
> > > > is ready for last call as per our minutes from the Minneapolis meeting.
> > >
> > >I think that the latest version of the draft still require few
> > >changes/updates.
> > >
> > >1. The document should state up front the following:
> > >
> > >       This document doesn't make any claims with respect to whether
> > >       it is possible to have a practical solution that meets all the
> > >       requirements listed in this document.
> > >
> > >(That point have been discussed before, and I thought the authors
> > >agreed to include the above in the text, but I wasn't able to find
> > >it in the -03 version).
> >
> > In section 6.1, I included wording "
> >
> > If a solution can fulfill just a subset of those requirements in
> >     section 5, then it MUST be explicitly documented"
> >
>Would this reflect your point above ?
>
>No, I don't think this is sufficient. I really like to have the
>sentence I suggested up front in the document.

Ok, no problem. I will add it in the intro section.

Cheers,
Raymond
>
> > >2. From 5.1.5 ("Re-optimization"):
> > >
> > >    Once an inter-AS TE LSP has been established and should there be any
> > >    resource or other changes inside anyone of transiting ASes, the
> > >    solution MUST be able to re-optimize the LSP accordingly and
> > >    non-disruptively, either upon expiration of a configurable timer or
> > >    triggered by a network event or a manual request at the TE tunnel
> > >    Head-end.
> > >
> > >    The solution SHOULD provide an option for the Head-End LSRs to
> > >    control if re-optimizing or not should there exist a more optimal
> > >    path in one of the transit ASes along the inter-AS TE LSP path.
> > >
> > >The above it too restrictive, as it restricts re-optimization to
> > >only the case where resource changes are in the set of ASs (currently)
> > >transited by the LSP. To remove this restriction I'd like to propose the
> > >following replacement:
> > >
> > >    Once an inter-AS TE LSP has been established and should there be any
> > >    resource or other changes inside anyone of the ASes, the
> > >    solution MUST be able to re-optimize the LSP accordingly and
> > >    non-disruptively, either upon expiration of a configurable timer or
> > >    triggered by a network event or a manual request at the TE tunnel
> > >    Head-end.
> > >
> > >    The solution SHOULD provide an option for the Head-End LSRs to
> > >    control if re-optimizing or not should there exist a more optimal
> > >    path in one of the ASes.
> >
> > "along the inter-AS TE LSP path" was left there by mistake, sorry...  As
> > per our last discussion, the text should appear exactly the same as you
> > proposed above.  Thanks for catching it !
>
>welcome !
>
> >
> > >3. Section 6.2 ("Performance") should include control plane overhead
> > >as one of the criteria. Ditto for data plane overhead.
> >
> > Will do, thanks.
>
>Ok.
> > >4. In 5.1.6 replace "CSPF" with "Path computation").
> >
> > You meant 5.1.8 ?
>
>Yes.
>
> > Will do...
>
>Thanks !!!
>
>Yakov.





From owner-te-wg@ops.ietf.org  Mon Jan 12 20:23:52 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03783
	for <tewg-archive@lists.ietf.org>; Mon, 12 Jan 2004 20:23:52 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1AgDF6-0000lq-Vy
	for te-wg-data@psg.com; Tue, 13 Jan 2004 01:21:16 +0000
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AgDEm-0000kz-Uh
	for te-wg@ops.ietf.org; Tue, 13 Jan 2004 01:20:56 +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 i0D1K4Bm099195;
	Mon, 12 Jan 2004 17:20:05 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0D1K4h52713;
	Mon, 12 Jan 2004 17:20:04 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401130120.i0D1K4h52713@merlot.juniper.net>
To: raymond zhang <zhangr@info.net>
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-03.txt 
In-Reply-To: Your message of "Mon, 12 Jan 2004 16:29:23 PST."
             <5.2.0.9.2.20040112162822.02d74548@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <71882.1073956804.1@juniper.net>
Date: Mon, 12 Jan 2004 17:20:04 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

[clipped...]

> > > >I think that the latest version of the draft still require few
> > > >changes/updates.
> > > >
> > > >1. The document should state up front the following:
> > > >
> > > >       This document doesn't make any claims with respect to whether
> > > >       it is possible to have a practical solution that meets all the
> > > >       requirements listed in this document.
> > > >
> > > >(That point have been discussed before, and I thought the authors
> > > >agreed to include the above in the text, but I wasn't able to find
> > > >it in the -03 version).
> > >
> > > In section 6.1, I included wording "
> > >
> > > If a solution can fulfill just a subset of those requirements in
> > >     section 5, then it MUST be explicitly documented"
> > >
> >Would this reflect your point above ?
> >
> >No, I don't think this is sufficient. I really like to have the
> >sentence I suggested up front in the document.
> 
> Ok, no problem. I will add it in the intro section.

Thanks !!! Looking forward for the 04 version.

Yakov.



From owner-te-wg@ops.ietf.org  Wed Jan 14 14:28:31 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04531
	for <tewg-archive@lists.ietf.org>; Wed, 14 Jan 2004 14:28:30 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Agqbn-000PyB-KW
	for te-wg-data@psg.com; Wed, 14 Jan 2004 19:23:19 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Agqba-000Pvv-31
	for te-wg@ops.ietf.org; Wed, 14 Jan 2004 19:23:06 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 14 Jan 2004 20:23:50 +0100
Received: from xbe-lon-302.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id i0EJMh5v026682;
	Wed, 14 Jan 2004 20:22:44 +0100 (MET)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Wed, 14 Jan 2004 19:23:02 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Size of "experimental" range in BC Model Id
Date: Wed, 14 Jan 2004 19:23:01 -0000
Message-ID: <AC60B39EEE7320498063D37799FB82D9022B4F3D@xbe-lon-313.cisco.com>
Thread-Topic: Size of "experimental" range in BC Model Id
Thread-Index: AcPWsJSj5V60UwW0SB6+aNe0O23P2AEIiI+Q
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ed Kern" <ejk@tech.org>, "Jim Boyle" <jboyle@pdnets.com>
Cc: "Tewg (E-mail)" <te-wg@ops.ietf.org>,
        "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Ina Minei" <ina@juniper.net>
X-OriginalArrivalTime: 14 Jan 2004 19:23:02.0685 (UTC) FILETIME=[D40974D0:01C3DAD3]
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Ed, Jim,

We've done all the edits on -proto. The only thing holding its posting
now is a conclusion on the size for the "experimental" range in the BC
Model ID name space.

As I mentioned earlier on the list, we're assuming a size of 16 for now
and would like to post the updated version by Friday morning US time.
Please let us know before then, if you see any issue with that value.

Thanks

Francois

>> -----Original Message-----
>> From: owner-te-wg@ops.ietf.org=20
>> [mailto:owner-te-wg@ops.ietf.org] On Behalf Of Wijnen, Bert (Bert)
>> Sent: vendredi 9 janvier 2004 12:10
>> To: Ina Minei; Wijnen, Bert (Bert)
>> Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
>> Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
>>=20
>>=20
>> Not sure why some people think (or that is how I=20
>> perceive your last email) that an AD has any more weight than
>> other WG members. I have made my opinion clear that I think
>> that 32 is far too much.
>>=20
>> I have asked WG chairs to check this also.
>>=20
>> It is best if WG chairs take initiative to drive resolution of
>> these questions.
>>=20
>> Thanks,
>> Bert=20
>>=20
>> > -----Original Message-----
>> > From: Ina Minei [mailto:ina@juniper.net]
>> > Sent: vrijdag 9 januari 2004 1:19
>> > To: Wijnen, Bert (Bert)
>> > Cc: Ash, Gerald R (Jerry), ALABS; Tewg (E-mail)
>> > Subject: RE: AD evaluation: draft-ietf-tewg-diff-te-mar-02.txt
>> >=20
>> >=20
>> >=20
>> > 	Bert,
>> >=20
>> > 	So can we just agree on 32 "experimental/vendor private"
>> > numbers starting at 255 and down?
>> >=20
>> > 			Thank you,
>> >=20
>> > 				Ina
>> >=20
>> > On Mon, 29 Dec 2003, Ina Minei wrote:
>> >=20
>> > >
>> > >
>> > > 	Bert,
>> > >
>> > > 	I think we both agree :). and in the end it all boils down to
>> > > experimental vs vendor-private. What I am thinking of
>> > > is vendor-private numbers, and what you are thinking of is=20
>> > experimental.
>> > > We are both right. How we decide to solve it is a=20
>> different issue.
>> > >
>> > > 	We can  either: 1) allocate two spaces, one for experimental and
>> > > one for vendor-private. In that case, 3 should be enough=20
>> > for experimental,
>> > > but as  for vendor-private more than 3 would be required,=20
>> > for the reason I
>> > > was  mentioning in the original mail or 2) allocate one=20
>> > bigger space for
>> > > both experimental and vendor-private. I prefer (2).
>> > >
>> > > 	Let's just pick one of the options, and carry it forward. Let me
>> > > know what you prefer.
>> > >
>> > > 			Ina
>> > >
>> >=20
>>=20
>>=20



From owner-te-wg@ops.ietf.org  Wed Jan 14 15:57:16 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11665
	for <tewg-archive@lists.ietf.org>; Wed, 14 Jan 2004 15:57:15 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1Ags2S-0008Db-99
	for te-wg-data@psg.com; Wed, 14 Jan 2004 20:54:56 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ags2B-0008Cw-43
	for te-wg@ops.ietf.org; Wed, 14 Jan 2004 20:54:39 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11230;
	Wed, 14 Jan 2004 15:54:36 -0500 (EST)
Message-Id: <200401142054.PAA11230@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-interas-mpls-te-req-04.txt
Date: Wed, 14 Jan 2004 15:54:36 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60
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		: MPLS Inter-AS Traffic Engineering requirements
	Author(s)	: R. Zhang, J. Vasseur
	Filename	: draft-ietf-tewg-interas-mpls-te-req-04.txt
	Pages		: 26
	Date		: 2004-1-14
	
This document discusses requirements for the support of inter-AS
MPLS Traffic Engineering (MPLS TE).  The main objective of this
document is to present a set of requirements which would result in
a set of general guidelines in the definition, selection and
specification development for any technical solution(s) meeting
these requirements.

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Fri Jan 16 13:58: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 NAA24719
	for <tewg-archive@lists.ietf.org>; Fri, 16 Jan 2004 13:58:07 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1AhZ9O-0009Pd-6v
	for te-wg-data@psg.com; Fri, 16 Jan 2004 18:56:58 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AhZ9B-0009MY-8C
	for te-wg@ops.ietf.org; Fri, 16 Jan 2004 18:56:45 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id i0GIuDf0026629;
	Fri, 16 Jan 2004 18:56:16 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id SAA04321;
	Fri, 16 Jan 2004 18:56:12 GMT
Message-Id: <5.2.0.9.2.20040114153440.02a86a58@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Fri, 16 Jan 2004 10:56:06 -0800
To: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>
From: Internet-Drafts@ietf.org (by way of raymond zhang <zhangr@info.net>)
Subject: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Jim and Ed,

Here is the most updated one.  Would you please initiate the WG last call 
for this draft ?

Thanks,
Raymond


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		: MPLS Inter-AS Traffic Engineering requirements
	Author(s)	: R. Zhang, J. Vasseur
	Filename	: draft-ietf-tewg-interas-mpls-te-req-04.txt
	Pages		: 26
	Date		: 2004-1-14
	
This document discusses requirements for the support of inter-AS
MPLS Traffic Engineering (MPLS TE).  The main objective of this
document is to present a set of requirements which would result in
a set of general guidelines in the definition, selection and
specification development for any technical solution(s) meeting
these requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-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-interas-mpls-te-req-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-interas-mpls-te-req-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.
Content-Type: text/plain
Content-ID:	<2004-1-14161529.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt

<ftp://ftp.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt>




From owner-te-wg@ops.ietf.org  Fri Jan 16 13:58:36 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24775
	for <tewg-archive@lists.ietf.org>; Fri, 16 Jan 2004 13:58:35 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.24; FreeBSD)
	id 1AhZ6J-0008zY-9O
	for te-wg-data@psg.com; Fri, 16 Jan 2004 18:53:47 +0000
Received: from [171.68.10.87] (helo=sj-iport-5.cisco.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AhZ62-0008xk-VA
	for te-wg@ops.ietf.org; Fri, 16 Jan 2004 18:53:30 +0000
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-5.cisco.com with ESMTP; 16 Jan 2004 10:53:32 -0800
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id i0GIrSVM000473;
	Fri, 16 Jan 2004 10:53:28 -0800 (PST)
Received: from jvasseur-w2k01.cisco.com (rtp-vpn3-774.cisco.com [10.82.219.10]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id KAA03394; Fri, 16 Jan 2004 10:53:26 -0800 (PST)
Message-Id: <4.3.2.7.2.20040116135134.04653cf8@wells.cisco.com>
X-Sender: jvasseur@wells.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 16 Jan 2004 13:53:24 -0500
To: Jim Boyle <jboyle@pdnets.com>, ejk@tech.org
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt
Cc: te-wg@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.60
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Jim and Ed,

As already pointed out by Raymond in several emails, may we now proceed to 
last call, as agreed a few months ago during the last IETF ? This last 
revision incorporate all the comments we received.

Thanks.

JP.

>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-interas-mpls-te-req-04.txt
>Date: Wed, 14 Jan 2004 15:54:36 -0500
>X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
>X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
>         NO_REAL_NAME autolearn=no version=2.60
>Sender: owner-te-wg@ops.ietf.org
>
>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           : MPLS Inter-AS Traffic Engineering requirements
>         Author(s)       : R. Zhang, J. Vasseur
>         Filename        : draft-ietf-tewg-interas-mpls-te-req-04.txt
>         Pages           : 26
>         Date            : 2004-1-14
>
>This document discusses requirements for the support of inter-AS
>MPLS Traffic Engineering (MPLS TE).  The main objective of this
>document is to present a set of requirements which would result in
>a set of general guidelines in the definition, selection and
>specification development for any technical solution(s) meeting
>these requirements.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-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-interas-mpls-te-req-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-interas-mpls-te-req-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.
>Content-Type: text/plain
>Content-ID:     <2004-1-14161529.I-D@ietf.org>
>
>ENCODING mime
>FILE /internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt
>
><ftp://ftp.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt>




From owner-te-wg@ops.ietf.org  Mon Jan 19 10:28:47 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20800
	for <tewg-archive@lists.ietf.org>; Mon, 19 Jan 2004 10:28:41 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AibDG-0001kb-I0
	for te-wg-data@psg.com; Mon, 19 Jan 2004 15:21:14 +0000
Received: from [193.205.242.5] (helo=nausicaa.coritel.it)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AibD2-0001k2-SR
	for te-wg@ops.ietf.org; Mon, 19 Jan 2004 15:21:01 +0000
Received: from Poisson ([151.100.37.144])
	by nausicaa.coritel.it (8.11.2/8.11.2) with SMTP id i0JFSCw29478
	for <te-wg@ops.ietf.org>; Mon, 19 Jan 2004 16:28:15 +0100
Message-ID: <00e101c3dea0$591b4980$90256497@coritel>
From: "alessio d'achille" <dachille@coritel.it>
To: <te-wg@ops.ietf.org>
Subject: A new draft !
Date: Mon, 19 Jan 2004 16:24:04 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00DC_01C3DEA8.A786B0C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-1.2 required=5.0 tests=BAYES_20,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE autolearn=no version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00DC_01C3DEA8.A786B0C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,=20

we have just submitted to the IETF a new draft about inter-area path =
protection; in this document we addressed the problem of establishing =
two disjoint LSPs between two nodes which belongs to different areas =
(with the term "areas" we refer to an
- OSPF area or
- Autonomous System or
- Optical island      )

The draft is now available in the IETF draft directory and its name is :

<draft-dachille-inter-area-path-protection-00.txt>

A URL for this Internet-Draft is:=20

http://www.ietf.org/internet-drafts/draft-dachille-inter-area-path-protec=
tion-00.txt
=20
Best regards to all,
=20
Alessio D'Achille (one of the authors of this draft),=20
on behalf of

Vishal Sharma (co-author), Fabio Ricciato (author), Marco Listanti =
(Author) and Ugo Monaco (Author).


P.S. We have noticed that there is an error in the authors' referencs in =
the very first page in the version of the draft in the IETF draft =
directory (in fact, in the very first page, "Ed." figures next to Vishal =
Sharma, but he is a co-author, and "Ed." should be next to Alessio =
D'Achille, Fabio Ricciato, Marco Listanti and Ugo Monaco)


------=_NextPart_000_00DC_01C3DEA8.A786B0C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi all, </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>we have =
just submitted to=20
the IETF a new draft about inter-area path protection; in this document =
we=20
addressed the problem of establishing two disjoint LSPs between two =
nodes which=20
belongs to different areas (with the term "areas" we refer to=20
an</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>- OSPF area =

or</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>- =
Autonomous System=20
or</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>- Optical=20
island&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; )</FONT></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The draft is now available in the IETF =
draft=20
directory and its name is :</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial=20
size=3D2>&lt;draft-dachille-inter-area-path-protection-00.txt&gt;</FONT><=
/DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>A URL for this Internet-Draft is: =
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff><FONT face=3DArial size=3D2><FONT =
face=3DArial size=3D2><U><A=20
href=3D"http://www.ietf.org/internet-drafts/draft-dachille-inter-area-pat=
h-protection-00.txt">http://www.ietf.org/internet-drafts/draft-dachille-i=
nter-area-path-protection-00.txt</A></U></FONT></FONT></FONT></DIV>
<DIV><FONT color=3D#0000ff><FONT face=3DArial size=3D2><FONT =
face=3DArial=20
size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>Best =
regards to=20
all,</FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial =
size=3D2></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>Alessio =
D'Achille (one of=20
the authors of this draft), </FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2>on behalf of</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Vishal Sharma (co-author), Fabio =
Ricciato (author),=20
Marco Listanti (Author) and Ugo Monaco (Author).</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>P.S. We have noticed that there is an =
error in the=20
authors' referencs in the very first page in the version of the draft in =
the=20
IETF draft directory (in fact, in the very first page, "Ed." figures =
next to=20
Vishal Sharma, but he is a co-author, and "Ed." should be next to =
Alessio=20
D'Achille, Fabio Ricciato, Marco Listanti and Ugo Monaco)</FONT></DIV>
<DIV>&nbsp;</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_00DC_01C3DEA8.A786B0C0--




From owner-te-wg@ops.ietf.org  Mon Jan 19 13:34: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 NAA00989
	for <tewg-archive@lists.ietf.org>; Mon, 19 Jan 2004 13:34:48 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AieAQ-000KC6-7k
	for te-wg-data@psg.com; Mon, 19 Jan 2004 18:30:30 +0000
Received: from [66.163.169.226] (helo=smtp106.mail.sc5.yahoo.com)
	by psg.com with smtp (Exim 4.24; FreeBSD)
	id 1Aie9x-000K8l-FT
	for te-wg@ops.ietf.org; Mon, 19 Jan 2004 18:30:01 +0000
Received: from unknown (HELO RAKHILAPTOP) (vsharma87@67.117.149.0 with login)
  by smtp106.mail.sc5.yahoo.com with SMTP; 19 Jan 2004 18:30:00 -0000
From: "Vishal Sharma" <v.sharma@ieee.org>
To: <ccamp@ops.ietf.org>, "TE" <te-wg@ops.ietf.org>
Cc: "alessio d'achille" <dachille@coritel.it>
Subject: Inter-region TE
Date: Mon, 19 Jan 2004 10:29:58 -0800
Message-ID: <MMECLKMDFPCEJFECIBCMCEPAEEAA.v.sharma@ieee.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002C_01C3DE77.2FD8D5C0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <00ac01c3de9f$98153980$90256497@coritel>
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.7 required=5.0 tests=BAYES_00,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE autolearn=no version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_002C_01C3DE77.2FD8D5C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Folks,

I just wanted to add that this work ties in to the recent
inter-AS/inter-area TE
work that has been a focus of the TE and CCAMP WGs.

As Alessio mentioned, this work takes a unified view of areas and AS's, and
is applicable to both inter-AS and inter-area scenarios.

Therefore, we would be particularly interested in feedback from some of the
principal WG members who are involved in the inter-AS/inter-area activity.

Regards,
-Vishal
  -----Original Message-----
  From: owner-ccamp@ops.ietf.org [mailto:owner-ccamp@ops.ietf.org]On Behalf
Of alessio d'achille
  Sent: Monday, January 19, 2004 7:19 AM
  To: ccamp@ops.ietf.org
  Cc: te-wg@osp.ietf.org
  Subject: A new draft is available


  Hi all,

  we have just submitted to the IETF a new draft about inter-area path
protection; in this document we addressed the problem of establishing two
disjoint LSPs between two nodes which belongs to different areas (with the
term "areas" we refer to an
  - OSPF area or
  - Autonomous System or
  - Optical island      )

  The draft is now available in the IETF draft directory and its name is :

  <draft-dachille-inter-area-path-protection-00.txt>

  A URL for this Internet-Draft is:


http://www.ietf.org/internet-drafts/draft-dachille-inter-area-path-protectio
n-00.txt

  Best regards to all,

  Alessio D'Achille (one of the authors of this draft),
  on behalf of

  Vishal Sharma (co-author), Fabio Ricciato (author), Marco Listanti
(Author) and Ugo Monaco (Author).


  P.S. We have noticed that there is an error in the authors' referencs in
the very first page in the version of the draft in the IETF draft directory
(in fact, in the very first page, "Ed." figures next to Vishal Sharma, but
he is a co-author, and "Ed." should be next to Alessio D'Achille, Fabio
Ricciato, Marco Listanti and Ugo Monaco)





------=_NextPart_000_002C_01C3DE77.2FD8D5C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004>Folks,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D798550518-19012004>I just=20
wanted to add that this work ties in&nbsp;to the recent =
inter-AS/inter-area=20
TE</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004>work&nbsp;that has been&nbsp;a&nbsp;focus =
of&nbsp;the=20
TE and CCAMP WGs.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D798550518-19012004>As=20
Alessio mentioned, this work takes a unified view of areas and AS's,=20
and</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D798550518-19012004>is=20
applicable to both inter-AS and inter-area =
scenarios.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004>Therefore, we would be particularly =
interested in=20
feedback from some of the</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004>principal WG members who are involved in the=20
inter-AS/inter-area activity.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004>Regards,</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D798550518-19012004>-Vishal</SPAN></FONT></DIV></DIV></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> =
owner-ccamp@ops.ietf.org=20
  [mailto:owner-ccamp@ops.ietf.org]<B>On Behalf Of </B>alessio=20
  d'achille<BR><B>Sent:</B> Monday, January 19, 2004 7:19 =
AM<BR><B>To:</B>=20
  ccamp@ops.ietf.org<BR><B>Cc:</B> te-wg@osp.ietf.org<BR><B>Subject:</B> =
A new=20
  draft is available<BR><BR></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>Hi all, </FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>we have =
just submitted to=20
  the IETF a new draft about inter-area path protection; in this =
document we=20
  addressed the problem of establishing two disjoint LSPs between two =
nodes=20
  which belongs to different areas (with the term "areas" we refer to=20
  an</FONT></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>- OSPF =
area=20
  or</FONT></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>- =
Autonomous System=20
  or</FONT></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>- Optical =

  island&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; )</FONT></FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>The draft is now available in the =
IETF draft=20
  directory and its name is :</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial=20
  =
size=3D2>&lt;draft-dachille-inter-area-path-protection-00.txt&gt;</FONT><=
/DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>A URL for this Internet-Draft is: =
</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT color=3D#0000ff><FONT face=3DArial size=3D2><FONT =
face=3DArial size=3D2><U><A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-dachille-inter-area-pat=
h-protection-00.txt">http://www.ietf.org/internet-drafts/draft-dachille-i=
nter-area-path-protection-00.txt</A></U></FONT></FONT></FONT></DIV>
  <DIV><FONT color=3D#0000ff><FONT face=3DArial size=3D2><FONT =
face=3DArial=20
  size=3D2></FONT></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>Best =
regards to=20
  all,</FONT></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial=20
size=3D2></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2>Alessio =
D'Achille (one of=20
  the authors of this draft), </FONT></FONT></DIV>
  <DIV><FONT face=3DArial size=3D2>on behalf of</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>Vishal Sharma (co-author), Fabio =
Ricciato=20
  (author), Marco Listanti (Author) and Ugo Monaco =
(Author).</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2>P.S. We have noticed that there is an =
error in=20
  the authors' referencs in the very first page in the version of the =
draft in=20
  the IETF draft directory (in fact, in the very first page, "Ed." =
figures next=20
  to Vishal Sharma, but he is a co-author, and "Ed." should be next to =
Alessio=20
  D'Achille, Fabio Ricciato, Marco Listanti and Ugo Monaco)</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial=20
size=3D2></FONT></FONT>&nbsp;</DIV>
  <DIV><FONT face=3DArial size=3D2><FONT face=3DArial size=3D2><A=20
  =
href=3D"http://www.ietf.org/internet-drafts/draft-inter-area"></A></FONT>=
</FONT>&nbsp;</DIV>
  <DIV>&nbsp;</DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_002C_01C3DE77.2FD8D5C0--




From owner-te-wg@ops.ietf.org  Mon Jan 19 17:02:01 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10631
	for <tewg-archive@lists.ietf.org>; Mon, 19 Jan 2004 17:02:01 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AihN6-000Ey7-7s
	for te-wg-data@psg.com; Mon, 19 Jan 2004 21:55:48 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AihMt-000EwR-ES
	for te-wg@ops.ietf.org; Mon, 19 Jan 2004 21:55:35 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id i0JLrPVA009868;
	Mon, 19 Jan 2004 21:53:25 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id VAA27711;
	Mon, 19 Jan 2004 21:53:24 GMT
Message-Id: <5.2.0.9.2.20040119133320.02b04890@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 19 Jan 2004 13:38:20 -0800
To: Yakov Rekhter <yakov@juniper.net>
From: raymond zhang <zhangr@info.net>
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
Cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
In-Reply-To: <200401192059.i0JKx3h72761@merlot.juniper.net>
References: <Your message of "Fri, 16 Jan 2004 10:56:06 PST." <5.2.0.9.2.20040114153440.02a86a58@delta.info.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yakov,


At 12:59 PM 1/19/2004 -0800, Yakov Rekhter wrote:
>Raymond,
>
> > Hi Jim and Ed,
> >
> > Here is the most updated one.  Would you please initiate the WG last call
> > for this draft ?
>
>This draft still doesn't include some of the changes you agreed to make
>in your e-mail on Jan 12 (the e-mail is attached).
>
>Specifically, it doesn't include the changes you agreed to make
>to 5.1.5, and it didn't list forwarding plane overhead in the
>list of criteria in 6.2.

[snip..]
> >3. Section 6.2 ("Performance") should include control plane overhead
> >as one of the criteria. Ditto for data plane overhead.
>
>Will do, thanks.
[snip..]

I see... I interpreted "ditto" as "ok" above, meaning no additional changes 
required regarding data plane.

Can you propose some wording which can be incorporated into the final 
version after the last call commenting period ?

Regards,
Raymond




From owner-te-wg@ops.ietf.org  Mon Jan 19 17:08:19 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11029
	for <tewg-archive@lists.ietf.org>; Mon, 19 Jan 2004 17:08:19 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AihWV-000G5n-7q
	for te-wg-data@psg.com; Mon, 19 Jan 2004 22:05:31 +0000
Received: from [207.17.137.64] (helo=colo-dns-ext2.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AihWH-000G2a-7V
	for te-wg@ops.ietf.org; Mon, 19 Jan 2004 22:05:17 +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 i0JKx4Bm031624;
	Mon, 19 Jan 2004 12:59:04 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0JKx3h72761;
	Mon, 19 Jan 2004 12:59:03 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401192059.i0JKx3h72761@merlot.juniper.net>
To: zhangr@info.net
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen,
    Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
In-Reply-To: Your message of "Fri, 16 Jan 2004 10:56:06 PST."
             <5.2.0.9.2.20040114153440.02a86a58@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <59163.1074545943.1@juniper.net>
Date: Mon, 19 Jan 2004 12:59:03 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

> Hi Jim and Ed,
> 
> Here is the most updated one.  Would you please initiate the WG last call 
> for this draft ?

This draft still doesn't include some of the changes you agreed to make
in your e-mail on Jan 12 (the e-mail is attached).

Specifically, it doesn't include the changes you agreed to make
to 5.1.5, and it didn't list forwarding plane overhead in the
list of criteria in 6.2.

Yakov.
-----------------------------------------------------------------------
Date:    Mon, 12 Jan 2004 09:23:41 PST
To:      Yakov Rekhter <yakov@juniper.net>
cc:      Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
	 "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
From:    raymond zhang <zhangr@info.net>
Subject: Re: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-03.txt 

Hi Yakov,

Thanks for the additional input...

At 08:28 AM 1/12/2004 -0800, Yakov Rekhter wrote:
>Raymond,
>
> > Hi Jim and Ed,
> >
> > Happy new year !
> >
> > The following emails were sent to both of you nearly a month ago.  I am 
> not
> > sure if you are having problem receiving email again so I am copying Bert
> > and posting to the list also.
> >
> > The -03 version of the draft
> > 
> (http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-03.t
>xt)
> > is ready for last call as per our minutes from the Minneapolis meeting.
>
>I think that the latest version of the draft still require few
>changes/updates.
>
>1. The document should state up front the following:
>
>       This document doesn't make any claims with respect to whether
>       it is possible to have a practical solution that meets all the
>       requirements listed in this document.
>
>(That point have been discussed before, and I thought the authors
>agreed to include the above in the text, but I wasn't able to find
>it in the -03 version).

In section 6.1, I included wording "

If a solution can fulfill just a subset of those requirements in
    section 5, then it MUST be explicitly documented"

Would this reflect your point above ?


>2. From 5.1.5 ("Re-optimization"):
>
>    Once an inter-AS TE LSP has been established and should there be any
>    resource or other changes inside anyone of transiting ASes, the
>    solution MUST be able to re-optimize the LSP accordingly and
>    non-disruptively, either upon expiration of a configurable timer or
>    triggered by a network event or a manual request at the TE tunnel
>    Head-end.
>
>    The solution SHOULD provide an option for the Head-End LSRs to
>    control if re-optimizing or not should there exist a more optimal
>    path in one of the transit ASes along the inter-AS TE LSP path.
>
>The above it too restrictive, as it restricts re-optimization to
>only the case where resource changes are in the set of ASs (currently)
>transited by the LSP. To remove this restriction I'd like to propose the
>following replacement:
>
>    Once an inter-AS TE LSP has been established and should there be any
>    resource or other changes inside anyone of the ASes, the
>    solution MUST be able to re-optimize the LSP accordingly and
>    non-disruptively, either upon expiration of a configurable timer or
>    triggered by a network event or a manual request at the TE tunnel
>    Head-end.
>
>    The solution SHOULD provide an option for the Head-End LSRs to
>    control if re-optimizing or not should there exist a more optimal
>    path in one of the ASes.

"along the inter-AS TE LSP path" was left there by mistake, sorry...  As 
per our last discussion, the text should appear exactly the same as you 
proposed above.  Thanks for catching it !

>3. Section 6.2 ("Performance") should include control plane overhead
>as one of the criteria. Ditto for data plane overhead.

Will do, thanks.

>4. In 5.1.6 replace "CSPF" with "Path computation").

You meant 5.1.8 ?  Will do...

Cheers,
Raymond
>Yakov.





From owner-te-wg@ops.ietf.org  Tue Jan 20 04:50:10 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20619
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 04:50:10 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AisQG-0003by-6l
	for te-wg-data@psg.com; Tue, 20 Jan 2004 09:43:48 +0000
Received: from [144.254.74.5] (helo=ams-iport-1.cisco.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AisQ3-0003Xy-RE
	for te-wg@ops.ietf.org; Tue, 20 Jan 2004 09:43:35 +0000
Received: from cisco.com (144.254.74.60)
  by ams-iport-1.cisco.com with ESMTP; 20 Jan 2004 10:44:17 +0100
Received: from xbe-lon-302.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.12.2/8.12.6) with ESMTP id i0K9hBKl011039;
	Tue, 20 Jan 2004 10:43:12 +0100 (MET)
Received: from xbe-lon-313.cisco.com ([64.103.99.73]) by xbe-lon-302.cisco.com with Microsoft SMTPSVC(5.0.2195.5329);
	 Tue, 20 Jan 2004 09:43:31 +0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Progress on DS-TE
Date: Tue, 20 Jan 2004 09:43:30 -0000
Message-ID: <AC60B39EEE7320498063D37799FB82D9022B4F8E@xbe-lon-313.cisco.com>
Thread-Topic: Progress on DS-TE
Thread-Index: AcPJceLdJOdBY+j2TGi1Wtzmg9JPhAVwZN7w
From: "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>
To: "Ed Kern" <ejk@tech.org>, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Jim Boyle" <jboyle@pdnets.com>
Cc: <te-wg@ops.ietf.org>
X-OriginalArrivalTime: 20 Jan 2004 09:43:32.0071 (UTC) FILETIME=[DD9D4F70:01C3DF39]
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Ed, Jim, Bert,

The latest version of DSTE <-proto, -russian, -mam> have just been
posted and should be announced shortly. We believe they address all the
comments from the IESG Review, with resolution as discussed on the list.
I believe Jerry will also post DSTE <-mar> shortly.

Could you please move these documents forward towards their RFCization?

Thank you

Francois



From owner-te-wg@ops.ietf.org  Tue Jan 20 07:44:39 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26722
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 07:44:39 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AivBm-000LGm-3e
	for te-wg-data@psg.com; Tue, 20 Jan 2004 12:41:02 +0000
Received: from [193.205.242.5] (helo=nausicaa.coritel.it)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AivBL-000LD7-Ei; Tue, 20 Jan 2004 12:40:36 +0000
Received: from Poisson ([151.100.37.144])
	by nausicaa.coritel.it (8.11.2/8.11.2) with SMTP id i0KClWw02030;
	Tue, 20 Jan 2004 13:47:45 +0100
Message-ID: <00dd01c3df53$0d3a25a0$90256497@coritel>
From: "alessio d'achille" <dachille@coritel.it>
To: <ccamp@ops.ietf.org>
Cc: <te-wg@ops.ietf.org>
Subject: revised version of the draft
Date: Tue, 20 Jan 2004 13:43:25 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00D8_01C3DF5B.611526E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=0.2 required=5.0 tests=BAYES_44,HTML_FONTCOLOR_BLUE,
	HTML_MESSAGE autolearn=no version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00D8_01C3DF5B.611526E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi folks,=20

Wer have just submitted a revised version of our draft: =
<draft-dachille-inter-area-path-protection-01.txt>, since the previous =
version included few errors; you will find the new version soon, and we =
ask you to send your feedback to us about this new version and not about =
the previous one.

As Vishal said in a previous e-mail, we would be particularly interested =
in feedback from some of the principal WG members who are involved in =
the inter-AS/inter-area activity.

Best regards,=20

Alessio D'Achille=20

on behalf of Vishal Sharma, Marco Listanti, Fabio Ricciato, and Ugo =
monaco

------=_NextPart_000_00D8_01C3DF5B.611526E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi folks, </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Wer have just submitted a revised =
version of our=20
draft: &lt;draft-dachille-inter-area-path-protection-01.txt&gt;, since =
the=20
previous version included few errors; you will find the new version =
soon, and we=20
ask you to send your feedback to us about this new version and not about =
the=20
previous one.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>As Vishal said in a previous e-mail, =
we&nbsp;would=20
be particularly interested in feedback from some of the <FONT =
color=3D#0000ff=20
face=3DArial size=3D2><SPAN class=3D798550518-19012004><FONT =
color=3D#000000>principal=20
WG members who are involved in the inter-AS/inter-area=20
activity</FONT>.</SPAN></FONT></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><FONT color=3D#0000ff face=3DArial =
size=3D2><SPAN=20
class=3D798550518-19012004></SPAN></FONT></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Best regards, </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Alessio D'Achille </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>on behalf of Vishal Sharma, Marco =
Listanti, Fabio=20
Ricciato, and Ugo monaco</FONT></DIV></BODY></HTML>

------=_NextPart_000_00D8_01C3DF5B.611526E0--




From owner-te-wg@ops.ietf.org  Tue Jan 20 10:09:34 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02712
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 10:09:33 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AixRK-000BBt-OE
	for te-wg-data@psg.com; Tue, 20 Jan 2004 15:05:14 +0000
Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AixR6-000BA5-OE
	for te-wg@ops.ietf.org; Tue, 20 Jan 2004 15:05:00 +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 i0KF50l68403;
	Tue, 20 Jan 2004 07:05:00 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0KF4th63567;
	Tue, 20 Jan 2004 07:04:55 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401201504.i0KF4th63567@merlot.juniper.net>
To: raymond zhang <zhangr@info.net>
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
In-Reply-To: Your message of "Mon, 19 Jan 2004 13:38:20 PST."
             <5.2.0.9.2.20040119133320.02b04890@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <88099.1074611095.1@juniper.net>
Date: Tue, 20 Jan 2004 07:04:55 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

> Hi Yakov,
> 
> 
> At 12:59 PM 1/19/2004 -0800, Yakov Rekhter wrote:
> >Raymond,
> >
> > > Hi Jim and Ed,
> > >
> > > Here is the most updated one.  Would you please initiate the WG last call
> > > for this draft ?
> >
> >This draft still doesn't include some of the changes you agreed to make
> >in your e-mail on Jan 12 (the e-mail is attached).
> >
> >Specifically, it doesn't include the changes you agreed to make
> >to 5.1.5, and it didn't list forwarding plane overhead in the
> >list of criteria in 6.2.
> 
> [snip..]
> > >3. Section 6.2 ("Performance") should include control plane overhead
> > >as one of the criteria. Ditto for data plane overhead.
> >
> >Will do, thanks.
> [snip..]
> 
> I see... I interpreted "ditto" as "ok" above, meaning no additional changes 
> required regarding data plane.
> 
> Can you propose some wording which can be incorporated into the final 
> version after the last call commenting period ?

Here is the proposed text, although I think that the text has to be
incorporated *prior* (and not after) the last call commenting period.

In  5.1.5 replace
    Once an inter-AS TE LSP has been established and should there be any
    resource or other changes inside anyone of transiting ASes, the
    solution MUST be able to re-optimize the LSP accordingly and
    non-disruptively, either upon expiration of a configurable timer or
    triggered by a network event or a manual request at the TE tunnel
    Head-end.

    The solution SHOULD provide an option for the Head-End LSRs to
    control if re-optimizing or not should there exist a more optimal
    path in one of the transit ASes along the inter-AS TE LSP path.

with the following:
 
    Once an inter-AS TE LSP has been established and should there be any
    resource or other changes inside anyone of the ASes, the
    solution MUST be able to re-optimize the LSP accordingly and
    non-disruptively, either upon expiration of a configurable timer or
    triggered by a network event or a manual request at the TE tunnel
    Head-end.

    The solution SHOULD provide an option for the Head-End LSRs to
    control if re-optimizing or not should there exist a more optimal
    path in one of the ASes.

In 6.2 add the following:

    - Impact and scalability of the data/forwarding plane due to added
        overheads, etc.

Yakov.



From owner-te-wg@ops.ietf.org  Tue Jan 20 14:18:54 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16648
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 14:18:53 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1Aj1Ie-000CfC-Nn
	for te-wg-data@psg.com; Tue, 20 Jan 2004 19:12:32 +0000
Received: from [195.101.245.15] (helo=p-mail1.rd.francetelecom.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Aj1IQ-000CeE-FA
	for te-wg@ops.ietf.org; Tue, 20 Jan 2004 19:12:18 +0000
Received: from lanmhs30.rd.francetelecom.fr ([10.193.21.61]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(5.0.2195.6747);
	 Tue, 20 Jan 2004 20:12:05 +0100
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
Subject: Re : MPLS Inter-area TE requirement draft
Date: Tue, 20 Jan 2004 20:12:04 +0100
Message-ID: <B7D1592DFC5137478D0385A9595C45539561AB@lanmhs30.rd.francetelecom.fr>
Thread-Topic: Re : MPLS Inter-area TE requirement draft
Thread-Index: AcPPRhEx1wd9Fff/Rla7BDXgT0ohUAPcQEPAADMgCsA=
From: "LE ROUX Jean-Louis FTRD/DAC/LAN" <jeanlouis.leroux@rd.francetelecom.com>
To: "Jim Boyle" <jboyle@pdnets.com>
Cc: <te-wg@ops.ietf.org>, <ejk@tech.org>, <bwijnen@lucent.com>,
        <Raymond_Zhang@infonet.com>, "Kenji Kumaki" <ke-kumaki@kddi.com>,
        "Yuichi Ikejiri" <y.ikejiri@ntt.com>,
        "Parantap Lahiri" <parantap.lahiri@mci.com>, <ting_wo.chung@bell.ca>
X-OriginalArrivalTime: 20 Jan 2004 19:12:05.0476 (UTC) FILETIME=[4AC9D240:01C3DF89]
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Hi Jim,

Please find answer to your comments in the text.
(Apologize for this late answer)


> -----Message d'origine-----
> De : Jim Boyle [mailto:jboyle@pdnets.com]
> Envoy=E9 : mercredi 31 d=E9cembre 2003 03:30
> =C0 : Jean Philippe Vasseur
> Cc : te-wg@ops.ietf.org; ejk@tech.org; Jim Boyle;=20
> bwijnen@lucent.com; LE ROUX Jean-Louis FTRD/DAC/LAN;=20
> Raymond_Zhang@infonet.com; Kenji Kumaki; Yuichi Ikejiri;=20
> Parantap Lahiri; ting_wo.chung@bell.ca
> Objet : Re: MPLS Inter-area TE requirement draft
>=20
>=20
>=20
>=20
> Jean Philippe and Jean Louis,
>=20
> I have read the draft of you and your 6 co-authors, I am
> happy that you now also agree that inter-area is important to=20
> consider (especially if inter-as is!).  With 7 authors,=20
> including 2 editors, I am a bit amused that your references=20
> section seems out of sorts, you or your co-editor may want to=20
> cross-check them.  You may also want to take a look at the=20
> RFC editor's policy on Author overload:
>=20
	http://www.rfc-editor.org/policy.html#policy.authlist

Thanks, you are right, a contributor section will be added in next =
version.

>But some of the non-referenced references do actually hint at some of=20
>my concerns with
>the work that may lead out of inter-area and inter-as requirements.  As =
examples=20
>[BANDWIDTH-PROTECTION], [PATH-COMP], [OSPF-TE-CAP], [LOOSE-PATH-REOPT], =
[NODE-ID] and=20
>[INTER-AS-TE-LINK]. Specifically, I worry about loosely bounded =
extensions, some of which >may seriously limit practical scalability of =
use (or ease of operation/understanding).

This list just gives potential solution building blocks as illustration. =
We do not want to restrict the solution field.=20
But actually this is a good point, and we will remove any solution =
related reference in next version.

>I would like to work to bring our drafts together, however first I=20
>think there is a
>crucial difference between them, something perhaps that some list =
comment may shed light >on.

Actually, these differences motivated us to write a separate draft. =
Basically your draft appears too solution dependant, which is not really =
the goal of a reqs ID, isn't it ?=20
It seems that you recommand only crankback routing approach, precluding =
any other approach.=20
If we refer to section 3.1 "In overview, the requirements below call for =
what may be called a
   crankback method which employs head end direction for regional
   optimization"

In return our draft do not assume any solution, it just lists a set of =
functional requirements.

Crankback is a possible solution, that do not allow to find the optimal =
path, and that may face path setup time issues. PCS is another solution =
that is quite scalable and allows to find a constrained shortest path in =
a recursive manner thanks to light message exchange between ABRs.

Our draft do not recommend any particular solution and do not preclude =
any solution provided that it meets functional requirements that are =
mandatory (MUST).


>In mine, edge to edge optimality yields to scalability.  Solutions that =

>come to mind
>include standard crankback approaches.  LSPs are likely to be greedy =
within each region. =20
>In yours, it appears that scalability yields to optimality, or as =
another level of=20
>complexity, this is one possible mode.

Definitely no.=20
What we want to point out is that solutions allowing to compute an =
optimal path  may require more job on LSRs, but without necessarily =
impacting network scalability.

> Your path computation servers would seem one
>approach here, as these "straddle" and can bridge at least two areas,=20
>however this would
>seem to involve a round of coordination with the head end, and once an =
LSP goes across=20
>the second area into a third (Such as an edge to edge LSP would likely =
do), there is=20
>again a limited visibility that must be dealt with.

Basically PCS approach allows, IMHO, to find an e2e optimal path. This =
path is computed in a polynomial time, thanks to recursive computation =
on ABRs. Actually it requires only a light coordination between Head-End =
LSR, Head-End ABR and Tail-End ABR.
But all in all there is definitely no text on PCS in our draft! (except =
in the reference, we will remove it), so I don't really catch the issue =
here.

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

Hope this clarify possible misunderstanding
All in all, your draft also contains highly relevant points, =
(particularly a good analysis of current MPLS-TE uses
in section 1, that eases understanding of requirements in following =
sections),
and it appears, from a more recent mail you sent, that we are in strong =
aggreement
Thus, I think that it is now time to merge our proposals.

Best Regards,

JL




From owner-te-wg@ops.ietf.org  Tue Jan 20 14:47:27 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17481
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 14:47:27 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1Aj1ns-000Fpb-Ff
	for te-wg-data@psg.com; Tue, 20 Jan 2004 19:44:48 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Aj1nV-000Fmd-1T
	for te-wg@ops.ietf.org; Tue, 20 Jan 2004 19:44:25 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id i0KJhY6A028926;
	Tue, 20 Jan 2004 19:43:34 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id TAA18039;
	Tue, 20 Jan 2004 19:43:33 GMT
Message-Id: <5.2.0.9.2.20040120114029.021d82b0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Tue, 20 Jan 2004 11:43:26 -0800
To: Yakov Rekhter <yakov@juniper.net>
From: raymond zhang <zhangr@info.net>
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
Cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
In-Reply-To: <200401201504.i0KF4th63567@merlot.juniper.net>
References: <Your message of "Mon, 19 Jan 2004 13:38:20 PST." <5.2.0.9.2.20040119133320.02b04890@delta.info.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yakov,


At 07:04 AM 1/20/2004 -0800, Yakov Rekhter wrote:
>Raymond,
>
> > Hi Yakov,
> >
> >
> > At 12:59 PM 1/19/2004 -0800, Yakov Rekhter wrote:
> > >Raymond,
> > >
> > > > Hi Jim and Ed,
> > > >
> > > > Here is the most updated one.  Would you please initiate the WG 
> last call
> > > > for this draft ?
> > >
> > >This draft still doesn't include some of the changes you agreed to make
> > >in your e-mail on Jan 12 (the e-mail is attached).
> > >
> > >Specifically, it doesn't include the changes you agreed to make
> > >to 5.1.5, and it didn't list forwarding plane overhead in the
> > >list of criteria in 6.2.
> >
> > [snip..]
> > > >3. Section 6.2 ("Performance") should include control plane overhead
> > > >as one of the criteria. Ditto for data plane overhead.
> > >
> > >Will do, thanks.
> > [snip..]
> >
> > I see... I interpreted "ditto" as "ok" above, meaning no additional 
> changes
> > required regarding data plane.
> >
> > Can you propose some wording which can be incorporated into the final
> > version after the last call commenting period ?
>
>Here is the proposed text, although I think that the text has to be
>incorporated *prior* (and not after) the last call commenting period.

Surely.. I will post -05 for it.

>In  5.1.5 replace
>     Once an inter-AS TE LSP has been established and should there be any
>     resource or other changes inside anyone of transiting ASes, the
>     solution MUST be able to re-optimize the LSP accordingly and
>     non-disruptively, either upon expiration of a configurable timer or
>     triggered by a network event or a manual request at the TE tunnel
>     Head-end.
>
>     The solution SHOULD provide an option for the Head-End LSRs to
>     control if re-optimizing or not should there exist a more optimal
>     path in one of the transit ASes along the inter-AS TE LSP path.

This was the text in -03...  In -04, I have updated the text to the following:

"
The solution SHOULD provide an option for the Head-End LSRs to
    control if re-optimizing or not should there exist a more optimal
    path in one of the transit ASes."


>with the following:
>
>     Once an inter-AS TE LSP has been established and should there be any
>     resource or other changes inside anyone of the ASes, the
>     solution MUST be able to re-optimize the LSP accordingly and
>     non-disruptively, either upon expiration of a configurable timer or
>     triggered by a network event or a manual request at the TE tunnel
>     Head-end.
>
>     The solution SHOULD provide an option for the Head-End LSRs to
>     control if re-optimizing or not should there exist a more optimal
>     path in one of the ASes.

But I have not problem with proposed above either (one word difference 
"transit as")

>In 6.2 add the following:
>
>     - Impact and scalability of the data/forwarding plane due to added
>         overheads, etc.

thanks !

Cheers,
Raymond

>Yakov.





From owner-te-wg@ops.ietf.org  Tue Jan 20 15:06:30 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18103
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 15:06:30 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1Aj26L-000Ijq-Ha
	for te-wg-data@psg.com; Tue, 20 Jan 2004 20:03:53 +0000
Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Aj25x-000IeH-2L
	for te-wg@ops.ietf.org; Tue, 20 Jan 2004 20:03:29 +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 i0KK3Il69439;
	Tue, 20 Jan 2004 12:03:18 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0KK3Dh92189;
	Tue, 20 Jan 2004 12:03:13 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401202003.i0KK3Dh92189@merlot.juniper.net>
To: raymond zhang <zhangr@info.net>
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
In-Reply-To: Your message of "Tue, 20 Jan 2004 11:43:26 PST."
             <5.2.0.9.2.20040120114029.021d82b0@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <60587.1074628993.1@juniper.net>
Date: Tue, 20 Jan 2004 12:03:13 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

> > > At 12:59 PM 1/19/2004 -0800, Yakov Rekhter wrote:
> > > >Raymond,
> > > >
> > > > > Hi Jim and Ed,
> > > > >
> > > > > Here is the most updated one.  Would you please initiate the WG 
> > last call
> > > > > for this draft ?
> > > >
> > > >This draft still doesn't include some of the changes you agreed to make
> > > >in your e-mail on Jan 12 (the e-mail is attached).
> > > >
> > > >Specifically, it doesn't include the changes you agreed to make
> > > >to 5.1.5, and it didn't list forwarding plane overhead in the
> > > >list of criteria in 6.2.
> > >
> > > [snip..]
> > > > >3. Section 6.2 ("Performance") should include control plane overhead
> > > > >as one of the criteria. Ditto for data plane overhead.
> > > >
> > > >Will do, thanks.
> > > [snip..]
> > >
> > > I see... I interpreted "ditto" as "ok" above, meaning no additional 
> > changes
> > > required regarding data plane.
> > >
> > > Can you propose some wording which can be incorporated into the final
> > > version after the last call commenting period ?
> >
> >Here is the proposed text, although I think that the text has to be
> >incorporated *prior* (and not after) the last call commenting period.
> 
> Surely.. I will post -05 for it.
> 
> >In  5.1.5 replace
> >     Once an inter-AS TE LSP has been established and should there be any
> >     resource or other changes inside anyone of transiting ASes, the
> >     solution MUST be able to re-optimize the LSP accordingly and
> >     non-disruptively, either upon expiration of a configurable timer or
> >     triggered by a network event or a manual request at the TE tunnel
> >     Head-end.
> >
> >     The solution SHOULD provide an option for the Head-End LSRs to
> >     control if re-optimizing or not should there exist a more optimal
> >     path in one of the transit ASes along the inter-AS TE LSP path.
> 
> This was the text in -03...  In -04, I have updated the text to the following
:
> 
> "
> The solution SHOULD provide an option for the Head-End LSRs to
>     control if re-optimizing or not should there exist a more optimal
>     path in one of the transit ASes."
> 
> 
> >with the following:
> >
> >     Once an inter-AS TE LSP has been established and should there be any
> >     resource or other changes inside anyone of the ASes, the
> >     solution MUST be able to re-optimize the LSP accordingly and
> >     non-disruptively, either upon expiration of a configurable timer or
> >     triggered by a network event or a manual request at the TE tunnel
> >     Head-end.
> >
> >     The solution SHOULD provide an option for the Head-End LSRs to
> >     control if re-optimizing or not should there exist a more optimal
> >     path in one of the ASes.
> 
> But I have not problem with proposed above either (one word difference 
> "transit as")

Great !!!

> >In 6.2 add the following:
> >
> >     - Impact and scalability of the data/forwarding plane due to added
> >         overheads, etc.
> 
> thanks !

Looking forward for the -05 version.

Yakov.



From owner-te-wg@ops.ietf.org  Tue Jan 20 19:00:50 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02194
	for <tewg-archive@lists.ietf.org>; Tue, 20 Jan 2004 19:00:49 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1Aj5jR-000IvD-DR
	for te-wg-data@psg.com; Tue, 20 Jan 2004 23:56:29 +0000
Received: from [192.128.166.71] (helo=almso2.proxy.att.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Aj5jE-000Iu9-Jr
	for te-wg@ops.ietf.org; Tue, 20 Jan 2004 23:56:16 +0000
Received: from attrh5i.attrh.att.com ([135.38.62.12])
	by almso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id i0KNu5Jg017604
	for <te-wg@ops.ietf.org>; Tue, 20 Jan 2004 18:56:16 -0500
Received: from KCCLUST06EVS1.ugd.att.com (135.38.164.89) by attrh5i.attrh.att.com (6.5.032)
        id 400ABCEB00113618; Tue, 20 Jan 2004 18:55:48 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Progress on DS-TE
Date: Tue, 20 Jan 2004 17:56:15 -0600
Message-ID: <9473683187ADC049A855ED2DA739ABCA02BA3836@KCCLUST06EVS1.ugd.att.com>
Thread-Topic: Progress on DS-TE
Thread-Index: AcPJceLdJOdBY+j2TGi1Wtzmg9JPhAVwZN7wAB846AA=
From: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>
To: "Ed Kern" <ejk@tech.org>, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        "Jim Boyle" <jboyle@pdnets.com>
Cc: "Ash, Gerald R (Jerry), ALABS" <gash@att.com>,
        "Francois Le Faucheur (flefauch)" <flefauch@cisco.com>,
        <te-wg@ops.ietf.org>
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.6 required=5.0 tests=BAYES_00,DNS_FROM_RFCI_DSN 
	autolearn=no version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk
Content-Transfer-Encoding: quoted-printable

Ed, Jim, Bert,

The latest version of DSTE <-mar> has been posted and should be =
announced shortly.  It incorporates comments based on the IESG Review, =
with resolution as discussed on the list.

Please also move this document forward towards RFCization.

Thanks,
Jerry

-----Original Message-----
From: Francois Le Faucheur (flefauch) [mailto:flefauch@cisco.com]
Sent: Tuesday, January 20, 2004 4:44 AM
To: Ed Kern; Wijnen, Bert (Bert); Jim Boyle
Cc: te-wg@ops.ietf.org
Subject: Progress on DS-TE

Ed, Jim, Bert,

The latest version of DSTE <-proto, -russian, -mam> have just been
posted and should be announced shortly. We believe they address all the
comments from the IESG Review, with resolution as discussed on the list.
I believe Jerry will also post DSTE <-mar> shortly.

Could you please move these documents forward towards their RFCization?

Thank you

Francois




From owner-te-wg@ops.ietf.org  Wed Jan 21 16:32:21 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10011
	for <tewg-archive@lists.ietf.org>; Wed, 21 Jan 2004 16:32:20 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AjPrL-000PAn-VJ
	for te-wg-data@psg.com; Wed, 21 Jan 2004 21:25:59 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AjPr9-000P9i-IH
	for te-wg@ops.ietf.org; Wed, 21 Jan 2004 21:25:47 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09364;
	Wed, 21 Jan 2004 16:25:45 -0500 (EST)
Message-Id: <200401212125.QAA09364@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-proto-06.txt
Date: Wed, 21 Jan 2004 16:25:44 -0500
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
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		: Protocol extensions for support of Diff-Serv-aware MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur
	Filename	: draft-ietf-tewg-diff-te-proto-06.txt
	Pages		: 31
	Date		: 2004-1-21
	
This document specifies the protocol extensions for support of 
  Differentiated-Service-aware MPLS Traffic Engineering (DS-TE). This 
  includes generalization of the semantic of a number of IGP extensions 
  already defined for existing MPLS Traffic Engineering in RFC3630 and 
  RFC-TBD as well as additional IGP extensions beyond those. This also 
  includes extensions to RSVP-TE signaling beyond those already 
  specified in RFC3209 for existing MPLS Traffic Engineering. These 
  extensions address the Requirements for DS-TE spelt out in RFC3564.

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

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-proto-06.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Jan 21 16:32:51 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10032
	for <tewg-archive@lists.ietf.org>; Wed, 21 Jan 2004 16:32:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AjPrc-000PEE-U0
	for te-wg-data@psg.com; Wed, 21 Jan 2004 21:26:16 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AjPrG-000PAP-Ki
	for te-wg@ops.ietf.org; Wed, 21 Jan 2004 21:25:54 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09382;
	Wed, 21 Jan 2004 16:25:52 -0500 (EST)
Message-Id: <200401212125.QAA09382@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-05.txt
Date: Wed, 21 Jan 2004 16:25:51 -0500
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
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-05.txt
	Pages		: 11
	Date		: 2004-1-21
	
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-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-diff-te-russian-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-diff-te-russian-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:	<2004-1-21164057.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Jan 21 16:33:21 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10088
	for <tewg-archive@lists.ietf.org>; Wed, 21 Jan 2004 16:33:20 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AjPr8-000P9Z-7c
	for te-wg-data@psg.com; Wed, 21 Jan 2004 21:25:46 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AjPqv-000P8W-Sb
	for te-wg@ops.ietf.org; Wed, 21 Jan 2004 21:25:34 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09332;
	Wed, 21 Jan 2004 16:25:31 -0500 (EST)
Message-Id: <200401212125.QAA09332@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-mam-02.txt
Date: Wed, 21 Jan 2004 16:25:31 -0500
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
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		: Maximum Allocation Bandwidth Constraints Model for   
			  Diff-Serv-aware MPLS Traffic Engineering
	Author(s)	: F. Le Faucheur, W. Lai
	Filename	: draft-ietf-tewg-diff-te-mam-02.txt
	Pages		: 11
	Date		: 2004-1-21
	
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-ietf-tewg-diff-te-mam-02.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-mam-02.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-mam-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  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:	<2004-1-21164029.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-diff-te-mam-02.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Jan 21 16:33:51 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10116
	for <tewg-archive@lists.ietf.org>; Wed, 21 Jan 2004 16:33:50 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AjPqT-000P5u-Kd
	for te-wg-data@psg.com; Wed, 21 Jan 2004 21:25:05 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AjPqF-000P4V-EI
	for te-wg@ops.ietf.org; Wed, 21 Jan 2004 21:24:51 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09292;
	Wed, 21 Jan 2004 16:24:48 -0500 (EST)
Message-Id: <200401212124.QAA09292@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-diff-te-mar-03.txt
Date: Wed, 21 Jan 2004 16:24:48 -0500
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Max Allocation with Reservation Bandwidth Constraint 
			  Model for MPLS/DiffServ TE & Performance Comparisons
	Author(s)	: J. Ash
	Filename	: draft-ietf-tewg-diff-te-mar-03.txt
	Pages		: 0
	Date		: 2004-1-21
	
This document complements the DiffServ-aware MPLS TE (DS-TE) requirements document by giving a functional specification for the Maximum Allocation with Reservation (MAR) Bandwidth Constraints Model. Assumptions, applicability, and examples of the operation of the MAR Bandwidth Constraints Model are presented.  MAR performance is analyzed relative to the criteria for selecting a Bandwidth Constraints Model, in order to provide guidance to user implementation of the model in their networks.

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

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

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

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-tewg-diff-te-mar-03.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:	<2004-1-21164021.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Wed Jan 21 16:34:20 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10163
	for <tewg-archive@lists.ietf.org>; Wed, 21 Jan 2004 16:34:20 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AjPru-000PEy-8P
	for te-wg-data@psg.com; Wed, 21 Jan 2004 21:26:34 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AjPr3-000P95-0o
	for te-wg@ops.ietf.org; Wed, 21 Jan 2004 21:25:41 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09348;
	Wed, 21 Jan 2004 16:25:38 -0500 (EST)
Message-Id: <200401212125.QAA09348@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-interas-mpls-te-req-05.txt
Date: Wed, 21 Jan 2004 16:25:38 -0500
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
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		: MPLS Inter-AS Traffic Engineering requirements
	Author(s)	: R. Zhang, J. Vasseur
	Filename	: draft-ietf-tewg-interas-mpls-te-req-05.txt
	Pages		: 26
	Date		: 2004-1-21
	
This document discusses requirements for the support of inter-AS
MPLS Traffic Engineering (MPLS TE).  The main objective of this
document is to present a set of requirements which would result in
a set of general guidelines in the definition, selection and
specification development for any technical solution(s) meeting
these requirements.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-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-interas-mpls-te-req-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-interas-mpls-te-req-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:	<2004-1-21164039.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-tewg-interas-mpls-te-req-05.txt

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Fri Jan 23 16:10:31 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23021
	for <tewg-archive@lists.ietf.org>; Fri, 23 Jan 2004 16:10:29 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1Ak8QY-000I57-VD
	for te-wg-data@psg.com; Fri, 23 Jan 2004 21:01:18 +0000
Received: from [132.151.1.176] (helo=ietf.org)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Ak8QM-000I4E-7V
	for te-wg@ops.ietf.org; Fri, 23 Jan 2004 21:01:06 +0000
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22345;
	Fri, 23 Jan 2004 16:01:03 -0500 (EST)
Message-Id: <200401232101.QAA22345@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: te-wg@ops.ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-tewg-diff-te-mar-04.txt
Date: Fri, 23 Jan 2004 16:01:02 -0500
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

--NextPart

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

	Title		: Max Allocation with Reservation Bandwidth Constraint 
			  Model for MPLS/DiffServ TE & Performance Comparisons
	Author(s)	: J. Ash
	Filename	: draft-ietf-tewg-diff-te-mar-04.txt
	Pages		: 18
	Date		: 2004-1-23
	
This document complements the DiffServ-aware MPLS TE (DS-TE) requirements document by giving a functional specification for the Maximum Allocation with Reservation (MAR) Bandwidth Constraints Model. Assumptions, applicability, and examples of the operation of the MAR Bandwidth Constraints Model are presented.  MAR performance is analyzed relative to the criteria for selecting a Bandwidth Constraints Model, in order to provide guidance to user implementation of the model in their networks.

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--





From owner-te-wg@ops.ietf.org  Sun Jan 25 11:17: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 LAA09342
	for <tewg-archive@lists.ietf.org>; Sun, 25 Jan 2004 11:17:34 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AkmqS-000PMq-0O
	for te-wg-data@psg.com; Sun, 25 Jan 2004 16:10:44 +0000
Received: from [171.71.176.72] (helo=sj-iport-3.cisco.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1AkmqF-000PLj-1L
	for te-wg@ops.ietf.org; Sun, 25 Jan 2004 16:10:31 +0000
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-3.cisco.com with ESMTP; 25 Jan 2004 08:15:24 +0000
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by sj-core-1.cisco.com (8.12.9/8.12.6) with ESMTP id i0PGASNM016248;
	Sun, 25 Jan 2004 08:10:29 -0800 (PST)
Received: from jvasseur-w2k01.cisco.com (che-vpn-cluster-1-155.cisco.com [10.86.240.155]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA03013; Sun, 25 Jan 2004 08:10:27 -0800 (PST)
Message-Id: <4.3.2.7.2.20040125110606.057cbb20@wells.cisco.com>
X-Sender: jvasseur@wells.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Sun, 25 Jan 2004 11:10:26 -0500
To: Jim Boyle <jboyle@pdnets.com>, ejk@tech.org, bwijnen@lucent.com
From: Jean Philippe Vasseur <jvasseur@cisco.com>
Subject: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt
Cc: te-wg@ops.ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Jim and Ed,

Right after the last IETF, several months ago, we tried to make everything 
possible to conclude the work on the inter-AS TE requirements draft, as 
requested by Bert. As you noticed, we produced several releases since then, 
incorporating all the comments that we received on the list. Despite 
several requests for last call we never received any answer from you: could 
you please let us know whether we can proceed for last call ?

Many thanks.

JP.

>Date: Fri, 16 Jan 2004 13:53:24 -0500
>To: Jim Boyle <jboyle@pdnets.com>, ejk@tech.org
>From: Jean Philippe Vasseur <jvasseur@cisco.com>
>Subject: Fwd: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt
>Cc: te-wg@ops.ietf.org
>
>Hi Jim and Ed,
>
>As already pointed out by Raymond in several emails, may we now proceed to 
>last call, as agreed a few months ago during the last IETF ? This last 
>revision incorporate all the comments we received.
>
>Thanks.
>
>JP.
>
>>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-interas-mpls-te-req-04.txt
>>Date: Wed, 14 Jan 2004 15:54:36 -0500
>>X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on psg.com
>>X-Spam-Status: No, hits=-4.2 required=5.0 tests=BAYES_00,MIME_BOUND_NEXTPART,
>>         NO_REAL_NAME autolearn=no version=2.60
>>Sender: owner-te-wg@ops.ietf.org
>>
>>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           : MPLS Inter-AS Traffic Engineering requirements
>>         Author(s)       : R. Zhang, J. Vasseur
>>         Filename        : draft-ietf-tewg-interas-mpls-te-req-04.txt
>>         Pages           : 26
>>         Date            : 2004-1-14
>>
>>This document discusses requirements for the support of inter-AS
>>MPLS Traffic Engineering (MPLS TE).  The main objective of this
>>document is to present a set of requirements which would result in
>>a set of general guidelines in the definition, selection and
>>specification development for any technical solution(s) meeting
>>these requirements.
>>
>>A URL for this Internet-Draft is:
>>http://www.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-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-interas-mpls-te-req-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-interas-mpls-te-req-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.
>>Content-Type: text/plain
>>Content-ID:     <2004-1-14161529.I-D@ietf.org>
>>
>>ENCODING mime
>>FILE /internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt
>>
>><ftp://ftp.ietf.org/internet-drafts/draft-ietf-tewg-interas-mpls-te-req-04.txt>




From owner-te-wg@ops.ietf.org  Mon Jan 26 10:20:06 2004
Received: from psg.com (mailnull@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09331
	for <tewg-archive@lists.ietf.org>; Mon, 26 Jan 2004 10:20:06 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1Al8Qg-0001iT-LT
	for te-wg-data@psg.com; Mon, 26 Jan 2004 15:13:34 +0000
Received: from [207.17.137.57] (helo=colo-dns-ext1.juniper.net)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Al8QT-0001hi-Is
	for te-wg@ops.ietf.org; Mon, 26 Jan 2004 15:13:21 +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 i0QFDKl95739;
	Mon, 26 Jan 2004 07:13:20 -0800 (PST)
	(envelope-from yakov@juniper.net)
Received: from juniper.net (garnet.juniper.net [172.17.28.17])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id i0QFDFh75318;
	Mon, 26 Jan 2004 07:13:15 -0800 (PST)
	(envelope-from yakov@juniper.net)
Message-Id: <200401261513.i0QFDFh75318@merlot.juniper.net>
To: raymond zhang <zhangr@info.net>
cc: Jim Boyle <jboyle@pdnets.com>, Ed Kern <ejk@tech.org>,
        "Wijnen, Bert (Bert)" <bwijnen@lucent.com>, te-wg@ops.ietf.org
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
In-Reply-To: Your message of "Tue, 20 Jan 2004 11:43:26 PST."
             <5.2.0.9.2.20040120114029.021d82b0@delta.info.net> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20860.1075129995.1@juniper.net>
Date: Mon, 26 Jan 2004 07:13:15 -0800
From: Yakov Rekhter <yakov@juniper.net>
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Raymond,

[clipped..]

> > > Can you propose some wording which can be incorporated into the final
> > > version after the last call commenting period ?
> >
> >Here is the proposed text, although I think that the text has to be
> >incorporated *prior* (and not after) the last call commenting period.
> 
> Surely.. I will post -05 for it.
> 
> >In  5.1.5 replace
> >     Once an inter-AS TE LSP has been established and should there be any
> >     resource or other changes inside anyone of transiting ASes, the
> >     solution MUST be able to re-optimize the LSP accordingly and
> >     non-disruptively, either upon expiration of a configurable timer or
> >     triggered by a network event or a manual request at the TE tunnel
> >     Head-end.
> >
> >     The solution SHOULD provide an option for the Head-End LSRs to
> >     control if re-optimizing or not should there exist a more optimal
> >     path in one of the transit ASes along the inter-AS TE LSP path.
> > 
> >with the following:
> >
> >     Once an inter-AS TE LSP has been established and should there be any
> >     resource or other changes inside anyone of the ASes, the
> >     solution MUST be able to re-optimize the LSP accordingly and
> >     non-disruptively, either upon expiration of a configurable timer or
> >     triggered by a network event or a manual request at the TE tunnel
> >     Head-end.
> >
> >     The solution SHOULD provide an option for the Head-End LSRs to
> >     control if re-optimizing or not should there exist a more optimal
> >     path in one of the ASes.

I am quite suprprised (to say the least) that after you agreed with
the change I proposed to 5.1.5, the -05 version still has doesn't fully 
incorporate that change. Specifically, the first sentence in 5.1.5 is 
still from the old text. 

Yakov.



From owner-te-wg@ops.ietf.org  Wed Jan 28 14:00: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 OAA20313
	for <tewg-archive@lists.ietf.org>; Wed, 28 Jan 2004 14:00:14 -0500 (EST)
Received: from lserv by psg.com with local (Exim 4.30; FreeBSD)
	id 1AlupA-000N3Z-Ll
	for te-wg-data@psg.com; Wed, 28 Jan 2004 18:54:04 +0000
Received: from [192.157.130.21] (helo=sa.infonet.com)
	by psg.com with esmtp (Exim 4.24; FreeBSD)
	id 1Aluow-000N0p-F4
	for te-wg@ops.ietf.org; Wed, 28 Jan 2004 18:53:50 +0000
Received: from delta.info.net (delta.info.net [192.237.125.34])
	by sa.infonet.com  with ESMTP id i0SIrnY7007712;
	Wed, 28 Jan 2004 18:53:49 GMT
Received: from zhangr2.info.net (sfjl114.us.info.net [204.79.139.114])
	by delta.info.net  with ESMTP id SAA14205;
	Wed, 28 Jan 2004 18:53:48 GMT
Message-Id: <5.2.0.9.2.20040128105059.02b658b0@delta.info.net>
X-Sender: zhangr@delta.info.net
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Wed, 28 Jan 2004 10:53:42 -0800
To: Yakov Rekhter <yakov@juniper.net>
From: raymond zhang <zhangr@info.net>
Subject: Re: I-D ACTION:draft-ietf-tewg-interas-mpls-te-req-04.txt 
Cc: Yakov Rekhter <yakov@juniper.net>, te-wg@ops.ietf.org
In-Reply-To: <200401281800.i0SI07h87751@merlot.juniper.net>
References: <Your message of "Mon, 26 Jan 2004 09:17:39 PST." <5.2.0.9.2.20040126091555.00af8420@delta.info.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Checker-Version: SpamAssassin 2.61 (1.212.2.1-2003-12-09-exp) on 
	psg.com
X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham 
	version=2.61
Sender: owner-te-wg@ops.ietf.org
Precedence: bulk

Hi Yakov,

[snip...]
 > >
> > >I am quite suprprised (to say the least) that after you agreed with
> > >the change I proposed to 5.1.5, the -05 version still has doesn't fully
> > >incorporate that change. Specifically, the first sentence in 5.1.5 is
> > >still from the old text.
> >
> > Sorry I was travelling in the past a couple of days.
> >
> > Now I must apologize.  Did not notice the "transiting" in the first
> > paragraph in the proposed text, tho I did remove the one in the 2nd
> > paragraph.  Sorry.  I will post -06 version for it.
> >
> > Attached pls find the -v06 and it would be great if you could look it over
> > before I post.
>
>Looks fine. Please post it asap, so that we could proceed to the Last Call.

Ok... Just posted -06.

Regards,
Raymond
P.S. I also cc-ed the list which I forgot to do previously...

>Yakov.





