
From root@core3.amsl.com  Tue Feb  2 10:00:01 2010
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 8A1373A6856; Tue,  2 Feb 2010 10:00:01 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100202180001.8A1373A6856@core3.amsl.com>
Date: Tue,  2 Feb 2010 10:00:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-p2mp-extensions-07.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, 02 Feb 2010 18:00: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           : 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-07.txt
	Pages           : 31
	Date            : 2010-02-02

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-07.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-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2010-02-02094850.I-D@ietf.org>


--NextPart--

From daniel@olddog.co.uk  Tue Feb  2 10:14:51 2010
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 D0D6A3A6B31 for <pce@core3.amsl.com>; Tue,  2 Feb 2010 10:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 DC8Qb2CIeZOo for <pce@core3.amsl.com>; Tue,  2 Feb 2010 10:14:50 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by core3.amsl.com (Postfix) with ESMTP id 9777C28C10F for <pce@ietf.org>; Tue,  2 Feb 2010 10:14:49 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id o12IF8oE019613 for <pce@ietf.org>; Tue, 2 Feb 2010 18:15:13 GMT
Received: from Serenity (88-97-23-122.dsl.zen.co.uk [88.97.23.122]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id o12IF72k019604 for <pce@ietf.org>; Tue, 2 Feb 2010 18:15:08 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <pce@ietf.org>
References: <20100202174850.D39F13A6975@core3.amsl.com>
In-Reply-To: <20100202174850.D39F13A6975@core3.amsl.com>
Date: Tue, 2 Feb 2010 18:15:10 -0000
Message-ID: <000701caa433$a8ce7330$fa6b5990$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqkMBkZCHi92vvWT1WeMM42qOZiwQAACgrw
Content-Language: en-gb
Subject: [Pce] New Version Notification for draft-ietf-pce-pcep-p2mp-extensions-07
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, 02 Feb 2010 18:14:51 -0000

Hi All,=20

This new version of our draft incorporates a number of minor updates, =
specifically:

- Updated Trust Legal Provisions as per Dec 28 (2009) bulletin.=20
- Clearer introductory text
- Slightly expanded Section 3.1.1 (P2MP Computation TLV in the Existing =
PCE Discovery Protocol)=09
- Clearer text for the Efficient Presentation of P2MP LSPs
- Plus a few minor nits and comments

Special thanks to Adrian for his review!

Br, pcep-p2mp-extensions authors

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of =
Internet-Drafts@ietf.org
Sent: 02 February 2010 18:00
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-p2mp-extensions-07.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           : 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-07.txt
	Pages           : 31
	Date            : 2010-02-02

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-0=
7.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.


From jvasseur@cisco.com  Wed Feb  3 09:48:36 2010
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 699EF28C110 for <pce@core3.amsl.com>; Wed,  3 Feb 2010 09:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.439
X-Spam-Level: 
X-Spam-Status: No, score=-10.439 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 USlXcGTYlJ+A for <pce@core3.amsl.com>; Wed,  3 Feb 2010 09:48:35 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id A5FC328C186 for <pce@ietf.org>; Wed,  3 Feb 2010 09:48:28 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApgFAGJFaUurR7Ht/2dsb2JhbACBbL5OmBaERQQ
X-IronPort-AV: E=Sophos;i="4.49,399,1262563200";  d="scan'208,217";a="477603245"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 03 Feb 2010 17:49:11 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o13HnBJH027247 for <pce@ietf.org>; Wed, 3 Feb 2010 17:49:11 GMT
Received: from xfe-rcd-102.cisco.com ([72.163.62.137]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Feb 2010 11:49:11 -0600
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 3 Feb 2010 11:49:10 -0600
Message-Id: <40A1847B-945E-4DED-B181-8E1A17798513@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-420--850658730
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 3 Feb 2010 18:49:09 +0100
References: <20100203173153.864F928C0F7@core3.amsl.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 03 Feb 2010 17:49:10.0657 (UTC) FILETIME=[30D52F10:01CAA4F9]
Subject: [Pce] Fwd: Revised Guidelines to Authors of Internet-Drafts
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, 03 Feb 2010 17:48:36 -0000

--Apple-Mail-420--850658730
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: IESG Secretary <iesg-secretary@ietf.org>
> Date: February 3, 2010 6:31:53 PM CEST
> To: IETF Announcement list <ietf-announce@ietf.org>
> Subject: Revised Guidelines to Authors of Internet-Drafts
>
> An updated version of the Guidelines to Authors of Internet-Drafts  
> is now
> available and has been posted on the IETF website:
>
>  http://www.ietf.org/id-info/guidelines.html  OR
>  http://www.ietf.org/id-info/1id-guidelines.txt
>
> Summary of changes in this version:
>
> o Update the references to reflect the current BCPs. Remove the
>  reference to rfc2333bis, which is no longer an active work item.
>  Add a references for the I-D Submission Tool and the Data Tracker.
>
> o Rewrite of Section 3.
>
> o Structure the choices in Section 4 to match the current BCPs.
>
> o Provide two boilerplate options in Section 5, as approved by the
>  IESG on 7 January 2010.
>
> o Remove the discussion of grace period from Section 7. With the
>  I-D Submission Tool, there is no longer a need for one.
>
> o Include URLs that are not redirected.
>
> o Significant editorial changes.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


--Apple-Mail-420--850658730
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px =
Helvetica">IESG Secretary &lt;<a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt;</f=
ont></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"4" color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>Date: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica">February 3, 2010 6:31:53 PM =
CEST</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"4" color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>To: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica">IETF Announcement list &lt;<a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;</fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" =
color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>Subject: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica"><b>Revised Guidelines to Authors of =
Internet-Drafts<span =
class=3D"Apple-converted-space">&nbsp;</span></b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </div><div>An updated =
version of the Guidelines to Authors of Internet-Drafts is =
now<br>available and has been posted on the IETF website:<br><br> =
&nbsp;<a =
href=3D"http://www.ietf.org/id-info/guidelines.html">http://www.ietf.org/i=
d-info/guidelines.html</a> &nbsp;OR<br> &nbsp;<a =
href=3D"http://www.ietf.org/id-info/1id-guidelines.txt">http://www.ietf.or=
g/id-info/1id-guidelines.txt</a><br><br>Summary of changes in this =
version:<br><br>o Update the references to reflect the current BCPs. =
Remove the<br> &nbsp;reference to rfc2333bis, which is no longer an =
active work item.<br> &nbsp;Add a references for the I-D Submission Tool =
and the Data Tracker.<br><br>o Rewrite of Section 3.<br><br>o Structure =
the choices in Section 4 to match the current BCPs.<br><br>o Provide two =
boilerplate options in Section 5, as approved by the<br> &nbsp;IESG on 7 =
January 2010.<br><br>o Remove the discussion of grace period from =
Section 7. With the<br> &nbsp;I-D Submission Tool, there is no longer a =
need for one.<br><br>o Include URLs that are not redirected.<br><br>o =
Significant editorial =
changes.<br>_______________________________________________<br>IETF-Announ=
ce mailing list<br><a =
href=3D"mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a><br>https=
://www.ietf.org/mailman/listinfo/ietf-announce<br></div></blockquote></div=
><br></body></html>=

--Apple-Mail-420--850658730--

From jvasseur@cisco.com  Thu Feb  4 08:40:51 2010
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 D257F3A6A1F for <pce@core3.amsl.com>; Thu,  4 Feb 2010 08:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level: 
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[AWL=0.998, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 GhZN9ybcypl9 for <pce@core3.amsl.com>; Thu,  4 Feb 2010 08:40:50 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 1A29A3A69ED for <pce@ietf.org>; Thu,  4 Feb 2010 08:40:49 -0800 (PST)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsMAAKeHakuQ/uCWe2dsb2JhbACBbJlkAQEWJAakApgDhEwE
X-IronPort-AV: E=Sophos;i="4.49,405,1262563200"; d="scan'208,217";a="56788968"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 04 Feb 2010 16:41:35 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o14GfZJk028364 for <pce@ietf.org>; Thu, 4 Feb 2010 16:41:35 GMT
Received: from xfe-ams-101.cisco.com ([144.254.231.93]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Feb 2010 17:41:35 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 4 Feb 2010 17:41:34 +0100
Message-Id: <0726760D-7B12-432E-9F6F-28B43749BD1C@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-499--768314353
Mime-Version: 1.0 (Apple Message framework v936)
Date: Thu, 4 Feb 2010 17:41:34 +0100
References: <000701caa433$a8ce7330$fa6b5990$@co.uk>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 04 Feb 2010 16:41:34.0651 (UTC) FILETIME=[E9AD88B0:01CAA5B8]
Subject: [Pce] Working Group Last Call: draft-ietf-pce-pcep-p2mp-extensions-07
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, 04 Feb 2010 16:40:52 -0000

--Apple-Mail-499--768314353
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Dear all,

Thanks to the authors for the work.

This starts a WG Last call on "draft-ietf-pce-pcep-p2mp-extensions-07"  
that will end on Feb 19, noon ET. Please send your comments to the  
authors and copy the mailing list.

Thanks.

JP.

Begin forwarded message:

> From: "Daniel King" <daniel@olddog.co.uk>
> Date: February 2, 2010 7:15:10 PM CEST
> To: <pce@ietf.org>
> Subject: [Pce] New Version Notification for draft-ietf-pce-pcep-p2mp- 
> extensions-07
>
> Hi All,
>
> This new version of our draft incorporates a number of minor  
> updates, specifically:
>
> - Updated Trust Legal Provisions as per Dec 28 (2009) bulletin.
> - Clearer introductory text
> - Slightly expanded Section 3.1.1 (P2MP Computation TLV in the  
> Existing PCE Discovery Protocol)	
> - Clearer text for the Efficient Presentation of P2MP LSPs
> - Plus a few minor nits and comments
>
> Special thanks to Adrian for his review!
>
> Br, pcep-p2mp-extensions authors
>
> -----Original Message-----
> From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf  
> Of Internet-Drafts@ietf.org
> Sent: 02 February 2010 18:00
> To: i-d-announce@ietf.org
> Cc: pce@ietf.org
> Subject: [Pce] I-D Action:draft-ietf-pce-pcep-p2mp-extensions-07.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           : 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-07.txt
> 	Pages           : 31
> 	Date            : 2010-02-02
>
> 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-07.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


--Apple-Mail-499--768314353
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Dear =
all,<div><br></div><div>Thanks to the authors for the =
work.</div><div><br></div><div>This starts a WG Last call on =
"draft-ietf-pce-pcep-p2mp-extensions-07" that will end on Feb 19, noon =
ET. Please send your comments to the authors and copy the mailing =
list.</div><div><br></div><div>Thanks.</div><div><br></div><div>JP.<br><di=
v><br><div>Begin forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px =
Helvetica">"Daniel King" &lt;<a =
href=3D"mailto:daniel@olddog.co.uk">daniel@olddog.co.uk</a>&gt;</font></di=
v><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>Date: =
</b></font><font face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px =
Helvetica">February 2, 2010 7:15:10 PM CEST</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>To: </b></font><font =
face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px Helvetica">&lt;<a =
href=3D"mailto:pce@ietf.org">pce@ietf.org</a>&gt;</font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>Subject: =
</b></font><font face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px =
Helvetica"><b>[Pce] New Version Notification for =
draft-ietf-pce-pcep-p2mp-extensions-07</b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </div><div>Hi All, =
<br><br>This new version of our draft incorporates a number of minor =
updates, specifically:<br><br>- Updated Trust Legal Provisions as per =
Dec 28 (2009) bulletin. <br>- Clearer introductory text<br>- Slightly =
expanded Section 3.1.1 (P2MP Computation TLV in the Existing PCE =
Discovery Protocol)<span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span><br>- Clearer text for the =
Efficient Presentation of P2MP LSPs<br>- Plus a few minor nits and =
comments<br><br>Special thanks to Adrian for his review!<br><br>Br, =
pcep-p2mp-extensions authors<br><br>-----Original Message-----<br>From: =
<a href=3D"mailto:pce-bounces@ietf.org">pce-bounces@ietf.org</a> [<a =
href=3D"mailto:pce-bounces@ietf.org">mailto:pce-bounces@ietf.org</a>] On =
Behalf Of <a =
href=3D"mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a><br>S=
ent: 02 February 2010 18:00<br>To: <a =
href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>Cc: =
<a href=3D"mailto:pce@ietf.org">pce@ietf.org</a><br>Subject: [Pce] I-D =
Action:draft-ietf-pce-pcep-p2mp-extensions-07.txt<br><br>A New =
Internet-Draft is available from the on-line Internet-Drafts =
directories.<br>This draft is a work item of the Path Computation =
Element Working Group of the IETF.<br><br><br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Extensions =
to the Path Computation Element Communication Protocol (PCEP) for =
Point-to-Multipoint Traffic Engineering Label Switched Paths<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: Q. Zhao, et al.<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Filename =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
draft-ietf-pce-pcep-p2mp-extensions-07.txt<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Pages =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
31<br><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>Date =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
2010-02-02<br><br>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. &nbsp;The Path Computation Element =
(PCE) has been identified as an appropriate technology for the =
determination of the paths of P2MP TE LSPs.<br><br>This document =
describes extensions to the PCE communication Protocol<br>(PCEP) to =
handle requests and responses for the computation of paths for P2MP TE =
LSPs.<br><br>A URL for this Internet-Draft is:<br><a =
href=3D"http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-p2mp-exten=
sions-07.txt">http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-p2mp=
-extensions-07.txt</a><br><br>Internet-Drafts are also available by =
anonymous FTP at:<br><a =
href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-d=
rafts/</a><br><br>Below is the data which will enable a MIME compliant =
mail reader implementation to automatically retrieve the ASCII version =
of the =
Internet-Draft.<br><br>_______________________________________________<br>=
Pce mailing =
list<br>Pce@ietf.org<br>https://www.ietf.org/mailman/listinfo/pce<br></div=
></blockquote></div><br></div></body></html>=

--Apple-Mail-499--768314353--

From qzhao@huawei.com  Thu Feb  4 16:38:48 2010
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 8B6253A689F for <pce@core3.amsl.com>; Thu,  4 Feb 2010 16:38:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_96_XX=1.69, J_CHICKENPOX_52=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 DMXdhiXvH+mt for <pce@core3.amsl.com>; Thu,  4 Feb 2010 16:38:47 -0800 (PST)
Received: from usaga02-in.huawei.com (usaga02-in.huawei.com [206.16.17.70]) by core3.amsl.com (Postfix) with ESMTP id CA43A3A67A4 for <pce@ietf.org>; Thu,  4 Feb 2010 16:38:47 -0800 (PST)
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 <0KXC00GWYF5WW6@usaga02-in.huawei.com> for pce@ietf.org; Thu, 04 Feb 2010 16:39:33 -0800 (PST)
Received: from Z73671a ([10.192.21.54]) by usaga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KXC0037FF5VTD@usaga02-in.huawei.com> for pce@ietf.org; Thu, 04 Feb 2010 16:39:32 -0800 (PST)
From: Quintin Zhao <qzhao@huawei.com>
To: pce@ietf.org
Message-id: <000d01ca8d9f$8ce8e470$3615c00a@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: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acql+20lXLGkLg6uRRGGbaRpjzVjhgYXBPQQ
Subject: [Pce] New Version Notification for draft-zhao-pce-pcep-inter-domain-p2mp-procedures-03
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>
Date: Fri, 05 Feb 2010 00:38:48 -0000
X-Original-Date: Mon, 04 Jan 2010 19:39:27 -0500
X-List-Received-Date: Fri, 05 Feb 2010 00:38:48 -0000

PCE'rs, 

The authors of draft-zhao-pce-pcep-inter-domain-p2mp-procedures have posted
a new version. This version includes the following updates:

- Clarification of work and update of Abstract;
- Reordered and cleaned up Introduction text;
- Cleaned up Terminology;
- Expanded Problem Statement and added some requirements;
- Cleaned up Definition of X-VSPT.

We have made more corrections throughout the document and updated the
references.

Thank you!	
Quintin

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: Thursday, February 04, 2010 7:37 PM
To: qzhao@huawei.com
Cc: zali@cisco.com; tsaad@cisco.com; daniel@olddog.co.uk;
david.Amzallag@bt.com; fabien.verhaeghe@gmail.com; ke-kumaki@kddi.com
Subject: New Version Notification for
draft-zhao-pce-pcep-inter-domain-p2mp-procedures-03


A new version of I-D,
draft-zhao-pce-pcep-inter-domain-p2mp-procedures-03.txt has been successfuly
submitted by Quintin Zhao and posted to the IETF repository.

Filename:	 draft-zhao-pce-pcep-inter-domain-p2mp-procedures
Revision:	 03
Title:		 PCE-based Computation Procedure To Compute Shortest
Constrained P2MP Inter-domain Traffic Engineering Label Switched Paths
Creation_date:	 2010-02-04
WG ID:		 Independent Submission
Number_of_pages: 20

Abstract:
The ability to compute paths for constrained point-to-multipoint 
(P2MP) Traffic Engineering Label Switched Paths(TE LSPs) across 
multiple domains has been identified as a key requirement for the
deployment of P2MP services in MPLS and GMPLS networks. The Path
Computation Element (PCE) has been recognized as an appropriate
technology for the determination of inter-domain paths of P2MP TE
LSPs. 

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



The IETF Secretariat.



From dhruvd@huawei.com  Sun Feb  7 21:25:18 2010
Return-Path: <dhruvd@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 0DA853A6B45 for <pce@core3.amsl.com>; Sun,  7 Feb 2010 21:25:18 -0800 (PST)
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 H6xJW1qa9jxw for <pce@core3.amsl.com>; Sun,  7 Feb 2010 21:25:13 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 355B03A682E for <pce@ietf.org>; Sun,  7 Feb 2010 21:25:13 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KXI00874CFMXQ@szxga04-in.huawei.com> for pce@ietf.org; Mon, 08 Feb 2010 13:26:10 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KXI00IIMCFM94@szxga04-in.huawei.com> for pce@ietf.org; Mon, 08 Feb 2010 13:26:10 +0800 (CST)
Received: from BLRNSHTIPL1NC ([10.18.1.31]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KXI00943CFKPW@szxml04-in.huawei.com> for pce@ietf.org; Mon, 08 Feb 2010 13:26:10 +0800 (CST)
Date: Mon, 08 Feb 2010 10:56:08 +0530
From: Dhruv Dhody <dhruvd@huawei.com>
To: rbradfor@cisco.com, jpv@cisco.com, adrian@olddog.co.uk
Message-id: <000001caa87f$38c359c0$1f01120a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.3168
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_L0HBaj6y0AxOeuIoYbJAdA)"
Thread-index: AcqofzfJPNrF/+YlSWiaO2LhHvbUbA==
Cc: govindappasy@huawei.com, pce@ietf.org, qiss@huawei.com
Subject: [Pce] Comments on draft-ietf-pce-path-key
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, 08 Feb 2010 05:25:18 -0000

This is a multi-part message in MIME format.

--Boundary_(ID_L0HBaj6y0AxOeuIoYbJAdA)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Dear Authors, 

 

Kindly find following comments with respect to Path-Key draft. 

 

PathKey and Hop-Count 

Hop count is needed during the inter-domain best path computation when HOP
LIMIT constraint is given. 

Using the ERO Object length one can easily find the hop-count. 

But if PCRep message has the 'Path Key Subobject' present in the PCEP ERO
then there is no way to find the actual hop-count at PCE (1) because the
actual hops are replaced with a path key. 

Suggestion: If path key exists in the ERO Object, it should be followed by
TWO metric objects.

The first metric object carries the metric value of the CPS .Metric type of
this object is TE/IGP which was received in the path request. So in case of
path key exists the second metric object carries Hopcount of the CPS. Metric
type of this object is Type 3 - Hop Counts

 

Error Handling

In RP Object, if the path-key flag is set and there is no Path-key Object
included in PCReq message, then the receiving PCEP Peer MUST trigger the
Error message with Error Type 6 , Error Value 4 to set PATH-KEY object
missing. 

 

Thanks & Regards,

Dhruv Dhody

Huawei Technologies India Pvt. Ltd,

Bangalore, India

 

 

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

 


--Boundary_(ID_L0HBaj6y0AxOeuIoYbJAdA)
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:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
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]--><o:SmartTagType
 namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" =
name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Lucida Handwriting";
	panose-1:3 1 1 1 1 1 1 1 1 1;}
@font-face
	{font-family:"\@SimSun";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{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;}
-->
</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=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Dear Authors, <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Kindly find following comments with respect to =
Path-Key
draft. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><u><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana;font-weight:bold'>PathKey and Hop-Count =
<o:p></o:p></span></font></u></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Hop count is needed during the inter-domain best =
path computation
when HOP LIMIT constraint is given. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Using the ERO Object length one can easily find the
hop-count. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>But if PCRep message has the &#8216;Path Key =
Subobject&#8217;
present in the PCEP ERO then there is no way to find the actual =
hop-count at
PCE (1) because the actual hops are replaced with a path key. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><u><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Suggestion:</span></font></u><font size=3D2 =
face=3DVerdana><span
style=3D'font-size:10.0pt;font-family:Verdana'> If path key exists in =
the ERO
Object, it should be followed by TWO metric =
objects.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>The first metric object carries the metric value of =
the
CPS .Metric type of this object is TE/IGP which was received in the path
request. So in case of path key exists the second metric object carries
Hopcount of the CPS. Metric type of this object is Type 3 - Hop =
Counts<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><b><u><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana;font-weight:bold'>Error =
Handling<o:p></o:p></span></font></u></b></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>In RP Object, if the path-key flag is set and there =
is no
Path-key Object included in PCReq message, then the receiving PCEP Peer =
MUST
trigger the Error message with Error Type 6 , Error Value 4 to set =
PATH-KEY
object missing. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Thanks &amp; Regards,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Dhruv Dhody<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;
font-family:Verdana'>Huawei Technologies India Pvt. =
Ltd,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><st1:place w:st=3D"on"><st1:City w:st=3D"on"><font =
size=3D2
  face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana'>Bangalore</span></font></s=
t1:City><font
 size=3D2 face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana'>, <st1:country-region
 w:st=3D"on">India</st1:country-region></span></font></st1:place><font =
size=3D2
face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:Verdana'><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'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><em><i><font=

size=3D2 color=3D"#484848" face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:
Verdana;color:#484848'>**************************************************=
*************************************</span></font></i></em><i><font
size=3D2 color=3D"#484848" face=3DVerdana><span =
style=3D'font-size:10.0pt;font-family:
Verdana;color:#484848;font-style:italic'><br>
</span></font></i><em><i><font size=3D2 color=3D"#484848" face=3D"Lucida =
Handwriting"><span
style=3D'font-size:10.0pt;font-family:"Lucida =
Handwriting";color:#484848'>This
e-mail and 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 herein 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 e-mail =
in
error, please notify the sender by phone or email immediately and delete =
it!</span></font></i></em><!--[if gte vml 1]><v:shapetype=20
 id=3D"_x0000_t74" coordsize=3D"21600,21600" 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"355B170GGB445B81C1B8C1@@GGE4@84D089:E[89:E[CMSORIUHQM0,BIHO@]e6149=
5!!!!!!!!!!1113308@D@E@EOnsl`m/enu!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!=
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!1!5"=20
 =
style=3D'position:absolute;margin-left:0;margin-top:0;width:.05pt;height:=
.05pt;
 z-index:1;visibility:hidden;mso-position-horizontal-relative:text;
 mso-position-vertical-relative:text'>
 <w:anchorlock/>
</v:shape><![endif]--><o:p></o:p></p>

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

</div>

</body>

</html>

--Boundary_(ID_L0HBaj6y0AxOeuIoYbJAdA)--

From adrian@olddog.co.uk  Mon Feb  8 02:52:50 2010
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 84A193A7021 for <pce@core3.amsl.com>; Mon,  8 Feb 2010 02:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.319
X-Spam-Level: 
X-Spam-Status: No, score=-2.319 tagged_above=-999 required=5 tests=[AWL=0.279,  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 6F3sSn2vocsx for <pce@core3.amsl.com>; Mon,  8 Feb 2010 02:52:49 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id 7AF4C3A67C1 for <pce@ietf.org>; Mon,  8 Feb 2010 02:52:48 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o18ArIto009027;  Mon, 8 Feb 2010 10:53:18 GMT
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 o18ArBwq009005;  Mon, 8 Feb 2010 10:53:14 GMT
Message-ID: <7A8FFD9AC0524248AB13D3768CE6D3EE@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "Dhruv Dhody" <dhruvd@huawei.com>, <rbradfor@cisco.com>, <jpv@cisco.com>
References: <000001caa87f$38c359c0$1f01120a@china.huawei.com>
Date: Mon, 8 Feb 2010 10:52:45 -0000
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: govindappasy@huawei.com, pce@ietf.org, qiss@huawei.com
Subject: Re: [Pce] Comments on draft-ietf-pce-path-key
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: Mon, 08 Feb 2010 10:52:50 -0000

Hi Dhruv,

> Kindly find following comments with respect to Path-Key draft.

Heads-up that this has been RFC 5520 since April 2009.

> PathKey and Hop-Count
>
> Hop count is needed during the inter-domain best path computation when HOP
> LIMIT constraint is given.
>
> Using the ERO Object length one can easily find the hop-count.
>
> But if PCRep message has the 'Path Key Subobject' present in the PCEP ERO
> then there is no way to find the actual hop-count at PCE (1) because the
> actual hops are replaced with a path key.
>
> Suggestion: If path key exists in the ERO Object, it should be followed by
> TWO metric objects.
>
> The first metric object carries the metric value of the CPS .Metric type 
> of
> this object is TE/IGP which was received in the path request. So in case 
> of
> path key exists the second metric object carries Hopcount of the CPS. 
> Metric
> type of this object is Type 3 - Hop Counts

The example you give of hop-count being deduced from an explicit ERO is an 
example of why hop count is a special metric. But when we do 
constraint-based computations, hop-count is *usually* less important than 
other metrics. And you should notice that even without and PKS, we cannot 
know the per-hop values of the other metrics for a returned ERO.

But that is OK, because we do not need to know this!

We are only interested in the net metrics for the path fragment returned in 
the PCRep. That is, we need to know the cumulative effect of including this 
fragment in the whole path.

PCEP already provides this by allowing the METRIC object on the PCRep 
message with the semntic that it applies to the whole path fragment.

> Error Handling
>
> In RP Object, if the path-key flag is set and there is no Path-key Object
> included in PCReq message, then the receiving PCEP Peer MUST trigger the
> Error message with Error Type 6 , Error Value 4 to set PATH-KEY object
> missing.

Yes, this would be correct behaviour.

Cheers,
Adrian 


From jvasseur@cisco.com  Tue Feb  9 21:37:34 2010
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 22C7928C0EE for <pce@core3.amsl.com>; Tue,  9 Feb 2010 21:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.599
X-Spam-Level: 
X-Spam-Status: No, score=-9.599 tagged_above=-999 required=5 tests=[AWL=0.999,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 0amGkoj5D+sL for <pce@core3.amsl.com>; Tue,  9 Feb 2010 21:37:33 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 483543A7442 for <pce@ietf.org>; Tue,  9 Feb 2010 21:37:33 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArcFABHVcUutJV2c/2dsb2JhbACBRpkfdKRymC6EVQQ
X-IronPort-AV: E=Sophos;i="4.49,441,1262563200";  d="scan'208,217";a="297708025"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by sj-iport-1.cisco.com with ESMTP; 10 Feb 2010 05:38:42 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id o1A5cfGU013235 for <pce@ietf.org>; Wed, 10 Feb 2010 05:38:41 GMT
Received: from xfe-ams-202.cisco.com ([144.254.231.96]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 10 Feb 2010 06:38:41 +0100
Received: from [10.108.68.111] ([10.55.94.216]) by xfe-ams-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 10 Feb 2010 06:38:40 +0100
Message-Id: <180C714D-DE46-464E-9271-1DC2B2E50D16@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-97--289688041
Mime-Version: 1.0 (Apple Message framework v936)
Date: Wed, 10 Feb 2010 06:38:40 +0100
References: <20100210001234.48C7A28C104@core3.amsl.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 10 Feb 2010 05:38:40.0860 (UTC) FILETIME=[4D2129C0:01CAAA13]
Subject: [Pce] Fwd: Revised Guidelines to Authors of Internet-Drafts
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 Feb 2010 05:37:34 -0000

--Apple-Mail-97--289688041
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

FYI

Begin forwarded message:

> From: IESG Secretary <iesg-secretary@ietf.org>
> Date: February 10, 2010 1:12:34 AM CEST
> To: IETF Announcement list <ietf-announce@ietf.org>
> Subject: Revised Guidelines to Authors of Internet-Drafts
>
> An updated version of the Guidelines to Authors of Internet-Drafts  
> is now
> available and has been posted on the IETF website:
>
>  http://www.ietf.org/id-info/guidelines.html  OR
>  http://www.ietf.org/id-info/1id-guidelines.txt
>
> Summary of changes in this version:
>
> o Correct the typographical errors in the excerpts from the Trust
> License Policy (TLP) in Section 4.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


--Apple-Mail-97--289688041
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">FYI<br><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px =
Helvetica">IESG Secretary &lt;<a =
href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt;</f=
ont></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"4" color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>Date: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica">February 10, 2010 1:12:34 AM =
CEST</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"4" color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>To: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica">IETF Announcement list &lt;<a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>&gt;</fon=
t></div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" =
color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>Subject: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica"><b>Revised Guidelines to Authors of =
Internet-Drafts<span =
class=3D"Apple-converted-space">&nbsp;</span></b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </div><div>An updated =
version of the Guidelines to Authors of Internet-Drafts is =
now<br>available and has been posted on the IETF website:<br><br> =
&nbsp;<a =
href=3D"http://www.ietf.org/id-info/guidelines.html">http://www.ietf.org/i=
d-info/guidelines.html</a> &nbsp;OR<br> &nbsp;<a =
href=3D"http://www.ietf.org/id-info/1id-guidelines.txt">http://www.ietf.or=
g/id-info/1id-guidelines.txt</a><br><br>Summary of changes in this =
version:<br><br> o Correct the typographical errors in the excerpts from =
the Trust<br>License Policy (TLP) in Section =
4.<br>_______________________________________________<br>IETF-Announce =
mailing list<br><a =
href=3D"mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a><br>https=
://www.ietf.org/mailman/listinfo/ietf-announce<br></div></blockquote></div=
><br></body></html>=

--Apple-Mail-97--289688041--

From root@core3.amsl.com  Wed Feb 10 13:45:02 2010
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 57A7D3A7603; Wed, 10 Feb 2010 13:45:02 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100210214502.57A7D3A7603@core3.amsl.com>
Date: Wed, 10 Feb 2010 13:45:02 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-svec-list-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: Wed, 10 Feb 2010 21:45: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           : 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-04.txt
	Pages           : 17
	Date            : 2010-02-10

A Path Computation Element (PCE) may be required to perform 
dependent path computations. Dependent path computations are 
requests that need to be synchronized in order to meet specific 
objectives. An example of a dependent request would be a PCE 
computing a set of services which are required to be diverse 
(disjointed) from each other. When a PCE computes sets of dependent 
path computation requests concurrently, it is required to use the 
Synchronization VECtor (SVEC) list for association among the sets of 
dependent path computation requests. The SVEC object is optional and 
carried within the Path Computation Element Protocol (PCEP) 
PCRequest (PCReq) message. 

This document does not specify the PCEP SVEC object or procedure.
 
This informational document clarifies the use of the SVEC list for 
synchronized path computations when computing dependent requests. 
The document also describes a number of usage scenarios for SVEC 
lists within single domain and multi-domain environments.

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

Content-Type: text/plain
Content-ID: <2010-02-10133724.I-D@ietf.org>


--NextPart--

From daniel@olddog.co.uk  Wed Feb 10 13:51:23 2010
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 1FEEE3A77BF for <pce@core3.amsl.com>; Wed, 10 Feb 2010 13:51:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 xrJoGmFZCW34 for <pce@core3.amsl.com>; Wed, 10 Feb 2010 13:51:22 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.193.159]) by core3.amsl.com (Postfix) with ESMTP id 169173A77BD for <pce@ietf.org>; Wed, 10 Feb 2010 13:51:20 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id o1ALqHI7025709 for <pce@ietf.org>; Wed, 10 Feb 2010 21:52:23 GMT
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 o1ALqHT1025702 for <pce@ietf.org>; Wed, 10 Feb 2010 21:52:17 GMT
From: "Daniel King" <daniel@olddog.co.uk>
To: <pce@ietf.org>
References: <20100210214502.57A7D3A7603@core3.amsl.com>
In-Reply-To: <20100210214502.57A7D3A7603@core3.amsl.com>
Date: Wed, 10 Feb 2010 21:52:19 -0000
Message-ID: <009a01caaa9b$51ca5db0$f55f1910$@co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcqqmnzcBqjLgpsHTBKjMd1s3xYXvAAALjTg
Content-Language: en-gb
Subject: Re: [Pce] I-D Action:draft-ietf-pce-pcep-svec-list-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: Wed, 10 Feb 2010 21:51:23 -0000

Howdy all, 

Adrian identified a number of items during his AD review of
draft-ietf-pce-pcep-svec-list-03.txt. Itaru and I have endeavoured to
resolve the issues raised by Adrian. We believe the document is better for
his suggestions and would appreciate any comments regarding this new
version. Updates include:

- Clearer abstract, clarifying the object of the draft
- Reordered the Introduction	
- Provided ASCII art for some examples
- Described Associated SVECs in more detail
- Identified security considerations when using Associated SVECs. We also
provided some suggestions for negating or minimising the effect of Dos using
Associated SVECs.  

Best regards, Itaru and Dan.

-----Original Message-----
From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: 10 February 2010 21:45
To: i-d-announce@ietf.org
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-pcep-svec-list-04.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           : 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-04.txt
	Pages           : 17
	Date            : 2010-02-10

A Path Computation Element (PCE) may be required to perform dependent path
computations. Dependent path computations are requests that need to be
synchronized in order to meet specific objectives. An example of a dependent
request would be a PCE computing a set of services which are required to be
diverse
(disjointed) from each other. When a PCE computes sets of dependent path
computation requests concurrently, it is required to use the Synchronization
VECtor (SVEC) list for association among the sets of dependent path
computation requests. The SVEC object is optional and carried within the
Path Computation Element Protocol (PCEP) PCRequest (PCReq) message. 

This document does not specify the PCEP SVEC object or procedure.
 
This informational document clarifies the use of the SVEC list for
synchronized path computations when computing dependent requests. 
The document also describes a number of usage scenarios for SVEC lists
within single domain and multi-domain environments.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-svec-list-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.


From julien.meuric@orange-ftgroup.com  Mon Feb 15 08:23:40 2010
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 E790A28C0F3 for <pce@core3.amsl.com>; Mon, 15 Feb 2010 08:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.248
X-Spam-Level: 
X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=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 FGhDHl23Mtsf for <pce@core3.amsl.com>; Mon, 15 Feb 2010 08:23:40 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by core3.amsl.com (Postfix) with ESMTP id BE97128C0F0 for <pce@ietf.org>; Mon, 15 Feb 2010 08:23:39 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id DF73A104880; Mon, 15 Feb 2010 17:25:08 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id C664727C09A; Mon, 15 Feb 2010 17:25:08 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 15 Feb 2010 17:25:08 +0100
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, 15 Feb 2010 17:25:08 +0100
Message-ID: <11730_1266251108_4B797564_11730_42872_1_D109C8C97C15294495117745780657AE0C5194EC@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nomcom 2009-2010: IESG Appointments 
Thread-Index: AcqsBcTNcS8sQlA4RyKL6JOq5tVebACUHR+Q
From: <julien.meuric@orange-ftgroup.com>
To: <pce@ietf.org>, <rcallon@juniper.net>, <stbryant@cisco.com>
X-OriginalArrivalTime: 15 Feb 2010 16:25:08.0962 (UTC) FILETIME=[70B49420:01CAAE5B]
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.2.15.154228
Subject: [Pce] FW: Nomcom 2009-2010: IESG Appointments
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, 15 Feb 2010 16:23:41 -0000

Hi all.

As you may be aware, Ross has reached the term of his AD mandate.
Stewart Bryant, who you probably already know, has been nominated to
join Adrian as routing AD. We do not know if they will swap some of
their WG advisor hats, but I do not expect any change for the PCE WG.

Thank you Ross, good luck in IAB. Hi Stewart, welcome among us.

Regards

Julien

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

Hi all,

The 2009-2010 IETF Nominating committee is pleased to announce the
selection of the IESG members whose two year terms start in March 2010.=20

The following have been selected to serve as ADs by the nominating
committee for the open IESG positions and confirmed by the IAB in their
role as confirming body:

Applications: Peter Saint-Andre
Internet: Jari Arkko
Operations and Management: Dan Romascanu
Real-time Applications and Infrastructure: Gonzalo Camarillo
Routing: Stewart Bryant
Security: Sean Turner
Transport: David Harrington

Our thanks to the incumbents who are not returning for their outstanding
service, to the many qualified members of the community who offered to
serve, to the community for their assistance in this process, and to the
named individuals above for agreeing to serve the community on the IESG.


Best Regards,
Mary Barnes
nomcom-chair@ietf.org
mary.ietf.barnes@gmail.com
mary.barnes@nortel.com

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

*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From julien.meuric@orange-ftgroup.com  Wed Feb 17 08:19:45 2010
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 04FF028C102 for <pce@core3.amsl.com>; Wed, 17 Feb 2010 08:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, UNPARSEABLE_RELAY=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 idZNeHl6PrJg for <pce@core3.amsl.com>; Wed, 17 Feb 2010 08:19:43 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by core3.amsl.com (Postfix) with ESMTP id 16E1C28C0EC for <pce@ietf.org>; Wed, 17 Feb 2010 08:19:43 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id B48CD2AC644 for <pce@ietf.org>; Wed, 17 Feb 2010 17:21:20 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id 958D13840E6 for <pce@ietf.org>; Wed, 17 Feb 2010 17:21:20 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 17 Feb 2010 17:21:20 +0100
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: Wed, 17 Feb 2010 17:21:18 +0100
Message-ID: <11523_1266423680_4B7C1780_11523_49_1_D109C8C97C15294495117745780657AE0C519BEF@ftrdmel1>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: RFC 5385 on Version 2.0 Microsoft Word Template for Creating InternetDrafts and RFCs
Thread-Index: AcqsJFn/Hi9owssOTgasdhOnefo/6ADyAXMA
From: <julien.meuric@orange-ftgroup.com>
To: <pce@ietf.org>
X-OriginalArrivalTime: 17 Feb 2010 16:21:20.0064 (UTC) FILETIME=[3D190400:01CAAFED]
X-PMX-Version: 5.5.7.378829, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.2.11.132124
Subject: [Pce] FW: RFC 5385 on Version 2.0 Microsoft Word Template for Creating InternetDrafts and RFCs
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, 17 Feb 2010 16:19:45 -0000

Hi all.

I am sure everyone edits I-Ds with NROFF (or maybe XML-Mind?), but in
case you use MS-Word...

Julien

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

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

=20=20=20=20=20=20=20=20
        RFC 5385

        Title:      Version 2.0 Microsoft Word Template=20
                    for Creating Internet Drafts and RFCs=20
        Author:     J. Touch
        Status:     Informational
        Date:       February 2010
        Mailbox:    touch@isi.edu
        Pages:      20
        Characters: 38421
        Obsoletes:  RFC3285

        I-D Tag:    draft-touch-msword-template-v2.0-07.txt

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

This document describes the properties and use of a revised Microsoft
Word template (.dot) for writing Internet Drafts and RFCs.  It replaces
the initial template described in RFC 3285 to more fully support
Word's outline modes and to be easier to use.  This template can be
direct-printed and direct-viewed, where either is line-for-line
identical with RFC Editor-compliant ASCII output.  This version
obsoletes
RFC 3285.

The most recent version of this template and post-processing scripts
are available at http://www.isi.edu/touch/tools.  This document is not
an=20
Internet Standards Track specification; it is published for
informational=20
purposes.


INFORMATIONAL: This memo provides information for the Internet
community.
It does not specify an Internet standard of any kind. 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
Association Management Solutions, LLC


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

*********************************
This message and any attachments (the "message") are confidential and inten=
ded solely for the addressees.=20
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.=20
France Telecom Group shall not be liable for the message if altered, change=
d or falsified.
If you are not the intended addressee of this message, please cancel it imm=
ediately and inform the sender.
********************************


From Senoo.Shoichiro@dc.MitsubishiElectric.co.jp  Wed Feb 17 17:54:57 2010
Return-Path: <Senoo.Shoichiro@dc.MitsubishiElectric.co.jp>
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 4EC3528C2B5 for <pce@core3.amsl.com>; Wed, 17 Feb 2010 17:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.11
X-Spam-Level: *
X-Spam-Status: No, score=1.11 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_13=0.6, J_CHICKENPOX_21=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 CxtIK9b8R6Zg for <pce@core3.amsl.com>; Wed, 17 Feb 2010 17:54:56 -0800 (PST)
Received: from mx06.melco.co.jp (mx06.melco.co.jp [192.218.140.146]) by core3.amsl.com (Postfix) with ESMTP id EACF628C2A4 for <pce@ietf.org>; Wed, 17 Feb 2010 17:54:55 -0800 (PST)
Received: from mr06.melco.co.jp (mr06 [133.141.98.164]) by mx06.melco.co.jp (Postfix) with ESMTP id 1B8365E6C5 for <pce@ietf.org>; Thu, 18 Feb 2010 10:56:35 +0900 (JST)
Received: from mr06.melco.co.jp (localhost [127.0.0.1]) by mr06.imss (Postfix) with ESMTP id DA56E25E3F for <pce@ietf.org>; Thu, 18 Feb 2010 10:56:34 +0900 (JST)
Received: from elgw.isl.melco.co.jp (unknown [133.141.13.130]) by mr06.melco.co.jp (Postfix) with ESMTP id A41C725E29 for <pce@ietf.org>; Thu, 18 Feb 2010 10:56:34 +0900 (JST)
Received: from iswall2a.isl.melco.co.jp (iswall2a.isl.melco.co.jp [10.74.245.24]) by elgw.isl.melco.co.jp (Postfix) with ESMTP id 745E431F3DD for <pce@ietf.org>; Thu, 18 Feb 2010 10:56:34 +0900 (JST)
Received: from iswall2a.isl.melco.co.jp (localhost.localdomain [127.0.0.1]) by localhost.isl.melco.co.jp (Postfix) with ESMTP id 2648D22CBE6 for <pce@ietf.org>; Thu, 18 Feb 2010 10:56:34 +0900 (JST)
Received: from LeakStopper186 (stopper2.isl.melco.co.jp [10.74.245.36]) by iswall2a.isl.melco.co.jp (Postfix) with SMTP id 0FA4A22CBD2 for <pce@ietf.org>; Thu, 18 Feb 2010 10:56:34 +0900 (JST)
Received: (qmail 25653 invoked by uid 507); 18 Feb 2010 10:56:33 +0900
Received: from unknown (HELO mob2501.isl.melco.co.jp) (133.141.13.135) by 0 with SMTP; 18 Feb 2010 10:51:35 +0900
Received: from KF5ZXSFDNOKJ9H8 (unknown [10.62.216.183]) by mob2501.isl.melco.co.jp (Postfix) with ESMTP id D2B9421D8148; Thu, 18 Feb 2010 10:51:34 +0900 (JST)
From: "Shoichiro Seno" <Senoo.Shoichiro@dc.MitsubishiElectric.co.jp>
To: <mpls@ietf.org>, <mpls-tp@ietf.org>, <ccamp@ietf.org>, <pce@ietf.org>
Date: Thu, 18 Feb 2010 10:51:38 +0900
Message-ID: <B46E9D53236C4D339736E74D842E80D0@KF5ZXSFDNOKJ9H8>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Thread-index: AcqwPOiWRafWxv+2Q/6NVNU13BvRMA==
Subject: [Pce] iPOP 2010 submission deadline extended to March 1
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, 18 Feb 2010 01:54:57 -0000

CCAMP, MPLS, MPLS-TP and PCE subscribers,

Please find below iPOP 2010 CFP with the extended deadline.

Sorry for multiple messages.

Sho Seno
-----------------------------------------------------------------------
                                 Call for Presentation

           6th International Conference on IP + Optical Network (iPOP 2010)
                                   June 10-11, 2010
                   NTT Musashino R&D Center, Tokyo, Japan
                         http://www.pilab.jp/ipop2010/

The conference is intended to share among the industry and the academia, the
knowledge, new findings, and experience on the state-of-the art of IP and
optical networking technologies. It features technical sessions and planned
exhibitions. The opportunity to participate is open to all.

Important Dates:
Submission deadline of one-page abstract: March 1, 2010 (extended) 
Notification of acceptance: April 2, 2010 
Submission deadline of final presentation slides: April 23, 2010

The Technical Program Committee for iPOP 2010 is soliciting presentation
proposals for this conference. Protocol design, experiment, theory,
implementation, and operational experiences are solicited.
The topics of the conference will include but not limited to the following:

* GMPLS/ASON technologies
* GMPLS Network management, OA&M
* Multi-layer network (MLN) / Multi-region network (MRN)
* Path Computation Element (PCE), Traffic engineering
* Inter-area/Inter-AS network
* L1VPN, Bandwidth on Demand, and Photonic Grid
* Wavelength Switched Optical Networks (WSON), Routing wavelength
  assignment, Impairment management
* GMPLS-controlled Ethernet Label Switching (GELS) and related Ethernet
  transport technologies
* Carrier Ethernet and MPLS-TP
* Photonic Network for NxGN and NwGN
* Application with high-bandwidth demand
* Testbed, field trial

If you wish to submit a topic for consideration, please send an Extended
Abstracts of a 400 words and a maximum of 1 page, including figures and
diagrams, speaker's name, affiliation, and contact information to the
Technical Program Committee at ipop2010-CFP@pilab.jp.
Please see http://www.pilab.jp/ipop2010/ for more details.

General Chairs:
Tomonori Aoyama, Keio University, Japan
Bijan Jabbari, ISOCORE, USA
Hisashi Koumura, NTT, Japan

Organization Committee Co-Chairs:
Naoaki Yamanaka, Keio University, Japan
Atsushi Hiramatsu, NTT, Japan
Soichiro Araki, NEC, Japan

Exhibition Committee Co-Chairs:
Kohei Shiomoto, NTT, Japan
Munefumi Tsurusawa, KDDI R&D, Japan

Technical Program Committee Co-Chairs:
Eiji Oki, University of Electro-Communications, Japan 
Monique Morrow, Cisco Systems, USA
----------------------------------------------------------------------------
----


From jvasseur@cisco.com  Fri Feb 19 14:29:08 2010
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 E6BD828C0DD for <pce@core3.amsl.com>; Fri, 19 Feb 2010 14:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.668
X-Spam-Level: 
X-Spam-Status: No, score=-5.668 tagged_above=-999 required=5 tests=[AWL=-3.070, 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 W1O2KOdg7Qpr for <pce@core3.amsl.com>; Fri, 19 Feb 2010 14:29:08 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id A34A23A7B99 for <pce@ietf.org>; Fri, 19 Feb 2010 14:29:07 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoAAC+gfkuQ/uCWe2dsb2JhbACbCRUBARYkBhymV5dyhGcE
X-IronPort-AV: E=Sophos;i="4.49,506,1262563200"; d="scan'208,217";a="3615162"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-2.cisco.com with ESMTP; 19 Feb 2010 21:59:08 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o1JMUsQr001872 for <pce@ietf.org>; Fri, 19 Feb 2010 22:30:54 GMT
Received: from xfe-ams-102.cisco.com ([144.254.231.94]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Feb 2010 23:30:54 +0100
Received: from ams-jvasseur-8714.cisco.com ([10.55.201.133]) by xfe-ams-102.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Fri, 19 Feb 2010 23:30:53 +0100
Message-Id: <E806F970-49AF-4E73-BE51-5DA15FB2F1AB@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-133-548644360
Mime-Version: 1.0 (Apple Message framework v936)
Date: Fri, 19 Feb 2010 23:30:53 +0100
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 19 Feb 2010 22:30:53.0607 (UTC) FILETIME=[3262AB70:01CAB1B3]
X-TM-AS-Product-Ver: SMEX-8.0.0.1181-6.000.1038-17204.002
X-TM-AS-Result: No--5.059400-8.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
Subject: [Pce] Porviosional Agenda
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, 19 Feb 2010 22:29:09 -0000

--Apple-Mail-133-548644360
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Here is the provisional agenda for the PCE WG Meeting - IETF-77 - Note  
that the final agenda will be available Feb 26:
THURSDAY, March 25, 2010

1300-1500  Afternoon Session I
Redondo         	INT 	netext      	Network-Based Mobility Extensions WG
Manhattan       	IRTF	SAMRG       	Scalable Adaptive Multicast  
Research Group
California B    	OPS 	grow        	Global Routing Operations WG
California A    	RAI 	p2psip      	Peer-to-Peer Session Initiation  
Protocol WG
Huntington      	RTG 	pce         	Path Computation Element WG
Palos Verdes    	RTG 	rtgwg       	Routing Area Working Group WG
California D    	SEC 	saag        	Security Area Open Meeting
California C    	TSV 	behave      	Behavior Engineering for Hindrance  
Avoidance WG
We will soon start working on the agenda.

Thanks.

JP.
--Apple-Mail-133-548644360
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"font-family: Times; "><span class=3D"Apple-style-span" =
style=3D"font-family: Helvetica; ">Here is the provisional agenda for =
the PCE WG Meeting - IETF-77 - Note that the final agenda will be =
available Feb 26:</span><pre style=3D"word-wrap: break-word; =
white-space: pre-wrap; ">THURSDAY, March 25, 2010</pre><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; ">
1300-1500  Afternoon Session I
Redondo         	INT 	netext      	Network-Based Mobility =
Extensions WG
Manhattan       	IRTF	SAMRG       	Scalable Adaptive =
Multicast Research Group=20
California B    	OPS 	grow        	Global Routing =
Operations WG
California A    	RAI 	p2psip      	Peer-to-Peer Session =
Initiation Protocol WG
Huntington      	RTG 	pce         	Path Computation Element =
WG
Palos Verdes    	RTG 	rtgwg       	Routing Area Working =
Group WG
California D    	SEC 	saag        	Security Area Open =
Meeting=20
California C    	TSV 	behave      	Behavior Engineering for =
Hindrance Avoidance WG</pre><pre style=3D"word-wrap: break-word; =
white-space: pre-wrap; "><span class=3D"Apple-style-span" =
style=3D"font-family: Times; white-space: normal; "><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; "><span =
class=3D"Apple-style-span" style=3D"font-family: Helvetica; white-space: =
normal; ">We will soon start working on the agenda.</span></pre><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; "><font =
class=3D"Apple-style-span" face=3D"Helvetica"><span =
class=3D"Apple-style-span" style=3D"white-space: normal; =
"><br></span></font></pre><pre style=3D"word-wrap: break-word; =
white-space: pre-wrap; "><font class=3D"Apple-style-span" =
face=3D"Helvetica"><span class=3D"Apple-style-span" style=3D"white-space: =
normal; ">Thanks.</span></font></pre><pre style=3D"word-wrap: =
break-word; white-space: pre-wrap; "><font class=3D"Apple-style-span" =
face=3D"Helvetica"><span class=3D"Apple-style-span" style=3D"white-space: =
normal; "><br></span></font></pre><pre style=3D"word-wrap: break-word; =
white-space: pre-wrap; "><font class=3D"Apple-style-span" =
face=3D"Helvetica"><span class=3D"Apple-style-span" style=3D"white-space: =
normal; ">JP.</span></font></pre></span></pre></span></body></html>=

--Apple-Mail-133-548644360--

From wwwrun@core3.amsl.com  Mon Feb 22 06:04:57 2010
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 27F8428C125; Mon, 22 Feb 2010 06:04:57 -0800 (PST)
X-idtracker: yes
To: IETF-Announce <ietf-announce@ietf.org> 
From: The IESG <iesg-secretary@ietf.org>
Message-Id: <20100222140457.27F8428C125@core3.amsl.com>
Date: Mon, 22 Feb 2010 06:04:57 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] Last Call: draft-ietf-pce-pcep-svec-list (The use of SVEC (Synchronization VECtor) list for Synchronized dependent path computations) 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: Mon, 22 Feb 2010 14:04:57 -0000

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

- 'The use of SVEC (Synchronization VECtor) list for Synchronized 
   dependent path computations '
   <draft-ietf-pce-pcep-svec-list-04.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 2010-03-08. 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-pcep-svec-list-04.txt


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


From wwwrun@core3.amsl.com  Mon Feb 22 09:36:42 2010
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 3987728C151; Mon, 22 Feb 2010 09:36:41 -0800 (PST)
X-idtracker: yes
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <20100222173642.3987728C151@core3.amsl.com>
Date: Mon, 22 Feb 2010 09:36:42 -0800 (PST)
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: 'PCC-PCE Communication Requirements for Point to Multipoint Multiprotocol Label Switching Traffic Engineering (MPLS-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: Mon, 22 Feb 2010 17:36:42 -0000

The IESG has approved the following document:

- 'PCC-PCE Communication Requirements for Point to Multipoint 
   Multiprotocol Label Switching Traffic Engineering (MPLS-TE) '
   <draft-ietf-pce-p2mp-req-05.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-req-05.txt

Technical Summary

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

Working Group Summary

   Good consensus reported with no controversy (see PROTO writeup by
   JP Vasseur in the ID Tracker). 

Document Quality

   The document thas had adequate review, and has passed WG and IETF
   last calls, and has been updated based on minor comments received
   during IETF last call. As an informational requirements document
   this is not subject to be implemented. There is ongoing work in the 
   PCE working group to define point to multipoint extensions to PCE. 

Personnel

   JP Vasseur is the Document Shepherd for this document. Ross Callon
   is the Responsible Area Director.


From jvasseur@cisco.com  Mon Feb 22 23:24:30 2010
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 41A9128C536 for <pce@core3.amsl.com>; Mon, 22 Feb 2010 23:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.505
X-Spam-Level: 
X-Spam-Status: No, score=-5.505 tagged_above=-999 required=5 tests=[AWL=-2.907, 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 JpzEoxTUhUom for <pce@core3.amsl.com>; Mon, 22 Feb 2010 23:24:29 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by core3.amsl.com (Postfix) with ESMTP id DA44C28C540 for <pce@ietf.org>; Mon, 22 Feb 2010 23:24:28 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvAAABwSg0uQ/uCWe2dsb2JhbACBQplEFQEBFiQGHKIQmEKEaQQ
X-IronPort-AV: E=Sophos;i="4.49,524,1262563200"; d="scan'208,217";a="3685767"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-2.cisco.com with ESMTP; 23 Feb 2010 06:54:28 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o1N7QU4S028677 for <pce@ietf.org>; Tue, 23 Feb 2010 07:26:30 GMT
Received: from xfe-ams-201.cisco.com ([144.254.231.95]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 23 Feb 2010 08:26:30 +0100
Received: from ams-jvasseur-8712.cisco.com ([10.55.201.131]) by xfe-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.3959);  Tue, 23 Feb 2010 08:26:30 +0100
Message-Id: <6FE9B571-9518-4056-8855-DFDD3F175AFC@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
To: pce@ietf.org
Content-Type: multipart/alternative; boundary=Apple-Mail-233-839981126
Mime-Version: 1.0 (Apple Message framework v936)
Date: Tue, 23 Feb 2010 08:26:29 +0100
References: <20100222200002.042C53A8142@core3.amsl.com>
X-Mailer: Apple Mail (2.936)
X-OriginalArrivalTime: 23 Feb 2010 07:26:30.0280 (UTC) FILETIME=[84931080:01CAB459]
Subject: [Pce] Fwd: Internet Draft Cut-off Dates Reminder
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, 23 Feb 2010 07:24:30 -0000

--Apple-Mail-233-839981126
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit



Begin forwarded message:

> From: IETF Secretariat <ietf-secretariat@ietf.org>
> Date: February 22, 2010 9:00:01 PM CEST
> To: ietf-announce@ietf.org
> Subject: Internet Draft Cut-off Dates Reminder
>
>
> This is a reminder that the Internet Draft Cut-off Dates are  
> approaching.
>
>
> The initial draft (version -00) cut-off date is Monday, March 1, 2010.
> These submissions are due by 17:00 PST (01:00 Tuesday, March 2 UTC).
>
> The Internet Draft final submission (version -01 and up) cut-off is
> Monday, March 8, 2010 at 17:00 PST (01:00 Tuesday, March 2 UTC).
>
> All drafts can be uploaded using the ID submission tool located here:
> https://datatracker.ietf.org/idst/upload.cgi
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


--Apple-Mail-233-839981126
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><br><div>Begin =
forwarded message:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" color=3D"#000000" =
style=3D"font: 14.0px Helvetica; color: #000000"><b>From: =
</b></font><font face=3D"Helvetica" size=3D"4" style=3D"font: 14.0px =
Helvetica">IETF Secretariat &lt;<a =
href=3D"mailto:ietf-secretariat@ietf.org">ietf-secretariat@ietf.org</a>&gt=
;</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"4" color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>Date: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica">February 22, 2010 9:00:01 PM =
CEST</font></div><div style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><font face=3D"Helvetica" =
size=3D"4" color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>To: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica"><a =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a></font></=
div><div style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><font face=3D"Helvetica" size=3D"4" =
color=3D"#000000" style=3D"font: 14.0px Helvetica; color: =
#000000"><b>Subject: </b></font><font face=3D"Helvetica" size=3D"4" =
style=3D"font: 14.0px Helvetica"><b>Internet Draft Cut-off Dates =
Reminder<span =
class=3D"Apple-converted-space">&nbsp;</span></b></font></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><br></div> </div><div><br>This is =
a reminder that the Internet Draft Cut-off Dates are =
approaching.<br><br><br>The initial draft (version -00) cut-off date is =
Monday, March 1, 2010. <br>These submissions are due by 17:00 PST (01:00 =
Tuesday, March 2 UTC).<br><br>The Internet Draft final submission =
(version -01 and up) cut-off is<br>Monday, March 8, 2010 at 17:00 PST =
(01:00 Tuesday, March 2 UTC).<br><br>All drafts can be uploaded using =
the ID submission tool located here:<br><a =
href=3D"https://datatracker.ietf.org/idst/upload.cgi">https://datatracker.=
ietf.org/idst/upload.cgi</a><br>__________________________________________=
_____<br>IETF-Announce mailing =
list<br>IETF-Announce@ietf.org<br>https://www.ietf.org/mailman/listinfo/ie=
tf-announce<br></div></blockquote></div><br></body></html>=

--Apple-Mail-233-839981126--

From root@core3.amsl.com  Fri Feb 26 01:45:01 2010
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 53D983A85EB; Fri, 26 Feb 2010 01:45:00 -0800 (PST)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20100226094501.53D983A85EB@core3.amsl.com>
Date: Fri, 26 Feb 2010 01:45:01 -0800 (PST)
Cc: pce@ietf.org
Subject: [Pce] I-D Action:draft-ietf-pce-manageability-requirements-08.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, 26 Feb 2010 09: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           : Inclusion of Manageability Sections in PCE Working Group Drafts
	Author(s)       : A. Farrel
	Filename        : draft-ietf-pce-manageability-requirements-08.txt
	Pages           : 12
	Date            : 2010-02-26

It has often been the case that manageability considerations have
been retrofitted to protocols after they have been specified,
standardized, implemented, or deployed. This is sub-optimal.

Similarly, new protocols or protocol extensions are frequently
designed without due consideration of manageability requirements.

This document specifies the recommendation for all new
Internet-Drafts in the PCE Working Group to include a
"Manageability Considerations" section, and gives guidance on what
that section should contain.

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

Content-Type: text/plain
Content-ID: <2010-02-26013815.I-D@ietf.org>


--NextPart--

From adrian@olddog.co.uk  Fri Feb 26 01:47:15 2010
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 A811B28C103 for <pce@core3.amsl.com>; Fri, 26 Feb 2010 01:47:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.31
X-Spam-Level: 
X-Spam-Status: No, score=-2.31 tagged_above=-999 required=5 tests=[AWL=0.288,  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 hTfa-S0hpTX9 for <pce@core3.amsl.com>; Fri, 26 Feb 2010 01:47:15 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id A04BA28C0D7 for <pce@ietf.org>; Fri, 26 Feb 2010 01:47:14 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id o1Q9nB7X008749 for <pce@ietf.org>; Fri, 26 Feb 2010 09:49:16 GMT
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 o1Q9n8aB008719 for <pce@ietf.org>; Fri, 26 Feb 2010 09:49:10 GMT
Message-ID: <76F0884DE18D475CA4AA355716E3DD20@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Fri, 26 Feb 2010 09:49:06 -0000
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: [Pce] draft-ietf-pce-manageability-requirements
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, 26 Feb 2010 09:47:15 -0000

Hi PCE WG,

Over the last couple of years, you have been reasonably willing 
experimenters with draft-ietf-pce-manageability-requirements. IMHO, this has 
resulted in greatly improved output from the working group, and we have seen 
PCE drafts progress through IESG review with a bit more ease as a result.

However, with the recent publication of RFC 5706, the working group needs to 
decide what to do about this draft. It seems that the choices are:

- Continue to keep the draft alive as a reference for the WG, but do not
  seek to progress it to RFC
- Abandon the draft and use RFC 5706 as the reference for
  future manageability work
- Request publication of this draft as a Historic RFC and move to use
  RFC 5706 as the reference for future manageability work

I have just posted a new revision of 
draft-ietf-pce-manageability-requirements to keep it alive, but this is most 
certainly not an attempt by your AD to dictate what you should do.

Maybe this is a topic the WG chairs would like to discuss with you (possibly 
in Anaheim) with a view to letting me know what you would like to do with 
this draft.

Thanks,
Adrian 

