Subject: [multipathtcp] draft-ietf-mptcp-rfc6824bis

From: <[email-masked]>
Date: Wed, 7 Dec 2016 14:40:22 +0000

Hi Alan, all,

It seems that some fixes are needed in https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-07#section-3.1 given that C-bit has now a meaning:

==

   D through H:  The remaining bits, labeled "C" through "H", are used

      for crypto algorithm negotiation.  Currently only the rightmost

      bit, labeled "H", is assigned.  Bit "H" indicates the use of HMAC-

      SHA1 (as defined in Section 3.2<https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-07#section-3.2>).  An implementation that only

      supports this method MUST set bit "H" to 1, and bits "C" through

      "G" to 0.

   A crypto algorithm MUST be specified.  If flag bits C through H are

   all 0, the MP_CAPABLE option MUST be treated as invalid and ignored

   (that is, it must be treated as a regular TCP handshake).

..
====

Also, https://tools.ietf.org/html/draft-ietf-mptcp-rfc6824bis-07#section-8.2 needs to be updated.

Thank you.

Cheers,
Med