Re: [TLS] Recommended yes->no for max_fragment_length extension?
Eric Rescorla <ekr@rtfm.com> Wed, 07 February 2018 20:56 UTC
Return-Path: <ekr@rtfm.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 5823D128959 for <tls@ietfa.amsl.com>; Wed, 7 Feb 2018 12:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 nTNzm2KlxG9f for <tls@ietfa.amsl.com>; Wed, 7 Feb 2018 12:56:12 -0800 (PST)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::22a]) (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 4DA97127863 for <tls@ietf.org>; Wed, 7 Feb 2018 12:56:12 -0800 (PST)
Received: by mail-yw0-x22a.google.com with SMTP id x190so1057458ywd.10 for <tls@ietf.org>; Wed, 07 Feb 2018 12:56:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pwcGnUYiIGixINWceBzN5sl3DnGaDsRTkHH2hJnelUY=; b=w/P72H0aGoQQ/IzF28oWA18RoMRHA8XIZVZpX51kYZFxO44sjvk9pMnJDOQco+IOEC 62zAL2M7KMRZ8/nfxA3XQ4xkd3jl9HiOH3/s7mWqO85VFSN+IWuBcvXDPcI/bTb7u5jc Ax91ddI2GJcjDbDLneNPxs8DIRlT/ikCbvrLJpg7V9bqjrwYSmnDT+XQSkYWOIvgqvuo BuDi1NbUpc5biEmAEHh1YzQSBiIBdQAls6ucGL9q9lEzbJwpE0Te4/0cbITm3gSeEtOh AXumnDdB7n3PWpjAUTVu6RgiugV042MJUMWQeFa0oEviV2LPJUDgbjuwZYm+0GAgN1i9 MSTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pwcGnUYiIGixINWceBzN5sl3DnGaDsRTkHH2hJnelUY=; b=b81YB40suVnKle9AbgUu10me2MKlrqzkE/b1rsVSI29Tm494DwaxpYoxg5XsRSTClH 5zCqSh+rEx+fEZg/PAg2vmg5RWmE1tWMk6FlZEoKFI1BTw8dXg3dVKV3flQ7tTCJvIxV p6rRCtmS1YSX6f69Fv1PKLsWQUU/TnCwwNflUf4pylcJeROYgZNvL6kvZcb68mYeIxFd 2N/WCnvlzdrqZNQBu9aCFeFVf+gKbFqxJOuHyfVESa2wDwRvKsJtXFrjll+8hIZHN0Q5 wB7pbCT5g73mljOCv9lzj2H43kzkf4TjgHmY+7YKwlc8PH3Dj7cBTJoDjH39XhZQs+U6 JTNw==
X-Gm-Message-State: APf1xPBZj+QedYzEI/H9cIHlV5X4sipynApUerBp3USNBgswkfIwf/D5 XQEGRyevrwAM5M/Wc0S9c4ckZZdq+ONVefhVv0iv7EEb
X-Google-Smtp-Source: AH8x225TWO+mdyrM1Z6pJ32Y1v6nLeypdE2eoitktRah8XgkONAZF+MrNhLH5esj2Oizn3S4AjJRo7NvbXkgS4RItFE=
X-Received: by 10.129.161.16 with SMTP id y16mr5000003ywg.2.1518036971329; Wed, 07 Feb 2018 12:56:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.160.201 with HTTP; Wed, 7 Feb 2018 12:55:30 -0800 (PST)
In-Reply-To: <0BD40460-F194-4A2B-8E7C-4FD2D084111B@sn3rd.com>
References: <0BD40460-F194-4A2B-8E7C-4FD2D084111B@sn3rd.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 07 Feb 2018 12:55:30 -0800
Message-ID: <CABcZeBOV1s8dpjxdCMhwnG1ZnEJQX7oSDFHn6W2wt6pq+9+D0Q@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: "<tls@ietf.org>" <tls@ietf.org>
Content-Type: multipart/alternative; boundary="001a114f89bc6eaf7e0564a5860e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/OAyGmjzQrDgNI0HdrW3LldZ3oCk>
Subject: Re: [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:56:14 -0000
I am for this change. -Ekr On Wed, Feb 7, 2018 at 12:33 PM, Sean Turner <sean@sn3rd.com> wrote: > 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/ > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls >
- Re: [TLS] Recommended yes->no for max_fragment_le… Eric Rescorla
- Re: [TLS] Recommended yes->no for max_fragment_le… Martin Thomson
- Re: [TLS] Recommended yes->no for max_fragment_le… Russ Housley
- [TLS] Recommended yes->no for max_fragment_length… Sean Turner
- Re: [TLS] Recommended yes->no for max_fragment_le… Russ Housley
- Re: [TLS] Recommended yes->no for max_fragment_le… Sean Turner
- Re: [TLS] Recommended yes->no for max_fragment_le… Sean Turner