On 7/19/2017 10:43 PM, mohamed.boucad...@orange.com wrote: > ... >>> 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? > [Med] The converter is explicilty configured (e.g., locally configured or y > means of https://tools.ietf.org/html/draft-boucadair-mptcp-dhc-07). AOK. If these are independent TCP connections that are explicitly addressed, they should be described as such. The current doc implies SYN translation - whether that's an implementation optimization (limited to successful TFO SYNs) or not needs to be very clearly described as such as well.
Joe
