Hi Toerless,
thanks a lot for the updated text. I still have one little point I would like
to discuss a bit further on this text:
"The above described behavior/policy for MPTCP must be controllable by
applications or libraries acting on behalf of applications. APIs
and/or data models
Thanks, Mirja. Inline.
On Mon, Jan 22, 2018 at 01:37:58PM +0100, Mirja Kuehlewind (IETF) wrote:
> Hi Toerless,
>
> thanks a lot for the updated text. I still have one little point I would like
> to discuss a bit further on this text:
>
> "The above described behavior/policy for MPTCP must be
Hi Toerless,
Thanks for the updates. It looks better to me.
Just one very minor comment..
"GACP and data-plane addresses exist in different VRFs. The MPTCP
stack needs to be able to access multiple VRFs and know which local
address is existing in which VRF. There also needs to be a