Re: PCE BOF - Thursday August 5, 13:00 to 15:00

--=====================_94041604==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi,

At 08:53 AM 8/5/2004 +0800, lidefeng wrote:
>Hi,
>
>I think it is very necessary to do this work in IETF, Service Providers in 
>China also expressed such requirements during the technical exchanges.

Thanks for the feed-back, feel free to join the BOF.

>
>I have delved into PCE.ppt in the link, however, I can't find the 
>following drafts, If anyone can share with me? Could you please send me 
>these drafts in e-mail, Thanks!
>
>draft-mescal-pce-interas-00.txt
>draft-mescal-pcp-interas-00.txt
>draft-mescal-pceid-00.txt

Those drafts falls in the "Under Work" category ... and have not been 
published yet. I'll say a few words about them this afternoon, the goal was 
just to highlight on-going work related to this area.

JP.

>
>Best Regards
>Defeng Li
>----- Original Message -----
>From: <mailto:[email protected]>Jean Philippe Vasseur
>To: <mailto:[email protected]>[email protected] ; 
><mailto:[email protected]>[email protected] ; <mailto:[email protected]>TEWG ; 
><mailto:[email protected]>[email protected]
>Cc: <mailto:[email protected]>[email protected] ; 
><mailto:[email protected]>[email protected] ; <mailto:[email protected]>Bill 
>Fenner
>Sent: Sunday, August 01, 2004 1:07 PM
>Subject: PCE BOF - Thursday August 5, 13:00 to 15:00
>
>Hi,
>
>Just to let you know that the set of slides for the PCE BOF will be 
>available next Monday morning (http://www.olddog.co.uk/60/pce.ppt)
>
>Cheers,
>
>JP and Adrian.
>
>Path Computation Element BOF (PCE BOF)
>60th IETF, San Diego, August 2004
>
>Routing Area Ads: Alex Zinin (<mailto:[email protected]>[email protected]),
>Bill Fenner (<mailto:[email protected]>[email protected])
>
>BOF Chairs: JP Vasseur (<mailto:[email protected]>[email protected]), 
>Adrian Farrel (<mailto:[email protected]>[email protected])
>
>Description:
>In certain MPLS TE networks it may be beneficial or desirable to have path
>computation performed by a distinct node (termed the Path Computation
>Element PCE) that is not the LSR that needs to know the path. This BOF
>examines the scope of such function, what extensions to existing protocols
>might required, what additional protocols may need to be developed, and
>whether there is cuase and support for this work within the IETF.
>
>Proposed WG Charter
>
>Organizational Overview
>The PCE working group coordinates the work within the IETF of defining the
>operation of path computation elements within the Internet. Path
>computation elements are responsible for computing paths through IP
>networks for uses such as traffic engineering so that a prime consumer of
>such paths might be an MPLS-TE LSR. Areas of responsibility will include
>the collection of attributes relevant to the computation of paths, the
>discovery by LSRs of available path computation elements, the communication
>with LSRs for the request of path computation, the collaboration between
>path computation elements within the network, and analysis of path
>computation algorithms with a view to ensuring consistency between computed
>paths. The working group will work closely with many working groups in the
>Routing Area including the OSPF, IS-IS, IDR, MPLS and CCAMP working groups.
>
>Working Group Scope
>
>The PCE working group scope includes:
>- Definition of Generalized Traffic Engineered LSP paths computation
>techniques involving Path Computation Element(s). This includes the intra
>IGP area, inter IGP area, inter-AS and inter-provider TE LSPs path
>computation for Point-to-Point, Point-to-Multipoint and
>Multipoint-to-Multipoint TE LSPs.
>- Definition of protocol-independent metrics and constraints defining path
>quality measurement criteria, algorithm complexity and scalability criteria
>related to path computation techniques.
>- Definition of requirements for communication between LSRs and PCEs
>including routing extensions in support of PCE discovery techniques within
>an IGP area and across multiple IGP areas, ASes and Provider networks, and
>including the development of new protocols or protocol extensions for
>requesting path computation and supplying responses. Any protocol
>extensions will developed in conjunction with the working groups in charge
>of the specific protocols.
>- Specification of routing (OSPF, ISIS, BGP) and signalling extensions
>(RSVP-TE) required by PCE-based path computation techniques. The extensions
>will developed in conjunction with the working groups in charge of the
>specific protocols.
>- Specification of requirements and protocol extensions related to the
>policy, security and confidentiality aspects of PCE-based path computation
>techniques involving PCEs of multiple Providers.
>- Definition of MIBs, management procedures related to the protocol
>extensions defined by the WG
>In doing this work, the WG will closely work with at least the following
>other WGs: CCAMP, MPLS, ISIS, OSPF, IDR. The WG will also cooperate with
>the ITU-T and OIF.
>
>Goals and Milestones
>Dates for milestones to be decided later.
>- Post strawman WG goals and charter.
>- Submit WG document defining the framework and applicability of the
>PCE model.
>- Select a single candidate protocol from communication between LSRs
>and PCEs.
>- Submit document(s) that define various path computation models
>- Submit an analysis document examining the requirements for coherent
>computation techniques and the implication of cooperation between
>PCEs.
>- Submit a document defining the protocol for communication between
>LSRs and PCEs.
>- Submit document(s) defining extensions to routing and signalling
>protocols necessary to support the use of a PCE model within MPLS
>networks.
>- Submit a document defining MIB modules for modeling and management
>of PCE systems.

--=====================_94041604==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hi,<br>
<br>
At 08:53 AM 8/5/2004 +0800, lidefeng wrote:<br>
<blockquote type=cite cite><font face="arial" size=2>Hi,</font><br>
&nbsp;<br>
<font face="arial" size=2>I think it is very necessary to do this work in
IETF, Service Providers in China also expressed such requirements during
the technical exchanges.</font><br>
</blockquote><br>
Thanks for the feed-back, feel free to join the BOF.<br>
<br>
<blockquote type=cite cite>&nbsp;<br>
<font face="arial" size=2>I have delved into PCE.ppt in the link,
however, I can't find the following drafts, If anyone can share with me?
Could you please send me these drafts in e-mail, Thanks!</font><br>
&nbsp;<br>
<font face="arial" size=2>draft-mescal-pce-interas-00.txt</font><br>
<font face="arial" size=2>draft-mescal-pcp-interas-00.txt</font><br>
<font face="arial" size=2>draft-mescal-pceid-00.txt</font><br>
</blockquote><br>
Those drafts falls in the &quot;Under Work&quot; category ... and have
not been published yet. I'll say a few words about them this afternoon,
the goal was just to highlight on-going work related to this area. <br>
<br>
JP.<br>
<br>
<blockquote type=cite cite>&nbsp;<br>
<font face="arial" size=2>Best Regards</font><br>
<font face="arial" size=2>Defeng Li</font> 
<dl>
<dd>----- Original Message ----- 
<dd>From:</b> <a href="mailto:[email protected]">Jean Philippe
Vasseur</a> 
<dd>To:</b> <a href="mailto:[email protected]">[email protected]</a> ;
<a href="mailto:[email protected]">[email protected]</a> ;
<a href="mailto:[email protected]">TEWG</a> ;
<a href="mailto:[email protected]">[email protected]</a> 
<dd>Cc:</b> <a href="mailto:[email protected]">[email protected]</a>
; <a href="mailto:[email protected]">[email protected]</a> ; <a href="mailto:[email protected]">Bill Fenner</a> 
<dd>Sent:</b> Sunday, August 01, 2004 1:07 PM
<dd>Subject:</b> PCE BOF - Thursday August 5, 13:00 to 15:00<br>
<br>

<dd>Hi,<br>
<br>

<dd>Just to let you know that the set of slides for the PCE BOF will be available next Monday morning (<a href="http://www.olddog.co.uk/60/pce.ppt" eudora="autourl">http://www.olddog.co.uk/60/pce.ppt</a>)<br>
<br>
</b>
<dd>Cheers,<br>
<br>

<dd>JP and Adrian.<br>
<br>

<dd>Path Computation Element BOF (PCE BOF) 
<dd>60th IETF, San Diego, August 2004<br>
<br>
</b>
<dd>Routing Area Ads: Alex Zinin (<a href="mailto:[email protected]">[email protected]</a>), 
<dd>Bill Fenner (<a href="mailto:[email protected]">[email protected]</a>)<br>
<br>

<dd>BOF Chairs: JP Vasseur (<a href="mailto:[email protected]">[email protected]</a>), Adrian Farrel (<a href="mailto:[email protected]">[email protected]</a>)<br>
<br>

<dd>Description: 
<dd>In certain MPLS TE networks it may be beneficial or desirable to have path 
<dd>computation performed by a distinct node (termed the Path Computation 
<dd>Element PCE) that is not the LSR that needs to know the path. This BOF 
<dd>examines the scope of such function, what extensions to existing protocols 
<dd>might required, what additional protocols may need to be developed, and 
<dd>whether there is cuase and support for this work within the IETF. <br>
<br>

<dd>Proposed WG Charter <br>
<br>

<dd>Organizational Overview 
<dd>The PCE working group coordinates the work within the IETF of defining the 
<dd>operation of path computation elements within the Internet. Path 
<dd>computation elements are responsible for computing paths through IP 
<dd>networks for uses such as traffic engineering so that a prime consumer of 
<dd>such paths might be an MPLS-TE LSR. Areas of responsibility will include 
<dd>the collection of attributes relevant to the computation of paths, the 
<dd>discovery by LSRs of available path computation elements, the communication 
<dd>with LSRs for the request of path computation, the collaboration between 
<dd>path computation elements within the network, and analysis of path 
<dd>computation algorithms with a view to ensuring consistency between computed 
<dd>paths. The working group will work closely with many working groups in the 
<dd>Routing Area including the OSPF, IS-IS, IDR, MPLS and CCAMP working groups. <br>
<br>

<dd>Working Group Scope <br>
<br>

<dd>The PCE working group scope includes: 
<dd>- Definition of Generalized Traffic Engineered LSP paths computation 
<dd>techniques involving Path Computation Element(s). This includes the intra 
<dd>IGP area, inter IGP area, inter-AS and inter-provider TE LSPs path 
<dd>computation for Point-to-Point, Point-to-Multipoint and 
<dd>Multipoint-to-Multipoint TE LSPs. 
<dd>- Definition of protocol-independent metrics and constraints defining path 
<dd>quality measurement criteria, algorithm complexity and scalability criteria 
<dd>related to path computation techniques. 
<dd>- Definition of requirements for communication between LSRs and PCEs 
<dd>including routing extensions in support of PCE discovery techniques within 
<dd>an IGP area and across multiple IGP areas, ASes and Provider networks, and 
<dd>including the development of new protocols or protocol extensions for 
<dd>requesting path computation and supplying responses. Any protocol 
<dd>extensions will developed in conjunction with the working groups in charge 
<dd>of the specific protocols. 
<dd>- Specification of routing (OSPF, ISIS, BGP) and signalling extensions 
<dd>(RSVP-TE) required by PCE-based path computation techniques. The extensions 
<dd>will developed in conjunction with the working groups in charge of the 
<dd>specific protocols. 
<dd>- Specification of requirements and protocol extensions related to the 
<dd>policy, security and confidentiality aspects of PCE-based path computation 
<dd>techniques involving PCEs of multiple Providers. 
<dd>- Definition of MIBs, management procedures related to the protocol 
<dd>extensions defined by the WG 
<dd>In doing this work, the WG will closely work with at least the following 
<dd>other WGs: CCAMP, MPLS, ISIS, OSPF, IDR. The WG will also cooperate with 
<dd>the ITU-T and OIF. <br>
<br>

<dd>Goals and Milestones 
<dd>Dates for milestones to be decided later. 
<dd>- Post strawman WG goals and charter. 
<dd>- Submit WG document defining the framework and applicability of the 
<dd>PCE model. 
<dd>- Select a single candidate protocol from communication between LSRs 
<dd>and PCEs. 
<dd>- Submit document(s) that define various path computation models 
<dd>- Submit an analysis document examining the requirements for coherent 
<dd>computation techniques and the implication of cooperation between 
<dd>PCEs. 
<dd>- Submit a document defining the protocol for communication between 
<dd>LSRs and PCEs. 
<dd>- Submit document(s) defining extensions to routing and signalling 
<dd>protocols necessary to support the use of a PCE model within MPLS 
<dd>networks. 
<dd>- Submit a document defining MIB modules for modeling and management 
<dd>of PCE systems.
</dl></blockquote></html>

--=====================_94041604==_.ALT--