From pce-bounces@lists.ietf.org Wed Sep 06 19:00:14 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GL6N0-0006qj-7R; Wed, 06 Sep 2006 18:59:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GL6My-0006np-IR
	for pce@ietf.org; Wed, 06 Sep 2006 18:59:44 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GL3iV-0004Cw-Vl
	for pce@ietf.org; Wed, 06 Sep 2006 16:09:48 -0400
Received: from mail2.noc.data.net.uk ([80.68.34.49])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1GL3Y6-0000al-3Y
	for pce@ietf.org; Wed, 06 Sep 2006 15:59:08 -0400
Received: from 57-99.dsl.data.net.uk ([80.68.57.99]
	helo=cortex.aria-networks.com)
	by mail2.noc.data.net.uk with esmtp (Exim 3.36 #1)
	id 1GL3Y0-0000Y7-00 for pce@ietf.org; Wed, 06 Sep 2006 20:58:56 +0100
Received: from your029b8cecfe ([217.158.132.162] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 6 Sep 2006 20:58:59 +0100
Message-ID: <003001c6d1ee$e21b4f20$a2849ed9@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <pce@ietf.org>
Date: Wed, 6 Sep 2006 20:57:20 +0100
Organization: Old Dog Consulting
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 06 Sep 2006 19:59:00.0418 (UTC)
	FILETIME=[E52FE220:01C6D1EE]
X-Spam-Score: -2.0 (--)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: 
Subject: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi,

We have posted a new version of this I-D discussing the additional 
requirements for PCECP to support the use of PCE for P2MP MPLS-TE and GMPLS.

The main changes are the additions of sections 2.1.9 and 2.1.10 that 
describe re-optimisation and the addition/removal of destinations.

Other changes are editorial and re-wordings for clarity.

Your comments are very welcome.

Regards,
Adrian and Seisho

----- Original Message ----- 
From: "IETF Secretariat" <ietf-secretariat-reply@ietf.org>
To: "Adrian Farrel" <adrian@olddog.co.uk>
Cc: "Seisho Yasukawa" <yasukawa.seisho@lab.ntt.co.jp>
Sent: Wednesday, September 06, 2006 8:50 PM
Subject: Posting of draft-yasukawa-pce-p2mp-req-01.txt


> As you requested, draft-yasukawa-pce-p2mp-req-01.txt, an updated version 
> of an
> expired Internet-Drafts, has been posted.  The draft will expire on March 
> 10,
> 2007 unless it is replaced by an updated version, or the Secretariat has 
> been
> notified that the document is under official review by the IESG or has 
> been
> passed to the RFC Editor for review and/or publication as an RFC.
>
> The IETF Secretariat.
>
>
> 



_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Thu Sep 07 15:29:46 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLPYu-0004rB-0j; Thu, 07 Sep 2006 15:29:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLPYt-0004r3-3g; Thu, 07 Sep 2006 15:29:19 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLPYr-0004UK-MB; Thu, 07 Sep 2006 15:29:19 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 07 Sep 2006 15:29:17 -0400
X-IronPort-AV: i="4.08,226,1154923200"; 
	d="scan'208,217"; a="101215468:sNHT49780892"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13])
	by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k87JTH4M026755; Thu, 7 Sep 2006 15:29:17 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k87JTFuI020310; 
	Thu, 7 Sep 2006 15:29:17 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 15:29:15 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 7 Sep 2006 15:29:14 -0400
References: <003001c6d1ee$e21b4f20$a2849ed9@your029b8cecfe>
Mime-Version: 1.0 (Apple Message framework v752.2)
X-Priority: 3
Message-Id: <1ABE3FD2-A213-4CE5-9566-4A27EBD7CFAB@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Subject: Fwd: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt 
Date: Thu, 7 Sep 2006 15:29:12 -0400
To: mpls@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 07 Sep 2006 19:29:14.0224 (UTC)
	FILETIME=[E6F20F00:01C6D2B3]
DKIM-Signature: a=rsa-sha1; q=dns; l=10057; t=1157657357; x=1158521357;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Fwd=3A=20[Pce]=20Fw=3A=20Posting=20of=20draft-yasukawa-pce-p2mp-req-01.t
	xt=20 |To:mpls@ietf.org;
	X=v=3Dcisco.com=3B=20h=3DfAgHumO9E48nrfpXp1bUJYankSs=3D;
	b=o8GODEw9IvJ86+W856JQvuJ3YoeKP/wFAtHs4aj/PPbZW6YOZrlSJQ59qv60RpGTsxAMQt9k
	ueyQ8JRtBs1EihBICpjPo8PeFWvOrIZIZnqvPKAYhS/ZcnzohCPepKci;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass (
	31 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Cc: pce@ietf.org
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2111018793=="
Errors-To: pce-bounces@lists.ietf.org


--===============2111018793==
Content-Type: multipart/alternative; boundary=Apple-Mail-33--1038473459


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

Any feed-back from the MPLS WG would be most welcome.

Thanks.

JP.

Begin forwarded message:

> From: "Adrian Farrel" <adrian@olddog.co.uk>
> Date: September 6, 2006 3:57:20 PM EDT
> To: <pce@ietf.org>
> Subject: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt
> Reply-To: Adrian Farrel <adrian@olddog.co.uk>
>
> Hi,
>
> We have posted a new version of this I-D discussing the additional  
> requirements for PCECP to support the use of PCE for P2MP MPLS-TE  
> and GMPLS.
>
> The main changes are the additions of sections 2.1.9 and 2.1.10  
> that describe re-optimisation and the addition/removal of  
> destinations.
>
> Other changes are editorial and re-wordings for clarity.
>
> Your comments are very welcome.
>
> Regards,
> Adrian and Seisho
>
> ----- Original Message ----- From: "IETF Secretariat" <ietf- 
> secretariat-reply@ietf.org>
> To: "Adrian Farrel" <adrian@olddog.co.uk>
> Cc: "Seisho Yasukawa" <yasukawa.seisho@lab.ntt.co.jp>
> Sent: Wednesday, September 06, 2006 8:50 PM
> Subject: Posting of draft-yasukawa-pce-p2mp-req-01.txt
>
>
>> As you requested, draft-yasukawa-pce-p2mp-req-01.txt, an updated  
>> version of an
>> expired Internet-Drafts, has been posted.  The draft will expire  
>> on March 10,
>> 2007 unless it is replaced by an updated version, or the  
>> Secretariat has been
>> notified that the document is under official review by the IESG or  
>> has been
>> passed to the RFC Editor for review and/or publication as an RFC.
>>
>> The IETF Secretariat.
>>
>>
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/pce


--Apple-Mail-33--1038473459
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Any=A0feed-back from the MPLS WG =
would be most welcome.<BR><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Thanks.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>JP.</DIV><DIV><BR><DIV>Begin =
forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica">"Adrian Farrel" &lt;<A =
href=3D"mailto:adrian@olddog.co.uk">adrian@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"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Date: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica">September 6, 2006 3:57:20 PM EDT</FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>To: </B></FONT><FONT =
face=3D"Helvetica" size=3D"5" style=3D"font: 16.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"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Subject: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><B>[Pce] Fw: Posting of =
draft-yasukawa-pce-p2mp-req-01.txt<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></B></FONT></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>Reply-To: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica">Adrian Farrel &lt;<A =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</A>&gt;</FONT></DI=
V><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> <DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">Hi,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">We have posted a new version of this I-D discussing =
the additional requirements for PCECP to support the use of PCE for P2MP =
MPLS-TE and GMPLS.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">The main changes are the =
additions of sections 2.1.9 and 2.1.10 that describe re-optimisation and =
the addition/removal of destinations.</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Other changes =
are editorial and re-wordings for clarity.</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Your comments =
are very welcome.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Regards,</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Adrian and =
Seisho</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">----- Original Message ----- From: "IETF =
Secretariat" &lt;<A =
href=3D"mailto:ietf-secretariat-reply@ietf.org">ietf-secretariat-reply@iet=
f.org</A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">To: "Adrian Farrel" &lt;<A =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</A>&gt;</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Cc: "Seisho Yasukawa" &lt;<A =
href=3D"mailto:yasukawa.seisho@lab.ntt.co.jp">yasukawa.seisho@lab.ntt.co.j=
p</A>&gt;</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Sent: Wednesday, September 06, =
2006 8:50 PM</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Subject: Posting of =
draft-yasukawa-pce-p2mp-req-01.txt</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV> =
<BLOCKQUOTE type=3D"cite"><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">As you requested, =
draft-yasukawa-pce-p2mp-req-01.txt, an updated version of an</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">expired Internet-Drafts, has been posted.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>The draft will expire on =
March 10,</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">2007 unless it is replaced by an =
updated version, or the Secretariat has been</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">notified that the document is under official review =
by the IESG or has been</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">passed to the =
RFC Editor for review and/or publication as an RFC.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">The IETF =
Secretariat.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV> </BLOCKQUOTE><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Pce mailing list</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:Pce@lists.ietf.org">Pce@lists.ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/pce">https://www1.ietf.org/=
mailman/listinfo/pce</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>=

--Apple-Mail-33--1038473459--


--===============2111018793==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--===============2111018793==--




From pce-bounces@lists.ietf.org Fri Sep 08 08:01:57 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLf32-0007zQ-5y; Fri, 08 Sep 2006 08:01:28 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLezC-00065D-Hv; Fri, 08 Sep 2006 07:57:30 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GLezC-0003Q1-Fi; Fri, 08 Sep 2006 07:57:30 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GLezA-0003IV-Ce; Fri, 08 Sep 2006 07:57:30 -0400
Received: from ietf.org (stiedprweb1.va.neustar.com [10.91.34.42])
	by ns3.neustar.com (Postfix) with ESMTP id 050AD175D0;
	Fri,  8 Sep 2006 11:56:58 +0000 (GMT)
Received: from mirror by ietf.org with local (Exim 4.43)
	id 1GLeyf-00088V-Jw; Fri, 08 Sep 2006 07:56:57 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: Greg Jones <greg.jones@itu.int>
From: Adrian Farrel (IETF PCE WG) <adrian@olddog.co.uk>
Message-Id: <E1GLeyf-00088V-Jw@ietf.org>
Date: Fri, 08 Sep 2006 07:56:57 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-Mailman-Approved-At: Fri, 08 Sep 2006 08:01:27 -0400
Cc: Stephen Trowbridge <sjtrowbridge@lucent.com>,
	Bill Fenner <fenner@research.att.com>,
	Kam Lam <hklam@lucent.com>, Scott Bradner <sob@harvard.edu>,
	JP Vasseur <jpv@cisco.com>, PCE mailing list <pce@ietf.org>,
	Ross Callon <rcallon@juniper.net>
Subject: [Pce] New Liaison Statement, "Publication of new RFC on PCE 
 Architecture" 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org


Title: Publication of new RFC on PCE Architecture
Submission Date: 2006-09-08
URL of the IETF Web page: https://datatracker.ietf.org/public/liaison_detail.cgi?detail_id=260 

From: Adrian Farrel(IETF PCE WG) <adrian@olddog.co.uk>
To: ITU-T SG15 Q14(Greg Jones <greg.jones@itu.int>)
Cc: Kam Lam <hklam@lucent.com>
Dean Cheng <dcheng@cisco.com>
Stephen Trowbridge <sjtrowbridge@lucent.com>
Scott Bradner <sob@harvard.edu>
Ross Callon <rcallon@juniper.net>
Bill Fenner <fenner@research.att.com>
JP Vasseur <jpv@cisco.com>
PCE mailing list <pce@ietf.org>
Reponse Contact: Adrian Farrel <adrian@olddog.co.uk>
Technical Contact: Adrian Farrel <adrian@olddog.co.uk>
Purpose: For information 
Body: The PCE Working Group of the IETF is pleased to inform you of the publication of a new RFC on the PCE architecture.

RFC 4655 is titled "A Path Computation Element (PCE)-Based Architecture"

The Abstract of this RFC reads as follows:

   Constraint-based path computation is a fundamental building block for
   traffic engineering systems such as Multiprotocol Label Switching
   (MPLS) and Generalized Multiprotocol Label Switching (GMPLS)
   networks.  Path computation in large, multi-domain, multi-region, or
   multi-layer networks is complex and may require special computational
   components and cooperation between the different network domains.

   This document specifies the architecture for a Path Computation
   Element (PCE)-based model to address this problem space.  This
   document does not attempt to provide a detailed description of all
   the architectural components, but rather it describes a set of
   building blocks for the PCE architecture from which solutions may be
   constructed.

The RFC can be downloaded without charge from:
http://www.ietf.org/rfc/rfc4655.txt

We believe that this RFC will be of interest to you in your work on G.7715.2 and we would welcome any comments or questions about this RFC or any other issues related to PCE through our open mailing list. For subscription information about the mailing list and other information about the PCE working group, please visit our Web page at:
http://www.ietf.org/html.charters/pce-charter.html

Best regards,
Adrian Farrel and JP Vasseur
PCE Working Group Co-chairs
Attachment(s):
No document has been attached



_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Sat Sep 09 00:07:49 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GLu7R-0005gR-O9; Sat, 09 Sep 2006 00:07:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GLu7Q-0005gC-69
	for pce@ietf.org; Sat, 09 Sep 2006 00:07:00 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GLu7M-0003k9-G7
	for pce@ietf.org; Sat, 09 Sep 2006 00:07:00 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186])
	by sj-iport-6.cisco.com with ESMTP; 08 Sep 2006 21:06:55 -0700
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238])
	by sj-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8946tvX006898; Fri, 8 Sep 2006 21:06:55 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com
	[128.107.191.63])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id k8946t1E008304;
	Fri, 8 Sep 2006 21:06:55 -0700 (PDT)
Received: from xmb-sjc-234.amer.cisco.com ([128.107.191.111]) by
	xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 8 Sep 2006 21:06:55 -0700
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
Subject: RE: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt 
Date: Fri, 8 Sep 2006 21:06:52 -0700
Message-ID: <70BC84B185C3EE448EDB7AB8956D3B0E023EF0C6@xmb-sjc-234.amer.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt 
Thread-Index: AcbTV/OMb9FZqPIiR3GAif3wL3ijpAAF3WAg
From: "Dean Cheng \(dcheng\)" <dcheng@cisco.com>
To: "Adrian Farrel" <adrian@olddog.co.uk>, <s.yasukawa@hco.ntt.co.jp>
X-OriginalArrivalTime: 09 Sep 2006 04:06:55.0064 (UTC)
	FILETIME=[630FDD80:01C6D3C5]
DKIM-Signature: a=rsa-sha1; q=dns; l=6129; t=1157774815; x=1158638815;
	c=relaxed/simple; s=sjdkim2002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=dcheng@cisco.com;
	z=From:=22Dean=20Cheng=20\(dcheng\)=22=20<dcheng@cisco.com>
	|Subject:RE=3A=20[Pce]=20Fw=3A=20Posting=20of=20draft-yasukawa-pce-p2mp-req-01.tx
	t=20; X=v=3Dcisco.com=3B=20h=3D5kbqvbi4os9uP+ZyjVdHsqLsbI8=3D;
	b=fRepJeq6nnOt++KkoSpZSywvcA+RajLvTo6yUZh20sDCWZRGzocOI2oesY2c+BnB78wqoypH
	KNKsJADsrIKEJ0BGvakFot0LIJEPnCdZ2cuR0kBG3GZ5advQvLgzVje1;
Authentication-Results: sj-dkim-2.cisco.com; header.From=dcheng@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d890c9ddd0b0a61e8c597ad30c1c2176
Cc: pce@ietf.org
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi Adrian,

Thanks for the response.

Please see below.

Dean=20

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]=20
> Sent: Friday, September 08, 2006 6:07 AM
> To: Dean Cheng (dcheng); s.yasukawa@hco.ntt.co.jp
> Subject: Re: [Pce] Fw: Posting of draft-yasukawa-pce-p2mp-req-01.txt=20
>=20
> Hi Dean,
>=20
> Thanks for your thoughts:
>=20
> > 1) Relate to Section 2.1.1/2.1.2/2.1.3
> >
> >    In case a path computation is required just for
> >    a P2P "short path" (could be a branch of a P2MP LSP,
> >    such as a last segment leading to a leaf node)
> >    where the semantics is not that different from
> >    a simple P2P path, it would be possibly be performed
> >    just by a PCE that is not capable of computing
> >    P2MP path in general.
> >
> >    If this is correct, this PCE does not need to
> >    know the requested path is part of a P2MP LSP,
> >    as long as there is no P2MP specific parameters
> >    contained in the PCEP request message. On the
> >    other hand, the PCC in this case does not need to
> >    include P2MP specific parameters in the request message.
>=20
> I'm a bit confused. Are you talking about adding a branch=20
> (e.g. adding a
> leaf) into an existing P2MP tree?
>=20
> There are two questions to be addressed when you do that:
> 1. Choice of branch node in order to optimise the path from=20
> the tree to the leaf.
> 2. Choice of path from tree to the leaf considering the=20
> constraints on the whole tree.
>=20
> But, if the choice of 1 is determined simply by running CSPF=20
> from root to leaf, and if the choice of 2 is determined=20
> simply by running CSPF from branch to leaf, then you are=20
> correct. However:
>=20
> a. This is a really BIG "if" that doesn't (or shouldn't)=20
> apply to P2MP TE path computation b. If that is what you=20
> want, then you are not doing a P2MP computation and this I-D=20
> simply doesn't apply.

  What I meant is that sometimes there is a need to compute a
  P2P LSP that is part of a P2MP LSP, and when that occurs,=20
  the PCC (although it knows the P2P LSP is a part of a P2MP LSP)
  may need just to ask a PCE for a route for that P2P LSP, where
  the PCEP message does not need to contain any P2MP specific
  paremeters, which the PCE may not understand, and the PCE only
  needs to compute a P2P path.

  This P2P LSP may be between a branch node and a leaf node, or
  between a intermediate node and a branch node (a trunk path),=20
  etc.=20
 =20
  One other reason doing so may be because a PCC has learnt that
  some PCEs cannot compute routes for a P2MP LSP as a whole
  during discovery process.

  But (as you suggested) in this case, it has nothing to do with
  this I-D; but it may be helpful to add one sentence for=20
  this scenario to clarify.=20

>=20
> > 2) Section 2.1.9
> >
> >    The 3rd line of the second paragraph.
> >
> >    "availablity" =3D> "availability"
>=20
> Thanks.
>=20
> > 3) Section 2.1.10
> >
> >    The second word.
> >
> >    "varitation" =3D> "variation"
>=20
> Thanks.
>=20
> > 4) Section 2.1.10
> >
> >    4a) For leaf additions, in addition to the "indications"
> >        included in the PCEP request message, as listed in
> >        current text (three bullets now), the following may
> >        also be useful:
> >
> >        - Which branch nodes currently on the P2MP LSP must
> >          still or must not be used.
>=20
> Yes? Can you suggest why this would be useful?
> I can see that when you place a P2MP LSP you might want to=20
> constraint the branches, to come from a set, but why would=20
> you want this specific function?
>=20
> No problem adding this PCECP requirement, but I just want to=20
> be able to back it up with an underlying functional requirement.

I think this is a policy based function. The default for optimization
of a tree/subtree is relying on the PCE's computation algorithm. But
a policy may be imposed so that an existing branch node must stay as=20
is (even a better option exists), or the opposite.=20

>=20
> >        - The subtree rooted at a specific branch node currently
> >          on the P2MP LSP must not be recomputed.
>=20
> That is good, I think.
>=20
> >        - The subtree rooted at a specific branch node currently
> >          on the P2MP LSP may be recomputed for re-optimization
> >          purpose.
>=20
> Converse of above.
> Yes.

Yes the two above can be combined as one with an "or".

>=20
> >    4b) If modification/optimization occurs when deleting one
> >        or more leaf nodes, some of the "indications" currently
> >        listed for leaf additions (include the 4a above) are
> >        equally applied. If agreed, perhaps these indications
> >        should be listed for both cases (certainly, indications
> >        for which leaf nodes are to be added or deleted need
> >        to be specifically expressed), for simplicity.
>=20
> Yes. Makes sense.
>=20
> > 5) Section 4
> >
> >    For security and confidentiality, there may be special
> >    considerations for P2MP LSP using PCE. For example,
> >    subtrees that have the same root or branch node may be in
> >    different areas/domains such that the handling/requirements
> >    for confidentiality/security are different, and therefore PCE
> >    and PCEP must be able to deal with it.
>=20
> Right.
> These things probably need to be brought out in their own section.
> I suspect that what you are suggesting is that it MUST be=20
> possible to require that the tree has no more than one entry=20
> point into any domain? And possibly other issues.

Yes, the number of entries and which ones are security concerns and
should be part of the constraints for path findings.

>=20
> Do you want to have a go at some text for that?
Sure, I'll propose some text for that.

>=20
>=20
> Many thanks.
>=20
> If you want to bring ay or all of this to the PCE mailing=20
> list, that would be really helpful.
OK

>=20
> Cheers,
> Adrian=20
>=20

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Wed Sep 20 15:50:45 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQ858-0005gY-4o; Wed, 20 Sep 2006 15:50:06 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQ853-0005cB-UO; Wed, 20 Sep 2006 15:50:01 -0400
Received: from ns0.neustar.com ([156.154.16.158])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GQ853-0003Ig-LF; Wed, 20 Sep 2006 15:50:01 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns0.neustar.com (Postfix) with ESMTP id 9878632884;
	Wed, 20 Sep 2006 19:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GQ853-0005wA-GL; Wed, 20 Sep 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GQ853-0005wA-GL@stiedprstage1.ietf.org>
Date: Wed, 20 Sep 2006 15:50:01 -0400
X-Spam-Score: -2.5 (--)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-ospf-00.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

--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		: OSPF protocol extensions for Path Computation Element (PCE) Discovery 
	Author(s)	: J. Le Roux, et al.
	Filename	: draft-ietf-pce-disco-proto-ospf-00.txt
	Pages		: 24
	Date		: 2006-9-20
	
There are various circumstances in which it is highly desirable for a 
Path Computation Client (PCC) to be able to dynamically and 
automatically discover a set of Path Computation Element(s) (PCE), 
along with some of information that can be used for PCE selection. 
When the PCE is an LSR participating to the IGP, or even a server 
participating passively to the IGP, a simple and efficient way for 
PCE discovery consists of relying on IGP flooding. For that purpose 
this document defines OSPF extensions for the advertisement of PCE 
Discovery information within an OSPF area or within the entire OSPF 
routing domain.  


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-disco-proto-ospf-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pce-disco-proto-ospf-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pce-disco-proto-ospf-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-9-20142926.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pce-disco-proto-ospf-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pce-disco-proto-ospf-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-20142926.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--NextPart--




From pce-bounces@lists.ietf.org Wed Sep 20 20:18:42 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQCGh-0005Z1-Fl; Wed, 20 Sep 2006 20:18:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQCGe-0005Xu-KL; Wed, 20 Sep 2006 20:18:16 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129]
	helo=chiedprmail1.ietf.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GQ8Xz-0008Qs-Gj; Wed, 20 Sep 2006 16:19:55 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1GQ8OC-0002eZ-AI; Wed, 20 Sep 2006 16:09:50 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id DE6A5175CB;
	Wed, 20 Sep 2006 19:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1GQ853-0005w7-Fn; Wed, 20 Sep 2006 15:50:01 -0400
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1GQ853-0005w7-Fn@stiedprstage1.ietf.org>
Date: Wed, 20 Sep 2006 15:50:01 -0400
X-Spam-Score: -5.9 (-----)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: pce@ietf.org
Subject: [Pce] I-D ACTION:draft-ietf-pce-disco-proto-isis-00.txt 
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

--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		: IS-IS protocol extensions for Path Computation Element (PCE) Discovery 
	Author(s)	: J. Le Roux, et al.
	Filename	: draft-ietf-pce-disco-proto-isis-00.txt
	Pages		: 21
	Date		: 2006-9-20
	
There are various circumstances in which it is highly desirable for a 
Path Computation Client (PCC) to be able to dynamically and 
automatically discover a set of Path Computation Element(s) (PCE), 
along with some of information that can be used for PCE selection. 
When the PCE is an LSR participating to the IGP, or even a server 
participating passively to the IGP, a simple and efficient way for 
PCE discovery consists of relying on IGP flooding. For that purpose 
this document defines ISIS extensions for the advertisement of PCE 
Discovery information within an ISIS area or within the entire ISIS 
routing domain.  


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-disco-proto-isis-00.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-pce-disco-proto-isis-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-pce-disco-proto-isis-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

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: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-9-20142623.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-pce-disco-proto-isis-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-pce-disco-proto-isis-00.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-9-20142623.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--NextPart--




From pce-bounces@lists.ietf.org Fri Sep 22 17:49:51 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQstG-0006fR-2s; Fri, 22 Sep 2006 17:48:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQstD-0006bb-F1; Fri, 22 Sep 2006 17:48:55 -0400
Received: from nit.isi.edu ([128.9.160.116])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1GQstC-0004EB-3h; Fri, 22 Sep 2006 17:48:55 -0400
Received: from nit.isi.edu (loopback [127.0.0.1])
	by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id k8MLmrgT004071; 
	Fri, 22 Sep 2006 14:48:53 -0700
Received: (from apache@localhost)
	by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id k8MLmrt1004070;
	Fri, 22 Sep 2006 14:48:53 -0700
Date: Fri, 22 Sep 2006 14:48:53 -0700
Message-Id: <200609222148.k8MLmrt1004070@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
X-Spam-Score: -14.8 (--------------)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: pce@ietf.org, rfc-editor@rfc-editor.org
Subject: [Pce] RFC 4657 on Path Computation Element (PCE) Communication
	Protocol Generic Requirements
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org


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

        
        RFC 4657

        Title:      Path Computation Element (PCE) Communication 
                    Protocol Generic Requirements 
        Author:     J. Ash, Ed.,
                    J.L. Le Roux, Ed.
        Status:     Informational
        Date:       September 2006
        Mailbox:    gash@att.com, 
                    jeanlouis.leroux@orange-ft.com
        Pages:      21
        Characters: 45284
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pce-comm-protocol-gen-reqs-07.txt

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

The PCE model is described in the "PCE Architecture" document and
facilitates path computation requests from Path Computation Clients
(PCCs) to Path Computation Elements (PCEs).  This document specifies
generic requirements for a communication protocol between PCCs and
PCEs, and also between PCEs where cooperation between PCEs is
desirable.  Subsequent documents will specify application-specific
requirements for the PCE communication protocol.  This memo provides information for the Internet community.

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


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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

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

Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...



_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



From pce-bounces@lists.ietf.org Fri Sep 22 19:32:09 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GQuUc-0001WY-8X; Fri, 22 Sep 2006 19:31:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GQuUb-0001WT-04
	for pce@ietf.org; Fri, 22 Sep 2006 19:31:37 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GQuUZ-00083i-Dw
	for pce@ietf.org; Fri, 22 Sep 2006 19:31:36 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158])
	by rtp-iport-2.cisco.com with ESMTP; 22 Sep 2006 19:31:35 -0400
X-IronPort-AV: i="4.09,205,1157342400"; 
	d="scan'208,217"; a="104058497:sNHT58485356"
Received: from rtp-core-1.cisco.com (rtp-core-1.cisco.com [64.102.124.12])
	by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8MNVZfe006099; Fri, 22 Sep 2006 19:31:35 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k8MNVYdM029750; 
	Fri, 22 Sep 2006 19:31:34 -0400 (EDT)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Sep 2006 19:31:34 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-202.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 22 Sep 2006 19:31:33 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
References: <200609222148.k8MLmrt1004070@nit.isi.edu>
Message-Id: <606C3E29-43FB-4CB0-84C2-C427D4EF43AA@cisco.com>
From: JP Vasseur <jvasseur@cisco.com>
Subject: Fwd: [Pce] RFC 4657 on Path Computation Element (PCE) Communication
	Protocol Generic Requirements
Date: Fri, 22 Sep 2006 19:31:31 -0400
To: pce@ietf.org
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 22 Sep 2006 23:31:33.0708 (UTC)
	FILETIME=[3D5980C0:01C6DE9F]
DKIM-Signature: a=rsa-sha1; q=dns; l=19891; t=1158967895; x=1159831895;
	c=relaxed/simple; s=rtpdkim1001;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Fwd=3A=20[Pce]=20RFC=204657=20on=20Path=20Computation=20Element=20(PCE)=
	20Communication=20Protocol=20Generic=20Requirements
	|To:pce@ietf.org;
	X=v=3Dcisco.com=3B=20h=3DOTjjVkg4QvSm9QlU6vp2LAhbeVE=3D;
	b=frbTRGkaHWtu/5v1L4TzNiG3ENN/ZGbw4aAR2IC6HcaDTCFvCCi4QrgE8W5ZxqJcwv3Ee+7l
	R+1XEMP217zkXi0S5TrnVp8x76wcTb+Y7nUlyAd9soP4jrRVyWW2wzYm;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass (
	29 extraneous bytes; sig from cisco.com verified; ); 
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 8eeb555810cda1f2c5989480370dc4ca
Cc: Ross Callon <rcallon@juniper.net>
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2031085341=="
Errors-To: pce-bounces@lists.ietf.org


--===============2031085341==
Content-Type: multipart/alternative; boundary=Apple-Mail-67-272064810


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

Thanks to the WG for this important Milestone and in particular to  
the authors who worked quite hard to address  a number of comments  
received on the documents. Next step on the PCECP requirements front,  
is now to complete the work on the other requirements IDs (inter- 
area, inter-AS, inter-layer).

Thanks.

JP and Adrian.

Begin forwarded message:

> From: rfc-editor@rfc-editor.org
> Date: September 22, 2006 5:48:53 PM EDT
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
> Cc: pce@ietf.org, rfc-editor@rfc-editor.org
> Subject: [Pce] RFC 4657 on Path Computation Element (PCE)  
> Communication Protocol Generic Requirements
>
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 4657
>
>         Title:      Path Computation Element (PCE) Communication
>                     Protocol Generic Requirements
>         Author:     J. Ash, Ed.,
>                     J.L. Le Roux, Ed.
>         Status:     Informational
>         Date:       September 2006
>         Mailbox:    gash@att.com,
>                     jeanlouis.leroux@orange-ft.com
>         Pages:      21
>         Characters: 45284
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-ietf-pce-comm-protocol-gen-reqs-07.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc4657.txt
>
> The PCE model is described in the "PCE Architecture" document and
> facilitates path computation requests from Path Computation Clients
> (PCCs) to Path Computation Elements (PCEs).  This document specifies
> generic requirements for a communication protocol between PCCs and
> PCEs, and also between PCEs where cooperation between PCEs is
> desirable.  Subsequent documents will specify application-specific
> requirements for the PCE communication protocol.  This memo  
> provides information for the Internet community.
>
> This document is a product of the Path Computation Element
> Working Group of the IETF.
>
>
> 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 list and the RFC-DIST list.
> Requests to be added to or deleted from the IETF distribution list
> should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
> added to or deleted from the RFC-DIST distribution list should
> be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
>
> Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
> an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
>
> help: ways_to_get_rfcs. For example:
>
>         To: rfc-info@RFC-EDITOR.ORG
>         Subject: getting rfcs
>
>         help: ways_to_get_rfcs
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.   
> Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
> Submissions for Requests for Comments should be sent to
> RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions  
> to RFC
> Authors, for further information.
>
>
> Joyce K. Reynolds and Sandy Ginoza
> USC/Information Sciences Institute
>
> ...
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/pce


--Apple-Mail-67-272064810
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=ISO-8859-1

<HTML><BODY style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; ">Thanks to the WG for this =
important Milestone and in particular to the authors who worked quite =
hard to address=A0 a number of comments received on the documents. Next =
step on the PCECP requirements front, is now to complete the work on the =
other requirements IDs (inter-area, inter-AS, inter-layer).<BR><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>Thanks.</DIV><DIV><BR =
class=3D"khtml-block-placeholder"></DIV><DIV>JP and =
Adrian.</DIV><DIV><BR><DIV>Begin forwarded message:</DIV><BR =
class=3D"Apple-interchange-newline"><BLOCKQUOTE type=3D"cite"><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><FONT face=3D"Helvetica" size=3D"5" color=3D"#000000" =
style=3D"font: 16.0px Helvetica; color: #000000"><B>From: =
</B></FONT><FONT face=3D"Helvetica" size=3D"5" style=3D"font: 16.0px =
Helvetica"><A =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</A></F=
ONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>Date: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica">September 22, 2006 5:48:53 PM =
EDT</FONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>To: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica"><A =
href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</A>, <A =
href=3D"mailto:rfc-dist@rfc-editor.org">rfc-dist@rfc-editor.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"5" =
color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>Cc: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica"><A =
href=3D"mailto:pce@ietf.org">pce@ietf.org</A>, <A =
href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</A></F=
ONT></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><FONT face=3D"Helvetica" =
size=3D"5" color=3D"#000000" style=3D"font: 16.0px Helvetica; color: =
#000000"><B>Subject: </B></FONT><FONT face=3D"Helvetica" size=3D"5" =
style=3D"font: 16.0px Helvetica"><B>[Pce] RFC 4657 on Path Computation =
Element (PCE) Communication Protocol Generic =
Requirements</B></FONT></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV> <DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">A new Request for Comments is now available in =
online RFC libraries.</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>RFC 4657</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>Title:<SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =
</SPAN>Path Computation Element (PCE) Communication<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
</SPAN>Protocol Generic Requirements<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>Author: <SPAN =
class=3D"Apple-converted-space">=A0 =A0 </SPAN>J. Ash, Ed.,</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 </SPAN>J.L. Le Roux, Ed.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>Status: <SPAN class=3D"Apple-converted-space">=A0 =A0 =
</SPAN>Informational</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>Date: <SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 </SPAN>September =
2006</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>Mailbox:<SPAN =
class=3D"Apple-converted-space">=A0 =A0 </SPAN><A =
href=3D"mailto:gash@att.com">gash@att.com</A>,<SPAN =
class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
</SPAN><A =
href=3D"mailto:jeanlouis.leroux@orange-ft.com">jeanlouis.leroux@orange-ft.=
com</A></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>Pages:<SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 </SPAN>21</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>Characters: 45284</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>Updates/Obsoletes/SeeAlso: <SPAN class=3D"Apple-converted-space">=A0=
 </SPAN>None</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>I-D Tag:<SPAN class=3D"Apple-converted-space">=A0 =A0 =
</SPAN>draft-ietf-pce-comm-protocol-gen-reqs-07.txt</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>URL:<SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN><A =
href=3D"http://www.rfc-editor.org/rfc/rfc4657.txt">http://www.rfc-editor.o=
rg/rfc/rfc4657.txt</A></DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; min-height: 14px; =
"><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">The PCE model is described in =
the "PCE Architecture" document and</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">facilitates =
path computation requests from Path Computation Clients</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">(PCCs) to Path Computation Elements (PCEs).<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>This document =
specifies</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">generic requirements for a =
communication protocol between PCCs and</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">PCEs, =
and also between PCEs where cooperation between PCEs is</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">desirable.<SPAN class=3D"Apple-converted-space">=A0 =
</SPAN>Subsequent documents will specify application-specific</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">requirements for the PCE communication =
protocol.<SPAN class=3D"Apple-converted-space">=A0 </SPAN>This memo =
provides information for the Internet community.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">This =
document is a product of the Path Computation Element</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Working Group of the IETF.</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">INFORMATIONAL: This memo provides information for the Internet =
community.<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">It does not specify an Internet standard of any =
kind. Distribution</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">of this memo is =
unlimited.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">This announcement is sent to the IETF list and the =
RFC-DIST list.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">Requests to be added to or =
deleted from the IETF distribution list</DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">should =
be sent to <A =
href=3D"mailto:IETF-REQUEST@IETF.ORG">IETF-REQUEST@IETF.ORG</A>.<SPAN =
class=3D"Apple-converted-space">=A0 </SPAN>Requests to be</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">added to or deleted from the RFC-DIST distribution =
list should</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">be sent to <A =
href=3D"mailto:RFC-DIST-REQUEST@RFC-EDITOR.ORG">RFC-DIST-REQUEST@RFC-EDITO=
R.ORG</A>.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Details on obtaining RFCs via FTP or EMAIL may be =
obtained by sending</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">an EMAIL message to <A =
href=3D"mailto:rfc-info@RFC-EDITOR.ORG">rfc-info@RFC-EDITOR.ORG</A> with =
the message body<SPAN class=3D"Apple-converted-space">=A0</SPAN></DIV><DIV=
 style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">help: =
ways_to_get_rfcs. For example:</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>To: <A =
href=3D"mailto:rfc-info@RFC-EDITOR.ORG">rfc-info@RFC-EDITOR.ORG</A></DIV><=
DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><SPAN class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 =
</SPAN>Subject: getting rfcs</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; "><SPAN =
class=3D"Apple-converted-space">=A0 =A0 =A0 =A0 </SPAN>help: =
ways_to_get_rfcs</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Requests for special distribution should be =
addressed to either the</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">author of the =
RFC in question, or to <A =
href=3D"mailto:RFC-Manager@RFC-EDITOR.ORG">RFC-Manager@RFC-EDITOR.ORG</A>.=
<SPAN class=3D"Apple-converted-space">=A0 </SPAN>Unless</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">specifically noted otherwise on the RFC itself, all =
RFCs are for</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">unlimited =
distribution.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Submissions for Requests for Comments should be sent =
to</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: =
0px; margin-left: 0px; "><A =
href=3D"mailto:RFC-EDITOR@RFC-EDITOR.ORG">RFC-EDITOR@RFC-EDITOR.ORG</A>.<S=
PAN class=3D"Apple-converted-space">=A0 </SPAN>Please consult RFC 2223, =
Instructions to RFC</DIV><DIV style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px; ">Authors, for further =
information.</DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">Joyce K. =
Reynolds and Sandy Ginoza</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
">USC/Information Sciences Institute</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; ">...</DIV><DIV style=3D"margin-top:=
 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; =
min-height: 14px; "><BR></DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; min-height: =
14px; "><BR></DIV><DIV style=3D"margin-top: 0px; margin-right: 0px; =
margin-bottom: 0px; margin-left: 0px; min-height: 14px; "><BR></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; =
">_______________________________________________</DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; ">Pce mailing list</DIV><DIV style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A =
href=3D"mailto:Pce@lists.ietf.org">Pce@lists.ietf.org</A></DIV><DIV =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px; "><A =
href=3D"https://www1.ietf.org/mailman/listinfo/pce">https://www1.ietf.org/=
mailman/listinfo/pce</A></DIV> </BLOCKQUOTE></DIV><BR></BODY></HTML>=

--Apple-Mail-67-272064810--


--===============2031085341==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce

--===============2031085341==--




From pce-bounces@lists.ietf.org Wed Sep 27 09:32:26 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1GSZW7-0003hy-Sj; Wed, 27 Sep 2006 09:32:03 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1GSZW6-0003hs-DM
	for pce@ietf.org; Wed, 27 Sep 2006 09:32:02 -0400
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GSZW5-0000yD-4G
	for pce@ietf.org; Wed, 27 Sep 2006 09:32:02 -0400
Received: from sj-dkim-5.cisco.com ([171.68.10.79])
	by sj-iport-5.cisco.com with ESMTP; 27 Sep 2006 06:32:01 -0700
X-IronPort-AV: i="4.09,224,1157353200"; 
	d="scan'208"; a="325837224:sNHT46758784"
Received: from sj-core-4.cisco.com (sj-core-4.cisco.com [171.68.223.138])
	by sj-dkim-5.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id
	k8RDW00u009070 for <pce@ietf.org>; Wed, 27 Sep 2006 06:32:00 -0700
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com
	[64.102.31.12])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id k8RDVxid017148
	for <pce@ietf.org>; Wed, 27 Sep 2006 06:32:00 -0700 (PDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by
	xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Sep 2006 09:31:59 -0400
Received: from [10.86.104.178] ([10.86.104.178]) by xfe-rtp-201.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 27 Sep 2006 09:31:59 -0400
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <9907FEA5-33C6-4289-B053-6BE3E8E2F7E1@cisco.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: pce@ietf.org
From: JP Vasseur <jvasseur@cisco.com>
Date: Wed, 27 Sep 2006 09:31:57 -0400
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 27 Sep 2006 13:31:59.0154 (UTC)
	FILETIME=[4EE8F120:01C6E239]
DKIM-Signature: a=rsa-sha1; q=dns; l=126; t=1159363920; x=1160227920;
	c=relaxed/simple; s=sjdkim5002;
	h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
	d=cisco.com; i=jvasseur@cisco.com;
	z=From:JP=20Vasseur=20<jvasseur@cisco.com>
	|Subject:Slot=20request=20for=20IETF-67=20working=20group=20meeting=20?;
	X=v=3Dcisco.com=3B=20h=3DHE/aRP+yOAVcJTt9Vb3wS52YjB4=3D;
	b=H6+6jaA7EhNxhgx1S31jhor5ee5OXPNx3y1Kcb7457qcAZe82lWL4rP0nAsC0FXB3ww8a1z0
	VYw81SmFxySbPJj2mOOdJ3W9FwzlCfuNcpkaXGtWvHQhi4tObAkYQqzZ;
Authentication-Results: sj-dkim-5.cisco.com; header.From=jvasseur@cisco.com;
	dkim=pass ( sig from cisco.com verified; ); 
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Cc: 
Subject: [Pce] Slot request for IETF-67 working group meeting ?
X-BeenThere: pce@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Path Computation Element  <pce.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pce>
List-Post: <mailto:pce@lists.ietf.org>
List-Help: <mailto:pce-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pce>,
	<mailto:pce-request@lists.ietf.org?subject=subscribe>
Errors-To: pce-bounces@lists.ietf.org

Hi,

Let us know If you'd like a slot for the next WG meeting (ID,  
duration, "presenter").

Thanks.

JP and Adrian.

_______________________________________________
Pce mailing list
Pce@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/pce



