Re: [TLS] [Last-Call] Last Call: <draft-ietf-tls-oldversions-deprecate-09.txt> (Deprecating TLSv1.0 and TLSv1.1) to Best Current Practice

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 04 December 2020 15:22 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 EF5A03A0E57; Fri, 4 Dec 2020 07:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, NICE_REPLY_A=-0.001, 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 (1024-bit key) header.d=cs.tcd.ie
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 VxZo6feMuyNV; Fri, 4 Dec 2020 07:22:05 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E0E53A0E1A; Fri, 4 Dec 2020 07:22:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2366CBE4D; Fri, 4 Dec 2020 15:21:59 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQs1rHIhgzMx; Fri, 4 Dec 2020 15:21:57 +0000 (GMT)
Received: from [10.244.2.119] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 3EA81BE50; Fri, 4 Dec 2020 15:21:57 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1607095317; bh=5hM82oYKviR3QcP14VyG/jINu8Em5tAyHfZ0lLd43ys=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=uj6t4TFJAwCXwePpqzREiQIU1AAQ1OWfvHmXUMRjzwN62YzsbnwyyjnSEJZsG2TuG aTiBWMGXt67csLyiTwIou/k0MkFBjNwGu/EolCcjQKpE9/80SYUIqcohJCBjIqS9Bg WNQPQDk1ifHUxQd8XN+C3584azA1LS3Gy4cTuZJo=
To: "Ackermann, Michael" <MAckermann@bcbsm.com>, "BRUNGARD, DEBORAH A" <db3546@att.com>, Rob Sayre <sayrer@gmail.com>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, Peter Gutmann <pgut001@cs.auckland.ac.nz>, "STARK, BARBARA H" <bs7652@att.com>, Watson Ladd <watsonbladd@gmail.com>, "draft-ietf-tls-oldversions-deprecate@ietf.org" <draft-ietf-tls-oldversions-deprecate@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "tls-chairs@ietf.org" <tls-chairs@ietf.org>, "tls@ietf.org" <tls@ietf.org>
References: <160496076356.8063.5138064792555453422@ietfa.amsl.com> <SN6PR02MB4512B95842251AE4C04B199CC3F30@SN6PR02MB4512.namprd02.prod.outlook.com> <BYAPR14MB31765FD24F4DFD90F81AEE2BD7F30@BYAPR14MB3176.namprd14.prod.outlook.com> <SN6PR02MB4512CBA9E4BF6AAC778BC674C3F30@SN6PR02MB4512.namprd02.prod.outlook.com> <DM6PR14MB31789349B737961728B7691ED7F30@DM6PR14MB3178.namprd14.prod.outlook.com> <CACsn0ckvoqZ5-JPRkOXp2Mw2zeTOdyCYLvX1NV1waJ-yidTwMQ@mail.gmail.com> <SN6PR02MB45129E647485BA5794D5CF4EC3F20@SN6PR02MB4512.namprd02.prod.outlook.com> <MWHPR02MB2464CD5D5B7568E9EAC58B26D6F20@MWHPR02MB2464.namprd02.prod.outlook.com> <DM6PR14MB3178EC0521427BF7C3523CACD7F10@DM6PR14MB3178.namprd14.prod.outlook.com> <CAChr6SzvQK+exfgYEwfVNknMjr-Y-UJ4A7k0DkOkL9wmLQ84aQ@mail.gmail.com> <MWHPR02MB246499F35613820D45EB55AAD6F10@MWHPR02MB2464.namprd02.prod.outlook.com> <DM6PR14MB3178A0C152A746E41C6A01C6D7F10@DM6PR14MB3178.namprd14.prod.outlook.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Message-ID: <f8486514-9726-68d0-2bc8-dccd4293017e@cs.tcd.ie>
Date: Fri, 4 Dec 2020 15:21:55 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <DM6PR14MB3178A0C152A746E41C6A01C6D7F10@DM6PR14MB3178.namprd14.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Ht8BAX0yUmkXo4Um3TmM9sHdZhOkRpLMT"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/J0fAJX5auWQId5AXWZAarm8ME_o>
Subject: Re: [TLS] [Last-Call] Last Call: <draft-ietf-tls-oldversions-deprecate-09.txt> (Deprecating TLSv1.0 and TLSv1.1) to Best Current Practice
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: Fri, 04 Dec 2020 15:22:14 -0000

Hi Michael,

On 04/12/2020 15:14, Ackermann, Michael wrote:

> We (Enterprises) are not as involved as we should be in IETF, and
> that is our own problem/fault. What I think irritates people like
> Stephen,

I'm not irritated at all:-)

> is that there have been situations where we finally try to
> get involved and provide input/use cases, etc., but at the 11th hour
> or after the ship has pretty much sailed.

Getting involved late is just something that happens when
one first gets involved in any new thing so is entirely ok.

If I was irritated (and I'm still not:-), what would have
caused that would be a claim that someone somehow represents
all "Enterprises" and that nobody else has a clue what may
be needed for such networks. I don't buy that at all and
I guess never will, because it just isn't correct.

Cheers,
S.


> 
> So as you say Deborah, I very much want to get more Enterprises
> involved in IETF initiatives,  but beyond that, being involved up
> front in the process (perhaps even making positive contributions
> OMG),  rather than only whining about deployment/operational issues
> on the back end.   (or explaining why they exist, which is
> essentially what I was doing on this issue ☹).
> 
> How to accomplish this is a challenge and I think that is what
> Barbara suggested taking off to the other list.
>