[multipathtcp] [Technical Errata Reported] RFC8684 (6609)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 14 June 2021 17:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 211F03A2C69 for <multipathtcp@ietfa.amsl.com>; Mon, 14 Jun 2021 10:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PjZqd2vQJRV6 for <multipathtcp@ietfa.amsl.com>; Mon, 14 Jun 2021 10:52:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A46603A2C65 for <multipathtcp@ietf.org>; Mon, 14 Jun 2021 10:52:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B15BFF4078D; Mon, 14 Jun 2021 10:51:36 -0700 (PDT)
To: alan.ford@gmail.com, costin.raiciu@cs.pub.ro, m.handley@cs.ucl.ac.uk, olivier.bonaventure@uclouvain.be, cpaasch@apple.com, martin.h.duke@gmail.com, Zaheduzzaman.Sarker@ericsson.com, philip.eardley@bt.com, nsd.ietf@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: erkrishna.khanal@gmail.com, multipathtcp@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210614175136.B15BFF4078D@rfc-editor.org>
Date: Mon, 14 Jun 2021 10:51:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/XRQMAEkSr08zQpnslvH-dIpIf8U>
X-Mailman-Approved-At: Mon, 14 Jun 2021 11:07:21 -0700
Subject: [multipathtcp] [Technical Errata Reported] RFC8684 (6609)
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 17:52:22 -0000

The following errata report has been submitted for RFC8684,
"TCP Extensions for Multipath Operation with Multiple Addresses".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6609

--------------------------------------
Type: Technical
Reported by: Krishna Khanal <erkrishna.khanal@gmail.com>

Section: B.3

Original Text
-------------
   initiator                                                    listener
       |                                                           |
       |    S  0(20) <MP_CAPABLE>, <TFO cookie>                    |
       | --------------------------------------------------------> |
       |                                                           |
       |    S. 0(0) ack 21 <MP_CAPABLE>                            |
       | <-------------------------------------------------------- |
       |                                                           |
       |    .  1(100) ack 21 <DSS ack=1 seq=1 ssn=1 dlen=100>      |
       | <-------------------------------------------------------- |
       |                                                           |
       |    .  21(0) ack 1 <MP_CAPABLE>                            |
       | --------------------------------------------------------> |
       |                                                           |
       |    .  21(20) ack 101 <DSS ack=101 seq=1 ssn=1 dlen=20>    |
       | --------------------------------------------------------> |
       |                                                           |

                    Figure 19: The Listener Supports TFO

Corrected Text
--------------
initiator                                                    listener
       |                                                           |
       |    S  0(20) <MP_CAPABLE>, <TFO cookie>                    |
       | --------------------------------------------------------> |
       |                                                           |
       |    S. 0(0) ack 21 <MP_CAPABLE>                            |
       | <-------------------------------------------------------- |
       |                                                           |
       |    .  1(100) ack 21 <DSS seq=1 ssn=1 dlen=100, M=1, A=0>  |
       | <-------------------------------------------------------- |
       |                                                           |
       |    .  21(0) ack 1 <MP_CAPABLE>                            |
       | --------------------------------------------------------> |
       |                                                           |
       |    .  21(20) ack 101 <DSS ack=101 seq=1 ssn=1 dlen=20>    |
       | --------------------------------------------------------> |
       |                                                           |

                    Figure 19: The Listener Supports TFO

Notes
-----
The example for TCP Fastopen with MPTCPv1 in RFC8684, Appendix-B.3 shows the listener sending an incorrect data-ack in its first data packet to the initiator sent immediately after its SYN-ACK.
At this point, the listener has not received the initiator's key, so it cannot generate the data-ack in it's response packets.
The correct behaviour would be to set flag 'A' to 0 and exclude sending data-ack until the initiator's key is received.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC8684 (draft-ietf-mptcp-rfc6824bis-18)
--------------------------------------
Title               : TCP Extensions for Multipath Operation with Multiple Addresses
Publication Date    : March 2020
Author(s)           : A. Ford, C. Raiciu, M. Handley, O. Bonaventure, C. Paasch
Category            : PROPOSED STANDARD
Source              : Multipath TCP
Area                : Transport
Stream              : IETF
Verifying Party     : IESG