60 likes | 160 Views
Gabriel Montenegro gab@sun.com Sun IETF-47, Adelaide 3/00. SLOW and ERROR Updates (rev 03) draft-ietf-pilc-slow-03.txt dawkins, montenegro,kojo, magret draft-ietf-pilc-error-03.txt dawkins, montenegro,kojo, magret, vaidya. Cosmetic changes to prepare for advancement as BCP
E N D
Gabriel Montenegro gab@sun.com Sun IETF-47, Adelaide 3/00 SLOW and ERROR Updates(rev 03)draft-ietf-pilc-slow-03.txtdawkins, montenegro,kojo, magretdraft-ietf-pilc-error-03.txtdawkins, montenegro,kojo, magret, vaidya
Cosmetic changes to prepare for advancement as BCP change from Explicit Corruption Notification to Explicit Transmission Error Notification in ERROR New sections in both drafts to separate recommended mechanisms Topics for Further Work section on interesting, but not completely understood or easily standardized mechanisms New Appendixes on experimental mechanisms Both drafts currently in LAST CALL till April 7 SLOW and ERROR Changes
example in section 2.3 with respect to receive and router buffer sizes needs to be redone (markku) should we recommend RED? should we recommend ECN? Section on MTU, beef up with LINK’s section Issues with SLOW
section 1.2 on relationship with LINK could use some editing section 2.2 on aimd is not accurate section 2.2, why congestion windows remain small #2 is inaccurate #3 must be removed, it is not general (only applies to LTNs) Issues with Error
section 4.0, first paragraph on SACK-EXT (aka DSACK) needs to be updated as it is no longer an experimental mechanism (confirm with s.floyd) section 4.0, second paragraph on delayed dupacks needs clarification Appendix A: Delayed Dupacks clarify link-layers in which it is usefuol (from rfc2757) Appendix B: Transmission Error Notifications or should there be a new appendix on link outages and contribute my text on it Issues with Error (2)
Still some changes are desireable. Do we need another last call? Conclusion