TCP RST Diagnostic Paylaod

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 1 October 2022.¶

Copyright Notice

Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

A TCP connection [I-D.ietf-tcpm-rfc793bis] can be reset by a peer for various reasons, e.g., a received data does not correspond to an active connection. Also, a TCP connection can be reset by an on-path service function (e.g., CGN [RFC6888], NAT64 [RFC6146], firewall) for various reasons. Typically, a NAT function can generate an RST segment to notify the peers upon the expiry of the lifetime of the corresponding mapping entry or because an RST segment was received from a peer (Section 2.2 of [RFC7857]). A TCP connection can also be closed by a user or an application at any time. However, the peer that receives an RST segment does not have any hint about the reason that led to terminating the connection. Likewise, the application that relies upon such a TCP connection may not easily identify the reason for a connection closure. Troubleshooting such events at the terminal side that receives the RST segment may not be trivial.¶

This document fills this void by specifying a diagnostic payload that is returned in an RST segment. Returning such data is consistent with the provision in Section 3.5.3 of [I-D.ietf-tcpm-rfc793bis] for RST segments.¶

This document does not change the conditions under which an RST segment is generated (Section 3.5.2 of [I-D.ietf-tcpm-rfc793bis]).¶

The generic procedure for processing an RST segment is specified in Section 3.5.3 of [I-D.ietf-tcpm-rfc793bis]. Only the deviation from that procedure to identify and validate an enclosed diagnostic payload is provided in Section 3.¶

A peer that receives a diagnostic payload may pass that information to the local application in addition to the information (MUST-12) described in Section 3.6 of [I-D.ietf-tcpm-rfc793bis]. That information may also be logged locally, unless a local policy specifies otherwise.¶

The first version of the specification is meant to discuss the format and the overall approach to ease maintaining the list of codes while allowing for adding new codes as needed in the future. As such, this first version of the specification does not include a comprehensive list of error codes. These codes will be completed in future versions (Table 1).¶

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶

This document makes use of the terms defined in Section 4 of [I-D.ietf-tcpm-rfc793bis].¶

3. RST Diagnostic Payload

In order to unambiguously identify an RST diagnostic payload that is compliant with the present specification, the payload MUST use the I-JSON message format [RFC7493]. The following parameters are defined:¶

rc:

Stands for "Reason Code". This parameter takes a value from the "TCP Failure Causes" registry (Section 4.1). This parameter is omitted if none of the values maintained by IANA can be used to report a reset failure cause.¶

rd:

Stands for "Reason Description". It includes a brief description of the reason code. This parameter SHOULD NOT be included if a code that covers this error case is already registered in Section 4.1. This parameter is useful only for codes that are not yet registered or application-specific codes.¶

At least one of the above parameters MUST be included in an RST diagnostic payload that is compliant with the present specification.¶

Figure 1 depicts an example of an RST diagnostic payload that is generated to inform the peer that the connection is reset because an ACK was received while the connection is still in the LISTEN state.¶

{
 "rc": 2
}

Figure 2 shows an example of an RST diagnostic payload that includes a free description to report a case that is not covered yet by the table maintained by IANA (Section 4.1).¶

{
 "rd": "brief human-readable description"
}

An RST diagnostic payload may be included by the peer that resets the connection or by an on-path service function. For example, the following payload can be returned by a NAT when a mapping entry expires (Figure 3).¶

{
 "rc": 8
}

4. IANA Considerations

5. Security Considerations

[I-D.ietf-tcpm-rfc793bis] discusses TCP-related security considerations. RST-specific attacks and their mitigation are discussed in Section 3.10.7.3 of [I-D.ietf-tcpm-rfc793bis].¶

In addition to these considerations, it is RECOMMENDED to control the size of acceptable diagnostic payload and keep it as brief as possible. Also, it is RECOMMENDED to avoid leaking privacy-related information as part of the diagnostic payload (e.g., including a description such as "user X resets explicitly the connection").¶

6. Acknowledgements

TBC.¶

Author's Address