1 / 7

IETF 66, PCE WG, Montreal 07/13/2006

urit
Télécharger la présentation

IETF 66, PCE WG, Montreal 07/13/2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. PCE Communication Protocol (PCEP)draft-ietf-pce-pcep-02.txtJ.P. Vasseur (Cisco System Inc.) J.L. Le Roux (France Telecom) A. Ayyangar (Juniper Networks) E. Oki (NTT) A. Atlas (Google) A. Dolganow (Alcatel) Y. Ikejiri (NTT Communications Corporation) K. Kumaki (KDDI Corporation) IETF 66, PCE WG, Montreal 07/13/2006

  2. Changes since last version • One new bit defined in the RP object, the F bit, to indicate a request for a backup path computation after Failure • The requests includes the current path (carried in an RRO), and the failed element (carried in an XRO) • Allows avoiding the failed elements and avoiding double bandwidth booking • Added a Finite State Machine • Added a section that discusses compliance to generic requirements

  3. PCEP Finite State Machine (1) • Simple State Machine common to PCC and PCE • Five states • PCE-PCE communication with a single TCP session • If two PCEP peers try simultaneously to setup a TCP connection (collision) the connection with the lower source IP @ is killed • Distinct parameters (keepalive timer, deadtimer) to be negotiated in each direction • Independent parameters negotiation • OpenWait state used to negotiate remote parameters • KeepWait state used to negotiate local parameters • The session is up once local and remote parameters are agreed

  4. PCEP Finite State Machine (2)

  5. Compliance to the requirements • Evaluation of the PCEP spec against requirements listed in the PCECP generic requirement ID • All MUST requirements are covered, except three points: • Indication whether load balancing is allowed, and associated parameters (minimum bandwidth per path, max #path) • Inclusion of the desired objective function in the request • Resynchronization of information & requests between sender & receiver after a communication failure

  6. Next steps • Need to address not yet covered generic requirements • Load balancing will be covered in the next revision • Objectives functions will be covered in a separate ID • More discussion required on protocol recovery • Need to add elements for PCE identification (for multiple PCE computation) • PCE list enforcement in the PCReq message • PCE list recording in the PCRep message • PCE identification in the PCErr message • Start working on extensions to cover Inter-Area, Inter-AS and inter-layer specific requirements • Will be done in separate IDs • Continue discussion on the list

  7. ThanksQuestions?

More Related