IETF Logo Mail Archive

Re: Window Scale option

braden@isi.edu Tue, 05 May 1998 21:49 UTC

Delivery-Date: Tue, 05 May 1998 17:49:09 -0400
Return-Path: tcplw-relay@services.BSDI.COM
Received: from cnri.reston.va.us (ns.cnri.reston.va.us [132.151.1.1]) by ietf.org (8.8.5/8.8.7a) with ESMTP id RAA15979 for <ietf-archive@ietf.org>; Tue, 5 May 1998 17:49:08 -0400 (EDT)
Received: from services.BSDI.COM (services.BSDI.COM [205.230.225.19]) by cnri.reston.va.us (8.8.5/8.8.7a) with ESMTP id RAA10304 for <IETF-archive@cnri.reston.va.us>; Tue, 5 May 1998 17:51:35 -0400 (EDT)
Received: (from daemon@localhost) by services.BSDI.COM (8.8.7/8.8.8) id PAA24243 for tcplw-list@bsdi.com; Tue, 5 May 1998 15:48:49 -0600 (MDT)
Received: from mailfilter.bsdi.com (mailfilter.BSDI.COM [205.230.225.21]) by services.BSDI.COM (8.8.7/8.8.8) with ESMTP id PAA24203 for <tcplw@bsdi.com>; Tue, 5 May 1998 15:48:47 -0600 (MDT)
From: braden@isi.edu
Received: from zephyr.isi.edu (zephyr.isi.edu [128.9.160.160]) by mailfilter.bsdi.com (BSDI-MF 1.0) with ESMTP id PAA29856 for <tcplw@bsdi.com> env-from (braden@ISI.EDU); Tue, 5 May 1998 15:47:39 -0600 (MDT)
Received: from gra.isi.edu (gra.isi.edu [128.9.160.133]) by zephyr.isi.edu (8.8.7/8.8.6) with SMTP id OAA19308; Tue, 5 May 1998 14:48:42 -0700 (PDT)
Date: Tue, 05 May 1998 14:48:31 -0700
Posted-Date: Tue, 5 May 1998 14:48:31 -0700
Message-Id: <199805052148.AA21759@gra.isi.edu>
Received: by gra.isi.edu (5.65c/4.0.3-6) id <AA21759>; Tue, 5 May 1998 14:48:31 -0700
To: braden@isi.edu, mathis@psc.edu
Subject: Re: Window Scale option
Cc: tcplw@bsdi.com

  *> 
  *> I considered this approach, but the difficulty is that there is no
  *> distiction between "timestamp" and "timestamp reply".  Thus turning
  *> off timestamps requires having some way to discover that the other end
  *> isn't using them.  For example the value zero could be used to indicate
  *> that a reply is not needed.
  *> 

It isn't clear to me that any bad thing happens if one end simply
refrains from sending a TSopt even though it could send it.
The other end could take this as a signal to itself stop sending
TSopts.  (We would have to make sure this cannot confuse PAWS).

Bob

v2.23.0 | Report a Bug | By Email