Re: PCE BOF - Thursday August 5, 13:00 to 15:00
lidefeng <[email protected]> Thu, 05 Aug 2004 08:53:27 +0800
| Newsgroups | gmane.ietf.ccamp,gmane.ietf.tewg |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --Boundary_(ID_gb/wjlgfADm6KyH/g6t6xw) Content-type: text/plain; charset=gb2312 Content-transfer-encoding: 7BIT 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. 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 Best Regards Defeng Li ----- Original Message ----- From: Jean Philippe Vasseur To: [email protected] ; [email protected] ; TEWG ; [email protected] Cc: [email protected] ; [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 ([email protected]), Bill Fenner ([email protected]) BOF Chairs: JP Vasseur ([email protected]), Adrian Farrel ([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. --Boundary_(ID_gb/wjlgfADm6KyH/g6t6xw) Content-type: text/html; charset=gb2312 Content-transfer-encoding: 7BIT <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=gb2312"> <META content="MSHTML 6.00.2800.1264" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>Hi,</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><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></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><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></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>draft-mescal-pce-interas-00.txt</FONT></DIV> <DIV><FONT face=Arial size=2>draft-mescal-pcp-interas-00.txt</FONT></DIV> <DIV><FONT face=Arial size=2>draft-mescal-pceid-00.txt</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>Best Regards</FONT></DIV> <DIV><FONT face=Arial size=2>Defeng Li</FONT> </DIV> <BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original Message ----- </DIV> <DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B> <A [email protected] href="mailto:[email protected]">Jean Philippe Vasseur</A> </DIV> <DIV style="FONT: 10pt arial"><B>To:</B> <A [email protected] href="mailto:[email protected]">[email protected]</A> ; <A [email protected] href="mailto:[email protected]">[email protected]</A> ; <A [email protected] href="mailto:[email protected]">TEWG</A> ; <A [email protected] href="mailto:[email protected]">[email protected]</A> </DIV> <DIV style="FONT: 10pt arial"><B>Cc:</B> <A [email protected] href="mailto:[email protected]">[email protected]</A> ; <A [email protected] href="mailto:[email protected]">[email protected]</A> ; <A [email protected] href="mailto:[email protected]">Bill Fenner</A> </DIV> <DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, August 01, 2004 1:07 PM</DIV> <DIV style="FONT: 10pt arial"><B>Subject:</B> PCE BOF - Thursday August 5, 13:00 to 15:00</DIV> <DIV><BR></DIV>Hi,<BR><BR>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"><FONT face="Arial, Helvetica"><B>http://www.olddog.co.uk/60/pce.ppt</A>)<BR><BR></B></FONT>Cheers,<BR><BR>JP and Adrian.<BR><BR><B>Path Computation Element BOF (PCE BOF) <BR>60th IETF, San Diego, August 2004<BR><BR></B>Routing Area Ads: Alex Zinin (<A href="mailto:[email protected]">[email protected]</A>), <BR>Bill Fenner (<A href="mailto:[email protected]">[email protected]</A>)<BR><BR>BOF Chairs: JP Vasseur (<A href="mailto:[email protected]">[email protected]</A>), Adrian Farrel (<A href="mailto:[email protected]">[email protected]</A>)<BR><BR>Description: <BR>In certain MPLS TE networks it may be beneficial or desirable to have path <BR>computation performed by a distinct node (termed the Path Computation <BR>Element PCE) that is not the LSR that needs to know the path. This BOF <BR>examines the scope of such function, what extensions to existing protocols <BR>might required, what additional protocols may need to be developed, and <BR>whether there is cuase and support for this work within the IETF. <BR><BR>Proposed WG Charter <BR><BR>Organizational Overview <BR>The PCE working group coordinates the work within the IETF of defining the <BR>operation of path computation elements within the Internet. Path <BR>computation elements are responsible for computing paths through IP <BR>networks for uses such as traffic engineering so that a prime consumer of <BR>such paths might be an MPLS-TE LSR. Areas of responsibility will include <BR>the collection of attributes relevant to the computation of paths, the <BR>discovery by LSRs of available path computation elements, the communication <BR>with LSRs for the request of path computation, the collaboration between <BR>path computation elements within the network, and analysis of path <BR>computation algorithms with a view to ensuring consistency between computed <BR>paths. The working group will work closely with many working groups in the <BR>Routing Area including the OSPF, IS-IS, IDR, MPLS and CCAMP working groups. <BR><BR>Working Group Scope <BR><BR>The PCE working group scope includes: <BR>- Definition of Generalized Traffic Engineered LSP paths computation <BR>techniques involving Path Computation Element(s). This includes the intra <BR>IGP area, inter IGP area, inter-AS and inter-provider TE LSPs path <BR>computation for Point-to-Point, Point-to-Multipoint and <BR>Multipoint-to-Multipoint TE LSPs. <BR>- Definition of protocol-independent metrics and constraints defining path <BR>quality measurement criteria, algorithm complexity and scalability criteria <BR>related to path computation techniques. <BR>- Definition of requirements for communication between LSRs and PCEs <BR>including routing extensions in support of PCE discovery techniques within <BR>an IGP area and across multiple IGP areas, ASes and Provider networks, and <BR>including the development of new protocols or protocol extensions for <BR>requesting path computation and supplying responses. Any protocol <BR>extensions will developed in conjunction with the working groups in charge <BR>of the specific protocols. <BR>- Specification of routing (OSPF, ISIS, BGP) and signalling extensions <BR>(RSVP-TE) required by PCE-based path computation techniques. The extensions <BR>will developed in conjunction with the working groups in charge of the <BR>specific protocols. <BR>- Specification of requirements and protocol extensions related to the <BR>policy, security and confidentiality aspects of PCE-based path computation <BR>techniques involving PCEs of multiple Providers. <BR>- Definition of MIBs, management procedures related to the protocol <BR>extensions defined by the WG <BR>In doing this work, the WG will closely work with at least the following <BR>other WGs: CCAMP, MPLS, ISIS, OSPF, IDR. The WG will also cooperate with <BR>the ITU-T and OIF. <BR><BR>Goals and Milestones <BR>Dates for milestones to be decided later. <BR>- Post strawman WG goals and charter. <BR>- Submit WG document defining the framework and applicability of the <BR>PCE model. <BR>- Select a single candidate protocol from communication between LSRs <BR>and PCEs. <BR>- Submit document(s) that define various path computation models <BR>- Submit an analysis document examining the requirements for coherent <BR>computation techniques and the implication of cooperation between <BR>PCEs. <BR>- Submit a document defining the protocol for communication between <BR>LSRs and PCEs. <BR>- Submit document(s) defining extensions to routing and signalling <BR>protocols necessary to support the use of a PCE model within MPLS <BR>networks. <BR>- Submit a document defining MIB modules for modeling and management <BR>of PCE systems.<BR></BLOCKQUOTE></BODY></HTML> --Boundary_(ID_gb/wjlgfADm6KyH/g6t6xw)--