Date: Sat, 26 Sep 2015 17:10:05 -0700 From: Eitan Adler <lists@eitanadler.com> To: George Neville-Neil <gnn@neville-neil.com> Cc: hiren panchasara <hiren@strugglingcoder.info>, transport@freebsd.org Subject: Re: TCP rfc compliance Message-ID: <CAF6rxgkB6ug4KmheDyH1_VmJ-bUr=nGBcM5dxJO8PyBVcEuH=w@mail.gmail.com> In-Reply-To: <391A3F4B-84B9-4681-8F5C-A68319C2E0D6@neville-neil.com> References: <20150926225750.GE19325@strugglingcoder.info> <391A3F4B-84B9-4681-8F5C-A68319C2E0D6@neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks! I reformatted it, intending to keep all the content the same. On 26 September 2015 at 16:39, George Neville-Neil <gnn@neville-neil.com> wrote: > Excellent. Thanks! > > Best > George > > > On 26 Sep 2015, at 16:57, hiren panchasara wrote: > >> As discussed in the transport group meeting (and because it's a good >> idea anyways), I've created a page to list what rfcs we do and don't >> support here: >> https://wiki.freebsd.org/TransportProtocols/tcp_rfc_compliance >> >> Treat it as just a starting point and please add/modify/edit as you see fit. >> >> Cheers, >> Hiren -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgkB6ug4KmheDyH1_VmJ-bUr=nGBcM5dxJO8PyBVcEuH=w>