On Thu, Aug 13, 2015 at 3:11 PM, David Mazieres < [email protected]> wrote:
> Daniel Kahn Gillmor <[email protected]> writes: > > > On Thu 2015-08-13 17:05:38 -0400, Kyle Rose wrote: > > That said, one could imagine a fringe use case where an application > wants to prove that two anonymous TCP connections belong to the same two > processes, in which case the session ID of the first connection might be > used as a MAC key to authenticate the session ID of the second. So you > don't want the session ID to be predictable, even if making it public > doesn't hurt TCPINC itself. > > I don't think I understand this use case. To whom does the application want to prove this? regards, Ted
_______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
