Re: [OPSEC] Fwd: Security Assessment of the Transmission Control Protocol (TCP)
Jari Arkko <jari.arkko@piuha.net> Sat, 14 February 2009 11:24 UTC
Return-Path: <jari.arkko@piuha.net>
X-Original-To: opsec@core3.amsl.com
Delivered-To: opsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 66ED03A69F4; Sat, 14 Feb 2009 03:24:24 -0800 (PST)
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=[AWL=0.000, 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 xGJdBf5qRaHA; Sat, 14 Feb 2009 03:24:23 -0800 (PST)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 6FC513A68AB; Sat, 14 Feb 2009 03:24:23 -0800 (PST)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id AF9B419872A; Sat, 14 Feb 2009 13:24:27 +0200 (EET)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 4AC611986EF; Sat, 14 Feb 2009 13:24:27 +0200 (EET)
Message-ID: <4996A99C.40003@piuha.net>
Date: Sat, 14 Feb 2009 13:23:08 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
References: <4994A4EB.5030607@gmail.com> <0B030ADA-F621-4FDF-9CAF-23A27C16E26B@multicasttech.com> <49961BDB.9030905@network-heretics.com> <49963A14.1090106@bogus.com> <49967CF9.7090105@network-heretics.com>
In-Reply-To: <49967CF9.7090105@network-heretics.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Mailman-Approved-At: Sat, 14 Feb 2009 07:50:08 -0800
Cc: opsec wg mailing list <opsec@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: [OPSEC] Fwd: Security Assessment of the Transmission Control Protocol (TCP)
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Feb 2009 11:24:24 -0000
Keith, Joel, >>> It's difficult to imagine that these things could be adequately captured >>> in a static document, for TCP or any other protocol, because new threats >>> and countermeasures continue to be identified decades after the base >>> protocol is well-settled. Maybe something like an expanded version of >>> the RFC Editor's errata pages would be more appropriate? >>> >> One might imagine an informational document which was routinely >> obsoleted by future iterations. Keeping it tractable is a product of >> necessarily limiting the scope. >> I am in favor of publishing things like these in informational RFCs. And no, we should not shoot for completeness, for obvious reasons. Jari
- Re: [OPSEC] Fwd: Security Assessment of the Trans… Joel Jaeggli
- Re: [OPSEC] Fwd: Security Assessment of the Trans… Keith Moore
- Re: [OPSEC] Fwd: Security Assessment of the Trans… Jari Arkko
- Re: [OPSEC] Fwd: Security Assessment of the Trans… TSG
- [OPSEC] Security Assessment of the Transmission C… Fernando Gont