Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ?

JP Vasseur <jvasseur@cisco.com> Tue, 12 June 2007 20:16 UTC

Return-path: <pce-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCnA-0004ac-0L; Tue, 12 Jun 2007 16:16:40 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HyCn8-0004Zx-5H for pce@ietf.org; Tue, 12 Jun 2007 16:16:38 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HyCn6-0001FF-SG for pce@ietf.org; Tue, 12 Jun 2007 16:16:38 -0400
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 12 Jun 2007 16:16:36 -0400
X-IronPort-AV: i="4.16,412,1175486400"; d="scan'208"; a="123422029:sNHT47737702"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l5CKGa9c010528; Tue, 12 Jun 2007 16:16:36 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l5CKGaBk016118; Tue, 12 Jun 2007 20:16:36 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 16:16:20 -0400
Received: from [10.86.104.179] ([10.86.104.179]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 12 Jun 2007 16:16:19 -0400
In-Reply-To: <1181573369.466d60f9583ab@www.imp.polymtl.ca>
References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> <1181573369.466d60f9583ab@www.imp.polymtl.ca>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ?
Date: Tue, 12 Jun 2007 16:15:56 -0400
To: Meral Shirazipour <meral.shirazipour@polymtl.ca>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 12 Jun 2007 20:16:19.0955 (UTC) FILETIME=[8A0CE430:01C7AD2E]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1402; t=1181679396; x=1182543396; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jvasseur@cisco.com; z=From:=20JP=20Vasseur=20<jvasseur@cisco.com> |Subject:=20Re=3A=20[Pce]=20Adopting=20draft-lee-pce-global-concurrent-op timization-04.txt=09as=20a=20WG=20document=20? |Sender:=20 |To:=20Meral=20Shirazipour=20<meral.shirazipour@polymtl.ca>; bh=Tsk0Nm9jpz5Qf8B5y8vvlJ+F9GanMKmez+a6A11zkns=; b=XlOYmMPAlDHOvQi+191L1zCV6G3qksraYX3iSLUYNKVUZP3t8rIaPvqqmsQqFs1Vin3bWgXE Nb90mY1442n5WBRZO0Qeeafd+9i2GZ/sKBxN0y6dYqOqeItpf9aCmn1z;
Authentication-Results: rtp-dkim-2; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: "pce@ietf.org" <pce@ietf.org>
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi Meral,

On Jun 11, 2007, at 10:49 AM, Meral Shirazipour wrote:

> Hi,
> I would support this draft based on its content, but I only see one  
> problem: it
> does not consider or even refer to draft-ietf-pce-brpc-04.txt (or  
> maybe I
> missed it?).
> I would rather see a single draft covering all possible optimization
> scenarios/solutions based on the PCE architecture.
>

BRPC is a multi-PCE path computation technique used to compute a  
shortest constrained
inter-domain path wheres this ID specifies a (preferably) NMS based  
technique where a
set of path computation requests are bundled and send to a PCE with  
the objective of
"optimizing" the set of computed paths.

> Having several IDs for optimization applications is ok as long as  
> they refer to
> each other and maybe provide an <inter-working> section between the  
> different
> methods.

There is no real reason for referring to each other since there is no  
dependency.

Thanks.

JP.

>
> Cordially,
> Meral
>
>
>
> Selon JP Vasseur <jvasseur@cisco.com>:
>
>> Dear WG,
>>
>> Do you support the adoption of draft-lee-pce-global-concurrent-
>> optimization-04.txt as a Working Group document ?
>>
>> Thanks.
>>
>> JP.
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@lists.ietf.org
>> https://www1.ietf.org/mailman/listinfo/pce
>>
>

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