1 / 15

Stateful PCE - update

Stateful PCE - update. draft-ietf-pce-stateful-pce-07 draft-crabbe-pce-pce-initated-lsp-03. Ina Minei Ed Crabbe Jan Medved Robert Varga Siva Sivabalan. Common updates to both drafts.

brie
Download Presentation

Stateful PCE - update

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. Stateful PCE - update draft-ietf-pce-stateful-pce-07 draft-crabbe-pce-pce-initated-lsp-03 Ina Minei Ed Crabbe Jan Medved Robert Varga Siva Sivabalan

  2. Common updates to both drafts • Removed references to the LSP signaling type – aligning with the new version of draft-sivabalan-pce-lsp-setup-type-01.

  3. Base draft – draft-ietf-pce-stateful-pce-07

  4. Base draft updates • Address comments received during the last IETF • Very productive meetings in Berlin • Two revisions were produced (06 and 07) • Document slim-down from 59 to 46 pages • Focus on the base functionality • Stable document, ready for last review

  5. Base draft – what was removed? • Use cases – draft-ietf-pce-stateful-pce-app is now the only source of use cases • Optional state sync optimizations (and associated TLV) and triggered optimization moved to draft-minei-pce-stateful-sync-optimizations • Removed PCRep/PCReq extensions – lack of strong use cases. • Delegation parameters – lack of use

  6. Base draft updates – error handling • Spell out the encoding of the PCErr message • Clean up error handling for synchronization failures • Spell out error handling for the case of reaching the limits of resource consumption • Check error handling throughout the document

  7. Base draft - updates • Make the SRP object optional (and its absence equivalent to an SRP-ID-number of 0) • Based on feedback from the working group • Clarify • State compression • Use of the RRO • Add the egress node identifier to the LSP identifiers TLV

  8. Base draft - next steps • The document is stable • Implementation status • At least two vendors working on implementations, early versions available in shipping code from at least two vendors. • Request the working group for a thorough review, in preparation for last call.

  9. PCE-initiated LSP draft – draft-crabbe-pce-pce-initiated-lsp-03

  10. PCE-initiated LSP draft updates • Added the C flag to tag LSPs that were instantiated by the PCE • Clarified error reporting throughout • Updated the security section • Updated RBNF for LSP deletion to only send the SRP and LSP objects. • Added an implementation report section

  11. Next steps • Implementation survey showed several implementations already exist • Severaldrafts depend on this draft • The draft is stable • Ask the chairs to poll for working group adoption

  12. Stateful PCE synchronization draft-minei-pce-stateful-sync-optimizations-00 Ina Minei Ed Crabbe Jan Medved Robert Varga Xian Zhang Dhruv Dhody

  13. What is this? • Merged all the synchronization optimizations into one document • draft-zhx-pce-stateful-lsp-sync-00 • Synchronization optimization procedures from draft-ietf-pce-stateful-pce • No new content • Just clarification of the procedures

  14. Topics covered • State synchronization avoidance • PCE-triggered state synchronization • Incremental state synchronization

  15. Next steps • The content of this document was discussed in the past • Thoughts on how to progress?

More Related