Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ?
Meral Shirazipour <meral.shirazipour@polymtl.ca> Fri, 15 June 2007 15:53 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 1HzE7Z-0005eh-4a; Fri, 15 Jun 2007 11:53:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzE7X-0005ec-UJ for pce@ietf.org; Fri, 15 Jun 2007 11:53:55 -0400
Received: from smtp.polymtl.ca ([132.207.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzE7X-0000WE-Ks for pce@ietf.org; Fri, 15 Jun 2007 11:53:55 -0400
Received: from localhost (imp-4-2.polymtl.ca [132.207.4.77]) by smtp.polymtl.ca (8.13.6/8.13.6) with ESMTP id l5FFrrU7004503; Fri, 15 Jun 2007 11:53:53 -0400
Received: from lmcprb.ericsson.ca (lmcprb.ericsson.ca [192.75.88.232]) by www.imp.polymtl.ca (IMP) with HTTP for <meshi@132.207.4.132>; Fri, 15 Jun 2007 11:53:55 -0400
Message-ID: <1181922835.4672b613b90d9@www.imp.polymtl.ca>
Date: Fri, 15 Jun 2007 11:53:55 -0400
From: Meral Shirazipour <meral.shirazipour@polymtl.ca>
To: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [Pce] Adopting draft-lee-pce-global-concurrent-optimization-04.txt as a WG document ?
References: <991B1574-7163-4B0F-A46E-F2D884BDB682@cisco.com> <1181573369.466d60f9583ab@www.imp.polymtl.ca> <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com>
In-Reply-To: <18233BB2-3F21-4F59-98C3-A99124E3103A@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.3
X-Originating-IP: 192.75.88.232
X-Poly-FromMTA: (imp-4-2.polymtl.ca [132.207.4.77]) at Fri, 15 Jun 2007 15:54:10 +0000
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
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, Thank you for the answer. But I still think any optimization application draft should refer to the others, even if it is only one sentence to say that there are no dependencies. Also, since each optimization application draft will probably propose similar extensions to PCEP, it would be better, at least from an implementation point of view, to generalize these extensions instead of making them application specific. Cordially, Meral Selon JP Vasseur <jvasseur@cisco.com>: > 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
- [Pce] Adopting draft-lee-pce-global-concurrent-op… JP Vasseur
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Dan Li
- RE: [Pce] Adopting draft-lee-pce-global-concurren… Lucy Yong
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Kohei Shiomoto
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Tomonori TAKEDA
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Mach Chen
- Re: [Pce] Adopting draft-lee-pce-global-concurren… inoue.ichiro@lab.ntt.co.jp
- RE: [Pce] Adopting draft-lee-pce-global-concurren… Dean Cheng (dcheng)
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Greg Bernstein
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Meral Shirazipour
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Thomas Morin
- Re: [Pce] Adopting draft-lee-pce-global-concurren… JP Vasseur
- Re: [Pce] Adopting draft-lee-pce-global-concurren… Meral Shirazipour
- Re: [Pce] Adoptingdraft-lee-pce-global-concurrent… Adrian Farrel
- Re: [Pce] Adopting draft-lee-pce-global-concurren… JP Vasseur