Re: [Pce] draft-leroux-pce-of-00.txt

JP Vasseur <jvasseur@cisco.com> Wed, 07 March 2007 13:54 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 1HOwap-0008LE-9c; Wed, 07 Mar 2007 08:54:11 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HOwan-0008L2-E1 for pce@ietf.org; Wed, 07 Mar 2007 08:54:09 -0500
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HOwal-0000Hl-PP for pce@ietf.org; Wed, 07 Mar 2007 08:54:09 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by sj-iport-2.cisco.com with ESMTP; 07 Mar 2007 05:54:06 -0800
X-IronPort-AV: i="4.14,258,1170662400"; d="scan'208,217"; a="364441588:sNHT86132696"
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 l27Ds6eW005901; Wed, 7 Mar 2007 08:54:06 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l27Ds0Zv001445; Wed, 7 Mar 2007 13:54:04 GMT
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 08:53:59 -0500
Received: from [161.44.113.141] ([161.44.113.141]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Mar 2007 08:53:59 -0500
In-Reply-To: <45EE12F8.9040902@redback.com>
References: <D109C8C97C15294495117745780657AE071BB0F7@ftrdmel1.rd.francetelecom.fr> <45EE12F8.9040902@redback.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Message-Id: <82DA0B86-6482-430B-959A-8342B5C5E0E4@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Subject: Re: [Pce] draft-leroux-pce-of-00.txt
Date: Wed, 07 Mar 2007 08:53:57 -0500
To: Wenhu Lu <luw@redback.com>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 07 Mar 2007 13:53:59.0220 (UTC) FILETIME=[0E3CC740:01C760C0]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=8783; t=1173275646; x=1174139646; 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]=20draft-leroux-pce-of-00.txt |Sender:=20 |To:=20Wenhu=20Lu=20<luw@redback.com>; bh=aEr55CJ+Ly8t8cCh4yRSEfVjwn6qQUuhj20V9oC0SF8=; b=QGqX/r3pbk6I9NIpkm+g2ptAbtss7SKRswptlt5z6d9akDG+3hcd2eUsGlnnujo8f4b9ZMCe UE3m9W8FFiTtBDEtIGnNFOZXEdXliTpsWnKDMA/1zF+QYiRwVmP1DSLM;
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: e8c5db863102a3ada84e0cd52a81a79e
Cc: 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>
Content-Type: multipart/mixed; boundary="===============1175620338=="
Errors-To: pce-bounces@lists.ietf.org

Hi,

On Mar 6, 2007, at 8:18 PM, Wenhu Lu wrote:

> Hi Jean-Louis,
>
> It came to my attention that the acronym PCEP was used throughout  
> this draft
> whereas the acronym PCECP was used in drafts such as this one -
>
> _PCE Communication Protocol (PCECP) Specific Requirements for Inter- 
> Area Multi Protocol Label Switching (MPLS) and Generalized MPLS  
> (GMPLS) Traffic Engineering <http://www.ietf.org/internet-drafts/ 
> draft-ietf-pce-pcecp-interarea-reqs-05.txt> (26301 bytes)._
>
> Are these two acronyms going to converge at some time?
>

The term PCECP is used in the requirement drafts because they refer  
to requirements for a PCE Communication Protocol: PCEP is the  
protocol that has been defined.

Hope this clarifies.

JP.

> Regards,
> -wenhu
>
>
>
> LE ROUX Jean-Louis RD-CORE-LAN wrote:
>>
>> Hi all,
>>
>> This new draft defines PCED and PCEP extensions for the encoding  
>> of objective functions.
>> We are waiting for WG feedback/comments.
>>
>> _http://www.ietf.org/internet-drafts/draft-leroux-pce-of-00.txt_
>>
>> Regards,
>>
>> JL
>>
>>
>> --------------------------------------------------------------------- 
>> ---
>>
>> _______________________________________________
>> 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 mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce