
From daniel@olddog.co.uk  Mon Oct 11 14:27:07 2010
Return-Path: <daniel@olddog.co.uk>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32BA43A6B83 for <pce@core3.amsl.com>; Mon, 11 Oct 2010 14:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.457
X-Spam-Level: 
X-Spam-Status: No, score=-101.457 tagged_above=-999 required=5 tests=[AWL=0.542, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X6LfZfMdcTPE for <pce@core3.amsl.com>; Mon, 11 Oct 2010 14:27:05 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by core3.amsl.com (Postfix) with ESMTP id 5F38E3A6864 for <pce@ietf.org>; Mon, 11 Oct 2010 14:27:05 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id o9BLSBoI028064;  Mon, 11 Oct 2010 22:28:11 +0100
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id o9BLSAHN028051;  Mon, 11 Oct 2010 22:28:10 +0100
From: "Daniel King" <daniel@olddog.co.uk>
To: <pce@ietf.org>
References: <20100712211504.475353A6B87@core3.amsl.com> <000a01cb228c$3063be00$912b3a00$@co.uk>
In-Reply-To: <000a01cb228c$3063be00$912b3a00$@co.uk>
Date: Mon, 11 Oct 2010 22:28:10 +0100
Message-ID: <002401cb698b$34d499f0$9e7dcdd0$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-language: en-gb
Thread-index: AcsiB1gy1yNkkxn2TLqyRySj2G/lMQAhC1XQEb+bJBA=
x-cr-hashedpuzzle: C4FB Ippd O8IP P7kV SedN Vvy+ XTpO Yz0h Z6ke mMqn oGXf xfUt y4zh 9/us +Fb0 /RXN; 7; ZABhAG4AaQBlAGwAQABvAGwAZABkAG8AZwAuAGMAbwAuAHUAawA7AGYAagBqAGMAQAB0AGkAZAAuAGUAcwA7AGoAdQBsAGkAZQBuAC4AbQBlAHUAcgBpAGMAQABvAHIAYQBuAGcAZQAtAGYAdABnAHIAbwB1AHAALgBjAG8AbQA7AG8AZwBvAG4AZABpAG8AQAB0AGkAZAAuAGUAcwA7AG8AbABpAHYAaQBlAHIALgBkAHUAZwBlAG8AbgBAAG8AcgBhAG4AZwBlAC0AZgB0AGcAcgBvAHUAcAAuAGMAbwBtADsAcABjAGUAQABpAGUAdABmAC4AbwByAGcAOwBxAHoAaABhAG8AQABoAHUAYQB3AGUAaQAuAGMAbwBtAA==; Sosha1_v1; 7; {8165D219-7639-417B-B8A0-E0E901207752}; ZABhAG4AaQBlAGwAQABvAGwAZABkAG8AZwAuAGMAbwAuAHUAawA=; Mon, 11 Oct 2010 21:27:59 GMT; SQAtAEQAIABBAGMAdABpAG8AbgA6AGQAcgBhAGYAdAAtAGsAaQBuAGcALQBwAGMAZQAtAGkAbgB0AGUAcgAtAGEAcgBlAGEALQBhAHMALQBhAHAAcABsAGkAYwBhAGIAaQBsAGkAdAB5AC0AMAAyAC4AdAB4AHQA
x-cr-puzzleid: {8165D219-7639-417B-B8A0-E0E901207752}
Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com
Subject: [Pce] I-D Action:draft-king-pce-inter-area-as-applicability-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Oct 2010 21:27:07 -0000

Hi PCE'rs, 

Please find a new version of our pce-inter-area-as-applicability draft: 

http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt

This document examines the applicability of the PCE architecture, protocols,
and protocol extensions for computing multi-area and multi-AS paths in MPLS
and GMPLS networks.

This revision combines the addition of new co-authors and various updates
including:

- Discussion on domain meshes. 
- Discussion on route diversity. 
- Discussion on synchronized path computations. 
- Minor readability updates. 
- Minor grammar and nit fixes.

The document is not complete and will require further revisions. It is
however a good platform to build upon and as always we seek WG feedback and
suggestions.

See you in Beijing!
	
Br, Dan


From jpv@cisco.com  Tue Oct 12 12:49:14 2010
Return-Path: <jpv@cisco.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 431C63A6A5E for <pce@core3.amsl.com>; Tue, 12 Oct 2010 12:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.949
X-Spam-Level: 
X-Spam-Status: No, score=-109.949 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VG7Q92rDgq02 for <pce@core3.amsl.com>; Tue, 12 Oct 2010 12:49:13 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 399EC3A6996 for <pce@ietf.org>; Tue, 12 Oct 2010 12:49:13 -0700 (PDT)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMdYtEyrR7Ht/2dsb2JhbAChXXGiUJ0AhUgEikGDCQ
X-IronPort-AV: E=Sophos;i="4.57,321,1283731200";  d="scan'208,217";a="602929711"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 12 Oct 2010 19:50:28 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o9CJoR3X023619; Tue, 12 Oct 2010 19:50:27 GMT
Received: from xfe-ams-202.cisco.com ([144.254.231.96]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 12 Oct 2010 21:50:26 +0200
Received: from ams-emgil-871.cisco.com ([10.61.86.203]) by xfe-ams-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 12 Oct 2010 21:50:26 +0200
From: JP Vasseur <jpv@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-160--631820371
Date: Tue, 12 Oct 2010 21:50:24 +0200
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk>
To: pce@ietf.org
Message-Id: <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
X-Mailer: Apple Mail (2.1081)
X-OriginalArrivalTime: 12 Oct 2010 19:50:26.0114 (UTC) FILETIME=[B7071220:01CB6A46]
Cc: olivier.dugeon@orange-ftgroup.com, Quintin Zhao <qzhao@huawei.com>, fjjc@tid.es
Subject: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 19:49:14 -0000

--Apple-Mail-160--631820371
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks Dan for this new revision. Major progress, thanks, this is part =
of our milstones, good to see
some progress. Even if there is lot of work to do on this ID, this is =
probably a good time to poll the=20
WG to adopt it as the base document for inter-area-as applicability.

All, are you in favor/opposed in adopting =
draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
document ?

Thanks.

JP.

Begin forwarded message:

> From: "Daniel King" <daniel@olddog.co.uk>
> Date: October 11, 2010 11:28:10 PM GMT+02:00
> To: <pce@ietf.org>
> Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com
> Subject: [Pce] I-D =
Action:draft-king-pce-inter-area-as-applicability-02.txt
>=20
> Hi PCE'rs,=20
>=20
> Please find a new version of our pce-inter-area-as-applicability =
draft:=20
>=20
> =
http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt
>=20
> This document examines the applicability of the PCE architecture, =
protocols,
> and protocol extensions for computing multi-area and multi-AS paths in =
MPLS
> and GMPLS networks.
>=20
> This revision combines the addition of new co-authors and various =
updates
> including:
>=20
> - Discussion on domain meshes.=20
> - Discussion on route diversity.=20
> - Discussion on synchronized path computations.=20
> - Minor readability updates.=20
> - Minor grammar and nit fixes.
>=20
> The document is not complete and will require further revisions. It is
> however a good platform to build upon and as always we seek WG =
feedback and
> suggestions.
>=20
> See you in Beijing!
> =09
> Br, Dan
>=20
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


--Apple-Mail-160--631820371
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Thanks Dan for this new revision. Major progress, thanks, this is part =
of our milstones, good to see<div>some progress. Even if there is lot of =
work to do on this ID, this is probably a good time to poll =
the&nbsp;</div><div>WG to adopt it as the base document for =
inter-area-as applicability.</div><div><br></div><div>All, are you in =
favor/opposed in =
adopting&nbsp;draft-king-pce-inter-area-as-applicability-02.txt as a PCE =
Wg</div><div>document =
?</div><div><br></div><div>Thanks.</div><div><br></div><div>JP.</div><div>=
<div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">"Daniel King" =
&lt;<a =
href=3D"mailto:daniel@olddog.co.uk">daniel@olddog.co.uk</a>&gt;<br></span>=
</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">October 11, 2010 =
11:28:10 PM GMT+02:00<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">&lt;<a =
href=3D"mailto:pce@ietf.org">pce@ietf.org</a>&gt;<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:olivier.dugeon@orange-ftgroup.com">olivier.dugeon@orange-ft=
group.com</a>, <a href=3D"mailto:fjjc@tid.es">fjjc@tid.es</a>, <a =
href=3D"mailto:qzhao@huawei.com">qzhao@huawei.com</a><br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>[Pce] I-D =
Action:draft-king-pce-inter-area-as-applicability-02.txt</b><br></span></d=
iv><br><div>Hi PCE'rs, <br><br>Please find a new version of our =
pce-inter-area-as-applicability draft: <br><br><a =
href=3D"http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-=
02.txt">http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-=
02.txt</a><br><br>This document examines the applicability of the PCE =
architecture, protocols,<br>and protocol extensions for computing =
multi-area and multi-AS paths in MPLS<br>and GMPLS networks.<br><br>This =
revision combines the addition of new co-authors and various =
updates<br>including:<br><br>- Discussion on domain meshes. <br>- =
Discussion on route diversity. <br>- Discussion on synchronized path =
computations. <br>- Minor readability updates. <br>- Minor grammar and =
nit fixes.<br><br>The document is not complete and will require further =
revisions. It is<br>however a good platform to build upon and as always =
we seek WG feedback and<br>suggestions.<br><br>See you in =
Beijing!<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><br>Br, =
Dan<br><br>_______________________________________________<br>Pce =
mailing =
list<br>Pce@ietf.org<br>https://www.ietf.org/mailman/listinfo/pce<br></div=
></blockquote></div><br></div></body></html>=

--Apple-Mail-160--631820371--

From jpv@cisco.com  Tue Oct 12 14:42:04 2010
Return-Path: <jpv@cisco.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B6413A6A9E for <pce@core3.amsl.com>; Tue, 12 Oct 2010 14:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.949
X-Spam-Level: 
X-Spam-Status: No, score=-105.949 tagged_above=-999 required=5 tests=[AWL=-3.951, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5YIaedyOsksw for <pce@core3.amsl.com>; Tue, 12 Oct 2010 14:42:01 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 26C953A6A87 for <pce@ietf.org>; Tue, 12 Oct 2010 14:42:00 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0EAENztEyQ/khLgWdsb2JhbAChXxUBAQsLIiKhRZ0AhUgEikGDCQ
X-IronPort-AV: E=Sophos;i="4.57,322,1283731200"; d="scan'208,217";a="11193891"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 12 Oct 2010 21:43:14 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9CLhEJO011820; Tue, 12 Oct 2010 21:43:14 GMT
Received: from xfe-ams-102.cisco.com ([144.254.231.94]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 12 Oct 2010 23:43:14 +0200
Received: from ams-emgil-871.cisco.com ([10.61.86.203]) by xfe-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 12 Oct 2010 23:43:13 +0200
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: multipart/alternative; boundary=Apple-Mail-4--625052548
From: JP Vasseur <jpv@cisco.com>
In-Reply-To: <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
Date: Tue, 12 Oct 2010 23:43:12 +0200
Message-Id: <653C7AD5-C6EA-4AC5-AE65-8CB95174AEE8@cisco.com>
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
To: pce@ietf.org
X-Mailer: Apple Mail (2.1081)
X-OriginalArrivalTime: 12 Oct 2010 21:43:13.0890 (UTC) FILETIME=[78EFBC20:01CB6A56]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.500.1024-17700.000
X-TM-AS-Result: No--30.275700-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, Quintin Zhao <qzhao@huawei.com>
Subject: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document ??
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Oct 2010 21:42:04 -0000

--Apple-Mail-4--625052548
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Oct 12, 2010, at 9:50 PM, JP Vasseur wrote:

> Thanks Dan for this new revision. Major progress, thanks, this is part =
of our milstones, good to see
> some progress. Even if there is lot of work to do on this ID, this is =
probably a good time to poll the=20
> WG to adopt it as the base document for inter-area-as applicability.
>=20
> All, are you in favor/opposed in adopting =
draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
> document ?
>=20
> Thanks.
>=20
> JP.
>=20
> Begin forwarded message:
>=20
>> From: "Daniel King" <daniel@olddog.co.uk>
>> Date: October 11, 2010 11:28:10 PM GMT+02:00
>> To: <pce@ietf.org>
>> Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com
>> Subject: [Pce] I-D =
Action:draft-king-pce-inter-area-as-applicability-02.txt
>>=20
>> Hi PCE'rs,=20
>>=20
>> Please find a new version of our pce-inter-area-as-applicability =
draft:=20
>>=20
>> =
http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt
>>=20
>> This document examines the applicability of the PCE architecture, =
protocols,
>> and protocol extensions for computing multi-area and multi-AS paths =
in MPLS
>> and GMPLS networks.
>>=20
>> This revision combines the addition of new co-authors and various =
updates
>> including:
>>=20
>> - Discussion on domain meshes.=20
>> - Discussion on route diversity.=20
>> - Discussion on synchronized path computations.=20
>> - Minor readability updates.=20
>> - Minor grammar and nit fixes.
>>=20
>> The document is not complete and will require further revisions. It =
is
>> however a good platform to build upon and as always we seek WG =
feedback and
>> suggestions.
>>=20
>> See you in Beijing!
>> =09
>> Br, Dan
>>=20
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
>=20
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


--Apple-Mail-4--625052548
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 12, 2010, at 9:50 PM, JP Vasseur wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Thanks Dan for this new =
revision. Major progress, thanks, this is part of our milstones, good to =
see<div>some progress. Even if there is lot of work to do on this ID, =
this is probably a good time to poll the&nbsp;</div><div>WG to adopt it =
as the base document for inter-area-as =
applicability.</div><div><br></div><div>All, are you in favor/opposed in =
adopting&nbsp;draft-king-pce-inter-area-as-applicability-02.txt as a PCE =
Wg</div><div>document =
?</div><div><br></div><div>Thanks.</div><div><br></div><div>JP.</div><div>=
<div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">"Daniel King" =
&lt;<a =
href=3D"mailto:daniel@olddog.co.uk">daniel@olddog.co.uk</a>&gt;<br></span>=
</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">October 11, 2010 =
11:28:10 PM GMT+02:00<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">&lt;<a =
href=3D"mailto:pce@ietf.org">pce@ietf.org</a>&gt;<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:olivier.dugeon@orange-ftgroup.com">olivier.dugeon@orange-ft=
group.com</a>, <a href=3D"mailto:fjjc@tid.es">fjjc@tid.es</a>, <a =
href=3D"mailto:qzhao@huawei.com">qzhao@huawei.com</a><br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>[Pce] I-D =
Action:draft-king-pce-inter-area-as-applicability-02.txt</b><br></span></d=
iv><br><div>Hi PCE'rs, <br><br>Please find a new version of our =
pce-inter-area-as-applicability draft: <br><br><a =
href=3D"http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-=
02.txt">http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-=
02.txt</a><br><br>This document examines the applicability of the PCE =
architecture, protocols,<br>and protocol extensions for computing =
multi-area and multi-AS paths in MPLS<br>and GMPLS networks.<br><br>This =
revision combines the addition of new co-authors and various =
updates<br>including:<br><br>- Discussion on domain meshes. <br>- =
Discussion on route diversity. <br>- Discussion on synchronized path =
computations. <br>- Minor readability updates. <br>- Minor grammar and =
nit fixes.<br><br>The document is not complete and will require further =
revisions. It is<br>however a good platform to build upon and as always =
we seek WG feedback and<br>suggestions.<br><br>See you in =
Beijing!<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><br>Br, =
Dan<br><br>_______________________________________________<br>Pce =
mailing list<br><a =
href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>https://www.ietf.org/mail=
man/listinfo/pce<br></div></blockquote></div><br></div></div>_____________=
__________________________________<br>Pce mailing list<br><a =
href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>https://www.ietf.org/mail=
man/listinfo/pce<br></blockquote></div><br></body></html>=

--Apple-Mail-4--625052548--

From julien.meuric@orange-ftgroup.com  Wed Oct 13 10:51:27 2010
Return-Path: <julien.meuric@orange-ftgroup.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 028E63A67B7 for <pce@core3.amsl.com>; Wed, 13 Oct 2010 10:51:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.505
X-Spam-Level: 
X-Spam-Status: No, score=-101.505 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJdnG7itMP2V for <pce@core3.amsl.com>; Wed, 13 Oct 2010 10:51:24 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 63D2B3A69CD for <pce@ietf.org>; Wed, 13 Oct 2010 10:51:23 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id CD9266C002B for <pce@ietf.org>; Wed, 13 Oct 2010 19:52:59 +0200 (CEST)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id C5D606C002E for <pce@ietf.org>; Wed, 13 Oct 2010 19:52:59 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 13 Oct 2010 19:49:05 +0200
Received: from [10.193.71.161] ([10.193.71.161]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 13 Oct 2010 19:49:04 +0200
Message-ID: <4CB5F110.4000907@orange-ftgroup.com>
Date: Wed, 13 Oct 2010 19:49:04 +0200
From: Julien Meuric <julien.meuric@orange-ftgroup.com>
Organization: France Telecom
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100915 Lightning/1.0b1 Thunderbird/3.0.8
MIME-Version: 1.0
To: pce@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Oct 2010 17:49:04.0749 (UTC) FILETIME=[ED68B1D0:01CB6AFE]
Subject: [Pce] Building PCE Agenda for IETF 79
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Oct 2010 17:51:27 -0000

Hi PCE'rs.

For IETF 79 in Beijing, the PCE session is scheduled on Thursday 11th at 
5:40 PM (unless a ROLL co-chair need to rest after his session...). If 
you intend to discuss the issues of your draft, now it is time to 
request a slot to your devoted co-chairs (you may CC your beloved 
secretary). Please, indicate the expected duration per draft.

Regards,

JP & Julien


From dhruvd@huawei.com  Thu Oct 14 03:36:28 2010
Return-Path: <dhruvd@huawei.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C09483A67FA for <pce@core3.amsl.com>; Thu, 14 Oct 2010 03:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.194
X-Spam-Level: 
X-Spam-Status: No, score=-0.194 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpE517jrq9Z3 for <pce@core3.amsl.com>; Thu, 14 Oct 2010 03:36:23 -0700 (PDT)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id 6D95B3A68FA for <pce@ietf.org>; Thu, 14 Oct 2010 03:36:22 -0700 (PDT)
Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAA002S606E03@szxga01-in.huawei.com> for pce@ietf.org; Thu, 14 Oct 2010 18:37:26 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAA00ALE06E1L@szxga01-in.huawei.com> for pce@ietf.org; Thu, 14 Oct 2010 18:37:26 +0800 (CST)
Received: from BLRNSHTIPL1NC ([10.18.1.31]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LAA00HJF06CIM@szxml04-in.huawei.com> for pce@ietf.org; Thu, 14 Oct 2010 18:37:26 +0800 (CST)
Date: Thu, 14 Oct 2010 16:07:24 +0530
From: Dhruv Dhody <dhruvd@huawei.com>
In-reply-to: <653C7AD5-C6EA-4AC5-AE65-8CB95174AEE8@cisco.com>
To: 'JP Vasseur' <jpv@cisco.com>, pce@ietf.org
Message-id: <921D66C30E0741BAAC2787487A99662D@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.4657
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_7V6MkOx6dK80qyoyzOF58w)"
Thread-index: ActqVoRTWTXFS3rYR4S9QPREineG0QBNP30g
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com> <653C7AD5-C6EA-4AC5-AE65-8CB95174AEE8@cisco.com>
Cc: olivier.dugeon@orange-ftgroup.com, 'Quintin Zhao' <qzhao@huawei.com>
Subject: Re: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as	a PCE WG document ??
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 10:36:28 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_7V6MkOx6dK80qyoyzOF58w)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear All, 

 

I support the adopting of "draft-king-pce-inter-area-as-applicability" as a
PCE WG document?

 

Thanks & Regards,

Dhruv Dhody

 

****************************************************************************
***********
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!

  _____  

From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of JP
Vasseur
Sent: Wednesday, October 13, 2010 3:13 AM
To: pce@ietf.org
Cc: olivier.dugeon@orange-ftgroup.com; fjjc@tid.es; Quintin Zhao
Subject: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as
a PCE WG document ??

 

 


On Oct 12, 2010, at 9:50 PM, JP Vasseur wrote:





Thanks Dan for this new revision. Major progress, thanks, this is part of
our milstones, good to see

some progress. Even if there is lot of work to do on this ID, this is
probably a good time to poll the 

WG to adopt it as the base document for inter-area-as applicability.

 

All, are you in favor/opposed in adopting
draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg

document ?

 

Thanks.

 

JP.

 

Begin forwarded message:





From: "Daniel King" <daniel@olddog.co.uk>

Date: October 11, 2010 11:28:10 PM GMT+02:00

To: <pce@ietf.org>

Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com

Subject: [Pce] I-D Action:draft-king-pce-inter-area-as-applicability-02.txt

 

Hi PCE'rs, 

Please find a new version of our pce-inter-area-as-applicability draft: 

http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt

This document examines the applicability of the PCE architecture, protocols,
and protocol extensions for computing multi-area and multi-AS paths in MPLS
and GMPLS networks.

This revision combines the addition of new co-authors and various updates
including:

- Discussion on domain meshes. 
- Discussion on route diversity. 
- Discussion on synchronized path computations. 
- Minor readability updates. 
- Minor grammar and nit fixes.

The document is not complete and will require further revisions. It is
however a good platform to build upon and as always we seek WG feedback and
suggestions.

See you in Beijing!
            
Br, Dan

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

 

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

 


--Boundary_(ID_7V6MkOx6dK80qyoyzOF58w)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Lucida Handwriting";
	panose-1:3 1 1 1 1 1 1 1 1 1;}
@font-face
	{font-family:Candara;
	panose-1:2 14 5 2 3 3 3 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1027" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue style=3D'word-wrap: =
break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3D"#666699" =
face=3DCandara><span
style=3D'font-size:11.0pt;font-family:Candara;color:#666699'>Dear All, =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#666699" =
face=3DCandara><span
style=3D'font-size:11.0pt;font-family:Candara;color:#666699'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#666699" =
face=3DCandara><span
style=3D'font-size:11.0pt;font-family:Candara;color:#666699'>I support =
the </span></font><font
size=3D2 color=3D"#666699" face=3DCandara><span =
style=3D'font-size:11.0pt;font-family:
Candara;color:#666699'>adopting&nbsp;of =
&#8220;draft-king-pce-inter-area-as-applicability&#8221;
as a PCE WG document?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#666699" =
face=3DCandara><span
style=3D'font-size:11.0pt;font-family:Candara;color:#666699'><o:p>&nbsp;<=
/o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#666699" =
face=3DCandara><span
style=3D'font-size:11.0pt;font-family:Candara;color:#666699'>Thanks =
&amp; Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3D"#666699" =
face=3DCandara><span
style=3D'font-size:11.0pt;font-family:Candara;color:#666699'>Dhruv =
Dhody<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><em><i><font=

size=3D2 color=3D"#484848" face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:
Verdana;color:#484848'>**************************************************=
*************************************</span></font></i></em><i><font
size=3D2 color=3D"#484848" face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:
Verdana;color:#484848;font-style:italic'><br>
</span></font></i><em><i><font size=3D2 color=3D"#484848" face=3D"Lucida =
Handwriting"><span
style=3D'font-size:10.0pt;font-family:"Lucida =
Handwriting";color:#484848'>This
e-mail and attachments contain confidential information from HUAWEI, =
which is
intended only for the person or entity whose address is listed above. =
Any use
of the information contained herein in any way (including, but not =
limited to,
total or partial disclosure, reproduction, or dissemination) by persons =
other
than the intended recipient's) is prohibited. If you receive this e-mail =
in
error, please notify the sender by phone or email immediately and delete =
it!</span></font></i></em><o:p></o:p></p>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'>
pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] <b><span =
style=3D'font-weight:
bold'>On Behalf Of </span></b>JP Vasseur<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, October =
13, 2010
3:13 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> pce@ietf.org<br>
<b><span style=3D'font-weight:bold'>Cc:</span></b>
olivier.dugeon@orange-ftgroup.com; fjjc@tid.es; Quintin Zhao<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> [Pce] Adopting
draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document =
??</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><!--[if gte vml 1]><v:shapetype id=3D"_x0000_t74" =
coordsize=3D"21600,21600"=20
 o:spt=3D"74" =
path=3D"m10860,2187c10451,1746,9529,1018,9015,730,7865,152,6685,,5415,,41=
75,152,2995,575,1967,1305,1150,2187,575,3222,242,4220,,5410,242,6560,575,=
7597l10860,21600,20995,7597v485,-1037,605,-2187,485,-3377c21115,3222,2042=
0,2187,19632,1305,18575,575,17425,152,16275,,15005,,13735,152,12705,730v-=
529,288,-1451,1016,-1845,1457xe">
 <v:stroke joinstyle=3D"miter" />
 <v:path gradientshapeok=3D"t" o:connecttype=3D"custom" =
o:connectlocs=3D"10860,2187;2928,10800;10860,21600;18672,10800"=20
  o:connectangles=3D"270,180,90,0" textboxrect=3D"5037,2277,16557,13677" =
/>
</v:shapetype><v:shape id=3D"DtsShapeName" o:spid=3D"_x0000_s1026" =
type=3D"#_x0000_t74"=20
 =
alt=3D"355B170GGB445B81C1B8C1@@GGE4@84D089:E[;6G4CCMSORIUHQM0,BIHO@]e6149=
5!!!!!!!!!!1113308@D@E@EOnsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!1"=20
 =
style=3D'position:absolute;margin-left:0;margin-top:0;width:.05pt;height:=
.05pt;
 z-index:1;visibility:hidden'>
 <w:anchorlock/>
</v:shape><![endif]--></span><o:p>&nbsp;</o:p></font></p>

<br style=3D'mso-ignore:vglayout' clear=3DALL>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>On Oct 12, 2010, at 9:50 PM, JP Vasseur =
wrote:<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
<br>
<o:p></o:p></span></font></p>

<div style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Thanks Dan for this new revision. Major progress, thanks, this =
is part
of our milstones, good to see<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>some progress. Even if there is lot of work to do on this ID, =
this is
probably a good time to poll the&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>WG to adopt it as the base document for inter-area-as =
applicability.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>All, are you in favor/opposed in
adopting&nbsp;draft-king-pce-inter-area-as-applicability-02.txt as a PCE =
Wg<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>document ?<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Thanks.<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>JP.<o:p></o:p></span></font></p>

</div>

<div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Begin forwarded message:<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><br>
<br>
<o:p></o:p></span></font></p>

<div><span style=3D'color:rgba(0, 0, 0, 1)'>

<p class=3DMsoNormal><b><font size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;
font-family:Helvetica;font-weight:bold'>From: =
</span></span></font></b><font
size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;font-family:Helvetica'>&quot;Daniel
King&quot; &lt;<a =
href=3D"mailto:daniel@olddog.co.uk">daniel@olddog.co.uk</a>&gt;</span></f=
ont><o:p></o:p></p>

</div>

<div><span style=3D'color:rgba(0, 0, 0, 1)'>

<p class=3DMsoNormal><b><font size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;
font-family:Helvetica;font-weight:bold'>Date: =
</span></span></font></b><font
size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;font-family:Helvetica'>October
11, 2010 11:28:10 PM GMT+02:00</span></font><o:p></o:p></p>

</div>

<div><span style=3D'color:rgba(0, 0, 0, 1)'>

<p class=3DMsoNormal><b><font size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;
font-family:Helvetica;font-weight:bold'>To: =
</span></span></font></b><font
size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;font-family:Helvetica'>&lt;<a
href=3D"mailto:pce@ietf.org">pce@ietf.org</a>&gt;</span></font><o:p></o:p=
></p>

</div>

<div><span style=3D'color:rgba(0, 0, 0, 1)'>

<p class=3DMsoNormal><b><font size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;
font-family:Helvetica;font-weight:bold'>Cc: =
</span></span></font></b><font
size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;font-family:Helvetica'><a
href=3D"mailto:olivier.dugeon@orange-ftgroup.com">olivier.dugeon@orange-f=
tgroup.com</a>,
<a href=3D"mailto:fjjc@tid.es">fjjc@tid.es</a>, <a =
href=3D"mailto:qzhao@huawei.com">qzhao@huawei.com</a></span></font><o:p><=
/o:p></p>

</div>

<div><span style=3D'color:rgba(0, 0, 0, 1)'>

<p class=3DMsoNormal><b><font size=3D4 face=3DHelvetica><span =
style=3D'font-size:13.5pt;
font-family:Helvetica;font-weight:bold'>Subject: </span>[Pce] I-D
Action:draft-king-pce-inter-area-as-applicability-02.txt</span></font></b=
><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Hi PCE'rs, <br>
<br>
Please find a new version of our pce-inter-area-as-applicability draft: =
<br>
<br>
<a
href=3D"http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability=
-02.txt">http://www.ietf.org/id/draft-king-pce-inter-area-as-applicabilit=
y-02.txt</a><br>
<br>
This document examines the applicability of the PCE architecture, =
protocols,<br>
and protocol extensions for computing multi-area and multi-AS paths in =
MPLS<br>
and GMPLS networks.<br>
<br>
This revision combines the addition of new co-authors and various =
updates<br>
including:<br>
<br>
- Discussion on domain meshes. <br>
- Discussion on route diversity. <br>
- Discussion on synchronized path computations. <br>
- Minor readability updates. <br>
- Minor grammar and nit fixes.<br>
<br>
The document is not complete and will require further revisions. It =
is<br>
however a good platform to build upon and as always we seek WG feedback =
and<br>
suggestions.<br>
<br>
See you in Beijing!<br>
<span =
class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; </span><br>
Br, Dan<br>
<br>
_______________________________________________<br>
Pce mailing list<br>
<a href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/pce<o:p></o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>_______________________________________________<br>
Pce mailing list<br>
<a href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/pce<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

--Boundary_(ID_7V6MkOx6dK80qyoyzOF58w)--

From danli@huawei.com  Thu Oct 14 04:24:36 2010
Return-Path: <danli@huawei.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E384A3A68F7 for <pce@core3.amsl.com>; Thu, 14 Oct 2010 04:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.403
X-Spam-Level: ****
X-Spam-Status: No, score=4.403 tagged_above=-999 required=5 tests=[AWL=0.218,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, MIME_CHARSET_FARAWAY=2.45, RCVD_NUMERIC_HELO=2.067, SARE_RECV_IP_061172=1.666]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Pn1oTKFfAOj for <pce@core3.amsl.com>; Thu, 14 Oct 2010 04:24:35 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id CD9DA3A697C for <pce@ietf.org>; Thu, 14 Oct 2010 04:24:35 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAA00EWL2F594@usaga01-in.huawei.com> for pce@ietf.org; Thu, 14 Oct 2010 04:25:54 -0700 (PDT)
Received: from 89.130.173.61.broad.xw.sh.dynamic.163data.com.cn (89.130.173.61.broad.xw.sh.dynamic.163data.com.cn [61.173.130.89]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPSA id <0LAA00AHY2ETEG@usaga01-in.huawei.com> for pce@ietf.org; Thu, 14 Oct 2010 04:25:53 -0700 (PDT)
Date: Thu, 14 Oct 2010 19:25:36 +0800
From: Dan Li <danli@huawei.com>
In-reply-to: <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
To: JP Vasseur <jpv@cisco.com>
Message-id: <0B6BD3B8-0F80-4A08-BB39-B2A56BEF0EF6@huawei.com>
MIME-version: 1.0
X-Mailer: Apple Mail (2.1081)
Content-type: multipart/alternative; boundary="Boundary_(ID_5OK5rqvBQ4HFsVZDE9x5tQ)"
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
Cc: olivier.dugeon@orange-ftgroup.com, pce@ietf.org, Quintin Zhao <qzhao@huawei.com>
Subject: Re: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as	a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 11:24:37 -0000

--Boundary_(ID_5OK5rqvBQ4HFsVZDE9x5tQ)
Content-type: text/plain; charset=GB2312
Content-transfer-encoding: quoted-printable

Yes/Support!

Dan

=D4=DA 2010-10-13=A3=AC=C9=CF=CE=E73:50=A3=AC JP Vasseur =D0=B4=B5=C0=A3=BA=


> Thanks Dan for this new revision. Major progress, thanks, this is part =
of our milstones, good to see
> some progress. Even if there is lot of work to do on this ID, this is =
probably a good time to poll the=20
> WG to adopt it as the base document for inter-area-as applicability.
>=20
> All, are you in favor/opposed in adopting =
draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
> document ?
>=20
> Thanks.
>=20
> JP.
>=20
> Begin forwarded message:
>=20
>> From: "Daniel King" <daniel@olddog.co.uk>
>> Date: October 11, 2010 11:28:10 PM GMT+02:00
>> To: <pce@ietf.org>
>> Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com
>> Subject: [Pce] I-D =
Action:draft-king-pce-inter-area-as-applicability-02.txt
>>=20
>> Hi PCE'rs,=20
>>=20
>> Please find a new version of our pce-inter-area-as-applicability =
draft:=20
>>=20
>> =
http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt
>>=20
>> This document examines the applicability of the PCE architecture, =
protocols,
>> and protocol extensions for computing multi-area and multi-AS paths =
in MPLS
>> and GMPLS networks.
>>=20
>> This revision combines the addition of new co-authors and various =
updates
>> including:
>>=20
>> - Discussion on domain meshes.=20
>> - Discussion on route diversity.=20
>> - Discussion on synchronized path computations.=20
>> - Minor readability updates.=20
>> - Minor grammar and nit fixes.
>>=20
>> The document is not complete and will require further revisions. It =
is
>> however a good platform to build upon and as always we seek WG =
feedback and
>> suggestions.
>>=20
>> See you in Beijing!
>> =09
>> Br, Dan
>>=20
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
>=20
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


--Boundary_(ID_5OK5rqvBQ4HFsVZDE9x5tQ)
Content-type: text/html; charset=GB2312
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Yes/Support!<div><br></div><div>Dan</div><div><br><div><div>=D4=DA =
2010-10-13=A3=AC=C9=CF=CE=E73:50=A3=AC JP Vasseur =D0=B4=B5=C0=A3=BA</div>=
<br class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Thanks Dan for this new =
revision. Major progress, thanks, this is part of our milstones, good to =
see<div>some progress. Even if there is lot of work to do on this ID, =
this is probably a good time to poll the&nbsp;</div><div>WG to adopt it =
as the base document for inter-area-as =
applicability.</div><div><br></div><div>All, are you in favor/opposed in =
adopting&nbsp;draft-king-pce-inter-area-as-applicability-02.txt as a PCE =
Wg</div><div>document =
?</div><div><br></div><div>Thanks.</div><div><br></div><div>JP.</div><div>=
<div><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>From: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">"Daniel King" =
&lt;<a =
href=3D"mailto:daniel@olddog.co.uk">daniel@olddog.co.uk</a>&gt;<br></span>=
</div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Date: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;">October 11, 2010 =
11:28:10 PM GMT+02:00<br></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span =
style=3D"font-family:'Helvetica'; font-size:medium; color:rgba(0, 0, 0, =
1);"><b>To: </b></span><span style=3D"font-family:'Helvetica'; =
font-size:medium;">&lt;<a =
href=3D"mailto:pce@ietf.org">pce@ietf.org</a>&gt;<br></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Cc: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><a =
href=3D"mailto:olivier.dugeon@orange-ftgroup.com">olivier.dugeon@orange-ft=
group.com</a>, <a href=3D"mailto:fjjc@tid.es">fjjc@tid.es</a>, <a =
href=3D"mailto:qzhao@huawei.com">qzhao@huawei.com</a><br></span></div><div=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;"><span style=3D"font-family:'Helvetica'; =
font-size:medium; color:rgba(0, 0, 0, 1);"><b>Subject: </b></span><span =
style=3D"font-family:'Helvetica'; font-size:medium;"><b>[Pce] I-D =
Action:draft-king-pce-inter-area-as-applicability-02.txt</b><br></span></d=
iv><br><div>Hi PCE'rs, <br><br>Please find a new version of our =
pce-inter-area-as-applicability draft: <br><br><a =
href=3D"http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-=
02.txt">http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-=
02.txt</a><br><br>This document examines the applicability of the PCE =
architecture, protocols,<br>and protocol extensions for computing =
multi-area and multi-AS paths in MPLS<br>and GMPLS networks.<br><br>This =
revision combines the addition of new co-authors and various =
updates<br>including:<br><br>- Discussion on domain meshes. <br>- =
Discussion on route diversity. <br>- Discussion on synchronized path =
computations. <br>- Minor readability updates. <br>- Minor grammar and =
nit fixes.<br><br>The document is not complete and will require further =
revisions. It is<br>however a good platform to build upon and as always =
we seek WG feedback and<br>suggestions.<br><br>See you in =
Beijing!<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span><br>Br, =
Dan<br><br>_______________________________________________<br>Pce =
mailing list<br><a =
href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>https://www.ietf.org/mail=
man/listinfo/pce<br></div></blockquote></div><br></div></div>_____________=
__________________________________<br>Pce mailing list<br><a =
href=3D"mailto:Pce@ietf.org">Pce@ietf.org</a><br>https://www.ietf.org/mail=
man/listinfo/pce<br></blockquote></div><br></div></body></html>=

--Boundary_(ID_5OK5rqvBQ4HFsVZDE9x5tQ)--

From ramon.casellas@cttc.es  Thu Oct 14 04:48:30 2010
Return-Path: <ramon.casellas@cttc.es>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0385D3A679C for <pce@core3.amsl.com>; Thu, 14 Oct 2010 04:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level: 
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDGyWUIZGLMb for <pce@core3.amsl.com>; Thu, 14 Oct 2010 04:48:29 -0700 (PDT)
Received: from Scorpius.cttc.es (scorpius.cttc.es [84.88.62.197]) by core3.amsl.com (Postfix) with ESMTP id B9B7D3A68EC for <pce@ietf.org>; Thu, 14 Oct 2010 04:48:28 -0700 (PDT)
Received: from castor (postfix@castor.cttc.es [84.88.62.196]) by Scorpius.cttc.es (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id o9EFlp6I001598 for <pce@ietf.org>; Thu, 14 Oct 2010 17:47:56 +0200
Received: from [84.88.61.50] (pcrcasellas.cttc.es [84.88.61.50]) by castor (Postfix) with ESMTP id C00C52FC28F for <pce@ietf.org>; Thu, 14 Oct 2010 13:49:33 +0200 (CEST)
Message-ID: <4CB6EE16.4020309@cttc.es>
Date: Thu, 14 Oct 2010 13:48:38 +0200
From: Ramon Casellas <ramon.casellas@cttc.es>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.11) Gecko/20101004 Thunderbird/3.1.5
MIME-Version: 1.0
To: pce@ietf.org
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
In-Reply-To: <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (castor); Thu, 14 Oct 2010 13:49:33 +0200 (CEST)
X-Scanned-By: MIMEDefang 2.67 on 84.88.62.197
Subject: Re: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 11:48:30 -0000

On 12/10/2010 21:50, JP Vasseur wrote:
> All, are you in favor/opposed in 
> adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
> document ?

In favor,

thanks
R.

From db3546@att.com  Thu Oct 14 06:12:18 2010
Return-Path: <db3546@att.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5FED33A69E7 for <pce@core3.amsl.com>; Thu, 14 Oct 2010 06:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.99
X-Spam-Level: 
X-Spam-Status: No, score=-105.99 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E91vTnooPSTD for <pce@core3.amsl.com>; Thu, 14 Oct 2010 06:12:16 -0700 (PDT)
Received: from mail129.messagelabs.com (mail129.messagelabs.com [216.82.250.147]) by core3.amsl.com (Postfix) with ESMTP id E83933A6A3F for <pce@ietf.org>; Thu, 14 Oct 2010 06:12:15 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: db3546@att.com
X-Msg-Ref: server-9.tower-129.messagelabs.com!1287062013!46961398!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 7516 invoked from network); 14 Oct 2010 13:13:34 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-9.tower-129.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 14 Oct 2010 13:13:34 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9EDCvxr012632 for <pce@ietf.org>; Thu, 14 Oct 2010 09:12:57 -0400
Received: from gaalpa1msgusr7e.ugd.att.com (gaalpa1msgusr7e.ugd.att.com [135.53.26.19]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o9EDCsVj012610 for <pce@ietf.org>; Thu, 14 Oct 2010 09:12:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 14 Oct 2010 09:13:29 -0400
Message-ID: <D6CB948F7AFD6F4881D4B4F80C8509AA085578B1@gaalpa1msgusr7e.ugd.att.com>
In-Reply-To: <002401cb698b$34d499f0$9e7dcdd0$@co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] I-D Action:draft-king-pce-inter-area-as-applicability-02.txt
Thread-Index: AcsiB1gy1yNkkxn2TLqyRySj2G/lMQAhC1XQEb+bJBAAhegGsA==
References: <20100712211504.475353A6B87@core3.amsl.com><000a01cb228c$3063be00$912b3a00$@co.uk> <002401cb698b$34d499f0$9e7dcdd0$@co.uk>
From: "BRUNGARD, DEBORAH A (ATTLABS)" <db3546@att.com>
To: "Daniel King" <daniel@olddog.co.uk>, <pce@ietf.org>
Cc: olivier.dugeon@orange-ftgroup.com, qzhao@huawei.com
Subject: Re: [Pce] I-D Action:draft-king-pce-inter-area-as-applicability-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 13:12:18 -0000

Support-

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of
Daniel King
Sent: Monday, October 11, 2010 5:28 PM
To: pce@ietf.org
Cc: olivier.dugeon@orange-ftgroup.com; fjjc@tid.es; qzhao@huawei.com
Subject: [Pce] I-D
Action:draft-king-pce-inter-area-as-applicability-02.txt

Hi PCE'rs,=20

Please find a new version of our pce-inter-area-as-applicability draft:=20

http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt

This document examines the applicability of the PCE architecture,
protocols,
and protocol extensions for computing multi-area and multi-AS paths in
MPLS
and GMPLS networks.

This revision combines the addition of new co-authors and various
updates
including:

- Discussion on domain meshes.=20
- Discussion on route diversity.=20
- Discussion on synchronized path computations.=20
- Minor readability updates.=20
- Minor grammar and nit fixes.

The document is not complete and will require further revisions. It is
however a good platform to build upon and as always we seek WG feedback
and
suggestions.

See you in Beijing!
=09
Br, Dan

_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce

From meral.shirazipour@polymtl.ca  Thu Oct 14 07:02:38 2010
Return-Path: <meral.shirazipour@polymtl.ca>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 68BC83A69DC for <pce@core3.amsl.com>; Thu, 14 Oct 2010 07:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WSqdyqSTucEI for <pce@core3.amsl.com>; Thu, 14 Oct 2010 07:02:37 -0700 (PDT)
Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by core3.amsl.com (Postfix) with ESMTP id 598393A6948 for <pce@ietf.org>; Thu, 14 Oct 2010 07:02:37 -0700 (PDT)
Received: from localhost (imp-4-3.polymtl.ca [132.207.4.78]) by smtp.polymtl.ca (8.14.3/8.14.3) with ESMTP id o9EE3oBf006025; Thu, 14 Oct 2010 10:03:53 -0400
Received: from lmcpra.ericsson.ca (lmcpra.ericsson.ca [192.75.88.231]) by www.imp.polymtl.ca (Horde MIME library) with HTTP; Thu, 14 Oct 2010 10:03:50 -0400
Message-ID: <20101014100350.jpj83b72g4kc4sc0@www.imp.polymtl.ca>
Date: Thu, 14 Oct 2010 10:03:50 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: pce@ietf.org
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
In-Reply-To: <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Poly-FromMTA: (imp-4-3.polymtl.ca [132.207.4.78]) at Thu, 14 Oct 2010 14:03:50 +0000
Cc: JP Vasseur <jpv@cisco.com>
Subject: Re: [Pce] Adopting	draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Oct 2010 14:02:38 -0000

Hi,
   I am in favor of draft-king-pce-inter-area-as-applicability-02.txt.

Regards,
Meral


JP Vasseur <jpv@cisco.com> a =C3=A9crit=C2=A0:

> Thanks Dan for this new revision. Major progress, thanks, this is 
> part of our milstones, good to see
> some progress. Even if there is lot of work to do on this ID, this is 
> probably a good time to poll the
> WG to adopt it as the base document for inter-area-as applicability.
>
> All, are you in favor/opposed in adopting 
> draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
> document ?
>
> Thanks.
>
> JP.
>
> Begin forwarded message:
>
>> From: "Daniel King" <daniel@olddog.co.uk>
>> Date: October 11, 2010 11:28:10 PM GMT+02:00
>> To: <pce@ietf.org>
>> Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com
>> Subject: [Pce] I-D Action:draft-king-pce-inter-area-as-applicability-02.=
txt
>>
>> Hi PCE'rs,
>>
>> Please find a new version of our pce-inter-area-as-applicability draft:
>>
>> http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt
>>
>> This document examines the applicability of the PCE architecture, protoc=
ols,
>> and protocol extensions for computing multi-area and multi-AS paths in M=
PLS
>> and GMPLS networks.
>>
>> This revision combines the addition of new co-authors and various update=
s
>> including:
>>
>> - Discussion on domain meshes.
>> - Discussion on route diversity.
>> - Discussion on synchronized path computations.
>> - Minor readability updates.
>> - Minor grammar and nit fixes.
>>
>> The document is not complete and will require further revisions. It is
>> however a good platform to build upon and as always we seek WG feedback =
and
>> suggestions.
>>
>> See you in Beijing!
>>
>> Br, Dan
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
>
>




From daniel@olddog.co.uk  Fri Oct 15 10:15:17 2010
Return-Path: <daniel@olddog.co.uk>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 101033A6CAA for <pce@core3.amsl.com>; Fri, 15 Oct 2010 10:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.489
X-Spam-Level: 
X-Spam-Status: No, score=-101.489 tagged_above=-999 required=5 tests=[AWL=0.510, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wpAkMhQ2yTqa for <pce@core3.amsl.com>; Fri, 15 Oct 2010 10:15:14 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by core3.amsl.com (Postfix) with ESMTP id 890AF3A6CD4 for <pce@ietf.org>; Fri, 15 Oct 2010 10:15:10 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id o9FHGTC7006855 for <pce@ietf.org>; Fri, 15 Oct 2010 18:16:30 +0100
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id o9FHGTi1006851 for <pce@ietf.org>; Fri, 15 Oct 2010 18:16:29 +0100
From: "Daniel King" <daniel@olddog.co.uk>
To: <pce@ietf.org>
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com> <20101014100350.jpj83b72g4kc4sc0@www.imp.polymtl.ca>
In-Reply-To: <20101014100350.jpj83b72g4kc4sc0@www.imp.polymtl.ca>
Date: Fri, 15 Oct 2010 18:16:35 +0100
Message-ID: <000001cb6c8c$b8aa7070$29ff5150$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
thread-index: ActrqKlYd4RQmtYvQdyC7zCVTGlG1AA4+MJA
Content-Language: en-gb
Subject: Re: [Pce] Adopting	draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Oct 2010 17:15:17 -0000

Thanks JP.=20

As a co-author, I would also like to support the adoption of the draft =
by
the WG.

Br, Dan. =20

JP Vasseur <jpv@cisco.com> a =C3=A9crit=C2=A0:

> Thanks Dan for this new revision. Major progress, thanks, this is=20
> part of our milstones, good to see
> some progress. Even if there is lot of work to do on this ID, this is=20
> probably a good time to poll the
> WG to adopt it as the base document for inter-area-as applicability.
>
> All, are you in favor/opposed in adopting=20
> draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
> document ?
>
> Thanks.
>
> JP.
>
> Begin forwarded message:
>
>> From: "Daniel King" <daniel@olddog.co.uk>
>> Date: October 11, 2010 11:28:10 PM GMT+02:00
>> To: <pce@ietf.org>
>> Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com
>> Subject: [Pce] I-D
Action:draft-king-pce-inter-area-as-applicability-02.txt
>>
>> Hi PCE'rs,
>>
>> Please find a new version of our pce-inter-area-as-applicability =
draft:
>>
>> =
http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt
>>
>> This document examines the applicability of the PCE architecture,
protocols,
>> and protocol extensions for computing multi-area and multi-AS paths =
in
MPLS
>> and GMPLS networks.
>>
>> This revision combines the addition of new co-authors and various =
updates
>> including:
>>
>> - Discussion on domain meshes.
>> - Discussion on route diversity.
>> - Discussion on synchronized path computations.
>> - Minor readability updates.
>> - Minor grammar and nit fixes.
>>
>> The document is not complete and will require further revisions. It =
is
>> however a good platform to build upon and as always we seek WG =
feedback
and
>> suggestions.
>>
>> See you in Beijing!
>>
>> Br, Dan
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
>
>



_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


From giomarti@cisco.com  Sat Oct 16 00:22:19 2010
Return-Path: <giomarti@cisco.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D408E3A6A75 for <pce@core3.amsl.com>; Sat, 16 Oct 2010 00:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.965
X-Spam-Level: 
X-Spam-Status: No, score=-8.965 tagged_above=-999 required=5 tests=[AWL=1.033,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lnGWl2XCRNwg for <pce@core3.amsl.com>; Sat, 16 Oct 2010 00:22:18 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 356B63A685B for <pce@ietf.org>; Sat, 16 Oct 2010 00:22:18 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-AV: E=Sophos;i="4.57,338,1283731200"; d="scan'208,217";a="66805388"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 16 Oct 2010 07:23:40 +0000
Received: from dhcp-10-61-106-70.cisco.com (dhcp-10-61-106-70.cisco.com [10.61.106.70]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id o9G7NdTr031882; Sat, 16 Oct 2010 07:23:39 GMT
Message-ID: <4CB952FA.1050405@cisco.com>
Date: Sat, 16 Oct 2010 09:23:38 +0200
From: Giovanni Martinelli <giomarti@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: JP Vasseur <jpv@cisco.com>
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
In-Reply-To: <D37955B4-9098-441C-8381-74891FEFE215@cisco.com>
Content-Type: multipart/alternative; boundary="------------010302080907070905090809"
Cc: olivier.dugeon@orange-ftgroup.com, pce@ietf.org, Quintin Zhao <qzhao@huawei.com>
Subject: Re: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as	a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Oct 2010 07:22:19 -0000

This is a multi-part message in MIME format.
--------------010302080907070905090809
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

  Support.

Cheers
G

On 10/12/10 9:50 PM, JP Vasseur wrote:
> Thanks Dan for this new revision. Major progress, thanks, this is part 
> of our milstones, good to see
> some progress. Even if there is lot of work to do on this ID, this is 
> probably a good time to poll the
> WG to adopt it as the base document for inter-area-as applicability.
>
> All, are you in favor/opposed in 
> adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
> document ?
>
> Thanks.
>
> JP.
>
> Begin forwarded message:
>
>> *From: *"Daniel King" <daniel@olddog.co.uk <mailto:daniel@olddog.co.uk>>
>> *Date: *October 11, 2010 11:28:10 PM GMT+02:00
>> *To: *<pce@ietf.org <mailto:pce@ietf.org>>
>> *Cc: *olivier.dugeon@orange-ftgroup.com 
>> <mailto:olivier.dugeon@orange-ftgroup.com>, fjjc@tid.es 
>> <mailto:fjjc@tid.es>, qzhao@huawei.com <mailto:qzhao@huawei.com>
>> *Subject: **[Pce] I-D 
>> Action:draft-king-pce-inter-area-as-applicability-02.txt*
>>
>> Hi PCE'rs,
>>
>> Please find a new version of our pce-inter-area-as-applicability draft:
>>
>> http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt
>>
>> This document examines the applicability of the PCE architecture, 
>> protocols,
>> and protocol extensions for computing multi-area and multi-AS paths 
>> in MPLS
>> and GMPLS networks.
>>
>> This revision combines the addition of new co-authors and various updates
>> including:
>>
>> - Discussion on domain meshes.
>> - Discussion on route diversity.
>> - Discussion on synchronized path computations.
>> - Minor readability updates.
>> - Minor grammar and nit fixes.
>>
>> The document is not complete and will require further revisions. It is
>> however a good platform to build upon and as always we seek WG 
>> feedback and
>> suggestions.
>>
>> See you in Beijing!
>>
>> Br, Dan
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce

--------------010302080907070905090809
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <font face="Helvetica, Arial, sans-serif">Support.<br>
      <br>
      Cheers<br>
      G<br>
    </font><br>
    On 10/12/10 9:50 PM, JP Vasseur wrote:
    <blockquote
      cite="mid:D37955B4-9098-441C-8381-74891FEFE215@cisco.com"
      type="cite">Thanks Dan for this new revision. Major progress,
      thanks, this is part of our milstones, good to see
      <div>some progress. Even if there is lot of work to do on this ID,
        this is probably a good time to poll the&nbsp;</div>
      <div>WG to adopt it as the base document for inter-area-as
        applicability.</div>
      <div><br>
      </div>
      <div>All, are you in favor/opposed in
        adopting&nbsp;draft-king-pce-inter-area-as-applicability-02.txt as a
        PCE Wg</div>
      <div>document ?</div>
      <div><br>
      </div>
      <div>Thanks.</div>
      <div><br>
      </div>
      <div>JP.</div>
      <div>
        <div><br>
          <div>Begin forwarded message:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">
            <div style="margin: 0px;"><span style="font-family:
                'Helvetica'; font-size: medium; color: rgb(0, 0, 0);"><b>From:
                </b></span><span style="font-family: 'Helvetica';
                font-size: medium;">"Daniel King" &lt;<a
                  moz-do-not-send="true"
                  href="mailto:daniel@olddog.co.uk">daniel@olddog.co.uk</a>&gt;<br>
              </span></div>
            <div style="margin: 0px;"><span style="font-family:
                'Helvetica'; font-size: medium; color: rgb(0, 0, 0);"><b>Date:
                </b></span><span style="font-family: 'Helvetica';
                font-size: medium;">October 11, 2010 11:28:10 PM
                GMT+02:00<br>
              </span></div>
            <div style="margin: 0px;"><span style="font-family:
                'Helvetica'; font-size: medium; color: rgb(0, 0, 0);"><b>To:
                </b></span><span style="font-family: 'Helvetica';
                font-size: medium;">&lt;<a moz-do-not-send="true"
                  href="mailto:pce@ietf.org">pce@ietf.org</a>&gt;<br>
              </span></div>
            <div style="margin: 0px;"><span style="font-family:
                'Helvetica'; font-size: medium; color: rgb(0, 0, 0);"><b>Cc:
                </b></span><span style="font-family: 'Helvetica';
                font-size: medium;"><a moz-do-not-send="true"
                  href="mailto:olivier.dugeon@orange-ftgroup.com">olivier.dugeon@orange-ftgroup.com</a>,
                <a moz-do-not-send="true" href="mailto:fjjc@tid.es">fjjc@tid.es</a>,
                <a moz-do-not-send="true" href="mailto:qzhao@huawei.com">qzhao@huawei.com</a><br>
              </span></div>
            <div style="margin: 0px;"><span style="font-family:
                'Helvetica'; font-size: medium; color: rgb(0, 0, 0);"><b>Subject:
                </b></span><span style="font-family: 'Helvetica';
                font-size: medium;"><b>[Pce] I-D
                  Action:draft-king-pce-inter-area-as-applicability-02.txt</b><br>
              </span></div>
            <br>
            <div>Hi PCE'rs, <br>
              <br>
              Please find a new version of our
              pce-inter-area-as-applicability draft: <br>
              <br>
              <a moz-do-not-send="true"
href="http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt">http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt</a><br>
              <br>
              This document examines the applicability of the PCE
              architecture, protocols,<br>
              and protocol extensions for computing multi-area and
              multi-AS paths in MPLS<br>
              and GMPLS networks.<br>
              <br>
              This revision combines the addition of new co-authors and
              various updates<br>
              including:<br>
              <br>
              - Discussion on domain meshes. <br>
              - Discussion on route diversity. <br>
              - Discussion on synchronized path computations. <br>
              - Minor readability updates. <br>
              - Minor grammar and nit fixes.<br>
              <br>
              The document is not complete and will require further
              revisions. It is<br>
              however a good platform to build upon and as always we
              seek WG feedback and<br>
              suggestions.<br>
              <br>
              See you in Beijing!<br>
              <span class="Apple-tab-span" style="white-space: pre;"> </span><br>
              Br, Dan<br>
              <br>
              _______________________________________________<br>
              Pce mailing list<br>
              <a class="moz-txt-link-abbreviated" href="mailto:Pce@ietf.org">Pce@ietf.org</a><br>
              <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</a><br>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
Pce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Pce@ietf.org">Pce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</a>
</pre>
    </blockquote>
  </body>
</html>

--------------010302080907070905090809--

From zhangfatai@huawei.com  Sun Oct 17 18:45:55 2010
Return-Path: <zhangfatai@huawei.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 796773A6C6A for <pce@core3.amsl.com>; Sun, 17 Oct 2010 18:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.597
X-Spam-Level: 
X-Spam-Status: No, score=0.597 tagged_above=-999 required=5 tests=[AWL=0.491,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jcw0PiMfMdav for <pce@core3.amsl.com>; Sun, 17 Oct 2010 18:45:54 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id C6F8F3A6C2E for <pce@ietf.org>; Sun, 17 Oct 2010 18:45:53 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAG00H8JQAMNR@szxga04-in.huawei.com> for pce@ietf.org; Mon, 18 Oct 2010 09:47:10 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAG00KS1QAMP0@szxga04-in.huawei.com> for pce@ietf.org; Mon, 18 Oct 2010 09:47:10 +0800 (CST)
Received: from Z41162C ([10.70.76.101]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LAG00D0IQAMOW@szxml06-in.huawei.com> for pce@ietf.org; Mon, 18 Oct 2010 09:47:10 +0800 (CST)
Date: Mon, 18 Oct 2010 09:47:10 +0800
From: Fatai Zhang <zhangfatai@huawei.com>
To: Giovanni Martinelli <giomarti@cisco.com>, JP Vasseur <jpv@cisco.com>
Message-id: <016601cb6e66$60ef82e0$654c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3598
Content-type: multipart/alternative; boundary="Boundary_(ID_B07VKGbiywwClqLY6A20dg)"
X-Priority: 3
X-MSMail-priority: Normal
References: <002401cb698b$34d499f0$9e7dcdd0$@co.uk> <D37955B4-9098-441C-8381-74891FEFE215@cisco.com> <4CB952FA.1050405@cisco.com>
Cc: olivier.dugeon@orange-ftgroup.com, pce@ietf.org, Quintin Zhao <qzhao@huawei.com>
Subject: Re: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as	a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 01:45:55 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_B07VKGbiywwClqLY6A20dg)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT

Yes/Support.




Best Regards
 
Fatai
 
  ----- Original Message ----- 
  From: Giovanni Martinelli 
  To: JP Vasseur 
  Cc: olivier.dugeon@orange-ftgroup.com ; pce@ietf.org ; Quintin Zhao 
  Sent: Saturday, October 16, 2010 3:23 PM
  Subject: Re: [Pce] Adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document


  Support.

  Cheers
  G

  On 10/12/10 9:50 PM, JP Vasseur wrote: 
    Thanks Dan for this new revision. Major progress, thanks, this is part of our milstones, good to see 
    some progress. Even if there is lot of work to do on this ID, this is probably a good time to poll the 
    WG to adopt it as the base document for inter-area-as applicability.


    All, are you in favor/opposed in adopting draft-king-pce-inter-area-as-applicability-02.txt as a PCE Wg
    document ?


    Thanks.


    JP.


    Begin forwarded message:


      From: "Daniel King" <daniel@olddog.co.uk>

      Date: October 11, 2010 11:28:10 PM GMT+02:00

      To: <pce@ietf.org>

      Cc: olivier.dugeon@orange-ftgroup.com, fjjc@tid.es, qzhao@huawei.com

      Subject: [Pce] I-D Action:draft-king-pce-inter-area-as-applicability-02.txt



      Hi PCE'rs, 

      Please find a new version of our pce-inter-area-as-applicability draft: 

      http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt

      This document examines the applicability of the PCE architecture, protocols,
      and protocol extensions for computing multi-area and multi-AS paths in MPLS
      and GMPLS networks.

      This revision combines the addition of new co-authors and various updates
      including:

      - Discussion on domain meshes. 
      - Discussion on route diversity. 
      - Discussion on synchronized path computations. 
      - Minor readability updates. 
      - Minor grammar and nit fixes.

      The document is not complete and will require further revisions. It is
      however a good platform to build upon and as always we seek WG feedback and
      suggestions.

      See you in Beijing!

      Br, Dan

      _______________________________________________
      Pce mailing list
      Pce@ietf.org
      https://www.ietf.org/mailman/listinfo/pce




_______________________________________________
Pce mailing list
Pce@ietf.org
https://www.ietf.org/mailman/listinfo/pce


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


  _______________________________________________
  Pce mailing list
  Pce@ietf.org
  https://www.ietf.org/mailman/listinfo/pce

--Boundary_(ID_B07VKGbiywwClqLY6A20dg)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><FONT face=Arial>Yes/Support.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><BR>Best Regards<BR>&nbsp;<BR>Fatai<BR>&nbsp;</DIV>
<BLOCKQUOTE 
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style="FONT: 9pt &#23435;&#20307;">----- Original Message ----- </DIV>
  <DIV style="BACKGROUND: #e4e4e4; FONT: 9pt &#23435;&#20307;; font-color: black"><B>From:</B> 
  <A title=giomarti@cisco.com href="mailto:giomarti@cisco.com">Giovanni 
  Martinelli</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>To:</B> <A title=jpv@cisco.com 
  href="mailto:jpv@cisco.com">JP Vasseur</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Cc:</B> <A 
  title=olivier.dugeon@orange-ftgroup.com 
  href="mailto:olivier.dugeon@orange-ftgroup.com">olivier.dugeon@orange-ftgroup.com</A> 
  ; <A title=pce@ietf.org href="mailto:pce@ietf.org">pce@ietf.org</A> ; <A 
  title=qzhao@huawei.com href="mailto:qzhao@huawei.com">Quintin Zhao</A> </DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Sent:</B> Saturday, October 16, 2010 3:23 
PM</DIV>
  <DIV style="FONT: 9pt &#23435;&#20307;"><B>Subject:</B> Re: [Pce] Adopting 
  draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document</DIV>
  <DIV><BR></DIV><FONT 
  face="Helvetica, Arial, sans-serif">Support.<BR><BR>Cheers<BR>G<BR></FONT><BR>On 
  10/12/10 9:50 PM, JP Vasseur wrote: 
  <BLOCKQUOTE cite=mid:D37955B4-9098-441C-8381-74891FEFE215@cisco.com 
  type="cite">Thanks Dan for this new revision. Major progress, thanks, this 
    is part of our milstones, good to see 
    <DIV>some progress. Even if there is lot of work to do on this ID, this is 
    probably a good time to poll the&nbsp;</DIV>
    <DIV>WG to adopt it as the base document for inter-area-as 
    applicability.</DIV>
    <DIV><BR></DIV>
    <DIV>All, are you in favor/opposed in 
    adopting&nbsp;draft-king-pce-inter-area-as-applicability-02.txt as a PCE 
    Wg</DIV>
    <DIV>document ?</DIV>
    <DIV><BR></DIV>
    <DIV>Thanks.</DIV>
    <DIV><BR></DIV>
    <DIV>JP.</DIV>
    <DIV>
    <DIV><BR>
    <DIV>Begin forwarded message:</DIV><BR class=Apple-interchange-newline>
    <BLOCKQUOTE type="cite">
      <DIV style="MARGIN: 0px"><SPAN 
      style="FONT-SIZE: medium; COLOR: rgb(0,0,0); FONT-FAMILY: 'Helvetica'"><B>From: 
      </B></SPAN><SPAN 
      style="FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'">"Daniel King" &lt;<A 
      href="mailto:daniel@olddog.co.uk" 
      moz-do-not-send="true">daniel@olddog.co.uk</A>&gt;<BR></SPAN></DIV>
      <DIV style="MARGIN: 0px"><SPAN 
      style="FONT-SIZE: medium; COLOR: rgb(0,0,0); FONT-FAMILY: 'Helvetica'"><B>Date: 
      </B></SPAN><SPAN 
      style="FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'">October 11, 2010 
      11:28:10 PM GMT+02:00<BR></SPAN></DIV>
      <DIV style="MARGIN: 0px"><SPAN 
      style="FONT-SIZE: medium; COLOR: rgb(0,0,0); FONT-FAMILY: 'Helvetica'"><B>To: 
      </B></SPAN><SPAN 
      style="FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'">&lt;<A 
      href="mailto:pce@ietf.org" 
      moz-do-not-send="true">pce@ietf.org</A>&gt;<BR></SPAN></DIV>
      <DIV style="MARGIN: 0px"><SPAN 
      style="FONT-SIZE: medium; COLOR: rgb(0,0,0); FONT-FAMILY: 'Helvetica'"><B>Cc: 
      </B></SPAN><SPAN style="FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'"><A 
      href="mailto:olivier.dugeon@orange-ftgroup.com" 
      moz-do-not-send="true">olivier.dugeon@orange-ftgroup.com</A>, <A 
      href="mailto:fjjc@tid.es" moz-do-not-send="true">fjjc@tid.es</A>, <A 
      href="mailto:qzhao@huawei.com" 
      moz-do-not-send="true">qzhao@huawei.com</A><BR></SPAN></DIV>
      <DIV style="MARGIN: 0px"><SPAN 
      style="FONT-SIZE: medium; COLOR: rgb(0,0,0); FONT-FAMILY: 'Helvetica'"><B>Subject: 
      </B></SPAN><SPAN 
      style="FONT-SIZE: medium; FONT-FAMILY: 'Helvetica'"><B>[Pce] I-D 
      Action:draft-king-pce-inter-area-as-applicability-02.txt</B><BR></SPAN></DIV><BR>
      <DIV>Hi PCE'rs, <BR><BR>Please find a new version of our 
      pce-inter-area-as-applicability draft: <BR><BR><A 
      href="http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt" 
      moz-do-not-send="true">http://www.ietf.org/id/draft-king-pce-inter-area-as-applicability-02.txt</A><BR><BR>This 
      document examines the applicability of the PCE architecture, 
      protocols,<BR>and protocol extensions for computing multi-area and 
      multi-AS paths in MPLS<BR>and GMPLS networks.<BR><BR>This revision 
      combines the addition of new co-authors and various 
      updates<BR>including:<BR><BR>- Discussion on domain meshes. <BR>- 
      Discussion on route diversity. <BR>- Discussion on synchronized path 
      computations. <BR>- Minor readability updates. <BR>- Minor grammar and nit 
      fixes.<BR><BR>The document is not complete and will require further 
      revisions. It is<BR>however a good platform to build upon and as always we 
      seek WG feedback and<BR>suggestions.<BR><BR>See you in Beijing!<BR><SPAN 
      class=Apple-tab-span style="WHITE-SPACE: pre"></SPAN><BR>Br, 
      Dan<BR><BR>_______________________________________________<BR>Pce mailing 
      list<BR><A class=moz-txt-link-abbreviated 
      href="mailto:Pce@ietf.org">Pce@ietf.org</A><BR><A 
      class=moz-txt-link-freetext 
      href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</A><BR></DIV></BLOCKQUOTE></DIV><BR></DIV><PRE wrap=""><FIELDSET class=mimeAttachmentHeader></FIELDSET>
_______________________________________________
Pce mailing list
<A class=moz-txt-link-abbreviated href="mailto:Pce@ietf.org">Pce@ietf.org</A>
<A class=moz-txt-link-freetext href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</A>
</PRE></BLOCKQUOTE>
  <P>
  <HR>

  <P></P>_______________________________________________<BR>Pce mailing 
  list<BR>Pce@ietf.org<BR>https://www.ietf.org/mailman/listinfo/pce<BR></BLOCKQUOTE></BODY></HTML>

--Boundary_(ID_B07VKGbiywwClqLY6A20dg)--

From jpv@cisco.com  Sun Oct 17 22:40:59 2010
Return-Path: <jpv@cisco.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3A8AB3A6A87 for <pce@core3.amsl.com>; Sun, 17 Oct 2010 22:40:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.226
X-Spam-Level: 
X-Spam-Status: No, score=-106.226 tagged_above=-999 required=5 tests=[AWL=-3.628, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQxcmchYTI1S for <pce@core3.amsl.com>; Sun, 17 Oct 2010 22:40:57 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id 450413A6ADB for <pce@ietf.org>; Sun, 17 Oct 2010 22:40:57 -0700 (PDT)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AswEAH97u0yQ/khMgWdsb2JhbACBRZ9jFQEBFiIinyubYoVJBIpKgws
X-IronPort-AV: E=Sophos;i="4.57,345,1283731200"; d="scan'208,217";a="11496140"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 18 Oct 2010 05:42:24 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id o9I5gOsH013651; Mon, 18 Oct 2010 05:42:24 GMT
Received: from xfe-ams-102.cisco.com ([144.254.231.94]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 18 Oct 2010 07:42:24 +0200
Received: from ams-jvasseur-8716.cisco.com ([10.55.201.135]) by xfe-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 18 Oct 2010 07:42:23 +0200
From: JP Vasseur <jpv@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-2--164302495
Date: Mon, 18 Oct 2010 07:42:22 +0200
Message-Id: <FB4D7FCB-5A7B-4541-99B6-27451E9AA5A7@cisco.com>
To: pce@ietf.org, Dan King <daniel@olddog.co.uk>
Mime-Version: 1.0 (Apple Message framework v1081)
X-Mailer: Apple Mail (2.1081)
X-OriginalArrivalTime: 18 Oct 2010 05:42:23.0468 (UTC) FILETIME=[3D15F2C0:01CB6E87]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.500.1024-17710.004
X-TM-AS-Result: No--8.430900-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Subject: [Pce] Adoption of draft-king-pce-inter-area-as-applicability-02.txt as	 a PCE WG document
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 05:40:59 -0000

--Apple-Mail-2--164302495
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear authors,

There is a consensus to adopt =
draft-king-pce-inter-area-as-applicability-02.txt as a PCE WG document.

Please resubmit as draft-ietf-pce-inter-area-as-applicability-00.txt =
with no change other than dates, name and title.

Thanks.

JP.=

--Apple-Mail-2--164302495
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear authors,<div><br></div><div>There is a consensus to adopt&nbsp;<span class="Apple-style-span" style="font-size: 14px; "><b>draft-king-pce-inter-area-as-applicability-02.txt as&nbsp;a PCE WG document.</b></span></div><div><span class="Apple-style-span" style="font-size: 14px; "><b><br></b></span></div><div><b><span class="Apple-style-span" style="font-weight: normal; ">Please resubmit as draft-ietf-pce-inter-area-as-applicability-00.txt with no change other than dates, name and title.</span></b></div><div><b><span class="Apple-style-span" style="font-weight: normal; "><br></span></b></div><div><b><span class="Apple-style-span" style="font-weight: normal; ">Thanks.</span></b></div><div><b><span class="Apple-style-span" style="font-weight: normal; "><br></span></b></div><div>JP.</div></body></html>
--Apple-Mail-2--164302495--

From root@core3.amsl.com  Mon Oct 18 03:45:01 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id AC1E33A6D68; Mon, 18 Oct 2010 03:45:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101018104501.AC1E33A6D68@core3.amsl.com>
Date: Mon, 18 Oct 2010 03:45:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-inter-area-as-applicability-00.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 10:45:01 -0000

--NextPart

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


	Title           : Applicability of the Path Computation Element to Inter-Area and Inter-AS MPLS and GMPLS Traffic Engineering
	Author(s)       : D. King, et al.
	Filename        : draft-ietf-pce-inter-area-as-applicability-00.txt
	Pages           : 17
	Date            : 2010-10-18

The Path Computation Element (PCE) may be used for computing services 
that traverse multi-area and multi-AS Multiprotocol Label Switching 
(MPLS) and Generalized MPLS (GMPLS) Traffic Engineered (TE) networks. 

This document examines the applicability of the PCE architecture,
protocols, and protocol extensions for computing multi-area and
multi-AS paths in MPLS and GMPLS networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-area-as-applicability-00.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-pce-inter-area-as-applicability-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-18034402.I-D@ietf.org>


--NextPart--

From ogondio@tid.es  Mon Oct 18 06:55:05 2010
Return-Path: <ogondio@tid.es>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 041573A69DF for <pce@core3.amsl.com>; Mon, 18 Oct 2010 06:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.632
X-Spam-Level: 
X-Spam-Status: No, score=-3.632 tagged_above=-999 required=5 tests=[AWL=-1.334, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4w0-EElpt3Qo for <pce@core3.amsl.com>; Mon, 18 Oct 2010 06:55:00 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by core3.amsl.com (Postfix) with ESMTP id 6CFEF3A67AD for <pce@ietf.org>; Mon, 18 Oct 2010 06:55:00 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LAH000A9O23K8@tid.hi.inet> for pce@ietf.org; Mon, 18 Oct 2010 15:56:27 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Brightmail Gateway) with SMTP id B8.A2.02820.E025CBC4; Mon, 18 Oct 2010 15:56:30 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0LAH000A6O23K8@tid.hi.inet> for pce@ietf.org; Mon, 18 Oct 2010 15:56:27 +0200 (MEST)
Received: from EXCLU2K7.hi.inet ([10.95.67.65]) by htcasmad1.hi.inet ([192.168.0.1]) with mapi; Mon, 18 Oct 2010 15:56:27 +0200
Date: Mon, 18 Oct 2010 15:56:26 +0200
From: =?iso-8859-1?Q?Oscar_Gonz=E1lez_de_Dios?= <ogondio@tid.es>
To: "pce@ietf.org" <pce@ietf.org>
Message-id: <DDC46D6645A1BB448DBD92E06A6401DA4F51F888AE@EXCLU2K7.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_F3p2k+qLRkjUZU8losEDPA)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: New draf: PCEP Extensions for Temporary Reservation of Computed Path Resources and  Support for Limited Context State in PCE
Thread-index: ActuzEG2fmoaKUZTRFqzpzBrzJIXNA==
acceptlanguage: es-ES, en-US
X-AuditID: 0a5f4068-b7bfbae000000b04-be-4cbc520e868f
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: AAAAAA==
Subject: [Pce] New draf: PCEP Extensions for Temporary Reservation of Computed Path Resources and Support for Limited Context State in PCE
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 13:55:05 -0000

--Boundary_(ID_F3p2k+qLRkjUZU8losEDPA)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

Dear PCErs

                We have submitted a new draft called "PCEP Extensions for T=
emporary Reservation of Computed Path Resources and  Support for Limited Co=
ntext State in PCE". You can find it in http://tools.ietf.org/id/draft-gonz=
alezdedios-pce-resv-res-context-state-00.txt.

As it was pointed out in the PCE Architecture RFC, a limited form of statef=
ulness is useful to improve PCE functionality  in situations in which the l=
ocal TED might not be up to date, or in the case of concurrent requests whe=
re most of the LSPs are computed
   before the end of the set-up of the LSPs when the TED is updated.  The P=
CE can retain some context from the resources assigned to Path  Requests du=
ring a certain period of time, so that it avoids  suggesting the use of the=
 same resources for subsequent TE LSPs.

 The draft we have submitted proposes an extension to the PCEP protocol to =
allow the PCC to request the PCE to block or reserve the resources computed=
 in a path request of a TE LSP for subsequent requests for a certain time.

                Please consider taking a look at the draft and send us your=
 opinion and comments,

                Best Regards,

                               =D3scar


--Boundary_(ID_F3p2k+qLRkjUZU8losEDPA)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EstiloCorreo17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 3.0cm 70.85pt 3.0cm;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DES link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span lang=3DEN-US>Dear PCErs<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 We have submitted a new
draft called &#8220;PCEP Extensions for Temporary Reservation of Computed P=
ath
Resources and=A0 Support for Limited Context State in PCE&#8221;. You can f=
ind it
in <a
href=3D"http://tools.ietf.org/id/draft-gonzalezdedios-pce-resv-res-context-=
state-00.txt">http://tools.ietf.org/id/draft-gonzalezdedios-pce-resv-res-co=
ntext-state-00.txt</a>.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-indent:35.4pt'><span lang=3DEN-US>As it =
was pointed
out in the PCE Architecture RFC, a limited form of statefulness is useful t=
o
improve PCE functionality=A0 in situations in which the local TED might not=
 be up
to date, or in the case of concurrent requests where most of the LSPs are
computed<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>=A0=A0 before the end of the set-up=
 of the LSPs
when the TED is updated.=A0 The PCE can retain some context from the resour=
ces
assigned to Path=A0 Requests during a certain period of time, so that it av=
oids=A0
suggesting the use of the same resources for subsequent TE LSPs.<o:p></o:p>=
</span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-indent:35.4pt'><span lang=3DEN-US>=A0The=
 draft we
have submitted proposes an extension to the PCEP protocol to allow the PCC =
to
request the PCE to block or reserve the resources computed in a path reques=
t of
a TE LSP for subsequent requests for a certain time.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 Please consider taking a
look at the draft and send us your opinion and comments,<o:p></o:p></span><=
/p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 Best Regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =D3scar<o:p></o:p=
></span></p>

<p class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

--Boundary_(ID_F3p2k+qLRkjUZU8losEDPA)--

From meral.shirazipour@polymtl.ca  Mon Oct 18 11:36:35 2010
Return-Path: <meral.shirazipour@polymtl.ca>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 518323A6B8F for <pce@core3.amsl.com>; Mon, 18 Oct 2010 11:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GtnhVJMRGhiG for <pce@core3.amsl.com>; Mon, 18 Oct 2010 11:36:33 -0700 (PDT)
Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by core3.amsl.com (Postfix) with ESMTP id C81C33A6B90 for <pce@ietf.org>; Mon, 18 Oct 2010 11:36:33 -0700 (PDT)
Received: from localhost (imp-4-3.polymtl.ca [132.207.4.78]) by smtp.polymtl.ca (8.14.3/8.14.3) with ESMTP id o9IIbsjP017097; Mon, 18 Oct 2010 14:37:58 -0400
Received: from lmcpra.ericsson.ca (lmcpra.ericsson.ca [192.75.88.231]) by www.imp.polymtl.ca (Horde MIME library) with HTTP; Mon, 18 Oct 2010 14:37:51 -0400
Message-ID: <20101018143751.burogva9uscoggsc@www.imp.polymtl.ca>
Date: Mon, 18 Oct 2010 14:37:51 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: pce@ietf.org
References: <DDC46D6645A1BB448DBD92E06A6401DA4F51F888AE@EXCLU2K7.hi.inet>
In-Reply-To: <DDC46D6645A1BB448DBD92E06A6401DA4F51F888AE@EXCLU2K7.hi.inet>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Poly-FromMTA: (imp-4-3.polymtl.ca [132.207.4.78]) at Mon, 18 Oct 2010 18:37:54 +0000
Subject: Re: [Pce] New draf: PCEP Extensions for Temporary Reservation of	Computed Path Resources and Support for Limited Context State in PCE
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 18:36:35 -0000

Hi,

I think the extensions proposed by this draft are extremely important 
and necessary for a real scale deployment of the PCE architecture.

Please see comments/questions below.

(1)
The idea of resource pre-reservation (reservation) by the PCE is very 
useful especially when multiple sequential PCEs are in play (i.e. not 
one PCE can provide the end-to-end path). Given the distributed nature 
of the problem, determining the correct reservation time is not trivial.

The necessary PCEP extensions might slightly vary depending on the 
method used to determine and convey the reservation times. Therefore it 
is crucial to determine the method(s) before finalizing the PCEP 
extensions.



(2)
Section 3.1:
"The RESERVATION object is optional in a PCReq message.  Multiple
   instances of the object MUST NOT be used on a single PCReq message
   and if a PCE finds multiple instances of the object it MUST use the
   first one and discard the rest (Editors note: alternatively, it could
   send a PCErr).  The RESERVATION object may appear either at an
   individual request level or within a SVEC.  The latter means that the
   RESERVATION object applies to all requests involved in the SVEC
   object. "


What is the reason to not allow a RESERVATION object "per path" request?
Isn't it too limiting to say that all path requests within the SVEC 
will need to apply the same RESERVATION object?


(3)
Section 3.5:
"A PCE MAY apply reservations as a means of internal policy and/or operatio=
n."

I would ad an example for this, as it is significant/high impact 
operational practice: an example could be when the rate of incoming 
path requests reaches a given threshold value, the PCE may decide to 
apply reservations.

(4)
Section 3.5, The reservation timer:
"Timer is the value in ms of the time that the resources are blocked"

Is this a relative time? Would is be better to convey this information 
as an absolute time?
In any case, what should the format be?


(5)
Section 4, Page 13,
"Send the Responses (successful or not) using PCRep message(s) and, 
where appropriate, indicate the level of reservation and associated 
period. "

Same question as in 4) : how to interpret this period? (6)
Section 4:
"Specify what level of reservation to apply after the request."

What is level here? Granularity or path level vs SVEC level?


(7) Section 5, use cases. We should discuss various path computation 
methods e.g. BRPC (RFC5441), draft-king-pce-hierarchy-fwk-05, etc.
This discussion may bring new insights as what is the best method for 
determining the reservation time: see comment (1) above



(8)
5.2 and 5.3 , I don't quite see why they are separated.
In 5.2, if a path is returned and a domain sequence is selected, what 
guarantees that once we try to compute a path (5.3) the resources will 
be available? To avoid confusion I will discuss these in one section 
and point out that reservation requests should be applied carefully 
when interrogating multiple PCEs in multiple domains?



(9)
Is it a possibility to have request priorities associated with the 
reservations? Will this be policy based applied per PCE?



Best Regards,
Meral







Oscar Gonz=E1lez de Dios <ogondio@tid.es> a =C3=A9crit=C2=A0:

> Dear PCErs
>
>                We have submitted a new draft called "PCEP Extensions 
> for Temporary Reservation of Computed Path Resources and  Support for 
> Limited Context State in PCE". You can find it in 
> http://tools.ietf.org/id/draft-gonzalezdedios-pce-resv-res-context-state-=
00.txt.
>
> As it was pointed out in the PCE Architecture RFC, a limited form of 
> statefulness is useful to improve PCE functionality  in situations in 
> which the local TED might not be up to date, or in the case of 
> concurrent requests where most of the LSPs are computed
>   before the end of the set-up of the LSPs when the TED is updated.  
> The PCE can retain some context from the resources assigned to Path  
> Requests during a certain period of time, so that it avoids  
> suggesting the use of the same resources for subsequent TE LSPs.
>
> The draft we have submitted proposes an extension to the PCEP 
> protocol to allow the PCC to request the PCE to block or reserve the 
> resources computed in a path request of a TE LSP for subsequent 
> requests for a certain time.
>
>                Please consider taking a look at the draft and send us 
> your opinion and comments,
>
>                Best Regards,
>
>                               =D3scar
>
>




From ramon.casellas@cttc.es  Mon Oct 18 13:37:22 2010
Return-Path: <ramon.casellas@cttc.es>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 551E53A6AA7 for <pce@core3.amsl.com>; Mon, 18 Oct 2010 13:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U21CW+a4WMpd for <pce@core3.amsl.com>; Mon, 18 Oct 2010 13:37:17 -0700 (PDT)
Received: from aries.cttc.es (aries.cttc.es [84.88.62.194]) by core3.amsl.com (Postfix) with ESMTP id AFB243A6A12 for <pce@ietf.org>; Mon, 18 Oct 2010 13:37:14 -0700 (PDT)
Received: from webmail.cttc.es (web.cttc.es [84.88.62.199]) (authenticated bits=0) by aries.cttc.es (8.13.8/8.13.8) with ESMTP id o9IKcfsl015286; Mon, 18 Oct 2010 22:38:41 +0200
Received: from 62.83.143.151 (SquirrelMail authenticated user rcasellas) by webmail.cttc.es with HTTP; Mon, 18 Oct 2010 22:44:06 +0200 (CEST)
Message-ID: <64491.62.83.143.151.1287434646.squirrel@webmail.cttc.es>
In-Reply-To: <20101018143751.burogva9uscoggsc@www.imp.polymtl.ca>
References: <DDC46D6645A1BB448DBD92E06A6401DA4F51F888AE@EXCLU2K7.hi.inet> <20101018143751.burogva9uscoggsc@www.imp.polymtl.ca>
Date: Mon, 18 Oct 2010 22:44:06 +0200 (CEST)
From: "Ramon Casellas" <ramon.casellas@cttc.es>
To: "Meral Shirazipour" <meral.shirazipour@polymtl.ca>
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Cc: pce@ietf.org
Subject: Re: [Pce] New draf: PCEP Extensions for Temporary Reservation of	Computed Path Resources and Support for Limited Context State in PCE
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 20:37:22 -0000

Dear Meral, all,

On Mon, October 18, 2010 8:37 pm, Meral Shirazipour wrote:

> I think the extensions proposed by this draft are extremely important
> and necessary for a real scale deployment of the PCE architecture.

Thank you for your supportive words, and for your insightful comments,
they clearly pin-point room for improvements, and open issues.  Please see
inline.


> (1)
> The idea of resource pre-reservation (reservation) by the PCE is very
> useful especially when multiple sequential PCEs are in play (i.e. not
> one PCE can provide the end-to-end path). Given the distributed nature
> of the problem, determining the correct reservation time is not trivial.

Indeed. One of the first use cases was the intra-domain case and the
compute-setup-update_ted cycle, but the multi-domain and collaborative PCE
setting (sequential or hierarchical) should definitely be considered
carefully: on the one hand, we believe it may be a good idea to reserve
resources in an upstream PCE to avoid contention or another request
"stealing" the resources while the PCE is e.g. waiting for a downstream
response and similar examples.
However, it is also true that in approaches such as BRPC, the number of
potential path segments to be concatenated may grow significantly and
reserving for all of them may cause excessive reservations. In short, yes,
not only the reservation time is critical but also the fact that
reservations for the VSPT paths (except the one that is part of the e2e
path) should be avoided.

> The necessary PCEP extensions might slightly vary depending on the
> method used to determine and convey the reservation times. Therefore it
> is crucial to determine the method(s) before finalizing the PCEP
> extensions.

Yes, although for now the actual determination of the reservation time is
still open. As a main guideline, it should be of the order of the setup
delay or, more precisely of the compute-setup-update. This is mainly
driven by the original use case.

>
>
> (2)
> Section 3.1:
> "The RESERVATION object is optional in a PCReq message.  Multiple
>    instances of the object MUST NOT be used on a single PCReq message
>    and if a PCE finds multiple instances of the object it MUST use the
>    first one and discard the rest (Editors note: alternatively, it could
>    send a PCErr).  The RESERVATION object may appear either at an
>    individual request level or within a SVEC.  The latter means that the
>    RESERVATION object applies to all requests involved in the SVEC
>    object. "

>
> What is the reason to not allow a RESERVATION object "per path" request?
> Isn't it too limiting to say that all path requests within the SVEC
> will need to apply the same RESERVATION object?

Thanks for catching this up. In fact, I'm afraid that the current text is
not correct. it should say : "the RESERVATION object is optional in a
request [within a PCReq message] (...) MUST NOT be used on a single
request."

The intended behavior is to allow different reservations per request and
per path (i.e. when a response has more than one path, all reservations
are distinct): the pcc requests a reservation within the request, and the
PCE assigns a reservation for every single path (the RESERVATION_CONF
response is an attribute of the path). In other words, typical usage would
be: N:1 requests within a PCReq message with (up to) N reservation
requests (RESERVATIONS) and, if a response contains M paths, there are (up
to) M actual reservations (_CONFs) with distinct reservation identifiers.

The exception for this is when the RESERVATION object appears at the SVEC
tuple level: in that case it is assumed that the same reservation
parameters apply to all requests referred to in the SVEC tuple. This does
not preclude that the PCE assigns different reservations (in fact
different reservation ids) to individual paths (thus a PCC may cancel
individual reservations bound to some of the paths within a request).

Note that you can have a SVEC yet individual requests have different
RESERVATION objects.

It has been left for next version the possibility, for a PCC, to specify
whether it requests the same reservation for all the paths or individual
reservations for each path. A flag could be added to mean "all paths for a
single request/response should share the same reservation so, if it is
cancelled, all they are."



> (3)
> Section 3.5:
> "A PCE MAY apply reservations as a means of internal policy and/or
> operation."
>
> I would ad an example for this, as it is significant/high impact
> operational practice: an example could be when the rate of incoming
> path requests reaches a given threshold value, the PCE may decide to
> apply reservations.

Good point. We will try to update the draft with this (more generally,
referring to the selection of the timer and how this impacts PCE behavior
and the relationship with what the client actually requests). Currently,
it is pcc-driven + PCE policy-checked.


> (4)
> Section 3.5, The reservation timer:
> "Timer is the value in ms of the time that the resources are blocked"
>
> Is this a relative time? Would is be better to convey this information
> as an absolute time?
> In any case, what should the format be?

We have considered a relative amount of milliseconds, encoded as a
uint32_t, indicating the amount of time the reservation is to be applied
(thus resources excluded) right after the computation. However, in
multi-domain path computations, it may be a good idea to also consider the
possibility to reserve resources at the point when a request is
sent/forwarded to a downstream / parent PCE, not only when the computation
is finished.

We have not considered (but I think we should!) absolute timestamps.
Having a common deadline for all resources and all involved PCEs
regardless of the latency until they get the request seems a valid option.
I guess in this case it should be encoded in UTC or GMT, using timestamps
(ISO format, or some equivalent?)



>
> (5)
> Section 4, Page 13,
> "Send the Responses (successful or not) using PCRep message(s) and,
> where appropriate, indicate the level of reservation and associated
> period. "
>
> Same question as in 4) : how to interpret this period? (6)

For now, in the lines of "I'll be reserving the resources for this amount
of ms, right after I finished the computation" (i.e. relative values +
some unknown offset encompassing the "latency" from the PCE to the PCC).
The same comment applies regardless absolute times. I think this may be a
valid addition for -01



> Section 4:
> "Specify what level of reservation to apply after the request."
>
> What is level here? Granularity or path level vs SVEC level?

Level here means either "basic" resource (wavelength, bandwidth, Timeslot,
Tributary) with regard to any other more "aggressive" reservation
excluding link/node/srlg.



>
> (7) Section 5, use cases. We should discuss various path computation
> methods e.g. BRPC (RFC5441), draft-king-pce-hierarchy-fwk-05, etc.
> This discussion may bring new insights as what is the best method for
> determining the reservation time: see comment (1) above


Completely agreed. I am not (yet?) confident enough to comment on this but
definitely a work item.



> (8)
> 5.2 and 5.3 , I don't quite see why they are separated.
> In 5.2, if a path is returned and a domain sequence is selected, what
> guarantees that once we try to compute a path (5.3) the resources will
> be available? To avoid confusion I will discuss these in one section
> and point out that reservation requests should be applied carefully
> when interrogating multiple PCEs in multiple domains?

The idea is that if, for some reason, domain sequence selection is
decoupled from path computation (e.g. a parent PCE just returns a list of
domains so the ingress PCE is able to apply BRPC), reservation should be
applied during BRPC. The wording should be improved though. This does not
solve the issue of excessive reservations, as mentioned above.


>
>
> (9)
> Is it a possibility to have request priorities associated with the
> reservations? Will this be policy based applied per PCE?

I am not sure. I guess that managing priorities and (eventually)
preemption seems a logical extension to the proposed mechanism, but we
would need to think about it (do you have a use case in mind?) but right
now we simply considered having an exclusive flag with binary state
(reserved/not reserved) for a given resource. The original scope is to
allow some context state, and although priorities would extend this by
tagging a resource with a current priority (plus some extra book-keeping),
I tend to think that leaving the room for over-engineering resource
reservation protocol within PCEP would be out of scope, raising more
questions than it solves :-)


I hope this clarifies at least some of your questions. We will discuss
your points to improve the idea.

Thanks for reading

Ramon,



>
>
> Oscar González de Dios <ogondio@tid.es> a Ã©critÂ :
>
>> Dear PCErs
>>
>>                We have submitted a new draft called "PCEP Extensions
>> for Temporary Reservation of Computed Path Resources and  Support for
>> Limited Context State in PCE". You can find it in
>> http://tools.ietf.org/id/draft-gonzalezdedios-pce-resv-res-context-state-00.txt.
>>
>> As it was pointed out in the PCE Architecture RFC, a limited form of
>> statefulness is useful to improve PCE functionality  in situations in
>> which the local TED might not be up to date, or in the case of
>> concurrent requests where most of the LSPs are computed
>>   before the end of the set-up of the LSPs when the TED is updated.
>> The PCE can retain some context from the resources assigned to Path
>> Requests during a certain period of time, so that it avoids
>> suggesting the use of the same resources for subsequent TE LSPs.
>>
>> The draft we have submitted proposes an extension to the PCEP
>> protocol to allow the PCC to request the PCE to block or reserve the
>> resources computed in a path request of a TE LSP for subsequent
>> requests for a certain time.
>>
>>                Please consider taking a look at the draft and send us
>> your opinion and comments,
>>
>>                Best Regards,
>>
>>                               Óscar
>>
>>
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>


-- 



From root@core3.amsl.com  Tue Oct 19 20:15:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 1ED613A6997; Tue, 19 Oct 2010 20:15:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101020031502.1ED613A6997@core3.amsl.com>
Date: Tue, 19 Oct 2010 20:15:02 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-gmpls-aps-req-03.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 03:15:02 -0000

--NextPart

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


	Title           : Document: draft-ietf-pce-gmpls-aps-req-03.txt
	Author(s)       : T. Otani, et al.
	Filename        : draft-ietf-pce-gmpls-aps-req-03.txt
	Pages           : 12
	Date            : 2010-10-19

The initial effort of PCE WG is specifically focused on MPLS (Multi-
protocol label switching). As a next step, this draft describes 
functional requirements for GMPLS (Generalized MPLS) application of 
PCE (Path computation element).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-gmpls-aps-req-03.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-pce-gmpls-aps-req-03.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-19200802.I-D@ietf.org>


--NextPart--

From meral.shirazipour@polymtl.ca  Wed Oct 20 11:24:04 2010
Return-Path: <meral.shirazipour@polymtl.ca>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C25D43A6838 for <pce@core3.amsl.com>; Wed, 20 Oct 2010 11:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeccRcj77QLW for <pce@core3.amsl.com>; Wed, 20 Oct 2010 11:24:03 -0700 (PDT)
Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by core3.amsl.com (Postfix) with ESMTP id E88533A67D9 for <pce@ietf.org>; Wed, 20 Oct 2010 11:24:02 -0700 (PDT)
Received: from localhost (imp-4-3.polymtl.ca [132.207.4.78]) by smtp.polymtl.ca (8.14.3/8.14.3) with ESMTP id o9KIPMG6031497; Wed, 20 Oct 2010 14:25:24 -0400
Received: from lmcpra.ericsson.ca (lmcpra.ericsson.ca [192.75.88.231]) by www.imp.polymtl.ca (Horde MIME library) with HTTP; Wed, 20 Oct 2010 14:25:21 -0400
Message-ID: <20101020142521.ca9u9i8n4ws8www4@www.imp.polymtl.ca>
Date: Wed, 20 Oct 2010 14:25:21 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: Ramon Casellas <ramon.casellas@cttc.es>
References: <DDC46D6645A1BB448DBD92E06A6401DA4F51F888AE@EXCLU2K7.hi.inet> <20101018143751.burogva9uscoggsc@www.imp.polymtl.ca> <64491.62.83.143.151.1287434646.squirrel@webmail.cttc.es>
In-Reply-To: <64491.62.83.143.151.1287434646.squirrel@webmail.cttc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.0.4)
X-Poly-FromMTA: (imp-4-3.polymtl.ca [132.207.4.78]) at Wed, 20 Oct 2010 18:25:22 +0000
Cc: "pce@ietf.org" <pce@ietf.org>
Subject: Re: [Pce] New draf: PCEP Extensions for Temporary Reservation of Computed Path Resources and Support for Limited Context State in PCE
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Oct 2010 18:24:04 -0000

Hi,

    Thank you Ramon for the detailed explanations. Please see inline.


> Dear Meral, all,
>
> On Mon, October 18, 2010 8:37 pm, Meral Shirazipour wrote:
>
>> I think the extensions proposed by this draft are extremely important
>> and necessary for a real scale deployment of the PCE architecture.
>
> Thank you for your supportive words, and for your insightful comments,
> they clearly pin-point room for improvements, and open issues.  Please se=
e
> inline.
>
>
>> (1)
>> The idea of resource pre-reservation (reservation) by the PCE is very
>> useful especially when multiple sequential PCEs are in play (i.e. not
>> one PCE can provide the end-to-end path). Given the distributed nature
>> of the problem, determining the correct reservation time is not trivial.
>
> Indeed. One of the first use cases was the intra-domain case and the
> compute-setup-update_ted cycle, but the multi-domain and collaborative PC=
E
> setting (sequential or hierarchical) should definitely be considered
> carefully: on the one hand, we believe it may be a good idea to reserve
> resources in an upstream PCE to avoid contention or another request
> "stealing" the resources while the PCE is e.g. waiting for a downstream
> response and similar examples.


By intra-domain do you mean single PCE scenarios? Because I believe in 
the same domain (AS or Area) we can deploy multiple PCEs, sharing or 
not the same TED. I believe that the reservation extensions proposed by 
this draft are valid for both single and multiple PCE scenarios (with 
probably more benefits in the multiple PCE case).




> However, it is also true that in approaches such as BRPC, the number of
> potential path segments to be concatenated may grow significantly and
> reserving for all of them may cause excessive reservations. In short, yes=
,
> not only the reservation time is critical but also the fact that
> reservations for the VSPT paths (except the one that is part of the e2e
> path) should be avoided.


I don't think that reservation should be avoided in all BRPC cases. 
Depending on the case at hand, it may be more beneficial to reserve 
resources (along the VSPT) with the 'right' reservation times to avoid 
blockage at deployment time. One such example is when the PCEs are 
triggered at a higher rate than usual and where not reserving causes 
high chances of blockage at LSP signaling time.


>> The necessary PCEP extensions might slightly vary depending on the
>> method used to determine and convey the reservation times. Therefore it
>> is crucial to determine the method(s) before finalizing the PCEP
>> extensions.
>
> Yes, although for now the actual determination of the reservation time is
> still open. As a main guideline, it should be of the order of the setup
> delay or, more precisely of the compute-setup-update. This is mainly
> driven by the original use case.


This is good and unfortunately determining the right reservation times 
is not a trivial question. Looking forward to discuss it further with 
you and the co-authors:)


>>
>>
>> (2)
>> Section 3.1:
>> "The RESERVATION object is optional in a PCReq message.  Multiple
>>    instances of the object MUST NOT be used on a single PCReq message
>>    and if a PCE finds multiple instances of the object it MUST use the
>>    first one and discard the rest (Editors note: alternatively, it could
>>    send a PCErr).  The RESERVATION object may appear either at an
>>    individual request level or within a SVEC.  The latter means that the
>>    RESERVATION object applies to all requests involved in the SVEC
>>    object. "
>
>>
>> What is the reason to not allow a RESERVATION object "per path" request?
>> Isn't it too limiting to say that all path requests within the SVEC
>> will need to apply the same RESERVATION object?
>
> Thanks for catching this up. In fact, I'm afraid that the current text is
> not correct. it should say : "the RESERVATION object is optional in a
> request [within a PCReq message] (...) MUST NOT be used on a single
> request."


The new text makes perfect sense, thanks.


> The intended behavior is to allow different reservations per request and
> per path (i.e. when a response has more than one path, all reservations
> are distinct): the pcc requests a reservation within the request, and the
> PCE assigns a reservation for every single path (the RESERVATION_CONF
> response is an attribute of the path). In other words, typical usage woul=
d
> be: N:1 requests within a PCReq message with (up to) N reservation
> requests (RESERVATIONS) and, if a response contains M paths, there are (u=
p
> to) M actual reservations (_CONFs) with distinct reservation identifiers.


I completely agree.


> The exception for this is when the RESERVATION object appears at the SVEC
> tuple level: in that case it is assumed that the same reservation
> parameters apply to all requests referred to in the SVEC tuple. This does
> not preclude that the PCE assigns different reservations (in fact
> different reservation ids) to individual paths (thus a PCC may cancel
> individual reservations bound to some of the paths within a request).
>
> Note that you can have a SVEC yet individual requests have different
> RESERVATION objects.
>
> It has been left for next version the possibility, for a PCC, to specify
> whether it requests the same reservation for all the paths or individual
> reservations for each path. A flag could be added to mean "all paths for =
a
> single request/response should share the same reservation so, if it is
> cancelled, all they are."


At first glance I would recommend assigning the same value as the 
Request-ID-number to the reservation ID. This way any path request 
inside a PCReq that requires a reservation will also have its own 
reservation ID irrespective of being part of a SVEC or not. This may 
also make it easier to match the reservation to the right LSP at 
signaling time?



>> (3)
>> Section 3.5:
>> "A PCE MAY apply reservations as a means of internal policy and/or
>> operation."
>>
>> I would ad an example for this, as it is significant/high impact
>> operational practice: an example could be when the rate of incoming
>> path requests reaches a given threshold value, the PCE may decide to
>> apply reservations.
>
> Good point. We will try to update the draft with this (more generally,
> referring to the selection of the timer and how this impacts PCE behavior
> and the relationship with what the client actually requests). Currently,
> it is pcc-driven + PCE policy-checked.


Sounds good.



>> (4)
>> Section 3.5, The reservation timer:
>> "Timer is the value in ms of the time that the resources are blocked"
>>
>> Is this a relative time? Would is be better to convey this information
>> as an absolute time?
>> In any case, what should the format be?
>
> We have considered a relative amount of milliseconds, encoded as a
> uint32_t, indicating the amount of time the reservation is to be applied
> (thus resources excluded) right after the computation. However, in
> multi-domain path computations, it may be a good idea to also consider th=
e
> possibility to reserve resources at the point when a request is
> sent/forwarded to a downstream / parent PCE, not only when the computatio=
n
> is finished.


That is why I also think that it would be worth using absolute timestamps.




> We have not considered (but I think we should!) absolute timestamps.

I agree.


> Having a common deadline for all resources and all involved PCEs
> regardless of the latency until they get the request seems a valid option=
.
> I guess in this case it should be encoded in UTC or GMT, using timestamps
> (ISO format, or some equivalent?)
>

Yes, NTP or (ISO 8601 (?)) timestamps Another comment about Section 
3.3) Cancelling a Reservation:

Would it make sense to say this: A PCC that triggers more than once PCE 
with reservation requests SHOULD explicitly cancel the reservations on 
all other (remaining) PCEs as soon as it decides on using the path 
returned by one of them. That would avoid counting only on the 
reservations expiry times, and therefore avoid holding in reserve mode 
resources that the PCC does not plan to use?
>>
>> (5)
>> Section 4, Page 13,
>> "Send the Responses (successful or not) using PCRep message(s) and,
>> where appropriate, indicate the level of reservation and associated
>> period. "
>>
>> Same question as in 4) : how to interpret this period? (6)
>
> For now, in the lines of "I'll be reserving the resources for this amount
> of ms, right after I finished the computation" (i.e. relative values +
> some unknown offset encompassing the "latency" from the PCE to the PCC).
> The same comment applies regardless absolute times. I think this may be a
> valid addition for -01


agree, same comment as above on absolute timestamps.



>
>> Section 4:
>> "Specify what level of reservation to apply after the request."
>>
>> What is level here? Granularity or path level vs SVEC level?
>
> Level here means either "basic" resource (wavelength, bandwidth, Timeslot=
,
> Tributary) with regard to any other more "aggressive" reservation
> excluding link/node/srlg.
>

My confusion came from Section 3.1 which uses the word "level" as : 
"The RESERVATION object may appear either at an individual request 
level or within a SVEC. "


>
>>
>> (7) Section 5, use cases. We should discuss various path computation
>> methods e.g. BRPC (RFC5441), draft-king-pce-hierarchy-fwk-05, etc.
>> This discussion may bring new insights as what is the best method for
>> determining the reservation time: see comment (1) above
>
>
> Completely agreed. I am not (yet?) confident enough to comment on this bu=
t
> definitely a work item.

The WG?s help and feedbacks are going to be needed..

>
>> (8)
>> 5.2 and 5.3 , I don't quite see why they are separated.
>> In 5.2, if a path is returned and a domain sequence is selected, what
>> guarantees that once we try to compute a path (5.3) the resources will
>> be available? To avoid confusion I will discuss these in one section
>> and point out that reservation requests should be applied carefully
>> when interrogating multiple PCEs in multiple domains?
>
> The idea is that if, for some reason, domain sequence selection is
> decoupled from path computation (e.g. a parent PCE just returns a list of
> domains so the ingress PCE is able to apply BRPC), reservation should be
> applied during BRPC. The wording should be improved though. This does not
> solve the issue of excessive reservations, as mentioned above.
>

Ok.

>>
>>
>> (9)
>> Is it a possibility to have request priorities associated with the
>> reservations? Will this be policy based applied per PCE?
>
> I am not sure. I guess that managing priorities and (eventually)
> preemption seems a logical extension to the proposed mechanism, but we
> would need to think about it (do you have a use case in mind?) but right
> now we simply considered having an exclusive flag with binary state
> (reserved/not reserved) for a given resource. The original scope is to
> allow some context state, and although priorities would extend this by
> tagging a resource with a current priority (plus some extra book-keeping)=
,
> I tend to think that leaving the room for over-engineering resource
> reservation protocol within PCEP would be out of scope, raising more
> questions than it solves :-)


I raised this question by looking at the whole thing from a path 
computation algorithm perspective :) Also this addition may be be 
natural ...given the optional 3 bit PRI bits specified in the RP object 
(section 7.4.1 in RFC5440).
> I hope this clarifies at least some of your questions. We will discuss
> your points to improve the idea.
>
> Thanks for reading


Thank you for the clarifications.

> Ramon,



Best Regards,
Meral





>> Oscar Gonz=E1lez de Dios <ogondio@tid.es> a =C3=A9crit=C2=A0:
>>
>>> Dear PCErs
>>>
>>>                We have submitted a new draft called "PCEP Extensions
>>> for Temporary Reservation of Computed Path Resources and  Support for
>>> Limited Context State in PCE". You can find it in
>>> http://tools.ietf.org/id/draft-gonzalezdedios-pce-resv-res-context-stat=
e-00.txt.
>>>
>>> As it was pointed out in the PCE Architecture RFC, a limited form of
>>> statefulness is useful to improve PCE functionality  in situations in
>>> which the local TED might not be up to date, or in the case of
>>> concurrent requests where most of the LSPs are computed
>>>   before the end of the set-up of the LSPs when the TED is updated.
>>> The PCE can retain some context from the resources assigned to Path
>>> Requests during a certain period of time, so that it avoids
>>> suggesting the use of the same resources for subsequent TE LSPs.
>>>
>>> The draft we have submitted proposes an extension to the PCEP
>>> protocol to allow the PCC to request the PCE to block or reserve the
>>> resources computed in a path request of a TE LSP for subsequent
>>> requests for a certain time.
>>>
>>>                Please consider taking a look at the draft and send us
>>> your opinion and comments,
>>>
>>>                Best Regards,
>>>
>>>                               =D3scar
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce
>>
>
>
> --
>
>
>




From root@core3.amsl.com  Mon Oct 25 13:15:02 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 7FFC33A6AF4; Mon, 25 Oct 2010 13:15:02 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20101025201502.7FFC33A6AF4@core3.amsl.com>
Date: Mon, 25 Oct 2010 13:15:02 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-gmpls-pcep-extensions-01.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 20:15:02 -0000

--NextPart

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


	Title           : PCEP extensions for GMPLS
	Author(s)       : C. Margaria, et al.
	Filename        : draft-ietf-pce-gmpls-pcep-extensions-01.txt
	Pages           : 36
	Date            : 2010-10-25

This memo provides extensions for the Path Computation Element
communication Protocol (PCEP) for the support of GMPLS control plane.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-gmpls-pcep-extensions-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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: Message/External-body;
	name="draft-ietf-pce-gmpls-pcep-extensions-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-10-25130416.I-D@ietf.org>


--NextPart--

From julien.meuric@orange-ftgroup.com  Wed Oct 27 11:17:07 2010
Return-Path: <julien.meuric@orange-ftgroup.com>
X-Original-To: pce@core3.amsl.com
Delivered-To: pce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D51373A6996 for <pce@core3.amsl.com>; Wed, 27 Oct 2010 11:17:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.821
X-Spam-Level: 
X-Spam-Status: No, score=-101.821 tagged_above=-999 required=5 tests=[AWL=0.428, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wnfRR1AldGI for <pce@core3.amsl.com>; Wed, 27 Oct 2010 11:17:03 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id C32BA3A695B for <pce@ietf.org>; Wed, 27 Oct 2010 11:16:54 -0700 (PDT)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 161BD6C000C for <pce@ietf.org>; Wed, 27 Oct 2010 20:19:05 +0200 (CEST)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 0E6276C0009 for <pce@ietf.org>; Wed, 27 Oct 2010 20:19:05 +0200 (CEST)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 27 Oct 2010 20:18:42 +0200
Received: from [10.193.116.59] ([10.193.116.59]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 27 Oct 2010 20:18:43 +0200
Message-ID: <4CC86D01.4040306@orange-ftgroup.com>
Date: Wed, 27 Oct 2010 20:18:41 +0200
From: Julien Meuric <julien.meuric@orange-ftgroup.com>
Organization: France Telecom
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.12) Gecko/20100915 Lightning/1.0b1 Thunderbird/3.0.8
MIME-Version: 1.0
To: pce@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Oct 2010 18:18:43.0136 (UTC) FILETIME=[63318400:01CB7603]
Subject: [Pce] PCE Agenda for Beijing
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Path Computation Element  <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pce>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 18:17:07 -0000

Hi all.

The 1st draft of the PCE WG's agenda for IETF 79 is available: 
http://www.ietf.org/proceedings/79/agenda/pce.html

If you have any comments, please contact the chairs. Authors, do not 
wait for the meeting to start discussing your I-Ds on the mailing list.

Regards,

JP & Julien

