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

Joe Touch <touch@ISI.EDU> Thu, 27 August 2009 05:48 UTC

Return-Path: <touch@ISI.EDU>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1DA73A6D5A for <tcpm@core3.amsl.com>; Wed, 26 Aug 2009 22:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l95dLaJbAh+q for <tcpm@core3.amsl.com>; Wed, 26 Aug 2009 22:48:36 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id DD85128C101 for <tcpm@ietf.org>; Wed, 26 Aug 2009 22:48:26 -0700 (PDT)
Received: from [192.168.1.46] (pool-71-106-88-10.lsanca.dsl-w.verizon.net [71.106.88.10]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n7R5loEl017581; Wed, 26 Aug 2009 22:47:51 -0700 (PDT)
Message-ID: <4A961E05.4020100@isi.edu>
Date: Wed, 26 Aug 2009 22:47:49 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
References: <4A8CBF98.1070809@gont.com.ar><4A8D939E.9050008@isi.edu> <C304DB494AC0C04C87C6A6E2FF5603DB479B7E7359@NDJSSCC01.ndc.nasa.gov> <4A94307E.2080209@gont.com.ar><4A943CEA.4000905@isi.edu> <4A944A03.1090803@gont.com.ar> <4A944B56.5080200@isi.edu> <AEDCAF87EEC94F49BA92EBDD49854CC70CC81561@E03MVZ1-UKDY.domain1.systemhost.net> <4A960E85.8000608@gont.com.ar>
In-Reply-To: <4A960E85.8000608@gont.com.ar>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm@ietf.org
Subject: Re: [tcpm] tcp-security: Request for feedback on the outline of the document
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 27 Aug 2009 05:48:37 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Fernando Gont wrote:
> Hello, Toby,
> 
>> I definitely agree that Joe's structure looks more organised. As he
>> points out, it is impossible to create a comprehensive structure that
>> removes all overlap or contradictions. If you want this document to
>> succeed (rather than join an ever-growing pile of RFCs that no-one
>> outside the IETF have even read) then making it easily readable has
>> to be the first requirement. A significant part of readability is the
>> structure used to present the data in the document. 
> 
> Before bringing this document to the IETF, most major vendors (including
> Cisco, Juniper, Microsoft, and others) received a copy of it, and had
> the chance to review it.

It'd be useful to get input from a high-end server vendor. I would value
their input on TCP security/performance issues more.

As to input from outside the IETF, they're welcome to participate here.
The feedback from the meeting in Stockholm was to start with an outline,
and work the outline first, which is what I thought we were doing.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkqWHgUACgkQE5f5cImnZrurygCdFS+NJhwcy/1zDEd/SVmMrFpP
fcYAoNRkBl7HTCbLU4FUTULDWqXVFsk8
=fXjO
-----END PGP SIGNATURE-----