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

"Tom Petch" <nwnetworks@dial.pipex.com> Tue, 25 September 2007 18:11 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 1IaEsL-0000vt-7L; Tue, 25 Sep 2007 14:11:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IaEsK-0000vo-9Q for tcpm@ietf.org; Tue, 25 Sep 2007 14:11:12 -0400
Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IaEsE-0005Gn-2z for tcpm@ietf.org; Tue, 25 Sep 2007 14:11:12 -0400
Received: from pc6 (1Cust238.tnt29.lnd3.gbr.da.uu.net [62.188.120.238]) by astro.systems.pipex.net (Postfix) with SMTP id D2B95E0007D0; Tue, 25 Sep 2007 19:09:32 +0100 (BST)
Message-ID: <05fb01c7ff95$ed6cf7e0$0601a8c0@pc6>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: <mallman@icir.org>, <tcpm@ietf.org>
References: <20070924174444.F2C662A7182@lawyers.icir.org>
Subject: Re: [tcpm] tcpsecure: how strong to recommend?
Date: Tue, 25 Sep 2007 16:47:32 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Score: -98.6 (---------------------------------------------------)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Cc:
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Tom Petch <nwnetworks@dial.pipex.com>
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>
Errors-To: tcpm-bounces@ietf.org

all SHOULDs (I was not at the meeting)

I have been persuaded in the past, during IETF Last Calls, that  MAY might as
well be MAY NOT in which case it conveys very little.  If it is worth expressing
in an RFC, then it is worth a SHOULD.

Tom Petch


----- Original Message -----
From: "Mark Allman" <mallman@icir.org>
To: <tcpm@ietf.org>
Sent: Monday, September 24, 2007 7:44 PM
Subject: [tcpm] tcpsecure: how strong to recommend?


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


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