Re: [TLS] Chatter on consensus

Martin Rex <mrex@sap.com> Wed, 27 January 2010 15:08 UTC

Return-Path: <mrex@sap.com>
X-Original-To: tls@core3.amsl.com
Delivered-To: tls@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8BCBF3A690B for <tls@core3.amsl.com>; Wed, 27 Jan 2010 07:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level:
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 4Sq2BIaOKYvJ for <tls@core3.amsl.com>; Wed, 27 Jan 2010 07:08:55 -0800 (PST)
Received: from smtpde03.sap-ag.de (smtpde03.sap-ag.de [155.56.68.140]) by core3.amsl.com (Postfix) with ESMTP id 9BE453A68C4 for <tls@ietf.org>; Wed, 27 Jan 2010 07:08:55 -0800 (PST)
Received: from mail.sap.corp by smtpde03.sap-ag.de (26) with ESMTP id o0RF98W1021223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Jan 2010 16:09:08 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201001271509.o0RF97fO015438@fs4113.wdf.sap.corp>
To: DPKemp@missi.ncsc.mil (Kemp, David P.)
Date: Wed, 27 Jan 2010 16:09:07 +0100 (MET)
In-Reply-To: <201001271440.o0REeTJU015911@stingray.missi.ncsc.mil> from "Kemp, David P." at Jan 27, 10 09:39:34 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal05
X-SAP: out
Cc: tls@ietf.org
Subject: Re: [TLS] Chatter on consensus
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mrex@sap.com
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2010 15:08:56 -0000

Kemp, David P. wrote:
> 
> As noted earlier, I think -03 has already gotten it right in
> terms of normative requirements -- MUST NOTs.  I have no position
> on whether informative text should continue to be refined.

These two MUST NOTs and the two unexplained NOT RECOMMENDEDs
to which I'm opposed are clear violations of rfc-2119 section 6:

http://tools.ietf.org/html/rfc2119#section-6

6. Guidance in the use of these Imperatives


   Imperatives of the type defined in this memo must be used with care
   and sparingly.  In particular, they MUST only be used where it is
   actually required for interoperation or to limit behavior which has
   potential for causing harm (e.g., limiting retransmisssions)  For
   example, they must not be used to try to impose a particular method
   on implementors where the method is not required for
   interoperability.


-Martin