From daniel@olddog.co.uk  Thu Aug  6 09:45:08 2009
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 7660E3A6E0E for <pce@core3.amsl.com>; Thu,  6 Aug 2009 09:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.089
X-Spam-Level: 
X-Spam-Status: No, score=-0.089 tagged_above=-999 required=5 tests=[AWL=-0.691, BAYES_50=0.001, HTML_MESSAGE=0.001, 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 HUQtEnDmK+lB for <pce@core3.amsl.com>; Thu,  6 Aug 2009 09:45:06 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.193.159]) by core3.amsl.com (Postfix) with ESMTP id 75BA23A6A1F for <pce@ietf.org>; Thu,  6 Aug 2009 09:43:38 -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 n76GhNUB012586;  Thu, 6 Aug 2009 17:43:29 +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 n76GhMKW012576;  Thu, 6 Aug 2009 17:43:23 +0100
From: "Daniel King" <daniel@olddog.co.uk>
To: <pce@ietf.org>
Date: Thu, 6 Aug 2009 17:43:23 +0100
Message-ID: <004201ca16b5$03f85b20$0be91160$@co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01CA16BD.65BCC320"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcoWtQMipJWhJY42QyS9dXlj7ijIOw==
Content-Language: en-gb
Subject: [Pce] IETF-75 Draft PCE Minutes
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, 06 Aug 2009 16:45:08 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0043_01CA16BD.65BCC320
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello PCE'rs,

 

The draft minutes for our IETF-75 meeting have been uploaded to:

 

http://www.ietf.org/proceedings/75/minutes/pce.html

 

Please suggest any corrections by August 21, 2009. 

 

Br, Dan. 

 


------=_NextPart_000_0043_01CA16BD.65BCC320
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: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=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</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=3DEN-GB link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoPlainText>Hello PCE&#8217;rs,<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>The draft minutes for our IETF-75 meeting have =
been
uploaded to:<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><a
href=3D"http://www.ietf.org/proceedings/75/minutes/pce.html">http://www.i=
etf.org/proceedings/75/minutes/pce.html</a><o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Please suggest any corrections by August 21, =
2009. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Br, Dan. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0043_01CA16BD.65BCC320--


From root@core3.amsl.com  Mon Aug 17 07:15:01 2009
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 925093A6A87; Mon, 17 Aug 2009 07: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: <20090817141501.925093A6A87@core3.amsl.com>
Date: Mon, 17 Aug 2009 07:15:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-p2mp-app-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, 17 Aug 2009 14:15: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           : draft-ietf-pce-p2mp-app-02.txt
	Author(s)       : S. Yasukawa, A. Farrel
	Filename        : draft-ietf-pce-p2mp-app-02.txt
	Pages           : 15
	Date            : 2009-08-17

The Path Computation Element (PCE) provides path computation
functions in support of traffic engineering in Multiprotocol Label
Switching (MPLS) and Generalized MPLS (GMPLS) networks.

Extensions to the MPLS and GMPLS signaling and routing protocols have
been made in support of point-to-multipoint (P2MP) Traffic Engineered
(TE) Label Switched Paths (LSPs).

This document examines the applicability of PCE to path computation
for P2MP TE LSPs in MPLS and GMPLS networks. It describes the
motivation for using a PCE to compute these paths, and examines which
of the PCE architectural models are appropriate.



Yasukawa and Farrel














[page 1]

draft-ietf-pce-p2mp-app-02.txt









 August 2009

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-p2mp-app-02.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-p2mp-app-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-08-17070104.I-D@ietf.org>


--NextPart--

From root@core3.amsl.com  Tue Aug 18 06:00:01 2009
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 DB2DC3A6AE9; Tue, 18 Aug 2009 06:00: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: <20090818130001.DB2DC3A6AE9@core3.amsl.com>
Date: Tue, 18 Aug 2009 06:00:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-p2mp-extensions-04.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: Tue, 18 Aug 2009 13:00: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           : Extensions to the Path Computation Element Communication Protocol (PCEP) for Point-to-Multipoint Traffic Engineering Label Switched Paths
	Author(s)       : Q. Zhao, et al.
	Filename        : draft-ietf-pce-pcep-p2mp-extensions-04.txt
	Pages           : 28
	Date            : 2009-08-18

Point-to-point Multiprotocol Label Switching (MPLS) and Generalized
MPLS (GMPLS) Traffic Engineering Label Switched Paths (TE LSPs) may
be established using signaling techniques, but their paths may first
need to be determined.  The Path Computation Element (PCE) has been
identified as an appropriate technology for the determination of the
paths of P2MP TE LSPs.

This document describes extensions to the PCE communication Protocol
(PCEP) to handle requests and responses for the computation of paths
for P2MP TE LSPs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-p2mp-extensions-04.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-pcep-p2mp-extensions-04.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-08-18055021.I-D@ietf.org>


--NextPart--

From qzhao@huawei.com  Tue Aug 18 06:15:58 2009
Return-Path: <qzhao@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 E87E33A6977 for <pce@core3.amsl.com>; Tue, 18 Aug 2009 06:15:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 UPWNuZWGHjKi for <pce@core3.amsl.com>; Tue, 18 Aug 2009 06:15:58 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id 1D51C3A67A3 for <pce@ietf.org>; Tue, 18 Aug 2009 06:15:58 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOK00FJAP7QS9@usaga02-in.huawei.com> for pce@ietf.org; Tue, 18 Aug 2009 05:55:03 -0700 (PDT)
Received: from huawei.com ([172.18.4.104]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOK00GAOP7QQX@usaga02-in.huawei.com> for pce@ietf.org; Tue, 18 Aug 2009 05:55:02 -0700 (PDT)
Received: from [172.18.4.6] (Forwarded-For: [202.106.79.2]) by usams01-in.huawei.com (mshttpd); Tue, 18 Aug 2009 08:55:02 -0400
Date: Tue, 18 Aug 2009 08:55:02 -0400
From: ZhaoQianglin 73671 <qzhao@huawei.com>
To: pce@ietf.org
Message-id: <fd7dfd9c2832e.2832efd7dfd9c@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
Subject: [Pce] draft-ietf-pce-pcep-p2mp-extensions-04 Updates
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, 18 Aug 2009 13:15:59 -0000

Dear WG, 

Please note that the authors of draft-ietf-pce-pcep-p2mp-extensions recently submitted a new version of their document. This version contains the following updates:

- Cleaned up readability of text where relevant

- References updated 

- IANA Requirements checked

Thanks, 

Draft-ietf-pce-pcep-p2mp-extension Authors



******************************************************************************************
 This email and its 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 here 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 email in error, please notify the sender by phone or email immediately and delete it!
 *****************************************************************************************

From root@core3.amsl.com  Thu Aug 20 07:30:01 2009
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 373D13A68B7; Thu, 20 Aug 2009 07:30:00 -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: <20090820143001.373D13A68B7@core3.amsl.com>
Date: Thu, 20 Aug 2009 07:30:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-p2mp-req-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, 20 Aug 2009 14:30: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           : PCC-PCE Communication Requirements for Point to Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
	Author(s)       : S. Yasukawa, A. Farrel
	Filename        : draft-ietf-pce-p2mp-req-02.txt
	Pages           : 10
	Date            : 2009-08-20

The Path Computation Element (PCE) provides path computation
functions in support of traffic engineering in Multi-Protocol Label
Switching (MPLS) and Generalized MPLS (GMPLS) networks.

Extensions to the MPLS and GMPLS signaling and routing protocols have
been made in support of point-to-multipoint (P2MP) Traffic Engineered
(TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is
already established, and since P2MP TE LSP routes are sometimes
complex to compute, it is likely that PCE will be used for P2MP LSPs.

Generic requirements for a communication protocol between Path
Computation Clients (PCCs) and PCEs are presented in "Path
Computation Element (PCE) Communication Protocol Generic
Requirements". This document complements the generic requirements and
presents a detailed set of PCC-PCE communication protocol
requirements for point-to-multipoint MPLS/GMPLS traffic engineering.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-p2mp-req-02.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-p2mp-req-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-08-20071632.I-D@ietf.org>


--NextPart--

From adrian@olddog.co.uk  Thu Aug 20 07:46:17 2009
Return-Path: <adrian@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 5F1C23A6BD1 for <pce@core3.amsl.com>; Thu, 20 Aug 2009 07:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.82
X-Spam-Level: 
X-Spam-Status: No, score=-1.82 tagged_above=-999 required=5 tests=[AWL=0.778,  BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 9hcAFCc71BgG for <pce@core3.amsl.com>; Thu, 20 Aug 2009 07:46:16 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id 4351B3A67F7 for <pce@ietf.org>; Thu, 20 Aug 2009 07:46:16 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id n7KEk3l9002015 for <pce@ietf.org>; Thu, 20 Aug 2009 15:46:10 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id n7KEk2lB001994 for <pce@ietf.org>; Thu, 20 Aug 2009 15:46:03 +0100
Message-ID: <7DF59463AE9B41A3B7F393A610B5E544@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
References: <20090820143001.373D13A68B7@core3.amsl.com>
Date: Thu, 20 Aug 2009 15:46:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [Pce] I-D Action:draft-ietf-pce-p2mp-req-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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, 20 Aug 2009 14:46:17 -0000

Hi,

This revision only updates references and authors' coordinates.

The authors believe that this work is pretty much done, but we are waiting 
for the protocol extensions to stabilise.

We would welcome review input and especially comments from the people 
working on the protocol extensions. Have we explained all of the 
requirements clearly? have you come across anything else that we haven't 
captured?

Thanks,
Adrian
----- Original Message ----- 
From: <Internet-Drafts@ietf.org>
To: <i-d-announce@ietf.org>
Cc: <pce@ietf.org>
Sent: Thursday, August 20, 2009 3:30 PM
Subject: [Pce] I-D Action:draft-ietf-pce-p2mp-req-02.txt


>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           : PCC-PCE Communication Requirements for Point to 
> Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
> Author(s)       : S. Yasukawa, A. Farrel
> Filename        : draft-ietf-pce-p2mp-req-02.txt
> Pages           : 10
> Date            : 2009-08-20
>
> The Path Computation Element (PCE) provides path computation
> functions in support of traffic engineering in Multi-Protocol Label
> Switching (MPLS) and Generalized MPLS (GMPLS) networks.
>
> Extensions to the MPLS and GMPLS signaling and routing protocols have
> been made in support of point-to-multipoint (P2MP) Traffic Engineered
> (TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is
> already established, and since P2MP TE LSP routes are sometimes
> complex to compute, it is likely that PCE will be used for P2MP LSPs.
>
> Generic requirements for a communication protocol between Path
> Computation Clients (PCCs) and PCEs are presented in "Path
> Computation Element (PCE) Communication Protocol Generic
> Requirements". This document complements the generic requirements and
> presents a detailed set of PCC-PCE communication protocol
> requirements for point-to-multipoint MPLS/GMPLS traffic engineering.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pce-p2mp-req-02.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.
>


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


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


From root@core3.amsl.com  Thu Aug 20 18:45:01 2009
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 759803A6BAB; Thu, 20 Aug 2009 18: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: <20090821014501.759803A6BAB@core3.amsl.com>
Date: Thu, 20 Aug 2009 18:45:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-inter-layer-req-10.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: Fri, 21 Aug 2009 01: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           : PCC-PCE Communication and PCE Discovery Requirements for Inter-Layer Traffic Engineering
	Author(s)       : E. Oki, et al.
	Filename        : draft-ietf-pce-inter-layer-req-10.txt
	Pages           : 12
	Date            : 2009-08-20

The Path Computation Element (PCE) provides functions of path
computation in support of traffic engineering in Multi-Protocol Label
Switching (MPLS) and Generalized MPLS (GMPLS) networks.

MPLS and GMPLS networks may be constructed from layered client/server
networks. It is advantageous for overall network efficiency to
provide end-to-end traffic engineering across multiple network
layers. PCE is a candidate solution for such requirements.

Generic requirements for a communication protocol between Path
Computation Clients (PCCs) and PCEs are presented in "PCE
Communication Protocol Generic Requirements". Generic requirements
for PCE discovery protocol are presented in "Requirements for Path
Computation Element (PCE) Discovery".

This document complements the generic requirements and presents
detailed sets of PCC-PCE communication protocol requirements and PCE
discovery protocol requirements for inter-layer traffic engineering.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-req-10.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-layer-req-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-08-20184426.I-D@ietf.org>


--NextPart--

From fabien.verhaeghe@gmail.com  Fri Aug 21 00:46:17 2009
Return-Path: <fabien.verhaeghe@gmail.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 4E34D3A6ABD for <pce@core3.amsl.com>; Fri, 21 Aug 2009 00:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 FhAvzz8a7T1h for <pce@core3.amsl.com>; Fri, 21 Aug 2009 00:46:16 -0700 (PDT)
Received: from mail-ew0-f206.google.com (mail-ew0-f206.google.com [209.85.219.206]) by core3.amsl.com (Postfix) with ESMTP id 8206428C12B for <pce@ietf.org>; Fri, 21 Aug 2009 00:46:15 -0700 (PDT)
Received: by ewy2 with SMTP id 2so489332ewy.43 for <pce@ietf.org>; Fri, 21 Aug 2009 00:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=CPJ4ddCnUX2DgRr7R9pEId06ErIq3hL7IpmLrdI0s9M=; b=lo0zSKb7KG1ZvP0v3XgIKPuPgViIXAZS/jU6mFSvlOZXI7ovfWicMMUHvzXVOtwy9H nfE9a4Hp3lDWyEJKu5JIR1keiehHdCbcSNQvzz1UCyRSk0VWb/AOgMI0Z6cHacYXnt7j jn0cO0y0T77fYDvEqrqVt6TmWb5R3gY6OPZ+E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=t7CCvxBxaAlXWmn/7TPYIkQ161gCm1jHXBLxJWdBlSDujj0TUcdqUd6Otr5nXbZFGz u0gn0VMOBnrpdJ4QrnpSnT3IvLg6UMLyVnqyhoJXPNpDeEzYtYfHHON2GQoGYUG1hwB/ cot99csvrSk/756HsRBfZpzmlepdhjI2dQHUg=
MIME-Version: 1.0
Received: by 10.216.88.195 with SMTP id a45mr150673wef.63.1250840776303; Fri,  21 Aug 2009 00:46:16 -0700 (PDT)
In-Reply-To: <7DF59463AE9B41A3B7F393A610B5E544@your029b8cecfe>
References: <20090820143001.373D13A68B7@core3.amsl.com> <7DF59463AE9B41A3B7F393A610B5E544@your029b8cecfe>
Date: Fri, 21 Aug 2009 09:46:16 +0200
Message-ID: <755b8f290908210046j171a75a6ya15014bf729d8f1e@mail.gmail.com>
From: Fabien Verhaeghe <fabien.verhaeghe@gmail.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=0016e6d99a212466810471a21032
Cc: pce@ietf.org
Subject: Re: [Pce] I-D Action:draft-ietf-pce-p2mp-req-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: Fri, 21 Aug 2009 07:46:17 -0000

--0016e6d99a212466810471a21032
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi Adrian,

2 minor comment/question

2.1.10
"Therefore, a P2MP Path Computation Request SHOULD
   contain a parameter that allows the PCC to express a cost-benefit
   reoptimization threshold for the whole LSP as well as per
   destination"

Just to be sure to capture correctly this new requirement for the future
P2MP protocol extensions.
Basically that means encoding a new opaque to PCEP field (for instance in a
new object or TLV) that would be pass to PCE policy module.
Is that correct?

2.1.11.
"  It MAY also be possible to indicate on a path computation request a
   cost-benefit reoptimization threshold such that the tree and/or a new
   path to any individual destination is not supplied unless a certain
   improvement is made. Compare with Section 2.1.10."

Does it mean that a PCE may deny the addition of a leaf because the tree
does not provide
certain improvement?
Or do you rather mean that the PCE would not change the existing Path unless
it provides certain improvment?

I guess second option makes more sense. If correct I would suggest something
like:
"The addition of new leaves will not cause reoptimization of the existing
P2MP tree unless a certain improvement is made."
BR
Fabien
On Thu, Aug 20, 2009 at 4:46 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
>
> This revision only updates references and authors' coordinates.
>
> The authors believe that this work is pretty much done, but we are waiting
> for the protocol extensions to stabilise.
>
> We would welcome review input and especially comments from the people
> working on the protocol extensions. Have we explained all of the
> requirements clearly? have you come across anything else that we haven't
> captured?
>
> Thanks,
> Adrian
> ----- Original Message ----- From: <Internet-Drafts@ietf.org>
> To: <i-d-announce@ietf.org>
> Cc: <pce@ietf.org>
> Sent: Thursday, August 20, 2009 3:30 PM
> Subject: [Pce] I-D Action:draft-ietf-pce-p2mp-req-02.txt
>
>
> 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           : PCC-PCE Communication Requirements for Point to
>> Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
>> Author(s)       : S. Yasukawa, A. Farrel
>> Filename        : draft-ietf-pce-p2mp-req-02.txt
>> Pages           : 10
>> Date            : 2009-08-20
>>
>> The Path Computation Element (PCE) provides path computation
>> functions in support of traffic engineering in Multi-Protocol Label
>> Switching (MPLS) and Generalized MPLS (GMPLS) networks.
>>
>> Extensions to the MPLS and GMPLS signaling and routing protocols have
>> been made in support of point-to-multipoint (P2MP) Traffic Engineered
>> (TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is
>> already established, and since P2MP TE LSP routes are sometimes
>> complex to compute, it is likely that PCE will be used for P2MP LSPs.
>>
>> Generic requirements for a communication protocol between Path
>> Computation Clients (PCCs) and PCEs are presented in "Path
>> Computation Element (PCE) Communication Protocol Generic
>> Requirements". This document complements the generic requirements and
>> presents a detailed set of PCC-PCE communication protocol
>> requirements for point-to-multipoint MPLS/GMPLS traffic engineering.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-pce-p2mp-req-02.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.
>>
>>
>
>
> --------------------------------------------------------------------------------
>
>
> _______________________________________________
>> 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
>

--0016e6d99a212466810471a21032
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hi Adrian,</div>
<div>=A0</div>
<div>2 minor comment/question</div>
<div>=A0</div>
<div>2.1.10<br>&quot;Therefore, a P2MP Path Computation Request SHOULD<br>=
=A0=A0 contain a parameter that allows the PCC to express a cost-benefit<br=
>=A0=A0 reoptimization threshold for the whole LSP as well as per<br>=A0=A0=
 destination&quot;</div>

<div>=A0</div>
<div>Just to be sure to capture correctly this new requirement for the futu=
re P2MP protocol extensions.<br>Basically that means encoding a new opaque =
to PCEP field (for instance in a new object or TLV) that would be pass to P=
CE policy module.<br>
Is that correct?</div>
<div>=A0</div>
<div>2.1.11.</div>
<div>&quot;=A0 It MAY also be possible to indicate on a path computation re=
quest a<br>=A0=A0 cost-benefit reoptimization threshold such that the tree =
and/or a new<br>=A0=A0 path to any individual destination is not supplied u=
nless a certain<br>
=A0=A0 improvement is made. Compare with Section 2.1.10.&quot;</div>
<div>=A0</div>
<div>Does it mean that a PCE may deny the addition of a leaf because the tr=
ee does not provide<br>certain improvement?<br>Or do you rather mean that t=
he PCE would not change the existing Path unless it provides certain improv=
ment?</div>

<div>=A0</div>
<div>I guess second option makes more sense. If correct I would suggest som=
ething like:</div>
<div>&quot;The addition of new leaves will not cause reoptimization of the =
existing P2MP tree unless a certain improvement is made.&quot;<br></div>
<div>BR</div>
<div>Fabien<br></div>
<div class=3D"gmail_quote">On Thu, Aug 20, 2009 at 4:46 PM, Adrian Farrel <=
span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.c=
o.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi,<br><br>This revision only up=
dates references and authors&#39; coordinates.<br><br>The authors believe t=
hat this work is pretty much done, but we are waiting for the protocol exte=
nsions to stabilise.<br>
<br>We would welcome review input and especially comments from the people w=
orking on the protocol extensions. Have we explained all of the requirement=
s clearly? have you come across anything else that we haven&#39;t captured?=
<br>
<br>Thanks,<br>Adrian<br>----- Original Message ----- From: &lt;<a href=3D"=
mailto:Internet-Drafts@ietf.org" target=3D"_blank">Internet-Drafts@ietf.org=
</a>&gt;<br>To: &lt;<a href=3D"mailto:i-d-announce@ietf.org" target=3D"_bla=
nk">i-d-announce@ietf.org</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:pce@ietf.org" target=3D"_blank">pce@ietf.org</a>&=
gt;<br>Sent: Thursday, August 20, 2009 3:30 PM<br>Subject: [Pce] I-D Action=
:draft-ietf-pce-p2mp-req-02.txt<br><br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">A New Internet-Draft is availabl=
e from the on-line Internet-Drafts directories.<br>This draft is a work ite=
m of the Path Computation Element Working Group of the IETF.<br>
<br><br>Title =A0 =A0 =A0 =A0 =A0 : PCC-PCE Communication Requirements for =
Point to Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS=
-TE)<br>Author(s) =A0 =A0 =A0 : S. Yasukawa, A. Farrel<br>Filename =A0 =A0 =
=A0 =A0: draft-ietf-pce-p2mp-req-02.txt<br>
Pages =A0 =A0 =A0 =A0 =A0 : 10<br>Date =A0 =A0 =A0 =A0 =A0 =A0: 2009-08-20<=
br><br>The Path Computation Element (PCE) provides path computation<br>func=
tions in support of traffic engineering in Multi-Protocol Label<br>Switchin=
g (MPLS) and Generalized MPLS (GMPLS) networks.<br>
<br>Extensions to the MPLS and GMPLS signaling and routing protocols have<b=
r>been made in support of point-to-multipoint (P2MP) Traffic Engineered<br>=
(TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is<br>
already established, and since P2MP TE LSP routes are sometimes<br>complex =
to compute, it is likely that PCE will be used for P2MP LSPs.<br><br>Generi=
c requirements for a communication protocol between Path<br>Computation Cli=
ents (PCCs) and PCEs are presented in &quot;Path<br>
Computation Element (PCE) Communication Protocol Generic<br>Requirements&qu=
ot;. This document complements the generic requirements and<br>presents a d=
etailed set of PCC-PCE communication protocol<br>requirements for point-to-=
multipoint MPLS/GMPLS traffic engineering.<br>
<br>A URL for this Internet-Draft is:<br><a href=3D"http://www.ietf.org/int=
ernet-drafts/draft-ietf-pce-p2mp-req-02.txt" target=3D"_blank">http://www.i=
etf.org/internet-drafts/draft-ietf-pce-p2mp-req-02.txt</a><br><br>Internet-=
Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br><br>Below is the data which will enable a=
 MIME compliant mail reader<br>implementation to automatically retrieve the=
 ASCII version of the<br>
Internet-Draft.<br><br></blockquote><br><br>-------------------------------=
-------------------------------------------------<br><br><br>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">________________________________=
_______________<br>Pce mailing list<br><a href=3D"mailto:Pce@ietf.org" targ=
et=3D"_blank">Pce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/pce</a><br><br></blockquote><br>________=
_______________________________________<br>Pce mailing list<br><a href=3D"m=
ailto:Pce@ietf.org" target=3D"_blank">Pce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pce" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/pce</a><br></blockquote></div><br>

--0016e6d99a212466810471a21032--

From adrian@olddog.co.uk  Fri Aug 21 04:08:09 2009
Return-Path: <adrian@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 B055B3A6A41 for <pce@core3.amsl.com>; Fri, 21 Aug 2009 04:08:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.846
X-Spam-Level: 
X-Spam-Status: No, score=-1.846 tagged_above=-999 required=5 tests=[AWL=0.752,  BAYES_00=-2.599, STOX_REPLY_TYPE=0.001]
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 u45qsCHyxQPO for <pce@core3.amsl.com>; Fri, 21 Aug 2009 04:08:08 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 4F0133A69A4 for <pce@ietf.org>; Fri, 21 Aug 2009 04:08:06 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id n7LB7sIN011507;  Fri, 21 Aug 2009 12:08:00 +0100
Received: from your029b8cecfe (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id n7LB7rOW011497;  Fri, 21 Aug 2009 12:07:53 +0100
Message-ID: <E9205DA2D5A047E39668320A64F4B2C1@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Fabien Verhaeghe" <fabien.verhaeghe@gmail.com>
References: <20090820143001.373D13A68B7@core3.amsl.com> <7DF59463AE9B41A3B7F393A610B5E544@your029b8cecfe> <755b8f290908210046j171a75a6ya15014bf729d8f1e@mail.gmail.com>
Date: Fri, 21 Aug 2009 12:06:45 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Cc: pce@ietf.org
Subject: Re: [Pce] I-D Action:draft-ietf-pce-p2mp-req-02.txt
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
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, 21 Aug 2009 11:08:09 -0000

Hello Fabien,

> 2 minor comment/question
>
> 2.1.10
> "Therefore, a P2MP Path Computation Request SHOULD
>   contain a parameter that allows the PCC to express a cost-benefit
>   reoptimization threshold for the whole LSP as well as per
>   destination"
>
> Just to be sure to capture correctly this new requirement for the future
> P2MP protocol extensions.

For some definition of "new" :-)

This requirement was in the draft (dated May 2008) that the working group 
accepted as a working group document.

> Basically that means encoding a new opaque to PCEP field (for
> instance in a new object or TLV) that would be pass to PCE
> policy module.
> Is that correct?

I don't think it has to be like that.

I think a number of the PCEP data are transparent, but are still passed to 
(optionally) to the PCE policy module. Is this PCC allowed to request this 
type of computation for this type of service? Reoptimization is more subtle 
than initial computation because it can disrupt traffic. So reoptimization 
can also be subject to policy on the PCE relating to by how much a 
computation must be "better" than the in-place path, before the new path is 
returned to the requester.

In RFC 5440, we deal with reoptimization of individual drafts. The METRIC 
object contains the B flag. This allows the PCC to effectively set a 
reoptimization threshold - and the value supplied could be less than the 
value of the actual path.

Reoptimizing a single P2MP LSP is like a cross between RFC 5440 and RFC 
5557. There is only one LSP, but there are multiple destinations. As for the 
first computation, the PCC needs to be able to indicate how the LSP is to be 
optimized (e.g., shortest path to detination, least cost tree, etc.), but 
since the LSP is already in place and reoptimization of one factor may make 
another factor worse, there will be a trade-off. Thus, the reoptimization 
request needs to be able to guide the PCE as to which factors to reoptimize 
for and what are the acceptable variations of the other factors. 
Additionally, as for the p2p case, an optimization of a very small 
percentage may be considered unwise.

All of these P2MP parameters, just like any other PCEP parameter, is subject 
to policy at the PCE. The PCE is likely to be aware of network policies and 
the concept of "fareness". It may protect the other PCCs against a greedy 
PCC, and it may protect the network against instability.

> 2.1.11.
> "  It MAY also be possible to indicate on a path computation request a
>   cost-benefit reoptimization threshold such that the tree and/or a new
>   path to any individual destination is not supplied unless a certain
>   improvement is made. Compare with Section 2.1.10."
>
> Does it mean that a PCE may deny the addition of a leaf because the tree
> does not provide certain improvement?
> Or do you rather mean that the PCE would not change the existing Path 
> unless
> it provides certain improvment?
>
> I guess second option makes more sense. If correct I would suggest 
> something
> like:
> "The addition of new leaves will not cause reoptimization of the existing
> P2MP tree unless a certain improvement is made."

Yes, the original wording is broken.

Your suggestion is good.

This paragraph now reads...

   It MAY also be possible to indicate on a path computation request a
   cost-benefit reoptimization threshold such that the addition of new
   leaves will not cause reoptimization of the existing P2MP tree unless
   a certain improvement is made over simply grafting the new leaves to
   the existing tree. (Compare with Section 2.1.10.)


Cheers,
Adrian






> On Thu, Aug 20, 2009 at 4:46 PM, Adrian Farrel <adrian@olddog.co.uk> 
> wrote:
>
>> Hi,
>>
>> This revision only updates references and authors' coordinates.
>>
>> The authors believe that this work is pretty much done, but we are 
>> waiting
>> for the protocol extensions to stabilise.
>>
>> We would welcome review input and especially comments from the people
>> working on the protocol extensions. Have we explained all of the
>> requirements clearly? have you come across anything else that we haven't
>> captured?
>>
>> Thanks,
>> Adrian
>> ----- Original Message ----- From: <Internet-Drafts@ietf.org>
>> To: <i-d-announce@ietf.org>
>> Cc: <pce@ietf.org>
>> Sent: Thursday, August 20, 2009 3:30 PM
>> Subject: [Pce] I-D Action:draft-ietf-pce-p2mp-req-02.txt
>>
>>
>> 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           : PCC-PCE Communication Requirements for Point to
>>> Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-TE)
>>> Author(s)       : S. Yasukawa, A. Farrel
>>> Filename        : draft-ietf-pce-p2mp-req-02.txt
>>> Pages           : 10
>>> Date            : 2009-08-20
>>>
>>> The Path Computation Element (PCE) provides path computation
>>> functions in support of traffic engineering in Multi-Protocol Label
>>> Switching (MPLS) and Generalized MPLS (GMPLS) networks.
>>>
>>> Extensions to the MPLS and GMPLS signaling and routing protocols have
>>> been made in support of point-to-multipoint (P2MP) Traffic Engineered
>>> (TE) Label Switched Paths (LSPs). The use of PCE in MPLS networks is
>>> already established, and since P2MP TE LSP routes are sometimes
>>> complex to compute, it is likely that PCE will be used for P2MP LSPs.
>>>
>>> Generic requirements for a communication protocol between Path
>>> Computation Clients (PCCs) and PCEs are presented in "Path
>>> Computation Element (PCE) Communication Protocol Generic
>>> Requirements". This document complements the generic requirements and
>>> presents a detailed set of PCC-PCE communication protocol
>>> requirements for point-to-multipoint MPLS/GMPLS traffic engineering.
>>>
>>> A URL for this Internet-Draft is:
>>> http://www.ietf.org/internet-drafts/draft-ietf-pce-p2mp-req-02.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.
>>>
>>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>>> 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 qzhao@huawei.com  Sun Aug 23 23:26:52 2009
Return-Path: <qzhao@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 9096C3A6A63 for <pce@core3.amsl.com>; Sun, 23 Aug 2009 23:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 F26SCB0l4smq for <pce@core3.amsl.com>; Sun, 23 Aug 2009 23:26:51 -0700 (PDT)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id E0DAA3A68AA for <pce@ietf.org>; Sun, 23 Aug 2009 23:26:51 -0700 (PDT)
Received: from huawei.com (localhost [127.0.0.1]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOV009YKB8WTZ@usaga02-in.huawei.com> for pce@ietf.org; Sun, 23 Aug 2009 23:26:57 -0700 (PDT)
Received: from huawei.com ([172.18.4.104]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KOV0031RB8WG1@usaga02-in.huawei.com> for pce@ietf.org; Sun, 23 Aug 2009 23:26:56 -0700 (PDT)
Received: from [172.24.1.33] (Forwarded-For: [10.112.28.128]) by usams01-in.huawei.com (mshttpd); Mon, 24 Aug 2009 14:26:56 +0800
Date: Mon, 24 Aug 2009 14:26:56 +0800
From: ZhaoQianglin 73671 <qzhao@huawei.com>
To: Jp Vasseur <jvasseur@cisco.com>, julien.meuric@orange-ftgroup.com
Message-id: <fd52d3b72dc4e.2dc4efd52d3b7@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug  8 2006)
Content-type: text/plain; charset=us-ascii
Content-language: en
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-Accept-Language: en
Priority: normal
Cc: pce@ietf.org
Subject: [Pce] WG Last Call Request draft-ietf-pce-pcep-p2mp-extensions-04
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, 24 Aug 2009 06:26:52 -0000

Dear WG Co-Chairs,

When convenient, we kindly request working group last call for document draft-ietf-pce-pcep-p2mp-extensions-04. 

Thank you. 

Co-authors of draft-ietf-pce-pcep-p2mp-extensions




From wwwrun@core3.amsl.com  Thu Aug 27 10:45:17 2009
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: pce@ietf.org
Delivered-To: pce@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id 9763728C648; Thu, 27 Aug 2009 10:45:17 -0700 (PDT)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20090827174517.9763728C648@core3.amsl.com>
Date: Thu, 27 Aug 2009 10:45:17 -0700 (PDT)
Cc: Internet Architecture Board <iab@iab.org>, pce mailing list <pce@ietf.org>, pce chair <pce-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Pce] Document Action: 'Applicability of the Path Computation Element (PCE) to Point-to-Multipoint (P2MP) Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) Traffic Engineering (TE)' to Informational RFC
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, 27 Aug 2009 17:45:17 -0000

The IESG has approved the following document:

- 'Applicability of the Path Computation Element (PCE) to 
   Point-to-Multipoint (P2MP) Multiprotocol Label Switching (MPLS) and 
   Generalized MPLS (GMPLS) Traffic Engineering (TE) '
   <draft-ietf-pce-p2mp-app-02.txt> as an Informational RFC


This document is the product of the Path Computation Element Working Group. 

The IESG contact persons are Ross Callon and Adrian Farrel.

A URL of this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-p2mp-app-02.txt

Technical Summary

   The Path Computation Element (PCE) provides path computation
   functions in support of traffic engineering in Multiprotocol Label
   Switching (MPLS) and Generalized MPLS (GMPLS) networks.

   Extensions to the MPLS and GMPLS signaling and routing protocols have
   been made in support of point-to-multipoint (P2MP) Traffic Engineered
   (TE) Label Switched Paths (LSPs).

   This informational document examines the applicability of PCE to path
   computation for P2MP TE LSPs in MPLS and GMPLS networks. It describes
   the motivation for using a PCE to compute these paths, and examines
   which of the PCE architectural models are appropriate.

Working Group Summary

   The I-D has had some level of discussions and review in the PCE
   working group, and has gone through IETF last call. No controversy
   reported (see PROTO writeup by JP Vasseur). 

Document Quality

   This informational document does not define any protocol that could
   be implemented. Rather, there are other documents currently being 
   progressed in the PCE WG that define the associated requirements and 
   protocol extensions. Multiple service providers have expressed a 
   requirement for these extensions, and reportedly there is at least
   one implementation in testing. 

Personnel

   JP Vasseur is the Document Shepherd for this document. Ross Callon
   is the Responsible Area Director. The document has no IANA
   implications.


From root@core3.amsl.com  Fri Aug 28 04:45:01 2009
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 CE58E3A6C0C; Fri, 28 Aug 2009 04: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: <20090828114501.CE58E3A6C0C@core3.amsl.com>
Date: Fri, 28 Aug 2009 04:45:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-svec-list-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: Fri, 28 Aug 2009 11: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           : The use of SVEC (Synchronization VECtor) list for Synchronized dependent path computations
	Author(s)       : I. Nishioka, D. King
	Filename        : draft-ietf-pce-pcep-svec-list-02.txt
	Pages           : 15
	Date            : 2009-08-28

A Path Computation Element (PCE) performing dependent path
computations, for instance calculating a diverse working and
protected path do not share common network points, would need to
synchronize the computations in order to increase the probability of
meeting the working and protected path disjoint objective and
network resource optimization objective. When a PCE computes
multiple sets of dependent path computation requests concurrently,
it is required to use Synchronization VECtor (SVEC) list for
association among the sets of dependent path computation requests.
SVEC is also applicable to end-to-end diverse path computation
across multiple domains. This document describes the usage of SVECs
in the SVEC list and diverse path computation guideline, for the
synchronized computation of dependent paths.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-svec-list-02.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-pcep-svec-list-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2009-08-28043456.I-D@ietf.org>


--NextPart--

From vishwas.ietf@gmail.com  Fri Aug 28 18:14:32 2009
Return-Path: <vishwas.ietf@gmail.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 784FF3A6B61 for <pce@core3.amsl.com>; Fri, 28 Aug 2009 18:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[AWL=0.156,  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 ICNJ93ldfPlG for <pce@core3.amsl.com>; Fri, 28 Aug 2009 18:14:31 -0700 (PDT)
Received: from mail-gx0-f226.google.com (mail-gx0-f226.google.com [209.85.217.226]) by core3.amsl.com (Postfix) with ESMTP id 9C5303A6877 for <pce@ietf.org>; Fri, 28 Aug 2009 18:14:31 -0700 (PDT)
Received: by gxk26 with SMTP id 26so176351gxk.18 for <pce@ietf.org>; Fri, 28 Aug 2009 18:14:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=GxfQ3e/mDqeVXKMNkhwZu65a82TiMQV2VUxQbefgi00=; b=NwKt45pQdYf6JospYkiS5d1ASDyj2hNGPTzctfyjgyFTJAC/z4otdZzldEwUIARkgX 47Qx/CdTt0a8+mq8P/IziXq2PWDT6AdlQatMqqHuiC7LvTtmF67Iu5fkObnNOjgUIPrd r6Qdtusz9bskWnWmklvDLLhfl2g0V40HtxNDA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=k3JxKTkhKTcGvG17QEWI4DiiMZwBZ6ddCUHgVtrTbU0/9kL1Vf3kNRXC/MA8ZDdBOh i9IHSKkWyatU5Mj2oV1OmRD4yESY4CYV+Aqf61UGLwPdbvyfYfqFVXmsmIJHfdSSegjg 2hA+HC+YxlJC0zgsi9rMTgCIYtXfBGGxNu6Dc=
MIME-Version: 1.0
Received: by 10.150.253.10 with SMTP id a10mr1922737ybi.275.1251508473275;  Fri, 28 Aug 2009 18:14:33 -0700 (PDT)
Date: Fri, 28 Aug 2009 18:14:33 -0700
Message-ID: <77ead0ec0908281814m77b76502xeea41fbd9324ea80@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: pce@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Pce] RFC5440
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, 29 Aug 2009 01:14:32 -0000

Hi,

While readint the RFC5440 and the
http://www.iana.org/assignments/pcep/pcep.xml IANA assignments I
noticed a discripancy.

RRO in the RFC refers to a Reported Route Object but in the IANA it is
refered to a Recorded Route Object.

Thanks,
Vishwas