Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13.txt
Joe Touch <touch@isi.edu> Fri, 24 May 2013 18:39 UTC
Return-Path: <touch@isi.edu>
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 C452411E80E6 for <tcpm@ietfa.amsl.com>;
Fri, 24 May 2013 11:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.682
X-Spam-Level:
X-Spam-Status: No,
score=-103.682 tagged_above=-999 required=5 tests=[AWL=-1.083, BAYES_00=-2.599,
USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdjMv1NMwDts for
<tcpm@ietfa.amsl.com>; Fri, 24 May 2013 11:39:39 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by
ietfa.amsl.com (Postfix) with ESMTP id 052E911E80A2 for <tcpm@ietf.org>;
Fri, 24 May 2013 11:39:38 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated
bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4OIcZgq027132
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
Fri, 24 May 2013 11:38:35 -0700 (PDT)
Message-ID: <519FB3A2.4050502@isi.edu>
Date: Fri, 24 May 2013 11:38:26 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Olivier.Bonaventure@uclouvain.be
References: <20130518155753.17946.96581.idtracker@ietfa.amsl.com>
<CAK6E8=d_LTZgnGAncdWDAi+7ebd3Lo5aevPeGG0=KSbBMeBhcg@mail.gmail.com>
<519A8322.6030405@isi.edu> <519F1D68.604@uclouvain.be>
In-Reply-To: <519F1D68.604@uclouvain.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Subject: Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 24 May 2013 18:39:44 -0000
FWIW, I was not opening any new issues; I was clarifying the text only. I don't believe my new text changes any of the meaning from the previous intended version; IMO it only better handles ambiguities. We discussed the reason for these requirements before. Joe On 5/24/2013 12:57 AM, Olivier Bonaventure wrote: > Joe, Yuchung, > >> I suggest clarifying this as: >> >> Once TSopt has been successfully negotiated (sent and received) >> during the <SYN>, <SYN,ACK> exchange, TSopt MUST be sent in every >> non-<RST> segment for the duration of the connection, and SHOULD be >> sent in a <RST> segment (see Section 4.2 for details). > > I fail to see the rationale for forcing a TCP connection to always send > the TSopt in every segment. The timestamp aids to estimate the rtt and > provides PAWS for long connections. Given the size of the TCP option > space, we should not force the utilisation of the TSopt in all segments. > Consider a TCP implementation that supports SACK, RFC1323 and TCP-AO or > Multipath TCP. When this implementation sends an ACK segment that > contains a SACK, is it better to encode a long SACK block or to use > option space to encode a timestamp ? I'd vote for providing a timestamp > from time to time and reporting accurate SACK blocks. > > > > If a non- > > <RST> segment is received without a TSopt, a TCP MUST drop the > > segment > > and MAY also send an <ACK> for the last in-sequence segment. > > A TCP MUST NOT abort a TCP connection because any segment lacks > > an expected TSopt. > > Dropping segments that do not contain the TSopt is excessive. There are > on the Internet middleboxes that coalesce or split segments. While doing > that, they may remove options. Dropping a segment because it does not > contain the TSopt which is only informative appears overkill to me. > Dropping a segment that does not contain the negotiated TCP-AO option > makes sens, but not for the TSopt. > > > Olivier > >
- [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13.txt internet-drafts
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Yuchung Cheng
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Yuchung Cheng
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Scheffenegger, Richard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Olivier Bonaventure
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Scheffenegger, Richard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Yuchung Cheng
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Christoph Paasch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Scheffenegger, Richard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Scheffenegger, Richard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Scheffenegger, Richard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… l.wood
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Fernando Gont
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Tim Shepard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Scheffenegger, Richard
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Andre Oppermann
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Yuchung Cheng
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Jakob Heitz
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Pasi Sarolahti
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch
- Re: [tcpm] I-D Action: draft-ietf-tcpm-1323bis-13… Joe Touch