@article{ Ludwig03,
  author = {R. Ludwig and A. Gurtov},
  title = {The {Eifel} Response Algorithm for {TCP}},
  journal = {Work in progress, {IETF}},
  year = {2003},
  annote = {This Internet draft comprises a complement to RFC 3522. In particular, the
                 Eifel algorithm as originally described by Reiner Ludwig has been partitioned
                 into two separate algorithms: a detection algorithm which is described in RFC
                 3522, and a response algorithm. The reason to this separation is that IETF
                 requires the detection algorithm as described in RFC 3522, but permits variations
                 in the response algorithm. The response algorithm described in this Internet
                 draft is pretty straighforward and entails that the state of the cwnd and sstresh
                 variables are reset to the values before the retransmission.},
  url = {papers/draft-ietf-tsvwg-tcp-eifel-response-04.txt},
  submitter = {Karl-Johan Grinnemo},
  bibdate = {Tuesday, February 24, 2004 at 21:27:25 (CEST)}
}

{"_id":"8CqjrueECx6vST84J","bibbaseid":"ludwig-gurtov-theeifelresponsealgorithmfortcp-2003","downloads":0,"creationDate":"2015-12-04T23:32:58.825Z","title":"The Eifel Response Algorithm for TCP","author_short":["Ludwig, R.","Gurtov, A."],"year":2003,"bibtype":"article","biburl":"http://www.cs.kau.se/cs/prtp/prtp.bib","bibdata":{"annote":"This Internet draft comprises a complement to RFC 3522. In particular, the Eifel algorithm as originally described by Reiner Ludwig has been partitioned into two separate algorithms: a detection algorithm which is described in RFC 3522, and a response algorithm. The reason to this separation is that IETF requires the detection algorithm as described in RFC 3522, but permits variations in the response algorithm. The response algorithm described in this Internet draft is pretty straighforward and entails that the state of the cwnd and sstresh variables are reset to the values before the retransmission.","author":["Ludwig, R.","Gurtov, A."],"author_short":["Ludwig, R.","Gurtov, A."],"bibdate":"Tuesday, February 24, 2004 at 21:27:25 (CEST)","bibtex":"@article{ Ludwig03,\n author = {R. Ludwig and A. Gurtov},\n title = {The {Eifel} Response Algorithm for {TCP}},\n journal = {Work in progress, {IETF}},\n year = {2003},\n annote = {This Internet draft comprises a complement to RFC 3522. In particular, the\n Eifel algorithm as originally described by Reiner Ludwig has been partitioned\n into two separate algorithms: a detection algorithm which is described in RFC\n 3522, and a response algorithm. The reason to this separation is that IETF\n requires the detection algorithm as described in RFC 3522, but permits variations\n in the response algorithm. The response algorithm described in this Internet\n draft is pretty straighforward and entails that the state of the cwnd and sstresh\n variables are reset to the values before the retransmission.},\n url = {papers/draft-ietf-tsvwg-tcp-eifel-response-04.txt},\n submitter = {Karl-Johan Grinnemo},\n bibdate = {Tuesday, February 24, 2004 at 21:27:25 (CEST)}\n}","bibtype":"article","id":"Ludwig03","journal":"Work in progress, IETF","key":"Ludwig03","submitter":"Karl-Johan Grinnemo","title":"The Eifel Response Algorithm for TCP","type":"article","url":"papers/draft-ietf-tsvwg-tcp-eifel-response-04.txt","year":"2003","bibbaseid":"ludwig-gurtov-theeifelresponsealgorithmfortcp-2003","role":"author","urls":{"Paper":"http://www.cs.kau.se/cs/prtp/papers/draft-ietf-tsvwg-tcp-eifel-response-04.txt"},"downloads":0},"search_terms":["eifel","response","algorithm","tcp","ludwig","gurtov"],"keywords":[],"authorIDs":[],"dataSources":["6WGcSu2Ku7pZzqCcg"]}