diff mbox series

.topmsg: mptcp: parse and emit MP_CAPABLE option according to v1 spec

Message ID 20191213005822.29791-6-mathew.j.martineau@linux.intel.com
State Accepted, archived
Delegated to: Matthieu Baerts
Headers show
Series .topmsg: mptcp: parse and emit MP_CAPABLE option according to v1 spec | expand

Commit Message

Mat Martineau Dec. 13, 2019, 12:58 a.m. UTC 
Use newly assigned RFC number, fix up line wrapping.

Signed-off-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
---
 .topmsg | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
diff mbox series

Patch

diff --git a/.topmsg b/.topmsg
index 74ccce6fb301..dfa69fc7582d 100644
--- a/.topmsg
+++ b/.topmsg
@@ -1,16 +1,16 @@ 
 From: Christoph Paasch <cpaasch@apple.com>
-Subject: [PATCH] mptcp: parse and emit MP_CAPABLE option according to v1 spec.
+Subject: [PATCH] mptcp: parse and emit MP_CAPABLE option according to v1 spec
 
 This implements MP_CAPABLE options parsing and writing according
-to the RFC 6824 bis - MPTCP v1.
+to RFC 6824 bis / RFC 8684: MPTCP v1.
+
 Local key is sent on syn/ack, and both keys are sent on 3rd ack.
-MP_CAPABLE messages len are updated accordingly.
-We need the skbuff to emit correctly the above, so we push the skbuff
-struct as an argument all the way from tcp code to the relevant mptcp
-callbacks.
+MP_CAPABLE messages len are updated accordingly. We need the skbuff to
+correctly emit the above, so we push the skbuff struct as an argument
+all the way from tcp code to the relevant mptcp callbacks.
 
 When processing incoming MP_CAPABLE + data, build a full blown DSS-like
-map info, to simplify later processing.
-On child socket creation, we need to record the remote key, if available.
+map info, to simplify later processing.  On child socket creation, we
+need to record the remote key, if available.
 
 Signed-off-by: Christoph Paasch <cpaasch@apple.com>