Re: [TLS] MUST <x> or what?

Peter Gutmann <pgut001@cs.auckland.ac.nz> Fri, 28 August 2015 04:24 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9787A1B2CBB for <tls@ietfa.amsl.com>; Thu, 27 Aug 2015 21:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TidH9uyIesYQ for <tls@ietfa.amsl.com>; Thu, 27 Aug 2015 21:24:43 -0700 (PDT)
Received: from mx4.auckland.ac.nz (mx4.auckland.ac.nz [130.216.125.248]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42E791B2CA8 for <tls@ietf.org>; Thu, 27 Aug 2015 21:24:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1440735884; x=1472271884; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=OSwy2jBIdkf14WM68X+b1jUKTb3XANo8WX/wt9nP960=; b=zevZugXfozLIdZlOxN8/BMOEQeEwG1EAlNLRGqqZ+aHQK1OLcfRGnZe5 lNXbhuTp4U2DWKMHYZAxFMe6sRl9tvHuZW/jp4+FChrsAewWbiIl//OCt fDUNdp44dELj1YBOT0yO5KWrHHSlpnDu6DbHN16URpP5zIOO3TxW0Sq9G TEhQ/R/sTfowL+ThrHPNkG0SLk5ogjGK4KUVxubdr0JTnj8rIM07W6btQ CqemuwpBzYDQL4Nfv2zEd8+Rrfcex8smzNsn8M/0CJYaiEB4gI5aJkpZ7 XEYPs1rrCoXJ/j5wYOCPwXAglxk1lJk17UJc5YzfugGlZt56eerqbou5L g==;
X-IronPort-AV: E=Sophos;i="5.17,424,1437393600"; d="scan'208";a="38271944"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.112 - Outgoing - Outgoing
Received: from uxchange10-fe1.uoa.auckland.ac.nz ([130.216.4.112]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 28 Aug 2015 16:24:38 +1200
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.48]) by uxchange10-fe1.UoA.auckland.ac.nz ([130.216.4.112]) with mapi id 14.03.0174.001; Fri, 28 Aug 2015 16:24:37 +1200
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Martin Thomson <martin.thomson@gmail.com>, Dave Garrett <davemgarrett@gmail.com>
Thread-Topic: [TLS] MUST <x> or what?
Thread-Index: AQHQ4Pj2LgOoeHtO7kayfT/An/ayC54fb5KAgAABvoCAAAcqAIAABAsAgAFUHYQ=
Date: Fri, 28 Aug 2015 04:24:36 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73F4AE9CFB@uxcn10-5.UoA.auckland.ac.nz>
References: <CABkgnnXFyuf_3pPs8ByJpbOGgPDb2XMfVOZAUA42bmJEB_Vynw@mail.gmail.com> <201508271519.49848.davemgarrett@gmail.com> <CABcZeBM5SiO1dh2YxkLcmgspYm-Ug3p_mWs_OypKiHcK-iqD_w@mail.gmail.com> <201508271551.42561.davemgarrett@gmail.com>, <CABkgnnXkta_mHK_k6a+RuDLnH1YFJSbjKQ+2SgF6QmEzLM6OTA@mail.gmail.com>
In-Reply-To: <CABkgnnXkta_mHK_k6a+RuDLnH1YFJSbjKQ+2SgF6QmEzLM6OTA@mail.gmail.com>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/rycxO_xh_0TWd_8d8Sxi_q7wLDk>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] MUST <x> or what?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 28 Aug 2015 04:24:46 -0000

Martin Thomson <martin.thomson@gmail.com> writes:

>An endpoint that receives an illegal combination of "things" MAY choose to 
>treat that as a fatal error.

Does that actually help?  What it's saying in full is:

  An endpoint that receives an illegal combination of "things" MAY choose to 
  treat that as a fatal error or MAY choose not to treat it as a fatal error.

which is a no-op.  Admittedly it explicitly allows you to treat it as an error 
while previously the response was left open, but it's still not terribly 
useful, anyone writing a client that submits gibberish things can claim it's 
OK and the server needs to be fixed to accept it.

Peter.