IETF Logo Mail Archive

Re: [TLS] Publication has been requested for draft-ietf-tls-oldversions-deprecate-05

Rob Sayre <sayrer@gmail.com> Thu, 10 October 2019 17:45 UTC

Return-Path: <sayrer@gmail.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 057E31200F6; Thu, 10 Oct 2019 10:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Hx34WaxS8ygx; Thu, 10 Oct 2019 10:45:26 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 71762120115; Thu, 10 Oct 2019 10:45:26 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id a1so15644106ioc.6; Thu, 10 Oct 2019 10:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CHkOi3h9ra1tIFk26LVUfdQXrHbBU02sMwvED6B4ZH4=; b=e9kbqBCtSgIH0jm86Mt5LK0mOfM1TVxJjq7JlxLDtliUaCot0DuMGtrqp9P6GCPdbv z32RZa9Tydc3STxillGW7H6gp3qPzbnkTXIG4JIfRZ22jQ9vynuI4RMEGvUx/axKuPNy Go1I99YHGy+9G7cOogq9oIC7hsVM7myZzJEFVYV9GxqCx+tqMBoZ7FlX97dNyMoo7Dvm VhK9b7v8M6icTzwi2ncE+bNrZ5tn3YMq1iBGl+qznAp7mrKda9UIXR1KHAFeGHRorzc7 NDiJZFFXi9QrZ+w8KIKf1Hyo6Da6PEJDJQKPsfE8lIJOxUtwuV21WbXbYcbk9qjfrWLj 39Ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CHkOi3h9ra1tIFk26LVUfdQXrHbBU02sMwvED6B4ZH4=; b=ZfxwoTQu0pZJorlg04xXlv1zbMjcK5Ke9dx7+JePmTUxjpzjp9KGwgnt5Yh7QHYPYU TKTfP8VrB//N44SXR+TEd/Hj7cZzlvpQZbCHLD/fteheVSvBel8BNnkR6GOmrp+tO0qE TSmDlpph4zuHMKKHgs71wLTn8KjM1ZF2J69LCbhN4bW4aYYHF79CDFBAkmMLGxKBfe8L 9acOyPuNtnzqCZUVReHLipELXK8Gj7I5tjIUeErXizfd045Wp6CPEa+sCKHqEkBB6FYy +f3wQqnc9qA6hLpx2GYEBEnfGfvdjjQLWGpU/hYkhkZR3nDqx1VcFR6MZgu7nPMmIb2A QnnA==
X-Gm-Message-State: APjAAAV2KI0i3jx9UGgrV1b6eUpeQ5MBUGHDghaAm9U+YvbQGR2cqVJh HoK+MOUzORK/IpW0K/58ulxcMSeNII/i0df7BYw=
X-Google-Smtp-Source: APXvYqxTpSM4VvLktpOLpbVAva1BdAk554TZk/k/LwQbLNtyWoF09bFkG98+05XExiZxXO5uK2E/woEE3k96wjQp2j0=
X-Received: by 2002:a5d:9297:: with SMTP id s23mr12323777iom.49.1570729525648; Thu, 10 Oct 2019 10:45:25 -0700 (PDT)
MIME-Version: 1.0
References: <6F040DD1-C2E2-4FD2-BB37-E1B6330230BD@ericsson.com> <149BDA3C-14CF-459F-90D4-5F53DBEF9808@iii.ca> <CAChr6Sx4AVjkoKWiD2-cT2ZBNg=mKzeOX603gVs0f7vQ_FgN7A@mail.gmail.com> <CABcZeBNOVOBifOSnWdxSDTLizUUUn6ctLrBT43CHK+4B7KWGiQ@mail.gmail.com> <CAChr6SzT3GqmidPbmVjmrZX=u1UpBee4e8K2C-zHuNHEqgB7uQ@mail.gmail.com> <CABcZeBOGjPYy9FaOzaf-bHKaoMtXpO0SjQO5RTx9fMUo3r8vUg@mail.gmail.com> <CAChr6SwjdhpL2jQgNVjjuLosa8ycZEi9rGHuZ=K8=ToRy-gfJw@mail.gmail.com> <858a91dc-eb59-de20-4abb-7845d55f8a1b@cs.tcd.ie> <20191008120506.GF76545@kduck.mit.edu> <CAChr6SyhpUWoyhDiCp-UQ49HYVK-=Mk8DdXSpcAGK9hm+p00MQ@mail.gmail.com> <20191010161657.GA76545@kduck.mit.edu>
In-Reply-To: <20191010161657.GA76545@kduck.mit.edu>
From: Rob Sayre <sayrer@gmail.com>
Date: Fri, 11 Oct 2019 00:45:11 +0700
Message-ID: <CAChr6SyLUxj8Niu4d4TeGeyb4SxH1o+w3KE6PHob3=TX3-cnAA@mail.gmail.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Eric Rescorla <ekr@rtfm.com>, Sean Turner via Datatracker <noreply@ietf.org>, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, "tls@ietf.org" <tls@ietf.org>, IESG Secretary <iesg-secretary@ietf.org>, "tls-chairs@ietf.org" <tls-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006a223f059491f712"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/CietKXAAOn2I-ac5_TRYlr5rr50>
Subject: Re: [TLS] Publication has been requested for draft-ietf-tls-oldversions-deprecate-05
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 10 Oct 2019 17:45:28 -0000

On Thu, Oct 10, 2019 at 11:17 PM Benjamin Kaduk <kaduk@mit.edu> wrote:

> The decision about
> whether to make changes to the technical content thus lies with the
> sponsoring AD for that document.
>
>
I don't think that is true. Here is one comment from the document shepherd:
https://mailarchive.ietf.org/arch/msg/tls/GfbxWMXoSufeAozlzs7i-Tv-MV0

This one of those situations where the IETF rules are deliberately
ambiguous (I know most of the rules...).


> I disagree that draft-ietf-tls-oldversions-deprecate needs to update all
> consumers of DTLS 1.0/1.2, at least for the reason you give.  Those
> documents properly refer to RFC 6347 (or 4347), and it is that RFC that we
> are updating now.  We do not directly change those consuming documents'
> needs, but rather do so indirectly.
>

That is not what the draft does. For example, it updates RFC 4823, "FTP
Transport for Secure Peer-to-Peer Business Data Interchange over the
Internet".

Have you read the draft?


> from the IETF perspective
> it's approved and done, and the barrier to making any further substantive
> changes is extremely high.
>

Nope, it can get changed. And it can get updated too. It's just a text
file, and the rules are fluid. :)

thanks,
Rob

v2.23.0 | Report a Bug | By Email