Re: [tcpm] Is RFC1323bis' title still appropriate?
David Borman <dab@weston.borman.com> Fri, 15 November 2013 00:03 UTC
Return-Path: <dab@weston.borman.com>
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 62E4C11E8167 for <tcpm@ietfa.amsl.com>; Thu, 14 Nov 2013 16:03:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599]
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 6sAWOo6TA2Ub for <tcpm@ietfa.amsl.com>; Thu, 14 Nov 2013 16:02:57 -0800 (PST)
Received: from frantic.weston.borman.com (frantic.weston.borman.com [70.57.156.33]) by ietfa.amsl.com (Postfix) with ESMTP id 07ACA11E8165 for <tcpm@ietf.org>; Thu, 14 Nov 2013 16:02:55 -0800 (PST)
Received: from [127.0.0.1] (frantic.weston.borman.com [70.57.156.33]) by frantic.weston.borman.com (8.14.7/8.14.7) with ESMTP id rAF00Pau009495; Thu, 14 Nov 2013 18:00:27 -0600 (CST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: David Borman <dab@weston.borman.com>
In-Reply-To: <012C3117EDDB3C4781FD802A8C27DD4F25E96F48@SACEXCMBX02-PRD.hq.netapp.com>
Date: Thu, 14 Nov 2013 18:00:25 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <045012AD-1B4A-488A-B6D0-DC228CAA8380@weston.borman.com>
References: <8D54398D-C3A0-47D7-AAB5-922A8FB7B9E4@netapp.com> <012C3117EDDB3C4781FD802A8C27DD4F25E94B57@SACEXCMBX02-PRD.hq.netapp.com>, <alpine.DEB.2.02.1311141724400.14052@melkinpaasi.cs.helsinki.fi> <977B28B6-E1A6-4C89-AED3-FE14BBA057D4@netapp.com> <alpine.DEB.2.02.1311141827200.14052@melkinpaasi.cs.helsinki.fi> <012C3117EDDB3C4781FD802A8C27DD4F25E96F48@SACEXCMBX02-PRD.hq.netapp.com>
To: Richard Scheffenegger <rs@netapp.com>
X-Mailer: Apple Mail (2.1822)
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>
Subject: Re: [tcpm] Is RFC1323bis' title still appropriate?
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, 15 Nov 2013 00:03:01 -0000
I have mixed feelings about changing the name of the document, but the original title was from when it also included SACK, which was removed before 1323 was published. So I guess it makes some sense to clarify the title. On Nov 14, 2013, at 5:38 PM, Scheffenegger, Richard <rs@netapp.com> wrote: > Ilpo, > > Very well then. But I'll need a good speaker to tell me which one is most correct > > "TCP Window Scale and Timestamps option" (sounds like one combined option) > > "TCP Window Scale and Timestamps options" (sounds odd) This one. It sounds less odd if you switch it to “TCP Timestamps and Window Scale options”, but I think we want to keep Timestamps as the second one, given the pushback on it. But in any case, Options should be capitalized, because this is a document title. -David Borman > > "TCP Window Scale and TCP Timestamps options" (imho better) > > "TCP Window Scale option and TCP Timestamps option" (least ambiguity, but is this proper?) > > (prefixed with a "The"?) > > > PS: I'm glad that we have come to the point to discuss the title :) > > > Richard Scheffenegger > > >> -----Original Message----- >> From: Ilpo Järvinen [mailto:ilpo.jarvinen@helsinki.fi] >> Sent: Donnerstag, 14. November 2013 17:46 >> To: Scheffenegger, Richard >> Cc: Zimmermann, Alexander; David Borman; Pasi Sarolahti >> (pasi.sarolahti@iki.fi); tcpm@ietf.org Extensions >> Subject: Re: [tcpm] Is RFC1323bis' title still appropriate? >> >> On Thu, 14 Nov 2013, Scheffenegger, Richard wrote: >> >>> Would you like to see WS and TS in the title, or keep the old one? >> >> For some reason I've never liked RFC1323 title to begin with so I'd prefer >> the actual option names here. It would actually be rather misleading to >> say everything that benefits from WS today would have particularly "high >> performance". >> >> BTW, I just noticed that 1323 is also a counter-example: >> >> RFC1072 TCP Extensions for Long-Delay Paths >> RFC1185 TCP Extension for High-Speed Paths >> RFC1323 TCP Extensions for High Performance >> (+RFC2018 TCP Selective Acknowledgment Options) >> >> >> -- >> i. > _______________________________________________ > tcpm mailing list > tcpm@ietf.org > https://www.ietf.org/mailman/listinfo/tcpm
- [tcpm] Is RFC1323bis' title still appropriate? Zimmermann, Alexander
- Re: [tcpm] Is RFC1323bis' title still appropriate? Scheffenegger, Richard
- Re: [tcpm] Is RFC1323bis' title still appropriate? Zimmermann, Alexander
- Re: [tcpm] Is RFC1323bis' title still appropriate? Ilpo Järvinen
- Re: [tcpm] Is RFC1323bis' title still appropriate? Scheffenegger, Richard
- Re: [tcpm] Is RFC1323bis' title still appropriate? Ilpo Järvinen
- Re: [tcpm] Is RFC1323bis' title still appropriate? Scheffenegger, Richard
- Re: [tcpm] Is RFC1323bis' title still appropriate? David Borman
- Re: [tcpm] Is RFC1323bis' title still appropriate? l.wood
- Re: [tcpm] Is RFC1323bis' title still appropriate? Zimmermann, Alexander
- Re: [tcpm] Is RFC1323bis' title still appropriate? David Borman
- Re: [tcpm] Is RFC1323bis' title still appropriate? Mark Allman
- Re: [tcpm] Is RFC1323bis' title still appropriate? Scheffenegger, Richard