Re: [Tsvwg] WGLC for draft-ietf-tsvwg-sctpthreat-01 starts NOW

Lars Eggert <lars.eggert@netlab.nec.de> Wed, 25 October 2006 13:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcj4H-0000mb-3U; Wed, 25 Oct 2006 09:45:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gcj4F-0000mJ-Mf for tsvwg@ietf.org; Wed, 25 Oct 2006 09:45:15 -0400
Received: from smtp1.netlab.nec.de ([195.37.70.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gcj4C-0000d4-6y for tsvwg@ietf.org; Wed, 25 Oct 2006 09:45:15 -0400
Received: from localhost (localhost.office [127.0.0.1]) by smtp1.netlab.nec.de (Postfix) with ESMTP id 19901A00016E; Wed, 25 Oct 2006 15:49:51 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office)
Received: from smtp1.netlab.nec.de ([127.0.0.1]) by localhost (atlas2.office [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6NSn5oz0t6D; Wed, 25 Oct 2006 15:49:50 +0200 (CEST)
Received: from mx1.office (mx1.office [10.1.1.23]) by smtp1.netlab.nec.de (Postfix) with ESMTP id D0C72A000318; Wed, 25 Oct 2006 15:49:50 +0200 (CEST)
Received: from n-eggert.office ([10.1.1.112]) by mx1.office over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Wed, 25 Oct 2006 15:39:20 +0200
Received: from [127.0.0.1] (localhost [127.0.0.1]) by n-eggert.office (Postfix) with ESMTP id 7252D25CE32; Wed, 25 Oct 2006 15:39:20 +0200 (CEST)
In-Reply-To: <4.3.2.7.2.20061015030131.036c68a0@email.cisco.com>
References: <4.3.2.7.2.20061015030131.036c68a0@email.cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: multipart/signed; micalg="sha1"; boundary="Apple-Mail-9-940248087"; protocol="application/pkcs7-signature"
Message-Id: <3F1BB508-77A1-4DF4-A48D-02FF81042E8A@netlab.nec.de>
From: Lars Eggert <lars.eggert@netlab.nec.de>
Subject: Re: [Tsvwg] WGLC for draft-ietf-tsvwg-sctpthreat-01 starts NOW
Date: Wed, 25 Oct 2006 15:39:17 +0200
To: tsvwg <tsvwg@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-OriginalArrivalTime: 25 Oct 2006 13:39:20.0581 (UTC) FILETIME=[F9965B50:01C6F83A]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b132cb3ed2d4be2017585bf6859e1ede
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

   This document talks about the SCTP implementors' guide a lot and how
   it "makes changes" to SCTP to fix the threats described here. The
   guide is not a specification - I assume 2960bis will also include
   these fixes? If so, it should be referred to instead of (or at least
   in addition to) the guide.

   The sections labeled "Errata" aren't errata ("a list of corrected
   errors"), they often contain a further analysis of the attack vector.
   Suggest to pick a different heading.

   The sections labeled "Countermeasure" often don't describe
   countermeasures but instead only offer observations about the attack
   (4.3) or partial mitigation (6.3). Suggest to pick a different
   headings for those cases.


Section 2.3., paragraph 1:
 >    HEARTBEAT-ACK the random nonce MUST match the value sent in the

   s/MUST/must/ (is the only 2119 term in the document)


Section 2.3., paragraph 2:
 >    will prevent an attacker from generating false HEARTBEAT-ACK's  
with

   Nit: s/HEARTBEAT-ACK's/HEARTBEAT-ACKs/


Section 4.2., paragraph 2:
 >       local lan is concerned.

   Nit: s/local lan/LAN/

-- 
Lars Eggert                                     NEC Network Laboratories