Internet-Drafts | 1 Mar 2010 18:15
Picon
Favicon

I-D Action:draft-ietf-pce-wson-routing-wavelength-01.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           : PCEP Requirements for WSON Routing and Wavelength Assignment
	Author(s)       : Y. Lee, et al.
	Filename        : draft-ietf-pce-wson-routing-wavelength-01.txt
	Pages           : 12
	Date            : 2010-03-01

This memo provides application-specific requirements for the Path
Computation Element communication Protocol (PCEP) for the support of
Wavelength Switched Optical Networks (WSON). Lightpath provisioning
in WSONs requires a routing and wavelength assignment (RWA) process.
From a path computation perspective, wavelength assignment is the
process of determining which wavelength can be used on each hop of a
path and forms an additional routing constraint to optical light path
computation. Requirements for Optical impairments will be addressed
in a separate document.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-wson-routing-wavelength-01.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.
(Continue reading)

julien.meuric | 1 Mar 2010 19:03

FW: Internet Draft Initial Version (-00) Cut-Off Today

Beware...

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

This is a reminder that the Internet Draft Initial Version (-00) cut-off
is today, Monday, March 1, 2010. 

All Initial Version (-00) submissions are due by 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

Thank you!
_______________________________________________
IETF-Announce mailing list
IETF-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

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

(Continue reading)

JP Vasseur | 1 Mar 2010 20:05
Picon
Favicon

PCE WG Agenda

is now confirmed. Please send us an email if you would like to get a slot:

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


<div>is now confirmed. Please send us an email if you would like to get a slot:<div><br></div>
<div><span class="Apple-style-span"><table>
<tr><td colspan="4"><h4>THURSDAY, March 25, 2010</h4></td></tr>
<tr><td colspan="4"></td></tr>
<tr><td colspan="4">1300-1500 Afternoon Session I</td></tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=redondo">Redondo</a></td>
<td>INT</td>
<td><a href="http://www.ietf.org/dyn/wg/charter/netext-charter.html">netext</a></td>
<td>Network-Based Mobility Extensions WG</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=manhattan">Manhattan</a></td>
<td>IRTF</td>
<td>samrg</td>
<td>Scalable Adaptive Multicast Research Group</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=california-b">California B</a></td>
<td>OPS</td>
<td><a href="http://www.ietf.org/dyn/wg/charter/grow-charter.html">grow</a></td>
<td>Global Routing Operations WG</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=california-a">California A</a></td>
<td>RAI</td>
<td><a href="http://www.ietf.org/dyn/wg/charter/p2psip-charter.html">p2psip</a></td>
<td>Peer-to-Peer Session Initiation Protocol WG</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=huntington">Huntington</a></td>
<td>RTG</td>
<td><a href="http://www.ietf.org/dyn/wg/charter/pce-charter.html">pce</a></td>
<td>Path Computation Element WG</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=palos-verdes">Palos Verdes</a></td>
<td>RTG</td>
<td><a href="http://www.ietf.org/dyn/wg/charter/rtgwg-charter.html">rtgwg</a></td>
<td>Routing Area Working Group WG</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=california-d">California D</a></td>
<td>SEC</td>
<td>saag</td>
<td>Security Area Open Meeting</td>
</tr>
<tr>
<td><a href="http://tools.ietf.org/agenda/77/venue/?room=california-c">California C</a></td>
<td>TSV</td>
<td><a href="http://www.ietf.org/dyn/wg/charter/behave-charter.html">behave</a></td>
<td>Behavior Engineering for Hindrance Avoidance WG</td>
</tr>
<tr><td colspan="4"><br></td></tr>
</table>
<br></span></div>
</div>
Internet-Drafts | 2 Mar 2010 00:00
Picon
Favicon

I-D Action:draft-ietf-pce-vendor-constraints-01.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           : Conveying Vendor-Specific Constraints in the Path Computation Element Protocol
	Author(s)       : A. Farrel, G. Bernstein
	Filename        : draft-ietf-pce-vendor-constraints-01.txt
	Pages           : 9
	Date            : 2010-03-01

The Path Computation Element Protocol (PCEP) is used to convey path
computation requests and responses between Path Computation Clients
(PCCs) and Path Computation Elements (PCEs), and also between
cooperating PCEs. In PCEP the path computation requests carry details
of the constraints and objective functions that the PCC wishes the
PCE to apply in its computation.

The mechanisms defined for indicating objective functions include
the capability to convey vendor-specific objective functions. This
document defines a facility to carry vendor-specific constraints in
PCEP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-vendor-constraints-01.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.
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           : Conveying Vendor-Specific Constraints in the Path Computation Element Protocol
	Author(s)       : A. Farrel, G. Bernstein
	Filename        : draft-ietf-pce-vendor-constraints-01.txt
	Pages           : 9
	Date            : 2010-03-01

The Path Computation Element Protocol (PCEP) is used to convey path
computation requests and responses between Path Computation Clients
(PCCs) and Path Computation Elements (PCEs), and also between
cooperating PCEs. In PCEP the path computation requests carry details
of the constraints and objective functions that the PCC wishes the
PCE to apply in its computation.

The mechanisms defined for indicating objective functions include
the capability to convey vendor-specific objective functions. This
document defines a facility to carry vendor-specific constraints in
PCEP.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-vendor-constraints-01.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.
JP Vasseur | 5 Mar 2010 11:57
Picon
Favicon

Please discuss new ID on the mailing list

Dear all,

We have a number of new -00 ID posted, and would like to encourage you  
to start polling the WG on the potential interest rather than just  
posting and request a time slot at the next IETF meeting.

Thanks.

JP and Julien.
POUYLLAU, HELIA (HELIA | 5 Mar 2010 13:59
Favicon

New I-D : draft-pouyllau-pce-enhanced-errors-00.txt

Dear all,
 
I was waiting for the automated announcement but it did not come. So here is a new draft we submitted that propose extending PCEP so that general behaviours associated to specific error or notification types can be supported:
 
 
        Title           : Extension to the Path Computation Element Communication Protocol for Enhanced Errors and Notifications
        Author(s)       : H. Pouyllau, R. Theillaud, J. Meuric
        Filename        : draft-pouyllau-pce-enhanced-errors-00.txt
        Pages           : 13
        Date            : 2010-03-01
 
        Abstract
                This document defines new error and notification types and codes for
                 the PCE Communication Protocol (PCEP) [RFC5440]. It identifies the
                 possible PCEP behaviors in case of error or notification. Thus, this
                 draft extends error and notification types in order to associate
                 predefined PCEP behaviors.
 
 
 
 
A -01 version will be submitted Monday to correct some typos and formatting issues.
 
Comments are welcomed
 
Regards
Hélia
 
 
--------------------------------------------------
Hélia Pouyllau, Ph.D.
Alcatel-Lucent Bell Labs
Networking & Networks/Semantic and Autonomous Technologies
Centre de Villarceaux
91620 Nozay - France
Phone: +33 130 776 311
 
 
 
<div>

<div>Dear all,</div>
<div>&nbsp;</div>
<div>I was waiting for the automated announcement but it did not come. So here is a new draft we submitted that propose extending PCEP so that general behaviours associated to specific error or notification types can be supported:</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Extension to the Path Computation Element Communication Protocol for Enhanced Errors and Notifications</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : H. Pouyllau, R. Theillaud, J. Meuric</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : draft-pouyllau-pce-enhanced-errors-00.txt</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 13</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2010-03-01</div>
<div>&nbsp;</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Abstract </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This document defines new error and notification types and codes for</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the PCE Communication Protocol (PCEP) [RFC5440]. It identifies the</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; possible PCEP behaviors in case of error or notification. Thus, this</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; draft extends error and notification types in order to associate</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; predefined PCEP behaviors.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>URL&nbsp;: <a href="http://www.ietf.org/id/draft-pouyllau-pce-enhanced-errors-00.txt">http://www.ietf.org/id/draft-pouyllau-pce-enhanced-errors-00.txt</a>
</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>A -01 version will be submitted Monday to correct some typos and formatting issues.</div>
<div>&nbsp;</div>
<div>Comments are welcomed </div>
<div>&nbsp;</div>
<div>Regards</div>
<div>H&eacute;lia</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<a name="_MailAutoSig"></a>
<div>--------------------------------------------------</div>
<div>H&eacute;lia Pouyllau, Ph.D.</div>
<div>Alcatel-Lucent Bell Labs</div>
<div>Networking &amp; Networks/Semantic and Autonomous Technologies</div>
<div>Centre de Villarceaux</div>
<div>91620 Nozay - France</div>
<div>Phone: +33 130 776 311 </div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>

</div>
Daniel King | 7 Mar 2010 15:45
Picon

Re: I-D Action:draft-king-pce-inter-area-as-applicability-00.txt

Resend. Strangely the original email never made it to the list. 

-----Original Message-----
From: Daniel King [mailto:daniel <at> olddog.co.uk] 
Sent: 06 March 2010 14:15
To: pce <at> ietf.org
Subject: I-D Action:draft-king-pce-inter-area-as-applicability-00.txt

Howdy all, 

I recently submitted a new draft:

Applicability of the Path Computation Element to Inter-Area and Inter-AS
MPLS and GMPLS Traffic Engineering:

http://www.ietf.org/internet-drafts/draft-king-pce-inter-area-as-applicabi
lity-00.txt

The document examines the applicability of the PCE architecture, protocols,
and protocol extensions for computing multi-area and multi-AS paths in MPLS
and GMPLS networks. I plan to present the work in Anaheim (IETF77). As
always I would appreciate any comments or feedback via the list. 

Thanks,
Dan

Meral Shirazipour | 7 Mar 2010 16:50
Picon
Picon
Favicon

Re: I-D Action:draft-king-pce-inter-area-as-applicability-00.txt

Hi Daniel,
  Here are 1-2 quick comments on the draft:

Section 5:
I would add a section 5.5 for Loop Avoidance in the inter-domain case.
Would it be just to say that we count on the peering agreements or the 
H-PCE for loop avoidance.(Then does that mean we don?t need a mechanism 
to detect loops specifically for inter-AS scenarios? What would be the 
definition of a loop here?)

5.2 Inter-AS Bandwidth Guarantees
I think here and in general it would be great to mention some PCE 
inter-layer work. One way to guarantee BW would then be to provision a 
new lower layer connection. (Nested LSP...).

Regards,
Meral

Daniel King <daniel <at> olddog.co.uk> a écrit :

> Resend. Strangely the original email never made it to the list.
>
> -----Original Message-----
> From: Daniel King [mailto:daniel <at> olddog.co.uk]
> Sent: 06 March 2010 14:15
> To: pce <at> ietf.org
> Subject: I-D Action:draft-king-pce-inter-area-as-applicability-00.txt
>
> Howdy all,
>
> I recently submitted a new draft:
>
> Applicability of the Path Computation Element to Inter-Area and Inter-AS
> MPLS and GMPLS Traffic Engineering:
>
> http://www.ietf.org/internet-drafts/draft-king-pce-inter-area-as-applicabi
> lity-00.txt
>
> The document examines the applicability of the PCE architecture, protocols,
> and protocol extensions for computing multi-area and multi-AS paths in MPLS
> and GMPLS networks. I plan to present the work in Anaheim (IETF77). As
> always I would appreciate any comments or feedback via the list.
>
> Thanks,
> Dan
>
>
>
>
>
> _______________________________________________
> Pce mailing list
> Pce <at> ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>

Fatai Zhang | 8 Mar 2010 10:48
Favicon

discussion on draft-zhang-pce-pcep-extensions-for-gmpls

Hi PCEers,
 
To respond to the call from JP, I trigger this discussion and hope you can review this draft and give your comments or suggestions.
 
Note that this draft (draft-zhang-pce-pcep-extensions-for-gmpls) is used to replace another draft (draft-zhang-pce-pcep-extensions-for-sdh), which was discussed in the mailing list about two months ago.
 
 
 
 

Thanks
 
Fatai
 
Huawei Technologies Co., LTD.
Huawei Base, Bantian, Longgang,
Shenzhen 518129 P.R.China
Tel: +86-755-28972912
Fax: +86-755-28972935
 

 
----- Original Message -----
From: "JP Vasseur" <jvasseur <at> cisco.com>
Sent: Friday, March 05, 2010 6:57 PM
Subject: [Pce] Please discuss new ID on the mailing list

> Dear all,
>
> We have a number of new -00 ID posted, and would like to encourage you 
> to start polling the WG on the potential interest rather than just 
> posting and request a time slot at the next IETF meeting.
>
> Thanks.
>
> JP and Julien.
> _______________________________________________
> Pce mailing list
> Pce <at> ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
<div>
<div>Hi PCEers,</div>
<div>&nbsp;</div>
<div>To&nbsp;respond to the call from JP,&nbsp;I trigger this 
discussion and&nbsp;hope you can review this draft and give your comments or 
suggestions.</div>
<div>&nbsp;</div>
<div>Note that this draft (<a href="http://tools.ietf.org/id/draft-zhang-pce-pcep-extensions-for-gmpls-00.txt">draft-zhang-pce-pcep-extensions-for-gmpls</a>) is&nbsp;used to replace another draft (<a href="http://tools.ietf.org/id/draft-zhang-pce-pcep-extensions-for-sdh-00.txt">draft-zhang-pce-pcep-extensions-for-sdh</a>), 
which was discussed in the mailing list about two months ago.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>
<br>Thanks<br>&nbsp;<br>Fatai<br>&nbsp;<br>Huawei Technologies Co., 
LTD.<br>Huawei Base, Bantian, Longgang,<br>Shenzhen 518129 P.R.China<br>Tel: 
+86-755-28972912<br>Fax: +86-755-28972935</div>
<div>&nbsp;</div>
<div>
<br>&nbsp;</div>
<div>----- Original Message ----- 
<div>From: "JP Vasseur" &lt;<a href="mailto:jvasseur <at> cisco.com">jvasseur <at> cisco.com</a>&gt;</div>
<div>To: &lt;<a href="mailto:pce <at> ietf.org">pce <at> ietf.org</a>&gt;</div>
<div>Sent: Friday, March 05, 2010 6:57 PM</div>
<div>Subject: [Pce] Please discuss new ID on the mailing 
list</div>
</div>
<div><br></div>&gt; Dear all,<br>&gt; 
<br>&gt; We have a number of new -00 ID posted, and would like to encourage 
you&nbsp; <br>&gt; to start polling the WG on the potential interest rather than 
just&nbsp; <br>&gt; posting and request a time slot at the next IETF 
meeting.<br>&gt; <br>&gt; Thanks.<br>&gt; <br>&gt; JP and Julien.<br>&gt; 
_______________________________________________<br>&gt; Pce mailing list<br>&gt; 
<a href="mailto:Pce <at> ietf.org">Pce <at> ietf.org</a><br>&gt; <a href="https://www.ietf.org/mailman/listinfo/pce">https://www.ietf.org/mailman/listinfo/pce</a><br>&gt;</div>
Internet-Drafts | 8 Mar 2010 16:15
Picon
Favicon

I-D Action:draft-ietf-pce-pcep-mib-01.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           : PCE communication protocol(PCEP) Management Information Base
	Author(s)       : K. Koushik, et al.
	Filename        : draft-ietf-pce-pcep-mib-01.txt
	Pages           : 23
	Date            : 2010-03-08

This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the
Internet community.  In particular, it describes managed objects
for modeling of Path Computation Element communication
Protocol (PCEP) for communications between a Path Computation Client
(PCC) and a Path Computation Element (PCE), or between two PCEs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pce-pcep-mib-01.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.
Attachment (draft-ietf-pce-pcep-mib-01.txt): message/external-body, 70 bytes
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           : PCE communication protocol(PCEP) Management Information Base
	Author(s)       : K. Koushik, et al.
	Filename        : draft-ietf-pce-pcep-mib-01.txt
	Pages           : 23
	Date            : 2010-03-08

This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the
Internet community.  In particular, it describes managed objects
for modeling of Path Computation Element communication
Protocol (PCEP) for communications between a Path Computation Client
(PCC) and a Path Computation Element (PCE), or between two PCEs.

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

Gmane