Joe,


I don't think that TCP-AO is a use case for the proposed converters.

You don't get to decide that. If you use TCP, then TCP-AO could be
enabled on the client.

The converter is not intended to be used for all TCP connections. In
the draft we explain how an MPTCP endpoint can bypass the converter if
the destination server supports MPTCP. For TCP-AO, my recommendation
would be that the default policy of the client would be to never use
the converter if TCP-AO is requested by the application.

How do you know you're using the converter? Is the initial connection to
that converter? Or does the converter hijack (the latter is the
implication of the text, AFAICT).

Consider a simple implementation using LD_PRELOAD to overload the connect system call on Linux. When the application issues connect, it has already set the required socket options that apply for this new connection. The converter implementation uses the destination address of the connect system call to create the TLV message and sets the TFO socket option to send it during its own connect with the converter. If the application had requested TFO, then the converter library simply uses the regular connect call and everything is fine.


Olivier

--

------------------------------
DISCLAIMER.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

_______________________________________________
Int-area mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/int-area

Reply via email to