IETF Logo Mail Archive

Re: [tcpm] tcpsecure: how strong to recommend?

Mark Allman <mallman@icir.org> Mon, 01 October 2007 12:48 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 1IcKhh-0000U8-C5; Mon, 01 Oct 2007 08:48:53 -0400
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1IcKhg-0000U3-8K for tcpm-confirm+ok@megatron.ietf.org; Mon, 01 Oct 2007 08:48:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IcKhf-0000Rb-TT for tcpm@ietf.org; Mon, 01 Oct 2007 08:48:51 -0400
Received: from pork.icsi.berkeley.edu ([192.150.186.19]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IcKhf-0002pd-IK for tcpm@ietf.org; Mon, 01 Oct 2007 08:48:51 -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 l91CmoFc014147; Mon, 1 Oct 2007 05:48:50 -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 5271E1018264; Mon, 1 Oct 2007 08:48:44 -0400 (EDT)
Received: from lawyers.icir.org (localhost [127.0.0.1]) by lawyers.icir.org (Postfix) with ESMTP id 32E282AB9B1; Mon, 1 Oct 2007 08:47:30 -0400 (EDT)
To: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
From: Mark Allman <mallman@icir.org>
Subject: Re: [tcpm] tcpsecure: how strong to recommend?
In-Reply-To: <0C53DCFB700D144284A584F54711EC580409FCEF@xmb-sjc-21c.amer.cisco.com>
Organization: ICSI Center for Internet Research (ICIR)
Song-of-the-Day: Car Phone
MIME-Version: 1.0
Date: Mon, 01 Oct 2007 08:47:30 -0400
Message-Id: <20071001124730.32E282AB9B1@lawyers.icir.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: tcpm@ietf.org
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="===============1879687522=="
Errors-To: tcpm-bounces@ietf.org

Hyperbole elided, but still trying to understand ...

> but
> saying that "SHOULD doesn't give leeway not to do something", is
> something which I would want to dis-agree.

If tcpsecure is a SHOULD then what would be an invalid reason for me to
exclude it from my implementation?

allman




_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email