1 / 5

Quick Failover Algorithm in SCTP draft- ietf - tsvwg - sctp -failover

Quick Failover Algorithm in SCTP draft- ietf - tsvwg - sctp -failover. Y. Nishida, P. Natarajan , A. Caro, P. Amer , K. Nielsen. IETF90, Toronto. Status. - 05 has been submitted We appreciate very detailed reviews!

cheung
Download Presentation

Quick Failover Algorithm in SCTP draft- ietf - tsvwg - sctp -failover

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. Quick Failover Algorithm in SCTPdraft-ietf-tsvwg-sctp-failover Y. Nishida, P. Natarajan, A. Caro, P. Amer, K. Nielsen IETF90, Toronto

  2. Status • -05 has been submitted • We appreciate very detailed reviews! • Re-structuring and language clarifications were judged to be necessary for PS request to be taken into consideration • -05 aimed to address needed clarifications (0405: editorial change with removal of one line) • Differences from -03 • Structural changes: Discussion of (deficient) Alternative Approaches is moved to Appendix • Abstract has been updated to more clearly set the scope of document • Algorithm descriptions have been clarified; More explicit descriptions and stringent usage of RFC2119 standards recommendation language • All are clarifications, not technical updates. No change of function.

  3. Abstract – Scope Clarification • Complements RFC4960 by: • The PotentiallyFailed state and new Quick Failover operation • AlternativePermanent FailoverSwitchover operation mode (Optional)

  4. Algorithm Clarifications • Added MUST, SHOULD and MAY terms with qualification of terms used where relevant. • Made more explicit descriptions in some places. • Please see draft text for details

  5. Proposed Next Steps • draft-ietf-tsvwg-sctp-failover-05 is requested for consideration for PS • As the updates are considered to not alter the technical substance then evaluation of the text, as it appears after the clarifications and the more stringent standards language following RFC2119, to bedone as part of the WGLC

More Related