
From wwwrun@core3.amsl.com  Tue Jun  2 14:36:15 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 3E6473A6AAA; Tue,  2 Jun 2009 14:36:14 -0700 (PDT)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20090602213615.3E6473A6AAA@core3.amsl.com>
Date: Tue,  2 Jun 2009 14:36:15 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] Last Call: draft-ietf-pce-inter-layer-frwk (Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering) to Informational RFC
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: ietf@ietf.org
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, 02 Jun 2009 21:36:15 -0000

The IESG has received a request from the Path Computation Element WG 
(pce) to consider the following document:

- 'Framework for PCE-Based Inter-Layer MPLS and GMPLS Traffic Engineering '
   <draft-ietf-pce-inter-layer-frwk-10.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send substantive comments to the
ietf@ietf.org mailing lists by 2009-06-16. Exceptionally, 
comments may be sent to iesg@ietf.org instead. In either case, please 
retain the beginning of the Subject line to allow automated sorting.

The file can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-pce-inter-layer-frwk-10.txt


IESG discussion can be tracked via
https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&dTag=14628&rfc_flag=0


From rfc-editor@rfc-editor.org  Tue Jun  9 17:00:03 2009
Return-Path: <rfc-editor@rfc-editor.org>
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 79AA03A69A4; Tue,  9 Jun 2009 17:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.012
X-Spam-Level: 
X-Spam-Status: No, score=-17.012 tagged_above=-999 required=5 tests=[AWL=-0.013, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 Astz6bXLg9os; Tue,  9 Jun 2009 17:00:02 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 873FD3A6841; Tue,  9 Jun 2009 17:00:02 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 8590F2C791A; Tue,  9 Jun 2009 16:59:21 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20090609235921.8590F2C791A@bosco.isi.edu>
Date: Tue,  9 Jun 2009 16:59:21 -0700 (PDT)
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 5541 on Encoding of Objective Functions in the Path Computation Element Communication Protocol (PCEP)
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, 10 Jun 2009 00:00:03 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5541

        Title:      Encoding of Objective Functions in 
                    the Path Computation Element Communication Protocol 
                    (PCEP) 
        Author:     JL. Le Roux, JP. Vasseur,
                    Y. Lee
        Status:     Standards Track
        Date:       June 2009
        Mailbox:    jeanlouis.leroux@orange-ftgroup.com, 
                    jpv@cisco.com, 
                    ylee@huawei.com
        Pages:      23
        Characters: 45589
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-of-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5541.txt

The computation of one or a set of Traffic Engineering Label Switched
Paths (TE LSPs) in MultiProtocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) networks is subject to a set of one or more
specific optimization criteria, referred to as objective functions
(e.g., minimum cost path, widest path, etc.).

In the Path Computation Element (PCE) architecture, a Path
Computation Client (PCC) may want a path to be computed for one or
more TE LSPs according to a specific objective function.  Thus, the
PCC needs to instruct the PCE to use the correct objective function.
Furthermore, it is possible that not all PCEs support the same set of
objective functions; therefore, it is useful for the PCC to be able to
automatically discover the set of objective functions supported by
each PCE.

This document defines extensions to the PCE communication Protocol
(PCEP) to allow a PCE to indicate the set of objective functions it
supports.  Extensions are also defined so that a PCC can indicate in
a path computation request the required objective function, and
a PCE can report in a path computation reply the objective
function that was used for path computation.

This document defines objective function code types for six
objective functions previously listed in the PCE requirements work,
and provides the definition of four new metric types that apply to a
set of synchronized requests.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute



From jvasseur@cisco.com  Wed Jun 10 23:21:20 2009
Return-Path: <jvasseur@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 652813A6B34 for <pce@core3.amsl.com>; Wed, 10 Jun 2009 23:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 EpSMa88CUUWX for <pce@core3.amsl.com>; Wed, 10 Jun 2009 23:21:19 -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 1E4E93A6A41 for <pce@ietf.org>; Wed, 10 Jun 2009 23:21:18 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.42,200,1243814400"; d="scan'208";a="42538875"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 11 Jun 2009 06:21:25 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id n5B6LPod020324;  Thu, 11 Jun 2009 08:21:25 +0200
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n5B6LOLH024883; Thu, 11 Jun 2009 06:21:24 GMT
Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 11 Jun 2009 08:21:24 +0200
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.1830);  Thu, 11 Jun 2009 08:21:24 +0200
Message-Id: <2C2E0FE5-3F44-499B-923F-730F5375A109@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 11 Jun 2009 08:21:23 +0200
X-Mailer: Apple Mail (2.935.3)
X-OriginalArrivalTime: 11 Jun 2009 06:21:24.0546 (UTC) FILETIME=[D8699A20:01C9EA5C]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=255; t=1244701285; x=1245565285; c=relaxed/simple; s=amsdkim1002; 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:=20Welcome=20to=20Dan=20King=20as=20our=20Secretar y |Sender:=20; bh=T5GAIuLqaNvGhF2nfK+0EfUwYIxQFt4T1dDx1kLlC0s=; b=gCh3KGNChs3vUalSW08f6mw7uLYVUELTXWRIcdxr8RG+1Abi2+hMgK+ylM YGT/cCbaqrpHPKPQlDIDSE5H0MyjST5vCrP1xc5s4B4vFB7ppazGPlp6EYrr MMzixQ1UTe;
Authentication-Results: ams-dkim-1; header.From=jvasseur@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; ); 
Subject: [Pce] Welcome to Dan King as our Secretary
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, 11 Jun 2009 06:21:20 -0000

Dear WG,

I have the extreme pleasure to announce you that Dan King kindly  
accepted to help our WG as PCE WG Secretary. Needless to introduce  
Dan, he has been quite active in the WG for a while and a key  
contributor. Thanks again Dan !

JP.

From ylee@huawei.com  Thu Jun 11 22:33:02 2009
Return-Path: <ylee@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 7CC2F3A6A73 for <pce@core3.amsl.com>; Thu, 11 Jun 2009 22:33:02 -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 gEeiYI3HYcT6 for <pce@core3.amsl.com>; Thu, 11 Jun 2009 22:32:59 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 0372A3A6A6E for <pce@ietf.org>; Thu, 11 Jun 2009 22:32:59 -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 <0KL4001U8236TN@usaga01-in.huawei.com> for pce@ietf.org; Thu, 11 Jun 2009 22:33:06 -0700 (PDT)
Received: from L73682 (p16136-ipbffx02marunouchi.tokyo.ocn.ne.jp [221.189.115.136]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0KL400H0L232WQ@usaga01-in.huawei.com> for pce@ietf.org; Thu, 11 Jun 2009 22:33:04 -0700 (PDT)
Date: Fri, 12 Jun 2009 00:32:59 -0500
From: Young Lee <ylee@huawei.com>
To: pce@ietf.org
Message-id: <000001c9eb1f$40d42bd0$5300a8c0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_2rsAD65RfgdJpx8yC8+27Q)"
Thread-index: AcnrHz9KtHcwV31RTR6OvSyZq0k4ag==
Subject: [Pce] some editorial changes for GCO
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, 12 Jun 2009 05:33:02 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_2rsAD65RfgdJpx8yC8+27Q)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT

Hi PCErs, 

 

During the RFC Editor's review on the GCO draft, the following changes were
proposed by the authors of the draft: 

 

In Section 5.1:

 

>> Section 5.1

>> OLD :

>>    Note: This can be achieved by the following objective function:

>>    minimize max over all links {(C(i)-A(i))/C(i)} where C(i) is the

>>    link capacity for link i and A(i) is the total bandwidth allocated

>>    on link i.

>> NEW :

>>    Note: This can be achieved by the following objective function:

>>    minimize max over all links {A(i))/C(i)} where C(i) is the

>>    link capacity for link i and A(i) is the total bandwidth allocated

>>    on link i.

 

The reason for this change is to make this Objective Function (MLL) defined
in the GCO draft to be consistent with RFC 5541. 

Note that this does not incur any functional change. 

 

If you have any questions on this, please discuss in the mailing list.
Thanks. 

 

Young 


--Boundary_(ID_2rsAD65RfgdJpx8yC8+27Q)
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:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
h1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:16.0pt;
	font-family:Arial;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:Tahoma;}
p.Style1, li.Style1, div.Style1
	{margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:3.0pt;
	margin-left:.3in;
	text-indent:-.3in;
	page-break-after:avoid;
	mso-list:l0 level1 lfo1;
	font-size:12.0pt;
	font-family:"Times New Roman";}
span.EmailStyle19
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1792360828;
	mso-list-template-ids:1288485006;}
@list l0:level1
	{mso-level-style-link:"Heading 1";
	mso-level-text:%1;
	mso-level-tab-stop:.3in;
	mso-level-number-position:left;
	margin-left:.3in;
	text-indent:-.3in;
	font-family:"Times New Roman";}
@list l0:level2
	{mso-level-text:"%1\.%2";
	mso-level-tab-stop:.4in;
	mso-level-number-position:left;
	margin-left:.4in;
	text-indent:-.4in;
	font-family:"Times New Roman";}
@list l0:level3
	{mso-level-text:"%1\.%2\.%3";
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	margin-left:.5in;
	text-indent:-.5in;
	font-family:"Times New Roman";}
@list l0:level4
	{mso-level-text:"%1\.%2\.%3\.%4";
	mso-level-tab-stop:.6in;
	mso-level-number-position:left;
	margin-left:.6in;
	text-indent:-.6in;}
@list l0:level5
	{mso-level-text:"%1\.%2\.%3\.%4\.%5";
	mso-level-tab-stop:.7in;
	mso-level-number-position:left;
	margin-left:.7in;
	text-indent:-.7in;}
@list l0:level6
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6";
	mso-level-tab-stop:.8in;
	mso-level-number-position:left;
	margin-left:.8in;
	text-indent:-.8in;}
@list l0:level7
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7";
	mso-level-tab-stop:.9in;
	mso-level-number-position:left;
	margin-left:.9in;
	text-indent:-.9in;}
@list l0:level8
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8";
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	margin-left:1.0in;
	text-indent:-1.0in;}
@list l0:level9
	{mso-level-text:"%1\.%2\.%3\.%4\.%5\.%6\.%7\.%8\.%9";
	mso-level-tab-stop:1.1in;
	mso-level-number-position:left;
	margin-left:1.1in;
	text-indent:-1.1in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</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=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
11.0pt'>Hi PCErs, <o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
11.0pt'>During the RFC Editor&#8217;s review on the GCO draft, the =
following
changes were proposed by the authors of the draft: =
<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
style=3D'font-size:
11.0pt'>In Section 5.1:<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span style=3D'font-size:11.0pt'>&gt;&gt; =
Section 5.1<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span style=3D'font-size:11.0pt'>&gt;&gt; OLD =
:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
Note: This can be achieved by the following objective =
function:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
minimize max over all links {(C(i)-A(i))/C(i)} where C(i) is =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
link capacity for link i and A(i) is the total bandwidth =
allocated<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
on link i.<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span style=3D'font-size:11.0pt'>&gt;&gt; NEW =
:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
Note: This can be achieved by the following objective =
function:<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
minimize max over all links {A(i))/C(i)} where C(i) is =
the<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
link capacity for link i and A(i) is the total bandwidth =
allocated<o:p></o:p></span></font></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><font size=3D2
face=3D"Times New Roman"><span =
style=3D'font-size:11.0pt'>&gt;&gt;&nbsp;&nbsp;&nbsp;
on link i.<o:p></o:p></span></font></p>

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

<p class=3DMsoNormal><font size=3D2 face=3D"Times New Roman"><span =
lang=3DEN
style=3D'font-size:11.0pt'>The reason for this change is to make this =
Objective
Function (MLL) defined in the GCO draft to be consistent with RFC 5541. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><!--[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"47E529CG097D5920@5BB2C5D2BED5405097@8h87:GHM62793!!!!!!BIHO@]M6279=
3!!!!!!!!!!1110BCGBD3519Onsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!80L8Z80NC=3DM62793!!!!!!BIHO@]m62793!!!!!!!!!!1110BCGBD351=
9110BCGBD3519!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!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></font><span lang=3DEN>Note that this does =
not incur
any functional change. <o:p></o:p></span></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN
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 =
lang=3DEN
style=3D'font-size:12.0pt'>If you have any questions on this, please =
discuss in
the mailing list. Thanks. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN
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 =
lang=3DEN
style=3D'font-size:12.0pt'>Young </span></font><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

</div>

</body>

</html>

--Boundary_(ID_2rsAD65RfgdJpx8yC8+27Q)--

From root@core3.amsl.com  Fri Jun 12 03: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 337563A69DE; Fri, 12 Jun 2009 03:45: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: <20090612104501.337563A69DE@core3.amsl.com>
Date: Fri, 12 Jun 2009 03:45:01 -0700 (PDT)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-monitoring-05.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, 12 Jun 2009 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           : A set of monitoring tools for Path Computation Element based Architecture
	Author(s)       : J. Vasseur, et al.
	Filename        : draft-ietf-pce-monitoring-05.txt
	Pages           : 25
	Date            : 2009-06-12

A Path Computation Element (PCE) based architecture has been
specified for the computation of Traffic Engineering (TE) Label
Switched Paths (LSPs) in Multiprotocol Label Switching (MPLS) and
Generalized MPLS (GMPLS) networks in the context of single or
multiple domains (where a domain refers to a collection of network
elements within a common sphere of address management or path
computational responsibility such as IGP areas and Autonomous
Systems).  Path Computation Clients (PCCs) send computation requests
to PCEs, and these may forward the requests to and cooperate with
other PCEs forming a "path computation chain".

In PCE-based environments, it is thus critical to monitor the state
of the path computation chain for troubleshooting and performance
monitoring purposes: liveness of each element (PCE) involved in the
PCE chain, detection of potential resource contention states and
statistics in term of path computation times are examples of such
metrics of interest.  This document specifies procedures and
extensions to the Path Computation Element Protocol (PCEP) in order
to gather such information.

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

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


--NextPart--

From julien.meuric@orange-ftgroup.com  Mon Jun 29 01:29:12 2009
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 314D428C18E for <pce@core3.amsl.com>; Mon, 29 Jun 2009 01:29:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.947
X-Spam-Level: 
X-Spam-Status: No, score=-0.947 tagged_above=-999 required=5 tests=[AWL=0.432,  BAYES_00=-2.599, HELO_EQ_FR=0.35, SARE_MLH_Stock1=0.87]
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 cxnyuqe5ERSB for <pce@core3.amsl.com>; Mon, 29 Jun 2009 01:29:11 -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 813DF28C1A4 for <pce@ietf.org>; Mon, 29 Jun 2009 01:29:00 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 29 Jun 2009 10:28:44 +0200
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: Mon, 29 Jun 2009 10:28:43 +0200
Message-ID: <D109C8C97C15294495117745780657AE0BC92261@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Internet-Drafts Submission Cutoff Dates for IETF 75 in Stockholm, Sweden 
Thread-Index: Acn2byGVDw+xbh2/Qt2RELpZhWc5gACJAkFw
From: <julien.meuric@orange-ftgroup.com>
To: <pce@ietf.org>
X-OriginalArrivalTime: 29 Jun 2009 08:28:44.0353 (UTC) FILETIME=[9D872310:01C9F893]
Subject: [Pce] FW: Internet-Drafts Submission Cutoff Dates for IETF 75 in Stockholm, Sweden
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, 29 Jun 2009 08:29:12 -0000

Hi all.

Beware of the cut-off dates for IETF 75:
* Monday, July 6 for Initial (i.e., version -00) I-Ds;
* Monday, Jul 13 for Revised (i.e., version -01 and higher) I-Ds.

Julien


-----Original Message-----
From: ietf-announce-bounces@ietf.org
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of IETF Secretariat

There are two (2) Internet-Draft cutoff dates for IETF 75 in Stockholm,
Sweden.

* Monday, July 6, 2009 (17:00 PDT; 24:00 UTC/GMT):=20
Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions.

As always, all initial submissions with a filename beginning with
"draft-ietf" must be approved by the appropriate working group chair
before they can be processed or announced.  The Secretariat would
appreciate receiving working group chair approval by Monday, June 29 at
17:00 PDT (24:00 UTC/GMT).

* Monday, Jul 13, 2009 (17:00 PDT; 24:00 UTC/GMT):=20
Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft
Submissions.

Initial and revised Internet-Drafts received after their respective
cutoff dates will not be made available in the Internet-Drafts directory
or announced until on or after Monday, July 27, when Internet-Draft
posting resumes.  Please do not wait until the last minute to submit.

The Internet-Draft cutoff dates as well as other significant dates
for IETF 75 can be found at:
http://www.ietf.org/meetings/75/cutoff-dates.html

The Internet-Draft submission tool can be found at:
https://datatracker.ietf.org/idst/upload.cgi

Thank you for your understanding and cooperation. If you have any
questions or concerns, then please send a message to
internet-drafts@ietf.org.

The IETF Secretariat
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

From julien.meuric@orange-ftgroup.com  Mon Jun 29 02:13:27 2009
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 555213A6D46 for <pce@core3.amsl.com>; Mon, 29 Jun 2009 02:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.481
X-Spam-Level: 
X-Spam-Status: No, score=-0.481 tagged_above=-999 required=5 tests=[AWL=-0.321, BAYES_05=-1.11, HELO_EQ_FR=0.35, J_CHICKENPOX_13=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 XH2l5resxfNY for <pce@core3.amsl.com>; Mon, 29 Jun 2009 02:13:26 -0700 (PDT)
Received: from R-MAIL2.rd.francetelecom.com (r-mail2.rd.francetelecom.com [217.108.152.42]) by core3.amsl.com (Postfix) with ESMTP id 45FDD3A6D5F for <pce@ietf.org>; Mon, 29 Jun 2009 02:13:26 -0700 (PDT)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 29 Jun 2009 11:13:45 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 29 Jun 2009 11:13:44 +0200
Message-ID: <D109C8C97C15294495117745780657AE0BC922C8@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Slot Requests for PCE Meeting
Thread-Index: Acn4meazehwL1i2qT1i3jgTOxMovtg==
From: <julien.meuric@orange-ftgroup.com>
To: <pce@ietf.org>
X-OriginalArrivalTime: 29 Jun 2009 09:13:45.0264 (UTC) FILETIME=[E7657300:01C9F899]
Subject: [Pce] Slot Requests for PCE Meeting
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, 29 Jun 2009 09:13:27 -0000

Hi all.

If you wish to speak in favour of some drafts during our next meeting, =
please send slot requests to JP and me.

Be aware that, due to L3VPN conflicting with IDR, final schedule is =
likely to change, especially for the Routing area.

Cheers,

JP & Julien
