[tcpm] strength of tcpsecure recommendation
Mark Allman <mallman@icir.org> Tue, 03 April 2007 20:27 UTC
Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYpbD-0001f4-FW; Tue, 03 Apr 2007 16:27:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYpbC-0001es-74 for tcpm@ietf.org; Tue, 03 Apr 2007 16:27:26 -0400
Received: from pork.icsi.berkeley.edu ([192.150.186.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYpb9-0003I5-Qx for tcpm@ietf.org; Tue, 03 Apr 2007 16:27:26 -0400
Received: from guns.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by pork.ICSI.Berkeley.EDU (8.12.11.20060308/8.12.11) with ESMTP id l33KAasO002848 for <tcpm@ietf.org>; Tue, 3 Apr 2007 13:10:36 -0700
Received: from lawyers.icir.org (adsl-69-222-35-58.dsl.bcvloh.ameritech.net [69.222.35.58]) by guns.icir.org (Postfix) with ESMTP id 7BD4898971C for <tcpm@ietf.org>; Tue, 3 Apr 2007 16:10:30 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 85DAE1C3901 for <tcpm@ietf.org>; Tue, 3 Apr 2007 16:10:07 -0400 (EDT)
To: tcpm@ietf.org
From: Mark Allman <mallman@icir.org>
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Play Guitar
MIME-Version: 1.0
Date: Tue, 03 Apr 2007 16:10:07 -0400
Message-Id: <20070403201007.85DAE1C3901@lawyers.icir.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Subject: [tcpm] strength of tcpsecure recommendation
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: mallman@icir.org
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0740250599=="
Errors-To: tcpm-bounces@ietf.org
Folks- I'd like to try to be a bit systematic about figuring out how to proceed with the tcpsecure i-d and so I have cooked a poll below. The essential questions on the table is the mitigations ought to be labeled as SHOULD or MAY and whether these labels ought to be conditioned or not. We have had some good conversation on the topic and lots of points have been aired (how baked these solutions are, IPR, cost v. benefit, etc.). So, I am asking that the answers to the following questions be succinct and not rehash a bunch of previous argument. If you feel you have a **new** point then that is clearly fine. I am trying to get a good read of the WG here and so even if you have clearly aired opinions before, please take the minute and answer these questions. (Note that SHOULD and MAY are clearly not the only choices. If you want to vote for MUST or MUST NOT then that is fine, even though they are not listed as choices below. If you do, please then do provide some justification.) The questions then ... (1) (a) Do you believe the draft should allow the "blind reset attack using the RST bit" mitigation described in section 3 of the document as a SHOULD or a MAY? (b) Should we apply a condition to the recommendation? If so, please state the condition you'd like to see very succinctly. (2) (a) Do you believe the draft should allow the "blind reset attack using the SYN bit" mitigation described in section 4 of the document as a SHOULD or a MAY? (b) Should we apply a condition to the recommendation? If so, please state the condition you'd like to see very succinctly. (3) (a) Do you believe the draft should allow the "blind data injection attack" mitigation described in section 5 of the document as a SHOULD or a MAY? (b) Should we apply a condition to the recommendation? If so, please state the condition you'd like to see very succinctly. Thanks in advance for the input! allman
_______________________________________________ tcpm mailing list tcpm@ietf.org https://www1.ietf.org/mailman/listinfo/tcpm
- [tcpm] strength of tcpsecure recommendation Mark Allman
- [tcpm] Re: strength of tcpsecure recommendation Mark Allman
- RE: [tcpm] strength of tcpsecure recommendation Mitesh Dalal (mdalal)