@techreport{briscoe-tcpm-echo-cookie-00,
    number =    {draft-briscoe-tcpm-echo-cookie-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-briscoe-tcpm-echo-cookie/00/},
    author =    {Bob Briscoe},
    title =     {{The Echo Cookie TCP Option}},
    pagetotal = 6,
    year =      2014,
    month =     oct,
    day =       27,
    abstract =  {This document specifies a TCP Option called EchoCookie. It provides a single field that a TCP server can use to store opaque cookie data 'in flight' rather than in memory. As new TCP options are defined, they can require that implementations support the EchoCookie option. Then if a server's SYN queue is under pressure from a SYN flooding attack, it can ask clients to echo its connection state in their acknowledgement. This facility is similar to the classic SYN Cookie, but it provides enough space for connection state associated with TCP options. In contrast, the classic location for a SYN Cookie only provides enough space for a degraded encoding of the Maximum Segment Size (MSS) TCP option and no others.},
}