Re: [tcpm] [Technical Errata Reported] RFC5961 (5068)
Mirja Kuehlewind <ietf@kuehlewind.net> Wed, 04 March 2020 10:40 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 218F53A0C4E for <tcpm@ietfa.amsl.com>; Wed, 4 Mar 2020 02:40:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 XEuiaBOH9xeH for <tcpm@ietfa.amsl.com>; Wed, 4 Mar 2020 02:40:37 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B09A3A0C1F for <tcpm@ietf.org>; Wed, 4 Mar 2020 02:40:37 -0800 (PST)
Received: from p200300dee7239a0084809b28d0f22131.dip0.t-ipconnect.de ([2003:de:e723:9a00:8480:9b28:d0f2:2131]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1j9RS1-0003kB-4b; Wed, 04 Mar 2020 11:40:29 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <20170712170307.B28CCB81EBE@rfc-editor.org>
Date: Wed, 04 Mar 2020 11:40:28 +0100
Cc: ananth@cisco.com, randall@lakerest.net, mdalal@cisco.com, "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>, Michael Tuexen <tuexen@fh-muenster.de>, Yoshifumi Nishida <nishida@sfc.wide.ad.jp>, Wesley Eddy <wes@mti-systems.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A47DAAD-9579-42C8-A90C-B7A62557079F@kuehlewind.net>
References: <20170712170307.B28CCB81EBE@rfc-editor.org>
To: tcpm IETF list <tcpm@ietf.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1583318437;81360368;
X-HE-SMSGID: 1j9RS1-0003kB-4b
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/cWiv00dATxxvRQuEL3wvJWDrjrw>
Subject: Re: [tcpm] [Technical Errata Reported] RFC5961 (5068)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2020 10:40:41 -0000
Hi tcpm, I’m planning to mark the errata below as verified. Please let me know if there are any concern about this! Mirja > On 12. Jul 2017, at 19:03, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC5961, > "Improving TCP's Robustness to Blind In-Window Attacks". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata/eid5068 > > -------------------------------------- > Type: Technical > Reported by: Wesley Eddy <wes@mti-systems.com> > > Section: 3.2 > > Original Text > ------------- > [RFC0793] currently requires handling of a segment with the RST bit > when in a synchronized state to be processed as follows: > ... > Instead, implementations SHOULD implement the following steps in > place of those specified in [RFC0793] (as listed above). > > Corrected Text > -------------- > [RFC0793] currently requires handling of a segment with the RST bit > when in a synchronized state to be processed as follows: > ... > Instead, when in either a synchronized state or SYN-RECEIVED, > implementations SHOULD implement the following steps in place of > those specified in [RFC0793] (as listed above, for the synchronized > states). Note that transition from SYN-RECEIVED to either LISTEN or > CLOSED and user signaling is still subject to whether the connection > was originated by a passive OPEN (as described in RFC 793). > > > Notes > ----- > The text in section 3.2 begins by stating a change from RFC 793 for RST bit handling "when in a synchronized state" (which means all states except for LISTEN, SYN-SENT, and SYN-RECEIVED). Later in the section, the same change is described more loosely and text states that it's applicable "In all states except SYN-SENT", and separate behavior is provided for SYN-SENT, but the earlier text leaves uncertainty if the former is supposed to apply to SYN-RECEIVED as well, since the earlier text in the section section begins by discussing only "synchronized" states. > > Since the check is totally valid for SYN-RECEIVED, and the behavior in steps 1, 2, and 3 are valid for SYN-RECEIVED, it seems appropriate to make sure this is clarified in the earlier text. > > 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. > > -------------------------------------- > RFC5961 (draft-ietf-tcpm-tcpsecure-13) > -------------------------------------- > Title : Improving TCP's Robustness to Blind In-Window Attacks > Publication Date : August 2010 > Author(s) : A. Ramaiah, R. Stewart, M. Dalal > Category : PROPOSED STANDARD > Source : TCP Maintenance and Minor Extensions > Area : Transport > Stream : IETF > Verifying Party : IESG
- [tcpm] [Technical Errata Reported] RFC5961 (5068) RFC Errata System
- Re: [tcpm] [Technical Errata Reported] RFC5961 (5… Mirja Kuehlewind