Re: [TLS] TLS Impact on Network Security draft updated

"Ackermann, Michael" <MAckermann@bcbsm.com> Wed, 24 July 2019 03:17 UTC

Return-Path: <mackermann@bcbsm.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 82CA912008A for <tls@ietfa.amsl.com>; Tue, 23 Jul 2019 20:17:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (1024-bit key) header.from=MAckermann@bcbsm.com header.d=bcbsm.com; dkim=pass (1024-bit key) header.d=bcbsm.com header.b=bWZukGZ3; dkim=fail (1024-bit key) reason="fail (body has been altered)" header.d=bcbsm.onmicrosoft.com header.b=URs884EH
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 E2ETkNIteFki for <tls@ietfa.amsl.com>; Tue, 23 Jul 2019 20:17:48 -0700 (PDT)
Received: from mx.z120.zixworks.com (bcbsm.zixworks.com [199.30.235.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B90E120046 for <tls@ietf.org>; Tue, 23 Jul 2019 20:17:48 -0700 (PDT)
Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with SMTP id 62EB41C464A for <tls@ietf.org>; Tue, 23 Jul 2019 22:17:47 -0500 (CDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ZIXVPM1670e2ded26; d=bcbsm.com; h=From:To:Subject:Date; b=ZpS6Pgb9Yx0ueK5Xu7XTzXQklxCLitaXTJhl+5mA4Bd9yJKpAUw9foZfuizv/kSz 8fC2G3c/E0JgGnjVCidlbxS3CCZu571KuxqoGCTQd0Zixj7A/w+0pxyl1mww0H jCV04cTyAn1DiUtIy1tR58lC7FPQVMs6NIQPQcg9mZL2Q=;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bcbsm.com; s=ZIXVPM1670e2ded26; t=1563938267; bh=Ri4ok9iUxxuE5vc2i26r+mvGny1cdJHPVeftmU6bZYw=; h=From:To:Subject:Date; b=bWZukGZ32UUVVWgjMdVOAbtivCW1ZSfEvVPh8Rkm5VZ1WAzU9AAgdzjloLS+a2uqY GIOSRus8jhFrWDXwAmy6JWpkveXndGRlVEoTpsHOALaEOgWvJC5LE4Q1d2JeErmiCA pWpPHI6RV3nyV/uha3IyCtLuZeJ/ALmEV8WoRQhw=
Received: from imsva2.bcbsm.com (inetmta04.bcbsm.com [12.107.172.81]) by mx.z120.zixworks.com (Proprietary) with SMTP id 171FC1C4646; Tue, 23 Jul 2019 22:17:46 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D0E2EFE04E; Tue, 23 Jul 2019 23:17:45 -0400 (EDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 866D9FE055; Tue, 23 Jul 2019 23:17:45 -0400 (EDT)
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (unknown [104.47.50.57]) by imsva2.bcbsm.com (Postfix) with ESMTPS; Tue, 23 Jul 2019 23:17:45 -0400 (EDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nYWRFMxVDWhRe4n+JFmQX5GaUnObH5lC+el3ffkhfN9tyQADw4oJ0sdzcZRUdx+p1fRN1MjfnTKDU3hwTZtTQ2qrjbmKApPKTZ47ye4f9ZNVrrIUZOoUpCeOQjPNY8uifZXsiOHaZcZZsffx5BN029TJNEWRC7gz609I3Q/OA3W+UnzxzYu6seEdC0dQc2b/1mA10iIPp/lMSC5W4vDj5//1XJ59E/G6f03pl1NCy7AfFAHQVDngH5xTxP5B9GbEsORuKk3GgIpwWqSwINqxcdvWXmbhYdRbtv9s8IM033u5UvBk/JJPW2b8cNiv5GA0B6CqNXMpEzRaz1ITtC5GMg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pQu2QjY3HSYh5Oyvrj6ibrb0EmBo03nCsFHZc+FsbX0=; b=IV3omwzt/Nt/vSooxo/JGEnW2837clVLCk7isCn8YTFFi5FmJY+441wZ5CdvIK2GI+qTkvU7nvxcTQK0gbiB4Zl5iflGWL9KkagTYNWY1d2LUlIXw/DViqSt3gxdB5Apm2QR5wWPpLBnReNRERGVHOVsAFapIUdzvjy9TP2wPpD3G+3T9Uza68Ksb8hYIFuGejJSZFu0s8rjWN84WCbLfNa5KQsoqzwQaX1X8xVaZx10U3Ch7HKtvBBreZgqDF118dRHcEp794GHTq+JBWjH7NpBbTGju7lT6HBhzHJCFySTEadozHM2MbDn4F7N+MXVYOnL+ahefxW2PUNOBYHCJA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=bcbsm.com;dmarc=pass action=none header.from=bcbsm.com;dkim=pass header.d=bcbsm.com;arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bcbsm.onmicrosoft.com; s=selector1-bcbsm-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pQu2QjY3HSYh5Oyvrj6ibrb0EmBo03nCsFHZc+FsbX0=; b=URs884EHnS7cdgaif2kBU17agz2OzsFvx4TIFhs+8LuOYLMj5xY3fN9dv4qguoJ5EibR+V+a7+PvSxQfScxubmlF1RMoJvunOdPtctpap2pnHynkKI8dvZkoYAT9u6joP5C2p0uismPnXotS2GPN280FoKVoQOQGwB4d7qRx/SY=
Received: from DM6PR14MB2474.namprd14.prod.outlook.com (20.177.221.205) by DM6PR14MB2540.namprd14.prod.outlook.com (20.178.30.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.10; Wed, 24 Jul 2019 03:17:38 +0000
Received: from DM6PR14MB2474.namprd14.prod.outlook.com ([fe80::168:5560:a095:93e3]) by DM6PR14MB2474.namprd14.prod.outlook.com ([fe80::168:5560:a095:93e3%7]) with mapi id 15.20.2094.013; Wed, 24 Jul 2019 03:17:38 +0000
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Watson Ladd <watsonbladd@gmail.com>, Filippo Valsorda <filippo@ml.filippo.io>
CC: TLS List <tls@ietf.org>
Thread-Topic: [TLS] TLS Impact on Network Security draft updated
Thread-Index: AQHVP8tnovYBmAyQbUu5TybMCHUv66bY0WiAgAADLgCAAEc1gA==
Date: Wed, 24 Jul 2019 03:17:37 +0000
Message-ID: <DM6PR14MB24745D7DDD5F1503387A7694D7C60@DM6PR14MB2474.namprd14.prod.outlook.com>
References: <6AF48228-19C2-41C7-BA86-BA16940C3CFF@cisco.com> <77d58a41-7a6b-4886-a4d4-22dcb229100b@www.fastmail.com> <CACsn0cmxuUTxAGxdmmtyg7BX0GPJLht343CRcFrakLvsbKM2zQ@mail.gmail.com>
In-Reply-To: <CACsn0cmxuUTxAGxdmmtyg7BX0GPJLht343CRcFrakLvsbKM2zQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=MAckermann@bcbsm.com;
x-originating-ip: [165.225.39.74]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 11cb08c5-9582-4f08-76a7-08d70fe57b2f
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600148)(711020)(4605104)(1401327)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7167020)(7193020); SRVR:DM6PR14MB2540;
x-ms-traffictypediagnostic: DM6PR14MB2540:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <DM6PR14MB254079B94039398BFD7C699DD7C60@DM6PR14MB2540.namprd14.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0108A997B2
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(366004)(136003)(346002)(39860400002)(199004)(189003)(478600001)(11346002)(7696005)(446003)(52536014)(26005)(256004)(110136005)(790700001)(74316002)(14444005)(476003)(6116002)(4326008)(486006)(5024004)(3846002)(66066001)(316002)(186003)(8676002)(33656002)(81166006)(81156014)(2420400007)(55236004)(99286004)(6306002)(71200400001)(53546011)(66946007)(71190400001)(76116006)(86362001)(9686003)(54896002)(8936002)(6506007)(66446008)(66476007)(64756008)(66556008)(53936002)(6436002)(55016002)(6246003)(68736007)(25786009)(7110500001)(15650500001)(5660300002)(236005)(80792005)(14454004)(2906002)(7736002)(76176011)(229853002)(102836004); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR14MB2540; H:DM6PR14MB2474.namprd14.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: bcbsm.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: nSi6mRDGdULU6hlhimXwd/bgTtaUxtfPRrHt/lfG/vN6O1NykPwLnrIvLPBkH76at9rjrOcvi5mTKOmRfK1pqtqBPQ2hMFm5HUgdPeu4WrCjLB7Q9PWm8V/51FI894bkCXu56CKsLnHwo3Pe8p+qI3v9l4Eb3KGpgIcrdjymBvEBx1v3tFr0q/5z981qIrfnB53QUDWl48kDuw/JdUvX34P/GsO+ewZcg4MI1o0vPcTC/My1mKoRlgNrjcbmXjbx/L2ohaM8FPLaG4ea0nU7fbwFWyddAySRkA35R8gFX5Nv+QslEov6JRSZNV4ZRQwsQPCVG8eaVzeg/A8U+6ZxAh26Rsg11V5zDssBJWcckej/+/V2DJjpP1qaxc6M96TzVRBaOTt5TE3uAVCbKd2nSZe4f6rFq+m/3Ne32UcmUSo=
Content-Type: multipart/alternative; boundary="_000_DM6PR14MB24745D7DDD5F1503387A7694D7C60DM6PR14MB2474namp_"
MIME-Version: 1.0
X-OriginatorOrg: bcbsm.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 11cb08c5-9582-4f08-76a7-08d70fe57b2f
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jul 2019 03:17:38.0362 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 6f56d3fa-5682-4261-b169-bc0d615da17c
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: MAckermann@bcbsm.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR14MB2540
X-TM-AS-GCONF: 00
X-VPM-HOST: vmvpm01.z120.zixworks.com
X-VPM-GROUP-ID: 71daa57b-8dd6-4262-8f05-019fdb0a8c8e
X-VPM-MSG-ID: 1adc64d9-629f-480b-af97-3be8aad34729
X-VPM-ENC-REGIME: Plaintext
X-VPM-IS-HYBRID: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/5Ow-vuIwkn5OPd4SvDFnmU6FKag>
Subject: Re: [TLS] TLS Impact on Network Security draft updated
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: Wed, 24 Jul 2019 03:17:51 -0000

This should not be dismissed as small segments of industries.    This represents ubiquitous use cases at all large organizations in Insurance, Health Care, Banking, Automotive and many others.
We as the IETF should not lightly dismiss such significant numbers and volume, even (or especially),  if the answers are not easy ones.    Do we really want related solutions to be developed elsewhere?

From: TLS <tls-bounces@ietf.org> On Behalf Of Watson Ladd
Sent: Tuesday, July 23, 2019 6:58 PM
To: Filippo Valsorda <filippo@ml.filippo.io>
Cc: TLS List <tls@ietf.org>
Subject: Re: [TLS] TLS Impact on Network Security draft updated

 ALERT This email was sent from a source external to BCBSM/BCN.
 DO NOT CLICK links or attachments unless you recognize the sender and trust the content.


On Tue, Jul 23, 2019, 3:47 PM Filippo Valsorda <filippo@ml.filippo.io<mailto:filippo@ml.filippo.io>> wrote:
Before any technical or wording feedback, I am confused as to the nature of this document. It does not seem to specify any protocol change or mechanism, and it does not even focus on solutions to move the web further.

Instead, it looks like a well edited blog post, presenting the perspective of one segment of the industry. (The perspective seems to also lack consensus, but I believe even that is secondary.) Note how as of draft-camwinget-tls-use-cases-05 there are no IANA considerations, no security considerations, and no occurrences of any of the BCP 14 key words (MUST, SHOULD, etc.).

Is there precedent for publishing such a document as an RFC?

I was going to say RFC 691 but no, it recommends changes to the protocol (as well as being quite amusing). RFC 4074 comes close describing bad behavior without an explicit plea to stop doing it, but has a security considerations section. RFC 7021 describes the impact of a particular networking technique on applications.

So there is precedent.

Sincerely,
Watson


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.