Richard Scheffenegger Mirja Kühlewind TCP Timestamp Negotiation draft-scheffenegger-tcpm-timestamp- negotiation th IETF, Vancouver, Canada

tcpm-timestamp-negotiation-04  Received numerous feedback  Removed timestamp clock range negotiation from draft  Benefits unclear  potentially confusing implementers  Moved Use Cases to Appendix  Keep TS.recent on receiver for PAWS 2 84 th IETF, Vancouver, Canada

tcpm-timestamp-negotiation-04 Open issues:  Draft tries to address (too?) many things:  Semantic change when TS used with SACK  Timestamp clock exposure  Security mechanism (Mask)  Versioning  TSecr no longer available on SYN (TFO, SYN flood protection (?) in Linux) 3 84 th IETF, Vancouver, Canada

tcpm-timestamp-negotiation-04 Split draft in  Semantic change of TS w/ SACK  Basic negotiation  Clear description of the PAWS, RTTM modifications necessary  Exposing timestamp clock interval  Based on basic negotiation  Refine encoding and mechanisms 4 84 th IETF, Vancouver, Canada

tcpm-timestamp-negotiation-04 Poll:  Who has read the -04 draft?  Security mechanism necessary for TS (Masking)?  Split document or keep single draft?  Other comments… 5 84 th IETF, Vancouver, Canada

6