1. Requirements for ROHC TCP1Lars-Erik Jonsson, 2001-03-23 Requirements for ROHC TCP Lars-Erik Jonsson Ericsson Research, Luleå Sweden lars-erik.jonsson@ericsson.com ROHC @ IETF 50, Minneapolis 2001-03-23

2. Requirements for ROHC TCP2Lars-Erik Jonsson, 2001-03-23 Outline The 00 draft Open issues and comments received How to proceed

3. Requirements for ROHC TCP3Lars-Erik Jonsson, 2001-03-23 draft-ietf-rohc-tcp-requirements-00.txt 2.2-5. TCP: Compression also in the cases when the SYN or FIN bits are set 2.2-6. TCP Options that should be compressed "Window scale "Selective acknowledgements (SACK) "Timestamp 2.3-2. For TCP, it is not a primary goal to have robustness mechanisms 2.3-3. The scheme should provide mechanisms for efficient compression of short-lived TCP transfers 2.4-4. The TCP scheme must be part of the ROHC framework

4. Requirements for ROHC TCP4Lars-Erik Jonsson, 2001-03-23 Open issues and comments received, 1(2) The requirements assume reliable link layers for TCP traffic "Is this ok? Any input from PILC on this one?? "Otherwise, should we have multiple profiles, adjustable robustness within a profile or always provide a certain amount of robustness at the expense of efficiency? "If non-reliable links is an issue, should that be clarified in each section that is reflected or should the 2.3 requirements be defined in two sections, one for reliable and one for unreliable link layers? Support for non-reliable transmission of ACKs (comment, J.K.) "The intention is to make delay reduction possible by not using link layer ARQ for acks. "This means that the HC scheme must provide some robustness capabilities for ACKs (see above).

5. Requirements for ROHC TCP5Lars-Erik Jonsson, 2001-03-23 Open issues and comments received, 2(2) Residual BER?? "How do we handle residual BER for TCP? "Error propagation (2.3-2) could be split in two sections, loss propagation and damage propagation ECN "Can someone volunteer to provide a suitable input regarding ECN concerns? Should we require that the TCP profile MUST be IPR free?

6. Requirements for ROHC TCP6Lars-Erik Jonsson, 2001-03-23 How to proceed Let us discuss the remaining issues on the mailing list in separate threads An updated version out before April 13th A stable version ready before London IETF (August)