IETF-61–WashingtonDCPathComputationElement(PCE).ppt

IETF-61–WashingtonDCputationElement(PCE)BOF-2Slidescanbefoundathttp://rtg./bof/pce/pce-bof-Co-chairs:JPVasseur/AdrianFarrelADs:AlexZinin/BillFenner1Agenda1)Introduction,admin,statementofobjectivesofthissecondBOF(5minutes)Adrian/JP2)QuicksummaryoftheconclusionofthefirstBOFheldinSanDiego(5minutes)JP3)Problemspace:recapofthePCEarchitectureIDdraft-ash-pce-architecture-(15minutes)Jerry4)Summaryofexisting/futuredrafts(5minutes)Adrian/JP5)Proposedcharter(15minutes)6)Discussion(andpossiblyconclusion!)(45minutes)-Needforthisworkandneedforaworkinggroup-Architecture-Charter7)Summaryandconclusions(15minutes)ChairsandADs21)Intro,admin,objectivesBluesheetsMinutetakersAgendabashAtthemic…QuestionsforclarificationonlySavetherestforopendiscussionsession31)Intro,admin,objectivesScopeofthePotentialPCEWGSpecifyasetofmechanismforPCE-eupwithanewInter-domainroutingparadigmScopedapplicabilitytoalimitednumberofTELSPsScopedapplicabilitytoa‘simple’topologyofASesorareasObjectivesofthisBOFExamineproposedarchitectureRecapdifferentperceivedrequirementspacesbysummaryofexistingdraftsAgreeaproposedcharterforaworkinggroup42)SummaryoftheBOFinSanDiegoClearstatementsofrequirementsfrommanyproviders(,KDDI,AT&T,FT,NTT,MCI)SeveraldistinctproblemsbeingsolvedShortestinter-area/AS/putation(putationrequirementsMultiplediversepaths(protectionandloadsharing)Re-optimizationMinimalpre-emptionPoint-to-putationPrevailingsub-textisinter-putationUnclearonwhatneedstobespecified(?)AMPwasaskedforitsopinionon:doesPCEaddressaninter-domainproblemthatneedaddressing?eptablewaytoresolvetheproblem?AMPchairas:Manypeople,especiallySPs,considerPCEmaybeappropriatetosolve,putationissuesassociatedwithinter-mitstohelpproviderequirementsforPCEforthiswork,putationElement(PCE)Architecturedraft-ash-pce-architecture-&T ******@******@,Inc.******@quicksummaryyoureadthedraftissuesraisedonlistnextstep:putationelement(PCE)pone