Updated QUICKSTART spec
2006-03-03 23:14![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
fanfhttp://www-uxsup.csx.cam.ac.uk/~fanf2/hermes/doc/antiforgery/draft-fanf-smtp-quickstart.txt
This version has a basic subset which should be easy to implement, and which brings the MAIL command forward from the client's 9th packet to its 5th in typical use.
Full QUICKSTART allows the client to pipeline commands before the server greeting and after the TLS handshake in a way that should be safe, albeit not so trivial to implement. If all goes well, the MAIL command appears in
the client's 3rd packet, which I think is pretty good :-) If the client has to recover from a cache miss, it should be no slower than basic QUICKSTART.
This version has a basic subset which should be easy to implement, and which brings the MAIL command forward from the client's 9th packet to its 5th in typical use.
Full QUICKSTART allows the client to pipeline commands before the server greeting and after the TLS handshake in a way that should be safe, albeit not so trivial to implement. If all goes well, the MAIL command appears in
the client's 3rd packet, which I think is pretty good :-) If the client has to recover from a cache miss, it should be no slower than basic QUICKSTART.
