On 11/18/2014 4:36 PM, Nico Williams wrote: > On Tue, Nov 18, 2014 at 04:02:32PM -0800, Joe Touch wrote: >> On 11/18/2014 3:51 PM, Nico Williams wrote: >>> On Tue, Nov 18, 2014 at 03:10:58PM -0800, Joe Touch wrote: >>>> I'm speaking of the private interface. Yes, it could be >>>> implementation-specific, but if you are intending to define a complete >>>> spec for using SSL over raw TCP segments you first have to explain what >>>> you expect from raw TCP segments. >>> >>> This sub-thread is about your "However, there's should never be "early >>> read"." comment. I agreed that "early read", whether through public >>> interfaces or private ones, creates DoS considerations. Therefore we're >>> not really disagreeing, right? >> >> No. >> >> But I'm making another point - "early read" is a property of the TCP >> application interface. > > And I'm saying that for this particular protocol (TLS in TCP) the > early data is best handled by the system, with a system interface, not > an application interface.
I think we're agreeing, but my concern is how much the early data handling by the system needs to be spec'd out, not just left to the implementation. Joe _______________________________________________ Tcpinc mailing list Tcpinc@ietf.org https://www.ietf.org/mailman/listinfo/tcpinc
