[TLS] Recommended yes->no for max_fragment_length extension?

Sean Turner <sean@sn3rd.com> Wed, 07 February 2018 20:34 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615DE12D863 for <tls@ietfa.amsl.com>; Wed, 7 Feb 2018 12:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 Y6cZTFWLpeF1 for <tls@ietfa.amsl.com>; Wed, 7 Feb 2018 12:34:02 -0800 (PST)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 061C512D86C for <tls@ietf.org>; Wed, 7 Feb 2018 12:34:02 -0800 (PST)
Received: by mail-qk0-x22b.google.com with SMTP id y204so2848386qkb.10 for <tls@ietf.org>; Wed, 07 Feb 2018 12:34:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=FGoQlmIyhBEwqORJ0mAEyUaOA55XTHT+GDLhwCWLgGY=; b=D85xRGV9bL2w6hGZsCRazwsjgPcDvmJvu14kIdXttaqqZAsdqx+nkzoOkK7kwbV0jg te3qO8YZ5rX/dwmUcTwQMQZSSSZE7F/UBGXHlcfBxhYMSy6QaV0CTcFqOKbwJ+vkksFO dLKrCkt0EGyIgnjo/tmiaoLjY9+pwOGBzr7bA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=FGoQlmIyhBEwqORJ0mAEyUaOA55XTHT+GDLhwCWLgGY=; b=J6CAWBaa0tJp0GlGI22YX2vYiAbRZiAX5QtCnRKLqJ/Y1BeiCk1ARMW1FW9AFxrHFK xkGpuN9mt0E5xSfyqZsLV3S/01kS2Ti0YqzJVeWrXd9zZb83aElbcagAZ1/VE034Wqao Lj7/aVETs4+KOFeAKKUfOPzuBl6SNXLGmvKoqZgWBzAAikxd6Twns3VHGQVX3ErKjbpi 603dzCaOjynawrOlEc/Buxx7laUWe4lVD6HskPhqaI8Kn2f8JW0l7SQK+taPAKORBQCF XPBCH1UgBdaMFAJ8dVjZdHMlk2zitu+r0m0NAKfDAOMv6qjleTcL0USF8UxVXilrcoWv bKYA==
X-Gm-Message-State: APf1xPD+9EXtAZYZD1sv3lpJ2t2rOzA9uHrkYg0ROre8mqHP9imSwj7I lHOU8/jJKTR6BagVDofqW4XUvekK3Es=
X-Google-Smtp-Source: AH8x224RsDD3jmxyDz52/xCtYZMULHdaXvg1ycKeaQRNfj6sEWAou7iSO2gmCfux2ErE1VXSo8BG3w==
X-Received: by 10.55.125.197 with SMTP id y188mr11180587qkc.111.1518035640914; Wed, 07 Feb 2018 12:34:00 -0800 (PST)
Received: from [172.16.0.18] ([96.231.218.194]) by smtp.gmail.com with ESMTPSA id u1sm1663553qtb.65.2018.02.07.12.34.00 for <tls@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Feb 2018 12:34:00 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <0BD40460-F194-4A2B-8E7C-4FD2D084111B@sn3rd.com>
Date: Wed, 07 Feb 2018 15:33:59 -0500
To: "<tls@ietf.org>" <tls@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/LE_qwYLvrIxOtORWwlOxxMMeXMM>
Subject: [TLS] Recommended yes->no for max_fragment_length extension?
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 07 Feb 2018 20:34:05 -0000

All,

Prior to pushing draft-ietf-tls-record-limit [0] to the IESG, the WG needs to confirm that draft-ietf-tls-record-limit should change max_fragment_length [1] from “Yes” in our soon to be created Recommended column (see [2]) to a “No”.  Please indicate by 2359 UTC on 14 Feb whether you are for or against this change; and if you are against please indicate why.

spt

[0] https://datatracker.ietf.org/doc/draft-ietf-tls-record-limit/
[1] https://datatracker.ietf.org/doc/rfc6066/
[2] https://datatracker.ietf.org/doc/draft-ietf-tls-iana-registry-updates/