RE: PCE BOF - Thursday August 5, 13:00 to 15:00
"BOUCADAIR Mohamed RD-CORE-CAE" <[email protected]> Mon, 9 Aug 2004 10:37:44 +0200
| Newsgroups | gmane.ietf.mpls,gmane.ietf.ccamp,gmane.ietf.tewg |
|---|---|
| Message-ID | <6CF039C5B32037498B02251E11CDE6B019D37E@ftrdmel3.rd.francetelecom.fr> |
This is a multi-part message in MIME format. --===============0994592947== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C47DEC.24650716" This is a multi-part message in MIME format. ------_=_NextPart_001_01C47DEC.24650716 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi,=20 =20 The=20 =20 draft-mescal-pce-interas-00.txt draft-mescal-pcp-interas-00.txt draft-mescal-pceid-00.txt =20 drafts are work in progress. Further information about related work = could be found in <http://www.mescal.org> www.mescal.org. =20 Best regards, =20 Mohamed -----Message d'origine----- De : [email protected] [mailto:[email protected]]De la = part de lidefeng Envoy=A8=A6 : jeudi 5 ao?t 2004 02:53 =A8=A4 : Jean Philippe Vasseur; [email protected]; [email protected]; TEWG; = [email protected] Cc : [email protected]; [email protected]; Bill Fenner Objet : Re: PCE BOF - Thursday August 5, 13:00 to 15:00 Hi, =20 I think it is very necessary to do this work in IETF, Service Providers = in China also expressed such requirements during the technical = exchanges. =20 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! =20 draft-mescal-pce-interas-00.txt draft-mescal-pcp-interas-00.txt draft-mescal-pceid-00.txt =20 Best Regards Defeng Li=20 ----- Original Message -----=20 From: Jean Philippe <mailto:[email protected]> Vasseur=20 To: [email protected] ; [email protected] ; TEWG = <mailto:[email protected]> ; [email protected]=20 Cc: [email protected] ; [email protected] ; Bill = <mailto:[email protected]> Fenner=20 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> = http://www.olddog.co.uk/60/pce.ppt) Cheers, JP and Adrian. Path Computation Element BOF (PCE BOF)=20 60th IETF, San Diego, August 2004 Routing Area Ads: Alex Zinin ( [email protected]),=20 Bill Fenner ( [email protected]) BOF Chairs: JP Vasseur ( [email protected]), Adrian Farrel ( = [email protected]) Description:=20 In certain MPLS TE networks it may be beneficial or desirable to have = path=20 computation performed by a distinct node (termed the Path Computation=20 Element PCE) that is not the LSR that needs to know the path. This BOF=20 examines the scope of such function, what extensions to existing = protocols=20 might required, what additional protocols may need to be developed, and=20 whether there is cuase and support for this work within the IETF.=20 Proposed WG Charter=20 Organizational Overview=20 The PCE working group coordinates the work within the IETF of defining = the=20 operation of path computation elements within the Internet. Path=20 computation elements are responsible for computing paths through IP=20 networks for uses such as traffic engineering so that a prime consumer = of=20 such paths might be an MPLS-TE LSR. Areas of responsibility will include = the collection of attributes relevant to the computation of paths, the=20 discovery by LSRs of available path computation elements, the = communication=20 with LSRs for the request of path computation, the collaboration between = path computation elements within the network, and analysis of path=20 computation algorithms with a view to ensuring consistency between = computed=20 paths. The working group will work closely with many working groups in = the=20 Routing Area including the OSPF, IS-IS, IDR, MPLS and CCAMP working = groups.=20 Working Group Scope=20 The PCE working group scope includes:=20 - Definition of Generalized Traffic Engineered LSP paths computation=20 techniques involving Path Computation Element(s). This includes the = intra=20 IGP area, inter IGP area, inter-AS and inter-provider TE LSPs path=20 computation for Point-to-Point, Point-to-Multipoint and=20 Multipoint-to-Multipoint TE LSPs.=20 - Definition of protocol-independent metrics and constraints defining = path=20 quality measurement criteria, algorithm complexity and scalability = criteria=20 related to path computation techniques.=20 - Definition of requirements for communication between LSRs and PCEs=20 including routing extensions in support of PCE discovery techniques = within=20 an IGP area and across multiple IGP areas, ASes and Provider networks, = and=20 including the development of new protocols or protocol extensions for=20 requesting path computation and supplying responses. Any protocol=20 extensions will developed in conjunction with the working groups in = charge=20 of the specific protocols.=20 - Specification of routing (OSPF, ISIS, BGP) and signalling extensions=20 (RSVP-TE) required by PCE-based path computation techniques. The = extensions=20 will developed in conjunction with the working groups in charge of the=20 specific protocols.=20 - Specification of requirements and protocol extensions related to the=20 policy, security and confidentiality aspects of PCE-based path = computation=20 techniques involving PCEs of multiple Providers.=20 - Definition of MIBs, management procedures related to the protocol=20 extensions defined by the WG=20 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.=20 Goals and Milestones=20 Dates for milestones to be decided later.=20 - Post strawman WG goals and charter.=20 - Submit WG document defining the framework and applicability of the=20 PCE model.=20 - Select a single candidate protocol from communication between LSRs=20 and PCEs.=20 - Submit document(s) that define various path computation models=20 - Submit an analysis document examining the requirements for coherent=20 computation techniques and the implication of cooperation between=20 PCEs.=20 - Submit a document defining the protocol for communication between=20 LSRs and PCEs.=20 - Submit document(s) defining extensions to routing and signalling=20 protocols necessary to support the use of a PCE model within MPLS=20 networks.=20 - Submit a document defining MIB modules for modeling and management=20 of PCE systems. ------_=_NextPart_001_01C47DEC.24650716 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dgb2312"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2>Hi, </FONT></SPAN></DIV> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2>The </FONT> <DIV><FONT color=3D#0000ff size=3D2></FONT> </DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff=20 size=3D2>draft-mescal-pce-interas-00.txt</FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff=20 size=3D2>draft-mescal-pcp-interas-00.txt</FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff=20 size=3D2>draft-mescal-pceid-00.txt</FONT></DIV> <DIV><FONT face=3D"Courier New" color=3D#0000ff = size=3D2></FONT> </DIV> <DIV><SPAN class=3D368213508-09082004><FONT color=3D#0000ff = size=3D2><FONT=20 face=3D"Courier New">drafts are work in progress. Further information = about=20 related work could be found in </FONT><A = href=3D"http://www.mescal.org"><FONT=20 face=3D"Courier New">www.mescal.org</FONT></A><FONT=20 face=3D"Courier New">.</FONT></FONT></SPAN></DIV> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2>Best regards,</FONT></SPAN></DIV> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2></FONT></SPAN> </DIV> <DIV><SPAN class=3D368213508-09082004><FONT face=3D"Courier New" = color=3D#0000ff=20 size=3D2>Mohamed</FONT></SPAN></DIV></SPAN></DIV> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT = face=3DTahoma=20 size=3D2>-----Message d'origine-----<BR><B>De :</B>=20 [email protected] [mailto:[email protected]]<B>De la = part de</B>=20 lidefeng<BR><B>Envoy=A8=A6 :</B> jeudi 5 août 2004 = 02:53<BR><B>À :</B>=20 Jean Philippe Vasseur; [email protected]; [email protected]; TEWG;=20 [email protected]<BR><B>Cc :</B> [email protected]; [email protected]; = Bill=20 Fenner<BR><B>Objet :</B> Re: PCE BOF - Thursday August 5, 13:00 = to=20 15:00<BR><BR></FONT></DIV> <DIV><FONT face=3DArial size=3D2>Hi,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I think it is very necessary to do = this work in=20 IETF, Service Providers in China also expressed such requirements = during the=20 technical exchanges.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>I have delved into PCE.ppt in the = link, however,=20 I can't find the following drafts, If anyone can share with me? = Could you=20 please send me these drafts in e-mail, Thanks!</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial = size=3D2>draft-mescal-pce-interas-00.txt</FONT></DIV> <DIV><FONT face=3DArial = size=3D2>draft-mescal-pcp-interas-00.txt</FONT></DIV> <DIV><FONT face=3DArial = size=3D2>draft-mescal-pceid-00.txt</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Best Regards</FONT></DIV> <DIV><FONT face=3DArial size=3D2>Defeng Li</FONT> </DIV> <BLOCKQUOTE=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A [email protected] = href=3D"mailto:[email protected]">Jean Philippe=20 Vasseur</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A = [email protected]=20 href=3D"mailto:[email protected]">[email protected]</A> ; <A=20 [email protected] = href=3D"mailto:[email protected]">[email protected]</A> ; <A=20 [email protected] = href=3D"mailto:[email protected]">TEWG</A> ; <A=20 [email protected] = href=3D"mailto:[email protected]">[email protected]</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A = [email protected]=20 href=3D"mailto:[email protected]">[email protected]</A> ; <A=20 [email protected] = href=3D"mailto:[email protected]">[email protected]</A> ; <A=20 [email protected] = href=3D"mailto:[email protected]">Bill=20 Fenner</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, August 01, 2004 = 1:07=20 PM</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> PCE BOF - Thursday = August 5,=20 13:00 to 15:00</DIV> <DIV><BR></DIV>Hi,<BR><BR>Just to let you know that the set of = slides for=20 the PCE BOF will be available next Monday morning (<A=20 href=3D"http://www.olddog.co.uk/60/pce.ppt" eudora=3D"autourl"><FONT = face=3D"Arial, = Helvetica"><B>http://www.olddog.co.uk/60/pce.ppt</A>)<BR><BR></B></FONT>C= heers,<BR><BR>JP=20 and Adrian.<BR><BR><B>Path Computation Element BOF (PCE BOF) = <BR>60th IETF,=20 San Diego, August 2004<BR><BR></B>Routing Area Ads: Alex Zinin (<A=20 href=3D"mailto:[email protected]">[email protected]</A>), <BR>Bill Fenner = (<A=20 = href=3D"mailto:[email protected]">[email protected]</A>)<BR><= BR>BOF=20 Chairs: JP Vasseur (<A=20 href=3D"mailto:[email protected]">[email protected]</A>), Adrian = Farrel (<A=20 = href=3D"mailto:[email protected]">[email protected]</A>)<BR><BR>Descr= iption:=20 <BR>In certain MPLS TE networks it may be beneficial or desirable to = have=20 path <BR>computation performed by a distinct node (termed the Path=20 Computation <BR>Element PCE) that is not the LSR that needs to know = the=20 path. This BOF <BR>examines the scope of such function, what = extensions to=20 existing protocols <BR>might required, what additional protocols may = need to=20 be developed, and <BR>whether there is cuase and support for this = work=20 within the IETF. <BR><BR>Proposed WG Charter <BR><BR>Organizational = Overview=20 <BR>The PCE working group coordinates the work within the IETF of = defining=20 the <BR>operation of path computation elements within the Internet. = Path=20 <BR>computation elements are responsible for computing paths through = IP=20 <BR>networks for uses such as traffic engineering so that a prime = consumer=20 of <BR>such paths might be an MPLS-TE LSR. Areas of responsibility = will=20 include <BR>the collection of attributes relevant to the computation = of=20 paths, the <BR>discovery by LSRs of available path computation = elements, the=20 communication <BR>with LSRs for the request of path computation, the = collaboration between <BR>path computation elements within the = network, and=20 analysis of path <BR>computation algorithms with a view to ensuring=20 consistency between computed <BR>paths. The working group will work = closely=20 with many working groups in the <BR>Routing Area including the OSPF, = IS-IS,=20 IDR, MPLS and CCAMP working groups. <BR><BR>Working Group Scope = <BR><BR>The=20 PCE working group scope includes: <BR>- Definition of Generalized = Traffic=20 Engineered LSP paths computation <BR>techniques involving Path = Computation=20 Element(s). This includes the intra <BR>IGP area, inter IGP area, = inter-AS=20 and inter-provider TE LSPs path <BR>computation for Point-to-Point,=20 Point-to-Multipoint and <BR>Multipoint-to-Multipoint TE LSPs. <BR>-=20 Definition of protocol-independent metrics and constraints defining = path=20 <BR>quality measurement criteria, algorithm complexity and = scalability=20 criteria <BR>related to path computation techniques. <BR>- = Definition of=20 requirements for communication between LSRs and PCEs <BR>including = routing=20 extensions in support of PCE discovery techniques within <BR>an IGP = area and=20 across multiple IGP areas, ASes and Provider networks, and = <BR>including the=20 development of new protocols or protocol extensions for = <BR>requesting path=20 computation and supplying responses. Any protocol <BR>extensions = will=20 developed in conjunction with the working groups in charge <BR>of = the=20 specific protocols. <BR>- Specification of routing (OSPF, ISIS, BGP) = and=20 signalling extensions <BR>(RSVP-TE) required by PCE-based path = computation=20 techniques. The extensions <BR>will developed in conjunction with = the=20 working groups in charge of the <BR>specific protocols. <BR>- = Specification=20 of requirements and protocol extensions related to the <BR>policy, = security=20 and confidentiality aspects of PCE-based path computation = <BR>techniques=20 involving PCEs of multiple Providers. <BR>- Definition of MIBs, = management=20 procedures related to the protocol <BR>extensions defined by the WG = <BR>In=20 doing this work, the WG will closely work with at least the = following=20 <BR>other WGs: CCAMP, MPLS, ISIS, OSPF, IDR. The WG will also = cooperate with=20 <BR>the ITU-T and OIF. <BR><BR>Goals and Milestones <BR>Dates for = milestones=20 to be decided later. <BR>- Post strawman WG goals and charter. <BR>- = Submit=20 WG document defining the framework and applicability of the <BR>PCE = model.=20 <BR>- Select a single candidate protocol from communication between = LSRs=20 <BR>and PCEs. <BR>- Submit document(s) that define various path = computation=20 models <BR>- Submit an analysis document examining the requirements = for=20 coherent <BR>computation techniques and the implication of = cooperation=20 between <BR>PCEs. <BR>- Submit a document defining the protocol for=20 communication between <BR>LSRs and PCEs. <BR>- Submit document(s) = defining=20 extensions to routing and signalling <BR>protocols necessary to = support the=20 use of a PCE model within MPLS <BR>networks. <BR>- Submit a document = defining MIB modules for modeling and management <BR>of PCE=20 systems.<BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML> ------_=_NextPart_001_01C47DEC.24650716-- --===============0994592947== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list [email protected] https://www1.ietf.org/mailman/listinfo/mpls --===============0994592947==--