Yeah - ENO.
> On Jul 29, 2016, at 12:18 PM, Wesley Eddy <[email protected]> wrote: > >> On 7/29/2016 2:47 PM, Joe Touch wrote: >> FWIW, IMO the best wording would: >> >> - start with the simplest case, i.e., NOT trying to optimize EDO to use >> SYN data >> >> - present the use of SYN data with EDO as an optimization >> that optimization might be a MAY or SHOULD, but not a MUST >> >> Otherwise, you're needlessly complicating your spec for an optimization. > > Just to be clear, this is actually talking about ENO, and not EDO, correct? > (I'm assuming a repeated typo in your message) > > SYN data with EDO does not need any special discussion, because EDO only > alters DO semantics for later (non-SYN) segments. So, how a stack deals with > data on SYN is un-related to EDO (but more critical for ENO). > > > > > _______________________________________________ > Tcpinc mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/tcpinc _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
