Re: [tcpm] Comments draft-ietf-tcpm-rtorestart-06.txt

"Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com> Thu, 09 April 2015 16:13 UTC

Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA271A885B for <tcpm@ietfa.amsl.com>; Thu, 9 Apr 2015 09:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 THAISsr3Uj_E for <tcpm@ietfa.amsl.com>; Thu, 9 Apr 2015 09:13:24 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 351381A8869 for <tcpm@ietf.org>; Thu, 9 Apr 2015 09:13:24 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (unknown [135.239.2.42]) by Websense Email Security Gateway with ESMTPS id C71735CC1C39; Thu, 9 Apr 2015 16:13:19 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id t39GCp5N007138 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Apr 2015 18:13:21 +0200
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.102]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Thu, 9 Apr 2015 18:12:59 +0200
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Thread-Topic: [tcpm] Comments draft-ietf-tcpm-rtorestart-06.txt
Thread-Index: AQHQcthi18OtKPJvV0GQAv07ZswCDZ1E18dQ
Date: Thu, 09 Apr 2015 16:12:59 +0000
Message-ID: <655C07320163294895BBADA28372AF5D16C84CD8@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <20150408135752.3890.64572.idtracker@ietfa.amsl.com> <552697FD.2070807@erg.abdn.ac.uk>
In-Reply-To: <552697FD.2070807@erg.abdn.ac.uk>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tcpm/UB9fO6Wn5u3Pc9eUHEaH7u98OtY>
Cc: "tcpm@ietf.org" <tcpm@ietf.org>
Subject: Re: [tcpm] Comments draft-ietf-tcpm-rtorestart-06.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 09 Apr 2015 16:13:25 -0000

> A few quick comments on this latest revision:
> 
> * I believe this is a sender-side only change, but the abstract doesn't
> explicitly say this, i.e. "This document specifies a sender-only
> modification to TCP and SCTP "

Good point - this could help with reviews
 
> * The introduction does not explain why the WG has requested this to be
> experimental (is it the maturity or options of the algorithm;
> deployment
> experience; etc), e.g. "The specification in this draft is classified
> as
> "Experimental" pending experience with deployed implementations of the
> methods."

This is a valid concern, but I wonder if there is a more future-proof wording.

For similar TCPM documents we explicitly noted what further experimentation would be useful. In case of draft-ietf-tcpm-rtorestart, some of these experiments directly follow from some of the content in Section 5.

IMHO, the areas in which further experimentation is needed could be stated more explicitly, e.g., in the introduction with a reference to Section 5. This would also explain the status while being valid even if deployment experience increases in future.

Michael

> * Section 4 specifies the experimental algorithm, it may be useful to
> add a sentence at the start of this section that explicitly says this
> "This section specifies the modifications required", to contrast with
> the informative material in section 3,5,6.
> 
> * I have reviewed section 7, and this seems to me to address the
> SCTP-related comments received at the Dallas IETF meeting.
> 
> * To avoid doubt by security reviewers, You could possibly also note
> this in the security considerations section:  i.e. "This document
> specifies an experimental sender-only modification to TCP and SCTP."
> 
> Gorry