50 likes | 60 Views
This draft proposes a way to specify new code points for Diff-Serv Traffic Engineering (DS-TE) support in Path Computation Element Protocol (PCEP). It addresses the need for path computation considering class-type bandwidth constraints and introduces an optional CLASSTYPE object for PCEP. The draft outlines next steps for recommended values and suggests adoption as a working group identification.
E N D
Diff-Serv aware PCEPdraft-sivabalan-pce-dste-00.txt Siva Sivabalan (Cisco Systems) Jon Parker (Cisco Systems) Sami Boutros (Cisco Systems) Kenji Kumaki (KDDI)
Overview • Simple ID to specify new code points for DS-TE support • DS-TE identified as a requirement in inter-area TE and inter-AS TE requirements (RFC4105 and RFC4216)
Specifics • Path computation for a DS-TE LSP must take into account the class-type (CT) bandwidth constraints • A PCE needs to know the CT of a path computation request it receives
Purpose of the draft • Defines an optional CLASSTYPE object for PCEP (matching that of RFC4124) • The CLASSTYPE object is carried in the PCReq message and specifies the CT to be used for the path computation
Next steps • Settle on recommended values (object type, error) • Adopt as WG ID?