Re: [tcpm] tcp-security: Request for feedback on the outline of the document

Fernando Gont <> Wed, 09 September 2009 05:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5EF423A6804 for <>; Tue, 8 Sep 2009 22:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[AWL=0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OvRWeB5EnMqZ for <>; Tue, 8 Sep 2009 22:35:56 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1D0343A672F for <>; Tue, 8 Sep 2009 22:35:55 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 8409B6B681C; Wed, 9 Sep 2009 02:36:32 -0300 (ART)
Received: from [] ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id n895aNsf027772; Wed, 9 Sep 2009 02:36:24 -0300
Message-ID: <>
Date: Wed, 09 Sep 2009 02:36:21 -0300
From: Fernando Gont <>
User-Agent: Thunderbird (Windows/20090812)
MIME-Version: 1.0
References: <><> <><> <> <>
In-Reply-To: <>
X-Enigmail-Version: 0.95.7
OpenPGP: id=D076FFF1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 ( []); Wed, 09 Sep 2009 02:36:31 -0300 (ART)
Cc:,, touch@ISI.EDU
Subject: Re: [tcpm] tcp-security: Request for feedback on the outline of the document
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 09 Sep 2009 05:35:57 -0000

Hello, Toby,

Comments in-line...

> I think there needs to be some form of hum relating to this. There seems
> to be a relatively small number of people expressing relatively strong
> opinions on this document that are clearly incompatible. One key thing,
> regardless of how we actually decide to split the work, Fernando's
> current ToC is too long... 3 pages of ToC is excessive. 

For the most part it's a three-page ToC because it's a 130+ page
document. So no matter how the sections are reorganized, I don't think
the ToC will get much shorter.....

> I think the
> sections aren't grouped at a high enough level (e.g. connection
> establishment and tear-down could be in one section on connection
> management, 

I have no problem with this. Probably the only drawback is that the
corresponding sections will have a depth of four sections (i.e. one more
level). But that shouldn't be a problem. Please let me know if you still
feel this would improve the document, and I'll apply this change.

> buffer management and re-assembly could probably be grouped
> into memory management, etc). 

If you are referring to Section 7 and Section 8, one might argue that
those are two different issues. Buffer management is memory management.
Segment reassembly algorithm (Section 8) is about e.g., what you do if
you get segments that overlap (which does not really have anything to do
with how you manage memory). Nevertheless, if you have any specific
proposal on how to merge these two sections, please let me know.


Kind regards,
Fernando Gont
e-mail: ||
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1