<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tcpm-dctcp" target="https://datatracker.ietf.org/doc/html/draft-ietf-tcpm-dctcp-05">
   <front>
      <title>Datacenter TCP (DCTCP): TCP Congestion Control for Datacenters</title>
      <author initials="S." surname="Bensley" fullname="Stephen Bensley">
         </author>
      <author initials="D." surname="Thaler" fullname="Dave Thaler">
         </author>
      <author initials="P." surname="Balasubramanian" fullname="Praveen Balasubramanian">
         </author>
      <author initials="L." surname="Eggert" fullname="Lars Eggert">
         </author>
      <author initials="G." surname="Judd" fullname="Glenn Judd">
         </author>
      <date month="March" day="27" year="2017" />
      <abstract>
	 <t>   This informational memo describes Datacenter TCP (DCTCP), an
   improvement to TCP congestion control for datacenter traffic.  DCTCP
   uses improved Explicit Congestion Notification (ECN) processing to
   estimate the fraction of bytes that encounter congestion, rather than
   simply detecting that some congestion has occurred.  DCTCP then
   scales the TCP congestion window based on this estimate.  This method
   achieves high burst tolerance, low latency, and high throughput with
   shallow-buffered switches.  This memo also discusses deployment
   issues related to the coexistence of DCTCP and conventional TCP, the
   lack of a negotiating mechanism between sender and receiver, and
   presents some possible mitigations.  DCTCP as described in this draft
   is applicable to deployments in controlled environments like
   datacenters but it MUST NOT be deployed over the public Internet
   without additional measures, as detailed in Section 5.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tcpm-dctcp-05" />
   
</reference>
