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

Joe Touch <touch@ISI.EDU> Thu, 03 September 2009 23:43 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 959F33A6853 for <tcpm@core3.amsl.com>; Thu, 3 Sep 2009 16:43:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 WeIw7Fp8+S-1 for <tcpm@core3.amsl.com>; Thu, 3 Sep 2009 16:43:17 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 480B33A686A for <tcpm@ietf.org>; Thu, 3 Sep 2009 16:43:14 -0700 (PDT)
Received: from [75.214.129.204] (204.sub-75-214-129.myvzw.com [75.214.129.204]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n83Ng6Yf017350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Sep 2009 16:42:10 -0700 (PDT)
Message-ID: <4AA0544E.5060802@isi.edu>
Date: Thu, 03 Sep 2009 16:42:06 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Lars Eggert <lars.eggert@nokia.com>
References: <200908262238.AAA06336@TR-Sys.de><4A9624CB.6040203@isi.edu> <4A9894C3.4020300@gont.com.ar><4A9AB5C2.4090209@isi.edu> <4A9CB254.7050802@gont.com.ar> <AEDCAF87EEC94F49BA92EBDD49854CC70CDCE9FF@E03MVZ1-UKDY.domain1.systemhost.net> <4A9FFF8C.7040001@gont.com.ar> <E25D669B-F0B2-4AED-B8B3-81E39FB2FEE5@nokia.com>
In-Reply-To: <E25D669B-F0B2-4AED-B8B3-81E39FB2FEE5@nokia.com>
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: "ah@tr-sys.de" <ah@tr-sys.de>, "tcpm@ietf.org" <tcpm@ietf.org>, Fernando Gont <fernando@gont.com.ar>
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, 03 Sep 2009 23:43:18 -0000

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



Lars Eggert wrote:
> On 2009-9-3, at 20:40, Fernando Gont wrote:
> So if this is entirely aimed at implementers shouldn't that be
>>> explicitly stated in the title? I appreciate that in theory BCP is meant
>>> to imply implementation guidance but this might be more appropriately
>>> titled something like "Implementers guidelines for mitigating TCP
>>> security threats" or "Guidance on secure implementation of TCP"
>>
>> Point taken. How about "Guidance on secure implementation of the
>> Transmission Control Protocol (TCP)"?
> 
> Personally, I'd avoid the word "secured" in the title and maybe in other
> places in the document. Maybe use "hardened" or "robust" or
> "attack-resistant" or something, but "secure" isn't quite accurate

Guidance to Mitigate TCP Implementation-Based Vulnerabilities

This makes more sense to me if this is indeed focused on
implementation-based vulnerabilities, rather than general security threats

If this is all the ways an implementer can avoid security threats in
general, then I reiterate my suggestion that we need a security
vulnerabilities doc.

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

iEYEARECAAYFAkqgVE4ACgkQE5f5cImnZrvXfwCdGZNJw5Wr0KsxR2N8zf0gADzQ
mrIAn3/Tpr6tAazbnzX3tD80qQFLihrP
=lejH
-----END PGP SIGNATURE-----