idnits 2.17.1 draft-floyd-tcp-reset-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 BCP 60 4 RFC 3360 6 Title: Inappropriate TCP Resets Considered Harmful 7 Author(s): S. Floyd 8 Status: Best Current Practice 9 Date: August 2002 10 Mailbox: floyd@icir.org 11 Pages: 19 12 Characters: 46748 13 SeeAlso: BCP 60 15 I-D Tag: draft-floyd-tcp-reset-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3360.txt 19 This document is being written because there are a number of 20 firewalls in the Internet that inappropriately reset a TCP connection 21 upon receiving certain TCP SYN packets, in particular, packets with 22 flags set in the Reserved field of the TCP header. In this document 23 we argue that this practice is not conformant with TCP standards, and 24 is an inappropriate overloading of the semantics of the TCP reset. 25 We also consider the longer-term consequences of this and similar 26 actions as obstacles to the evolution of the Internet infrastructure. 28 This document specifies an Internet Best Current Practices for the 29 Internet Community, and requests discussion and suggestions for 30 improvements. Distribution of this memo is unlimited. 32 This announcement is sent to the IETF list and the RFC-DIST list. 33 Requests to be added to or deleted from the IETF distribution list 34 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 35 added to or deleted from the RFC-DIST distribution list should 36 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 38 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 39 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 40 help: ways_to_get_rfcs. For example: 42 To: rfc-info@RFC-EDITOR.ORG 43 Subject: getting rfcs 45 help: ways_to_get_rfcs 47 Requests for special distribution should be addressed to either the 48 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 49 specifically noted otherwise on the RFC itself, all RFCs are for 50 unlimited distribution.echo 51 Submissions for Requests for Comments should be sent to 52 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 53 Authors, for further information.