Re: [TLS] Publication of draft-rhrd-tls-tls13-visibility-00

"Ackermann, Michael" <> Mon, 23 October 2017 16:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 9B91E138105 for <>; Mon, 23 Oct 2017 09:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.09
X-Spam-Status: No, score=-4.09 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id geG_tcoEWvoN for <>; Mon, 23 Oct 2017 09:39:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 68EEA1380DB for <>; Mon, 23 Oct 2017 09:39:09 -0700 (PDT)
Received: from (ZixVPM []) by (Proprietary) with SMTP id EE3EEC0DA6 for <>; Mon, 23 Oct 2017 11:39:08 -0500 (CDT)
Received: from (unknown []) by (Proprietary) with SMTP id 0B79BC0A19; Mon, 23 Oct 2017 11:39:08 -0500 (CDT)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id C5405FE04E; Mon, 23 Oct 2017 12:39:07 -0400 (EDT)
Received: from (unknown []) by IMSVA (Postfix) with ESMTP id 7E340FE048; Mon, 23 Oct 2017 12:39:07 -0400 (EDT)
Received: from (unknown []) by (Postfix) with ESMTPS; Mon, 23 Oct 2017 12:39:07 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-bcbsm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8+oqE1Euc7fZlfKyriVkfRLkt26Vml5vrzY09YRG8Us=; b=cPmhvQAhBHt3aci/j8VBq5fu87uR3/LUZAJdqcZTDRS8DNCq9wk9pZd87EAPbVgQ4RK83FrrFXpRuWD+JZ131E/bLgpOmQeuBk+YrrFFncXNV+OxycLaxST99oqmWWPnnhUaE7gTiCnT++J/uieyLIvf+t8cSGUgg56K3cQM1GA=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id; Mon, 23 Oct 2017 16:39:05 +0000
Received: from ([]) by ([]) with mapi id 15.20.0077.022; Mon, 23 Oct 2017 16:39:05 +0000
From: "Ackermann, Michael" <>
To: "Salz, Rich" <>, Ted Lemon <>
CC: "" <>
Thread-Topic: [TLS] Publication of draft-rhrd-tls-tls13-visibility-00
Date: Mon, 23 Oct 2017 16:39:05 +0000
Message-ID: <>
References: <> <> <> <> <000501d348e5$1f273450$5d759cf0$> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
authentication-results: spf=none (sender IP is );
x-originating-ip: []
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR14MB1366; 20:5jy0NdlGpmV19xwksphIZI/Nwf8E4nCPm2HrKMipr6i+xvrRpKgIEvcR2mDEFm53bZ4oO7IXUfGU/XMY/v4lHJWh1/r38MIrkU84nvdhxd4wqIJPNhSYjlRRGyAhC9nXpWV+YS8HqJqObLKFTaoKOaUHqopIgQhe+Ee0exoljNs=
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 01f90394-7e37-4c87-ba02-08d51a34937c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627075)(201703031133081)(201702281549075)(2017052603199); SRVR:CY4PR14MB1366;
x-ms-traffictypediagnostic: CY4PR14MB1366:
x-exchange-antispam-report-test: UriScan:(158342451672863)(21748063052155)(86572411397741);
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(5005006)(8121501046)(3002001)(100000703101)(100105400095)(3231020)(93006095)(93001095)(10201501046)(6041248)(20161123555025)(20161123564025)(20161123562025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR14MB1366; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR14MB1366;
x-forefront-prvs: 046985391D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(199003)(189002)(6306002)(6246003)(54356999)(9686003)(54896002)(55016002)(33656002)(6116002)(102836003)(230783001)(86362001)(76176999)(790700001)(99286003)(7696004)(50986999)(66066001)(106356001)(3846002)(74316002)(5660300001)(2950100002)(478600001)(53936002)(6506006)(72206003)(101416001)(97736004)(77096006)(105586002)(14454004)(2906002)(68736007)(8676002)(2900100001)(189998001)(7736002)(80792005)(25786009)(53546010)(8936002)(6436002)(4326008)(3280700002)(81166006)(81156014)(110136005)(229853002)(3660700001)(316002)(93886005); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR14MB1366;; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR14MB1368378B42A6C46B27F5EF01D7460CY4PR14MB1368namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Oct 2017 16:39:05.6589 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6f56d3fa-5682-4261-b169-bc0d615da17c
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR14MB1366
X-VPM-GROUP-ID: f1d5b9a5-9679-4b8b-ad90-5c4e202a7ca2
X-VPM-MSG-ID: 545831fd-651c-4a37-a7e9-3bb7650f9a4c
Archived-At: <>
Subject: Re: [TLS] Publication of draft-rhrd-tls-tls13-visibility-00
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Oct 2017 16:39:12 -0000

Thanks Rich
I have seen these suggestions previously.
But as numerous messages on this chain, from various people have discussed, neither  of those suggestions are viable from an Enterprise Architecture planning perspective.

  1.  If staying with TLS 1.2 indefinitely was considered acceptable,  would we even be having these discussions?
  2.  Modifying Server,  application and logging infrastructure is a huge, expensive proposition,  that executive management would not be receptive to at all.   Not to mention the logistics to follow if they were.

From: Salz, Rich []
Sent: Monday, October 23, 2017 12:27 PM
To: Ackermann, Michael <>;; Ted Lemon <>;
Subject: Re: [TLS] Publication of draft-rhrd-tls-tls13-visibility-00

  *   I am merely trying to understand if there are any constructive suggestions amongst all these discussions, that we should consider.

Yes.  To repeat myself, here are two:

  1.  Continue to use your existing schemes. You won’t have to change to TLS 1.3 for years.
  2.  Modify your servers and logging infrastructure to report-out the PFS keys and use them

Do you need me to post links to my messages?

The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.